Bug#675435: CC-BY-SA-2.0 license not suitable for main
Source: freemedforms-project
Version: 0.7.1-1
Severity: serious
Quoting your copyright file:
==
Files: global_resources/pixmap/svg/{Gnome-applications-science.svg
Office-calendar-modified.svg
Printer.svg
unadvised.svg}
Copyright: 2006-2008 Lapo Calamandrei, Jakub Steiner, Andreas Nilsson
License: CC-BY-SA-2.0
==
CC-BY-SA-2.0 is not considered suitable for main.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591969: status
Hi, whats the status of this bug? cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667138: marked as done (codeblocks: ftbfs with GCC-4.7)
Your message dated Fri, 01 Jun 2012 07:03:26 + with message-id and subject line Bug#667138: fixed in codeblocks 10.05-2.1 has caused the Debian Bug report #667138, regarding codeblocks: ftbfs with GCC-4.7 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.) -- 667138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: codeblocks Version: 10.05-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. ../../../../src/include/scripting/squirrel/squtils.h:38:4: error: 'sq_vm_free' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/codeblocks_10.05-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] In file included from ../../../../src/include/scripting/squirrel/sqpcheader.h:17:0, from sqvm.cpp:4: ../../../../src/include/scripting/squirrel/sqstate.h:142:6: note: 'void sq_vm_free(void*, SQUnsignedInteger)' declared here, later in the translation unit In file included from ../../../../src/include/scripting/squirrel/sqobject.h:5:0, from ../../../../src/include/scripting/squirrel/sqpcheader.h:16, from sqvm.cpp:4: ../../../../src/include/scripting/squirrel/squtils.h: In instantiation of 'void sqvector::_realloc(SQUnsignedInteger) [with T = long int; SQUnsignedInteger = long unsigned int]': ../../../../src/include/scripting/squirrel/squtils.h:45:4: required from 'void sqvector::resize(SQUnsignedInteger, const T&) [with T = long int; SQUnsignedInteger = long unsigned int]' ../../../../src/include/scripting/squirrel/squtils.h:27:3: required from 'void sqvector::copy(const sqvector&) [with T = long int]' ../../../../src/include/scripting/squirrel/sqclosure.h:97:34: required from here ../../../../src/include/scripting/squirrel/squtils.h:97:3: error: 'sq_vm_realloc' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] In file included from ../../../../src/include/scripting/squirrel/sqpcheader.h:17:0, from sqvm.cpp:4: ../../../../src/include/scripting/squirrel/sqstate.h:141:7: note: 'void* sq_vm_realloc(void*, SQUnsignedInteger, SQUnsignedInteger)' declared here, later in the translation unit make[5]: *** [sqstate.lo] Error 1 make[5]: *** [sqbaselib.lo] Error 1 make[5]: *** [sqobject.lo] Error 1 make[5]: *** [sqvm.lo] Error 1 make[5]: Leaving directory `/«PKGBUILDDIR»/src/sdk/scripting/squirrel' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/«PKGBUILDDIR»/src/sdk/scripting' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/src/sdk' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j10 returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 --- End Message --- --- Begin Message --- Source: codeblocks Source-Version: 10.05-2.1 We believe that the bug you reported is fixed in the latest version of codeblocks, which is due to be installed in the Debian FTP archive: codeblocks-common_10.05-2.1_all.deb to main/c/codeblocks/codeblocks-common_10.05-2.1_all.deb codeblocks-contrib-dbg_10.05-2.1_amd64.deb to main/c/codeblocks/codeblocks-contrib-dbg_10.05-2.1_amd64.deb codeblocks-contrib_10.05-2.1_amd64.deb to main/c/codeblocks/codeblocks-contrib_10.05-2.1_amd64.deb codeblocks-dbg_10.05-2.1_amd64.deb to main/c/codeblocks/codeblocks-dbg_10.05-2.1_amd64.deb codeblocks-dev_10.05-2.1_amd64.deb to main/c/codeblocks/codeblocks-dev_10.05-2.1_amd64.deb codeblocks_10.05-2.1.debian.tar.gz to main/c/codeblocks/codeblocks_10.05-2.1.debian.tar.gz codeblocks_10.05-2.1.dsc to main/c/codeblocks/codeblocks_10.05-2.1.dsc codebl
Bug#674391: NMU cancelled
tags 671391 -pending thanks NMU has been cancelled last night. Sorry, for any inconvenience caused. -- Regards, Dmitrijs. signature.asc Description: OpenPGP digital signature
Bug#621460: marked as done (Still uses libdb4.8)
Your message dated Fri, 01 Jun 2012 07:19:42 + with message-id and subject line Bug#621460: fixed in subversion 1.6.17dfsg-3.1 has caused the Debian Bug report #621460, regarding Still uses libdb4.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 621460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: subversion Version: 1.6.16dfsg-1 Severity: normal User: pkg-db-de...@lists.alioth.debian.org Usertags: db5.1 Your package currently still uses Berkeley DB version 4.8 (libdb4.8). However, there is a newer Berkeley DB version in the archive (libdb5.1), with a compatible API. Berkeley DB version 4.8 will be eventually removed from unstable in favor of version 5.1. Please port your package to libdb5.1 as soon as possible. In most cases only change required is to update build depends from libdb4.8-dev to libdb-dev, or just recompile the package. More complicated scenarios: - Package does check for DB_VERSION_MAJOR == 4 - this should be updated to (DB_VERSION_MAJOR > 4) || ((DB_VERSION_MAJOR == 4) && (DB_VERSION_MINOR >= XX)). - Configure checks - sometime there is a list of db-4.8 db-4.6 db-4.2, etc., this needs to be updated to just db (or db-5.1 db-5 db), or at least list the 'db' in the front You can see example patch in cyrus-imapd-2.2: http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.2.git;a=blob;f=debian/patches/99-berkelydb-5.1.dpatch;hb=HEAD - The packages which use Berkeley DB transactional mode need to upgrade the database files before the upgrade. This is fairly straightforward and is well documented on the Berkeley DB website. But you probably already know that because it's not the first Berkeley DB transition. The example script can be found in the cyrus-imapd-2.4 (not yet released): http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db;hb=HEAD Thanks, -- Ondřej Surý -- System Information: Debian Release: squeeze/sid APT prefers maverick-updates APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: subversion Source-Version: 1.6.17dfsg-3.1 We believe that the bug you reported is fixed in the latest version of subversion, which is due to be installed in the Debian FTP archive: libapache2-svn_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/libapache2-svn_1.6.17dfsg-3.1_amd64.deb libsvn-dev_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/libsvn-dev_1.6.17dfsg-3.1_amd64.deb libsvn-doc_1.6.17dfsg-3.1_all.deb to main/s/subversion/libsvn-doc_1.6.17dfsg-3.1_all.deb libsvn-java_1.6.17dfsg-3.1_all.deb to main/s/subversion/libsvn-java_1.6.17dfsg-3.1_all.deb libsvn-jni_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/libsvn-jni_1.6.17dfsg-3.1_amd64.deb libsvn-perl_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/libsvn-perl_1.6.17dfsg-3.1_amd64.deb libsvn-ruby1.8_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/libsvn-ruby1.8_1.6.17dfsg-3.1_amd64.deb libsvn-ruby_1.6.17dfsg-3.1_all.deb to main/s/subversion/libsvn-ruby_1.6.17dfsg-3.1_all.deb libsvn1_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/libsvn1_1.6.17dfsg-3.1_amd64.deb python-subversion_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/python-subversion_1.6.17dfsg-3.1_amd64.deb subversion-tools_1.6.17dfsg-3.1_all.deb to main/s/subversion/subversion-tools_1.6.17dfsg-3.1_all.deb subversion_1.6.17dfsg-3.1.diff.gz to main/s/subversion/subversion_1.6.17dfsg-3.1.diff.gz subversion_1.6.17dfsg-3.1.dsc to main/s/subversion/subversion_1.6.17dfsg-3.1.dsc subversion_1.6.17dfsg-3.1_amd64.deb to main/s/subversion/subversion_1.6.17dfsg-3.1_amd64.deb 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 621...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated subversion 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: Tue,
Bug#624810: marked as done (subversion: FTBFS on some archs during binNMU)
Your message dated Fri, 01 Jun 2012 07:19:42 + with message-id and subject line Bug#624810: fixed in subversion 1.6.17dfsg-3.1 has caused the Debian Bug report #624810, regarding subversion: FTBFS on some archs during binNMU 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.) -- 624810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: subversion Version: 1.6.16dfsg-1 Severity: serious Justification: fails to build from source The package FTBFS on ia64 and kfreebsd-* when binNMUed for the current Python transition. Here are the relevant snippets from the build logs: Tail of logs for subversion on ia64: Test Summary Report --- /build/buildd-subversion_1.6.16dfsg-1+b1-ia64-70XUQh/subversion-1.6.16dfsg/subversion/bindings/swig/perl/native/t/3client.t (Wstat: 1280 Tests: 119 Failed: 5) Failed tests: 12, 19, 56, 91, 108 Non-zero exit status: 5 Files=10, Tests=214, 12 wallclock secs ( 0.16 usr 0.02 sys + 4.06 cusr 0.41 csys = 4.65 CPU) Result: FAIL Failed 1/10 test programs. 5/214 subtests failed. make[3]: *** [test_dynamic] Error 255 make[3]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b1-ia64-70XUQh/subversion-1.6.16dfsg/BUILD/subversion/bindings/swig/perl/native' make[2]: *** [check-swig-pl] Error 2 make[2]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b1-ia64-70XUQh/subversion-1.6.16dfsg/BUILD' make[1]: *** [check-swig-pl] Error 2 make[1]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b1-ia64-70XUQh/subversion-1.6.16dfsg' make: *** [debian/stamp-build-arch] Error 2 Tail of logs for subversion on kfreebsd-amd64: /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/util.rb:304:in `wait_until_svnserve_gets_available_at' /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/util.rb:297:in `times' /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/util.rb:297:in `wait_until_svnserve_gets_available_at' /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/util.rb:226:in `setup_svnserve' /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/util.rb:217:in `each' /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/util.rb:217:in `setup_svnserve' /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/util.rb:39:in `setup_basic' /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/test_client.rb:11:in `setup' 219 tests, 1326 assertions, 0 failures, 18 errors make[2]: *** [check-swig-rb] Error 1 make[2]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg/BUILD' make[1]: *** [check-swig-rb] Error 2 make[1]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-amd64-0cFuqz/subversion-1.6.16dfsg' make: *** [debian/stamp-build-arch] Error 2 Tail of logs for subversion on kfreebsd-i386: /build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-i386-HBvtpB/subversion-1.6.16dfsg/subversion/bindings/swig/ruby/test/test_client.rb:11:in `setup' 219 tests, 922 assertions, 0 failures, 70 errors make[2]: *** [check-swig-rb] Error 1 make[2]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-i386-HBvtpB/subversion-1.6.16dfsg/BUILD' make[1]: *** [check-swig-rb] Error 2 make[1]: *** Waiting for unfinished jobs . -- Ran 106 tests in 682.180s OK make[2]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-i386-HBvtpB/subversion-1.6.16dfsg/BUILD' make[1]: Leaving directory `/build/buildd-subversion_1.6.16dfsg-1+b2-kfreebsd-i386-HBvtpB/subversion-1.6.16dfsg' make: *** [debian/stamp-build-arch] Error 2 -- System Information: Debian Release: squeeze/sid --- End Message --- --- Begin Message --- Source: subversion Source-Version: 1.6.17dfsg-3.1 We believe that the bug you reported is fixed in the latest version of subversion, which is due to be installed in the Debian FTP archive: libapache2-svn_1
Bug#663388: marked as done (gnustep-back-common: unowned files after purge (policy 6.8, 10.8) violating FHS (policy 9.1) too)
Your message dated Fri, 01 Jun 2012 07:18:22 + with message-id and subject line Bug#663388: fixed in gnustep-back 0.22.0-1 has caused the Debian Bug report #663388, regarding gnustep-back-common: unowned files after purge (policy 6.8, 10.8) violating FHS (policy 9.1) too 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.) -- 663388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnustep-back-common Version: 0.20.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails >From the attached log (scroll to the bottom...): 0m32.0s ERROR: FAIL: Package purging left files on system: /root/GNUstep not owned /root/GNUstep/Library not owned /var/lib/GNUstep not owned /var/lib/GNUstep/Fonts not owned /var/log/gnustep-back-common.log not owned As putting files into /root is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. cheers, Andreas gnustep-back-common_0.20.1-2.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: gnustep-back Source-Version: 0.22.0-1 We believe that the bug you reported is fixed in the latest version of gnustep-back, which is due to be installed in the Debian FTP archive: gnustep-back-common_0.22.0-1_all.deb to main/g/gnustep-back/gnustep-back-common_0.22.0-1_all.deb gnustep-back-dbg_0.22.0-1_amd64.deb to main/g/gnustep-back/gnustep-back-dbg_0.22.0-1_amd64.deb gnustep-back0.22-art_0.22.0-1_amd64.deb to main/g/gnustep-back/gnustep-back0.22-art_0.22.0-1_amd64.deb gnustep-back0.22-cairo_0.22.0-1_amd64.deb to main/g/gnustep-back/gnustep-back0.22-cairo_0.22.0-1_amd64.deb gnustep-back0.22_0.22.0-1_all.deb to main/g/gnustep-back/gnustep-back0.22_0.22.0-1_all.deb gnustep-back_0.22.0-1.debian.tar.gz to main/g/gnustep-back/gnustep-back_0.22.0-1.debian.tar.gz gnustep-back_0.22.0-1.dsc to main/g/gnustep-back/gnustep-back_0.22.0-1.dsc gnustep-back_0.22.0.orig.tar.gz to main/g/gnustep-back/gnustep-back_0.22.0.orig.tar.gz gnustep-gpbs_0.22.0-1_amd64.deb to main/g/gnustep-back/gnustep-gpbs_0.22.0-1_amd64.deb 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 663...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated gnustep-back 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: Mon, 28 May 2012 14:56:36 +0300 Source: gnustep-back Binary: gnustep-back0.22 gnustep-back0.22-art gnustep-back0.22-cairo gnustep-gpbs gnustep-back-common gnustep-back-dbg Architecture: source all amd64 Version: 0.22.0-1 Distribution: experimental Urgency: low Maintainer: Debian GNUstep maintainers Changed-By: Yavor Doganov Description: gnustep-back-common - GNUstep GUI Backend - common files gnustep-back-dbg - GNUstep GUI Backend - debugging symbols gnustep-back0.22 - GNUstep GUI Backend gnustep-back0.22-art - GNUstep GUI Backend (art) gnustep-back0.22-cairo - GNUstep GUI Backend (cairo) gnustep-gpbs - GNUstep PasteBoard server Closes: 663388 666334 Changes: gnustep-back (0.22.0-1) experimental; urgency=low . * New major upstream release. * debian/rules (v_gui): Bump to 0.22, which depends on -base 1.24 which in turn does not lead to the automatic creation of $HOME/GNUstep (Closes: #663388). Don't include /usr/share/quilt/quilt.make; remove patch/unpatch depedencies. Enable hardening. * debian/control.m4 (Build-Depends): Remove quilt. Add libxcursor-dev. (Depends, Suggests): Replace ttf-freefont with fonts-freefont-ttf. (Replaces, Breaks, Provides): Remove; no longer needed. (gnustep-back-dbg) : Set to libgnustep-gui0.22-dbg. (Standards-Version): Set to 3.9.3; no changes required. * debian/control: Regenerate. * debian/source/format: Switch to 3.0 (quilt) so that patches are always applied (Closes: #666334). * de
Bug#666334: marked as done (gnustep-back: FTBFS: build-arch doesn't apply patches)
Your message dated Fri, 01 Jun 2012 07:18:22 + with message-id and subject line Bug#666334: fixed in gnustep-back 0.22.0-1 has caused the Debian Bug report #666334, regarding gnustep-back: FTBFS: build-arch doesn't apply patches 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.) -- 666334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnustep-back Version: 0.20.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: > gcc-4.6 -shared -rdynamic -Wl,-z,defs -Wl,--as-needed -shared-libgcc > -fexceptions -o ./libgnustep-cairo-020.bundle/./libgnustep-cairo-020 > ./obj/libgnustep-cairo-020.obj/GSBackend.m.o ./gsc/obj/subproject.o > ./x11/obj/subproject.o ./cairo/obj/subproject.o -L/usr/local/lib > -L/usr/lib -lcairo -lfreetype -lXrender -lcairo -lX11 -lXft-lXmu > -lXt -lXext -lX11 -lGL -lgnustep-gui-lgnustep-base -lpthread -lobjc > -lm > ./cairo/obj/subproject.o: In function `-[CairoFontEnumerator > enumerateFontsAndFamilies]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:152: undefined > reference to `FcPatternCreate' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:153: undefined > reference to `FcObjectSetBuild' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:155: undefined > reference to `FcFontList' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:157: undefined > reference to `FcPatternDestroy' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:158: undefined > reference to `FcObjectSetDestroy' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:164: undefined > reference to `FcPatternGetString' > ./cairo/obj/subproject.o: In function `faFromFc': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:73: undefined > reference to `FcPatternGetInteger' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:74: undefined > reference to `FcPatternGetInteger' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:75: undefined > reference to `FcPatternGetString' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:79: undefined > reference to `FcPatternGetInteger' > ./cairo/obj/subproject.o: In function `-[CairoFontEnumerator > enumerateFontsAndFamilies]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:198: undefined > reference to `FcFontSetDestroy' > ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet > initWithFontconfigCharSet:]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:246: undefined > reference to `FcCharSetCopy' > ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet dealloc]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:259: undefined > reference to `FcCharSetDestroy' > ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet > characterIsMember:]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:270: undefined > reference to `FcCharSetHasChar' > ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet > longCharacterIsMember:]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:275: undefined > reference to `FcCharSetHasChar' > ./cairo/obj/subproject.o: In function `-[CairoFaceInfo > initWithfamilyName:weight:traits:pattern:]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:44: undefined > reference to `FcPatternReference' > ./cairo/obj/subproject.o: In function `-[CairoFaceInfo dealloc]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:59: undefined > reference to `FcPatternDestroy' > ./cairo/obj/subproject.o: In function `-[CairoFaceInfo fontFace]': > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:107: undefined > reference to `FcConfigSubstitute' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:108: undefined > reference to `FcDefaultSubstitute' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:109: undefined > reference to `FcFontMatch' > /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:112: undef
Bug#669494: marked as done (subversion: FTBFS: tests failed)
Your message dated Fri, 01 Jun 2012 07:19:42 +
with message-id
and subject line Bug#669494: fixed in subversion 1.6.17dfsg-3.1
has caused the Debian Bug report #669494,
regarding subversion: FTBFS: tests failed
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.)
--
669494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: subversion
Version: 1.6.17dfsg-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120419 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'
> cd ./subversion/bindings/swig/python; \
> python2.6
> /«PKGBUILDDIR»/subversion/bindings/swig/python/tests/run_all.py
> ..FF..
> ==
> FAIL: test_diff_dir_different_dirs
> (trac.versioncontrol.tests.svn_fs.SubversionRepositoryTestCase)
> --
> Traceback (most recent call last):
> File
> "/«PKGBUILDDIR»/subversion/bindings/swig/python/tests/trac/versioncontrol/tests/svn_fs.py",
> line 242, in test_diff_dir_different_dirs
> (Node.DIRECTORY, Changeset.ADD)), diffs.next())
> File
> "/«PKGBUILDDIR»/subversion/bindings/swig/python/tests/trac/versioncontrol/tests/svn_fs.py",
> line 202, in _cmp_diff
> self.assertEqual((new.path, new.rev), (got[1].path, got[1].rev))
> AssertionError: ('branches/v1x/dir1', 5) != ('branches/v1x/README.txt', 9)
>
> ==
> FAIL: test_diff_dir_different_revs
> (trac.versioncontrol.tests.svn_fs.SubversionRepositoryTestCase)
> --
> Traceback (most recent call last):
> File
> "/«PKGBUILDDIR»/subversion/bindings/swig/python/tests/trac/versioncontrol/tests/svn_fs.py",
> line 228, in test_diff_dir_different_revs
> (Node.DIRECTORY, Changeset.ADD)), diffs.next())
> File
> "/«PKGBUILDDIR»/subversion/bindings/swig/python/tests/trac/versioncontrol/tests/svn_fs.py",
> line 202, in _cmp_diff
> self.assertEqual((new.path, new.rev), (got[1].path, got[1].rev))
> AssertionError: ('trunk/dir1/dir2', 5) != ('trunk/README2.txt', 6)
>
> --
> Ran 106 tests in 13.460s
>
> FAILED (failures=2)
> make[2]: *** [check-swig-py] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/04/19/subversion_1.6.17dfsg-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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--- End Message ---
--- Begin Message ---
Source: subversion
Source-Version: 1.6.17dfsg-3.1
We believe that the bug you reported is fixed in the latest version of
subversion, which is due to be installed in the Debian FTP archive:
libapache2-svn_1.6.17dfsg-3.1_amd64.deb
to main/s/subversion/libapache2-svn_1.6.17dfsg-3.1_amd64.deb
libsvn-dev_1.6.17dfsg-3.1_amd64.deb
to main/s/subversion/libsvn-dev_1.6.17dfsg-3.1_amd64.deb
libsvn-doc_1.6.17dfsg-3.1_all.deb
to main/s/subversion/libsvn-doc_1.6.17dfsg-3.1_all.deb
libsvn-java_1.6.17dfsg-3.1_all.deb
to main/s/subversion/libsvn-java_1.6.17dfsg-3.1_all.deb
libsvn-jni_1.6.17dfsg-3.1_amd64.deb
to main/s/subversion/libsvn-jni_1.6.17dfsg-3.1_amd64.deb
libsvn-perl_1.6.17dfsg-3.1_amd64.deb
to main/s/subversion/libsvn-perl_1.6.17dfsg-3.1_amd64.deb
libsvn-ruby1.8_1.6.17dfsg-3.1_amd64.deb
to main/s/subversion/libsvn-ruby1.8_1.6.17dfsg-3.1_amd64.deb
libsvn-ruby_1.6.17dfsg-3.1_all.deb
to main/s/subversion/libsvn-ruby_1.6.17dfsg-3.1_all.deb
libsvn1_1.6.17dfsg-3.1_amd64.deb
to main/s/subversion/libsvn1_1.6.17dfsg-3.1_amd64.deb
python-subversion_1.6.17dfsg-3.1_amd64.deb
to main/s/subversion/python-subversion_1.6.17dfsg-3.1_amd64.deb
subversion-tools_1.6.17dfsg-3.1_all.deb
to main/s/subversion/subversion-tools_1.6.17dfsg-3.1_all.deb
subversion_1.6.17dfsg-3.1.diff.gz
to main/s/subversion/subversion_1.6.17dfsg-3.1.diff.gz
subversion_1.6.17dfsg-3.1.dsc
to main/s/subversion/subversion_1.6.17dfsg-3.
Bug#671991: marked as done (grass: FTBFS: mm.cc:259:32: error: declaration of 'void* operator new [](size_t)' has a different exception specifier)
Your message dated Fri, 01 Jun 2012 07:18:36 + with message-id and subject line Bug#671991: fixed in grass 6.4.2-1 has caused the Debian Bug report #671991, regarding grass: FTBFS: mm.cc:259:32: error: declaration of 'void* operator new [](size_t)' has a different exception specifier 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.) -- 671991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grass Version: 6.4.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > c++ -I/«PKGBUILDDIR»/dist.x86_64-pc-linux-gnu/include -g -O2 > -D_FILE_OFFSET_BITS=64 -DPACKAGE=\""grasslibs"\" > -I/«PKGBUILDDIR»/dist.x86_64-pc-linux-gnu/include -o > OBJ.x86_64-pc-linux-gnu/mm.o -c mm.cc > mm.cc: In function 'void* operator new [](size_t)': > mm.cc:259:32: error: declaration of 'void* operator new [](size_t)' has a > different exception specifier > In file included from mm.cc:29:0: > /«PKGBUILDDIR»/dist.x86_64-pc-linux-gnu/include/grass/iostream/mm.h:114:17: > error: from previous declaration 'void* operator new [](std::size_t) throw > (std::bad_alloc)' > mm.cc:310:30: error: declaration of 'void* operator new(size_t)' has a > different exception specifier > In file included from mm.cc:29:0: > /«PKGBUILDDIR»/dist.x86_64-pc-linux-gnu/include/grass/iostream/mm.h:113:17: > error: from previous declaration 'void* operator new(std::size_t) throw > (std::bad_alloc)' > mm.cc:362:32: error: declaration of 'void operator delete(void*)' has a > different exception specifier > In file included from mm.cc:29:0: > /«PKGBUILDDIR»/dist.x86_64-pc-linux-gnu/include/grass/iostream/mm.h:115:15: > error: from previous declaration 'void operator delete(void*) throw ()' > mm.cc:402:34: error: declaration of 'void operator delete [](void*)' has a > different exception specifier > In file included from mm.cc:29:0: > /«PKGBUILDDIR»/dist.x86_64-pc-linux-gnu/include/grass/iostream/mm.h:116:15: > error: from previous declaration 'void operator delete [](void*) throw ()' > make[4]: *** [OBJ.x86_64-pc-linux-gnu/mm.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/grass_6.4.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: grass Source-Version: 6.4.2-1 We believe that the bug you reported is fixed in the latest version of grass, which is due to be installed in the Debian FTP archive: grass-core_6.4.2-1_i386.deb to main/g/grass/grass-core_6.4.2-1_i386.deb grass-dev-doc_6.4.2-1_all.deb to main/g/grass/grass-dev-doc_6.4.2-1_all.deb grass-dev_6.4.2-1_i386.deb to main/g/grass/grass-dev_6.4.2-1_i386.deb grass-doc_6.4.2-1_all.deb to main/g/grass/grass-doc_6.4.2-1_all.deb grass-gui_6.4.2-1_i386.deb to main/g/grass/grass-gui_6.4.2-1_i386.deb grass_6.4.2-1.debian.tar.gz to main/g/grass/grass_6.4.2-1.debian.tar.gz grass_6.4.2-1.dsc to main/g/grass/grass_6.4.2-1.dsc grass_6.4.2-1_all.deb to main/g/grass/grass_6.4.2-1_all.deb grass_6.4.2.orig.tar.gz to main/g/grass/grass_6.4.2.orig.tar.gz 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 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francesco Paolo Lovergine (supplier of updated grass 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: Tue, 29 May 2012 17:23:07 +0200 Source: grass Binary: grass grass-core grass-gui grass-doc grass-dev-doc grass-dev Architecture: source all i386 Version: 6.4.2-1 Distribution: unstable Urgency: low Maintainer: Debian GIS Project Changed-By: Francesco Paolo Lovergine Description: grass - Geographic Resources Analysis Support System (GRASS GIS) grass-core
Processed: tagging 674391
Processing commands for cont...@bugs.debian.org: > tags 674391 - pending Bug #674391 [src:autofs] autofs: FTBFS: dpkg-buildpackage: error: dpkg-source -b autofs-5.0.6 gave error exit status 2 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 674391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674391 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#669246: marked as done (zfs-fuse: fails to install due to insserv rejecting the script header)
Your message dated Fri, 1 Jun 2012 15:25:15 +0800 with message-id and subject line has caused the Debian Bug report #669246, regarding zfs-fuse: fails to install due to insserv rejecting the script header 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.) -- 669246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zfs-fuse Version: 0.7.0-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install due to insserv rejecting the script header. Some notes are available from at http://wiki.debian.org/LSBInitScripts >From the attached log (scroll to the bottom...): Setting up zfs-fuse (0.7.0-6) ... invoke-rc.d: policy-rc.d denied execution of restart. insserv: Service fuse has to be enabled to start service zfs-fuse insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing zfs-fuse (--configure): subprocess installed post-installation script returned error exit status 1 This problem has just appeared without zfs-fuse being updated in the archive ... so probably the fuse dependency was indirectly satisfied before, but changes to other packages may have removed that indirect dependency inbetween. cheers, Andreas libguestfs0_1:1.16.18-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- I think this bug should be fixed in the latest version 0.7.0-7 -- Asias He --- End Message ---
Bug#664907: tennix: 664907: upstream patch
tags 664907 + fixed-upstream patch thanks It seems this is fixed in the upstream git repo by this commit: http://repo.or.cz/w/tennix.git/commitdiff/6144cb7626dfdc0820a0036af83a531e8e68bae6 I've tested build with this patch applied and it works, please check and apply it and or ask upstream to release a new version. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: tennix: 664907: upstream patch
Processing commands for cont...@bugs.debian.org:
> tags 664907 + fixed-upstream patch
Bug #664907 [src:tennix] tennix: FTBFS: network.c:189:28: error:
reinterpret_cast from type 'const Uint32* {aka const unsigned int*}' to type
'Uint32* {aka unsigned int*}' casts away qualifiers
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
664907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664907
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#675277: [Pkg-nagios-devel] Bug#675277: icinga-idoutils: fails to install, remove, and install again
On Fri, 01 Jun 2012, Alexander Wirt wrote: > tags 675277 moreinfo > thanks > > On Wed, 30 May 2012, Andreas Beckmann wrote: > > Hi, > > > Package: icinga-idoutils > > Version: 1.7.0-1 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > > > Hi, > > > > during a test with piuparts I noticed your package failed to install, > > remove (but not purge), and install again. > > Before the second installation the package is in config-files-remaining > > state. The configuration is remaining from the last version that was > > successfully configured - which is the same version that is going to be > > installed again. > > > > Like a plain failure on initial install this makes the package too buggy > > for a release, thus the severity. > I am really not sure if this is a bug. If you do the install again, dbconfig > asks you again for upgrading the database and if you hit yes the same update > is applied to the database. This of course fails. > > I added the dbconfig maintaner to Cc, Sean what do you think is this a bug > and how should it addressed? I did a little debugging in the morning (thanks to melissa) as it seems naming the files .sql did wrong things with the comparision of dbc. I fixed that in git and it should fix that problem. Alex -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672021: marked as done (libpqxx3: FTBFS: ../include/pqxx/util.hxx:412:5: error: 'to_string' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point
Your message dated Fri, 01 Jun 2012 07:33:43 + with message-id and subject line Bug#672021: fixed in libpqxx 4.0-1 has caused the Debian Bug report #672021, regarding libpqxx3: FTBFS: ../include/pqxx/util.hxx:412:5: error: 'to_string' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] 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.) -- 672021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpqxx3 Version: 3.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /bin/bash ../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ > -DHAVE_CONFIG_H -I../include -I../include -I/usr/include/postgresql -c > -o connection_base.lo connection_base.cxx > libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../include > -I../include -I/usr/include/postgresql -c connection_base.cxx -fPIC -DPIC -o > .libs/connection_base.o > In file included from ../include/pqxx/util:18:0, > from ../include/pqxx/except.hxx:27, > from ../include/pqxx/except:19, > from ../include/pqxx/result.hxx:31, > from ../include/pqxx/result:19, > from ../include/pqxx/binarystring.hxx:26, > from ../include/pqxx/binarystring:18, > from connection_base.cxx:46: > ../include/pqxx/util.hxx: In instantiation of 'std::string > pqxx::separated_list(const string&, ITER, ITER, ACCESS) [with ITER = > __gnu_cxx::__normal_iterator std::vector >; ACCESS = > pqxx::prepare::internal::get_sqltype; std::string = std::basic_string]': > connection_base.cxx:1018:35: required from here > ../include/pqxx/util.hxx:412:5: error: 'to_string' was not declared in this > scope, and no declarations were found by argument-dependent lookup at the > point of instantiation [-fpermissive] > In file included from ../include/pqxx/strconv:18:0, > from ../include/pqxx/result.hxx:32, > from ../include/pqxx/result:19, > from ../include/pqxx/binarystring.hxx:26, > from ../include/pqxx/binarystring:18, > from connection_base.cxx:46: > ../include/pqxx/strconv.hxx:239:22: note: 'std::string pqxx::to_string(const > char*)' declared here, later in the translation unit > In file included from ../include/pqxx/util:18:0, > from ../include/pqxx/except.hxx:27, > from ../include/pqxx/except:19, > from ../include/pqxx/result.hxx:31, > from ../include/pqxx/result:19, > from ../include/pqxx/binarystring.hxx:26, > from ../include/pqxx/binarystring:18, > from connection_base.cxx:46: > ../include/pqxx/util.hxx:416:7: error: 'to_string' was not declared in this > scope, and no declarations were found by argument-dependent lookup at the > point of instantiation [-fpermissive] > In file included from ../include/pqxx/strconv:18:0, > from ../include/pqxx/result.hxx:32, > from ../include/pqxx/result:19, > from ../include/pqxx/binarystring.hxx:26, > from ../include/pqxx/binarystring:18, > from connection_base.cxx:46: > ../include/pqxx/strconv.hxx:239:22: note: 'std::string pqxx::to_string(const > char*)' declared here, later in the translation unit > make[2]: *** [connection_base.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/libpqxx3_3.1-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: libpqxx Source-Version: 4.0-1 We believe that the bug you reported is fixed in the latest version of libpqxx, which is due to be installed in the Debian FTP archive: libpqxx-4.0_4.0-1_amd64.deb to main/libp/libpqxx/libpqxx-4.0_4.0-1_amd64.deb libpqxx4-dbg_4.0-1_amd64.deb to main/libp/libpqxx/libpqxx4-dbg_4.0-1_amd64.deb libpqxx4-dev_4.0-1_amd64.deb t
Processed: limit source to icinga, tagging 675277
Processing commands for cont...@bugs.debian.org: > #icinga (1.7.0-2) UNRELEASED; urgency=low > # > # * [c57ac90] Fix filenames for dbconfig-common sql files (Closes: #675277) > # > limit source icinga Limiting to bugs with field 'source' containing at least one of 'icinga' Limit currently set to 'source':'icinga' > tags 675277 + pending Bug #675277 [icinga-idoutils] icinga-idoutils: fails to install, remove, and install again Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 675277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675277 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#674728: #674728 chromium: FTBFS on armel and armhf
Hi,
shawn writes:
> Here is a working patch against current sid version. (for at least
> armel)
>
> It won't cleanly "git am" against git, but if you read it, it is trivial
> to resolve (but tedious)
> however, I do not know how to check against git anyways, as that debian
> directory doesn't seem to be capable of building the sid source package,
> and i don't know where and what version of source i should use against
> it.
I just tested the binary you built. It prints
[28996:28996:383359135708:ERROR:data_pack.cc(133)] Entry #3 in data pack points
off end of file. Was the file corrupted?
[28996:28996:383359136274:FATAL:resource_bundle_posix.cc(56)] Check failed:
resources_data_. failed to load chrome.pak
but then sleeps forever. gdb shows
#0 0x40b414fc in recvmsg () at ../sysdeps/unix/syscall-template.S:82
#1 0x2b0a14b4 in UnixDomainSocket::RecvMsg (fd=11, buf=,
length=, fds=0xbe83b67c) at
content/common/unix_domain_socket_posix.cc:69
#2 0x2bf1df9c in ZygoteHost::Init (this=0x40024eec, sandbox_cmd=...) at
content/browser/zygote_host_linux.cc:181
#3 0x2be18038 in SetupSandbox (parsed_command_line=...) at
content/browser/browser_main_loop.cc:97
#4 content::BrowserMainLoop::EarlyInitialization (this=0x2d3516b0) at
content/browser/browser_main_loop.cc:256
#5 0x2be177c8 in BrowserMain (parameters=...) at
content/browser/browser_main.cc:54
#6 0x2ab2ef9c in RunNamedProcessTypeMain (delegate=,
main_function_params=..., process_type=...) at content/app/content_main.cc:264
#7 content::ContentMain (argc=28992, argv=0xbe83c234, delegate=0xbe83c0b4) at
content/app/content_main.cc:457
#8 0x2a1bb974 in ChromeMain (argc=2, argv=0xbe83c234) at
chrome/app/chrome_main.cc:32
#9 0x2a1baba8 in main (argc=, argv=) at
chrome/app/chrome_exe_main_gtk.cc:18
This is exactly the same behavior I saw with 16.0.912.77~r118311-1:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660187
I can't use strace directly since there is some suid helper:
Failed to move to new PID namespace: Operation not permitted
If I replace chromium-sandbox with a wrapper shell script then I can see
29492 execve("/usr/lib/chromium/chromium", ["/usr/lib/chromium/chromium",
"--type=zygote"], [/* 37 vars */]) = 0
29492 brk(0)= 0x2d344000
29492 uname({sys="Linux", node="mv78100", ...}) = 0
...
29492 stat64("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
29492 stat64("/home/lindi", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
29492 stat64("/home/lindi/.pki", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
29492 stat64("/home/lindi/.pki/nssdb", {st_mode=S_IFDIR|0700, st_size=4096,
...}) = 0
29492 statfs64("/home/lindi/.pki/nssdb", 88, {f_type="NFS_SUPER_MAGIC",
f_bsize=4096, f_blocks=69946375, f_bfree=17608227, f_bavail=14055152,
f_files=0, f_ffree=0, f_fsid={0, 0}, f_namelen=255, f_frsize=4096}) = 0
29492 uname({sys="Linux", node="mv78100", ...}) = 0
29492 readlink("/proc/self/exe", "/usr/lib/chromium/chromium", 4096) = 26
29492 open("/usr/lib/chromium/chrome.pak", O_RDONLY|O_LARGEFILE) = 4
29492 fstat64(4, {st_mode=S_IFREG|0644, st_size=3484478, ...}) = 0
29492 mmap2(NULL, 3484478, PROT_READ, MAP_SHARED, 4, 0) = 0x4216
29492 gettid() = 29492
29492 clock_gettime(CLOCK_MONOTONIC, {384255, 54286444}) = 0
29492 write(2, "[29492:29492:384255054286:ERROR:data_pack.cc(133)] Entry #3 in
data pack points off end of file. Was the file corrupted?\n", 121) = 121
29492 munmap(0x4216, 3484478) = 0
29492 close(4) = 0
29492 gettid() = 29492
29492 clock_gettime(CLOCK_MONOTONIC, {384255, 56244162}) = 0
29492 write(2, "[29492:29492:384255056244:FATAL:resource_bundle_posix.cc(56)]
Check failed: resources_data_. failed to load chrome.pak\n", 119) = 119
29492 open("/proc/self/status", O_RDONLY|O_LARGEFILE) = 4
29492 read(4, "Name:\tchromium\nState:\tR
(running)\nTgid:\t29492\nPid:\t29492\nPPid:\t29490\nTracerPid:\t29490\nUid:\t1001\t1001\t1001\t1001\nGid:\t1001\t1001\t1001\t1001\nFDSize:\t32\nGroups:\t1001
\nVmPeak:\t 90168 kB\nVmSize:\t 86764 kB\nVmLck:\t 0 kB\nVmHWM:\t
8672 kB\nVmRSS:\t8668 kB\nVmData:\t 444 kB\nVmStk:\t 88
kB\nVmExe:\t 51300 kB\nVmLib:\t 31696 kB\nVmPTE:\t 64
kB\nThreads:\t1\nSigQ:\t2/16382\nSigPnd:\t\nShdPnd:\t\nSigBlk:\t\nSigIgn:\t1000\nSigCgt:\t00018000\nCapInh:\t\nCapPrm:\t\nCapEff:\t\nCapBnd:\tfeff\nvoluntary_ctxt_switches:\t3301\nnonvoluntary_ctxt_switches:\t9\n",
1024) = 664
29492 close(4) = 0
29492 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
29492 tgkill(29492, 29492, SIGABRT) = 0
29492 --- SIGABRT (Aborted) @ 0 (0) ---
29492 +++ killed by SIGABRT +++
$ chromium --no-sandbox
Xlib: extension "RANDR" missing on display ":5".
[29624:29629:384546534600:ERROR:bus.cc(261)] Failed to connect to the b
Bug#671948: marked as done (atlas-cpp: FTBFS: symbols errors)
Your message dated Fri, 01 Jun 2012 08:47:53 +
with message-id
and subject line Bug#671948: fixed in atlas-cpp 0.6.2-3
has caused the Debian Bug report #671948,
regarding atlas-cpp: FTBFS: symbols errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
671948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atlas-cpp
Version: 0.6.2-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 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»'
> set -e; \
> for pkg in libatlas-cpp-0.6-1; do \
> dh_strip -p${pkg} --dbg-package=${pkg}-dbg; \
> done
> dh_strip -s --remaining-packages
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>dh_makeshlibs
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
> diff output below
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols
> file: see diff output below
> dpkg-gensymbols: warning: debian/libatlas-cpp-0.6-1/DEBIAN/symbols doesn't
> match completely debian/libatlas-cpp-0.6-1.symbols
> --- debian/libatlas-cpp-0.6-1.symbols (libatlas-cpp-0.6-1_0.6.2-2_amd64)
> +++ dpkg-gensymbolsCxXA5V 2012-05-08 09:02:27.283852263 +
> @@ -43,6 +43,7 @@
> _ZN5Atlas9filterbufD1Ev@Base 0.6.2
> _ZN5Atlas9filterbufD2Ev@Base 0.6.2
> _ZNK5Atlas9Exception4whatEv@Base 0.6.2
> + _ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base 0.6.2-2
> _ZTIN5Atlas5CodecE@Base 0.6.2
> _ZTIN5Atlas6BridgeE@Base 0.6.2
> _ZTIN5Atlas6FilterE@Base 0.6.2
> @@ -107,7 +108,7 @@
> _ZN5Atlas6Codecs4Bach4pollEb@Base 0.6.2
> _ZN5Atlas6Codecs4Bach6mapEndEv@Base 0.6.2
> _ZN5Atlas6Codecs4Bach7listEndEv@Base 0.6.2
> - _ZN5Atlas6Codecs4Bach9parseDataEc@Base 0.6.2
> +#MISSING: 0.6.2-2# _ZN5Atlas6Codecs4Bach9parseDataEc@Base 0.6.2
> _ZN5Atlas6Codecs4Bach9streamEndEv@Base 0.6.2
> _ZN5Atlas6Codecs4Bach9writeLineERKSsbb@Base 0.6.2
> _ZN5Atlas6Codecs4BachC1ERSdRNS_6BridgeE@Base 0.6.2
> @@ -130,7 +131,7 @@
> _ZN5Atlas6Codecs6Packed4pollEb@Base 0.6.2
> _ZN5Atlas6Codecs6Packed6mapEndEv@Base 0.6.2
> _ZN5Atlas6Codecs6Packed7listEndEv@Base 0.6.2
> - _ZN5Atlas6Codecs6Packed8parseMapEc@Base 0.6.2
> +#MISSING: 0.6.2-2# _ZN5Atlas6Codecs6Packed8parseMapEc@Base 0.6.2
> _ZN5Atlas6Codecs6Packed9streamEndEv@Base 0.6.2
> _ZN5Atlas6Codecs6PackedC1ERSdRNS_6BridgeE@Base 0.6.2
> _ZN5Atlas6Codecs6PackedC2ERSdRNS_6BridgeE@Base 0.6.2
> @@ -150,15 +151,22 @@
> (regex)_ZNSt11_Deque_baseISsSaISsEE17_M_initialize_mapE[mj]@Base 0.6.2
> _ZNSt11_Deque_baseISsSaISsEED1Ev@Base 0.6.2
> _ZNSt11_Deque_baseISsSaISsEED2Ev@Base 0.6.2
> -
> (regex)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE17_M_reallocate_mapE[mj]b@Base
> 0.6.2
> -
> (regex)_ZNSt5dequeIN5Atlas6Codecs4Bach5StateESaIS3_EE17_M_reallocate_mapE[mj]b@Base
> 0.6.2
> -
> (regex)_ZNSt5dequeIN5Atlas6Codecs6Packed5StateESaIS3_EE17_M_reallocate_mapE[mj]b@Base
> 0.6.2
> + _ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE15_M_pop_back_auxEv@Base
> 0.6.2-2
> + _ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE16_M_push_back_auxERKS3_@Base
> 0.6.2-2
> +#MISSING: 0.6.2-2#
> (regex)_ZNSt5dequeIN5Atlas6Codecs3XML5StateESaIS3_EE17_M_reallocate_mapE[mj]b@Base
> 0.6.2
> + _ZNSt5dequeIN5Atlas6Codecs4Bach5StateESaIS3_EE15_M_pop_back_auxEv@Base
> 0.6.2-2
> + _ZNSt5dequeIN5Atlas6Codecs4Bach5StateESaIS3_EE16_M_push_back_auxERKS3_@Base
> 0.6.2-2
> +#MISSING: 0.6.2-2#
> (regex)_ZNSt5dequeIN5Atlas6Codecs4Bach5StateESaIS3_EE17_M_reallocate_mapE[mj]b@Base
> 0.6.2
> + _ZNSt5dequeIN5Atlas6Codecs6Packed5StateESaIS3_EE15_M_pop_back_auxEv@Base
> 0.6.2-2
> +
> _ZNSt5dequeIN5Atlas6Codecs6Packed5StateESaIS3_EE16_M_push_back_auxERKS3_@Base
> 0.6.2-2
> +#MISSING: 0.6.2-2#
> (regex)_ZNSt5dequeIN5Atlas6Codecs6Packed5StateESaIS3_EE17_M_reallocate_mapE[mj]b@Base
> 0.6.2
> _ZNSt5dequeISsSaISsEE16_M_push_back_auxERKSs@Base 0.6.2
> - (regex)_ZNSt5dequeISsSaISsEE17_M_reallocate_mapE[mj]b@Base 0.6.2
> -
> (optional)_ZNSt5dequeISsSaISsEE19_M_destroy_data_auxESt15_Deque_iteratorISsRSsPSsES5_@Base
> 0.6.2
> +#MISSING: 0.6.2-2#
> (regex)_ZNSt5dequeISsSaISsEE17_M_reallocate_mapE[mj]b@Base 0.6.2
> +#MISSING: 0.6.2-2#
> (optional)_ZNSt5dequeISsSaISsEE19_M_destroy_data_auxESt15_Deque_iteratorISsRSsPSsES5_@Base
> 0.6.2
> _ZNSt5dequeISsSaISsEED1Ev@Base 0.6.2
> _ZNSt5dequeISsSaISsEED2Ev@Base 0.6.2
> -
> _ZSt6__findIN9__gnu_cxx17__norma
Bug#667274: marked as done (mercator: ftbfs with GCC-4.7)
Your message dated Fri, 01 Jun 2012 08:57:24 + with message-id and subject line Bug#667274: fixed in mercator 0.3.0-2 has caused the Debian Bug report #667274, regarding mercator: ftbfs with GCC-4.7 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.) -- 667274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mercator Version: 0.3.0-1 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. dpkg-gensymbols returned exit code 1 The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/mercator_0.3.0-1_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] @@ -456,6 +467,7 @@ _ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE10_M_insert_EPKSt18_Rb_tree_node_baseSE_RKS5_@Base 0.3.0 _ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE16_M_insert_uniqueERKS5_@Base 0.3.0 _ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE17_M_insert_unique_ESt23_Rb_tree_const_iteratorIS5_ERKS5_@Base 0.3.0 + _ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE4findERS1_@Base 0.3.0-1 _ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base 0.3.0 _ZNSt8_Rb_treeIiSt4pairIKiSt3mapIiN8Mercator5PlantESt4lessIiESaIS0_IS1_S4_St10_Select1stISA_ES6_SaISA_EE10_M_insert_EPKSt18_Rb_tree_node_baseSH_RKSA_@Base 0.3.0 _ZNSt8_Rb_treeIiSt4pairIKiSt3mapIiN8Mercator5PlantESt4lessIiESaIS0_IS1_S4_St10_Select1stISA_ES6_SaISA_EE16_M_insert_uniqueERKSA_@Base 0.3.0 @@ -469,14 +481,15 @@ _ZNSt8_Rb_treeIiSt4pairIKiSt3mapIiPN8Mercator7SegmentESt4lessIiESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE16_M_insert_uniqueERKSB_@Base 0.3.0 _ZNSt8_Rb_treeIiSt4pairIKiSt3mapIiPN8Mercator7SegmentESt4lessIiESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE17_M_insert_unique_ESt23_Rb_tree_const_iteratorISB_ERKSB_@Base 0.3.0 _ZNSt8_Rb_treeIiSt4pairIKiSt3mapIiPN8Mercator7SegmentESt4lessIiESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 0.3.0 - (regex)_ZSt11__push_heapIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_[il]S3_NS2_7EdgeAtYEEvT_T0_SB_T1_T2_@Base 0.3.0 +#MISSING: 0.3.0-1# (regex)_ZSt11__push_heapIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_[il]S3_NS2_7EdgeAtYEEvT_T0_SB_T1_T2_@Base 0.3.0 (regex)_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_[il]S3_NS2_7EdgeAtYEEvT_T0_SB_T1_T2_@Base 0.3.0 _ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS2_7EdgeAtYEEvT_SA_SA_T0_@Base 0.3.0 _ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS2_7EdgeAtYEEvT_SA_T0_@Base 0.3.0 (regex)_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_[il]NS2_7EdgeAtYEEvT_SA_T0_T1_@Base 0.3.0 - _ZSt19__move_median_firstIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS2_7EdgeAtYEEvT_SA_SA_T0_@Base 0.3.0 +#MISSING: 0.3.0-1# _ZSt19__move_median_firstIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS2_7EdgeAtYEEvT_SA_SA_T0_@Base 0.3.0 _ZSt21__unguarded_partitionIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_S3_NS2_7EdgeAtYEET_SA_SA_RKT0_T1_@Base 0.3.0 _ZSt25__unguarded_linear_insertIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS2_7EdgeAtYEEvT_T0_@Base 0.3.0 + _ZSt9sort_heapIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS2_7EdgeAtYEEvT_SA_T0_@Base 0.3.0-1 _ZTI18ZeroSpiralOrdering@Base 0.3.0 _ZTIN8Mercator10AreaShaderE@Base 0.3.0 _ZTIN8Mercator10BandShaderE@Base 0.3.0 dh_makeshlibs: dpkg-gensymbols -plibmercator-0.3-1 -Idebian/libmercator-0.3-1.symbols -Pdebian/libmercator-0.3-1 -edebian/libmercator-0.3-1/usr/lib/x86_64-l
Bug#675304: reassigning
reassign 675304 amarok thanks I am much clearer about this now. This bug is clearly a duplicate of #672207. That said I think we could have instead of changing " language= /usr/share/mysql/english" to "lc-messages-dir = /usr/share/mysql" changed it to " loose-lc-messages-dir = /usr/share/mysql/ # This option is deprecated and will be removed in a later version language= /usr/share/mysql/english " This would have maintained backwards compatibility and removed the need for the Breaks clauses. However it is also clear that an application with an embedded MySQL server, like amarok, should avoiding making use of system wide MySQL config files to insulate itself not just to changes in the Debian packaging but also changes that the DBA makes to the MySQL configuration. amarok seems to have done this now. I am trying to draw wider lessons from this, but for now I am reassigning this report to amarok, with the expectation that one of more of the following will happen: 1.) The bug will be merged into #672207 effectively closing it. 2.) That it will be reassigned to a request to have amarok aged so that the user can upgrade his amarok. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassigning
Processing commands for cont...@bugs.debian.org: > reassign 675304 amarok Bug #675304 [mysql-common] upgrade from 5.1.61-3 to 5.5.23+dfsg-2 broke amarok Bug reassigned from package 'mysql-common' to 'amarok'. No longer marked as found in versions mysql-5.5/5.5.23+dfsg-2. Ignoring request to alter fixed versions of bug #675304 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 675304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675304 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#675277: marked as done (icinga-idoutils: fails to install, remove, and install again)
Your message dated Fri, 01 Jun 2012 09:19:38 + with message-id and subject line Bug#675277: fixed in icinga 1.7.0-2 has caused the Debian Bug report #675277, regarding icinga-idoutils: fails to install, remove, and install again 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.) -- 675277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: icinga-idoutils Version: 1.7.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install, remove (but not purge), and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is the same version that is going to be installed again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package icinga-idoutils. (Reading database ... 9007 files and directories currently installed.) Unpacking icinga-idoutils (from .../icinga-idoutils_1.7.0-1_amd64.deb) ... Setting up icinga-idoutils (1.7.0-1) ... dbconfig-common: writing config to /etc/dbconfig-common/icinga-idoutils.conf creating database backup in /var/cache/dbconfig-common/backups/icinga-idoutils_1.7.0-1.pgsql. applying upgrade sql for 1.7.0-1 -> 1.7.0-1.sql. error encountered processing /usr/share/dbconfig-common/data/icinga-idoutils/upgrade/pgsql/1.7.0-1.sql: ERROR: relation "statehist_state_idx" already exists dbconfig-common: icinga-idoutils configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing icinga-idoutils (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: icinga-idoutils cheers, Andreas icinga-idoutils_1.7.0-1.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: icinga Source-Version: 1.7.0-2 We believe that the bug you reported is fixed in the latest version of icinga, which is due to be installed in the Debian FTP archive: icinga-cgi_1.7.0-2_amd64.deb to main/i/icinga/icinga-cgi_1.7.0-2_amd64.deb icinga-common_1.7.0-2_all.deb to main/i/icinga/icinga-common_1.7.0-2_all.deb icinga-core_1.7.0-2_amd64.deb to main/i/icinga/icinga-core_1.7.0-2_amd64.deb icinga-dbg_1.7.0-2_amd64.deb to main/i/icinga/icinga-dbg_1.7.0-2_amd64.deb icinga-doc_1.7.0-2_all.deb to main/i/icinga/icinga-doc_1.7.0-2_all.deb icinga-idoutils_1.7.0-2_amd64.deb to main/i/icinga/icinga-idoutils_1.7.0-2_amd64.deb icinga_1.7.0-2.diff.gz to main/i/icinga/icinga_1.7.0-2.diff.gz icinga_1.7.0-2.dsc to main/i/icinga/icinga_1.7.0-2.dsc icinga_1.7.0-2_amd64.deb to main/i/icinga/icinga_1.7.0-2_amd64.deb 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 675...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Wirt (supplier of updated icinga 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: Fri, 01 Jun 2012 10:12:50 +0200 Source: icinga Binary: icinga-common icinga-cgi icinga-idoutils icinga icinga-core icinga-doc icinga-dbg Architecture: source amd64 all Version: 1.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Nagios Maintainer Group Changed-By: Alexander Wirt Description: icinga - host and network monitoring system - metapackage icinga-cgi - host and network monitoring system - CGI scripts icinga-common - host and network monitoring system - support files icinga-core - host and network monitoring system - core files icinga-dbg - host and network monitoring system - debug files icinga-doc - host and network monitoring system - documentation icinga-idoutils - host and network monitoring system - icinga-dataobjects support Closes: 671908 675041 675043 675046 675277 Changes: icinga (1.7.0-2) unstable; urgency=medium . * [57cc621] Fix example path for idoutils broker * [c27a750] Depend on dpkg >= 1.16.1 for s-s-d --status (Closes: #675041)
Bug#670122: libsdl1.2-dev – Missing dependencies on libcaca-dev and libpulse-dev
severity 670122 normal thanks On 17.05.2012 13:19, Sebastian Dröge wrote: > On Sa, 2012-05-05 at 17:56 +0200, Julien Cristau wrote: >> On Mon, Apr 23, 2012 at 09:45:01 +0200, Sebastian Dröge wrote: >> >>> Package: libsdl1.2-dev >>> Severity: serious >>> >>> Hi, >>> libsdl1.2-dev must depend on libcaca-dev and libpulse-dev as >>> 'sdl-config --libs --static-libs' adds both libraries to the >>> linker flags. >>> Also all remaining other libraries that might be missing from >>> the -dev package dependencies from that list must be added. >>> >> Which debian packages use --static-libs, and why? > gst-plugins-bad0.10 uses this in the configure check. Check > m4/gst-sdl.m4 for the configure check used there. I hope it doesn't actually use the static library in which case the check can just be fixed. I'm considering adding the -dev packages required for static linking as Recommends. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670633: invasive NMUs are not appropriate
It is not appropriate to use NMUs to change packages in ways that are unrelated to the bugs you are fixing, please refrain from doing that. http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#670122: libsdl1.2-dev – Missing dependencies on libcaca-dev and libpulse-dev
Processing commands for cont...@bugs.debian.org: > severity 670122 normal Bug #670122 [libsdl1.2-dev] libsdl1.2-dev â Missing dependencies on libcaca-dev and libpulse-dev Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 670122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670122 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#675373: virtualbox: segfault in libQtCore.so.4.8.1
severity 675373 normal tags 675373 moreinfo thanks On 31.05.2012 18:48, Damien Couroussé wrote: > Package: virtualbox > Version: 4.1.14-dfsg-1 > Severity: grave > Justification: renders package unusable > > > > hello, > > virtualbox segfaults. dmesg displays the following: > [33391.906793] VirtualBox[25243]: segfault at 0 ip 7fa49a5cf43a sp > 7fffc3ee1140 error 4 in libQtCore.so.4.8.1[7fa49a54e000+2cc000] Unfortunately I don't have a crystal ball that lets me see the cause of all segfaults. So at the very least you have to describe in which situation VirtualBox crashed and how to reproduce it. A stacktrace of the crash would also be very helpful. Felix -- 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#675373: virtualbox: segfault in libQtCore.so.4.8.1
Processing commands for cont...@bugs.debian.org: > severity 675373 normal Bug #675373 [virtualbox] virtualbox: segfault in libQtCore.so.4.8.1 Severity set to 'normal' from 'grave' > tags 675373 moreinfo Bug #675373 [virtualbox] virtualbox: segfault in libQtCore.so.4.8.1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 675373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675373 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#675457: FTBFS: `make check' fails on test_stack on i386
Package: libatomic-ops-dev
Version: 7.3~alpha1+git20111031-1
Justification: fails to build from source
Severity: serious
Tags: patch
Upstream commit https://github.com/ivmai/libatomic_ops/commit/30cea1b
fixes AO_compare_double_and_swap_double_full() which is broken on
gcc/x86 and causes `make check' to fail (tested on a sid x86 chroot).
--
Emanuele
diff --git c/src/atomic_ops/sysdeps/gcc/x86.h i/src/atomic_ops/sysdeps/gcc/x86.h
index b304dd0..e49f057 100644
--- c/src/atomic_ops/sysdeps/gcc/x86.h
+++ i/src/atomic_ops/sysdeps/gcc/x86.h
@@ -161,13 +161,16 @@ AO_compare_double_and_swap_double_full(volatile AO_double_t *addr,
/* If PIC is turned on, we can't use %ebx as it is reserved for the
GOT pointer. We can save and restore %ebx because GCC won't be
using it for anything else (such as any of the m operands) */
- __asm__ __volatile__("pushl %%ebx;" /* save ebx used for PIC GOT ptr */
- "movl %6,%%ebx;" /* move new_val2 to %ebx */
+ /* We use %edi (for new_val1) instead of a memory operand and swap*/
+ /* instruction instead of push/pop because some GCC releases have */
+ /* a bug in processing memory operands (if address base is %esp) in */
+ /* the inline assembly after push.*/
+ __asm__ __volatile__("xchg %%ebx,%6;" /* swap GOT ptr and new_val1 */
"lock; cmpxchg8b %0; setz %1;"
- "pop %%ebx;" /* restore %ebx */
+ "xchg %%ebx,%6;" /* restore ebx and edi */
: "=m"(*addr), "=a"(result)
: "m"(*addr), "d" (old_val2), "a" (old_val1),
- "c" (new_val2), "m" (new_val1) : "memory");
+ "c" (new_val2), "D" (new_val1) : "memory");
#else
/* We can't just do the same thing in non-PIC mode, because GCC
* might be using %ebx as the memory operand. We could have ifdef'd
Bug#670633: invasive NMUs are not appropriate
On Fri, Jun 1, 2012 at 5:35 PM, Paul Wise wrote: > It is not appropriate to use NMUs to change packages in ways that are > unrelated to the bugs you are fixing, please refrain from doing that. > > http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-guidelines > I would like to repeat again that if you are the maintainer and you think it's not appropriate, then I'll do what you wish. Of course I will do measurement for every package about what are possibly acceptable and what are not, the situation varies from one package to another. But if you are not the maintainer, please don't just jump in and say "foo is not appropriate nor bar", which just wastes your time on working more stuff that are in need of your help. I would like to thank you for your contributions to other parts of Debian and they are really splendid work, but I feel not that thankful on this particular topic. Everyone has his own opinions on other people's NMUing their packages, some of them think NMU is generally bad, while some of them just place their name in the LowNMU list. But people aren't machine, which sometimes hold a boolen value regarding something. I agree that appropriate NMU notification and reasonable delay is very well needed, and at some degree it's even better to tell them this NMU is not for invading (reminds me about modifying the mail template of nmudiff), but I sincerely disagree that following the practice in devref is a reason for you to jump in and bugging people from time to time, just like pushing them as Policy. In the end, they are not Policy, but only "reference", which is telling people they are proven to be safe and sometimes be easy to do when you don't know how. Whether an NMU is welcomed is up to the maintainer's choice, but not a random person who holds his own rules and saying please read whatever section in devref as policy. For some of my packages, I do think that NMU changes too much is bad, but NMUing important bugs (like security) when I am not able to react quick enough is highly appreciated; for some others that I maintain, I'm sincerely feeling grateful when someone is NMUing them and wish they can incorporate some changes that I've committed but not uploaded due to whatever reason. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661492: marked as done (python-quantumclient: removal of python-quantumclient makes files disappear from quantum-client)
Your message dated Fri, 1 Jun 2012 12:15:34 +0200
with message-id <20120601101534.ge22...@sileht.net>
and subject line Close
has caused the Debian Bug report #661492,
regarding python-quantumclient: removal of python-quantumclient makes files
disappear from quantum-client
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.)
--
661492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-quantumclient
Version: 2012.1~e3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and EDOS tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.
The installation sequence to reproduce this problem is
apt-get install quantum-client
# (1)
apt-get install python-quantumclient
apt-get remove python-quantumclient
# (2)
The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:
/usr/{share/pyshared,lib/python2.?/dist-packages}/quantum/client/{__init__,cli,cli_lib}.py
This is a serious bug violating policy 7.6, see
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
http://www.debian.org/doc/debian-policy/footnotes.html#f53
The python-quantumclient package has the following relationships with
quantum-client:
Conflicts: n/a
Breaks:n/a
Replaces: quantum-client
>From the attached log (scroll to the bottom...):
0m23.0s ERROR: FAIL: After purging files have disappeared:
/usr/bin/quantum owned by: python-quantumclient
/usr/lib/python2.6/dist-packages/quantum/client/__init__.pyowned by:
python-quantumclient
/usr/lib/python2.6/dist-packages/quantum/client/cli.py owned by:
python-quantumclient
/usr/lib/python2.6/dist-packages/quantum/client/cli_lib.py owned by:
python-quantumclient
/usr/lib/python2.7/dist-packages/quantum/client/__init__.pyowned by:
python-quantumclient
/usr/lib/python2.7/dist-packages/quantum/client/__init__.pyc not owned
/usr/lib/python2.7/dist-packages/quantum/client/cli.py owned by:
python-quantumclient
/usr/lib/python2.7/dist-packages/quantum/client/cli.pycnot owned
/usr/lib/python2.7/dist-packages/quantum/client/cli_lib.py owned by:
python-quantumclient
/usr/lib/python2.7/dist-packages/quantum/client/cli_lib.pycnot owned
/usr/share/pyshared/quantum/client/__init__.py owned by:
python-quantumclient
/usr/share/pyshared/quantum/client/cli.py owned by: python-quantumclient
/usr/share/pyshared/quantum/client/cli_lib.py owned by: python-quantumclient
0m23.0s ERROR: FAIL: After purging files have been modified:
/var/lib/dpkg/info/quantum-client.list not owned
cheers,
Andreas
REPL_quantum-client_python-quantumclient.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Reason in previous message
Fixed are now in testing
--
Mehdi Abaakouk
sil...@sileht.net
signature.asc
Description: Digital signature
--- End Message ---
Processed (with 1 errors): merge 675457 632604
Processing commands for cont...@bugs.debian.org:
> merge 675457 632604
Bug #675457 [libatomic-ops-dev] FTBFS: `make check' fails on test_stack on i386
Unable to merge bugs because:
package of #632604 is 'src:libatomic-ops' not 'libatomic-ops-dev'
Failed to merge 675457: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x24e9068)',
'requester', 'Emanuele Aina ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'<1338548772.29753.8.ca...@autarpio.lan>', 'request_subject', ...) called at
/usr/lib/debbugs/service line 872
eval {...} called at /usr/lib/debbugs/service line 871
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
632604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632604
675457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675457
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#674942: ruby blocks buildd for a day (or more)
tags 674942 + patch thanks Uhhh I changed my mind. My patch could still be used as an interim fix (enforce a 2h time limit on the test suite with SIGKILL), then maybe clone+downgrade this to try to work out what causes the slower build times... Regards, -- Steven Chamberlain ste...@pyro.eu.org -- 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#674942: ruby blocks buildd for a day (or more)
Processing commands for cont...@bugs.debian.org: > tags 674942 + patch Bug #674942 [ruby1.8] ruby blocks buildd for a day (or more) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 674942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674942 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: merge 675457 632604
Processing commands for cont...@bugs.debian.org: > reassign 675457 src:libatomic-ops Bug #675457 [libatomic-ops-dev] FTBFS: `make check' fails on test_stack on i386 Bug reassigned from package 'libatomic-ops-dev' to 'src:libatomic-ops'. No longer marked as found in versions libatomic-ops/7.3~alpha1+git20111031-1. Ignoring request to alter fixed versions of bug #675457 to the same values previously set > merge 675457 632604 Bug #675457 [src:libatomic-ops] FTBFS: `make check' fails on test_stack on i386 Bug #675457 [src:libatomic-ops] FTBFS: `make check' fails on test_stack on i386 Marked as found in versions libatomic-ops/7.2~alpha5+cvs20101124-1. Added tag(s) unreproducible. Bug #632604 [src:libatomic-ops] libatomic-ops: FTBFS on i386 Added tag(s) patch. Merged 632604 675457 > thanks Stopping processing here. Please contact me if you need assistance. -- 632604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632604 675457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675457 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#675304: [debian-mysql] Bug#675304: reassigning
On Fri, Jun 1, 2012 at 11:17 AM, Nicholas Bamber wrote: > However it is also clear that an application with an embedded MySQL server, > like amarok, should avoiding making use of system wide MySQL config files to > insulate itself not just to changes in the Debian packaging but also > changes that the DBA makes to the MySQL configuration. amarok seems to have > done this now. Sure, but why was it doing this? Is it the default behaviour of the embedded MySQL server? And just wondering: why is Amarok using MySQL instead of something like sqlite? -- Olaf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674391: autofs: diff for NMU version 5.0.6-1.1
Hi Dmitrijs, > First of all thank you for picking up the maintenance of this package. > It is non-trivial. :) > > I'd like to thank you for your care for the 'autofs' package > > but please excuse me for expressing my non-appreciation of your NMU. > > I have cancelled it due to bug that Jakub Wilk expressed. Thank you for this. You can read more about conflict with autotools-dev in CAVEATS section of dh-autoreconf(7). > > Although perhaps not fast enough we're working on 'autofs' - we have a > > team of three and a different fix to the problem is already committed > > to repository. > > The changelog entry says: > " * declare myself as Maintainer (adopting package)" > > And the control says, that there is one maintainer & one uploader. > > Please, either change the maintainer to a team, or list all people on > the team. > > Please, set Vcs-* fields as per: > http://www.debian.org/doc/manuals/developers-reference/best-pkging-practic > es.html#bpp-vcs You're right. All the changes you're mentioned are pending. The team has formed after the package was sponsored so I was just trying to explain the current situation. Nevertheless for one or three maintainers NMU approach would still be invasive without first contacting the person(s) responsible. > If the fix has been committed to Vcs-*, you should set the 'pending' tag > on the bug. Normally I would agree but usually I'm trying to consider the fact that looking for sponsor may take weeks or even months in which case 'pending' may not be very useful. Sometimes I set 'pending' when package is ready and waiting for upload. Also one would expect that new 'serious' will hardly be unnoticed or ignored. If you have doubts, gentle reminder (accompanied with patch) will be always appreciated. :) > Correct Vcs-* headers, together with the pending tag would allowed me to > find the patches I was looking for. I'm with you, sorry for delay. Lesson learned. > > I do believe the pressure you impose with your NMU is unnecessary > > because simply asking or sharing your suggestions in email to any of > > us would be better. > > True. I'm sorry for putting you in the spotlight. We are days away from > the freeze, the package has RC bugs and did not transition to testing > yet. I do not want to release wheezy without autofs. There is pressure > from the release team. No worries, I understand this. I had very serious issue preventing me from working on package. :( > From the changelog, I understood that there was only one maintainer who > did ample of work to update the package. > > RC http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673796 has no > response from maintainer. Do you have a patch committed to some private > Vcs repository? Yes, we're using the following repository: http://anonscm.debian.org/gitweb/?p=collab-maint/autofs.git > > RC http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674391 has no > response from maintainer. And you say you do have a patch ready. Yes, see the above repository. > Who sponsored your upload? You can find out with 'who-uploads' from devscripts. ;) > Because bug #674391 is Fail To Build From > Source (in a sane manner) filed the day after the upload. Autoconf was > last updated on 2012-05-12. Did the package FTBFS (in a sane manner) on > the upload? Autoconf is unrelated to the issue. Yes package was building fine but I think the second build would be broken due to modification introduced by upstream patches to a generated file. I'm not sure what has changed (if any) to provoke FTBFS - perhaps something was built differently because problem was discovered during automatic rebuild. (Shortly after upload I noticed that it was impossible to un-apply patches after build.) But I knew how to avoid the issue. > > Also I'm sure you're aware that I'm not a DD, so to override your NMU > > I must complete changes for new release and find a sponsor within 5 > > days only. > > I am aware that you are not a DD. > To cancel an NMU you only need to get any DD to 'sponsor' this one line: > > "dcut ftp-eu cancel autofs_5.0.6-1.1_amd64.changes" Thank you. However when there is only little time left I need to ask more than one person in order to stop it for sure. > Nobody is forcing you to complete changes for a new release in an > unreasonable quick amount of time. > > I am sure anyone from #debian-mentors would have done it, if it was not > already done by me. True. > Do you have a DD in your team of three people to review and sponsor > packages? Fortunately. :) > > You're welcome to the team if you want to help but please consider > > first to communicate whatever improvements you might have and then > > perhaps sponsor the existing effort rather than override it with > > premature NMU. > > Yes, I do want to be part of the team. Thank you and welcome :) Feel free to add yourself to Uploaders. > Do you have a team setup on alioth with a Vcs repository and mailing > list? Or
Processed: tagging 674391
Processing commands for cont...@bugs.debian.org: > tags 674391 + pending Bug #674391 [src:autofs] autofs: FTBFS: dpkg-buildpackage: error: dpkg-source -b autofs-5.0.6 gave error exit status 2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 674391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674391 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: tagging 673796
Processing commands for cont...@bugs.debian.org: > tags 673796 + pending Bug #673796 [autofs5,autofs5-ldap,autofs5-hesiod] autofs5: prompting due to modified conffiles which were not modified by the user Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 673796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 675455 is serious
Processing commands for cont...@bugs.debian.org:
> severity 675455 serious
Bug #675455 {Done: Laurent Bigonville } [empathy] empathy:
emapthy depends on libgstfarsight which conflicts with libpurple0
Bug #675146 {Done: Laurent Bigonville } [empathy] Empathy
blocks Pidgin upgrade
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
675146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675146
675455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675455
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#675309: nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open "/usr/share/sgml/mutter-common/catalog
clone 675309 -1 reassign -1 sgml-base thanks On 31.05.2012 15:52, Michael Biebl wrote: > On 31.05.2012 13:47, Michael Biebl wrote: >> Hi, >> >> On 31.05.2012 09:20, Robert Luberda wrote: >>> po4a or any other program that calls nsgmls fails with: >>> nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open >>> "/usr/share/sgml/mutter-common/catalog" (No such file or directory) >>> >>> I can see in the changelog for 3.4.1-2 that removal of >>> mutter-common.catalog file was intentional but >>> /etc/sgml/mutter-common.cat still referes to it. >> >> Since update-catalog was responsible for installing this file into >> /etc/sgml, I'm wondering if it isn't also update-catalog's job to clean >> up the conffile once the package is removed or it stops shipping the >> catalog file. > > In case of mutter-common the file /usr/share/sgml/mutter-common/catalog > is gone for good so I guess we can just forcefully remove > /etc/sgml/mutter-common.cat on upgrades. > > I'm wondering though, what to do about metacity-common, which exposes > the same problem if the package is removed, but not purged. > Cleaning up the conffile on "remove" might be tricky, since you can't > just delete it. You'd have to move it away / rename it and move it back > if the package is re-installed. > >> # cat /etc/sgml/metacity-common.cat >> CATALOG /usr/share/sgml/metacity-common/catalog >> # ls /usr/share/sgml/metacity-common/catalog >> ls: cannot access /usr/share/sgml/metacity-common/catalog: No such file >> or directory > > As said, those dangling conffiles in /etc/sgml are a more general > problem. I'm wondering if nsgmls should handle that more gracefully/in a > more robust way. I completely missed that those files are not conffiles but completely managed by update-catalog via the maintainer scripts/dpkg triggers. I'm cloning and re-assignig this bug to sgml-base. It should handle the case of removed-but-not-purged packages in a way that it doesn't break existing software like nsgmls. As for mutter-common, I'll just rm -f the files on upgrade. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#675309: nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open "/usr/share/sgml/mutter-common/catalog
Processing commands for cont...@bugs.debian.org: > clone 675309 -1 Bug #675309 [mutter-common] nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open "/usr/share/sgml/mutter-common/catalog Bug 675309 cloned as bug 675462 > reassign -1 sgml-base Bug #675462 [mutter-common] nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open "/usr/share/sgml/mutter-common/catalog Bug reassigned from package 'mutter-common' to 'sgml-base'. No longer marked as found in versions mutter/3.4.1-3. Ignoring request to alter fixed versions of bug #675462 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 675309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675309 675462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675462 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#673770: Problem with NMU version?
Is this "modifying files from another package" (found by piuparts) bug specific to 1:2.22-1.1 NMU version or is it also present in 1:2.22-1? If it isn't NMU spesific then BTS version tracking should let know it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675407: xserver-xorg-video-openchrome: openchrome relink against new xserver results in null pointer dereference
On Fri, Jun 01, 2012 at 02:40:04AM +0200, Cyril Brulebois wrote: > Sebastian Reichel (31/05/2012): > > Hi, > > > > It's not enough to rebuild openchrome against the new X-Server, > > since the new X-Server does not run vgaHWSetStdFuncs(hwp) anymore: > > > > http://cgit.freedesktop.org/xorg/xserver/commit/?id=4bd6579188e718654c35f95623fd4772f9e0ef06 > > > > Please update the driver to support the X-Server's ABI change. > > Hello, > > can you please test the attached patch? Seems like upstream's svn (no > comment) has no fix at the moment. This might be because upstream switched to git :) and I didn't have time to update to package to track the git version yet. I hope I can find some time soon. -- Julien Viard de Galbert http://silicone.homelinux.org/ GPG Key ID: D00E52B6 Published on: hkp://keys.gnupg.net Key Fingerprint: E312 A31D BEC3 74CC C49E 6D69 8B30 6538 D00E 52B6 signature.asc Description: Digital signature
Processed: block 671853 with 671675
Processing commands for cont...@bugs.debian.org: > block 671853 with 671675 Bug #671853 [release.debian.org] Transition: cpl 671853 was not blocked by any bugs. 671853 was not blocking any bugs. Added blocking bug(s) of 671853: 671675 > thanks Stopping processing here. Please contact me if you need assistance. -- 671853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671853 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#675309: marked as done (nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open "/usr/share/sgml/mutter-common/catalog)
Your message dated Fri, 01 Jun 2012 12:33:44 + with message-id and subject line Bug#675309: fixed in mutter 3.4.1-4 has caused the Debian Bug report #675309, regarding nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open "/usr/share/sgml/mutter-common/catalog 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.) -- 675309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mutter-common Version: 3.4.1-3 Severity: serious Justification: breaks unrelated software Hi, po4a or any other program that calls nsgmls fails with: nsgmls:/etc/sgml/mutter-common.cat:8:8:E: cannot open "/usr/share/sgml/mutter-common/catalog" (No such file or directory) I can see in the changelog for 3.4.1-2 that removal of mutter-common.catalog file was intentional but /etc/sgml/mutter-common.cat still referes to it. Regards, robert -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (200, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/dash Versions of packages mutter-common depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-1 mutter-common recommends no packages. mutter-common suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: mutter Source-Version: 3.4.1-4 We believe that the bug you reported is fixed in the latest version of mutter, which is due to be installed in the Debian FTP archive: gir1.2-mutter-3.0_3.4.1-4_amd64.deb to main/m/mutter/gir1.2-mutter-3.0_3.4.1-4_amd64.deb libmutter-dev_3.4.1-4_amd64.deb to main/m/mutter/libmutter-dev_3.4.1-4_amd64.deb libmutter0_3.4.1-4_amd64.deb to main/m/mutter/libmutter0_3.4.1-4_amd64.deb mutter-common_3.4.1-4_all.deb to main/m/mutter/mutter-common_3.4.1-4_all.deb mutter-dbg_3.4.1-4_amd64.deb to main/m/mutter/mutter-dbg_3.4.1-4_amd64.deb mutter_3.4.1-4.debian.tar.gz to main/m/mutter/mutter_3.4.1-4.debian.tar.gz mutter_3.4.1-4.dsc to main/m/mutter/mutter_3.4.1-4.dsc mutter_3.4.1-4_amd64.deb to main/m/mutter/mutter_3.4.1-4_amd64.deb 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 675...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated mutter 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: Fri, 01 Jun 2012 12:49:07 +0200 Source: mutter Binary: mutter mutter-dbg libmutter0 mutter-common libmutter-dev gir1.2-mutter-3.0 Architecture: source all amd64 Version: 3.4.1-4 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers Changed-By: Michael Biebl Description: gir1.2-mutter-3.0 - GObject introspection data for Mutter libmutter-dev - Development files for the Mutter window manager libmutter0 - window manager library from the Mutter window manager mutter - lightweight GTK+ window manager mutter-common - shared files for the Mutter window manager mutter-dbg - Debugging symbols for the Mutter window manager Closes: 675309 Changes: mutter (3.4.1-4) unstable; urgency=low . * Clean up /etc/sgml/mutter-common.cat and /etc/sgml/mutter-common.cat.old on upgrades. Closes: #675309 Checksums-Sha1: ba94788edad2f4da72e7eaa405d3f13e9e85c87e 2842 mutter_3.4.1-4.dsc d45e974bbeebf8243de1845d1591537f3b0d05a6 16456 mutter_3.4.1-4.debian.tar.gz 0105dc8213aa0317870ce198e1c6d672b923240c 1472530 mutter-common_3.4.1-4_all.deb 7df42433f37f2f9105c2a50691706ff261393080 258946 mutter_3.4.1-4_amd64.deb 07338dd271164f2311a06d2974f088a3292d5d0e 1384862 mutter-dbg_3.4.1-4_amd64.deb 3feb69aae7bea1e77b43f8fbb0cc887390fec1b5 564806 libmutter0_3.4.1-4_amd64.deb 0c68f1a0f94f991184649376bb29711596c73827 691968 libmutter-dev_3.4.1-4_amd64.deb a1d9caecf4ca890ef751904a522398986ff4bfee 239366 gir1.2-mutter-3.0_3.4.1-4_amd64.deb Checksums-Sha256: 16702728502d0136171383863502daa95b3964f62fc6c592ad76d1aa19928d0d 2842 mutter_3.4.1-4.dsc a61a45992913e96d1abb9a563496ff138f2108ee9a920db4715bc76588823d5f 16456 mutter_3.4.1-4.debian.tar.gz 3633f2984a96cb153b6316c54ad128abced83a5
Bug#666337: euler: FTBFS: gcc: error: unrecognized option '-V'
On 01/06/12 01:03, gregor herrmann wrote:
> If you have the time to create a debdiff, great.
> Otherwise I can also do it myself.
Here it is. LDFLAGS is exported now as well. Otherwise the maintainer's change
from 1.61.0-5 is reverted, i.e the unneeded dependencies are back.
Cheers
--
Sebastian Ramacher
diff -Nru euler-1.61.0/debian/changelog euler-1.61.0/debian/changelog
--- euler-1.61.0/debian/changelog 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/changelog 2012-06-01 14:09:21.0 +0200
@@ -1,3 +1,16 @@
+euler (1.61.0-8.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Use dh-autoreconf to regenerate ./configure. This fixes the FTBFS and
+lintian's binary-or-shlib-defines-rpath. (Closes: #666337)
+- debian/control: Build-Dep on dh-autoreconf instead of autotools-dev.
+- debian/rules:
+ - Call dh with --with autoreconf and don't copy config.{guess,sub}
+manually.
+ - Export LDFLAGS to not revert the maintainer's change in 1.61.0-5.
+
+ -- Sebastian Ramacher Fri, 01 Jun 2012 13:48:31 +0200
+
euler (1.61.0-8) unstable; urgency=low
* Switched to source format "3.0 (quilt)".
diff -Nru euler-1.61.0/debian/control euler-1.61.0/debian/control
--- euler-1.61.0/debian/control 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/control 2012-05-31 19:32:06.0 +0200
@@ -2,7 +2,7 @@
Section: math
Priority: optional
Maintainer: Frank S. Thomas
-Build-Depends: debhelper (>= 7), autotools-dev, libgtk2.0-dev (>= 2.6.0)
+Build-Depends: debhelper (>= 7), dh-autoreconf, libgtk2.0-dev (>= 2.6.0)
Standards-Version: 3.8.3
Vcs-Git: git://git.debian.org/git/collab-maint/euler.git
Vcs-Browser: http://git.debian.org/?p=collab-maint/euler.git
diff -Nru euler-1.61.0/debian/rules euler-1.61.0/debian/rules
--- euler-1.61.0/debian/rules 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/rules 2012-06-01 14:04:57.0 +0200
@@ -1,13 +1,9 @@
#!/usr/bin/make -f
-LDFLAGS += -Wl,--as-needed
-
-build:
- cp -f /usr/share/misc/config.guess .
- cp -f /usr/share/misc/config.sub .
- dh build
+export LDFLAGS += -Wl,--as-needed
%:
- dh $@
+ dh $@ --with autoreconf
-.PHONY: build
+# override_dh_autoreconf:
+# dh_autoreconf --as-needed
signature.asc
Description: OpenPGP digital signature
Bug#672054: marked as done (parser: FTBFS: ld: cannot find -l-l)
Your message dated Fri, 01 Jun 2012 12:50:34 + with message-id and subject line Bug#672054: fixed in parser 3.4.1-7 has caused the Debian Bug report #672054, regarding parser: FTBFS: ld: cannot find -l-l 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.) -- 672054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: parser Version: 3.4.1-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 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 -shared -o mod_parser3.so -Wl,--whole-archive libmod_parser3.a > ../../classes/libclasses.a ../../types/libtypes.a ../../main/libmain.a > ../../lib/gd/libgd.a ../../lib/cord/libcord.a ../../lib/md5/libmd5.a > ../../lib/sdbm/libsdbm.a ../../lib/smtp/libsmtp.a ../../lib/json/libjson.a > ../../../src/lib/ltdl/libltdlc.a -Wl,--no-whole-archive \ > -L/usr/ -lgc -L/usr//lib -l -l -l -ldl -lstdc++ > /usr/bin/ld: cannot find -l-l > /usr/bin/ld: cannot find -l-ldl > collect2: error: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/parser_3.4.1-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: parser Source-Version: 3.4.1-7 We believe that the bug you reported is fixed in the latest version of parser, which is due to be installed in the Debian FTP archive: libapache2-mod-parser3_3.4.1-7_amd64.deb to main/p/parser/libapache2-mod-parser3_3.4.1-7_amd64.deb parser3-cgi_3.4.1-7_amd64.deb to main/p/parser/parser3-cgi_3.4.1-7_amd64.deb parser3-common_3.4.1-7_amd64.deb to main/p/parser/parser3-common_3.4.1-7_amd64.deb parser3-dev_3.4.1-7_amd64.deb to main/p/parser/parser3-dev_3.4.1-7_amd64.deb parser3_3.4.1-7_all.deb to main/p/parser/parser3_3.4.1-7_all.deb parser_3.4.1-7.debian.tar.gz to main/p/parser/parser_3.4.1-7.debian.tar.gz parser_3.4.1-7.dsc to main/p/parser/parser_3.4.1-7.dsc 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 672...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergey B Kirpichev (supplier of updated parser 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: Fri, 01 Jun 2012 15:58:59 +0400 Source: parser Binary: parser3 parser3-common parser3-cgi libapache2-mod-parser3 parser3-dev Architecture: source all amd64 Version: 3.4.1-7 Distribution: unstable Urgency: low Maintainer: Sergey B Kirpichev Changed-By: Sergey B Kirpichev Description: libapache2-mod-parser3 - Parser 3, HTML-embedded scripting language (Apache2 module) parser3- Parser 3, HTML-embedded scripting language (metapackage) parser3-cgi - Parser 3, HTML-embedded scripting language (CGI binary) parser3-common - Common files for packages built from the Parser 3 source parser3-dev - Files for Parser 3 module development Closes: 672054 Changes: parser (3.4.1-7) unstable; urgency=low . * Added patch 115 to call pa_setup_module_cells() while real request handling. * Fix syntax error for debian/copyright * Fix FTBFS: multiarch path for xml lib (Closes: #672054) * Refresh 199_reconfigure.patch * Change dh compat to 9, enable hardening support * Drop custom CFLAGS, LDFLAGS in debian/rules * Add -fPIC to CFLAGS/CXXFLAGS Checksums-Sha1: 69fd8f45fdd547f9a33e2387f568088527a5f024 2187 parser_3.4.1-7.dsc c6743d53413dc04401004e44abf2b96c59cc7f89 380366 parser_3.4.1-7.debian.tar.gz 16508139c86ce85964b16a4891f78632ca612174 1058 parser3_3.4.1-7_all.deb 88574675651272d30822c9a7c7d05b21dd16268b 105880 parser3-common_3.4.1-7_amd64.deb 684d68dcd16aa55d523f75dbbfe5e28b49caa077 444354 parser3-cgi_3.4.1-7_amd64.deb 3c9d1ee6d2fb3a140b0f9a2f255f5aaa026cb4f6 494978 libapache2-mod-parser3_3.4.1-7_amd64.deb e47b
Bug#666337: euler: FTBFS: gcc: error: unrecognized option '-V'
On 01/06/12 14:17, Sebastian Ramacher wrote:
> On 01/06/12 01:03, gregor herrmann wrote:
>> If you have the time to create a debdiff, great.
>> Otherwise I can also do it myself.
>
> Here it is. LDFLAGS is exported now as well. Otherwise the maintainer's change
> from 1.61.0-5 is reverted, i.e the unneeded dependencies are back.
Sorry, that was the wrong patch. Here is the right one.
Cheers
--
Sebastian Ramacher
diff -Nru euler-1.61.0/debian/changelog euler-1.61.0/debian/changelog
--- euler-1.61.0/debian/changelog 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/changelog 2012-06-01 14:09:21.0 +0200
@@ -1,3 +1,16 @@
+euler (1.61.0-8.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Use dh-autoreconf to regenerate ./configure. This fixes the FTBFS and
+lintian's binary-or-shlib-defines-rpath. (Closes: #666337)
+- debian/control: Build-Dep on dh-autoreconf instead of autotools-dev.
+- debian/rules:
+ - Call dh with --with autoreconf and don't copy config.{guess,sub}
+manually.
+ - Export LDFLAGS to not revert the maintainer's change in 1.61.0-5.
+
+ -- Sebastian Ramacher Fri, 01 Jun 2012 13:48:31 +0200
+
euler (1.61.0-8) unstable; urgency=low
* Switched to source format "3.0 (quilt)".
diff -Nru euler-1.61.0/debian/control euler-1.61.0/debian/control
--- euler-1.61.0/debian/control 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/control 2012-05-31 19:32:06.0 +0200
@@ -2,7 +2,7 @@
Section: math
Priority: optional
Maintainer: Frank S. Thomas
-Build-Depends: debhelper (>= 7), autotools-dev, libgtk2.0-dev (>= 2.6.0)
+Build-Depends: debhelper (>= 7), dh-autoreconf, libgtk2.0-dev (>= 2.6.0)
Standards-Version: 3.8.3
Vcs-Git: git://git.debian.org/git/collab-maint/euler.git
Vcs-Browser: http://git.debian.org/?p=collab-maint/euler.git
diff -Nru euler-1.61.0/debian/rules euler-1.61.0/debian/rules
--- euler-1.61.0/debian/rules 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/rules 2012-06-01 14:11:14.0 +0200
@@ -1,13 +1,6 @@
#!/usr/bin/make -f
-LDFLAGS += -Wl,--as-needed
-
-build:
- cp -f /usr/share/misc/config.guess .
- cp -f /usr/share/misc/config.sub .
- dh build
+export LDFLAGS += -Wl,--as-needed
%:
- dh $@
-
-.PHONY: build
+ dh $@ --with autoreconf
signature.asc
Description: OpenPGP digital signature
Bug#666337: euler: diff for NMU version 1.61.0-8.1
tags 666337 + pending
thanks
Dear maintainer,
Sebastian Ramacher has prepared an NMU for euler (versioned as
1.61.0-8.1) and I've 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: Simon And Garfunkel: 59th St. Bridge Song
diff -Nru euler-1.61.0/debian/changelog euler-1.61.0/debian/changelog
--- euler-1.61.0/debian/changelog 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/changelog 2012-06-01 15:19:19.0 +0200
@@ -1,3 +1,16 @@
+euler (1.61.0-8.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Use dh-autoreconf to regenerate ./configure. This fixes the FTBFS and
+lintian's binary-or-shlib-defines-rpath. (Closes: #666337)
+- debian/control: Build-Dep on dh-autoreconf instead of autotools-dev.
+- debian/rules:
+ - Call dh with --with autoreconf and don't copy config.{guess,sub}
+manually.
+ - Export LDFLAGS to not revert the maintainer's change in 1.61.0-5.
+
+ -- Sebastian Ramacher Fri, 01 Jun 2012 13:48:31 +0200
+
euler (1.61.0-8) unstable; urgency=low
* Switched to source format "3.0 (quilt)".
diff -Nru euler-1.61.0/debian/control euler-1.61.0/debian/control
--- euler-1.61.0/debian/control 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/control 2012-06-01 15:17:25.0 +0200
@@ -2,7 +2,7 @@
Section: math
Priority: optional
Maintainer: Frank S. Thomas
-Build-Depends: debhelper (>= 7), autotools-dev, libgtk2.0-dev (>= 2.6.0)
+Build-Depends: debhelper (>= 7), dh-autoreconf, libgtk2.0-dev (>= 2.6.0)
Standards-Version: 3.8.3
Vcs-Git: git://git.debian.org/git/collab-maint/euler.git
Vcs-Browser: http://git.debian.org/?p=collab-maint/euler.git
diff -Nru euler-1.61.0/debian/rules euler-1.61.0/debian/rules
--- euler-1.61.0/debian/rules 2009-11-18 13:39:47.0 +0100
+++ euler-1.61.0/debian/rules 2012-06-01 15:17:25.0 +0200
@@ -1,13 +1,6 @@
#!/usr/bin/make -f
-LDFLAGS += -Wl,--as-needed
-
-build:
- cp -f /usr/share/misc/config.guess .
- cp -f /usr/share/misc/config.sub .
- dh build
+export LDFLAGS += -Wl,--as-needed
%:
- dh $@
-
-.PHONY: build
+ dh $@ --with autoreconf
signature.asc
Description: Digital signature
Processed: euler: diff for NMU version 1.61.0-8.1
Processing commands for cont...@bugs.debian.org: > tags 666337 + pending Bug #666337 [src:euler] euler: FTBFS: gcc: error: unrecognized option '-V' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 666337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666337 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#666337: euler: FTBFS: gcc: error: unrecognized option '-V'
On Fri, 01 Jun 2012 14:19:42 +0200, Sebastian Ramacher wrote: > >> If you have the time to create a debdiff, great. > >> Otherwise I can also do it myself. > > Here it is. LDFLAGS is exported now as well. Otherwise the maintainer's > > change > > from 1.61.0-5 is reverted, i.e the unneeded dependencies are back. Good catch. > Sorry, that was the wrong patch. Here is the right one. Thank you, uploaded to DELAYED/2. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Simon And Garfunkel: 59th St. Bridge Song signature.asc Description: Digital signature
Bug#673770: Problem with NMU version?
On 2012-06-01 13:57, Touko Korpela wrote: > Is this "modifying files from another package" (found by piuparts) bug > specific to 1:2.22-1.1 NMU version or is it also present in 1:2.22-1? > If it isn't NMU spesific then BTS version tracking should let know it. Just looked into the issue. 1:2.22-1.1 split out the libpam-cap package, but there is no clean upgrade path. If you had libcap2-bin installed and upgrade from squeeze or wheezy to sid, you end up without pam_cap.so but the module is still enabled. Probably libcap2-bin needs a Depends: libpam-cap Andreas -- 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 631807 is serious
Processing commands for cont...@bugs.debian.org: > #breaks users of this library on some architectures > severity 631807 serious Bug #631807 [libcap-ng0] segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc Bug #635664 [libcap-ng0] regression: bluetoothd segfaults when upgrading from 4.94-2 to 4.94-3 Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 631807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631807 635664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635664 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#674391: autofs upload [update]
On 01.06.2012 16:23, Michael Tokarev wrote: > On 01.06.2012 16:15, Dmitry Smirnov wrote: >> Hi Michael and William >> >> Dmitrijs called off his NMU and expressed his interest to join our team >> while I updated repository with more changes. > > I'm doing some last-minute changes too, which we discussed > before (namely, including the initscript). > > The ftbfs with kmod/module-init-tools is due to my change, > I removed the ugly config.h patching in > 450dfb2c4fc1d6caf7653a3bef33c2aa5e897361. > In order to fix the issue right, the easiest solution is > to set ac_cv_path_MODPROBE=/sbin/modprobe before invoking > ./configure. Ditto for the related test which I also removed > in the same commit, for linux /proc filesystem (HAVE_LINUX_PROCFS). Ok. This is just too much wrong. Dmitry, your two changes, both marked as fixing #674391, are wrong and needs revered. First, a small thing, the kmod change, c6ac061e12208cdf32291223b27caeefec6ce241. Here's the changelog difference from it: [Dmitry Smirnov] - * update upstream patches to avoid patching 'configure' (Closes: #674391) + * added 'kmod' to Build-Depends to fix FTBFS (Closes: #674391) + * update upstream patches to avoid patching 'configure' * use 'autoconf' to regenerate 'configure' Now please tell me how this kmod thing is relevant for #674391? It is wrong, and it is very confusing, since I started thinking about entirely different thing and not about the real problem. The change itself is right, well, sort of, -- it fixes the issue as the package isn't built correctly without /sbin/modprobe (even if it never uses /sbin/modprobe to start with, which is a different issue). But the misplacing of the Closes/FTBFS line is troubling. I reverted this whole commit. And second, the more serious change, which actually tries to fix the FTBFS mentioned in #674391. You took a wrong approach with this, by taking patches from upstream and removing patching of configure. This way, we're patching upstream patches, the result is a unverifiable mess. (Why upstream keeps configure in git is another question, to which there's no sane answer). The proposed by Dmitrijs approach -- using dh-autoreconf or similar, plus maybe patching Makefile to not remade configure.in (which is another strange thing to do) -- is the way to go here. dh-autoreconf will save all autoconf-related files and will restore them in `clean' target, making whole thing working. Alternatively, if you think dh_autoreconf is too heavy somehow, it is possible to save configure.in and configure in debian/rules "configure" step and restore them in "clean" target without using helpers/addons, it is just as easy. Now, we need to re-run autoconf anyway. I'm reverting this change too, because it is just the wrong thing to go. I'll try to fix this mess in a most accurate way, but we have more and more work to resolve with upstream, the package (upstream code) is in rather bad state. Dmitrijs: #674391 contains another change which everyone missed now, about gold and --no-as-needed, which should be incorporated too, I think. Oh well. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675473: docbook: please rebuild to fix your copy of #477751
Source: docbook Severity: serious Dear maintainer(s) of docbook, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675474: debiandoc-sgml: please rebuild to fix your copy of #477751
Source: debiandoc-sgml Severity: serious Dear maintainer(s) of debiandoc-sgml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675475: docbook-dsssl: please rebuild to fix your copy of #477751
Source: docbook-dsssl Severity: serious Dear maintainer(s) of docbook-dsssl, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675476: docbook-ebnf: please rebuild to fix your copy of #477751
Source: docbook-ebnf Severity: serious Dear maintainer(s) of docbook-ebnf, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675477: docbook-html-forms: please rebuild to fix your copy of #477751
Source: docbook-html-forms Severity: serious Dear maintainer(s) of docbook-html-forms, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675478: docbook-mathml: please rebuild to fix your copy of #477751
Source: docbook-mathml Severity: serious Dear maintainer(s) of docbook-mathml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675479: docbook-simple: please rebuild to fix your copy of #477751
Source: docbook-simple Severity: serious Dear maintainer(s) of docbook-simple, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675480: docbook-slides: please rebuild to fix your copy of #477751
Source: docbook-slides Severity: serious Dear maintainer(s) of docbook-slides, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675481: docbook-website: please rebuild to fix your copy of #477751
Source: docbook-website Severity: serious Dear maintainer(s) of docbook-website, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675482: docbook-xml: please rebuild to fix your copy of #477751
Source: docbook-xml Severity: serious Dear maintainer(s) of docbook-xml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675483: xml-core: please rebuild to fix your copy of #477751
Source: xml-core Severity: serious Dear maintainer(s) of xml-core, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#631807: GCC workarounds should be dropped too
When fixing this bug, #563935 and #583881 (GCC workarounds for long time fixed bugs) should be fixed too. They are about sparc and armel arcs. Now this package is compiled unoptimized in these arcs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675485: libcommons-validator-java: please rebuild to fix your copy of #477751
Source: libcommons-validator-java Severity: serious Dear maintainer(s) of libcommons-validator-java, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Processed: ooops
Processing commands for cont...@bugs.debian.org: > severity 660686 grave Bug #660686 [libmysqlclient18] libmysqlclient18 does not used versioned symbols libmysqlclient18 does not used versioned symbols Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 660686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660686 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#674089: mime-support: removed application/x-httpd-* can lead to immense security problems
On Thursday 31 May 2012, Christoph Anton Mitterer wrote: > So from my side I'd say the following: > > 1) IF a change like this happens,.. it definitely must go to the > NEWS file, as - in the case of Apache HTTPD Server - it can even > have security relevant outcomes. > So Brian, as long as this change stays, could you please add such > information? Documenting this in a prominent place is a good idea. I would vote for the release notes plus either apache2 or mod_php NEWS file. It seems exessive to have it in the mime-support NEWS file since it is just noise to all non-apache2 users. > > 2) I Agree with Thijs (IIRC it was him) comment, that there are > security implications in apache, i.e. that the mime.types file > _alone_ would also have files like foo.php.jpeg marked as > application/x-httpd-php and therefore possibly interpreted as PHP > code (which is well known, but stupid and dangerous anyway. > But that's easy to solve, see below. > > 3) Given that mime.types may be used by many programs, which may > want to know about PHP files as well... it's a bad idea to fix > Apache HTTPD's stupidity (well at least "difficult" extension > handling) by removing types from mime.types. The x-httpd- types are really historic ballast from the time there was no separate way to configure the handler (Apache 1.3.x or even 1.2.x). Because of their special properties, they are called magic MIME types in apache httpd. Therefore I think they should be considered an internal (and deprecated) implementation detail of apache httpd and should not be used as real MIME types anywhere else. As #589384 explained, declaring them globally is bad for security. And it would be really strange to set these magic types globally just to remove them with "RemoveType php" again in the default apache2 configuration. But adding a different type for .php to /etc/mime.types is fine with me. There is some discussion at http://cweiske.de/tagebuch/php- mimetype.htm which type may be best. Both text/x-php and application/x-php seem ok to me. Cheers, Stefan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675488: sgml-data: please rebuild to fix your copy of #477751
Source: sgml-data Severity: serious Dear maintainer(s) of sgml-data, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675489: python-docutils: please rebuild to fix your copy of #477751
Source: python-docutils Severity: serious Dear maintainer(s) of python-docutils, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675490: sgml2x: please rebuild to fix your copy of #477751
Source: sgml2x Severity: serious Dear maintainer(s) of sgml2x, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Bug#675495: Should not be released with Wheezy
Package: openjdk-6 Severity: serious Upstream support for Java 6 ends in November: http://www.oracle.com/technetwork/java/javase/eol-135779.html As such, we should not include it in Wheezy and fix up the rdepends to use openjdk-7 instead. Especially, since openjdk is quite a burden to update even for a single package (huge size, weird upstream situation with bits of icectea mixed in). An alternative would be to exclude it from security support as we do for some web browsers, but that's a non-optimal solution IMHO. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674805: gcc transit
Hi The relesae team is not happy about the transit of gcc from 4.6 to 4.7 and is trying to revert it, so it would be a good idea to wait with a rebuild until that issue is sorted. Cheers, Ãli -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674391: autofs upload [update]
Hi Michael, > Dmitry, your two changes, both marked as fixing #674391, > are wrong and needs revered. > > First, a small thing, the kmod change, > c6ac061e12208cdf32291223b27caeefec6ce241. > Here's the changelog difference from it: > > [Dmitry Smirnov] > - * update upstream patches to avoid patching 'configure' (Closes: #674391) > + * added 'kmod' to Build-Depends to fix FTBFS (Closes: #674391) > + * update upstream patches to avoid patching 'configure' > * use 'autoconf' to regenerate 'configure' > > Now please tell me how this kmod thing is relevant for #674391? Please feel free to undo my latest change introducing 'kmod' to Build-Depends. Initially I thought I already fixed #674391 but today when I was building in pbuilder there were FTBFS. I did not tracked it to your change and thought that I could have been wrong regarding diagnosis of reported FTBFS' cause and that it was related to recent changes in 'sid'. (It would be nice if you try to avoid breaking master with incomplete commits or mark them as such) I realised that this change was unrelated from one of your earlier emails and since I already mentioned to you what I did I thought you would realise what's happened. > It is wrong, and it is very confusing, since I started thinking > about entirely different thing and not about the real problem. > The change itself is right, well, sort of, -- it fixes the issue > as the package isn't built correctly without /sbin/modprobe (even > if it never uses /sbin/modprobe to start with, which is a different > issue). But the misplacing of the Closes/FTBFS line is troubling. Yes, sorry. Somehow we're collided with our changes to the package. :( > > I reverted this whole commit. Great. ### > And second, the more serious change, which actually tries to > fix the FTBFS mentioned in #674391. Not 'tries' - it fixes it. > You took a wrong approach with this, by taking patches from > upstream and removing patching of configure. This way, we're > patching upstream patches, the result is a unverifiable mess. > (Why upstream keeps configure in git is another question, to > which there's no sane answer). Wait a sec., before criticising, consider that we don't have to patch with pristine patches. I'm not sure why do you call it 'unverifiable' - I'm quite concerned regarding not having hack-ish workaround for upstream mess. Removing junk from upstream patches reduces the size of archive and allows us to have nice and tidy packaging. I was experimenting with different approaches for hours and what I did is the clean and nice alternative to some other things I tried. Why do you protect those junky hunks in upstream patches?? > The proposed by Dmitrijs approach -- using dh-autoreconf or > similar, plus maybe patching Makefile to not remade configure.in > (which is another strange thing to do) -- is the way to go here. > dh-autoreconf will save all autoconf-related files and will > restore them in `clean' target, making whole thing working. We can do it, but it would be nice to discuss why it is better (if it is). At the moment I do not like this approach. dh-autoreconf is great and I use it in some of my packages but here it looks like it would be unnecessary overkill just for the sake of having dirty patches for generated files. > Alternatively, if you think dh_autoreconf is too heavy > somehow, it is possible to save configure.in and configure > in debian/rules "configure" step and restore them in "clean" > target without using helpers/addons, it is just as easy. I'm not against dh-autoreconf where appropriate, but here we will be misusing it for moving stuff out of the way... It doesn't feels right. > I'm reverting this change too, Too bad, I wish you didn't do it. > because it is just the wrong thing to go. To me such claim appears as unsubstantiated. No it is not the wrong thing to do! It is right thing to do. You did not demonstrated convincing evidence that what I did was wrong, but that's not the point. It is wrong to redo the elegant solution without discussion and substitute it with something which is not necessarily nicer. If we want to release soon we need to keep re-factoring for later time and settle our disagreements first. Now it is more important to avoid making too many changes at once. > I'll try to fix this mess in a most accurate > way, but we have more and more work to resolve with upstream, > the package (upstream code) is in rather bad state. Certainly we need to notify upstream that they should not patch generated files. Would you be able to carry out that message? > Dmitrijs: #674391 contains another change which everyone > missed now, about gold and --no-as-needed, which should be > incorporated too, I think. Please excuse my ignorance but what 'gold' has to do with it? '--no-as-needed' is for Ubuntu because they use '--as-needed' by default, right? Perhaps we can try introducing '--as-needed' and see if it works, but I'd rather do it later, after mi
Processed: severity of 639466 is serious
Processing commands for cont...@bugs.debian.org: > severity 639466 serious Bug #639466 [bacula] bacula: Please move to postgresql-9.1 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 639466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639466 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#639466: [pkg-bacula-devel] Bug#639466: bacula: Please move to postgresql-9.1
On Sun, Feb 26, 2012 at 12:17:57 +0100, Martin Pitt wrote: > bts severity 639466 serious > thanks > > Hello Luca, > > Luca Capello [2011-10-30 3:26 +0100]: > > tags 639466 + pending > > Any chance to do an upload soon? I'll bump the severity of the > remaining four 8.4 bugs to RC now, and request removal of 8.4. > Ping. This is the last reverse dep of pg 8.4 now. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 674330
Processing commands for cont...@bugs.debian.org: > tags 674330 + fixed-upstream Bug #674330 [src:clamav] clamav: FTBFS: llvm/lib/ExecutionEngine/JIT/Intercept.cpp:69:67: error: 'lseek64' was not declared in this scope Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 674330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674330 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#674534: closed by Kartik Mistry (Bug#674534: fixed in dee 1.0.10-2)
Version: 1.0.10-2 > dee (1.0.10-2) unstable; urgency=low > + gir1.2-dee-1.0: Added Breaks field, which prevents removal of files that > also belong to gir1.2-dee-0.5 (Closes: #674534) the problem persists, there is no Breaks field: Package: gir1.2-dee-1.0 Source: dee Version: 1.0.10-2 Installed-Size: 120 Maintainer: Kartik Mistry Architecture: amd64 Replaces: gir1.2-dee-0.5 Depends: gir1.2-glib-2.0, libdee-1.0-4 (>= 1.0.6) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675496: dtd-ead: please rebuild to fix your copy of #477751
Source: dtd-ead Severity: serious Dear maintainer(s) of dtd-ead, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-rc
Processed: clamav: diff for NMU version 0.97.3+dfsg-2.2
Processing commands for cont...@bugs.debian.org: > tags 674330 + pending Bug #674330 [src:clamav] clamav: FTBFS: llvm/lib/ExecutionEngine/JIT/Intercept.cpp:69:67: error: 'lseek64' was not declared in this scope Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 674330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674330 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#674330: clamav: diff for NMU version 0.97.3+dfsg-2.2
tags 674330 + pending thanks Dear maintainer, I've prepared an NMU for clamav (versioned as 0.97.3+dfsg-2.2) 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: Soluna Samay: Like A Rose diff -u clamav-0.97.3+dfsg/debian/changelog clamav-0.97.3+dfsg/debian/changelog --- clamav-0.97.3+dfsg/debian/changelog +++ clamav-0.97.3+dfsg/debian/changelog @@ -1,3 +1,13 @@ +clamav (0.97.3+dfsg-2.2) unstable; urgency=low + + * Non-maintainer upload. + * Fix "FTBFS: llvm/lib/ExecutionEngine/JIT/Intercept.cpp:69:67: error: +'lseek64' was not declared in this scope": add missing include. +Also fixed in upstream git already [bb8ab5c]. +(Closes: #674330) + + -- gregor herrmann Fri, 01 Jun 2012 16:46:45 +0200 + clamav (0.97.3+dfsg-2.1) unstable; urgency=low * Non-maintainer upload. only in patch2: unchanged: --- clamav-0.97.3+dfsg.orig/libclamav/c++/llvm/lib/ExecutionEngine/JIT/Intercept.cpp +++ clamav-0.97.3+dfsg/libclamav/c++/llvm/lib/ExecutionEngine/JIT/Intercept.cpp @@ -19,6 +19,7 @@ #include "llvm/Support/ErrorHandling.h" #include "llvm/System/DynamicLibrary.h" #include "llvm/Config/config.h" +#include using namespace llvm; // AtExitHandlers - List of functions to call when the program exits, signature.asc Description: Digital signature
Bug#663388: gnustep-back-common: unowned files after purge (policy 6.8, 10.8) violating FHS (policy 9.1) too
Package: gnustep-back-common Version: 0.22.0-1 Followup-For: Bug #663388 Hi, there are now fewer directories, but there is still something in $HOME: 0m47.6s ERROR: FAIL: Package purging left files on system: /root/GNUstep/ not owned /root/GNUstep/Library/ not owned Andreas gnustep-back-common_0.22.0-1.log.gz Description: GNU Zip compressed data
Bug#621460: Accepted subversion 1.6.17dfsg-3.1 (source all amd64)
On Fri, Jun 1, 2012 at 4:48 PM, Peter Samuelson wrote: > (Aside: half this NMU will be reverted or modified anyway. I explained > in #621460 why we have to be explicit about db versions, but Ondrej's > NMU says libdb-dev with no qualifications. And I'll probably revert > the libsvn-java split, as multiarch for java makes little sense.) I did reply you: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621460#34 and you didn't respond from that time at all. There's really no reason to depend on specific libdbX.Y-dev version and dbX.Y-util, you would only break the ability to do binNMUs when needed to switch the default db version in the unstable archive. I would be happy to work with you on a viable solution to allow binNMUs and yet keep you reasonable asured that nothing will break - the procedure of upgrading Berkeley DB environment is well documented and works reasonably well. The approach taken by cyrus-imapd-2.4 (f.e.)[1] is to note the Berkeley DB database version used in previous version and do something (upgrade the database, print debconf message) if that differ from a newly installed version. Again I would be happy to help to write such logic into maintainer scripts. Links: 1. http://anonscm.debian.org/gitweb/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db Ondrej -- Ondřej Surý -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663388: gnustep-back-common: unowned files after purge (policy 6.8, 10.8) violating FHS (policy 9.1) too
Andreas Beckmann wrote: > there are now fewer directories, but there is still something in $HOME: > > 0m47.6s ERROR: FAIL: Package purging left files on system: > /root/GNUstep/ not owned > /root/GNUstep/Library/ not owned Yes, this is because mknfonts.tool which is run in postinst is still linked with libgnustep-base1.22. When it is rebuilt during the forthcoming transition, the problem will go way. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675474: debiandoc-sgml: please rebuild to fix your copy of #477751
Hi, Thanks for reminder. On Fri, Jun 01, 2012 at 03:52:37PM +0200, Helmut Grohne wrote: > Source: debiandoc-sgml > Severity: serious > > Dear maintainer(s) of debiandoc-sgml, > > TL;DR: Please upload a new version of this package closing this bug. I do not understand "TL;DR". You mean: Too long ; Didn't read. > Problem > ~~~ > Your package uses the dh_installcatalogs helper from debhelper. This helper > added code to the postinst that unconditionally overwrites files in /etc which > is a policy violation. The corresponding bug #477751 is now solved in > debhelper. Nevertheless the code overwriting files in /etc is still present in > a binary package built from this source package, so your package needs a > rebuild. Unfortunately the binary package in question is Architecture: all, so > a binNMU is not enough. > > How to solve > > This bug tracks the progress of the rebuild and should be closed by any upload > of this package. Before building, please ensure that your debhelper version is > at least 9.20120528 which should be the case if you are running sid. > > > Is my package really/still affected? > > Any binary package using the dh_installcatalogs helper will add a versioned I see. > dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, > your package is not affected. In that case, just close this bug. > > > If you have any further questions concerning this issue, please don't hesitate > to contact me. > > Thanks for your help You could have uploaded as NMU for this package too. I will upload it now ... :-) Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666337: euler: FTBFS: gcc: error: unrecognized option '-V'
On Friday 01 June 2012 15:23:27 gregor herrmann wrote: > On Fri, 01 Jun 2012 14:19:42 +0200, Sebastian Ramacher wrote: > > >> If you have the time to create a debdiff, great. > > >> Otherwise I can also do it myself. > > > > > > Here it is. LDFLAGS is exported now as well. Otherwise the maintainer's > > > change from 1.61.0-5 is reverted, i.e the unneeded dependencies are > > > back. > > Good catch. > > > Sorry, that was the wrong patch. Here is the right one. > > Thank you, uploaded to DELAYED/2. Thank you guys for fixing this bug! signature.asc Description: This is a digitally signed message part.
Processed: block 671115 with 660686
Processing commands for cont...@bugs.debian.org: > block 671115 with 660686 Bug #671115 [release.debian.org] transition: mysql-5.5 671115 was blocked by: 674328 673528 667428 673263 650058 674122 649955 651110 674309 672714 650060 666331 672619 672950 673264 672716 651317 674210 673262 672765 661422 673260 673183 673161 649638 668232 673153 672824 672621 672816 672207 672588 671115 was blocking: 672928 Added blocking bug(s) of 671115: 660686 > thanks Stopping processing here. Please contact me if you need assistance. -- 671115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671115 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#674391: minimal change
I think a minimal change to fix the FTBFS is (changing it to not call upstream's distclean might be saner, though): diff -r -u o/autofs-5.0.6/debian/clean n/autofs-5.0.6/debian/clean --- o/autofs-5.0.6/debian/clean 2012-04-23 17:18:20.0 +0200 +++ n/autofs-5.0.6/debian/clean 2012-06-01 16:56:51.315205416 +0200 @@ -2,4 +2,5 @@ config.log config.status include/config.h -#configure +include/config.h.in +configure diff -r -u o/autofs-5.0.6/debian/rules n/autofs-5.0.6/debian/rules --- o/autofs-5.0.6/debian/rules 2012-04-23 17:13:10.0 +0200 +++ n/autofs-5.0.6/debian/rules 2012-06-01 16:56:38.607148473 +0200 @@ -7,7 +7,7 @@ dh $@ override_dh_auto_configure: - #autoconf --force + $(MAKE) configure dh_auto_configure -- \ --enable-forced-shutdown \ --enable-ignore-busy \ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674089: mime-support: removed application/x-httpd-* can lead to immense security problems
On Fri, 2012-06-01 at 16:16 +0200, Stefan Fritsch wrote: > I would vote for > the release notes plus Release notes is a good idea, Stefan, Brian... can anyone of you take care of this or should I (but I'm on vacation starting next Tue, so that would take some time). > either apache2 or mod_php NEWS file. It seems > exessive to have it in the mime-support NEWS file since it is just > noise to all non-apache2 users. I'm not sure whether I can agree... At least mod_php is not enough,... people seem to always forget that it's totally ok (and IMHO from a security point of view even much better) to run PHP as CGI. Neither am I sure, whether Apache is enough, there may be other webservers in Debian that could use mime.types (though I haven't checked this). In principle, as mime-types is the canonical location of the change, the safest place to put it, would be there. > see below. Stefan, you haven't commented on this... I've already opened #674205, where I ask the php people to include what I'd consider the "safest/best" way to handle PHP mime-type in Apache. IF mime.types will really ship no further definitions for PHP AND if that change is accordingly documented in release-notes/NEWS file(s) than I think there should be no definitions for PHP in Apache's default configs at all. > The x-httpd- types are really historic ballast from the time there was > no separate way to configure the handler (Apache 1.3.x or even 1.2.x). > Because of their special properties, they are called magic MIME types > in apache httpd. Therefore I think they should be considered an > internal (and deprecated) implementation detail of apache httpd and > should not be used as real MIME types anywhere else. If we see it from that point, and given that the types are */httpd-* then I'm in principle ok with your interpretation and dropping it from mime.types. But we should perhaps check (how?) whether any other packages have started to use that mime type (things like nautilus/file/etc.) > As #589384 explained, declaring them globally is bad for security. And > it would be really strange to set these magic types globally just to > remove them with "RemoveType php" again in the default apache2 > configuration. Agreed upon. I've added this just a s safety measure to remove any definitions for .php that are potentially already in place and are prone to the "foo.php.jpeg" problem. > But adding a different type for .php to /etc/mime.types is fine with > me. There is some discussion at http://cweiske.de/tagebuch/php- > mimetype.htm which type may be best. Both text/x-php and > application/x-php seem ok to me. As outlined before, I wouldn't use text/ anymore... and further... I'd strongly recommend against any type that is not and */x-* type... (unless there was an official delegation). OTOH,... there's no need to discuss such a type now, right? As soon as someone needs it, he will step up. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#674089: mime-support: removed application/x-httpd-* can lead to immense security problems
On 01.06.2012 17:21, Christoph Anton Mitterer wrote: > Neither am I sure, whether Apache is enough, there may be other > webservers in Debian that could use mime.types (though I haven't checked > this). Lighttpd - at very least - uses /etc/mime.types as well. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Processed (with 1 errors): merge 665487 664625
Processing commands for cont...@bugs.debian.org:
> merge 665487 664625
Bug #665487 [dovecot-managesieved] dovecot-managesieved: Error upgrading
dovecot with managesieved
Unable to merge bugs because:
severity of #664625 is 'important' not 'grave'
package of #664625 is 'dovecot-core' not 'dovecot-managesieved'
Failed to merge 665487: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x3004af0)',
'requester', 'Gedalya ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '<4fc8e23c.1080...@gedalya.net>',
'request_subject', ...) called at /usr/lib/debbugs/service line 872
eval {...} called at /usr/lib/debbugs/service line 871
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
664625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664625
665487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665487
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#621460: Accepted subversion 1.6.17dfsg-3.1 (source all amd64)
[OndÅej Surý] > I did reply you: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621460#34 > > and you didn't respond from that time at all. Yes, your reply was: | I thing it is reasonable that in your case it's probably better to | either depend directly on libdb5.1-dev + db5.1-util (and db4.8-util) | or on libdb-dev (>= 5.1), libdb-dev (<< 5.2), db-util (>= 5.1), | db-util (<< 5.2)." I agree (which is why I didn't reply). That is what I will do, but it is not what your NMU did. > There's really no reason to depend on specific libdbX.Y-dev version > and dbX.Y-util, you would only break the ability to do binNMUs when > needed to switch the default db version in the unstable archive. Correct. I don't want the DB version to change with a binNMU! If that were true, it would mean the new version, and the upgrade, has not been tested! I have good historical reason to believe that each new DB version _does_ need to be tested. 4.2 -> 4.3 -> 4.4 was quite unpleasant, and I don't trust Oracle not to do that again. Peter -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669246: zfs-fuse: fails to install due to insserv rejecting the script header
Package: zfs-fuse Version: 0.7.0-7 Followup-For: Bug #669246 Hi, since /etc/init.d/fuse does no longer exist, that dependency needs to be dropped from from the zfs-fuse initscript. Selecting previously unselected package zfs-fuse. (Reading database ... 7189 files and directories currently installed.) Unpacking zfs-fuse (from .../zfs-fuse_0.7.0-7_amd64.deb) ... Setting up zfs-fuse (0.7.0-7) ... invoke-rc.d: policy-rc.d denied execution of restart. insserv: Service fuse has to be enabled to start service zfs-fuse insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing zfs-fuse (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: zfs-fuse Andreas zfs-fuse_0.7.0-7.log.gz Description: GNU Zip compressed data
Bug#675474: marked as done (debiandoc-sgml: please rebuild to fix your copy of #477751)
Your message dated Fri, 01 Jun 2012 15:48:07 + with message-id and subject line Bug#675474: fixed in debiandoc-sgml 1.2.27 has caused the Debian Bug report #675474, regarding debiandoc-sgml: please rebuild to fix your copy of #477751 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.) -- 675474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debiandoc-sgml Severity: serious Dear maintainer(s) of debiandoc-sgml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut --- End Message --- --- Begin Message --- Source: debiandoc-sgml Source-Version: 1.2.27 We believe that the bug you reported is fixed in the latest version of debiandoc-sgml, which is due to be installed in the Debian FTP archive: debiandoc-sgml_1.2.27.dsc to main/d/debiandoc-sgml/debiandoc-sgml_1.2.27.dsc debiandoc-sgml_1.2.27.tar.gz to main/d/debiandoc-sgml/debiandoc-sgml_1.2.27.tar.gz debiandoc-sgml_1.2.27_all.deb to main/d/debiandoc-sgml/debiandoc-sgml_1.2.27_all.deb 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 675...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Osamu Aoki (supplier of updated debiandoc-sgml 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: Sat, 02 Jun 2012 00:12:58 +0900 Source: debiandoc-sgml Binary: debiandoc-sgml Architecture: source all Version: 1.2.27 Distribution: unstable Urgency: low Maintainer: Osamu Aoki Changed-By: Osamu Aoki Description: debiandoc-sgml - DebianDoc SGML DTD and formatting tools Closes: 675474 Changes: debiandoc-sgml (1.2.27) unstable; urgency=low . * Rebuild with debhelper sgml-base >=1.26+nmu2. Closes: #675474 Checksums-Sha1: b6c2757ede716e9ae27bfa3c44f63f42e06a92f9 956 debiandoc-sgml_1.2.27.dsc ad47464b3f1b025f3e612f307299dd996a00c1b3 122638 debiandoc-sgml_1.2.27.tar.gz 77419bffd2745d83241cf208d0408d30681ff021 129464 debiandoc-sgml_1.2.27_all.deb Checksums-Sha256: a8727968e62122822ad1b1c83bcdd4e3c56e0c161f4bc86f8f3016ef30d6c444 956 debiandoc-sgml_1.2.27.dsc d69984f781a2589b43aef74131a6ef43b252074bcd48d654436e57e4f683aa9b 122638 debiandoc-sgml_1.2.27.tar.gz f4c6e3f2ccde5f021359a13e38192c19f54b16775d6b0c14500a8caf9ef9ac37 129464 debiandoc-sgml_1.2.27_all.deb Files: 531ca20edd0ce03f83795aeeb0d502a2 956 text optional debiandoc-sgml_1.2.27.dsc ba23efd06c644cfe93a6420e55df1402 122638 text optional debiandoc-sgml_1.2.27.tar.gz 0a3796f809c7c84cdde190de867a 129464 text optional debiandoc-sgml_1.2.27_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/I31oACgkQ6A/EwagGHzKuGQCeLHLo5ihVX7SLJYz5ljoOFxI4 22sAn0FxvL1vpCcGbNa8ZO9eMrOLlYBW =kGKR -END PGP SIGNATURE- --- End Message ---
Bug#675489: python-docutils: please rebuild to fix your copy of #477751
* Helmut Grohne , 2012-06-01, 15:52: Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. Thanks. I'll upload the package in a few (< 3) days. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673263: Bug#590905: libmysqld-dev: Missing dependency or wrong flags in mysql_config
Rene Engelhard, le Wed 30 May 2012 09:41:28 +0200, a écrit : > Samuel, you probably should check all those and clean this up... They all work fine now indeed, closing the remainders. Samuel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672619: marked as done (gmysqlcc: FTBFS /usr/bin/ld: cannot find -lssl)
Your message dated Fri, 1 Jun 2012 18:00:54 +0200 with message-id <20120601160054.gj18...@type.bordeaux.inria.fr> and subject line Re: Bug#673263: Bug#590905: libmysqld-dev: Missing dependency or wrong flags in mysql_config has caused the Debian Bug report #672619, regarding gmysqlcc: FTBFS /usr/bin/ld: cannot find -lssl 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.) -- 672619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gmysqlcc Version: 0.3.0-2 Severity: serious Justification: FTBFS Hello, gmysqlcc currently FTBFS in sid: x86_64-linux-gnu-gcc -Wall -Wall -g -ggdb -Wl,-z,defs -o gmysqlcc gmlc_gui_helpers.o gmlc_gui_connexions.o gmlc_gui_server.o gmlc_gui_server_tab.o gmlc_gui_server_tab_data.o gmlc_gui_server_tab_help.o gmlc_gui_server_tab_query.o gmlc_main.o gmlc_misc_config.o gmlc_misc_hashtable.o gmlc_mysql_structure.o gmlc_mysql_server.o gmlc_mysql_query.o gmlc_mysql_database.o gmlc_mysql_table.o gmlc_mysql_view.o gmlc_mysql_procedure.o gmlc_mysql_function.o -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lgtksourceview-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -L/usr/lib/x86_64-linux-gnu -lmysqlclient -lpthread -lz -lm -lrt -lssl -lcrypto -ldl /usr/bin/ld: cannot find -lssl Samuel -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Thibault /* Amuse the user in a SPARC fashion */ if (err) printk( KERN_CRIT " ___ \n" KERN_CRIT " < Your System ate a SPARC! Gah! >\n" KERN_CRIT " --- \n" KERN_CRIT " \\ ^__^\n" KERN_CRIT " \\ (xx)\\___\n" KERN_CRIT " (__)\\ )\\/\\\n" KERN_CRIT " U ||w |\n" KERN_CRIT " || ||\n"); (From linux/arch/parisc/kernel/traps.c:die_if_kernel()) --- End Message --- --- Begin Message --- Rene Engelhard, le Wed 30 May 2012 09:41:28 +0200, a écrit : > Samuel, you probably should check all those and clean this up... They all work fine now indeed, closing the remainders. Samuel --- End Message ---
Bug#673262: marked as done (mydumper: FTBFS with multiarch libmysqlclient)
Your message dated Fri, 1 Jun 2012 18:00:54 +0200
with message-id <20120601160054.gj18...@type.bordeaux.inria.fr>
and subject line Re: Bug#673263: Bug#590905: libmysqld-dev: Missing dependency
or wrong flags in mysql_config
has caused the Debian Bug report #673262,
regarding mydumper: FTBFS with multiarch libmysqlclient
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.)
--
673262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mydumper
Version: 0.5.1-2
Severity: serious
Justification: FTBFS
Hello,
mydumper currently FTBFS in sid:
CMake Error: The following variables are used in this project, but they are set
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake
files:
MYSQL_LIBRARIES_crypto
linked by target "mydumper" in directory /tmp/buildd/mydumper-0.5.1
linked by target "myloader" in directory /tmp/buildd/mydumper-0.5.1
MYSQL_LIBRARIES_inux-gnu
linked by target "mydumper" in directory /tmp/buildd/mydumper-0.5.1
linked by target "myloader" in directory /tmp/buildd/mydumper-0.5.1
MYSQL_LIBRARIES_ssl
linked by target "mydumper" in directory /tmp/buildd/mydumper-0.5.1
linked by target "myloader" in directory /tmp/buildd/mydumper-0.5.1
Full log is attached.
Samuel
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
Samuel Thibault
make
oops
make clean
W: /home/samy/.pbuilderrc does not exist
dpkg-buildpackage: source package mydumper
dpkg-buildpackage: source version 0.5.1-2
dpkg-buildpackage: source changed by Mateusz Kijowski
dpkg-source -i -I --before-build mydumper-0.5.1
fakeroot debian/rules clean
dh clean --with sphinxdoc
dh_testdir
dh_auto_clean
dh_clean
rm -f debian/mydumper.substvars
rm -f debian/mydumper.*.debhelper
rm -rf debian/mydumper/
rm -f debian/*.debhelper.log
rm -f debian/files
find . \( \( -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} \; \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} \; \)
\)
rm -f *-stamp
dpkg-source -i -I -b mydumper-0.5.1
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building mydumper using existing ./mydumper_0.5.1.orig.tar.gz
dpkg-source: info: building mydumper in mydumper_0.5.1-2.debian.tar.gz
dpkg-source: info: building mydumper in mydumper_0.5.1-2.dsc
dpkg-genchanges -S >../mydumper_0.5.1-2_source.changes
dpkg-genchanges: not including original source code in upload
dpkg-source -i -I --after-build mydumper-0.5.1
dpkg-buildpackage: binary and diff upload (original source NOT included)
W: /home/samy/.pbuilderrc does not exist
I: using fakeroot in build.
I: Current time: Thu May 17 12:48:14 CEST 2012
I: pbuilder-time-stamp: 1337251694
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /dev/pts filesystem
I: Mounting /var/cache/pbuilder/ccache
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Setting up ccache
I: Installing the build-deps
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (>= 8.0.0), cmake, quilt, libmysqlclient-dev,
libglib2.0-dev, libpcre3-dev, zlib1g-dev, python-sphinx (>= 1.0.7+dfsg),
python-docutils
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in
`/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 11946 files and direc
