Bug#678311: [Debconf-devel] Bug#678311: apt-listchanges: debconf passthrough frontend for use with packagekit

2012-06-25 Thread Matthias Klumpp
Hello!
I've added a patch to PackageKit which will set the environment var,
so PackageKit is ready to use this feature.
PackageKit *can* do background package upgrades, but this is disabled
for Debian at time (we use apt itself)
Changing the env var for background tasks would work, of course.
Is there a chance to have this merged  uploaded before freeze, as it
is quite important for PK?
Thank you for working on this!
Cheers,
   Matthias

2012/6/20 Julien Cristau jcris...@debian.org:
 Thanks for the feedback.

 On Wed, Jun 20, 2012 at 17:22:41 -0400, Joey Hess wrote:

 Julien Cristau wrote:
  when using packagekit, which seems to be the way gnome is going for
  graphical package management nowadays, the apt-listchanges output
  doesn't go anywhere, and the gpk window just seems to hang.
  In order to fix that, it'd be nice if apt-listchanges could send its
  output using the debconf protocol so it could show up in the packagekit
  frontend.  The below patch is a proof of concept to that effect.  pk
  would have to set APT_LISTCHANGES_FRONTEND=debconf for this to work (it
  already sets APT_LISTBUGS_FRONTEND=none).  packagekit and debconf
  maintainers cc:ed in case they have comments.
 
  I'm not too happy about the tempfile thing instead of just using
  db.subst to change the contents of the note, but I couldn't figure out
  how to SUBST something with newlines (it didn't seem to work when I
  tested with the dialog frontend, anyway).

 Does this have the potential to have security updates being applied in
 the background be blocked on the user pressing Ok on a news window?

 I don't know if packagekit does package upgrades in the background.
 If it does it should probably do it with DEBIAN_FRONTEND=noninteractive,
 which I think this would respect.

 It might be better to just email the changes.

 Right, the problem with that is you don't know if a mta is
 installed/configured, and even then if anybody will read local mail to
 root.

 Cheers,
 Julien



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#678311: [Debconf-devel] Bug#678311: apt-listchanges: debconf passthrough frontend for use with packagekit

2012-06-20 Thread Joey Hess
Julien Cristau wrote:
 when using packagekit, which seems to be the way gnome is going for
 graphical package management nowadays, the apt-listchanges output
 doesn't go anywhere, and the gpk window just seems to hang.
 In order to fix that, it'd be nice if apt-listchanges could send its
 output using the debconf protocol so it could show up in the packagekit
 frontend.  The below patch is a proof of concept to that effect.  pk
 would have to set APT_LISTCHANGES_FRONTEND=debconf for this to work (it
 already sets APT_LISTBUGS_FRONTEND=none).  packagekit and debconf
 maintainers cc:ed in case they have comments.
 
 I'm not too happy about the tempfile thing instead of just using
 db.subst to change the contents of the note, but I couldn't figure out
 how to SUBST something with newlines (it didn't seem to work when I
 tested with the dialog frontend, anyway).

Does this have the potential to have security updates being applied in
the background be blocked on the user pressing Ok on a news window?

It might be better to just email the changes.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#678311: [Debconf-devel] Bug#678311: apt-listchanges: debconf passthrough frontend for use with packagekit

2012-06-20 Thread Julien Cristau
Thanks for the feedback.

On Wed, Jun 20, 2012 at 17:22:41 -0400, Joey Hess wrote:

 Julien Cristau wrote:
  when using packagekit, which seems to be the way gnome is going for
  graphical package management nowadays, the apt-listchanges output
  doesn't go anywhere, and the gpk window just seems to hang.
  In order to fix that, it'd be nice if apt-listchanges could send its
  output using the debconf protocol so it could show up in the packagekit
  frontend.  The below patch is a proof of concept to that effect.  pk
  would have to set APT_LISTCHANGES_FRONTEND=debconf for this to work (it
  already sets APT_LISTBUGS_FRONTEND=none).  packagekit and debconf
  maintainers cc:ed in case they have comments.
  
  I'm not too happy about the tempfile thing instead of just using
  db.subst to change the contents of the note, but I couldn't figure out
  how to SUBST something with newlines (it didn't seem to work when I
  tested with the dialog frontend, anyway).
 
 Does this have the potential to have security updates being applied in
 the background be blocked on the user pressing Ok on a news window?
 
I don't know if packagekit does package upgrades in the background.
If it does it should probably do it with DEBIAN_FRONTEND=noninteractive,
which I think this would respect.

 It might be better to just email the changes.
 
Right, the problem with that is you don't know if a mta is
installed/configured, and even then if anybody will read local mail to
root.

Cheers,
Julien


signature.asc
Description: Digital signature