Vincent Lefevre [EMAIL PROTECTED] wrote:
On 2006-12-28 21:03:57 +0100, Paul Slootman wrote:
This is I think a question of interpretation;
if the local change modifies the way the package works in any way, then
I agree; but a comment?! Where does it end? Do you want upgrades to
preserve the
severity 404861 important
thanks
On Fri 29 Dec 2006, Frank K?ster wrote:
Vincent Lefevre [EMAIL PROTECTED] wrote:
On 2006-12-28 21:03:57 +0100, Paul Slootman wrote:
This is I think a question of interpretation;
if the local change modifies the way the package works in any way, then
I
severity 404861 important
tags 404861 moreinfo
thanks
Frank Küster [EMAIL PROTECTED] wrote:
If really you can't preserve the comments, it must be said at the
beginning of the configuration file.
That would also be a good idea.
In summary, I think that wwwoffle's handling of wwwoffle.conf
Paul Slootman [EMAIL PROTECTED] wrote:
IMHO, comments should
be preserved,
Often this is possible using sed on the configuration file.
The thing is, upstream provides a quite complicated perl script to
handle the upgrades; and that script is pretty good at doing that,
apart from the
tags 404861 -moreinfo
thanks
Frank Küster [EMAIL PROTECTED] wrote:
Paul Slootman [EMAIL PROTECTED] wrote:
IMHO, comments should
be preserved,
Often this is possible using sed on the configuration file.
The thing is, upstream provides a quite complicated perl script to
handle the
Package: wwwoffle
Version: 2.9a-1
Severity: serious
Justification: Policy 10.7.3
The upgrade from wwwoffle 2.9-2 to 2.9a-1 overwrote a local change in
/etc/wwwoffle/wwwoffle.conf (at least a comment I had added at the end
of the file, which disappeared).
Section 10.7.3 of the Debian policy says:
On Thu 28 Dec 2006, Vincent Lefevre wrote:
The upgrade from wwwoffle 2.9-2 to 2.9a-1 overwrote a local change in
/etc/wwwoffle/wwwoffle.conf (at least a comment I had added at the end
of the file, which disappeared).
Section 10.7.3 of the Debian policy says:
local changes must be
On 2006-12-28 21:03:57 +0100, Paul Slootman wrote:
This is I think a question of interpretation;
if the local change modifies the way the package works in any way, then
I agree; but a comment?! Where does it end? Do you want upgrades to
preserve the mtime of the configuration file as well?
8 matches
Mail list logo
