Steve Dickson wrote:
> This makes sense but the reason the libnfsidmap-devel package is not
> be upgraded (or installed) is because:
>
> dnf install /tmp/libnfsidmap-devel*
> Last metadata expiration check: 0:10:48 ago on Fri 27 Oct 2017 11:19:35 AM
> EDT. Error:
> Problem: conflicting requests
> - nothing provides libnfsidmap = 2.2.1-0.fc28 needed by
> libnfsidmap-devel-1:2.2.1-0.fc28.x86_64
>
> even though libnfsidmap-2.2.1-0 is installed.
>
> The problem is caused by the Requires: in the libnfsidmap-devel subpackage
>
> %package -n libnfsidmap-devel
> Summary: Development files for the libnfsidmap library
> Group: Development/Libraries
> Requires: pkgconfig
> Requires: libnfsidmap = %{version}-%{release}
> ^^^^^^^^^^^
>
> Now if I remove the '%{version}-%{release}' the package
> is installed/upgraded... but seems wrong to me
> the -devel should be tied to a particular version, right?
>
> Plus this was the way it was in the original libnfsidmap rpm.
The versioned dependency must include the Epoch (which is 1), i.e.:
Requires: libnfsidmap = %{epoch}:%{version}-%{release}
Note that subpackages inherit the Epoch from the main package unless you
explicitly set Epoch: 0 in them (and you will probably not make rel-eng
happy if you set that now after you already pushed the packages with Epoch 1
into Rawhide, there was unfortunately a FESCo decision that EVRs (Epoch-
Version-Release versions) should never go backwards in Rawhide).
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
