Bug#755157: marked as done (gst-plugins-bad1.0: FTBFS: unsatisfiable build-dependency: libbluetooth-dev ( 5))
Your message dated Mon, 21 Jul 2014 07:33:49 + with message-id e1x986x-0003aq...@franck.debian.org and subject line Bug#755157: fixed in gst-plugins-bad1.0 1.4.0-1 has caused the Debian Bug report #755157, regarding gst-plugins-bad1.0: FTBFS: unsatisfiable build-dependency: libbluetooth-dev ( 5) 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.) -- 755157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gst-plugins-bad1.0 Version: 1.2.4-1 Severity: serious Justification: FTBFS libbluetooth-dev is provided as ver. 5.21-1 on sid, so unsatisfiable build-dependency libbluetooth-dev ( 5). Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC ---End Message--- ---BeginMessage--- Source: gst-plugins-bad1.0 Source-Version: 1.4.0-1 We believe that the bug you reported is fixed in the latest version of gst-plugins-bad1.0, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Dröge sl...@debian.org (supplier of updated gst-plugins-bad1.0 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, 19 Jul 2014 17:22:10 +0200 Source: gst-plugins-bad1.0 Binary: gstreamer1.0-plugins-bad-doc gstreamer1.0-plugins-bad gstreamer1.0-plugins-bad-dbg libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-bad1.0-dev Architecture: source all amd64 Version: 1.4.0-1 Distribution: unstable Urgency: medium Maintainer: Maintainers of GStreamer packages pkg-gstreamer-maintain...@lists.alioth.debian.org Changed-By: Sebastian Dröge sl...@debian.org Description: gstreamer1.0-plugins-bad - GStreamer plugins from the bad set gstreamer1.0-plugins-bad-dbg - GStreamer plugins from the bad set (debug symbols) gstreamer1.0-plugins-bad-doc - GStreamer documentation for plugins from the bad set libgstreamer-plugins-bad1.0-0 - GStreamer development files for libraries from the bad set libgstreamer-plugins-bad1.0-dev - GStreamer development files for libraries from the bad set Closes: 755157 Changes: gst-plugins-bad1.0 (1.4.0-1) unstable; urgency=medium . * New upstream stable release. * debian/rules: + Disable bluez plugin for now until someone ports it to bluez5 (Closes: #755157). Checksums-Sha1: 1fb6c0c7e19ed427dbe48f3b24f35c2be9d5f6df 4426 gst-plugins-bad1.0_1.4.0-1.dsc ccd014f90c3a0418a114e6ed4e73776c4392492e 3797420 gst-plugins-bad1.0_1.4.0.orig.tar.xz 9d35917e64f09afa8dbdd5160ccf835602a0b460 31740 gst-plugins-bad1.0_1.4.0-1.debian.tar.xz b5a11e600274b5d5a8a401d54b590d62d696f54c 1222350 gstreamer1.0-plugins-bad-doc_1.4.0-1_all.deb 5feca03238acb4662042a9982b7b95cfd9338f55 2342366 gstreamer1.0-plugins-bad_1.4.0-1_amd64.deb 11d9f4f9a2bfb6fada739260dd2709fb0b2cc549 6663742 gstreamer1.0-plugins-bad-dbg_1.4.0-1_amd64.deb 69a55b1245d8ac496c93016740a7eab927fb8538 1312148 libgstreamer-plugins-bad1.0-0_1.4.0-1_amd64.deb 9515844de4e0404933a7641ac5e960d98d3608fb 1096494 libgstreamer-plugins-bad1.0-dev_1.4.0-1_amd64.deb Checksums-Sha256: 6a0817f1fa0fad90bf661826116ad6707703ffa25e388ecb1e694bded5a21386 4426 gst-plugins-bad1.0_1.4.0-1.dsc ff2cb754f7725b205aec66002b1406e440f3a03194b6cad2d126ef5cd00902f9 3797420 gst-plugins-bad1.0_1.4.0.orig.tar.xz 7344e4d0857a361c7fc0e47698e0914dbdf2faf7a4a44f969bb1d882fd1c6ccd 31740 gst-plugins-bad1.0_1.4.0-1.debian.tar.xz 86326d96ef38ed632a146015a51d197e8f186b326e073ef304dab046be0e6728 1222350 gstreamer1.0-plugins-bad-doc_1.4.0-1_all.deb 873608343e8aceeebfd3784ec53507fd4e50b3705e2aecdb9c7798a0bf5f4128 2342366 gstreamer1.0-plugins-bad_1.4.0-1_amd64.deb 0478c2331f4356c04ee2e09df4bbb7522c1d79058ff1519ec8273fb0f844af48 6663742 gstreamer1.0-plugins-bad-dbg_1.4.0-1_amd64.deb 7e85cd0546797e02e2a956cb1a0f0c0c468dce4de3ac3a98543f4e0fcf4fc2d5 1312148 libgstreamer-plugins-bad1.0-0_1.4.0-1_amd64.deb d56ae003cb7a76390d1f87a99dc41815f8c45b07c0d47abbf52ff39eaf915a24 1096494 libgstreamer-plugins-bad1.0-dev_1.4.0-1_amd64.deb Files: 7abc0d11a8ffa32c834a1d40ed3b3980 1222350 doc extra gstreamer1.0-plugins-bad-doc_1.4.0-1_all.deb
Bug#755467: [nvidia-legacy-304xx-driver] Does not start the video driver since the last update 304.123-1
Package: nvidia-legacy-304xx-driver Severity: grave --- Please enter the report below this line. --- Hello maintainer, After the last update of the driver, it is not working. I had to uninstall it completely and use the nouveau driver. Which output you need to verify the problem? Kindly, Davide Governale. --- System information. --- Architecture: i386 Kernel: Linux 3.14-1-686-pae Debian Release: jessie/sid 500 unstablewww.deb-multimedia.org 500 unstableftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== libgl1-nvidia-legacy-304xx-glx (= 304.123-1) | 304.123-1 xserver-xorg-video-nvidia-legacy-304xx (= 304.123-1) | 304.123-1 nvidia-legacy-304xx-alternative (= 304.123-1) | 304.123-1 nvidia-legacy-304xx-kernel-dkms(= 304.123-1) | OR nvidia-legacy-304xx-kernel-304.123| nvidia-support| 20131102+1 Recommends(Version) | Installed ===-+-=== nvidia-settings-legacy-304xx| 304.123-1 Suggests (Version) | Installed ===-+-== nvidia-legacy-304xx-kernel-dkms (= 304.123) | OR nvidia-legacy-304xx-kernel-source (= 304.123) | signature.asc Description: PGP signature
Bug#750643: antlr: missing licence for PyANTLR
On Sat, 19 Jul 2014, Terence Parr wrote: Here you go :) http://www.antlr2.org/license.html Thanks, wonderful! I really appreciate you taking the time for this. Now we have this statement and Wolfgang’s (who “only” needs to decide on which BSD variants and GPL versions he wants), which removes every _possible_ legal issue, so everyone involved can *finally* go back to hacking, which, I am sure, we all prefer over dealing with licences ☺ bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753402: gosh segfaults on s390x causing libguess to FTBFS
Hello, On Mon, 14 Jul 2014 17:52:15 +0200 Aurelien Jarno aurel...@aurel32.net wrote: The problem is once again the infamous setjmp/longjmp ABI breakage on s390x [1]. Simply rebuilding gauche would fix the problem, but I am not sure it is the best way to deal with it. So, anything new on this? This blocks libguess from migrating to testing, which blocks audacious from migrating too. -- Cheers, Andrew signature.asc Description: PGP signature
Bug#753402: gosh segfaults on s390x causing libguess to FTBFS
On 21/07/14 10:01, Andrew Shadura wrote: Hello, On Mon, 14 Jul 2014 17:52:15 +0200 Aurelien Jarno aurel...@aurel32.net wrote: The problem is once again the infamous setjmp/longjmp ABI breakage on s390x [1]. Simply rebuilding gauche would fix the problem, but I am not sure it is the best way to deal with it. So, anything new on this? This blocks libguess from migrating to testing, which blocks audacious from migrating too. audacious has an uncoordinated transition as well... https://release.debian.org/transitions/html/auto-audacious.html Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748326: gnome-session: Can't login after after locked screen
Hi, Stephen Allen wrote (16 Jul 2014 22:06:35 GMT) : I'm happy to report that this bug (on my laptop) seems to be fixed. To sum up, both reporters tell us that this bug is fixed: * one by installing systemd-sysv: before closing this bug, maybe it's worth investigating what part of the dependency chain is missing, especially given the shim will apparently be reintroduced relatively soon; * the other without indication of any change; presumably by completing the upgrade to GNOME 3.12, I guess; nothing to worry about. Also, I'm wondering if this bug should be reassigned to gnome-shell or gdm3, perhaps. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 707240 to gnustep-games: no longer installable in sid since shisen.app has been removed from sid
Processing commands for cont...@bugs.debian.org: retitle 707240 gnustep-games: no longer installable in sid since shisen.app has been removed from sid Bug #707240 [gnustep-games] shisen.app is going to be removed from the archive Changed Bug title to 'gnustep-games: no longer installable in sid since shisen.app has been removed from sid' from 'shisen.app is going to be removed from the archive' thanks Stopping processing here. Please contact me if you need assistance. -- 707240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707240 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#755478: libmrpt-base1.0: not installable in sid, needs migration to libavcodec55
Package: libmrpt-base1.0 Version: 1:1.0.2-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hello, libmrpt-base1.0 is not installable in sid on any of the architecture where it exsists. This is the case since at least 2014-04-05: Architectures: mipsel Version: 1:1.0.0-1 No package matches the dependency libavcodec53 (= 6:0.8.3-1~) | libavcodec-extra-53 (= 6:0.8.5) of package libmrpt-base1.0 (=1:1.0.0-1) Architectures: powerpc, s390x Version: 1:1.0.2-1 No package matches the dependency libavcodec54 (= 6:9.1-1) | libavcodec-extra-54 (= 6:9.8) of package libmrpt-base1.0 (=1:1.0.2-1) Architectures: mips Version: 1:1.0.1-1 No package matches the dependency libavcodec53 (= 6:0.8.3-1~) | libavcodec-extra-53 (= 6:0.8.7) of package libmrpt-base1.0 (=1:1.0.1-1) This package should migrate to libavcodec55. Cheers -Ralf. -- 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#755439: pcre3: DFA matching behaviour changed, breaking glib2.0 tests
Processing commands for cont...@bugs.debian.org: retitle 755439 pcre3: DFA matching behaviour changed, breaking glib2.0 tests Bug #755439 [src:glib2.0] glib2.0: likely future FTBFS with pcre3/8.35: TEST_MATCH_ALL* regex tests fail Changed Bug title to 'pcre3: DFA matching behaviour changed, breaking glib2.0 tests' from 'glib2.0: likely future FTBFS with pcre3/8.35: TEST_MATCH_ALL* regex tests fail' reassign 755439 libpcre3,glib2.0 Bug #755439 [src:glib2.0] pcre3: DFA matching behaviour changed, breaking glib2.0 tests Bug reassigned from package 'src:glib2.0' to 'libpcre3,glib2.0'. No longer marked as found in versions glib2.0/2.40.0-3. Ignoring request to alter fixed versions of bug #755439 to the same values previously set found 755439 pcre3/8.35-2,glib2.0/2.40.0-3 Bug #755439 [libpcre3,glib2.0] pcre3: DFA matching behaviour changed, breaking glib2.0 tests The source pcre3 and version 8.35-2 do not appear to match any binary packages Marked as found in versions pcre3/8.35-2 and glib2.0/2.40.0-3. forwarded 755439 http://bugs.exim.org/show_bug.cgi?id=1504,https://bugzilla.gnome.org/show_bug.cgi?id=733325 Bug #755439 [libpcre3,glib2.0] pcre3: DFA matching behaviour changed, breaking glib2.0 tests Changed Bug forwarded-to-address to 'http://bugs.exim.org/show_bug.cgi?id=1504,https://bugzilla.gnome.org/show_bug.cgi?id=733325' from 'https://bugzilla.gnome.org/show_bug.cgi?id=733325' severity 755439 serious Bug #755439 [libpcre3,glib2.0] pcre3: DFA matching behaviour changed, breaking glib2.0 tests Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 755439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755439 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#755478: libmrpt-base1.0: not installable in sid, needs migration to libavcodec55
Hi and thanks for noticing, A newer version of the package (1.2.1) was uploaded recently to Debian mentors [1] which hopefully fixes all build errors in those archs. I already let my mentor (José Luis Redejo, jredr...@debian.org) know about it, so I expect the new package to be uploaded soon. Best, JL [1] http://mentors.debian.net/package/mrpt On Mon, Jul 21, 2014 at 11:02 AM, Ralf Treinen trei...@pps.univ-paris-diderot.fr wrote: Package: libmrpt-base1.0 Version: 1:1.0.2-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hello, libmrpt-base1.0 is not installable in sid on any of the architecture where it exsists. This is the case since at least 2014-04-05: Architectures: mipsel Version: 1:1.0.0-1 No package matches the dependency libavcodec53 (= 6:0.8.3-1~) | libavcodec-extra-53 (= 6:0.8.5) of package libmrpt-base1.0 (=1:1.0.0-1) Architectures: powerpc, s390x Version: 1:1.0.2-1 No package matches the dependency libavcodec54 (= 6:9.1-1) | libavcodec-extra-54 (= 6:9.8) of package libmrpt-base1.0 (=1:1.0.2-1) Architectures: mips Version: 1:1.0.1-1 No package matches the dependency libavcodec53 (= 6:0.8.3-1~) | libavcodec-extra-53 (= 6:0.8.7) of package libmrpt-base1.0 (=1:1.0.1-1) This package should migrate to libavcodec55. Cheers -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754754: jq: FTBFS on s390x: test suite timeout
Hello, the same error is noticed for other big endian architectures like mips and powerpc. This patch from upstream fixes this issue for me on mips. https://github.com/stedolan/jq/commit/20e629284f94e0c8a14e8425309c913b6ee5b280 The patch is attached. Could you please consider including this patch. Best Regards, Dejandiff -uNr jq-1.4.orig/configure.ac jq-1.4/configure.ac --- jq-1.4.orig/configure.ac 2014-07-18 15:29:28.0 + +++ jq-1.4/configure.ac 2014-07-18 14:37:53.0 + @@ -96,6 +96,12 @@ fi AC_MSG_RESULT($have___thread) +AC_C_BIGENDIAN( + AC_DEFINE([IEEE_MC68k], 1, [machine is bigendian]), + AC_DEFINE([IEEE_8087], 1, [machine is littleendian]), + AC_MSG_ERROR(unknown endianess), + AC_MSG_ERROR(universial endianess not supported) +) AC_SUBST([BUNDLER], [$bundle_cmd]) diff -uNr jq-1.4.orig/jv_dtoa.c jq-1.4/jv_dtoa.c --- jq-1.4.orig/jv_dtoa.c 2014-06-19 23:31:18.0 + +++ jq-1.4/jv_dtoa.c 2014-07-18 14:38:17.0 + @@ -187,7 +187,6 @@ * used for input more than STRTOD_DIGLIM digits long (default 40). */ -#define IEEE_8087 #define NO_ERRNO #define NO_HEX_FP #define No_Hex_NaN
Bug#718139: marked as done (zeroc-icee-translators: FTBFS: Trying patch debian/patches/10-add-common-flags.patch at level 1 ... 0 ... 2 ... failure.)
Your message dated Mon, 21 Jul 2014 09:36:12 + with message-id e1x9a0y-000405...@franck.debian.org and subject line Bug#718139: fixed in zeroc-icee-translators 1.2.0-6.1 has caused the Debian Bug report #718139, regarding zeroc-icee-translators: FTBFS: Trying patch debian/patches/10-add-common-flags.patch at level 1 ... 0 ... 2 ... failure. 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.) -- 718139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: zeroc-icee-translators Version: 1.2.0-6 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130726 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' /usr/share/cdbs/1/rules/simple-patchsys.mk:31: WARNING: simple-patchsys.mk is deprecated - please use source format 3.0 (quilt) instead make[1]: Nothing to be done for `reverse-config'. make[1]: Leaving directory `/«PKGBUILDDIR»' if [ debian/stamp-patched = reverse-patches ]; then rm -f debian/stamp-patched; fi patches: debian/patches/10-add-common-flags.patch debian/patches/10-endian-limits.patch debian/patches/10-gcc4.3-compilation.patch debian/patches/20-kfreebsd-config.patch Trying patch debian/patches/10-add-common-flags.patch at level 1 ... 0 ... 2 ... failure. make: *** [debian/stamp-patched] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/07/26/zeroc-icee-translators_1.2.0-6_unstable.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: zeroc-icee-translators Source-Version: 1.2.0-6.1 We believe that the bug you reported is fixed in the latest version of zeroc-icee-translators, 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 718...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su s...@debian.org (supplier of updated zeroc-icee-translators 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: Mon, 21 Jul 2014 08:57:28 + Source: zeroc-icee-translators Binary: icee-translators Architecture: source amd64 Version: 1.2.0-6.1 Distribution: unstable Urgency: medium Maintainer: Francisco Moya p...@debian.org Changed-By: YunQiang Su s...@debian.org Description: icee-translators - ZeroC IceE Slice translators for C++ and Java Closes: 718139 Changes: zeroc-icee-translators (1.2.0-6.1) unstable; urgency=medium . [10-add-common-flags.patch] * patch config/Make.rules.Linux only, as config/Make.rules.GNU config/Make.rules.GNU_kFreeBSD is symlink (Closes: #718139). Checksums-Sha1: d4d5e585dde09e50770f7018b85f54cac7cfe6a0 1451 zeroc-icee-translators_1.2.0-6.1.dsc 23095f9f0fac717089331f3ac9bb9f8488a136fc 7063 zeroc-icee-translators_1.2.0-6.1.diff.gz 4cae53a5ff050117e36d1ecac3fe7be96b2c5df6 422912 icee-translators_1.2.0-6.1_amd64.deb Checksums-Sha256: dcd95801a8a6dcfcf7d2607a98cb3517ee0ea21c364521507cf09d99ba6b8030 1451 zeroc-icee-translators_1.2.0-6.1.dsc fa48f7814315b78a92c6a403d48fca50df7e74dbde67a9266e3a3264a49bb9b6 7063 zeroc-icee-translators_1.2.0-6.1.diff.gz 3c3d47485f72e94eecbd2536e7ca46d91b55fb271148e3b6d63f72659609bb75 422912 icee-translators_1.2.0-6.1_amd64.deb Files: b1627dc4d17d987c682098141d72a932 422912 devel optional icee-translators_1.2.0-6.1_amd64.deb b3a345c4da093dd7e138a0fd8eec21d2 1451 devel optional zeroc-icee-translators_1.2.0-6.1.dsc e0ac196af06e5d826e8d152f0c6edc06 7063 devel optional zeroc-icee-translators_1.2.0-6.1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTzNxYAAoJECVrfCskLhmeBV0IALeWbGOBpodGDTUClDUVsqHu
Bug#741761: marked as done (zssh: FTBFS: completion.c:56:40: error: 'CPPFunction' undeclared (first use in this function))
Your message dated Mon, 21 Jul 2014 09:36:18 + with message-id e1x9a14-00043p...@franck.debian.org and subject line Bug#741761: fixed in zssh 1.5c.debian.1-3.2 has caused the Debian Bug report #741761, regarding zssh: FTBFS: completion.c:56:40: error: 'CPPFunction' undeclared (first use in this function) 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.) -- 741761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: zssh Version: 1.5c.debian.1-3.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140315 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. On new readline versions old-style function typedefs have been deprecated. Relevant part (hopefully): gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wall -DHAVE_CONFIG_H -D_FORTIFY_SOURCE=2 -c -o completion.o completion.c completion.c: In function 'initialize_readline': completion.c:56:40: error: 'CPPFunction' undeclared (first use in this function) rl_attempted_completion_function = (CPPFunction *) zssh_completion; ^ completion.c:56:40: note: each undeclared identifier is reported only once for each function it appears in completion.c:56:53: error: expected expression before ')' token rl_attempted_completion_function = (CPPFunction *) zssh_completion; ^ make[1]: *** [completion.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/03/15/zssh_1.5c.debian.1-3.1_unstable.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: zssh Source-Version: 1.5c.debian.1-3.2 We believe that the bug you reported is fixed in the latest version of zssh, 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 741...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su s...@debian.org (supplier of updated zssh 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: Mon, 21 Jul 2014 08:22:29 + Source: zssh Binary: zssh Architecture: source amd64 Version: 1.5c.debian.1-3.2 Distribution: unstable Urgency: medium Maintainer: Ben Wong b...@wongs.net Changed-By: YunQiang Su s...@debian.org Description: zssh - interactive file transfers over ssh Closes: 741761 Changes: zssh (1.5c.debian.1-3.2) unstable; urgency=medium . * Non-maintainer upload. * Use format 3 quilt. * Replace CPPFunction with rl_completion_func_t (Closes: #741761). Checksums-Sha1: a6e5de42b36a331c2bbb92f1ab0b3b2b2d81dbb0 1388 zssh_1.5c.debian.1-3.2.dsc 106cfe889ca2bddae91e8a895a1e07be2a80228b 4764 zssh_1.5c.debian.1-3.2.debian.tar.xz c08160d398051e4be134b4be3b441f1f8e396bbb 21806 zssh_1.5c.debian.1-3.2_amd64.deb Checksums-Sha256: 65e9ed1940ebbebf0de87948f5653315ea078243c12e482bdb693fd18b9cbf8c 1388 zssh_1.5c.debian.1-3.2.dsc c2ce134b197d69c3b850e89f0891b9e61a6b0727d427aa2aa1494ac900aadc99 4764 zssh_1.5c.debian.1-3.2.debian.tar.xz 10aea1c43071ce1dfb0a4b947040dd5f4d710d0f3234c77bd2c3dfddfac36541 21806 zssh_1.5c.debian.1-3.2_amd64.deb Files: 7a8de359c54a58ce43e0bab10d536fe2 21806 net optional zssh_1.5c.debian.1-3.2_amd64.deb 95d811c359d23c026420b05d0f720c71 1388 net optional zssh_1.5c.debian.1-3.2.dsc 16caf47c5b08bb92a79ee9c02c6ee1ad 4764 net optional zssh_1.5c.debian.1-3.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTzNDyAAoJECVrfCskLhmeda8H/3Au/vrbJdb0CWkdmQc2IYH1 84ghzUO8wR2XBNJW9sxdwWiICDsPXu1k8qSkcxY7yf1P+7XRLEr0/MVWqkTVH4Kf jM36ljJ1g4pSh4EVZJz7YKVwbkew8st3GQW2j6aDHi0xUF3NQiMKT4/DXhdT0yMI
Bug#755484: Unfulfillable dependency on libgtkspell-3-0
Source: libgwibber-gtk2 Version: 3.5.2-1 Severity: serious The dependency should be on libgtkspell3-3-0, not libgtkspell-3-0. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Processed: NMU debdiff for jq_1.4-2.1
Processing control commands: tags -1 + pending Bug #754754 [src:jq] jq: FTBFS on s390x: test suite timeout Added tag(s) pending. -- 754754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754754 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#754754: NMU debdiff for jq_1.4-2.1
Control: tags -1 + pending Hello Simon, At Imagination Technologies (http://imgtec.com/) Dejan Latinovic has found a solution to Debian bug #754754. https://bugs.debian.org/754754 My NMU debdiff for jq_1.4-2.1 is below, at the end of this message. With the changes in the NMU debdiff, jq builds successfully on mips, mipsel and amd64. Regards, Aníbal -- Aníbal Monsalve Salazar anibal.monsalvesala...@imgtec.com debdiff jq_1.4-2.dsc jq_1.4-2.1.dsc diff -Nru jq-1.4/debian/changelog jq-1.4/debian/changelog --- jq-1.4/debian/changelog 2014-07-06 01:18:20.0 +0100 +++ jq-1.4/debian/changelog 2014-07-21 07:53:57.0 +0100 @@ -1,3 +1,14 @@ +jq (1.4-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Restore the 1.3-1.1 NMU changelog. + * Fix FTBFS on big endian architectures. +Add big-endian-fix.patch. +Patch by Dejan Latinovic dejan.latino...@imgtec.com. +Closes: #754754. + + -- Anibal Monsalve Salazar ani...@debian.org Mon, 21 Jul 2014 07:42:05 +0100 + jq (1.4-2) unstable; urgency=medium * Set valgrind build-dep to amd64 i386 only (Closes: #752529) @@ -14,6 +25,14 @@ -- Simon Elsbrock si...@iodev.org Sun, 22 Jun 2014 20:49:15 +0200 +jq (1.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Remove build dependency on valgrind on archs where the valgrind +tests are disabled. (Closes: #729138) + + -- Christian Hofstaedtler z...@debian.org Thu, 13 Feb 2014 13:30:29 +0100 + jq (1.3-1) unstable; urgency=low * New upstream release. (Closes: #725118) diff -Nru jq-1.4/debian/patches/big-endian-fix.patch jq-1.4/debian/patches/big-endian-fix.patch --- jq-1.4/debian/patches/big-endian-fix.patch 1970-01-01 01:00:00.0 +0100 +++ jq-1.4/debian/patches/big-endian-fix.patch 2014-07-21 07:40:03.0 +0100 @@ -0,0 +1,42 @@ +Date: Fri, 18 Jul 2014 16:47:47 +0100 +From: Dejan Latinovic dejan.latino...@imgtec.com +Subject: fix big endian for jq + +https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754754 + +package jq FTBFS for mips and other BE architectures. + +This patch from upstream fixes this issue for me. +https://github.com/stedolan/jq/commit/20e629284f94e0c8a14e8425309c913b6ee5b280 + +The patch is attached. + +Index: jq-1.4/configure.ac +=== +--- jq-1.4.orig/configure.ac jq-1.4/configure.ac +@@ -96,6 +96,12 @@ if test $have___thread = yes; then + fi + AC_MSG_RESULT($have___thread) + ++AC_C_BIGENDIAN( ++ AC_DEFINE([IEEE_MC68k], 1, [machine is bigendian]), ++ AC_DEFINE([IEEE_8087], 1, [machine is littleendian]), ++ AC_MSG_ERROR(unknown endianess), ++ AC_MSG_ERROR(universial endianess not supported) ++) + + AC_SUBST([BUNDLER], [$bundle_cmd]) + +Index: jq-1.4/jv_dtoa.c +=== +--- jq-1.4.orig/jv_dtoa.c jq-1.4/jv_dtoa.c +@@ -187,7 +187,6 @@ + *used for input more than STRTOD_DIGLIM digits long (default 40). + */ + +-#define IEEE_8087 + #define NO_ERRNO + #define NO_HEX_FP + #define No_Hex_NaN diff -Nru jq-1.4/debian/patches/series jq-1.4/debian/patches/series --- jq-1.4/debian/patches/series2014-06-22 21:36:53.0 +0100 +++ jq-1.4/debian/patches/series2014-07-21 07:34:21.0 +0100 @@ -3,3 +3,4 @@ remove-unecessary-rakefile-deps.patch patch-version-into-build.patch disable-shared-lib.patch +big-endian-fix.patch signature.asc Description: Digital signature
Bug#755333: [pkg-eucalyptus-maintainers] Bug#755333: wsdl2c: FTBFS: [javac] /«PKGBUILDDIR»/src/org/apache/axis2/builder/MultipartFormDataBuilder.java:28: error: package javax.servlet.http does not
Hello everybody,
I received a bug report that the wsdl2c package started to fail to build from
source (see below).
On my side, I could confirm that indeed, after upgrading my machine to the
latest Sid, it also failed to build locally, while before the upgrade it did
not give a problem.
I am not sure what to do. Is that due to some transition ? Shall I just wait
and try again in a couple of weeks ?
(The VCS URL of the package is svn+ssh://svn.debian.org/svn/svn/pkg-eucalyptus)
Have a nice day,
-- Charles Plessy, Tsurumi, Kanagawa, Japan
Le Sat, Jul 19, 2014 at 08:34:02PM +0200, David Suárez a écrit :
Source: wsdl2c
Version: 0.1-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140718 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
debian/rules build
test -x debian/rules
mkdir -p .
cd . /usr/lib/jvm/default-java/bin/java -classpath
/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/commons-logging.jar:/usr/share/java/wsdl4j.jar:/usr/share/java/backport-util-concurrent.jar:/usr/share/java/gnumail.jar:/usr/share/java/httpcore.jar:/usr/share/java/jaxen.jar:/usr/share/java/commons-fileupload.jar:/usr/share/java/commons-cli.jar:/usr/share/java/geronimo-jms_1.1_spec.jar:/usr/share/java/commons-httpclient.jar:/usr/share/java/httpcore-nio.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true
-Dcompile.optimize=true -buildfile build.xml
Buildfile: /«PKGBUILDDIR»/build.xml
compile:
[mkdir] Created dir: /«PKGBUILDDIR»/build
[mkdir] Created dir: /«PKGBUILDDIR»/build/classes
[javac] /«PKGBUILDDIR»/build.xml:9: warning: 'includeantruntime' was
not set, defaulting to build.sysclasspath=last; set to false for repeatable
builds
[javac] Compiling 1665 source files to /«PKGBUILDDIR»/build/classes
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/builder/MultipartFormDataBuilder.java:28:
error: package javax.servlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/builder/MultipartFormDataBuilder.java:79:
error: cannot find symbol
[javac] private MultipleEntryHashMap
getParameterMap(HttpServletRequest request,
[javac] ^
[javac] symbol: class HttpServletRequest
[javac] location: class MultipartFormDataBuilder
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/deployment/WarBasedAxisConfigurator.java:35:
error: package javax.servlet does not exist
[javac] import javax.servlet.ServletConfig;
[javac] ^
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/deployment/WarBasedAxisConfigurator.java:54:
error: cannot find symbol
[javac] private ServletConfig config;
[javac] ^
[javac] symbol: class ServletConfig
[javac] location: class WarBasedAxisConfigurator
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/deployment/WarBasedAxisConfigurator.java:95:
error: cannot find symbol
[javac] public WarBasedAxisConfigurator(ServletConfig
servletConfig) throws DeploymentException {
[javac] ^
[javac] symbol: class ServletConfig
[javac] location: class WarBasedAxisConfigurator
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/transport/http/AbstractAgent.java:27:
error: package javax.servlet does not exist
[javac] import javax.servlet.ServletException;
[javac] ^
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/transport/http/AbstractAgent.java:28:
error: package javax.servlet.http does not exist
[javac] import javax.servlet.http.HttpServletRequest;
[javac] ^
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/transport/http/AbstractAgent.java:29:
error: package javax.servlet.http does not exist
[javac] import javax.servlet.http.HttpServletResponse;
[javac] ^
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/transport/http/AbstractAgent.java:55:
error: cannot find symbol
[javac] public void handle(HttpServletRequest httpServletRequest,
[javac]^
[javac] symbol: class HttpServletRequest
[javac] location: class AbstractAgent
[javac]
/«PKGBUILDDIR»/src/org/apache/axis2/transport/http/AbstractAgent.java:56:
error: cannot find symbol
[javac]HttpServletResponse httpServletResponse)
[javac]^
[javac] symbol: class HttpServletResponse
[javac] location: class AbstractAgent
[javac]
Processed (with 1 errors): Re: NMU debdiff for jq_1.4-2.1
Processing commands for cont...@bugs.debian.org: tags 754754 + patch + fixedupstream Unknown tag/s: fixedupstream. 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 etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore. Bug #754754 [src:jq] jq: FTBFS on s390x: test suite timeout Added tag(s) patch. Bug #754754 [src:jq] jq: FTBFS on s390x: test suite timeout Requested to add no tags; doing nothing. stop Stopping processing here. Please contact me if you need assistance. -- 754754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754754 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: NMU debdiff for jq_1.4-2.1
Processing commands for cont...@bugs.debian.org: tags 754754 + fixed-upstream Bug #754754 [src:jq] jq: FTBFS on s390x: test suite timeout Added tag(s) fixed-upstream. stop Stopping processing here. Please contact me if you need assistance. -- 754754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754754 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#755462: Fails to build
Package: nvidia-legacy-304xx-kernel-source Version: 304.123-1 Followup-For: Bug #755462 I confirm the bug. Thanks, Marco -- Package-specific info: uname -a: Linux baudolino 3.14-1-amd64 #1 SMP Debian 3.14.12-1 (2014-07-11) x86_64 GNU/Linux /proc/version: Linux version 3.14-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-4) ) #1 SMP Debian 3.14.12-1 (2014-07-11) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:81f2] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at fd00 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at d000 (64-bit, prefetchable) [size=256M] Region 3: Memory at fc00 (64-bit, non-prefetchable) [size=16M] Expansion ROM at fe9e [disabled] [size=128K] Capabilities: access denied dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.00] Console: colour VGA+ 80x25 [0.149289] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.149289] vgaarb: loaded [0.149289] vgaarb: bridge control possible :01:00.0 [0.270182] Linux agpgart interface v0.103 OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Jul 21 11:02 /etc/alternatives/glx - /usr/lib/nvidia lrwxrwxrwx 1 root root 41 Jul 21 11:02 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 41 Jul 21 11:02 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jul 21 11:02 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Jul 21 11:02 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 49 Jul 21 11:02 /etc/alternatives/glx--libXvMCNVIDIA.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 51 Jul 21 11:02 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 57 Jul 21 11:02 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 59 Jul 21 11:02 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 49 Jul 21 11:02 /etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 51 Jul 21 11:02 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Jul 21 11:02 /etc/alternatives/glx--linux-libglx.so - /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Jul 21 11:02 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf - /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Jul 21 11:02 /etc/alternatives/glx--nvidia-bug-report.sh - /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Jul 21 11:02 /etc/alternatives/glx--nvidia_drv.so - /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 28 Jul 21 10:59 /etc/alternatives/nvidia - /usr/lib/nvidia/legacy-304xx lrwxrwxrwx 1 root root 54 Jul 21 10:59 /etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 54 Jul 21 10:59 /etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 56 Jul 21 10:59 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 56 Jul 21 10:59 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.1 lrwxrwxrwx 1 root root 62 Jul 21 10:59 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-i386-linux-gnu - /usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 64 Jul 21 10:59 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 70 Jul 21 10:59 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-i386-linux-gnu -
Bug#748326: marked as done (gnome-session: Can't login after after locked screen)
Your message dated Mon, 21 Jul 2014 12:28:50 +0200 with message-id 53cceb62.8010...@debian.org and subject line Re: Bug#748326: systemd-sysv has caused the Debian Bug report #748326, regarding gnome-session: Can't login after after locked screen 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.) -- 748326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-session Version: 3.12.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, After i clicked on «Lock screen» if i wan't unlock my computer, i type my password but nothing happening. No error message. Only field for password become empty and my computer stay lock. If i want use my computer, i need to use configuration file to auto login my user so i need to reboot each time after locked screen. Thank you, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 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 gnome-session depends on: ii gnome-session-bin 3.12.1-2 ii gnome-session-common 3.12.1-2 ii gnome-settings-daemon 3.12.1-3 ii gnome-shell3.12.1-3 Versions of packages gnome-session recommends: ii systemd 204-8 Versions of packages gnome-session suggests: ii desktop-base 7.0.3 ii gnome-keyring 3.10.1-1 ii gnome-user-guide 3.8.2-1 -- no debconf information ---End Message--- ---BeginMessage--- On 19/05/14 14:17, Alexandre Russo wrote: I installed systemd-sysv and my problem was fixed. Ok good. In the meantime we have added some dependencies such as on libpam-systemd, so this should be fixed. Emilio---End Message---
Bug#755490: please update to build from the gcc 4.9.1 tarball
Package: src:gnat-4.9 Version: 4.9.0-2 Severity: serious Tags: sid jessie Please update gnat-4.9 to build from the gcc-4.9 4.9.1 sources. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755462: Same console_lock problem
I do get a similar build error on 3.16.0-rc5. The previous module version built fine on the same kernel. It seems that some post of the console_lock detection is broken. If not resolved within a few days I will try to look deeper into the problem.
Bug#755059: I can confirm this bug also
Dear Maintainer, I confirm this bug also. This package couldn't be installed without using unstable packages. I get the exact same output with Fabien. Many Thanks, -Engin
Bug#754715: Debian claims source missing for rgl
On 19 July 2014 at 22:28, Dirk Eddelbuettel wrote: | | On 19 July 2014 at 20:43, Duncan Murdoch wrote: | | On 19/07/2014, 7:18 PM, Dirk Eddelbuettel wrote: | | | | On 19 July 2014 at 17:48, Duncan Murdoch wrote: | | | On 19/07/2014, 2:52 PM, Bastien ROUCARIES wrote: | | | On Sat, Jul 19, 2014 at 4:11 PM, Dirk Eddelbuettel e...@debian.org wrote: | | | Duncan, | | | | | | The Debian package linter claims that the included file | | | | | | inst/WebGL/CanvasMatrix.js | | | | | | in your rgl package lacks source code. | | | | | | I know next to nothing about Javascript, and to me Javascript always appeared | | | to _be_ source code. | | | No ti is minified javascript, not source code. You lose comments and | | | variable name. | | | | | | It's a compiled Javascript file -- minified, as Bastien says. The | | | docs describe where to get the original source, and have a copy of the | | | copyright notice. It's a very commonly included file in WebGL pages. | | | | | | I'd rather not include the source, as it is redundant, and easily | | | available elsewhere. | | | | The powers-that-be and sticklers within Debian may then throw it out of the archive. | | | | I don't really care too much about including the source, but I | | definitely can't remove the compiled version. Is it sufficient to | | have both? | | Yes, I am asked to provide the source in the sources we use for building. | | Sorry if I was unclear, I was _not_ asking you to replace the minimized | source with the full source, but the source for everything Policy wants the | source along with the version you deploy :-/ That said, the problem is of course more between me and the Debian packaging (unless CRAN eventually follows suit and also asks for source on .js; I am not suggesting they do). Do you have a canonical URL for a source of that file CanvasMatrix.js ? Dirk | Dirk | | | Duncan | | | | | | Dirk | | | | | | | | Duncan Murdoch | | | The GNU file tool seems to agree | | | | | | edd@max:~/src/debian/CRAN/rgl-0.93.1098$ file inst/WebGL/CanvasMatrix.js | | | inst/WebGL/CanvasMatrix.js: ASCII text, with very long lines | | | edd@max:~/src/debian/CRAN/rgl-0.93.1098$ | | | | | | Do you have a good answer? | | | | | | I am CCing the (to me at least somewhat overzealous) Debian colleague who | | | filed this; maybe he has added insights. I am also ccing the bug report for | | | process; records are at http://bugs.debian.org/754715 | | | | | | Dirk | | | | | | -- | | | http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org | | | | | | | | | -- | http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- 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#746825: ACE FTBFS status
Hi, As the Debian diagnostics maintainer I'm also affected by this issue. I cannot necessarily offer to spend a great deal of time on ACE packaging, but I'm certainly willing to help as much as I can. If this bug cannot be fixed on time for jessie, I'll have to disable ACE in diagnostics after all :-( Best, Michael pgp6YCDPeQjjA.pgp Description: PGP signature
Bug#755498: elilo: Add a Built-Using field for gnu-efi
Package: elilo
Severity: serious
Justification: Policy 7.8
Your package build-depends against gnu-efi. As such, the produced
binary package incorporates code from the static library gnu-efi
provides.
Policy 7.8 specifies that a package must list all packages incorporated
during the build.
I applied the following patch to gummiboot which was also affected by
this, you can use that as a starting point.
You also want to make sure not to build against gnu-efi ( 3.0v-5~),
as the older 3.0v versions are broken.
diff --git a/debian/control b/debian/control
index 061d24c..cb046be 100644
--- a/debian/control
+++ b/debian/control
@@ -12,6 +12,7 @@ Homepage: http://freedesktop.org/wiki/Software/gummiboot/
Package: gummiboot
Architecture: i386 amd64 x32 ia64
Depends: ${misc:Depends}, ${shlibs:Depends}
+Built-Using: ${misc:Built-Using}
Pre-Depends: systemd
Multi-Arch: foreign
Description: Simple UEFI bootloader
diff --git a/debian/rules b/debian/rules
index d367029..a98c06e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,3 +4,7 @@
override_dh_auto_configure:
dh_auto_configure -- --disable-silent-rules
+
+override_dh_gencontrol:
+ dh_gencontrol -- -Vmisc:Built-Using=$(shell dpkg-query -W \
+ -f='$${source:Package} (= $${source:Version})' gnu-efi)
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (980, 'unstable'), (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 Netiquette.
- If you don't I might ignore you.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755500: refit: Add a Built-Using field for gnu-efi
Package: refit
Severity: serious
Justification: Policy 7.8
Your package build-depends against gnu-efi. As such, the produced
binary package incorporates code from the static library gnu-efi
provides.
Policy 7.8 specifies that a package must list all packages incorporated
during the build.
I applied the following patch to gummiboot which was also affected by
this, you can use that as a starting point.
You also want to make sure not to build against gnu-efi ( 3.0v-5~),
as the older 3.0v versions are broken.
diff --git a/debian/control b/debian/control
index 061d24c..cb046be 100644
--- a/debian/control
+++ b/debian/control
@@ -12,6 +12,7 @@ Homepage: http://freedesktop.org/wiki/Software/gummiboot/
Package: gummiboot
Architecture: i386 amd64 x32 ia64
Depends: ${misc:Depends}, ${shlibs:Depends}
+Built-Using: ${misc:Built-Using}
Pre-Depends: systemd
Multi-Arch: foreign
Description: Simple UEFI bootloader
diff --git a/debian/rules b/debian/rules
index d367029..a98c06e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,3 +4,7 @@
override_dh_auto_configure:
dh_auto_configure -- --disable-silent-rules
+
+override_dh_gencontrol:
+ dh_gencontrol -- -Vmisc:Built-Using=$(shell dpkg-query -W \
+ -f='$${source:Package} (= $${source:Version})' gnu-efi)
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (980, 'unstable'), (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 Netiquette.
- If you don't I might ignore you.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 755317 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=97372
Processing commands for cont...@bugs.debian.org: forwarded 755317 https://rt.cpan.org/Public/Bug/Display.html?id=97372 Bug #755317 [src:libnet-bonjour-perl] libnet-bonjour-perl: FTBFS: Tests failures Changed Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=97372' from 'https://rt.cpan.org/Ticket/Display.html?id=97361' thanks Stopping processing here. Please contact me if you need assistance. -- 755317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755317 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#755317: libnet-bonjour-perl: FTBFS: Tests failures
HI gregor, On Sun, Jul 20, 2014, at 14:39, gregor herrmann wrote: Control: tag -1 + confirmed On Sat, 19 Jul 2014 20:44:36 +0200, David Suárez wrote: Source: libnet-bonjour-perl Version: 0.96-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/1-use.t . ok Use of uninitialized value in uc at /«PKGBUILDDIR»/blib/lib/Net/Bonjour/Entry.pm line 272. Use of uninitialized value $_[4] in join or string at /usr/lib/perl5/Net/DNS/RR.pm line 69. Use of uninitialized value $argument in concatenation (.) or string at /usr/lib/perl5/Net/DNS/RR/.pm line 75. in new Net::DNS::RR( type ttl 3600 address name server.local ... ) at /«PKGBUILDDIR»/blib/lib/Net/Bonjour/Entry.pm line 327. # Looks like you planned 18 tests but ran 15. # Looks like your test exited with 255 just after 15. t/2-entry.t ... Dubious, test returned 255 (wstat 65280, 0xff00) Failed 3/18 subtests Breakage by recent Net::DNS? I would guess so, there were some packages using undocumented internal APIs in Net::DNS that got cleaned up. I will forward this to upstream, but I think this needs to get fixed in libnet-bounjour-perl. O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 755317 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=97372,https://rt.cpan.org/Public/Bug/Display.html?id=97361
Processing commands for cont...@bugs.debian.org: forwarded 755317 https://rt.cpan.org/Public/Bug/Display.html?id=97372,https://rt.cpan.org/Public/Bug/Display.html?id=97361 Bug #755317 [src:libnet-bonjour-perl] libnet-bonjour-perl: FTBFS: Tests failures Changed Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=97372,https://rt.cpan.org/Public/Bug/Display.html?id=97361' from 'https://rt.cpan.org/Public/Bug/Display.html?id=97372' thanks Stopping processing here. Please contact me if you need assistance. -- 755317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755317 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#738122: nut: riello_usb fills up /var/log filesystem
El sáb, 19-07-2014 a las 14:39 +0200, Laurent Bigonville escribió: Hello all, Hello all there Noel, are you still able to reproduce this? Do you have the same issue with the version currently in testing (2.6.5-4)? Could you please attach here the ups.conf file. What kernel version are you running? root@host:~# uname -a Linux host 3.14-1-amd64 #1 SMP Debian 3.14.10-1 (2014-07-07) x86_64 GNU/Linux root@host:~# cat /etc/nut/ups.conf | grep -v ^# [riello] driver = riello_usb port = auto #vendorid = 04b4 #productid = 5500 desc = Riello iDialog IDG1200 root@host:~# lsusb |grep 04b4 Bus 005 Device 005: ID 04b4:5500 Cypress Semiconductor Corp. HID-COM RS232 Adapter The UPS is a Riello IDG1200. NUT's page indicates that the driver is riello_usb This driver is not available in Wheezy's nut-server 2.6.4-2.3+deb7u1 This driver is not available in Jessie's nut-server 2.6.5-4 This driver is available only in Sid's nut-server 2.7.2-1 Using 2.7.2-1 /var/log/syslog grow 368MiB in the 20 seconds between these: root@host:/etc/rc2.d# service nut-server restart [ ok ] Restarting NUT - power devices information server and drivers: upsd driver(s) driver(s). upsd. root@host:/etc/rc2.d# service nut-server stop [ ok ] Stopping NUT - power devices information server and drivers: upsd driver(s). root@host:/etc/rc2.d# @Arnaud: This bug prevents the latest version of the package from migrating to testing and I can reproduce it myself and as you said on the upstream bug the code should be used by all the other drivers as well. So I'm thinking about reducing the severity of the bug to important. Any thoughts? Laurent Bigonville Thanks for getting in touch about this. The resume of the above is that yes, the issue is reproducible for me using nut-server 2.7.2-1 and I can not use the driver in other versions because it is not there. Many thanks Noel er Envite signature.asc Description: This is a digitally signed message part
Bug#738122: nut: riello_usb fills up /var/log filesystem
El sáb, 19-07-2014 a las 14:39 +0200, Laurent Bigonville escribió: Hello all, Hello all there Noel, are you still able to reproduce this? Do you have the same issue with the version currently in testing (2.6.5-4)? Could you please attach here the ups.conf file. What kernel version are you running? root@host:~# uname -a Linux host 3.14-1-amd64 #1 SMP Debian 3.14.10-1 (2014-07-07) x86_64 GNU/Linux root@host:~# cat /etc/nut/ups.conf | grep -v ^# [riello] driver = riello_usb port = auto #vendorid = 04b4 #productid = 5500 desc = Riello iDialog IDG1200 root@host:~# lsusb |grep 04b4 Bus 005 Device 005: ID 04b4:5500 Cypress Semiconductor Corp. HID-COM RS232 Adapter The UPS is a Riello IDG1200. NUT's page indicates that the driver is riello_usb This driver is not available in Wheezy's nut-server 2.6.4-2.3+deb7u1 This driver is not available in Jessie's nut-server 2.6.5-4 This driver is available only in Sid's nut-server 2.7.2-1 Using 2.7.2-1 /var/log/syslog grow 368MiB in the 20 seconds between these: root@host:/etc/rc2.d# service nut-server restart [ ok ] Restarting NUT - power devices information server and drivers: upsd driver(s) driver(s). upsd. root@host:/etc/rc2.d# service nut-server stop [ ok ] Stopping NUT - power devices information server and drivers: upsd driver(s). root@host:/etc/rc2.d# @Arnaud: This bug prevents the latest version of the package from migrating to testing and I can reproduce it myself and as you said on the upstream bug the code should be used by all the other drivers as well. So I'm thinking about reducing the severity of the bug to important. Any thoughts? Laurent Bigonville Thanks for getting in touch about this. The resume of the above is that yes, the issue is reproducible for me using nut-server 2.7.2-1 and I can not use the driver in other versions because it is not there. Many thanks Noel er Envite signature.asc Description: This is a digitally signed message part
Bug#754715: Debian claims source missing for rgl
On 21/07/2014, 6:21 AM, Dirk Eddelbuettel wrote: On 19 July 2014 at 22:28, Dirk Eddelbuettel wrote: | | On 19 July 2014 at 20:43, Duncan Murdoch wrote: | | On 19/07/2014, 7:18 PM, Dirk Eddelbuettel wrote: | | | | On 19 July 2014 at 17:48, Duncan Murdoch wrote: | | | On 19/07/2014, 2:52 PM, Bastien ROUCARIES wrote: | | | On Sat, Jul 19, 2014 at 4:11 PM, Dirk Eddelbuettel e...@debian.org wrote: | | | Duncan, | | | | | | The Debian package linter claims that the included file | | | | | | inst/WebGL/CanvasMatrix.js | | | | | | in your rgl package lacks source code. | | | | | | I know next to nothing about Javascript, and to me Javascript always appeared | | | to _be_ source code. | | | No ti is minified javascript, not source code. You lose comments and | | | variable name. | | | | | | It's a compiled Javascript file -- minified, as Bastien says. The | | | docs describe where to get the original source, and have a copy of the | | | copyright notice. It's a very commonly included file in WebGL pages. | | | | | | I'd rather not include the source, as it is redundant, and easily | | | available elsewhere. | | | | The powers-that-be and sticklers within Debian may then throw it out of the archive. | | | | I don't really care too much about including the source, but I | | definitely can't remove the compiled version. Is it sufficient to | | have both? | | Yes, I am asked to provide the source in the sources we use for building. | | Sorry if I was unclear, I was _not_ asking you to replace the minimized | source with the full source, but the source for everything Policy wants the | source along with the version you deploy :-/ That said, the problem is of course more between me and the Debian packaging (unless CRAN eventually follows suit and also asks for source on .js; I am not suggesting they do). Do you have a canonical URL for a source of that file CanvasMatrix.js ? I've added the source file to the package on R-forge. Unfortunately, it's currently in an unstable state (a segfault on OSX), so I can't push this change to CRAN yet. Once I track down that bug and I'm happy it's stable again, I'll let you know. If you want to put in a link to the file before that, this one should work: https://r-forge.r-project.org/scm/viewvc.php/pkg/rgl/inst/WebGL/CanvasMatrix.src.js?root=rglview=log I can't guarantee that R-forge won't change its location, but the rgl/inst/WebGL/CanvasMatrix.src.js part should be stable. Duncan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722035: marked as done (ffgtk: FTBFS agains evolution-data-server 3.8)
Your message dated Mon, 21 Jul 2014 12:25:54 + with message-id e1x9cfc-0003qq...@franck.debian.org and subject line Bug#755450: Removed package(s) from unstable has caused the Debian Bug report #722035, regarding ffgtk: FTBFS agains evolution-data-server 3.8 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.) -- 722035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ffgtk Version: 0.8.1-3 Severity: important User: pkg-evolution-maintain...@lists.alioth.debian.org Usertags: eds-3.8 Hi, we are planning to upload evolution and evolution-data-server 3.8 to unstable soon. Your package ffgtk declares a build dependency on one of these packages: evolution-data-server-dev libedataserver1.2-dev libcamel1.2-dev libebook1.2-dev libedataserverui-3.0-dev libedata-book1.2-dev libecal1.2-dev libedata-cal1.2-dev libebackend1.2-dev During a rebuild, ffgtk failed to build against evolution-data-server 3.8. The build log can be found at [1]. One notable change is, that libedataserverui has been dropped. If your package build-depends on libedataserverui-3.0-dev, you'll need to get rid of that dependency. As for some of the other API changes, see the release announcements of evolution-data-server 3.5.3 [2]. If you want to test-build ffgtk, version 3.8 of evolution-data-server is currently available in experimental. If you don't have the time porting to the new e-d-s interfaces, disabling e-d-s support (temporarily) might be an option. Otherwise ffgtk will have to be removed from testing to not block the transition. Ubuntu and Fedora have already done this transition, so it might be worthwile having a look at the patches they ship. Thanks for your cooperation. Michael, on behalf of the Debian GNOME and Evolution team. [1] http://people.debian.org/~biebl/eds-3.8/ffgtk_0.8.1-3.log [2] https://mail.gnome.org/archives/ftp-release-list/2012-June/msg00100.html ---End Message--- ---BeginMessage--- Version: 0.8.1-3+rm Dear submitter, as the package ffgtk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/755450 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#726994: marked as done (xserver-xorg-video-nvidia-legacy-96xx: does not support Xorg Xserver 1.13 or later)
Your message dated Mon, 21 Jul 2014 12:29:24 + with message-id e1x9cia-0003hk...@franck.debian.org and subject line Bug#755454: Removed package(s) from unstable has caused the Debian Bug report #726994, regarding xserver-xorg-video-nvidia-legacy-96xx: does not support Xorg Xserver 1.13 or later 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.) -- 726994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-nvidia-legacy-96xx Version: 96.43.23-7 Severity: serious Tags: upstream jessie wontfix NVIDIA does not plan to update the 96xx legacy driver series any more to add support for newer Linux or Xorg releases: http://nvidia.custhelp.com/app/answers/detail/a_id/3142 Support for X.Org xserver version 1.12 was added to the 96.43.* legacy driver series with version 96.43.23. No further releases from the 96.43.* series are planned. Andreas ---End Message--- ---BeginMessage--- Version: 96.43.20-3+rm Dear submitter, as the package nvidia-settings-legacy-96xx has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/755454 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#729080: marked as done (software-center: uninstallable in sid, broken by python-gi)
Your message dated Mon, 21 Jul 2014 12:28:45 + with message-id e1x9chx-0003gf...@franck.debian.org and subject line Bug#755452: Removed package(s) from unstable has caused the Debian Bug report #729080, regarding software-center: uninstallable in sid, broken by python-gi 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.) -- 729080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: software-center Version: 5.1.2debian3.1 Severity: serious Tags: sid jessie User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: Package: software-center Version: 5.1.2debian3.1 Depends: ... , python-aptdaemon (= 0.40), ... Package: python-aptdaemon Source: aptdaemon Version: 1.1.1-1 Depends: ... , python-gi, ... Package: python-gi Source: pygobject Version: 3.10.1-1 Breaks: python-aptdaemon ( 1.0), ... , software-center (= 5.6.0-0ubuntu2) this Breaks was added here: pygobject (3.10.0-1) unstable; urgency=low * debian/control.in: Add Breaks for older python-aptdaemon and software-center (Ubuntu specific) to avoid potential crash caused by new python-gi with old python-aptdaemon. (LP: #1173249) Cheers, Andreas ---End Message--- ---BeginMessage--- Version: 5.1.2debian3.1+rm Dear submitter, as the package software-center has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/755452 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#721666: marked as done (software-center hangs indefinitely)
Your message dated Mon, 21 Jul 2014 12:28:45 +
with message-id e1x9chx-0003gf...@franck.debian.org
and subject line Bug#755452: Removed package(s) from unstable
has caused the Debian Bug report #721666,
regarding software-center hangs indefinitely
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.)
--
721666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: software-center
Version: 5.1.2debian3.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
running software-center causes the main window to open, but then the spinning
loading
symbol shows up and spins indefinitely. The content is never displayed.
Running it from a terminal throws this error in a loop:
RuntimeError: Data access methods are unsupported. Use normal Python attributes
instead
2013-09-02 23:30:12,926 - softwarecenter.view.appview - WARNING -
ubuntu-almost-fixed-height-mode extension not available
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/gi/overrides/GLib.py, line 629, in
lambda
return (lambda data: callback(*data), user_data)
File
/usr/share/software-center/softwarecenter/ui/gtk3/panes/viewswitcher.py, line
263, in config_view
pane = vm.set_active_view(view_id)
File
/usr/share/software-center/softwarecenter/ui/gtk3/session/viewmanager.py,
line 125, in set_active_view
view_widget.init_view()
File
/usr/share/software-center/softwarecenter/ui/gtk3/panes/installedpane.py,
line 119, in init_view
SoftwarePane.init_view(self)
File
/usr/share/software-center/softwarecenter/ui/gtk3/panes/softwarepane.py, line
280, in init_view
self)
File
/usr/share/software-center/softwarecenter/ui/gtk3/views/appdetailsview_gtk.py,
line 698, in __init__
self._layout_page()
File
/usr/share/software-center/softwarecenter/ui/gtk3/views/appdetailsview_gtk.py,
line 948, in _layout_page
self.pkg_statusbar = PackageStatusBar(self)
File
/usr/share/software-center/softwarecenter/ui/gtk3/views/appdetailsview_gtk.py,
line 132, in __init__
self.progress.set_data(transparent-bg-hint, True)
File /usr/lib/python2.7/dist-packages/gi/overrides/GObject.py, line 555, in
_unsupported_data_method
raise RuntimeError('Data access methods are unsupported. '
RuntimeError: Data access methods are unsupported. Use normal Python attributes
instead
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.10-2-686-pae (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 software-center depends on:
ii app-install-data2012.06.16.1
ii aptdaemon 1.1.1-1
ii gir1.2-glib-2.0 1.36.0-2+b1
ii gir1.2-gmenu-3.03.8.0-2
ii gir1.2-gtk-3.0 3.8.2-3
ii gir1.2-webkit-3.0 2.0.4-2
ii gnome-icon-theme3.8.2-2
ii lsb-release 4.1+Debian12
ii policykit-1 0.105-3
ii policykit-1-gnome 0.105-2
ii python 2.7.5-4
ii python-apt 0.8.9
ii python-aptdaemon1.1.1-1
ii python-aptdaemon.gtk3widgets1.1.1-1
ii python-dbus 1.2.0-2+b1
ii python-defer1.0.6-2
ii python-gi-cairo [python-gobject-cairo] 3.8.2-1
ii python-gobject 3.8.2-1
ii python-lazr.restfulclient 0.13.3-1
ii python-xapian 1.2.15-4
ii python-xdg 0.25-3
ii synaptic0.80.2
Versions of packages software-center recommends:
ii apt-xapian-index 0.46
pn gir1.2-launchpad-integration-3.0 none
ii lzma 9.22-2
ii sessioninstaller 0.20-1
pn software-properties-gtk none
pn update-notifier none
ii xz-utils [lzma] 5.1.1alpha+20120614-2
ii zeitgeist-core0.9.0.1-1
software-center suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Version: 5.1.2debian3.1+rm
Dear submitter,
as the package software-center has just been removed from the Debian archive
Bug#726494: marked as done (xserver-xorg-video-nvidia-legacy-96xx: does not support Xorg Xserver 1.13 or later)
Your message dated Mon, 21 Jul 2014 12:30:11 + with message-id e1x9cjl-0003jy...@franck.debian.org and subject line Bug#755453: Removed package(s) from unstable has caused the Debian Bug report #726494, regarding xserver-xorg-video-nvidia-legacy-96xx: does not support Xorg Xserver 1.13 or later 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.) -- 726494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-nvidia-legacy-96xx Version: 96.43.23-7 Severity: serious Tags: upstream jessie wontfix NVIDIA does not plan to update the 96xx legacy driver series any more to add support for newer Linux or Xorg releases: http://nvidia.custhelp.com/app/answers/detail/a_id/3142 Support for X.Org xserver version 1.12 was added to the 96.43.* legacy driver series with version 96.43.23. No further releases from the 96.43.* series are planned. Andreas ---End Message--- ---BeginMessage--- Version: 96.43.23-8+rm Dear submitter, as the package nvidia-graphics-drivers-legacy-96xx has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/755453 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#754754: marked as done (jq: FTBFS on s390x: test suite timeout)
Your message dated Mon, 21 Jul 2014 12:34:03 + with message-id e1x9cn5-0004hx...@franck.debian.org and subject line Bug#754754: fixed in jq 1.4-2.1 has caused the Debian Bug report #754754, regarding jq: FTBFS on s390x: test suite timeout 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.) -- 754754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jq Version: 1.4-2 Severity: serious Justification: FTBFS Hi, your package no longer builds on s390x: | CCLD jq | make[2]: Leaving directory '/«PKGBUILDDIR»' | make[1]: Leaving directory '/«PKGBUILDDIR»' |dh_auto_test -a | make[1]: Entering directory '/«PKGBUILDDIR»' | make check-am | make[2]: Entering directory '/«PKGBUILDDIR»' | make check-TESTS | make[3]: Entering directory '/«PKGBUILDDIR»' | make[4]: Entering directory '/«PKGBUILDDIR»' | make[4]: *** Deleting file 'tests/all.log' | Terminated | make: *** wait: No child processes. Stop. | make: *** Waiting for unfinished jobs | make: *** wait: No child processes. Stop. | make[4]: *** [tests/all.log] Terminated | make[3]: *** [check-TESTS] Terminated | make[2]: *** [check-am] Terminated | make[1]: *** [check] Terminated | Makefile:1037: recipe for target 'tests/all.log' failed | Makefile:1016: recipe for target 'check-TESTS' failed | Makefile:1218: recipe for target 'check-am' failed | Makefile:1220: recipe for target 'check' failed | Build killed with signal TERM after 150 minutes of inactivity Full build log: https://buildd.debian.org/status/fetch.php?pkg=jqarch=s390xver=1.4-2stamp=1405274990 Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: jq Source-Version: 1.4-2.1 We believe that the bug you reported is fixed in the latest version of jq, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated jq 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: Mon, 21 Jul 2014 07:42:05 +0100 Source: jq Binary: jq Architecture: source mips Version: 1.4-2.1 Distribution: unstable Urgency: medium Maintainer: Simon Elsbrock si...@iodev.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: jq - lightweight and flexible command-line JSON processor Closes: 754754 Changes: jq (1.4-2.1) unstable; urgency=medium . * Non-maintainer upload. * Restore the 1.3-1.1 NMU changelog. * Fix FTBFS on big endian architectures. Add big-endian-fix.patch. Patch by Dejan Latinovic dejan.latino...@imgtec.com. Closes: #754754. Checksums-Sha1: 80c708c432b75dc71ed11d1a2619786f8ab3667d 1830 jq_1.4-2.1.dsc 2f3b6aaed3da9051701434bcf7d947c4e1c05902 11700 jq_1.4-2.1.debian.tar.xz 1b70a701d4515ecc7cef7547d078dea2dc85d36e 100728 jq_1.4-2.1_mips.deb Checksums-Sha256: 3a0be3ea85bfd0f8e78b7b0b3e24785753e17dce8890604e131a71f716f01c33 1830 jq_1.4-2.1.dsc b30ce5f4b03bb7310a0c944c6cb63372b746a47d49387c45d4eb99909dd79a55 11700 jq_1.4-2.1.debian.tar.xz 8984aea9b1adf2512ae24e8272bbeba82ce9a3f8cd4a0096f74c65d90b7284cd 100728 jq_1.4-2.1_mips.deb Files: 6052104c9f96dc126d38d85e6e1022bf 100728 utils optional jq_1.4-2.1_mips.deb 69f0c44ba9de02a2aeaeafd4a277b457 1830 utils optional jq_1.4-2.1.dsc 6c681b1902958cd310c0c4a02fd66a3d 11700 utils optional jq_1.4-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTzQWIAAoJEHxWrP6UeJfYWNMP+wSG1vQ2pFlUxULyiDCpV6QP vVk65T0ci3N5loDd4/zMc4tmuL0Qgq2E/LI2mmc1qn/oUHf+s6uCNagJ3P0i+9sp wexeiS5BKKhBzEzQJKXU5xpRxD4zwL63vLCMkC26+4RdKXs+wVv8a/cvd5Zf0/eT Rk+aw11wq7aJPvUMtY/LGpuOf/TZ8KJ8urjhzwKDUD+Sby3q2AA2tdFwRb/Q1PIv f133ed6Q3LFb/0bHELynhW3Avu2kQxdJIeLA4B7em4h/XF9vci30DOVD6EbLTt2i qucffkx5V33qhvlTklKieE0Rd2nYrsJxKIEadRwAAxKcmIbx2+f3ZHvYdCx2X+eg IUwqDwjHmTIX5dUUvaYHOyEq2DClDRnOksrvF2X1WZDn0/s618fPenn75APuzzeE DyMasU88nwYFnUHoNw2sjAj0NCseQl9RQQ0gGKpPgS9xIJer6kA0rGB/aMUgsFIQ B2iqLzhEAYYjD9wcI+9In1nyYi8XLDicFKei+Ndr/L0DRd34D6C+Y5X8TRg0+Tml pLB+2XL2RI54OnBRzNtJE0QdAciNA5GPj1kUzEjPobhvhLEQTdxXJ/LL17ocGs7k
Bug#725909: marked as done (isns: typo in initscript)
Your message dated Mon, 21 Jul 2014 12:34:07 +
with message-id e1x9cn9-0004id...@franck.debian.org
and subject line Bug#755422: Removed package(s) from unstable
has caused the Debian Bug report #725909,
regarding isns: typo in initscript
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.)
--
725909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: isns
Version: 2.1-01+dfsg-3
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
There is a typo in the initscript for isns. It specifies the PID as
/var/run/isnss.pid, when in actuality it is /var/run/isnsd.pid.
this causes the daemon to start improperly with the error
Oct 9 18:22:33 dns isnsd: src/iSNSLinux.c:241#011isnss daemon not started#012
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
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 isns depends on:
ii libc6 2.13-38
ii libgdbm3 1.8.3-11
isns recommends no packages.
isns suggests no packages.
-- Configuration Files:
/etc/init.d/isns changed:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
PID_FILE=/var/run/isnsd.pid
CONFIG_FILE=/etc/isns/isns.conf
DAEMON=/usr/sbin/isnsd
NAME=isnsd
DESC=iSNS Internet Storage Naming Service
test -x $DAEMON || exit 0
set -e
case $1 in
start)
echo -n Starting $DESC:
start-stop-daemon --start --quiet --oknodo --pidfile $PID_FILE \
--exec $DAEMON -- $DAEMON_OPTS
echo $NAME.
;;
stop)
echo -n Stopping $DESC:
start-stop-daemon --stop --quiet --oknodo --pidfile $PID_FILE \
--exec $DAEMON
echo $NAME.
;;
#reload)
#
# If the daemon can reload its config files on the fly
# for example by sending it SIGHUP, do it here.
#
# If the daemon responds to changes in its config file
# directly anyway, make this a do-nothing entry.
#
# echo Reloading $DESC configuration files.
# start-stop-daemon --stop --signal 1 --quiet --pidfile \
# $PID_FILE --exec $DAEMON
#;;
force-reload)
#
# If the reload option is implemented, move the force-reload
# option to the reload entry above. If not, force-reload is
# just the same as restart except that it does nothing if the
# daemon isn't already running.
# check wether $DAEMON is running. If so, restart
start-stop-daemon --stop --test --quiet --oknodo --pidfile \
$PID_FILE --exec $DAEMON \
$0 restart \
|| exit 0
;;
restart)
echo -n Restarting $DESC:
start-stop-daemon --stop --quiet --oknodo --pidfile \
$PID_FILE --exec $DAEMON
sleep 1
start-stop-daemon --start --quiet --oknodo --pidfile \
$PID_FILE --exec $DAEMON -- $DAEMON_OPTS
echo $NAME.
;;
*)
N=/etc/init.d/$NAME
# echo Usage: $N {start|stop|restart|reload|force-reload} 2
echo Usage: $N {start|stop|restart|force-reload} 2
exit 1
;;
esac
exit 0
-- no debconf information
---End Message---
---BeginMessage---
Version: 2.1-01+dfsg-3+rm
Dear submitter,
as the package isns has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/755422
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Processed: fixed in another version
Processing commands for cont...@bugs.debian.org:
fixed 716949 2.13-4
Bug #716949 {Done: Ivo De Decker ivo.dedec...@ugent.be} [nagios-nrpe-server]
nagios-nrpe-server: removes its PID on connection errors
There is no source info for the package 'nagios-nrpe-server' at version
'2.13-4' with architecture ''
Unable to make a source version for version '2.13-4'
Marked as fixed in versions 2.13-4.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
716949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716949
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#755317: [rt.cpan.org #97372] Fwd: Re: Bug#755317: libnet-bonjour-perl: FTBFS: Tests failures
From: gregor herrmann gre...@debian.org To: 755...@bugs.debian.org Cc:
Ondřej Surý ond...@debian.org Subject: Re: Bug#755317: libnet-bonjour-perl:
FTBFS: Tests failures Date: Sun, 20 Jul 2014 14:39:02 +0200 Control: tag -1 +
confirmed On Sat, 19 Jul 2014 20:44:36 +0200, David Suárez wrote:
Source: libnet-bonjour-perl
Version: 0.96-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140718 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
make[1]: Entering directory '/«PKGBUILDDIR»'
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e
test_harness(0, 'blib/lib', 'blib/arch') t/*.t
t/1-use.t . ok
Use of uninitialized value in uc at
/«PKGBUILDDIR»/blib/lib/Net/Bonjour/Entry.pm line 272.
Use of uninitialized value $_[4] in join or string at
/usr/lib/perl5/Net/DNS/RR.pm line 69.
Use of uninitialized value $argument in concatenation (.) or string at
/usr/lib/perl5/Net/DNS/RR/.pm line 75.
in new Net::DNS::RR( type ttl 3600 address name server.local ... ) at
/«PKGBUILDDIR»/blib/lib/Net/Bonjour/Entry.pm line 327.
# Looks like you planned 18 tests but ran 15.
# Looks like your test exited with 255 just after 15.
t/2-entry.t ...
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 3/18 subtests
Breakage by recent Net::DNS?
Yes, but caused by wrong usage (initializing address with undef value)
by Net::Bonjour. Here is a patch:
--- lib/Net/Bonjour/Entry.pm.orig 2014-07-21 09:43:40.378946335 -0400
+++ lib/Net/Bonjour/Entry.pm2014-07-21 09:44:39.011734092 -0400
@@ -324,6 +324,8 @@
foreach my $type (qw(A )) {
+ next unless $self-{'_' . $type};
+
my $rr = Net::DNS::RR-new(
'type'= $type,
'ttl' = $self-ttl,
@@ -331,7 +333,7 @@
'name'= $self-hostname
);
- push(@addrs, $rr) if $self-{'_' . $type};
+ push(@addrs, $rr);
}
$packet-push('additional', @addrs);
However since Net::DNS 0.75 also test 7 of Net::Bonjour's
t/4-enterprise.ot fails. Still looking into that...
Cheers,
-- Willem
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754354: Something holds dentry-related mutex forever in Wheezy amd64 kernel
It is possible that I'm seeing the same problem. Our AMD Opteron 4386 (16 cores) machine is also getting stuck with lots of hung tasks. Although it responds to ping, and even a KVM virtual machine running on it appears to continue working correctly, the host itself is locked up. This happens once a week - probably when the machine is under the most direct CPU load and NFS load. Once the machine is in this state I can type in a username at the login prompt but no password prompt ever appears. I forced a crashdump and it contained hundreds of tasks with backtraces involving a mutex_lock in walk_component or nfsd_lookup_dentry which look similar to Alexander's: PID: 499TASK: 880490a29080 CPU: 11 COMMAND: nrpe #0 [880454e099a8] __schedule at 8134f195 #1 [880454e09a30] __mutex_lock_common.isra.5 at 8134fb74 #2 [880454e09aa0] mutex_lock at 8134fa62 #3 [880454e09ac0] walk_component at 81103868 #4 [880454e09b30] link_path_walk at 811040c1 #5 [880454e09bc0] path_openat at 8110611d #6 [880454e09c50] do_filp_open at 8110646d #7 [880454e09d20] open_exec at 810fed80 #8 [880454e09d40] load_elf_binary at 81135939 #9 [880454e09e50] search_binary_handler at 810ff7fd #10 [880454e09ea0] do_execve_common.isra.24 at 81100551 #11 [880454e09f10] sys_execve at 81014dd2 #12 [880454e09f50] stub_execve at 813559ec RIP: 7fcc8991ca87 RSP: 7fffe8b91ef8 RFLAGS: 0246 RAX: 003b RBX: 0003 RCX: RDX: 0164d180 RSI: 7fffe8b91f10 RDI: 7fcc899bc3ad RBP: 0003 R8: R9: 01f2 R10: 7fcc8a88f9d0 R11: 0246 R12: 7fffe8b91f10 R13: 0400 R14: 0001 R15: 7fffe8b91f10 ORIG_RAX: 003b CS: 0033 SS: 002b and: PID: 4087 TASK: 88040ea63840 CPU: 2 COMMAND: nfsd #0 [8804034b9c00] __schedule at 8134f195 #1 [8804034b9c88] __mutex_lock_common.isra.5 at 8134fb74 #2 [8804034b9cf8] mutex_lock at 8134fa62 #3 [8804034b9d18] fh_lock_nested.isra.6 at a043d63c [nfsd] #4 [8804034b9d28] nfsd_lookup_dentry at a043df1a [nfsd] #5 [8804034b9d98] nfsd4_secinfo.part.15 at a0447692 [nfsd] #6 [8804034b9dc8] nfsd4_proc_compound at a04468d6 [nfsd] #7 [8804034b9e18] nfsd_dispatch at a043a7cd [nfsd] #8 [8804034b9e48] svc_process_common at a0336c3f [sunrpc] #9 [8804034b9eb8] svc_process at a0337050 [sunrpc] #10 [8804034b9ed8] nfsd at a043a0e3 [nfsd] #11 [8804034b9ef8] kthread at 8105f701 #12 [8804034b9f48] kernel_thread_helper at 813576f4 and: PID: 5013 TASK: 880805c8b180 CPU: 8 COMMAND: getty #0 [88080cb8b9a8] __schedule at 8134f195 #1 [88080cb8ba30] __mutex_lock_common.isra.5 at 8134fb74 #2 [88080cb8baa0] mutex_lock at 8134fa62 #3 [88080cb8bac0] walk_component at 81103868 #4 [88080cb8bb30] link_path_walk at 811040c1 #5 [88080cb8bbc0] path_openat at 8110611d #6 [88080cb8bc50] do_filp_open at 8110646d #7 [88080cb8bd20] open_exec at 810fed80 #8 [88080cb8bd40] load_elf_binary at 81135939 #9 [88080cb8be50] search_binary_handler at 810ff7fd #10 [88080cb8bea0] do_execve_common.isra.24 at 81100551 #11 [88080cb8bf10] sys_execve at 81014dd2 #12 [88080cb8bf50] stub_execve at 813559ec RIP: 7f0d1ed74a87 RSP: 7fffab157528 RFLAGS: 0206 RAX: 003b RBX: RCX: RDX: 7fffab159ee8 RSI: 7fffab157600 RDI: 00405d7c RBP: 0003 R8: R9: R10: R11: 0206 R12: 006075a0 R13: 011da750 R14: R15: ORIG_RAX: 003b CS: 0033 SS: 002b ii linux-image-amd643.2+46 ii nfs-kernel-server1:1.2.6-4 Mike. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750643: antlr: missing licence for PyANTLR
excellent! Ter On Jul 21, 2014, at 12:44 AM, Thorsten Glaser t.gla...@tarent.de wrote: On Sat, 19 Jul 2014, Terence Parr wrote: Here you go :) http://www.antlr2.org/license.html Thanks, wonderful! I really appreciate you taking the time for this. Now we have this statement and Wolfgang’s (who “only” needs to decide on which BSD variants and GPL versions he wants), which removes every _possible_ legal issue, so everyone involved can *finally* go back to hacking, which, I am sure, we all prefer over dealing with licences ☺ bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 754583 grave Bug #754583 [libdcmtk4] libdcmtk4: fails to upgrade: tries to overwrite files in libdcmtk3 Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 754583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754583 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#755337: [monkeysphere] Bug#755337: monkeysphere: FTBFS: Tests failures
On 07/19/2014 02:45 PM, David Suárez wrote: --- /«PKGBUILDDIR»/tests/tmp/monkeyspheretest.dBAA7Ae/expectedout 2014-07-19 06:21:14.404014808 + +++ /dev/fd/63 2014-07-19 06:21:14.404014808 + @@ -1,5 +1,5 @@ pub:u:1024:1:44B73C40DB5AE932:1405750874:::u:::scSC: uid:u1405750874::E90EC72E68C6C2A0751DADC70F54F60D27B88C3D::monkeymonkey: -sig:!::1:44B73C40DB5AE932:1405750874monkeymonkey:13x: +sig:!::1:44B73C40DB5AE932:1405750874monkeymonkey:13x:8: uid:u1405750874::8200BD0425CC70C7D698DF3FE412044EAAB83F94::testtest: -sig:!::1:44B73C40DB5AE932:1405750874monkeymonkey:13x: +sig:!::1:44B73C40DB5AE932:1405750874monkeymonkey:13x:8: FAILED! ### removing temp dir... make[1]: *** [test-keytrans] Error 1 dh_auto_test: make -j1 test returned exit code 2 woo, this is due to gnupg 1 finally updating its with-colons output to match the (more-detailed) gnupg 2 output: http://lists.gnupg.org/pipermail/gnupg-announce/2014q2/000344.html I think the right way to fix this is just to update the test output to match the modern gnupg output. Anyone building against older versions of gnupg can patch it back. Any objections? --dkg signature.asc Description: OpenPGP digital signature
Bug#755513: nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1
Package: nvidia-opencl-dev Version: 5.5.22-4 Severity: serious Tags: patch Dear maintainer Installing ocl-icd-libopencl1 followed by nvidia-cuda-toolkit results in the following error: dpkg: error processing archive /var/cache/apt/archives/nvidia-opencl-dev_5.5.22-4_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libOpenCL.so', which is also in package ocl-icd-libopencl1:amd64 2.1.3-4 Selecting previously unselected package nvidia-cuda-toolkit. Preparing to unpack .../nvidia-cuda-toolkit_5.5.22-4_amd64.deb ... Unpacking nvidia-cuda-toolkit (5.5.22-4) ... Errors were encountered while processing: /var/cache/apt/archives/nvidia-opencl-dev_5.5.22-4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Ideally, the unversioned libOpenCL.so should not be in package ocl-icd-libopencl1, but please see bug #679228 for reasons why it is so. I believe the simplest solution is for package nvidia-opencl-dev to simply conflict with ocl-icd-libopencl1 in addition to opencl-dev, as per the attached patch. Regards Graham [1] https://bugs.debian.org/679228 diff -Nru nvidia-cuda-toolkit-5.5.22/debian/control nvidia-cuda-toolkit-5.5.22/debian/control --- nvidia-cuda-toolkit-5.5.22/debian/control 2014-03-10 08:11:48.0 + +++ nvidia-cuda-toolkit-5.5.22/debian/control 2014-05-25 11:32:35.0 + @@ -172,7 +171,7 @@ Provides: opencl-dev, Conflicts: - opencl-dev, + opencl-dev, ocl-icd-libopencl1 Breaks: nvidia-libopencl1 ( 304.88-7), Replaces:
Processed: cloning 749794, reassign -1 to libnetclasses0 ..., severity of -1 is serious, tagging -1, affects -1
Processing commands for cont...@bugs.debian.org: clone 749794 -1 Bug #749794 [src:talksoup.app] talksoup.app: GCC warnings that may lead to runtime issues with new GNUstep libraries Bug 749794 cloned as bug 755514 reassign -1 libnetclasses0 1.06.dfsg-5 Bug #755514 [src:talksoup.app] talksoup.app: GCC warnings that may lead to runtime issues with new GNUstep libraries Bug reassigned from package 'src:talksoup.app' to 'libnetclasses0'. No longer marked as found in versions talksoup.app/1.0alpha-32-g55b4d4e-1.2. Ignoring request to alter fixed versions of bug #755514 to the same values previously set Bug #755514 [libnetclasses0] talksoup.app: GCC warnings that may lead to runtime issues with new GNUstep libraries Marked as found in versions gnustep-netclasses/1.06.dfsg-5. retitle -1 libnetclasses0: rec_join is never called on amd64 Bug #755514 [libnetclasses0] talksoup.app: GCC warnings that may lead to runtime issues with new GNUstep libraries Changed Bug title to 'libnetclasses0: rec_join is never called on amd64' from 'talksoup.app: GCC warnings that may lead to runtime issues with new GNUstep libraries' severity -1 serious Bug #755514 [libnetclasses0] libnetclasses0: rec_join is never called on amd64 Severity set to 'serious' from 'grave' tags -1 + jessie sid Bug #755514 [libnetclasses0] libnetclasses0: rec_join is never called on amd64 Ignoring request to alter tags of bug #755514 to the same tags previously set affects -1 talksoup.app Bug #755514 [libnetclasses0] libnetclasses0: rec_join is never called on amd64 Added indication that 755514 affects talksoup.app thanks Stopping processing here. Please contact me if you need assistance. -- 749794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749794 755514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755514 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#754532: marked as done (Conflicting build-depencies: libgnomevfs2-dev/libgnutls-dev)
Your message dated Mon, 21 Jul 2014 15:48:44 +
with message-id e1x9fpu-lj...@franck.debian.org
and subject line Bug#754532: fixed in camorama 0.19-3
has caused the Debian Bug report #754532,
regarding Conflicting build-depencies: libgnomevfs2-dev/libgnutls-dev
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.)
--
754532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: camorama
Version: 0.19-2.3
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ametz...@debian.org
Usertags: gnutls3
Hello,
camorama's b-d cannot be installed since libgnomevfs2-dev has been
upgraded to use libgnutls28-dev instead of libgnutls-dev.
Afaict the build-dependency on libgnutls-dev can simply be dropped:
--
(SID)ametzler@argenau:/tmp/REBUiLD/camorama-0.19$ grep -ril gnutl *
debian/changelog
debian/control
--
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'
---End Message---
---BeginMessage---
Source: camorama
Source-Version: 0.19-3
We believe that the bug you reported is fixed in the latest version of
camorama, 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 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alessio Treglia ales...@debian.org (supplier of updated camorama 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: Mon, 21 Jul 2014 16:13:28 +0100
Source: camorama
Binary: camorama
Architecture: source amd64
Version: 0.19-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Alessio Treglia ales...@debian.org
Description:
camorama - gnome utility to view and save images from a webcam
Closes: 623982 754532
Changes:
camorama (0.19-3) unstable; urgency=medium
.
* Adopting camorama.
Thanks to Leo Antunes for the great work. (Closes: #623982)
* ACK NMUs.
* Drop include simple-patchsys.mk in favor of the modern 3.0 (quilt)
packaging format.
* Convert patches to quilt format.
* Drop CDBS in favor of debhelper.
* Bump DH compatibility to 9.
* Build-dep on autotools-dev to update config.{guess,sub}.
* Move in-source changes to a quilt patch.
* Drop libgnutls-dev to fix build-deps conflict which caused FTBFS.
Thanks to Matteo F. Vescovi (Closes: #754532)
* Stick to Standards 3.9.5.
Checksums-Sha1:
bb9e7a7d73a460c891fd0c4a41036057a156020a 2169 camorama_0.19-3.dsc
cf7b720be0f366633bce107e4a1427ca6d5a41a6 9171 camorama_0.19-3.debian.tar.gz
eccc2e44fa23a5d52527c1df6bfb9d06955794d4 139754 camorama_0.19-3_amd64.deb
Checksums-Sha256:
f8bdd9db3d26180987b8cdcf804a7eca8aab6afb0e41363f680c0f3d058b38fc 2169
camorama_0.19-3.dsc
b5794759494d4d52b0ca68d098fd3d7bf549bd03fec5075c9ac3d417861fd97f 9171
camorama_0.19-3.debian.tar.gz
143996e11804c006b5e14598ba8e3ca8ec7d600c3863f0ce44abef396bd1951d 139754
camorama_0.19-3_amd64.deb
Files:
a546b7b6a9fd072e28155284d416b608 139754 gnome optional
camorama_0.19-3_amd64.deb
36c5918ce191545f8e9b8c97f47b3004 2169 gnome optional camorama_0.19-3.dsc
ef762417d1f27f2296d75447918fde32 9171 gnome optional
camorama_0.19-3.debian.tar.gz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJTzTDBAAoJEOikiuUxHXZaO4QP/i9b3ISUQnt+x/e85/NWwcdu
RTRZ40mwAplsRfqvv1oBTU1eIwVlHJtbxXK3IQFJEs9TghCtZyPesX0WQAXrHFMX
Oz65TTJYkkVef91glzS43rNThsKrDIcmacB8fSejfSVt8PoFjhYuuEjzFoa5h42T
XcG16rsZ1EkfkhvOThulu2yyd7ysh2LLl2hmio2id3Ks7pdJMpaJyi7Np4IYDJ2M
hoHftE/3E2xU7UNak+o9iCqWA/VEzfC4R7JoIaaIKCU0h/JPMmJGyxsFsvVftY81
6ktFY95jrKWW/zKLKES/XPP0RJLWdzUnE6zxLeJf2w9acp0laZiZ5XoXnCcfyXeV
foETDdANvFBJgh6D7M1RiH4pqyp1dE595WUYBZ5A6HyBVI61uhThv3ovj3saNPvR
C/IkqERxpSPR6ii3gsmLFTqawi6iPXZm/GA7iYBC014Tbeq6vjnauNPqyrQGkfqQ
aZQuPbr4vEDV9bmwiMp/F4Qg0yIgHrUVktfGXiNBEuM/dhVTz8DYPs70Au06qtNA
rlWDuG5MWA9h8Mh1Pqv1DSz/QyuaEg73erd0rfOhto9UbZLb+thUkra8pHye2ZMK
Processed (with 5 errors): Re: Bug#745897: closed by Hideki Yamane henr...@debian.org (Bug#745897: fixed in libstruts1.2-java 1.2.9-9)
Processing commands for cont...@bugs.debian.org:
unarchive 745897
Bug #745897 {Done: Hideki Yamane henr...@debian.org} [libstruts1.2-java]
libstruts1.2-java: CVE-2014-0114
Unarchived Bug 745897
2014-06-16 20:27 GMT+09:00 Emmanuel Bourg ebo...@apache.org:
Unknown command or malformed arguments to command.
Le 15/06/2014 06:43, Hideki Yamane a écrit :
Unknown command or malformed arguments to command.
Unknown command or malformed arguments to command.
Then, question: commons-beanutils version in Debian is
Unknown command or malformed arguments to command.
both seems to be still vulunerable version. Can you provide security-
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
745897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745897
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#745897: closed by Hideki Yamane henr...@debian.org (Bug#745897: fixed in libstruts1.2-java 1.2.9-9)
Hi all, 2014-06-16 20:27 GMT+09:00 Emmanuel Bourg ebo...@apache.org: I got confirmation from the Struts developers that a new release using commons-beanutils 1.9.2 is planned soon. So I'm going to prepare the backport of commons-beanutils 1.9.2 in stable and wait for the new release of Struts 1.x. Security fix was committed over 1 month ago [1], but not released (from upstream) yet. So, I made a Debian fix using [1]. [1] http://svn.apache.org/r1603883 Regards, Nobuhiro 745897.tar.gz Description: GNU Zip compressed data
Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
Package: laptop-mode-tools Version: 1.65-2 Severity: serious Justification: Breaks normal system boot The lmt-udev script appears to be breaking systemd boot for me due to introducing a deadlock / dependency circle. Based on usage of debug-shell.service, it appears that systemd is waiting for udev to settle, which is needed for the lvm2 volumes to be present and active, which is needed for /usr to be mounted. However, the lmt-udev script is waiting for /usr to be mounted too, and this appears to be blocking the udev settle. The timeout for lmt-udev to wait for /usr is as long as the timeout for udevadm settle, and so eventually this times out and the system tries to limp along and finish booting, but many things are not started properly in this case. The lmt-udev script appears to be trying to run itself in the background, but this is not successful, as udev / systemd are clearly waiting on it. Based on the arguments to the script, it appears that this is related to usb autosuspend. Removing laptop-mode-tools causes my system to boot properly. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-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/bash Versions of packages laptop-mode-tools depends on: ii lsb-base4.1+Debian13 ii psmisc 22.21-2 ii util-linux 2.20.1-5.8 Versions of packages laptop-mode-tools recommends: ii ethtool 1:3.13-1 ii hdparm 9.43-1.1 ii net-tools 1.60-26 ii python-qt4 4.11.1+dfsg-1 pn sdparm none ii udev208-6 ii wireless-tools 30~pre9-8 Versions of packages laptop-mode-tools suggests: ii acpid 1:2.0.22-3 pn hal none ii python 2.7.8-1 -- Configuration Files: /etc/laptop-mode/conf.d/cpufreq.conf changed: DEBUG=0 CONTROL_CPU_FREQUENCY=auto BATT_CPU_MAXFREQ=fastest BATT_CPU_MINFREQ=slowest BATT_CPU_GOVERNOR=powersave BATT_CPU_IGNORE_NICE_LOAD=1 LM_AC_CPU_MAXFREQ=fastest LM_AC_CPU_MINFREQ=slowest LM_AC_CPU_GOVERNOR=performance LM_AC_CPU_IGNORE_NICE_LOAD=0 NOLM_AC_CPU_MAXFREQ=fastest NOLM_AC_CPU_MINFREQ=slowest NOLM_AC_CPU_GOVERNOR=performance NOLM_AC_CPU_IGNORE_NICE_LOAD=0 CONTROL_CPU_THROTTLING=0 BATT_CPU_THROTTLING=medium LM_AC_CPU_THROTTLING=medium NOLM_AC_CPU_THROTTLING=minimum /etc/laptop-mode/conf.d/usb-autosuspend.conf changed: DEBUG=0 CONTROL_USB_AUTOSUSPEND=auto AUTOSUSPEND_USE_WHITELIST=0 AUTOSUSPEND_USBID_BLACKLIST=046d:c245 1c88:003f 1c88:0007 AUTOSUSPEND_USBTYPE_BLACKLIST= AUTOSUSPEND_USBID_WHITELIST= AUTOSUSPEND_USBTYPE_WHITELIST= BATT_SUSPEND_USB=1 LM_AC_SUSPEND_USB=0 NOLM_AC_SUSPEND_USB=0 AUTOSUSPEND_TIMEOUT=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#755518: marked as done (laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot)
Your message dated Mon, 21 Jul 2014 23:31:32 +0530 with message-id 53cd557c.40...@debian.org and subject line Re: Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot has caused the Debian Bug report #755518, regarding laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot 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.) -- 755518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: laptop-mode-tools Version: 1.65-2 Severity: serious Justification: Breaks normal system boot The lmt-udev script appears to be breaking systemd boot for me due to introducing a deadlock / dependency circle. Based on usage of debug-shell.service, it appears that systemd is waiting for udev to settle, which is needed for the lvm2 volumes to be present and active, which is needed for /usr to be mounted. However, the lmt-udev script is waiting for /usr to be mounted too, and this appears to be blocking the udev settle. The timeout for lmt-udev to wait for /usr is as long as the timeout for udevadm settle, and so eventually this times out and the system tries to limp along and finish booting, but many things are not started properly in this case. The lmt-udev script appears to be trying to run itself in the background, but this is not successful, as udev / systemd are clearly waiting on it. Based on the arguments to the script, it appears that this is related to usb autosuspend. Removing laptop-mode-tools causes my system to boot properly. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-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/bash Versions of packages laptop-mode-tools depends on: ii lsb-base4.1+Debian13 ii psmisc 22.21-2 ii util-linux 2.20.1-5.8 Versions of packages laptop-mode-tools recommends: ii ethtool 1:3.13-1 ii hdparm 9.43-1.1 ii net-tools 1.60-26 ii python-qt4 4.11.1+dfsg-1 pn sdparm none ii udev208-6 ii wireless-tools 30~pre9-8 Versions of packages laptop-mode-tools suggests: ii acpid 1:2.0.22-3 pn hal none ii python 2.7.8-1 -- Configuration Files: /etc/laptop-mode/conf.d/cpufreq.conf changed: DEBUG=0 CONTROL_CPU_FREQUENCY=auto BATT_CPU_MAXFREQ=fastest BATT_CPU_MINFREQ=slowest BATT_CPU_GOVERNOR=powersave BATT_CPU_IGNORE_NICE_LOAD=1 LM_AC_CPU_MAXFREQ=fastest LM_AC_CPU_MINFREQ=slowest LM_AC_CPU_GOVERNOR=performance LM_AC_CPU_IGNORE_NICE_LOAD=0 NOLM_AC_CPU_MAXFREQ=fastest NOLM_AC_CPU_MINFREQ=slowest NOLM_AC_CPU_GOVERNOR=performance NOLM_AC_CPU_IGNORE_NICE_LOAD=0 CONTROL_CPU_THROTTLING=0 BATT_CPU_THROTTLING=medium LM_AC_CPU_THROTTLING=medium NOLM_AC_CPU_THROTTLING=minimum /etc/laptop-mode/conf.d/usb-autosuspend.conf changed: DEBUG=0 CONTROL_USB_AUTOSUSPEND=auto AUTOSUSPEND_USE_WHITELIST=0 AUTOSUSPEND_USBID_BLACKLIST=046d:c245 1c88:003f 1c88:0007 AUTOSUSPEND_USBTYPE_BLACKLIST= AUTOSUSPEND_USBID_WHITELIST= AUTOSUSPEND_USBTYPE_WHITELIST= BATT_SUSPEND_USB=1 LM_AC_SUSPEND_USB=0 NOLM_AC_SUSPEND_USB=0 AUTOSUSPEND_TIMEOUT=2 -- no debconf information ---End Message--- ---BeginMessage--- On 07/21/2014 09:50 PM, Matthew Gabeler-Lee wrote: The lmt-udev script appears to be breaking systemd boot for me due to introducing a deadlock / dependency circle. Based on usage of debug-shell.service, it appears that systemd is waiting for udev to settle, which is needed for the lvm2 volumes to be present and active, which is needed for /usr to be mounted. However, the lmt-udev script is waiting for /usr to be mounted too, and this appears to be blocking the udev settle. The timeout for lmt-udev to wait for /usr is as long as the timeout for udevadm settle, and so eventually this times out and the system tries to limp along and finish booting, but many things are not started properly in this case. The lmt-udev script appears to be trying to run itself in the background, but this is not successful, as udev / systemd are clearly waiting on it. Based on the arguments to the script, it appears that this is related to usb autosuspend. Removing laptop-mode-tools causes my system to boot properly. In the 1.65-2 release, usb-autosuspend module was removed. Please re-open if you have other modules causing the conflict. And please, it may be serious for you, but not for
Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
On 07/21/2014 09:50 PM, Matthew Gabeler-Lee wrote: The lmt-udev script appears to be breaking systemd boot for me due to introducing a deadlock / dependency circle. Based on usage of debug-shell.service, it appears that systemd is waiting for udev to settle, which is needed for the lvm2 volumes to be present and active, which is needed for /usr to be mounted. However, the lmt-udev script is waiting for /usr to be mounted too, and this appears to be blocking the udev settle. The timeout for lmt-udev to wait for /usr is as long as the timeout for udevadm settle, and so eventually this times out and the system tries to limp along and finish booting, but many things are not started properly in this case. The lmt-udev script appears to be trying to run itself in the background, but this is not successful, as udev / systemd are clearly waiting on it. Based on the arguments to the script, it appears that this is related to usb autosuspend. Removing laptop-mode-tools causes my system to boot properly. In the 1.65-2 release, usb-autosuspend module was removed. Please re-open if you have other modules causing the conflict. And please, it may be serious for you, but not for laptop-mode-tools in general. Please be more judicious when choosing the severity. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
Bug#755059: redmine: Unable to install backported version of Redmine (2.5.1-2~bpo70+1) due to missing deps
Hi Fabien, On Thu, Jul 17, 2014 at 10:20:54AM +, Fabien Boucher wrote: Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Package: redmine Version: 2.5.1-2~bpo70+1 Severity: grave Justification: renders package unusable Dear Maintainer, I cannot install the wheezy-backport version of Redmine since today due to the new uploaded debian version of redmine. Some dependencies are unavailable in backport but only in jessie/sid/exp. I'm not sure but I guess that dependencies for Redmine should be at least in backport too. Here are the apt error: You are right. I have just uploaded a fixed version 2.5.1-2~bpo70+2 that will solve most of the dependency problems, _except_ the absence of ruby-awesome-nested-set. That package should be available in wheezy-backports in a few days, but until then it is safe to grab the package from unstable and install it manually before installing redmine from wheezy-backports. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#755528: moc not working: FATAL_ERROR: Can't receive value from the
Package: moc Version: 1:2.5.0~beta2-1+b1 Severity: serious Justification: unusuable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? What I did today was: Open moc (mocp) trying to play a *.mp4, but my mp4_s weren't shown (as they use to be). But I could play mp3_s. I noticed moc-ffmpeg-plugin was missing and installed it - *.mp4 files were shown but there was an error, something like ..couldn't initiate sent() on server or the like. I reinstalled moc and moc-ffmpeg-plugin and rebooted. *.mp4 files still shown, but now a different error, no matter what files (mp3 or mp4) I try to play: FATAL_ERROR: Can't receive value from the server! Neither deleteing ~/.moc or rm -rf ~/.moc/cache nor --reinstall does solve the problem. Currently moc is unusuable here. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.15-6.towo-siduction-686 (SMP w/1 CPU core; PREEMPT) 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 moc depends on: ii libasound21.0.28-1 ii libc6 2.19-7 ii libcurl3-gnutls 7.37.1-1 ii libdb5.3 5.3.28-5 ii libfaad2 2.7-8 ii libflac8 1.3.0-2 ii libgcc1 1:4.9.1-1 ii libid3tag00.15.1b-10 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140610git97e0e80b~dfsg-1 ii libltdl7 2.4.2-1.7 ii libmad0 0.15.1b-8 ii libmagic1 1:5.19-1 ii libmodplug1 1:0.8.8.4-4.1 ii libmpcdec62:0.1~r459-4.1 ii libncursesw5 5.9+20140712-2 ii libogg0 1.3.2-1 ii libopusfile0 0.5-1 ii librcc0 0.2.12-0.1 ii libresid-builder0c2a 2.1.1-14 ii libsamplerate00.1.8-8 ii libsidplay2 2.1.1-14 ii libsidutils0 2.1.1-14 ii libsndfile1 1.0.25-9 ii libspeex1 1.2~rc1.1-1 ii libstdc++64.9.1-1 ii libtagc0 1.9.1-2.1 ii libtinfo5 5.9+20140712-2 ii libvorbis0a 1.3.2-1.4 ii libvorbisfile31.3.2-1.4 ii libwavpack1 4.70.0-1 ii zlib1g1:1.2.8.dfsg-1 moc recommends no packages. Versions of packages moc suggests: ii moc-ffmpeg-plugin 1:2.5.0~beta2-1+b1 -- 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#755484: Unfulfillable dependency on libgtkspell-3-0
Control: reassign -1 libgwibber-gtk2 3.5.2-1 On Lu, 21 iul 14, 11:52:29, martin f krafft wrote: Source: libgwibber-gtk2 Version: 3.5.2-1 Severity: serious The dependency should be on libgtkspell3-3-0, not libgtkspell-3-0. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Processed: Re: Bug#755484: Unfulfillable dependency on libgtkspell-3-0
Processing control commands: reassign -1 libgwibber-gtk2 3.5.2-1 Bug #755484 [src:libgwibber-gtk2] Unfulfillable dependency on libgtkspell-3-0 Warning: Unknown package 'src:libgwibber-gtk2' Bug reassigned from package 'src:libgwibber-gtk2' to 'libgwibber-gtk2'. No longer marked as found in versions libgwibber-gtk2/3.5.2-1. Ignoring request to alter fixed versions of bug #755484 to the same values previously set Bug #755484 [libgwibber-gtk2] Unfulfillable dependency on libgtkspell-3-0 Marked as found in versions gwibber/3.5.2-1. -- 755484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755484 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#755484: Unfulfillable dependency on libgtkspell-3-0
Processing control commands: reassign -1 src:libgwibber-gtk2 3.5.2-1 Bug #755484 [src:libgwibber-gtk2] Unfulfillable dependency on libgtkspell-3-0 Warning: Unknown package 'src:libgwibber-gtk2' Ignoring request to reassign bug #755484 to the same package Warning: Unknown package 'src:libgwibber-gtk2' Bug #755484 [src:libgwibber-gtk2] Unfulfillable dependency on libgtkspell-3-0 Warning: Unknown package 'src:libgwibber-gtk2' The source 'libgwibber-gtk2' and version '3.5.2-1' do not appear to match any binary packages Ignoring request to alter found versions of bug #755484 to the same values previously set Warning: Unknown package 'src:libgwibber-gtk2' -- 755484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755484 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#754830: [Pkg-bluetooth-maintainers] Bug#754830: bluez: rfcomm and bluetoothd fail to start
On 16/07/14 01:34, Nobuhiro Iwamatsu wrote: tags 754830 pending thanks Hi, Thanks for your report. I will fix this next upload. That's great! It'd be good to see this (and #755274) fixed soon as they are blocking bluez from migrating to testing. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755484: Unfulfillable dependency on libgtkspell-3-0
Control: reassign -1 src:libgwibber-gtk2 3.5.2-1 On Lu, 21 iul 14, 11:52:29, martin f krafft wrote: Source: libgwibber-gtk2 Version: 3.5.2-1 Severity: serious The dependency should be on libgtkspell3-3-0, not libgtkspell-3-0. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#706185: your mail
Hi Helmut, On 07/18/2014 03:52 PM, Helmut Grohne wrote: While your patch moves a lot of files, it does not address the underlying problem. The libpam-ldap package still creates the very same configuration files using its postinst script and it still removes them in postrm. Right. As I explained to you, I was planning to create a config-only package, and a different package for the binaries, which doesn't seem to be the best solution, as you already explained. So, since these /etc/pam_ldap.conf is not a conffile, I am creating a patch that just removes the file if there is no further package (libpam_ldap) installed in the system (as from a different arch), thus, olving the problem here specified, as it doesn't remove the /etc/pam_ldap.conf files if there are further packages installed in the system. I didn't touch the postinst packages because it is already configured to not override an already installed configuration file. The scripts becomes very short, and I am attaching as a RFC. Thank you, Breno Index: libpam-ldap/libpam-ldap-184/debian/libpam-ldap.postrm === --- libpam-ldap.orig/libpam-ldap-184/debian/libpam-ldap.postrm +++ libpam-ldap/libpam-ldap-184/debian/libpam-ldap.postrm @@ -7,7 +7,8 @@ PASSWDFILE=/etc/pam_ldap.secret action=$1 -if [ $action = purge ]; then +if [ $action = purge ] \ +[ $(dpkg-query --show libpam-ldap 2 /dev/null | wc -l) = 1 ]; then rm -f $CONFFILE $PASSWDFILE fi Index: libpam-ldap/libpam-ldap-184/debian/libpam-ldap.prerm === --- libpam-ldap.orig/libpam-ldap-184/debian/libpam-ldap.prerm +++ libpam-ldap/libpam-ldap-184/debian/libpam-ldap.prerm @@ -2,7 +2,8 @@ set -e -if [ $1 = remove ]; then +if [ $1 = remove ] \ +[ $(dpkg-query --show libpam-ldap 2 /dev/null | wc -l) = 1 ]; then pam-auth-update --package --remove ldap fi
Bug#741331: marked as done (ruby-rspec-puppet - Fails to find rspec: Could not find rspec (= 2.0.0) amongst [] (Gem::LoadError))
Your message dated Mon, 21 Jul 2014 21:24:12 + with message-id e1x9l48-0002m6...@franck.debian.org and subject line Bug#741331: fixed in ruby-puppetlabs-spec-helper 0.4.1-2 has caused the Debian Bug report #741331, regarding ruby-rspec-puppet - Fails to find rspec: Could not find rspec (= 2.0.0) amongst [] (Gem::LoadError) 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.) -- 741331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-rspec-puppet Version: 1.0.1-1 Severity: important A minimal rspec/puppet setup fails to find rspec: | $ rspec | /usr/lib/ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find rspec (= 2.0.0) amongst [] (Gem::LoadError) | from /usr/lib/ruby/1.9.1/rubygems/dependency.rb:256:in `to_spec' | from /usr/lib/ruby/1.9.1/rubygems.rb:1231:in `gem' | from /usr/lib/ruby/vendor_ruby/puppetlabs_spec_helper/puppet_spec_helper.rb:10:in `top (required)' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `require' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `rescue in require' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:35:in `require' | from /usr/lib/ruby/vendor_ruby/puppetlabs_spec_helper/module_spec_helper.rb:2:in `top (required)' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `require' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `rescue in require' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:35:in `require' | from …/spec/spec_helper.rb:2:in `top (required)' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `require' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `rescue in require' | from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:35:in `require' | from …/spec/defines/grub2_spec.rb:1:in `top (required)' | from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load' | from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `block in load_spec_files' | from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `each' | from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load_spec_files' | from /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:22:in `run' | from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run' | from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in autorun' | $ cat spec/defines/grub2_spec.rb | require 'spec_helper' | | describe 'sysinit::grub2' do | | end | $ cat spec/spec_helper.rb | require 'rubygems' | require 'puppetlabs_spec_helper/module_spec_helper' | $ cat Rakefile | require 'rubygems' | require 'puppetlabs_spec_helper/rake_tasks' Bastian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby-rspec-puppet depends on: ii ruby 1:1.9.3 ii ruby-rspec2.14.1-1 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-1 ruby-rspec-puppet recommends no packages. ruby-rspec-puppet suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: ruby-puppetlabs-spec-helper Source-Version: 0.4.1-2 We believe that the bug you reported is fixed in the latest version of ruby-puppetlabs-spec-helper, 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 741...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier bou...@debian.org (supplier of updated ruby-puppetlabs-spec-helper 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: Mon, 21 Jul 2014 22:17:01 +0200 Source: ruby-puppetlabs-spec-helper Binary:
Bug#754177: marked as done (stumpwm does not work if `cl-asdf' is not installed.)
Your message dated Mon, 21 Jul 2014 21:24:20 + with message-id e1x9l4g-0002om...@franck.debian.org and subject line Bug#754177: fixed in stumpwm 2:0.9.8-5 has caused the Debian Bug report #754177, regarding stumpwm does not work if `cl-asdf' is not installed. 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.) -- 754177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: stumpwm Version: 2:0.9.8-1 Severity: grave Justification: renders package unusable Dear Maintainer, after installing `stumpwm' I could not start the window manager. There was some error message mentioning `asdf', which was *not* installed. Note that `cl-asdf' is not `required' by `stumpwm', just `recommended'. After `cl-asdf' was installed, I could start `stumpwm' as expected. Thank you for your time! Emilio -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages stumpwm depends on: ii cl-ppcre 2.0.3-1 ii clisp-module-clx 1:2.49-8.2 Versions of packages stumpwm recommends: ii cl-asdf 2:3.0.3-1 Versions of packages stumpwm suggests: ii iceweasel [www-browser] 30.0-2 ii info [info-browser] 5.2.0.dfsg.1-4 ii menu 2.1.47 ii rlwrap 0.37-5 pn slimenone ii w3m [www-browser]0.5.3-16 ii x11-utils7.7+1 ii xterm [x-terminal-emulator] 308-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: stumpwm Source-Version: 2:0.9.8-5 We believe that the bug you reported is fixed in the latest version of stumpwm, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Milan Zamazal p...@debian.org (supplier of updated stumpwm 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: Mon, 21 Jul 2014 22:46:21 +0200 Source: stumpwm Binary: stumpwm Architecture: source all Version: 2:0.9.8-5 Distribution: unstable Urgency: low Maintainer: Debian Common Lisp Team pkg-common-lisp-de...@lists.alioth.debian.org Changed-By: Milan Zamazal p...@debian.org Description: stumpwm- tiling, keyboard driven Common Lisp window manager Closes: 754177 Changes: stumpwm (2:0.9.8-5) unstable; urgency=low . * Depend on cl-asdf; closes: #754177. Checksums-Sha1: 28c0d2f58620d4183c804e41dd5827eee6887479 1440 stumpwm_0.9.8-5.dsc e6224bb540840610255e404a145548a4ced818e7 97056 stumpwm_0.9.8-5.debian.tar.xz e56cb5ec792c1b2ceb1cd1aeb3bc6e7188f5a51c 290358 stumpwm_0.9.8-5_all.deb Checksums-Sha256: 1d075e0a9a5f7a1b6fef8cb632d604361b1807060c5fb9b5411b6bd4da8c1f20 1440 stumpwm_0.9.8-5.dsc 794733439d4d61575867cb1c1df81a26e7b6c252fddf8ff9544403016501a75d 97056 stumpwm_0.9.8-5.debian.tar.xz 6bfd909f497f4af58e04a9029423b349a43132dff431f6f1d374a6543592093d 290358 stumpwm_0.9.8-5_all.deb Files: c0257a8bfe4cc4b976653ded4b856c75 290358 x11 optional stumpwm_0.9.8-5_all.deb 4d30262e5a52e8808b2bca1f98fbff7c 1440 x11 optional stumpwm_0.9.8-5.dsc 3177dc6e777bff76990841417d88c4e3 97056 x11 optional stumpwm_0.9.8-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlPNgKMACgkQkSkk/j3Cm0HFDQCgle38GUqRAcSMUl/S92cnYmnf UuAAnRg8Ovny7zUTjt0S4ITJ4pSJmq8H =eQT/ -END PGP SIGNATUREEnd Message---
Bug#755537: boot hangs at Loading, please wait...
Package: plymouth Version: 0.9.0-4 Severity: serious Since the migration of plymouth 0.9.0-4 to testing, my (testing) laptop no longer boots properly with plymouth. It just hangs at Loading, please wait... immediately after grub choice. At that point, in theory, it should ask my passphrase to unluck my encrypted LVM drives, but it doesn't. I've even tried entering the passphrase (with console echo...), but that didn't work either. Removing the splash option from the grub boot entry makes the boot completely properly (obviously without any graphical splash screen). As during the past weeks I've also played with init systems, I can confirm that the problem is present with both sysvinit and systemd. FWIW, my /etc/plymouth/plymouthd.conf looks like this: zack@timira:~$ cat /etc/plymouth/plymouthd.conf # Administrator customizations go in this file #[Daemon] #Theme=text #ShowDelay=0 zack@timira:~$ Cheers. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 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 plymouth depends on: ii init-system-helpers 1.19 ii initramfs-tools 0.115 ii libc62.19-7 ii libudev1 208-6 ii multiarch-support2.19-7 plymouth recommends no packages. Versions of packages plymouth suggests: ii desktop-base 7.0.3 ii plymouth-drm 0.9.0-4 -- 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#751828: pcre3: FTBFS [ppc64el]: Test failure in common with amd64
Thanks for the patch. In fact I was intending to do an upload yesterday, and held off when I saw this message. Looking at the bugs you filed on PCRE and glib (thanks), it looks like I should go ahead with a pcre 8.35 release, and glib will have to deal with this, do you agree? On 20 Jul 2014, at 18:56, Simon McVittie s...@debian.org wrote: On Sun, 20 Jul 2014 at 16:07:06 +0100, Simon McVittie wrote: This was already reported as http://bugs.exim.org/show_bug.cgi?id=1463 and fixed upstream as part of r1472. However, the upstream fix did not update the expected output, so the tests still fail. The upstream fix did in fact update the expected output, I just wasn't paying enough attention to the other contents of the svn commit. I plan to do a delayed NMU soon with the attached changes, if the maintainer doesn't upload first. However, I haven't done so yet, because the updated pcre3 seems to trigger a test failure in the pcre consumer I'm mainly interested in (GLib), and I want to be sure that these changes aren't what's to blame for that. Thanks, S pcre3-nmudiff-751828.diff -- 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 753510 is important
Processing commands for cont...@bugs.debian.org: severity 753510 important Bug #753510 [liblognorm1] liblognorm1 - Conflicts against liblognorm0 without justification Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 753510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753510 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#753211: marked as done (qcustomplot: FTBFS: CMake Errors)
Your message dated Mon, 21 Jul 2014 22:03:50 + with message-id e1x9lgu-00077j...@franck.debian.org and subject line Bug#753211: fixed in qcustomplot 1.2.1-1 has caused the Debian Bug report #753211, regarding qcustomplot: FTBFS: CMake Errors 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.) -- 753211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: qcustomplot Version: 1.2.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140628 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh build --parallel dh_testdir -O--parallel dh_auto_configure -O--parallel -- The CXX compiler identification is GNU 4.9.0 -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 (message): The imported target Qt5::Gui references the file Qt5Gui_EGL_LIBRARY-NOTFOUND but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake but not all the files it references. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:31 (_qt5_Gui_check_file_exists) /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:58 (_qt5gui_find_extra_libs) /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:155 (include) /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:100 (find_package) CMakeLists.txt:9 (FIND_PACKAGE) -- Configuring incomplete, errors occurred! See also /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log. dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None returned exit code 1 make: *** [build] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/28/qcustomplot_1.2.0-1_unstable.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: qcustomplot Source-Version: 1.2.1-1 We believe that the bug you reported is fixed in the latest version of qcustomplot, 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 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky gl...@debian.org (supplier of updated qcustomplot 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: Mon, 21 Jul 2014 23:37:07 +0200 Source: qcustomplot Binary: libqcustomplot-dev libqcustomplot-doc libqcustomplot1.2 libqcustomplot1.2-dbg Architecture: source amd64 all Version: 1.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Anton Gladky gl...@debian.org Description: libqcustomplot-dev - Qt C++ widget for plotting. Header libqcustomplot-doc - Qt C++ widget for plotting. Documentation and examples libqcustomplot1.2 - Qt C++ widget for plotting libqcustomplot1.2-dbg - Qt C++ widget for plotting. Debugging symbols Closes: 753211 Changes: qcustomplot (1.2.1-1) unstable; urgency=medium . * [95aa0fd] Imported Upstream version 1.2.1. (Closes: #753211) * [334dfb7] Use wrap and sort. * [2f0e8f1] Add autopkgtest. Checksums-Sha1: 12843c18539a774f1227be58b199b61e8141bf74 2235
Bug#755543: gnome-shell-pomodoro: uninstallable on sid
Package: gnome-shell-pomodoro Version: 0.8.0-1 Severity: serious Your package is uninstallable on sid as it depends on gnome-shell ( 3.9), gnome-shell (= 3.7) but sid has gnome-shell 3.12. You probably want to upload the package from experimental to sid. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751644: marked as done (pystache: Depends on python3.3, which is due to be removed soon)
Your message dated Mon, 21 Jul 2014 23:19:54 + with message-id e1x9ms6-0007ts...@franck.debian.org and subject line Bug#751644: fixed in pystache 0.5.4-2 has caused the Debian Bug report #751644, regarding pystache: Depends on python3.3, which is due to be removed soon 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.) -- 751644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pystache Version: 0.5.3-4 Severity: important python3.3 is due to be removed from the archive soon. Once that happens, this package will be uninstallable and this bug will be RC. In order to prevent this from happening, please upload a rebuilt version soon that closes this bug. No changes should be needed, but since the package is arch:all it can't be binNMUed. ---End Message--- ---BeginMessage--- Source: pystache Source-Version: 0.5.4-2 We believe that the bug you reported is fixed in the latest version of pystache, 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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kouhei Maeda mkou...@palmtb.net (supplier of updated pystache 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: Sun, 20 Jul 2014 00:46:22 +0900 Source: pystache Binary: python-pystache python3-pystache Architecture: source all Version: 0.5.4-2 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda mkou...@palmtb.net Changed-By: Kouhei Maeda mkou...@palmtb.net Description: python-pystache - Python implementation of Mustache python3-pystache - Python3 implementation of Mustache Closes: 751644 Changes: pystache (0.5.4-2) unstable; urgency=medium . * Rebuild to drop python3.3 dependencies (Closes: #751644) - Set shebang for dh_python3 to /usr/bin/python3 to avoid python3.x version specific depend. - Thanks Scott Kitterman sc...@kitterman.com for NMU. I had missed his NMU 0.5.3-4.1, I have applied the same fix again. Checksums-Sha1: 3bf5f738f5fee0cd468aff4d03f5b2236d2805dc 1845 pystache_0.5.4-2.dsc 8ad3acbc53731f89e8be21aea7a2f91bbd9961db 4400 pystache_0.5.4-2.debian.tar.xz 541e461929a41b86bc1345f3d4ad0f656f3b642f 35198 python-pystache_0.5.4-2_all.deb 912034edf044a65a4cdc5d62b40d43519b98cc6a 27334 python3-pystache_0.5.4-2_all.deb Checksums-Sha256: ba760ce4cbd858c5a5801144091f3567e945f0571653294cbc693589f6b0490c 1845 pystache_0.5.4-2.dsc 7c6e882b6515622043178becda84686811bf194d7f07dffc0a7c130cb673261d 4400 pystache_0.5.4-2.debian.tar.xz fadb2f24ed8f0a55e07fc91ff436002f47dfd4455dd0e23aab819f18f23ecb8c 35198 python-pystache_0.5.4-2_all.deb 71533b2c942e6ef18f892dbf0d5013aa4c95d6b4da99f46f0239887fa6bce613 27334 python3-pystache_0.5.4-2_all.deb Files: f94ff5f5fc6ab220ade651b3dc081f99 35198 python optional python-pystache_0.5.4-2_all.deb e95c2358b93262fe8052a25820f81aa6 27334 python optional python3-pystache_0.5.4-2_all.deb dfaf4d69e8b314eae57a5cae0e7f6670 1845 python optional pystache_0.5.4-2.dsc b6c415e822cb4d8bc4dca94468f496d6 4400 python optional pystache_0.5.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTzZ6GAAoJEDIkf7tArR+mcYgQAJSU9WEwkjHGxKI37bVQ4qZI 2+RiVZ1+xmRODmehlxh8IsoHl+aQIC6cq8MlPRIIaaEjc4/bjXALWkr0WckMS0pm bBAQ0a/cp+NJm5Qr04CVJ54MhZ3w/MsJbfCnsROnp6L/ULYdfZ3sKeMgwQpkc7u9 +o0+90FnbKmAjP5PnKI9VO2cYy2GTlTtCg04hR3BBRIVsTAjAA5p0PH6jL7r43sZ SPrUqi33lsLkhGbJZ7VJjjN/8pAiNJmoi9nRHjQVh6mgBspq/GNHuonxQYW/Tf9l SoCVWQ34f8QqsBc6k0x3/eQbVg9hgL8zRcIj/adXVnvR1HJ+HhPQ2+BFilEhXdPs 3eVwyhUwbOzqm8gW/VfdhhpSGje8otVLY8HKd2rWBDi1Ec3gkcLhStLN4/87SRUy Y4hkPTPs83C9tkYKSOsOqWwVwmf1gbC6Gd571ijn8vS1kXwDqxa/jbhYcB6glLiL Tu03KrADwDRY3oCS3mMnArbBWqZUM+ORXea45/D3n3X8l1o+gicQfAem5aowYWb1 kxiPwXO32MUWHetqE0HSO5Kdu0Qv3eQvQztdVdt3w0IDY/FFq2w5I2+i+Jo2ZUtD f8C7YSNYvBaU7rU9LlEBJn7+ILBfKdw24uJ+YcMDnPY9AxhRXH8V+hW9ImJl5Rh4 EEIpUd02SkKq8Wx4s8Ar =VPDj -END PGP SIGNATUREEnd Message---
Bug#751828: pcre3: FTBFS [ppc64el]: Test failure in common with amd64
On Mon, 21 Jul 2014 at 22:18:47 +0100, Mark Baker wrote: Thanks for the patch. In fact I was intending to do an upload yesterday, and held off when I saw this message. Looking at the bugs you filed on PCRE and glib (thanks), it looks like I should go ahead with a pcre 8.35 release, and glib will have to deal with this, do you agree? I think that's correct, yes. The patches I sent upstream to GLib haven't been reviewed yet; but PCRE 8.35 is already in unstable on amd64, so it's already causing trouble for GLib, and an upload that builds on the other architectures would at least make multiarch work again. In any future PCRE updates it's probably worthwhile to try rebuilding glib2.0 against the new PCRE before uploading to unstable - its regression tests are fairly comprehensive. If the tests fail, either the new PCRE is problematic, or glib2.0 will need some attention before bringing in the new PCRE. Either way, I'm sure the glib2.0 maintainers would appreciate caution. Regards, 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: [Pkg-bluetooth-maintainers] Processed: Re: Bug#755345: obexpushd: FTBFS: bluetooth.h:177:9: error: expected specifier-qualifier-list before 'typeof'
Processing commands for cont...@bugs.debian.org: tags 755345 pending Bug #755345 [src:bluez] obexpushd: FTBFS: bluetooth.h:177:9: error: expected specifier-qualifier-list before 'typeof' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 755345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755345 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#755345: [Pkg-bluetooth-maintainers] Processed: Re: Bug#755345: obexpushd: FTBFS: bluetooth.h:177:9: error: expected specifier-qualifier-list before 'typeof'
tags 755345 pending
thanks
Hi,
I confirmed this problem. I fixed in my local changes.
I will fix this in next upload.
Best regards,
Nobuhiro
2014-07-20 10:00 GMT+09:00 Debian Bug Tracking System ow...@bugs.debian.org:
Processing control commands:
reassign -1 src:bluez
Bug #755345 [src:obexpushd] obexpushd: FTBFS: bluetooth.h:177:9: error:
expected specifier-qualifier-list before 'typeof'
Bug reassigned from package 'src:obexpushd' to 'src:bluez'.
No longer marked as found in versions obexpushd/0.11.2-1.
Ignoring request to alter fixed versions of bug #755345 to the same values
previously set
affects -1 src:obexpushd
Bug #755345 [src:bluez] obexpushd: FTBFS: bluetooth.h:177:9: error: expected
specifier-qualifier-list before 'typeof'
Added indication that 755345 affects src:obexpushd
--
755345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Pkg-bluetooth-maintainers mailing list
pkg-bluetooth-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bluetooth-maintainers
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754642: marked as done (cdrkit: FTBFS on kfreebsd-*: /usr/bin/ld: cannot find -lcap)
Your message dated Tue, 22 Jul 2014 00:18:31 + with message-id e1x9nmp-0005vs...@franck.debian.org and subject line Bug#754642: fixed in cdrkit 9:1.1.11-3 has caused the Debian Bug report #754642, regarding cdrkit: FTBFS on kfreebsd-*: /usr/bin/ld: cannot find -lcap 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.) -- 754642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cdrkit Version: 9:1.1.11-2.1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-*: | [ 88%] Building C object wodim/CMakeFiles/wodim.dir/xio.o | Linking C executable wodim | /usr/bin/ld: cannot find -lcap | collect2: error: ld returned 1 exit status | make[4]: *** [wodim/wodim] Error 1 | wodim/CMakeFiles/wodim.dir/build.make:689: recipe for target 'wodim/wodim' failed Full build logs: https://buildd.debian.org/status/fetch.php?pkg=cdrkitarch=kfreebsd-amd64ver=9%3A1.1.11-2.1stamp=1404395274 https://buildd.debian.org/status/fetch.php?pkg=cdrkitarch=kfreebsd-i386ver=9%3A1.1.11-2.1stamp=1404395187 Mraw, KiBi. ---End Message--- ---BeginMessage--- Source: cdrkit Source-Version: 9:1.1.11-3 We believe that the bug you reported is fixed in the latest version of cdrkit, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve McIntyre 93...@debian.org (supplier of updated cdrkit 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: Tue, 22 Jul 2014 00:56:34 +0100 Source: cdrkit Binary: wodim genisoimage icedax cdrkit-doc Architecture: source all amd64 Version: 9:1.1.11-3 Distribution: unstable Urgency: medium Maintainer: Joerg Jaspert jo...@debian.org Changed-By: Steve McIntyre 93...@debian.org Description: cdrkit-doc - Documentation for the cdrkit package suite genisoimage - Creates ISO-9660 CD-ROM filesystem images icedax - Creates WAV files from audio CDs wodim - command line CD/DVD writing tool Closes: 754642 Changes: cdrkit (9:1.1.11-3) unstable; urgency=medium . * Fix FTBFS on kfreebsd-*. Closes: #754642. kfreebsd-* now includes a sys/capability.h which is not compatible with the same file on linux, and nor does it imply -lcap will work. Fix the detection code to cope with this. Checksums-Sha1: 71b28fa3122c48466b2a2538283aacac0495beb5 2001 cdrkit_1.1.11-3.dsc c45fb87648a85b4a31c56ee899b958e821128866 28125 cdrkit_1.1.11-3.diff.gz 46d18b1cefff7801cf2556630ca31d9373b86c0e 150750 cdrkit-doc_1.1.11-3_all.deb 62712204b56b0e069f4652d34ceb9a1e8225b997 170584 icedax_1.1.11-3_amd64.deb 1aff7a2cbe46f1df4ae2d58df12d413a262c44db 341624 wodim_1.1.11-3_amd64.deb cef4046caa77bdfcea5738de79886644218d5bae 359786 genisoimage_1.1.11-3_amd64.deb Checksums-Sha256: a7f8a6110accd8ad7d77d76e7969b2d05e7477f3cffc3662e76318b241b2b252 2001 cdrkit_1.1.11-3.dsc 844f14425b79a58c585b10adf56db7d7e430843e8fdd11308f217864bf1cef5b 28125 cdrkit_1.1.11-3.diff.gz b4ea9bf0d52828f7c11e96cb23fdce3d6ede8deaee3c03f59d3e091d3f2e90fb 150750 cdrkit-doc_1.1.11-3_all.deb 36dbc05a15db8adc9741484870707d2f1594a91e1460d4ba34487d1f98fbf003 170584 icedax_1.1.11-3_amd64.deb ec99087a062626a1ddf22fa08b9a85bceb1398742482a8f311d0fa9b7f06dbca 341624 wodim_1.1.11-3_amd64.deb ff8ee0663a7cde69ffaa572c7f42ca908e3247987e8a12c05ffc213fdd1b0329 359786 genisoimage_1.1.11-3_amd64.deb Files: 508f8f7b3b8162bf5d5ca005eae6255f 150750 doc optional cdrkit-doc_1.1.11-3_all.deb a5fa4a2d7ebe8ea1f01c48f2cdcbebb1 170584 sound optional icedax_1.1.11-3_amd64.deb c9d67a0d635521a58f4cf6e5b9484954 341624 otherosfs optional wodim_1.1.11-3_amd64.deb 6f9b4997a7c821d78d2cf21f947ee1da 359786 otherosfs optional genisoimage_1.1.11-3_amd64.deb 1e5281cc8738b3b997f717c7a5d439f7 2001 otherosfs optional cdrkit_1.1.11-3.dsc 72651c180c74b80fb868a600dd52600b 28125 otherosfs optional cdrkit_1.1.11-3.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJTzaxdAAoJEFh5eVc0QmhOIVIQAIILsnu5Rl2npHZfiyogs3RN 59LAfYRe6obh/JUpooQQo7yVwyQJegcmJY3GSBQNy3bWjrMST8zN3QGgCyISdTnE
Processed: wxastrocapture: Please update to use wxwidgets3.0
Processing control commands: block 748169 by -1 Bug #748169 [release.debian.org] transition: wxwidgets3.0 748169 was blocked by: 750918 751552 751558 749844 749974 741580 750737 741988 751939 741732 742576 749463 749843 749993 738849 751255 749487 743334 750084 749834 742031 750914 729677 748634 746609 750972 749870 750087 748715 749835 749659 751566 749687 750743 744115 752947 749140 750619 741391 749976 741072 750910 748085 750906 749861 749978 751262 750145 749454 750968 750001 749493 748639 751241 748722 749488 751554 749128 748169 was not blocking any bugs. Added blocking bug(s) of 748169: 78 -- 748169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748169 78: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78 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#755558: wxastrocapture: Please update to use wxwidgets3.0
Package: wxastrocapture Version: 1.8.1+git20140303+dfsg-2 Severity: serious User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Control: block 748169 by -1 Dear maintainer, As I noted in #741294 (the ITP bug for wxastrocapture), we're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released. I'm filing with severity serious as this blocks the on-going wxwidgets3.0 transition. Also it doesn't seem helpful to let the package migrate to testing only to have to kick it out again. Cheers, Olly -- 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 751255 is serious
Processing commands for cont...@bugs.debian.org: # blocks the on-going wxwidgets3.0 transition severity 751255 serious Bug #751255 [treeviewx] treeviewx: Please update to use wxwidgets3.0 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 751255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751255 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#750918: Fixed in last upload
reopen 750918 found 750918 0.10.1-1 thanks On Thu, Jul 10, 2014 at 02:52:35AM +0200, Bas Wijnen wrote: I forgot to close this bug in the changelog of the last upload; the new upstream release fixes it. Although the new upstream release apparently adds wx3 support, you didn't update the build dependencies in debian/control, so you're still building against wxwidgets2.8. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Fixed in last upload
Processing commands for cont...@bugs.debian.org:
reopen 750918
Bug #750918 {Done: Bas Wijnen wij...@debian.org} [src:openmsx-catapult]
openmsx-catapult: Please update to use wxwidgets3.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.10.1-1.
found 750918 0.10.1-1
Bug #750918 [src:openmsx-catapult] openmsx-catapult: Please update to use
wxwidgets3.0
Marked as found in versions openmsx-catapult/0.10.1-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
750918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750918
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#755559: libcap-dev: no longer provides: libcap2-dev
Package: libcap-dev Version: 1:2.24-1 Severity: serious Justification: breaks reverse-build-depends Hi, you removed those lines between 1:2.22-2 and 1:2.24-1: | Provides: libcap2-dev | Conflicts: libcap2-dev | Replaces: libcap2-dev That broke your reverse build-depending packages. KiBi. -- 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 752947 is serious
Processing commands for cont...@bugs.debian.org: # blocks the on-going wxwidgets3.0 transition severity 752947 serious Bug #752947 [extrema] extrema: Please update to use wxwidgets3.0 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 752947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752947 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#755026: marked as done (src:salt: FTBFS due to network access during build)
Your message dated Tue, 22 Jul 2014 01:20:03 + with message-id e1x9okn-0007ep...@franck.debian.org and subject line Bug#755026: fixed in salt 2014.1.7+ds-2 has caused the Debian Bug report #755026, regarding src:salt: FTBFS due to network access during build 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.) -- 755026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:salt Version: 2014.1.7+ds-1 Severity: serious Justification: fails to build from source (but built successfully in the past) During a rebuild of the archive on armhf, I'm afraid your package repeatedly failed to build. It hangs forever, with tail part of the output being: Making output directory... Running Sphinx v1.2.2 loading translations [en]... done loading pickled environment... not yet created [autosummary] generating autosummary for: contents.rst, faq.rst, index.rst, ref/auth/all/index.rst, ref/auth/all/salt.auth.auto.rst, ref/auth/all/salt.auth.keystone.rst, ref/auth/all/salt.auth.ldap.rst, ref/auth/all/salt.auth.pam.rst, ref/auth/all/salt.auth.stormpath_mod.rst, ref/cli/index.rst, ..., topics/tutorials/states_pt2.rst, topics/tutorials/states_pt3.rst, topics/tutorials/states_pt4.rst, topics/tutorials/states_pt5.rst, topics/tutorials/walkthrough.rst, topics/tutorials/walkthrough_macosx.rst, topics/tutorials/writing_tests.rst, topics/virt/disk.rst, topics/virt/index.rst, topics/virt/nic.rst loading intersphinx inventory from http://docs.python.org/3/objects.inv... Netstat includes the following: Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 10.0.1.5:59968 23.235.43.175:https ESTABLISHED 7404/python ---End Message--- ---BeginMessage--- Source: salt Source-Version: 2014.1.7+ds-2 We believe that the bug you reported is fixed in the latest version of salt, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joe Healy joehe...@gmail.com (supplier of updated salt 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: Tue, 22 Jul 2014 10:49:40 +1000 Source: salt Binary: salt-common salt-master salt-minion salt-syndic salt-ssh salt-doc salt-cloud Architecture: source all Version: 2014.1.7+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Salt Team pkg-salt-t...@lists.alioth.debian.org Changed-By: Joe Healy joehe...@gmail.com Description: salt-cloud - public cloud VM management system salt-common - shared libraries that salt requires for all packages salt-doc - additional documentation for salt, the distributed remote executi salt-master - remote manager to administer servers via salt salt-minion - client package for salt, the distributed remote execution system salt-ssh - remote manager to administer servers via salt salt-syndic - master-of-masters for salt, the distributed remote execution syst Closes: 755026 Changes: salt (2014.1.7+ds-2) unstable; urgency=medium . * [f04fd3a] Load intersphinx data from filesystem. Closes: 755026 Checksums-Sha1: a51e3a0defec0fd7ed8086e6f0e2ce4e8405 2433 salt_2014.1.7+ds-2.dsc 79d2bd588d764e298beb8c9f37dd294a1d74fff0 22736 salt_2014.1.7+ds-2.debian.tar.xz 134ac9b51657d8be85a4896bbad2943e598e46e0 1357104 salt-common_2014.1.7+ds-2_all.deb 38433ed9d63eb44724cbd9fd39bcd940da764985 35068 salt-master_2014.1.7+ds-2_all.deb 0baf9c1d51fac868207a2c6c1857580b5c080aa9 26060 salt-minion_2014.1.7+ds-2_all.deb 1f4e810c67dc9c64667f64e441dfdbcaa37881a8 18832 salt-syndic_2014.1.7+ds-2_all.deb fcc0236ba62bc84bb70b0486ea92d4409946d1d0 18494 salt-ssh_2014.1.7+ds-2_all.deb 419ad1976deb939f5905902747bf54e4fce0e9c5 1515760 salt-doc_2014.1.7+ds-2_all.deb 5e8815133b4cea7a9946ed40552fefa44bc2c7c9 18266 salt-cloud_2014.1.7+ds-2_all.deb Checksums-Sha256: ba06741b960c89b1cde4b8ebdbe399101c3d94b2c9b7c93d11ba34bc7e3299b7 2433 salt_2014.1.7+ds-2.dsc 712a4305a7f1f044ace803df85d0b8e008f700690764e1ba4dab2871345c50d4 22736 salt_2014.1.7+ds-2.debian.tar.xz
Bug#755561: berusky2: FTBFS on mips*: undefined reference to `mmalloc'
Source: berusky2 Version: 0.10-2 Severity: serious Justification: FTBFS Hi, your package no longer builds on mips*: | /bin/bash ../libtool --tag=CXX --mode=link g++ -D_FORTIFY_SOURCE=2 -D_DEBUG -Wall -Wno-write-strings -g -g -O2 -Wformat -Werror=format-security -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -I/usr/include/libdrm -Wl,-z,relro -Wl,--as-needed -lSDL_image -lSDL -lGLU -lGL -lX11 -lalut -lopenal -lvorbisfile -lvorbis -lm -logg -L/usr/lib/mips-linux-gnu -lz -lpthread -o berusky2 3D_graphic.o 3D_menus.o 3d_math.o Apak.o Apakio.o Bind.o Camera.o Comics.o Command.o Dda.o Demo.o Init.o Menu.o Menu2.o Tools.o animend_functions.o apakdir.o apakfind.o apakstream.o controls.o controls3d.o credits.o font.o font3d.o game_init.o game_logic.o game_main.o grammar.o load_level.o menu_script.o profiles.o setup.o square_cut.o trigers.o volume.o water.o 3dinterface.o Berusky3d.o Berusky3d_castice.o Berusky3d_ini.o Berusky3d_kamery.o Berusky3d_kofola2d.o Berusky3d_kofola_interface.o Berusky3d_light.o Berusky3d_load.o Berusky3d_render.o Di.o Load.o Load_chunks.o Load_out.o compat.o 2D_graph ic.o age.o alpha.o animation.o animation_time.o animation_track.o animation_track_bezier.o animation_track_linear.o bitmap.o box.o camera.o camera_interface.o color.o color_hsv.o draw.o ferguson.o gext.o glwrapper.o gpipe.o graph3d.o intersect.o lighting.o material.o material_texture.o matrix.o matrix_animated.o matrix_notified.o mesh.o normals.o obb.o object_base.o object_box.o object_geometry.o object_hierarchy.o object_list.o object_render_list.o object_scene.o object_transformation.o object_world.o polar.o print.o scene.o scene_import_3ds.o scene_import_b2m.o scene_import_txt.o scene_load.o selection.o surface.o surface_height.o surface_mask.o surface_sdl.o surface_sw.o texture_func.o texture_unit.o triangle.o vector.o vertex_arrays.o world_interface.o age_main.o events.o input.o timer.o change.o data_file.o ini.o log.o mem_alloc.o mtree.o utils.o animationk.o generator_random.o Ddx.o kfile.o Berusky3d_animace.o 3dmath.o 3dproject.o Mat3d.o Keyframe.o Texture.o Texture_import.o obbo.o Kdtree.o json_export.o ambient_sounds.o audio_plug-in.o 3d_math_k.o adas.o ogg_io.o ogg_stream.o compat_mini.o alut_test.o aabb.o | libtool: link: g++ -D_FORTIFY_SOURCE=2 -D_DEBUG -Wall -Wno-write-strings -g -g -O2 -Wformat -Werror=format-security -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -I/usr/include/libdrm -Wl,-z -Wl,relro -Wl,--as-needed -o berusky2 3D_graphic.o 3D_menus.o 3d_math.o Apak.o Apakio.o Bind.o Camera.o Comics.o Command.o Dda.o Demo.o Init.o Menu.o Menu2.o Tools.o animend_functions.o apakdir.o apakfind.o apakstream.o controls.o controls3d.o credits.o font.o font3d.o game_init.o game_logic.o game_main.o grammar.o load_level.o menu_script.o profiles.o setup.o square_cut.o trigers.o volume.o water.o 3dinterface.o Berusky3d.o Berusky3d_castice.o Berusky3d_ini.o Berusky3d_kamery.o Berusky3d_kofola2d.o Berusky3d_kofola_interface.o Berusky3d_light.o Berusky3d_load.o Berusky3d_render.o Di.o Load.o Load_chunks.o Load_out.o compat.o 2D_graphic.o age.o alpha.o animation.o animation_time.o animation_track.o animation_track_bezier.o animation_track_linear.o bitmap.o box.o camera.o camera_interface.o co lor.o color_hsv.o draw.o ferguson.o gext.o glwrapper.o gpipe.o graph3d.o intersect.o lighting.o material.o material_texture.o matrix.o matrix_animated.o matrix_notified.o mesh.o normals.o obb.o object_base.o object_box.o object_geometry.o object_hierarchy.o object_list.o object_render_list.o object_scene.o object_transformation.o object_world.o polar.o print.o scene.o scene_import_3ds.o scene_import_b2m.o scene_import_txt.o scene_load.o selection.o surface.o surface_height.o surface_mask.o surface_sdl.o surface_sw.o texture_func.o texture_unit.o triangle.o vector.o vertex_arrays.o world_interface.o age_main.o events.o input.o timer.o change.o data_file.o ini.o log.o mem_alloc.o mtree.o utils.o animationk.o generator_random.o Ddx.o kfile.o Berusky3d_animace.o 3dmath.o 3dproject.o Mat3d.o Keyframe.o Texture.o Texture_import.o obbo.o Kdtree.o json_export.o ambient_sounds.o audio_plug-in.o 3d_math_k.o adas.o ogg_io.o ogg_stream.o compat_mini.o alut_test.o aabb.o -lSDL_image -lSDL -lGLU -lGL -lX11 -lalut -lopenal /usr/lib/mips-linux-gnu/libvorbisfile.so /usr/lib/mips-linux-gnu/libvorbis.so -lm -logg -L/usr/lib/mips-linux-gnu -lz -lpthread | mesh.o: In function `vertex_allocate': | /«PKGBUILDDIR»/src/age/graph/mesh.cpp:59: undefined reference to `mmalloc' | /«PKGBUILDDIR»/src/age/graph/mesh.cpp:43: undefined reference to `mmalloc' | /«PKGBUILDDIR»/src/age/graph/mesh.cpp:47: undefined reference to `mmalloc' | /«PKGBUILDDIR»/src/age/graph/mesh.cpp:51: undefined reference to `mmalloc' | /«PKGBUILDDIR»/src/age/graph/mesh.cpp:55: undefined reference to `mmalloc' | mesh.o:/«PKGBUILDDIR»/src/age/graph/mesh.cpp:97: more undefined references to `mmalloc' follow |
Processed: Re: Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
Processing commands for cont...@bugs.debian.org:
severity 755518 normal
Bug #755518 {Done: Ritesh Raj Sarraf r...@debian.org} [laptop-mode-tools]
laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
Severity set to 'normal' from 'serious'
reopen 755518
Bug #755518 {Done: Ritesh Raj Sarraf r...@debian.org} [laptop-mode-tools]
laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
Bug reopened
Ignoring request to alter fixed versions of bug #755518 to the same values
previously set
retitle 755518 laptop-mode-tools: fails to boot when /usr is on LVM
Bug #755518 [laptop-mode-tools] laptop-mode-tools: USB Autosuspend + LVM2
filesystems = failed boot
Changed Bug title to 'laptop-mode-tools: fails to boot when /usr is on LVM'
from 'laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot'
quit
Stopping processing here.
Please contact me if you need assistance.
--
755518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755518
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#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
severity 755518 normal reopen 755518 retitle 755518 laptop-mode-tools: fails to boot when /usr is on LVM quit On Mon, 21 Jul 2014, Ritesh Raj Sarraf wrote: On 07/21/2014 09:50 PM, Matthew Gabeler-Lee wrote: Removing laptop-mode-tools causes my system to boot properly. In the 1.65-2 release, usb-autosuspend module was removed. Please re-open if you have other modules causing the conflict. And please, it may be serious for you, but not for laptop-mode-tools in general. Please be more judicious when choosing the severity. I'll accept that the severity I originally reported may not have been correct, and I've reduced that here (FWIW, I think I misread the descriptions and intended to make it important, not serious, but I'll go with normal for now). And clearly my analysis of the cause was flawed, and may be due to it first happening with 1.65-1 and the same symptoms happening with 1.65-2, leading me to assume the same causes. But nonetheless with l-m-t installed, my system fails to boot, and without it it boots fine. That doesn't seem worthy of close the bug. What information would be most helpful in tracking down the source of this failure? I presume enabling systemd debug and the debug-shell, and using that to capture ps auxww and/or pstree -alp while systemd is stuck would be a good start, along with journalctl output to get the systemd debug messages? -- -Matt Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755562: libkolabxml: FTBFS on all non-x86 archs due to symbols errors
Source: libkolabxml Version: 1.0.1-1 Severity: serious Justification: FTBFS Hi, your package's latest version only built on *amd64 and *i386. Other architectures are getting a build failure due to symbols-related changes. You'll find an overview page here with links to the full build logs: https://buildd.debian.org/status/package.php?p=libkolabxmlsuite=sid Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755563: libvirt: FTBFS on i386: test failure
Source: libvirt Version: 1.2.4-3.1 Severity: serious Justification: FTBFS [ NMUer x-d-cc'd ] Hi, your package no longer builds on i386 due to some test failures: | FAIL: test-ffs | FAIL: test-ffsl […] | | Testsuite summary for libvirt 1.2.4 | | # TOTAL: 211 | # PASS: 181 | # SKIP: 28 | # XFAIL: 0 | # FAIL: 2 | # XPASS: 0 | # ERROR: 0 | Full build log: https://buildd.debian.org/status/fetch.php?pkg=libvirtarch=i386ver=1.2.4-3.1stamp=1405785832 This package will need more hand holding anyway since it no longer builds on kfreebsd-*, being stuck in BD-Uninstallable: | libvirt build-depends on missing: | - libhal-dev see #710195, which apparently has a patch in VCS. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749974: maitreya: Please update to use wxwidgets3.0
On Fri, Jul 18, 2014 at 09:43:38PM +0200, Emilio Pozuelo Monfort wrote: On 18/07/14 21:33, Paul Elliott wrote: That worked in the sense of turning off the display of errors. But it feels like turning off a saftey mechanism. I am trying to contact the upstream for his advise. As I said, that is what you are already doing with wxwidget2.8, as that disables all the assertions for you! So building against wxwidgets3.0 with -DNDEBUG isn't a regression. Of course it would be better to not do that and fix all those assertions, and it is great that upstream is no longer hiding those problems. But we shouldn't block on that. A bugfix release with fixes for those can come at any moment. With my wx maintainer hat on, I definitely agree. It would be nice to fix these assertions, but it doesn't make sense to hold up the wxwidgets3.0 or libwxsqlite3-3.0-0/auto-wxsqlite3 transitions while you or upstream look into them. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755564: python-astropy: FTBFS on kfreebsd-i386: assertion error
Source: python-astropy Version: 0.4-3 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-i386 due to an assertion error: | === FAILURES === | test_compose_fractional_powers | | def test_compose_fractional_powers(): | x = (u.kg / u.s ** 3 * u.au ** 2.5 / u.yr ** 0.5 / u.sr ** 2) | | factored = x.compose() | | for unit in factored: |assert x.decompose() == unit.decompose() | E assert Unit(1.54085e+24 kg m(5/2) / (rad4 s(7/2))) == Unit(3.68726e+41 A2 / (rad4 s(5/2))) | E+ where Unit(1.54085e+24 kg m(5/2) / (rad4 s(7/2))) = bound method CompositeUnit.decompose of Unit(AU(5/2) kg / (s3 sr2 yr(1/2)))() | E+where bound method CompositeUnit.decompose of Unit(AU(5/2) kg / (s3 sr2 yr(1/2))) = Unit(AU(5/2) kg / (s3 sr2 yr(1/2))).decompose | E+ and Unit(3.68726e+41 A2 / (rad4 s(5/2))) = bound method CompositeUnit.decompose of Unit(1.6915e+59 Ry S / (rad4 s(7/2)))() | E+where bound method CompositeUnit.decompose of Unit(1.6915e+59 Ry S / (rad4 s(7/2))) = Unit(1.6915e+59 Ry S / (rad4 s(7/2))).decompose | | astropy/units/tests/test_units.py:391: AssertionError | = 1 failed, 4949 passed, 286 skipped, 13 xfailed, 6 xpassed in 183.33 seconds == Full build log: https://buildd.debian.org/status/fetch.php?pkg=python-astropyarch=kfreebsd-i386ver=0.4-3stamp=1405700993 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755467: marked as done ([nvidia-legacy-304xx-driver] Does not start the video driver since the last update 304.123-1)
Your message dated Tue, 22 Jul 2014 03:38:50 +
with message-id e1x9qug-0005fh...@franck.debian.org
and subject line Bug#755467: fixed in nvidia-graphics-drivers-legacy-304xx
304.123-2
has caused the Debian Bug report #755467,
regarding [nvidia-legacy-304xx-driver] Does not start the video driver since
the last update 304.123-1
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.)
--
755467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nvidia-legacy-304xx-driver
Severity: grave
--- Please enter the report below this line. ---
Hello maintainer,
After the last update of the driver, it is not working. I had to
uninstall it completely and use the nouveau driver. Which output you
need to verify the problem?
Kindly,
Davide Governale.
--- System information. ---
Architecture: i386
Kernel: Linux 3.14-1-686-pae
Debian Release: jessie/sid
500 unstablewww.deb-multimedia.org
500 unstableftp.de.debian.org
500 stable dl.google.com
1 experimentalftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
=-+-===
libgl1-nvidia-legacy-304xx-glx (= 304.123-1) | 304.123-1
xserver-xorg-video-nvidia-legacy-304xx (= 304.123-1) | 304.123-1
nvidia-legacy-304xx-alternative (= 304.123-1) | 304.123-1
nvidia-legacy-304xx-kernel-dkms(= 304.123-1) |
OR nvidia-legacy-304xx-kernel-304.123|
nvidia-support| 20131102+1
Recommends(Version) | Installed
===-+-===
nvidia-settings-legacy-304xx| 304.123-1
Suggests (Version) | Installed
===-+-==
nvidia-legacy-304xx-kernel-dkms (= 304.123) |
OR nvidia-legacy-304xx-kernel-source (= 304.123) |
signature.asc
Description: PGP signature
---End Message---
---BeginMessage---
Source: nvidia-graphics-drivers-legacy-304xx
Source-Version: 304.123-2
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-304xx, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Cheng vch...@debian.org (supplier of updated
nvidia-graphics-drivers-legacy-304xx 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: Mon, 21 Jul 2014 19:19:02 -0700
Source: nvidia-graphics-drivers-legacy-304xx
Binary: nvidia-legacy-304xx-driver xserver-xorg-video-nvidia-legacy-304xx
libgl1-nvidia-legacy-304xx-glx libgl1-nvidia-legacy-304xx-glx-i386
nvidia-legacy-304xx-alternative nvidia-legacy-304xx-kernel-dkms
nvidia-legacy-304xx-kernel-source
Architecture: source amd64
Version: 304.123-2
Distribution: unstable
Urgency: high
Maintainer: Debian NVIDIA Maintainers pkg-nvidia-de...@lists.alioth.debian.org
Changed-By: Vincent Cheng vch...@debian.org
Description:
libgl1-nvidia-legacy-304xx-glx - NVIDIA binary OpenGL
libraries${nvidia:LegacyDesc}
libgl1-nvidia-legacy-304xx-glx-i386 - NVIDIA binary OpenGL 32-bit
libraries${nvidia:LegacyDesc}
nvidia-legacy-304xx-alternative - allows the selection of NVIDIA as GLX
provider
nvidia-legacy-304xx-driver - NVIDIA metapackage${nvidia:LegacyDesc}
nvidia-legacy-304xx-kernel-dkms - NVIDIA binary kernel module DKMS
source${nvidia:LegacyDesc}
nvidia-legacy-304xx-kernel-source - NVIDIA binary kernel module
source${nvidia:LegacyDesc}
xserver-xorg-video-nvidia-legacy-304xx - NVIDIA binary Xorg
driver${nvidia:LegacyDesc}
Closes: 755462 755467
Changes:
nvidia-graphics-drivers-legacy-304xx (304.123-2) unstable; urgency=high
.
* Fix FTBFS when building kernel module. (Closes: #755462, #755467)
* Urgency=high because nvidia is currently completely broken in testing due
to xserver 1.16 migration and ABI bump.
Checksums-Sha1:
Bug#751255: TreeView X abandonned upstream … (was: Re: [Debian-med-packaging] Processed: severity of 751255 is serious).
Le Tue, Jul 22, 2014 at 12:57:05AM +, Debian Bug Tracking System a écrit : Processing commands for cont...@bugs.debian.org: # blocks the on-going wxwidgets3.0 transition severity 751255 serious Bug #751255 [treeviewx] treeviewx: Please update to use wxwidgets3.0 Severity set to 'serious' from 'important' thanks Stopping processing here. Thanks Olly, in the meantime, I contacted upstream who informed me that he does not have time anymore for working on TreeView X, and we started to discuss on the Debian Med mailing list what would be the best solution. Is it enough for you to have it out of Testing, or is it needed to remove it from Sid to ease your work ? For us, I think that the next step is to call for help on general purpose mailign lists relevant to TreeView X, and to contact the Fedora and Gentoo maintainers of the treeviewx packages there to see if they have found a solution on their side. Thanks again, and have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751767: marked as done (libBLT changes SONAME without changing package name)
Your message dated Tue, 22 Jul 2014 08:27:09 +0400 with message-id caoq2pxgc6pvk53j5nausd77kqohmgupn8yk+p8wz5afal66...@mail.gmail.com and subject line Reverse dependencies have been updated has caused the Debian Bug report #751767, regarding libBLT changes SONAME without changing package name 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.) -- 751767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: blt Version: 2.4z-9 Severity: important Dear Maintainer, after upgrading blt to version 2.4z-9 the package python-matplotlib becomes unusable. My program t.py contains one single line: import matplotlib.pylab as plt Running the program gives the following traceback: File t.py, line 1, in module import matplotlib.pylab as plt File /usr/lib/pymodules/python2.7/matplotlib/pylab.py, line 269, in module from matplotlib.pyplot import * File /usr/lib/pymodules/python2.7/matplotlib/pyplot.py, line 98, in module _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup() File /usr/lib/pymodules/python2.7/matplotlib/backends/__init__.py, line 28, in pylab_setup globals(),locals(),[backend_name],0) File /usr/lib/pymodules/python2.7/matplotlib/backends/backend_tkagg.py, line 8, in module import Tkinter as Tk, FileDialog File /usr/lib/python2.7/lib-tk/Tkinter.py, line 42, in module raise ImportError, str(msg) + ', please install the python-tk package' ImportError: libBLT.2.4.so.8.5: cannot open shared object file: No such file or directory, please install the python-tk package Note 1: the package python-tk is already installed. Note 2: currently, there is the file /usr/lib/libBLT.2.4.so.8.6 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (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 Versions of packages blt depends on: ii libc6 2.19-1 ii libtcl8.6 8.6.1-6 ii libtk8.6 8.6.1-5 ii libx11-6 2:1.6.2-2 blt recommends no packages. Versions of packages blt suggests: pn blt-demo none -- no debconf information ---End Message--- ---BeginMessage--- Hi! As for now all the reverse dependencies of blt have been updated to use Tcl/Tk 8.6 and BLT 2.5, so I'm closing the bug. Cheers! -- Sergei Golovan---End Message---
Bug#751255: TreeView X abandonned upstream … (was: Re: [Debian-med-packaging] Processed: severity of 751255 is serious).
On Tue, Jul 22, 2014 at 12:58:45PM +0900, Charles Plessy wrote: in the meantime, I contacted upstream who informed me that he does not have time anymore for working on TreeView X, and we started to discuss on the Debian Med mailing list what would be the best solution. Is it enough for you to have it out of Testing, or is it needed to remove it from Sid to ease your work ? My focus is definitely on the jessie release, so testing is what really matters. It doesn't make sense to keep wxwidgets2.8 around in unstable indefinitely, but there isn't a firm deadline for that removal. So if it's useful to keep a package in unstable and depending on wxwidgets2.8 while its future is resolved, that's certainly fine with me. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
