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 ?
>
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
> >
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? Se
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 mi
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 af
5 matches
Mail list logo
