Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)
On 2019-05-28 at 18:26:31, Andreas Beckmann wrote: > safe-rm also breaks a stretch --merged-usr chroot, found while testing > with piuparts stretch->buster upgrades with --merged-usr enabled. > And it seems to be the only package causing outright havoc in such a > scenario. So if I understand correctly, this is only a problem when testing with this tool, right? Because: (1) users can't upgrade their system to a merged-usr one on stretch and (2) the default for new stretch installs was not usr-merged. > While a proper solution is too involved for stable, it should probably > be OK for the preinst to check for merged /usr systems and error out if > installation is attempted in such a case - instead of leaving a broken > system. I'd be happy to see it "fixed" that way in stretch. I don't have a lot of free time at the moment to make the change myself but I would support such a NMU. Francois -- https://fmarier.org/
Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)
Followup-For: Bug #759410 Control: found -1 0.12-2 Hi, safe-rm also breaks a stretch --merged-usr chroot, found while testing with piuparts stretch->buster upgrades with --merged-usr enabled. And it seems to be the only package causing outright havoc in such a scenario. While a proper solution is too involved for stable, it should probably be OK for the preinst to check for merged /usr systems and error out if installation is attempted in such a case - instead of leaving a broken system. Andreas safe-rm_0.12-7.log.gz Description: application/gzip
Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)
On 2016-10-25 at 09:12:30, Sven Joachim wrote: > >> In order to fix this while preserving safe-rm's default of automatic > >> protection on installation, safe-rm will need to divert and replace > >> /bin/rm. This will require quite a bit of care to do safely; see dash's > >> maintainer scripts for a safe procedure. > > Merged /usr is the default since debootstrap 1.0.85, so the package > > is uninstallable on new systems. > > It's worse than that. Because dpkg does not detect the file conflict > between coreutils' /bin/rm and safe-rm's /usr/bin/rm, the package is > installable but wreaks havoc, replacing the rm binary with its symlink. I was hoping to fix 837925 first since molly-guard is already using dpkg-divert instead of bare symlinks but I don't see what's wrong with the way that molly-guard does things, so I don't know what's going to fix it for safe-rm too. Francois -- https://fmarier.org/
Processed: Re: Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)
Processing control commands: > severity -1 critical Bug #759410 [safe-rm] Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin) Severity set to 'critical' from 'grave' -- 759410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)
Control: severity -1 critical On 2016-10-23 01:24 +0200, Marco d'Itri wrote: > Control: severity -1 grave > > On Aug 27, Josh Triplett wrote: > >> In order to fix this while preserving safe-rm's default of automatic >> protection on installation, safe-rm will need to divert and replace >> /bin/rm. This will require quite a bit of care to do safely; see dash's >> maintainer scripts for a safe procedure. > Merged /usr is the default since debootstrap 1.0.85, so the package > is uninstallable on new systems. It's worse than that. Because dpkg does not detect the file conflict between coreutils' /bin/rm and safe-rm's /usr/bin/rm, the package is installable but wreaks havoc, replacing the rm binary with its symlink. Cheers, Sven
Processed: Re: Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)
Processing control commands: > severity -1 grave Bug #759410 [safe-rm] Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin) Severity set to 'grave' from 'important' -- 759410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
