apt-listchanges setup ignored

Bug #141366 reported by Daniel Elstner
4
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: synaptic

Synaptic forces apt-listchanges to use the gtk frontend even if it is configured to only send mail. It's been like that for quite a while now but today I felt like investigating the matter. Apparently this is an inadvertent side effect of the fix committed for bug #17999. From gtk/rgdebinstallprogress.cc line 370 [1]:

    putenv("APT_LISTCHANGES_FRONTEND=gtk");

Judging from the apt-listchanges source code this environment variable always takes precedence over the setting in the configuration file. However, I really only want the mail output for easy reference in case I need it, and perhaps for a little relaxed bedtime reading... or maybe not. Anyway, right now there seems to be no way to shut up apt-listchanges and still get the mails, short of hacking synaptic or apt-listchanges. So, to fix this I could either add some logic in synaptic to handle the listchanges frontend properly, or alternatively redefine APT_LISTCHANGES_FRONTEND to only apply if the configuration file doesn't say "none" or "mail", which could be handled within apt-listchanges itself.

Any other ideas? Which is the preferred way to go?

[1] <http://codebrowse.launchpad.net/~ubuntu-core-dev/synaptic/ubuntu/annotate/michael.vogt%40ubuntu.com-20070910152852-gins4bdv4rdm0kxz?file_id=rgdebinstallprogress.cc-20060222190946-48af831e059fbbc9#L370>

Revision history for this message
Daniel Elstner (daniel-elstner) wrote :

OK, while investigating into this I found that there's in fact an (undocumented) configuration option "quiet" which can be used to make apt-listchanges do what I want if I put "quiet=2" in /etc/apt/listchanges.conf. But I'm not sure if this option was ever meant to be used that way, and it isn't reachable via the debconf dialog either.

What do you think, should this bug be reassigned to apt-listchanges as a documentation bug, or should synaptic be made to behave better? Maybe it'd be enough to simply remove the putenv("APT_LISTCHANGES_FRONTEND=gtk") from synaptic. The console window should open automatically after a timeout anyway, and apt-listchanges is not installed by default.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

This is indeed a "feature" (misfeature) of synaptic. It overwrites the default behavior to display a dialog frontend. The fix should probably be to default in apt-listchanges to gtk and not overwrite user changes in synaptic. I will see to this in early hardy.

Changed in synaptic:
importance: Undecided → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.