Bug#701380: boinc: ftbfs with eglibc-2.17
Control: fixed -1 7.0.65+dfsg-1 Marked as fixed in the current version in sid. Regards, GUO Yixuan 於 2013年05月07日 23:48, Gianfranco Costamagna 提到: This bug have been fixed between 7.0.36 and 7.0.38. You can see both changelogs (on ubuntu raring, not the same configuration but the same changelog) https://launchpadlibrarian.net/121599012/buildlog_ubuntu-raring-amd64.boinc_7.0.36%2Bdfsg-3_FAILEDTOBUILD.txt.gz https://launchpadlibrarian.net/121666774/buildlog_ubuntu-raring-amd64.boinc_7.0.36%2Bdfsg-4~raring1_BUILDING.txt.gz -- 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#701380: boinc: ftbfs with eglibc-2.17
Processing control commands: fixed -1 7.0.65+dfsg-1 Bug #701380 [src:boinc] boinc: ftbfs with eglibc-2.17 Marked as fixed in versions boinc/7.0.65+dfsg-1. -- 701380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701380 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#707375: boinc-app-seti: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory
Control: reassign src:boinc 7.0.65+dfsg-1 Control: affects -1 boinc-app-seti Hi, 於 2013年05月09日 15:16, Lucas Nussbaum 提到: Source: boinc-app-seti Version: 6.97~svn1409-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. ... In file included from /usr/include/boinc/lib/str_replace.h:24:0, from main.cpp:73: /usr/include/boinc/config.h:584:38: fatal error: project_specific_defines.h: No such file or directory compilation terminated. make[3]: *** [seti_boinc-main.o] Error 1 This is a known bug of boinc (libboinc-app-dev), which is fixed in the next upload (7.0.65+dfsg-2). Cheers, GUO Yixuan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#707375: boinc-app-seti: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory
Processing control commands: reassign src:boinc 7.0.65+dfsg-1 Unknown command or malformed arguments to command. affects -1 boinc-app-seti Bug #707375 [src:boinc-app-seti] boinc-app-seti: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory Added indication that 707375 affects boinc-app-seti -- 707375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign #688779 to ltt-control
Processing commands for cont...@bugs.debian.org:
reassign 688779 ltt-control
Bug #688779 {Done: Jon Bernard jbern...@debian.org} [liburcu1] liburcu1:
shlibs too weak
Bug reassigned from package 'liburcu1' to 'ltt-control'.
No longer marked as found in versions ltt-control/2.1.0~rc4-1.
No longer marked as fixed in versions ltt-control/2.1.0~rc4-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
688779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Sunday 12 May 08:03:04 UTC 2013 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: a href=http://packages.qa.debian.org/drslib;drslib/a tags 717513 + pending Failed to alter tags of Bug 717513: Unable to read any bugs successfully. # Source package in NEW: a href=http://packages.qa.debian.org/vdr;vdr/a tags 707413 + pending Bug #707413 [src:vdr] vdr: FTBFS: cc: fatal error: no input files Added tag(s) pending. # Source package in NEW: node-log4js tags 707883 + pending Bug #707883 [wnpp] ITP: node-log4js -- Conversion of the log4js framework to work with Node.js. Added tag(s) pending. # Source package in NEW: unorm.js tags 707887 + pending Bug #707887 [wnpp] ITP: unorm.js -- Common JS Unicode Normalizer Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 707413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707413 707883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707883 707887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707887 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: restore found/fixed
Processing commands for cont...@bugs.debian.org:
found 688779 ltt-control/2.1.0~rc4-1
Bug #688779 {Done: Jon Bernard jbern...@debian.org} [ltt-control] liburcu1:
shlibs too weak
Marked as found in versions ltt-control/2.1.0~rc4-1 and reopened.
fixed 688779 ltt-control/2.1.0~rc4-2
Bug #688779 [ltt-control] liburcu1: shlibs too weak
Marked as fixed in versions ltt-control/2.1.0~rc4-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
688779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign bugs
Processing commands for cont...@bugs.debian.org: reassign 707375 src:boinc 7.0.65+dfsg-1 Bug #707375 [src:boinc-app-seti] boinc-app-seti: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory Bug reassigned from package 'src:boinc-app-seti' to 'src:boinc'. No longer marked as found in versions boinc-app-seti/6.97~svn1409-1. Ignoring request to alter fixed versions of bug #707375 to the same values previously set Bug #707375 [src:boinc] boinc-app-seti: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory Marked as found in versions boinc/7.0.65+dfsg-1. reassign 707369 src:boinc 7.0.65+dfsg-1 Bug #707369 [src:boinc-app-milkyway] boinc-app-milkyway: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory Bug reassigned from package 'src:boinc-app-milkyway' to 'src:boinc'. No longer marked as found in versions boinc-app-milkyway/0.18d-1.1. Ignoring request to alter fixed versions of bug #707369 to the same values previously set Bug #707369 [src:boinc] boinc-app-milkyway: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory Marked as found in versions boinc/7.0.65+dfsg-1. affects 707369 boinc-app-milkyway Bug #707369 [src:boinc] boinc-app-milkyway: FTBFS: config.h:584:38: fatal error: project_specific_defines.h: No such file or directory Added indication that 707369 affects boinc-app-milkyway thanks Stopping processing here. Please contact me if you need assistance. -- 707369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707369 707375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707375 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#707922: src:augeas: FTBFS on all architectures (test failure)
Package: src:augeas Version: 1.0.0-1 Severity: serious The last augeas upload failed to build on all architectures due to a test failure: FAIL: test-run 1 of 182 tests failed Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: grumble, close again
Processing commands for cont...@bugs.debian.org: close 688779 2.1.0~rc4-2 Bug #688779 [ltt-control] liburcu1: shlibs too weak There is no source info for the package 'ltt-control' at version '2.1.0~rc4-2' with architecture '' Unable to make a source version for version '2.1.0~rc4-2' Marked as fixed in versions 2.1.0~rc4-2. Bug #688779 [ltt-control] liburcu1: shlibs too weak Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 688779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688779 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#707928: update-notifier: fails to install: touch: cannot touch '/var/lib/update-notifier/dpkg-run-stamp': No such file or directory
Package: update-notifier Version: 0.99.3debian11+perrm1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package update-notifier. (Reading database ... 16736 files and directories currently installed.) Unpacking update-notifier (from .../update-notifier_0.99.3debian11+perrm1_all.deb) ... Setting up update-notifier (0.99.3debian11+perrm1) ... touch: cannot touch '/var/lib/update-notifier/dpkg-run-stamp': No such file or directory dpkg: error processing update-notifier (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: update-notifier cheers, Andreas update-notifier_0.99.3debian11+perrm1.log.gz Description: GNU Zip compressed data
Bug#707353: marked as done (gnugk: FTBFS: job.cxx:88:2: error: 'PThreadIdentifer' does not name a type)
Your message dated Sun, 12 May 2013 09:03:09 + with message-id e1ubsbr-0005jv...@franck.debian.org and subject line Bug#707353: fixed in gnugk 2:3.2-2-2 has caused the Debian Bug report #707353, regarding gnugk: FTBFS: job.cxx:88:2: error: 'PThreadIdentifer' does not name a type 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.) -- 707353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gnugk Version: 2:3.0.2-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»' [CC] singleton.cxx [CC] job.cxx job.cxx:88:2: error: 'PThreadIdentifer' does not name a type job.cxx: In constructor 'Worker::Worker(Agent*, long int)': job.cxx:150:65: error: class 'Worker' does not have any field named 'm_id' job.cxx: In destructor 'virtual Worker::~Worker()': job.cxx:161:3: error: 'm_id' was not declared in this scope job.cxx:165:2: error: 'm_id' was not declared in this scope job.cxx: In member function 'virtual void Worker::Main()': job.cxx:170:2: error: 'm_id' was not declared in this scope job.cxx: In member function 'void Worker::Destroy()': job.cxx:246:2: error: 'm_id' was not declared in this scope make[3]: *** [obj_linux_x86_64/job.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/gnugk_3.0.2-3_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: gnugk Source-Version: 2:3.2-2-2 We believe that the bug you reported is fixed in the latest version of gnugk, 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 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Purcell m...@debian.org (supplier of updated gnugk 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 May 2013 18:17:36 +1000 Source: gnugk Binary: gnugk Architecture: source i386 Version: 2:3.2-2-2 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org Changed-By: Mark Purcell m...@debian.org Description: gnugk - OpenH323 Gatekeeper - The GNU Gatekeeper Closes: 707353 Changes: gnugk (2:3.2-2-2) unstable; urgency=low . * Upload to unstable - Fixes FTBFS: job.cxx:88:2: error: 'PThreadIdentifer' (Closes: #707353) Checksums-Sha1: b6354608c83f70e192a9281e01d8ea3701bef4a6 1548 gnugk_3.2-2-2.dsc 61590e2be7c113c1784a03396c29c3d273a2818b 11341 gnugk_3.2-2-2.debian.tar.gz 4869bc04964cf701593b246b972fc44cf2a5fc53 1344964 gnugk_3.2-2-2_i386.deb Checksums-Sha256: 6e7cf4a8608abf975ff1d95b6471a6be1ee3c387c098067dc715ad409c89b5f3 1548 gnugk_3.2-2-2.dsc bc1e6182275be97f4126dd0b3732aed549b8efc88d6efc3878da1a17cb77e6c2 11341 gnugk_3.2-2-2.debian.tar.gz c613ecaa3c40b456c348cfb71495eb9c6d77f36dcb0251e0d2e3f1b3bdad0188 1344964 gnugk_3.2-2-2_i386.deb Files: 6d4d91548e60639d162ee22f2265e383 1548 comm optional gnugk_3.2-2-2.dsc 4957ffcaea05c1cdc295a0d00ebabba1 11341 comm optional gnugk_3.2-2-2.debian.tar.gz cb8c25afda989030c264ce73e716959f 1344964 comm optional gnugk_3.2-2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGPUYcACgkQoCzanz0IthKQCgCfdmkro00Kdp7v2R4DLoJ6gKRa VGEAn1UZGDAgiPA0uShbznFQO5gtIm3k =NjuN -END PGP SIGNATUREEnd Message---
Bug#707463: [Pkg-xen-devel] Bug#707463: Bug#707463: xcp-storage-managers: FTBFS: xslib_wrap.c:125:20: fatal error: Python.h: No such file or directory
Hi Thomas, Would you please review and push this patch for me? Mike On Sat, May 11, 2013 at 2:15 PM, Mike McClurg mike.mccl...@gmail.comwrote: cc -O2 -I/usr/include/python2.6 -I/usr/include -fPIC -c -o xslib_wrap.o xslib_wrap.c Looks like the Makefile is specifying Python 2.6 instead of Python 2.7. I should have this fixed soon. Mike ___ Pkg-xen-devel mailing list pkg-xen-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel 0001-snapwatchd-includes-Python-2.7-headers-Closes-707463.patch Description: Binary data
Bug#707938: gup: fails to install, purge, and install again: gup.postinst: 11: cd: can't cd to /var/lib/gup/
Package: gup Version: 0.5.14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install, remove+purge, and install again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. This is often a problem with the home directory of a system user: the user is not deleted during purge (which is fine), but the home directory is removed. Since the user already exists on the next installation, adduser won't recreate the home. From the attached log (scroll to the bottom...): Selecting previously unselected package gup. (Reading database ... 7362 files and directories currently installed.) Unpacking gup (from .../archives/gup_0.5.14_amd64.deb) ... Setting up gup (0.5.14) ... /var/lib/dpkg/info/gup.postinst: 11: cd: can't cd to /var/lib/gup/ dpkg: error processing gup (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: gup cheers, Andreas gup_0.5.14.log.gz Description: GNU Zip compressed data
Bug#707940: code-aster-engine: fails to install, purge, and install again: ln: failed to create symbolic link '/usr/lib/codeaster/STABLE/config.txt': No such file or directory
Package: code-aster-engine Version: 11.3.0-2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install, remove+purge, and install again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. This is often a problem with the home directory of a system user: the user is not deleted during purge (which is fine), but the home directory is removed. Since the user already exists on the next installation, adduser won't recreate the home. From the attached log (scroll to the bottom...): Selecting previously unselected package code-aster-engine. (Reading database ... 7875 files and directories currently installed.) Unpacking code-aster-engine (from .../code-aster-engine_11.3.0-2-2+b1_amd64.deb) ... Setting up code-aster-engine (11.3.0-2-2+b1) ... + CODEASTER_VERSION=STA11.3 + pyversions -d + perl -pi -e s|python||g + dc_pyvers=2.7 + ln -sf /usr/lib/codeaster/STABLE/config-py2.7.txt /usr/lib/codeaster/STABLE/config.txt ln: failed to create symbolic link '/usr/lib/codeaster/STABLE/config.txt': No such file or directory dpkg: error processing code-aster-engine (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: code-aster-engine cheers, Andreas code-aster-engine_11.3.0-2-2+b1.log.gz Description: GNU Zip compressed data
Bug#702812: marked as done (init script stop fails because of missing pidfile)
Your message dated Sun, 12 May 2013 09:48:05 + with message-id e1ubssv-0003yy...@franck.debian.org and subject line Bug#702812: fixed in yate 4.3.0-1~dfsg-2 has caused the Debian Bug report #702812, regarding init script stop fails because of missing pidfile 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.) -- 702812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yate Version: 4.3.0-1~dfsg-1 Severity: serious yate's init script stop or restart doesn't work because the pidfile can't be created if yate runs as unprivileged user. Default is to run as user yate. A possible fix may be to create a subdirectory inside /var/run that is owned by the yate user. --- /etc/init.d/yate.orig 2013-03-11 19:49:08.204053159 +0100 +++ /etc/init.d/yate2013-03-11 19:49:55.99605 +0100 @@ -19,7 +19,7 @@ DAEMON=/usr/bin/yate NAME=yate DESC=yate -PIDFILE=/var/run/$NAME.pid +PIDFILE=/var/run/yate/$NAME.pid test -x $DAEMON || exit 0 @@ -41,6 +41,8 @@ #so yate won't load the client modules unset DISPLAY + [ -e /var/run/yate ] || \ + install -d -o $YATE_USER -g $YATE_GROUP /var/run/yate start-stop-daemon --start --quiet --oknodo --pidfile $PIDFILE \ --chuid $YATE_USER --group $YATE_GROUP \ --exec $DAEMON -- -p $PIDFILE $DAEMON_OPTS ---End Message--- ---BeginMessage--- Source: yate Source-Version: 4.3.0-1~dfsg-2 We believe that the bug you reported is fixed in the latest version of yate, 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 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Purcell m...@debian.org (supplier of updated yate 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 May 2013 19:15:44 +1000 Source: yate Binary: yate libyate4.3.0 yate-core yate-dev yate-doc yate-scripts yate-pgsql yate-qt4 yate-alsa yate-mysql yate-dahdi yate-sctp Architecture: source i386 all Version: 4.3.0-1~dfsg-2 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org Changed-By: Mark Purcell m...@debian.org Description: libyate4.3.0 - Shared library for YATE yate - Yet Another Telephony Engine (YATE) yate-alsa - ALSA module for YATE yate-core - YATE core modules yate-dahdi - Dahdi support for YATE yate-dev - Development files for YATE yate-doc - Documentation for YATE yate-mysql - MySQL support module for yate yate-pgsql - PostgreSQL module for yate yate-qt4 - YATE-based universal telephony client yate-scripts - PHP scripts for YATE yate-sctp - SCTP support for YATE Closes: 702812 Changes: yate (4.3.0-1~dfsg-2) unstable; urgency=low . [ Jeroen Dekkers ] * Put PID file in /var/run/yate instead of /var/run (Closes: #702812) * Put log file in /var/log/yate instead of /var/log * Call dh_install with --fail-missing * Add missing modules and config files Checksums-Sha1: 06a06b19aaa9ac560df181becd836749bcd8d71e 2213 yate_4.3.0-1~dfsg-2.dsc c8de27d118c94c44c215ec9a3b43decf23e41f4b 12532 yate_4.3.0-1~dfsg-2.debian.tar.gz 0e19b6b8b84841d40186ea7f4c36ef440fee04c4 23408 yate_4.3.0-1~dfsg-2_i386.deb 3e60afd9a80bdd806a9542080a38e99e18630719 1156060 libyate4.3.0_4.3.0-1~dfsg-2_i386.deb 581f54df723f9bae6630ce8d77f4a4c65a4a452f 2008500 yate-core_4.3.0-1~dfsg-2_i386.deb 3998effd6d0f29e3df6a9d38dcb135241e9b0c33 124346 yate-dev_4.3.0-1~dfsg-2_i386.deb 93478d342b35138736eee87f4d00201273ad5e02 376102 yate-doc_4.3.0-1~dfsg-2_all.deb fc5b4db96b203300fd54b232b4fedb1e7d525af1 42802 yate-scripts_4.3.0-1~dfsg-2_i386.deb 90adba7a9886ce7fa89cc4569645f4b02917c1a4 26956 yate-pgsql_4.3.0-1~dfsg-2_i386.deb 28441eafe28c694d91a7427718ca64260ab5b9fe 927918 yate-qt4_4.3.0-1~dfsg-2_i386.deb 96dc10261a270d297b6868ec666702066128961c 27644 yate-alsa_4.3.0-1~dfsg-2_i386.deb a51a9a3873ff4e82518cbb3ef619039de3239641 27974 yate-mysql_4.3.0-1~dfsg-2_i386.deb db57b4d95884b29fd9e737e58446e74b1df1c53f 49936 yate-dahdi_4.3.0-1~dfsg-2_i386.deb ae73935a86fe4893cd06d43eafc301debbf2f49a 25266
Bug#705644: marked as done (yate is unable to create a log / pid file)
Your message dated Sun, 12 May 2013 09:48:05 + with message-id e1ubssv-0003yy...@franck.debian.org and subject line Bug#702812: fixed in yate 4.3.0-1~dfsg-2 has caused the Debian Bug report #702812, regarding yate is unable to create a log / pid file 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.) -- 702812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yate Version: 4.3.0-1~dfsg-1 Hi, Bug #469729 has a patch which causes start-stop-daemon to set the user to be 'yate'. Unfortunately this means that Yate will never create its log files (by default /etc/log/yate) or pid file (/run/yate.pid) since it will not have permission to create files in those directories. Suggestions: - revert the patch - should those directories have a group called 'daemon', and then all daemons can have write access to that directory? - yate should be patched to create those files, then drop privileges and the patch removed Thanks, Anand -- “Don’t be sad because it’s over. Smile because it happened.” – Dr. Seuss ---End Message--- ---BeginMessage--- Source: yate Source-Version: 4.3.0-1~dfsg-2 We believe that the bug you reported is fixed in the latest version of yate, 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 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Purcell m...@debian.org (supplier of updated yate 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 May 2013 19:15:44 +1000 Source: yate Binary: yate libyate4.3.0 yate-core yate-dev yate-doc yate-scripts yate-pgsql yate-qt4 yate-alsa yate-mysql yate-dahdi yate-sctp Architecture: source i386 all Version: 4.3.0-1~dfsg-2 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org Changed-By: Mark Purcell m...@debian.org Description: libyate4.3.0 - Shared library for YATE yate - Yet Another Telephony Engine (YATE) yate-alsa - ALSA module for YATE yate-core - YATE core modules yate-dahdi - Dahdi support for YATE yate-dev - Development files for YATE yate-doc - Documentation for YATE yate-mysql - MySQL support module for yate yate-pgsql - PostgreSQL module for yate yate-qt4 - YATE-based universal telephony client yate-scripts - PHP scripts for YATE yate-sctp - SCTP support for YATE Closes: 702812 Changes: yate (4.3.0-1~dfsg-2) unstable; urgency=low . [ Jeroen Dekkers ] * Put PID file in /var/run/yate instead of /var/run (Closes: #702812) * Put log file in /var/log/yate instead of /var/log * Call dh_install with --fail-missing * Add missing modules and config files Checksums-Sha1: 06a06b19aaa9ac560df181becd836749bcd8d71e 2213 yate_4.3.0-1~dfsg-2.dsc c8de27d118c94c44c215ec9a3b43decf23e41f4b 12532 yate_4.3.0-1~dfsg-2.debian.tar.gz 0e19b6b8b84841d40186ea7f4c36ef440fee04c4 23408 yate_4.3.0-1~dfsg-2_i386.deb 3e60afd9a80bdd806a9542080a38e99e18630719 1156060 libyate4.3.0_4.3.0-1~dfsg-2_i386.deb 581f54df723f9bae6630ce8d77f4a4c65a4a452f 2008500 yate-core_4.3.0-1~dfsg-2_i386.deb 3998effd6d0f29e3df6a9d38dcb135241e9b0c33 124346 yate-dev_4.3.0-1~dfsg-2_i386.deb 93478d342b35138736eee87f4d00201273ad5e02 376102 yate-doc_4.3.0-1~dfsg-2_all.deb fc5b4db96b203300fd54b232b4fedb1e7d525af1 42802 yate-scripts_4.3.0-1~dfsg-2_i386.deb 90adba7a9886ce7fa89cc4569645f4b02917c1a4 26956 yate-pgsql_4.3.0-1~dfsg-2_i386.deb 28441eafe28c694d91a7427718ca64260ab5b9fe 927918 yate-qt4_4.3.0-1~dfsg-2_i386.deb 96dc10261a270d297b6868ec666702066128961c 27644 yate-alsa_4.3.0-1~dfsg-2_i386.deb a51a9a3873ff4e82518cbb3ef619039de3239641 27974 yate-mysql_4.3.0-1~dfsg-2_i386.deb db57b4d95884b29fd9e737e58446e74b1df1c53f 49936 yate-dahdi_4.3.0-1~dfsg-2_i386.deb ae73935a86fe4893cd06d43eafc301debbf2f49a 25266 yate-sctp_4.3.0-1~dfsg-2_i386.deb Checksums-Sha256: 5badbfd65f4d24447c20501a0816458ca5a219823c27a8be7b211648860a13ae 2213 yate_4.3.0-1~dfsg-2.dsc 96ee618d77a1a364be40a3b283f6e9c51061ee433dfccbe1b13873fcddaeefb0 12532 yate_4.3.0-1~dfsg-2.debian.tar.gz
Bug#702475: Bug#707879: apache2: mod_mpm_itk.so: undefined symbol: cap_set_proc
forcemerge 702475 707879 thanks Hi Ángel, On 12.05.2013 00:12, Ángel González wrote: mod_mpm_itk.so wasn't linked using -lcap ? Right. See #702475 as this bug is a duplicate of that. There is also a workaround noted. Having that said, fixing this is not a high priority as we are likely to split out the itk package soon, so that the issue can be addresses properly there. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Processed: found 707836 in 1:2.0.0-2, found 657146 in 8.0.5+dfsg-2, found 668724 in 0.0.20090925-7 ...
Processing commands for cont...@bugs.debian.org: found 707836 1:2.0.0-2 Bug #707836 [italc-client] italc-client: fails to install: italc-client.postinst: addgroup: not found Marked as found in versions italc/1:2.0.0-2. found 657146 8.0.5+dfsg-2 Bug #657146 [tango-common] tango-common: unowned files after purge (policy 6.8, 10.8) Marked as found in versions tango/8.0.5+dfsg-2. found 668724 0.0.20090925-7 Bug #668724 [prelink] prelink: unowned files after purge (policy 6.8, 10.8): /var/log/prelink.log Marked as found in versions prelink/0.0.20090925-7. affects 707301 + tdsodbc Bug #707301 [upgrade-reports] release-notes: odbcinst1debian2 : Breaks: tdsodbc ( 0.82-8) but 0.82-7 is to be installed Added indication that 707301 affects tdsodbc user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). usertags 707301 piuparts There were no usertags set. Usertags are now: piuparts. affects 645713 + open-cobol Bug #645713 [apt] many squeeze-wheezy upgrades fail with Could not perform immediate configuration Bug #701048 [apt] many squeeze-wheezy upgrades fail with Could not perform immediate configuration Added indication that 645713 affects open-cobol Added indication that 701048 affects open-cobol thanks Stopping processing here. Please contact me if you need assistance. -- 645713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645713 657146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657146 668724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668724 701048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701048 707301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707301 707836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707836 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: forcibly merging 702475 707879
Processing commands for cont...@bugs.debian.org: forcemerge 702475 707879 Bug #702475 [apache2] apache2: the itk MPM is underlinked: sys/capability.h symbols are not resolved Bug #707879 [apache2] apache2: mod_mpm_itk.so: undefined symbol: cap_set_proc Severity set to 'serious' from 'normal' Marked as found in versions apache2/2.4.2-2 and apache2/2.4.2-1. Added tag(s) experimental. Bug #702475 [apache2] apache2: the itk MPM is underlinked: sys/capability.h symbols are not resolved Marked as found in versions apache2/2.4.4-2. Merged 702475 707879 thanks Stopping processing here. Please contact me if you need assistance. -- 702475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702475 707879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707879 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#684489: marked as done (gksu-polkit: CVE-2011-0703)
Your message dated Sun, 12 May 2013 10:11:10 + with message-id e1ubtfg-00055n...@franck.debian.org and subject line Bug#702014: Removed package(s) from unstable has caused the Debian Bug report #684489, regarding gksu-polkit: CVE-2011-0703 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.) -- 684489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gksu-polkit Severity: grave Tags: security Justification: user security hole I just noticed that this never made it to the BTS: http://www.openwall.com/lists/oss-security/2011/03/15/8 It was assiged CVE-2011-0703 Cheers, Moritz ---End Message--- ---BeginMessage--- Version: 0.0.3-1+rm Dear submitter, as the package gksu-polkit 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 http://bugs.debian.org/702014 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...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#695807: marked as done (CVE-2012-5617: gksu-polkit privileged code execution with unprivileged credentials)
Your message dated Sun, 12 May 2013 10:11:10 + with message-id e1ubtfg-00055n...@franck.debian.org and subject line Bug#702014: Removed package(s) from unstable has caused the Debian Bug report #695807, regarding CVE-2012-5617: gksu-polkit privileged code execution with unprivileged credentials 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.) -- 695807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gksu-polkit Severity: grave Tags: security Hi, the following vulnerability was published for gksu-polkit. CVE-2012-5617[0,1]: privilege escalation due to improper authentication settings in policykit configuration file If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5617 http://security-tracker.debian.org/tracker/CVE-2012-5617 [1] http://www.openwall.com/lists/oss-security/2012/12/12/8 Please adjust the affected versions in the BTS as needed. Regards, Salvatore signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 0.0.3-1+rm Dear submitter, as the package gksu-polkit 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 http://bugs.debian.org/702014 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...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#707847: marked as done (hotwire: recommends python-gnomedesktop which is no longer built)
Your message dated Sun, 12 May 2013 10:13:23 + with message-id e1ubthp-0005qa...@franck.debian.org and subject line Bug#707863: Removed package(s) from unstable has caused the Debian Bug report #707847, regarding hotwire: recommends python-gnomedesktop which is no longer built 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.) -- 707847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: hotwire Version: 0.721-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs python-gnomedesktop Hi, Your package recommends python-gnomedesktop, which is gone. Please remove that recommendation from your package. Thanks, Emilio ---End Message--- ---BeginMessage--- Version: 0.721-2+rm Dear submitter, as the package hotwire 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 http://bugs.debian.org/707863 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...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#692078: marked as done (sea-defender: ships non-free files in main)
Your message dated Sun, 12 May 2013 10:16:14 + with message-id e1ubtka-0006vv...@franck.debian.org and subject line Bug#707798: Removed package(s) from unstable has caused the Debian Bug report #692078, regarding sea-defender: ships non-free files in main 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.) -- 692078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sea-defender Version: 0.9-2 Severity: serious Justification: Policy 2.2.1 Hi, i just browsed the package a little and discovered these files which make sea-defender more suited for non-free than for main. The author of sea-defender marked them clearly visible in his git repository. https://github.com/snoutmate/Sea-Defender data/fonts/kronika.svg data/model/OpenGL_logo_flat.svg snoutlib/perlin.cpp Kronika.svg was downloaded from apostrophiclab.pedroreina.net. The terms of use state clearly: http://apostrophiclab.pedroreina.net/info.html The fonts on this site are freeware and can be used as they are in any context without permission from Apostrophic Laboratories, except to produce material that is racist, criminal and/or illegal in nature. It is prohibited to modify any Apostrophic Laboratories font(s) for repackaging and/or re-release without an express written authorization by the designer(s) of the font(s) or Apostrophic Laboratories. Under no circumstance shall any Apostrophic Laboratories design or font design be sold or purchased. Email i...@apostrophiclab.com if you want more information. The Apostrophic Laboratories site and its contents are the property of Apostrophic Laboratories and the contents' creators. It is prohibited to use the graphic designs shown on this site or any of the site's elements without obtaining written authorization from the designer(s) and/or developer(s) of the content in question. Email i...@apostrophiclab.com if you want more information. The OpenGL_logo isn't free either. http://www.opengl.org/about/logos/ The copyright of the perlin noise cpp file is unclear. At least i can't find other information except (copyright Ken Perlin) Regards, Markus Koschany -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sea-defender depends on: ii libc6 2.13-35 ii libgcc1 1:4.7.1-7 ii libgl1-mesa-glx [libgl1] 8.0.4-2 ii libglfw2 2.7.2-1 ii libglu1-mesa [libglu1]8.0.4-2 ii libstdc++64.7.1-7 ii libx11-6 2:1.5.0-1 ii libxrandr22:1.3.2-2 sea-defender recommends no packages. sea-defender suggests no packages. -- no debconf information signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 0.9-2+rm Dear submitter, as the package sea-defender 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 http://bugs.debian.org/707798 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...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#707712: marked as done (importlib: FTBFS: pyversions: computed set of supported versions is empty)
Your message dated Sun, 12 May 2013 10:16:06 + with message-id e1ubtk2-0006sr...@franck.debian.org and subject line Bug#707799: Removed package(s) from unstable has caused the Debian Bug report #707712, regarding importlib: FTBFS: pyversions: computed set of supported versions is empty 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.) -- 707712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: importlib Version: 1.0.2-2 Severity: serious Tags: sid jessie User: debian-pyt...@lists.debian.org Usertags: python2.6-removal Justification: fails to build from source Now that 2.6 is no longer a supported version, importlib FTBFS: | fakeroot debian/rules clean | dh clean --with python2 |dh_testdir |dh_auto_clean | pyversions: computed set of supported versions is empty | dh_auto_clean: pyversions -r failed [4] | make: *** [clean] Error 4 -- Jakub Wilk ---End Message--- ---BeginMessage--- Version: 1.0.2-2+rm Dear submitter, as the package importlib 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 http://bugs.debian.org/707799 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...@debian.org. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)---End Message---
Bug#707355: fix pending
tag 707355 + pending thanks I have a local fix for this bug but I also need to do some conversions due to changes in the upstream support site, so haven't committed to VCS yet. (Also waiting for some build-deps to stabilise in sid before uploading.) --- main.c (revision 157) +++ main.c (working copy) @@ -148,7 +148,10 @@ remaining_args = NULL; num_args = 0; error = NULL; + // deprecated and useless for glib = 2.36 but needed before. +#ifndef GLIB_DEPRECATED_IN_2_36 g_type_init (); +#endif option_context = g_option_context_new (); g_option_context_add_main_entries (option_context, option_entries, GETTEXT_PACKAGE); -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpYnKzwbdsu4.pgp Description: PGP signature
Processed: fix pending
Processing commands for cont...@bugs.debian.org: tag 707355 + pending Bug #707355 [src:gpdftext] gpdftext: FTBFS: main.c:151:2: error: 'g_type_init' is deprecated (declared at /usr/include/glib-2.0/gobject/gtype.h:669) [-Werror=deprecated-declarations] Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 707355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707355 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#707408: marked as done (python-notify2: FTBFS: ImportError: No module named '_dbus_bindings')
Your message dated Sun, 12 May 2013 12:36:53 +0200 with message-id 20130512103653.ga1...@jwilk.net and subject line Re: Bug#707408: python-notify2: FTBFS: ImportError: No module named '_dbus_bindings' has caused the Debian Bug report #707408, regarding python-notify2: FTBFS: ImportError: No module named '_dbus_bindings' 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.) -- 707408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-notify2 Version: 0.3-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' python3.2 setup.py build running build running build_py creating build creating build/lib copying notify2.py - build/lib python3.3 setup.py build Traceback (most recent call last): File setup.py, line 2, in module import notify2 File /«PKGBUILDDIR»/notify2.py, line 38, in module import dbus File /usr/lib/python3/dist-packages/dbus/__init__.py, line 82, in module import dbus.types as types File /usr/lib/python3/dist-packages/dbus/types.py, line 6, in module from _dbus_bindings import ( ImportError: No module named '_dbus_bindings' make[1]: *** [build-python3.3] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/python-notify2_0.3-2_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--- * Lucas Nussbaum lu...@lucas-nussbaum.net, 2013-05-09, 10:25: python3.3 setup.py build Traceback (most recent call last): File setup.py, line 2, in module import notify2 File /«PKGBUILDDIR»/notify2.py, line 38, in module import dbus File /usr/lib/python3/dist-packages/dbus/__init__.py, line 82, in module import dbus.types as types File /usr/lib/python3/dist-packages/dbus/types.py, line 6, in module from _dbus_bindings import ( ImportError: No module named '_dbus_bindings' Now that dbus-python has been rebuilt against Python 3.3, the package builds correctly. Closing. -- Jakub Wilk---End Message---
Bug#707467: marked as done (python-distutils-extra: FTBFS: ImportError: /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0: undefined symbol: PyUnicode_AsUTF8)
Your message dated Sun, 12 May 2013 12:37:56 +0200 with message-id 20130512103756.ga1...@jwilk.net and subject line Re: Bug#707467: python-distutils-extra: FTBFS: ImportError: /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0: undefined symbol: PyUnicode_AsUTF8 has caused the Debian Bug report #707467, regarding python-distutils-extra: FTBFS: ImportError: /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0: undefined symbol: PyUnicode_AsUTF8 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.) -- 707467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-distutils-extra Version: 2.37-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' # run tests with all supported python 2 and 3 versions set -e; for python in `pyversions -s` `py3versions -s`; do \ echo -- Running tests with $python ; \ LC_ALL=C LANGUAGE= LANG=C PYTHONPATH=. $python test/auto.py -v; \ done -- Running tests with python2.7 test_apport_hook (__main__.T) Apport hooks ... ok test_binary_files (__main__.T) Binary files are ignored ... ok test_data (__main__.T) Auxiliary files in data/ ... ok test_dbus (__main__.T) D-BUS configuration and service files ... ok test_desktop (__main__.T) *.desktop.in files ... ok test_empty (__main__.T) empty source tree (just setup.py) ... ok test_etc (__main__.T) etc/* ... ok test_gsettings (__main__.T) GSettings schema files ... ok test_help_docbook (__main__.T) Docbook XML help ... ok test_help_mallard (__main__.T) Mallard XML help ... ok test_icons (__main__.T) data/icons/ ... ok test_manpages (__main__.T) manpages ... ok test_modules (__main__.T) Python modules ... ok test_packages (__main__.T) Python packages ... ok test_po (__main__.T) gettext *.po files ... ok test_policykit (__main__.T) *.policy.in PolicyKit files ... ok test_pot_auto (__main__.T) PO template creation with automatic POTFILES.in ... ok test_pot_auto_explicit (__main__.T) PO template creation with automatic POTFILES.in and explicit scripts ... ok test_pot_manual (__main__.T) PO template creation with manual POTFILES.in ... ok test_requires_provides (__main__.T) automatic requires/provides ... ok test_scripts (__main__.T) scripts ... ok test_sdist (__main__.T) default MANIFEST ... ok test_standard_files (__main__.T) Standard files (MANIFEST.in, COPYING, etc.) ... ok test_ui (__main__.T) GtkBuilder/Qt *.ui ... ok test_utf8_filenames (__main__.T) UTF-8 file names ... ok test_vcs (__main__.T) Ignores revision control files ... ok -- Ran 26 tests in 9.740s OK -- Running tests with python3.2 test_apport_hook (__main__.T) Apport hooks ... ok test_binary_files (__main__.T) Binary files are ignored ... ok test_data (__main__.T) Auxiliary files in data/ ... ok test_dbus (__main__.T) D-BUS configuration and service files ... ok test_desktop (__main__.T) *.desktop.in files ... ok test_empty (__main__.T) empty source tree (just setup.py) ... ok test_etc (__main__.T) etc/* ... ok test_gsettings (__main__.T) GSettings schema files ... ok test_help_docbook (__main__.T) Docbook XML help ... ok test_help_mallard (__main__.T) Mallard XML help ... ok test_icons (__main__.T) data/icons/ ... ok test_manpages (__main__.T) manpages ... ok test_modules (__main__.T) Python modules ... ok test_packages (__main__.T) Python packages ... ok test_po (__main__.T) gettext *.po files ... ok test_policykit (__main__.T) *.policy.in PolicyKit files ... ok test_pot_auto (__main__.T) PO template creation with automatic POTFILES.in ... ok test_pot_auto_explicit (__main__.T) PO template creation with automatic POTFILES.in and explicit scripts ... ok test_pot_manual (__main__.T) PO template creation with manual POTFILES.in ... ok test_requires_provides (__main__.T) automatic requires/provides ... FAIL test_scripts (__main__.T) scripts ... ok test_sdist (__main__.T) default MANIFEST ... ok test_standard_files (__main__.T) Standard files (MANIFEST.in, COPYING, etc.) ... ok test_ui (__main__.T) GtkBuilder/Qt *.ui ... ok test_utf8_filenames (__main__.T) UTF-8 file names ... ok test_vcs (__main__.T) Ignores
Bug#707653: grub2-common: After Grub 2.00-14 upgrade, system failed to boot (rescue, old grub 1.99 still in mbr)
Hi all, This (or maybe another?) bug also affects RAID-based systems. I have my system installed on RAID 1 (fakeraid). After upgrading 1.99-27.1 - 2.00-14 it was impossible to boot system. Workaround for those who met this: boot from livecd, chroot, downgrade grub to 1.99-27.1 (from Wheezy repo), manually grub-install update-grub2. Details for Debian developers maintainer (please let me know if u need any futher information or help to locate and fix this issue): Attempt to install grub 2.00-14 root@dagon:/var/lib/schroot/mount# grub-install /dev/mapper/isw_hbghdbjgf_SYSTEM Path `/boot/grub' is not readable by GRUB on boot. Installation is impossible. Aborting. --- Mounted FSes root@dagon:/var/lib/schroot/mount# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=196894,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1247016k,mode=755) /dev/dm-3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2494020k) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) /dev/mapper/isw_hbghdbjgf_SYSTEM1 on /boot type ext2 (rw,relatime,errors=continue) /dev/mapper/isw_hbghdbjgf_SYSTEM6 on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/isw_hbghdbjgf_SYSTEM6 on /var/lib/mysql type ext4 (rw,relatime,data=ordered) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) --- Attempt to update-grub2 root@dagon:/var/lib/schroot/mount# update-grub2 Generating grub.cfg ... /usr/sbin/grub-probe: error: unknown filesystem. Found background image: .background_cache.png Found linux image: /boot/vmlinuz-3.8-1-686-pae Found initrd image: /boot/initrd.img-3.8-1-686-pae /usr/sbin/grub-probe: error: unknown filesystem. /usr/sbin/grub-probe: error: unknown filesystem. /usr/sbin/grub-probe: error: unknown filesystem. Found linux image: /boot/vmlinuz-3.2.0-4-686-pae Found initrd image: /boot/initrd.img-3.2.0-4-686-pae /usr/sbin/grub-probe: error: unknown filesystem. /usr/sbin/grub-probe: error: unknown filesystem. /usr/sbin/grub-probe: error: unknown filesystem. Found memtest86+ image: /memtest86+.bin Found memtest86+ multiboot image: /memtest86+_multiboot.bin File descriptor 8 (pipe:[34]) leaked on lvs invocation. Parent PID 29937: /bin/sh No volume groups found grub-probe: error: unknown filesystem. rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy Found Debian GNU/Linux (jessie/sid) on /dev/mapper/isw_hbghdbjgf_SYSTEM5 done --- Grub2 versions ii grub-common 2.00-14i386 GRand Unified Bootloader (common files) ii grub-pc 2.00-14i386 GRand Unified Bootloader, version 2 (PC/BIOS version) ii grub-pc-bin 2.00-14i386 GRand Unified Bootloader, version 2 (PC/BIOS binaries) ii grub2 2.00-14i386 GRand Unified Bootloader, version 2 (dummy package) ii grub2-common 2.00-14i386 GRand Unified Bootloader (common files for version 2) -- WBR, Gleb Golubitsky Gnolltech signature.asc Description: This is a digitally signed message part.
Bug#707960: rpc.gssd segfaults when mounting a nfsv4 volume
Package: nfs-common Version: 1:1.2.8-1 Severity: grave (elided):/ /media/nfs nfs4noauto,soft,intr,sec=krb5p 0 0 [2262594.734234] rpc.gssd[2729]: segfault at 1 ip f74714ba sp ff830170 error 4 in libgssglue.so.1.0.0[f746e000+8000] Reverting nfs-common to 1:1.2.6-3 fixes the issue. BTW: /usr/share/bug/nfs-common/script: 5: /usr/share/bug/nfs-common/script: rpcinfo: not found -- Package-specific info: -- rpcinfo -- -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-41 ii libc6 2.17-1 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.5-1.1 ii libdevmapper1.02.1 2:1.02.77-1 ii libevent-2.0-5 2.0.19-stable-3 ii libgssglue1 0.4-2 ii libk5crypto31.10.1+dfsg-5 ii libkeyutils11.5.5-7 ii libkrb5-3 1.10.1+dfsg-5 ii libmount1 2.20.1-5.3 ii libnfsidmap20.25-4 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-24 ii lsb-base4.1+Debian9 ii rpcbind 0.2.0-8 ii ucf 3.0025+nmu3 Versions of packages nfs-common recommends: ii python 2.7.3-4 Versions of packages nfs-common suggests: pn open-iscsi none pn watchdognone -- no debconf information -- ciao, Marco signature.asc Description: Digital signature
Bug#701383: marked as done (mspdebug: ftbfs with eglibc-2.17)
Your message dated Sun, 12 May 2013 11:18:19 +
with message-id e1ubuif-0003xn...@franck.debian.org
and subject line Bug#701383: fixed in mspdebug 0.21-2
has caused the Debian Bug report #701383,
regarding mspdebug: ftbfs with eglibc-2.17
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.)
--
701383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:mspdebug
Version: 0.19-1
Severity: important
Tags: sid jessie
User: debian-gl...@lists.debian.org
Usertags: ftbfs-glibc-2.17
The package fails to build in a test rebuild on at least amd64 with
eglibc-2.17, but succeeds to build with eglibc-2.13. The
severity of this report may be raised before the jessie release.
The test rebuild was done together with GCC-4.8, so some issues
might be caused by the updated GCC as well.
util/sport.c:159:10: error: variable 'tv' has initializer but incomplete type
The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/mspdebug_0.19-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.
To install eglibc from experimental,
apt-get -t experimental install libc6-dev
To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev
[...]
debian/rules build-arch
dh build-arch
dh_testdir -a
dh_auto_configure -a
dh_auto_build -a
make[1]: Entering directory `/«PKGBUILDDIR»'
cc -DUSE_READLINE -O1 -Wall -Wno-char-subscripts -ggdb -I. -Isimio -Iformats
-Idrivers -Iutil -Iui -DLIB_DIR=\/usr/local/lib/\ -o util/btree.o -c
util/btree.c
cc -DUSE_READLINE -O1 -Wall -Wno-char-subscripts -ggdb -I. -Isimio -Iformats
-Idrivers -Iutil -Iui -DLIB_DIR=\/usr/local/lib/\ -o util/expr.o -c
util/expr.c
cc -DUSE_READLINE -O1 -Wall -Wno-char-subscripts -ggdb -I. -Isimio -Iformats
-Idrivers -Iutil -Iui -DLIB_DIR=\/usr/local/lib/\ -o util/list.o -c
util/list.c
cc -DUSE_READLINE -O1 -Wall -Wno-char-subscripts -ggdb -I. -Isimio -Iformats
-Idrivers -Iutil -Iui -DLIB_DIR=\/usr/local/lib/\ -o util/sockets.o -c
util/sockets.c
cc -DUSE_READLINE -O1 -Wall -Wno-char-subscripts -ggdb -I. -Isimio -Iformats
-Idrivers -Iutil -Iui -DLIB_DIR=\/usr/local/lib/\ -o util/sport.o -c
util/sport.c
util/sport.c: In function 'sport_read':
util/sport.c:159:10: error: variable 'tv' has initializer but incomplete type
struct timeval tv = {
^
util/sport.c:160:4: error: unknown field 'tv_sec' specified in initializer
.tv_sec = 5,
^
util/sport.c:160:4: warning: excess elements in struct initializer [enabled by
default]
util/sport.c:160:4: warning: (near initialization for 'tv') [enabled by default]
util/sport.c:161:4: error: unknown field 'tv_usec' specified in initializer
.tv_usec = 0
^
util/sport.c:162:3: warning: excess elements in struct initializer [enabled by
default]
};
^
util/sport.c:162:3: warning: (near initialization for 'tv') [enabled by default]
util/sport.c:159:18: error: storage size of 'tv' isn't known
struct timeval tv = {
^
util/sport.c:164:3: error: unknown type name 'fd_set'
fd_set set;
^
util/sport.c:166:3: warning: implicit declaration of function 'FD_ZERO'
[-Wimplicit-function-declaration]
FD_ZERO(set);
^
util/sport.c:167:3: warning: implicit declaration of function 'FD_SET'
[-Wimplicit-function-declaration]
FD_SET(s, set);
^
util/sport.c:169:3: warning: implicit declaration of function 'select'
[-Wimplicit-function-declaration]
r = select(s + 1, set, NULL, NULL, tv);
^
util/sport.c:159:18: warning: unused variable 'tv' [-Wunused-variable]
struct timeval tv = {
^
make[1]: *** [util/sport.o] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
---End Message---
---BeginMessage---
Source: mspdebug
Source-Version: 0.21-2
We believe that the bug you reported is fixed in the latest version of
mspdebug, 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 701...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luca Bruno
Bug#707961: glabels: depends on gnome-desktop-data which is going away
Package: glabels Version: 3.0.0-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnome-desktop Dear maintainer, Your last upload of glabels added a dependency on gnome-desktop-data, which I am about to remove. I am not even sure why you have added that dependency (the changelog mentions some license stuff, but gnome-desktop-data only ships a bunch of pixmaps and some translations). Perhaps you can avoid it entirely or depend on gnome-desktop3-data instead. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707962: julia: FTBFS (test failed: :((file_size=length(data))))
Source: julia Version: 0.1.2+dfsg-2 Severity: serious Justification: fails to build from source See the build logs at https://buildd.debian.org/status/fetch.php?pkg=juliaarch=amd64ver=0.1.2%2Bdfsg-2%2Bb1stamp=1368356377 and https://buildd.debian.org/status/fetch.php?pkg=juliaarch=i386ver=0.1.2%2Bdfsg-2%2Bb1stamp=1368354721 LD_LIBRARY_PATH=/build/buildd-julia_0.1.2+dfsg-2+b1-i386-LZt5lx/julia-0.1.2+dfsg/usr/lib /build/buildd-julia_0.1.2+dfsg-2+b1-i386-LZt5lx/julia-0.1.2+dfsg/julia ./runtests.jl extra [...] ERROR: test failed: :((file_size=length(data))) in default_handler at test.jl:18 in do_test at test.jl:27 in anonymous at no file:118 in include_from_node1 at loading.jl:76 in runtests at /build/buildd-julia_0.1.2+dfsg-2+b1-i386-LZt5lx/julia-0.1.2+dfsg/test/runtests.jl:6 in include_from_node1 at loading.jl:76 in runtests at /build/buildd-julia_0.1.2+dfsg-2+b1-i386-LZt5lx/julia-0.1.2+dfsg/test/runtests.jl:6 in anonymous at no file:22 in include_from_node1 at loading.jl:76 in process_options at client.jl:255 in _start at client.jl:318 at /build/buildd-julia_0.1.2+dfsg-2+b1-i386-LZt5lx/julia-0.1.2+dfsg/test/gzip.jl:141 make[2]: *** [extra] Error 1 Cheers, Julien signature.asc Description: Digital signature
Bug#707435: marked as done (w-scan: FTBFS: scan.c:1819:44: error: 'DTV_DVBT2_PLP_ID' undeclared (first use in this function))
Your message dated Sun, 12 May 2013 12:32:55 + with message-id e1ubvsr-h8...@franck.debian.org and subject line Bug#707435: fixed in w-scan 20130331-1 has caused the Debian Bug report #707435, regarding w-scan: FTBFS: scan.c:1819:44: error: 'DTV_DVBT2_PLP_ID' 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.) -- 707435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: w-scan Version: 20120605-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I.-Wall -Wextra -Wno-comment -Wswitch-default -Wno-unused-parameter -g -O2 -c scan.c scan.c: In function 'set_frontend': scan.c:1819:44: error: 'DTV_DVBT2_PLP_ID' undeclared (first use in this function) scan.c:1819:44: note: each undeclared identifier is reported only once for each function it appears in make[2]: *** [scan.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/w-scan_20120605-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: w-scan Source-Version: 20130331-1 We believe that the bug you reported is fixed in the latest version of w-scan, 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 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Grimm et...@debian.org (supplier of updated w-scan 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 May 2013 08:46:38 +0200 Source: w-scan Binary: w-scan Architecture: source amd64 Version: 20130331-1 Distribution: unstable Urgency: low Maintainer: Debian VDR Team pkg-vdr-dvb-de...@lists.alioth.debian.org Changed-By: Tobias Grimm et...@debian.org Description: w-scan - Channel scanning tool for DVB and ATSC channels Closes: 707435 Changes: w-scan (20130331-1) unstable; urgency=low . * New upstream release (Closes: #707435) . w-scan (2012-1) unstable; urgency=low . * New upstream release * Standards-Version: 3.9.4 * Used debhelper 9 Checksums-Sha1: 22f919aef97203183006e50f69b8929ae379bba5 1295 w-scan_20130331-1.dsc 0bfb7ca40c4c423520bf756df31c607d6ca37d80 215996 w-scan_20130331.orig.tar.bz2 b358e1cb813ca583c1145d8db8b472afad97374c 3433 w-scan_20130331-1.debian.tar.bz2 2a313acc95ed05142e2814fc0735b126a9470c39 116622 w-scan_20130331-1_amd64.deb Checksums-Sha256: 2f39b59d9a2768c55f54d463989f645aa7d3765fcaca0144a377f67f2ca5486a 1295 w-scan_20130331-1.dsc 422414e9f13bfb574aace014c6f4dd2175f7eeb08ba9d5e3187cf02fae1522bf 215996 w-scan_20130331.orig.tar.bz2 2953e2ed779b37f432d24f0044eb11b5ef7620bd4eaed3036e2a697e7dc13de6 3433 w-scan_20130331-1.debian.tar.bz2 ca814c2539519744786ce360f3e37c99fcca297050ee37e35c94affe62fc3bf3 116622 w-scan_20130331-1_amd64.deb Files: e6300c7587a173479e17a6796ad55457 1295 video extra w-scan_20130331-1.dsc dfc14a4707321e068a594d6899398df8 215996 video extra w-scan_20130331.orig.tar.bz2 caaabd447821edbb2a7555b1676301a4 3433 video extra w-scan_20130331-1.debian.tar.bz2 ddee341270b02d9a121394b59a7fef1f 116622 video extra w-scan_20130331-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGPiFIACgkQ9xgNJq7apkJkWQCfdFfNzvXZELaKA6jGMmZ8Mi+4 mEUAn0rqzMJEmkpv8kmqBeISTUYbgMFq =dBK4 -END PGP SIGNATUREEnd Message---
Bug#707482: marked as done (sugar-base-0.88: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707482, regarding sugar-base-0.88: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sugar-base-0.88 Version: 0.88.0-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»/build/src/sugar' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.88.0\ -DPACKAGE_STRING=\sugar-base\ 0.88.0\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.88.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o _sugarbaseext_la-_sugarbaseextmodule.lo `test -f '_sugarbaseextmodule.c' || echo '/«PKGBUILDDIR»/./src/sugar/'`_sugarbaseextmodule.c libtool: compile: gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.88.0\ -DPACKAGE_STRING=\sugar-base 0.88.0\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.88.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c -fPIC -DPIC -o .libs/_sugarbaseext_la-_sugarbaseextmodule.o /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c:30:1: warning: no previous prototype for 'init_sugarbaseext' [-Wmissing-prototypes] /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c: In function 'init_sugarbaseext': /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c:32:19: warning: variable 'd' set but not used [-Wunused-but-set-variable] /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.88.0\ -DPACKAGE_STRING=\sugar-base\ 0.88.0\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.88.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o _sugarbaseext_la-xdgmime.lo `test -f
Bug#707494: marked as done (dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707494, regarding dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: dia-newcanvas Version: 0.6.10-5.4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/python' /bin/bash ../libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../ -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/python2.7 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/pygtk-2.0 -I../src -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -g -O2 -Werror -g -MT dianewcanvasmodule_la-dianewcanvasmodule.lo -MD -MP -MF .deps/dianewcanvasmodule_la-dianewcanvasmodule.Tpo -c -o dianewcanvasmodule_la-dianewcanvasmodule.lo `test -f 'dianewcanvasmodule.c' || echo './'`dianewcanvasmodule.c libtool: compile: x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../ -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/python2.7 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/pygtk-2.0 -I../src -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -g -O2 -Werror -g -MT dianewcanvasmodule_la-dianewcanvasmodule.lo -MD -MP -MF .deps/dianewcanvasmodule_la-dianewcanvasmodule.Tpo -c dianewcanvasmodule.c -fPIC -DPIC -o .libs/dianewcanvasmodule_la-dianewcanvasmodule.o mv -f .deps/dianewcanvasmodule_la-dianewcanvasmodule.Tpo .deps/dianewcanvasmodule_la-dianewcanvasmodule.Plo (cd .\ /usr/bin/pygtk-codegen-2.0 \ --register /usr/share/pygtk/2.0/defs/pango-types.defs \ --register /usr/share/pygtk/2.0/defs/gdk-types.defs \ --register /usr/share/pygtk/2.0/defs/gtk-types.defs \ --override dianewcanvas.override \ --prefix pydianewcanvas dianewcanvas.defs) gen-dianewcanvas.c \ cp gen-dianewcanvas.c dianewcanvas.c \ rm -f gen-dianewcanvas.c note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0
Bug#707497: marked as done (python-gtkglext1: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707497, regarding python-gtkglext1: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-gtkglext1 Version: 1.1.0-9.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»/build-2.7/gtk/gdkgl' (cd ../../../gtk/gdkgl \ /usr/bin/pygtk-codegen-2.0 \ --register /usr/share/pygtk/2.0/defs/pango-types.defs \ --register /usr/share/pygtk/2.0/defs/atk-types.defs \ --register /usr/share/pygtk/2.0/defs/gdk-types.defs \ --register /usr/share/pygtk/2.0/defs/gtk-types.defs \ --override gdkglext.override \ --prefix pygdkglext gdkglext.defs) xgen-pygc \ cp xgen-pygc ../../../gtk/gdkgl/gdkglext.c \ rm -f xgen-pygc note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead note: I will now try to invoke pygobject-codegen-2.0 in the same directory /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found make[4]: *** [../../../gtk/gdkgl/gdkglext.c] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/python-gtkglext1_1.1.0-9.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--- On Thu, May 9, 2013 at 10:53:05 +0200, Lucas Nussbaum wrote: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found Fixed in newer pygobject. Closing these bugs. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#707498: marked as done (python-xklavier: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707498, regarding python-xklavier: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-xklavier Version: 0.4-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/build/xklavier' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./xklavier -I.. -I/usr/include/python2.7 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0-D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o xklavier_la-xklaviermodule.lo `test -f 'xklaviermodule.c' || echo '/«PKGBUILDDIR»/./xklavier/'`xklaviermodule.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./xklavier -I.. -I/usr/include/python2.7 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/./xklavier/xklaviermodule.c -fPIC -DPIC -o .libs/xklavier_la-xklaviermodule.o (cd /«PKGBUILDDIR»/./xklavier \ /usr/bin/pygobject-codegen-2.0 \ --override xklavier.override \ --prefix xklavier xklavier.defs) gen-xklavier.c \ cp gen-xklavier.c xklavier.c \ rm -f gen-xklavier.c /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found make[3]: *** [xklavier.c] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/python-xklavier_0.4-4_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--- On Thu, May 9, 2013 at 10:53:05 +0200, Lucas Nussbaum wrote: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found Fixed in newer pygobject. Closing these bugs. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#707500: marked as done (gupnp-igd: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707500, regarding gupnp-igd: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gupnp-igd Version: 0.2.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/debian/build/python' pygobject-codegen-2.0 \ --prefix igd\ --override /«PKGBUILDDIR»/./python/pygupnp-igd.override \ /«PKGBUILDDIR»/./python/pygupnp-igd.defs pygupnp-igd.c /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found make[3]: *** [pygupnp-igd.c] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/gupnp-igd_0.2.1-2_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--- On Thu, May 9, 2013 at 10:53:05 +0200, Lucas Nussbaum wrote: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found Fixed in newer pygobject. Closing these bugs. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#707508: marked as done (sugar-base-0.96: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707508, regarding sugar-base-0.96: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sugar-base-0.96 Version: 0.96.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»/build/src/sugar' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.96.0\ -DPACKAGE_STRING=\sugar-base\ 0.96.0\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.96.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o _sugarbaseext_la-_sugarbaseextmodule.lo `test -f '_sugarbaseextmodule.c' || echo '/«PKGBUILDDIR»/./src/sugar/'`_sugarbaseextmodule.c libtool: compile: gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.96.0\ -DPACKAGE_STRING=\sugar-base 0.96.0\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.96.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c -fPIC -DPIC -o .libs/_sugarbaseext_la-_sugarbaseextmodule.o /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c:30:1: warning: no previous prototype for 'init_sugarbaseext' [-Wmissing-prototypes] /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c: In function 'init_sugarbaseext': /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c:32:19: warning: variable 'd' set but not used [-Wunused-but-set-variable] /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.96.0\ -DPACKAGE_STRING=\sugar-base\ 0.96.0\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.96.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c
Bug#707511: marked as done (pida: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707511, regarding pida: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pida Version: 0.5.1-6 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»/moo' echo '#include moomarshals.h' moomarshals.c.tmp \ glib-genmarshal --prefix=_moo_marshal --body\ moomarshals.list moomarshals.c.tmp mv moomarshals.c.tmp moomarshals.c glib-genmarshal --prefix=_moo_marshal --header\ moomarshals.list moomarshals.h.tmp mv moomarshals.h.tmp moomarshals.h gdk-pixbuf-csource --static --build-list \ MOO_HIDE_ICON hide.png \ MOO_CLOSE_ICON close.png\ MOO_STICKY_ICON sticky.png \ MOO_DETACH_ICON detach.png \ MOO_ATTACH_ICON attach.png \ MOO_KEEP_ON_TOP_ICON keepontop.png \ stock-moo.h.tmp mv stock-moo.h.tmp stock-moo.h pygtk-codegen-2.0 --prefix _moo_stub \ --register `pkg-config --variable=defsdir pygtk-2.0`/gtk-types.defs \ --register `pkg-config --variable=defsdir pygtk-2.0`/gdk-types.defs \ --override moo.override \ --outfilename moo-pygtk.c \ moo.defs moo-pygtk.c.tmp \ mv moo-pygtk.c.tmp moo-pygtk.c note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead note: I will now try to invoke pygobject-codegen-2.0 in the same directory /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found make[1]: *** [moo-pygtk.c] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/pida_0.5.1-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--- On Thu, May 9, 2013 at 10:53:05 +0200, Lucas Nussbaum wrote: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found Fixed in newer pygobject. Closing these bugs. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#707519: marked as done (pyabiword: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707519, regarding pyabiword: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pyabiword Version: 0.8.0-11 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/build/src' /usr/bin/pygtk-codegen-2.0 --prefix pyabiword \ --register /usr/share/pygtk/2.0/defs/gdk-types.defs \ --register /usr/share/pygtk/2.0/defs/gtk-types.defs \ --override /«PKGBUILDDIR»/./src/pyabiword.override /«PKGBUILDDIR»/./src/pyabiword.defs pyabiword.c note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead note: I will now try to invoke pygobject-codegen-2.0 in the same directory /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found make[2]: *** [pyabiword.c] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/pyabiword_0.8.0-11_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--- On Thu, May 9, 2013 at 10:53:05 +0200, Lucas Nussbaum wrote: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found Fixed in newer pygobject. Closing these bugs. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#707524: marked as done (planner: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707524, regarding planner: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: planner Version: 0.14.6-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/python' CC planner_la-plannermodule.lo ( cd . /usr/bin/pygobject-codegen-2.0 \ --override planner.override \ --load-types planner-arg-types.py \ --register /usr/share/pygtk/2.0/defs/gtk-types.defs \ --prefix planner planner.defs ) gen-planner.c \ cp gen-planner.c planner.c \ rm -f gen-planner.c /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found make[3]: *** [planner.c] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/planner_0.14.6-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--- On Thu, May 9, 2013 at 10:53:05 +0200, Lucas Nussbaum wrote: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found Fixed in newer pygobject. Closing these bugs. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#707532: marked as done (sugar-base-0.84: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707532, regarding sugar-base-0.84: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sugar-base-0.84 Version: 0.84.2-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»/build/src/sugar' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.84.2\ -DPACKAGE_STRING=\sugar-base\ 0.84.2\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.84.2\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o _sugarbaseext_la-_sugarbaseextmodule.lo `test -f '_sugarbaseextmodule.c' || echo '/«PKGBUILDDIR»/./src/sugar/'`_sugarbaseextmodule.c libtool: compile: gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.84.2\ -DPACKAGE_STRING=\sugar-base 0.84.2\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.84.2\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c -fPIC -DPIC -o .libs/_sugarbaseext_la-_sugarbaseextmodule.o /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c:30:1: warning: no previous prototype for 'init_sugarbaseext' [-Wmissing-prototypes] /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c: In function 'init_sugarbaseext': /«PKGBUILDDIR»/./src/sugar/_sugarbaseextmodule.c:32:19: warning: variable 'd' set but not used [-Wunused-but-set-variable] /bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\sugar-base\ -DPACKAGE_TARNAME=\sugar-base\ -DPACKAGE_VERSION=\0.84.2\ -DPACKAGE_STRING=\sugar-base\ 0.84.2\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\sugar-base\ -DVERSION=\0.84.2\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\.libs/\ -DGETTEXT_PACKAGE=\sugar-base\ -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -I. -I/«PKGBUILDDIR»/./src/sugar -DXDG_PREFIX=sugar_mime -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pygtk-2.0 -I/usr/include/python2.7 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o _sugarbaseext_la-xdgmime.lo `test -f
Bug#707533: marked as done (zbar: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found)
Your message dated Sun, 12 May 2013 14:49:03 +0200 with message-id 20130512124903.gl12...@radis.cristau.org and subject line Re: Bug#707494: dia-newcanvas: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found has caused the Debian Bug report #707533, regarding zbar: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found 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.) -- 707533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: zbar Version: 0.10+doc-8 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«BUILDDIR»/zbar-0.10+doc/build-python2.7' /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«BUILDDIR»/zbar-0.10+doc -I./include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/python2.7 -I/usr/include/python2.7 -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/pygtk-2.0 -I/«BUILDDIR»/zbar-0.10+doc/include -Wall -Wno-parentheses -MT pygtk/pygtk_zbarpygtk_la-zbarpygtkmodule.lo -MD -MP -MF pygtk/.deps/pygtk_zbarpygtk_la-zbarpygtkmodule.Tpo -c -o pygtk/pygtk_zbarpygtk_la-zbarpygtkmodule.lo `test -f 'pygtk/zbarpygtkmodule.c' || echo '/«BUILDDIR»/zbar-0.10+doc/'`pygtk/zbarpygtkmodule.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«BUILDDIR»/zbar-0.10+doc -I./include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/python2.7 -I/usr/include/python2.7 -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/pygtk-2.0 -I/«BUILDDIR»/zbar-0.10+doc/include -Wall -Wno-parentheses -MT pygtk/pygtk_zbarpygtk_la-zbarpygtkmodule.lo -MD -MP -MF pygtk/.deps/pygtk_zbarpygtk_la-zbarpygtkmodule.Tpo -c /«BUILDDIR»/zbar-0.10+doc/pygtk/zbarpygtkmodule.c -fPIC -DPIC -o pygtk/.libs/pygtk_zbarpygtk_la-zbarpygtkmodule.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/«BUILDDIR»/zbar-0.10+doc -I./include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/python2.7 -I/usr/include/python2.7 -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
Bug#700527: [Pkg-javascript-devel] Bug#700527: jquery: diff for NMU version 1.7.2+dfsg-1.1
On Sat, May 11, 2013 at 13:12:14 -0300, Marcelo Jorge Vieira wrote: On Sat, 2013-05-11 at 17:47 +0200, gregor herrmann wrote: On Sat, 11 May 2013 12:43:14 -0300, Marcelo Jorge Vieira wrote: Dominic Hargreaves has prepared an NMU for jquery (versioned as 1.7.2+dfsg-1.1) and I've uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. His patch sets 'Conflicts' instead of 'Breaks'. Is this really the best way? I'm not sure but I left the Conflicts since this is about an actual file conflict, so it seemed safer ... I will replace 'Conflicts' with 'Breaks' and upload it to unstable now. See: http://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts Does this sounds good to you? Breaks on its own is unlikely to be sufficient. Without reading the details of this bug, with file conflicts you'd either need Breaks+Replaces or Conflicts. Cheers, Julien signature.asc Description: Digital signature
Bug#707994: Does not work with python-requests 1
Package: httpie Version: 0.3.1-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! httpie does not work anymore with python-requests 1.2.0: Traceback (most recent call last): File /usr/bin/http, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2809, in module parse_requirements(__requires__), Environment() File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 594, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: requests=0.10.1,1.0 - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages httpie depends on: ii python 2.7.3-5 ii python-argparse 1.2.1-2 ii python-pygments 1.6+dfsg-1 ii python-requests 1.2.0-2 ii python2.7 [python-argparse] 2.7.3-8 httpie recommends no packages. httpie suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRj5SnAAoJEJWkL+g1NSX5zqcP/A/IJcCgS85Aq2IpY4htlc1N 5dVb7sF02f5zGBJhG0GQs4f3QWtKzysmYIGSNyWMwqSLJIaEgd6VNSmkCCbfI8br s1112awhp0rKduugXK+e0+uf1brgwTg83ZXABkgKwHkijzLLP8Q+xraG5ILxkJ/1 cYG/ILdt3NNWmSeFJpLKEfsyfOeOsJ9LAkgajttZmlOhgrXBhwNxGM5ke26U6Wfm yWWWTqpO8IApUtr+s7CtAk1pzeIqBNryY2Ebzb7QxNRZLGqFqk6fBpK3UH18NUqC 2d7zdA+DzYugmfT2AXiIJ8wdD7KmLzObMLFQy8AkO9z2k4jUHN6ede5X88Olvcaz KmA6UdHX1AIW3EuhrMjewADTYeLs5NoQoA/S3LBrHUOsafrzq8I1RyCoofNuP9RG Ycg9K3n9c5uHwA3YXMiu1fy41K+QkVwSgyCB79ayQlbYgfqP0Cxqrl5D6Jho5ds3 jtfl0TALi7hfm7WHK/fCZUqzKJ8g0uMJeYgtEQteXr1LGRKaNcgoSjbv8hW3L63b kzE9zJR7dKtP86/023czRKTaAw5w7eo5tHIMC7wSJGb0KJZJ7NoBmZl8LTM9OoSD 9/D2/BonCgKD7jn4qa6u/ICq8kwXW2O2h6g+bXN0539Tgc81eudDRB+j8ZL++SaC iYCZg/9vWEn1cvB2R5Xi =eNKL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707996: util-linux: Needs rebuild against new glibc; causes other packages to FTBFS
Package: util-linux Version: 2.20.1-5.4 Severity: serious Justification: ftbfs From the e2fsprogs build: make[1]: Entering directory `/«PKGBUILDDIR»/debian/BUILD-STD/e2fsck' gcc -Wl,-z,relro -static -o e2fsck.static crc32.o dict.o unix.o e2fsck.o super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o b adblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o quota.o recovery.o region.o revoke.o ea_refcount.o rehash.o profile.o prof_err.o logfile.o sigcatcher.o ../lib/libquota.a ../lib/libext2fs.a ../lib/libcom_err.a -lpthread -lblkid -luuid -luuid-luuid ../lib/libe2p.a logfile.o: In function `expand_percent_expression': /«PKGBUILDDIR»/e2fsck/logfile.c:133: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries f rom the glibc version used for linking /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/libblkid.a(env.o): In function `safe_getenv': (.text+0x1be): undefined reference to `__secure_getenv' collect2: error: ld returned 1 exit status make[1]: *** [e2fsck.static] Error 1 This is due to util-linux having libblkid.a built against the old glibc and this is no longer compatible with the new glibc. It just needs a rebuild. According to jcristau this needs a sourceful upload, i.e. not a binNMU, due to it being m-a: same. Regards, Roger -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (550, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 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 util-linux depends on: ii debconf [debconf-2.0] 1.5.50 ii dpkg 1.16.10 ii initscripts2.88dsf-41+jessie1 ii install-info 5.1.dfsg.1-3 ii libblkid1 2.20.1-5.4 ii libc6 2.17-1 ii libncurses55.9+20130504-1 ii libselinux12.1.13-1 ii libslang2 2.2.4-15 ii libtinfo5 5.9+20130504-1 ii libuuid1 2.20.1-5.4 ii lsb-base 4.1+Debian9 ii tzdata 2013b-2 ii zlib1g 1:1.2.8.dfsg-1 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 3.0.16-2 ii kbd 1.15.5-1 ii util-linux-locales 2.20.1-5.4 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfixed 674094 in 4.5.0-1, fixed 674094 in 0.4.5-1
Processing commands for cont...@bugs.debian.org:
notfixed 674094 4.5.0-1
Bug #674094 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[src:lxmusic] lxmusic: FTBFS: unknown type name 'LXMusicNotification' (missing
libnotify-dev)
The source 'lxmusic' and version '4.5.0-1' do not appear to match any binary
packages
No longer marked as fixed in versions 4.5.0-1.
fixed 674094 0.4.5-1
Bug #674094 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[src:lxmusic] lxmusic: FTBFS: unknown type name 'LXMusicNotification' (missing
libnotify-dev)
Marked as fixed in versions lxmusic/0.4.5-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
674094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674094
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: ltspfs: diff for NMU version 1.1-2.1
Processing commands for cont...@bugs.debian.org: tags 698127 + patch Bug #698127 [ltspfs] ltspfs: Depends on fuse-utils; uninstallable in sid Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 698127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698127 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: Owner bug 707861
Processing commands for cont...@bugs.debian.org: owner 707861 ! Bug #707861 [gcdmaster] gcdmaster: uses libgnomeui which is going away Owner recorded as Markus Koschany a...@gambaru.de. thanks Stopping processing here. Please contact me if you need assistance. -- 707861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707861 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#698127: ltspfs: diff for NMU version 1.1-2.1
tags 698127 + patch
thanks
Dear maintainer,
I've prepared an NMU for ltspfs (versioned as 1.1-2.1). The diff
is attached to this message.
Regards.
diff -Nru ltspfs-1.1/debian/changelog ltspfs-1.1/debian/changelog
--- ltspfs-1.1/debian/changelog 2012-04-02 02:16:06.0 +0200
+++ ltspfs-1.1/debian/changelog 2013-05-12 15:25:22.0 +0200
@@ -1,3 +1,10 @@
+ltspfs (1.1-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * ltspfs: Depend on fuse instead of fuse-utils. (Closes: #698127)
+
+ -- Ansgar Burchardt ans...@debian.org Sun, 12 May 2013 15:25:17 +0200
+
ltspfs (1.1-2) unstable; urgency=low
* ltspfsd: Add symlink for init-ltsp.d hook for forward compatibility with
diff -Nru ltspfs-1.1/debian/control ltspfs-1.1/debian/control
--- ltspfs-1.1/debian/control 2012-04-02 02:09:30.0 +0200
+++ ltspfs-1.1/debian/control 2013-05-12 15:24:09.0 +0200
@@ -11,7 +11,7 @@
Package: ltspfs
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, python (= 2.4), fuse-utils
+Depends: ${shlibs:Depends}, ${misc:Depends}, python (= 2.4), fuse
Description: Fuse based remote filesystem for LTSP thin clients
LtspFS is a remote filesystem consisting of two parts:
1) A network server daemon that runs on the LTSP terminal.
Bug#706764: assaultcube-data: diff for NMU version 1.1.0.4+repack1-2.1
tags 706764 + patch
tags 706764 + pending
thanks
Dear maintainer,
I've prepared an NMU for assaultcube-data (versioned as 1.1.0.4+repack1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: J.J. Cale: Trouble In The City
diff -Nru assaultcube-data-1.1.0.4+repack1/debian/changelog assaultcube-data-1.1.0.4+repack1/debian/changelog
--- assaultcube-data-1.1.0.4+repack1/debian/changelog 2011-11-02 08:27:43.0 +0100
+++ assaultcube-data-1.1.0.4+repack1/debian/changelog 2013-05-12 15:27:32.0 +0200
@@ -1,3 +1,14 @@
+assaultcube-data (1.1.0.4+repack1-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix fails to upgrade from squeeze - trying to overwrite
+/usr/share/man/man6/assaultcube-server.6.gz:
+Add versioned Breaks/Replaces on assaultcube.
+Thanks to Andreas Beckmann for the bug report and patch.
+(Closes: #706764)
+
+ -- gregor herrmann gre...@debian.org Sun, 12 May 2013 15:26:57 +0200
+
assaultcube-data (1.1.0.4+repack1-2) unstable; urgency=low
[ Martin Erik Werner]
diff -Nru assaultcube-data-1.1.0.4+repack1/debian/control assaultcube-data-1.1.0.4+repack1/debian/control
--- assaultcube-data-1.1.0.4+repack1/debian/control 2011-11-02 09:31:22.0 +0100
+++ assaultcube-data-1.1.0.4+repack1/debian/control 2013-05-12 15:26:30.0 +0200
@@ -12,6 +12,8 @@
Package: assaultcube-data
Architecture: all
Depends: ${misc:Depends}
+Breaks: assaultcube ( 1.1.0.4+dfsg2-1)
+Replaces: assaultcube ( 1.1.0.4+dfsg2-1)
Description: data files and documentation for AssaultCube
AssaultCube, formerly ActionCube, is a first-person-shooter based on the
game Cube. Set in a realistic looking environment, as far as that's
signature.asc
Description: Digital signature
Processed: assaultcube-data: diff for NMU version 1.1.0.4+repack1-2.1
Processing commands for cont...@bugs.debian.org: tags 706764 + patch Bug #706764 [assaultcube-data] assaultcube-data: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man6/assaultcube-server.6.gz Added tag(s) patch. tags 706764 + pending Bug #706764 [assaultcube-data] assaultcube-data: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man6/assaultcube-server.6.gz Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 706764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706764 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#707960: rpc.gssd segfaults when mounting a nfsv4 volume
severity 707960 important thanks While a segfault is not tolerable you should still not file bugs as grave that do not break other packages. It's even not serious as the package is still functional for a lot of people that use it in another context than you do. Now to the bug in question: On 05/12/2013 01:06 PM, Marco d'Itri wrote: (elided)://media/nfs nfs4noauto,soft,intr,sec=krb5p 0 0 [2262594.734234] rpc.gssd[2729]: segfault at 1 ip f74714ba sp ff830170 error 4 in libgssglue.so.1.0.0[f746e000+8000] Does statd run? Does installing nfs-kernel-server by any chance fix the bug? Reverting nfs-common to 1:1.2.6-3 fixes the issue. BTW: /usr/share/bug/nfs-common/script: 5: /usr/share/bug/nfs-common/script: rpcinfo: not found Thanks, will be fixed in the next upload. Cheers Luk -- 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#707960: rpc.gssd segfaults when mounting a nfsv4 volume
Processing commands for cont...@bugs.debian.org: severity 707960 important Bug #707960 [nfs-common] rpc.gssd segfaults when mounting a nfsv4 volume Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 707960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707960 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#698128: mhddfs: diff for NMU version 0.1.39+nmu1
tags 698128 + patch
thanks
Dear maintainer,
I've prepared an NMU for mhddfs (versioned as 0.1.39+nmu1). The diff
is attached to this message.
Regards.
diff -Nru mhddfs-0.1.39/debian/changelog mhddfs-0.1.39+nmu1/debian/changelog
--- mhddfs-0.1.39/debian/changelog 2012-06-17 16:09:56.0 +0200
+++ mhddfs-0.1.39+nmu1/debian/changelog 2013-05-12 15:35:11.0 +0200
@@ -1,3 +1,10 @@
+mhddfs (0.1.39+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Depend on fuse instead of fuse-utils. (Closes: #698128)
+
+ -- Ansgar Burchardt ans...@debian.org Sun, 12 May 2013 15:35:08 +0200
+
mhddfs (0.1.39) unstable; urgency=low
* Kalyanov Dmitry optimized readdir function: now we use HASH-tables
diff -Nru mhddfs-0.1.39/debian/control mhddfs-0.1.39+nmu1/debian/control
--- mhddfs-0.1.39/debian/control 2012-06-17 16:09:56.0 +0200
+++ mhddfs-0.1.39+nmu1/debian/control 2013-05-12 15:33:34.0 +0200
@@ -14,7 +14,7 @@
Package: mhddfs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends},
- fuse-utils [!kfreebsd-amd64 !kfreebsd-i386]
+ fuse [!kfreebsd-amd64 !kfreebsd-i386]
Description: file system for unifying several mount points into one
This FUSE-based file system allows mount points (or directories) to be
combined, simulating a single big volume which can merge several hard
Processed: mhddfs: diff for NMU version 0.1.39+nmu1
Processing commands for cont...@bugs.debian.org: tags 698128 + patch Bug #698128 [mhddfs] mhddfs: Depends on fuse-utils; uninstallable in sid Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 698128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698128 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#694987: obexfs: diff for NMU version 0.11-1.1
tags 694987 + patch
thanks
Dear maintainer,
I've prepared an NMU for obexfs (versioned as 0.11-1.1). The diff
is attached to this message.
Regards.
diff -u obexfs-0.11/debian/changelog obexfs-0.11/debian/changelog
--- obexfs-0.11/debian/changelog
+++ obexfs-0.11/debian/changelog
@@ -1,3 +1,10 @@
+obexfs (0.11-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Depend on fuse instead of fuse-utils. (Closes: #694987)
+
+ -- Ansgar Burchardt ans...@debian.org Sun, 12 May 2013 15:42:20 +0200
+
obexfs (0.11-1) unstable; urgency=low
* New upstream release
diff -u obexfs-0.11/debian/control obexfs-0.11/debian/control
--- obexfs-0.11/debian/control
+++ obexfs-0.11/debian/control
@@ -7,7 +7,7 @@
Package: obexfs
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, fuse-utils
+Depends: ${shlibs:Depends}, ${misc:Depends}, fuse
Description: mount filesystem of ObexFTP capable devices
ObexFS uses FUSE to mount filesystems of ObexFTP capable
devices either manually or in autofs style mode.
Processed: obexfs: diff for NMU version 0.11-1.1
Processing commands for cont...@bugs.debian.org: tags 694987 + patch Bug #694987 [obexfs] obexfs: depends on transitional package fuse-utils Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 694987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694987 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#698127: marked as done (ltspfs: Depends on fuse-utils; uninstallable in sid)
Your message dated Sun, 12 May 2013 13:48:09 + with message-id e1ubwdf-0005nk...@franck.debian.org and subject line Bug#698127: fixed in ltspfs 1.1-2.1 has caused the Debian Bug report #698127, regarding ltspfs: Depends on fuse-utils; uninstallable in sid 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.) -- 698127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ltspfs Version: 1.1-2 Severity: serious Tags: sid User: car...@debian.org Usertags: depends-on-fuse-utils Hi ltspfs 1.1-2 has a Depends on fuse-utils. In unstable fuse-utils was dropped. This makes ltspfs uninstallable in sid. Wheezy is not directly affected as the transitional package fuse-utils is still present there, so tagging this 'sid' only. Please change this dependency to fuse. Regards, Salvatore ---End Message--- ---BeginMessage--- Source: ltspfs Source-Version: 1.1-2.1 We believe that the bug you reported is fixed in the latest version of ltspfs, 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 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt ans...@debian.org (supplier of updated ltspfs 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 May 2013 15:25:17 +0200 Source: ltspfs Binary: ltspfs ltspfsd ltspfsd-core Architecture: all amd64 source Version: 1.1-2.1 Distribution: unstable Urgency: low Maintainer: Debian LTSP Maintainers pkg-ltsp-de...@lists.alioth.debian.org Changed-By: Ansgar Burchardt ans...@debian.org Closes: 698127 Description: ltspfs - Fuse based remote filesystem for LTSP thin clients ltspfsd- Fuse based remote filesystem hooks for LTSP thin clients ltspfsd-core - Fuse based remote filesystem daemon for LTSP thin clients Changes: ltspfs (1.1-2.1) unstable; urgency=low . * Non-maintainer upload. * ltspfs: Depend on fuse instead of fuse-utils. (Closes: #698127) Checksums-Sha1: 20e33fcef654f901e2c9f25d31b726b69aafa614 2097 ltspfs_1.1-2.1.dsc f925fb8fa2193fd88ee33994a4f6ce2e0927bda4 8596 ltspfs_1.1-2.1.debian.tar.gz eecc579bcecf80f5f88d58676043a94f4408d1aa 29728 ltspfs_1.1-2.1_amd64.deb 6b541b6a0cde9055c4e3579a85c0ff20f896c19a 15942 ltspfsd_1.1-2.1_all.deb a3ad34380f93301047147efe89239007eb8ae762 31872 ltspfsd-core_1.1-2.1_amd64.deb Checksums-Sha256: cbc33ef946a130f3de083e0cddafe9115b69b782b68267f2cedba0482188fda8 2097 ltspfs_1.1-2.1.dsc f56d26e7cb57083bb49d8f718c16a686371be5cee16cf527b506351b55e4156c 8596 ltspfs_1.1-2.1.debian.tar.gz 678a44dbc5104bf8482393cf11c9397157308cf76197b56674ee5391bf9c444c 29728 ltspfs_1.1-2.1_amd64.deb d715f466e03209c43d511b5aabac227af200e5be7bb4d4671178a3837852028a 15942 ltspfsd_1.1-2.1_all.deb 453be02b46792e5040db1e0309bf9ee902d9f7d57481185a579c4e66bb113469 31872 ltspfsd-core_1.1-2.1_amd64.deb Files: eb43cc93d27822da1e3b6c9b6a58861f 2097 net optional ltspfs_1.1-2.1.dsc 474aa301a1412a9a65236c8bd0671d28 8596 net optional ltspfs_1.1-2.1.debian.tar.gz 12cb08358dbfc4dfb08c49fe03628b6d 29728 net optional ltspfs_1.1-2.1_amd64.deb 689634fcb627be9302686bce9a96ef25 15942 net optional ltspfsd_1.1-2.1_all.deb ebaea9e3ce5328c587d309f3897d569b 31872 net optional ltspfsd-core_1.1-2.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJRj5mEAAoJEIATJTTdNH3Il7UP/AuRsGX+76Wj4VLwzsYqXxy5 XfMz6wYUaUoUuGiLZF21LO+gHwfUvq3BauGdIfp3XkKHZeTud+gWmlP/MZ3sIa4E XwsRkn1hAl0j0zyPFXT92ITRQJ1WzXzhf3UNaS7v01Txk0cEsuBzNbQXYf20Swz5 6SY3y26uUJf2wpWNPmFw1nhFnkFDCdrkybk9vHDzeKKn7cN9FDO+2JbhyPyk5iOS i3DndWNpgm/xWyKFa7VfDBr6zBn5LNWPCwsWt0zu2wp6u61mZxQOFOmb5G21MASf +/+fwCwMHfCzeNxRgwT0lWMi244yOgkgY2xFs0HDW5e4TLXj7A/lSxbywA6O/H47 attWSDTlABF6v78Pe0lwnQWNYKzF3YxkoHeE9Pi0wa/4p1AUz2tLNQySSG1LFLOL 5BpYOt+YHh/9nKG0pwvSq/lqyEkzfxN46xbioWafbO9OGv9+4jugi36/0NvJSqLq Gs9g2gLpyf62pb3ZBKVPVtitWdKid6s+8a3xOolD2bfeat2in9HubbGBt0wMjFuq UZPq4+PCWOi1X/gDjtZmJr+YxFZh8BN7xNYk9XLBYiy3fvpW35f427MsRzefqFt1 PmzKfpisst1LD4LleAsIrkQgxm5wgD+gPuLkeSeAIvFYdI2jWXfevWbBbZzGLd/S rjad7DPaRzjR2G081ZO8 =HqLU -END PGP SIGNATUREEnd Message---
Bug#698128: marked as done (mhddfs: Depends on fuse-utils; uninstallable in sid)
Your message dated Sun, 12 May 2013 13:48:12 + with message-id e1ubwdi-0005o9...@franck.debian.org and subject line Bug#698128: fixed in mhddfs 0.1.39+nmu1 has caused the Debian Bug report #698128, regarding mhddfs: Depends on fuse-utils; uninstallable in sid 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.) -- 698128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mhddfs Version: 0.1.39 Severity: serious Tags: sid User: car...@debian.org Usertags: depends-on-fuse-utils Hi mhddfs 0.1.39 has a Depends on fuse-utils. In unstable fuse-utils was dropped. This makes mhddfs uninstallable in sid. Wheezy is not directly affected as the transitional package fuse-utils is still present there, so tagging this 'sid' only. Please change this dependency to fuse. Regards, Salvatore ---End Message--- ---BeginMessage--- Source: mhddfs Source-Version: 0.1.39+nmu1 We believe that the bug you reported is fixed in the latest version of mhddfs, 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 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt ans...@debian.org (supplier of updated mhddfs 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 May 2013 15:35:08 +0200 Source: mhddfs Binary: mhddfs Architecture: amd64 source Version: 0.1.39+nmu1 Distribution: unstable Urgency: low Maintainer: Dmitry E. Oboukhov un...@debian.org Changed-By: Ansgar Burchardt ans...@debian.org Closes: 698128 Description: mhddfs - file system for unifying several mount points into one Changes: mhddfs (0.1.39+nmu1) unstable; urgency=low . * Non-maintainer upload. * Depend on fuse instead of fuse-utils. (Closes: #698128) Checksums-Sha1: b4fb6dcd76829be8852260f61524afa863efa51a 1530 mhddfs_0.1.39+nmu1.dsc 405185f21cebd3e43156ed7c3fe9b9b611de36e0 40505 mhddfs_0.1.39+nmu1.tar.gz 6290fe1a9aa6305e335344ac1a5393c1769625dd 27826 mhddfs_0.1.39+nmu1_amd64.deb Checksums-Sha256: f2e3c6351c471cee7f4a2e8591d15dfff6cd184e3496b1c12a8574aff73e7e98 1530 mhddfs_0.1.39+nmu1.dsc f2238713d5306ccfa69b35a48c83d79a4d3164fc40e2c4f8be460b1b18d79646 40505 mhddfs_0.1.39+nmu1.tar.gz 5316f348f2a0d6b31c2d94a429ea250fa258651942b31c5f0be3420aa10ba3cd 27826 mhddfs_0.1.39+nmu1_amd64.deb Files: cb67d99d2d020b63687300759efbdb81 1530 utils extra mhddfs_0.1.39+nmu1.dsc 7f3ef558869a662b83590007ad34676f 40505 utils extra mhddfs_0.1.39+nmu1.tar.gz c1adb3895d8e1d85ddf618d1f054da77 27826 utils extra mhddfs_0.1.39+nmu1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJRj5s3AAoJEIATJTTdNH3IPLIP/jkajeCcFDWotVgFyTAWmaoe q9TCpGki9RNEFrQYxwyeuokE+3symbEGyPIx2sX+jJfkIC83l56MmG436e0BpqNV DpNYELt9R7N78sscfe8PNpuzKgsLRrK+duAHaqyRyNkbRLldiwNsAYrwTf9Aj9nT zeK6utulAd9TJZbwREmM4ieggCQVIvc5PnNB6+ySexuIsXEX3MRGthkHKbXeKEku mqTsxt22HjpSo9/kjrjWNKsw3RM7e+bgUo7tnK1Jc/99yGgGB0Pryt/Ny5Xz1bCF AiLrXWKPHX7NZqqh2KdbuIx8FfXJx0x5f8tA4k7TARVDEch+Kfy45Lng1VBvw+cQ yOfwy3sujiCvolQ0ribU0Tl4ap/LvJKKNr8+dZ70Bprjg+qna6EXh5qD60gn14B0 oSwM4TKsYkrkbWFr9M7ejgNrHQdCZ/62jdoKcI2VkbBusuvqEzQSOexkniCpCeLy j/mDyxF6oaUxuYqK27bflcB5iQz6J4nc+VkzGiSW+Ch3OWcCY+QTLf+WpCtBR07p Izmh5FHQYsxkx51pBwpghVAdnVkUdCO/G//Wwf5C5GHLFCzTnRut5M6aLLJjT6m7 w6+VW6DOgHAsiCIMBvggQh+OLNAQLCvd3CU1unJ1MtN7w0kk0hcIdR10WC3QBQ89 wzFKDKquc0y7xswwvZ22 =mcHk -END PGP SIGNATUREEnd Message---
Bug#698122: fuse-umfuse-ext2: diff for NMU version 0.4-1.1
tags 698122 + patch
thanks
Dear maintainer,
I've prepared an NMU for fuse-umfuse-ext2 (versioned as 0.4-1.1). The diff
is attached to this message.
Regards.
diff -u fuse-umfuse-ext2-0.4/debian/control fuse-umfuse-ext2-0.4/debian/control
--- fuse-umfuse-ext2-0.4/debian/control
+++ fuse-umfuse-ext2-0.4/debian/control
@@ -2,7 +2,6 @@
Priority: optional
Maintainer: Debian VSquare Team pkg-vsquare-de...@lists.alioth.debian.org
Uploaders: Ludovico Gardenghi gar...@debian.org, Guido Trotter ultrot...@debian.org, Filippo Giunchedi fili...@debian.org
-DM-Upload-Allowed: yes
Build-Depends: debhelper (= 5), libumlib-dev, libfuse-dev, e2fslibs-dev, cdbs
Vcs-Svn: svn://svn.debian.org/pkg-vsquare/fuse-umfuse-ext2/trunk
Vcs-Browser: http://svn.debian.org/wsvn/pkg-vsquare/fuse-umfuse-ext2/trunk/
@@ -37,7 +36,7 @@
Package: fuseext2
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, fuse-utils
+Depends: ${shlibs:Depends}, ${misc:Depends}, fuse
Description: File System in User Space - Module for ext2
This module for the FUSE kernel service allows any FUSE-enabled user to mount
Second Extended file systems, e.g. disk images.
diff -u fuse-umfuse-ext2-0.4/debian/changelog fuse-umfuse-ext2-0.4/debian/changelog
--- fuse-umfuse-ext2-0.4/debian/changelog
+++ fuse-umfuse-ext2-0.4/debian/changelog
@@ -1,3 +1,11 @@
+fuse-umfuse-ext2 (0.4-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Depend on fuse instead of fuse-utils. (Closes: #698122)
+ * debian/control: Remove deprecated DM-Upload-Allowed field.
+
+ -- Ansgar Burchardt ans...@debian.org Sun, 12 May 2013 15:48:18 +0200
+
fuse-umfuse-ext2 (0.4-1) unstable; urgency=low
[ Filippo Giunchedi ]
Processed: adjust severity
Processing commands for cont...@bugs.debian.org:
severity 707842 important
Bug #707842 [conduit] conduit: recommends python-evolution which is no longer
built
Severity set to 'important' from 'serious'
severity 707843 important
Bug #707843 [gbirthday] gbirthday: recommends python-evolution which is no
longer built
Severity set to 'important' from 'serious'
severity 707845 important
Bug #707845 [screenlets] screenlets: recommends python-evolution which is no
longer built
Severity set to 'important' from 'serious'
severity 707846 important
Bug #707846 [awn-applets-python-core] awn-applets-python-core: recommends
python-gnomedesktop which is no longer built
Severity set to 'important' from 'serious'
severity 707847 important
Bug #707847 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org}
[hotwire] hotwire: recommends python-gnomedesktop which is no longer built
Severity set to 'important' from 'serious'
severity 707848 important
Bug #707848 [winswitch] winswitch: recommends python-gnomedesktop which is no
longer built
Severity set to 'important' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
707842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707842
707843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707843
707845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707845
707846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707846
707847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707847
707848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707848
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: fuse-umfuse-ext2: diff for NMU version 0.4-1.1
Processing commands for cont...@bugs.debian.org: tags 698122 + patch Bug #698122 [fuseext2] fuseext2: Depends on fuse-utils; uninstallable in sid Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 698122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698122 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#707733: pygobject: FTBFS on kfreebsd
Emilio Pozuelo Monfort po...@debian.org writes: Package: pygobject Version: 3.8.1-2 Severity: serious (CCing BSD porters, help wanted here) pygobject currently fails to build on kfreebsd, see [1] I've tried to debug this on falla. I can reproduce the hang somewhat reliably by running: dpkg-buildpackage And if it doesn't hang or if you want to hang it again: while true; do xvfb-run dh_auto_test --builddirectory=build-2.7; done The hanging test is in test_overrides_gtk.py, but running with TEST_FILES=test_overrides_gtk.py doesn't reproduce the hang so reliably here. I've run gdb on the hanging python process and I get: (gdb) thread apply all bt Thread 1 (process 75189): #0 0x00080161ed4a in kevent () at ../sysdeps/unix/syscall-template.S:82 #1 0x000802a57bd7 in _kqueue_thread_func (arg=optimized out) at /build/buildd-glib2.0_2.36.1-2-kfreebsd- amd64-CmfXXB/glib2.0-2.36.1/./gio/kqueue/kqueue-thread.c:226 #2 0x000800a91c4a in pthread_start_thread (arg=optimized out) at manager.c:317 #3 0x in ?? () (gdb) Note that this is with libc0.1-dbg and libglib2.0-0-dbg installed. After this I'm lost. Any help is welcome. Otherwise I'll just have to stop running the whole test suite on kfreebsd, but I'd be sad to do that. Sounds like it could be similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706276 Looking at it right now Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fuse-umfuse-fat: diff for NMU version 0.1a-1.1
Processing commands for cont...@bugs.debian.org: tags 698123 + patch Bug #698123 [fusefat] fusefat: Depends on fuse-utils; uninstallable in sid Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 698123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698123 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#698123: fuse-umfuse-fat: diff for NMU version 0.1a-1.1
tags 698123 + patch
thanks
Dear maintainer,
I've prepared an NMU for fuse-umfuse-fat (versioned as 0.1a-1.1). The diff
is attached to this message.
Regards.
diff -u fuse-umfuse-fat-0.1a/debian/changelog fuse-umfuse-fat-0.1a/debian/changelog
--- fuse-umfuse-fat-0.1a/debian/changelog
+++ fuse-umfuse-fat-0.1a/debian/changelog
@@ -1,3 +1,10 @@
+fuse-umfuse-fat (0.1a-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Depend on fuse instead of fuse-utils. (Closes: #698123)
+
+ -- Ansgar Burchardt ans...@debian.org Sun, 12 May 2013 15:55:04 +0200
+
fuse-umfuse-fat (0.1a-1) unstable; urgency=low
[ Ludovico Gardenghi ]
diff -u fuse-umfuse-fat-0.1a/debian/control fuse-umfuse-fat-0.1a/debian/control
--- fuse-umfuse-fat-0.1a/debian/control
+++ fuse-umfuse-fat-0.1a/debian/control
@@ -36,7 +36,7 @@
Package: fusefat
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, fuse-utils
+Depends: ${shlibs:Depends}, ${misc:Depends}, fuse
Description: File System in User Space - Module for FAT
This module for the FUSE kernel service allows any FUSE-enabled user to mount
FAT file systems.
signature.asc
Description: Digital signature
Bug#698124: fuse-umfuse-iso9660: diff for NMU version 0.3-1.1
tags 698124 + patch
thanks
Dear maintainer,
I've prepared an NMU for fuse-umfuse-iso9660 (versioned as 0.3-1.1). The diff
is attached to this message.
Regards.
diff -u fuse-umfuse-iso9660-0.3/debian/control fuse-umfuse-iso9660-0.3/debian/control
--- fuse-umfuse-iso9660-0.3/debian/control
+++ fuse-umfuse-iso9660-0.3/debian/control
@@ -2,7 +2,6 @@
Priority: optional
Maintainer: Debian VSquare Team pkg-vsquare-de...@lists.alioth.debian.org
Uploaders: Ludovico Gardenghi gar...@debian.org, Guido Trotter ultrot...@debian.org, Filippo Giunchedi fili...@debian.org
-DM-Upload-Allowed: yes
Build-Depends: debhelper (= 5), libumlib-dev, libfuse-dev, libiso9660-dev, libz-dev, cdbs
Standards-Version: 3.9.3
Vcs-Svn: svn://svn.debian.org/pkg-vsquare/fuse-umfuse-iso9660/trunk
@@ -37,7 +36,7 @@
Package: fuseiso9660
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, fuse-utils
+Depends: ${shlibs:Depends}, ${misc:Depends}, fuse
Description: File System in User Space - Module for ISO9660
This module for the FUSE kernel service allows any FUSE-enabled user to mount
ISO9660 file systems, e.g. CDROM disk images.
diff -u fuse-umfuse-iso9660-0.3/debian/changelog fuse-umfuse-iso9660-0.3/debian/changelog
--- fuse-umfuse-iso9660-0.3/debian/changelog
+++ fuse-umfuse-iso9660-0.3/debian/changelog
@@ -1,3 +1,11 @@
+fuse-umfuse-iso9660 (0.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Depend on fuse instead of fuse-utils. (Closes: #698124)
+ * debian/control: Remove deprecated DM-Upload-Allowed field.
+
+ -- Ansgar Burchardt ans...@debian.org Sun, 12 May 2013 16:02:05 +0200
+
fuse-umfuse-iso9660 (0.3-1) unstable; urgency=low
[ Filippo Giunchedi ]
signature.asc
Description: Digital signature
Processed: fuse-umfuse-iso9660: diff for NMU version 0.3-1.1
Processing commands for cont...@bugs.debian.org: tags 698124 + patch Bug #698124 [fuseiso9660] fuseiso9660: Depends on fuse-utils; uninstallable in sid Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 698124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698124 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#701385: Block
block 701385 by 707996 thanks This is due to libblkid.a using a symbol removed in the new glibc. It needs either a straight rebuild and/or updating to the latest upstream. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Block
Processing commands for cont...@bugs.debian.org: block 701385 by 707996 Bug #701385 [src:e2fsprogs] e2fsprogs: ftbfs with eglibc-2.17 701385 was not blocked by any bugs. 701385 was not blocking any bugs. Added blocking bug(s) of 701385: 707996 thanks Stopping processing here. Please contact me if you need assistance. -- 701385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701385 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#707577: wl driver leads to general protection fault on 3.8.11 kernel
Hello, I have exactely the same problem. -- Philippe Abdessemed 22 bis allée des Raisiniers 97217 Les Anses d'Arlet 0696 72 72 37
Bug#698122: marked as done (fuseext2: Depends on fuse-utils; uninstallable in sid)
Your message dated Sun, 12 May 2013 15:02:34 + with message-id e1ubxng-0007gz...@franck.debian.org and subject line Bug#698122: fixed in fuse-umfuse-ext2 0.4-1.1 has caused the Debian Bug report #698122, regarding fuseext2: Depends on fuse-utils; uninstallable in sid 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.) -- 698122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fuseext2 Version: 0.4-1 Severity: serious Tags: sid User: car...@debian.org Usertags: depends-on-fuse-utils Hi fuseext2 0.4-1 has a Depends on fuse-utils. In unstable fuse-utils was dropped. This makes fuseext2 uninstallable in sid. Wheezy is not directly affected as the transitional package fuse-utils is still present there, so tagging this 'sid' only. Please change this dependency to fuse. Regards, Salvatore ---End Message--- ---BeginMessage--- Source: fuse-umfuse-ext2 Source-Version: 0.4-1.1 We believe that the bug you reported is fixed in the latest version of fuse-umfuse-ext2, 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 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt ans...@debian.org (supplier of updated fuse-umfuse-ext2 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 May 2013 15:48:18 +0200 Source: fuse-umfuse-ext2 Binary: umview-mod-umfuseext2 fuseext2 Architecture: amd64 source Version: 0.4-1.1 Distribution: unstable Urgency: low Maintainer: Debian VSquare Team pkg-vsquare-de...@lists.alioth.debian.org Changed-By: Ansgar Burchardt ans...@debian.org Closes: 698122 Description: fuseext2 - File System in User Space - Module for ext2 umview-mod-umfuseext2 - View-OS in user space - ext2 module for UMFUSE Changes: fuse-umfuse-ext2 (0.4-1.1) unstable; urgency=low . * Non-maintainer upload. * Depend on fuse instead of fuse-utils. (Closes: #698122) * debian/control: Remove deprecated DM-Upload-Allowed field. Checksums-Sha1: 599840d13ba284c09126edd7da52c2d7554b5402 2134 fuse-umfuse-ext2_0.4-1.1.dsc 5b9639c37e570deb74ad4bbd1fcbac57cc549172 2959 fuse-umfuse-ext2_0.4-1.1.diff.gz 7663cc6b76761dc92596cf7ef131384312888509 27580 umview-mod-umfuseext2_0.4-1.1_amd64.deb f8ad0a8372dcd98b83f8f8d3ded2bbc85e53c8ca 25234 fuseext2_0.4-1.1_amd64.deb Checksums-Sha256: 871f5ef4e5ce6d7435958381ceadc8c2afe47f3947fe9a7a318572162c1419f2 2134 fuse-umfuse-ext2_0.4-1.1.dsc 181e627e8f31c91f653c19da21008801fb1a42883e264d4065d433fd9d4f2652 2959 fuse-umfuse-ext2_0.4-1.1.diff.gz 4aa78a8083e329ba7c0cb53adf3313dfc555d21ec0721617e13b8f370eb2e53b 27580 umview-mod-umfuseext2_0.4-1.1_amd64.deb a5247d1e5c3df90cd11138f0658951b705c5de2d5a24e78010b6ab0ad7958ace 25234 fuseext2_0.4-1.1_amd64.deb Files: 0542d4ff56316a80fff956e745e1b98a 2134 misc optional fuse-umfuse-ext2_0.4-1.1.dsc 01f9fc1d4b67eae8ac59cbac520818ae 2959 misc optional fuse-umfuse-ext2_0.4-1.1.diff.gz 9e2766c9a4f15d7f4729a3517e351711 27580 misc optional umview-mod-umfuseext2_0.4-1.1_amd64.deb 8bfbe30740633f0298bcb87aff5fa7bf 25234 misc optional fuseext2_0.4-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJRj56UAAoJEIATJTTdNH3I1QkQAJr9Kp1ANhGGTlWlDPuhB/66 VxMYlqAKhLziMPAfUN4qGyIDPfnFIPJImWUl9csbLO+/BsSG+9p21zUqx3QapGBe EF7S5Qh8BNnYGH0SksgsIDhbjnIcpTXqc0NrjjfNVkSRPbMP4yKrItHjqOQ8i43a yZ+CseHNFar+iJeCURTLeAkvMWwZyfjbzpS20whaSW8WxLe3mrv7UsfKYEMbeYp0 IsXXducAYsyHsRE9quizcc3Gl7yUG1rPslBH0xDlrXtlnM9I5w5zpOfM2n1EBk9E y/LocN79rPyvbzSlZQHTFvSGSl9G+nBlSELhFXyXhuXFmI0vQLasIhGWHDQYYQbj sWxj7/wvqf6dbDCQoxXttNUU04EWOHNHLWWSH1rwcnErZYYnZC40zBWS5NVbyR02 oZsG03raCZU2H4fIwqC7JTdqvx03J4U1Q3C5RJjAUaXdWjN9OXMyQcYJVjJX7Imn svenxitVkEO33GNYIbRdYv/NSeI+d7+YsDhKQuwvYfkTMHLpjveBnDd7+uE9bnX8 2iMtzdDpw/CjSuLm10dsfjLFfLGbZw0xnN+yL6lDXY4ccxXNKrjXTJmPWnsHOACb HfJp9hG+x5kRrLCC+3aKx92w28qShh42d6/hOr5fq8YaUN746eq36Fmj8mKppFAr BRe7tyaXLegU6zRmL58q =f6eu -END PGP SIGNATUREEnd Message---
Bug#698123: marked as done (fusefat: Depends on fuse-utils; uninstallable in sid)
Your message dated Sun, 12 May 2013 15:02:37 + with message-id e1ubxnj-0007hy...@franck.debian.org and subject line Bug#698123: fixed in fuse-umfuse-fat 0.1a-1.1 has caused the Debian Bug report #698123, regarding fusefat: Depends on fuse-utils; uninstallable in sid 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.) -- 698123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fusefat Version: 0.1a-1 Severity: serious Tags: sid User: car...@debian.org Usertags: depends-on-fuse-utils Hi fusefat 0.1a-1 has a Depends on fuse-utils. In unstable fuse-utils was dropped. This makes fusefat uninstallable in sid. Wheezy is not directly affected as the transitional package fuse-utils is still present there, so tagging this 'sid' only. Please change this dependency to fuse. Regards, Salvatore ---End Message--- ---BeginMessage--- Source: fuse-umfuse-fat Source-Version: 0.1a-1.1 We believe that the bug you reported is fixed in the latest version of fuse-umfuse-fat, 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 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt ans...@debian.org (supplier of updated fuse-umfuse-fat 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 May 2013 15:55:04 +0200 Source: fuse-umfuse-fat Binary: umview-mod-umfusefat fusefat Architecture: amd64 source Version: 0.1a-1.1 Distribution: unstable Urgency: low Maintainer: Debian VSquare Team pkg-vsquare-de...@lists.alioth.debian.org Changed-By: Ansgar Burchardt ans...@debian.org Closes: 698123 Description: fusefat- File System in User Space - Module for FAT umview-mod-umfusefat - View-OS in user space - FAT module for UMFUSE Changes: fuse-umfuse-fat (0.1a-1.1) unstable; urgency=low . * Non-maintainer upload. * Depend on fuse instead of fuse-utils. (Closes: #698123) Checksums-Sha1: 827a3c5acff0b2608c7beeca52163cfca57df065 2132 fuse-umfuse-fat_0.1a-1.1.dsc 25ee673bc1eede3dd4307fefd59d49a8b54b8916 2249 fuse-umfuse-fat_0.1a-1.1.diff.gz d520e0be8e59f051d4e81839551d7ec3c802d203 35470 umview-mod-umfusefat_0.1a-1.1_amd64.deb 11956b14bd5fadd5e1e48c0e733366637c9c875d 34674 fusefat_0.1a-1.1_amd64.deb Checksums-Sha256: 9e2ab258a55d13bc7a56ee0d770b3be96a70636fb5dfc98b0591e50b9821eba9 2132 fuse-umfuse-fat_0.1a-1.1.dsc 7144495c33aadd4b159207dd35854c5b5c28cc3d0072a545b02b512dd9b78981 2249 fuse-umfuse-fat_0.1a-1.1.diff.gz 4b4f1bf41ed67a25e56f19af4184d99348cb1a002a39ad83cb0c91ab0f0c0a38 35470 umview-mod-umfusefat_0.1a-1.1_amd64.deb 81f1c9bdf83b4cd6677a21890f52bfc823ebee851877462422291d0f5b37fa8b 34674 fusefat_0.1a-1.1_amd64.deb Files: 91b3488fc875605d3eee530bea6b6855 2132 misc optional fuse-umfuse-fat_0.1a-1.1.dsc 954c66f417115c3875969cae4d48c42c 2249 misc optional fuse-umfuse-fat_0.1a-1.1.diff.gz a97083fd0e862c6e74ebe6c61d7680d4 35470 misc optional umview-mod-umfusefat_0.1a-1.1_amd64.deb 448d3dfd06e2cf3f30f58ba76fae1c2e 34674 misc optional fusefat_0.1a-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJRj5/lAAoJEIATJTTdNH3Irn4QANjhuVtxblnzeHh4PMuGBVMv 1s8gwmPiQOSm5WoGLaijCLt9R9xkSwrjxBm8MjrZ6X9wyunLSc02HA7+RfRX/EEo tHP+BcZmh/0sgiGitMJVkauOQKbwZ5aSpdNUCrxBgium3vRSs5LP66CbZP17t+1u o6TRJfCvawVC4fuGWeDWbv9aagwhCPwHUz1UTwyDaFi60e5nDBE/7uD2SSrJT6fm VNcakFLdyIHi+S3mb8AFQWSv7KRB+HCEEhydjUGO8u8of65bNj89abPC0MKTLZu0 Z9D94SBGpJP9lXL0zCyAa+93rAHRlVzVOg4vlsQ5HLAfBr8sY7qVF7rsKzh/6/Uh o1pZn195fbP6w7kk3cCatbKI6MEjRr0wHtiiDNAt1yXxAKTWV4GvKG2jG1z6QZm5 J9e7K2pZJ/DhPx9wvVbbfGTlASsrHJCkQsGuBSDklpJJn+TL0fL5ACI8v8ThNT5p 2qGyH96lhjyeamcJnFad1VflqoZRGrqmHUqX0CdSfo6Kt9DRWngy/MfpCOmxJONT DroL1BRlmEltsLoXMb/TL6LVhi/fnQ9ZQi+XMyOOSpv+yX2Ojpz8P19j89JtNiPs Cd9ysU0s1UMGpRrrLVMP5/dJgDHC7YRb/WR156Z2LrFTUVUYvyAQ+dDoMd043Ptm K/XY/ZiVl4cP86zlAI4n =E7E+ -END PGP SIGNATUREEnd Message---
Bug#698124: marked as done (fuseiso9660: Depends on fuse-utils; uninstallable in sid)
Your message dated Sun, 12 May 2013 15:02:40 + with message-id e1ubxnm-0007io...@franck.debian.org and subject line Bug#698124: fixed in fuse-umfuse-iso9660 0.3-1.1 has caused the Debian Bug report #698124, regarding fuseiso9660: Depends on fuse-utils; uninstallable in sid 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.) -- 698124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fuseiso9660 Version: 0.3-1 Severity: serious Tags: sid User: car...@debian.org Usertags: depends-on-fuse-utils Hi fuseiso9660 0.3-1 has a Depends on fuse-utils. In unstable fuse-utils was dropped. This makes fuseiso9660 uninstallable in sid. Wheezy is not directly affected as the transitional package fuse-utils is still present there, so tagging this 'sid' only. Please change this dependency to fuse. Regards, Salvatore ---End Message--- ---BeginMessage--- Source: fuse-umfuse-iso9660 Source-Version: 0.3-1.1 We believe that the bug you reported is fixed in the latest version of fuse-umfuse-iso9660, 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 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt ans...@debian.org (supplier of updated fuse-umfuse-iso9660 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 May 2013 16:02:05 +0200 Source: fuse-umfuse-iso9660 Binary: umview-mod-umfuseiso9660 fuseiso9660 Architecture: amd64 source Version: 0.3-1.1 Distribution: unstable Urgency: low Maintainer: Debian VSquare Team pkg-vsquare-de...@lists.alioth.debian.org Changed-By: Ansgar Burchardt ans...@debian.org Closes: 698124 Description: fuseiso9660 - File System in User Space - Module for ISO9660 umview-mod-umfuseiso9660 - View-OS in user space - ISO9660 module for UMFUSE Changes: fuse-umfuse-iso9660 (0.3-1.1) unstable; urgency=low . * Non-maintainer upload. * Depend on fuse instead of fuse-utils. (Closes: #698124) * debian/control: Remove deprecated DM-Upload-Allowed field. Checksums-Sha1: 0511e292594ddd02aa370dbd0cecb1d69e2d0b8e 2185 fuse-umfuse-iso9660_0.3-1.1.dsc f7ed07aa51172ca6fd395eed3e74ed1488b83ccf 2786 fuse-umfuse-iso9660_0.3-1.1.diff.gz b7df6df98b5d2b6eda0e6dfcf0f0dfcea58dc0e9 10048 umview-mod-umfuseiso9660_0.3-1.1_amd64.deb a864c9eba8e88e5b94cbcd3fba4215bb9f20de6b 10770 fuseiso9660_0.3-1.1_amd64.deb Checksums-Sha256: 71eb43309554bd64a4bc645665915d1f87aac9c14879ae6b038d55d839bc943c 2185 fuse-umfuse-iso9660_0.3-1.1.dsc 23ed9d2a399a63b629ccb13fb8ca7f2e20461c88693c34ea520269cc425acd0b 2786 fuse-umfuse-iso9660_0.3-1.1.diff.gz c3145439b5f5eebb6932b5c13afec87d6caf20271e83543629b5b7945d891e52 10048 umview-mod-umfuseiso9660_0.3-1.1_amd64.deb bfa9e35aab1f15380cff29d1005fc263943cf31dba3a46c2863d23ddcccfe32a 10770 fuseiso9660_0.3-1.1_amd64.deb Files: 703548a1990fb12ca908efa760003a68 2185 misc optional fuse-umfuse-iso9660_0.3-1.1.dsc 768e1926048f2cacec4c241f20c05365 2786 misc optional fuse-umfuse-iso9660_0.3-1.1.diff.gz c4fd0d7f82236552126f371f9321699b 10048 misc optional umview-mod-umfuseiso9660_0.3-1.1_amd64.deb 05ddbc14f29a35f0aeca3dff25da630d 10770 misc optional fuseiso9660_0.3-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJRj6G0AAoJEIATJTTdNH3IbtoQAIrQLgb6dijsdrmPp2DXghBG rack793+dn7H3cXFFGgRJG2jvxGw59JdcFHX+t4QCptEEOIswohNQXU9WpmQtezy ez9sYdNb7vugYmx/NaX/D5zB9B+P/E4JvScda8UYwunEa6OnLiZ3A9MpBXyyOX1X p63AvLBVv/2sM/wChPTIWgRoD48P9KcshwkbxhzhVI9rortZAE8IIFaOL4nPwoGX MuIAD0+bZTyoZzDfabWbo2RSACPoz/uZKMwzT5c/rbWZa3sSYiUqotNRanHld7Mz jnl+nxoAUx4GcdjDe3gUbDD/8pqYsbwf3R9NTomBjMNGWt/+GkDn88e5Cl6KgoEX imfo9Wgr7gcu5ZNWAerLYAu5lb0dedIbSr6tONtVOwV1C4gsOQxMmI8783VytPWZ FUNbcJRCkjjNkCKrtWT2a1frAzLwf8394YmV5RQwgv+fFBd210VDbfGML/JpNVBq NKq7nyd/JAaYjWTpaFW/aJtmhQILPtdZFWFS6PIyrbmp0q/hoOGt/pNt/bZKEP1n X7SJsx0nSwFMjZ0n2YDAMSOEKm3B0EN0P9ZgyFLs171Xbw8Mtxj4Sg94w3K2KGo8 0oTCR+JEdZIBPdbYhNL/8CpGdpjdygC+MbTlS805FizonXf2Eau7A5sb6PaRyuiW yLuU4a1hB4vtz3aI0/aa =cWVz -END PGP SIGNATUREEnd Message---
Bug#694987: marked as done (obexfs: depends on transitional package fuse-utils)
Your message dated Sun, 12 May 2013 15:05:07 + with message-id e1ubxpj-0007mi...@franck.debian.org and subject line Bug#694987: fixed in obexfs 0.11-1.1 has caused the Debian Bug report #694987, regarding obexfs: depends on transitional package fuse-utils 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.) -- 694987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: obexfs Version: 0.11-1 obexfs depends on fuse-utils, which has been replaced by the fuse package. Please update the dependency! Julian ---End Message--- ---BeginMessage--- Source: obexfs Source-Version: 0.11-1.1 We believe that the bug you reported is fixed in the latest version of obexfs, 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 694...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt ans...@debian.org (supplier of updated obexfs 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 12 May 2013 15:42:20 +0200 Source: obexfs Binary: obexfs Architecture: amd64 source Version: 0.11-1.1 Distribution: unstable Urgency: low Maintainer: Hendrik Sattler deb...@hendrik-sattler.de Changed-By: Ansgar Burchardt ans...@debian.org Closes: 694987 Description: obexfs - mount filesystem of ObexFTP capable devices Changes: obexfs (0.11-1.1) unstable; urgency=low . * Non-maintainer upload. * Depend on fuse instead of fuse-utils. (Closes: #694987) Checksums-Sha1: 03f704d66d4c012018dcf334394906312447d2cb 1731 obexfs_0.11-1.1.dsc bffd3dff8c845e61ed4e4a9c27e172b76744f6ae 5002 obexfs_0.11-1.1.diff.gz 1e21ac5f715525348be9e52ee61531dd5d9b05ed 17472 obexfs_0.11-1.1_amd64.deb Checksums-Sha256: 55f89b15d063f72db247250e4a75cda00067ace6b485fb63761403fe8a970393 1731 obexfs_0.11-1.1.dsc e027717bef8962a258ef76d4aef79d99e9888a69e11b26e610ba10d06d5edc30 5002 obexfs_0.11-1.1.diff.gz 88c640495e0a47adb9677adcc45b68016313a6335e7f4a287e7b7aea63327c63 17472 obexfs_0.11-1.1_amd64.deb Files: a22911c0d17b0e2a2dd0ecec973d646b 1731 comm optional obexfs_0.11-1.1.dsc 0b058b937426130af7a5f524baba2dc7 5002 comm optional obexfs_0.11-1.1.diff.gz 0c42a88e5666fb48d8ba51ba07c806d2 17472 comm optional obexfs_0.11-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJRj50QAAoJEIATJTTdNH3IsocQAMeuUOvxK2aG9W/gIw77umhr MVAzV5uXWDdHg/Mdz1Ly03bSjk7zjdRpiU+vGqLo2KsxDhkDGRjSMXf9ySWujU1i MGJV5fRAGeO4MCzYQKVE7t7+YXlZu3tMAUldvMxt0okE6ORDiUhvSCZbvPAiJv0k cUp0rpJvXzynWghBKwNNaHC/U6QFKepf3YxRdzDXMqdj+XFkpAv9/25bEEjwupfb AuwKhRSEfNGVDYzRTK0As2BPMK+yZiKbA8Py6y4tjNXNsFrfySqJ9i7IkS4C9rHm XHW3jXNl8wOCH91yBvI5WMTkG67DTd+CpNaFR4qxgvX4II7YtvbS4V+9Eoatx7jW 4mkWtDOYgInOdyU/NAfjLTJTvUY0bD+IsyyHxlfv8lgGSMLjqE4X/EDu796Y9eNF jCdO3k3HEfrv/iv4LcW9nHokS8bC0UMJ+WMDDmmEUmBsM1sXMPpo7AfcOnHtXW9R ljoZEgULPTGaMLfEz8TkgoFJDp6uQReecIZMzazKhmVgkul76ww12lqj/JINUMly tPaB79tVa01bUZUCbTanAP18QWnRUCqw6jS4kwzaAZEsnYgcpWsnp5KMzeuFggUp /KX0+UUCnPr/1h1g2ivZOeHZzDP1AMiBI163qxM7HUqr46aYoJiN7sYRiBBBYQ/p DNiHbEgtasQZneQhwRE7 =rmRn -END PGP SIGNATUREEnd Message---
Bug#707611: marked as done (File conflict with old munin-plugins-extra)
Your message dated Sun, 12 May 2013 15:04:55 + with message-id e1ubxpx-0007kn...@franck.debian.org and subject line Bug#707611: fixed in munin 2.0.14-1 has caused the Debian Bug report #707611, regarding File conflict with old munin-plugins-extra 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.) -- 707611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: munin-plugins-core Version: 2.0.13-1 Severity: serious /usr/share/munin/plugins/ntp_ was moved from munin-plugins-extra to munin- plugins-core between 2.0.6-4 and 2.0.13-1 so it's not possible to upgrade if both packages are installed. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.0-wrar-1 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: munin Source-Version: 2.0.14-1 We believe that the bug you reported is fixed in the latest version of munin, 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 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen hol...@debian.org (supplier of updated munin 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 12 May 2013 15:50:01 +0200 Source: munin Binary: munin-node munin-plugins-core munin-plugins-extra munin-plugins-java munin munin-common munin-async munin-doc Architecture: source all Version: 2.0.14-1 Distribution: unstable Urgency: low Maintainer: Munin Debian Maintainers packag...@munin-monitoring.org Changed-By: Holger Levsen hol...@debian.org Description: munin - network-wide graphing framework (grapher/gatherer) munin-async - network-wide graphing framework (async master/client) munin-common - network-wide graphing framework (common) munin-doc - network-wide graphing framework (documentation) munin-node - network-wide graphing framework (node) munin-plugins-core - network-wide graphing framework (plugins for node) munin-plugins-extra - network-wide graphing framework (user contributed plugins for nod munin-plugins-java - network-wide graphing framework (java plugins for node) Closes: 707611 707811 Changes: munin (2.0.14-1) unstable; urgency=low . * New upstream bugfix release. (Closes: #707811) - See upstream changelog for the full list of changes. * ntp_ plugin was moved from munin-plugins-extra to munin-plugins-core, add appropriate Breaks: and Replaces: relationsships. (Closes: #707611) * Make dependencies on librrds-perl and liblog-log4perl-perl unversioned. Checksums-Sha1: 0f6924aeaa84e52641b3edd8c2b5d105ce2ca93d 2362 munin_2.0.14-1.dsc 94d6a00cf6458cedb5febcdd632536b44959ceac 1333774 munin_2.0.14.orig.tar.gz 28302befe791872af5d2944a547cefd8999ec2cd 49546 munin_2.0.14-1.diff.gz d05e1a77133a18170076a4b9a684da99c170fb4e 133796 munin-node_2.0.14-1_all.deb f60269cdd64c2e7b3b7dc3d2502fd8d9a9e4ddf3 310352 munin-plugins-core_2.0.14-1_all.deb 502a81d496a530744cfcdc477f38bc36941acdf5 158364 munin-plugins-extra_2.0.14-1_all.deb 7f61e83084a99be9c2733f4eb7c3b044d4306cdf 152360 munin-plugins-java_2.0.14-1_all.deb a4e22bb2524561ab75fe170b2cec39b7271dcfbc 208404 munin_2.0.14-1_all.deb cfed7afb53540ee75fbebe9918ab16cbf350ef3a 98858 munin-common_2.0.14-1_all.deb a9ebb69443b6d5235377b1f1ee3ad2cb424ac138 91058 munin-async_2.0.14-1_all.deb 2a7e30c37a842e38c8709fdf8ec49d51cfd13fce 219480 munin-doc_2.0.14-1_all.deb Checksums-Sha256: 11dde8869e654a9248e97de1efe3a4015b18bc7693039d9e99f50cc75824bff2 2362 munin_2.0.14-1.dsc 7526c7a582dd1ede3c7e78e2b0d9fc19240b289b402feeabe495df1ee70b0dbe 1333774 munin_2.0.14.orig.tar.gz 1e039ebc68c8199c2ea21c40e8f69bff62c688c84ea0abc9941a6abac0283cb9 49546 munin_2.0.14-1.diff.gz de8674f15820a5918d4f88a06143c890c7049cc105db062bc7a867e6ca72c95e 133796 munin-node_2.0.14-1_all.deb df6706ad1f18dd4b8076a2aa0e714d2003b372aa6118b6d0e0d6c9923759593f 310352
Bug#702475: Bug#707879: apache2: mod_mpm_itk.so: undefined symbol: cap_set_proc
Thanks Arno, I didn't find 702475 when searching earlier. Stefan, I confirm that the workaround works (but you need to use the full path). --- /etc/apache2/mods-available/mpm_itk.load2013-05-12 10:39:44.743748291 + +++ /etc/apache2/mods-available/mpm_itk.load2013-05-12 10:39:44.743748291 + @@ -1,2 +1,3 @@ # Conflicts: mpm_event mpm_worker mpm_prefork +LoadFile /lib/x86_64-linux-gnu/libcap.so.2 LoadModule mpm_itk_module /usr/lib/apache2/modules/mod_mpm_itk.so -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707861: marked as done (gcdmaster: uses libgnomeui which is going away)
Your message dated Sun, 12 May 2013 15:47:43 + with message-id e1ubyux-0001q5...@franck.debian.org and subject line Bug#707861: fixed in cdrdao 1:1.2.3-2 has caused the Debian Bug report #707861, regarding gcdmaster: uses libgnomeui which is going away 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.) -- 707861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gcdmaster Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs libgnomeuimm Hi, Your package uses libgnomeuimm which is long deprecated and going to be removed from the archive. Your package should be ported away from it soon. Thanks, Emilio ---End Message--- ---BeginMessage--- Source: cdrdao Source-Version: 1:1.2.3-2 We believe that the bug you reported is fixed in the latest version of cdrdao, 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 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany a...@gambaru.de (supplier of updated cdrdao 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 12 May 2013 15:18:48 +0200 Source: cdrdao Binary: cdrdao Architecture: source amd64 Version: 1:1.2.3-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: cdrdao - records CDs in Disk-At-Once (DAO) mode Closes: 699320 707861 Changes: cdrdao (1:1.2.3-2) unstable; urgency=low . * QA upload. * Do not build the gcdmaster binary package anymore because it depends on the obsolete libgnomeuimm library which is going to be removed from Debian. (Closes: #707861) * debian/control: - Drop libgnomeuimm-2.6-dev and libgtkmm-2.4-dev from Build-Depends, they are going to be removed from Debian. - Add libgconf2-dev and dh-autoreconf to Build-Depends and remove autotools-dev. - Make libperl4-corelibs-perl | perl ( 5.12.3-7) a recommendation instead of a full dependency. This is acceptable because the example perl scripts are not required by cdrdao to function properly. (Closes: #699320) * Override lintian warning script-uses-perl4-libs-without-dep. * debian/rules: - Build with --autoreconf instead with --autotools_dev to recreate the whole build system during build time. - Disable lame, scglib and xdao support explicitly. - Override dh_auto_install and change the destination directory to debian/tmp thus no further changes are required for the existing install files. Checksums-Sha1: d480f6f8c83bd39d5cac71ba059bc0188d3a194c 1814 cdrdao_1.2.3-2.dsc 70d6547795a1342631c7ab56709fd1940c2aff9f 1428695 cdrdao_1.2.3.orig.tar.bz2 cfee04248661a7e0d0e866de07cf7f2ffbbac1fd 20856 cdrdao_1.2.3-2.debian.tar.gz 3ac2f587ee828c166ae04036fdac81780587aa0d 475080 cdrdao_1.2.3-2_amd64.deb Checksums-Sha256: 5e2c1e7fba77ad958e408d95c776b80f91c81b316a6fa820e6849ba7734cf941 1814 cdrdao_1.2.3-2.dsc 8193cb8fa6998ac362c55807e89ad0b3c63edc6b01afaeb3d5042519527fb75e 1428695 cdrdao_1.2.3.orig.tar.bz2 bb9798caf379335ad6ab3fd3ed821835011e797088156a1fa9e0c27559dbccdf 20856 cdrdao_1.2.3-2.debian.tar.gz 2e394d49d36c6215d223f7c11ff12d7cda5e1338b0a046aa195651718a8d4da9 475080 cdrdao_1.2.3-2_amd64.deb Files: f2faeece9056559e3b270902c71dadc0 1814 otherosfs optional cdrdao_1.2.3-2.dsc 8d15ba6280bb7ba2f4d6be31d28b3c0c 1428695 otherosfs optional cdrdao_1.2.3.orig.tar.bz2 8945666328387c80c8507e2206fee899 20856 otherosfs optional cdrdao_1.2.3-2.debian.tar.gz 35d52c7f7d3c4f0ecfe06575e5cc2cc1 475080 otherosfs optional cdrdao_1.2.3-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRj7W+AAoJEHQmOzf1tfkTu3sP/R9WjkrWVaEkjme4s7MZW6fr 74nDMuE0L9gAf90YmsM9Fn2XDB2Mfi00xJ61ehtnpei+lMU0EMZf6VTrdW/sudco jET51zD2f/wBf8INj/BMyEOFMjojr0N0UUmxpTRED1s9Kv0TmMFM7fXt+2m1pEA7 qsKjVrzzagJvm67qYYeFh32XL3rMHt2BrZ3wBJpTNgX4H6t3Q/mD5yUUg5/Ymxva OnUDHtH2HkwwydYxwb+ivJbVoIUr02WJeFNLdGvCR5m2r3R7XcfhyYXSI8gFa2GH
Bug#701673: No-change sourceful upload required to get rid of python2.6 dependencies
user release.debian@packages.debian.org usertags 701673 = binnmu reassign 701673 release.debian.org retitle 701673 nmu: shogun (python2.6 removal) thanks I overlooked this, a binNMU should be enough. Release Team, please schedule a binNMU for shogun, I was unable to reproduce the FTBFS reported in #701673. nmu shogun_1.1.0-6 . ALL . -m 'Drop python2.6' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: No-change sourceful upload required to get rid of python2.6 dependencies
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was dktrkr...@debian.org). usertags 701673 = binnmu There were no usertags set. Usertags are now: binnmu. reassign 701673 release.debian.org Bug #701673 [src:shogun] shogun: FTBFS on i386, amd64 and powerpcspe Bug reassigned from package 'src:shogun' to 'release.debian.org'. No longer marked as found in versions shogun/1.1.0-6. Ignoring request to alter fixed versions of bug #701673 to the same values previously set retitle 701673 nmu: shogun (python2.6 removal) Bug #701673 [release.debian.org] shogun: FTBFS on i386, amd64 and powerpcspe Changed Bug title to 'nmu: shogun (python2.6 removal)' from 'shogun: FTBFS on i386, amd64 and powerpcspe' thanks Stopping processing here. Please contact me if you need assistance. -- 701673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701673 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#707908: Missing source for nfsdcltrack.8
On 05/12/2013 04:54 AM, David Prévot wrote: Hi, Hi David The nfsdcltrack.8 man page is “Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)” but the POD source is not provided, thus failing to comply with the terms of its licence (GPL2+) and DFSG2. The POD source is not meant to be used anymore according to the original provider of the man page. So I sent a patch upstream to remove the auto generated comments and unneeded parts of the man page. Cheers Luk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 701673 to shogun, found 701673 in 1.1.0-6 ...
Processing commands for cont...@bugs.debian.org: reassign 701673 shogun Bug #701673 [release.debian.org] nmu: shogun (python2.6 removal) Bug reassigned from package 'release.debian.org' to 'shogun'. Ignoring request to alter found versions of bug #701673 to the same values previously set Ignoring request to alter fixed versions of bug #701673 to the same values previously set found 701673 1.1.0-6 Bug #701673 [shogun] nmu: shogun (python2.6 removal) There is no source info for the package 'shogun' at version '1.1.0-6' with architecture '' Unable to make a source version for version '1.1.0-6' Marked as found in versions 1.1.0-6. retitle 701673 shogun: FTBFS on i386, amd64 and powerpcspe Bug #701673 [shogun] nmu: shogun (python2.6 removal) Changed Bug title to 'shogun: FTBFS on i386, amd64 and powerpcspe' from 'nmu: shogun (python2.6 removal)' thanks Stopping processing here. Please contact me if you need assistance. -- 701673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701673 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#694928: marked as done (flash-kernel: postinst modifies /etc/default/rcS)
Your message dated Sun, 12 May 2013 16:17:43 + with message-id e1ubyxz-0003jn...@franck.debian.org and subject line Bug#694928: fixed in flash-kernel 3.6 has caused the Debian Bug report #694928, regarding flash-kernel: postinst modifies /etc/default/rcS 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.) -- 694928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initscripts Version: 2.88dsf-34 Severity: serious After a fresh installation of Debian Squeeze and immediate upgrade to Wheezy, I am asked to confirm changes for /etc/default/rcS which i never touched. Setting up initscripts (2.88dsf-34) ... Installing new version of config file /etc/init.d/bootlogs ... Installing new version of config file /etc/init.d/bootmisc.sh ... Installing new version of config file /etc/init.d/checkfs.sh ... Installing new version of config file /etc/init.d/checkroot.sh ... Installing new version of config file /etc/init.d/mountall.sh ... Installing new version of config file /etc/init.d/mountall-bootclean.sh ... Installing new version of config file /etc/init.d/mountnfs.sh ... Installing new version of config file /etc/init.d/mountnfs-bootclean.sh ... Installing new version of config file /etc/init.d/mountdevsubfs.sh ... Installing new version of config file /etc/init.d/mountkernfs.sh ... Installing new version of config file /etc/init.d/mtab.sh ... Installing new version of config file /etc/init.d/rc.local ... Installing new version of config file /etc/init.d/sendsigs ... Installing new version of config file /etc/init.d/umountfs ... Installing new version of config file /etc/init.d/umountnfs.sh ... Installing new version of config file /etc/init.d/umountroot ... Installing new version of config file /etc/init.d/urandom ... Configuration file `/etc/default/rcS' == File on system created by you or by a script. == File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** rcS (Y/I/N/O/D/Z) [default=N] ? D --- /etc/default/rcS2012-11-10 18:33:22.812057000 + +++ /etc/default/rcS.dpkg-new 2012-08-31 20:14:04.0 + @@ -7,11 +7,18 @@ # # This file belongs to the initscripts package. -TMPTIME=0 -SULOGIN=no -DELAYLOGIN=no -UTC=yes -VERBOSE=no -FSCKFIX=yes -RAMRUN=no -RAMLOCK=no +# delete files in /tmp during boot older than x days. +# '0' means always, -1 or 'infinite' disables the feature +#TMPTIME=0 + +# spawn sulogin during boot, continue normal boot if not used in 30 seconds +#SULOGIN=no + +# do not allow users to log in until the boot has completed +#DELAYLOGIN=no + +# be more verbose during the boot process +#VERBOSE=no + +# automatically repair filesystems with inconsistencies during boot +#FSCKFIX=no -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 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 initscripts depends on: ii coreutils 8.20-3 ii debianutils 4.3.4 ii libc6 2.13-37 ii lsb-base4.1+Debian9 ii mount 2.20.1-5.2 ii sysv-rc 2.88dsf-34 ii sysvinit-utils 2.88dsf-34 Versions of packages initscripts recommends: ii e2fsprogs 1.42.5-1 ii psmisc 22.20-1 initscripts suggests no packages. -- no debconf information -- Martin Zobel-Helas zo...@debian.org | Debian System Administrator Debian GNU/Linux Developer | Debian Listmaster GPG key http://go.debian.net/B11B627B |Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: flash-kernel Source-Version: 3.6 We believe that the bug you reported is fixed in the latest version of flash-kernel, 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 694...@bugs.debian.org, and the
Bug#707424: marked as done (xmp: FTBFS: src/plugin/audacious3.c:388:36: error: 'const struct OutputAPI' has no member named 'buffer_playing')
Your message dated Sun, 12 May 2013 16:18:28 + with message-id e1ubyyi-0003ta...@franck.debian.org and subject line Bug#707424: fixed in xmp 3.4.0-2 has caused the Debian Bug report #707424, regarding xmp: FTBFS: src/plugin/audacious3.c:388:36: error: 'const struct OutputAPI' has no member named 'buffer_playing' 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.) -- 707424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xmp Version: 3.4.0-1.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' CC src/loaders/common.o CC src/loaders/iff.o CC src/loaders/itsex.o CC src/loaders/asif.o CC src/loaders/voltable.o CC src/loaders/xm_load.o CC src/loaders/mod_load.o CC src/loaders/s3m_load.o CC src/loaders/stm_load.o CC src/loaders/669_load.o CC src/loaders/far_load.o CC src/loaders/mtm_load.o CC src/loaders/ptm_load.o CC src/loaders/okt_load.o CC src/loaders/alm_load.o CC src/loaders/amd_load.o CC src/loaders/rad_load.o CC src/loaders/ult_load.o CC src/loaders/mdl_load.o CC src/loaders/it_load.o CC src/loaders/stx_load.o CC src/loaders/pt3_load.o CC src/loaders/sfx_load.o CC src/loaders/flt_load.o CC src/loaders/st_load.o CC src/loaders/emod_load.o CC src/loaders/imf_load.o CC src/loaders/digi_load.o CC src/loaders/fnk_load.o CC src/loaders/ice_load.o CC src/loaders/hsc_load.o CC src/loaders/liq_load.o CC src/loaders/ims_load.o CC src/loaders/masi_load.o CC src/loaders/amf_load.o CC src/loaders/psm_load.o CC src/loaders/stim_load.o CC src/loaders/mmd_common.o CC src/loaders/mmd1_load.o CC src/loaders/mmd3_load.o CC src/loaders/rtm_load.o CC src/loaders/dmf_load.o CC src/loaders/tcb_load.o CC src/loaders/dt_load.o CC src/loaders/gtk_load.o CC src/loaders/no_load.o CC src/loaders/arch_load.o CC src/loaders/sym_load.o CC src/loaders/dtt_load.o CC src/loaders/mgt_load.o CC src/loaders/med2_load.o CC src/loaders/med3_load.o CC src/loaders/med4_load.o CC src/loaders/ssmt_load.o CC src/loaders/dbm_load.o CC src/loaders/umx_load.o CC src/loaders/gdm_load.o CC src/loaders/coco_load.o CC src/loaders/pw_load.o CC src/loaders/gal5_load.o CC src/loaders/gal4_load.o CC src/loaders/mfp_load.o CC src/loaders/polly_load.o CC src/loaders/prowizard/prowiz.o CC src/loaders/prowizard/ptktable.o CC src/loaders/prowizard/tuning.o CC src/loaders/prowizard/ac1d.o CC src/loaders/prowizard/di.o CC src/loaders/prowizard/eureka.o CC src/loaders/prowizard/fc-m.o CC src/loaders/prowizard/fuchs.o CC src/loaders/prowizard/fuzzac.o CC src/loaders/prowizard/gmc.o CC src/loaders/prowizard/heatseek.o CC src/loaders/prowizard/kris.o CC src/loaders/prowizard/ksm.o CC src/loaders/prowizard/mp.o CC src/loaders/prowizard/np1.o CC src/loaders/prowizard/np2.o CC src/loaders/prowizard/np3.o CC src/loaders/prowizard/p60a.o CC src/loaders/prowizard/p61a.o CC src/loaders/prowizard/pm10c.o CC src/loaders/prowizard/pm18a.o CC src/loaders/prowizard/pha.o CC src/loaders/prowizard/prun1.o CC src/loaders/prowizard/prun2.o CC src/loaders/prowizard/tdd.o CC src/loaders/prowizard/unic.o CC src/loaders/prowizard/unic2.o CC src/loaders/prowizard/wn.o CC src/loaders/prowizard/zen.o CC src/loaders/prowizard/tp3.o CC src/loaders/prowizard/p40.o CC src/loaders/prowizard/xann.o CC src/loaders/prowizard/p50a.o CC src/loaders/prowizard/pp21.o CC src/loaders/prowizard/starpack.o CC src/loaders/prowizard/titanics.o CC src/loaders/prowizard/skyt.o CC src/loaders/prowizard/novotrade.o CC src/loaders/prowizard/hrt.o CC src/loaders/prowizard/noiserun.o CC src/misc/control.o CC src/misc/info.o CC src/misc/readdata.o CC src/misc/load.o CC src/misc/ppdepack.o CC src/misc/unsqsh.o CC src/misc/mmcmp.o CC src/misc/readrle.o CC src/misc/readhuff.o CC src/misc/readlzw.o CC src/misc/unarc.o CC src/misc/arcfs.o CC src/misc/oxm.o CC src/misc/mkstemp.o CC src/misc/xfd.o CC src/misc/crc32.o CC src/misc/inflate.o CC src/misc/muse.o CC src/misc/unlzx.o CC src/misc/s404_dec.o CC src/player/convert.o CC src/player/driver.o CC src/player/formats.o CC src/player/misc.o CC src/player/period.o CC src/player/player.o CC src/player/readrc.o CC src/player/scan.o CC src/player/ulaw.o CC src/player/cruncher.o CC src/player/med_synth.o CC src/player/filter.o CC
Bug#707464: marked as done (spice-gtk: FTBFS: SpiceClientGLib-2.0.gir:79.11-79.30: error: expected start element of `parameter')
Your message dated Sun, 12 May 2013 16:18:24 + with message-id e1ubyye-0003s8...@franck.debian.org and subject line Bug#707464: fixed in spice-gtk 0.19-0nocelt2 has caused the Debian Bug report #707464, regarding spice-gtk: FTBFS: SpiceClientGLib-2.0.gir:79.11-79.30: error: expected start element of `parameter' 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.) -- 707464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: spice-gtk Version: 0.12-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/build-gtk3/vapi' GENspice-client-glib-2.0.vapi SpiceClientGLib-2.0.gir:79.11-79.30: error: expected start element of `parameter' instance-parameter name=audio transfer-ownership=none SpiceClientGLib-2.0.gir:81.11-81.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:178.11-178.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:180.11-180.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:188.11-188.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:190.11-190.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:201.11-201.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:203.11-203.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:214.11-214.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:216.11-216.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:224.11-224.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:226.11-226.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:237.11-237.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:239.11-239.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:247.11-247.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:249.11-249.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:272.11-272.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:274.11-274.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:283.11-283.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:285.11-285.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:296.11-296.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:298.11-298.10: error: expected end element of `parameter' /instance-parameter SpiceClientGLib-2.0.gir:315.11-315.34: error: expected start element of `parameter' instance-parameter name=channel transfer-ownership=none SpiceClientGLib-2.0.gir:317.11-317.10: error:
Processed: block 667906 with 705067 707440
Processing commands for cont...@bugs.debian.org: block 667906 with 705067 707440 Bug #667906 [release.debian.org] transition: libffi6 667906 was blocked by: 707797 701393 707399 701397 707509 707441 667906 was not blocking any bugs. Added blocking bug(s) of 667906: 705067 and 707440 thanks Stopping processing here. Please contact me if you need assistance. -- 667906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667906 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: block 667906 with 707361
Processing commands for cont...@bugs.debian.org: block 667906 with 707361 Bug #667906 [release.debian.org] transition: libffi6 667906 was blocked by: 707797 707399 707440 701397 701393 705067 707509 707441 667906 was not blocking any bugs. Added blocking bug(s) of 667906: 707361 thanks Stopping processing here. Please contact me if you need assistance. -- 667906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667906 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#701385: Block
On Sun, May 12, 2013 at 02:35:07PM -0400, Theodore Ts'o wrote: On Sun, May 12, 2013 at 03:09:42PM +0100, Roger Leigh wrote: This is due to libblkid.a using a symbol removed in the new glibc. It needs either a straight rebuild and/or updating to the latest upstream. Any reason to keep this open? Once util-linux is recompiled, the FTBFS will be resolved automatically. Or is eglibc buggy by not being backwards compatible, such that binaries compiled against the old glibc won't run if eglibc is installed, requiring a rebuild from source of the entire universe, and meaning that any old binaries from say, Steam, will all break? If so, I'd call this a huge, horrendous eglibc bug that should disqualify it from being installed as the default C library until it is fixed. Though Shalt Not Break Backwards Compatibility. That's a good question. It may well be the case that whatever e2fsprogs linked statically against libblkid.a is broken until rebuilt due to the missing symbol. I think it's fair to say that util-linux was using what appears to be an internal symbol, so questionable whether it was using public API/ABI; what was __secure_getenv is now secure_getenv. If it's clear that this has caused breakage then __secure_getenv should probably be re-introduced. If the existing packages are still fully functional, and it's only an issue for rebuilding, then I think the bug should be safe to close. If I don't get a reply from the (inactive) maintainer of util-linux by tonight, I'll NMU it--it's just a rebuild with no source changes. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707460: marked as done (units-filter: FTBFS: unites.y:655:37: error: conversion from 'mpq_class {aka __gmp_expr__mpq_struct [1], __mpq_struct [1]}' to non-scalar type 'mpz_class {aka __gmp_expr
Your message dated Sun, 12 May 2013 18:47:55 +
with message-id e1ubbjl-00052g...@franck.debian.org
and subject line Bug#707460: fixed in units-filter 3.5-3
has caused the Debian Bug report #707460,
regarding units-filter: FTBFS: unites.y:655:37: error: conversion from
'mpq_class {aka __gmp_expr__mpq_struct [1], __mpq_struct [1]}' to non-scalar
type 'mpz_class {aka __gmp_expr__mpz_struct [1], __mpz_struct [1]}' requested
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.)
--
707460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: units-filter
Version: 3.5-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
g++ -g -c -DRECODE_SUPPORT=1 unitesparser.cc
unites.y: In function 'void printValue(optiontype, yystype, int)':
unites.y:655:37: error: conversion from 'mpq_class {aka
__gmp_expr__mpq_struct [1], __mpq_struct [1]}' to non-scalar type
'mpz_class {aka __gmp_expr__mpz_struct [1], __mpz_struct [1]}' requested
make[2]: *** [unitesparser.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2013/05/09/units-filter_3.5-2_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: units-filter
Source-Version: 3.5-3
We believe that the bug you reported is fixed in the latest version of
units-filter, 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 707...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
georg...@debian.org (supplier of updated units-filter 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...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 12 May 2013 19:52:37 +0200
Source: units-filter
Binary: units-filter
Architecture: source amd64
Version: 3.5-3
Distribution: unstable
Urgency: low
Maintainer: Georges Khaznadar georg...@debian.org
Changed-By: georg...@debian.org
Description:
units-filter - Parser for expressions concerning physical values
Closes: 707460
Changes:
units-filter (3.5-3) unstable; urgency=low
.
* Modified my DEBEMAIL
* fixed a conversion not allowed by the last version of gcc. Closes:#707460
* updated Standards-Version and compat level
* fixed the Suggests: field in control file
* introduced hardening-wrapper in the rules and build-dependencies
* fixed src/unites.y: added a format string for printf
* fixed src/Makefile to take in account fortifying options in CXXFLAGS
Checksums-Sha1:
cd86c2be98f356413807ae07bd4ca0daff6c97bf 1122 units-filter_3.5-3.dsc
d31bfa65fb031de9302712af5f7207fa0775ac27 6808 units-filter_3.5-3.debian.tar.gz
97d7a0f132f593b6af4739c0aa86bc51330a6b96 33380 units-filter_3.5-3_amd64.deb
Checksums-Sha256:
6ea878d782c4af0e72fc70a70c04bd7a63f41c028171451469ac469d48c62f01 1122
units-filter_3.5-3.dsc
d8c7340e6ca5c5b1c2f9ec7896a352836763105ed51b19525edc717642fc547f 6808
units-filter_3.5-3.debian.tar.gz
46f98a44cd5cf5c6d26fee1ecf73dc0d2dd2154bc75a73d60e18e01a544ee346 33380
units-filter_3.5-3_amd64.deb
Files:
d9d44f1c9896fa5e2bd39f03cb44be6f 1122 science optional units-filter_3.5-3.dsc
098eef6fb46439b301ce62bbc841ae66 6808 science optional
units-filter_3.5-3.debian.tar.gz
a51c96da19e3349afd7fad06d897b0fa 33380 science optional
units-filter_3.5-3_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iD8DBQFRj+Bcnfmb2hFpETARAvIcAJ4oJMoujziLnyhj/UBpVC9qJlyd8QCeL8kt
V08GcZwZUuEL8FXd3BQZbyw=
=p0YD
-END PGP SIGNATUREEnd Message---
Bug#708048: base: Kernel Panic after resume from suspend/hibernation
Package: base Severity: critical Justification: breaks the whole system Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? After hibernation, and suspend (on a Acer 3820T laptop) after hibernation I got my laptop broke with a kernel panic. -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707849: [Python-apps-team] Bug#707849: ocrfeeder: depends on python-gtkspell which is going away
On Sat, May 11, 2013 at 10:07:28PM +0200, Emilio Pozuelo Monfort wrote: Your package depends on python-gtkspell which is about to be removed from the archive. Please remove the gtkspell support and the dependency from your package for now. Hey, how urgent is this? Upstream is looking into porting the gtkspell support to PyGI. Berto -- 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 708040 is important
Processing commands for cont...@bugs.debian.org: severity 708040 important Bug #708040 [libgl1-mesa-dri] libgl1-mesa-dri: uninstallable Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 708040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708040 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#708048: base: Kernel Panic after resume from suspend/hibernation
Control: tags -1 moreinfo Control: severity -1 important On Sun, May 12, 2013 at 20:56:00 +0200, giova wrote: Package: base Severity: critical Justification: breaks the whole system Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? After hibernation, and suspend (on a Acer 3820T laptop) after hibernation I got my laptop broke with a kernel panic. You'll need to at least provide the kernel log before anything can be done with this report. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#708048: base: Kernel Panic after resume from suspend/hibernation
Processing control commands: tags -1 moreinfo Bug #708048 [base] base: Kernel Panic after resume from suspend/hibernation Added tag(s) moreinfo. severity -1 important Bug #708048 [base] base: Kernel Panic after resume from suspend/hibernation Severity set to 'important' from 'critical' -- 708048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708048 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: your mail
Processing commands for cont...@bugs.debian.org:
unarchive 602056
Bug #602056 {Done: Nicholas Bamber nicho...@periapt.co.uk}
[libsoap-lite-perl] libsoap-lite-perl: Client dies with Not a HASH reference
at /usr/share/perl5/SOAP/Lite.pm line 3755.
Unarchived Bug 602056
reopen 602056
Bug #602056 {Done: Nicholas Bamber nicho...@periapt.co.uk}
[libsoap-lite-perl] libsoap-lite-perl: Client dies with Not a HASH reference
at /usr/share/perl5/SOAP/Lite.pm line 3755.
'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 libsoap-lite-perl/0.712-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
602056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602056
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#602056: libsoap-lite-perl: Client dies with Not a HASH reference at /usr/share/perl5/SOAP/Lite.pm line 3755.
Hi,
On Sun, May 12, 2013 at 06:45:18PM +0200, Xavier wrote:
Hi all,
according to https://rt.cpan.org/Public/Bug/Display.html?id=62667
discussion, this bug is rejected and the associated patch may break code
using Moose and SOAP::Lite. Can I remove it ?
I am using SOAP::Lite on lenny (without the patch) which acts as a client.
The server is a .NET monster (which is maintained by a 3rd party).
About a month ago my code using this service broke with the same message.
(Because the server side did not send the message my code expected.)
I added checks
if( ref $something eg 'HASH' ) { ... }
to the code to avoid the code path which would access hash elements.
So I do not consider the referenced debian bugreport classification as grave
right.
Working it around on the client side is possible.
(and maybe is the right thing to do)
Regards,
cstamas
--
CSILLAG Tamas (cstamas) - http://cstamas.hu/
--
To UNSUBSCRIBE, email to debian-perl-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130512182305.GT19172@rivendell
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701385: Block
On Sun, May 12, 2013 at 03:09:42PM +0100, Roger Leigh wrote: This is due to libblkid.a using a symbol removed in the new glibc. It needs either a straight rebuild and/or updating to the latest upstream. Any reason to keep this open? Once util-linux is recompiled, the FTBFS will be resolved automatically. Or is eglibc buggy by not being backwards compatible, such that binaries compiled against the old glibc won't run if eglibc is installed, requiring a rebuild from source of the entire universe, and meaning that any old binaries from say, Steam, will all break? If so, I'd call this a huge, horrendous eglibc bug that should disqualify it from being installed as the default C library until it is fixed. Though Shalt Not Break Backwards Compatibility. - Ted -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
