Will there be a new release of apt soon to fix this bug? If not, is there a workaround I can apply to apt-listchanges to get it working again?
----- Forwarded message from Matt Zimmerman <[EMAIL PROTECTED]> ----- Date: Tue, 6 Mar 2001 21:43:09 -0500 From: Matt Zimmerman <[EMAIL PROTECTED]> To: Daniel Burrows <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#88805: New apt seems to have broken apt-listchanges On Tue, Mar 06, 2001 at 07:41:00PM -0500, Daniel Burrows wrote: > Just in case you don't know already..(no bugs yet) > > It looks like the new apt has broken apt-listchanges. I think (not sure, > sorry) that maybe the mechanism for invoking programs when apt installs > packages has changed. Debconf had a similar problem, maybe you can look > at how Joey solved it. This is Important bug #88675 against apt, and there is nothing I know of that I can do to apt-listchanges to work around it. As far as I could tell (before I patched my copy of apt 0.5.2), this affects debconf as well (though it only breaks preconfiguration, and debconf continues to work, asking questions in the postinst). I'll leave this bug open so that others don't report new ones, and close it when a fixed version of apt is released. I have a new apt-listchanges that requires a working apt 0.5, and I am waiting for a non-broken version to be released before uploading it. -- - mdz ----- End forwarded message ----- -- - mdz
