Bug#643521: libexml-java: FTBFS: XXX

Source: libexml-java Version: 0.0.20080703-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643522: libflexdock-java: FTBFS: JAVA_HOME not defined correctly.

Source: libflexdock-java Version: 0.5.2-dfsg1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643524: libjboss-deployers-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjboss-deployers-java Version: 2.0.4.GA-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643525: libjboss-microcontainer-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjboss-microcontainer-java Version: 2.0.10.GA-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant

Bug#643527: libjboss-xml-binding-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjboss-xml-binding-java Version: 2.0.3.GA-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant

Bug#643526: libjboss-web-services-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjboss-web-services-java Version: 0.0+svn5660+dak2-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64.

Bug#643529: libjgroups-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjgroups-java Version: 2.7.0.GA-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643530: libjgroups2.6-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjgroups2.6-java Version: 2.6.15.GA-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643531: libjibx1.1-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjibx1.1-java Version: 1.1.6a-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643532: libjibx1.2-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjibx1.2-java Version: 1.2.3-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot

Bug#643533: libjogl-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjogl-java Version: 1.1.1+dak1-10 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643534: libjrosetta-java: FTBFS: JAVA_HOME not defined correctly.

Source: libjrosetta-java Version: 1.0.2+gpl-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643535: liblastfm-java: FTBFS: JAVA_HOME not defined correctly.

Source: liblastfm-java Version: 1:0.1.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643536: libskinlf-java: FTBFS: JAVA_HOME not defined correctly.

Source: libskinlf-java Version: 6.7-7 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot

Bug#643538: mathpiper: FTBFS: JAVA_HOME not defined correctly.

Source: mathpiper Version: 0.0.svn2556-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot

Bug#643537: lwjgl: FTBFS: JAVA_HOME not defined correctly.

Source: lwjgl Version: 2.7.1+dfsg-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules

Bug#643539: omegat-plugin-tokenizer: FTBFS: JAVA_HOME not defined correctly.

Source: omegat-plugin-tokenizer Version: 0.4.2+dfsg-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant

Bug#643540: omegat: FTBFS: JAVA_HOME not defined correctly.

Source: omegat Version: 2.3.0.1+dfsg-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643541: maven-antrun-plugin: FTBFS: Error building POM

Source: maven-antrun-plugin Version: 1.6-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO]

Bug#643542: maven-bundle-plugin: FTBFS: Error building POM

Source: maven-bundle-plugin Version: 2.3.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643543: maven-compiler-plugin: FTBFS: Error building POM

Source: maven-compiler-plugin Version: 2.0.2-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643544: maven-dependency-plugin: FTBFS: Error building POM

Source: maven-dependency-plugin Version: 2.1-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643545: maven-doxia-tools: FTBFS: There are test failures.

Source: maven-doxia-tools Version: 1.2.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO]

Bug#643546: maven-install-plugin: FTBFS: Error building POM

Source: maven-install-plugin Version: 2.3-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643547: maven-jar-plugin: FTBFS: Error building POM

Source: maven-jar-plugin Version: 2.2-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO]

Bug#643548: maven-plugin-tools: FTBFS: JAVA_HOME not defined correctly.

Source: maven-plugin-tools Version: 2.8-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643549: maven-repository-builder: FTBFS: There are test failures.

Source: maven-repository-builder Version: 1.0~alpha2-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643550: maven-resources-plugin: FTBFS: Error building POM

Source: maven-resources-plugin Version: 2.3-6 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643551: maven-scm: FTBFS: Failed to resolve artifact.

Source: maven-scm Version: 1.3-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO]

Bug#643552: maven-shade-plugin: FTBFS: Error building POM

Source: maven-shade-plugin Version: 1.2.1-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643553: maven-war-plugin: FTBFS: Error building POM

Source: maven-war-plugin Version: 2.1~beta1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part:

Bug#643555: plexus-velocity: FTBFS: There are test failures

Source: plexus-velocity Version: 1.1.7-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO]

Bug#643349: alpine: FTBFS: flocklnx.c:60:7: error: format not a string literal and no format arguments [-Werror=format-security]

Thanks for filing this bug. I will take a look and see what the best fix is. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#643556: gdb-mingw-w64: FTBFS: Unpack-time patching fails.

Source: gdb-mingw-w64 Version: 0.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build tar

Bug#643557: gtk+2.0: FTBFS: Failed to start xvfb.

Source: gtk+2.0 Version: 2.24.6-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering

Processed: retitle 643491 to animal-sniffer: FTBFS: Error while creating archive

Processing commands for cont...@bugs.debian.org: retitle 643491 animal-sniffer: FTBFS: Error while creating archive Bug #643491 [src:animal-sniffer] animal-sniffer: FTBFS: XXX Changed Bug title to 'animal-sniffer: FTBFS: Error while creating archive' from 'animal-sniffer: FTBFS: XXX' thanks

Processed: retitle 643492 to antlr-maven-plugin: FTBFS: Error building POM.

Processing commands for cont...@bugs.debian.org: retitle 643492 antlr-maven-plugin: FTBFS: Error building POM. Bug #643492 [src:antlr-maven-plugin] antlr-maven-plugin: FTBFS: XXX Changed Bug title to 'antlr-maven-plugin: FTBFS: Error building POM.' from 'antlr-maven-plugin: FTBFS: XXX' thanks

Processed: retitle 643493 to antlr3: FTBFS: Error building POM.

Processing commands for cont...@bugs.debian.org: retitle 643493 antlr3: FTBFS: Error building POM. Bug #643493 [src:antlr3] antlr3: FTBFS: XXX Changed Bug title to 'antlr3: FTBFS: Error building POM.' from 'antlr3: FTBFS: XXX' thanks Stopping processing here. Please contact me if you need

Processed: retitle 643521 to libexml-java: FTBFS: JAVA_HOME not defined correctly.

Processing commands for cont...@bugs.debian.org: retitle 643521 libexml-java: FTBFS: JAVA_HOME not defined correctly. Bug #643521 [src:libexml-java] libexml-java: FTBFS: XXX Changed Bug title to 'libexml-java: FTBFS: JAVA_HOME not defined correctly.' from 'libexml-java: FTBFS: XXX' thanks

Processed: retitle 643495 to bridge-method-injector: FTBFS: Error building POM.

Processing commands for cont...@bugs.debian.org: retitle 643495 bridge-method-injector: FTBFS: Error building POM. Bug #643495 [src:bridge-method-injector] bridge-method-injector: FTBFS: XXX Changed Bug title to 'bridge-method-injector: FTBFS: Error building POM.' from 'bridge-method-injector:

Bug#642731: marked as done (nodejs: FTBFS: make[1]: *** [test] Error 1)

Your message dated Tue, 27 Sep 2011 14:51:55 + with message-id e1r8z0l-0006xx...@franck.debian.org and subject line Bug#642731: fixed in nodejs 0.4.12-1 has caused the Debian Bug report #642731, regarding nodejs: FTBFS: make[1]: *** [test] Error 1 to be marked as done. This means that you

Bug#642566: marked as done (python-saga: doesn't depend on python)

Your message dated Tue, 27 Sep 2011 14:53:49 + with message-id e1r8z2b-0007mg...@franck.debian.org and subject line Bug#642566: fixed in saga 2.0.7+dfsg-2 has caused the Debian Bug report #642566, regarding python-saga: doesn't depend on python to be marked as done. This means that you claim

Bug#577435: marked as done (python-tdb: can be compiled by a wrong Python version)

Your message dated Tue, 27 Sep 2011 15:03:19 + with message-id e1r8zbn-000101...@franck.debian.org and subject line Bug#577435: fixed in tdb 1.2.9-4 has caused the Debian Bug report #577435, regarding python-tdb: can be compiled by a wrong Python version to be marked as done. This means that

Bug#642817: pyxnat: FTBFS: tests failed

Hi, Does the build machine have an internet connection? My package needs to connect to a database server to perform its tests. Best, Yannick Source: pyxnat Version: 0.9.0~dev0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs

Bug#643304: python-awn-extras: can't install: unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new'

Disclaimer: I'm not maintainer of this package. * nick black d...@qemfd.net, 2011-09-27, 02:17: Retrieving bug reports... Done Parsing Found/Fixed information... Done (Reading database ... 336028 files and directories currently installed.) Unpacking python-awn-extras (from

Bug#643473: python-kinterbasdb: FTBFS: _configtest.c:7:3: error: unknown type name 'useconds_t'

retitle 643473 python-kinterbasdb: FTBFS with firebird-dev (2.5) -- removed defines thanks -=| Didier Raboud, 27.09.2011 14:51:01 +0200 |=- _kiservices.c: In function '_init_kiservices_ibase_header_constants': _kiservices.c:809:3: error: 'isc_info_db_impl_isc_a' undeclared (first use

Bug#642812: marked as done (ibus-table-chinese: FTBFS: __main__.InvalidTableName: Value of NAME attribute)

Your message dated Tue, 27 Sep 2011 15:18:47 + with message-id e1r8zql-0002cd...@franck.debian.org and subject line Bug#642812: fixed in ibus-table-chinese 1.3.4-1 has caused the Debian Bug report #642812, regarding ibus-table-chinese: FTBFS: __main__.InvalidTableName: Value of NAME attribute

Bug#642928: marked as done (Problem with closures on kfreebsd-amd64)

Your message dated Tue, 27 Sep 2011 15:19:17 + with message-id e1r8zrf-0002qi...@franck.debian.org and subject line Bug#642928: fixed in libffi 3.0.10-1 has caused the Debian Bug report #642928, regarding Problem with closures on kfreebsd-amd64 to be marked as done. This means that you claim

Bug#642928: marked as done (Problem with closures on kfreebsd-amd64)

Your message dated Tue, 27 Sep 2011 15:19:31 + with message-id e1r8zrt-0002y5...@franck.debian.org and subject line Bug#642928: fixed in libffi 3.0.11~rc1-3 has caused the Debian Bug report #642928, regarding Problem with closures on kfreebsd-amd64 to be marked as done. This means that you

Bug#643304: python-awn-extras: can't install: unable to open '/usr/share/pyshared/awn/extras/__init__.py.dpkg-new'

Jakub Wilk jw...@debian.org writes: Disclaimer: I'm not maintainer of this package. * nick black d...@qemfd.net, 2011-09-27, 02:17: Retrieving bug reports... Done Parsing Found/Fixed information... Done (Reading database ... 336028 files and directories currently installed.) Unpacking

Bug#643435: lingot: FTBFS: lingot-gui-mainframe.c:245:8: error: format not a string literal and no format arguments [-Werror=format-security]

Hi Didier, Fixed: http://hg.savannah.gnu.org/hgweb/lingot/rev/07c7af181ae0 I'll ask the maintainer for a new package. Thanks!, Ibán. 2011/9/27 Didier Raboud o...@debian.org Source: lingot Version: 0.9.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags:

Bug#642817: pyxnat: FTBFS: tests failed

On 27/09/2011 16:32, Yannick SCHWARTZ wrote: Hi, Does the build machine have an internet connection? My package needs to connect to a database server to perform its tests. Your pacakge is supposed to build just find, even if network is down. I think that accessing wild network is

Bug#642817: pyxnat: FTBFS: tests failed

On 27/09/2011 17:50, Mehdi Dogguy wrote: On 27/09/2011 16:32, Yannick SCHWARTZ wrote: Hi, Does the build machine have an internet connection? My package needs to connect to a database server to perform its tests. Your pacakge is supposed to build just find, even if network is down.

Bug#643434: marked as done (libvformat: FTBFS: vf_writer.c:231:5: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Tue, 27 Sep 2011 16:02:57 + with message-id e1r8a7v-000112...@franck.debian.org and subject line Bug#643434: fixed in libvformat 1.13-9 has caused the Debian Bug report #643434, regarding libvformat: FTBFS: vf_writer.c:231:5: error: format not a string literal and no format

Bug#643454: pd-zexy: FTBFS: freadln.c:115:7: error: format not a string literal and no format arguments [-Werror=format-security]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-09-27 14:36, Didier Raboud wrote: This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. thanks for your bugreport. a new upstream release is available that has this problem fixed. i have

Processed: block 643343 with 642950

Processing commands for cont...@bugs.debian.org: block 643343 with 642950 Bug #643343 [src:abe] abe: FTBFS: Game.c:22:5: error: format not a string literal and no format arguments [-Werror=format-security] Was not blocked by any bugs. Added blocking bug(s) of 643343: 642950 thanks Stopping

Processed: block 643361 with 642950

Processing commands for cont...@bugs.debian.org: block 643361 with 642950 Bug #643361 [src:catdvi] catdvi: FTBFS: bytesex.c:39:17: error: format not a string literal and no format arguments [-Werror=format-security] Was not blocked by any bugs. Added blocking bug(s) of 643361: 642950 thanks

Processed: block 643395 with 642950

Processing commands for cont...@bugs.debian.org: block 643395 with 642950 Bug #643395 [src:gnubik] gnubik: FTBFS: src/menus.c:552:8: error: format not a string literal and no format arguments [-Werror=format-security] Was not blocked by any bugs. Added blocking bug(s) of 643395: 642950 thanks

Processed: block 643449 with 642950

Processing commands for cont...@bugs.debian.org: block 643449 with 642950 Bug #643449 [src:open-cobol] open-cobol: FTBFS: error.c:234:4: error: format not a string literal and no format arguments [-Werror=format-security] Was not blocked by any bugs. Added blocking bug(s) of 643449: 642950

Bug#643279: marked as done (libisfreetype-java: uninstallable: depends on non-existent libisnativec-5.2-java)

Your message dated Tue, 27 Sep 2011 16:32:22 + with message-id e1r8azy-00046p...@franck.debian.org and subject line Bug#643279: fixed in libisfreetype-java 5.3.20100629-3 has caused the Debian Bug report #643279, regarding libisfreetype-java: uninstallable: depends on non-existent

Bug#606642: marked as done (lilypond: fails to build with G++ 4.5)

Your message dated Tue, 27 Sep 2011 17:17:56 + with message-id e1r8bi4-0008jq...@franck.debian.org and subject line Bug#606642: fixed in lilypond 2.12.3-7.1 has caused the Debian Bug report #606642, regarding lilypond: fails to build with G++ 4.5 to be marked as done. This means that you

Bug#621879: marked as done (lilypond: FTBFS on kfreebsd-*: spacing-spanner.cc:41:35: error: expected primary-expression before '*' token)

Your message dated Tue, 27 Sep 2011 17:17:56 + with message-id e1r8bi4-0008jq...@franck.debian.org and subject line Bug#606642: fixed in lilypond 2.12.3-7.1 has caused the Debian Bug report #606642, regarding lilypond: FTBFS on kfreebsd-*: spacing-spanner.cc:41:35: error: expected

Bug#643569: isc-dhcp: FTBFS: error: redefinition of 'struct in6_pktinfo'

Package: src:isc-dhcp Version: 4.2.2-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: gcc -DHAVE_CONFIG_H -I. -I../includes -I.. -DLOCALSTATEDIR='/var'

Processed: tagging 642601, severity of 642601 is serious

Processing commands for cont...@bugs.debian.org: tags 642601 + wheezy sid Bug #642601 [update-manager] python2.7 incompatible use of locale.format Added tag(s) sid and wheezy. severity 642601 serious Bug #642601 [update-manager] python2.7 incompatible use of locale.format Severity set to

Bug#643570: ipsec-tools: FTBFS(kfreebsd): symbol change

Package: src:ipsec-tools Version: 1:0.8.0-6 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Hi! Your package failed to build on the kfreebsd-* buildds: --- debian/ipsec-tools.symbols

Bug#580548: marked as done (..find a new name, gmp-ecm got there (/usr/bin/ecm) first.)

Your message dated Tue, 27 Sep 2011 17:32:32 + with message-id e1r8bwc-0001xq...@franck.debian.org and subject line Bug#580548: fixed in ecm 1.00-2 has caused the Debian Bug report #580548, regarding ..find a new name, gmp-ecm got there (/usr/bin/ecm) first. to be marked as done. This means

Bug#606642: marked as done (lilypond: fails to build with G++ 4.5)

Your message dated Tue, 27 Sep 2011 17:33:39 + with message-id e1r8bxh-0001cb...@franck.debian.org and subject line Bug#606642: fixed in lilypond 2.14.2-1 has caused the Debian Bug report #606642, regarding lilypond: fails to build with G++ 4.5 to be marked as done. This means that you claim

Bug#621879: marked as done (lilypond: FTBFS on kfreebsd-*: spacing-spanner.cc:41:35: error: expected primary-expression before '*' token)

Your message dated Tue, 27 Sep 2011 17:33:39 + with message-id e1r8bxh-0001cb...@franck.debian.org and subject line Bug#606642: fixed in lilypond 2.14.2-1 has caused the Debian Bug report #606642, regarding lilypond: FTBFS on kfreebsd-*: spacing-spanner.cc:41:35: error: expected

Bug#642696: marked as done (apt-dater: FTBFS: apt-dater.c:74:12: error: 'LC_ALL' undeclared (first use in this function))

Your message dated Tue, 27 Sep 2011 17:47:10 + with message-id e1r8bkm-0003p6...@franck.debian.org and subject line Bug#642696: fixed in apt-dater 0.8.6-1 has caused the Debian Bug report #642696, regarding apt-dater: FTBFS: apt-dater.c:74:12: error: 'LC_ALL' undeclared (first use in this

Bug#643487: marked as done (maven-ant-tasks: FTBFS: dpkg-buildpackage: error: dpkg-source --after-build maven-ant-tasks-2.0.10 gave error exit status 1)

Your message dated Tue, 27 Sep 2011 17:48:07 + with message-id e1r8blh-0003sn...@franck.debian.org and subject line Bug#643487: fixed in maven-ant-tasks 2.1.3-1 has caused the Debian Bug report #643487, regarding maven-ant-tasks: FTBFS: dpkg-buildpackage: error: dpkg-source --after-build

Bug#643572: gnushogi: FTBFS: book.c:296:13: error: format not a string literal and no format arguments [-Werror=format-security]

Source: gnushogi Version: 1.3.2-7 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64.

Bug#643468: rubrica: FTBFS: app.c:1831:8: error: format not a string literal and no format arguments [-Werror=format-security]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/09/2011 14:37, Didier Raboud ha scritto: Hi, rubrica-2.0 is very old, you can find last stable release 2.0.10 on www.nicolafragale.org Ciao Nicola Fragale Source: rubrica Version: 2.0-1.1 Severity: serious Tags: wheezy sid User:

Bug#643503: marked as done (libquartz-java: FTBFS: Failed to resolve artifact.)

Your message dated Tue, 27 Sep 2011 18:17:55 + with message-id e1r8ce7-00077f...@franck.debian.org and subject line Bug#643503: fixed in libquartz-java 1.7.3-2 has caused the Debian Bug report #643503, regarding libquartz-java: FTBFS: Failed to resolve artifact. to be marked as done. This

Bug#643504: marked as done (libspring-ldap-java: FTBFS: Cannot open sRGB.pdf)

Your message dated Tue, 27 Sep 2011 20:32:05 +0200 with message-id calj2o_2b2-mgfrjdagmaqxtm5_sqbp1x5mpbfqdshwpislv...@mail.gmail.com and subject line Re: Bug#643504: libspring-ldap-java: FTBFS: Cannot open sRGB.pdf has caused the Debian Bug report #643504, regarding libspring-ldap-java: FTBFS:

Bug#642601: (no subject)

Yep, we fixed this in Ubuntu back in November. Here's the merge proposal at the time: https://code.launchpad.net/~barry/update-manager/673297-py27/+merge/40510 And the patch we applied (omitting debian/changelog): === modified file 'UpdateManager/Core/utils.py' --- UpdateManager/Core/utils.py

Bug#643345: marked as done (aee: FTBFS: aee.c:2496:3: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Tue, 27 Sep 2011 18:47:09 + with message-id e1r8cgp-0001fz...@franck.debian.org and subject line Bug#643345: fixed in aee 2.2.15b-5 has caused the Debian Bug report #643345, regarding aee: FTBFS: aee.c:2496:3: error: format not a string literal and no format arguments

Bug#643352: marked as done (arpalert: FTBFS: ./log.c:122:3: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Tue, 27 Sep 2011 18:47:23 + with message-id e1r8cgd-0001ia...@franck.debian.org and subject line Bug#643352: fixed in arpalert 2.0.11-7.1 has caused the Debian Bug report #643352, regarding arpalert: FTBFS: ./log.c:122:3: error: format not a string literal and no format

Bug#632494: marked as done (darcs: FTBFS (tests fail))

Your message dated Tue, 27 Sep 2011 19:02:30 + with message-id e1r8cvg-0004ke...@franck.debian.org and subject line Bug#632494: fixed in darcs 2.5.2-3 has caused the Debian Bug report #632494, regarding darcs: FTBFS (tests fail) to be marked as done. This means that you claim that the problem

Bug#642710: marked as done (darcs: FTBFS: etup: At least the following dependencies are missing regex-compat =0.71 0.94)

Your message dated Tue, 27 Sep 2011 19:02:30 + with message-id e1r8cvg-0004kj...@franck.debian.org and subject line Bug#642710: fixed in darcs 2.5.2-3 has caused the Debian Bug report #642710, regarding darcs: FTBFS: etup: At least the following dependencies are missing regex-compat =0.71

Bug#643576: antlr-doc: Examples have non-commercial clause

Package: antlr-doc Version: 2.7.7-16 Severity: serious Tags: upstream Justification: Policy 2.1.6 User: gnewsense-...@nongnu.org Usertags: libreplanet gnewsense In directory examples/java/unicode.IDENTs there are 2 files, ShowString.java and StreamConverter.java that have this license statement:

Processed: severity of 606724 is serious, tagging 606724, severity of 629145 is serious, tagging 629145 ...

Processing commands for cont...@bugs.debian.org: # http://packages.qa.debian.org/p/python-defaults/news/20110927T190906Z.html severity 606724 serious Bug #606724 [cyphesis-cpp] cyphesis-cpp: Please add support for Python 2.7 detection Severity set to 'serious' from 'important' tags 606724 +

Bug#642601: marked as done (python2.7 incompatible use of locale.format)

Your message dated Tue, 27 Sep 2011 19:19:38 + with message-id e1r8dbq-0008ak...@franck.debian.org and subject line Bug#642601: fixed in update-manager 0.200.5-2 has caused the Debian Bug report #642601, regarding python2.7 incompatible use of locale.format to be marked as done. This means

Bug#643407: marked as done (infernal: FTBFS: esl_getopts.c:1273:2: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Tue, 27 Sep 2011 19:17:29 + with message-id e1r8d9l-0007se...@franck.debian.org and subject line Bug#643407: fixed in infernal 1.0.2-2 has caused the Debian Bug report #643407, regarding infernal: FTBFS: esl_getopts.c:1273:2: error: format not a string literal and no format

Bug#643460: marked as done (qfits: FTBFS: hierarch28.c:576:5: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Tue, 27 Sep 2011 19:49:46 + with message-id e1r8df0-0004zi...@franck.debian.org and subject line Bug#643460: fixed in qfits 6.2.0-5 has caused the Debian Bug report #643460, regarding qfits: FTBFS: hierarch28.c:576:5: error: format not a string literal and no format

Bug#636166: exiftran: dies with Segmentation fault when rotating an image

On Thu, Sep 22, 2011 at 12:18:22PM +0100, Steve Cotton wrote: package exiftran tags 636166 +fixed-upstream thanks Upstream version 2.08 adds support for libjpeg8. As a patch, copying the files from 2.08's jpeg/80/ to 2.07's jpeg/ worked for me, without copying any of the makefile

Processed: severity of 639875 is serious

Processing commands for cont...@bugs.debian.org: # uninstallable in sid, soon removed from testing severity 639875 serious Bug #639875 [fglrx-driver] fglrx-driver: xorg-video-abi-11 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need

Processed: severity of 641621 is serious

Processing commands for cont...@bugs.debian.org: # uninstallable in sid, soon removed from testing severity 641621 serious Bug #641621 [xserver-xorg-video-nvidia-legacy-173xx] missing support for xorg-video-abi-11, does not install with Xorg Xserver 1.11.0 Severity set to 'serious' from

Processed: cloning 641621, reassign -1 to xserver-xorg-video-nvidia-legacy-96xx

Processing commands for cont...@bugs.debian.org: clone 641621 -1 Bug#641621: missing support for xorg-video-abi-11, does not install with Xorg Xserver 1.11.0 Bug 641621 cloned as bug 643584. reassign -1 xserver-xorg-video-nvidia-legacy-96xx 96.43.20-2 Bug #643584

Bug#554554: closed by Michael Biebl bi...@debian.org (FTBFS with binutils-gold)

On Tue, Sep 27, 2011 at 00:50:43 +0200, Jakub Wilk wrote: Version: 3.10.0-2 Hmm, glade has no such version as far as I can see... $ dak ls -s unstable glade glade | 3.10.0-2 | unstable | source, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel,

Bug#554554: closed by Michael Biebl bi...@debian.org (FTBFS with binutils-gold)

* Julien Cristau jcris...@debian.org, 2011-09-27, 22:38: Version: 3.10.0-2 Hmm, glade has no such version as far as I can see... $ dak ls -s unstable glade glade | 3.10.0-2 | unstable | source, amd64, armel, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel,

Bug#565088: marked as done (nitpic: ftbfs with gcc-4.5)

Your message dated Tue, 27 Sep 2011 20:54:04 + with message-id e1r8efe-0002w1...@franck.debian.org and subject line Bug#565088: fixed in nitpic 0.1-12 has caused the Debian Bug report #565088, regarding nitpic: ftbfs with gcc-4.5 to be marked as done. This means that you claim that the

Bug#625756: electric-fence: FTBFS due to OOM with gcc-4.5

On 19/09/11 15:55, Colin Watson wrote: On Thu, Sep 08, 2011 at 06:14:49PM +0100, Colin Watson wrote: * Build with -fno-tree-dse, since otherwise GCC= 4.5 misoptimises allocateMoreSlots() (closes: #625756, LP: #749139). In fact, as GCC upstream pointed out, a more targeted - and I

Processed: Re: Bug#632494 closed by Iain Lane la...@debian.org (Bug#632494: fixed in darcs 2.5.2-3)

Processing commands for cont...@bugs.debian.org: reopen 632494 = Bug #632494 {Done: Iain Lane la...@debian.org} [darcs] darcs: FTBFS (tests fail) 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. thanks Stopping

Bug#643493: marked as done (antlr3: FTBFS: Error building POM.)

Your message dated Tue, 27 Sep 2011 21:19:38 + with message-id e1r8f3y-0006mx...@franck.debian.org and subject line Bug#643493: fixed in antlr3 3.2-6 has caused the Debian Bug report #643493, regarding antlr3: FTBFS: Error building POM. to be marked as done. This means that you claim that the

Bug#643570: ipsec-tools: FTBFS(kfreebsd): symbol change

Hi Setting up a Debian kfreebsd sid VM to get this sorted on the weekend. If you want to help, can give you ssh access. Cheers, Matthew On Wed, Sep 28, 2011 at 6:28 AM, Christoph Egger christ...@debian.orgwrote: Package: src:ipsec-tools Version: 1:0.8.0-6 Severity: serious Tags: sid

Bug#632494: closed by Iain Lane la...@debian.org (Bug#632494: fixed in darcs 2.5.2-3)

reopen 632494 = thanks Hello, On Tue, Sep 27, 2011 at 07:03:05PM +, Debian Bug Tracking System wrote: […] We believe that the bug you reported is fixed in the latest version of darcs, which is due to be installed in the Debian FTP archive: No, it clearly was not. Reopening. Cheers, --

Processed: tagging 642912

Processing commands for cont...@bugs.debian.org: tags 642912 - moreinfo Bug #642912 [network-manager] network-manager 0.9.0-2 fails with numeric SSIDs Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 642912:

Processed: tagging 642912

Processing commands for cont...@bugs.debian.org: tags 642912 + moreinfo Bug #642912 [network-manager] network-manager 0.9.0-2 fails with numeric SSIDs Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 642912:

Bug#636802: fpc fails to link against libc on some architectures, due to multiarch

Over a month ago I posted a patch to add the new (multiarch) directory containing crti.o to the default fpc.cfg. Without this patch (or an equivilent manual config edit or manual command line parameter) freepascal will (silently) fail to include include crti.o in the linker script and this

Bug#617514: MeetMe() does not accept any options after Answer() and falls back to default options.

severety 617514 normal tag 617514 + moreinfo unreproducible thanks Sorry for the delay, On Wed, Mar 09, 2011 at 03:25:34PM +0100, Julius Kempa wrote: Package: asterisk Version: 1:1.6.2.9-2+squeeze1 Severity: critical MeetMe application does not work properly. for example:

<    1   2   3   4   >