Your message dated Fri, 13 May 2005 23:21:23 -0700 with message-id <[EMAIL PROTECTED]> and subject line [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79] 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) -------------------------------------- Received: (at submit) by bugs.debian.org; 6 Apr 2005 14:16:32 +0000 >From [EMAIL PROTECTED] Wed Apr 06 07:16:31 2005 Return-path: <[EMAIL PROTECTED]> Received: from zeus.penguinhosting.net [69.9.164.98] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1DJBKZ-00061n-00; Wed, 06 Apr 2005 07:16:31 -0700 Received: (qmail 19954 invoked by uid 1000); 6 Apr 2005 14:16:30 -0000 Date: Wed, 6 Apr 2005 10:16:30 -0400 From: Ian Gulliver <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: mkinitrd fails with cryptsetup and libdevmapper1.01 Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XStn23h1fwudRqtG" Content-Disposition: inline X-Operating-System: Linux sheba 2.6.11-1-686 User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --XStn23h1fwudRqtG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: initrd-tools Version: 0.1.77 Severity: important Line 385 of mkinitrd contains a reference to /lib/libdevmapper.so.1.00; this code is run when cryptsetup is installed, presumably to handle encrypted root filesystems. However, the current version of cryptsetup in sarge (20050111-3) depends on libdevmapper1.01, and the file above doesn't exist. Perhaps there needs to be a more future-proof way to handle this? --=20 Ian Gulliver Penguin Hosting "Failure is not an option; it comes bundled with your Microsoft products." --XStn23h1fwudRqtG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCU+89efI+qeoOjxURAsoAAJ9rfnqexvdOkI1QzSeaKfiyWMp2lgCfUV// HzEzbEqjJvM+eyrJU3SRb9A= =ezCR -----END PGP SIGNATURE----- --XStn23h1fwudRqtG-- --------------------------------------- Received: (at 298727-done) by bugs.debian.org; 14 May 2005 06:21:26 +0000 >From [EMAIL PROTECTED] Fri May 13 23:21:26 2005 Return-path: <[EMAIL PROTECTED]> Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DWq1c-0008Up-00; Fri, 13 May 2005 23:21:24 -0700 Received: by localhost.localdomain (Postfix, from userid 1000) id 67E54172CDB; Fri, 13 May 2005 23:21:23 -0700 (PDT) Date: Fri, 13 May 2005 23:21:23 -0700 From: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [EMAIL PROTECTED]: Fixed in NMU of initrd-tools 0.1.79] Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1ccMZA6j1vT5UqiK" Content-Disposition: inline User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.0 required=4.0 tests=BAYES_00,SORTED_RECIPS, VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 11 --1ccMZA6j1vT5UqiK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable These bugs were all closed in the most recent initrd-tools upload, but owing to pilot error, were not marked as such. The original closure message was as follows. Cheers, --=20 Steve Langasek postmodern programmer ----- Forwarded message from Steve Langasek <[EMAIL PROTECTED]> ----- X-Original-To: [EMAIL PROTECTED] =46rom: Steve Langasek <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Steve Langasek <[EMAIL PROTECTED]>, Debian kernel team <debian-kernel@lists.debian.org> X-Katie: $Revision: 1.55 $ Subject: Fixed in NMU of initrd-tools 0.1.79 Date: Sat, 14 May 2005 01:32:13 -0400 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on norad.dodds.net X-Spam-Level:=20 X-Spam-Status: No, score=3D-2.6 required=3D5.0 tests=3DBAYES_00 autolearn= =3Dham=20 version=3D3.0.2 tag 266591 + fixed tag 279382 + fixed tag 285767 + fixed tag 290329 + fixed tag 291386 + fixed tag 292080 + fixed tag 295412 + fixed tag 295422 + fixed tag 296894 + fixed tag 297724 + fixed tag 298727 + fixed tag 301455 + fixed tag 303281 + fixed tag 303401 + fixed tag 306219 + fixed quit This message was generated automatically in response to a non-maintainer upload. The .changes file follows. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Fri, 13 May 2005 21:25:52 -0700 Source: initrd-tools Binary: initrd-tools Architecture: source all Version: 0.1.79 Distribution: unstable Urgency: high Maintainer: Debian kernel team <debian-kernel@lists.debian.org> Changed-By: Steve Langasek <[EMAIL PROTECTED]> Description:=20 initrd-tools - tools to create initrd image for prepackaged Linux kernel Closes: 266591 279382 285767 290329 291386 292080 295412 295422 296894 2977= 24 298727 301455 303281 303401 306219 Changes:=20 initrd-tools (0.1.79) unstable; urgency=3Dhigh . * Steve Langasek - Don't be so hasty to use lvm10: only use it if lvmiopversion says we're lvm10-only, *or* there's no dm-mod for the kernel; this avoids breaking lvm2 volumes in 2.4 when the lvm10 package is installed. Closes: #291386. - Add myself to uploaders. * GOTO Masanori - Make mkinitrd work with new ldd format which change is introduced in glibc 2.3.4. (Closes: #301455, #303281) This change also fixes amd64 mkinitrd breakage. (Closes: #279382, #292080, #295412, #295422, #297724) * Maximilian Attems - Resynchronise with Ubuntu: * Error message should refer to mdadm, not raidtools2. * Take /etc/mkinitrd/DSDT and put it in the initrd if it exists. * Use mktemp, not $$ for creating temporary directories. - Function module_exist recognizes modules in subdirs. Closes: #296894 - Fix upgrade path from woody for sparc arch. thanks to Jurij Smakov <[EMAIL PROTECTED]> Closes: #306219 - Use libdevmapper1.01 Closes: #266591, #298727, #303401 - Fix permissions of the initrd files. thanks to patch for debian/rules from Horms <[EMAIL PROTECTED]> Closes: #285767 * Sven Luther - Powerpc now defaults to MODULES=3Ddep. (Closes: #290329) Files:=20 d55fad2edd46b490476c6e640037e622 608 utils optional initrd-tools_0.1.79.dsc 048265f342b32440466b256296878af8 27103 utils optional initrd-tools_0.1.79.= tar.gz 6180afbac9c9516ec2ce696b4c8b237d 29558 utils optional initrd-tools_0.1.79_= all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFChYpTKN6ufymYLloRArmxAJ96ibimA1H8yQI3sjosX6nQyoRCngCglJ9/ NJ1vAGYLxonkH4h3dY1TPis=3D =3Dgt9k -----END PGP SIGNATURE----- ----- End forwarded message ----- --1ccMZA6j1vT5UqiK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFChZjdKN6ufymYLloRAh/aAKCUibLxWjHdzA2tuJL7cfz8YOHi9ACffIh9 MehFc/TKvmzF4JAlLq4Z84g= =kBEU -----END PGP SIGNATURE----- --1ccMZA6j1vT5UqiK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]