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

Bug#377294: new concept of upgrading configuration fails on versions management



-----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-----




Reply to: