Bug#764298: Still an issue
On 3 March 2015 at 20:45, Michael Biebl bi...@debian.org wrote: Am 2015-03-04 01:13, schrieb Michael Biebl: Am 04.03.2015 um 01:34 schrieb Michael Biebl: Am 04.03.2015 um 01:07 schrieb Daurnimator: Did you dist-upgrade the VM and those failures are from before the upgrade? Can you attach your /var/log/dpkg.log The reason why I'm asking is, that the fixed version 215-12 migrated to testing on 2015-02-28. The latest AMI according to [1] is from 20150213, so it can't have 215-12 yet. So this looks like the VM was upgraded and the error messages are from before the upgrade when systemd 215-12 was installed. [1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie Just double checked: The latest AMI provided by Debian ships 215-11. So, if you have 215-12 installed, this means the VM was upgraded after the VM was instantiated and booted and the error messages you see are most likely from 215-11, which does not ship the fix yet. Ah ha! It appears something along the way upgraded systemd without me knowing. I just rebooted the system and everything seems to be fine now :) dpkg.log contains: 2015-03-03 20:57:32 upgrade libsystemd0:amd64 215-11 215-12 2015-03-03 20:57:32 status half-configured libsystemd0:amd64 215-11 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-11 2015-03-03 20:57:32 status half-installed libsystemd0:amd64 215-11 2015-03-03 20:57:32 status half-installed libsystemd0:amd64 215-11 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12 2015-03-03 20:57:32 configure libsystemd0:amd64 215-12 none 2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12 2015-03-03 20:57:32 status half-configured libsystemd0:amd64 215-12 2015-03-03 20:57:32 status installed libsystemd0:amd64 215-12 2015-03-03 20:57:32 upgrade systemd:amd64 215-11 215-12 2015-03-03 20:57:32 status half-configured systemd:amd64 215-11 2015-03-03 20:57:32 status unpacked systemd:amd64 215-11 2015-03-03 20:57:32 status half-installed systemd:amd64 215-11 2015-03-03 20:57:33 status half-installed systemd:amd64 215-11 2015-03-03 20:57:33 status unpacked systemd:amd64 215-12 2015-03-03 20:57:33 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 configure systemd:amd64 215-12 none 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd:amd64 215-12 2015-03-03 20:57:34 status half-configured systemd:amd64 215-12 2015-03-03 20:57:34 status installed systemd:amd64 215-12 2015-03-03 20:57:34 upgrade systemd-sysv:amd64 215-11 215-12 2015-03-03 20:57:34 status half-configured systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status half-installed systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status half-installed systemd-sysv:amd64 215-11 2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-12 2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-12 2015-03-03 20:57:35 configure systemd-sysv:amd64 215-12 none 2015-03-03 20:57:35 status unpacked systemd-sysv:amd64 215-12 2015-03-03 20:57:35 status half-configured systemd-sysv:amd64 215-12 2015-03-03 20:57:35 status installed systemd-sysv:amd64 215-12 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735120: Bug#750853: ITA: postfix-cluebringer -- anti-spam plugin for Postfix
Hi there Joost, On 03/04/2015 03:54 PM, Joost van Baal-Ilić wrote: Hi Nigel e.a., On Sat, 07 Jun 2014 15:50:41 +, Nigel Kukard wrote: I intend to adopt postfix-cluebringer and will make an upload asap. Excellent! Did you manage to publish some work, e.g. in some git repo somewhere? FWIW, I found out v2.0.14 was released upstream on 2013-10-26. Furthermore, Bug #735120 (non-free w3c icons) is fixed upstream in https://gitlab.devlabs.linuxassist.net/policyd/policyd/commit/925edf8630b83e3f474e47490369b830829a16b6, at around 2014-05. So it should not be that hard to get postfix-cluebringer back in Debian... I've not had a terrible amount of time since then to work on the package. I have discussed the path I want to take with Eriberto and Tobias, but after spending a few days on it, I realized it will take a few more. Since then I've gotten a few other packages into Debian, but I've just been a bit busy with DC15 and DC16 this year. What I need to do is fix upstream a bit more, then rename the package. But at the same time fixing naming upstream to be in line with this. If you have any suggestions or want to discuss, just let me know :) -N -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779689: libjson-rpc-cpp: FTBFS: test suite errors
Peter Spiess-Knafl p...@autistici.org writes: Honestly I am kind of lost how I could fix this without access to a porterbox. Are there any specific ports which are not allowed to be used? I am using port 8383 on localhost to test the networking part of this framework. Good question; I know the autobuilders have historically had limited networking. However, if that were the problem, wouldn't the failures have been more consistent? On most affected architectures, only two of the three tests in question failed, and not the same two everywhere. At any rate, one affected architecture was i386, so you can try to reproduce the problem in a 32-bit chroot. Thanks for looking into this bug (and the other two I reported)! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779717: FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file
On 2015-03-04 14:10 +0100, 積丹尼 Dan Jacobson wrote: Package: chromium Version: 41.0.2272.76-1 Severity: grave $ chromium [0304/210821:FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file Same here. Upstream bug reports which seem to be related: https://code.google.com/p/chromium/issues/detail?id=437136 https://code.google.com/p/chromium/issues/detail?id=421063 Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725284: hdparm + systemd: Patch to restore configuration after resume
Hi, The specific one you posted above could probably use oneshot: [Service] Type=oneshot Thanks! I'm not sure if I want anything to wait for hdparm being done with this (which seems to be the only consequence), but in any case it sounds more appropriate to what that unit is doing. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 779784 is forwarded to https://github.com/tj/git-extras/issues/142
Processing commands for cont...@bugs.debian.org: forwarded 779784 https://github.com/tj/git-extras/issues/142 Bug #779784 [git-extras] git-extras: fresh-branch deletes everything without asking Set Bug forwarded-to-address to 'https://github.com/tj/git-extras/issues/142'. thanks Stopping processing here. Please contact me if you need assistance. -- 779784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779784 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: Re: Bug#771617: installer beta 2: jessie parted_server segfault on AMD Athlon64
Processing control commands:
reassign -1 partman-base
Bug #771617 [installation-reports] installer beta 2: jessie parted_server
segfault on AMD Athlon64
Bug reassigned from package 'installation-reports' to 'partman-base'.
Ignoring request to alter found versions of bug #771617 to the same values
previously set
Ignoring request to alter fixed versions of bug #771617 to the same values
previously set
forcemerge 778773 -1
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Bug #771617 [partman-base] installer beta 2: jessie parted_server segfault on
AMD Athlon64
Severity set to 'serious' from 'important'
Marked Bug as done
There is no source info for the package 'partman-base' at version '181' with
architecture ''
Unable to make a source version for version '181'
Marked as fixed in versions 181.
Added tag(s) patch.
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Added tag(s) d-i.
Added tag(s) d-i.
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Merged 771617 773274 778773
--
771617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771617
773274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773274
778773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778773
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#779738: Downgrading libxml2 and/or gnupg2 does not solve the issue
I've tried downgrading libxml2 and gnupg2 to the previously installed versions, but the problem remains. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747863: systemd service fails by default and causes package install failure
There are two ways how this could be addressed, I think: 1/ disabled systemd services shouldn't be started by invoke-rc.d This is a bug in sysv-rc and should be fixed irregardless of nut [1] 2/ nut could work-around this (for jessie), by using a dh_installinit --error-handler function, which simply ignores a non-zero return code when the service is started unconfigured and fails. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768450 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#755202:
On ma, 2015-03-02 at 22:14 +0100, Frederik Himpe wrote: I removed the netconsole stuff, removed the eth0 network connection in NM, and rebooted the system, and everything was OK again. I spoke too soon. Now I'm again experiencing this problem, even without netconsole. It looks like there is a race somewhere, causing the network interface to be brought up before Network Manager is started, and this prevents correct configuration by NM... -- Frederik Himpe frede...@frehi.be -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 778773 is serious, fixed 778773 in 181
Processing commands for cont...@bugs.debian.org:
severity 778773 serious
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
fixed 778773 181
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
There is no source info for the package 'partman-base' at version '181' with
architecture ''
Unable to make a source version for version '181'
Marked as fixed in versions 181.
Marked as fixed in versions 181.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
773274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773274
778773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778773
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#779738: evolution-ews: The server cannot service this request right now. Try again later
Package: evolution-ews Version: 3.12.9~git20141130.278fe7-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, the bug appear after an upgrade of the following packages: Install: python-mock:amd64 (1.0.1-3, automatic), python-nose:amd64 (1.3.4-1, automatic), libva-x11-1:i386 (1.4.1-1, automatic) Upgrade: bind9-host:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), libwinpr- thread0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), liblwres90:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), e2fslibs:amd64 (1.42.12-1, 1.42.12-1.1), apt:amd64 (1.0.9.6, 1.0.9.7), freerdp-x11:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libfreerdp-client1.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), host:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), multiarch-support:amd64 (2.19-13, 2.19-15), libwinpr-utils0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libdns100:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), libisc-export95:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), libfreerdp- core1.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), python-samba:amd64 (4.1.13+dfsg-2, 4.1.17+dfsg-1), libisccfg90:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), libwinpr- synch0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libc6-dev-x32:amd64 (2.19-13, 2.19-15), libbind9-90:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), libwinpr-pool0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), e2fsprogs:amd64 (1.42.12-1, 1.42.12-1.1), dbus:amd64 (1.8.12-3, 1.8.16-1), dpkg:amd64 (1.17.23, 1.17.24), winbind:amd64 (4.1.13+dfsg-2, 4.1.17+dfsg-1), libwinpr-handle0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libc6-i686:i386 (2.19-13, 2.19-15), libwinpr-crt0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libgtk2.0-cil:amd64 (2.12.10-5, 2.12.10-5.1), libfreerdp-cache1.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libwinpr-interlocked0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libc6-dev-i386:amd64 (2.19-13, 2.19-15), dpkg-dev:amd64 (1.17.23, 1.17.24), apt-utils:amd64 (1.0.9.6, 1.0.9.7), libtiff5:amd64 (4.0.3-12, 4.0.3-12.1), libtiff5:i386 (4.0.3-12, 4.0.3-12.1), libcomerr2:amd64 (1.42.12-1, 1.42.12-1.1), libcomerr2:i386 (1.42.12-1, 1.42.12-1.1), gnupg-agent:amd64 (2.0.26-4, 2.0.26-6), samba:amd64 (4.1.13+dfsg-2, 4.1.17+dfsg-1), libgudev-1.0-0:amd64 (215-11, 215-12), busybox:amd64 (1.22.0-9+b1, 1.22.0-9+deb8u1), libc-dev-bin:amd64 (2.19-13, 2.19-15), libfreerdp-codec1.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libwinpr-input0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libpam-systemd:amd64 (215-11, 215-12), libc-bin:amd64 (2.19-13, 2.19-15), libc6:amd64 (2.19-13, 2.19-15), libc6:i386 (2.19-13, 2.19-15), libfreerdp- gdi1.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libss2:amd64 (1.42.12-1, 1.42.12-1.1), python-libxml2:amd64 (2.9.1+dfsg1-4, 2.9.1+dfsg1-5), libapt-inst1.5:amd64 (1.0.9.6, 1.0.9.7), libwinpr-heap0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), xdg-utils:amd64 (1.1.0~rc1+git20111210-7.3, 1.1.0~rc1+git20111210-7.4), dnsutils:amd64 (9.9.5.dfsg-8, 9.9.5.dfsg-9), openjdk-7-jdk:amd64 (7u71-2.5.3-2, 7u75-2.5.4-2), libwinpr-rpc0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), iceweasel:amd64 (31.4.0esr-1, 31.5.0esr-1), libdbus-1-3:amd64 (1.8.12-3, 1.8.16-1), libdbus-1-3:i386 (1.8.12-3, 1.8.16-1), udev:amd64 (215-11, 215-12), libwinpr-library0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), samba-dsdb-modules:amd64 (4.1.13+dfsg-2, 4.1.17+dfsg-1), openjdk-7-jre- headless:amd64 (7u71-2.5.3-2, 7u75-2.5.4-2), libfreerdp-locale1.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libfreerdp-plugins-standard:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), libfreerdp-primitives1.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), samba-common-bin:amd64 (4.1.13+dfsg-2, 4.1.17+dfsg-1), libldb1:amd64 (1.1.17-1, 1.1.17-2), libxml2:amd64 (2.9.1+dfsg1-4, 2.9.1+dfsg1-5), libxml2:i386 (2.9.1+dfsg1-4, 2.9.1+dfsg1-5), libudev1:amd64 (215-11, 215-12), libudev1:i386 (215-11, 215-12), python-matplotlib:amd64 (1.3.1-2, 1.4.2-3.1), libwinpr- registry0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), wine-staging-i386:i386 (1.7.36-1~jessie, 1.7.37~jessie), libwinpr-sspi0.1:amd64 (1.1.0~git20140921.1.440916e+dfsg1-2+b1, 1.1.0~git20140921.1.440916e+dfsg1-3), samba-libs:amd64 (4.1.13+dfsg-2, 4.1.17+dfsg-1),
Bug#779784: git-extras: fresh-branch deletes everything without asking
Package: git-extras Version: 1.9.1-1 Severity: grave Tags: upstream Justification: causes non-serious data loss Using fresh-branch command like: $ git fresh-branch new_branch nukes all the files, without a warning and confirmation, it directly runs git clean -fdx. This causes a (non serious??) data loss, conflicts with the standard git clean behavior (which most git users would expect) and shouldn't be tolerated. Please either add a warning prompt or disable the command altogether. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.14.33 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages git-extras depends on: ii git 1:2.1.4-2.1 git-extras recommends no packages. git-extras suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725284: hdparm + systemd: Patch to restore configuration after resume
I don't know whether udev just doesn't trigger after a resume Either a generic systemd unit file is required to trigger an udev change event http://bugs.debian.org/779412, or a hdparm specific one to trigger just the hdparm script. The specific one you posted above could probably use oneshot: [Service] Type=oneshot -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779370: hdparm + systemd: old apm/pm-utils hooks not working/migrated
Actually, I now filed a separate bug report for the proper default wildard configuration. https://bugs.debian.org/779787 And the systemd unit file to call hdparm on resume is covered by https://bugs.debian.org/725284 So this report is just to cover the refactoring of the former pm-utils and apmd specific functions (maybe also into some /lib/hdparm/hdparm.sh) and call that from all apmd/pm-utils/udev/systemd files shiped. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779689: libjson-rpc-cpp: FTBFS: test suite errors
Peter Spiess-Knafl p...@autistici.org writes: https://dsa.debian.org/doc/guest-account/ OK, though I'm at work right now (it's mid-afternoon here) and won't be able to sign off formally for another few hours. That said, please bear in mind that if the problem does relate to autobuilder configuration, you're unlikely to encounter the relevant setup elsewhere, even on porter boxes. (If it's instead architecture-dependent, you may have better luck.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779689: libjson-rpc-cpp: FTBFS: test suite errors
Hi Aaron! As I learned from mentors, it is possibly for non-DDs to get a guest-account on various porter machines. Would you sponsor/sign my request for this? https://dsa.debian.org/doc/guest-account/ I will prepare a request with the required infos. I think this would be the most straight forward way to fix this issues. It would be great if you could agree to that. Greetings Peter On 03/04/2015 05:08 PM, Aaron M. Ucko wrote: Peter Spiess-Knafl p...@autistici.org writes: Honestly I am kind of lost how I could fix this without access to a porterbox. Are there any specific ports which are not allowed to be used? I am using port 8383 on localhost to test the networking part of this framework. Good question; I know the autobuilders have historically had limited networking. However, if that were the problem, wouldn't the failures have been more consistent? On most affected architectures, only two of the three tests in question failed, and not the same two everywhere. At any rate, one affected architecture was i386, so you can try to reproduce the problem in a 32-bit chroot. Thanks for looking into this bug (and the other two I reported)! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777520: marked as done (patch: regression causes u-boot to FTBFS)
Your message dated Wed, 4 Mar 2015 21:14:35 +0100 with message-id CAKjSHr35G=pnQENFZ2BD7yAogApdOfukMg=Hb75Cxbs9Et=g...@mail.gmail.com and subject line not a patch bug has caused the Debian Bug report #777520, regarding patch: regression causes u-boot to FTBFS 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.) -- 777520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: patch Version: 2.7.4-1 Severity: serious Justification: causes FTBFS in other packages Control: affects -1 u-boot $ dpkg-source -x u-boot_2014.10+dfsg1-2.dsc dpkg-source: warning: failed to verify signature on ./u-boot_2014.10+dfsg1-2.dsc dpkg-source: info: extracting u-boot in u-boot-2014.10+dfsg1 dpkg-source: info: unpacking u-boot_2014.10+dfsg1.orig.tar.xz dpkg-source: info: unpacking u-boot_2014.10+dfsg1-2.debian.tar.xz dpkg-source: info: applying add-debian-revision-to-u-boot-version ... The next patch would create the file tools/logos/solidrun.bmp, which already exists! Skipping patch. dpkg-source: info: the patch has fuzz which is not allowed, or is malformed dpkg-source: info: if patch 'cubox-i/cubox-i-support.diff' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: info: restoring quilt backup files for cubox-i/cubox-i-support.diff dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/cubox-i/cubox-i-support.diff/ --reject-file=- u-boot-2014.10+dfsg1/debian/patches/cubox-i/cubox-i-support.diff gave error exit status 1 After downgrading to patch 2.7.1-6 from jessie, I'm able to unpack the source just fine. I suspect some of the recent CVE fixes to be the cause, but haven't looked deeply into the issue. I may be able to work around the issue in u-boot by adjusting the patch, but this may affect other packages as well and result in FTBFS in security updates and binNMUs. FWIW, I've filed a more detailed bug on u-boot specifically: https://bugs.debian.org/777518 live well, vagrant signature.asc Description: PGP signature ---End Message--- ---BeginMessage--- It was a problem in u-boot, which asked patch to overwrite an already existing file. As it has a security risk, patch now refuses to do it.---End Message---
Bug#766448: marked as done (initramfs-tools: fsck.* not added to initrd image for mount by UUID or label with type=auto)
Your message dated Wed, 04 Mar 2015 21:19:26 +
with message-id e1ytghs-0004vz...@franck.debian.org
and subject line Bug#766448: fixed in initramfs-tools 0.119
has caused the Debian Bug report #766448,
regarding initramfs-tools: fsck.* not added to initrd image for mount by UUID
or label with type=auto
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.)
--
766448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: initramfs-tools
Version: 0.118
Severity: grave
On all my systems, 0.116 works fine,
0.118 just gives some message about rebooting in 5 seconds that is not
enough time to read.
I.e., the system becomes unbootable.
1. Please tell me what steps you would like me to take.
Thanks.
---End Message---
---BeginMessage---
Source: initramfs-tools
Source-Version: 0.119
We believe that the bug you reported is fixed in the latest version of
initramfs-tools, 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 766...@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 initramfs-tools
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: Sun, 01 Mar 2015 23:58:49 +
Source: initramfs-tools
Binary: initramfs-tools
Architecture: all source
Version: 0.119
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team debian-ker...@lists.debian.org
Changed-By: Ben Hutchings b...@decadent.org.uk
Closes: 627547 678696 688794 697335 707583 744836 752789 759552 762042 762768
762984 764020 764022 764388 765614 766448 771301 773250
Description:
initramfs-tools - generic modular initramfs generator
Changes:
initramfs-tools (0.119) unstable; urgency=medium
.
The Wait smarter not harder release
.
[ Ben Hutchings ]
* [bf238f6] Always generate ORDER files in mkinitramfs (Closes: #688794)
* [8529550] Move get_source, set_initlist, get_prereq_pairs, call_scripts to
hook-functions
* [6ba2e93] hook-functions: Add modules for various important device types
(Closes: #762042)
* [9c8bde8] mkinitramfs.8: Update default temporary directory
(Closes: #764388)
* [1bd461e] initramfs-tools.8: Refer to lsinitramfs rather than suggesting
gunzip | cpio (Closes: #764022)
* [64d39d0] Add comment to /usr/share/initramfs-tools/modules that it is not
a config file (Closes: #752789)
* [4f1414b] initramfs-tools.8: Improve documentation of break parameter.
Thanks to Helmut Grohne hel...@subdivi.de (Closes: #707583)
* [a5fbfb8] update-initramfs: Fix error message in case of excess arguments
(Closes: #627547)
* [738678f] initramfs.conf.5: Update configuration directory (Closes:
#759552)
* [3862d9b] update-initramfs: Consistently show which options take arguments
(Closes: #762768)
* [35bdb74] Refer to lsinitramfs(8) from {initramfs-tools,mkinitramfs,
update-initramfs}(8) (Closes: #764020)
* [cf9691d] mkinitramfs: Use default xz compression level rather than -8
(Closes: #697335)
* [10ebca7] mkinitramfs: Improve warning text when missing modules.
Thanks to Trent W. Buck trentb...@gmail.com (Closes: #744836)
* [540dcb6] initramfs-tools.8: Refer to 'phase' rather than 'stage' of
initramfs execution
* [c7a3b31] initramfs-tools.8: Briefly document the kernel hooks
* [274f945] hooks/fsck: Remove dependency on hwclock by disabling e2fsck time
check
* [1780a66] checkfs: Continue unless fsck reports uncorrectable errors
(Closes: #765614)
* [e5526cd] checkfs: Correct error messages and emergency shell in case of
failure
* [9daea18] hooks/fsck: Fix type lookup for mount by UUID or label with
type=auto (Closes: #766448)
* [2b1d834] dep_add_modules: Add modules needed for /usr device
* [a164229] NEWS: Begin a NEWS entry for the fsck and /usr-mount changes
* [2bbe817] NEWS: Document the possible need to update mdadm INITRDSTART
(Closes: #771301)
* [884a518] control: Ensure cryptsetup is upgraded to support mounting /usr
* [7b4635c] Allow passing arguments to hooks and scripts
Bug#779798: openjfx: FTBFS error: conflicting declaration 'typedef int32_t UChar32'
Source: openjfx Version: 8u20-b26-3 Severity: serious Justification: fails to build from source Dear Maintainer, openjfx fails to build on sid/amd64: In file included from /usr/include/x86_64-linux-gnu/unicode/utypes.h:36:0, from /usr/include/x86_64-linux-gnu/unicode/ucnv_err.h:86, from /usr/include/x86_64-linux-gnu/unicode/ucnv.h:50, from /usr/include/libxml2/libxml/encoding.h:31, from /usr/include/libxml2/libxml/parser.h:810, from ../../../../src/main/native/Source/WebCore/xml/XSLStyleSheet.h:32, from ../../../../src/main/native/Source/WebCore/xml/XSLTProcessor.h:29, from generated/JSXSLTProcessor.h:27, from generated/JSDOMWindow.cpp:614: /usr/include/x86_64-linux-gnu/unicode/umachine.h:298:17: error: conflicting declaration 'typedef int32_t UChar32' typedef int32_t UChar32; ^ In file included from ../../../../src/main/native/Source/WTF/wtf/unicode/Unicode.h:36:0, from ../../../../src/main/native/Source/WTF/wtf/text/ASCIIFastPath.h:31, from ../../../../src/main/native/Source/WTF/wtf/text/WTFString.h:28, from ../../../../src/main/native/Source/WTF/wtf/DateMath.h:54, from ../../../../src/main/native/Source/WebCore/webcorejava_pch.h:57: ../../../../src/main/native/Source/WTF/wtf/unicode/java/UnicodeJava.h:24:18: note: previous declaration as 'typedef uint32_t UChar32' typedef uint32_t UChar32; ^ This can also be seen in the reproducibility rebuild [1]. Best regards, Andreas 1: https://reproducible.debian.net/rb-pkg/sid/amd64/openjfx.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778387: squeeze update of cups?
Le vendredi, 27 février 2015, 04.39:08 Ben Hutchings a écrit : On Fri, 2015-02-27 at 03:17 +, Ben Hutchings wrote: This does not fix the bug! I cherry-picked git commit 6c087a72a0708bcb7929955c75770ee364755c42 (Add some range checking (probably more to come) to avoid divide-by-0 errors.), after which the critical hunk of the patch for CVE-2014-9679 applied cleanly. With Didier's original patch, zcat bogus.raster.gz | rastertohp foo bar baz 1 '' still crashes (segmentation fault). With the two patches applied, it fails cleanly (no pages found). I was still able to print a test page (though I'm not certain that this uses the raster filter code in my configuration). So I've uploaded with those two patches applied. Thanks! I've now updated the VCS with your patches. http://anonscm.debian.org/cgit/printing/cups.git/log/?h=master-squeeze-lts OdyX signature.asc Description: This is a digitally signed message part.
Bug#678696: Event based block device handling (fixes USB and nested devices problem)
Thanks for your work on this bug. I ended up with a somewhat different implementation as I don't think it's necessary to duplicate the information that udev provides, and as we may now need to mount more than one filesystem. But I should have credited you in the changelog for prototyping this, and I forgot to do so. Ben. -- Ben Hutchings Horngren's Observation: Among economists, the real world is often a special case. signature.asc Description: This is a digitally signed message part
Bug#779799: linux: Older patches causing FTBFS on armhf
Source: linux Version: 3.19-1~exp1 Justification: fails to build from source Severity: serious Hello, The two patches: features/arm/dts-sun7i-Add-spi0_pins_a-pinctrl-setting.patch features/arm/dts-sun7i-Add-uart3_pins_b-pinctrl-setting.patch are no longer needed in 3.19-1~exp1 because they were accepted upstream in v3.19 as these commits: 2dad53b54a 0510e4b52a Keeping the patches means getting duplicate nodes in the device tree which causes this build failure on armhf: https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armhfver=3.19-1~exp1stamp=1424044478 Please could you remove the patches from the next experimental version? Thanks a lot, B.R. Oake. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.16.0-4-armmp (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779801: CVE-2015-2158
Package: pngcrush Severity: grave Tags: security Hi, this has been assigned CVE-2015-2158: http://www.openwall.com/lists/oss-security/2015/02/28/6 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616689: marked as done (Root-on-LVM setup fails often due to timing issues)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004ud...@franck.debian.org and subject line Bug#678696: fixed in initramfs-tools 0.119 has caused the Debian Bug report #678696, regarding Root-on-LVM setup fails often due to timing issues 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.) -- 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.98.8 Severity: normal Hello, On my box (Sunblade 1000) the LVM initialization does not happen fast enough, so mounting root filesystem fails in roughly 95% of the cases: [ 90.520448] qla2xxx 0001:00:04.0: Allocated (252 KB) for firmware dump... [ 90.764373] qla2xxx 0001:00:04.0: LIP reset occurred (f8e8). [ 90.867334] scsi0 : qla2xxx [ 90.935081] qla2xxx 0001:00:04.0: LIP occurred (f7f7). [ 91.031152] qla2xxx 0001:00:04.0: LOOP UP detected (1 Gbps). [ 91.135284] qla2xxx 0001:00:04.0: [ 91.135288] QLogic Fibre Channel HBA Driver: 8.03.05-k0 [ 91.135293] QLogic QLA22xx - [ 91.135297] ISP2200: PCI (66 MHz) @ 0001:00:04.0 hdma-, host#=0, fw=2.02.08 TP Begin: Loading essential drivers ... done. Begin: Run[ 91.621764] device-mapper: uevent: version 1.0.3 ning /scripts/init-premount ... don[ 91.713376] device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-de...@redhat.com e. Begin: Mounting root file system ... Begin: Running /scrip[ 91.879330] scsi 0:0:0:0: Direct-Access HITACHI DKR1C-J072FC D7V5 PQ: 0 ANSI: 3 ts/local-top ... [ 92.031443] sd 0:0:0:0: Attached scsi generic sg2 type 0 [ 92.035463] sd 0:0:0:0: [sdb] 142410400 512-byte logical blocks: (72.9 GB/67.9 GiB) [ 92.054186] sd 0:0:0:0: [sdb] Write Protect is off [ 92.061913] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 92.101015] sdb: sdb1 sdb2 sdb3 [ 92.607567] sd 0:0:0:0: [sdb] Attached SCSI disk Volume group debian not found Skipping volume group debian Unable to find LVM volume debian/root done. Begin: Waiting for root file system ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/debian-root does not exist. Dropping to a shell! BusyBox v1.17.1 (Debian 1:1.17.1-10) built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs) Running 'vgchange -a y' at this point activates all volume groups and exiting the initramfs shell causes the boot to proceed normally. The problem can be solved by passing either 'scsi_mod.scan=sync' or 'rootdelay=20' on the command line. The rootdelay option handling is slightly counterintuitive: in /scripts/init-top/udev we will sleep for $ROOTDELAY seconds if it is set, however if rootdelay= is not specified on the command line we will not sleep here, and boot will fail. in /scripts/local ROOTDELAY is set to a default of 30 seconds if rootdelay= is not set, but sleeping here does not help, as the LVM devices will not magically appear without vgchange being called, and that's not going to happen, because /scripts/local/top have been run at this point already. There are a few options of fixing it in the generic case: 1. Make scsi_mod.scan=sync the default. The implication of this are unclear to me. 2. Try to activate the volume groups at the end of the waiting-for-root time in /scripts/local. 3. Come up with some way of asynchronous notification of volume groups being available for activation, and invoke vgchange on this notification. I clearly don't know about how LVM works internally to accomplish something like this, an udev hook, perhaps? While the bug is fairly harmless and plenty of workarounds exist, I consider fixing it desirable, as it would case a boot failure on some systems immediately after installation, and figuring out what's going on may be a bit of a challenge for the user. Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC ---End Message--- ---BeginMessage--- Source: initramfs-tools Source-Version: 0.119 We believe that the bug you reported is fixed in the latest version of initramfs-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and
Bug#765614: marked as done (Missing fsck.type should be non-fatal)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004vt...@franck.debian.org and subject line Bug#765614: fixed in initramfs-tools 0.119 has caused the Debian Bug report #765614, regarding Missing fsck.type should be non-fatal 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.) -- 765614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: vmdebootstrap Version: 0.3-1 Hello, I just tried to build an image of current sid for running autopkgtests in: $ sudo vmdebootstrap --verbose --serial-console --distribution=sid --user=adt/adt --size=20 --mbr --image=adt-sid.raw This worked in the past, but now they are stuck in a boot failure loop; $ kvm -m 2048 -snapshot -drive file=adt-sid.raw,if=virtio -monitor none -nographic -serial stdio [...] Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Checking root file system ... fsck from util-linux 2.25.1 fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/vda1 fsck exited with status code 8 done. Failure: An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. Warning: The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. sulogin: cannot open password database! [1.380144] tsc: Refined TSC clocksource calibration: 2594.111 MHz [3.237861] sulogin[94]: segfault at 8 ip 004018e0 sp 7324d340 error 4 in sulogin[40+3000] Segment violation Failure: Attempt to start maintenance shell failed. Will restart in 5 seconds. [8.245048] Unregister pv shared memory for cpu 0 [8.294086] reboot: Restarting system [8.295631] reboot: machine restart Then the kernel reboots, and it goes back to the very same problem again, over and over. This might be a regression from recent util-linux, or some misconfiguration, or incompatibility with extlinux, not sure. fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and /dev/vda1 also exists; it's also apparently able to map the root UUID to /dev/vda1. I also tried with --grub; image generation succeeds and it says Configuring grub2 Installing extlinux Cleaning up at the end, but booting in qemu doesn't work at all (there's not a single message). That's a different bug/report, but I wanted to mention it. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: initramfs-tools Source-Version: 0.119 We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 765...@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 initramfs-tools 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: Sun, 01 Mar 2015 23:58:49 + Source: initramfs-tools Binary: initramfs-tools Architecture: all source Version: 0.119 Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-ker...@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Closes: 627547 678696 688794 697335 707583 744836 752789 759552 762042 762768 762984 764020 764022 764388 765614 766448 771301 773250 Description: initramfs-tools - generic modular initramfs generator Changes: initramfs-tools (0.119) unstable; urgency=medium . The Wait smarter not harder release . [ Ben Hutchings ] * [bf238f6] Always
Bug#773643: marked as done (initramfs-tools: fsck.* not added to initrd image for mount by UUID or label with type=auto)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004vz...@franck.debian.org and subject line Bug#766448: fixed in initramfs-tools 0.119 has caused the Debian Bug report #766448, regarding initramfs-tools: fsck.* not added to initrd image for mount by UUID or label with type=auto 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.) -- 766448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.118 Severity: important Dear Debian folks, since some time, the filesystem type of the LUKS encrypted root partition (/) is not detected. $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 Warning: couldn't identify filesystem type for fsck hook, ignoring. setupcon is missing. Please install the 'console-setup' package. $ mount […] /dev/mapper/luks-6fb2f31d-ca5f-4c02-b120-13fd929fcac1 on / type ext4 (rw,noatime,discard,errors=remount-ro,commit=600,data=ordered) […] Unfortunately, I do not know when started. Either due to a `initramfs-tool` upgrade or testing `dracut`, where I had to switch to using UUIDs. Thanks, Paul -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii busybox1:1.22.0-14 ii cpio 2.11+dfsg-2+b1 ii klibc-utils2.0.4-2 ii kmod 18-3 ii module-init-tools 18-3 ii udev 215-8 ii util-linux 2.25.2-4 Versions of packages initramfs-tools recommends: ii busybox 1:1.22.0-14 Versions of packages initramfs-tools suggests: ii bash-completion 1:2.1-4 -- no debconf information signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: initramfs-tools Source-Version: 0.119 We believe that the bug you reported is fixed in the latest version of initramfs-tools, 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 766...@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 initramfs-tools 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: Sun, 01 Mar 2015 23:58:49 + Source: initramfs-tools Binary: initramfs-tools Architecture: all source Version: 0.119 Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-ker...@lists.debian.org Changed-By: Ben
Bug#771301: marked as done (cannot mount /usr if INITRDSTART in /etc/default/mdadm does not include the necessary device)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004vf...@franck.debian.org and subject line Bug#771301: fixed in initramfs-tools 0.119 has caused the Debian Bug report #771301, regarding cannot mount /usr if INITRDSTART in /etc/default/mdadm does not include the necessary device 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.) -- 771301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.117 Severity: normal LVM2 running on top of RAID1. /usr is separated on an extra volume. sh -x mkinitramfs -o /dev/null /tmp/trace.log 21 attached -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 4.6M Sep 26 21:47 /boot/initrd.img-3.14.19-pipin-lxtec-amd64 -rw-r--r-- 1 root root 4.6M Sep 26 21:47 /boot/initrd.img-3.16.3-pipin-lxtec-amd64 -rw-r--r-- 1 root root 4.9M Sep 26 21:51 /boot/initrd.img-3.17.0-rc6-pipin-lxtec-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.16.3-pipin-lxtec-amd64 root=/dev/mapper/vg0-root ro init=/lib/systemd/systemd systemd.show_status=true -- /proc/filesystems ext3 ext2 ext4 fuseblk vfat -- lsmod Module Size Used by nfsd 227542 2 auth_rpcgss41958 1 nfsd oid_registry2227 1 auth_rpcgss nfs_acl 2575 1 nfsd nfsv4 126863 1 nfs 116231 4 nfsv4 lockd 58596 2 nfs,nfsd sunrpc172182 16 nfs,nfsd,auth_rpcgss,lockd,nfsv4,nfs_acl vfat 10015 1 fat50584 1 vfat snd_hda_codec_hdmi 35253 1 x86_pkg_temp_thermal 4839 0 snd_hda_codec_realtek51232 1 snd_hda_codec_generic50127 1 snd_hda_codec_realtek hid_logitech_dj10200 0 snd_hda_intel 19335 5 snd_hda_controller 15930 1 snd_hda_intel usbhid 24997 0 snd_hda_codec 82786 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller snd_pcm77267 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller aesni_intel 143128 0 aes_x86_64 7359 1 aesni_intel glue_helper 4249 1 aesni_intel hid93397 2 usbhid,hid_logitech_dj snd_timer 17774 1 snd_pcm lrw 1 aesni_intel gf128mul5530 1 lrw ablk_helper 1804 1 aesni_intel snd56028 17 snd_hda_codec_realtek,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel soundcore 5231 2 snd,snd_hda_codec microcode 8070 0 acpi_cpufreq6607 0 evdev 11519 4 processor 22935 1 acpi_cpufreq nct677537028 0 hwmon_vid 3156 1 nct6775 coretemp5772 0 fuse 76310 1 ipv6 284503 49 autofs422273 2 e1000e161291 0 ptp10360 1 e1000e sr_mod 12759 0 cdrom 25982 1 sr_mod ehci_pci3560 0 ehci_hcd 41894 1 ehci_pci pps_core6465 1 ptp xhci_hcd 99490 0 fan 2489 0 thermal 8231 0 -- /etc/initramfs-tools/modules -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : [raid0] [raid1] [raid10] md6 : active raid1 sda6[0] sdb6[1] 629014528 blocks super 1.2 [2/2] [UU] bitmap: 0/5 pages [0KB], 65536KB chunk md5 : active raid1 sda5[0] sdb5[1] 1023424 blocks super 1.2 [2/2] [UU] unused devices: none -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox dmsetup fsck fuse keymap klibc kmod lvm2 mdadm ntfs_3g resume thermal udev zz-busybox -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.3-pipin-lxtec-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11+dfsg-2 ii klibc-utils2.0.4-1.1 ii kmod
Bug#762984: marked as done (New boot script stage needed for preparing non-root block devices)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004v5...@franck.debian.org and subject line Bug#762984: fixed in initramfs-tools 0.119 has caused the Debian Bug report #762984, regarding New boot script stage needed for preparing non-root block devices 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.) -- 762984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.117 Severity: normal LVM2 running on top of RAID1. /usr is separated on an extra volume. sh -x mkinitramfs -o /dev/null /tmp/trace.log 21 attached -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 4.6M Sep 26 21:47 /boot/initrd.img-3.14.19-pipin-lxtec-amd64 -rw-r--r-- 1 root root 4.6M Sep 26 21:47 /boot/initrd.img-3.16.3-pipin-lxtec-amd64 -rw-r--r-- 1 root root 4.9M Sep 26 21:51 /boot/initrd.img-3.17.0-rc6-pipin-lxtec-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.16.3-pipin-lxtec-amd64 root=/dev/mapper/vg0-root ro init=/lib/systemd/systemd systemd.show_status=true -- /proc/filesystems ext3 ext2 ext4 fuseblk vfat -- lsmod Module Size Used by nfsd 227542 2 auth_rpcgss41958 1 nfsd oid_registry2227 1 auth_rpcgss nfs_acl 2575 1 nfsd nfsv4 126863 1 nfs 116231 4 nfsv4 lockd 58596 2 nfs,nfsd sunrpc172182 16 nfs,nfsd,auth_rpcgss,lockd,nfsv4,nfs_acl vfat 10015 1 fat50584 1 vfat snd_hda_codec_hdmi 35253 1 x86_pkg_temp_thermal 4839 0 snd_hda_codec_realtek51232 1 snd_hda_codec_generic50127 1 snd_hda_codec_realtek hid_logitech_dj10200 0 snd_hda_intel 19335 5 snd_hda_controller 15930 1 snd_hda_intel usbhid 24997 0 snd_hda_codec 82786 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller snd_pcm77267 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller aesni_intel 143128 0 aes_x86_64 7359 1 aesni_intel glue_helper 4249 1 aesni_intel hid93397 2 usbhid,hid_logitech_dj snd_timer 17774 1 snd_pcm lrw 1 aesni_intel gf128mul5530 1 lrw ablk_helper 1804 1 aesni_intel snd56028 17 snd_hda_codec_realtek,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel soundcore 5231 2 snd,snd_hda_codec microcode 8070 0 acpi_cpufreq6607 0 evdev 11519 4 processor 22935 1 acpi_cpufreq nct677537028 0 hwmon_vid 3156 1 nct6775 coretemp5772 0 fuse 76310 1 ipv6 284503 49 autofs422273 2 e1000e161291 0 ptp10360 1 e1000e sr_mod 12759 0 cdrom 25982 1 sr_mod ehci_pci3560 0 ehci_hcd 41894 1 ehci_pci pps_core6465 1 ptp xhci_hcd 99490 0 fan 2489 0 thermal 8231 0 -- /etc/initramfs-tools/modules -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : [raid0] [raid1] [raid10] md6 : active raid1 sda6[0] sdb6[1] 629014528 blocks super 1.2 [2/2] [UU] bitmap: 0/5 pages [0KB], 65536KB chunk md5 : active raid1 sda5[0] sdb5[1] 1023424 blocks super 1.2 [2/2] [UU] unused devices: none -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox dmsetup fsck fuse keymap klibc kmod lvm2 mdadm ntfs_3g resume thermal udev zz-busybox -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.3-pipin-lxtec-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11+dfsg-2 ii klibc-utils2.0.4-1.1 ii kmod 18-2 ii
Bug#742962: marked as done (fails to mount root when root is on lvm.)
Your message dated Wed, 04 Mar 2015 21:19:26 +
with message-id e1ytghs-0004ud...@franck.debian.org
and subject line Bug#678696: fixed in initramfs-tools 0.119
has caused the Debian Bug report #678696,
regarding fails to mount root when root is on lvm.
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.)
--
678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: initramfs-tool
Version: 0.115
So I updated to latest kernel package in SID 3.13-1 and system did not
reboot.
problem is that the ramdisk can't find root.
looking into this I can see that the raid device is found but the lvm on
top of the raid is never started.
if*//*I run lvm vgchange -ay then the disks shows up in /dev/mapper/
not sure how I can continue the boot from there but it looks like this
lvm command is not run or run to early before the raid is up or something.
Also got a bit confused as I saw systemd running from the ramdisk and I
have not yet installed systemd.
I was trying to just restart the boot with exec init but that did not
work. I think it used to work. how do I continue an aborted boot.
---End Message---
---BeginMessage---
Source: initramfs-tools
Source-Version: 0.119
We believe that the bug you reported is fixed in the latest version of
initramfs-tools, 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 678...@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 initramfs-tools
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: Sun, 01 Mar 2015 23:58:49 +
Source: initramfs-tools
Binary: initramfs-tools
Architecture: all source
Version: 0.119
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team debian-ker...@lists.debian.org
Changed-By: Ben Hutchings b...@decadent.org.uk
Closes: 627547 678696 688794 697335 707583 744836 752789 759552 762042 762768
762984 764020 764022 764388 765614 766448 771301 773250
Description:
initramfs-tools - generic modular initramfs generator
Changes:
initramfs-tools (0.119) unstable; urgency=medium
.
The Wait smarter not harder release
.
[ Ben Hutchings ]
* [bf238f6] Always generate ORDER files in mkinitramfs (Closes: #688794)
* [8529550] Move get_source, set_initlist, get_prereq_pairs, call_scripts to
hook-functions
* [6ba2e93] hook-functions: Add modules for various important device types
(Closes: #762042)
* [9c8bde8] mkinitramfs.8: Update default temporary directory
(Closes: #764388)
* [1bd461e] initramfs-tools.8: Refer to lsinitramfs rather than suggesting
gunzip | cpio (Closes: #764022)
* [64d39d0] Add comment to /usr/share/initramfs-tools/modules that it is not
a config file (Closes: #752789)
* [4f1414b] initramfs-tools.8: Improve documentation of break parameter.
Thanks to Helmut Grohne hel...@subdivi.de (Closes: #707583)
* [a5fbfb8] update-initramfs: Fix error message in case of excess arguments
(Closes: #627547)
* [738678f] initramfs.conf.5: Update configuration directory (Closes:
#759552)
* [3862d9b] update-initramfs: Consistently show which options take arguments
(Closes: #762768)
* [35bdb74] Refer to lsinitramfs(8) from {initramfs-tools,mkinitramfs,
update-initramfs}(8) (Closes: #764020)
* [cf9691d] mkinitramfs: Use default xz compression level rather than -8
(Closes: #697335)
* [10ebca7] mkinitramfs: Improve warning text when missing modules.
Thanks to Trent W. Buck trentb...@gmail.com (Closes: #744836)
* [540dcb6] initramfs-tools.8: Refer to 'phase' rather than 'stage' of
initramfs execution
* [c7a3b31] initramfs-tools.8: Briefly document the kernel hooks
* [274f945] hooks/fsck: Remove dependency on hwclock by disabling e2fsck time
check
* [1780a66] checkfs: Continue unless fsck reports uncorrectable errors
(Closes: #765614)
* [e5526cd] checkfs: Correct error messages and emergency shell in case of
failure
* [9daea18] hooks/fsck: Fix type lookup for mount by UUID or label with
type=auto
Bug#678696: marked as done (Event based block device handling (fixes USB and nested devices problem))
Your message dated Wed, 04 Mar 2015 21:19:26 +
with message-id e1ytghs-0004ud...@franck.debian.org
and subject line Bug#678696: fixed in initramfs-tools 0.119
has caused the Debian Bug report #678696,
regarding Event based block device handling (fixes USB and nested devices
problem)
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.)
--
678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: initramfs-tools
Version: 0.106
Severity: wishlist
Tags: patch
Hi,
the attached patch adds an event based loop for block devices to the
init script. New blockdevices are recorded in
/run/initramfs/block-events by an udev rule as they appear. The init
script repeadately waits for that and then calls
/scripts/local-block/* with a list of new devices storedin NEWDEVS
until $ROOT and $resume (if set) exists or a timeout is reached.
This fixes the problem that USB devices take too long to be
discovered and crypto, raid, lvm or multipath can't be started on
them. It also adds support for arbitrary nestings of them, e.g. raid5
over raid1.
For the event loop I needed the $resume device translated to the
device node earlier. This was previously done in
scripts/local-premount/resume. It was essentially the same code used
to translate the $ROOT so I created a new function translate_device()
in script/functions and used that for both $ROOT and $resume.
Note: hooks/block-event and scripts/block-event are executable, not
represented in the patch.
MfG
Goswin
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages initramfs-tools depends on:
ii cpio 2.11-7
ii klibc-utils2.0~rc3-1
ii module-init-tools 3.16-1
ii udev 175-3.1
Versions of packages initramfs-tools recommends:
ii busybox 1:1.19.3-5
Versions of packages initramfs-tools suggests:
ii bash-completion 1:1.99-3
-- no debconf information
Description: event based loop
This patch adds an event based loop for block devices to the init
script. New blockdevices are recorded in /run/initramfs/block-events
by an udev rule as they appear. The init script repeadately waits for
that and then calls /scripts/local-block/* with a list of new devices
storedin NEWDEVS until $ROOT and $resume (if set) exists or a timeout
is reached.
.
This fixes the problem that USB devices take too long to be
discovered and crypto, raid, lvm or multipath can't be started on
them. It also adds support for arbitrary nestings of them, e.g. raid5
over raid1.
.
For the event loop I needed the $resume device translated to the
device node earlier. This was previously done in
scripts/local-premount/resume. It was essentially the same code used
to translate the $ROOT so I created a new function translate_device()
in script/functions and used that for both $ROOT and $resume.
.
Note: hooks/block-event and scripts/block-event are executable, not
represented in the patch.
Author: Goswin von Brederlow
Last-Update: 2012-06-23
--
diff -Nru initramfs-tools-0.106/hooks/block-event initramfs-tools-0.106a0mrvn1/hooks/block-event
--- initramfs-tools-0.106/hooks/block-event 1970-01-01 01:00:00.0 +0100
+++ initramfs-tools-0.106a0mrvn1/hooks/block-event 2012-06-23 18:52:54.0 +0200
@@ -0,0 +1,13 @@
+#!/bin/sh
+
+mkdir -p $DESTDIR/etc/udev/rules.d
+
+cat $DESTDIR/etc/udev/rules.d/99-block-event.rules EOF
+# we are only interested in add and change actions for block devices
+ACTION==remove, GOTO=block_event_end
+SUBSYSTEM!=block, GOTO=block_event_end
+
+RUN+=/scripts/block-event $name
+
+LABEL=block_event_end
+EOF
diff -Nru initramfs-tools-0.106/init initramfs-tools-0.106a0mrvn1/init
--- initramfs-tools-0.106/init 2012-06-06 15:04:52.0 +0200
+++ initramfs-tools-0.106a0mrvn1/init 2012-06-23 21:14:40.0 +0200
@@ -69,41 +69,10 @@
init=${x#init=}
;;
root=*)
- ROOT=${x#root=}
- case $ROOT in
- LABEL=*)
- ROOT=${ROOT#LABEL=}
-
- # support any / in LABEL= path (escape to \x2f)
- case ${ROOT} in
- */*)
- if command -v sed /dev/null 21; then
-ROOT=$(echo ${ROOT} | sed 's,/,\\x2f,g')
- else
-if [ ${ROOT} != ${ROOT#/} ]; then
- ROOT=\x2f${ROOT#/}
-fi
-if [ ${ROOT} != ${ROOT%/} ]; then
- ROOT=${ROOT%/}\x2f
-fi
-IFS='/'
-
Bug#735120: Bug#750853: ITA: postfix-cluebringer -- anti-spam plugin for Postfix
Hi Nigel e.a., On Sat, 07 Jun 2014 15:50:41 +, Nigel Kukard wrote: I intend to adopt postfix-cluebringer and will make an upload asap. Excellent! Did you manage to publish some work, e.g. in some git repo somewhere? FWIW, I found out v2.0.14 was released upstream on 2013-10-26. Furthermore, Bug #735120 (non-free w3c icons) is fixed upstream in https://gitlab.devlabs.linuxassist.net/policyd/policyd/commit/925edf8630b83e3f474e47490369b830829a16b6, at around 2014-05. So it should not be that hard to get postfix-cluebringer back in Debian... Bye, Joost -- Joost van Baal-Ilić http://abramowitz.uvt.nl/ Tilburg University mailto:joostvb.uvt.nl The Netherlands signature.asc Description: Digital signature
Bug#712984: marked as done (linux-image-3.9-1-amd64: Unable to find LVM volume system/root)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004ud...@franck.debian.org and subject line Bug#678696: fixed in initramfs-tools 0.119 has caused the Debian Bug report #678696, regarding linux-image-3.9-1-amd64: Unable to find LVM volume system/root 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.) -- 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.9.6-1 Severity: grave Justification: renders package unusable Hallo, I am using Debian testing and today I got an update of the kernel from 3.2 to 3.9. I can't boot with the new kernel, I can however still boot with the old (3.2) kernel becaus I didn't remove it. I have multiple harddisks in my computer. On one of it, I have a normal partition, formated with ext4 for /boot which I use for booting. The other disk space is used for LVM as phisical disks in my volume group system. This volume group contains among others the logical volumes root and swap. The kernel is started with the argument: root=/dev/mapper/system-root This configuration (still) works with the 3.2 kernel. When I'm booting the 3.9 kernel, I get the following messages: Booting kernel Loading, please wait... Volume group system not found Skipping volume group system Unable to find LVM volume system/root ... Unable to find LVM volume system/swap After a timeout, I get a busybox shell. The commands lvm vgs and lvm lvs do show there the correct information. The directory /dev/mapper shows however only the entry control. Can it be that a module isn't loaded? But how can then the LVM be found in the busybox shell? Regards, Vincent Smeets -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: MSI product_name: MS-7250 product_version: 1.0 chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: MS-7250 bios_version: V1.11 board_vendor: MSI board_name: MS-7250 board_version: 1.0 ** PCI devices: 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP55 Memory Controller [10de:0369] (rev a1) Subsystem: Micro-Star International Co., Ltd. Device [1462:7250] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP55 LPC Bridge [10de:0360] (rev a2) Subsystem: Micro-Star International Co., Ltd. Device [1462:7250] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: I/O ports at 2f00 [size=128] 00:01.1 SMBus [0c05]: NVIDIA Corporation MCP55 SMBus [10de:0368] (rev a2) Subsystem: Micro-Star International Co., Ltd. Device [1462:7250] Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at 2900 [size=64] Region 4: I/O ports at 2d00 [size=64] Region 5: I/O ports at 2e00 [size=64] Capabilities: access denied Kernel driver in use: nForce2_smbus 00:02.0 USB controller [0c03]: NVIDIA Corporation MCP55 USB Controller [10de:036c] (rev a1) (prog-if 10 [OHCI]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7250] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at fbefb000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP55 USB Controller [10de:036d] (rev a2) (prog-if 20 [EHCI]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7250] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Bug#633024: marked as done (initramfs-tools: Race condition when root filesystem is on a LV and mdadm array)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004ud...@franck.debian.org and subject line Bug#678696: fixed in initramfs-tools 0.119 has caused the Debian Bug report #678696, regarding initramfs-tools: Race condition when root filesystem is on a LV and mdadm array 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.) -- 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.99 Severity: important When booting the system, it seems there is a race condition between assembling a mdadm array, and scanning and / or activating VGs which have it's PV on this array. I have a mdadm array (ICH9R fakeraid BIOS array), where one of the partitions is a PV. On this PV, there is a LV for the root filesystem. Since ~ 2.6.37, the initramfs does not find the VG all the time. This means, I have to boot the system a couple of times, before the VG is found, and the root filesystem is mounted. There is no real logic in how often initramfs succesfully finds the VG. It's about a 1 in 3 chance of it booting succesfull. However, sometimes I have to reboot the system about 10 times before the VG is finally found. Sometimes it finds it immediatly. When in the shell for the initramfs, the RAID array seems to be assembled fine (this is also reported in the console output). Also, when executing a lvm vgdisplay, the VG is there. Once the VG is activated, the LV's can be mounted fine. Attached are the dmesg output, the contents of /proc/mdstat and the output of lvm vgdisplay after running a lvm vgchange -ay -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 9.2M May 29 18:31 /boot/initrd.img-2.6.32-5-amd64 -rw-r--r-- 1 root root 11M Jun 2 14:36 /boot/initrd.img-2.6.39-1-amd64 -rw-r--r-- 1 root root 11M Jul 6 00:45 /boot/initrd.img-2.6.39-2-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.39-2-amd64 root=/dev/mapper/vgLocal-lvRoot ro -- resume RESUME=/dev/mapper/vgLocal-lvSwap -- /proc/filesystems ext4 ext2 fuseblk -- lsmod Module Size Used by ip6table_filter12540 0 ip6_tables 21907 1 ip6table_filter ebtable_nat12580 0 ebtables 26089 1 ebtable_nat vboxnetadp 13185 0 vboxnetflt 24179 0 ipt_REJECT 12465 4 xt_CHECKSUM12471 2 iptable_mangle 12536 1 vboxdrv 178736 2 vboxnetadp,vboxnetflt xt_tcpudp 12527 10 iptable_filter 12536 1 ip_tables 21818 2 iptable_mangle,iptable_filter x_tables 18886 9 ip6table_filter,ip6_tables,ebtables,ipt_REJECT,xt_CHECKSUM,iptable_mangle,xt_tcpudp,iptable_filter,ip_tables tun18084 2 bridge 65614 0 stp12392 1 bridge acpi_cpufreq 12849 1 mperf 12411 1 acpi_cpufreq cpufreq_userspace 12576 0 cpufreq_stats 12762 0 cpufreq_powersave 12454 0 cpufreq_conservative13147 0 parport_pc 22191 0 ppdev 12725 0 lp 17190 0 parport31650 3 parport_pc,ppdev,lp bnep 17424 2 rfcomm 32744 0 bluetooth 107224 10 bnep,rfcomm binfmt_misc12914 1 fuse 61554 3 ext2 62796 3 loop 22479 0 firewire_sbp2 17825 0 kvm_intel 49912 0 kvm 263518 1 kvm_intel snd_hda_codec_hdmi 22174 4 arc4 12458 2 ecb12737 2 nvidia 11757407 40 snd_hda_codec_analog77600 1 rtl818735388 0 mac80211 181270 1 rtl8187 cfg80211 126244 2 rtl8187,mac80211 rfkill 19014 4 bluetooth,cfg80211 snd_hda_intel 25946 1 snd_hda_codec 67865 3 snd_hda_codec_hdmi,snd_hda_codec_analog,snd_hda_intel eeprom_93cx6 12455 1 rtl8187 snd_hwdep 13148 1 snd_hda_codec snd_pcm67276 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec joydev 17138 0 snd_seq44678 0 snd_timer 22658 2 snd_pcm,snd_seq snd_seq_device 13155 1 snd_seq snd52324 11 snd_hda_codec_hdmi,snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device processor 27431 1
Bug#720716: marked as done (initramfs-tools: workaround in 707286 solves serious problem)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004ud...@franck.debian.org and subject line Bug#678696: fixed in initramfs-tools 0.119 has caused the Debian Bug report #678696, regarding initramfs-tools: workaround in 707286 solves serious problem 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.) -- 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Followup-For: Bug #707286 Package: initramfs-tools Version: 0.113 Dear Maintainer, The workaround from 707286 (add ‘sleep 1’ before “modprobe -q dm-mod” in scripts/local-top/lvm2) has made the latest Debian kernels bootable again! They all got stuck in the initramfs shell because the root on LVM could not be found. Hugo Vanwoerkom -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 12M Jul 31 09:36 /boot/initrd.img-3.10-1-amd64 -rw-r--r-- 1 root root 12M Aug 24 10:06 /boot/initrd.img-3.10-2-amd64 -rw-r--r-- 1 root root 3.1M Aug 15 11:01 /boot/initrd.img-3.10.4-nodeb-amd64 -rw-r--r-- 1 root root 3.1M Aug 20 20:11 /boot/initrd.img-3.10.7-nodeb-amd64 -rw-r--r-- 1 root root 11M Jul 4 15:02 /boot/initrd.img-3.2.0-4-amd64 -rw-r--r-- 1 root root 3.1M Jul 4 17:30 /boot/initrd.img-3.8.1-nodeb-amd64 -rw-r--r-- 1 root root 12M Jul 18 10:37 /boot/initrd.img-3.9-1-amd64 -- /proc/cmdline root=/dev/mapper/vgHDB-HDBB vga=791 nouveau.modeset=0 resume=LABEL=HD502HJ_02.08 -- resume RESUME=UUID=f2b6dbbe-6ed3-4d57-8c11-823ce166b7c5 -- /proc/filesystems ext2 -- lsmod Module Size Used by nvidia 9315617 50 drm 211856 2 nvidia pci_stub 12429 1 vboxpci19094 0 vboxnetadp 25443 0 vboxnetflt 23697 0 vboxdrv 217395 4 vboxnetadp,vboxnetflt,vboxpci nf_conntrack_irc 12427 0 nf_conntrack_ftp 12651 0 xt_helper 12507 12 xt_tcpudp 12570 32 nf_conntrack_ipv4 18549 61 nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 xt_conntrack 12681 49 xt_limit 12638 14 nf_conntrack 59788 5 xt_helper,xt_conntrack,nf_conntrack_ftp,nf_conntrack_irc,nf_conntrack_ipv4 ipt_ULOG 12862 13 nfnetlink_log 17396 1 nfnetlink 12989 2 nfnetlink_log iptable_filter 12536 1 ip_tables 22036 1 iptable_filter x_tables 19041 7 xt_helper,ipt_ULOG,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,iptable_filter loop 22869 0 snd_hda_codec_via 22832 1 snd_hda_intel 35718 13 snd_hda_codec 122850 2 snd_hda_codec_via,snd_hda_intel snd_hwdep 13189 1 snd_hda_codec snd_pcm68525 6 snd_hda_codec,snd_hda_intel acpi_cpufreq 13280 1 i2c_nforce212628 0 edac_mce_amd 17070 0 edac_core 43448 0 mperf 12453 1 acpi_cpufreq psmouse74832 0 serio_raw 12940 0 snd_page_alloc 13018 2 snd_pcm,snd_hda_intel video 17792 0 kvm_amd47719 0 processor 28526 1 acpi_cpufreq i2c_core 24353 3 drm,nvidia,i2c_nforce2 snd_timer 22773 5 snd_pcm kvm 301458 1 kvm_amd snd53068 24 snd_hwdep,snd_timer,snd_hda_codec_via,snd_pcm,snd_hda_codec,snd_hda_intel hid_a4tech 12531 0 pcspkr 12632 0 soundcore 13026 1 snd wmi13243 0 thermal_sys23137 2 video,processor microcode 30413 0 button 12944 0 asus_atk0110 17246 0 evdev 17611 15 ext2 59601 8 mbcache13082 1 ext2 hid_generic12393 0 usb_storage48158 0 usbhid 40964 0 hid81894 3 hid_a4tech,hid_generic,usbhid sr_mod 21988 0 cdrom 35212 1 sr_mod sg 26095 0 sd_mod 40541 10 crc_t10dif 12348 1 sd_mod dm_mod 64008 27 ata_generic12490 0 firewire_ohci 31931 0 firewire_core 49211 1 firewire_ohci crc_itu_t 12347 1 firewire_core ehci_pci 12472 0 ohci_hcd 26678 0 ehci_hcd 40590 1 ehci_pci ahci 25148 9 libahci23136 1 ahci pata_amd 13378 0 forcedeth 54034 0 libata
Bug#712999: marked as done (linux-image-3.9-1-amd64: Unable to find LVM volume)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004ud...@franck.debian.org and subject line Bug#678696: fixed in initramfs-tools 0.119 has caused the Debian Bug report #678696, regarding linux-image-3.9-1-amd64: Unable to find LVM volume 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.) -- 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.9.6-1 Severity: critical Justification: breaks the whole system Hi, Today I updated my system, and got update of the kernel, to 3.9 version(did it with dist-upgrade). On booting with new version, I got some error messages, like: Booting kernel Loading, please wait... modprobe: can't load module microcode (kernel//microcode.ko): No such device Volume group vg-all not found Skipping volume group vg-all Unable to find LVM volume vg-all/lv-root Volume group vg-all not found Skipping volume group vg-all Unable to find LVM volume vg-all/lv-swap Gave up waiting for root device. After these messages, busybox shell is loaded. Now is running kernel version 3.2. Also, sometimes, on boot with 3.9 apper an TSC failed error. Regards, Alexander Balaban -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: MSI product_name: MS-7369 product_version: 1.0 chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: V2.0 board_vendor: MSI board_name: MS-7369 board_version: 1.0 ** PCI devices: 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP65 Memory Controller [10de:0444] (rev a3) Subsystem: Micro-Star International Co., Ltd. Device [1462:7369] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP65 LPC Bridge [10de:0441] (rev a3) Subsystem: Micro-Star International Co., Ltd. Device [1462:7369] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Region 0: I/O ports at 2f00 [size=256] 00:01.1 SMBus [0c05]: NVIDIA Corporation MCP65 SMBus [10de:0446] (rev a1) Subsystem: Micro-Star International Co., Ltd. Device [1462:7369] Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at 2900 [size=64] Region 4: I/O ports at 2d00 [size=64] Region 5: I/O ports at 2e00 [size=64] Capabilities: access denied Kernel driver in use: nForce2_smbus 00:01.2 RAM memory [0500]: NVIDIA Corporation MCP65 Memory Controller [10de:0445] (rev a1) Subsystem: Micro-Star International Co., Ltd. Device [1462:7369] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:02.0 USB controller [0c03]: NVIDIA Corporation MCP65 USB 1.1 OHCI Controller [10de:0454] (rev a3) (prog-if 10 [OHCI]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7369] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at f9eff000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP65 USB 2.0 EHCI Controller [10de:0455] (rev a3) (prog-if 20 [EHCI]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7369] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns
Bug#707286: marked as done (linux-image-3.8-1-amd64: makes system unbootable)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004ud...@franck.debian.org and subject line Bug#678696: fixed in initramfs-tools 0.119 has caused the Debian Bug report #678696, regarding linux-image-3.8-1-amd64: makes system unbootable 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.) -- 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.8.11-1 Severity: important Dear Maintainer, Boot process with linux 3.8 stops with message that root device wasn't found and I should check kernel command line or increase timeout required for root device get ready. Also it opens busybox where I can do something to fix the issue. If I run ls /sys/block I see only sda, sdb and sr0. While in good system there sh'ld also present dm-0 (root) and dm-1 (swap). If I run scripts/local-top/lvm2 I see message like [ 90.701171] bio: create slab bio-1 at 1 Now I leave console and boot process continues successfully. In dmesg for linux 3.2 I can see that device-mapper shows it's messages after sda sdb get ready, but in 3.8 they are in the middle of the process. So I added line sleep 1 into scripts/local-top/lvm2 before modprobe -q dm-mod (and so before 'activate_vg $ROOT'), it helped. Dmesg for system loaded by hands is attached. -- Package-specific info: ** Version: Linux version 3.8-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.8.11-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.8-1-amd64 root=/dev/mapper/globus-root ro ** Model information sys_vendor: Gigabyte Technology Co., Ltd. product_name: GA-MA69VM-S2 product_version: chassis_vendor: Gigabyte Technology Co., Ltd. chassis_version: bios_vendor: Award Software International, Inc. bios_version: F8 board_vendor: Gigabyte Technology Co., Ltd. board_name: GA-MA69VM-S2 board_version: ** Loaded modules: ip6table_filter ip6_tables cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT xt_multiport xt_recent nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter binfmt_misc xt_conntrack nf_conntrack_ftp nf_conntrack xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ip_tables x_tables pppoe pppox ppp_generic slhc bridge stp llc ext2 mbcache it87 hwmon_vid rtl8180 mac80211 cfg80211 rfkill eeprom_93cx6 loop fuse ecryptfs dm_crypt snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq sp5100_tco fglrx(PO) snd_seq_device i2c_piix4 snd_timer powernow_k8 snd kvm_amd serio_raw kvm soundcore i2c_core processor parport_pc parport pcspkr k8temp edac_mce_amd edac_core thermal_sys button evdev reiserfs hid_generic usbhid hid sg sr_mod cdrom sd_mod crc_t10dif dm_mirror dm_region_hash dm_log dm_mod ata_generic r8169 mii ahci libahci pata_atiixp ehci_pci ohci_hcd ehci_hcd libata usbcore usb_common scsi_mod ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge [1002:7910] Subsystem: Giga-byte Technology Device [1458:5000] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 32 00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (PCI Express Graphics Port 0) [1002:7913] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: fdf0-fdff Prefetchable memory behind bridge: d000-dfff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:12.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB600 Non-Raid-5 SATA [1002:4380] (prog-if 01 [AHCI 1.0]) Subsystem: Giga-byte
Bug#718533: marked as done (linux-image-3.10-1-amd64 fails to boot with RAID5)
Your message dated Wed, 04 Mar 2015 21:19:26 + with message-id e1ytghs-0004ud...@franck.debian.org and subject line Bug#678696: fixed in initramfs-tools 0.119 has caused the Debian Bug report #678696, regarding linux-image-3.10-1-amd64 fails to boot with RAID5 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.) -- 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.113 Severity: serious Justification: unbootable I rebooted a system today on linux-image-3.10-1-amd64 and it was unable to boot. linux-image-3.2.0-x-amd64 works fine. A initrd.img-3.2.0-4-amd64 file was generated at the same time the 3.10 one was crated and it boots normally. I don't know what the difference is. The problem is that the raid456 module is not being loaded by initramfs. I manually loaded the module with modprobe raid5, assembled by arrays with mdadm, and was able to boot normally. The initramfs file /conf/modules says dm-raid45, but I suspect it should say dm-raid456. I suspect this typo is causing the module to not be loaded, causing boot to fail, but I have not verified this yet. I will repack it and reboot on it in a few minutes here. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 11M Nov 15 2011 /boot/initrd.img-2.6.39-2-amd64 -rw-r--r-- 1 root root 11M Jan 22 2012 /boot/initrd.img-3.1.0-1-amd64 -rw-r--r-- 1 root root 13M Jul 31 16:31 /boot/initrd.img-3.10-1-amd64 -rw-r--r-- 1 root root 11M Feb 28 2012 /boot/initrd.img-3.2.0-1-amd64 -rw-r--r-- 1 root root 12M Jun 21 2012 /boot/initrd.img-3.2.0-2-amd64 -rw-r--r-- 1 root root 12M Sep 13 2012 /boot/initrd.img-3.2.0-3-amd64 -rw-r--r-- 1 root root 12M Jul 31 16:22 /boot/initrd.img-3.2.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10-1-amd64 root=UUID=b2c4c911-6183-452f-aed1-db72a09cd15d ro 8250.nr_uarts=16 quiet -- resume RESUME=UUID=d19e628c-7562-43c3-abff-5c974577bb3f -- /proc/filesystems ext4 fuseblk -- lsmod Module Size Used by xt_multiport 12548 4 8021q 23888 0 garp 13188 1 8021q stp12437 1 garp mrp13274 1 8021q llc12822 2 stp,garp cpufreq_stats 12866 0 cpufreq_conservative14159 0 cpufreq_userspace 12576 0 cpufreq_powersave 12454 0 xt_LOG 17220 6 ipt_REJECT 12502 2 xt_recent 13367 3 xt_conntrack 12681 9 iptable_filter 12536 1 xt_tcpudp 12570 46 xt_nat 12601 10 iptable_nat12646 1 nf_conntrack_ipv4 18549 10 nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 nf_nat_ipv412950 1 iptable_nat nf_nat 18378 3 nf_nat_ipv4,xt_nat,iptable_nat iptable_mangle 12536 0 ip_tables 22036 3 iptable_filter,iptable_mangle,iptable_nat x_tables 19041 10 xt_recent,ip_tables,xt_tcpudp,xt_conntrack,xt_LOG,xt_nat,xt_multiport,iptable_filter,ipt_REJECT,iptable_mangle binfmt_misc12925 1 nfsd 192007 13 auth_rpcgss39085 1 nfsd oid_registry 12419 1 auth_rpcgss nfs_acl12511 1 nfsd nfs 110304 0 lockd 59673 2 nfs,nfsd dns_resolver 12641 1 nfs fscache37551 1 nfs sunrpc164583 29 nfs,nfsd,auth_rpcgss,lockd,nfs_acl k8temp 12711 0 i2c_dev13110 0 it87 30219 0 hwmon_vid 12430 1 it87 ixgbe 157728 0 mdio 12653 1 ixgbe e1000 90558 0 skge 41078 0 forcedeth 54034 0 nf_conntrack_ftp 12651 0 nf_conntrack 59788 6 nf_nat,nf_nat_ipv4,xt_conntrack,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4 raid1 30999 0 sata_promise 13551 0 sata_nv26909 0 loop 22869 0 firewire_sbp2 17956 0 fuse 67458 1 acpi_cpufreq 13280 0 mperf 12453 1 acpi_cpufreq processor 28526 1 acpi_cpufreq parport_pc 22409 0 parport31901 1 parport_pc snd_hda_codec_hdmi 31720 1 radeon689925 1 ttm54470 1 radeon snd_hda_codec_realtek32712 1 button 12944 0 snd_hda_intel
Bug#779787: damaging default apm_on_ac configuration
Package: hdparm
Severity: serious
Tags: jessie sid
It is very common that hard disks default to do excessive head parking
attempts (click-ripples like every 8 seconds), just to be woken up
immediately.
To prevent early damage, a save default is: hdparm -B 254,
but there seems to be no possible way to configure such a default
that works for all disks out of the box.
To support a proper default, and actually shipping such a default,
I would suggest to support wildcards in hdparm.conf. And ship with a
visible default like this:
# default to prevent excessive hard disk wear
# (head parking, load-cycling)
/dev/disk/by-id/ata-* {
apm_on_ac = 254
apm_on_battery = 128
}
Note 1)
There is currently some code in 95hdparm-apm that conditionally applies
*hardcoded* apm values (128/254) on battery/ac changes, but *nothing*
for booting/udev plugging with proper defaults.
Note 2)
It makes sense to have some new apm_on_battery and
apm_on_ac options (in addition to the current apm option), to
avoid disabling quick head parking for mobile battery devices on the
move.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 770918 in flac/1.2.1-6+deb7u1
Processing commands for cont...@bugs.debian.org:
fixed 770918 flac/1.2.1-6+deb7u1
Bug #770918 {Done: Fabian Greffrath fabian+deb...@greffrath.com} [flac] flac:
CVE-2014-8962/CVE-2014-9028: heap buffer overflows
Marked as fixed in versions flac/1.2.1-6+deb7u1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
770918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770918
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#765154: gwave: FTBFS: build-dependency not installable: libgwrap-runtime-dev
Package: gwave Version: 20090213-5 Followup-For: Bug #765154 Dear Maintainer, Attached is git commit against current src:gwave master from pkg-electronics to resolve FTBFS. These changes were test-compiled against Ubuntu Vivid/amd64. -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty-proposed'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-31-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash commit 2b2b5ea0bedbd0b0b23158c297efba715c199656 Author: Dan crimsun@ubuntu-server Date: Wed Mar 4 16:48:35 2015 -0500 Resolved FTBFS diff --git a/debian/changelog b/debian/changelog index 200ef65..f8f0a0f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +gwave (20090213-5ubuntu1) vivid-proposed; urgency=low + + * Rebased on Debian's git + * Resolved FTBFS (Closes: #765154): ++ Completed GH to scm transition ++ Added missing variable declaration ++ Added missing library to link + + -- Daniel T Chen crim...@ubuntu.com Wed, 04 Mar 2015 12:15:14 -0500 + gwave (20090213-5) unstable; urgency=medium * debian/control: diff --git a/debian/control b/debian/control index 3defcf0..1eb8d48 100644 --- a/debian/control +++ b/debian/control @@ -1,7 +1,8 @@ Source: gwave Section: electronics Priority: optional -Maintainer: Debian Electronics Team pkg-electronics-de...@lists.alioth.debian.org +Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com +Original-Maintainer: Debian Electronics Team pkg-electronics-de...@lists.alioth.debian.org Uploaders: Hamish Moffatt ham...@debian.org, أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@users.sourceforge.net Standards-Version: 3.9.5 Build-Depends: debhelper (= 9), libgtk2.0-dev, guile-2.0-dev | libguile-dev, libglib2.0-dev, libreadline-dev, guile-gnome2-dev, guile-cairo-dev, libgwrap-runtime-dev diff --git a/debian/patches/fix_as-needed_linking.diff b/debian/patches/fix_as-needed_linking.diff index 102b59b..87e470c 100644 --- a/debian/patches/fix_as-needed_linking.diff +++ b/debian/patches/fix_as-needed_linking.diff @@ -8,8 +8,10 @@ Bug-Debian: http://bugs.debian.org/641725 Bug-Ubuntu: https://launchpad.net/bugs/770956 Last-Update: 2011-09-15 a/spicefile/Makefile.am -+++ b/spicefile/Makefile.am +Index: gwave-20090213/spicefile/Makefile.am +=== +--- gwave-20090213.orig/spicefile/Makefile.am 2015-03-04 14:53:49.184605415 -0500 gwave-20090213/spicefile/Makefile.am 2015-03-04 14:53:49.180605415 -0500 @@ -10,11 +10,9 @@ noinst_PROGRAMS = test_read @@ -24,8 +26,10 @@ Last-Update: 2011-09-15 -sp2sp_LDADD= libspicefile.a +sp2sp_LDADD= libspicefile.a @GTK_LIBS@ a/src/Makefile.in -+++ b/src/Makefile.in +Index: gwave-20090213/src/Makefile.in +=== +--- gwave-20090213.orig/src/Makefile.in 2015-03-04 14:53:49.184605415 -0500 gwave-20090213/src/Makefile.in 2015-03-04 14:59:00.784607430 -0500 @@ -55,7 +55,7 @@ GtkTable_indel.$(OBJEXT) gwave_OBJECTS = $(am_gwave_OBJECTS) @@ -35,8 +39,19 @@ Last-Update: 2011-09-15 $(LDFLAGS) -o $@ DEFAULT_INCLUDES = -I. -I$(top_builddir)@am__isrc@ depcomp = $(SHELL) $(top_srcdir)/depcomp a/spicefile/Makefile.in -+++ b/spicefile/Makefile.in +@@ -189,7 +189,7 @@ + rgeval.c xgserver.c measurebtn.c measurebtn.h \ + GtkTable_indel.c GtkTable_indel.h xsnarf.h + +-gwave_LDADD = ../spicefile/libspicefile.a @GTK_LIBS@ @GUILE_GNOME_LIBS@ -lX11 ++gwave_LDADD = ../spicefile/libspicefile.a @GTK_LIBS@ @GUILE_GNOME_LIBS@ -lX11 -lm + gwave_LDFLAGS = @GUILE_LDFLAGS@ + AM_CFLAGS = @GTK_CFLAGS@ @GUILE_CFLAGS@ @GUILE_GNOME_CFLAGS@ \ + -DDATADIR=\$(datadir)\ -DBINGWAVE=\$(bindir)/gwave\ +Index: gwave-20090213/spicefile/Makefile.in +=== +--- gwave-20090213.orig/spicefile/Makefile.in 2015-03-04 14:53:49.184605415 -0500 gwave-20090213/spicefile/Makefile.in 2015-03-04 14:53:49.184605415 -0500 @@ -186,11 +186,9 @@ libspicefile_a_SOURCES = spicestream.c ss_cazm.c ss_hspice.c ss_spice3.c ss_spice2.c ss_nsout.c spicestream.h wavefile.c wavefile.h spice2.h ssintern.h AM_CFLAGS = @GTK_CFLAGS@ diff --git a/debian/patches/guile2.0.diff b/debian/patches/guile2.0.diff index e4a6428..38b76b3 100644 --- a/debian/patches/guile2.0.diff +++ b/debian/patches/guile2.0.diff @@ -6,8 +6,8 @@ Bug-Debian: http://bugs.debian.org/746003 Index: gwave-20090213/src/scwm_guile.h === gwave-20090213.orig/src/scwm_guile.h -+++ gwave-20090213/src/scwm_guile.h +--- gwave-20090213.orig/src/scwm_guile.h 2015-03-04 14:59:23.528607577 -0500 gwave-20090213/src/scwm_guile.h
Bug#779802: vtk6: FTBFS: error: no matching function for call to 'min(unsigned int, int)'
Source: vtk6
Version: 6.1.0+dfsg2-5
Tags: sid
Severity: serious
Justification: fails to build from source
Dear Maintainer,
vtk6 fails to build on sid/amd64, but it works on jessie/amd64 (hence the sid
tag).
The errors are:
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx: In member
function 'bool vtkFreeTypeTools::CalculateBoundingBox(const T,
vtkFreeTypeTools::MetaData)':
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:1190:51: error: no
matching function for call to 'min(unsigned int, int)'
metaData.descent);
^
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:1190:51:
note: candidates are:
In file included from /usr/include/c++/4.9/bits/char_traits.h:39:0,
from /usr/include/c++/4.9/ios:40,
from /usr/include/c++/4.9/ostream:38,
from /usr/include/c++/4.9/iostream:39,
from /tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkIOStream.h:33,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkSystemIncludes.h:36,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/debian/build/Common/Core/vtkAtomicInt.h:38,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkObjectBase.h:44,
from /tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkObject.h:42,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.h:27,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:16:
/usr/include/c++/4.9/bits/stl_algobase.h:194:5: note: templateclass _Tp const _Tp
std::min(const _Tp, const _Tp)
min(const _Tp __a, const _Tp __b)
^
/usr/include/c++/4.9/bits/stl_algobase.h:194:5: note: template argument
deduction/substitution failed:
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:1190:51:
note: deduced conflicting types for parameter 'const _Tp' ('unsigned int' and
'int')
metaData.descent);
^
In file included from /usr/include/c++/4.9/bits/char_traits.h:39:0,
from /usr/include/c++/4.9/ios:40,
from /usr/include/c++/4.9/ostream:38,
from /usr/include/c++/4.9/iostream:39,
from /tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkIOStream.h:33,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkSystemIncludes.h:36,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/debian/build/Common/Core/vtkAtomicInt.h:38,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkObjectBase.h:44,
from /tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkObject.h:42,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.h:27,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:16:
/usr/include/c++/4.9/bits/stl_algobase.h:240:5: note: templateclass _Tp, class _Compare
const _Tp std::min(const _Tp, const _Tp, _Compare)
min(const _Tp __a, const _Tp __b, _Compare __comp)
^
/usr/include/c++/4.9/bits/stl_algobase.h:240:5: note: template argument
deduction/substitution failed:
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:1190:51:
note: deduced conflicting types for parameter 'const _Tp' ('unsigned int' and
'int')
metaData.descent);
^
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx: In member
function 'void vtkFreeTypeTools::GetLineMetrics(T, T, vtkFreeTypeTools::MetaData,
int, int*)':
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:1954:77: error: no
matching function for call to 'max(int, unsigned int)'
bbox[1] = std::max(bbox[1], pen[0] + bitmapGlyph-left + bitmap-width);
^
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.cxx:1954:77:
note: candidates are:
In file included from /usr/include/c++/4.9/bits/char_traits.h:39:0,
from /usr/include/c++/4.9/ios:40,
from /usr/include/c++/4.9/ostream:38,
from /usr/include/c++/4.9/iostream:39,
from /tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkIOStream.h:33,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkSystemIncludes.h:36,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/debian/build/Common/Core/vtkAtomicInt.h:38,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkObjectBase.h:44,
from /tmp/buildd/vtk6-6.1.0+dfsg2/Common/Core/vtkObject.h:42,
from
/tmp/buildd/vtk6-6.1.0+dfsg2/Rendering/FreeType/vtkFreeTypeTools.h:27,
from
Bug#777016: marked as done (linux-image-3.18.0-trunk-amd64: kernel panic in __intel_set_mode)
Your message dated Wed, 04 Mar 2015 21:16:16 +0100 with message-id 54f76810.8090...@oxanvanleeuwen.nl and subject line fixed has caused the Debian Bug report #777016, regarding linux-image-3.18.0-trunk-amd64: kernel panic in __intel_set_mode 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.) -- 777016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.18.5-1~exp1 Severity: serious My system hangs when booting using kernel 3.18 sometime after unlocking the encrypted root disk. Kernel 3.17 works fine. * Using the default kernel command line, the problem occurs everytime. * Using the nomodeset parameter, the kernel works fine but I can't use X. * When using netconsole, the system sometimes hangs and sometimes works fine, though outputting a warning in the kernel (see first log below). When the kernel hangs, unfortunately only the first few lines of the BUG show up in the netconsole (see second log at the bottom). Let me know if I can be of any more assistance. -- Package-specific info: ** Version: Linux version 3.18.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 3.18.5-1~exp1 (2015-01-31) ** Command line: BOOT_IMAGE=/vmlinuz-3.18.0-trunk-amd64 root=UUID=452d1dc1-2c61-4bba-b64a-8137c122bf0b ro net.ifnames=1 netconsole=@130.89.172.53/eth0,@130.89.171.131/60:a4:4c:d6:77:4d ** Tainted: W (512) * Taint on warning. ** Kernel log (when system was booted with netconsole and didn't panic): [9.236016] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [9.236361] acpi device:60: registered as cooling_device10 [9.236420] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9 [9.236629] [drm] Initialized i915 1.6.0 20140905 for :00:02.0 on minor 0 [9.236710] ACPI Warning: SystemIO range 0xf040-0xf05f conflicts with OpRegion 0xf040-0xf04f (\_SB_.PCI0.SBUS.SMBI) (20140926/utaddress-258) [9.236728] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [9.236820] snd_hda_intel :00:03.0: enabling device ( - 0002) [9.236883] snd_hda_intel :00:1b.0: enabling device ( - 0002) [9.237298] snd_hda_intel :00:03.0: irq 31 for MSI/MSI-X [9.237400] snd_hda_intel :00:1b.0: irq 32 for MSI/MSI-X [9.247250] sound hdaudioC1D0: autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [9.247255] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [9.247257] sound hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [9.247259] sound hdaudioC1D0:mono: mono_out=0x0 [9.247261] sound hdaudioC1D0:dig-out=0x1e/0x0 [9.247262] sound hdaudioC1D0:inputs: [9.247264] sound hdaudioC1D0: Front Mic=0x19 [9.247266] sound hdaudioC1D0: Rear Mic=0x18 [9.247268] sound hdaudioC1D0: Line=0x1a [9.260930] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input18 [9.261589] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card0/input19 [9.261619] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card1/input10 [9.261928] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card0/input20 [9.262246] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card1/input11 [9.262699] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input12 [9.262997] input: HDA Intel PCH Line Out Front as /devices/pci:00/:00:1b.0/sound/card1/input13 [9.263271] input: HDA Intel PCH Line Out Surround as /devices/pci:00/:00:1b.0/sound/card1/input14 [9.263535] input: HDA Intel PCH Line Out CLFE as /devices/pci:00/:00:1b.0/sound/card1/input15 [9.263815] input: HDA Intel PCH Line Out Side as /devices/pci:00/:00:1b.0/sound/card1/input16 [9.264073] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card1/input17 [9.279344] [ cut here ] [9.279372] WARNING: CPU: 0 PID: 411 at /build/linux-xmCjRp/linux-3.18.5/drivers/gpu/drm/i915/intel_display.c:11417 intel_crtc_set_config+0xbe8/0xe60 [i915]() [9.279374] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nls_utf8 nls_cp437 vfat fat iTCO_wdt mxm_wmi ppdev
Bug#779799: linux: Older patches causing FTBFS on armhf
On Wed, Mar 04, 2015 at 09:29:43PM +, B.R. Oake wrote: Source: linux Version: 3.19-1~exp1 Justification: fails to build from source Severity: serious Hello, The two patches: features/arm/dts-sun7i-Add-spi0_pins_a-pinctrl-setting.patch features/arm/dts-sun7i-Add-uart3_pins_b-pinctrl-setting.patch are no longer needed in 3.19-1~exp1 because they were accepted upstream in v3.19 as these commits: 2dad53b54a 0510e4b52a Keeping the patches means getting duplicate nodes in the device tree which causes this build failure on armhf: https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armhfver=3.19-1~exp1stamp=1424044478 Please could you remove the patches from the next experimental version? they are already removed in the repository for experimental, waiting for 3.19.X for the next upload. in any case thanks for the details. -- maks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779798: openjfx: FTBFS error: conflicting declaration 'typedef int32_t UChar32'
Thank you for the report Andreas, this is a side effect of the icu support recently enabled in libxml2 (#776254). I fixed it today in openjfx/8u40-b25. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779799: linux: Older patches causing FTBFS on armhf
On 04/03/15 22:20, maximilian attems wrote: they are already removed in the repository for experimental, waiting for 3.19.X for the next upload. in any case thanks for the details. Hi, maks; thanks, that's good to know. For the future, is there a way for me to check whether such things have already been fixed before I report them? Is the repository that you mentioned public? Thanks, B.R. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#771485: installation-reports: Installation disk scan hangs at 81% with LVM inside crypt partition
Processing control commands:
reassign -1 partman-base
Bug #771485 [installation-reports] installation-reports: Installation disk scan
hangs at 81% with LVM inside crypt partition
Bug reassigned from package 'installation-reports' to 'partman-base'.
Ignoring request to alter found versions of bug #771485 to the same values
previously set
Ignoring request to alter fixed versions of bug #771485 to the same values
previously set
forcemerge 778773 -1
Bug #778773 {Done: Cyril Brulebois k...@debian.org} [partman-base] Jessie RC1
Installer parted server segfault
Bug #771617 {Done: Cyril Brulebois k...@debian.org} [partman-base] installer
beta 2: jessie parted_server segfault on AMD Athlon64
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
Bug #771485 [partman-base] installation-reports: Installation disk scan hangs
at 81% with LVM inside crypt partition
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as fixed in versions partman-base/181.
Added tag(s) d-i and patch.
Bug #771485 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: Installation disk scan hangs at 81% with LVM inside crypt
partition
Ignoring request to alter fixed versions of bug #771485 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #771485 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: Installation disk scan hangs at 81% with LVM inside crypt
partition
Ignoring request to alter fixed versions of bug #771485 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #771485 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: Installation disk scan hangs at 81% with LVM inside crypt
partition
Ignoring request to alter fixed versions of bug #771485 to the same values
previously set
Bug #771617 {Done: Cyril Brulebois k...@debian.org} [partman-base] installer
beta 2: jessie parted_server segfault on AMD Athlon64
Bug #773274 {Done: Cyril Brulebois k...@debian.org} [partman-base]
installation-reports: parted_server segfault
After four attempts, the following changes were unable to be made:
fixed_versions of #771485 is 'partman-base/181' not '181'
Failed to forcibly merge 778773: Unable to modify bugs so they could be merged.
--
771485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771485
771617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771617
773274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773274
778773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778773
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#779812: diaspora-installer: package should be in contrib
Package: diaspora-installer Severity: serious The diaspora-installer package should be placed in contrib as it uses wget and rubygems instead of installing diaspora from Debian packages. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#779798: marked as done (openjfx: FTBFS error: conflicting declaration 'typedef int32_t UChar32')
Your message dated Thu, 05 Mar 2015 00:42:45 +0100 with message-id 54f79875.9050...@googlemail.com and subject line Re: Bug#779798: openjfx: FTBFS error: conflicting declaration 'typedef int32_t UChar32' has caused the Debian Bug report #779798, regarding openjfx: FTBFS error: conflicting declaration 'typedef int32_t UChar32' 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.) -- 779798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: openjfx Version: 8u20-b26-3 Severity: serious Justification: fails to build from source Dear Maintainer, openjfx fails to build on sid/amd64: In file included from /usr/include/x86_64-linux-gnu/unicode/utypes.h:36:0, from /usr/include/x86_64-linux-gnu/unicode/ucnv_err.h:86, from /usr/include/x86_64-linux-gnu/unicode/ucnv.h:50, from /usr/include/libxml2/libxml/encoding.h:31, from /usr/include/libxml2/libxml/parser.h:810, from ../../../../src/main/native/Source/WebCore/xml/XSLStyleSheet.h:32, from ../../../../src/main/native/Source/WebCore/xml/XSLTProcessor.h:29, from generated/JSXSLTProcessor.h:27, from generated/JSDOMWindow.cpp:614: /usr/include/x86_64-linux-gnu/unicode/umachine.h:298:17: error: conflicting declaration 'typedef int32_t UChar32' typedef int32_t UChar32; ^ In file included from ../../../../src/main/native/Source/WTF/wtf/unicode/Unicode.h:36:0, from ../../../../src/main/native/Source/WTF/wtf/text/ASCIIFastPath.h:31, from ../../../../src/main/native/Source/WTF/wtf/text/WTFString.h:28, from ../../../../src/main/native/Source/WTF/wtf/DateMath.h:54, from ../../../../src/main/native/Source/WebCore/webcorejava_pch.h:57: ../../../../src/main/native/Source/WTF/wtf/unicode/java/UnicodeJava.h:24:18: note: previous declaration as 'typedef uint32_t UChar32' typedef uint32_t UChar32; ^ This can also be seen in the reproducibility rebuild [1]. Best regards, Andreas 1: https://reproducible.debian.net/rb-pkg/sid/amd64/openjfx.html ---End Message--- ---BeginMessage--- Version: 8u40-b25-1 Hi Emmanuel, On 04.03.2015 23:39, Emmanuel Bourg wrote: Thank you for the report Andreas, this is a side effect of the icu support recently enabled in libxml2 (#776254). I fixed it today in openjfx/8u40-b25. Indeed, I hadn't noticed that. Sorry for the noise. Best regards, Andreas---End Message---
Bug#775624: procps: FTBFS in jessie: dh_auto_test: make -j1 check returned exit code 2
On Sat, 24 Jan 2015 08:59:23 +0100 Vincent Bernat ber...@debian.org wrote: ⦠24 janvier 2015 18:50 +1100, Craig Small csm...@debian.org : I'm not sure if you are able to, but if you could apply the attached patch to see if the test works now that would be great. make make test (fails) apply patch make make test (works) Yes, the patch makes the tests pass. -- Write and test a big program in small pieces. - The Elements of Programming Style (Kernighan Plauger) Hi, Is there anything holding up this bug from being fixed? If the linux patch will solve this then please CC the linux maintainers and ask them to apply it (assuming it was not included in their 3.16.7-ckt7-1 upload). Otherwise, if the test is broken, then please patch out the test. Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: user debian-secur...@lists.debian.org, usertagging 779801, tagging 779801 ...
Processing commands for cont...@bugs.debian.org: user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). usertags 779801 + tracked There were no usertags set. Usertags are now: tracked. tags 779801 + upstream fixed-upstream Bug #779801 [pngcrush] CVE-2015-2158 Added tag(s) upstream and fixed-upstream. retitle 779801 pngcrush: CVE-2015-2158 Bug #779801 [pngcrush] CVE-2015-2158 Changed Bug title to 'pngcrush: CVE-2015-2158' from 'CVE-2015-2158' thanks Stopping processing here. Please contact me if you need assistance. -- 779801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779801 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#779727: marked as done (Source package contains oracle-java8-jdk_8_amd64.deb)
Your message dated Thu, 05 Mar 2015 00:03:31 + with message-id e1ytjgf-00078j...@franck.debian.org and subject line Bug#779727: fixed in java-package 0.58 has caused the Debian Bug report #779727, regarding Source package contains oracle-java8-jdk_8_amd64.deb 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.) -- 779727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: java-package Version: 0.57 Severity: serious Looks like oracle-java8-jdk_8_amd64.deb was accidentally included in the source package upload. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (550, 'stable-updates'), (550, 'stable'), (530, 'testing'), (520, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16.0-0.bpo.4-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information ---End Message--- ---BeginMessage--- Source: java-package Source-Version: 0.58 We believe that the bug you reported is fixed in the latest version of java-package, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg ebo...@apache.org (supplier of updated java-package 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: SHA1 Format: 1.8 Date: Thu, 05 Mar 2015 00:09:05 +0100 Source: java-package Binary: java-package Architecture: source all Version: 0.58 Distribution: experimental Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: java-package - Utility for creating Java Debian packages Closes: 776395 779727 Changes: java-package (0.58) experimental; urgency=medium . [ Francesc Zacarias ] * New --with-system-certs option to use the system keystore (Closes: #776395) . [ Emmanuel Bourg ] * Removed the generated package mistakenly included in the source package (Closes: #779727) Checksums-Sha1: 95427492657f6d6fb494527d47f1f97abedb5fcc 1628 java-package_0.58.dsc 8e8505ab241dc6d5f247e4d46e4d22725d00abdb 18840 java-package_0.58.tar.xz 96afda095c16efec100d52b0e9feb2ea839e3ff9 21146 java-package_0.58_all.deb Checksums-Sha256: 6fc89275eb32e340daf61aa5248e0c094618cab62c9f325a844a1b6dad34f2da 1628 java-package_0.58.dsc 10099755471dd8206e272b09a01b3d0ba0137585af6579a5027ad8bbf29a5112 18840 java-package_0.58.tar.xz 36ece1d9a6e593bfb061c2308e73423f27747077690fa5d142bd6f433c6a01e4 21146 java-package_0.58_all.deb Files: 0ac8e5dfc7c6312534d402b418d1d04b 1628 contrib/misc optional java-package_0.58.dsc b554fc98350ec6cba420d3cd7f40fec9 18840 contrib/misc optional java-package_0.58.tar.xz 0c310d605c0f5d9bac538dbdc29e815e 21146 contrib/misc optional java-package_0.58_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU95tIAAoJEPUTxBnkudCsm8MQAIO0GMdI2h52iqp3ch4mJG9o 9YGkvQnWXRFP6QTrZ1dpaqlX5OMWGHZs1d0pLXtXpZCgeRIASW5gy+aaRpmFE/zq 2VdUCrvh31ApvHkcUJKB0F8W3/Zj2l8gnoZJk6wXoaqYD3YNvovzkgKnKHMt+3EY 2G6F5ZucCsYaTx+xLe3MANxGC0emKaWwevFOjZRYI7Nj3eD0DVxu3REbQ/iEhwkN bs83KlCWEctiClvEE94ccdrWlmBYa7mp1+317tiX0/rCjsW6WIXJpXawfdBPnEbc XRhqRGAMBOOljq/T2OowNuCct+hgs5uTlC9SqNy16rzXJ5HLtDiTGDraNouLv00b DL2b/VcPZt5zAl8xSv13E/ht82Gu93yE5EKdc95voqSKIHPKvFBCe5I1wZ//DmUF 5gTD5DXZjUwcUwfySepOTNBXTXnMsH5DnaN+/yM92YMmv3sYF52yg2JOkqyNAk9K 7Mo6uFaf6kMnGgQP7xfydiOmvoO2gXuUg+5Vg0TUiOkLS1hgU0G82zB4QcFDBQfA cFMwKYHcYeEmPtu9jocwrn2pjwBlH+76aHjGdrYAkcQ9OA4LN4WWmqiQwdG91gkH pteL/em4DiE6akpildwNqxhQmveoqsVAhH9R9ghpsPAM6Vyr503jQV9ACoLwdw7u j+o4LwLPr+Dd3COE/HLO =Vj20 -END PGP SIGNATUREEnd Message---
Bug#779112: marked as done (libjnr-constants-java, libconstantine-java: error when trying to install together)
Your message dated Thu, 05 Mar 2015 03:18:55 + with message-id e1ytmjl-0003jl...@franck.debian.org and subject line Bug#779112: fixed in jnr-constants 0.8.6-3 has caused the Debian Bug report #779112, regarding libjnr-constants-java, libconstantine-java: error when trying to install together 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.) -- 779112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libjnr-constants-java,libconstantine-java Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Architecture: amd64 Distribution: sid + experimental Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libconstantine-java. Preparing to unpack .../libconstantine-java_0.8.5-1_all.deb ... Unpacking libconstantine-java (0.8.5-1) ... dpkg: error processing archive /var/cache/apt/archives/libconstantine-java_0.8.5-1_all.deb (--unpack): trying to overwrite '/usr/share/java/jnr-constants.jar', which is also in package libjnr-constants-java 0.8.6-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libconstantine-java_0.8.5-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/java/constantine.jar usr/share/java/jnr-constants.jar usr/share/java/libconstantine.jar usr/share/maven-repo/com/github/jnr/jnr-constants/debian/jnr-constants-debian.jar usr/share/maven-repo/com/github/jnr/jnr-constants/debian/jnr-constants-debian.pom This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html libjnr-constants-java=0.8.6-2_libconstantine-java=0.8.5-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: jnr-constants Source-Version: 0.8.6-3 We believe that the bug you reported is fixed in the latest version of jnr-constants, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Potter t...@hp.com (supplier of updated jnr-constants 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: SHA1 Format: 1.8 Date: Wed, 04 Mar 2015 15:38:48 +1100 Source: jnr-constants Binary: libjnr-constants-java libjnr-constants-java-doc Architecture: source all Version: 0.8.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Tim Potter t...@hp.com Description: libjnr-constants-java - platform constants for Java libjnr-constants-java-doc - platform constants for Java - API documentation Closes: 779112 Changes: jnr-constants (0.8.6-3) unstable; urgency=medium . * Team upload. * Change dependency on libconstantine-java to Conflicts, from Breaks. (Closes: #779112). Checksums-Sha1: 8b0c7ee8c53b10b4a149e7ea30a50b045d67cd03 2125
Bug#767138: Business Project.
I am Mrs Yeung Wong, pardon me for this unsolicited email. I am contacting you confidentially to discuss a secure business project, I need your permission before I give details. Regards, Yeung -- Esta mensagem foi verificada pelo sistema de antivirus e acredita-se estar livre de perigo.
Bug#779799: linux: Older patches causing FTBFS on armhf
On Wed, 2015-03-04 at 22:44 +, B.R. Oake wrote: On 04/03/15 22:20, maximilian attems wrote: they are already removed in the repository for experimental, waiting for 3.19.X for the next upload. in any case thanks for the details. Hi, maks; thanks, that's good to know. For the future, is there a way for me to check whether such things have already been fixed before I report them? Is the repository that you mentioned public? It's in svn: http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
On 03/04/2015 01:02 AM, Mauricio Faria de Oliveira wrote: Hi Siresh, On 03/03/2015 08:32 AM, Mauricio Faria de Oliveira wrote: Sure, I can try and should send a patch soon. I've modified the build-arch target to build multipath-udeb first, and store its output in a different directory; and the install target to use that dir only for dh_install of multipath-udeb. May you please consider it for an upload? Thanks Mauricio. I've uploaded the package and raised an unblock request. Debian Bug #779701 Hopefully, this will be unblocked immediate. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#779703: isort is missing build dependencies, trying to download from pypi
Package: src:isort
Version: 3.9.2+ds1-1
Severity: serious
Tags: sid
without network connection, the package fails to build:
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:170: python3.4 setup.py test
running test
Searching for pies=2.6.0
Reading https://pypi.python.org/simple/pies/
Download error on https://pypi.python.org/simple/pies/: [Errno 111] Connection
refused -- Some packages may not be found!
Couldn't find index page for 'pies' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno 111] Connection
refused -- Some packages may not be found!
No local packages or download links found for pies=2.6.0
error: Could not find suitable distribution for Requirement.parse('pies=2.6.0')
E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1:
python3.4 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit
code 13
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 13
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779193: marked as done (grml2usb: syslinux fails to install, missing sync of filesystem)
Your message dated Wed, 04 Mar 2015 09:19:06 + with message-id e1yt5sm-0007j6...@franck.debian.org and subject line Bug#779193: fixed in grml2usb 0.14.10.1 has caused the Debian Bug report #779193, regarding grml2usb: syslinux fails to install, missing sync of filesystem 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.) -- 779193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: grml2usb Version: 0.14.10 Severity: grave There seems to be a regression when executing grml2usb on systems being Debian/jessie or newer, quite often causing syslinux to fail its execution: | [...] | Installing default MBR | Installing syslinux as bootloader | syslinux: /dev/sdb1: No such file or directory | Fatal: Error executing syslinux (either try --fat16 or use grub?) The installation of the MBR causes pending writes not being finished before syslinux is executed. This simple change fixes the problem: , [ pending fix ] | --- a/grml2usb | +++ b/grml2usb | @@ -645,6 +645,10 @@ def install_mbr(mbrtemplate, device, partition, ismirbsdmbr=True): | raise Exception(error executing dd (third run)) | del tmpf | | +# make sure we sync filesystems before returning | +proc = subprocess.Popen([sync]) | +proc.wait() | + | | def is_writeable(device): | Check if the device is writeable for the current user ` grml2usb shouldn't be released with Debian/jessie without this change, I'm planning to upload a grml2usb package to unstable including this fix and will submit an unblock request. regards, -mika- ---End Message--- ---BeginMessage--- Source: grml2usb Source-Version: 0.14.10.1 We believe that the bug you reported is fixed in the latest version of grml2usb, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Prokop m...@grml.org (supplier of updated grml2usb 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, 25 Feb 2015 14:27:19 +0100 Source: grml2usb Binary: grml2usb Architecture: source amd64 Version: 0.14.10.1 Distribution: unstable Urgency: medium Maintainer: Grml Team t...@grml.org Changed-By: Michael Prokop m...@grml.org Description: grml2usb - install Grml system / ISO to usb device Closes: 779193 Changes: grml2usb (0.14.10.1) unstable; urgency=medium . * [bfe149a] Sync filesystems before returning from MBR installation (Closes: #779193) * [83944f2] Add syslinux-utils to Recommends + adjust error message for isohybrid (related to #751724) Checksums-Sha1: 36adf53c63a4fcdb181f7c200fb0b84bd51ba791 1730 grml2usb_0.14.10.1.dsc 44c020393af802b2d12035c5518badfba52de2d1 384748 grml2usb_0.14.10.1.tar.xz 7409874a9ede5e2b626c999a8e75040e6041a226 216032 grml2usb_0.14.10.1_amd64.deb Checksums-Sha256: 6124da13cfe3a1d8791a25ada68f0e4ae956dbd30d19d0140d1554fee69cbee4 1730 grml2usb_0.14.10.1.dsc 36788a69f1a71ff76c8ef813c82a38e62324514866afd4fcead46009e1184605 384748 grml2usb_0.14.10.1.tar.xz 53e42be5d233a92f3a46b110ac79258e3fb771cf7d2a10314b9dcc287eecf649 216032 grml2usb_0.14.10.1_amd64.deb Files: 5d2154909d10ed4aae4cc8672d32ddca 1730 admin optional grml2usb_0.14.10.1.dsc dcdbd04f4517321b42e7ef4424938f4b 384748 admin optional grml2usb_0.14.10.1.tar.xz 62aae251b87f5333cb27f792c412a421 216032 admin optional grml2usb_0.14.10.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJU9r6FAAoJEJaoeHK36jc3XJkQAJ3mYzwGVzfXSXGRSZZIaw3n oAH1Tnemy4kDfB/+eDd5MWOdAluLiLcl21eDspukG/kjn33rZ+jv/LV6qijAA0kX dKZaMI/hO9H0EWQB4gSyI+ZN0ViQ4V9/bTMkdxZJ8etHnUV9SCUjh1HqA8R9HObO xANxakQdCey8ZVb6WZrqRDMPfLIIKzcCEmPw3vyHfiMwiWMPOxsUIlJ/1OGsOmcK hoiBOb95Sn96egyspEtZOCELLWYhnK/j/FApN5zqOuCOJX37JxSdTT+eaC5UVZJ5 KSJ9QIX330AffVsFjfSpG94EVhP8RPPqJXzv5odJ7DlDxe0zDM20za8u5b6D3lgg SE//ec0/AL8zZQdf8tRxBQUwG30ZeZ6pI8qvCpcIHmQG94VurLN5ocQYRt8xRdMd U9leBLOo1SX1ZqoR98DJVJsB8/ovUaP3a4UMNkyb8Qu/2F5Q3nnqEviX1Y5DKP7s xMDo1TCPrNYjejCWLbIIwD8Ia3vFcmIFfu3epcMg0iRyHKv5Wj7YBgOicvNuP7gQ a3xfiZMzLkIgFu1iwV51GqxxtwIEjMjKHzIl2TRRa0qeHG+ChkB3SFtSbzQ2Ctds
Bug#779579: marked as done (installer broken: multipath-udeb depends on non-existent libgcc1 udeb)
Your message dated Wed, 04 Mar 2015 09:19:38 + with message-id e1yt5ss-0007zd...@franck.debian.org and subject line Bug#779579: fixed in multipath-tools 0.5.0-6 has caused the Debian Bug report #779579, regarding installer broken: multipath-udeb depends on non-existent libgcc1 udeb 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.) -- 779579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:multipath-tools Version: 0.5.0-5 During a multipath installation (disk-detect/multipath/enable=true), the multipath binary fails to run because libgcc is missing: ~ # grep 'multipath\|libgcc' /var/log/syslog | grep -v kernel | cut -d' ' -f5- anna-install: Installing multipath-udeb anna[3505]: DEBUG: resolver (libgcc1): package doesn't exist (ignored) anna[3505]: DEBUG: retrieving multipath-modules-3.16.0-4-powerpc64le-di 3.16.7-ckt4-3 anna[3505]: DEBUG: retrieving multipath-udeb 0.5.0-5 disk-detect: /sbin/multipath: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory disk-detect: No multipath devices detected main-menu[191]: (process:3777): multipath: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory [snip; repeat] This can be verified in d-i's Packages file [1]: Package: multipath-udeb Source: multipath-tools Version: 0.5.0-5 [...] Depends: [...], libgcc1, [...] which has no such package: $ curl -s ftp://ftp.debian.org/debian/dists/sid/main/debian-installer/binary-amd64/Packages.xz | xzgrep '^Package: libgcc1' | wc -l 0 [1] ftp://ftp.debian.org/debian/dists/sid/main/debian-installer/binary-amd64/ -- Mauricio Faria de Oliveira IBM Linux Technology Center ---End Message--- ---BeginMessage--- Source: multipath-tools Source-Version: 0.5.0-6 We believe that the bug you reported is fixed in the latest version of multipath-tools, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ritesh Raj Sarraf r...@debian.org (supplier of updated multipath-tools 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: SHA1 Format: 1.8 Date: Tue, 03 Mar 2015 15:52:58 -0300 Source: multipath-tools Binary: multipath-tools multipath-tools-dbg kpartx multipath-tools-boot multipath-udeb kpartx-udeb Architecture: source amd64 all Version: 0.5.0-6 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team pkg-lvm-maintain...@lists.alioth.debian.org Changed-By: Ritesh Raj Sarraf r...@debian.org Description: kpartx - create device mappings for partitions kpartx-udeb - create device mappings for partitions - udeb package (udeb) multipath-tools - maintain multipath block device access multipath-tools-boot - Support booting from multipath devices multipath-tools-dbg - maintain multipath block device access - debugging symbols multipath-udeb - maintain multipath block device access - udeb package (udeb) Closes: 779579 Changes: multipath-tools (0.5.0-6) unstable; urgency=medium . [ Mauricio Faria de Oliveira ] * Build multipath-udeb with static libgcc (Closes: #779579) Checksums-Sha1: 3d20ba2611d8f2b34e4a049803c33368a9ef63ef 2429 multipath-tools_0.5.0-6.dsc 3188c9132b108c28aca3cbea3955cc27546ff6d5 28136 multipath-tools_0.5.0-6.debian.tar.xz 689e5a7a5653e448b5b8216db0763a144db3cf85 185514 multipath-tools_0.5.0-6_amd64.deb 762236a85aea1eb8e5d01276e6b10e9f193e16d5 355668 multipath-tools-dbg_0.5.0-6_amd64.deb 9271f736d10ed5154133a7d34c7680b29d7ecd84 31194 kpartx_0.5.0-6_amd64.deb 2165c60d3b5dfcc86e7817638ccbbf61519aaacb 17712 multipath-tools-boot_0.5.0-6_all.deb 80af09f89fe17ae93fb0a74ac808e6ac4bf858c9 119570 multipath-udeb_0.5.0-6_amd64.udeb 7e9ecc9db01760bf6add1996e312c7004beff9c3 15900 kpartx-udeb_0.5.0-6_amd64.udeb Checksums-Sha256: 5af471286e0024a855bdd46d8feb2722c43f664cc102f2b30f38da39eb5c63a1 2429 multipath-tools_0.5.0-6.dsc
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com (2015-03-03): (BTW, espeakup-udeb is broken too; that approach no longer works.) ~ # anna-install espeakup-udeb ~ # espeakup espeakup: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory (JFTR: espeakup certainly runs properly in the netboot-gtk mini.iso when selecting speech synthesis.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
On 03/04/2015 06:43 AM, Cyril Brulebois wrote: Mauricio Faria de Oliveiramauri...@linux.vnet.ibm.com (2015-03-03): (BTW, espeakup-udeb is broken too; that approach no longer works.) (JFTR: espeakup certainly runs properly in the netboot-gtk mini.iso when selecting speech synthesis.) Ah, thanks for clarifying. I didn't know of that context/option; sorry. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779688: libjson-rpc-cpp: FTBFS: gen/abstractsubserver.h: No such file or directory
Hi! You are probably right. Usually I build this with make -j8 on my machine, but maybe there is a dependency missing. Greetings Peter On 03/04/2015 04:39 AM, Aaron M. Ucko wrote: Source: libjson-rpc-cpp Version: 0.4.2-3 Severity: serious Justification: fails to build from source Builds of libjson-rpc-cpp failed for several architectures with the error /«PKGBUILDDIR»/src/test/test_integration.cpp:17:35: fatal error: gen/abstractsubserver.h: No such file or directory It looks like this error may stem from an undeclared dependency that's only a problem in parallel builds; if so, you might consider simply dropping --parallel from your dh invocations for now. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779123: marked as done (mono-apache-server4: depend on perl instead of perl-modules)
Your message dated Wed, 4 Mar 2015 11:08:12 + with message-id 20150304110812.ga18...@pc1.creditreform.bg and subject line Re: Bug#779123: xsp: diff for NMU version 3.8-2.1 has caused the Debian Bug report #779123, regarding mono-apache-server4: depend on perl instead of perl-modules 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.) -- 779123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mono-apache-server4 Version: 3.8-2 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Version: 3.8-2.1 +xsp (3.8-2.1) unstable; urgency=high + + * Non-maintainer upload fixing bugs blocking serious bug #777597 -- +perl-modules: upgrade regression: dpkg: dependency problems prevent +configuration of perl-modules + + * replace dependencies on 'perl-modules' with 'perl' as per Perl policy +(Closes: #779124, #779122, #779125) + + -- Damyan Ivanov d...@debian.org Wed, 25 Feb 2015 21:14:04 + The above changelog missed this bug in the list of closed bug, so closing explicitly.---End Message---
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Hi Ritesh, On 03/04/2015 06:12 AM, Ritesh Raj Sarraf wrote: Thanks Mauricio. I've uploaded the package and raised an unblock request. Debian Bug #779701 Hopefully, this will be unblocked immediate. Thanks! I just tested the package in incoming.d.o and it's OK. If you or Cyril could please educate me: For it to reach the d-i Packages file (so it's available for installs), does it require a d-i rebuild, or it's an automatic process? (I'm unsure; there's no multipath-udeb listed in d-i build log.) -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779613: no such file or directory trying to connect through the blueman-applet
On 2015-03-04 02:20:45, Christopher Schramm wrote: Anyway, connecting to a NAP should work. You just have to select the service from the device menu and not use the generic connect item for that. There's no service from the menu, in fact, the Serial server menu item is gone. So you are talking about a serial service, not a NAP service. Frankly, I have no idea. I am just seeing this failing to work now, whereas it was working before. Support for serial services with BlueZ 5 is not available in the alpha1 snapshot, but recently made it into current upstream master. I'm actually planning to do an alpha2 snapshot release and package it for unstable or experimental at the end of the week. Okay that's great, I'll try to test that when it's available! It seems a little ... daring to ship Jessie with alpha releases however... A. -- Hard times are coming when we will be wanting the voices of writers who can see alternatives to how we live now and can see through our fear-stricken society and its obsessive technologies to other ways of being, and even imagine some real grounds for hope. We will need writers who can remember freedom. Poets, visionaries—the realists of a larger reality. - Ursula Le Guin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779689: libjson-rpc-cpp: FTBFS: test suite errors
Hi! Honestly I am kind of lost how I could fix this without access to a porterbox. Are there any specific ports which are not allowed to be used? I am using port 8383 on localhost to test the networking part of this framework. Is there a specific port which I am allowed to use for testing? Do you have any suggestion how I could try to fix this issues (from an infrastructure perspective)? Because always going through the sponsoring process without knowing for sure that the new fix will work, will probably annoy my sponsor. Greetings, Peter On 03/04/2015 04:43 AM, Aaron M. Ucko wrote: Source: libjson-rpc-cpp Version: 0.4.2-3 Severity: serious Justification: fails to build from source Builds of libjson-rpc-cpp failed on several platforms with test suite errors. On armel, The following tests FAILED: 4 - connector_http (Failed) 6 - integration (Failed) 7 - all (Failed) and each of those tests also failed on some other platforms, though never the whole set elsewhere. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Ritesh Raj Sarraf r...@debian.org (2015-03-04): On 03/04/2015 05:00 PM, Mauricio Faria de Oliveira wrote: Thanks! I just tested the package in incoming.d.o and it's OK. THank you very much for confirming with test results. Yep, definitely appreciated. If you or Cyril could please educate me: For it to reach the d-i Packages file (so it's available for installs), does it require a d-i rebuild, or it's an automatic process? d-i images are built weekly. So, if the unblock goes through, it'll migrate into testing, and then the next d-i weekly snapshot should include it. (I'm unsure; there's no multipath-udeb listed in d-i build log.) I'm not sure about this. Cyril should be able to provide more insight. He's part of the d-i team. For udebs that aren't used during the debian-installer build process (as in: source package going through build.debian.org like other packages, or being built daily -- see d-i.debian.org), they're either fetch from the installation image (CD/DVD/USB flash drive etc.) or from the network. That's the case for multipath-udeb, so you won't need a d-i (re)build, just the propagation of the relevant package to testing, and a subsequent installation image build, e.g. a weekly installation image build, or a full release. Mraw, KiBi. signature.asc Description: Digital signature
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
On 03/04/2015 08:32 AM, Ritesh Raj Sarraf wrote: d-i images are built weekly. So, if the unblock goes through, it'll migrate into testing, and then the next d-i weekly snapshot should include it. Got it. Thanks. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
On 03/04/2015 05:00 PM, Mauricio Faria de Oliveira wrote: Thanks! I just tested the package in incoming.d.o and it's OK. THank you very much for confirming with test results. If you or Cyril could please educate me: For it to reach the d-i Packages file (so it's available for installs), does it require a d-i rebuild, or it's an automatic process? d-i images are built weekly. So, if the unblock goes through, it'll migrate into testing, and then the next d-i weekly snapshot should include it. (I'm unsure; there's no multipath-udeb listed in d-i build log.) I'm not sure about this. Cyril should be able to provide more insight. He's part of the d-i team. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
On 03/04/2015 09:25 AM, Cyril Brulebois wrote: For udebs that aren't used during the debian-installer build process (as in: source package going through build.debian.org like other packages, or being built daily -- see d-i.debian.org), they're either fetch from the installation image (CD/DVD/USB flash drive etc.) or from the network. That's the case for multipath-udeb, so you won't need a d-i (re)build, just the propagation of the relevant package to testing, and a subsequent installation image build, e.g. a weekly installation image build, or a full release. Very educational. Thanks, Cyril. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- 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#779666: qtsmbstatus-server: fails to upgrade from 'wheezy': insserv: Service samba has to be enabled to start service qtsmbstatusd
Processing control commands: reassign -1 qtsmbstatus-server,samba Bug #779666 [qtsmbstatus-server] qtsmbstatus-server: fails to upgrade from 'wheezy': insserv: Service samba has to be enabled to start service qtsmbstatusd Bug reassigned from package 'qtsmbstatus-server' to 'qtsmbstatus-server,samba'. No longer marked as found in versions qtsmbstatus/2.2.1-3. Ignoring request to alter fixed versions of bug #779666 to the same values previously set tag -1 jessie sid patch Bug #779666 [qtsmbstatus-server,samba] qtsmbstatus-server: fails to upgrade from 'wheezy': insserv: Service samba has to be enabled to start service qtsmbstatusd Added tag(s) sid, jessie, and patch. -- 779666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779666 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#779687: libdevel-callchecker-perl: FTBFS on i386: DynaLoader bombs out
On Wed, Mar 04, 2015 at 09:02:05AM +0200, Niko Tyni wrote:
On Tue, Mar 03, 2015 at 10:32:50PM -0500, Aaron M. Ucko wrote:
Source: libdevel-callchecker-perl
Version: 0.006-1
Severity: serious
Justification: fails to build from source
The automated build of libdevel-callchecker-perl failed (only) on
i386 due to test suite errors (excerpted from
https://buildd.debian.org/status/fetch.php?pkg=libdevel-callchecker-perlarch=i386ver=0.006-1stamp=1425399391
):
cd . ./Build test --verbose 1
Can't use an undefined value as a subroutine reference at
/usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 210.
This is a sign of ABI incompatibility between perl and the built XS
modules. The build is not using $Config{ccflags} for some reason,
so it's missing -D_FILE_OFFSET_BITS=64 which affects the binary interface.
Looks like this is #770767 in cdbs, cc'd. Possibly that one should be
release critical instead.
--
Niko Tyni nt...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779717: FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file
Package: chromium Version: 41.0.2272.76-1 Severity: grave $ chromium [0304/210821:FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779666: qtsmbstatus-server: fails to upgrade from 'wheezy': insserv: Service samba has to be enabled to start service qtsmbstatusd
Control: reassign -1 qtsmbstatus-server,samba
Control: tag -1 jessie sid patch
Since qtsmbstatus-server was in wheezy but is not in jessie, the release
team prefers to have the samba package working around this upgrade
problem (the corresponding unblock bug is #779668).
I verified that the attached patch fixes the problematic upgrade paths,
but I don't intend to NMU samba.
Andreas
From 0686613cbce92aadb4893508a8a215c0acc2e2aa Mon Sep 17 00:00:00 2001
From: Andreas Beckmann a...@debian.org
Date: Wed, 4 Mar 2015 13:27:33 +0100
Subject: [PATCH] work around qtsmbdstatus-server releated upgrade problems
---
debian/changelog | 9 +
debian/samba.preinst | 18 ++
2 files changed, 27 insertions(+)
create mode 100644 debian/samba.preinst
diff --git a/debian/changelog b/debian/changelog
index 40abb9c..b44ce23 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+samba (2:4.1.17+dfsg-2) UNRELEASED; urgency=medium
+
+ * Add samba.preinst to temporarily deactivate the old qtsmbstatusd
+initscript which has dependencies incompatible with the new samba
+initscript. This will ensure a clean upgrade path for samba if the
+qtsmbstatus-server package was installed previously. (Closes: #779666)
+
+ -- Andreas Beckmann a...@debian.org Wed, 04 Mar 2015 12:12:57 +0100
+
samba (2:4.1.17+dfsg-1) unstable; urgency=high
* New upstream release. Fixes:
diff --git a/debian/samba.preinst b/debian/samba.preinst
new file mode 100644
index 000..ae8cfaa
--- /dev/null
+++ b/debian/samba.preinst
@@ -0,0 +1,18 @@
+#!/bin/sh
+set -e
+
+# Deactivate the old qtsmbstatusd initscript that has dependencies
+# incompatible with the new samba initscript. This will allow to
+# configure the new samba package and qtsmbstatus-server afterwards.
+if [ $1 = upgrade ] || [ $1 = install ]; then
+ if [ -x /etc/init.d/qtsmbstatusd ]; then
+ version=$(dpkg-query -f '${Config-Version} ${Version}' -W qtsmbstatus-server 2/dev/null | awk '{ print $1 }')
+ if dpkg --compare-versions $version lt-nl 2.2.1-3~ ; then
+ echo Deactivating qtsmbstatusd temporarily...
+ invoke-rc.d qtsmbstatusd stop
+ update-rc.d -f qtsmbstatusd remove
+ fi
+ fi
+fi
+
+#DEBHELPER#
--
2.1.4
Processed: severity of 770767 is serious
Processing commands for cont...@bugs.debian.org:
severity 770767 serious
Bug #770767 [cdbs] cdbs: perl-build-vars.mk overrides $Config{ccflags}
Severity set to 'serious' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
770767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770767
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#779727: Source package contains oracle-java8-jdk_8_amd64.deb
Source: java-package Version: 0.57 Severity: serious Looks like oracle-java8-jdk_8_amd64.deb was accidentally included in the source package upload. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (550, 'stable-updates'), (550, 'stable'), (530, 'testing'), (520, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16.0-0.bpo.4-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- 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
Bug#779727: Source package contains oracle-java8-jdk_8_amd64.deb
Le 04/03/2015 15:04, Sam Morris a écrit : Looks like oracle-java8-jdk_8_amd64.deb was accidentally included in the source package upload. Doh! Thank you for the report Sam, I'm going to fix this. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 772429 is serious
Processing commands for cont...@bugs.debian.org: severity 772429 serious Bug #772429 [cdbs] cdbs: Does not support case-insensitve field names Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 772429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772429 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
