Your message dated Thu, 05 Mar 2009 22:51:37 +0100
with message-id <20090305215137.ga29...@artemis.corp>
and subject line Re: Bug#517975: pdnsd: package update overrides configuration
has caused the Debian Bug report #517975,
regarding pdnsd: package update overrides configuration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
517975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pdnsd
Version: 1.2.7-par-1
Severity: serious

pdnsd stopped responding to requests from tap0 interface after the
package was updated. It appears to be a direct result of Debian policy
violations.

> 10.7.2 Location
>
> Any configuration files created or used by your package must reside
> in /etc. If there are several, consider creating a subdirectory of
> /etc named after your package.
>
> If your package creates or uses configuration files outside of /etc,
> and it is not feasible to modify the package to use /etc directly,
> put the files in /etc and create symbolic links to those files from
> the location that the package requires.

pdnsd uses `/usr/share/pdnsd/pdnsd-resolvconf.conf'. To complicate the
matters, there _is_ `/etc/pdnsd.conf' file, ignored by default package
installation. I am sure that many new pdnsd users edit this file and
are a bit surprised to see no result.

> 10.7.3 Behavior
>
> Configuration file handling must conform to the following behavior:
>
>   * local changes must be preserved during a package upgrade, and
>
>   * configuration files must be preserved when the package is removed,
>     and only deleted when the package is purged.

My /usr/share/pdnsd/pdnsd-resolvconf.conf was silently overwritten
during package update. All local changes[1] were discarded.

  [1] server_ip = any; // access restricted by firewall rules

(That is why tap0 interface got no responses.)

IMO, pdnsd should use /etc/pdnsd.conf by default and preserve local
changes to it.

Thank you.

-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pdnsd depends on:
ii  adduser                       3.110      add and remove users and groups
ii  debconf [debconf-2.0]         1.5.25     Debian configuration management sy
ii  libc6                         2.7-18     GNU C Library: Shared libraries

Versions of packages pdnsd recommends:
ii  resolvconf                    1.43       name server information handler

pdnsd suggests no packages.

-- debconf information:
* pdnsd/conf: Use resolvconf

-- 
vvv



--- End Message ---
--- Begin Message ---
> > 10.7.2 Location
> >
> > Any configuration files created or used by your package must reside
> > in /etc. If there are several, consider creating a subdirectory of
> > /etc named after your package.
> >
> > If your package creates or uses configuration files outside of /etc,
> > and it is not feasible to modify the package to use /etc directly,
> > put the files in /etc and create symbolic links to those files from
> > the location that the package requires.
> 
> pdnsd uses `/usr/share/pdnsd/pdnsd-resolvconf.conf'. To complicate the
> matters, there _is_ `/etc/pdnsd.conf' file, ignored by default package
> installation. I am sure that many new pdnsd users edit this file and
> are a bit surprised to see no result.

pdnsd proposes two default really usual configs in /usr/share that are
_not_ conffiles as per debian policy. You're free to chose "manual"
setting of pdnsd and use the default /etc/pdnsd.conf file. You're of
course free to create it from the ones in /usr/share/pdnsd if you want
to.

> > 10.7.3 Behavior
> >
> > Configuration file handling must conform to the following behavior:
> >
> >   * local changes must be preserved during a package upgrade, and
> >
> >   * configuration files must be preserved when the package is removed,
> >     and only deleted when the package is purged.

I pretty much know the policy and your changes to /etc/pdnsd.conf that
_IS_ the conffile won't be touched.

If you select manual setting in /etc/default/pdnsd by setting AUTO_MODE
to "" or using dpkg-reconfigure pdnsd, you'll be done with it.

Note that the debconf question is of "high" level so it's really
unlikely you didn't read it, and the template reads:
----8<----
  - Manual          : completely manual configuration. The pdnsd daemon
                      will not start until you edit /etc/pdnsd.conf and
                      /etc/default/pdnsd.
---->8----

IOW the packaging feature is totally documented.


-- 
·O·  Pierre Habouzit
··O                                                madco...@debian.org
OOO                                                http://www.madism.org

Attachment: pgp2BupTu5tTT.pgp
Description: PGP signature


--- End Message ---

Reply via email to