Install script does not properly configure ntlmaps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntlmaps (Debian) |
Fix Released
|
Unknown
|
|||
ntlmaps (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: ntlmaps
Version: ntlmaps_0.9.9-4_all
Under Ubuntu Dapper and Edgy.
The installer kicks off a series of questions needed to set up the server.conf file. A couple of key questions are not asked when this is run during installation, so the proxy doesn't work. Stuff like the proxy port and the domain are missing.
After installation, if the script is run manually via:
sudo dpkg-reconfigure ntlmaps
...the correct questions are asked, the server.conf file is correctly set up and the proxy works.
For what it's worth, the same appears to happen on Debian Etch with ntlmaps_0.9.9.0.1-4 and also appears to be the subject of a retired Debian bug (#315403). I'm reporting it here because I couldn't face the Debian bug reporting process.
Changed in ntlmaps: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in ntlmaps: | |
status: | Unknown → New |
Changed in ntlmaps (Debian): | |
status: | New → Fix Released |
This issue continues to be the case under Feisty.
It looks as though it's related to the debconf priority given to the package's setup questions. In the package, this appears to be set too high, so that unless someone already has their system debconf priority set to a very granular level, the initial setup of ntlmaps during installation can never work correctly.
I don't know enough about deb package creation to fix this, but it seems to me that changing the question priorities in the config script might solve the problem.