On Thu, Apr 05, 2018 at 12:21:45AM +0100, Sérgio Basto wrote:
On Sun, 2017-08-20 at 20:49 +0100, Sérgio Basto wrote:
> On Sun, 2017-08-20 at 18:49 +0000, Zbigniew Jędrzejewski-Szmek wrote:
> > On Sun, Aug 20, 2017 at 05:09:04PM +0100, Sérgio Basto wrote:
> > > On Sun, 2017-08-20 at 14:46 +0000, Zbigniew Jędrzejewski-Szmek
> > > wrote:
> > > > On Sun, Aug 20, 2017 at 05:16:54AM +0100, Sérgio Basto wrote:
> > > > > On Sun, 2017-08-20 at 03:26 +0000, Zbigniew Jędrzejewski-
> > > > > Szmek
> > > > > wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I pushed the changes and rebuilt the packages today.
> > > > >
> > > > > Hi,
> > > > > I got this [1] in log of wammu-0.43-1.fc28, so in [2] line 50
> > > > > you
> > > > > need
> > > > > replace
> > > > > Requires: %{name} = %{version}-%{release}
> > > > > by
> > > > > Requires: python2-%{name} = %{version}-%{release}
> > > > >
> > > > > isn't it ?
> > > >
> > > > Thanks. That's two bugs:
> > > > - the Provides for the old name without %{_isa} is missing
> > > > (Requires: %{name}%{_isa} is resolvable, but not Requires:
> > > > %{name})
> > > > - internal Requires should be updated to use the new name
> > > > (using the old name does not break anything in general, but
> > > > is
> > > > inelegant).
I found a 3rd bug , provides / obsoletes misses epoch
%{version}-%{release} needs be replaced by :
%{?epoch:%{epoch}:}%{version}-%{release}
where packages have epoch , IIRC this happens with python-blivet
I looked at python-blivet, and it wasn't modified as part of my mass update,
_and_ it looks all fine to me wrt. to epoch handling.
Zbyszek