Control: reassign -1 apt Hi!
On Wed, 2019-08-28 at 09:30:45 +0100, Mark Hindley wrote: > On Tue, Aug 27, 2019 at 08:26:30PM +0200, Julian Andres Klode wrote: > > > I suggest that --abort-after=1 should be apt's default when forcing > > > package > > > removal. This was a false lead and the wrong conclusion from an initially correctly diagnosed problem. :) Reducing the abort-after default would be an incorrect workaround. > > APT is the wrong place for that. We're trying to move to a future where > > we only tell dpkg all the actions to do and then run a single dpkg, so > > adding hacks like that feels counter-intuitive. > > > > If we agree that this is a good thing to do, dpkg should do it. > > OK, then I suppose from dpkg's point of view it should not go on to remove a > package's dependencies (in this case libsystemd0) if the prerm fails. Or the > default for --abort-after (currently 50) is wrong; perhaps it should be 1 when > dpkg is being invoked by APT? And dpkg does not remove packages when one of its dependencies is still present and has failed a maintainer script. The problem here is that apt is telling dpkg to ignore dependencies via --force-depends. Thanks, Guillem
