2011-08-10 22:05:03 |
kane oakenfull |
description |
Binary package hint: debconf
When reconfiguring a package that uses dpkg-trigger it fails with:
dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option)
For instance:
$ sudo dpkg-reconfigure selinux
dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option)
Setting DPKG_MAINTSCRIPT_PACKAGE fixes the problem:
$ sudo DPKG_MAINTSCRIPT_PACKAGE=selinux dpkg-reconfigure selinux
The usage of dpkg-trigger indicates that this is normally setup by dpkg:
$dpkg-trigger --help
...
--by-package=<package> Override trigger awaiter (normally set by dpkg).
...
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
debconf:
Installed: 1.5.19
Candidate: 1.5.19
Version table:
*** 1.5.19 0
500 http://us.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status
Thanks,
Caleb |
Binary package hint: debconf
When reconfiguring a package that uses dpkg-trigger it fails with:
dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option)
For instance:
$ sudo dpkg-reconfigure selinux
dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option)
Setting DPKG_MAINTSCRIPT_PACKAGE fixes the problem:
$ sudo DPKG_MAINTSCRIPT_PACKAGE=selinux dpkg-reconfigure selinux
The usage of dpkg-trigger indicates that this is normally setup by dpkg:
$dpkg-trigger --help
...
--by-package=<package> Override trigger awaiter (normally set by dpkg).
...
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
debconf:
Installed: 1.5.19
Candidate: 1.5.19
Version table:
*** 1.5.19 0
500 http://us.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status
Thanks,
Caleb |
|