How to warn about need to port changes to new configuration file?

2010-06-18 Thread Thomas Hood
It is planned that an upcoming version of resolvconf will add a new hook script for isc-dhcp-client which is identical to the existing one for dhcp3-client. An administrator who has made local changes to the latter hook script should probably make the same changes to the former. Is there a ne

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Xavier Oswald
On 16:06 Fri 18 Jun , Thomas Hood wrote: > It is planned that an upcoming version of resolvconf will add a new hook > script for isc-dhcp-client which is identical to the existing one for > dhcp3-client. An administrator who has made local changes to the latter > hook script should proba

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Petter Reinholdtsen
[Thomas Hood] > It is planned that an upcoming version of resolvconf will add a new > hook script for isc-dhcp-client which is identical to the existing one > for dhcp3-client. An administrator who has made local changes to the > latter hook script should probably make the same changes to the > fo

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Michael Biebl
On 18.06.2010 16:06, Thomas Hood wrote: > It is planned that an upcoming version of resolvconf will add a new hook > script for isc-dhcp-client which is identical to the existing one for > dhcp3-client. An administrator who has made local changes to the latter > hook script should probably make

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread James Vega
On Fri, Jun 18, 2010 at 10:46 AM, Michael Biebl wrote: > On 18.06.2010 16:06, Thomas Hood wrote: >> It is planned that an upcoming version of resolvconf will add a new hook >> script for isc-dhcp-client which is identical to the existing one for >> dhcp3-client.  An administrator who has made loca

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Stefano Zacchiroli
On Fri, Jun 18, 2010 at 04:46:15PM +0200, Michael Biebl wrote: > I assume the file in question is a conffile. If you just want to move its > location, read the section "Moving a conffile" at > http://wiki.debian.org/DpkgConffileHandling Or rather dpkg-maintscript-helper(1) . By the way, I believe

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Michael Biebl
On 18.06.2010 17:15, James Vega wrote: > On Fri, Jun 18, 2010 at 10:46 AM, Michael Biebl wrote: >> I assume the file in question is a conffile. If you just want to move its >> location, read the section "Moving a conffile" at >> http://wiki.debian.org/DpkgConffileHandling > > dpkg-maintscript-he

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Patrick Matthäi
Am 18.06.2010 18:10, schrieb Michael Biebl: On 18.06.2010 17:15, James Vega wrote: On Fri, Jun 18, 2010 at 10:46 AM, Michael Biebl wrote: I assume the file in question is a conffile. If you just want to move its location, read the section "Moving a conffile" at http://wiki.debian.org/DpkgCon

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Julien Cristau
On Fri, Jun 18, 2010 at 18:10:07 +0200, Michael Biebl wrote: > On 18.06.2010 17:15, James Vega wrote: > > On Fri, Jun 18, 2010 at 10:46 AM, Michael Biebl wrote: > > >> I assume the file in question is a conffile. If you just want to move its > >> location, read the section "Moving a conffile" at

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Philipp Kern
On 2010-06-18, Julien Cristau wrote: [dpkg-maintscript-helper] >> This means though, your package needs to add a versioned depends on dpkg,= > which >> imho is not so nice. > Make that pre-depends, since you need it in preinst iirc. As documented in its manpage, at least. It looks a tad mislead

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Raphael Hertzog
On Fri, 18 Jun 2010, Philipp Kern wrote: > As documented in its manpage, at least. It looks a tad misleading, though: > > | But in many cases the operation done by the program is not critical > | for the package, and instead of using a pre-dependency we can call the > program > | only if we

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Raphael Hertzog
On Fri, 18 Jun 2010, Stefano Zacchiroli wrote: > On Fri, Jun 18, 2010 at 04:46:15PM +0200, Michael Biebl wrote: > > I assume the file in question is a conffile. If you just want to move its > > location, read the section "Moving a conffile" at > > http://wiki.debian.org/DpkgConffileHandling > > Or

Re: How to warn about need to port changes to new configuration file?

2010-06-18 Thread Stefano Zacchiroli
On Fri, Jun 18, 2010 at 08:58:55PM +0200, Raphael Hertzog wrote: > What do you want us to review? The work on dpkg-maintscript-helper was > heavily inspired by the content of that page. Feel free to replace it by a > pointer to the dpkg-maintscript-helper documentation. I was mainly concerned by p

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Vincent Danjean
On 18/06/2010 16:57, Petter Reinholdtsen wrote: > [Thomas Hood] >> It is planned that an upcoming version of resolvconf will add a new >> hook script for isc-dhcp-client which is identical to the existing one >> for dhcp3-client. An administrator who has made local changes to the >> latter hook sc

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Julien Cristau
On Sat, Jun 19, 2010 at 10:20:49 +0200, Vincent Danjean wrote: > The difference here is that this is a copy, not a move, of the conffile. So you use cp instead of mv. Where's the problem exactly? Cheers, Julien signature.asc Description: Digital signature

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Petter Reinholdtsen
[Vincent Danjean] > The difference here is that this is a copy, not a move, of the conffile. That is why I suggested to use a symlink too. This I would propose to move the conffile to the new location, and add a symlink in the old location to the new location, or just add a symlink to the old loc

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Vincent Danjean
On 19/06/2010 10:44, Julien Cristau wrote: > On Sat, Jun 19, 2010 at 10:20:49 +0200, Vincent Danjean wrote: > >> The difference here is that this is a copy, not a move, of the conffile. > > So you use cp instead of mv. Where's the problem exactly? Should local modifications to the first script