Hi,
> <eddyp> vorlon: the patch is there, in case you want to look over it
> <eddyp>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=39;filename=default_mirror.patch;att=1;bug=333294
> <vorlon> eddyp: RC bug, you're editing a conffile
> <vorlon> (that was what I wanted to look at it for :)
> <eddyp> vorlon: I suspected that
> <eddyp> vorlon: if you look close it doesn't touch the admin's changes, it
> only operates on the default file
> <eddyp> this is quite a corner case, IMHO
> <vorlon> eddyp: no, it's not.
> <vorlon> eddyp: pbuilderrc never should've been a conffile in the first
> place, and I'm sick to death of getting conffile
> prompts about it on every upgrade
> <eddyp> unless the file is turned into a non-conffile then I don't see a way
> out
> <vorlon> eddyp: so you can be darn sure I'm going to block any attempt to
> inflict that same pain on other users of
> pbuilderrc when it's a policy violation besides
>
> <eddyp> and afaik there is no sane way of doing that ....
> <vorlon> yes, there is
> <vorlon> doing it is left as an exercise for the developer
My original plans wrt debconfiscating configuration file was:
1. no longer ship /etc/pbuilderrc in pbuilder package
2. generate /etc/pbuilderrc from /usr/share/pbuilder/pbuilderrc, using
the debconf-provided defaults.
3. make sure pbuilder doesn't change in such a way to require change in default
configuration file
pbuilder should work fine with an empty or nonexisting
/etc/pbuilderrc, since it can pull the default from
/usr/share/pbuilder/pbuilderrc, and newer configuration variables will
be taken from there, so upgrade cases shouldn't cause too much
problem.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
