On Sun, 20 Oct 2019 15:31:17 +0200 Alexandre Detiste <[email protected]> wrote: > Hi, > > > Is it prepared for the package "usrmerge" > > Not at all, and I don't plan to dig into the "cruft" engine to make it happen. > > I liked the idea behind cruft, that each file of a filesystem should > be accounted > to some package; but definitively not the original engine. > > That's why I wrote cruft-ng, give it a try. > This one is UsrMerge compatible. > > Is a "Breaks: cruft" in usrmerge package enough to please you ? > > It is lowest hanging fruit; there's certainly still much to do. > Still hoping that one day much of "cruft" functionality > would be merged into packages&dpkg. > > The cruft-common package shared accros cruft & cruft-ng with the > definitions wil remain. > > Le mar. 8 oct. 2019 à 21:33, Harry Haller <[email protected]> a écrit : > > My call of cruft: > > #cruft --ignore "/root /home /mnt /proc /sys /Dummy /Schafott /Pax /dev > > /lost+found /opt /run /srv /tmp" -r ~/Cruft.report > > Sorry but not all of this has been re-implemented yet in cruft-ng; > but the defaults are better (always ignore /sys /root /home /tmp) > and most are inherited from "mlocate" database. > > > Since more than 10 years (felt) the debian-users waste their lifetime > > with this - at best - "sid"-package. > > Nothing justifies, that cruft finds it's way always into whatever is stable at > > the moment. > > > > Please be consequent and kick it out of the stable releases until it works > > (some day in a distant future)... > > One could remove the "cruft" binary package and I wouldn't be the one > to complain; > as long a "cruft-common" is still built. > > I need more feedback.
Hello Alexandre,
With the usrmerge transition happening [0] we should revisit this.
Specifically, there's a failure case with aptitude:
# aptitude upgrade
Resolving dependencies...
The following NEW packages will be installed:
usr-is-merged{a}
The following packages will be upgraded:
init-system-helpers
1 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/54.5 kB of archives. After unpacking 12.3 kB will be
used.
Do you want to continue? [Y/n/?] n
Abort.
root@luca-desktop:/tmp# aptitude dist-upgrade
The following NEW packages will be installed:
usr-is-merged{a}
The following packages will be upgraded:
init-system-helpers
1 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
This happens because usrmerge conflicts with cruft, in case it is
installed manually. This is the wrong thing, as usr-is-merged simply
attests that the system is converted, so the upgrade will fail.
We could add a conflict in usr-is-merged as well, but that effectively
makes cruft uninstallable anywhere.
So, how about doing as you suggested and dropping the cruft binary
package? Or maybe make it a transitional metapackage, and then we can
make the conflict in usrmerge versioned? What do you think?
[0] https://lists.debian.org/debian-devel-announce/2022/09/msg00001.html
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
