reassign 367052 aptitude
thanks
Frank Lichtenheld <[EMAIL PROTECTED]> wrote:
> But I have now found a way to reproduce this bug (although I'm not
> sure it is really fully the same situation as with the submitters).
> Normally aptitude uses libapt-pkg to call dpkg which sets
> DPKG_NO_TSTP. If dpkg fails with an error, aptitude calls dpkg
> --configure -a directly ("A package failed to install. Trying to
> recover:") without setting DPKG_NO_TSTP which leads to the situation
> described in the bug report.Now that you point out that method of reproducing the problem, I recall that the times I encountered the problem did indeed occur after a broken package caused aptitude to do the second pass with dpkg --configure -a. So it sounds like you've found the right root cause. > Unless someone convinces me that dpkg should do something about this > (e.g. by changing the default behaviour of 'Z') or that there are > other situations where this bug occours I will reassign it to aptitude > and ask for setting DPKG_NO_TSTP before the dpkg --configure -a > call. That looks like the right fix; reassigning the bug.. This definitely looks like an aptitude bug, not a dpkg bug. - Josh Triplett
signature.asc
Description: OpenPGP digital signature
