Undefined %epoch problem (Re: rawhide report: 20150730 changes)

[Michael Schwendt]

On Fri, 28 Aug 2015 16:36:51 +0200, Ralf Corsepius wrote:

> > See:
> >
> >    https://lists.fedoraproject.org/pipermail/devel/2015-August/213209.html
> >    https://lists.fedoraproject.org/pipermail/devel/2015-August/213208.html
> 
> Bugs ... an undefined epoch is supposed to be treated as 0.

No, that's the old case. No Epoch = Epoch 0.

Here it's an undefined %{epoch} macro in a versioned dependency,
making it a string that isn't expanded. It must not be treated as 0,
because that pretends the dependency resolves fine when in fact it
doesn't. The package cannot be installed. Only RPM notices it, and
the transaction check comes rather late in the game after downloading
lots of packages. Ugly.