Processed: retitle 766920 to produces unbootable initramfs with lilo hexadecimal syntax (root=803)
Processing commands for cont...@bugs.debian.org: retitle 766920 produces unbootable initramfs with lilo hexadecimal syntax (root=803) Bug #766920 [initramfs-tools] initramfs-tools: update-initramfs makes system unbootable due to missing rootfs Changed Bug title to 'produces unbootable initramfs with lilo hexadecimal syntax (root=803)' from 'initramfs-tools: update-initramfs makes system unbootable due to missing rootfs' thanks Stopping processing here. Please contact me if you need assistance. -- 766920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766920 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#771163: libreoffice: CVE-2014-9093
Package: libreoffice Severity: grave Tags: security Justification: user security hole Hi, please see https://bugs.freedesktop.org/show_bug.cgi?id=86449 for the bug report with a reproducer (which also crashes the version in wheezy). 4.3 fix by Caolan: http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-4-3id=b4840d3632e4404bee4bd192a7db916cbad3a401 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#770918: Two CVEs against FLAC
Am Mittwoch, den 26.11.2014, 19:58 -0800 schrieb Erik de Castro Lopo: One more patch to cherry pick: Thank you very much! I hope to be able to prepare updated packages by next week. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: please confirm the version of ruby-i18n
Processing control commands: tags -1 + moreinfo Bug #770194 [src:ruby-stringex] ruby-stringex: FTBFS: Test failures Added tag(s) moreinfo. -- 770194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770194 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#770194: please confirm the version of ruby-i18n
Control: tags -1 + moreinfo Hi, This bug looks very much like #765124 [1], which is triggered by a version of ruby-i18n not compatible with the version of ruby-stringex in Jessie. Could you please ensure that you can reproduce the bug with ruby-i18n set to version 0.6.9-2? 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765124 If the bug is not reproducible with the version of ruby-i18n in Jessie, then I'll probably add a version 0.6.11~ for ruby-i18n in the dependency line of ruby-stringex. Best wishes, Cédric signature.asc Description: Digital signature
Bug#769947: mate-terminal: Segfaults after update
Control: reopen -1 Control: tag -1 patch On Mi 26 Nov 2014 11:17:57 CET, Mike Gabriel wrote: Control: close -1 Hi Alex, hi Ben, On Di 25 Nov 2014 20:40:03 CET, Alex Corcoles wrote: More or less, doing some trial and error I discovered that using desktopConfig instead of defaultConfig fixes magically the problem. https://github.com/alexpdp7/xmonad.pdp7/commit/037a44a8f7541fb3983ade528e34b4cfa0ea81a5 . I suppose there's some bug somewhere, but I'm happy for now- don't know if Ben Whyall has the same problem or not. ok. Thanks for feedback. Closing this bug as it is probably not (only) related to mate-terminal. Mike Re-opening... It seems we have an upstream patch [1] (currently still a pull request) for this segfault behaviour. @Alex: do you think you could build mate-terminal from source with the referenced patch included and confirm that the patch fixes your issues? Mike [1] https://github.com/mar-kolya/mate-terminal/commit/bb659a752efbeedbe60fb6df5541a57c95777279 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp68m8Z0JEIe.pgp Description: Digitale PGP-Signatur
Processed: Re: Bug#769947: mate-terminal: Segfaults after update
Processing control commands:
reopen -1
Bug #769947 {Done: Mike Gabriel mike.gabr...@das-netzwerkteam.de}
[mate-terminal] mate-terminal: Segfaults after update
Bug reopened
Ignoring request to alter fixed versions of bug #769947 to the same values
previously set
tag -1 patch
Bug #769947 [mate-terminal] mate-terminal: Segfaults after update
Added tag(s) patch.
--
769947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769947
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#770194: please confirm the version of ruby-i18n
On Thu, 27 Nov 2014 10:37:09 +0100, Cédric Boutillier wrote: This bug looks very much like #765124 [1], which is triggered by a version of ruby-i18n not compatible with the version of ruby-stringex in Jessie. Could you please ensure that you can reproduce the bug with ruby-i18n set to version 0.6.9-2? I tried to build the package in an up2date cowbuilder sid amd64 chroot, so I got whatever was in sid yesterday :) 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765124 If the bug is not reproducible with the version of ruby-i18n in Jessie, then I'll probably add a version 0.6.11~ for ruby-i18n in the dependency line of ruby-stringex. I can try with a jessie chroot later today. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #157: Incorrect time synchronization -- 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 771125 is grave
Processing commands for cont...@bugs.debian.org: # bumping severity (at least for now) as causing denial of service condition and potentially code execution (can this be ruled out in this case already?) severity 771125 grave Bug #771125 [mutt] mutt: CVE-2014-9116: buffer overflow Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 771125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771125 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: jessie
Processing commands for cont...@bugs.debian.org: tags 771092 + sid jessie Bug #771092 [libuuid1] insighttoolkit: Build failure on sparc Added tag(s) sid and jessie. End of message, stopping processing here. Please contact me if you need assistance. -- 771092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771092 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#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot
On Sun, 02 Nov 2014 at 22:21:16 +0100, zer0 divide wrote: I chose during installation luks partitioning (not lvm), and separated /boot (on an usb pendrive) partition from /root partition (on another drive with the other one). That isn't a full description of what you did; I can tell because you mention a separate /usr, /var, /home later. Please attach your /etc/fstab and /etc/crypttab. You can censor them if necessary, but please make it obvious where you have done so. The output of reportbug --template initramfs-tools would also be useful. My system does not start automatically after I enter the password for unlocking the root partition. I have to unlock manually /usr (from initramfs ), and then do CTRL + D. The regression here is that initramfs-tools/0.118 mounts /usr in the initramfs, whereas initramfs-tools/0.116 does not; and cryptsetup's initramfs hook has not been updated to provide the necessary devices for /usr as well as the root. I'm testing a potential solution: making cryptsetup open /usr, not just /, during the initramfs. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
control: tags -1 + wheezy-ignore control: retitle -1 libav/lena.pnm: non-DFSG free + not mentioned in copyright first of all, the file in question is libav-11/tests/lena.pnm second, as referred in the mail referred to by the original bugreport, please read https://en.wikipedia.org/wiki/File:Lenna.png#Licensing According to that and also to https://en.wikipedia.org/wiki/Wikipedia:Files_for_deletion/2011_November_4#File:Lenna.png it seems to me that this file is distributable under fair use policy, especially since it's a low-res thumbnail as well. (the wikipedia low-res image is 512x512, the image in libav is 256x245). Yet while it's distributable, it's also clearly not DFSG free and btw it's also not mentioned in debian/copyright at all. So for sid+jessie I recommend to drop this file. Also not least because Suggestive pictures used in lectures on image processing ... convey the message that the lecturer caters to the males only. For example, it is amazing that the Lena pin-up image is still used as an example in courses and published as a test image in journals today. as explained in https://en.wikipedia.org/wiki/Lenna (btw, regarding usage in test cases: I have to admit I don't understand how/if usage of this file as a test case is relevant in the Debian context. Explainations welcome...) signature.asc Description: This is a digitally signed message part.
Processed: libav/tests/lena.pnm: also not mentioned in debian/copyright
Processing control commands: tags -1 + wheezy-ignore Bug #771126 [src:libav] libav: contains non-DFSG image file tests/lena.pnm Added tag(s) wheezy-ignore. retitle -1 libav/lena.pnm: non-DFSG free + not mentioned in copyright Bug #771126 [src:libav] libav: contains non-DFSG image file tests/lena.pnm Changed Bug title to 'libav/lena.pnm: non-DFSG free + not mentioned in copyright' from 'libav: contains non-DFSG image file tests/lena.pnm' -- 771126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771126 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#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot
On Thu, 27 Nov 2014 at 10:02:34 +, Simon McVittie wrote: On Sun, 02 Nov 2014 at 22:21:16 +0100, zer0 divide wrote: My system does not start automatically after I enter the password for unlocking the root partition. I have to unlock manually /usr (from initramfs ), and then do CTRL + D. Steps to reproduce what I think is the same bug: Install jessie on a virtual machine in this arrangement: /dev/vda1: ext4 /boot, 200M /dev/vda2: LUKS encrypted (volume named vda2_crypt), 1.5G containing ext4 / (root filesystem), 1.5G /dev/vda3: LUKS encrypted (volume named vda3_crypt), 1.5G containing ext4 /usr, 1.5G Reboot from the installer into the real system. The root filesystem is decrypted and mounted by the initramfs; the /usr filesystem is decrypted and mounted after systemd starts, with a visibly different passphrase prompt. Upgrade to current jessie and reboot. The same things happen. Upgrade initramfs-tools (only) to the version from sid, 0.118, and reboot. The initramfs unlocks and fscks vda2_crypt, then after a delay: Gave up waiting for /usr device. Common problems: ... ALERT! /dev/mapper/vda3_crypt does not exist. Dropping to a shell! ... (initramfs) To recover: type at the initramfs prompt cryptsetup luksOpen /dev/vda3 vda3_crypt exit and the system boots. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771169: curl: relocation error, missing symbol
Package: curl Version: 7.38.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, curl won't start curl: relocation error: /usr/lib/x86_64-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference Best -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.2d (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages curl depends on: ii libc6 2.19-13 ii libcurl3 7.38.0-3 ii zlib1g1:1.2.8.dfsg-2 curl recommends no packages. curl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot
Processing control commands: retitle 767832 cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 Bug #767832 [initramfs-tools] Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot Changed Bug title to 'cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118' from 'Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot' reassign 767832 cryptsetup Bug #767832 [initramfs-tools] cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 Bug reassigned from package 'initramfs-tools' to 'cryptsetup'. Ignoring request to alter found versions of bug #767832 to the same values previously set Ignoring request to alter fixed versions of bug #767832 to the same values previously set found 767832 cryptsetup/2:1.6.6-3 Bug #767832 [cryptsetup] cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 Marked as found in versions cryptsetup/2:1.6.6-3. affects 767832 initramfs-tools Bug #767832 [cryptsetup] cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 Added indication that 767832 affects initramfs-tools tags 767832 + patch Bug #767832 [cryptsetup] cryptsetup: does not decrypt a split /usr as required by initramfs-tools = 0.118 Added tag(s) patch. -- 767832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767832 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#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot
Control: retitle 767832 cryptsetup: does not decrypt a split /usr as required
by initramfs-tools = 0.118
Control: reassign 767832 cryptsetup
Control: found 767832 cryptsetup/2:1.6.6-3
Control: affects 767832 initramfs-tools
Control: tags 767832 + patch
I think this is a cryptsetup bug. The attached patch solves my test-case
in a virtual machine.
Regards,
S
diffstat for cryptsetup-1.6.6 cryptsetup-1.6.6
changelog|8
initramfs/cryptroot-hook | 11 +++
2 files changed, 15 insertions(+), 4 deletions(-)
diff -Nru cryptsetup-1.6.6/debian/changelog cryptsetup-1.6.6/debian/changelog
--- cryptsetup-1.6.6/debian/changelog 2014-10-22 18:28:59.0 +0100
+++ cryptsetup-1.6.6/debian/changelog 2014-11-27 10:13:13.0 +
@@ -1,3 +1,11 @@
+cryptsetup (2:1.6.6-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/initramfs/cryptroot-script: decrypt /usr as well as / so that
+split-/usr will work with initramfs-tools (= 0.118). (closes: #767832)
+
+ -- Simon McVittie s...@debian.org Thu, 27 Nov 2014 10:12:15 +
+
cryptsetup (2:1.6.6-3) unstable; urgency=medium
* debian/initramfs/cryptroot-script: fix environment variable $CRYPTTAB_TRIED
diff -Nru cryptsetup-1.6.6/debian/initramfs/cryptroot-hook cryptsetup-1.6.6/debian/initramfs/cryptroot-hook
--- cryptsetup-1.6.6/debian/initramfs/cryptroot-hook 2014-10-02 12:20:55.0 +0100
+++ cryptsetup-1.6.6/debian/initramfs/cryptroot-hook 2014-11-27 10:27:45.0 +
@@ -16,8 +16,9 @@
. /usr/share/initramfs-tools/hook-functions
-get_root_devices() {
+get_fs_devices() {
local device mount type options dump pass
+ local wantmount=$1
if [ ! -r /etc/fstab ]; then
return 1
@@ -25,7 +26,7 @@
grep -s '^[^#]' /etc/fstab | \
while read device mount type options dump pass; do
- if [ $mount = / ]; then
+ if [ $mount = $wantmount ]; then
local devices
if [ $type = btrfs ]; then
for dev in $(btrfs filesystem show $(canonical_device $device --no-simplify) 2/dev/null | sed -r -e 's/.*devid .+ path (.+)/\1/;tx;d;:x') ; do
@@ -611,6 +612,7 @@
setup=no
rootdevs=
+usrdevs=
resumedevs=
# Include cryptsetup modules, regardless of _this_ machine
@@ -621,16 +623,17 @@
# Find the root and resume device(s)
if [ -r /etc/crypttab ]; then
- rootdevs=$(get_root_devices)
+ rootdevs=$(get_fs_devices /)
if [ -z $rootdevs ]; then
echo cryptsetup: WARNING: could not determine root device from /etc/fstab 2
fi
+ usrdevs=$(get_fs_devices /usr)
resumedevs=$(get_resume_devices)
initramfsdevs=$(get_initramfs_devices)
fi
# Load the config opts and modules for each device
-for dev in $rootdevs $resumedevs $initramfsdevs; do
+for dev in $rootdevs $usrdevs $resumedevs $initramfsdevs; do
if ! modules=$(add_device $dev); then
echo cryptsetup: FAILURE: could not determine configuration for $dev 2
continue
Bug#771163: libreoffice: CVE-2014-9093
close 771163 1:4.4.0~beta1-1 # see https://bugs.freedesktop.org/show_bug.cgi?id=86449#c4 thanks Hi, On Thu, Nov 27, 2014 at 10:18:46AM +0100, Moritz Muehlenhoff wrote: Package: libreoffice Severity: grave Tags: security Justification: user security hole sigh. See #770166 Hi, please see https://bugs.freedesktop.org/show_bug.cgi?id=86449 for the bug report with a reproducer (which also crashes the version in wheezy). 4.3 fix by Caolan: http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-4-3id=b4840d3632e4404bee4bd192a7db916cbad3a401 *shugs*, if you indeed think that this warrants a DSA, let's do it... Expect uploads tomorrow. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 769864 with 770670
Processing commands for cont...@bugs.debian.org: block 769864 with 770670 Bug #769864 [vcmi] vcmi: FTBFS on armhf, hurd-any, kfreebsd-any, mipsel and ppc64el 769864 was not blocked by any bugs. 769864 was not blocking any bugs. Added blocking bug(s) of 769864: 770670 thanks Stopping processing here. Please contact me if you need assistance. -- 769864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769864 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#771163: libreoffice: CVE-2014-9093
Processing commands for cont...@bugs.debian.org: close 771163 1:4.4.0~beta1-1 # see https://bugs.freedesktop.org/show_bug.cgi?id=86449#c4 Bug #771163 [libreoffice] libreoffice: CVE-2014-9093 The source 1:4.4.0~beta1-1 # see https://bugs.freedesktop.org and version show_bug.cgi?id=86449#c4 do not appear to match any binary packages Marked as fixed in versions 1:4.4.0~beta1-1 # see https://bugs.freedesktop.org/show_bug.cgi?id=86449#c4. Bug #771163 [libreoffice] libreoffice: CVE-2014-9093 Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 771163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771163 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#767589: systemd: cryptdisks other than root/swap fail cryptsetup
On Sat, 01 Nov 2014 at 11:50:40 +0100, Arnaud Installe wrote: After successfully unlocking and mounting root and swap devices, the system hangs a while, then drops to a rescue shell, with /usr, /var and /home not unlocked by cryptsetup. After manually running cryptsetup for the underlying devices, and exiting the rescue shell, boot proceeds normally. I think this may be the same thing as https://bugs.debian.org/767832. Am I right in saying that your system looks like this? /dev/sda (or whatever) \- /dev/sda1 (or whatever): /boot \- /dev/sda2 (or whatever): LVM PV for VG boulez \- boulez/root LV: encrypted, boulez-_root__crypt \- / (rootfs) \- boulez/swap LV: encrypted, boulez-_swap__crypt \- swap \- boulez/home LV: encrypted, boulez-_home__crypt \- /home \- boulez/usr LV: encrypted, boulez-_usr__crypt \- /usr \- boulez/var LV: encrypted, boulez-_var__crypt \- /var With initramfs-tools 0.117, the intended result for a system like this is that the initramfs decrypts the root filesystem and swap, mounts the root filesystem, and hands over to the real system (systemd as pid 1). The real system is meant to decrypt and mount /home, /usr and /var. With initramfs-tools = 0.117, the intended result for a system like this is that the initramfs also decrypts and mounts /usr. However, cryptsetup does not currently decrypt /usr. It should be unnecessary to decrypt /home or /var in the initramfs in either case. It would be great if you could try rebuilding the initramfs after installing a version of cryptsetup with the patch from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767832#22 applied. I believe that should fix your situation too, but so far I have only tested LUKS on partitions, not LUKS on LVM. S -- 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#771169: curl: relocation error, missing symbol
Processing control commands: reassign -1 openssl Bug #771169 [curl] curl: relocation error, missing symbol Bug reassigned from package 'curl' to 'openssl'. No longer marked as found in versions curl/7.38.0-3. Ignoring request to alter fixed versions of bug #771169 to the same values previously set forcemerge 768476 -1 Bug #768476 [openssl] openssl 1.0.2~beta3-1: relocation error in libraries depending on libssl.so Bug #768522 [openssl] libcurl3 (version 7.38.0-3) relocation error Bug #770278 [openssl] curl: Problems with SSL symbol Bug #771169 [openssl] curl: relocation error, missing symbol Added indication that 771169 affects libcurl3 Marked as found in versions openssl/1.0.2~beta3-1. Bug #768522 [openssl] libcurl3 (version 7.38.0-3) relocation error Bug #770278 [openssl] curl: Problems with SSL symbol Merged 768476 768522 770278 771169 -- 768476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768476 768522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768522 770278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770278 771169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771169 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: bug 771163 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=86449
Processing commands for cont...@bugs.debian.org:
forwarded 771163 https://bugs.freedesktop.org/show_bug.cgi?id=86449
Bug #771163 {Done: Rene Engelhard r...@debian.org} [libreoffice] libreoffice:
CVE-2014-9093
Set Bug forwarded-to-address to
'https://bugs.freedesktop.org/show_bug.cgi?id=86449'.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
771163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771163
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#771169: curl: relocation error, missing symbol
Control: reassign -1 openssl Control: forcemerge 768476 -1 On gio, nov 27, 2014 at 11:34:30 +0100, Salvo Tomaselli wrote: Package: curl Version: 7.38.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, curl won't start curl: relocation error: /usr/lib/x86_64-linux-gnu/libcurl.so.4: symbol SSLv3_client_method, version OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference No a curl bug, please install libssl1.0.0 from unstable. Cheers signature.asc Description: Digital signature
Processed: found 771163 in 1:4.3.3-1
Processing commands for cont...@bugs.debian.org:
found 771163 1:4.3.3-1
Bug #771163 {Done: Rene Engelhard r...@debian.org} [libreoffice] libreoffice:
CVE-2014-9093
Marked as found in versions libreoffice/1:4.3.3-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
771163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771163
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: found 771163 in 1:3.5.4+dfsg2-0+deb7u2
Processing commands for cont...@bugs.debian.org:
found 771163 1:3.5.4+dfsg2-0+deb7u2
Bug #771163 {Done: Rene Engelhard r...@debian.org} [libreoffice] libreoffice:
CVE-2014-9093
Marked as found in versions libreoffice/1:3.5.4+dfsg2-0+deb7u2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
771163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771163
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#771172: systemd-sysv-generator does not generate
Package: systemd Version: 215-6 Severity: critical Justification: breaks unrelated software Dear Maintainer, I am not providing the additional information that reportbug wants to provide because if I do, the mail will be rejected as spam by bogus filters. Dear Maintainer, somehow, after the last upgrade (which included dbus, console-setup, libpolkit-backend, schroot) I was unable to start postfix. While upgrading I had this message: insserv: FATAL: service dnsmasq is missed in the runlevels 2 3 4 5 to use service postfix that caused the entire upgrade to fail. I didn't know what was the problem, the LSB headers seemed fine, so I removed /etc/init.d/postfix and /etc/init.d/dnsmasq and proceeded with the upgrade. After the upgrade I put the scripts in their original position. Then, I noticed that postfix was not running and could not be started ● postfix.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) which is when I learnt about the existance of systemd-sysv-generator (which lacks a man page and doesn't support a -h switch) After some investigation I found out that these generated files belong in /run/systemd/generator.late/, for systemd to be able to run the service. There was no such file there for postfix, so I ran the tool, which generated files in /tmp, and then moved the postfix.service inside the correct location, to be able to start it. I have no clue of what happened with insserv and why it was failing in the first place, and I guess that systemd refusing to start my service was due to my removing and then adding the script. However, I might want to copy a script in /etc/init.d at anytime and I would expect systemd to be able to run it, without first having to run some undocumented tool. Please let me know if you need more information about the problem. Best -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.2d (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b1 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-6 ii mount 2.25.2-3 ii sysv-rc 2.88dsf-58 ii udev215-6 ii util-linux 2.25.2-3 Versions of packages systemd recommends: ii dbus1.8.12-1 ii libpam-systemd 215-6 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- 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#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Quoting Holger Levsen (2014-11-27 11:25:05) control: tags -1 + wheezy-ignore Are you part of the release team? first of all, the file in question is libav-11/tests/lena.pnm No, path (inside the source) is tests/lena.pnm. second, as referred in the mail referred to by the original bugreport, please read https://en.wikipedia.org/wiki/File:Lenna.png#Licensing Why read it again (sure you do not imply that I didn't read already)? [irrelevant details snipped] Yet while it's distributable, it's also clearly not DFSG free So your conclusion is same as mine. Why did you retitle? What was the purpose of your mail? Seems the only actual sensible action was ignoring for the next release. Please elaborate on your reasoning for that. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: libuuid1: add found version
Processing commands for cont...@bugs.debian.org: found 771092 2.25.1-1 Bug #771092 [libuuid1] insighttoolkit: Build failure on sparc Marked as found in versions util-linux/2.25.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 771092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771092 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#771177: develock-el: breaks c++ mode in sid and jessie
Package: develock-el
Version: 0.39-1
Severity: grave
Justification: renders package unusable
This package completely breaks the standard emacs c++ mode.
To reproduce: open the attached .cpp file and try to indent the
second line using tab.
This was fixed upstream and updating the package to 0.45 fixes
this problem.
I suggest doing this as soon as possible so that a freeze
exception can be requested for jessie. I'm happy to do an
NMU for it if you don't have time. Let me know if you need
my help.
Francois
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages develock-el depends on:
ii emacs 46.1
ii emacs24 [emacsen] 24.4+1-4
develock-el recommends no packages.
develock-el suggests no packages.
-- no debconf information
int main() {
return 0;
}
Bug#768751: ecb: FTBFS in jessie
Control: tags -1 help 2014-11-11 21:05 GMT+01:00 Bálint Réczey bal...@balintreczey.hu: Control: tags -1 confirmed Hi Lucas, 2014-11-09 8:31 GMT+01:00 Lucas Nussbaum lu...@lucas-nussbaum.net: Source: ecb Version: 2.40+git20140216-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory '/ĢBUILDDIRģ/ecb-2.40+git20140216' Makefile:38: Makefile.conf not found. Using defaults for Linux! Makefile:39: Create Makefile.conf from Makefile.conf.template to override the defaults. Byte-compiling ECB with LOADPATH= ... emacs -batch -no-site-file -l ecb-compile-script --eval '(ecb-byte-compile t)' ECB 2.40 uses CEDET 2.0 (contains semantic 2.2, eieio 1.4, speedbar 1.0). All requirements for ECB 2.40 fulfilled - Enjoy it! ... Wrote /ĢBUILDDIRģ/ecb-2.40+git20140216/ecb-winman-support.elc Wrote /ĢBUILDDIRģ/ecb-2.40+git20140216/ecb.elc Wrote /ĢBUILDDIRģ/ecb-2.40+git20140216/silentcomp.elc Wrote /ĢBUILDDIRģ/ecb-2.40+git20140216/tree-buffer.elc Args out of range: 0 make[2]: *** [ecb] Error 255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/ecb_2.40+git20140216-1_jessie.log It seems the latest emacs24 upload introduced some Elisp changes breaking ECB. I will try to fix it for the release, but if someone is more familiar with the changes then feel free to check the regression. Cheers, Balint I'm not sure if I can debug and fix this by 5 Dec, when the package is scheduled for removal from testing. If you are familiar with elisp please take a look. Thanks, Balint -- 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#768751: ecb: FTBFS in jessie
Processing control commands: tags -1 help Bug #768751 [src:ecb] ecb: FTBFS in jessie Added tag(s) help. -- 768751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768751 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#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Quoting Jonas Smedegaard (2014-11-27 12:15:13) Quoting Holger Levsen (2014-11-27 11:25:05) control: tags -1 + wheezy-ignore [...] Why did you retitle? What was the purpose of your mail? Seems the only actual sensible action was ignoring for the next release. Please elaborate on your reasoning for that. Correction: current stable release. Questions still stand: Why? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#770976: marked as done (X2Go desktop sharing broken)
Your message dated Thu, 27 Nov 2014 11:34:12 + with message-id e1xtxku-0008i8...@franck.debian.org and subject line Bug#770976: fixed in python-x2go 0.5.0.1-2 has caused the Debian Bug report #770976, regarding X2Go desktop sharing broken 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.) -- 770976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-x2go Version: 0.5.0.1-1 Severity: grave X2Go desktop sharing is broken in Python X2Go 0.5.0.1 upstream. A fix is available upstream, as well [1]. Mike [1] http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=d5472a9ce4bbffd5c32248135452796ea4f9d0c1 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de ---End Message--- ---BeginMessage--- Source: python-x2go Source-Version: 0.5.0.1-2 We believe that the bug you reported is fixed in the latest version of python-x2go, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel sunwea...@debian.org (supplier of updated python-x2go 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: Thu, 27 Nov 2014 12:18:47 +0100 Source: python-x2go Binary: python-x2go python-x2go-doc Architecture: source all Version: 0.5.0.1-2 Distribution: unstable Urgency: medium Maintainer: X2Go Packaging Team pkg-x2go-de...@lists.alioth.debian.org Changed-By: Mike Gabriel sunwea...@debian.org Description: python-x2go - Python module providing X2Go client API python-x2go-doc - Python module providing X2Go client API (documentation) Closes: 770976 Changes: python-x2go (0.5.0.1-2) unstable; urgency=medium . * debian/patches: + Add 0001_catch-connection-exception-during-session-startup.patch. Catch exceptions raised by connection failures during session startup/resumption. + Add 0002_fix-desktop-sharing.patch. Fix (cross-)user desktop sharing. (Closes: #770976). Checksums-Sha1: 0e487de1d7e9ffb6f33c65731bf7e9f5856f26c2 2131 python-x2go_0.5.0.1-2.dsc b472d1d5532971cc5dd3b57373128b4c209a1878 317104 python-x2go_0.5.0.1-2.debian.tar.xz f5f49729155f75b9ecd3e6488c4a56f0d7773f49 154710 python-x2go_0.5.0.1-2_all.deb 4677886cfba7f4d521f1bc2da986370f7cf3fa93 493050 python-x2go-doc_0.5.0.1-2_all.deb Checksums-Sha256: d11da9f315060c3674dd3ade6cb8187439814a3b9842ae2791a72d1d5a31a5d8 2131 python-x2go_0.5.0.1-2.dsc c0f9921bbf133e4b926db43e201f9d39f8971857703a1847e3ef281b7153 317104 python-x2go_0.5.0.1-2.debian.tar.xz 478244118ebe4605cda1848078d179cd52ed3970d2bcebfcbb6143ba2984a9e9 154710 python-x2go_0.5.0.1-2_all.deb e002dd68fd35f6b350b1158f847a19829c6a75ad5a5862f0e2a93c22f8489cc1 493050 python-x2go-doc_0.5.0.1-2_all.deb Files: 83de2db43db03f29533a900517fdab2c 2131 python optional python-x2go_0.5.0.1-2.dsc d01b15302aef810a1d1be6308e50f6ff 317104 python optional python-x2go_0.5.0.1-2.debian.tar.xz 0422e8059c9539aa9fbc5dabdf91059b 154710 python optional python-x2go_0.5.0.1-2_all.deb 62c023c57fab4c035eef295cbe1c0362 493050 doc optional python-x2go-doc_0.5.0.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUdwnSAAoJEJr0azAldxsx/1wP/32cZQh7jahrz3TkWfwA7CSk H/X9c1N7Lib64wSjSTJt1KimVUGbFiqXslhxl7Ud7Fx884cpS6BA5V3Uw4/5Zq7O lU/7C92gxtUOCrPN1IljZvL1S0isF6yURPy7ylh2plXSh318MgfbqozdudGho2MK qPs3B1VBrJWGp6l1YObEEBUCDEcpGOfOOzeX3bLi4eKhzR8NL1BsEfW4uSJKkkmC +LsBlixKKicxLmS3rzWmNZYVkZtWafbWqjcDiRQx9yI2Cmo5tcEMbLXpLiMo4du3 p+B4VhkCWKk4+/rTRHMNu3pxephFmrZLMI5byN32Ud/582dqbRXNepipEoE8vGCj 68FKDPxyYlUG0LXGP3JSNCbMynLTHLuluSYADA/cc0hVulfX5sldcaFeUSjpcsc0 lIVvEOQTq3C6wMpcimlR114zPzEDp5PWfTwSuLwW3FtYB/ReGOmPpzKN3H61uCL+ pdF9bLU9XC2MXJzFtWG3ybTjKjugP+pKh1NN7I67Tycy7qZPtb3H/WnPhkTJMcRl nAsfMabMPF+jzyz5Jy8H+tZEerxnUPY/wKyGujSEI4aOvW7i6JAitAvuv9KYINZE QgbGl+RjtpbPm0cq6HHY5SdWxwESqiB7KQKH/T/cmi9bxZEqxs0snF/VYjiK7zZ7 q3orNZHxwqfv2/SYNfcN =l3H+ -END PGP SIGNATUREEnd Message---
Bug#771092: libuuid1: moreinfo
Control: tags 771092 + moreinfo Just adding the passwd dependency would hide the real problem here. Someone needs to look into why the migration code is being run again and again (as it apparently does on a sparc buildd atleast)! This code is going to be dropped in Jessie+1 where it's expected that everyone has migrated. If there are cases where migration isn't working we need to fix those now. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: libuuid1: moreinfo
Processing control commands: tags 771092 + moreinfo Bug #771092 [libuuid1] insighttoolkit: Build failure on sparc Added tag(s) moreinfo. -- 771092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771092 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#770425: Possibility of update to 4.x
On Wed, Nov 26, 2014 at 11:45:29PM +, Nick Phillips wrote: Issues: * New package splits out the themes into separate packages. * New package no longer links /usr/share/wordpress/wp-config.php to /etc/wordpress/wp-config.php - customisations there will be ignored until admin intervenes. Both of these issues could fairly easily be reverted to old behaviour, I think. It's tricky because on the one hand I can back-port the patches (hopefully) to the version in stable. Alternatively I can push 4.0.1 down to stable and try to fix up the difference such as dependencies. Stable security fixes should have the minimal set of changes, but at what point does it become better to abandon that ideal? - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762984: Alert! /dev/vg0/usr does not exist
On Wed, 01 Oct 2014 at 22:18:53 +0100, Ben Hutchings wrote: I suspect this is essentially the same bug as #616689 and #678696, except that now it may affect mounting /usr as well as /. I think this bug report is actually describing more than one bug in more than one package that have similar symptoms. There might be things that can be fixed in mdadm and lvm2 to fix the initramfs-tools/0.117 regressions without needing to implement a full event-driven setup in initramfs-tools. RAID (Elimar, Sven) Elimar Riesebieter's System 2 has a bunch of mdadm (RAID) partitions. Elimar, what is in your /etc/default/mdadm on System 2 (and System 1 for that matter)? I predict that the answer includes something like INITRDSTART=/dev/md6. The problem here seems to be that mdadm tries to determine a minimal set of multi-disk partitions need to be assembled by the initramfs based on the assumption that the initramfs only needs the root device; but initramfs-tools = 0.117 wants to mount /usr as well, so that assumption is no longer true. So it might be necessary to modify mdadm so that, if /usr is a separate filesystem on (a LVM VG on) a MD array, it will try to prepare that too. LVM (Elimar's System 1, Sven, Torsten, IOhannes, Javier) In the LVM case, debian/initramfs-tools/lvm2/scripts/local-top does this: activate_vg $ROOT activate_vg $resume Note the lack of handling for /usr here. Further, activate_vg uses lvm lvchange to activate only the LV necessary for the root filesystem; if /usr is on a separate VG, it's not going to work. This on its own would be enough to make Sven Hartge's system fail: /usr needs a LVM partition activated that / does not. Similarly, I think Elimar's System 1 is going to activate vg0/root but not vg0/usr. We don't have enough information in this bug report to know what layout Torsten, IOhannes, Javier used on their systems, but we can guess from the fact that vgchange -a y is a successful workaround... I predict that these are LVM over either a single RAID array, or real partitions. The ideal thing in both of these situations would be to use the same logic as *mounting* /usr - mount the rootfs first, then read its fstab to find out where /usr is, avoiding hard-coding that knowledge into the initramfs - but I think that would need a significantly more complicated hook structure. Perhaps modifying mdadm and lvm2 so they will set up enough md/lvm bits for /usr in the initramfs would be sufficient for a 95% solution? S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
On Donnerstag, 27. November 2014, Jonas Smedegaard wrote: control: tags -1 + wheezy-ignore Are you part of the release team? No, but the release team is explicitly happy with *me* tagging stuff wheezy- ignore following guidelines discussed on debian-release. the conclusion there has been: (in stable) distributable stuff which is non- free or wrongly mentioned in debian/copyrights are serious bugs - but serious bugs which *can* be ignored. (and yeah, usually I cc: debian-release@l.d.o explicitly on such taggings, because it's the proper thing to do. as I also know that most if not all of the release team are subscribed to all RC bugs anyway, I sometimes forget this...) first of all, the file in question is libav-11/tests/lena.pnm No, path (inside the source) is tests/lena.pnm. you're so right, amazing! Questions still stand: Why? to save people from useless^w work. signature.asc Description: This is a digitally signed message part.
Bug#771125: CVE request: mutt: heap-based buffer overflow in mutt_substrdup()
On Thu, Nov 27, 2014 at 02:49:27PM +1100, Murray McAllister wrote: Good morning, Jakub Wilk reported a crash in mutt: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771125 Looking in mutt-1.5.23-2.fc20.x86_64: [...] I'll have a patch/solution ready for this by tonight; thanks for reporting it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768615: #768615: ruby-pygments.rb: FTBFS in jessie: ERROR: Test ruby2.1 failed
On 24/11/14 14:21, Christian Hofstaedtler wrote: Tobias, Tomasz, Thank you for working on this. Feel free to reschedule the NMU to an earlier date (e.g. immediate). Best, -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- Hi Christian, I think I made a mistake in this NMU, the changelog uploads it to unstable, but I think it should be testing instead (on the other hand you may unblock transition unstable = testing if I'm correct). Cheers, Tomasz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768690: latex-mk: FTBFS in jessie: build-dependency not installable: tgif
On 22/11/14 20:28, Tobias Frost wrote:
Control: tags -1 pending
Uploaded to DELAYED/5
Thanks Thomasz!
--
tobi
I think that my NMU is wrong since it uploads into unstable, but
it should be testing instead. Sorry for trouble, I attach a
modified NMU.
Tomasz
diff -Nru latex-mk-2.1/debian/changelog latex-mk-2.1/debian/changelog
--- latex-mk-2.1/debian/changelog 2014-04-25 16:45:24.0 +0200
+++ latex-mk-2.1/debian/changelog 2014-11-22 18:15:40.0 +0100
@@ -1,3 +1,10 @@
+latex-mk (2.1-1.3) testing; urgency=medium
+
+ * Non-maintainer upload.
+ * Disable support and dependency on tgif (Closes: #768690)
+
+ -- Tomasz Buchert tomasz.buch...@inria.fr Sat, 22 Nov 2014 18:14:45 +0100
+
latex-mk (2.1-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru latex-mk-2.1/debian/control latex-mk-2.1/debian/control
--- latex-mk-2.1/debian/control 2014-04-25 16:44:02.0 +0200
+++ latex-mk-2.1/debian/control 2014-11-22 18:14:34.0 +0100
@@ -6,7 +6,7 @@
Build-Depends-Indep: texlive-base, texlive-latex-base, texlive-latex-extra,
texlive-latex-recommended, texlive-fonts-recommended, texinfo, xsltproc,
docbook-xsl, graphicsmagick-imagemagick-compat, gv, hevea, latex2rtf, cups-bsd,
- ghostscript, tgif, transfig, csh, autoconf
+ ghostscript, transfig, csh, autoconf
Standards-Version: 3.9.2
Homepage: http://latex-mk.sourceforge.net/
@@ -15,7 +15,7 @@
Depends: ${misc:Depends}
Recommends: make, texlive-latex-recommended, texlive-base
Suggests: graphicsmagick-imagemagick-compat, gv, hevea, latex2rtf, cups-bsd,
- ghostscript, tgif, transfig
+ ghostscript, transfig
Description: tool for managing LaTeX projects
LaTeX-Mk is a collection of Makefile fragments and shell scripts for
managing small to large sized LaTeX projects. The typical LaTeX-Mk
diff -Nru latex-mk-2.1/debian/patches/disable-tgif.patch latex-mk-2.1/debian/patches/disable-tgif.patch
--- latex-mk-2.1/debian/patches/disable-tgif.patch 1970-01-01 01:00:00.0 +0100
+++ latex-mk-2.1/debian/patches/disable-tgif.patch 2014-11-22 18:57:09.0 +0100
@@ -0,0 +1,28 @@
+Description: Disables build dependency on tgif
+ tgif was removed from testing for various reasons.
+ First, its dependencies are not in testing (see https://bugs.debian.org/699301)
+ and then its own status is ambiguous (see https://bugs.debian.org/668249).
+ This patch disables tgif-related functionality by showing error
+ message if the user wants to use it.
+ .
+ latex-mk (2.1-1.3) unstable; urgency=medium
+ .
+ * Non-maintainer upload.
+ * Disable support and dependency on tgif (Closes: #768690)
+Author: Tomasz Buchert tomasz.buch...@inria.fr
+Bug-Debian: https://bugs.debian.org/768690
+
+--- a/latex.mk.in.in
b/latex.mk.in.in
+@@ -432,9 +432,11 @@
+ # pull in tgif.[g]mk if needed
+
+ BMK:.if defined(_USE_TGIF_MK)
++BMK:.error Support for tgif files is not available, see https://bugs.debian.org/768690
+ BMK:.include ${LATEX_MK_DIR}/tgif.mk
+ BMK:.endif
+ GMK:ifdef _USE_TGIF_MK
++GMK:$(error Support for tgif files is not available, see https://bugs.debian.org/768690)
+ GMK:include ${LATEX_MK_DIR}/tgif.gmk
+ GMK:endif
+
diff -Nru latex-mk-2.1/debian/patches/series latex-mk-2.1/debian/patches/series
--- latex-mk-2.1/debian/patches/series 2011-06-22 04:36:52.0 +0200
+++ latex-mk-2.1/debian/patches/series 2014-11-22 18:17:49.0 +0100
@@ -2,3 +2,4 @@
use-fancyhdr.patch
new-nomencl.patch
use-gunzip-instead-of-gzcat.patch
+disable-tgif.patch
Processed: openmw: FTBFS on ppc64el
Processing control commands: block -1 by 770670 Bug #771186 [openmw] openmw: FTBFS on ppc64el 771186 was not blocked by any bugs. 771186 was not blocking any bugs. Added blocking bug(s) of 771186: 770670 -- 771186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771186 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#768673: uploaded
Hi, I've just uploaded your fix. Thanks! Cédric signature.asc Description: Digital signature
Bug#770132: marked as done (crmsh: FTBFS: a2x error)
Your message dated Thu, 27 Nov 2014 12:48:54 +
with message-id e1xtyvc-0004cg...@franck.debian.org
and subject line Bug#770132: fixed in crmsh 1.2.6+git+e77add-1.3
has caused the Debian Bug report #770132,
regarding crmsh: FTBFS: a2x error
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.)
--
770132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: crmsh
Version: 1.2.6+git+e77add-1.2
Severity: serious
From my pbuilder build log (on amd64):
...
crmsh configuration:
Version = 2.0 (Build: unknown)
Features = ascii-docs
Prefix = /usr
Executables = /usr/sbin
Man pages= /usr/share/man
Libraries= /usr/lib
Header files = ${prefix}/include
Arch-independent files = /usr/share
State information= /var
System configuration = /etc
dh_auto_build
make[1]: Entering directory '/tmp/buildd/crmsh-1.2.6+git+e77add'
Making all in doc
make[2]: Entering directory '/tmp/buildd/crmsh-1.2.6+git+e77add/doc'
a2x -f manpage crm.8.txt
a2x: ERROR: xsltproc --stringparam callout.graphics 0 --stringparam
navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0
/etc/asciidoc/docbook-xsl/manpage.xsl
/tmp/buildd/crmsh-1.2.6+git+e77add/doc/crm.8.xml returned non-zero exit
status 5
Makefile:568: recipe for target 'crm.8' failed
make[2]: *** [crm.8] Error 1
make[2]: Leaving directory '/tmp/buildd/crmsh-1.2.6+git+e77add/doc'
Makefile:519: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/buildd/crmsh-1.2.6+git+e77add'
dh_auto_build: make -j1 returned exit code 2
debian/rules:21: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--
Daniel Schepler
---End Message---
---BeginMessage---
Source: crmsh
Source-Version: 1.2.6+git+e77add-1.3
We believe that the bug you reported is fixed in the latest version of
crmsh, 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 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Johann Felix Soden joh...@debian.org (supplier of updated crmsh 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: Sat, 22 Nov 2014 13:09:35 +0100
Source: crmsh
Binary: crmsh
Architecture: source amd64
Version: 1.2.6+git+e77add-1.3
Distribution: unstable
Urgency: low
Maintainer: Debian HA Maintainers
debian-ha-maintain...@lists.alioth.debian.org
Changed-By: Johann Felix Soden joh...@debian.org
Description:
crmsh - CRM shell for the pacemaker cluster manager
Closes: 770132
Changes:
crmsh (1.2.6+git+e77add-1.3) unstable; urgency=low
.
* Non-maintainer upload.
* Build-Depend on docbook-xsl to fix FTBFS
Closes: 770132
Checksums-Sha1:
e439ef798f2ac2206a5d918a44dc8f846eac06c9 2358 crmsh_1.2.6+git+e77add-1.3.dsc
9d366a48f775bf210339cc2290ffb7a1e77826bc 2980
crmsh_1.2.6+git+e77add-1.3.debian.tar.xz
93d0fe9c4fdb3fccd1d187d0460727082f9f57d7 340528
crmsh_1.2.6+git+e77add-1.3_amd64.deb
Checksums-Sha256:
a5f3068ad07795dc111f2df6171433c12cc681a91cce1134f02c324d89df5918 2358
crmsh_1.2.6+git+e77add-1.3.dsc
5b85c06f8a194748c0ff3bc30d3e087b0e6dbd58d0e93d634c42ea3d807586cc 2980
crmsh_1.2.6+git+e77add-1.3.debian.tar.xz
b76f84600cd04aa90038a7edb12a24b0acdca7f1e0af55b82ec91ce9e0c95a1c 340528
crmsh_1.2.6+git+e77add-1.3_amd64.deb
Files:
c541c1523ebf284c0268c3feb84daa2f 2358 admin extra
crmsh_1.2.6+git+e77add-1.3.dsc
c347e4b6f543160bfe1e0bfe351e7bd1 2980 admin extra
crmsh_1.2.6+git+e77add-1.3.debian.tar.xz
027ee9d5f2a663bb894505b93735893e 340528 admin extra
crmsh_1.2.6+git+e77add-1.3_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQJ8BAEBCgBmBQJUcH+iXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NzdDODMzOUQzNkQ3NjZFRDg1MzIwMUM4
MzU5MTkzQkZEQ0IwOUM0AAoJEINZGTv9ywnEuMoQAIrKI4IoiYEs3peVbwxCktU4
X4vq+iHa4wsAbo1W7WQ7OXAZHXkTp2cImM82gVDQrxtjLE55wvkgl5axNquH+wAs
Bug#768673: marked as done (ruby-httpclient: FTBFS in jessie: ERROR: Test ruby2.1 failed: Errno::ECONNRESET: Connection reset by peer - SSL_connect)
Your message dated Thu, 27 Nov 2014 12:49:05 + with message-id e1xtyvn-0004go...@franck.debian.org and subject line Bug#768673: fixed in ruby-httpclient 2.3.3-3.1 has caused the Debian Bug report #768673, regarding ruby-httpclient: FTBFS in jessie: ERROR: Test ruby2.1 failed: Errno::ECONNRESET: Connection reset by peer - SSL_connect 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.) -- 768673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-httpclient Version: 2.3.3-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): Errno::ECONNRESET: Connection reset by peer - SSL_connect /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/session.rb:303:in `connect' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/session.rb:303:in `ssl_connect' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/session.rb:760:in `block in connect' /usr/lib/ruby/2.1.0/timeout.rb:91:in `block in timeout' /usr/lib/ruby/2.1.0/timeout.rb:101:in `call' /usr/lib/ruby/2.1.0/timeout.rb:101:in `timeout' /usr/lib/ruby/2.1.0/timeout.rb:127:in `timeout' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/session.rb:751:in `connect' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/session.rb:609:in `query' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient/session.rb:164:in `query' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient.rb:1083:in `do_get_block' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient.rb:887:in `block in do_request' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient.rb:981:in `protect_keep_alive_disconnected' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient.rb:886:in `do_request' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient.rb:774:in `request' /«PKGBUILDDIR»/debian/ruby-httpclient/usr/lib/ruby/vendor_ruby/httpclient.rb:677:in `get' /«PKGBUILDDIR»/test/test_ssl.rb:69:in `test_verification' /usr/lib/ruby/2.1.0/minitest/unit.rb:1265:in `run' /usr/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run' /usr/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite' /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `map' /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite' /usr/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites' /usr/lib/ruby/2.1.0/test/unit.rb:661:in `each' /usr/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites' /usr/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything' /usr/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests' /usr/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run' /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each' /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run' /usr/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:27:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:780:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in autorun' /usr/lib/ruby/2.1.0/test/unit.rb:33:in `run_once' /usr/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun' 184 tests, 734 assertions, 1 failures, 4 errors, 0 skips ruby -v: ruby 2.1.4p265 (2014-10-27) [x86_64-linux-gnu] ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/ruby-httpclient_2.3.3-3_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: ruby-httpclient Source-Version: 2.3.3-3.1 We believe that the bug you reported is fixed in the latest version of ruby-httpclient, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and
Bug#770670: more affected packages
Hi, to get an idea about the severity of the issue I investigated the 29 source packages that build-depend on libsdl2-dev. The following fail on ppc64el and have build logs that seem to point to this problem: performous: https://buildd.debian.org/status/fetch.php?pkg=performousarch=ppc64elver=0.7.0%2Bgit20140715-2stamp=1414945247 /usr/include/boost/mpl/vector.hpp:36:73: fatal error: boost/mpl/__attribute__((altivec(vector__)))/__attribute__((altivec(vector__)))20.hpp: No such file or directory # include BOOST_PP_STRINGIZE(boost/mpl/vector/AUX778076_VECTOR_HEADER) mpv (#770197): https://buildd.debian.org/status/fetch.php?pkg=mpvarch=ppc64elver=0.6.2-2stamp=1415094069 ../audio/out/ao_sdl.c:180:18: error: incompatible types when assigning to type '__vector __bool int' from type 'int' blobby: https://buildd.debian.org/status/fetch.php?pkg=blobbyarch=ppc64elver=1.0-1stamp=1410483474 /«PKGBUILDDIR»/src/Clock.cpp:55:6: error: prototype for '__vector(4) __bool int Clock::isRunning() const' does not match any in class 'Clock' Those three are part of Jessie it seems. The packages vcmi and openmw ftbfs because of this too, but they are not part of Jessie. Thanks! cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 771172 to new services are not automatically picked up without explicit systemctl daemon-reload
Processing commands for cont...@bugs.debian.org: retitle 771172 new services are not automatically picked up without explicit systemctl daemon-reload Bug #771172 [systemd] systemd-sysv-generator does not generate Changed Bug title to 'new services are not automatically picked up without explicit systemctl daemon-reload' from 'systemd-sysv-generator does not generate' thanks Stopping processing here. Please contact me if you need assistance. -- 771172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771172 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: severity of 771172 is wishlist, tagging 771172
Processing commands for cont...@bugs.debian.org: severity 771172 wishlist Bug #771172 [systemd] new services are not automatically picked up without explicit systemctl daemon-reload Severity set to 'wishlist' from 'critical' tags 771172 + wontfix Bug #771172 [systemd] new services are not automatically picked up without explicit systemctl daemon-reload Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 771172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771172 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 (with 1 errors): Re: iceweasel: downloads Cisco's OpenH264 video codec
Processing commands for cont...@bugs.debian.org: tags 769716 + security Bug #769716 [iceweasel] iceweasel: downloads Cisco's OpenH264 video codec Added tag(s) security. tags 769716 grave Unknown tag/s: grave. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore. stop Stopping processing here. Please contact me if you need assistance. -- 769716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769716 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#769716: iceweasel: downloads Cisco's OpenH264 video codec
tags 769716 + security tags 769716 grave stop Wow... I've just stumbled over this by accident and this is really extremely outrageous. Adding security tag and raising severity to grave, since no one know what's actually contained in that binary blob, one must basically assume it's an security breach that tries to install a root-kit. And access to a normal user is usually equal to access to root on desktop systems - therefore the severity should actually be critical. It's really highly disturbing that something like this could slip into Debian, potentially compromising countless of systems. And it once more proves the points I've brought up several times on debian-devel, that we have some severe problems about downloader packages and software that circumvents the package management system. Chris. smime.p7s Description: S/MIME cryptographic signature
Processed: Re: Bug#771101: wheezy - jessie dist-upgrade failure when systemd is the active PID1
Processing control commands: reassign -1 systemd Bug #771101 [udev] wheezy - jessie dist-upgrade failure when systemd is the active PID1 Bug reassigned from package 'udev' to 'systemd'. No longer marked as found in versions systemd/215-6. Ignoring request to alter fixed versions of bug #771101 to the same values previously set forcemerge -1 761306 Bug #771101 [systemd] wheezy - jessie dist-upgrade failure when systemd is the active PID1 Bug #761306 [systemd] v208 - v215 upgrade fails to re-open notification socket Severity set to 'serious' from 'normal' Bug #771101 [systemd] wheezy - jessie dist-upgrade failure when systemd is the active PID1 Marked as found in versions systemd/215-2. Merged 761306 771101 -- 761306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761306 771101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771101 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#771101: wheezy - jessie dist-upgrade failure when systemd is the active PID1
control: reassign -1 systemd control: forcemerge -1 761306 Am 27.11.2014 um 02:49 schrieb Michael Biebl: control: forcemerge -1 761306 Am 26.11.2014 um 23:06 schrieb Michael Biebl: I think, that's the relevant part from the journal, specifically: Nov 26 19:36:57 debian systemd[1]: bind(@run/systemd/notify) failed: Address already in use Nov 26 19:36:57 debian systemd[1]: Failed to reload: Address already in use Running lsof /run/systemd/notify, doesn't show any process listening on the socket. systemd-udevd in v215 uses Type=notify and I suspect it get's stuck in State activating since the sd_notify call doesn't succeed. I remember Sjoerd running into this issue as well, but I don't remember anymore if he found the root cause and how to fix it. I think it's the same bug as [1] and since this affects the dist-upgrade from wheezy, I think a RC severity is justified. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761306 The notification socket changed from being in the abstract namespace to /run/systemd/notify in v209 IIRC. I made an interesting observation: I've added an ls -la /run/systemd/notify and lsof /run/systemd/notify in systemd.postinst right before systemd is re-execd. I would have expected, that the socket does *not* exist before systemd is re-execd, but apparently I had a file there: srw-rw-rw- 1 root root 0 Oct 10 10:41 /run/systemd/notify and no process listening on it. (don't worry about the date, it was run in a VM with a busted clock). *Some* process is triggering the creation of the notification socket and it also seems to have the wrong permissions (should be srwxrwxrwx). So I've tried and added a brute-force rm -f /run/systemd/notify right before the systemctl daemon-reexec and the upgrade of the systemd and udev package completed successfully. Does anyone have an idea what's going on here and how to fix it properly? -- 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
Processed: Re: iceweasel: downloads Cisco's OpenH264 video codec
Processing commands for cont...@bugs.debian.org: severity 769716 grave Bug #769716 [iceweasel] iceweasel: downloads Cisco's OpenH264 video codec Severity set to 'grave' from 'serious' stop Stopping processing here. Please contact me if you need assistance. -- 769716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769716 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#771203: lnav: FTBFS on mips, powerpc and s390x
Source: lnav Version: 0.7.1-1 Severity: serious Justification: FTBFS lnav/0.7.1-1 uploaded to experimental FTBFS on mips, powerpc and s390x. https://buildd.debian.org/status/fetch.php?pkg=lnavarch=mipsver=0.7.1-1stamp=1417091917 https://buildd.debian.org/status/fetch.php?pkg=lnavarch=powerpcver=0.7.1-1stamp=1417089688 https://buildd.debian.org/status/fetch.php?pkg=lnavarch=s390xver=0.7.1-1stamp=1417089614 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770157: marked as done ([libpython2.7-stdlib] Missing attribute PROTOCOL_SSLv3)
Your message dated Thu, 27 Nov 2014 15:22:54 +
with message-id e1xu0ue-0007so...@franck.debian.org
and subject line Bug#770157: fixed in python2.7 2.7.9~rc1-1
has caused the Debian Bug report #770157,
regarding [libpython2.7-stdlib] Missing attribute PROTOCOL_SSLv3
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.)
--
770157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libpython2.7-stdlib
Version: 2.7.8-12
Severity: grave
--- Please enter the report below this line. ---
ipython session:
In [7]: import requests
---
AttributeErrorTraceback (most recent call last)
ipython-input-7-686486c241c8 in module()
1 import requests
/usr/lib/python2.7/dist-packages/requests/__init__.py in module()
66 sys.modules[where + '.' + name] = module
67
--- 68 _attach_namespace(urllib3, 'requests.packages')
69 del _attach_namespace
70 # Python 3 needs this imported explicitly.
/usr/lib/python2.7/dist-packages/requests/__init__.py in
_attach_namespace(package, where)
61 package.__name__ +
'.'):
62 try:
--- 63 module = __import__(name)
64 except ImportError:
65 continue
/usr/lib/python2.7/dist-packages/urllib3/contrib/pyopenssl.py in module()
71 _openssl_versions = {
72 ssl.PROTOCOL_SSLv23: OpenSSL.SSL.SSLv23_METHOD,
--- 73 ssl.PROTOCOL_SSLv3: OpenSSL.SSL.SSLv3_METHOD,
74 ssl.PROTOCOL_TLSv1: OpenSSL.SSL.TLSv1_METHOD,
75 }
AttributeError: 'module' object has no attribute 'PROTOCOL_SSLv3'
In [5]: from _ssl import PROTOCOL_TLSv1, PROTOCOL_SSLv23, PROTOCOL_SSLv3
---
ImportError Traceback (most recent call last)
ipython-input-5-06c8522d918c in module()
1 from _ssl import PROTOCOL_TLSv1, PROTOCOL_SSLv23, PROTOCOL_SSLv3
ImportError: cannot import name PROTOCOL_SSLv3
In [6]: _ssl.__file__
Out[6]: '/usr/lib/python2.7/lib-dynload/_ssl.x86_64-linux-gnu.so'
Package affected:
root@paz:~# apt-file search
/usr/lib/python2.7/lib-dynload/_ssl.x86_64-linux-gnu.so
libpython2.7-stdlib: /usr/lib/python2.7/lib-dynload/_ssl.x86_64-linux-gnu.so
Error happens after this update:
Rcb:1 http://ftp.es.debian.org/debian/ unstable/main db5.1-util amd64 5.1.29-9
[674 kB]
Rcb:2 http://ftp.es.debian.org/debian/ unstable/main libudev1 i386 215-6 [52,6
kB]
Rcb:3 http://ftp.es.debian.org/debian/ unstable/main libudev1 amd64 215-6 [49,9
kB]
Rcb:4 http://ftp.es.debian.org/debian/ unstable/main udev amd64 215-6 [872 kB]
Rcb:5 http://ftp.es.debian.org/debian/ unstable/main libsystemd0 i386 215-6
[90,5 kB]
Rcb:6 http://ftp.es.debian.org/debian/ unstable/main libsystemd0 amd64 215-6
[82,7 kB]
Rcb:7 http://ftp.es.debian.org/debian/ unstable/main systemd amd64 215-6 [2532
kB]
Rcb:8 http://ftp.es.debian.org/debian/ unstable/main systemd-sysv amd64 215-6
[29,7 kB]
Rcb:9 http://ftp.es.debian.org/debian/ unstable/main libpam-systemd amd64 215-6
[119 kB]
Rcb:10 http://ftp.es.debian.org/debian/ unstable/main libgudev-1.0-0 amd64
215-6 [35,7 kB]
Rcb:11 http://ftp.es.debian.org/debian/ unstable/main libpangoft2-1.0-0 i386
1.36.8-3 [216 kB]
Rcb:12 http://ftp.es.debian.org/debian/ unstable/main libpangoft2-1.0-0 amd64
1.36.8-3 [213 kB]
Rcb:13 http://ftp.es.debian.org/debian/ unstable/main libpangocairo-1.0-0 i386
1.36.8-3 [202 kB]
Rcb:14 http://ftp.es.debian.org/debian/ unstable/main libpangocairo-1.0-0 amd64
1.36.8-3 [200 kB]
Rcb:15 http://ftp.es.debian.org/debian/ unstable/main libpangoxft-1.0-0 i386
1.36.8-3 [196 kB]
Rcb:16
Processed: Patch
Processing commands for cont...@bugs.debian.org: tags 771054 + patch Bug #771054 [lintian] lintian: FTBFS: binaries-from-other-arch fails with latest binutils Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 771054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771054 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#766670: RC bug in stable and oldstable for getmail4
Hi, On Tue, Nov 25, 2014 at 09:39:36PM +0900, Osamu Aoki wrote: On Tue, Nov 25, 2014 at 10:04:34AM +0100, Raphael Hertzog wrote: On Sun, 23 Nov 2014, Osamu Aoki wrote: We can consider a new upstream version for squeeze-lts and we can ask the security team's opinion for wheezy. Would you like to prepare a 4.46.0-1~deb6u1.dsc working in squeeze and submit it for review to debian-...@lists.debian.org ? See below. It does not look like simple re-versioning and safe backporting without careful review. It would be nice if you could test it though, because we don't have many testers before release... ... This package is one of those python package using debian/rules as: %: dh $@ --with python2 As I checked oldstable package %: dh $@ If everything is clean and neat, this change should have been the only thing needed for backports for important things, but things are a bit messy. I am not really motivated to do this I looked into this anyway. This squeeze package was made before I reorganized packaging to my taste. The source comes with setup.py. I now use setup.py to generate files to be installed for wheeze/jessie. Back then, the source was patched and installed directly from source tree. There are patches such as: # For Debian Python-support --- a/getmail_maildir +++ b/getmail_maildir @@ -26,6 +26,8 @@ import os +sys.path.append(/usr/share/getmail4) + from getmailcore.message import Message from getmailcore.utilities import * from getmailcore.exceptions import * Hmmm... this python-support thing, I do not remember how it should be done. It looks like modules were installed into /usr/share/getmail4/getmailcore by getmail.install. This does not look normal search path used even in these days. That was why these sys.path.append() was needed. Yack. Although I am not comfortable to package this way if I do it again (I inherited it and did not touch it back then.), I should do the same strange packaging style again considering oldstable update if I do. If I have time, I may make test package... I need to check how python-support package used to be used back then. If anyone can give my guidance for how lts packages should be made in this case, let me know. (Now I am leaning to follow the old ugly packkging style of squeeze package.) Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771101: Bug#761306: Bug#771101: wheezy - jessie dist-upgrade failure when systemd is the active PID1
Am 27.11.2014 um 15:59 schrieb Michael Biebl: I would have expected, that the socket does *not* exist before systemd is re-execd, but apparently I had a file there: srw-rw-rw- 1 root root 0 Oct 10 10:41 /run/systemd/notify and no process listening on it. (don't worry about the date, it was run in a VM with a busted clock). *Some* process is triggering the creation of the notification socket and it also seems to have the wrong permissions (should be srwxrwxrwx). It's actually a bit simpler: v44 *did* already use /run/systemd/notify (with permissions srw-rw-rw-), then it was changed to use an abstract namespace and it was changed back and forth a couple of times. Maybe a simple chmod will do when upgrading from v44. Will test. -- 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#769716: iceweasel: downloads Cisco's OpenH264 video codec
On Thu, Nov 27, 2014 at 03:54:24PM +0100, Christoph Anton Mitterer wrote: tags 769716 + security tags 769716 grave stop Wow... I've just stumbled over this by accident and this is really extremely outrageous. Adding security tag and raising severity to grave, since no one know what's actually contained in that binary blob, one must basically assume it's an security breach that tries to install a root-kit. And access to a normal user is usually equal to access to root on desktop systems - therefore the severity should actually be critical. It's really highly disturbing that something like this could slip into Debian, potentially compromising countless of systems. And it once more proves the points I've brought up several times on debian-devel, that we have some severe problems about downloader packages and software that circumvents the package management system. a) it's not in any release of Debian, and it's not in any upcoming release of Debian either. It's in a package from experimental. b) everyone knows what's actually contained in that binary blob, since it's built from open source code, and the build is (supposed to be) reproductible. c) the binary blob is verified against a sha256 checksum downloaded from a mozilla server through HTTPS with certificate pinning. So it's not as bad as you make it sound. And it's not going to stay that way anyways. Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 769716, severity of 769716 is serious, tagging 769716
Processing commands for cont...@bugs.debian.org: tags 769716 - security Bug #769716 [iceweasel] iceweasel: downloads Cisco's OpenH264 video codec Removed tag(s) security. severity 769716 serious Bug #769716 [iceweasel] iceweasel: downloads Cisco's OpenH264 video codec Severity set to 'serious' from 'grave' tags 769716 + experimental Bug #769716 [iceweasel] iceweasel: downloads Cisco's OpenH264 video codec Added tag(s) experimental. thanks Stopping processing here. Please contact me if you need assistance. -- 769716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769716 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#768394: marked as done (oss4-dkms: module FTBFS for Linux 3.16: endian.h: No such file or directory)
Your message dated Thu, 27 Nov 2014 15:50:18 + with message-id e1xu1kk-0002zc...@franck.debian.org and subject line Bug#768394: fixed in oss4 4.2-build2010-1.1 has caused the Debian Bug report #768394, regarding oss4-dkms: module FTBFS for Linux 3.16: endian.h: No such file or directory 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.) -- 768394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: oss4-dkms Version: 4.2-build2010-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to build a module for linux-3.16-3-amd64: DKMS make.log for oss4-4.2-build2010 for kernel 3.16-3-amd64 (x86_64) Fri Nov 7 01:14:30 UTC 2014 make: Entering directory '/usr/src/linux-headers-3.16-3-amd64' Makefile:10: *** mixed implicit and normal rules: deprecated syntax make[1]: Entering directory `/usr/src/linux-headers-3.16-3-amd64' CC [M] /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o In file included from /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.c:42:0: /var/lib/dkms/oss4/4.2-build2010/build/core/audio_core.h:3:20: fatal error: endian.h: No such file or directory #include endian.h ^ compilation terminated. /usr/src/linux-headers-3.16-3-common/scripts/Makefile.build:262: recipe for target '/var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o' failed make[3]: *** [/var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o] Error 1 /usr/src/linux-headers-3.16-3-common/Makefile:1350: recipe for target '_module_/var/lib/dkms/oss4/4.2-build2010/build/core' failed make[2]: *** [_module_/var/lib/dkms/oss4/4.2-build2010/build/core] Error 2 Makefile:181: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/usr/src/linux-headers-3.16-3-amd64' Andreas ---End Message--- ---BeginMessage--- Source: oss4 Source-Version: 4.2-build2010-1.1 We believe that the bug you reported is fixed in the latest version of oss4, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost t...@debian.org (supplier of updated oss4 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: Sat, 22 Nov 2014 16:22:36 +0100 Source: oss4 Binary: oss4-base oss4-gtk oss4-dkms oss4-source oss4-dev liboss4-salsa2 liboss4-salsa-dev liboss4-salsa-asound2 Architecture: source all amd64 Version: 4.2-build2010-1.1 Distribution: unstable Urgency: medium Maintainer: Debian OSS4 Maintainers pkg-oss4-maintain...@lists.alioth.debian.org Changed-By: Tobias Frost t...@debian.org Description: liboss4-salsa-asound2 - OSS to Alsa compatibility library - binary compatibility symlink liboss4-salsa-dev - OSS to Alsa compatibility library -- development files liboss4-salsa2 - OSS to Alsa compatibility library oss4-base - Open Sound System - base package oss4-dev - Open Sound System - development files oss4-dkms - Open Sound System - DKMS module sources oss4-gtk - Open Sound System - simple GTK2-based mixer control oss4-source - Open Sound System - drivers sources Closes: 768394 Changes: oss4 (4.2-build2010-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add dependency on libc-dev for oss4-dkms to avoid build failure when compiling the module (Closes: #768394) Checksums-Sha1: b4d86de1b611762abbff3382293dffb2aa323acf 2535 oss4_4.2-build2010-1.1.dsc 22a16cb615dc9b0116e4105d21e3d1acb933ab72 66584 oss4_4.2-build2010-1.1.debian.tar.xz d0d64ed07f76b03bd70ba9821411de7e7ef69a05 28028 oss4-dev_4.2-build2010-1.1_all.deb Checksums-Sha256: 24888db5e2f1cb24796bb72b24aad23fd32827be760433d0e3663f5996bec53a 2535 oss4_4.2-build2010-1.1.dsc df48f663a9cf76158b542d37e7aebe9d8b36a9bd4878d90756437c19d32412dc 66584 oss4_4.2-build2010-1.1.debian.tar.xz af0214f10db1349673d84a9edbf2700038b4198fe2874bf27893adc87e897d6d 28028 oss4-dev_4.2-build2010-1.1_all.deb Files: b9a2ed197620eacf7397cf4f7b5801d4 2535
Bug#771101: Bug#761306: Bug#771101: wheezy - jessie dist-upgrade failure when systemd is the active PID1
Am 27.11.2014 um 16:41 schrieb Michael Biebl: It's actually a bit simpler: v44 *did* already use /run/systemd/notify (with permissions srw-rw-rw-), then it was changed to use an abstract namespace and it was changed back and forth a couple of times. Maybe a simple chmod will do when upgrading from v44. Will test. Just tested, a chmod 777 is not sufficient. systemd will still fail to bind to the socket. Only removing it and letting systemd create it on daemon-reexec seems to do the trick. -- 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#768615: [DRE-maint] Bug#768615: #768615: ruby-pygments.rb: FTBFS in jessie: ERROR: Test ruby2.1 failed
२०१४-११-२७ १७:४७ [GMT]+०५:३०, Tomasz Buchert tomasz.buch...@inria.fr: Hi Christian, I think I made a mistake in this NMU, the changelog uploads it to unstable, but I think it should be testing instead (on the other hand you may unblock transition unstable = testing if I'm correct). Hi Tomasz, We should upload fixes to unstable and request release team to unblock. Thanks Praveen -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771054: Patch
tags 771054 + patch
thanks
Hi,
The following patch fixes this problem on my system:
diff -Nru lintian-2.5.30+deb8u2/helpers/coll/objdump-info-helper
lintian-2.5.30+deb8u3/helpers/coll/objdump-info-helper
--- lintian-2.5.30+deb8u2/helpers/coll/objdump-info-helper 2014-11-01
09:18:50.0 -0700
+++ lintian-2.5.30+deb8u3/helpers/coll/objdump-info-helper 2014-11-27
07:07:14.0 -0800
@@ -85,7 +85,8 @@
print UPX: yes\n;
}
} elsif (
-$line =~ m/^readelf: Error: Unable to read in 0x[0-9a-fA-F]+ bytes of/
+$line =~ m/^readelf: Error: Reading 0x[0-9a-fA-F]+ bytes extends past
end of file for section headers/
+or $line =~ m/^readelf: Error: Unable to read in 0x[0-9a-fA-F]+ bytes
of/
or $line
=~ m/^readelf: Error: .*: Failed to read .*(?:magic number|file
header)/
) {
--
Matt
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770918: marked as done (flac: CVE-2014-8962/CVE-2014-9028: heap buffer overflows)
Your message dated Thu, 27 Nov 2014 16:04:11 + with message-id e1xu1yb-0005p4...@franck.debian.org and subject line Bug#770918: fixed in flac 1.3.0-3 has caused the Debian Bug report #770918, regarding flac: CVE-2014-8962/CVE-2014-9028: heap buffer overflows 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.) -- 770918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flac Version: 1.3.0-2+b1 Severity: serious Tags: security From: http://lists.xiph.org/pipermail/flac-dev/2014-November/005226.html Google Security Team member, Michele Spagnuolo, recently found two potential problems in the FLAC code base. They are : CVE-2014-9028 : Heap buffer write overflow CVE-2014-8962 : Heap buffer read overflow For Linux distributions, the specific fixes for these two CVEs are available from Git here: https://git.xiph.org/?p=flac.git;a=commit;h=fcf0ba06ae12ccd7c67cee3c8d948df15f946b85 https://git.xiph.org/?p=flac.git;a=commit;h=5b3033a2b355068c11fe637e14ac742d273f076e and are simple enough that they should apply cleanly to the last official release 1.3.0 and possibly even the previous one, 1.2.1. A pre-release (version 1.3.1pre1) for the next version which includes these fixes and more is available here: http://downloads.xiph.org/releases/flac/beta/ A full release (version 1.3.1) will be available in the next couple of days. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flac depends on: ii libc6 2.19-13 ii libflac8 1.3.0-2+b1 flac recommends no packages. flac suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: flac Source-Version: 1.3.0-3 We believe that the bug you reported is fixed in the latest version of flac, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath fabian+deb...@greffrath.com (supplier of updated flac 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: Thu, 27 Nov 2014 16:52:51 +0100 Source: flac Binary: flac libflac8 libflac-doc libflac-dev libflac++6 libflac++-dev Architecture: source amd64 all Version: 1.3.0-3 Distribution: unstable Urgency: high Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Fabian Greffrath fabian+deb...@greffrath.com Description: flac - Free Lossless Audio Codec - command line tools libflac++-dev - Free Lossless Audio Codec - C++ development library libflac++6 - Free Lossless Audio Codec - C++ runtime library libflac-dev - Free Lossless Audio Codec - C development library libflac-doc - Free Lossless Audio Codec - library documentation libflac8 - Free Lossless Audio Codec - runtime C library Closes: 770918 Changes: flac (1.3.0-3) unstable; urgency=high . * Fixes for CVE-2014-8962 and CVE-2014-9028: + Backport three patches from upstream GIT repository: - CVE-2014-8962.patch: Fix a buffer read overflow. - CVE-2014-9028.patch: Avoid a heap overflow. - CVE-2014-9028-2.patch: Avoid a heap overflow. Closely related to the former fix, but strictly speaking not the same vulnerability. + Closes: #770918. + Thanks Erik de Castro Lopo for the bug report and the upstream fixes! Checksums-Sha1: afd9218d22316717874fa8819c1903bb9882f6c8 2259 flac_1.3.0-3.dsc d5cf793e8d010dab3b30280ef24f52c5f485186d 14772 flac_1.3.0-3.debian.tar.xz a52ffa2d39a70a51686ac063f925d802938b1206 121872 flac_1.3.0-3_amd64.deb 648e0ed79e5c48af542caa7fc07b207704609150 89338 libflac8_1.3.0-3_amd64.deb ac9628c3a1e31196162695438f2a0eb4fe9b26ba 697574 libflac-doc_1.3.0-3_all.deb
Bug#769470: marked as done (qemu-system-x86: qemu-system-i386 is unusable on mips/mipsel hosts)
Your message dated Thu, 27 Nov 2014 16:07:13 + with message-id e1xu1b7-0005z2...@franck.debian.org and subject line Bug#769470: fixed in qemu 2.1+dfsg-8 has caused the Debian Bug report #769470, regarding qemu-system-x86: qemu-system-i386 is unusable on mips/mipsel hosts 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.) -- 769470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qemu-system-x86 Version: 2.1+dfsg-7+b1 Severity: grave Since the upgrade from version 2.0 to 2.1, qemu-system-i386 is unusable mips and mipsel hosts. While the BIOS boots correctly, then any OS hang or crash almost immediately. This is already fixed upstream: http://git.qemu.org/?p=qemu.git;a=commit;h=0a2923f8488498000eec54871456aa64a4391da4 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: mipsel (mips) Kernel: Linux 3.16.0-00053-g6f17c28 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20141004.86285d1-1 ii libaio1 0.3.110-1 ii libasound2 1.0.28-1 ii libbluetooth3 5.23-1 ii libbrlapi0.65.2~20141018-2 ii libc6 2.19-11 ii libcurl3-gnutls 7.38.0-2 ii libfdt1 1.4.0+dfsg-1 ii libgcc1 1:4.9.1-16 ii libglib2.0-02.42.0-2 ii libgnutls-deb0-28 3.3.8-2 ii libiscsi2 1.12.0-2 ii libjpeg62-turbo 1:1.3.1-8 ii libncurses5 5.9+20140913-1 ii libpixman-1-0 0.32.6-3 ii libpng12-0 1.2.50-2 ii libpulse0 5.0-6+b1 ii librados2 0.80.7-1 ii librbd1 0.80.7-1 ii libsasl2-2 2.1.26.dfsg1-11 ii libsdl1.2debian 1.2.15-10 ii libssh2-1 1.4.3-4 ii libtinfo5 5.9+20140913-1 ii libusb-1.0-02:1.0.19-1 ii libusbredirparser1 0.7-1 ii libuuid12.20.1-5.11 ii libvdeplug2 2.3.2+r586-1 ii libx11-62:1.6.2-3 ii qemu-system-common 2.1+dfsg-7+b1 ii seabios 1.7.5-1 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages qemu-system-x86 recommends: pn qemu-utils none Versions of packages qemu-system-x86 suggests: ii kmod 18-3 pn ovmf none pn sambanone pn sgabios none pn vde2 none -- no debconf information ---End Message--- ---BeginMessage--- Source: qemu Source-Version: 2.1+dfsg-8 We believe that the bug you reported is fixed in the latest version of qemu, 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 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev m...@tls.msk.ru (supplier of updated qemu 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, 27 Nov 2014 18:32:45 +0300 Source: qemu Binary: qemu qemu-system qemu-system-common qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 2.1+dfsg-8 Distribution: unstable Urgency: low Maintainer: Debian QEMU Team pkg-qemu-de...@lists.alioth.debian.org Changed-By: Michael Tokarev m...@tls.msk.ru Description: qemu - fast processor emulator qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscelaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
Bug#768926: marked as done (qemu-user-static provides static executables but does not have Built-Using field)
Your message dated Thu, 27 Nov 2014 16:07:13 +
with message-id e1xu1b7-0005yq...@franck.debian.org
and subject line Bug#768926: fixed in qemu 2.1+dfsg-8
has caused the Debian Bug report #768926,
regarding qemu-user-static provides static executables but does not have
Built-Using field
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.)
--
768926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: qemu-user-static
Version: 1.1.2+dfsg-1
Severity: serious
Tags: jessie-ignore
Justification: Policy 7.8
As said in the subject, qemu-user-static package does not include the
Built-Using field which is required according to Debian Policy §7.8
if the package is using parts of other packages, for example when
linking to other libraries statically.
/mjt
---End Message---
---BeginMessage---
Source: qemu
Source-Version: 2.1+dfsg-8
We believe that the bug you reported is fixed in the latest version of
qemu, 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 768...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev m...@tls.msk.ru (supplier of updated qemu 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, 27 Nov 2014 18:32:45 +0300
Source: qemu
Binary: qemu qemu-system qemu-system-common qemu-system-misc qemu-system-arm
qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user
qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm
Architecture: source
Version: 2.1+dfsg-8
Distribution: unstable
Urgency: low
Maintainer: Debian QEMU Team pkg-qemu-de...@lists.alioth.debian.org
Changed-By: Michael Tokarev m...@tls.msk.ru
Description:
qemu - fast processor emulator
qemu-guest-agent - Guest-side qemu-system agent
qemu-kvm - QEMU Full virtualization on x86 hardware
qemu-system - QEMU full system emulation binaries
qemu-system-arm - QEMU full system emulation binaries (arm)
qemu-system-common - QEMU full system emulation binaries (common files)
qemu-system-mips - QEMU full system emulation binaries (mips)
qemu-system-misc - QEMU full system emulation binaries (miscelaneous)
qemu-system-ppc - QEMU full system emulation binaries (ppc)
qemu-system-sparc - QEMU full system emulation binaries (sparc)
qemu-system-x86 - QEMU full system emulation binaries (x86)
qemu-user - QEMU user mode emulation binaries
qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
qemu-user-static - QEMU user mode emulation binaries (static version)
qemu-utils - QEMU utilities
Closes: 763043 763841 768244 768926 769451 769470 770468 770880
Changes:
qemu (2.1+dfsg-8) unstable; urgency=low
.
[ Michael Tokarev ]
* add Built-Using control field for qemu-user-static package:
take contents of qemu-user ${shlibs:Depends} and transform it
into list of source packages with versions. (Closes: #768926)
* run remove-alternatives in qemu-system.postinst (the metapkg)
too, not only in qemu-system-XX.postinst, to handle upgrades
from wheezy (Closes: #768244)
* several fixes for debian/qemu-user.1 manpage. It needs more
work, but at least some easy and obvious errors are fixed now.
(Closes: #763841)
* migration-fix-parameter-validation-on-ram-load.patch from upstream
(Closes: #769451 CVE-2014-7840)
* fix x86_64 binfmt mask to allow more values in ELF_OSABI field
(byte7). Current gcc/binfmt sometimes produces binaries with
this field set to 3 (OSABI_GNU) not 0 (OSABI_SYSV) as used to be.
Set mask to 0xfb not 0xff here, to allow 0 (traditional SYSV),
1 (HPUX), 2 (NETBSD) or 3 (GNU). This lets 2 more types than
necessary, but qemu will reject wrong types so no harm is done.
Some other binfmts ignore this field completely (with mask=0).
Maybe some day we'll have 2 different binfmt registrations for
the 2 different ABI types. (Closes: #763043)
* usb-host-fix-usb_host_speed_compat-tyops.patch -- fix host usb devices
attach, without this patch many USB devices does not work
*
Processed: your mail
Processing commands for cont...@bugs.debian.org:
reopen 719943
Bug #719943 {Done: Louis Bouchard louis.bouch...@ubuntu.com} [makedumpfile]
makedumpfile: fails to dump kernel log, continually appends the line [
0.00] to dmesg file
Bug reopened
Ignoring request to alter fixed versions of bug #719943 to the same values
previously set
End of message, stopping processing here.
Please contact me if you need assistance.
--
719943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719943
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#769514: marked as done (emacs-calfw-howm: installation fails)
Your message dated Thu, 27 Nov 2014 16:18:59 + with message-id e1xu1mv-0007pb...@franck.debian.org and subject line Bug#769514: fixed in emacs-calfw 1.3+git20141031-2 has caused the Debian Bug report #769514, regarding emacs-calfw-howm: installation fails 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.) -- 769514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: emacs-calfw-howm Version: 1.3+git20141005-1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following extra packages will be installed: adwaita-icon-theme dconf-gsettings-backend dconf-service emacs-calfw emacs24 emacs24-bin-common emacs24-common emacsen-common fontconfig fontconfig-config fonts-dejavu-core gconf-service gconf2-common glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas hicolor-icon-theme howm imagemagick-common libasound2 libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2 libcairo2 libcolord2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-glib-1-2 libdconf1 libexpat1 libffi6 libfftw3-double3 libfontconfig1 libfreetype6 libfribidi0 libgconf-2-4 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgif4 libglib2.0-0 libgmp10 libgnutls-deb0-28 libgomp1 libgpm2 libgraphite2-3 libgssapi-krb5-2 libgtk-3-0 libgtk-3-bin libgtk-3-common libharfbuzz0b libhogweed2 libice6 libjasper1 libjbig0 libjpeg62-turbo libjson-glib-1.0-0 libjson-glib-1.0-common libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.4-2 liblockfile-bin liblockfile1 liblqr-1-0 libltdl7 libm17n-0 libmagickcore-6.q16-2 libmagickwand-6.q16-2 libnettle4 libotf0 libp11-kit0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpng12-0 libproxy1 librest-0.7-0 librsvg2-2 librsvg2-common libsasl2-2 libsasl2-modules-db libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libsqlite3-0 libtasn1-6 libthai-data libthai0 libtiff5 libvpx1 libwayland-client0 libwayland-cursor0 libx11-6 libx11-data libxau6 libxcb-render0 libxcb-shm0 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3 libxft2 libxi6 libxinerama1 libxkbcommon0 libxml2 libxpm4 libxrandr2 libxrender1 libxt6 m17n-db shared-mime-info ucf x11-common xkb-data Suggested packages: org-mode elscreen emacs24-common-non-dfsg emacs24-el ruby libasound2-plugins alsa-utils cups-common libfftw3-bin libfftw3-dev libgd-tools gnutls-bin gpm krb5-doc krb5-user gvfs libjasper-runtime liblcms2-utils m17n-docs libmagickcore-6.q16-2-extra librsvg2-bin gawk Recommended packages: at-spi2-core colord dbus libglib2.0-data xdg-user-dirs krb5-locales ghostscript gsfonts libsasl2-modules xml-core The following NEW packages will be installed: adwaita-icon-theme dconf-gsettings-backend dconf-service emacs-calfw emacs-calfw-howm emacs24 emacs24-bin-common emacs24-common emacsen-common fontconfig fontconfig-config fonts-dejavu-core gconf-service gconf2-common glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas hicolor-icon-theme howm imagemagick-common libasound2 libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2 libcairo2 libcolord2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-glib-1-2 libdconf1 libexpat1 libffi6 libfftw3-double3 libfontconfig1 libfreetype6 libfribidi0 libgconf-2-4 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgif4 libglib2.0-0 libgmp10 libgnutls-deb0-28 libgomp1 libgpm2 libgraphite2-3 libgssapi-krb5-2 libgtk-3-0 libgtk-3-bin libgtk-3-common libharfbuzz0b libhogweed2 libice6 libjasper1 libjbig0 libjpeg62-turbo libjson-glib-1.0-0 libjson-glib-1.0-common libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.4-2 liblockfile-bin liblockfile1 liblqr-1-0 libltdl7 libm17n-0 libmagickcore-6.q16-2 libmagickwand-6.q16-2 libnettle4 libotf0 libp11-kit0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpng12-0 libproxy1 librest-0.7-0 librsvg2-2 librsvg2-common libsasl2-2 libsasl2-modules-db libsm6 libsoup-gnome2.4-1 libsoup2.4-1
Bug#770194: please confirm the version of ruby-i18n
Control: tag -1 + sid On Thu, 27 Nov 2014 10:49:14 +0100, gregor herrmann wrote: If the bug is not reproducible with the version of ruby-i18n in Jessie, then I'll probably add a version 0.6.11~ for ruby-i18n in the dependency line of ruby-stringex. I can try with a jessie chroot later today. Results: - cowbuilder amd64 sid chroot, ruby-i18n=0.6.11-1: still failing - cowbuilder amd64 jessie chroot, ruby-i18n=0.6.9-2: builds successfully, no test problems Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Penelope Swales: Legacy signature.asc Description: Digital Signature
Processed: Re: Bug#770194: please confirm the version of ruby-i18n
Processing control commands: tag -1 + sid Bug #770194 [src:ruby-stringex] ruby-stringex: FTBFS: Test failures Added tag(s) sid. -- 770194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770194 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#771213: mariadb-server-10.0: file conflict with mysql-client-5.5
Package: mariadb-server-10.0 Severity: serious Here's me trying to migrate from MySQL to MariaDB: Unpacking mariadb-server-10.0 (10.0.14-4) ... dpkg: error processing archive /var/cache/apt/archives/mariadb-server-10.0_10.0.14-4_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/mysql_plugin.1.gz', which is also in package mysql-client-5.5 5.5.40-1 I'll let you figure out which combination of Conflicts/Breaks/Replaces is appropriate in this case. :) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16-2-amd64 (SMP w/3 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771092: it is a general issue, not sparc-specific
Control: severity -1 grave The same problem exists on other arches too, eg here are examples of i386 and amd64: https://buildd.debian.org/status/fetch.php?pkg=qemuarch=amd64ver=2.1%2Bdfsg-8stamp=1417104870 https://buildd.debian.org/status/fetch.php?pkg=qemuarch=i386ver=2.1%2Bdfsg-8stamp=1417105060 Since this greatly affects other software building, raising severity. Thanks, /mjt -- 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#771092: it is a general issue, not sparc-specific
Processing control commands: severity -1 grave Bug #771092 [libuuid1] insighttoolkit: Build failure on sparc Severity set to 'grave' from 'serious' -- 771092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771092 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#768889: marked as done (efibootmgr: dpkg-buildpackage -b installs efibootmgr in /usr/sbin)
Your message dated Thu, 27 Nov 2014 16:33:54 + with message-id e1xu20w-0001mi...@franck.debian.org and subject line Bug#768889: fixed in efibootmgr 0.11.0-1.1 has caused the Debian Bug report #768889, regarding efibootmgr: dpkg-buildpackage -b installs efibootmgr in /usr/sbin 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.) -- 768889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: efibootmgr Version: 0.11.0-1 Severity: serious Justification: Policy 4.9 Dear Maintainer, I used dpkg-buildpackage -b to build efibootmgr and it has created efibootmgr in /usr/sbin (in addition to building the .deb package). Here's a snippet from the build log, note the Installed File line: dh_installdirs install -d debian/efibootmgr install -d debian/efibootmgr/bin dh_auto_install make -j1 install DESTDIR=/root/src/debian/efibootmgr-0.11.0/debian/efibootmgr AM_UPDATE_INFO_DIR=no make[1]: Entering directory `/root/src/debian/efibootmgr-0.11.0' Made Dir: /usr/sbin Installed File: /usr/sbin/efibootmgr make[1]: Leaving directory `/root/src/debian/efibootmgr-0.11.0' debian/rules override_dh_install make[1]: Entering directory `/root/src/debian/efibootmgr-0.11.0' dh_install cp -a ./src/efibootmgr/efibootmgr debian/efibootmgr/bin/ make[1]: Leaving directory `/root/src/debian/efibootmgr-0.11.0' -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (820, 'stable'), (600, 'unstable'), (550, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages efibootmgr depends on: ii libc6 2.19-12 ii libefivar0 0.15-2 ii libpci3 1:3.2.1-3 ii zlib1g 1:1.2.7.dfsg-13 efibootmgr recommends no packages. efibootmgr suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: efibootmgr Source-Version: 0.11.0-1.1 We believe that the bug you reported is fixed in the latest version of efibootmgr, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Bombe a...@debian.org (supplier of updated efibootmgr 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: Sat, 22 Nov 2014 15:38:43 +0100 Source: efibootmgr Binary: efibootmgr Architecture: source amd64 Version: 0.11.0-1.1 Distribution: unstable Urgency: medium Maintainer: Daniel Jared Dominguez jared_doming...@dell.com Changed-By: Andreas Bombe a...@debian.org Description: efibootmgr - Interact with the EFI Boot Manager Closes: 768889 Changes: efibootmgr (0.11.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Skip dh_auto_install, it installs binary into /usr/sbin and is not actually needed with the current packaging (Closes: 768889) Checksums-Sha1: 7002fda839d372012a3dc6b537ae2b7728e39bdf 1975 efibootmgr_0.11.0-1.1.dsc 1b50a5eb67c17a6dd46795f4abde610900b1fbf9 6316 efibootmgr_0.11.0-1.1.debian.tar.xz 12783b3904e8691e244960dd851be375f8f05c47 42936 efibootmgr_0.11.0-1.1_amd64.deb Checksums-Sha256: 1daed532f839a6078be9e6af0cf8359db956ff1e730cfdf548456bb467cbe362 1975 efibootmgr_0.11.0-1.1.dsc d934e36616c8d83626bb421976434f481c3f9415e16261d3aa7e253f9c0cd20f 6316 efibootmgr_0.11.0-1.1.debian.tar.xz 373ce9beaee86e283fa80c3f89c62aa64666f0957458b25b763d9c30fd3f98a4 42936 efibootmgr_0.11.0-1.1_amd64.deb Files: 44f1acf7b2c35f5b67e772e153aee977 1975 admin optional efibootmgr_0.11.0-1.1.dsc ba7b27e8e5a493b94c2b2113e6c92727 6316 admin optional efibootmgr_0.11.0-1.1.debian.tar.xz 49ac49f06dc040200f8ce47cf58adcd1 42936 admin optional efibootmgr_0.11.0-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUcLB/AAoJEDFkcFsdox1MKHMP/3IdBx6F/6uo1p+DHM7jJHdM K+0d8eJbG+EK69l29miskH14Zc41RXwHWBabQ3h8r1/F+eddP683KXRDrvejmJj6 bJL9bsBue/GwDeXSA5Fuz22R29w2mwRwBripRwRxqFe+JymkdOdKwY5t94HkTmuB y/FT6ZGDjF19U3fh/+4s8aYOhYlh7quM+OJL+nRa4tu7L0+Zb5DdOlMWTM3Ooumm
Bug#761306: Bug#771101: Bug#761306: Bug#771101: wheezy - jessie dist-upgrade failure when systemd is the active PID1
Am 27.11.2014 um 16:41 schrieb Michael Biebl: Am 27.11.2014 um 15:59 schrieb Michael Biebl: I would have expected, that the socket does *not* exist before systemd is re-execd, but apparently I had a file there: srw-rw-rw- 1 root root 0 Oct 10 10:41 /run/systemd/notify and no process listening on it. (don't worry about the date, it was run in a VM with a busted clock). *Some* process is triggering the creation of the notification socket and it also seems to have the wrong permissions (should be srwxrwxrwx). It's actually a bit simpler: v44 *did* already use /run/systemd/notify (with permissions srw-rw-rw-), then it was changed to use an abstract namespace and it was changed back and forth a couple of times. Maybe a simple chmod will do when upgrading from v44. Will test. Sjoerd, you mentioned in your bug report, that you upgraded from v208-v215 v208 uses an abstract socket though, so I'm not sure if it's actually the same issue. Did you maybe first upgrade from v44 to v208 and then did the dist-upgrade to v215? -- 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#768615: marked as done (ruby-pygments.rb: FTBFS in jessie: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 using debian/ruby-tests.rb...)
Your message dated Thu, 27 Nov 2014 16:49:55 +
with message-id e1xu2gr-0003jq...@franck.debian.org
and subject line Bug#768615: fixed in ruby-pygments.rb 0.5.4~ds1-1.1
has caused the Debian Bug report #768615,
regarding ruby-pygments.rb: FTBFS in jessie: ERROR: Test ruby2.1 failed:
Running tests for ruby2.1 using debian/ruby-tests.rb...
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.)
--
768615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ruby-pygments.rb
Version: 0.5.4~ds1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
Running tests for ruby2.1 using debian/ruby-tests.rb...
Run options:
# Running tests:
FE..
Finished tests in 10.040664s, 4.7806 tests/s, 9.5611 assertions/s.
1) Failure:
PygmentsHighlightTest#test_highlight_works_with_larger_files
[/«PKGBUILDDIR»/test/test_pygments.rb:35]:
454107 expected but was
455203.
2) Error:
PygmentsHighlightTest#test_highlight_works_with_single_character_input:
MentosError: Traceback (most recent call last):
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 304, in start
res = self.get_data(method, lexer, args, kwargs, text)
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 172, in get_data
res = self.highlight_text(text, lexer, formatter_name, args,
_convert_keys(opts))
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 123, in highlight_text
lexer = self.return_lexer(lexer, args, kwargs, code)
File /«PKGBUILDDIR»/lib/pygments/mentos.py, line 103, in return_lexer
return lexers.guess_lexer(code, **inputs)
File /usr/lib/python2.7/dist-packages/pygments/lexers/__init__.py, line
250, in guess_lexer
raise ClassNotFound('no lexer matching the text found')
ClassNotFound: no lexer matching the text found
/«PKGBUILDDIR»/lib/pygments/popen.rb:386:in `header_to_json'
/«PKGBUILDDIR»/lib/pygments/popen.rb:268:in `handle_header_and_return'
/«PKGBUILDDIR»/lib/pygments/popen.rb:243:in `block in mentos'
/usr/lib/ruby/2.1.0/timeout.rb:91:in `block in timeout'
/usr/lib/ruby/2.1.0/timeout.rb:35:in `block in catch'
/usr/lib/ruby/2.1.0/timeout.rb:35:in `catch'
/usr/lib/ruby/2.1.0/timeout.rb:35:in `catch'
/usr/lib/ruby/2.1.0/timeout.rb:106:in `timeout'
/«PKGBUILDDIR»/lib/pygments/popen.rb:214:in `mentos'
/«PKGBUILDDIR»/lib/pygments/popen.rb:197:in `highlight'
/«PKGBUILDDIR»/test/test_pygments.rb:91:in
`test_highlight_works_with_single_character_input'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1265:in `run'
/usr/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run'
/usr/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite'
/usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `map'
/usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite'
/usr/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites'
/usr/lib/ruby/2.1.0/test/unit.rb:661:in `each'
/usr/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites'
/usr/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run'
/usr/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run'
/usr/lib/ruby/2.1.0/test/unit.rb:27:in `run'
/usr/lib/ruby/2.1.0/test/unit.rb:780:in `run'
/usr/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in autorun'
/usr/lib/ruby/2.1.0/test/unit.rb:33:in `run_once'
/usr/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun'
48 tests, 96 assertions, 1 failures, 1 errors, 0 skips
ruby -v: ruby 2.1.4p265 (2014-10-27) [x86_64-linux-gnu]
rake aborted!
Command failed with status (2): [ruby -Ilib -rubygems
-I/usr/lib/ruby/vendor_ruby
/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/test_pygments.rb ]
Tasks: TOP = default = test
(See full trace by running task with --trace)
ERROR: Test ruby2.1 failed:
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/ruby-pygments.rb_0.5.4~ds1-1_jessie.log
A list of current common problems and possible solutions is available at
Bug#771217: ruby-libxml: FTBFS with latest libxml2
-2.1.0 -I. -I/usr/include/libxml2 -I/usr/local/include -DRUBY_EXTCONF_H=\extconf.h\ -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/x86_64-linux-gnu/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -I/usr/include/libxml2 -I/usr/local/include -o ruby_xml_parser.o -c ruby_xml_parser.c gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -I/usr/include/libxml2 -I/usr/local/include -DRUBY_EXTCONF_H=\extconf.h\ -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/x86_64-linux-gnu/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -I/usr/include/libxml2 -I/usr/local/include -o ruby_xml_schema_facet.o -c ruby_xml_schema_facet.c gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -I/usr/include/libxml2 -I/usr/local/include -DRUBY_EXTCONF_H=\extconf.h\ -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/x86_64-linux-gnu/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -I/usr/include/libxml2 -I/usr/local/include -o ruby_xml_sax_parser.o -c ruby_xml_sax_parser.c rm -f libxml_ruby.so gcc -shared -o libxml_ruby.so ruby_xml_reader.o ruby_xml_schema_type.o ruby_xml_parser_context.o ruby_xml_parser_options.o ruby_xml_namespaces.o ruby_xml_html_parser_options.o ruby_xml_html_parser_context.o ruby_xml_schema.o ruby_xml_xinclude.o ruby_xml_error.o ruby_xml.o ruby_xml_xpath_expression.o ruby_xml_encoding.o ruby_xml_relaxng.o ruby_xml_attributes.o ruby_xml_schema_element.o ruby_xml_xpointer.o ruby_xml_namespace.o ruby_xml_html_parser.o ruby_xml_xpath_object.o ruby_xml_node.o ruby_xml_dtd.o ruby_xml_sax2_handler.o ruby_xml_schema_attribute.o ruby_xml_xpath.o ruby_xml_writer.o ruby_xml_input_cbg.o ruby_xml_cbg.o libxml.o ruby_xml_attr_decl.o ruby_xml_xpath_context.o ruby_xml_attr.o ruby_xml_io.o ruby_xml_document.o ruby_xml_parser.o ruby_xml_schema_facet.o ruby_xml_sax_parser.o -L. -L/usr/lib/x86_64-linux-gnu -L/usr/lib -L. -Wl,-z,relro -L/build/ruby2.1-yik_iE/ruby2.1-2.1.4/debian/lib -fstack-protector -rdynamic -Wl,-export-dynamic-lruby-2.1 -lxml2 -lc -lz -lm -lnsl -lpthread -lgmp -ldl -lcrypt -lm -lc make[1]: Leaving directory '/«PKGBUILDDIR»/ext/libxml' make V=1 DESTDIR= install make[1]: Entering directory '/«PKGBUILDDIR»/ext/libxml' /bin/mkdir -p . ./.gem.20141127-7034-1qohq5g exit .RUBYARCHDIR.time /usr/bin/install -c -m 0755 libxml_ruby.so ./.gem.20141127-7034-1qohq5g make[1]: Leaving directory '/«PKGBUILDDIR»/ext/libxml' rm -f /«PKGBUILDDIR»/debian/ruby-libxml/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/mkmf.log Running tests for ruby2.1 using debian/ruby-tests.rb... test/unit warning: method TestNamespaces#test_namespaces is redefined Run options: # Running tests: Node#properties is deprecated. Use Node#[] instead. Warning: failed to load external entity i_dont_exist.xml. Parser.register_error_handler is deprecated. Use Error.set_handler instead /«PKGBUILDDIR»/test/tc_error.rb:150: warning: Passing no parameters to XML::Parser.new is deprecated. Pass an instance of XML::Parser::Context instead. XML::Parser#string is deprecated. Use XML::Parser.string instead XML::Parser#string is deprecated. Use XML::Parser.string instead /«PKGBUILDDIR»/test/tc_error.rb:95: warning: already initialized constant STDERR /«PKGBUILDDIR»/test/tc_error.rb:101: warning: already initialized constant STDERR /«PKGBUILDDIR»/test/tc_error.rb:95: warning: previous definition of STDERR was here /«PKGBUILDDIR»/test/tc_error.rb:79: warning: already initialized constant STDERR /«PKGBUILDDIR»/test/tc_error.rb:101: warning: previous definition of STDERR was here /«PKGBUILDDIR»/test/tc_error.rb:85: warning: already initialized constant STDERR /«PKGBUILDDIR»/test/tc_error.rb:79: warning: previous definition of STDERR was here Error: Invalid predicate. xmlXPathEval: evaluation failed FFF.33 /«PKGBUILDDIR»/test/tc_parser.rb:315: warning: Passing no parameters to XML::Parser.new is deprecated. Pass an instance of XML::Parser::Context instead. XML::Parser#document= is deprecated. Use XML::Parser.document= instead /«PKGBUILDDIR»/test/tc_parser.rb:326: warning: Passing no parameters to XML::Parser.new is deprecated. Pass an instance of XML::Parser::Context instead. XML::Parser#file is deprecated. Use XML::Parser.file instead /«PKGBUILDDIR»/test/tc_parser.rb:335: warning: Passing no parameters to XML::Parser.new is deprecated. Pass
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
In order to address this, I've proposed to replace lena.pnm with a new image, taken by me, at https://github.com/libav/libav/pull/17 I don't really care about the licensing. Is the declaration in the commit message OK? How to declare that in debian/copyright? -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768739: marked as done (sphinxcontrib-actdiag: FTBFS in jessie: unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing)
Your message dated Thu, 27 Nov 2014 17:35:02 + with message-id e1xu2y6-00012n...@franck.debian.org and subject line Bug#768739: fixed in sphinxcontrib-actdiag 0.8.0-1.1 has caused the Debian Bug report #768739, regarding sphinxcontrib-actdiag: FTBFS in jessie: unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing 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.) -- 768739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sphinxcontrib-actdiag Version: 0.8.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install sphinxcontrib-actdiag build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-sphinxcontrib-actdiag-dummy : Depends: python-sphinx-testing but it is not installable Depends: python3-sphinx-testing but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/sphinxcontrib-actdiag_0.8.0-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: sphinxcontrib-actdiag Source-Version: 0.8.0-1.1 We believe that the bug you reported is fixed in the latest version of sphinxcontrib-actdiag, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost t...@debian.org (supplier of updated sphinxcontrib-actdiag 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: Sat, 22 Nov 2014 18:05:50 +0100 Source: sphinxcontrib-actdiag Binary: python-sphinxcontrib.actdiag python3-sphinxcontrib.actdiag Architecture: source all Version: 0.8.0-1.1 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda mkou...@palmtb.net Changed-By: Tobias Frost t...@debian.org Description: python-sphinxcontrib.actdiag - Sphinx actdiag extension python3-sphinxcontrib.actdiag - Sphinx actdiag extension for Python3 Closes: 768739 Changes: sphinxcontrib-actdiag (0.8.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Disable tests for now, required depedencies are not available in Jessie: sphinx-testing, python3-sphinx-testing (Closes: #768739) Checksums-Sha1: 61dd9e02539602d5e2a20e6449b42404b1a683f1 2104 sphinxcontrib-actdiag_0.8.0-1.1.dsc 08237cc846c15f9d57a6577fed49c0c1744205b6 7064 sphinxcontrib-actdiag_0.8.0-1.1.debian.tar.xz bb01b1718ca2288693fb6234672292d71ff5b0ef 7540 python-sphinxcontrib.actdiag_0.8.0-1.1_all.deb 0250c7e13a0cc03d4ba65adc90d5fabcb4d2c665 7164 python3-sphinxcontrib.actdiag_0.8.0-1.1_all.deb Checksums-Sha256: a3a5369d53ae6f2f12769c2044dd9402842b883e327dee8fbd8f43b97b6548de 2104 sphinxcontrib-actdiag_0.8.0-1.1.dsc 22ce483d516c60ea74c0c0498b5de69fef8a3b9f58a1846cd845d656ee863260 7064
Processed: Re: Bug#771100: dependency not scrict enough: libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)
Processing control commands: severity -1 wishlist Bug #771100 [libgcrypt20] dependency not scrict enough: libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20) Severity set to 'wishlist' from 'serious' -- 771100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771100 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#771100: dependency not scrict enough: libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)
Control: severity -1 wishlist On 2014-11-26 Michael Biebl bi...@debian.org wrote: Package: libgcrypt20 Version: 1.6.2-4 Severity: serious During a wheezy to jessie dist-upgrade I get dozens if not hundreds of the following messages: systemctl: /lib/x86_64-linux-gnu/libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20 libgcrypt20 has a versioned dependency on libgpg-error0 (= 1.10) which is satisfied by the version from wheezy. [...] I assume, once the dist-upgrade has completed successfully, the error message would go away. That said, it looks like libgcrypt20 should have a stricter versioned dependency on libgpg-error0 so this error does not show up during a dist-upgrade. [...] Afaik this is a strictly cosmetic problem. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765430#30 cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768519: nautilus: Nautilus doesn't start from Favourites Applications or as regular user
Package: nautilus Followup-For: Bug #768519 Seems to be ok for me now, with 3.14.1-2. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nautilus depends on: ii desktop-file-utils 0.22-1 ii gsettings-desktop-schemas 3.14.1-1 ii gvfs 1.22.1-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libexempi3 2.2.1-2 ii libexif12 0.6.21-2 ii libgail-3-03.14.4-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libglib2.0-data2.42.0-2 ii libgnome-desktop-3-10 3.14.1-1 ii libgtk-3-0 3.14.4-2 ii libnautilus-extension1a3.14.1-2 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-01.36.8-2 ii libselinux12.3-2 ii libtracker-sparql-1.0-01.2.2-2+b1 ii libx11-6 2:1.6.2-3 ii libxml22.9.1+dfsg1-4 ii nautilus-data 3.14.1-2 ii shared-mime-info 1.3-1 Versions of packages nautilus recommends: ii eject 2.1.5+deb1+cvs20081104-13.1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-sushi3.12.0-2+b1 ii gvfs-backends 1.22.1-1 ii librsvg2-common2.40.5-1 Versions of packages nautilus suggests: ii brasero3.11.4-1 ii eog3.14.1-1 ii evince [pdf-viewer]3.14.1-1 ii totem 3.14.0-2 ii tracker1.2.2-2+b1 ii vlc [mp3-decoder] 2.2.0~rc1-1 ii vlc-nox [mp3-decoder] 2.2.0~rc1-1 ii xdg-user-dirs 0.15-2 -- 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#768768: fnonlinear: FTBFS in jessie: ERROR: a 'NAMESPACE' file is required
On 9 November 2014 at 19:19, Lucas Nussbaum wrote: | On 09/11/14 at 18:41 +0100, Lucas Nussbaum wrote: | Hi Dirk, | | On 09/11/14 at 10:00 -0600, Dirk Eddelbuettel wrote: | so all we need is to tickle an armhf rebuild. | | How does one do that again? | | I just asked on #debian-buildd. | | Hi Dirk, | | The build was triggered, so the package should build fine. However, this | doesn't make it a candidate for migration due to the freeze. | | You need to either ask the package to be unblocked (I'm not sure how | likely it is, given it's a new upstream version, but it has been waiting | for 500+ days in unstable), or see if you can make a targetted fix in | testing. The unblock was accidental as a build dependency on one small arch had a hickup. That hickup got cleared years ago too, but never bubbled over here. So now the package just got removed from testing. Oh well. Dirk | | Lucas -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@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#768708: marked as done (sphinxcontrib-nwdiag: FTBFS in jessie: unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing)
Your message dated Thu, 27 Nov 2014 18:04:08 + with message-id e1xu3qg-0004ra...@franck.debian.org and subject line Bug#768708: fixed in sphinxcontrib-nwdiag 0.9.0-1.1 has caused the Debian Bug report #768708, regarding sphinxcontrib-nwdiag: FTBFS in jessie: unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing 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.) -- 768708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sphinxcontrib-nwdiag Version: 0.9.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install sphinxcontrib-nwdiag build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-sphinxcontrib-nwdiag-dummy : Depends: python-sphinx-testing but it is not installable Depends: python3-sphinx-testing but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/sphinxcontrib-nwdiag_0.9.0-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: sphinxcontrib-nwdiag Source-Version: 0.9.0-1.1 We believe that the bug you reported is fixed in the latest version of sphinxcontrib-nwdiag, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost t...@debian.org (supplier of updated sphinxcontrib-nwdiag 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: Sat, 22 Nov 2014 18:42:30 +0100 Source: sphinxcontrib-nwdiag Binary: python-sphinxcontrib.nwdiag python3-sphinxcontrib.nwdiag Architecture: source all Version: 0.9.0-1.1 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda mkou...@palmtb.net Changed-By: Tobias Frost t...@debian.org Description: python-sphinxcontrib.nwdiag - Sphinx nwdiag extension python3-sphinxcontrib.nwdiag - Sphinx nwdiag extension for Python 3 Closes: 768708 Changes: sphinxcontrib-nwdiag (0.9.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Disable tests for now, required depedencies are not available in Jessie: sphinx-testing, python3-sphinx-testing (Closes: #768708) Checksums-Sha1: 9739afeb36946f67540b724eaec25a67ce38a06c 2094 sphinxcontrib-nwdiag_0.9.0-1.1.dsc df51bd6fe10a3cc1463c00f8ad53c590251c453d 7832 sphinxcontrib-nwdiag_0.9.0-1.1.debian.tar.xz 3f9baa11c9d00f84b65b5d691ef843279e851fef 8192 python-sphinxcontrib.nwdiag_0.9.0-1.1_all.deb af86e1cae480d94cc4a55684735e49da28e3c6db 7804 python3-sphinxcontrib.nwdiag_0.9.0-1.1_all.deb Checksums-Sha256: 1dd8780f5b74284b4a153b908856fb91b8ee032bfb903d6aed76b9769944db9e 2094 sphinxcontrib-nwdiag_0.9.0-1.1.dsc e656c40b6e78e79408a784f0f19167ce21e75f02006c43a4090bee446a11d86d 7832
Bug#768765: marked as done (sphinxcontrib-seqdiag: FTBFS in jessie: unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing)
Your message dated Thu, 27 Nov 2014 18:04:16 + with message-id e1xu3qo-0004ug...@franck.debian.org and subject line Bug#768765: fixed in sphinxcontrib-seqdiag 0.8.0-1.1 has caused the Debian Bug report #768765, regarding sphinxcontrib-seqdiag: FTBFS in jessie: unsatisfiable build-dependencies: python-sphinx-testing, python3-sphinx-testing 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.) -- 768765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sphinxcontrib-seqdiag Version: 0.8.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install sphinxcontrib-seqdiag build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-sphinxcontrib-seqdiag-dummy : Depends: python-sphinx-testing but it is not installable Depends: python3-sphinx-testing but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/sphinxcontrib-seqdiag_0.8.0-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: sphinxcontrib-seqdiag Source-Version: 0.8.0-1.1 We believe that the bug you reported is fixed in the latest version of sphinxcontrib-seqdiag, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost t...@debian.org (supplier of updated sphinxcontrib-seqdiag 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: Sat, 22 Nov 2014 18:33:23 +0100 Source: sphinxcontrib-seqdiag Binary: python-sphinxcontrib.seqdiag python3-sphinxcontrib.seqdiag Architecture: source all Version: 0.8.0-1.1 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda mkou...@palmtb.net Changed-By: Tobias Frost t...@debian.org Description: python-sphinxcontrib.seqdiag - Sphinx seqdiag extension python3-sphinxcontrib.seqdiag - Sphinx seqdiag extension for Python3 Closes: 768765 Changes: sphinxcontrib-seqdiag (0.8.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Disable tests for now, required depedencies are not available in Jessie: sphinx-testing, python3-sphinx-testing (Closes: #768765) Checksums-Sha1: f80a9741126bb537fd92d64de24927c0b2da1805 2104 sphinxcontrib-seqdiag_0.8.0-1.1.dsc 020f4aa50b0b30859ed7ec3fe34d45197747a005 7072 sphinxcontrib-seqdiag_0.8.0-1.1.debian.tar.xz 246042cebe656468567098fbc9ab705114b15789 7484 python-sphinxcontrib.seqdiag_0.8.0-1.1_all.deb bee6084fb7fd5eb025f4309f66ed462ffed78859 7094 python3-sphinxcontrib.seqdiag_0.8.0-1.1_all.deb Checksums-Sha256: f5b6596224b5f01be6ba3386c687e6a3e145785c70dc29d73ac3b0a3f1058c7b 2104 sphinxcontrib-seqdiag_0.8.0-1.1.dsc 6acbd48339db3e28cb3a90a6dc12b1487f869d2cfbed2711c3c9f7f37d99845c 7072
Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Hi Reinhard, Quoting Reinhard Tartler (2014-11-27 18:35:05) In order to address this, I've proposed to replace lena.pnm with a new image, taken by me, at https://github.com/libav/libav/pull/17 Fun idea :-) I don't really care about the licensing. Is the declaration in the commit message OK? How to declare that in debian/copyright? I might get away with such custom set of licensing terms, but to ease processing (if not by lawyers in a later dispute then at least by fellow distro maintainers wanting to categorize, identify, verify etc.) it is recommended that you instead pick a common license. Preferrably one of those tracked by SPDX as listed at https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-specification. Seems what you want is as liberal and as briefly expressed license as possible. A popular common license of that kind is Expat. ideally you refer to that license by its canonical URL http://www.jclark.com/xml/copying.txt but since you seem to seek as brief as possible expression, you could simply state e.g. Licensed under the Expat license. I am not a lawyer, just interested in licensing and pay attention to licensing patterns commonly expressed by upstreams of Debian and approved in Debian. YMMV. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#768768: fnonlinear: FTBFS in jessie: ERROR: a 'NAMESPACE' file is required
Also see Bug#718739 which is the same (earlier) issue which was correctly closed. Dirk On 9 November 2014 at 19:19, Lucas Nussbaum wrote: | On 09/11/14 at 18:41 +0100, Lucas Nussbaum wrote: | Hi Dirk, | | On 09/11/14 at 10:00 -0600, Dirk Eddelbuettel wrote: | so all we need is to tickle an armhf rebuild. | | How does one do that again? | | I just asked on #debian-buildd. | | Hi Dirk, | | The build was triggered, so the package should build fine. However, this | doesn't make it a candidate for migration due to the freeze. | | You need to either ask the package to be unblocked (I'm not sure how | likely it is, given it's a new upstream version, but it has been waiting | for 500+ days in unstable), or see if you can make a targetted fix in | testing. | | Lucas -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@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#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
On Thu, Nov 27, 2014 at 1:08 PM, Jonas Smedegaard d...@jones.dk wrote: Hi Reinhard, Quoting Reinhard Tartler (2014-11-27 18:35:05) In order to address this, I've proposed to replace lena.pnm with a new image, taken by me, at https://github.com/libav/libav/pull/17 Fun idea :-) I don't really care about the licensing. Is the declaration in the commit message OK? How to declare that in debian/copyright? I might get away with such custom set of licensing terms, but to ease processing (if not by lawyers in a later dispute then at least by fellow distro maintainers wanting to categorize, identify, verify etc.) it is recommended that you instead pick a common license. Preferrably one of those tracked by SPDX as listed at https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-specification. Seems what you want is as liberal and as briefly expressed license as possible. A popular common license of that kind is Expat. ideally you refer to that license by its canonical URL http://www.jclark.com/xml/copying.txt but since you seem to seek as brief as possible expression, you could simply state e.g. Licensed under the Expat license. I am not a lawyer, just interested in licensing and pay attention to licensing patterns commonly expressed by upstreams of Debian and approved in Debian. YMMV. Sure, if you believe that the expat license is appropriate, I'd license it that way. Thanks for the feedback. Reinhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770670: marked as done (libsdl2-dev - SDL.h includes altivec.h, breaks c++ code)
Your message dated Thu, 27 Nov 2014 18:34:23 + with message-id e1xu3tx-hc...@franck.debian.org and subject line Bug#770670: fixed in libsdl2 2.0.2+dfsg1-6 has caused the Debian Bug report #770670, regarding libsdl2-dev - SDL.h includes altivec.h, breaks c++ code 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.) -- 770670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: g++ Version: 4.9.2-2 Severity: normal Hi, I'm trying to solve the build failure of my package vcmi on ppc64el: https://buildd.debian.org/status/fetch.php?pkg=vcmiarch=ppc64elver=0.97%2Bdfsg-2stamp=1416356066 The issue seems to only appear when compiling with c++. It does not happen when compiling with clang++. Thus I'm reporting this bug against g++. Please reassign if this was the wrong conclusion. The relevant first error message is: [ 68%] Building CXX object AI/StupidAI/CMakeFiles/StupidAI.dir/main.cpp.o cd /«BUILDDIR»/vcmi-0.97+dfsg/build/AI/StupidAI /usr/bin/c++ -DFL_CPP11 -DM_BIN_DIR=\/usr/games\ -DM_DATA_DIR=\/usr/share/vcmi\ -DM_LIB_DIR=\/usr/lib/powerpc64le-linux-gnu/vcmi\ -DStupidAI_EXPORTS -DUSE_SYSTEM_MINIZIP -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -std=c++0x -Wall -Wextra -Wpointer-arith -Wno-strict-aliasing -Wno-switch -Wno-sign-compare -Wno-unused-local-typedefs -Wno-unused-parameter -Wuninitialized -Wno-overloaded-virtual -Wno-type-limits -fvisibility=hidden -O2 -g -DNDEBUG -fPIC -I/«BUILDDIR»/vcmi-0.97+dfsg -I/«BUILDDIR»/vcmi-0.97+dfsg/AI/StupidAI -I/«BUILDDIR»/vcmi-0.97+dfsg/lib -Winvalid-pch -include /«BUILDDIR»/vcmi-0.97+dfsg/build/AI/StupidAI/cotire/StupidAI_CXX_prefix.hxx -o CMakeFiles/StupidAI.dir/main.cpp.o -c /«BUILDDIR»/vcmi-0.97+dfsg/AI/StupidAI/main.cpp /«BUILDDIR»/vcmi-0.97+dfsg/client/mapHandler.h:32:7: error: expected unqualified-id before '__attribute__' std::vector std::pairconst CGObjectInstance*,SDL_Rect objects; //pointers to objects being on this tile with rects to be easier to blit this tile on screen ^ This only happens on ppc64el. I was able to track this issue down to a combination of including SDL.h, using std::vector and compiling with -std=c++0x. In the following I will post some code and how I compile it and the results on ppc64el (on the left) and amd64 (on the right). Test 1 == $ cat test.cc #include SDL.h #include vector std::vectorint foo; $ c++ -I/usr/include/SDL2 -c test.cc ppc64el | amd64 ---|--- success | success Test 2 == $ cat test.cc #include SDL.h #include vector std::vectorint foo; $ c++ -std=c++0x -I/usr/include/SDL2 -c test.cc ppc64el | amd64 ---|--- (failure log attached)| success Test 3 == $ cat test.cc #include SDL.h std::vectorint foo; $ c++ -std=c++0x -I/usr/include/SDL2 -c test.cc ppc64el | amd64 ---|--- test.cc:4:6: error: expected | test.cc:4:6: error: ‘vector’ in unqualified-id before ‘__attribute__’ | namespace ‘std’ does not name a std::vectorint foo;| template type ^ | Test 4 == $ cat test.cc #include SDL.h #include vector std::vectorint foo; $ clang++ -std=c++0x -I/usr/include/SDL2 -c test.cc ppc64el | amd64 ---|--- success | success The error in test 3 is what I see on ppc64el in the build log entry above. It is probably just due to a missing #include vector. But as you can see, even if I #include vector I get an error as you can see in test 2. It only seems to compile fine on ppc64el if I do not pass -std=c++0x (test 1) or if one uses clang++ (test 4). One lead that I have is the following. When compiling on ppc64el with g++ and -std=c++0x, then the line: std::vectorint foo gets turned into std::__attribute__((altivec(vector__)))int foo by the preprocessor (I checked with g++ -E). This does not happen on amd64. It does also not happen with clang on either architecture. It does also not happen without passing -std=c++0x.
Bug#771071: marked as done ([cyrus-imapd-2.4] Missing separator breaks configure parameters)
Your message dated Thu, 27 Nov 2014 18:34:13 + with message-id e1xu3tn-dj...@franck.debian.org and subject line Bug#771071: fixed in cyrus-imapd-2.4 2.4.17+caldav~beta10-9 has caused the Debian Bug report #771071, regarding [cyrus-imapd-2.4] Missing separator breaks configure parameters 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.) -- 771071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cyrus-imapd-2.4 Version: 2.4.16-4+deb7u2 Severity: critical Tags: patch Dear Cyrus-Imapd maintainers, While looking for the reason why this version was using logging LOCAL6 as its logging facility, I came across an issue introduced on the parameters passed at configuring stage in which an order is missing a backslash, which breaks the configure line on several parameters, between others user/group of the cyrus daemon. Please find suitable applying this patch ASAP and requesting Release-Team a freeze exception: Thanks a lot for your work and keep the great work flowing! Cheers, Dererk -- BOFH excuse #59: failed trials, system needs redesigned diff -ruN cyrus-imapd-2.4-2.4.17+caldav~beta10/debian/rules cyrus-imapd-2.4-2.4.17+caldav~beta10-new/debian/rules --- cyrus-imapd-2.4-2.4.17+caldav~beta10/debian/rules 2014-11-18 10:37:11.0 -0300 +++ cyrus-imapd-2.4-2.4.17+caldav~beta10-new/debian/rules 2014-11-26 11:32:22.092151370 -0300 @@ -93,7 +93,7 @@ --enable-idled \ --enable-http \ --with-opendkim-libdir=/usr/include/opendkim \ - --with-opendkim-incdir=/usr/lib + --with-opendkim-incdir=/usr/lib \ --with-cyrus-user=cyrus --with-cyrus-group=mail \ --with-com_err= \ --with-pidfile=/var/run/cyrmaster.pid \ ---End Message--- ---BeginMessage--- Source: cyrus-imapd-2.4 Source-Version: 2.4.17+caldav~beta10-9 We believe that the bug you reported is fixed in the latest version of cyrus-imapd-2.4, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated cyrus-imapd-2.4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Nov 2014 09:28:43 +0100 Source: cyrus-imapd-2.4 Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder cyrus-replication cyrus-nntpd cyrus-caldav cyrus-clients cyrus-dev libcyrus-imap-perl cyrus-common-2.4 cyrus-doc-2.4 cyrus-imapd-2.4 cyrus-pop3d-2.4 cyrus-admin-2.4 cyrus-murder-2.4 cyrus-replication-2.4 cyrus-nntpd-2.4 cyrus-caldav-2.4 cyrus-clients-2.4 cyrus-dev-2.4 libcyrus-imap-perl24 Architecture: source amd64 all Version: 2.4.17+caldav~beta10-9 Distribution: unstable Urgency: medium Maintainer: Debian Cyrus Team pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: cyrus-admin - Cyrus mail system - administration tools cyrus-admin-2.4 - Cyrus mail system - administration tools [dummy package] cyrus-caldav - Cyrus mail system - CalDAV and CardDAV support cyrus-caldav-2.4 - Cyrus mail system - CalDAV and CardDAV support [dummy package] cyrus-clients - Cyrus mail system - test clients cyrus-clients-2.4 - Cyrus mail system - test clients [dummy package] cyrus-common - Cyrus mail system - common files cyrus-common-2.4 - Cyrus mail system - common files [dummy package] cyrus-dev - Cyrus mail system - developer files cyrus-dev-2.4 - Cyrus mail system - developer files [dummy package] cyrus-doc - Cyrus mail system - documentation files cyrus-doc-2.4 - Cyrus mail system - documentation files [dummy package] cyrus-imapd - Cyrus mail system - IMAP support cyrus-imapd-2.4 - Cyrus mail system - IMAP support [dummy package] cyrus-murder - Cyrus mail system - proxies and aggregator cyrus-murder-2.4 - Cyrus mail system - proxies and aggregator [dummy package] cyrus-nntpd - Cyrus mail system - NNTP support cyrus-nntpd-2.4 - Cyrus mail system - NNTP support [dummy package] cyrus-pop3d - Cyrus mail system - POP3 support cyrus-pop3d-2.4 - Cyrus mail system - POP3 support [dummy package] cyrus-replication -
Bug#771226: gcc-arm-linux-gnueabihf: Currently uninstallable
Source: gcc-arm-linux-gnueabihf Version: 4.9.2-2 Severity: serious Justification: Not installable Hello wookey, gcc-arm-linux-gnueabihf depends on gcc-4.9-arm-linux-gnueabihf which in turn: $ grep-aptavail -P -X -s Version,Depends gcc-4.9-arm-linux-gnueabihf Version: 4.9.2-2 Depends: cpp-4.9-arm-linux-gnueabihf (= 4.9.2-2), binutils-arm-linux-gnueabihf (= 2.24.90.2014), libgcc-4.9-dev:armhf (= 4.9.2-2), libc6 (= 2.14), libcloog-isl4 (= 0.17), libgmp10 (= 2:5.0.1~), libisl10 (= 0.10), libmpc3, libmpfr4 (= 3.1.2), zlib1g (= 1:1.1.4) wants libgcc-4.9-dev:armhf (= 4.9.2-2). Currently available however is only 4.9.1-19 in jessie and 4.9.2-3 in sid. https://qa.debian.org/excuses.php?package=cross-gcc-4.9-armhf knows still a few more unsatisfiable Depends (which I guess should all be fixed in a single new upload that bumps to 4.9.2-3). Other cross-gcc packages suffer the same problem, e.g. https://qa.debian.org/excuses.php?package=cross-gcc-4.9-mips https://qa.debian.org/excuses.php?package=cross-gcc-4.9-powerpc Best regards Uwe -- System Information: Debian Release: jessie/sid APT prefers proposed-updates APT policy: (900, 'proposed-updates'), (900, 'oldstable-updates'), (900, 'oldstable-proposed-updates'), (900, 'stable'), (900, 'oldstable'), (800, 'testing-proposed-updates'), (800, 'testing'), (700, 'unstable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armel mipsel mips Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768690: marked as done (latex-mk: FTBFS in jessie: build-dependency not installable: tgif)
Your message dated Thu, 27 Nov 2014 19:48:46 + with message-id e1xu53w-00013l...@franck.debian.org and subject line Bug#768690: fixed in latex-mk 2.1-1.3 has caused the Debian Bug report #768690, regarding latex-mk: FTBFS in jessie: build-dependency not installable: tgif 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.) -- 768690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: latex-mk Version: 2.1-1.2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install latex-mk build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-latex-mk-dummy : Depends: tgif but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/latex-mk_2.1-1.2_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: latex-mk Source-Version: 2.1-1.3 We believe that the bug you reported is fixed in the latest version of latex-mk, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tomasz Buchert tomasz.buch...@inria.fr (supplier of updated latex-mk 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: Sat, 22 Nov 2014 18:14:45 +0100 Source: latex-mk Binary: latex-mk Architecture: source all Version: 2.1-1.3 Distribution: unstable Urgency: medium Maintainer: Wences Arana ara...@debian.org.gt Changed-By: Tomasz Buchert tomasz.buch...@inria.fr Description: latex-mk - tool for managing LaTeX projects Closes: 768690 Changes: latex-mk (2.1-1.3) unstable; urgency=medium . * Non-maintainer upload. * Disable support and dependency on tgif (Closes: #768690) Checksums-Sha1: d43b64a8941229d6c5f4b4ca9f0244d27da08b3c 1988 latex-mk_2.1-1.3.dsc 6d13b2f6430deaea83ec257e88bcaca0815f6d90 9324 latex-mk_2.1-1.3.debian.tar.xz 551089afd5a871844aa07dd68e8e7ca129cc3164 281124 latex-mk_2.1-1.3_all.deb Checksums-Sha256: b29a5ffc813481bdc11153cccbff9491845dc10e1841948650524010c9c9d632 1988 latex-mk_2.1-1.3.dsc 925a2df4dc454e9cf24eb9f1936e6a1a68ec3b8d9c68f0d71c7e4ef3058f30ad 9324 latex-mk_2.1-1.3.debian.tar.xz 62e4e7eb0c3fe68f8aa17361cd811b3b8cf67c47b58957f3afe695d44067cb2a 281124 latex-mk_2.1-1.3_all.deb Files: 92c63e88749aa7ee67aa23a8a750971a 1988 tex optional latex-mk_2.1-1.3.dsc f78935fab8ad5dfe29aaa51f0f99291f 9324 tex optional latex-mk_2.1-1.3.debian.tar.xz e1c241809b82b764ef0f31dce074250d 281124 tex optional latex-mk_2.1-1.3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUcOMxAAoJEJFk+h0XvV02AwkQAL9FL64ffdqweyG5Wszopqp5 5gSk05ClIFNYpLDyoL5IOQ5vx0VWYKmNgGH2M44Du9J89HAfLziJ9gZWso73Z5YQ VnDr8qUng//arm9oGVQhX+ymytOTKq0cNFR0KBmdFgY1WQoNRYftFpZPiuRbShUo 1npIOHnCXnx9R/WASSHTLMloUnVP8tVY1B9AQN5EBuG+cep4sq84iuB8ELk0p3UJ
Bug#767504: [Pkg-mpd-maintainers] Bug#767504: mpd: licence clash with libmp4v2 (MPL) and mpd GPL-+2
On Sun, 02 Nov 2014 at 21:10:16 +0100, Florian Schlichting wrote: I'll prepare an upload disabling libmp4v2 in the next few days. I see this change has been sitting in pkg-mpd git since then. Would it be helpful for me to test and upload it? I would like mpd to not be hit with the autoremoval hammer :-) I know you wanted to get 0.19.2 in but did not get a freeze exception. There seem to be a couple of targeted fixes for Severity:important bugs which could be cherry-picked and included in an upload, but only if it happens within the next week. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot
On Thu, Nov 27, 2014 at 10:38:06AM +, Simon McVittie wrote: I think this is a cryptsetup bug. The attached patch solves my test-case in a virtual machine. I confirm that this also fixes things for me on a real system. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770425: Dependencies
Seems that the only new dep in 4.0.1 (besides the themes, which should probably be re-merged if taking this route) is on ca-certificates. In a pbuilder vanilla wheezy chroot, just installed current stable wordpress, then replaced with the built version and 3 themes using dpkg. Only extra package needed was ca-certificates. Which, obviously, is in stable. Craig - if you're going to do the work on backporting the fixes, you might also consider the likelihood of there being further such fixes required during the stable security support window. In this case already, the delay in getting a fixed version into the archive is probably long enough for these issues to be being exploited. Is there any reason to think we'd be able to be quicker next time? Cheers, Nick -- Nick Phillips / n...@debian.org / 03 479 4195 # These statements are mine, not those of the University of Otago
Bug#762984: Alert! /dev/vg0/usr does not exist
* Simon McVittie s...@debian.org [2014-11-27 11:51 +]: On Wed, 01 Oct 2014 at 22:18:53 +0100, Ben Hutchings wrote: I suspect this is essentially the same bug as #616689 and #678696, except that now it may affect mounting /usr as well as /. I think this bug report is actually describing more than one bug in more than one package that have similar symptoms. There might be things that can be fixed in mdadm and lvm2 to fix the initramfs-tools/0.117 regressions without needing to implement a full event-driven setup in initramfs-tools. RAID (Elimar, Sven) Elimar Riesebieter's System 2 has a bunch of mdadm (RAID) partitions. Elimar, what is in your /etc/default/mdadm on System 2 (and System 1 for that matter)? I predict that the answer includes something like INITRDSTART=/dev/md6. Right, adding root and usr raid partitions to INITRDSTART like INITRDSTART='/dev/md3 /dev/md5' or just 'all' does the job. There is no need to involve initramfs to mount /usr before init. [...] LVM (Elimar's System 1, Sven, Torsten, IOhannes, Javier) In the LVM case, debian/initramfs-tools/lvm2/scripts/local-top does this: activate_vg $ROOT activate_vg $resume Note the lack of handling for /usr here. Further, activate_vg uses lvm lvchange to activate only the LV necessary for the root filesystem; if /usr is on a separate VG, it's not going to work. This on its own would be enough to make Sven Hartge's system fail: /usr needs a LVM partition activated that / does not. Similarly, I think Elimar's System 1 is going to activate vg0/root but not vg0/usr. Right! We don't have enough information in this bug report to know what layout Torsten, IOhannes, Javier used on their systems, but we can guess from the fact that vgchange -a y is a successful workaround... I predict that these are LVM over either a single RAID array, or real partitions. The ideal thing in both of these situations would be to use the same logic as *mounting* /usr - mount the rootfs first, then read its fstab to find out where /usr is, avoiding hard-coding that knowledge into the initramfs - but I think that would need a significantly more complicated hook structure. Perhaps modifying mdadm and lvm2 so they will set up enough md/lvm bits for /usr in the initramfs would be sufficient for a 95% solution? What do you propose to adapt it to lvm2? Why should we avoid hardcoding via /etc/initramfs-tools/scripts? Maybe a move from /usr/share/initramfs-tools/scripts/local-top/lvm2 to /lib/initramfs-tools/scripts/local-top/lvm2 should work? Elimar -- Learned men are the cisterns of knowledge, not the fountainheads ;-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 771226 to gcc-arm-linux-gnueabifh
Processing commands for cont...@bugs.debian.org: reassign 771226 gcc-arm-linux-gnueabifh 4.9.2-2 Bug #771226 [src:gcc-arm-linux-gnueabihf] gcc-arm-linux-gnueabihf: Currently uninstallable Warning: Unknown package 'src:gcc-arm-linux-gnueabihf' Bug reassigned from package 'src:gcc-arm-linux-gnueabihf' to 'gcc-arm-linux-gnueabifh'. Warning: Unknown package 'gcc-arm-linux-gnueabifh' Warning: Unknown package 'gcc-arm-linux-gnueabifh' No longer marked as found in versions gcc-arm-linux-gnueabihf/4.9.2-2. Warning: Unknown package 'gcc-arm-linux-gnueabifh' Warning: Unknown package 'gcc-arm-linux-gnueabifh' Ignoring request to alter fixed versions of bug #771226 to the same values previously set Warning: Unknown package 'gcc-arm-linux-gnueabifh' Bug #771226 [gcc-arm-linux-gnueabifh] gcc-arm-linux-gnueabihf: Currently uninstallable Warning: Unknown package 'gcc-arm-linux-gnueabifh' There is no source info for the package 'gcc-arm-linux-gnueabifh' at version '4.9.2-2' with architecture '' Unable to make a source version for version '4.9.2-2' Marked as found in versions 4.9.2-2. Warning: Unknown package 'gcc-arm-linux-gnueabifh' thanks Stopping processing here. Please contact me if you need assistance. -- 771226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771226 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: limit source to gns3, tagging 771135
Processing commands for cont...@bugs.debian.org: #gns3 (0.8.7-2) unstable; urgency=medium # # * Do not install files needed by the program to /usr/share/doc #(Closes: #771135) # limit source gns3 Limiting to bugs with field 'source' containing at least one of 'gns3' Limit currently set to 'source':'gns3' tags 771135 + pending Bug #771135 [gns3] gns3: postinst uses /usr/share/doc content (Policy 12.3) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 771135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771135 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
