DPKG_MAINTSCRIPT_PACKAGE not set by dpkg-reconfigure causing dpkg-trigger to fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debconf (Debian) |
Fix Released
|
Unknown
|
|||
debconf (Ubuntu) |
Fix Released
|
High
|
Colin Watson |
Bug 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_MAINTSCRIP
$ sudo DPKG_MAINTSCRIP
The usage of dpkg-trigger indicates that this is normally setup by dpkg:
$dpkg-trigger --help
...
--by-
...
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
debconf:
Installed: 1.5.19
Candidate: 1.5.19
Version table:
*** 1.5.19 0
500 http://
100 /var/lib/
Thanks,
Caleb
Related branches
Changed in debconf: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in debconf: | |
assignee: | nobody → kamion |
Changed in debconf (Debian): | |
status: | Unknown → New |
description: | updated |
Changed in debconf (Ubuntu): | |
status: | In Progress → Triaged |
Changed in debconf (Ubuntu): | |
importance: | Medium → High |
Changed in debconf (Debian): | |
status: | New → Fix Released |
Linked to a bzr branch with a fix. This should go into Debian as well (they don't have triggers yet, though, but when they do, they'll wan this as well, and until then, it does no harm). Colin, will you push+sync?