Bug#317358: portmap bind to loopback install option doesn't work

2010-05-24 Thread Michael Prokop
* Petter Reinholdtsen p...@hungry.com [Don Feb 25, 2010 at 07:01:43 +0100]:
 I suspect this issue was solved when portmap version 6.0.0-2, but am
 unsure if it is true.  Please test and see if the issue is solved.

Nope it's not fully solved yet.

Executing dpkg-reconfigure portmap in interactive mode and
answering Should portmap be bound to the loopback address? with
yes results in OPTIONS=-i 127.0.0.1 in /etc/default/portmap as
expected.

But executing:

  echo portmap portmap/loopback boolean false | debconf-set-selections
  dpkg-reconfigure --frontend=noninteractive portmap

then results again in OPTIONS=-i 127.0.0.1 in /etc/default/portmap.

Demonstration:

, [ broken reconfigure ]
| # echo portmap portmap/loopback boolean true | debconf-set-selections
| # debconf-get-selections   | grep 'portmap.*boolean'
| portmap portmap/loopbackboolean true
| # dpkg-reconfigure --frontend=noninteractive portmap
| Stopping portmap daemon
| Starting portmap daemon
| # debconf-get-selections   | grep 'portmap.*boolean'
| portmap portmap/loopbackboolean false
`

And the other way arround:

, [ broken reconfigure ]
| # echo portmap portmap/loopback boolean false | debconf-set-selections
| # debconf-get-selections   | grep 'portmap.*boolean'
| portmap portmap/loopbackboolean false
| # dpkg-reconfigure --frontend=noninteractive portmap
| Stopping portmap daemon
| Starting portmap daemon
| # debconf-get-selections   | grep 'portmap.*boolean'
| portmap portmap/loopbackboolean true
`

So the portmap/loopback value is just being toggled, no matter
what's configured in debconf database.

The problem is located in /var/lib/dpkg/info/portmap.config:

, [ debugging mode ]
| # export DEBCONF_DEBUG=developer
| # dpkg-reconfigure --frontend=noninteractive portmap
| Stopping portmap daemon
| debconf (developer): starting /var/lib/dpkg/info/portmap.config reconfigure 
6.0.0-2
| debconf (developer): -- SET portmap/loopback true
| debconf (developer): -- 0 value set
| debconf (developer): -- INPUT medium portmap/loopback
| debconf (developer): -- 30 question skipped
| debconf (developer): -- GO
| debconf (developer): -- 0 ok
| debconf (developer): starting /var/lib/dpkg/info/portmap.postinst configure 
6.0.0-2
| debconf (developer): -- GET portmap/loopback
| debconf (developer): -- 0 true
| debconf (developer): -- STOP
| Starting portmap daemon
`

So the config script uses the value from /etc/default/portmap
and then just overrides the value in debconf database instead
of querying debconf before.

regards,
-mika-


signature.asc
Description: Digital signature


Bug#317358: portmap bind to loopback install option doesn't work

2010-05-24 Thread Petter Reinholdtsen
[Michael Prokop]
 * Petter Reinholdtsen p...@hungry.com [Don Feb 25, 2010 at 07:01:43 +0100]:
  I suspect this issue was solved when portmap version 6.0.0-2, but am
  unsure if it is true.  Please test and see if the issue is solved.
 
 Nope it's not fully solved yet.
 
 Executing dpkg-reconfigure portmap in interactive mode and
 answering Should portmap be bound to the loopback address? with
 yes results in OPTIONS=-i 127.0.0.1 in /etc/default/portmap as
 expected.
 
 But executing:
 
   echo portmap portmap/loopback boolean false | debconf-set-selections
   dpkg-reconfigure --frontend=noninteractive portmap
 
 then results again in OPTIONS=-i 127.0.0.1 in /etc/default/portmap.

What you are doing at the end here is not supposed to work.
Preseeding only work before the package is installed, as the
authorative configuration setting after installation is the content of
the configuration on disk, and not the values in the debconf database.
If you want to change settings using debconf automatically after
installation, you need to stack debconf backends and force debconf to
ignore the set command from the config script.  The reason for this is
that debconf is not a registry, only a mechanism to ask questions.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#317358: portmap bind to loopback install option doesn't work

2010-02-25 Thread Petter Reinholdtsen
I suspect this issue was solved when portmap version 6.0.0-2, but am
unsure if it is true.  Please test and see if the issue is solved.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#317358: portmap bind to loopback install option doesn't work

2009-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 317358 serious
Bug #317358 [portmap] portmap bind to loopback install option doesn't work
Severity set to 'serious' from 'normal'

 tags 317358 - unreproducible - moreinfo
Bug #317358 [portmap] portmap bind to loopback install option doesn't work
Removed tag(s) unreproducible.
Bug #317358 [portmap] portmap bind to loopback install option doesn't work
Removed tag(s) moreinfo.
 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org