Ubuntu
portmap package

portmap does not honor preseeded debconf value

Bug #261711 reported by Daniel Richard G.
4
Affects Status Importance Assigned to Milestone
portmap (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: portmap

Version: 6.0-4 (Ubuntu 8.04.1)

I am making use of debconf preseeding, via debconf-get-selections(1) + debconf-set-selections(1). Among the selections specified this way is portmap's "bind to loopback address" setting, which I want to set to YES with

    portmap portmap/loopback boolean true

However, when the package is installed, it stays with the default value of NO, ignoring the preseeded debconf value. It thus becomes necessary to (re)configure the package manually in order to make the loopback setting effective.

The configuration control script for the portmap package should pick up a preseeded value when the package is being installed; that does not appear to be happening currently.

Revision history for this message
Steve Langasek (vorlon) wrote :

I can confirm this; the problem is that the initial creation of /etc/default/portmap is being handled in the preinst instead of the postinst, so has no knowledge of the debconf preseed value. This is definitely a bug, config files should be created in the postinst.

Changed in portmap (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.