Your message dated Sun, 23 Nov 2008 08:21:33 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: uswsusp maintainer script modifies /etc/uswsusp.conf
has caused the Debian Bug report #459420,
regarding uswsusp breaks config on upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
459420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459420
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: uswsusp
Version: 0.3~cvs20060928-7etch1
Severity: serious
uswsusp messes with its config file on upgrade:
intrepid:/etc# head -n 2 uswsusp.conf
# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
resume device = /dev/md5
intrepid:/etc# apt-get install --reinstall uswsusp
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 511kB of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://ftp.at.debian.org etch/main uswsusp 0.3~cvs20060928-7etch1 [511kB]
Fetched 511kB in 2s (211kB/s)
Preconfiguring packages ...
(Reading database ... 178375 files and directories currently installed.)
Preparing to replace uswsusp 0.3~cvs20060928-7etch1 (using .../uswsusp_0.3~cvs20
060928-7etch1_i386.deb) ...
Unpacking replacement uswsusp ...
Setting up uswsusp (0.3~cvs20060928-7etch1) ...
update-initramfs: Generating /boot/initrd.img-2.6.22.10.vs2.2.0.4
cryptsetup: WARNING: target cswap has a random key, skipped
intrepid:/etc# head -n 2 uswsusp.conf
# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
resume device = /dev/mapper/cswap
It should not necessary to point out that this is a serious bug.
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--- End Message ---
--- Begin Message ---
version 0.5
On Sun, Nov 23, 2008 at 12:54:01AM +0100, Michael Biebl wrote:
> Tim Dijkstra wrote:
> > On Sat, Nov 22, 2008 at 08:53:02PM +0100, Peter Palfrader wrote:
> >> On Sat, 22 Nov 2008, Tim Dijkstra wrote:
> >
> >> Where is that setting saved? debconf is not a registry so it must not
> >> be used for keeping state.
> >
>
> If I understand Peter correctly, and Peter, please correct me if I'm wrong,
> his
> concern is not so much about a debconf prompt being shown or not, but the
> following two issues:
>
> a) your primary configuration source should be /etc/uswsusp.conf and *not* the
> debconf database, i.e. if you run dpkg-reconfigure uswsusp, you should first
> try
> to get the configuration data (e.g. for resume device) from uswsusp.conf and
...
>
> b) do not overwrite /etc/uswsusp.conf, if it contains local modifications that
> would not be preserved by the update.
BUT THIS IS WHAT IT DOES. Please people, read the source.
There used to be a bug in 0.3 or 0.4 or so (in etch), but that has been fixed
for
ages.
Apparently peter still sees a problem on upgrades, but I can't reproduce that.
I think he was just mistaken, really.
Peter if you can still reproduce it, please create a step by step
description of what you did. And reopen this bug
grts Tim
--- End Message ---
