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
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
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
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
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
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
6 matches
Mail list logo