-   Slackware (
-   -   Found minor package conflict: mountpoint(1) moved from sysvinit to util-linux (

Sl4ck3ver 08-10-2013 09:54 AM

Found minor package conflict: mountpoint(1) moved from sysvinit to util-linux
Beginning with util-linux 2.20 a new version of mountpoint is installed (in /bin).
This conflicts with the existing binary from sysvinit (in /usr/bin).

The accepted way is to maintain it now together with mount in util-linux.

Here is the original discussion which also includes a first draft version of a patch:

FYI: The development tree of sysvinit no more installs mountpoint by default.

Very nice if we could clean this up before 14.1!


Sl4ck3ver 08-10-2013 04:48 PM

There is another conflict, this time fsck in e2fsprogs. Also moved into util-linux.

[Seems reasonable for me since util-linux is essential, and it should contain the generic fsck demuxer.]


Opening another thread for this looks like overkill, so I simple reply to my own post here.
I'd surely posted this together with a slightly different subject, but I noticed it just now.

gnashley 08-12-2013 07:31 AM

The fsck 'conflict' has been there for a long time, IIRC.

Sl4ck3ver 08-13-2013 01:59 PM

Yes, you are right. Thanks for pointing this out.

My intention was to show the existing conflict somehow to the slackware team.
Just to make the coming Slackware 14.1 better than ever!

With the "minor" in the subject, I also meant: But don't panic now :-)
I also think in the past that was no big problem, the development was not very fast.

But this somehow changed with the merge of util-linux-ng starting with Slackware 14.0.
Now the features of these tools will go more and more out of sync in the future; it eventually
will become a problem for everyone during the whole life time of Slackware 14.1.

In the case of a new full install everything will be fine in the beginning as util-linux
is installed *after* all conflicting packages.
Ignoring net-tools here, since it is supposed to replace the basic binaries in util-linux.

The problem comes later in the form of "security fixes".
The install order of these conflicting packages is then turned around in an unforseeable way!

Hope you also see now what I meant...


mRgOBLIN 08-13-2013 04:47 PM

Hi Sl4ck3ver,

This is on the list of things to do.

Thanks =)

willysr 08-17-2013 02:38 AM

Now fixed on -Current :)

All times are GMT -5. The time now is 04:55 PM.