On 2012-09-05 10:32:45 +0200, Cyril Brulebois wrote:
> Fabian Greffrath <fab...@greffrath.com> (05/09/2012):
> > Obviously, you manually changed the symlink "70-no-bitmaps.conf" to
> > point to another file "../conf.avail/70-yes-bitmaps.conf". However,
> > the symlinks are expected to point to files of the same name in the
> > ../conf.avail directory.
> 
> Says which doc? None AFAICT. Does conf.d/README talk about debconf at
> all? Hell no.

I'd say that the conf.d/README file should be updated to mention
that some symlinks may be managed by debconf.

> I started with a removal of the symlink. That change (too) was lost by
> the upgrade process. This is a RC bug.

No, the fact that a symlink change (whether this is done manually or
by a configuration via debconf) is not preserved after upgrade is not
regarded as a RC bug. Quoting Steve Langasek[*]:

  Debian policy requires that local changes to configuration files are
  retained.  This generally implies that packages should try to preserve
  configuration values represented in other ways (such as symlinks), but
  this is not a requirement of policy.  And as I've pointed out, there
  are significant high-profile examples where admin changes to symlinks
  are not preserved.

[*] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412159#68

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


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

Reply via email to