Bug#779081: Still a no go with open-vm-tools/open-vm-dkms 2:8.8.0+2012.05.21-724730-1+nmu2
Hi, The fix in wheezy backports does not correct the issue. I upgraded open-vm-tools and open-vm-dkms from this repository (to version 2:8.8.0+2012.05.21-724730-1+nmu2) and I still cannot compile vmhgfs. I still get the same error: CC [M] /var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.o /var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.c: In function 'HgfsPe rmission': /var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.c:1821:19: error: 'str uct dentry' has no member named 'd_alias' /var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.c:1821:19: warning: in itialization from incompatible pointer type [enabled by default] /var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.c:1821:19: error: 'str uct dentry' has no member named 'd_alias' make[4]: *** [/var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.o] Error 1 make[3]: *** [_module_/var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 Jacques
Bug#774661: closed by Christian Hofstaedtler z...@debian.org (Bug#774661: fixed in ruby-kramdown 1.4.2-2)
On 2015-04-08 at 09:36:16, Debian Bug Tracking System wrote: ruby-kramdown (1.4.2-2) unstable; urgency=medium . * Team upload. * Install missing data files (Closes: #774661) Perhaps if this was broken for everyone, it should be submitted as a stable release update for jessie? Francois -- http://fmarier.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Mark the stunnel RC bugs as pending
Processing commands for cont...@bugs.debian.org: package stunnel4 Limiting to bugs with field 'package' containing at least one of 'stunnel4' Limit currently set to 'package':'stunnel4' severity 771241 serious Bug #771241 [stunnel4] stunnel4 sometimes truncates long server reply Severity set to 'serious' from 'important' tags 771241 + pending Bug #771241 [stunnel4] stunnel4 sometimes truncates long server reply Added tag(s) pending. tags 782030 + pending Bug #782030 [stunnel4] stunnel4: Fails to restart on slow/loaded systems Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 771241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771241 782030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780858: marked as done (Massive I/O data corruption on Marvell Armada XP machines)
Your message dated Wed, 08 Apr 2015 12:00:17 + with message-id e1yfoex-00062v...@franck.debian.org and subject line Bug#780858: fixed in linux 3.16.7-ckt9-1 has caused the Debian Bug report #780858, regarding Massive I/O data corruption on Marvell Armada XP machines 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 ow...@bugs.debian.org immediately.) -- 780858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.16.7-ckt7-1 Severity: grave Tags: upstream Hi folks, We've upgraded a couple of our Marvell Armada XP based (armel/armhf) buildd machines to Jessie, and they've almost immediately fallen over with symptoms of really bad data corruption. On further investigation and discussion with some of the upstream maintainers for this hardware, this is a known issue with I/O coherency and there are patches available for testing: * 8f1e8ee28660018a935c7576b9af8ffe1feab54c is a patch to disable coherency for now, and * http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/330104.html is a second patch needed too (do not register custom DMA operations when coherency is disabled) I'm just doing a local build right now with these patches applied so I can test. More news ASAP. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux Source-Version: 3.16.7-ckt9-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. 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 780...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 08 Apr 2015 01:03:08 +0100 Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all linux-headers-3.16.0-4-all-alpha kernel-image-3.16.0-4-alpha-generic-di nic-modules-3.16.0-4-alpha-generic-di nic-wireless-modules-3.16.0-4-alpha-generic-di nic-shared-modules-3.16.0-4-alpha-generic-di serial-modules-3.16.0-4-alpha-generic-di usb-serial-modules-3.16.0-4-alpha-generic-di ppp-modules-3.16.0-4-alpha-generic-di pata-modules-3.16.0-4-alpha-generic-di cdrom-core-modules-3.16.0-4-alpha-generic-di scsi-core-modules-3.16.0-4-alpha-generic-di scsi-modules-3.16.0-4-alpha-generic-di scsi-common-modules-3.16.0-4-alpha-generic-di scsi-extra-modules-3.16.0-4-alpha-generic-di loop-modules-3.16.0-4-alpha-generic-di btrfs-modules-3.16.0-4-alpha-generic-di ext4-modules-3.16.0-4-alpha-generic-di isofs-modules-3.16.0-4-alpha-generic-di jfs-modules-3.16.0-4-alpha-generic-di xfs-modules-3.16.0-4-alpha-generic-di fat-modules-3.16.0-4-alpha-generic-di md-modules-3.16.0-4-alpha-generic-di multipath-modules-3.16.0-4-alpha-generic-di usb-modules-3.16.0-4-alpha-generic-di usb-storage-modules-3.16.0-4-alpha-generic-di fb-modules-3.16.0-4-alpha-generic-di input-modules-3.16.0-4-alpha-generic-di event-modules-3.16.0-4-alpha-generic-di mouse-modules-3.16.0-4-alpha-generic-di nic-pcmcia-modules-3.16.0-4-alpha-generic-di pcmcia-modules-3.16.0-4-alpha-generic-di nic-usb-modules-3.16.0-4-alpha-generic-di sata-modules-3.16.0-4-alpha-generic-di core-modules-3.16.0-4-alpha-generic-di crc-modules-3.16.0-4-alpha-generic-di crypto-modules-3.16.0-4-alpha-generic-di crypto-dm-modules-3.16.0-4-alpha-generic-di ata-modules-3.16.0-4-alpha-generic-di nbd-modules-3.16.0-4-alpha-generic-di squashfs-modules-3.16.0-4-alpha-generic-di virtio-modules-3.16.0-4-alpha-generic-di zlib-modules-3.16.0-4-alpha-generic-di fuse-modules-3.16.0-4-alpha-generic-di srm-modules-3.16.0-4-alpha-generic-di linux-headers-3.16.0-4-common linux-image-3.16.0-4-alpha-generic linux-headers-3.16.0-4-alpha-generic linux-image-3.16.0-4-alpha-smp
Bug#782030: Mark the stunnel RC bugs as pending
package stunnel4 severity 771241 serious tags 771241 + pending tags 782030 + pending thanks Hi, I've fixed both bugs in the jessie-freeze branch of the Git repository for the Debian package of stunnel: https://anonscm.debian.org/cgit/collab-maint/stunnel.git?h=jessie-freeze I'm also marking #771421 as serious; this has been long overdue, it should have been serious from the very start, since it does make stunnel practically unusable for users in certain legitimate configurations. Once again, apologies for taking so long to get around to fixing this, and again, many thanks to Joachim Falk for backporting the patch! I'm now about to ask the release team for a pre-approval for the new version of stunnel to migrate to Jessie. If they should grant it, then I guess I'll ask Laszlo to upload stunnel4-3:5.06-3 (Git rev. 82a1554); of course, if he's too busy, the usual ways of finding another sponsor would apply. Thanks to everyone involved for the interest in stunnel and for the patience! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org p.penc...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: Digital signature
Bug#781586: Info received (no 3.2 kernel ??)
Don't worry, your bug is closed already. The fixed package will be shipped with the next point release, in the meantime you can get it from stable-proposed-updates. https://wiki.debian.org/StableProposedUpdates On 04/07/2015 07:37 PM, MAGNE Stephane wrote: Hey i use debian 7, not jessie ! Stéphane Magne /DSI /Admin -Message d'origine- De : Debian Bug Tracking System [mailto:ow...@bugs.debian.org] Envoyé : mardi 7 avril 2015 16:12 À : MAGNE Stephane Objet : Bug#781586: Info received (no 3.2 kernel ??) Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Bernd Zeimetz b...@debian.org If you wish to submit further information on this problem, please send it to 781...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 781586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782103: libucto2: fails to upgrade from 'sid' - trying to overwrite /etc/ucto/tokconfig-en
On Tue, Apr 07, 2015 at 11:20:12PM +0200, Andreas Beckmann wrote: Package: libucto2 Version: 0.5.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../libucto2_0.5.5-1_amd64.deb ... Unpacking libucto2 (0.5.5-1) over (0.5.3-3.1+b1) ... dpkg: error processing archive /var/cache/apt/archives/libucto2_0.5.5-1_amd64.deb (--unpack): trying to overwrite '/etc/ucto/tokconfig-en', which is also in package ucto 0.5.3-3.1+b1 Errors were encountered while processing: /var/cache/apt/archives/libucto2_0.5.5-1_amd64.deb Thanks, will get to it. Bye, Joost -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 781915 in 0.18
Processing commands for cont...@bugs.debian.org: # The submitter wrote that it appears in Jessie, that's the current version in Jessie found 781915 0.18 Bug #781915 [apt-zip] Checksum fails and other issues in Jessie Ignoring request to alter found versions of bug #781915 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 781915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: #774661: Re: ruby-kramdown: kramdown data directory not found!
Processing control commands: severity -1 grave Bug #774661 [ruby-kramdown] ruby-kramdown: kramdown data directory not found! This is a bug, please report it! (RuntimeError) Severity set to 'grave' from 'important' -- 774661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781915: Checksum fails and other issues in Jessie
Hi, s3v wrote: After much tries e much time spent in investigating these errors, i definitely give up :) I suppose the command apt-get --print-uris ... don't provide sha256 hash anymore and apt-zip fails. This sounds similar if not identical to https://bugs.debian.org/638840 (apt-zip: wrong checksum: checksum calculation broken) which contains a patch. I couldn't yet reproduce your issue yet, but I hope I can within the next few days. Hopefully the patch from #638840 fixes this bug report, too. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774643: [Pkg-puppet-devel] Bug#774643: fix introduces problems for Foreman
Hi Michael, On 17:52 Wed 08 Apr , Michael Moll wrote: Hello, while I've been packaging Foreman (http://theforeman.org/) for Debian/jessie I encountered problems when having ruby-activerecord-deprecated-finders installed. The mere presence of ruby-activerecord-deprecated-finders on the system should not impact foreman. What kind of problems did you encounter? At the end I had to add a Conflicts line, so at the moment Foreman would only work with Puppetlabs packages if installed on the same host as the Puppet master. You could add a Conflicts: ruby-activerecord-deprecated-finders, which would still allow puppet from Debian proper to be installed (since ruby-ar-d-f is only a Recommends). Still, conflicting with other packages should be avoided altogether if there's a better way to handle the issue. Note that even if we do turn this into a Suggests, you should still make sure that either foreman is compatible with the gem, or the gem is not installed at all (it may have been installed manually). It should also be noted that (AFAIK) storeconfig was deprecated in Puppet 3 and it's use strongly discouraged. This has been previously discussed. In short, it's no pretty situation, but we either have to support this, or break the upgrade path for many setups and ask that people install activerecord 3 from rubygems.org on their systems. If we can do the former without causing too much trouble, IMHO we should do it. I do see the point that PuppetDB is not yet packaged as debian.org package, but Recommending a decreated package is introducing also some problems. The package itself is not deprecated by any means. It's part of the Debian archive and there's no reason to not Recommend it if it's needed. This should IMHO be shifted to a Suggests (and from the Foreman POV I'd like to see that in the first jessie release as Foreman would have to depend on Puppetlabs packages otherwise). Yes, this could be done. The case for Recommends was that installing just another gem to the system wouldn't harm. But if it causes that much trouble, we could move it to a Suggests and rely on a NEWS entry to have people install it by hand if needed. Regards, Apollon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#759725: #759725: postgresql-common: non-synchronous service postgresql start/stop/reload
Processing control commands: severity -1 normal Bug #759725 [postgresql-common] postgresql-common: non-synchronous service postgresql start/stop/reload Severity set to 'normal' from 'serious' -- 759725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759725: #759725: postgresql-common: non-synchronous service postgresql start/stop/reload
Control: severity -1 normal Re: b...@debian.org 2015-04-08 20150408150359.ga11...@mail.beuc.net I need to introduce sleep 1's in FusionForge to work-around this issue, so I believe this is not on par with Debian quality standards for a release. I'm raising the severity to serious accordingly. For reference, this issue is not present in CentOS7, while they migrated to systemd (their .service is attached). This is not an issue that affects typical usage so much that it breaks the package. I'll revert the severity accordingly. Fixing would be much easier if you provided a patch :) Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781238: marked as done (ruby-rest-client: CVE-2015-1820)
Your message dated Wed, 08 Apr 2015 15:52:22 + with message-id e1yfsh8-0007v9...@franck.debian.org and subject line Bug#781238: fixed in ruby-rest-client 1.6.7-6 has caused the Debian Bug report #781238, regarding ruby-rest-client: CVE-2015-1820 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 ow...@bugs.debian.org immediately.) -- 781238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-rest-client Severity: grave Tags: security Justification: user security hole This was assigned CVE-2015-1820: https://github.com/rest-client/rest-client/issues/369 Cheers, Moritz ---End Message--- ---BeginMessage--- Source: ruby-rest-client Source-Version: 1.6.7-6 We believe that the bug you reported is fixed in the latest version of ruby-rest-client, which is due to be installed in the Debian FTP archive. 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 781...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Badia s...@sebian.fr (supplier of updated ruby-rest-client 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 08 Apr 2015 12:01:20 +0200 Source: ruby-rest-client Binary: ruby-rest-client Architecture: source all Version: 1.6.7-6 Distribution: sid Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Sebastien Badia s...@sebian.fr Description: ruby-rest-client - simple REST client for Ruby Closes: 781238 Changes: ruby-rest-client (1.6.7-6) unstable; urgency=medium . * Team upload. * d/control: - Bump Standards-Version (no changes) - Use https and cgit URL for VCS-Browser - Wrap and sort control file - Apply upstream patch for CVE-2015-1820 (Closes: #781238) Checksums-Sha1: aebdd7fe06333c49c8f5c8df5f8df45f788a7e14 2099 ruby-rest-client_1.6.7-6.dsc f8bce5c2f36af775a61e0a8516a06037648f6a14 5500 ruby-rest-client_1.6.7-6.debian.tar.xz 86cf0aab60a407e475d5ef0176a20d832e6924f2 20926 ruby-rest-client_1.6.7-6_all.deb Checksums-Sha256: 3c2bb59c80ccc7bbd6d5786ca6af9fc454533ab6da32d64f876fcbc4ceb73d95 2099 ruby-rest-client_1.6.7-6.dsc ff39dc6474af5994311bd01475ac99146122782827a089825bced706728e04dc 5500 ruby-rest-client_1.6.7-6.debian.tar.xz 521aeaaf558b3ada471e16917f9c0ebbf43b7aee2396fa0d683413a3b8da113d 20926 ruby-rest-client_1.6.7-6_all.deb Files: b9033c38ab53ba36f81eca43ab64d380 2099 ruby optional ruby-rest-client_1.6.7-6.dsc d76a849b4d7f999e61c9c7bf37d61d89 5500 ruby optional ruby-rest-client_1.6.7-6.debian.tar.xz 933fbeb822ddb8887a4cee318b82192e 20926 ruby optional ruby-rest-client_1.6.7-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVJTwUAAoJEFwT1tuTBS4DQ6wP/izwaTvipiSeGnBH+jgQeZtT aUaDtwmUfkxvoKDQv/kD4Ad7ddbyILpiMso5oK/gVVGVGuwdp0yWxLCEBzUJ3xSK Kx720qiMJji24b/JsJpXTi0QadcgeeeTpSjmd0wWROIZb4P/p8zujYEipkZs9uky QUgQr+FUhMSNpokJNkrJ2Uus84o06pPfNmAImAer359NNoowZgiAvlfG0TEQ38zj qOCqnh2p/5HO7pGqfhXjKPgw/EgquaBJxal8JWkGxTE0LK1zx0sKjHsBOSERzcX3 3lGpZ4I0ngAOsAGhlA7rBU5zW1Tb4Ajuhp4by4QkSPKdORUhUEJc4StfY4zNe/0V Fs65MJYzU1eOvO7hwKM6anRQwUlbp+3NjVaU5+6Z1YqDKBMg4BmJpiex64/2gZhf i5pDWZHH7JlxOa32N6YGTKw4IAPQeOVLtjliQOahVissPWmzkd6J4HJm+LmiExEf aHaNSvLkQs1f5/4UwYoi8guFlJGxxXNXPa+V2N86oSMrY4d2MKGN5TTJ35n8AFyR 6Q5Bq+JIESgCfaTL4GF//raGoSZI4uzehB7kzkGqNneP7Ylg54IJgoXsC2J5kue5 yZ0ySb6F5v3MaC/VIGx6LPAfVMVdUZA2kyQAV4Oy86DDAWq8oTRKfSn6xyVhWNU5 Di9OdoVqwi6w24pbtvhc =wgg2 -END PGP SIGNATUREEnd Message---
Bug#774643: fix introduces problems for Foreman
Hello, while I've been packaging Foreman (http://theforeman.org/) for Debian/jessie I encountered problems when having ruby-activerecord-deprecated-finders installed. At the end I had to add a Conflicts line, so at the moment Foreman would only work with Puppetlabs packages if installed on the same host as the Puppet master. It should also be noted that (AFAIK) storeconfig was deprecated in Puppet 3 and it's use strongly discouraged. I do see the point that PuppetDB is not yet packaged as debian.org package, but Recommending a decreated package is introducing also some problems. This should IMHO be shifted to a Suggests (and from the Foreman POV I'd like to see that in the first jessie release as Foreman would have to depend on Puppetlabs packages otherwise). Best Regards -- Michael Moll -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769351: docker.io: statically linked against libc6 without a Built-Using: field
On 6 April 2015 at 19:03, Tianon Gravi admwig...@gmail.com wrote: On 3 April 2015 at 17:16, Felipe Sateler fsate...@debian.org wrote: Hi, please find attached a patch implementing this, stealing from the patch at [1] implementing same thing for gdb-avr. Neat, thanks! It's not as cool as I was hoping for (something that detects use of libc and adds appropriate Built-Using generically based on that), but it'll do just fine, and solves the problem. Yes, there should probably be a helper to do this. I have used libc-dev-bin because libc-dev is a virtual package, libcN-dev has a different N in different architectures. Yeah, that's fair. :) Another option that might be worth trying (for a little more defensibility) is something with dpkg -S, ala dpkg -S /usr/lib/x86_64-linux-gnu/libc.a, but this is much definitely better than not having anything at all. Unfortunately, dpkg -S is slow, so I'm not sure it is the best option. A better one might be to somehow tell gcc to print the library it is using when told -lc. I've applied the change in Git, and plan to get a release of 1.6.0~rc4 including it in experimental ASAP. :) -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: #759725: postgresql-common: non-synchronous service postgresql start/stop/reload
Processing control commands: severity -1 serious Bug #759725 [postgresql-common] postgresql-common: non-synchronous service postgresql start/stop/reload Severity set to 'serious' from 'normal' -- 759725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782161: rspec 3 does not have --pattern option
package: gem2deb-test-runner version: 0.12 severity: critical After updating rspec to 3.2 from experimental, tests fail with /usr/bin/ruby2.1 -I/usr/lib/ruby/vendor_ruby /usr/bin/gem2deb-test-runner Running tests for ruby2.1 using debian/ruby-tests.rake ... /usr/bin/ruby2.1 -I /usr/lib/ruby/exe/rspec --pattern ./spec/\*\*/\*_spec.rb /usr/bin/ruby2.1: invalid option --pattern (-h will show valid options) (RuntimeError) /usr/bin/ruby2.1 -I /usr/lib/ruby/exe/rspec --pattern ./spec/\*\*/\*_spec.rb failed the gem tried was open_graph_reader signature.asc Description: OpenPGP digital signature
Processed: Re: libflint-2.4.5: fails to upgrade from 'sid' - trying to overwrite /usr/share/flint/CPimport.txt
Processing control commands: found -1 2.4.5-2 Bug #779584 [libflint-2.4.5] libflint-2.4.5: fails to upgrade from 'sid' - trying to overwrite /usr/share/flint/CPimport.txt Marked as found in versions flint/2.4.5-2. -- 779584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779584: libflint-2.4.5: fails to upgrade from 'sid' - trying to overwrite /usr/share/flint/CPimport.txt
Followup-For: Bug #779584 Control: found -1 2.4.5-2 Hi, the recently added Replaces is not sufficient to properly fix this bug, it needs a corresponding Breaks as well. Otherwise installing and removing libflint-2.4.5 will cause a previously installed libflint-2.4.4 to be crippled (some files will be missing afterwards) instead of being removed. From the attached log: 0m47.8s ERROR: FAIL: After purging files have disappeared: /usr/share/flint/CPimport.txt owned by: libflint-2.4.5 0m47.8s ERROR: FAIL: After purging files have been modified: /var/lib/dpkg/info/libflint-2.4.4.list not owned Andreas libflint-2.4.4=2.4.4-2_libflint-2.4.5=2.4.5-2.log.gz Description: application/gzip
Processed: user release.debian....@packages.debian.org, usertagging 779255, tagging 779255
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was ni...@thykier.net). usertags 779255 jessie-can-defer There were no usertags set. Usertags are now: jessie-can-defer. tags 779255 + jessie-ignore Bug #779255 [qemubuilder] qemubuilder: unable to build anything; can't find .DSC file Added tag(s) jessie-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 779255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782160: chrony: Multiple issues: CVE-2015-1821 CVE-2015-1822 CVE-2015-1853
Source: chrony Version: 1.30-1 Severity: grave Tags: security upstream patch fixed-upstream *** /tmp/chrony.reportbug Package: chrony Severity: FILLINSEVERITY Tags: security Hi, the following vulnerabilities were published for chrony. Note, that I choosed severity grave, since two CVEs seem to potentially be exploited to execute arbitrary code and chronyd is running as root. Please lower the severity if you don't agree (I don't know chrony very well): CVE-2015-1821[0]: Heap out of bound write in address filter CVE-2015-1822[1]: uninitialized pointer in cmdmon reply slots CVE-2015-1853[2]: authentication doesn't protect symmetric associations against DoS attacks If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-1821 [1] https://security-tracker.debian.org/tracker/CVE-2015-1822 [2] https://security-tracker.debian.org/tracker/CVE-2015-1853 Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#753442: debootstrap: host's /run/shm gets unmounted after debootstrap run
Processing control commands: found -1 1.0.48 Bug #753442 [debootstrap] debootstrap: host's /run/shm gets unmounted after debootstrap run Marked as found in versions debootstrap/1.0.48. fixed -1 1.0.51 Bug #753442 [debootstrap] debootstrap: host's /run/shm gets unmounted after debootstrap run Marked as fixed in versions debootstrap/1.0.51. -- 753442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753442: debootstrap: host's /run/shm gets unmounted after debootstrap run
Control: found -1 1.0.48 Control: fixed -1 1.0.51 Hi Daniel, Daniel Reichelt deb...@nachtgeist.net (2014-11-14): I seem to be unable to reproduce it with 1.0.60~bpo70+1 but I can with 1.0.48+deb7u1; I didn't spot anything obvious from a very quick look, but I'll try to track this down a bit later (probably after the release sprint). This bug actually is a duplicate of #702861 which was fixed in 1.0.51 yeah, thanks for the info. I'm not sure why but I don't seem to have received a copy of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753442#80… anyway what the commit message says, the bug reference, and the change itself look like a good thing to have in stable, so I'll double check and try to have that in the next point release. Mraw, KiBi. signature.asc Description: Digital signature
Processed (with 3 errors): cloning 767040, severity of -1 is important, reassign -1 to release-notes
Processing commands for cont...@bugs.debian.org: clone 767040 -1 Bug #767040 [clock-setup] Superblock time check causes problems for fsck in initramfs Bug #780261 [clock-setup] fsck scan of crypto-root on EVERY startup Failed to clone 767040: Bug is marked as being merged with others. Use an existing clone. severity -1 important Failed to set severity of Bug -1 to important: The 'bug' parameter (-1) to Debbugs::Control::set_severity did not pass regex check reassign -1 release-notes Failed to clear fixed versions and reopen on -1: The 'bug' parameter (-1) to Debbugs::Control::set_package did not pass regex check thanks Stopping processing here. Please contact me if you need assistance. -- Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774643: [Pkg-puppet-devel] Bug#774643: fix introduces problems for Foreman
Hi Apollon, On Wed, Apr 08, 2015 at 07:26:03PM +0300, Apollon Oikonomopoulos wrote: The mere presence of ruby-activerecord-deprecated-finders on the system should not impact foreman. What kind of problems did you encounter? The actual output: root@jessy:~# /usr/sbin/foreman-rake db:migrate rake aborted! NoMethodError: undefined method `matchers' for Method:Class /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `block in require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in `load_dependency' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:26:in `block in on_load' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in `each' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in `on_load' /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `block in require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in `load_dependency' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/will_paginate-3.0.7/lib/will_paginate/active_record.rb:6:in `top (required)' /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `block in require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in `load_dependency' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/will_paginate-3.0.7/lib/will_paginate/railtie.rb:10:in `block (2 levels) in class:Railtie' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:26:in `block in on_load' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in `each' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in `on_load' /usr/share/foreman/vendor/ruby/2.1.0/gems/will_paginate-3.0.7/lib/will_paginate/railtie.rb:9:in `block in class:Railtie' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:30:in `instance_exec' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:30:in `run' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:55:in `block in run_initializers' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:54:in `each' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:54:in `run_initializers' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/application.rb:136:in `initialize!' /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/railtie/configurable.rb:30:in `method_missing' /usr/share/foreman/config/environment.rb:12:in `top (required)' /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `block in require' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in `load_dependency' /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in `require'
Processed: Patch (potential NMU) for multiple RC-grade issues in apt-zip
Processing control commands: tag -1 + patch Bug #782179 [apt-zip] apt-zip: apt-zip-list --aptgetaction=update doesn't do anything because apt-get -qq --print-uris update outputs nothing Ignoring request to alter tags of bug #782179 to the same tags previously set -- 782179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767040: marked as done (Superblock time check causes problems for fsck in initramfs)
Your message dated Thu, 09 Apr 2015 00:48:35 + with message-id e1yg0e3-0006zo...@franck.debian.org and subject line Bug#767040: fixed in clock-setup 0.123 has caused the Debian Bug report #767040, regarding Superblock time check causes problems for fsck in initramfs 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 ow...@bugs.debian.org immediately.) -- 767040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: e2fsprogs Version: 1.42.12-1 Severity: important Tags: upstream We discussed this previously in person, but unfortunately the proposed solution doesn't work. The plan for jessie (yes I know it's late) is to mount and fsck the root and (if separate) /usr filesystems from initramfs code, before handing over to the real init system. e2fsck complains if the superblock write time is in the future, and because the RTC is set to local time on some systems, we are doing the necessary correction of system time in the initramfs. This is undesirable because changing the time zone may now require an initramfs rebuild. You said that this check could be disabled in a configuration file, e2fsck.conf, and we can create that in the initramfs. This works in so far as it suppresses warnings while the initramfs code is running. Unfortunately, every init system currently still checks the root file-system again. If the RTC is set to local time and that is east of UTC, the first fsck sets the write time in the future, and the second fsck warns. Please disable this warning by default. Ben. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages e2fsprogs depends on: ii e2fslibs1.42.12-1 ii libblkid1 2.25.1-5 ii libc6 2.19-12 ii libcomerr2 1.42.12-1 ii libss2 1.42.12-1 ii libuuid12.25.1-5 ii util-linux 2.25.1-5 e2fsprogs recommends no packages. Versions of packages e2fsprogs suggests: pn e2fsck-static none pn gpart none ii parted 3.2-6 -- no debconf information ---End Message--- ---BeginMessage--- Source: clock-setup Source-Version: 0.123 We believe that the bug you reported is fixed in the latest version of clock-setup, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated clock-setup 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 Apr 2015 00:49:23 +0100 Source: clock-setup Binary: clock-setup Architecture: source Version: 0.123 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Description: clock-setup - set up clock (udeb) Closes: 767040 Changes: clock-setup (0.123) unstable; urgency=medium . * Disable e2fsck superblock time check if RTC is set to local time (Closes: #767040) Checksums-Sha1: 967a86cad01290864e6072d63ed960708d04c479 1622 clock-setup_0.123.dsc bd96ffc419e42594d97d69f710560ab0f211405a 75372 clock-setup_0.123.tar.xz Checksums-Sha256: ad861a8568e2e704b1543a321283f3c7f9c211e5d1119fc93fdea9fb5b0d4069 1622 clock-setup_0.123.dsc 668d8000a5e8fe6cce56c69a5a606480f5612b2e655ebe630561b72b7ab38194 75372 clock-setup_0.123.tar.xz Files: 383610dc2c0628634259202cf0ecbd61 1622 debian-installer standard clock-setup_0.123.dsc 1ef0ef534cf7ecceb15f578c6c91a594 75372 debian-installer standard clock-setup_0.123.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVSXKrOe/yOyVhhEJAQrrhg//YIbrQHoZxBo0V6LfwEw5722hnLrHTiN7 AwpyYo5XC4f1j+6vbnVYci/IKbGrid0RkE+hITjHOFE3STWqSqU3zdtUaUCXRtsB WCEe2yOQC8TpwlQxWsOxvwZ3YzMnmV6sq7fn1iNMsUhGpNYPnsVRrCD1AY06906Z MYvDKJOO4iRDncXVnaMziSik4nLpMHIkaQrHDfRlIBAHJYOWdTA0O441C55XN19W
Processed: severity of 782178 is important, tagging 782178, reassign 782178 to release-notes
Processing commands for cont...@bugs.debian.org: severity 782178 important Bug #782178 [clock-setup] Superblock time check causes problems for fsck in initramfs Severity set to 'important' from 'serious' tags 782178 - pending upstream Bug #782178 [clock-setup] Superblock time check causes problems for fsck in initramfs Removed tag(s) upstream and pending. reassign 782178 release-notes Bug #782178 [clock-setup] Superblock time check causes problems for fsck in initramfs Bug reassigned from package 'clock-setup' to 'release-notes'. Ignoring request to alter found versions of bug #782178 to the same values previously set Ignoring request to alter fixed versions of bug #782178 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 782178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces
Holger Wansing li...@wansing-online.de (2015-02-14): Heiko Ernst gipfelsturm...@gmx.net wrote: this is my installer syslog [...] Feb 10 07:52:49 debootstrap: Creating /etc/network/interfaces. Hmm, at the beginning of the installation, /etc/network/interfaces is created and apparently works (OP did not complain about network problems _during_installation_ ). But at the end of install: Feb 10 08:14:44 finish-install: info: Running /usr/lib/finish- install.d/55netcfg-copy-config Feb 10 08:14:45 netcfg[29439]: INFO: Starting netcfg v.1.127 (built 20150104-2209) Feb 10 08:14:45 netcfg[29439]: INFO: Starting netcfg v.1.127 (built 20150104-2209) Feb 10 08:14:45 netcfg[29439]: DEBUG: No interface given; clearing /etc/network/interfaces Feb 10 08:14:45 netcfg[29439]: DEBUG: Writing informative header Feb 10 08:14:45 netcfg[29439]: DEBUG: Success! Feb 10 08:14:45 netcfg[29439]: DEBUG: Writing loopback interface Feb 10 08:14:45 netcfg[29439]: DEBUG: Success! /etc/network/interfaces is wiped out! This shouldn't have happened in a shell-only install ... Yeah, that looks fishy. Not sure whether there's something getting confused because of eth0 vs. wlan0, and/or because of the IPv6 configuration (see the bug that's getting fixed for D-I Jessie RC3)… With a little luck I'll stumble upon something similar while testing wireless things in the upcoming days. Mraw, KiBi. signature.asc Description: Digital signature
Bug#781915: Patch (potential NMU) for multiple RC-grade issues in apt-zip
Control: tag -1 + patch
Hi,
attached a debdiff which should fix the following issues:
#782179 [G|+| ] [apt-zip] apt-zip: apt-zip-list
--aptgetaction=update doesn't do anything because apt-get -qq
--print-uris update outputs nothing
#781915 [G| | ] [apt-zip] Checksum fails and other issues in
Jessie
#638840 [i|+| ] [apt-zip] apt-zip: wrong checksum: checksum
calculation broken
The last one (#638840) is currently only set to severity important,
but IMHO validates for severity grave, too.
This patch does not fix #718376 (Most deb data.tar member files are
unsupported) and there seem similar issues with package lists.
Additionally the patch also fixes this non-RC and no-op issue:
#624368 [m| | ] [apt-zip] Updating the apt-zip Uploaders list
I'll check with the release team if the attached patch would be
suitable for a freeze exception. If so, I'd upload it as NMU either
directly or to DELAYED/1 to get it in Jessie before the deadline for
the release.
Regards, Axel
--
,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
diff -Nru apt-zip-0.18/apt-zip-inst apt-zip-0.18+nmu1/apt-zip-inst
--- apt-zip-0.18/apt-zip-inst 2008-02-01 08:07:37.0 +0100
+++ apt-zip-0.18+nmu1/apt-zip-inst 2015-04-09 03:44:21.0 +0200
@@ -36,8 +36,9 @@
tar xvf ${MEDIUM}/${APTZIPTARFILE} |
while read FILE
do
- [ `basename $FILE .bz2` != $FILE ] bunzip2 -f $FILE
- [ `basename $FILE .gz` != $FILE ] gunzip -f $FILE
+ [ ! -s $FILE ] rm -f $FILE
+ [ -e $FILE -a `basename $FILE .bz2` != $FILE ] bunzip2
-f $FILE
+ [ -e $FILE -a `basename $FILE .gz` != $FILE ] gunzip
-f $FILE
done
rm -f foo-stamp
)
diff -Nru apt-zip-0.18/apt-zip-list apt-zip-0.18+nmu1/apt-zip-list
--- apt-zip-0.18/apt-zip-list 2008-02-01 07:57:01.0 +0100
+++ apt-zip-0.18+nmu1/apt-zip-list 2015-04-09 02:35:38.0 +0200
@@ -33,9 +33,15 @@
TMP=$(tempfile -p aptzip)
TEMP=$(tempfile -p aptzip)
+if [ $APTGETACTION = update ]; then
+APTGETQUIETLEVEL=-q
+else
+APTGETQUIETLEVEL=-qq
+fi
+
[ -n $PACKAGES ] apt-get ${APTGETEXTRAOPTS} -qq --print-uris install
$PACKAGES $TMP
-[ -n $APTGETACTION ] apt-get ${APTGETEXTRAOPTS} -qq --print-uris
${APTGETACTION} $TMP
-grep $GREP $TMP | tr -d ' | sed 's/SHA256://' | sort -u $TEMP
+[ -n $APTGETACTION ] apt-get ${APTGETEXTRAOPTS} ${APTGETQUIETLEVEL}
--print-uris ${APTGETACTION} $TMP
+grep $GREP $TMP | tr -d ' | sed 's/MD5Sum://' | sort -u $TEMP
if [ $? != 0 ]
then
error apt-get failed
diff -Nru apt-zip-0.18/debian/changelog apt-zip-0.18+nmu1/debian/changelog
--- apt-zip-0.18/debian/changelog 2008-02-01 08:18:33.0 +0100
+++ apt-zip-0.18+nmu1/debian/changelog 2015-04-09 03:49:29.0 +0200
@@ -1,3 +1,20 @@
+apt-zip (0.18+nmu1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload
+ * Fix updating package lists by using -q instead of -qq for apt-get
+update (Closes: #782179)
+ * Properly handle package list downloads (Closes: #781915)
++ Don't try to bunzip2 empty files
++ Don't save files with .bz2 or .gz suffix without suffix
++ Don't try to add .bz2 or .gz suffix to URIs which already have them.
++ Honour the fact that apt can't know checksums of package list in
+ advance.
+ * Fix checksum verification of packages (Closes: #638840; patch by
+Rainer Dorsch rdor...@web.de, thanks!)
+ * Remove François Févotte from Uploaders (Closes: #624368)
+
+ -- Axel Beckert a...@debian.org Thu, 09 Apr 2015 01:30:22 +0200
+
apt-zip (0.18) unstable; urgency=medium
* Use sha256 instead of md5 for checksum, as in apt 0.7.7.
diff -Nru apt-zip-0.18/debian/control apt-zip-0.18+nmu1/debian/control
--- apt-zip-0.18/debian/control 2008-02-01 08:24:00.0 +0100
+++ apt-zip-0.18+nmu1/debian/control2015-04-09 01:50:07.0 +0200
@@ -4,7 +4,7 @@
Build-Depends-Indep: docbook-utils, docbook
Build-Depends: debhelper (= 5), cdbs
Maintainer: Giacomo Catenazzi c...@debian.org
-Uploaders: Eddy Petrișor eddy.petri...@gmail.com, François Févotte
francois.fevo...@ensta.org
+Uploaders: Eddy Petrișor eddy.petri...@gmail.com
Standards-Version: 3.7.3
Homepage: http://alioth.debian.org/projects/apt-zip
diff -Nru apt-zip-0.18/methods/wget apt-zip-0.18+nmu1/methods/wget
--- apt-zip-0.18/methods/wget 2008-02-01 07:54:37.0 +0100
+++ apt-zip-0.18+nmu1/methods/wget 2015-04-09 03:34:04.0 +0200
@@ -31,10 +31,12 @@
[ ! ${USECHECKSUMS} = 'no' ] cat -EOF
check(){
[ ! -r \$1 ] return 1
+ [ ! -s \$1 ] return 1
[ \$2 = 0 ] return \$3
[ \$2 = ] return
Processed: Patch (potential NMU) for multiple RC-grade issues in apt-zip
Processing control commands: tag -1 + patch Bug #781915 [apt-zip] Checksum fails and other issues in Jessie Ignoring request to alter tags of bug #781915 to the same tags previously set -- 781915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780261: marked as done (fsck scan of crypto-root on EVERY startup)
Your message dated Thu, 09 Apr 2015 00:48:35 + with message-id e1yg0e3-0006zo...@franck.debian.org and subject line Bug#767040: fixed in clock-setup 0.123 has caused the Debian Bug report #767040, regarding fsck scan of crypto-root on EVERY startup 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 ow...@bugs.debian.org immediately.) -- 767040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.119 Severity: important Just what the topic says. I have encrypted root and plymouth and the bios clock runs in local time. And on every boot, fsck scans the rootfs in forced mode which takes a while. This started happening only after dist-upgrading today, and I also installed plymouth for other reasons. Regards, Eduard. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 9.6M Oct 25 10:32 /boot/initrd.img-3.12.31+ -rw-r--r-- 1 root root 9.7M Oct 11 12:03 /boot/initrd.img-3.16.2+ -rw-r--r-- 1 root root 9.6M Feb 10 22:00 /boot/initrd.img-3.18.1+ -rw-r--r-- 1 root root 12M Mar 11 10:33 /boot/initrd.img-3.19.0+ -rw-r--r-- 1 root root 12M Mar 11 11:21 /boot/initrd.img-3.19.1+ -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.19.1+ root=UUID=5df203d7-fe19-44e6-87e9-3228b863f54a ro resume=/dev/sda2 init=/bin/systemd -- resume RESUME=/dev/hda7 -- /proc/filesystems ext3 ext4 fuseblk -- lsmod Module Size Used by binfmt_misc12846 1 cfg80211 176397 0 cpufreq_powersave 12454 0 cpufreq_conservative14184 0 cpufreq_userspace 12525 0 cpufreq_stats 12871 0 nfsd 79048 11 nfs_acl12511 1 nfsd nfs 113704 0 lockd 59474 2 nfs,nfsd grace 12622 1 lockd fscache42337 1 nfs sunrpc164060 18 nfs,nfsd,lockd,nfs_acl ib_iser40609 0 libiscsi 39966 1 ib_iser scsi_transport_iscsi65287 3 ib_iser,libiscsi rdma_cm31917 1 ib_iser iw_cm 27182 1 rdma_cm ib_cm 31303 1 rdma_cm ib_sa 27180 2 rdma_cm,ib_cm ib_mad 36452 2 ib_cm,ib_sa ib_core66574 6 rdma_cm,ib_cm,ib_sa,iw_cm,ib_mad,ib_iser ib_addr13169 2 rdma_cm,ib_core snd_hda_codec_hdmi 37198 1 nvidia 10991750 28 kvm_amd47645 0 kvm 249242 1 kvm_amd pcspkr 12595 0 serio_raw 12894 0 k10temp12634 0 snd_hda_codec_realtek59184 1 snd_hda_codec_generic47272 1 snd_hda_codec_realtek nvidiafb 35028 0 snd_hda_intel 22235 5 vgastate 12617 1 nvidiafb wmi13243 0 snd_hda_controller 22145 1 snd_hda_intel snd_hda_codec 73714 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller button 12988 0 snd_hwdep 13189 1 snd_hda_codec i2c_piix4 12665 0 radeon 1127138 0 ttm62050 1 radeon drm_kms_helper 70432 1 radeon drm 224816 5 ttm,drm_kms_helper,nvidia,radeon i2c_algo_bit 12834 1 radeon i2c_core 24556 6 drm,i2c_piix4,drm_kms_helper,i2c_algo_bit,nvidia,radeon w83627ehf 35466 0 hwmon_vid 12388 1 w83627ehf k8temp 12711 0 nf_conntrack_irc 12427 0 nf_conntrack_ftp 12687 0 nf_conntrack 67672 2 nf_conntrack_ftp,nf_conntrack_irc acpi_cpufreq 13166 0 processor 28021 1 acpi_cpufreq thermal_sys23300 1 processor snd_pcm_oss36969 0 snd_pcm73066 5 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller snd_timer 22595 1 snd_pcm snd_mixer_oss 17991 1 snd_pcm_oss snd53213 20 snd_hda_codec_realtek,snd_pcm_oss,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_mixer_oss soundcore 13031 2 snd,snd_hda_codec evdev 17521 40 psmouse83740 0 fuse 72148 3 loop 22627 0 autofs427584 2 ext4 287220 3 crc16 12343 1 ext4 jbd2 57171 1 ext4 mbcache13528 1 ext4 xts12679 1
Bug#762465: RE
-- Achtung jeder Körper, Hier kommt ein Unternehmen, bieten ein Darlehen zu niedrigen Zinssatz von 3% zu kommen, haben Sie leiden für die finanzielle Hilfe? Sie müssen eine dringende Darlehen zu zahlen Sie Ihre Rechnungen? Wir bieten alle Arten von Krediten. bei Interesse mailen Sie uns bitte via wernermiller...@hotmail.com Motor: Ihre Fortschritte ist unser Cosinus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch (potential NMU) for multiple RC-grade issues in apt-zip
Processing control commands: tag -1 + patch Bug #781915 [apt-zip] Checksum fails and other issues in Jessie Added tag(s) patch. -- 781915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782179: apt-zip: apt-zip-list --aptgetaction=update doesn't do anything because apt-get -qq --print-uris update outputs nothing
Package: apt-zip
Version: 0.18
Severity: grave
Tags: patch jessie sid
Justification: Updating package lists silently broken
Dear Maintainer,
apt-zip-list --aptgetaction=update does nothing on Jessie:
# apt-zip-list --medium=/tmp/apt-zip-test/ --skip-mount --aptgetaction=update
-o tar --no-md5
The download size is unknown in 0 files.
#
Reason is that apt-get -qq --print-uris update has no output at all
anymore:
# apt-get -qq --print-uris update
#
The expected output comes back if I remove one q:
# apt-get -q --print-uris update
'http://debian.ethz.ch/debian/dists/jessie/main/source/Sources.bz2'
debian.ethz.ch_debian_dists_jessie_main_source_Sources 0 :
'http://debian.ethz.ch/debian/dists/jessie/main/binary-amd64/Packages.bz2'
debian.ethz.ch_debian_dists_jessie_main_binary-amd64_Packages 0 :
'http://debian.ethz.ch/debian/dists/jessie/main/i18n/Translation-en.bz2'
debian.ethz.ch_debian_dists_jessie_main_i18n_Translation-en 0 :
'http://debian.ethz.ch/debian/dists/jessie/InRelease'
debian.ethz.ch_debian_dists_jessie_InRelease 0
[...]
#
The following patch fixes the issue:
diff --git a/apt-zip-list b/apt-zip-list
index f5d7acb..49bb69e 100755
--- a/apt-zip-list
+++ b/apt-zip-list
@@ -33,9 +33,15 @@ APTGETEXTRAOPTS=${APTGETEXTRAOPTS} -o Debug::NoLocking=true
TMP=$(tempfile -p aptzip)
TEMP=$(tempfile -p aptzip)
+if [ $APTGETACTION = update ]; then
+APTGETQUIETLEVEL=-q
+else
+APTGETQUIETLEVEL=-qq
+fi
+
[ -n $PACKAGES ] apt-get ${APTGETEXTRAOPTS} -qq --print-uris install
$PACKAGES $TMP
-[ -n $APTGETACTION ] apt-get ${APTGETEXTRAOPTS} -qq --print-uris
${APTGETACTION} $TMP
+[ -n $APTGETACTION ] apt-get ${APTGETEXTRAOPTS} ${APTGETQUIETLEVEL}
--print-uris ${APTGETACTION} $TMP
grep $GREP $TMP | tr -d ' | sed 's/MD5Sum://' | sort -u $TEMP
if [ $? != 0 ]
then
(The above patch can be applied after the patch from #638840 has been
applied.)
-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages apt-zip depends on:
ii apt 1.0.9.7
apt-zip recommends no packages.
apt-zip suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [PATCH] apt-key del keyid is case sensitive
Processing control commands: severity -1 critical Bug #781696 [apt] apt-key del keyid is case sensitive Severity set to 'critical' from 'normal' tag -1 + security patch jessie sid Bug #781696 [apt] apt-key del keyid is case sensitive Added tag(s) sid, security, jessie, and patch. -- 781696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 767040 to clock-setup, tagging 767040
Processing commands for cont...@bugs.debian.org: reassign 767040 clock-setup Bug #767040 [e2fsprogs] Superblock time check causes problems for fsck in initramfs Bug #780261 [e2fsprogs] fsck scan of crypto-root on EVERY startup Bug reassigned from package 'e2fsprogs' to 'clock-setup'. Bug reassigned from package 'e2fsprogs' to 'clock-setup'. No longer marked as found in versions e2fsprogs/1.42.12-1. No longer marked as found in versions e2fsprogs/1.42.12-1. Ignoring request to alter fixed versions of bug #767040 to the same values previously set Ignoring request to alter fixed versions of bug #780261 to the same values previously set tags 767040 + pending Bug #767040 [clock-setup] Superblock time check causes problems for fsck in initramfs Bug #780261 [clock-setup] fsck scan of crypto-root on EVERY startup Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 767040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767040 780261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767040: Superblock time check causes problems for fsck in initramfs
On Sat, 14 Mar 2015 11:29:32 +0100 Beck, Andre b...@ibh.de wrote: Hi, isn't that a bug in e2fsck anyway? There is accept_time_fudge which defaults to true and should take care of this situation. Possibly; in any case it still logs a warning even when it 'accepts' the incorrect time. I don't know why it's also performing a full fsck on some systems. Even when it wouldn't default to true, my e2fsck.conf already had its alias buggy_init_scripts set to 1. Nevertheless, I'm briefly seeing an fsck running now on every boot (CMOS clock is ticking CET localtime). BTW, no longer fixing up system time before fsck is one thing, but what about mounting? Ain't that prone to create file timestamps in the future for everything that is touched before the init system has a chance to run a correctly parameterized hwclock? [...] No, because the filesystem is mounted read-only initially. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#770492: [RFC PATCH RESEND] vfs: Move security_inode_killpriv() after permission checks
On Sat, Jan 17, 2015 at 11:26:46PM +, Ben Hutchings wrote: chown() and write() should clear all privilege attributes on a file - setuid, setgid, setcap and any other extended privilege attributes. However, any attributes beyond setuid and setgid are managed by the LSM and not directly by the filesystem, so they cannot be set along with the other attributes. Currently we call security_inode_killpriv() in notify_change(), but in case of a chown() this is too early - we have not called inode_change_ok() or made any filesystem-specific permission/sanity checks. Add a new function setattr_killpriv() which calls security_inode_killpriv() if necessary, and change the setattr() implementation to call this in each filesystem that supports xattrs. This assumes that extended privilege attributes are always stored in xattrs. Compile-tested only. XXX This is a silent change to the VFS API, but we should probably change something so OOT filesystems fail to compile if they aren't updated to call setattr_killpriv(). This is still a problem. Any feedback about the patch? Reported-by: Ben Harris bj...@cam.ac.uk References: https://bugs.debian.org/770492 --- drivers/staging/lustre/lustre/llite/llite_lib.c | 4 fs/9p/vfs_inode.c | 4 fs/9p/vfs_inode_dotl.c | 4 fs/attr.c | 32 + fs/btrfs/inode.c| 4 fs/ceph/inode.c | 4 fs/cifs/inode.c | 11 - fs/ext2/inode.c | 4 fs/ext3/inode.c | 4 fs/ext4/inode.c | 4 fs/f2fs/file.c | 4 fs/fuse/dir.c | 15 +++- fs/fuse/file.c | 3 ++- fs/fuse/fuse_i.h| 2 +- fs/gfs2/inode.c | 3 +++ fs/hfs/inode.c | 4 fs/hfsplus/inode.c | 4 fs/jffs2/fs.c | 4 fs/jfs/file.c | 4 fs/kernfs/inode.c | 17 + fs/libfs.c | 3 +++ fs/nfs/inode.c | 11 +++-- fs/ocfs2/file.c | 6 - fs/reiserfs/inode.c | 4 fs/ubifs/file.c | 4 fs/xfs/xfs_acl.c| 3 ++- fs/xfs/xfs_file.c | 2 +- fs/xfs/xfs_ioctl.c | 2 +- fs/xfs/xfs_iops.c | 16 ++--- fs/xfs/xfs_iops.h | 10 ++-- include/linux/fs.h | 1 + mm/shmem.c | 4 32 files changed, 176 insertions(+), 25 deletions(-) diff --git a/drivers/staging/lustre/lustre/llite/llite_lib.c b/drivers/staging/lustre/lustre/llite/llite_lib.c index a8bcc51..2a714b2 100644 --- a/drivers/staging/lustre/lustre/llite/llite_lib.c +++ b/drivers/staging/lustre/lustre/llite/llite_lib.c @@ -1434,6 +1434,10 @@ int ll_setattr_raw(struct dentry *dentry, struct iattr *attr, bool hsm_import) spin_unlock(lli-lli_lock); } + rc = setattr_killpriv(dentry, attr); + if (rc) + return rc; + /* We always do an MDS RPC, even if we're only changing the size; * only the MDS knows whether truncate() should fail with -ETXTBUSY */ diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c index 296482f..735cbf84 100644 --- a/fs/9p/vfs_inode.c +++ b/fs/9p/vfs_inode.c @@ -1130,6 +1130,10 @@ static int v9fs_vfs_setattr(struct dentry *dentry, struct iattr *iattr) if (S_ISREG(dentry-d_inode-i_mode)) filemap_write_and_wait(dentry-d_inode-i_mapping); + retval = setattr_killpriv(dentry, iattr); + if (retval) + return retval; + retval = p9_client_wstat(fid, wstat); if (retval 0) return retval; diff --git a/fs/9p/vfs_inode_dotl.c b/fs/9p/vfs_inode_dotl.c index 02b64f4..f3ca76d 100644 --- a/fs/9p/vfs_inode_dotl.c +++ b/fs/9p/vfs_inode_dotl.c @@ -583,6 +583,10 @@ int v9fs_vfs_setattr_dotl(struct dentry *dentry, struct iattr *iattr) if (S_ISREG(inode-i_mode)) filemap_write_and_wait(inode-i_mapping); + retval = setattr_killpriv(dentry, iattr); + if (retval) + return retval; + retval = p9_client_setattr(fid, p9attr); if (retval 0) return retval; diff --git a/fs/attr.c
Processed: reassign 782069 to lvm2, forcibly merging 780319 782069, severity of 780319 is serious
Processing commands for cont...@bugs.debian.org: reassign 782069 lvm2 Bug #782069 [initramfs-tools] initramfs-tools: Required format of LVM volume names not compatible with manpage for lvchange Bug reassigned from package 'initramfs-tools' to 'lvm2'. No longer marked as found in versions initramfs-tools/0.119. Ignoring request to alter fixed versions of bug #782069 to the same values previously set forcemerge 780319 782069 Bug #780319 [lvm2] initramfs-tools hook doesn't support devices named as /dev/VG/LV Bug #780391 [lvm2] initramfs-tools: Boot drops to initramfs if usr as /dev/vg0/usr in fstab Bug #782069 [lvm2] initramfs-tools: Required format of LVM volume names not compatible with manpage for lvchange Severity set to 'important' from 'normal' Marked as found in versions lvm2/2.02.111-2.1. Bug #780391 [lvm2] initramfs-tools: Boot drops to initramfs if usr as /dev/vg0/usr in fstab Merged 780319 780391 782069 severity 780319 serious Bug #780319 [lvm2] initramfs-tools hook doesn't support devices named as /dev/VG/LV Bug #780391 [lvm2] initramfs-tools: Boot drops to initramfs if usr as /dev/vg0/usr in fstab Bug #782069 [lvm2] initramfs-tools: Required format of LVM volume names not compatible with manpage for lvchange Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 780319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780319 780391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780391 782069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
