Hi,

Op Sat 25 Dec 2010 om 09:38:19 +0200 schreef Avi Rozen:
> On 12/25/2010 08:21 AM, Joost van Baal wrote:
> > Andres Mejia wrote:
> > <snip>
> >> this package should be orphaned.
> > <snip>
> >
> > Is Avi Rozen no longer interested in working on the noip2 Debian package?
> 
> Not really.

> > If so, it should indeed get orphaned.  Googling revealed:
> >
> >     You should set the package maintainer to Debian QA Group
> >     <packa...@qa.debian.org> and submit a bug report against the
> >     pseudo package wnpp. The bug report should be titled O: package
> >     -- short description indicating that the package is now orphaned.
> >     The severity of the bug should be set to normal. [...] send a
> >     copy to <debian-de...@lists.debian.org> by putting the address
> >     in the X-Debbugs-CC: header of the message [...]

> I'm still using no-ip.com services, but I've recently switched to using
> ddclient as the update client.


Jakub Wilk wrote:
>>> The only place noip2 store configuration data (apart from the debconf 
>>> cache) is a binary blob in /var/lib/noip2/. This file will be happily 
>>> overwritten on each upgrade using *only* values supplied by debconf.

> > And the bug should be fixed too, of course...

> As for the current bug, I'd like to point out that noip2 configuration
> and runtime state has always been kept in a binary "configuration" file.
> This doesn't match the Debian policy, and the current "abuse" of debconf
> is the result of a our deliberate attempt to workaround it.

As documented in Bug #430842, I just found out.  However, this still is a
serious bug.  Currently, someone who makes local changes to the content of the
configuration file /var/lib/noip2/noip2.conf by running the noip2 client will
lose her changes at an upgrade.

Currently, no-ip offers debconf support for managing username, password,
updating, matchlist, netdevice and forcenatoff.  I assume this is generally
really sufficient to use no-ip.

An extra plain text conffile needs to be introduced, and the
advice in debconf-devel(7)'s "ADVANCED PROGRAMMING WITH DEBCONF - Config file
handling" needs to be followed.  Users should be advised not to change
/var/lib/noip2/noip2.conf directly.  I believe this way one fully adheres to
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.2 .  It won't be
trivial...

Bye,

Joost

-- 
irc:joos...@{oftc,freenode} ∙ http://mdcc.cx/http://ad1810.com/

Attachment: signature.asc
Description: Digital signature

Reply via email to