Your message dated Sat, 3 Dec 2011 19:31:18 +0100
with message-id <[email protected]>
and subject line Re: Bug#628996: Bug#628835: apt-listbugs, packagekit:
apt-listbugs block packagekit
has caused the Debian Bug report #628996,
regarding apt-listbugs: please work well with packagekit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
628996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628996
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-listbugs, packagekit
Severity: serious
On a system with both packagekit and apt-listbugs installed,
apt-listbugs will block installations made by packagekit, and simply
hang around waiting for input it seems.
This bug is release-critical, as installing apt-listbugs renders
packagekit unusable (you can't install or upgrade anymore). Just like
606025, this blocks any adoption of PackageKit as default.
Proposed solution: apt-listbugs should not wait for input when started
under PackageKit.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
On Fri, 3 Jun 2011 19:40:38 +0200 Francesco Poli wrote:
[...]
> On Thu, 02 Jun 2011 13:50:59 +0200 Matthias Klumpp wrote:
>
> > On Thu, 02 Jun 2011 13:14:50 +0200, Julian Andres Klode <[email protected]>
> > wrote:
[...]
> OK, this makes a wishlist bug for apt-listbugs: you are asking that
> apt-listbugs is modified so that it works well with packagekit
> (something that apt-listbugs was not designed to do, and has never done
> before).
[...]
> Open questions:
>
> (A) how can a program written in Ruby use debconf to interact with the
> user?
>
> (B) will a DebconfFrontend be (necessary and) enough to make
> apt-listbugs work well with packagekit?
>
> Suggestions and documentation for (A) would be appreciated.
> Help in investigating (B) is especially needed: that log file we were
> talking about would be useful to understand whether the problem is
> really that apt-listbugs wants to use stdout and stdin, but cannot
> (when started by packagekit).
[...]
>
> Please perform the following test.
> Create the following configuration file:
>
> $ cat /etc/apt/apt.conf.d/09hookinfo
> DPkg::Pre-Install-Pkgs {"/bin/cat - > /tmp/hookinfo.txt";};
> DPkg::Tools::Options::/bin/cat "";
> DPkg::Tools::Options::/bin/cat::Version "2";
>
> and try to install or upgrade some packages with packagekit.
> You should get what is sent through the hook interface in a nice file
> named /tmp/hookinfo.txt
[...]
> Please attach this file in your reply
[...]
> so that I can take a look at it.
[...]
>
> Maybe the problem is really that the aptcc back-end fails to provide
> the VERSION 2 apt hook interface protocol output...
>
> If this is confirmed, then I think the aptcc back-end should support
> the VERSION 2 apt hook interface protocol output.
> In the meanwhile (until aptcc is fixed to provide the correct hook
> output, and until apt-listbugs begins to work well with packagekit),
> I think packagekit should conflict with apt-listbugs.
This wishlist bug does not seem to have received much interest from its
original submitter, or other involved people, for quite some time.
Additional information was requested, but none has been provided.
I am closing the bug report with this message: if anyone is still
interested in seeing apt-listbugs work well with packagekit, please
don't hesitate to reopen the bug and provide additional information.
Bye.
--
http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
New GnuPG key, see the transition document!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpQwQgOWlkzz.pgp
Description: PGP signature
--- End Message ---