Issue #5604 has been updated by Michael Stahnke.

Target version changed from 2.6.x to 2.7.x

2.6.x is closed.  Moving to 2.7.x
----------------------------------------
Bug #5604: disabling of apt-listchanges in puppet provider is a bit aggressive
https://projects.puppetlabs.com/issues/5604

Author: micah -
Status: Accepted
Priority: High
Assignee: 
Category: package
Target version: 2.7.x
Affected Puppet version: 
Keywords: 
Branch: 


it seems like the puppet apt provider mysteriously disables apt-listchanges 
using an environment variable. This is a bit ugly, and hidden.

in /usr/lib/ruby/1.8/puppet/provider/package/apt.rb there is this:
<pre>
ENV['APT_LISTCHANGES_FRONTEND'] = "none" 
</pre>

Which is used by apt-listchanges in ./apt-listchanges/ALCConfig.py.

With this environment set, you cannot use apt-listchanges at all. Its true that 
if the listbugs or listchanges front-end is set to an interactive one, and one 
of those is not able to fallback to something else if run from a non 
interactive shell, this commit does the right thing to get things working from 
inside puppet. However, a legitimate way to use apt-listchanges is to set the 
front-end to use "mail" which is a non-interactive way to have it send you 
email about package upgrades... but this change makes even that impossible.

Is there a way we can override the provider's environment setting?

According to git logs, this was changed in b0636354 (Dean Wilson 2010-08-13 
13:50:52 +0100 19) with the commit msg: "Skip apt-listbugs and apt-listchanges 
when installing from puppet", but with no rationale.




-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to