[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#377294: marked as done (new concept of upgrading configuration fails on versions management)

Your message dated Sat, 28 Nov 2009 19:37:09 +0100
with message-id <20091128183709.GA12449@patate.is-a-geek.org>
and subject line Re: Bug#220469: xserver-xfree86: dpkg-reconfigure should create the config file if it doesn't exist
has caused the Debian Bug report #220469,
regarding new concept of upgrading configuration fails on versions management
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 owner@bugs.debian.org
immediately.)


-- 
220469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=220469
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: xserver-xorg
Version: 1:7.0.22

I'm building a new debootsrap system, and if i try to configure it
with dpkg-reconfigure, it doesn't write xorg.conf file. With a "set
- -x" i have traced the /var/lib/dpkg/info/xserver-xorg.postinst and
when i took a look to it, i've understood it was an "update", but as
long as my xorg.conf file is clean (blank file), he won't upgrade
anything and the xorg.conf file will continue blank... Then i needed
to "confuse" the script, exactly on the line 1669:

# here's a new concept: DON'T TOUCH THE CONFIG ON UPGRADES
if [ -z "$UPGRADE" ] || dpkg --compare-versions "$2" le "1:7.0.14"; then

i had to change the version 1:7.0.14 to 1:7.0.22 so deboostrap will
skip upgrading a file that has nothing (blank), but writing instead a
real file from your config or debconf

After that, i also needed to run this:

touch /etc/X11/xorg.conf
md5sum /etc/X11/xorg.conf > /var/lib/x11/xorg.conf.md5sum

to accept the MD5SUM verification

Well, i know that this bug is a little "riddled"  and it can be
produced by different things. IMHO my recomm. is simply this... before
all, have a look to xorg.conf file, and see if it exists. if it
doesn't, "touch it" and generate the new md5sum verification (same to
my 2 last commands), and then, DO NOT use the "upgrade" way when is
called on the postinst script (same to the thing explained first)

If any question about this, just email me



Thanatermesis

- --
Do you want a new Linux experience ? Just follow my legacy...

Verify the authenticity of my emails, takes my key from my own server
http://thanatermesis.org/mediawiki/index.php/Gpg_Keys_Signatures and
nothing more to do
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFErvaeisTnwngKr/ARAr+ZAJ9ZN2wOCNvmbSx9CUYxUzm+9t35CQCgmtNV
Rhzcph2illhgL6IQuzDAXFQ=
=Zi1E
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On Wed, Nov 12, 2003 at 23:05:07 +0100, Uwe Storbeck wrote:

> I like the idea protecting changes in the XF86Config-4 config file
> by a md5-sum.
> But if the config file doesn't exist dpkg-reconfigure should create
> a new one instead of refusing to write it:
> 
>   # dpkg-reconfigure xserver-xfree86
>   Note: not updating /etc/X11/XF86Config-4; file does not exist.
> 
> If you are playing around with different options or even different
> graphic cards and want to start from scratch with a new config file
> you have to remove and reinstall the xserver-package (or at least
> with knowledge of package internals to recreate the md5-file).
> Removing the config file would be the much easier way.
> 
We don't create an X config file anymore, as X works well enough without
one.  Closing this bug as obsolete.

Cheers,
Julien

--- End Message ---
Reply to: