Raphael Hertzog writes (Re: Bug#560317: dpkg-trigger complains at
dpkg-reconfigure time):
On Thu, 10 Dec 2009, Joey Hess wrote:
Does it actually make sense for dpkg-trigger to see those environment
variables when the postinst is not being run by dpkg? Seems possible that
any deferred
On Mon, 13 Sep 2010, Ian Jackson wrote:
Raphael Hertzog writes (Re: Bug#560317: dpkg-trigger complains at
dpkg-reconfigure time):
On Thu, 10 Dec 2009, Joey Hess wrote:
Does it actually make sense for dpkg-trigger to see those environment
variables when the postinst is not being run
Raphael Hertzog writes (Re: Bug#560317: dpkg-trigger complains at
dpkg-reconfigure time):
I agree with not setting DPKG_RUNNING_VERSION, but the others should be
set. [...]
Ah, good, then we are in agreement.
Can you explain why the analysis above is wrong ?
Did I say it's wrong?
Your
Hi,
On Thu, 10 Dec 2009, Joey Hess wrote:
Raphael Hertzog wrote:
Because the postinst is called by dpkg-reconfigure (of debconf) and it
doesn't set the same environment variables that dpkg does set when
it calls the postinst by itself. In particular DPKG_MAINTSCRIPT_PACKAGE
is missing.
FWIW, I wrote a patch a long time ago in an attempt to fix this.
http://bazaar.launchpad.net/~soren/debconf/dpkg-trigger-bug-198421/revision/618?remember=616compare_revid=616
The bzr branch is at:
https://code.launchpad.net/~soren/debconf/dpkg-trigger-bug-198421
--
Soren Hansen
Ubuntu
Hi!
On Fri, 2009-12-11 at 08:31:26 +0100, Raphael Hertzog wrote:
On Thu, 10 Dec 2009, Joey Hess wrote:
Raphael Hertzog wrote:
Because the postinst is called by dpkg-reconfigure (of debconf) and it
doesn't set the same environment variables that dpkg does set when
it calls the postinst
Raphael Hertzog wrote:
Does it actually make sense for dpkg-trigger to see those environment
variables when the postinst is not being run by dpkg? Seems possible that
any deferred trigger processing it then sets up will not take effect until
the next dpkg run, which could be well after
Dear all,
I have a question for sure stemming from my misunderstanding of triggers.
tex-common ships dh_installtex which makes installation of fonts etc
for TeX system easy, and it is used in quite some packages. We use
triggers (on popolar demand) since the most expensive operation is
the update
On Thu, Dec 10, 2009 at 04:05:25PM +0100, Norbert Preining wrote:
I have a question for sure stemming from my misunderstanding of triggers.
tex-common ships dh_installtex which makes installation of fonts etc
for TeX system easy, and it is used in quite some packages. We use
triggers (on
On Thu, 10 Dec 2009, Norbert Preining wrote:
I though well, yes, it is called from a maintainer script (postinst configure)
and the package should be clear. But why does dpkg-trigger complain?
Because the postinst is called by dpkg-reconfigure (of debconf) and it
doesn't set the same
reassign 560317 dpkg
retitle 560317 dpkg-reconfigure does not set DPKG_MAINTSCRIPT_PACKAGE (et al)
thanks
On Do, 10 Dez 2009, Steve Langasek wrote:
I think this should be regarded as a bug in dpkg-reconfigure.
On Do, 10 Dez 2009, Raphael Hertzog wrote:
It's a bug in dpkg-reconfigure, please
reassign 560317 debconf
thanks
On Thu, Dec 10, 2009 at 04:27:28PM +0100, Norbert Preining wrote:
reassign 560317 dpkg
retitle 560317 dpkg-reconfigure does not set DPKG_MAINTSCRIPT_PACKAGE (et al)
thanks
On Do, 10 Dez 2009, Steve Langasek wrote:
I think this should be regarded as a bug in
Raphael Hertzog wrote:
Because the postinst is called by dpkg-reconfigure (of debconf) and it
doesn't set the same environment variables that dpkg does set when
it calls the postinst by itself. In particular DPKG_MAINTSCRIPT_PACKAGE
is missing.
(dpkg does also set DPKG_MAINTSCRIPT_ARCH and
On Thu, 10 Dec 2009, Joey Hess wrote:
Raphael Hertzog wrote:
Because the postinst is called by dpkg-reconfigure (of debconf) and it
doesn't set the same environment variables that dpkg does set when
it calls the postinst by itself. In particular DPKG_MAINTSCRIPT_PACKAGE
is missing.
14 matches
Mail list logo
