Your message dated Wed, 26 Jul 2006 16:17:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#377391: fixed in apt 0.6.45
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: partman-lvm
Version: 41
Severity: important
Tags: patch, pending
After a RAID device has been set up and that device has been selected "for
use with LVM", the following message is displayed when changes to devices
and partitions are committed to disk before configuring LVM:
"Error informing the kernel about modifications to partition
/dev/md/0p1 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/md/0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting."
For Sarge installations a different, but similar message was shown:
"The kernel was unable to re-read the partition table on /dev/md/0
(Invalid argument). This means Linux won't know anything nothing
about the modifications you made until you reboot. You should reboot
your computer before doing anything with /dev/md/0."
The basic cause is that partitions on a software RAID device are not
really supported by parted. I did some tests using parted from shell with
very inconsistent results (changes are sometimes committed, but 'parted
print' does not show them while 'fdisk list' does; kernel/udev does not
create /dev/md/0p1 device nodes).
After investigation the only reason partman tries to commit changes at all
turned out to be that the script update.d/21lvm_sync_flag sets the "lvm"
flag for a "dummy" partition that is created by partman in
init.d/31md-devices.
Earlier hacks in partman-lvm have already made sure that partman itself
does not rely only on the flag, but sets "method" instead (based on the
output of 'pvdisplay') in case of LVM on RAID. In line with this and as
the flag is never actually written anyway, it seems safe not to try
setting the flag if the lvm device is on a /dev/md/X device.
The following patch implements this.
--- update.d/lvm_sync_flag (revision 38772)
+++ update.d/lvm_sync_flag (working copy)
@@ -24,6 +24,16 @@
method=$(cat $id/method)
fi
+# As setting flags on RAID devices does not work and causes errors from
+# libparted, do not attempt to sync flags in case of LVM on RAID.
+# This is in line with the hacks in init.d/lvm and undo.d/lvm.
+if [ -f device ]; then
+ case $(cat device) in
+ /dev/md/*)
+ exit 0 ;;
+ esac
+fi
+
has_lvm=no
flags=''
open_dialog GET_FLAGS $id
pgpQ8F91erayf.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: apt
Source-Version: 0.6.45
We believe that the bug you reported is fixed in the latest version of
apt, which is due to be installed in the Debian FTP archive:
apt-doc_0.6.45_all.deb
to pool/main/a/apt/apt-doc_0.6.45_all.deb
apt-utils_0.6.45_i386.deb
to pool/main/a/apt/apt-utils_0.6.45_i386.deb
apt_0.6.45.dsc
to pool/main/a/apt/apt_0.6.45.dsc
apt_0.6.45.tar.gz
to pool/main/a/apt/apt_0.6.45.tar.gz
apt_0.6.45_i386.deb
to pool/main/a/apt/apt_0.6.45_i386.deb
libapt-pkg-dev_0.6.45_i386.deb
to pool/main/a/apt/libapt-pkg-dev_0.6.45_i386.deb
libapt-pkg-doc_0.6.45_all.deb
to pool/main/a/apt/libapt-pkg-doc_0.6.45_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Vogt <[EMAIL PROTECTED]> (supplier of updated apt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 27 Jul 2006 00:52:05 +0200
Source: apt
Binary: apt-utils libapt-pkg-doc libapt-pkg-dev apt-doc apt
Architecture: source all i386
Version: 0.6.45
Distribution: unstable
Urgency: low
Maintainer: APT Development Team <[email protected]>
Changed-By: Michael Vogt <[EMAIL PROTECTED]>
Description:
apt - Advanced front-end for dpkg
apt-doc - Documentation for APT
apt-utils - APT utility programs
libapt-pkg-dev - Development files for APT's libapt-pkg and libapt-inst
libapt-pkg-doc - Documentation for APT development
Closes: 296103 368038 370551 373729 373864 375068 375640 376330 376408 376777
377391 378183 378901 379576
Changes:
apt (0.6.45) unstable; urgency=low
.
* apt-pkg/contrib/sha256.cc:
- fixed the sha256 generation (closes: #378183)
* ftparchive/cachedb.cc:
- applied patch from Anthony Towns to fix Clean() function
(closes: #379576)
* doc/apt-get.8.xml:
- fix path to the apt user build (Closes: #375640)
* doc/apt-cache.8.xml:
- typo (Closes: #376408)
* apt-pkg/deb/dpkgpm.cc:
- make progress reporting more robust against multiline error
messages (first half of a fix for #374195)
* doc/examples/configure-index:
- document Debug::pkgAcquire::Auth
* methods/gpgv.cc:
- deal with gpg error "NODATA". Closes: #296103, Thanks to
Luis Rodrigo Gallardo Cruz for the patch
* apt-inst/contrib/extracttar.cc:
- fix for string mangling, closes: #373864
* apt-pkg/acquire-item.cc:
- check for bzip2 in /bin (closes: #377391)
* apt-pkg/tagfile.cc:
- make it work on non-mapable files again, thanks
to James Troup for confirming the fix (closes: #376777)
* Merged from Christian Perrier bzr branch:
* ko.po: Updated to 512t. Closes: #378901
* hu.po: Updated to 512t. Closes: #376330
* km.po: New Khmer translation: 506t6f. Closes: #375068
* ne.po: New Nepali translation: 512t. Closes: #373729
* vi.po: Updated to 512t. Closes: #368038
* zh_TW.po: Remove an extra %s in one string. Closes: #370551
* dz.po: New Dzongkha translation: 512t
* ro.po: Updated to 512t
* eu.po: Updated
Files:
d3d7ccf2707bf9e45dd6821a8c60bfc6 784 admin important apt_0.6.45.dsc
56f29db0a19f4e8934a34d80899bc597 1672288 admin important apt_0.6.45.tar.gz
10f9d0b4b29e0235df580d2e062feac4 88600 doc optional apt-doc_0.6.45_all.deb
cfb7f92e3bf63e53a4872ef0c5bd8cc0 111964 doc optional
libapt-pkg-doc_0.6.45_all.deb
f16ea6de6ea4eca0461fd6b373870826 1406494 admin important apt_0.6.45_i386.deb
6a25cc0fafc4a2ecc856954e12860be5 82720 libdevel optional
libapt-pkg-dev_0.6.45_i386.deb
a1b320c9646595edbf63279a1ea1ea72 192782 admin important
apt-utils_0.6.45_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEx/RBliSD4VZixzQRAk9cAJ93wRCF1tTEZQPRR3xbVKUVfUgS8QCfc8zW
yPVDwnUlmiR2uNVDZiYmbLk=
=NIko
-----END PGP SIGNATURE-----
--- End Message ---
