On Wed, Nov 15, 2017 at 11:05 AM Karel Zak <kzak@xxxxxxxxxx> wrote:
On Tue, Nov 14, 2017 at 12:49:34PM +0100, Igor Gnatenko wrote:
> After removal[0] of other ancient Provides from coreutils, it is time[1] to
> remove next legacy part, /bin/* Provides.
Do you plan do the same cleanup for another packages? :)
For example util-linux:
grep 'Provides: /' util-linux.spec
Provides: /bin/dmesg
Provides: /bin/kill
Provides: /bin/more
Provides: /bin/mount
Provides: /bin/umount
Provides: /sbin/blkid
Provides: /sbin/blockdev
Provides: /sbin/findfs
Provides: /sbin/fsck
Provides: /sbin/nologin
coreutils needs special care because it provides two subpackages -- coreutils and coreutils-single -- which are identical in behavior but differ in Provides... and conflict with one another.
coreutils-single is often used in container images and other ultra-minimal deployments because it has a slightly smaller disk footprint (IIRC), whereas coreutils is slightly faster.
The problem we keep hitting is that some packages had Requires: on Provides: only offered by the coreutils package (and not by -single), which meant that trying to install that software on those minimal images would hit DNF conflicts and would need --allowerasing to succeed.
This effort is about unifying (and modernizing) their Provides:
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
