Bug#667664: marked as done (libpcre3: upgrade from 8.12 to 8.30 breaks (oldstable-era) dansguardian)
Your message dated Sun, 24 Jun 2012 07:17:48 + with message-id e1sih4u-0003jq...@franck.debian.org and subject line Bug#667664: fixed in dansguardian 2.10.1.1-5 has caused the Debian Bug report #667664, regarding libpcre3: upgrade from 8.12 to 8.30 breaks (oldstable-era) dansguardian 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.) -- 667664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libpcre3 Version: 1:8.30-4 Severity: normal X-Debbugs-CC: dansguard...@packages.debian.org Disclaimer: I am still using an old dansguardian (2.9.9.7-2.1, last pre-2.10 packaged version) because http://bugs.debian.org/536778 which in itself is a blow in the face of us developers, but that's another story which *should not* be related to compatibility breakages... After upgrading from 8.12-4 and restarting dansguardian (thanks logrotate), dansguardian began refusing virtually all pages. The cause appears to be any non-commented-out pattern from the bannedregexpurllist file. After downgrading just libpcre3 back to 8.12-4, it starts working again. Now dansguardian does not have a lot of debug traces to activate, and I didn't look at the libpcre API yet. Any idea of a particular change that could cause such a breakage ? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpcre3 depends on: ii libc6 2.13-27 ii multiarch-support 2.13-27 libpcre3 recommends no packages. libpcre3 suggests no packages. -- no debconf information -- debsums errors found: debsums: package libpcre3 is not installed ---End Message--- ---BeginMessage--- Source: dansguardian Source-Version: 2.10.1.1-5 We believe that the bug you reported is fixed in the latest version of dansguardian, which is due to be installed in the Debian FTP archive: dansguardian_2.10.1.1-5.diff.gz to main/d/dansguardian/dansguardian_2.10.1.1-5.diff.gz dansguardian_2.10.1.1-5.dsc to main/d/dansguardian/dansguardian_2.10.1.1-5.dsc dansguardian_2.10.1.1-5_amd64.deb to main/d/dansguardian/dansguardian_2.10.1.1-5_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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Wirt formo...@debian.org (supplier of updated dansguardian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 24 Jun 2012 09:02:21 +0200 Source: dansguardian Binary: dansguardian Architecture: source amd64 Version: 2.10.1.1-5 Distribution: unstable Urgency: low Maintainer: Alexander Wirt formo...@debian.org Changed-By: Alexander Wirt formo...@debian.org Description: dansguardian - Web content filtering Closes: 544654 597961 647870 667664 673691 Changes: dansguardian (2.10.1.1-5) unstable; urgency=low . * [0a5a03b] Add support for status action to init.d script. Thanks to Peter Eisentraut for the patch (Closes: #647870) * [f41be8c] Don't allocate memory up to reg.re_nsub (Closes: #667664, #673691) * [2ebb4bb] Remove obsolete preinst script (Closes: #597961) * [3d01758] Document grouphandling for clamdscan (Closes: #544654) * [0da0019] Add versioned dpatch dependency * [05242c0] wrap-and-sort * [817abff] Use dh9 for hardening Checksums-Sha1: 2748baf4c5ee8999887277e83dd57a26b676519d 1271 dansguardian_2.10.1.1-5.dsc e565daa24f9bfa383ea44e1ea5ab4d595891d202 23219 dansguardian_2.10.1.1-5.diff.gz 1caf197e46659e267efe2ff2cf6facba1f994afb 473182 dansguardian_2.10.1.1-5_amd64.deb Checksums-Sha256: 45707e73ad26b2ab26d90caf5c33037af0fd7cfe68b5d6af3ffea880dd500246 1271 dansguardian_2.10.1.1-5.dsc f211ae3e5e0ff5511e019b5eef6b43a2bf5573b8332d1d0b8418315ba3b432b1 23219 dansguardian_2.10.1.1-5.diff.gz 2df2d83343ca88304900ce819774691ba371c651726ee5ef3616bbe7483d9970 473182 dansguardian_2.10.1.1-5_amd64.deb Files: 5123021d3f52e9b00560a2d5e85d9495 1271 web optional
Bug#670776: marked as done (dansguardian ERR_EMPTY_RESPONSE libpcre3 bug)
Your message dated Sun, 24 Jun 2012 07:17:48 + with message-id e1sih4u-0003jq...@franck.debian.org and subject line Bug#667664: fixed in dansguardian 2.10.1.1-5 has caused the Debian Bug report #667664, regarding dansguardian ERR_EMPTY_RESPONSE libpcre3 bug 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.) -- 667664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dansguardian Version: 2.10.1.1-4 Severity: critical Justification: dansguardian not working anymore Using latest wheezy amd64 branch. Dansguardian is totally unusable. Each request is getting ERR_EMPTY_RESPONSE. The only workaround is to install libpcre3 from squeeze. More details at http://translate.googleusercontent.com/translate_c?hl=iwrurl=translate.google.co.ilsl=detl=entwu=1u=http://debianforum.de/forum/viewtopic.php%3Ff%3D18%26t%3D135441%26sid%3D8ba71c9deaab59c704516069b396190d%26start%3D15usg=ALkJrhiqpLmHbTiQKM_dMmhPRvJmB7MJMw#p877628 ---End Message--- ---BeginMessage--- Source: dansguardian Source-Version: 2.10.1.1-5 We believe that the bug you reported is fixed in the latest version of dansguardian, which is due to be installed in the Debian FTP archive: dansguardian_2.10.1.1-5.diff.gz to main/d/dansguardian/dansguardian_2.10.1.1-5.diff.gz dansguardian_2.10.1.1-5.dsc to main/d/dansguardian/dansguardian_2.10.1.1-5.dsc dansguardian_2.10.1.1-5_amd64.deb to main/d/dansguardian/dansguardian_2.10.1.1-5_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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Wirt formo...@debian.org (supplier of updated dansguardian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 24 Jun 2012 09:02:21 +0200 Source: dansguardian Binary: dansguardian Architecture: source amd64 Version: 2.10.1.1-5 Distribution: unstable Urgency: low Maintainer: Alexander Wirt formo...@debian.org Changed-By: Alexander Wirt formo...@debian.org Description: dansguardian - Web content filtering Closes: 544654 597961 647870 667664 673691 Changes: dansguardian (2.10.1.1-5) unstable; urgency=low . * [0a5a03b] Add support for status action to init.d script. Thanks to Peter Eisentraut for the patch (Closes: #647870) * [f41be8c] Don't allocate memory up to reg.re_nsub (Closes: #667664, #673691) * [2ebb4bb] Remove obsolete preinst script (Closes: #597961) * [3d01758] Document grouphandling for clamdscan (Closes: #544654) * [0da0019] Add versioned dpatch dependency * [05242c0] wrap-and-sort * [817abff] Use dh9 for hardening Checksums-Sha1: 2748baf4c5ee8999887277e83dd57a26b676519d 1271 dansguardian_2.10.1.1-5.dsc e565daa24f9bfa383ea44e1ea5ab4d595891d202 23219 dansguardian_2.10.1.1-5.diff.gz 1caf197e46659e267efe2ff2cf6facba1f994afb 473182 dansguardian_2.10.1.1-5_amd64.deb Checksums-Sha256: 45707e73ad26b2ab26d90caf5c33037af0fd7cfe68b5d6af3ffea880dd500246 1271 dansguardian_2.10.1.1-5.dsc f211ae3e5e0ff5511e019b5eef6b43a2bf5573b8332d1d0b8418315ba3b432b1 23219 dansguardian_2.10.1.1-5.diff.gz 2df2d83343ca88304900ce819774691ba371c651726ee5ef3616bbe7483d9970 473182 dansguardian_2.10.1.1-5_amd64.deb Files: 5123021d3f52e9b00560a2d5e85d9495 1271 web optional dansguardian_2.10.1.1-5.dsc 7a5f5e539dde31e2a51dad4e7ad01a73 23219 web optional dansguardian_2.10.1.1-5.diff.gz c325dcf3942ce5b1fc508565593bf214 473182 web optional dansguardian_2.10.1.1-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/mu9YACgkQ01u8mbx9Agq3DgCgocf8XqwyjgW8TjeZP0CRqvj3 Dk0AoMDNqfm+ZYZCAz+hKwn6KAciNC2D =9eXv -END PGP SIGNATURE- ---End Message---
Bug#677864: srsly?
Are we really sure it's a service to debian users or debian as a distribution to simply remove compiz from wheezy based on a number of minor(?) issues that are so obscure that they needed a fake RC bug? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678737: Cross site request forgery
Package: extplorer Severity: grave As per: http://www.autosectools.com/Advisories/eXtplorer.2.1.RC3_Cross-site.Request.Forgery_174.html there's a CSRF security issue in eXtplorer. Patch is on its way, I'm just opening a bug report to track it. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Sunday 24 June 08:03:30 UTC 2012 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: libsidplayfp tags 678700 + pending Bug #678700 [wnpp] ITP: libsidplayfp -- Library to play Commodore 64 music based on libsidplay2 Added tag(s) pending. # Source package in NEW: sidplayfp tags 678699 + pending Bug #678699 [wnpp] ITP: sidplayfp -- Fork of sidplay2, a C64 and C128 music player Added tag(s) pending. # Source package in NEW: a href=http://packages.qa.debian.org/roundcube;roundcube/a tags 677803 + pending Bug #677803 [roundcube] roundcube: Could not perform immediate configuration on 'roundcube-mysql'. Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 677803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677803 678699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678699 678700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678700 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#677202: biber packages version 0.9.9+git2012426-3 is beta and requires beta version of biblatex
Danai,
On Di, 19 Jun 2012, Danai SAE-HAN wrote:
Urgh, just got a half working X.org env.
Still skewed, but slightly workable.
Thanks for your patience. Off to work now.
Any progress here? Freeze is soon!
Did you also see the email of Werner concerning a stability fix
in CJK?
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
`The best way to get a drink out of a Vogon is to stick
your finger down his throat...'
--- The Book, on one of the Vogon's social inadequacies.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678484: cannot upgrade
On So, 24 Jun 2012, jida...@jidanni.org wrote:
reopen 678484
Yes, I know. I have to upload a version of maildir-utils that
conflcits with mailutils ... on the way .
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
BLITHBURY
A look someone gives you by which you become aware that they're much
too drunk to have understood anything you've said to them in the last
twenty minutes.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678746: desktop-base: Joy theme is a mix of incompatibly-licensed works
Package: desktop-base Version: 7.0.0~exp2 Severity: serious Justification: Policy 2.3 Hello, I read about the new Joy theme [1][2]. [1] http://blog.pault.ag/post/25614704596/my-quest-to-get-desktop-base-set-before-wheezy [2] http://blog.pault.ag/post/25747178764/debian-desktop-7-0-0-exp2-in-experimental It looks nice, but it seems to have licensing issues. In the debian/copyright file [3] I read: | The Joy theme is © 2012 Adrien Aubourg and released under the CC-BY-SA 3.0 | license. | | The Joy plymouth theme is Copyright © 2009 Canonical Ltd., | Copyright © 2010 Aurélien COUDERC and Copyright © 2012 Jonathan Carter under | the GPLv2+, with work from Adrien Aubourg under the CC-BY-SA 3.0 License. | | The Joy KDM, GDM and KSplash grub theme are © 2012 Paul Tagliamonte and released | under the CC-BY-SA 3.0 license, with work from all the previous authors, and | Adrien Aubourg. [3] http://packages.debian.org/changelogs/pool/main/d/desktop-base/desktop-base_7.0.0~exp2/copyright First of all, these debian/copyright paragraphs fail to acknowledge that the Joy theme is based on the Debian “Open Use” (without “Debian” word) logo. But this may be fixed easily. The major issue seems to be that the Joy plymouth theme mixes parts released under CC-by-sa-v3.0 and parts released under GPLv2+. Since CC-by-sa-v3.0 is incompatible with GPLv2+, I would say that the resulting work is legally undistributable. The same issue seems to hold for the Joy KDM, GDM and KSplash grub theme, since it said to incorporate work from all the previous authors. If all the previous authors includes Aurélien COUDERC and/or Jonathan Carter, it seems that their work is under GPLv2+ and thus the incompatibility of CC-by-sa-v3.0 again kicks in. (For the record, I am also convinced that CC-by-sa-v3.0 fails to meet the DFSG, but that's another story, since FTP masters disagree with me, unfortunately). I hope the incompatibility issue may be fixed soon for the Joy theme. Since everything else in the desktop-base package is GPL-compatible, I strongly recommend to persuade Adrien Aubourg and Paul Tagliamonte to re-license their work under the terms of the GNU GPL v2 or later. Or, at least, to dual-license it under CC-by-sa-v3.0 and GPLv2+. (In the latter case, the complete text of CC-by-sa-v3.0 should be included in the debian/copyright file, though.) Bye and thanks for your time. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678484: marked as done (mailutils and maildir-utils: error when trying to install together)
Your message dated Sun, 24 Jun 2012 09:17:55 + with message-id e1siix9-0005an...@franck.debian.org and subject line Bug#678484: fixed in maildir-utils 0.9.8.4-3 has caused the Debian Bug report #678484, regarding mailutils and maildir-utils: error when trying to install together 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.) -- 678484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: maildir-utils,mailutils Version: maildir-utils/0.9.8.4-2 Version: mailutils/1:2.99.97-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-22 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libkeyutils1 libkrb5support0 libk5crypto3 libkrb5-3 libgssapi-krb5-2 libsasl2-2 libldap-2.4-2 libpcre3 libwrap0 libexpat1 libffi5 libfribidi0 libglib2.0-0 libgmp10 libltdl7 mysql-common libmysqlclient18 exim4-config exim4-base exim4-daemon-light mime-support guile-1.8-libs libpth20 libgpgme11 libgmime-2.6-0 libntlm0 libgsasl7 mailutils-common python2.7-minimal python2.7 libpython2.7 libmailutils4 maildir-utils mailutils Extracting templates from packages: 88% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libkeyutils1:amd64. (Reading database ... 10726 files and directories currently installed.) Unpacking libkeyutils1:amd64 (from .../libkeyutils1_1.5.5-2_amd64.deb) ... Selecting previously unselected package libkrb5support0:amd64. Unpacking libkrb5support0:amd64 (from .../libkrb5support0_1.10.1+dfsg-1_amd64.deb) ... Selecting previously unselected package libk5crypto3:amd64. Unpacking libk5crypto3:amd64 (from .../libk5crypto3_1.10.1+dfsg-1_amd64.deb) ... Selecting previously unselected package libkrb5-3:amd64. Unpacking libkrb5-3:amd64 (from .../libkrb5-3_1.10.1+dfsg-1_amd64.deb) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Unpacking libgssapi-krb5-2:amd64 (from .../libgssapi-krb5-2_1.10.1+dfsg-1_amd64.deb) ... Selecting previously unselected package libsasl2-2:amd64. Unpacking libsasl2-2:amd64 (from .../libsasl2-2_2.1.25.dfsg1-4+b1_amd64.deb) ... Selecting previously unselected package libldap-2.4-2:amd64. Unpacking libldap-2.4-2:amd64 (from .../libldap-2.4-2_2.4.28-1.3_amd64.deb) ... Selecting previously unselected package libpcre3:amd64. Unpacking libpcre3:amd64 (from .../libpcre3_1%3a8.30-5_amd64.deb) ... Selecting previously unselected package libwrap0:amd64. Unpacking libwrap0:amd64 (from .../libwrap0_7.6.q-23_amd64.deb) ... Selecting previously unselected package libexpat1:amd64. Unpacking libexpat1:amd64 (from .../libexpat1_2.1.0-1_amd64.deb) ... Selecting previously unselected package libffi5:amd64. Unpacking libffi5:amd64 (from .../libffi5_3.0.10-3_amd64.deb) ... Selecting previously unselected package libfribidi0:amd64. Unpacking libfribidi0:amd64 (from .../libfribidi0_0.19.2-3_amd64.deb) ... Selecting previously unselected package libglib2.0-0:amd64. Unpacking libglib2.0-0:amd64 (from .../libglib2.0-0_2.32.3-1_amd64.deb) ... Selecting previously unselected package libgmp10:amd64. Unpacking libgmp10:amd64 (from .../libgmp10_2%3a5.0.5+dfsg-2_amd64.deb) ... Selecting previously unselected package libltdl7:amd64. Unpacking libltdl7:amd64 (from .../libltdl7_2.4.2-1.1_amd64.deb) ... Selecting previously unselected package mysql-common. Unpacking mysql-common (from .../mysql-common_5.5.24+dfsg-4_all.deb) ... Selecting previously unselected package libmysqlclient18:amd64. Unpacking libmysqlclient18:amd64 (from .../libmysqlclient18_5.5.24+dfsg-4_amd64.deb) ... Selecting previously unselected package exim4-config. Unpacking exim4-config (from .../exim4-config_4.80-3_all.deb) ... Selecting previously unselected package exim4-base. Unpacking exim4-base (from .../exim4-base_4.80-3_amd64.deb) ... Selecting previously unselected package exim4-daemon-light. Unpacking exim4-daemon-light (from .../exim4-daemon-light_4.80-3_amd64.deb) ... Selecting previously unselected package mime-support. Unpacking mime-support (from .../mime-support_3.52-1_all.deb) ... Selecting previously unselected package guile-1.8-libs. Unpacking guile-1.8-libs (from .../guile-1.8-libs_1.8.8+1-8_amd64.deb) ... Selecting previously
Bug#678750: argyll: FTBFS: ld: cannot find -lconv
Source: argyll Version: 1.4.0-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -DUNIX -I../cgats -I../gamut -I../h -I../jcnf -I../libusb1/libusb -I../numlib -I../plot -I../profile -I../render -I../rspl -I../spectro -I../target -I../ucmm -I../xicc -I../icc -I../jcnf/yajl -L../spectro -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c ctest.c In file included from imdi.h:20:0, from ctest.c:15: imdi_utl.h:36:9: note: #pragma message: Using 64 bit integer color kernel /bin/bash ../libtool --tag=CC --mode=link gcc -D_GNU_SOURCE -DUNIX -I../cgats -I../gamut -I../h -I../jcnf -I../libusb1/libusb -I../numlib -I../plot -I../profile -I../render -I../rspl -I../spectro -I../target -I../ucmm -I../xicc -I../icc -I../jcnf/yajl -L../spectro -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -o ctest ctest.o cgen.o -lrt -lpthread -lm libtool: link: gcc -D_GNU_SOURCE -DUNIX -I../cgats -I../gamut -I../h -I../jcnf -I../libusb1/libusb -I../numlib -I../plot -I../profile -I../render -I../rspl -I../spectro -I../target -I../ucmm -I../xicc -I../icc -I../jcnf/yajl -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,--as-needed -Wl,--no-undefined -o ctest ctest.o cgen.o -L../spectro -lrt -lpthread -lm make[4]: Leaving directory `/«PKGBUILDDIR»/imdi' fakeroot debian/rules binary make[3]: Leaving directory `/«PKGBUILDDIR»/imdi' make[2]: Leaving directory `/«PKGBUILDDIR»/imdi' make[1]: Leaving directory `/«PKGBUILDDIR»' dh binary --with quilt dh_testroot dh_prep dh_installdirs debian/rules override_dh_auto_install make[1]: Entering directory `/«PKGBUILDDIR»' chmod +x firmware-package-builder/argyll-firmware-spyder2/debian/rules tar cfCz firmware-package-builder/spyder2.tar.gz firmware-package-builder argyll-firmware-spyder2 /usr/bin/make install -i DESTDIR=/«PKGBUILDDIR»/debian/tmp make[2]: Entering directory `/«PKGBUILDDIR»' Making install in h make[3]: Entering directory `/«PKGBUILDDIR»/h' make[4]: Entering directory `/«PKGBUILDDIR»/h' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/«PKGBUILDDIR»/h' make[3]: Leaving directory `/«PKGBUILDDIR»/h' Making install in doc make[3]: Entering directory `/«PKGBUILDDIR»/doc' make[4]: Entering directory `/«PKGBUILDDIR»/doc' make[4]: Nothing to be done for `install-exec-am'. /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/share/doc/argyll' /usr/bin/install -c -m 644 DocLicense.txt License.txt License2.txt License3.txt SG_footer.txt SG_header.txt ArgyllDoc.html ChangesSummary.html ColorManagement.html Compiling.html CrushedDisplyBlacks.html Environment.html FWA.html File_Formats.html Installing.html Installing_Linux.html Installing_MSWindows.html Installing_OSX.html Limitations.html MinorTools.html Organisation.html Overview.html Performance.html Scenarios.html Source.html WideGamutColmters.html applycal.html average.html cal_format.html calvschar.html cb2ti3.html ccmxs.html cctiff.html ccxxmake.html chartread.html cht_format.html collink.html colprof.html dispcal.html dispprofloc.html '/«PKGBUILDDIR»/debian/tmp/usr/share/doc/argyll' /usr/bin/install -c -m 644 dispread.html dispwin.html evalInputTargets.html extracticc.html extractttag.html fakeCMY.html fakeread.html filmread.html filmtarg.html gamma.html greytiff.html i1d3ccss.html i1proDriver.html iccdump.html iccgamut.html iccgamutmapping.html icclu.html illumread.html instruments.html invprofcheck.html kodak2ti3.html monitorcontrols.html mppcheck.html mpplu.html mppprof.html printcal.html printtarg.html profcheck.html refine.html revfix.html scanin.html sepgen.html spec2cie.html specplot.html splitti3.html spotread.html spyd2en.html spyd4en.html synthcal.html synthread.html '/«PKGBUILDDIR»/debian/tmp/usr/share/doc/argyll' /usr/bin/install -c -m 644 targen.html ti3_format.html tiffgamut.html timage.html txt2ti3.html ucmm.html verify.html viewgam.html xicclu.html ArgyllFlow.jpg ArgyllFlowThumb.jpg CMP_DT_003.jpg CMP_Digital_Target-3.jpg CRTspectrum.jpg Chroma4.jpg ColorMunki.jpg ColorMunkiCreate.jpg DC.jpg DTP20.jpg DTP22.jpg DTP41.jpg DTP51.jpg DTP92.jpg DTP94.jpg FWA_measure.jpg Fluorescent.jpg HCFR.jpg HCT.jpg HiResLaser.jpg Huey.jpg Kgraph1.jpg Kgraph2.jpg Kgraph3.jpg Kgraph4.jpg Kgraph5.jpg Kgraph6.jpg Kgraph7.jpg Kgraph8.jpg Kparams.jpg LSDC.jpg '/«PKGBUILDDIR»/debian/tmp/usr/share/doc/argyll' /usr/bin/install -c -m 644 LabSteps.jpg Q60.jpg SG.jpg Spyd2.jpg Spyd3.jpg Spyd3x.jpg
Bug#678751: vsftpd: FTBFS: main.o: could not read symbols: Bad value
Source: vsftpd Version: 3.0.0-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /usr/bin/ld: main.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC main.o: could not read symbols: Bad value collect2: error: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/vsftpd_3.0.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678752: scim-unikey: FTBFS: unikey_setup.cpp:27:43: error: 'GTK_OBJECT' was not declared in this scope
Source: scim-unikey Version: 0.3.1+debian-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -DHAVE_CONFIG_H -I. -I.. -I../ukengine -I../src -DSCIM_ICONDIR=\/usr/share/scim/icons\ -DGLADE_DATA_DIR=\/usr/share/scim-unikey/setup\ -DLOCALEDIR=\/usr/share/locale\ -DLIBEXECDIR=\/usr/lib/scim-unikey\ -Wall -pthread -I/usr/include/scim-1.0 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -c -o scim_setup_unikey-unikey_setup.o `test -f 'unikey_setup.cpp' || echo './'`unikey_setup.cpp unikey_setup.cpp: In function 'int main(int, char**)': unikey_setup.cpp:27:43: error: 'GTK_OBJECT' was not declared in this scope unikey_setup.cpp:27:76: error: 'gtk_signal_connect' was not declared in this scope make[3]: *** [scim_setup_unikey-unikey_setup.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/scim-unikey_0.3.1+debian-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678753: banshee-community-extensions: FTBFS: error CS0006: Metadata file `@expanded_libdir@/cli/zeitgeist-sharp-0.8/zeitgeist-sharp.dll' could not be found
Source: banshee-community-extensions Version: 2.4.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»/src/ZeitgeistDataprovider' /usr/bin/mono-csc \ -define:RELEASE \ \ \ -debug -target:library -out:../../bin/Banshee.ZeitgeistDataprovider.dll \ \ -r:/usr/lib/banshee/Banshee.Core.dll -r:/usr/lib/banshee/Banshee.Services.dll -r:/usr/lib/banshee/Banshee.ThickClient.dll -r:/usr/lib/banshee/Banshee.Widgets.dll -r:/usr/lib/banshee/Hyena.Data.Sqlite.dll -r:/usr/lib/banshee/Hyena.Gui.dll -r:/usr/lib/banshee/Hyena.dll -r:/usr/lib/banshee/Mono.Media.dll -r:/usr/lib/banshee/MusicBrainz.dll -r:/usr/lib/cli/dbus-sharp-1.0/dbus-sharp.dll -r:/usr/lib/cli/dbus-sharp-glib-1.0/dbus-sharp-glib.dll -r:/usr/lib/cli/taglib-sharp-2.0/taglib-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/Mono.Addins-0.2/Mono.Addins.dll -r:/usr/lib/pkgconfig/../../lib/cli/atk-sharp-2.0/atk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/gdk-sharp-2.0/gdk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/glib-sharp-2.0/glib-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/pango-sharp-2.0/pango-sharp.dll -r:@expanded_libdir@/cli/zeitgeist-sharp-0.8/zeitgeist-sharp.dll -r:Mono.Cairo -r:Mono.Posix -r:System -resource:./ZeitgeistDataprovider.addin.xml,ZeitgeistDataprovider.addin.xml ./Banshee.ZeitgeistDataprovider/ZeitgeistDataprovider.cs ../../src/AssemblyInfo.cs error CS0006: Metadata file `@expanded_libdir@/cli/zeitgeist-sharp-0.8/zeitgeist-sharp.dll' could not be found Compilation failed: 1 error(s), 0 warnings make[4]: *** [../../bin/Banshee.ZeitgeistDataprovider.dll] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/banshee-community-extensions_2.4.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678754: pyth: FTBFS: tests failed
Source: pyth Version: 0.5.6-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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 python in python2.6 python2.7; do \ $python /usr/bin/nosetests; \ done .FF... == FAIL: Try to read a paragraph containing bold text -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_readxhtml.py, line 45, in test_bold assert text['bold'] AssertionError == FAIL: Try to read a paragraph containing italic text -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_readxhtml.py, line 54, in test_italic assert text['italic'] AssertionError == FAIL: Try to read a simple xhtml document containing tree paragraphs -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_readxhtml.py, line 29, in test_paragraphs self.assert_(len(doc.content) == 3) AssertionError == FAIL: Try to read a paragraph containing subscript -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_readxhtml.py, line 63, in test_sub assert text['sub'] AssertionError == FAIL: Try to read a paragraph containing supscript -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_readxhtml.py, line 72, in test_sup assert text['super'] AssertionError == FAIL: Try to read a paragraph containing an url -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/test_readxhtml.py, line 81, in test_url assert text['url'] == http://google.com; AssertionError -- Ran 18 tests in 0.432s FAILED (failures=6) make[1]: *** [override_dh_auto_test] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/pyth_0.5.6-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678755: psi-translations: FTBFS: build-dependency not installable: qt3-dev-tools
Source: psi-translations Version: 1.10 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install psi-translations build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-psi-translations-dummy : Depends: qt3-dev-tools but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/psi-translations_1.10_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678757: cantor: FTBFS: build-dependency not installable: kalgebra-dev
Source: cantor Version: 4:4.7.4-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install cantor build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-cantor-dummy : Depends: kalgebra-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/cantor_4.7.4-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678758: sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date.
Source: sisu-ioc
Version: 2.3.0-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
mh_patchpoms -plibsisu-ioc-java --debian-build --keep-pom-version
--maven-repo=/«PKGBUILDDIR»/debian/maven-repo --build-no-docs
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian-nodocs.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Sisu
[INFO] Sisu-Inject
[INFO] Sisu-Inject : Containers
[INFO] Sisu-Inject : Containers : Bean (JSR330)
[INFO] Sisu-Inject-Bean : Generic reflection
[INFO] Sisu-Inject-Bean : Property injection
[INFO] Sisu-Inject-Bean : @Named scanning
[INFO] Sisu-Inject-Bean : Type conversion
[INFO] Sisu-Inject-Bean : Dynamic bindings
[INFO] Sisu-Inject-Bean : @Inject auto-wiring
[INFO] Sisu-Inject-Bean : Container API
[INFO] Sisu-Inject-Bean : Aggregate OSGi bundle
[INFO] Sisu-Inject : Containers : Plexus
[INFO] Sisu-Inject-Plexus : @Component metadata
[INFO] Sisu-Inject-Plexus : @Component scanning
[INFO] Sisu-Inject-Plexus : @Configuration conversion
[INFO] Sisu-Inject-Plexus : Dynamic bindings
[INFO] Sisu-Inject-Plexus : @Requirement auto-wiring
[INFO] Sisu-Inject-Plexus : @Component lifecycles
[INFO] Sisu-Inject-Plexus : Container API
[INFO] Sisu-Inject-Plexus : Aggregate OSGi bundle
[INFO] Sisu-Inject : Registries
[INFO] Sisu-OSGi-Registry : Service bindings
[INFO] Sisu-SPI-Registry : Service bindings
[INFO]
[INFO] Building Sisu
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/sisu-parent/2.3.0/sisu-parent-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/sisu-inject/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/sisu-inject/2.3.0/sisu-inject-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject : Containers
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/sisu-inject/containers/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/inject/containers/2.3.0/containers-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject : Containers : Bean (JSR330)
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/sisu-inject/containers/guice-bean/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/inject/guice-bean/2.3.0/guice-bean-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject-Bean : Generic reflection
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/«PKGBUILDDIR»/sisu-inject/containers/guice-bean/guice-bean-reflect/src/main/resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 28 source files to
/«PKGBUILDDIR»/sisu-inject/containers/guice-bean/guice-bean-reflect/target/classes
[INFO] [resources:testResources
Bug#678759: mumble: FTBFS: unsatisfiable build-dependencies: libboost1.46-dev, libboost-python1.46-dev
Source: mumble Version: 1.2.3-349-g315b5f5-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install mumble build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-mumble-dummy : Depends: libboost1.46-dev but it is not installable Depends: libboost-python1.46-dev but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/mumble_1.2.3-349-g315b5f5-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678760: php-svn: FTBFS: svn.c:3220:17: error: dereferencing pointer to incomplete type
Source: php-svn Version: 1.0.1-1.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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 /«PKGBUILDDIR»/build-php5/libtool --mode=compile x86_64-linux-gnu-gcc -I/usr/include/subversion-1 -I/usr/include/apr-1.0 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -I. -I/«PKGBUILDDIR»/build-php5 -DPHP_ATOM_INC -I/«PKGBUILDDIR»/build-php5/include -I/«PKGBUILDDIR»/build-php5/main -I/«PKGBUILDDIR»/build-php5 -I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM -I/usr/include/php5/Zend -I/usr/include/php5/ext -I/usr/include/php5/ext/date/lib -I/usr/include/subversion-1 -I/usr/include/apr-1.0 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -DHAVE_CONFIG_H -Wall -g -O0 -c /«PKGBUILDDIR»/build-php5/svn.c -o svn.lo libtool: compile: x86_64-linux-gnu-gcc -I/usr/include/subversion-1 -I/usr/include/apr-1.0 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -I. -I/«PKGBUILDDIR»/build-php5 -DPHP_ATOM_INC -I/«PKGBUILDDIR»/build-php5/include -I/«PKGBUILDDIR»/build-php5/main -I/«PKGBUILDDIR»/build-php5 -I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM -I/usr/include/php5/Zend -I/usr/include/php5/ext -I/usr/include/php5/ext/date/lib -I/usr/include/subversion-1 -I/usr/include/apr-1.0 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -DHAVE_CONFIG_H -Wall -g -O0 -c /«PKGBUILDDIR»/build-php5/svn.c -fPIC -DPIC -o .libs/svn.o /«PKGBUILDDIR»/build-php5/svn.c: In function 'init_svn_client': /«PKGBUILDDIR»/build-php5/svn.c:350:2: warning: 'svn_client_get_simple_provider' is deprecated (declared at /usr/include/subversion-1/svn_client.h:151) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:353:2: warning: 'svn_client_get_username_provider' is deprecated (declared at /usr/include/subversion-1/svn_client.h:198) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:356:2: warning: 'svn_client_get_ssl_server_trust_prompt_provider' is deprecated (declared at /usr/include/subversion-1/svn_client.h:265) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:360:2: warning: 'svn_client_get_ssl_server_trust_file_provider' is deprecated (declared at /usr/include/subversion-1/svn_client.h:214) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:363:2: warning: 'svn_client_get_ssl_client_cert_file_provider' is deprecated (declared at /usr/include/subversion-1/svn_client.h:231) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:366:2: warning: 'svn_client_get_ssl_client_cert_pw_file_provider' is deprecated (declared at /usr/include/subversion-1/svn_client.h:248) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c: In function 'zif_svn_config_ensure': /«PKGBUILDDIR»/build-php5/svn.c:450:3: warning: 'svn_path_canonicalize' is deprecated (declared at /usr/include/subversion-1/svn_path.h:282) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c: In function 'zif_svn_import': /«PKGBUILDDIR»/build-php5/svn.c:491:2: warning: 'svn_path_canonicalize' is deprecated (declared at /usr/include/subversion-1/svn_path.h:282) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:493:2: warning: 'svn_client_import' is deprecated (declared at /usr/include/subversion-1/svn_client.h:1885) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c: In function 'zif_svn_checkout': /«PKGBUILDDIR»/build-php5/svn.c:727:2: warning: 'svn_path_canonicalize' is deprecated (declared at /usr/include/subversion-1/svn_path.h:282) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:728:2: warning: 'svn_path_canonicalize' is deprecated (declared at /usr/include/subversion-1/svn_path.h:282) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:734:2: warning: 'svn_client_checkout2' is deprecated (declared at /usr/include/subversion-1/svn_client.h:1147) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c: In function 'zif_svn_cat': /«PKGBUILDDIR»/build-php5/svn.c:805:2: warning: 'svn_path_canonicalize' is deprecated (declared at /usr/include/subversion-1/svn_path.h:282) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c: In function 'zif_svn_ls': /«PKGBUILDDIR»/build-php5/svn.c:873:2: warning: 'svn_path_canonicalize' is deprecated (declared at /usr/include/subversion-1/svn_path.h:282) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:880:3: warning: 'svn_client_ls2' is deprecated (declared at /usr/include/subversion-1/svn_client.h:4936) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c:888:3: warning: 'svn_client_ls' is deprecated (declared at /usr/include/subversion-1/svn_client.h:4953) [-Wdeprecated-declarations] /«PKGBUILDDIR»/build-php5/svn.c: In function 'php_svn_log_receiver': /«PKGBUILDDIR»/build-php5/svn.c:1009:16: warning: variable 'path' set but not used
Bug#678761: dragonegg: FTBFS: g++-4.6: error: directory: No such file or directory
Source: dragonegg Version: 3.0-3.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' Compiling utils/TargetInfo.cpp g++-4.6 -c -DTARGET_TRIPLE=\x86_64-linux-gnu\ \ -I/usr/lib/llvm-3.0/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -MD -MP -DIN_GCC -DREVISION=\Unversioned directory\ -DGCC_MAJOR=4 -DGCC_MINOR=6 -DGCC_MICRO=0 -I/«PKGBUILDDIR»/include -I/usr/lib/gcc/x86_64-linux-gnu/4.6/plugin/include -Wall -Wextra -fvisibility=hidden -I/usr/lib/llvm-3.0/include -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g -O2 -fomit-frame-pointer -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual /«PKGBUILDDIR»/utils/TargetInfo.cpp g++-4.6: error: directory: No such file or directory make[1]: *** [TargetInfo.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/dragonegg_3.0-3.2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678762: node-xmpp: FTBFS: Error: Cannot find module 'node-expat'
Source: node-xmpp Version: 0.3.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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 test -x debian/rules mkdir -p . WARNING: copyright-check disabled - licensecheck (from devscripts package) is missing. touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft vows --spec module.js:337 throw new Error(Cannot find module ' + request + '); ^ Error: Cannot find module 'node-expat' at Function._resolveFilename (module.js:337:11) at Function._load (module.js:279:25) at Module.require (module.js:359:17) at require (module.js:375:17) at Object.anonymous (/«PKGBUILDDIR»/lib/xmpp/stream_parser.js:3:13) at Module._compile (module.js:446:26) at Object..js (module.js:464:10) at Module.load (module.js:353:32) at Function._load (module.js:311:12) at Module.require (module.js:359:17) make: *** [build/node-node-xmpp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/node-xmpp_0.3.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678763: embassy-domsearch: FTBFS: unsatisfiable build-dependencies: emboss-lib ( 6.3.2~) but 6.4.0-2 is to be installed
Source: embassy-domsearch Version: 0.1.0++20100721-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install embassy-domsearch build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-embassy-domsearch-dummy : Depends: emboss-lib ( 6.3.2~) but 6.4.0-2 is to be installed Depends: libgd2-xpm-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/embassy-domsearch_0.1.0++20100721-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678765: activemq: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date.
Source: activemq
Version: 5.6.0+dfsg-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh
/«BUILDDIR»/activemq-5.6.0+dfsg/debian
mh_patchpoms -plibactivemq-java --debian-build --keep-pom-version
--maven-repo=/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] ActiveMQ
[INFO] ActiveMQ :: KahaDB
[INFO] ActiveMQ :: JAAS
[INFO] ActiveMQ :: jmdns 1.0
[INFO] ActiveMQ :: Core
[INFO] ActiveMQ :: Console
[INFO] ActiveMQ :: File Server
[INFO] ActiveMQ :: RA
[INFO] ActiveMQ :: Pool
[INFO] ActiveMQ :: Run Jar
[INFO] ActiveMQ :: Spring
[INFO]
[INFO] Building ActiveMQ
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [bundle:cleanVersions {execution: cleanVersions}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«BUILDDIR»/activemq-5.6.0+dfsg/pom.xml to
/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo/org/apache/activemq/activemq-parent/5.6.0/activemq-parent-5.6.0.pom
[INFO]
[INFO] Building ActiveMQ :: KahaDB
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [bundle:cleanVersions {execution: cleanVersions}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 50 source files to
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/target/classes
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[58,48]
unmappable character for encoding ASCII
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[58,49]
unmappable character for encoding ASCII
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[67,52]
unmappable character for encoding ASCII
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[67,53]
unmappable character for encoding ASCII
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Not compiling test sources
[WARNING] DEPRECATED [systemProperties]: Use systemPropertyVariables instead.
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/target/kahadb-5.6.0.jar to
/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo/org/apache/activemq/kahadb/5.6.0/kahadb-5.6.0.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Writing OBR metadata
[INFO] Installing org/apache/activemq/kahadb/5.6.0/kahadb-5.6.0.jar
[FATAL ERROR] org.apache.felix.obrplugin.ObrInstall#execute() caused a
linkage error (java.lang.UnsupportedClassVersionError) and may be
out-of-date. Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.felix:maven-bundle-plugin:2.3.5]
urls[0] =
file:/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo/org/apache/felix/maven-bundle-plugin/2.3.5/maven-bundle-plugin-2.3.5.jar
urls[1] =
file:/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven
Bug#678766: jetty8: FTBFS: 1 required artifact is missing
Source: jetty8
Version: 8.1.3-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
mh_patchpoms -plibjetty8-java --debian-build --keep-pom-version
--maven-repo=/«PKGBUILDDIR»/debian/maven-repo
touch debian/stamp-poms-patched
jh_linkjars
jh_build -J
touch debian/jh_build_stamp
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo -P-aggregates -P-osgi
package
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Jetty :: Project
[INFO] Jetty :: Utilities
[INFO] Jetty :: JMX Management
[INFO] Jetty :: IO Utility
[INFO] Jetty :: Http Utility
[INFO] Jetty :: Continuation
[INFO] Jetty :: Server Core
[INFO] Jetty :: Security
[INFO] Jetty :: Servlet Handling
[INFO] Jetty :: Websocket
[INFO] Jetty :: Asynchronous HTTP Client
[INFO] Jetty :: XML utilities
[INFO] Jetty :: JASPI Security
[INFO] Jetty :: Webapp Application Support
[INFO] Jetty :: Utility Servlets and Filters
[INFO] Jetty :: Deployers
[INFO] Jetty :: AJP
[INFO] Jetty :: JNDI Naming
[INFO] Jetty :: Plus
[INFO] Jetty :: Servlet Annotations
[INFO] Jetty :: Rewrite Handler
[INFO] Jetty :: Policy Tool
[INFO] Jetty :: Monitoring
[INFO] Jetty :: Start
[INFO] Jetty :: Nested
[INFO] Jetty :: Overlay Deployer
[INFO] Jetty :: JSP dependencies
[INFO]
[INFO] Building Jetty :: Project
[INFO]task-segment: [package]
[INFO]
[INFO] [build-helper:parse-version {execution: set-osgi-version}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO]
[INFO] Building Jetty :: Utilities
[INFO]task-segment: [package]
[INFO]
[INFO] [build-helper:parse-version {execution: set-osgi-version}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.tomcat:tomcat-servlet-api:jar:debian
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tomcat
-DartifactId=tomcat-servlet-api -Dversion=debian -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.tomcat
-DartifactId=tomcat-servlet-api -Dversion=debian -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.eclipse.jetty:jetty-util:jar:8.1.3.v20120416
2) org.apache.tomcat:tomcat-servlet-api:jar:debian
--
1 required artifact is missing.
for artifact:
org.eclipse.jetty:jetty-util:jar:8.1.3.v20120416
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Sat Jun 23 16:08:05 UTC 2012
[INFO] Final Memory: 13M/58M
[INFO]
make: *** [mvn-build] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/24/jetty8_8.1.3
Bug#678767: librpc-xml-perl: FTBFS: tests failed
Source: librpc-xml-perl Version: 0.76-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' /usr/bin/perl etc/make_method --base=lib/Apache/RPC/status /usr/bin/perl etc/make_method --base=methods/identity /usr/bin/perl etc/make_method --base=methods/introspection /usr/bin/perl etc/make_method --base=methods/listMethods /usr/bin/perl etc/make_method --base=methods/methodHelp /usr/bin/perl etc/make_method --base=methods/methodSignature /usr/bin/perl etc/make_method --base=methods/multicall /usr/bin/perl etc/make_method --base=methods/status cp methods/status.xpl blib/lib/RPC/XML/status.xpl cp lib/Apache/RPC/Status.pm blib/lib/Apache/RPC/Status.pm cp methods/methodHelp.xpl blib/lib/RPC/XML/methodHelp.xpl cp lib/RPC/XML/Procedure.pm blib/lib/RPC/XML/Procedure.pm cp methods/introspection.xpl blib/lib/RPC/XML/introspection.xpl cp lib/RPC/XML/Parser/XMLLibXML.pm blib/lib/RPC/XML/Parser/XMLLibXML.pm cp lib/RPC/XML/Parser.pm blib/lib/RPC/XML/Parser.pm cp methods/identity.xpl blib/lib/RPC/XML/identity.xpl cp lib/RPC/XML/Server.pm blib/lib/RPC/XML/Server.pm cp lib/Apache/RPC/Server.pm blib/lib/Apache/RPC/Server.pm cp methods/multicall.xpl blib/lib/RPC/XML/multicall.xpl cp lib/Apache/RPC/status.xpl blib/lib/Apache/RPC/status.xpl cp lib/RPC/XML.pm blib/lib/RPC/XML.pm cp methods/listMethods.xpl blib/lib/RPC/XML/listMethods.xpl cp lib/RPC/XML/Client.pm blib/lib/RPC/XML/Client.pm cp methods/methodSignature.xpl blib/lib/RPC/XML/methodSignature.xpl cp lib/RPC/XML/ParserFactory.pm blib/lib/RPC/XML/ParserFactory.pm cp lib/RPC/XML/Parser/XMLParser.pm blib/lib/RPC/XML/Parser/XMLParser.pm cp etc/make_method blib/script/make_method /usr/bin/perl -MExtUtils::MY -e 'MY-fixin(shift)' -- blib/script/make_method PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00_load.t . ok t/10_data.t . ok t/11_base64_fh.t ok t/12_nil.t .. ok t/13_no_deep_recursion.t ok t/14_datetime_iso8601.t . ok t/15_serialize.t ok t/20_xml_parser.t ... ok t/21_xml_libxml.t ... ok t/25_parser_negative.t .. ok t/29_parserfactory.t ok t/30_method.t ... ok t/35_namespaces.t ... ok t/40_server.t ... ok t/40_server_xmllibxml.t . ok t/41_server_hang.t .. ok t/50_client.t ... ok t/51_client_with_host_header.t .. ok # Failed test 'system.identity matches $srv-product_tokens' # at t/60_net_server.t line 60. # got: undef # expected: 'RPC::XML::Server/1.68' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 68. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 80. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 90. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned HASH ref' # at t/60_net_server.t line 100. # got: '' # expected: 'HASH' # Failed test 'system.methodHelp returned correct string' # at t/60_net_server.t line 110. # got: undef # expected: 'Return the server name and version as a string' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 116. # got: '' # expected: 'ARRAY' # Failed test 'system.methodHelp (bad arg) response isa RPC::XML::fault' # at t/60_net_server.t line 127. # system.methodHelp (bad arg) response isn't a 'RPC::XML::fault' it's a '' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 136. # got: '' # expected: 'ARRAY' # Failed test 'system.methodSignature (bad arg) response isa RPC::XML::fault' # at t/60_net_server.t line 146. # system.methodSignature (bad arg) response isn't a 'RPC::XML::fault' it's a '' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 193. # got: '' # expected: 'ARRAY' # Looks like you planned 30 tests but ran 29. # Looks like you failed 11 tests of 29 run. t/60_net_server.t ... Dubious, test returned 11 (wstat 2816, 0xb00) Failed 12/30 subtests (less 16 skipped subtests: 2 okay) t/70_compression_detect.t ... ok t/90_rt50013_parser_bugs.t .. ok t/90_rt54183_sigpipe.t .. ok t/90_rt54494_blessed_refs.t . ok t/90_rt58065_allow_nil.t ok t/90_rt58323_push_parser.t .. ok Test Summary Report
Bug#678769: linbox: FTBFS: ERROR: GIVARO not found!
Source: linbox
Version: 1.1.6~rc0-4.2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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»'
if test -e /usr/share/misc/config.guess ; then \
for i in ./config.guess ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination
/usr/share/misc/config.guess $i ; \
fi ; \
done ; \
fi
if test -e /usr/share/misc/config.sub ; then \
for i in ./config.sub ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination
/usr/share/misc/config.sub $i ; \
fi ; \
done ; \
fi
make[1]: Leaving directory `/«PKGBUILDDIR»'
if test -e /usr/share/misc/config.guess ; then \
for i in ./config.guess ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination
/usr/share/misc/config.guess $i ; \
fi ; \
done ; \
fi
if test -e /usr/share/misc/config.sub ; then \
for i in ./config.sub ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination
/usr/share/misc/config.sub $i ; \
fi ; \
done ; \
fi
cd . libtoolize -c -f
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `macros'.
libtoolize: copying file `macros/libtool.m4'
libtoolize: copying file `macros/ltoptions.m4'
libtoolize: copying file `macros/ltsugar.m4'
libtoolize: copying file `macros/ltversion.m4'
libtoolize: copying file `macros/lt~obsolete.m4'
cd . aclocal-1.10 -I macros
if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . `which
autoconf2.50 || which autoconf`; fi
if [ -e ./Makefile.am ]; then cd . automake-1.10 --add-missing ; fi
configure.in:7: not enough arguments for AC_CONFIG_HEADERS
examples/Makefile.am:62: `%'-style pattern rules are a GNU make extension
touch debian/stamp-autotools-files
chmod a+x /«PKGBUILDDIR»/./configure
mkdir -p .
cd .CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall
CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-z,relro
/«PKGBUILDDIR»/./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libexecdir=\${prefix}/lib/linbox --srcdir=. --disable-maintainer-mode
--disable-dependency-tracking --disable-silent-rules --with-gmp
--with-givaro --with-blas --with-ntl --enable-optimization --enable-docs
--enable-sage --enable-shared
configure: WARNING: unrecognized options: --disable-silent-rules,
--enable-docs
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
Bug#678770: libextractor: FTBFS: dh_install: libextractor3 missing files (usr/lib/*/libextractor/libextractor_pdf.so), aborting
Source: libextractor Version: 1:0.6.3-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»' make[4]: Nothing to be done for `install-exec-am'. /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig' /usr/bin/install -c -m 644 libextractor.pc '/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig' make[4]: Leaving directory `/«PKGBUILDDIR»' make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' # Removing useless files rm -f debian/tmp/usr/lib/*/*.la rm -f debian/tmp/usr/lib/*/libextractor/*.la rm -f debian/tmp/usr/share/info/dir* make[1]: Leaving directory `/«PKGBUILDDIR»' debian/rules override_dh_install make[1]: Entering directory `/«PKGBUILDDIR»' dh_install --fail-missing dh_install: libextractor3 missing files (usr/lib/*/libextractor/libextractor_pdf.so), aborting make[1]: *** [override_dh_install] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/libextractor_0.6.3-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678771: unagi: FTBFS: build-dependency not installable: libxcb-ewmh2-dev
Source: unagi Version: 0.3.3-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install unagi build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-unagi-dummy : Depends: libxcb-ewmh2-dev but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/unagi_0.3.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678772: libpoe-component-client-http-perl: FTBFS: tests failed
Source: libpoe-component-client-http-perl Version: 0.945-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t # Testing with Perl 5.014002, /usr/bin/perl # ExtUtils::MakeMaker version is 6.57_05 # HTTP::Headers version is 6.00 # HTTP::Request version is 6.00 # HTTP::Request::Common version is 6.03 # HTTP::Response version is 6.03 # HTTP::Status version is 6.03 # Net::HTTP::Methods version is 6.00 # POE version is 1.354 # POE::Component::Client::Keepalive version is 0.271 # Socket::GetAddrInfo version is 0.22 # Test::More version is 0.98 # Test::POE::Server::TCP version is 1.14 # URI version is 1.60 t/000-report-versions.t .. ok :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33 BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33. Compilation failed in require at (eval 71) line 1. BEGIN failed--compilation aborted at (eval 71) line 1. could not import qw(Component::Client::HTTP) at t/01_request.t line 4 BEGIN failed--compilation aborted at t/01_request.t line 9. t/01_request.t ... Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33 BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33. Compilation failed in require at (eval 64) line 1. BEGIN failed--compilation aborted at (eval 64) line 1. could not import qw(Component::Client::HTTP) at t/01_ssl.t line 7 BEGIN failed--compilation aborted at t/01_ssl.t line 7. t/01_ssl.t ... Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33 BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33. Compilation failed in require at (eval 71) line 1. BEGIN failed--compilation aborted at (eval 71) line 1. could not import qw(Component::Client::HTTP) at t/01_stream.t line 4 BEGIN failed--compilation aborted at t/01_stream.t line 9. t/01_stream.t Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33 BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33. Compilation failed in require at (eval 64) line 1. BEGIN failed--compilation aborted at (eval 64) line 1. could not import qw(Component::Client::HTTP) at t/02_keepalive.t line 7 BEGIN failed--compilation aborted at t/02_keepalive.t line 7. t/02_keepalive.t . Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run t/03_head_filter.t ... ok t/04_chunk_filter.t .. ok t/05_request.t ... ok :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33 BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33. Compilation failed in require at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP/RequestFactory.pm line 12. BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP/RequestFactory.pm line 12. Compilation failed in require at t/06_factory.t line 8. BEGIN failed--compilation aborted at t/06_factory.t line 8. # Looks like your test exited with 2 before it could output anything. t/06_factory.t ... Dubious, test returned 2 (wstat 512, 0x200) Failed 13/13 subtests :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33 BEGIN failed--compilation aborted at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33. Compilation failed in require at t/07_proxy.t line 19. BEGIN failed--compilation aborted at t/07_proxy.t line 19. # Looks like your test exited with 2 before it could output anything. t/07_proxy.t . Dubious, test returned 2 (wstat 512, 0x200) Failed 9/9 subtests :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly at /«PKGBUILDDIR»/blib/lib/POE/Component/Client/HTTP.pm line 33 BEGIN failed
Bug#678773: subcommander: FTBFS: ../../svn/WcStatus.cpp:28:41: error: invalid conversion from 'const svn_wc_entry_t*' to 'svn_wc_entry_t*' [-fpermissive]
Source: subcommander Version: 2.0.0~b5p2-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -DHAVE_CONFIG_H -I. -I../../svn -I.. -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -I.. -I/usr/include/subversion-1 -I/usr/include/apr-1.0 -Wno-deprecated -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wno-deprecated -I/«PKGBUILDDIR» -c -o WcStatus.o ../../svn/WcStatus.cpp ../../svn/WcStatus.cpp: In constructor 'svn::WcStatus::WcStatus(const sc::String, svn_wc_status2_t*)': ../../svn/WcStatus.cpp:28:41: error: invalid conversion from 'const svn_wc_entry_t*' to 'svn_wc_entry_t*' [-fpermissive] In file included from ../../svn/WcStatus.cpp:12:0: ../../svn/WcEntry.h:41:3: error: initializing argument 1 of 'svn::WcEntry::WcEntry(svn_wc_entry_t*)' [-fpermissive] make[4]: *** [WcStatus.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/subcommander_2.0.0~b5p2-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678774: plasma-widget-smooth-tasks: FTBFS: Task.h:79:2: error: 'TaskPtr' in namespace 'TaskManager' does not name a type
Source: plasma-widget-smooth-tasks Version: 0.0~wip20100227-1.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 4 [ 14%] Building CXX object applet/CMakeFiles/plasma_applet_smooth-tasks.dir/plasma_applet_smooth-tasks_automoc.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/applet /usr/bin/c++ -DMAKE_PLASMA_APPLET_SMOOTH_TASKS_LIB -D_BSD_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=40 -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -fPIC -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/applet -I/«PKGBUILDDIR»/applet -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -o CMakeFiles/plasma_applet_smooth-tasks.dir/plasma_applet_smooth-tasks_automoc.o -c /«PKGBUILDDIR»/obj-x86_64-linux-gnu/applet/plasma_applet_smooth-tasks_automoc.cpp In file included from /«PKGBUILDDIR»/applet/SmoothTasks/TaskItem.h:25:0, from /«PKGBUILDDIR»/applet/SmoothTasks/ToolTipBase.h:25, from /«PKGBUILDDIR»/applet/SmoothTasks/DelayedToolTip.h:23, from /«PKGBUILDDIR»/obj-x86_64-linux-gnu/applet/../../applet/SmoothTasks/PlasmaToolTip.h:23, from /«PKGBUILDDIR»/obj-x86_64-linux-gnu/applet/moc_PlasmaToolTip.cpp:10, from /«PKGBUILDDIR»/obj-x86_64-linux-gnu/applet/plasma_applet_smooth-tasks_automoc.cpp:4: /«PKGBUILDDIR»/applet/SmoothTasks/Task.h:79:2: error: 'TaskPtr' in namespace 'TaskManager' does not name a type /«PKGBUILDDIR»/applet/SmoothTasks/Task.h:83:2: error: 'StartupPtr' in namespace 'TaskManager' does not name a type make[3]: *** [applet/CMakeFiles/plasma_applet_smooth-tasks.dir/plasma_applet_smooth-tasks_automoc.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/plasma-widget-smooth-tasks_0.0~wip20100227-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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678775: lintian: FTBFS: build-dependency not installable: xz-lzma
Source: lintian Version: 2.5.9 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install lintian build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-lintian-dummy : Depends: xz-lzma but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/lintian_2.5.9_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678776: libpixels-java: FTBFS: The local variable w is never read
Source: libpixels-java
Version: 2.1.3+svn.42-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
dh_testdir
touch build-arch-stamp
dh_testdir
jh_build pixels.jar src/main/java
find src/main/java -name *.java -and -type f -print0 | xargs -0
/usr/lib/jvm/java-gcj/bin/javac -cp :debian/_jh_build.pixels -d
debian/_jh_build.pixels -source 1.5 -target 1.5
--
1. WARNING in src/main/java/com/jhlabs/image/CropFilter.java (at line 127)
int w = src.getWidth();
^
The local variable w is never read
--
2. WARNING in src/main/java/com/jhlabs/image/CropFilter.java (at line 128)
int h = src.getHeight();
^
The local variable h is never read
--
--
3. WARNING in src/main/java/com/jhlabs/image/GradientFilter.java (at line 21)
import java.util.*;
^
The import java.util is never used
--
4. WARNING in src/main/java/com/jhlabs/image/GradientFilter.java (at line 154)
int rgb1, rgb2;
The local variable rgb1 is never read
--
5. WARNING in src/main/java/com/jhlabs/image/GradientFilter.java (at line 154)
int rgb1, rgb2;
The local variable rgb2 is never read
--
--
6. WARNING in src/main/java/com/jhlabs/image/SparkleFilter.java (at line 19)
import java.awt.image.*;
^^
The import java.awt.image is never used
--
7. WARNING in src/main/java/com/jhlabs/image/SparkleFilter.java (at line 29)
private int width, height;
^
The field SparkleFilter.width is never read locally
--
8. WARNING in src/main/java/com/jhlabs/image/SparkleFilter.java (at line 29)
private int width, height;
^^
The field SparkleFilter.height is never read locally
--
--
9. WARNING in src/main/java/com/jhlabs/image/TileImageFilter.java (at line 29)
private int tileWidth;
^
The field TileImageFilter.tileWidth is never read locally
--
10. WARNING in src/main/java/com/jhlabs/image/TileImageFilter.java (at line
30)
private int tileHeight;
^^
The field TileImageFilter.tileHeight is never read locally
--
--
11. WARNING in src/main/java/com/jhlabs/image/MotionBlurFilter.java (at line
28)
private float falloff = 1.0f;
^^^
The field MotionBlurFilter.falloff is never read locally
--
--
12. WARNING in src/main/java/com/jhlabs/image/TransitionFilter.java (at line
23)
import java.util.*;
^
The import java.util is never used
--
13. WARNING in src/main/java/com/jhlabs/image/TransitionFilter.java (at line
54)
private TransitionFilter() {
^^
The constructor TransitionFilter() is never used locally
--
--
14. WARNING in src/main/java/com/jhlabs/image/ScratchFilter.java (at line 8)
import java.awt.geom.*;
^
The import java.awt.geom is never used
--
--
15. WARNING in src/main/java/com/jhlabs/image/PolarFilter.java (at line 19)
import java.awt.*;
The import java.awt is never used
--
--
16. WARNING in src/main/java/com/jhlabs/image/ErodeFilter.java (at line 20)
import java.awt.image.*;
^^
The import java.awt.image is never used
--
--
17. WARNING in src/main/java/com/jhlabs/image/DiffuseFilter.java (at line 19)
import java.awt.*;
The import java.awt is never used
--
18. WARNING in src/main/java/com/jhlabs/image/DiffuseFilter.java (at line 21)
import com.jhlabs.math.*;
^^^
The import com.jhlabs.math is never used
--
--
19. WARNING in src/main/java/com/jhlabs/image/SaturationFilter.java (at line
7)
import java.awt.*;
The import java.awt is never used
--
20. WARNING in src/main/java/com/jhlabs/image/SaturationFilter.java (at line
8)
import java.awt.image.*;
^^
The import java.awt.image is never used
--
--
21. WARNING in src/main/java/com/jhlabs/image/MaskFilter.java (at line 19)
import java.awt.*;
The import java.awt is never used
--
22. WARNING in src/main/java/com/jhlabs/image/MaskFilter.java (at line 20)
import java.awt.image.*;
^^
The import java.awt.image is never used
--
23. WARNING in src/main/java/com/jhlabs/image/MaskFilter.java (at line 21)
import java.io
Bug#678777: sorl-thumbnail: FTBFS: tests failed
Source: sorl-thumbnail Version: 11.12-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' mkdir -p tmp-locales localedef -i en_US -c -f UTF-8 tmp-locales/en_US.UTF-8 set -e; \ for python in python2.7 python2.6; do \ for name in pil pgmagick imagemagick graphicsmagick; do \ LOCPATH=/«PKGBUILDDIR»/tmp-locales LC_ALL=en_US.UTF-8 PYTHONPATH=tests LOCAL_BUILD=1 $python tests/runtests.py --settings=settings.$name ; \ done; \ done .ss.. -- Ran 37 tests in 1.971s OK (skipped=2) Running tests for 'settings.pil' Creating test database for alias 'default'... Destroying test database for alias 'default'... .F...ss.. == FAIL: test_orientation (thumbnail_tests.tests.TemplateTestCaseA) -- Traceback (most recent call last): File /«PKGBUILDDIR»/tests/thumbnail_tests/tests.py, line 349, in test_orientation self.assertEqual(exif.get(0x0112), 1) AssertionError: 2 != 1 -- Ran 37 tests in 1.242s FAILED (failures=1, skipped=2) Running tests for 'settings.pgmagick' Creating test database for alias 'default'... Destroying test database for alias 'default'... make[1]: *** [override_dh_auto_test] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/sorl-thumbnail_11.12-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678778: assimp: FTBFS: build-dependency not installable: libboost1.46-dev
Source: assimp Version: 2.0.863+dfsg-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install assimp build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-assimp-dummy : Depends: libboost1.46-dev but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/assimp_2.0.863+dfsg-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678779: libhtml-data-parser-perl: FTBFS: tests failed
Source: libhtml-data-parser-perl Version: 0.005-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(1, 'inc', 'blib/lib', 'blib/arch') t/01basic.t # Failed test 'RDFa parsed.' # at t/01basic.t line 23. # Looks like you failed 1 test of 2. t/01basic.t .. 1..2 ok 1 - use HTML::Data::Parser; not ok 2 - RDFa parsed. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 test programs. 1/2 subtests failed. Failed 1/2 subtests Test Summary Report --- t/01basic.t (Wstat: 256 Tests: 2 Failed: 1) Failed test: 2 Non-zero exit status: 1 Files=1, Tests=2, 1 wallclock secs ( 0.01 usr 0.03 sys + 0.67 cusr 0.08 csys = 0.79 CPU) Result: FAIL make[1]: *** [test_dynamic] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/libhtml-data-parser-perl_0.005-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678780: unburden-home-dir: FTBFS: tests failed
Source: unburden-home-dir Version: 0.3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' checkbashisms Xsession.d/95unburden-home-dir script Xsession.d/95unburden-home-dir does not appear to have a #! interpreter line; you may get strange results perl -c bin/unburden-home-dir bin/unburden-home-dir syntax OK prove t/*.t # Failed test 'Check command STDERR output' # at t/check-symlinks-in-path.t line 45. # Looks like you failed 1 test of 16. t/check-symlinks-in-path.t . Dubious, test returned 1 (wstat 256, 0x100) Failed 1/16 subtests # Failed test 'Check command STDERR output' # at t/check-symlinks-without-trailing-slash.t line 41. # Looks like you failed 1 test of 11. t/check-symlinks-without-trailing-slash.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/11 subtests # Failed test 'Check command STDERR output (should be empty)' # at t/create-empty-directories.t line 38. # Looks like you failed 1 test of 13. t/create-empty-directories.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/13 subtests # Failed test 'Check command STDERR output' # at t/find-per-user-stuff.t line 46. # Looks like you failed 1 test of 16. t/find-per-user-stuff.t Dubious, test returned 1 (wstat 256, 0x100) Failed 1/16 subtests # Failed test 'Check command STDERR output (should be empty)' # at t/moving-to-existing-subdir.t line 44. # Looks like you failed 1 test of 17. t/moving-to-existing-subdir.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/17 subtests # Failed test 'Check command STDERR output' # at t/parse-comments-and-blank-lines.t line 45. # Looks like you failed 1 test of 16. t/parse-comments-and-blank-lines.t . Dubious, test returned 1 (wstat 256, 0x100) Failed 1/16 subtests WARNING: lsof not found, not checking for files in use at bin/unburden-home-dir line 179. t/replacement-order-dryrun.t ... ok WARNING: lsof not found, not checking for files in use at bin/unburden-home-dir line 179. t/replacement-order.t .. ok # Failed test 'Check command STDERR output' # at t/skip-non-home.t line 42. # Failed test 'Check command STDERR output' # at t/skip-non-home.t line 42. # Looks like you failed 2 tests of 28. t/skip-non-home.t .. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/28 subtests t/undo-dryrun.t ok # Failed test 'Check command STDERR output (should be empty)' # at t/undo.t line 49. # Looks like you failed 1 test of 13. t/undo.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/13 subtests t/xsession-d.t . ok Test Summary Report --- t/check-symlinks-in-path.t (Wstat: 256 Tests: 16 Failed: 1) Failed test: 11 Non-zero exit status: 1 t/check-symlinks-without-trailing-slash.t (Wstat: 256 Tests: 11 Failed: 1) Failed test: 8 Non-zero exit status: 1 t/create-empty-directories.t (Wstat: 256 Tests: 13 Failed: 1) Failed test: 8 Non-zero exit status: 1 t/find-per-user-stuff.t (Wstat: 256 Tests: 16 Failed: 1) Failed test: 11 Non-zero exit status: 1 t/moving-to-existing-subdir.t(Wstat: 256 Tests: 17 Failed: 1) Failed test: 10 Non-zero exit status: 1 t/parse-comments-and-blank-lines.t (Wstat: 256 Tests: 16 Failed: 1) Failed test: 11 Non-zero exit status: 1 t/skip-non-home.t(Wstat: 512 Tests: 28 Failed: 2) Failed tests: 8, 22 Non-zero exit status: 2 t/undo.t (Wstat: 256 Tests: 13 Failed: 1) Failed test: 9 Non-zero exit status: 1 Files=12, Tests=184, 9 wallclock secs ( 0.09 usr 0.07 sys + 1.51 cusr 0.50 csys = 2.17 CPU) Result: FAIL make[1]: *** [test] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/unburden-home-dir_0.3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678782: vim-addon-manager: FTBFS: undefined method `multiline_arg' for #Gherkin::Formatter::Model::Step:0x2b16658cdb28 (NoMethodError)
Source: vim-addon-manager Version: 0.5.0 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' dh_auto_install /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting Encoding.default_external Entering dh_ruby --install install -d /«PKGBUILDDIR»/debian/vim-addon-manager/usr/bin install -D -m755 bin/vim-addon-manager /«PKGBUILDDIR»/debian/vim-addon-manager/usr/bin/vim-addon-manager install -D -m755 bin/vim-addons /«PKGBUILDDIR»/debian/vim-addon-manager/usr/bin/vim-addons install -D -m755 bin/vam /«PKGBUILDDIR»/debian/vim-addon-manager/usr/bin/vam install -d /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby install -D -m644 lib/vim/addon_manager.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager.rb install -D -m644 lib/vim/addon_manager/logger.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/logger.rb install -D -m644 lib/vim/addon_manager/upgrade_from_legacy.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/upgrade_from_legacy.rb install -D -m644 lib/vim/addon_manager/addon_status.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon_status.rb install -D -m644 lib/vim/addon_manager/addon.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon.rb install -D -m644 lib/vim/addon_manager/registry.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/registry.rb install -D -m644 lib/vim/addon_manager/addon/directory.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon/directory.rb install -D -m644 lib/vim/addon_manager/addon/legacy.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/addon/legacy.rb install -D -m644 lib/vim/addon_manager/constants.rb /«PKGBUILDDIR»/debian/vim-addon-manager/usr/lib/ruby/vendor_ruby/vim/addon_manager/constants.rb Rewriting shebang line of /«PKGBUILDDIR»/debian/vim-addon-manager/usr/bin/vam Rewriting shebang line of /«PKGBUILDDIR»/debian/vim-addon-manager/usr/bin/vim-addons Rewriting shebang line of /«PKGBUILDDIR»/debian/vim-addon-manager/usr/bin/vim-addon-manager /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /usr/bin/ruby1.8 -S rspec --color spec . Finished in 0.05957 seconds 21 examples, 0 failures /usr/bin/ruby1.8 -S cucumber --format progress undefined method `multiline_arg' for #Gherkin::Formatter::Model::Step:0x2b16658cdb28 (NoMethodError) /usr/lib/ruby/vendor_ruby/cucumber/parser/gherkin_builder.rb:98:in `step' /usr/lib/ruby/vendor_ruby/gherkin/formatter/tag_count_formatter.rb:43:in `__send__' /usr/lib/ruby/vendor_ruby/gherkin/formatter/tag_count_formatter.rb:43:in `method_missing' /usr/lib/ruby/vendor_ruby/gherkin/formatter/model.rb:150:in `replay' /usr/lib/ruby/vendor_ruby/gherkin/formatter/model.rb:178:in `replay' /usr/lib/ruby/vendor_ruby/gherkin/listener/formatter_listener.rb:87:in `replay' /usr/lib/ruby/vendor_ruby/gherkin/listener/formatter_listener.rb:138:in `replay_step_or_examples' /usr/lib/ruby/vendor_ruby/gherkin/listener/formatter_listener.rb:59:in `step' /usr/lib/ruby/vendor_ruby/gherkin/parser/parser.rb:46:in `__send__' /usr/lib/ruby/vendor_ruby/gherkin/parser/parser.rb:46:in `method_missing' /usr/lib/ruby/vendor_ruby/gherkin/lexer/i18n_lexer.rb:22:in `scan' /usr/lib/ruby/vendor_ruby/gherkin/lexer/i18n_lexer.rb:22:in `scan' /usr/lib/ruby/vendor_ruby/gherkin/parser/parser.rb:31:in `parse' /usr/lib/ruby/vendor_ruby/cucumber/feature_file.rb:37:in `parse' /usr/lib/ruby/vendor_ruby/cucumber/runtime/features_loader.rb:28:in `load' /usr/lib/ruby/vendor_ruby/cucumber/runtime/features_loader.rb:26:in `each' /usr/lib/ruby/vendor_ruby/cucumber/runtime/features_loader.rb:26:in `load' /usr/lib/ruby/vendor_ruby/cucumber/runtime/features_loader.rb:14:in `features' /usr/lib/ruby/vendor_ruby/cucumber/runtime.rb:132:in `features' /usr/lib/ruby/vendor_ruby/cucumber/runtime.rb:45:in `run!' /usr/lib/ruby/vendor_ruby/cucumber/cli/main.rb:38:in `execute!' /usr/lib/ruby/vendor_ruby/cucumber/cli/main.rb:15:in `execute' /usr/bin/cucumber:14 rake aborted! Command failed with status (1): [/usr/bin/ruby1.8 -S cucumber --format prog...] Tasks: TOP = default = cucumber (See full trace by running task with --trace) ERROR: Test ruby1.8 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/vim-addon-manager returned exit code 1 make[1]: *** [override_dh_auto_install] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/vim-addon
Bug#678783: flightgear: FTBFS: terrasync.cxx:133:14: error: 'svn_version_checklist_t' does not name a type
Source: flightgear Version: 2.4.0-1.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I/usr/include/subversion-1 -I/usr/include/apr-1.0 -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -I/usr/local/include -O2 -g -D_REENTRANT -Wall -I/usr -D_REENTRANT -MT terrasync.o -MD -MP -MF .deps/terrasync.Tpo -c -o terrasync.o terrasync.cxx terrasync.cxx:133:14: error: 'svn_version_checklist_t' does not name a type terrasync.cxx: In function 'int mysvn_setup()': terrasync.cxx:157:24: error: 'mysvn_version' was not declared in this scope terrasync.cxx:157:37: error: 'SVN_VERSION_DEFINE' was not declared in this scope terrasync.cxx:158:46: error: 'mysvn_checklist' was not declared in this scope terrasync.cxx:158:61: error: 'svn_ver_check_list' was not declared in this scope terrasync.cxx:183:11: warning: 'svn_error_t* svn_cmdline_setup_auth_baton(svn_auth_baton_t**, svn_boolean_t, const char*, const char*, const char*, svn_boolean_t, svn_config_t*, svn_cancel_func_t, void*, apr_pool_t*)' is deprecated (declared at /usr/include/subversion-1/svn_cmdline.h:361) [-Wdeprecated-declarations] terrasync.cxx:185:62: warning: 'svn_error_t* svn_cmdline_setup_auth_baton(svn_auth_baton_t**, svn_boolean_t, const char*, const char*, const char*, svn_boolean_t, svn_config_t*, svn_cancel_func_t, void*, apr_pool_t*)' is deprecated (declared at /usr/include/subversion-1/svn_cmdline.h:361) [-Wdeprecated-declarations] terrasync.cxx: In function 'void sync_tree(const char*)': terrasync.cxx:251:11: warning: 'svn_error_t* svn_client_checkout2(svn_revnum_t*, const char*, const char*, const svn_opt_revision_t*, const svn_opt_revision_t*, svn_boolean_t, svn_boolean_t, svn_client_ctx_t*, apr_pool_t*)' is deprecated (declared at /usr/include/subversion-1/svn_client.h:1147) [-Wdeprecated-declarations] terrasync.cxx:259:13: warning: 'svn_error_t* svn_client_checkout2(svn_revnum_t*, const char*, const char*, const svn_opt_revision_t*, const svn_opt_revision_t*, svn_boolean_t, svn_boolean_t, svn_client_ctx_t*, apr_pool_t*)' is deprecated (declared at /usr/include/subversion-1/svn_client.h:1147) [-Wdeprecated-declarations] make[3]: *** [terrasync.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/flightgear_2.4.0-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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678784: compiz: FTBFS: window.cpp:893:25: error: invalid conversion from 'long int' to 'KDecorationDefines::Region' [-fpermissive]
Source: compiz
Version: 0.8.4-5.2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include
-DQT_SHARED -I/usr/include/dbus-1.0
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/qt4
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtDBus
-I/usr/include/qt4/QtXml -I/usr/include/-g -O2 -Wall
-D_FORTIFY_SOURCE=2 -MT window.o -MD -MP -MF .deps/window.Tpo -c -o
window.o window.cpp; \
then mv -f .deps/window.Tpo .deps/window.Po; else rm -f
.deps/window.Tpo; exit 1; fi
window.cpp: In member function 'void KWD::Window::updateBlurProperty(int,
int, int, int)':
window.cpp:893:25: error: invalid conversion from 'long int' to
'KDecorationDefines::Region' [-fpermissive]
window.cpp:894:28: error: invalid conversion from 'long int' to
'KDecorationDefines::Region' [-fpermissive]
window.cpp:895:26: error: invalid conversion from 'long int' to
'KDecorationDefines::Region' [-fpermissive]
window.cpp:896:27: error: invalid conversion from 'long int' to
'KDecorationDefines::Region' [-fpermissive]
window.cpp:916:37: error: cannot convert 'Region {aka _XRegion*}' to
'KDecorationDefines::Region' in assignment
window.cpp:928:40: error: cannot convert 'Region {aka _XRegion*}' to
'KDecorationDefines::Region' in assignment
window.cpp:938:36: error: cannot convert 'Region {aka _XRegion*}' to
'KDecorationDefines::Region' in assignment
window.cpp:948:38: error: cannot convert 'Region {aka _XRegion*}' to
'KDecorationDefines::Region' in assignment
window.cpp:954:19: error: base operand of '-' is not a pointer
window.cpp:956:22: error: base operand of '-' is not a pointer
window.cpp:958:20: error: base operand of '-' is not a pointer
window.cpp:960:21: error: base operand of '-' is not a pointer
window.cpp:972:36: error: cannot convert 'KDecorationDefines::Region' to
'Region {aka _XRegion*}' for argument '6' to 'void
decor_region_to_blur_property(long int*, int, int, int, int, Region, int,
Region, int, Region, int, Region, int)'
make[4]: *** [window.o] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/24/compiz_0.8.4-5.2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678785: kalgebra: FTBFS: cp: cannot stat `debian/tmp/usr/lib/libanalitza.so.4.7.0': No such file or directory
Source: kalgebra Version: 4:4.7.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make[3]: Nothing to be done for `preinstall'. make[3]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: Debian -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/index.cache.bz2 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/commands.docbook -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/index.docbook -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/kalgebra-main-window.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitza.so.4.8.0 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitza.so.4 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitza.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/abstractlexer.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/analitzaexport.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/analyzer.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/analitzautils.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/expression.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/object.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/operations.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/operator.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/value.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/variables.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/expressiontype.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/builtinmethods.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/cmake/modules/FindAnalitza.cmake -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so.4.8.0 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so.4 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so.4.8.0 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/algebrahighlighter.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/analitzaguiexport.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/operatorsmodel.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/variablesmodel.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebra -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebra -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/applications/kde4/kalgebra.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/katepart/syntax/kalgebra.xml -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/128x128/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/64x64/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/16x16/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/48x48/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/32x32/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/plasma_applet_kalgebra.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/plasma_applet_kalgebra.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kalgebraplasmoid.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebramobile -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebramobile -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/applications/kde4/kalgebramobile.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/servicetypes/kalgebrascript.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kalgebra/scripts/console/console.js -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kalgebra/scripts/console/kalgebraconsole.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kalgebra/scripts/plot2d/plot2d.js -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kalgebra/scripts/plot2d/kalgebraplot2d.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kalgebra/scripts/tables/tables.js -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kalgebra/scripts/tables/kalgebratables.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kalgebra/scripts/variables/variables.js -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps
Bug#678786: haskell-llvm-base: FTBFS: error: 'class llvm::SMDiagnostic' has no member named 'Print'
Source: haskell-llvm-base Version: 3.0.1.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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 test -x debian/rules mkdir -p . /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING: DEB_COMPRESS_EXCLUDE is a deprecated variable if test ! -e Setup.lhs -a ! -e Setup.hs; then echo No setup script found!; exit 1; fi for setup in Setup.lhs Setup.hs; do if test -e $setup; then ghc --make $setup -o debian/hlibrary.setup; exit 0; fi; done [1 of 1] Compiling Main ( Setup.hs, Setup.o ) Linking debian/hlibrary.setup ... debian/hlibrary.setup configure --ghc -v2 \ --prefix=/usr --libdir=/usr/lib/haskell-packages/ghc/lib \ --builddir=dist-ghc \ --haddockdir=/usr/lib/ghc-doc/haddock/llvm-base-3.0.1.0/ \ --htmldir=/usr/share/doc/libghc-llvm-base-doc/html/ --enable-library-profiling \ Configuring llvm-base-3.0.1.0... Flags chosen: developer=False Dependency base =3 5: using base-4.5.0.0 Using Cabal-1.14.0 compiled by ghc-7.4 Using compiler: ghc-7.4.1 Using install prefix: /usr Binaries installed in: /usr/bin Libraries installed in: /usr/lib/haskell-packages/ghc/lib/llvm-base-3.0.1.0/ghc-7.4.1 Private binaries installed in: /usr/libexec Data files installed in: /usr/share/llvm-base-3.0.1.0 Documentation installed in: /usr/share/doc/llvm-base-3.0.1.0 No alex found Using ar found on system at: /usr/bin/ar No c2hs found No cpphs found No ffihugs found Using gcc version 4.7 found on system at: /usr/bin/gcc Using ghc version 7.4.1 found on system at: /usr/bin/ghc Using ghc-pkg version 7.4.1 found on system at: /usr/bin/ghc-pkg No greencard found Using haddock version 2.10.0 found on system at: /usr/bin/haddock No happy found No hmake found Using hpc version 0.6 found on system at: /usr/bin/hpc Using hsc2hs version 0.67 found on system at: /usr/bin/hsc2hs Using hscolour version 1.19 found on system at: /usr/bin/HsColour No hugs found No jhc found Using ld found on system at: /usr/bin/ld No lhc found No lhc-pkg found No nhc98 found No pkg-config found Using ranlib found on system at: /usr/bin/ranlib Using strip found on system at: /usr/bin/strip Using tar found on system at: /bin/tar No uhc found sh configure --with-compiler=ghc --prefix=/usr --libdir=/usr/lib/haskell-packages/ghc/lib --with-gcc=/usr/bin/gcc configure: WARNING: unrecognized options: --with-gcc checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for llvm-config... /usr/bin/llvm-config Target platform inferred as: x86_64-unknown-linux checking for library containing LLVMModuleCreateWithName... no checking how to run the C++ preprocessor... g++ -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking llvm-c/Core.h usability... yes checking llvm-c/Core.h presence... yes checking for llvm-c/Core.h... yes checking llvm/ADT/StringRef.h usability... yes checking llvm/ADT/StringRef.h presence... yes checking for llvm/ADT/StringRef.h... yes checking for llvm/Support/DynamicLibrary.h... yes checking for LLVMModuleCreateWithName in -lLLVMCore... yes configure: creating ./config.status config.status: creating llvm-base.buildinfo config.status: creating include/hs_llvm_config.h configure: WARNING: unrecognized options: --with-gcc Reading parameters from ./llvm-base.buildinfo debian/hlibrary.setup build --builddir=dist-ghc Building llvm-base-3.0.1.0... Preprocessing library llvm-base-3.0.1.0... [ 1 of 24] Compiling LLVM.Target.XCore ( LLVM/Target/XCore.hs, dist-ghc/build/LLVM/Target/XCore.o ) [ 2 of 24] Compiling LLVM.Target.SystemZ ( LLVM/Target/SystemZ.hs, dist-ghc/build/LLVM/Target/SystemZ.o ) [ 3 of 24] Compiling LLVM.Target.Sparc ( LLVM/Target/Sparc.hs, dist-ghc/build/LLVM/Target/Sparc.o ) [ 4 of 24] Compiling LLVM.Target.PowerPC ( LLVM/Target/PowerPC.hs, dist-ghc/build/LLVM/Target/PowerPC.o ) [ 5 of 24] Compiling LLVM.Target.PIC16 ( LLVM/Target/PIC16.hs, dist-ghc/build/LLVM/Target/PIC16.o ) [ 6 of 24] Compiling LLVM.Target.Mips ( LLVM/Target/Mips.hs, dist-ghc/build/LLVM/Target/Mips.o ) [ 7 of 24
Bug#678787: github-backup: FTBFS: build-dependency not installable: libghc-github-dev
Source: github-backup Version: 1.20120314 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install github-backup build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-github-backup-dummy : Depends: libghc-github-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/github-backup_1.20120314_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678788: parted: FTBFS: ABI has changed. Please, update you ABI package version.
Source: parted
Version: 2.3-9.2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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»/build-deb'
CDPATH=${ZSH_VERSION+.}: cd .. true -I m4
cd .. true --gnu
--- ../scripts/data/abi/baseline_symbols.txt 2012-06-23 16:16:27.588576525
+
+++ ./current_symbols.txt 2012-06-23 16:18:05.320560692 +
@@ -501,15 +501,11 @@
FUNC:version_etc_ar
FUNC:version_etc_arn
FUNC:version_etc_va
-FUNC:x2nrealloc
FUNC:x2realloc
FUNC:xalloc_die
FUNC:xcalloc
-FUNC:xcharalloc
FUNC:xmalloc
FUNC:xmemdup
-FUNC:xnmalloc
-FUNC:xnrealloc
FUNC:xrealloc
FUNC:xstrdup
FUNC:xstrndup
ABI has changed. Please, update you ABI package version.
make[1]: *** [check-abi] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/24/parted_2.3-9.2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678789: glance: FTBFS: E271 multiple spaces after keyword
Source: glance Version: 2012.1-3.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' bash run_tests.sh -N -p Running pep8 ... glance/common/auth.py:136:19: E271 multiple spaces after keyword glance/common/cfg.py:751:31: E502 the backslash is redundant between brackets glance/common/cfg.py:841:23: E711 comparison to None should be 'if cond is not None:' glance/common/client.py:575:39: E272 multiple spaces before keyword glance/common/client.py:577:39: E272 multiple spaces before keyword glance/common/utils.py:344:21: E711 comparison to None should be 'if cond is None:' glance/registry/db/migrate_repo/versions/003_add_disk_format.py:97:46: E711 comparison to None should be 'if cond is None:' glance/registry/db/migrate_repo/versions/010_default_update_at.py:67:39: E711 comparison to None should be 'if cond is None:' glance/tests/stubs.py:134:52: E502 the backslash is redundant between brackets glance/tests/unit/test_cfg.py:753:78: E502 the backslash is redundant between brackets make[1]: *** [override_dh_auto_test] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/glance_2012.1-3.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678790: kdeutils: FTBFS: cp: cannot stat `debian/tmp/usr/lib/libkerfuffle.so.4.7.0': No such file or directory
Source: kdeutils Version: 4:4.7.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make[3]: Nothing to be done for `preinstall'. make[3]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: Debian -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/arkpart.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/arkpart.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/ark_part.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/ark/ark_part.rc -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/ark -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/bin/ark -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/ServiceMenus/ark_addtoservicemenu.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/ServiceMenus/ark_servicemenu.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/applications/kde4/ark.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/ark/arkui.rc -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/libextracthere.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/libextracthere.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/ark_dndextract.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libarchive.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libarchive.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_libarchive.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_libarchive_readonly.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_clirar.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_clirar.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_clirar.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_cli7z.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_cli7z.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_cli7z.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_clizip.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_clizip.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_clizip.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libgz.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libgz.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_libgz.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libbz2.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libbz2.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_libbz2.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libxz.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/kerfuffle_libxz.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kerfuffle_libxz.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libkerfuffle.so.4.8.0 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libkerfuffle.so.4 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libkerfuffle.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/servicetypes/kerfufflePlugin.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/config.kcfg/ark.kcfg -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/ark/index.cache.bz2 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/ark/man-ark.1.docbook -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/ark/index.docbook -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/ark/ark-mainwindow.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/man/man1/ark.1 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libkdeinit4_kcalc.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/kcalc -- Set runtime path of /«PKGBUILDDIR»/debian/tmp/usr/bin/kcalc to /usr/lib/kde4/libkdeinit -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/applications/kde4/kcalc.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/config.kcfg/kcalc.kcfg -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kcalc/kcalcui.rc -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kcalc/scienceconstants.xml -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/kconf_update/kcalcrc.upd
Bug#678791: libsvn-notify-mirror-perl: FTBFS: tests failed
Source: libsvn-notify-mirror-perl
Version: 0.03800-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
dh_testdir
# redirect STDIN to avoid any prompting
/usr/bin/perl Build.PL installdirs=vendor /dev/null
Checking optional features...
config_supportdisabled
requires:
! SVN::Notify::Config is not installed
rsync_support.disabled
requires:
! File::Rsync is not installed
ssh_support...disabled
requires:
! Net::SSH is not installed
ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions
of the modules indicated above before proceeding with this installation
Run 'Build installdeps' to install missing prerequisites.
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'SVN-Notify-Mirror' version '0.038'
/usr/bin/perl Build
Building SVN-Notify-Mirror
SENDMAIL=/dev/null /usr/bin/perl Build test
# Failed test 'Correct files updated in project1/trunk at rev: 2'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/dir1} = Does not exist
# $expected-{project1/tags/TRUNK-1135534439/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/'.':} = 'Updating'
# $expected-{project1/tags/TRUNK-1135534439/'.':} = Does not exist
# Failed test 'Correct files updated in project1/branches/branch1 at rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/branches/branch1/dir1} = Does not exist
# $expected-{project1/branches/branch1/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/branches/branch1 at rev: 5'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/branches/branch1/'.':} = 'Updating'
# $expected-{project1/branches/branch1/'.':} = Does not exist
# Failed test 'Correct files updated in project1/trunk at rev: 6'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/trunk at rev: 2'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/dir1} = Does not exist
# $expected-{project1/tags/TRUNK-1135534439/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/'.':} = 'Updating'
# $expected-{project1/tags/TRUNK-1135534439/'.':} = Does not exist
# Failed test 'Correct files updated in project1/branches/branch1 at rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/branches/branch1/dir1} = Does not exist
# $expected-{project1/branches/branch1/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/branches/branch1 at rev: 5'
# at t/coretests.pm line 196
Bug#678792: python-scrapy: FTBFS: ImportError: cannot import name uses_query
Source: python-scrapy
Version: 0.14.1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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»'
dh_auto_clean
Traceback (most recent call last):
File setup.py, line 93, in module
version = __import__('scrapy').__version__
File /«PKGBUILDDIR»/scrapy/__init__.py, line 18, in module
from scrapy.xlib import twisted_250_monkeypatches, urlparse_monkeypatches
File /«PKGBUILDDIR»/scrapy/xlib/urlparse_monkeypatches.py, line 1, in
module
from urlparse import urlparse, uses_netloc, uses_query
ImportError: cannot import name uses_query
dh_auto_clean: python setup.py clean -a returned exit code 1
make[1]: *** [override_dh_auto_clean] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/24/python-scrapy_0.14.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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678737: marked as done (Cross site request forgery)
Your message dated Sun, 24 Jun 2012 09:47:34 + with message-id e1sijpq-0004bs...@franck.debian.org and subject line Bug#678737: fixed in extplorer 2.1.0b6+dfsg.3-3 has caused the Debian Bug report #678737, regarding Cross site request forgery 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.) -- 678737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: extplorer Severity: grave As per: http://www.autosectools.com/Advisories/eXtplorer.2.1.RC3_Cross-site.Request.Forgery_174.html there's a CSRF security issue in eXtplorer. Patch is on its way, I'm just opening a bug report to track it. Thomas ---End Message--- ---BeginMessage--- Source: extplorer Source-Version: 2.1.0b6+dfsg.3-3 We believe that the bug you reported is fixed in the latest version of extplorer, which is due to be installed in the Debian FTP archive: extplorer_2.1.0b6+dfsg.3-3.debian.tar.gz to main/e/extplorer/extplorer_2.1.0b6+dfsg.3-3.debian.tar.gz extplorer_2.1.0b6+dfsg.3-3.dsc to main/e/extplorer/extplorer_2.1.0b6+dfsg.3-3.dsc extplorer_2.1.0b6+dfsg.3-3_all.deb to main/e/extplorer/extplorer_2.1.0b6+dfsg.3-3_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 678...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated extplorer 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, 22 Jun 2012 13:48:15 + Source: extplorer Binary: extplorer Architecture: source all Version: 2.1.0b6+dfsg.3-3 Distribution: unstable Urgency: high Maintainer: Thomas Goirand z...@debian.org Changed-By: Thomas Goirand z...@debian.org Description: extplorer - web file explorer and manager using Ext JS Closes: 678737 Changes: extplorer (2.1.0b6+dfsg.3-3) unstable; urgency=high . * Fixes an Cross Site Request forgery security problem if user is logged by applyting upstream patch (Closes: #678737). * Bumps to compat level 8 and debhelper 8. * Added build-arch and build-indep targets in debian/rules. * Standards-Version is now 3.9.3. * Now uses format 1.0 for debian/copyright. * Removed leading article in short desc. Checksums-Sha1: 8c2a02dcf59b09d428594b08f65bb9f289587005 1259 extplorer_2.1.0b6+dfsg.3-3.dsc 6d711f234f04ef6cbe35bf7de0f23ef97f390df5 10398 extplorer_2.1.0b6+dfsg.3-3.debian.tar.gz 442d15ef192f4499b2634d6ad1458422ce276e4e 351832 extplorer_2.1.0b6+dfsg.3-3_all.deb Checksums-Sha256: 3b05132d27335b7f087438f098e223c4325728e3f58f5de4d0d0364ee9647ed1 1259 extplorer_2.1.0b6+dfsg.3-3.dsc 2701fddb0cce5890853601caab57adb05797392d472159f06b802633da47989e 10398 extplorer_2.1.0b6+dfsg.3-3.debian.tar.gz 47f622f6b237b472a33295fdba53286bf8bc14b6200fc7fd377bbad4a862f4eb 351832 extplorer_2.1.0b6+dfsg.3-3_all.deb Files: 96c4fdb9f7882cbdeebcff96b5124e75 1259 web optional extplorer_2.1.0b6+dfsg.3-3.dsc bec2a803aa70695a4fd30a971942bf10 10398 web optional extplorer_2.1.0b6+dfsg.3-3.debian.tar.gz 8b9d4538cee113c0a00dc2d8ffa53d07 351832 web optional extplorer_2.1.0b6+dfsg.3-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/m4NAACgkQl4M9yZjvmkkw+gCeJSjW9/vgpTznQEAStz0z0PfI 6n8AoI2HOpYXJ6H4wBfYOwHvxmjHtgJW =TmU+ -END PGP SIGNATURE- ---End Message---
Bug#676045: Needs writable $HOME during build
tags 676045 + patch thanks Dear maintainer, Attached is a patch to fix that, as the build needs a writable $HOME during build. I have not yet prepared a final NMU to upload. But as the freeze for Wheezy is near, I can do if needed. In any case it will be delayed if okay. Regards, Salvatore diff -Nru nautilus-image-manipulator-1.1/debian/changelog nautilus-image-manipulator-1.1/debian/changelog --- nautilus-image-manipulator-1.1/debian/changelog 2012-05-05 10:49:58.0 +0200 +++ nautilus-image-manipulator-1.1/debian/changelog 2012-06-24 11:45:14.0 +0200 @@ -1,3 +1,12 @@ +nautilus-image-manipulator (1.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Set temporary writable $HOME directory during build. +Fix FTBFS IOError: [Errno 2] No such file or directory: +'/sbuild-nonexistent/.nautilus-image-manipulator.ini'. (Closes: #676045) + + -- Salvatore Bonaccorso car...@debian.org Sun, 24 Jun 2012 11:45:08 +0200 + nautilus-image-manipulator (1.1-1) unstable; urgency=low * New upstream release diff -Nru nautilus-image-manipulator-1.1/debian/rules nautilus-image-manipulator-1.1/debian/rules --- nautilus-image-manipulator-1.1/debian/rules 2012-04-30 23:36:45.0 +0200 +++ nautilus-image-manipulator-1.1/debian/rules 2012-06-24 11:44:48.0 +0200 @@ -1,7 +1,14 @@ #!/usr/bin/make -f +BUILDHOME = $(CURDIR)/debian/build + +override_dh_clean: + dh_clean + rm -rf $(BUILDHOME) + override_dh_auto_test: - nosetests + mkdir -p $(BUILDHOME) + HOME=$(BUILDHOME) nosetests override_dh_auto_install: dh_auto_install -- --install-lib=/usr/share/nautilus-image-manipulator \ signature.asc Description: Digital signature
Processed: Needs writable $HOME during build
Processing commands for cont...@bugs.debian.org: tags 676045 + patch Bug #676045 [src:nautilus-image-manipulator] nautilus-image-manipulator: FTBFS: IOError: [Errno 2] No such file or directory: '/sbuild-nonexistent/.nautilus-image-manipulator.ini' Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 676045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676045 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#673304: libextractor: sponsorship for libpoppler transition
Hi Adam, I've grabbed your current git master and tested it locally, and would happily sponsor the upload to the archive. Let me know via email, or catch me on IRC (infinity) and tell me if that's cool. If I don't hear from you soon(ish), I'll probably just sponsor your current git head anyway, to get this RC bug cleared out. ;) I uploaded a new version last night on mentors, you are welcome to upload it: http://mentors.debian.net/debian/pool/main/libe/libextractor/libextractor_0.6.3-5.dsc Thanks ! Bertrand -- 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 678580 is serious
Processing commands for cont...@bugs.debian.org: severity 678580 serious Bug #678580 [kupfer] kupfer: program fails to start Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 678580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678580 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#676717: dh_installcatalogs transition and w3c-dtd-xhtml removal bugs
On Sun, Jun 24, 2012 at 02:22:06AM +0900, Osamu Aoki wrote: So you mean --quiet and error exit is good? I see. I still worry about being too quiet to hide source of the trouble. Do you think we need As far as I can see --quiet never hides error conditions. After all --quiet is not that quiet. It suppresses the Updating the super catalog... and it suppresses warnings about leftover or broken package catalogs. So whenever the exit code is non-zero there will be some (die) message. update-catalog --quiet --update-super || update-catalog --update-super If --quiet gives good enough indication of error, we do not need this. I have not checked Maybe I am too worried with no reason. If you think this is OK, no problem with me. As laid out above and as can be seen by searching update-catalog for '$quiet' the --quiet switch never suppresses messages for failures that result in a non-zero exit. So your proposed solution just prints the error twice (assuming idempotency) plus some additional messages. What kind of failures are normal errors? Which failures would you like not to be loud? I have no idea. That is why I marked FYI. Maybe non-essential variation. Unless you can answer the questions above, I see little point in changing the current --quiet behaviour. So thanks for having a look even though the issue turned out to be a non-issue thus far. It might well have been one. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673304: marked as done (libextractor: please migrate the libpoppler-dev build dependency to libpoppler-private-dev)
Your message dated Sun, 24 Jun 2012 10:49:24 + with message-id e1sikng-0002i5...@franck.debian.org and subject line Bug#673304: fixed in libextractor 1:0.6.3-5 has caused the Debian Bug report #673304, regarding libextractor: please migrate the libpoppler-dev build dependency to libpoppler-private-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 673304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libextractor Version: 0.6.3-4 Severity: wishlist Tags: patch Hi, I'm planning a move of the poppler private headers, currently shipped in libpoppler-dev, out of that package (which is installed by other poppler -dev packages) to a new libpoppler-private-dev. Could you please switch the libpoppler-dev build dependency to libpoppler-private-dev? Attached there is a patch for it. Thanks, -- Pino --- a/debian/control +++ b/debian/control @@ -5,7 +5,7 @@ Maintainer: Bertrand Marc beberking@gma Build-Depends: debhelper (= 9), autopoint, dh-autoreconf, libbz2-dev, libexiv2-dev, libflac-dev, libgsf-1-dev, libglib2.0-dev, libgtk2.0-dev, - libmagick++-dev, libmpeg2-4-dev, libpoppler-dev, libqt4-dev, libltdl-dev, + libmagick++-dev, libmpeg2-4-dev, libpoppler-private-dev, libqt4-dev, libltdl-dev, librpm-dev, libvorbis-dev, pkg-config, zlib1g-dev Standards-Version: 3.9.3 Homepage: http://www.gnu.org/software/libextractor/ ---End Message--- ---BeginMessage--- Source: libextractor Source-Version: 1:0.6.3-5 We believe that the bug you reported is fixed in the latest version of libextractor, which is due to be installed in the Debian FTP archive: extract_0.6.3-5_amd64.deb to main/libe/libextractor/extract_0.6.3-5_amd64.deb extract_0.6.3-5_i386.deb to main/libe/libextractor/extract_0.6.3-5_i386.deb libextractor-dbg_0.6.3-5_amd64.deb to main/libe/libextractor/libextractor-dbg_0.6.3-5_amd64.deb libextractor-dbg_0.6.3-5_i386.deb to main/libe/libextractor/libextractor-dbg_0.6.3-5_i386.deb libextractor-dev_0.6.3-5_amd64.deb to main/libe/libextractor/libextractor-dev_0.6.3-5_amd64.deb libextractor-dev_0.6.3-5_i386.deb to main/libe/libextractor/libextractor-dev_0.6.3-5_i386.deb libextractor-plugins_0.6.3-5_amd64.deb to main/libe/libextractor/libextractor-plugins_0.6.3-5_amd64.deb libextractor-plugins_0.6.3-5_i386.deb to main/libe/libextractor/libextractor-plugins_0.6.3-5_i386.deb libextractor3_0.6.3-5_amd64.deb to main/libe/libextractor/libextractor3_0.6.3-5_amd64.deb libextractor3_0.6.3-5_i386.deb to main/libe/libextractor/libextractor3_0.6.3-5_i386.deb libextractor_0.6.3-5.debian.tar.gz to main/libe/libextractor/libextractor_0.6.3-5.debian.tar.gz libextractor_0.6.3-5.dsc to main/libe/libextractor/libextractor_0.6.3-5.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 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bertrand Marc beberk...@gmail.com (supplier of updated libextractor 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, 23 Jun 2012 18:45:49 +0200 Source: libextractor Binary: libextractor3 libextractor-plugins libextractor-dbg libextractor-dev extract Architecture: amd64 i386 source Version: 1:0.6.3-5 Distribution: unstable Urgency: low Maintainer: Bertrand Marc beberk...@gmail.com Changed-By: Bertrand Marc beberk...@gmail.com Closes: 673304 675063 Description: extract- displays meta-data from files of arbitrary type libextractor3 - extracts meta-data from files of arbitrary type (library) libextractor-dbg - extracts meta-data from files of arbitrary type (debug) libextractor-dev - extracts meta-data from files of arbitrary type (development) libextractor-plugins - extracts meta-data from files of arbitrary type (plugins) Changes: libextractor (1:0.6.3-5) unstable; urgency=low . * debian/control: add Vcs-Git and Vcs-browser fields. * Switch the libpoppler-dev build dependency to libpoppler-private-dev (Closes: #673304). * Include a patch to load plugins from path with underscore, thanks to Harun Trefry (Closes: #675063). Checksums-Sha1: 5624e25086a431a21f9c90f02d4919677acf66d2 1706 libextractor_0.6.3-5.dsc
Bug#677202: biber packages version 0.9.9+git2012426-3 is beta and requires beta version of biblatex
Hi On Di, 19 Jun 2012, Danai SAE-HAN wrote: Urgh, just got a half working X.org env. Still skewed, but slightly workable. Thanks for your patience. Off to work now. Any progress here? Freeze is soon! Did you also see the email of Werner concerning a stability fix in CJK? I had to return to Beijing on a business trip again, and couldn't upload the packages before my flight. Network communication is not always easy in China. I have just tried a number of Debian machines, but I don't have my SSH key on this Windows laptop. I am now trying to get gpgsm to work on Windows so I can convert my GnuPG key. Google is not always available here so I will quickly catch up on the mail from Werner now that I have network access. Thanks for mentioning this. Luckily, the Debian source for cjk is not too complicated: just update the ISO date in debian/changelog, and that's it. BR -- Danai -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675971: what should we be doing?
Hi tcwardr...@gmail.com, I confess I'm not entirely certain how to respond to this suggestion of yours ... If, on the one hand, you actually are a black-hat, who has put in the effort to actually analyse this for your own benefit - then I tip my hat to you and your art, and wish you all the best in your future endeavours. I'm sure it's quite evident that you'll find lots of low hanging fruit here, even if we don't plant a whole new orchard of it for you. If, on the other hand, you aren't, and haven't ... then, uh ... maybe we should discuss the other ... uh, opportunities ... open to you, like ... uh ... how about this one perhaps: I have many milleons of DOLLURS ($ many,000,000,000,000) LEGITAMITELY obtained from the vaults of Sadd@m that I wish to transfer to YOUR b * n k a c c * u n t. But we must do it with UT MOST SECR3CY. I am sure that you will understand this valuabl proposition for our mutial benerfit. We can let all users decide on their own if they want to be a part of this once in a lifetime bonanza, right? It's not like they'd blame us if all the extra work to put them at risk then blew up in their faces ... would they? On Sat, Jun 23, 2012 at 09:54:07PM +0200, tcwardr...@gmail.com wrote: Hi folks, I guess shipping both versions with wheezy is not a viable option? At least I think that it would make sense. Disclaimer in the readme, explanation of the situation, if a major security exploit does surface (a mumble-client-crash is not a major security risk imho), remove that second version (if there is no somewhat easy fix at that time). Call the package mumble-client-buggy that conflicts with the normal client and I guess all users can decide on their own if they want to be safe or actually talk to other people. regards Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678580: marked as done (kupfer: program fails to start)
Your message dated Sun, 24 Jun 2012 11:17:54 + with message-id e1sikpg-0004xq...@franck.debian.org and subject line Bug#678580: fixed in kupfer 0+v208-2 has caused the Debian Bug report #678580, regarding kupfer: program fails to start 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.) -- 678580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kupfer Version: 0+v208-1 Severity: important Kupfer fails to start with the following backtrace: $ kupfer Kupfer: A free software (GPLv3+) launcher Copyright © 2007--2011 Ulrik Sverdrup with others http://kaizer.se/wiki/kupfer/ Traceback (most recent call last): File /usr/share/kupfer/kupfer.py, line 4, in module main.main() File /usr/share/kupfer/kupfer/main.py, line 182, in main gtkmain(quiet) File /usr/share/kupfer/kupfer/main.py, line 160, in gtkmain from kupfer.ui import browser File /usr/share/kupfer/kupfer/ui/browser.py, line 23, in module from kupfer.core import data, relevance, learn File /usr/share/kupfer/kupfer/core/data.py, line 11, in module from kupfer.obj import base, sources, compose File /usr/share/kupfer/kupfer/obj/compose.py, line 7, in module from kupfer import puid File /usr/share/kupfer/kupfer/puid.py, line 20, in module from kupfer.core import qfurl File /usr/share/kupfer/kupfer/core/qfurl.py, line 11, in module urlparse.uses_fragment.append(QFURL_SCHEME) AttributeError: 'module' object has no attribute 'uses_fragment' -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kupfer depends on: ii dbus 1.6.0-1 ii python2.7.3~rc2-1 ii python-dbus 1.1.0-1 ii python-gobject3.2.2-1 ii python-gtk2 2.24.0-3 ii python-keybinder 0.2.2-4 ii python-xdg0.19-4 Versions of packages kupfer recommends: ii python-keyring 0.7.1-1 ii python-wnck 2.32.0+dfsg-2+b1 Versions of packages kupfer suggests: ii python-cjson 1.0.5-4+b1 ii python-gdata 2.0.17-1 ii python-qrencode 1.01-2+b1 -- no debconf information ---End Message--- ---BeginMessage--- Source: kupfer Source-Version: 0+v208-2 We believe that the bug you reported is fixed in the latest version of kupfer, which is due to be installed in the Debian FTP archive: kupfer_0+v208-2.debian.tar.gz to main/k/kupfer/kupfer_0+v208-2.debian.tar.gz kupfer_0+v208-2.dsc to main/k/kupfer/kupfer_0+v208-2.dsc kupfer_0+v208-2_all.deb to main/k/kupfer/kupfer_0+v208-2_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 678...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Falavigna dktrkr...@debian.org (supplier of updated kupfer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 24 Jun 2012 12:34:02 +0200 Source: kupfer Binary: kupfer Architecture: source all Version: 0+v208-2 Distribution: unstable Urgency: low Maintainer: Luca Falavigna dktrkr...@debian.org Changed-By: Luca Falavigna dktrkr...@debian.org Description: kupfer - fast and lightweight desktop summoner/launcher Closes: 678580 Changes: kupfer (0+v208-2) unstable; urgency=low . * debian/patches/uses_fragment.patch: - Do not die if urlparse doesn't have uses_fragment method anymore, recent Python versions dropped it (Closes: #678580). Checksums-Sha1: 9bfd8c5fa979c27a2db3289374b161e126bdd3e9 2026 kupfer_0+v208-2.dsc 4e2e32cff5a13617ba80f80f537f09a7ff049b2f 14654 kupfer_0+v208-2.debian.tar.gz 58d06b48823844f86f9dd65261917eb5c4d0fe48 851572 kupfer_0+v208-2_all.deb Checksums-Sha256: 9caacec4613e0f12af78d7d281e22bbf87284f2b6eb6d6b6f881474bdda2ebee 2026 kupfer_0+v208-2.dsc 91bb36b551c75203cd9055aa502badcdd5ce62365af30eb36605248ba86bc7a3 14654 kupfer_0+v208-2.debian.tar.gz afede3250f54f825b711e7d66eb7f99a6331230324bb1b1836164630aef7c39b 851572 kupfer_0+v208-2_all.deb Files: 5ca6bca20e01d8aad6b8bd93dade408a 2026 utils
Processed: cloning 678758, reassign -1 to osgi-core, owner -1 ...
Processing commands for cont...@bugs.debian.org: clone 678758 -1 Bug #678758 [src:sisu-ioc] sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date. Bug 678758 cloned as bug 678802 reassign -1 osgi-core Bug #678802 [src:sisu-ioc] sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date. Bug reassigned from package 'src:sisu-ioc' to 'osgi-core'. No longer marked as found in versions sisu-ioc/2.3.0-3. Ignoring request to alter fixed versions of bug #678802 to the same values previously set owner -1 ! Bug #678802 [osgi-core] sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date. Owner recorded as Niels Thykier ni...@thykier.net. retitle -1 osgi-core: Build does not ensure backwards compatible byte-core Bug #678802 [osgi-core] sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date. Changed Bug title to 'osgi-core: Build does not ensure backwards compatible byte-core' from 'sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date.' thanks Stopping processing here. Please contact me if you need assistance. -- 678758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678758 678802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678802 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#678661: marked as done (openssh-server - Fails to start: OpenSSL version mismatch. Built against 1000103f, you have 1000007f)
Your message dated Sun, 24 Jun 2012 11:34:19 + with message-id e1sil59-0006pa...@franck.debian.org and subject line Bug#678661: fixed in openssh 1:6.0p1-2 has caused the Debian Bug report #678661, regarding openssh-server - Fails to start: OpenSSL version mismatch. Built against 1000103f, you have 107f 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.) -- 678661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: openssh-server Version: 1:6.0p1-1 Severity: serious sshd fails to start and therfor upgrade: | Setting up openssh-server (1:6.0p1-1) ... | Installing new version of config file /etc/init.d/ssh ... | Installing new version of config file /etc/pam.d/sshd ... | OpenSSL version mismatch. Built against 1000103f, you have 107f | OpenSSL version mismatch. Built against 1000103f, you have 107f | invoke-rc.d: initscript ssh, action restart failed. If openssh-server needs a new version of libssl1.0.0, it must depend on it. This already brought us a breaks in libssl1.0.0, so I intend to fix this with a NMU if necessary. Bastian -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-server depends on: ii adduser 3.113+nmu2 add and remove users and groups ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii dpkg 1.15.8.12 Debian package management system ii libc6 2.13-32Embedded GNU C Library: Shared lib ii libcomerr21.42.2-2 common error description library ii libgssapi-krb5-2 1.10.1+dfsg-1 MIT Kerberos runtime libraries - k ii libkrb5-3 1.10.1+dfsg-1 MIT Kerberos runtime libraries ii libpam-modules1.1.1-6.1+squeeze1 Pluggable Authentication Modules f ii libpam-runtime1.1.1-6.1+squeeze1 Runtime support for the PAM librar ii libpam0g 1.1.1-6.1+squeeze1 Pluggable Authentication Modules l ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii libssl1.0.0 1.0.0g-1 SSL shared libraries ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii openssh-client1:6.0p1-1 secure shell (SSH) client, for sec ii procps1:3.3.2-3 /proc file system utilities ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages openssh-server recommends: ii openssh-blacklist 0.4.1 list of default blacklisted OpenSS pn openssh-blacklist-extra none (no description available) ii xauth 1:1.0.4-1 X authentication utility Versions of packages openssh-server suggests: pn molly-guard none (no description available) pn monkeysphere none (no description available) pn rssh none (no description available) pn ssh-askpass none (no description available) pn ufw none (no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- Source: openssh Source-Version: 1:6.0p1-2 We believe that the bug you reported is fixed in the latest version of openssh, which is due to be installed in the Debian FTP archive: openssh-client-udeb_6.0p1-2_i386.udeb to main/o/openssh/openssh-client-udeb_6.0p1-2_i386.udeb openssh-client_6.0p1-2_i386.deb to main/o/openssh/openssh-client_6.0p1-2_i386.deb openssh-server-udeb_6.0p1-2_i386.udeb to main/o/openssh/openssh-server-udeb_6.0p1-2_i386.udeb openssh-server_6.0p1-2_i386.deb to main/o/openssh/openssh-server_6.0p1-2_i386.deb openssh_6.0p1-2.debian.tar.gz to main/o/openssh/openssh_6.0p1-2.debian.tar.gz openssh_6.0p1-2.dsc to main/o/openssh/openssh_6.0p1-2.dsc ssh-askpass-gnome_6.0p1-2_i386.deb to main/o/openssh/ssh-askpass-gnome_6.0p1-2_i386.deb ssh-krb5_6.0p1-2_all.deb to main/o/openssh/ssh-krb5_6.0p1-2_all.deb ssh_6.0p1-2_all.deb to main/o/openssh/ssh_6.0p1-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the
Bug#678746: desktop-base: Joy theme is a mix of incompatibly-licensed works
On Sun, Jun 24, 2012 at 11:13:31AM +0200, Francesco Poli (wintermute) wrote: Package: desktop-base Version: 7.0.0~exp2 Severity: serious Justification: Policy 2.3 Hello, I read about the new Joy theme [1][2]. [1] http://blog.pault.ag/post/25614704596/my-quest-to-get-desktop-base-set-before-wheezy [2] http://blog.pault.ag/post/25747178764/debian-desktop-7-0-0-exp2-in-experimental It looks nice, but it seems to have licensing issues. In the debian/copyright file [3] I read: | The Joy theme is © 2012 Adrien Aubourg and released under the CC-BY-SA 3.0 | license. | | The Joy plymouth theme is Copyright © 2009 Canonical Ltd., | Copyright © 2010 Aurélien COUDERC and Copyright © 2012 Jonathan Carter under | the GPLv2+, with work from Adrien Aubourg under the CC-BY-SA 3.0 License. | | The Joy KDM, GDM and KSplash grub theme are © 2012 Paul Tagliamonte and released | under the CC-BY-SA 3.0 license, with work from all the previous authors, and | Adrien Aubourg. [3] http://packages.debian.org/changelogs/pool/main/d/desktop-base/desktop-base_7.0.0~exp2/copyright First of all, these debian/copyright paragraphs fail to acknowledge that the Joy theme is based on the Debian “Open Use” (without “Debian” word) logo. But this may be fixed easily. ACK'd. I'll fix this tonight. Thank you! The major issue seems to be that the Joy plymouth theme mixes parts released under CC-by-sa-v3.0 and parts released under GPLv2+. Since CC-by-sa-v3.0 is incompatible with GPLv2+, I would say that the resulting work is legally undistributable. This *might* be true if it was two bits of code that get linked together, but since Plymouth (and the plugin, which is GPLv2) only render the CC-BY-SA 3.0 work, it should be fine. I'll CC debian-leagl for comment If this was the case, a lot of games would have to be removed from the archive. The same issue seems to hold for the Joy KDM, GDM and KSplash grub theme, since it said to incorporate work from all the previous authors. If all the previous authors includes Aurélien COUDERC and/or Jonathan Carter, it seems that their work is under GPLv2+ and thus the incompatibility of CC-by-sa-v3.0 again kicks in. Johnathan Carter contributed to the Plymouth script, not the artwork. The artwork is still the same. In this case, I'll modify this line to show the files that I edited are still GPLv2, and the images it's self is CC-BY-SA 3.0. No problem, no big deal. (For the record, I am also convinced that CC-by-sa-v3.0 fails to meet the DFSG, but that's another story, since FTP masters disagree with me, unfortunately). I hope the incompatibility issue may be fixed soon for the Joy theme. Not such a big deal :) Since everything else in the desktop-base package is GPL-compatible, I strongly recommend to persuade Adrien Aubourg and Paul Tagliamonte I'm fine with whatever license comes up. I just wanted to keep consistancy. to re-license their work under the terms of the GNU GPL v2 or later. Or, at least, to dual-license it under CC-by-sa-v3.0 and GPLv2+. (In the latter case, the complete text of CC-by-sa-v3.0 should be included in the debian/copyright file, though.) Bye and thanks for your time. Thank you, Paul signature.asc Description: Digital signature
Bug#678804: maelstrom: FTBFS on armhf: netlogic/liblogic.a: could not read symbols: Bad value
Source: maelstrom Version: 1.4.3-L3.0.6+main-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on armhf: | g++ -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -g -O2 -g -O2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I. -I./netlogic -I./screenlib -I./maclib -DLIBDIR=\/usr/lib/games/maelstrom\ -DBMPDIR=\/usr/share/games/maelstrom\ -fPIE -pie -Wl,-z,relro -Wl,-z,now -o Maelstrom checksum.o controls.o dialog.o fastrand.o init.o load.o main.o myerror.o netscore.o rect.o scores.o netlogic/liblogic.a screenlib/libSDLscreen.a maclib/libSDLmac.a -lm -L/usr/lib/arm-linux-gnueabihf -lSDL -lSDL_net | /usr/bin/ld: netlogic/liblogic.a(about.o): relocation R_ARM_THM_MOVW_ABS_NC against `sound' can not be used when making a shared object; recompile with -fPIC | netlogic/liblogic.a: could not read symbols: Bad value | collect2: ld returned 1 exit status | make[2]: *** [Maelstrom] Error 1 Full build logs: https://buildd.debian.org/status/package.php?p=maelstrom Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678583: texstudio: missing build dependency on zlib1g-dev
tag 678583 pending thanks On 22.06.2012 23:53, Pino Toscano wrote: as a followup of #675497: when doing my rebuilds for the drop of libfontconfig1-dev from libpoppler-dev, apparently I noted only pkg-config (already fixed, thanks!) as missing for texstudio... while there's also zlib1g-dev that is lacking :-/ (and zlib is used by the synctex code); it was previously pulled by the dependency chain: Fixed in git. Tom -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677040: marked as done (icedove: New Upstream (10.0.5))
Your message dated Sun, 24 Jun 2012 11:47:37 +
with message-id e1sili1-00077k...@franck.debian.org
and subject line Bug#677040: fixed in icedove 10.0.5-1
has caused the Debian Bug report #677040,
regarding icedove: New Upstream (10.0.5)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
677040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: icedove
Severity: serious
Tags: sid, wheezy, security
http://www.mozilla.org/security/known-vulnerabilities/thunderbirdESR.html#thunderbird
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet: http://people.progress-technologies.net/~daniel.baumann/
---End Message---
---BeginMessage---
Source: icedove
Source-Version: 10.0.5-1
We believe that the bug you reported is fixed in the latest version of
icedove, which is due to be installed in the Debian FTP archive:
calendar-google-provider_10.0.5-1_amd64.deb
to main/i/icedove/calendar-google-provider_10.0.5-1_amd64.deb
calendar-timezones_10.0.5-1_amd64.deb
to main/i/icedove/calendar-timezones_10.0.5-1_amd64.deb
icedove-dbg_10.0.5-1_amd64.deb
to main/i/icedove/icedove-dbg_10.0.5-1_amd64.deb
icedove-dev_10.0.5-1_amd64.deb
to main/i/icedove/icedove-dev_10.0.5-1_amd64.deb
icedove_10.0.5-1.debian.tar.gz
to main/i/icedove/icedove_10.0.5-1.debian.tar.gz
icedove_10.0.5-1.dsc
to main/i/icedove/icedove_10.0.5-1.dsc
icedove_10.0.5-1_amd64.deb
to main/i/icedove/icedove_10.0.5-1_amd64.deb
icedove_10.0.5.orig.tar.bz2
to main/i/icedove/icedove_10.0.5.orig.tar.bz2
iceowl-extension_10.0.5-1_amd64.deb
to main/i/icedove/iceowl-extension_10.0.5-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 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Goehre ch...@sigxcpu.org (supplier of updated icedove package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 24 Jun 2012 10:37:07 +0200
Source: icedove
Binary: icedove icedove-dev icedove-dbg calendar-timezones iceowl-extension
calendar-google-provider
Architecture: source amd64
Version: 10.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Alexander Sack a...@debian.org
Changed-By: Christoph Goehre ch...@sigxcpu.org
Description:
calendar-google-provider - Google Calendar support for lighting- and
iceowl-extension
calendar-timezones - Timezone Extension for Sunbird/Iceowl (mandatory)
icedove- mail/news client with RSS and integrated spam filter support
icedove-dbg - Debug Symbols for Icedove
icedove-dev - Development files for Icedove
iceowl-extension - Calendar Extension for Thunderbird/Icedove
Closes: 676505 677040
Changes:
icedove (10.0.5-1) unstable; urgency=low
.
* [9a9ff18] New Upstream version 10.0.5 (Closes: #677040)
* Fixes for MFSA2012-{34,36-38,40}, also known as
CVE-2012-1939, CVE-2012-1937, CVE-2011-3101, CVE-2012-1944,
CVE-2012-1945, CVE-2012-1946, CVE-2012-1947, CVE-2012-1940,
CVE-2012-1941
* [0b143db] rebuild patch queue from patch-queue branch
added patches:
- fixes/Bug-709259-Try-creating-a-named-cursor-before-a-bitm.patch
- fixes/Bug-734490-fix-build-failures-with-Clang-and-GCC-4.7.patch
* [3d769ec] replace transitional depens ttf-lyx with fonts-lyx
(Closes: #676505)
Checksums-Sha1:
9078478e4dc9ff6ceb4827a9fec9fdb21e0c0cb8 2774 icedove_10.0.5-1.dsc
63dbd7663cb26657185e6f7a309c658a7011c352 97028860 icedove_10.0.5.orig.tar.bz2
595bbd60e9ab0eb5a209b0d0b0b833eb67093a30 499585 icedove_10.0.5-1.debian.tar.gz
56821096ff2bb90bfd6f68ca3dbcd20320cfa6b5 18996960 icedove_10.0.5-1_amd64.deb
e9578a761718ce97120903221a4a4d59b687c983 5313440 icedove-dev_10.0.5-1_amd64.deb
88e31cfb7fe3e8f5be3ae968569f58c965e74e78 171671248
icedove-dbg_10.0.5-1_amd64.deb
20ac73d592a21ccd4bbc53c2b70e40a8b7a1f1a3 74640
calendar-timezones_10.0.5-1_amd64.deb
fa648c3f7e478baabc8d9bfc1b99dd663e6f4a53 1229438
iceowl-extension_10.0.5-1_amd64.deb
e576b45e5a1fda850b1204b909506c8030816e7c 88662
calendar-google-provider_10.0.5-1_amd64.deb
Checksums-Sha256:
Processed: found 678802 in 4.3.0-3
Processing commands for cont...@bugs.debian.org: found 678802 4.3.0-3 Bug #678802 [osgi-core] osgi-core: Build does not ensure backwards compatible byte-core There is no source info for the package 'osgi-core' at version '4.3.0-3' with architecture '' Unable to make a source version for version '4.3.0-3' Marked as found in versions 4.3.0-3. thanks Stopping processing here. Please contact me if you need assistance. -- 678802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 678802 in 4.3.0-2, notfound 678802 in 4.3.0-3
Processing commands for cont...@bugs.debian.org: found 678802 4.3.0-2 Bug #678802 [osgi-core] osgi-core: Build does not ensure backwards compatible byte-core There is no source info for the package 'osgi-core' at version '4.3.0-2' with architecture '' Unable to make a source version for version '4.3.0-2' Marked as found in versions 4.3.0-2. notfound 678802 4.3.0-3 Bug #678802 [osgi-core] osgi-core: Build does not ensure backwards compatible byte-core There is no source info for the package 'osgi-core' at version '4.3.0-3' with architecture '' Unable to make a source version for version '4.3.0-3' No longer marked as found in versions 4.3.0-3. thanks Stopping processing here. Please contact me if you need assistance. -- 678802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678802 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#678763: marked as done (embassy-domsearch: FTBFS: unsatisfiable build-dependencies: emboss-lib ( 6.3.2~) but 6.4.0-2 is to be installed)
Your message dated Sun, 24 Jun 2012 13:53:16 +0200 with message-id 20120624115316.gd30...@an3as.eu and subject line Re: Bug#678763: embassy-domsearch: FTBFS: unsatisfiable build-dependencies: emboss-lib ( 6.3.2~) but 6.4.0-2 is to be installed has caused the Debian Bug report #678763, regarding embassy-domsearch: FTBFS: unsatisfiable build-dependencies: emboss-lib ( 6.3.2~) but 6.4.0-2 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 678763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: embassy-domsearch Version: 0.1.0++20100721-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install embassy-domsearch build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-embassy-domsearch-dummy : Depends: emboss-lib ( 6.3.2~) but 6.4.0-2 is to be installed Depends: libgd2-xpm-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/embassy-domsearch_0.1.0++20100721-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- The package was just upgraded to 0.1.0+20110714-1 - the problem is probably a care condition and thus I'm closing the bug Andreas. On Sun, Jun 24, 2012 at 11:34:13AM +0200, Lucas Nussbaum wrote: Source: embassy-domsearch Version: 0.1.0++20100721-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install embassy-domsearch build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-embassy-domsearch-dummy : Depends: emboss-lib ( 6.3.2~) but 6.4.0-2 is to be installed Depends: libgd2-xpm-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/embassy-domsearch_0.1.0++20100721-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Debian-med-packaging mailing list debian-med
Bug#678770: marked as done (libextractor: FTBFS: dh_install: libextractor3 missing files (usr/lib/*/libextractor/libextractor_pdf.so), aborting)
Your message dated Sun, 24 Jun 2012 13:56:46 +0200 with message-id 4fe7007e.9080...@gmail.com and subject line Re: Bug#678770: libextractor: FTBFS: dh_install: libextractor3 missing files (usr/lib/*/libextractor/libextractor_pdf.so), aborting has caused the Debian Bug report #678770, regarding libextractor: FTBFS: dh_install: libextractor3 missing files (usr/lib/*/libextractor/libextractor_pdf.so), aborting 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.) -- 678770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libextractor Version: 1:0.6.3-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»' make[4]: Nothing to be done for `install-exec-am'. /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig' /usr/bin/install -c -m 644 libextractor.pc '/«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig' make[4]: Leaving directory `/«PKGBUILDDIR»' make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' # Removing useless files rm -f debian/tmp/usr/lib/*/*.la rm -f debian/tmp/usr/lib/*/libextractor/*.la rm -f debian/tmp/usr/share/info/dir* make[1]: Leaving directory `/«PKGBUILDDIR»' debian/rules override_dh_install make[1]: Entering directory `/«PKGBUILDDIR»' dh_install --fail-missing dh_install: libextractor3 missing files (usr/lib/*/libextractor/libextractor_pdf.so), aborting make[1]: *** [override_dh_install] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/libextractor_0.6.3-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- libextractor 0.6.3-5 was uploaded an hour ago and should fix this bug. Cheers, Bertrand ---End Message---
Bug#678347: marked as done (libffado: FTBFS on powerpc)
Your message dated Sun, 24 Jun 2012 12:03:35 + with message-id e1silxt-q4...@franck.debian.org and subject line Bug#678347: fixed in libffado 2.0.99+svn2171-1 has caused the Debian Bug report #678347, regarding libffado: FTBFS on powerpc 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.) -- 678347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libffado Version: 2.0.99+svn2163-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Please look at https://buildd.debian.org/status/package.php?p=libffado 2.0.99+svn2163 fails to build on powerpc ---End Message--- ---BeginMessage--- Source: libffado Source-Version: 2.0.99+svn2171-1 We believe that the bug you reported is fixed in the latest version of libffado, which is due to be installed in the Debian FTP archive: ffado-dbus-server_2.0.99+svn2171-1_amd64.deb to main/libf/libffado/ffado-dbus-server_2.0.99+svn2171-1_amd64.deb ffado-mixer-qt4_2.0.99+svn2171-1_all.deb to main/libf/libffado/ffado-mixer-qt4_2.0.99+svn2171-1_all.deb ffado-tools_2.0.99+svn2171-1_amd64.deb to main/libf/libffado/ffado-tools_2.0.99+svn2171-1_amd64.deb libffado-dev_2.0.99+svn2171-1_amd64.deb to main/libf/libffado/libffado-dev_2.0.99+svn2171-1_amd64.deb libffado2_2.0.99+svn2171-1_amd64.deb to main/libf/libffado/libffado2_2.0.99+svn2171-1_amd64.deb libffado_2.0.99+svn2171-1.debian.tar.gz to main/libf/libffado/libffado_2.0.99+svn2171-1.debian.tar.gz libffado_2.0.99+svn2171-1.dsc to main/libf/libffado/libffado_2.0.99+svn2171-1.dsc libffado_2.0.99+svn2171.orig.tar.gz to main/libf/libffado/libffado_2.0.99+svn2171.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 678...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Knoth a...@drcomp.erfurt.thur.de (supplier of updated libffado package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 24 Jun 2012 12:58:18 +0200 Source: libffado Binary: libffado-dev libffado2 ffado-tools ffado-dbus-server ffado-mixer-qt4 Architecture: source all amd64 Version: 2.0.99+svn2171-1 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Adrian Knoth a...@drcomp.erfurt.thur.de Description: ffado-dbus-server - FFADO D-Bus server ffado-mixer-qt4 - FFADO D-Bus mixer applets (QT4) ffado-tools - FFADO debugging and firmware tools libffado-dev - FFADO API - development files libffado2 - FFADO API Closes: 678347 Changes: libffado (2.0.99+svn2171-1) unstable; urgency=low . * Imported Upstream version 2.0.99+svn2171 (Closes: #678347 #620427) Checksums-Sha1: 598a8a86e7c94a9f602463b317e8bff6b1d951e2 2653 libffado_2.0.99+svn2171-1.dsc f669616fad11868aea961678bb2e27c63b22536a 1148515 libffado_2.0.99+svn2171.orig.tar.gz a465c60a4bfe461dd25f4582ffacc8a2783dc82d 7879 libffado_2.0.99+svn2171-1.debian.tar.gz 5fbec45efab3d7f5f9d4545df031d8ee15d13c35 112998 ffado-mixer-qt4_2.0.99+svn2171-1_all.deb 985d389db83c2393301cae6a9c50d75935220d75 19450 libffado-dev_2.0.99+svn2171-1_amd64.deb cdc3c419cf055b9458c61226e023b7182dc84186 1698128 libffado2_2.0.99+svn2171-1_amd64.deb fd2366ad640f073248b5e32eb9d24970e0dfa6bc 59776 ffado-tools_2.0.99+svn2171-1_amd64.deb c1ed31dbf8460968a12d12242f1d96a2ccd0c73b 71796 ffado-dbus-server_2.0.99+svn2171-1_amd64.deb Checksums-Sha256: 2a22529db76a9ec9a7728fffac586fc1fafe12de0e785a3d49ccb9c929db0aa4 2653 libffado_2.0.99+svn2171-1.dsc 56e9f860684298083b1cfef1e06e27555e8b7e52331c5c97c8f3992c1210a22e 1148515 libffado_2.0.99+svn2171.orig.tar.gz d7c007d53494704cdad91be110dbbd8dfd07f5aadb4b6366a253c9db0295ca28 7879 libffado_2.0.99+svn2171-1.debian.tar.gz f76b17cd59ffaede34235e9d8007866fb8d56bad489b8ce9fae9d0062e68414f 112998 ffado-mixer-qt4_2.0.99+svn2171-1_all.deb f94a157ad6f57611de1465198da5448d8f830a632a5678f06c55c9bcd92be3fc 19450 libffado-dev_2.0.99+svn2171-1_amd64.deb b5ebb7aecab16033a14e639815bd9eef22fc5e71e7e8fcffe965cfe19ebd7b8d 1698128 libffado2_2.0.99+svn2171-1_amd64.deb 39240b13db51e58b323c231c22f81c5a9ed2f60ccfc3d97696e65db9dd82b092 59776
Bug#678758: marked as done (sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date.)
Your message dated Sun, 24 Jun 2012 14:05:05 +0200
with message-id 4fe70271.1000...@thykier.net
and subject line Re: Bug#678758: sisu-ioc: FTBFS:
org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error
(java.lang.UnsupportedClassVersionError) and may be out-of-date.
has caused the Debian Bug report #678758,
regarding sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute()
caused a linkage error (java.lang.UnsupportedClassVersionError) and may be
out-of-date.
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.)
--
678758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: sisu-ioc
Version: 2.3.0-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
mh_patchpoms -plibsisu-ioc-java --debian-build --keep-pom-version
--maven-repo=/«PKGBUILDDIR»/debian/maven-repo --build-no-docs
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian-nodocs.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Sisu
[INFO] Sisu-Inject
[INFO] Sisu-Inject : Containers
[INFO] Sisu-Inject : Containers : Bean (JSR330)
[INFO] Sisu-Inject-Bean : Generic reflection
[INFO] Sisu-Inject-Bean : Property injection
[INFO] Sisu-Inject-Bean : @Named scanning
[INFO] Sisu-Inject-Bean : Type conversion
[INFO] Sisu-Inject-Bean : Dynamic bindings
[INFO] Sisu-Inject-Bean : @Inject auto-wiring
[INFO] Sisu-Inject-Bean : Container API
[INFO] Sisu-Inject-Bean : Aggregate OSGi bundle
[INFO] Sisu-Inject : Containers : Plexus
[INFO] Sisu-Inject-Plexus : @Component metadata
[INFO] Sisu-Inject-Plexus : @Component scanning
[INFO] Sisu-Inject-Plexus : @Configuration conversion
[INFO] Sisu-Inject-Plexus : Dynamic bindings
[INFO] Sisu-Inject-Plexus : @Requirement auto-wiring
[INFO] Sisu-Inject-Plexus : @Component lifecycles
[INFO] Sisu-Inject-Plexus : Container API
[INFO] Sisu-Inject-Plexus : Aggregate OSGi bundle
[INFO] Sisu-Inject : Registries
[INFO] Sisu-OSGi-Registry : Service bindings
[INFO] Sisu-SPI-Registry : Service bindings
[INFO]
[INFO] Building Sisu
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/sisu-parent/2.3.0/sisu-parent-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/sisu-inject/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/sisu-inject/2.3.0/sisu-inject-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject : Containers
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/sisu-inject/containers/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/inject/containers/2.3.0/containers-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject : Containers : Bean
Bug#678758: marked as done (sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date.)
Your message dated Sun, 24 Jun 2012 12:05:27 +
with message-id e1silzh-xu...@franck.debian.org
and subject line Bug#678758: fixed in osgi-core 4.3.0-3
has caused the Debian Bug report #678758,
regarding sisu-ioc: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute()
caused a linkage error (java.lang.UnsupportedClassVersionError) and may be
out-of-date.
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.)
--
678758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: sisu-ioc
Version: 2.3.0-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
mh_patchpoms -plibsisu-ioc-java --debian-build --keep-pom-version
--maven-repo=/«PKGBUILDDIR»/debian/maven-repo --build-no-docs
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian-nodocs.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Sisu
[INFO] Sisu-Inject
[INFO] Sisu-Inject : Containers
[INFO] Sisu-Inject : Containers : Bean (JSR330)
[INFO] Sisu-Inject-Bean : Generic reflection
[INFO] Sisu-Inject-Bean : Property injection
[INFO] Sisu-Inject-Bean : @Named scanning
[INFO] Sisu-Inject-Bean : Type conversion
[INFO] Sisu-Inject-Bean : Dynamic bindings
[INFO] Sisu-Inject-Bean : @Inject auto-wiring
[INFO] Sisu-Inject-Bean : Container API
[INFO] Sisu-Inject-Bean : Aggregate OSGi bundle
[INFO] Sisu-Inject : Containers : Plexus
[INFO] Sisu-Inject-Plexus : @Component metadata
[INFO] Sisu-Inject-Plexus : @Component scanning
[INFO] Sisu-Inject-Plexus : @Configuration conversion
[INFO] Sisu-Inject-Plexus : Dynamic bindings
[INFO] Sisu-Inject-Plexus : @Requirement auto-wiring
[INFO] Sisu-Inject-Plexus : @Component lifecycles
[INFO] Sisu-Inject-Plexus : Container API
[INFO] Sisu-Inject-Plexus : Aggregate OSGi bundle
[INFO] Sisu-Inject : Registries
[INFO] Sisu-OSGi-Registry : Service bindings
[INFO] Sisu-SPI-Registry : Service bindings
[INFO]
[INFO] Building Sisu
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/sisu-parent/2.3.0/sisu-parent-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/sisu-inject/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/sisu-inject/2.3.0/sisu-inject-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject : Containers
[INFO]task-segment: [install]
[INFO]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«PKGBUILDDIR»/sisu-inject/containers/pom.xml to
/«PKGBUILDDIR»/debian/maven-repo/org/sonatype/sisu/inject/containers/2.3.0/containers-2.3.0.pom
[INFO]
[INFO] Building Sisu-Inject : Containers : Bean (JSR330)
[INFO]task-segment: [install]
[INFO
Bug#678791: libsvn-notify-mirror-perl: FTBFS: tests failed
tags 678791 + confirmed
thanks
Hi
On Sun, Jun 24, 2012 at 11:30:01AM +0200, Lucas Nussbaum wrote:
Source: libsvn-notify-mirror-perl
Version: 0.03800-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
dh_testdir
# redirect STDIN to avoid any prompting
/usr/bin/perl Build.PL installdirs=vendor /dev/null
Checking optional features...
config_supportdisabled
requires:
! SVN::Notify::Config is not installed
rsync_support.disabled
requires:
! File::Rsync is not installed
ssh_support...disabled
requires:
! Net::SSH is not installed
ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the
versions
of the modules indicated above before proceeding with this installation
Run 'Build installdeps' to install missing prerequisites.
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'SVN-Notify-Mirror' version '0.038'
/usr/bin/perl Build
Building SVN-Notify-Mirror
SENDMAIL=/dev/null /usr/bin/perl Build test
# Failed test 'Correct files updated in project1/trunk at rev: 2'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/dir1} = Does not exist
# $expected-{project1/tags/TRUNK-1135534439/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/'.':} = 'Updating'
# $expected-{project1/tags/TRUNK-1135534439/'.':} = Does not exist
# Failed test 'Correct files updated in project1/branches/branch1 at rev:
4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/branches/branch1/dir1} = Does not exist
# $expected-{project1/branches/branch1/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/branches/branch1 at rev:
5'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/branches/branch1/'.':} = 'Updating'
# $expected-{project1/branches/branch1/'.':} = Does not exist
# Failed test 'Correct files updated in project1/trunk at rev: 6'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/trunk at rev: 2'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/dir1} = Does not exist
# $expected-{project1/tags/TRUNK-1135534439/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 3'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/trunk/'.':} = 'Updating'
# $expected-{project1/trunk/'.':} = Does not exist
# Failed test 'Correct files updated in project1/tags/TRUNK-1135534439 at
rev: 4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/tags/TRUNK-1135534439/'.':} = 'Updating'
# $expected-{project1/tags/TRUNK-1135534439/'.':} = Does not exist
# Failed test 'Correct files updated in project1/branches/branch1 at rev:
4'
# at t/coretests.pm line 196.
# Structures begin differing at:
# $got-{project1/branches/branch1/dir1} = Does not exist
# $expected-{project1/branches/branch1/dir1} = 'A'
# Failed test 'Correct files updated in project1/trunk at rev: 4'
# at t/coretests.pm line 196.
# Structures begin
Processed: Re: Bug#678791: libsvn-notify-mirror-perl: FTBFS: tests failed
Processing commands for cont...@bugs.debian.org: tags 678791 + confirmed Bug #678791 [src:libsvn-notify-mirror-perl] libsvn-notify-mirror-perl: FTBFS: tests failed Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 678791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678791 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#678750: marked as done (argyll: FTBFS: ld: cannot find -lconv)
Your message dated Sun, 24 Jun 2012 14:15:27 +0200 with message-id 87d34ohpnk@christian.marillat.net and subject line Re: Bug#678750: argyll: FTBFS: ld: cannot find -lconv has caused the Debian Bug report #678750, regarding argyll: FTBFS: ld: cannot find -lconv 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.) -- 678750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: argyll Version: 1.4.0-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -DUNIX -I../cgats -I../gamut -I../h -I../jcnf -I../libusb1/libusb -I../numlib -I../plot -I../profile -I../render -I../rspl -I../spectro -I../target -I../ucmm -I../xicc -I../icc -I../jcnf/yajl -L../spectro -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c ctest.c In file included from imdi.h:20:0, from ctest.c:15: imdi_utl.h:36:9: note: #pragma message: Using 64 bit integer color kernel /bin/bash ../libtool --tag=CC --mode=link gcc -D_GNU_SOURCE -DUNIX -I../cgats -I../gamut -I../h -I../jcnf -I../libusb1/libusb -I../numlib -I../plot -I../profile -I../render -I../rspl -I../spectro -I../target -I../ucmm -I../xicc -I../icc -I../jcnf/yajl -L../spectro -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -o ctest ctest.o cgen.o -lrt -lpthread -lm libtool: link: gcc -D_GNU_SOURCE -DUNIX -I../cgats -I../gamut -I../h -I../jcnf -I../libusb1/libusb -I../numlib -I../plot -I../profile -I../render -I../rspl -I../spectro -I../target -I../ucmm -I../xicc -I../icc -I../jcnf/yajl -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,--as-needed -Wl,--no-undefined -o ctest ctest.o cgen.o -L../spectro -lrt -lpthread -lm make[4]: Leaving directory `/«PKGBUILDDIR»/imdi' fakeroot debian/rules binary make[3]: Leaving directory `/«PKGBUILDDIR»/imdi' make[2]: Leaving directory `/«PKGBUILDDIR»/imdi' make[1]: Leaving directory `/«PKGBUILDDIR»' dh binary --with quilt dh_testroot dh_prep dh_installdirs debian/rules override_dh_auto_install make[1]: Entering directory `/«PKGBUILDDIR»' chmod +x firmware-package-builder/argyll-firmware-spyder2/debian/rules tar cfCz firmware-package-builder/spyder2.tar.gz firmware-package-builder argyll-firmware-spyder2 /usr/bin/make install -i DESTDIR=/«PKGBUILDDIR»/debian/tmp make[2]: Entering directory `/«PKGBUILDDIR»' Making install in h make[3]: Entering directory `/«PKGBUILDDIR»/h' make[4]: Entering directory `/«PKGBUILDDIR»/h' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/«PKGBUILDDIR»/h' make[3]: Leaving directory `/«PKGBUILDDIR»/h' Making install in doc make[3]: Entering directory `/«PKGBUILDDIR»/doc' make[4]: Entering directory `/«PKGBUILDDIR»/doc' make[4]: Nothing to be done for `install-exec-am'. /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/share/doc/argyll' /usr/bin/install -c -m 644 DocLicense.txt License.txt License2.txt License3.txt SG_footer.txt SG_header.txt ArgyllDoc.html ChangesSummary.html ColorManagement.html Compiling.html CrushedDisplyBlacks.html Environment.html FWA.html File_Formats.html Installing.html Installing_Linux.html Installing_MSWindows.html Installing_OSX.html Limitations.html MinorTools.html Organisation.html Overview.html Performance.html Scenarios.html Source.html WideGamutColmters.html applycal.html average.html cal_format.html calvschar.html cb2ti3.html ccmxs.html cctiff.html ccxxmake.html chartread.html cht_format.html collink.html colprof.html dispcal.html dispprofloc.html '/«PKGBUILDDIR»/debian/tmp/usr/share/doc/argyll' /usr/bin/install -c -m 644 dispread.html dispwin.html evalInputTargets.html extracticc.html extractttag.html fakeCMY.html fakeread.html filmread.html filmtarg.html gamma.html greytiff.html i1d3ccss.html i1proDriver.html iccdump.html iccgamut.html iccgamutmapping.html icclu.html illumread.html instruments.html invprofcheck.html kodak2ti3.html monitorcontrols.html mppcheck.html mpplu.html mppprof.html printcal.html printtarg.html profcheck.html refine.html revfix.html scanin.html sepgen.html
Processed: tagging 678780
Processing commands for cont...@bugs.debian.org: tags 678780 + confirmed Bug #678780 [src:unburden-home-dir] unburden-home-dir: FTBFS: tests failed Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 678780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678780 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#678807: ttf-root-installer: post installation fails
Package: ttf-root-installer Version: 5.34.00~rc1-1 Severity: serious Justification: can't upgrade package Hi, Upgrade of ttf-root-installer fails: Setting up ttf-root-installer (5.34.00~rc1-1) ... dpkg: error processing ttf-root-installer (--configure): subprocess installed post-installation script returned error exit status 4 When I add set -x into /var/lib/dpkg/info/ttf-root-installer.postinst, it is visible that the last command the script tries to download something with wget: + test -z + wget --continue --tries=1 --dns-timeout=10 --connect-timeout=5 --read-timeout=300 -q --directory-prefix . -c ftp://root.cern.ch/root/ttf/ttf_fonts.tar.gz dpkg: error processing ttf-root-installer (--configure): subprocess installed post-installation script returned error exit status 4 but it fails to do any error-handling in case of any downloads issues. There is a simillar bug report in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/root-system/+bug/349860 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 ttf-root-installer depends on: ii debconf 1.5.44 ii wget 1.13.4-3 ii xfonts-utils 1:7.7~1 ttf-root-installer recommends no packages. ttf-root-installer suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678746: desktop-base: Joy theme is a mix of incompatibly-licensed works
On Sun, 24 Jun 2012 07:34:50 -0400 Paul Tagliamonte wrote: On Sun, Jun 24, 2012 at 11:13:31AM +0200, Francesco Poli (wintermute) wrote: [...] First of all, these debian/copyright paragraphs fail to acknowledge that the Joy theme is based on the Debian “Open Use” (without “Debian” word) logo. But this may be fixed easily. ACK'd. I'll fix this tonight. Thank you! You're welcome! The major issue seems to be that the Joy plymouth theme mixes parts released under CC-by-sa-v3.0 and parts released under GPLv2+. Since CC-by-sa-v3.0 is incompatible with GPLv2+, I would say that the resulting work is legally undistributable. This *might* be true if it was two bits of code that get linked together, but since Plymouth (and the plugin, which is GPLv2) only render the CC-BY-SA 3.0 work, it should be fine. Well, if what you mean is that a GPL-licensed program loads a CC-licensed image (as input data) and renders it on the screen, then it seems that the license incompatibility is irrelevant. Sorry for the misunderstanding, but the debian/copyright file is not very clear on this. Hence, please, at least, clarify the debian/copyright file. I'll CC debian-leagl for comment OK, I am keeping debian-legal copied. [...] In this case, I'll modify this line to show the files that I edited are still GPLv2, and the images it's self is CC-BY-SA 3.0. No problem, no big deal. Yes, please: as I said above, a clarification is needed. [...] Since everything else in the desktop-base package is GPL-compatible, I strongly recommend to persuade Adrien Aubourg and Paul Tagliamonte I'm fine with whatever license comes up. I just wanted to keep consistancy. to re-license their work under the terms of the GNU GPL v2 or later. Or, at least, to dual-license it under CC-by-sa-v3.0 and GPLv2+. (In the latter case, the complete text of CC-by-sa-v3.0 should be included in the debian/copyright file, though.) My recommendation is very much related to consistency. Since rest of the package is all GPL-compatible, it would be really great if this new theme were GPL-compatible as well. Hence, I *still* recommend you to persuade Adrien Aubourg to re-license (or dual-license) under GPLv2+ ! I really hope this may be achieved. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpC18hWPhlWJ.pgp Description: PGP signature
Bug#678767: librpc-xml-perl: FTBFS: tests failed
tags 678767 + confirmed thanks Hi On Sun, Jun 24, 2012 at 11:29:56AM +0200, Lucas Nussbaum wrote: Source: librpc-xml-perl Version: 0.76-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 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»' /usr/bin/perl etc/make_method --base=lib/Apache/RPC/status /usr/bin/perl etc/make_method --base=methods/identity /usr/bin/perl etc/make_method --base=methods/introspection /usr/bin/perl etc/make_method --base=methods/listMethods /usr/bin/perl etc/make_method --base=methods/methodHelp /usr/bin/perl etc/make_method --base=methods/methodSignature /usr/bin/perl etc/make_method --base=methods/multicall /usr/bin/perl etc/make_method --base=methods/status cp methods/status.xpl blib/lib/RPC/XML/status.xpl cp lib/Apache/RPC/Status.pm blib/lib/Apache/RPC/Status.pm cp methods/methodHelp.xpl blib/lib/RPC/XML/methodHelp.xpl cp lib/RPC/XML/Procedure.pm blib/lib/RPC/XML/Procedure.pm cp methods/introspection.xpl blib/lib/RPC/XML/introspection.xpl cp lib/RPC/XML/Parser/XMLLibXML.pm blib/lib/RPC/XML/Parser/XMLLibXML.pm cp lib/RPC/XML/Parser.pm blib/lib/RPC/XML/Parser.pm cp methods/identity.xpl blib/lib/RPC/XML/identity.xpl cp lib/RPC/XML/Server.pm blib/lib/RPC/XML/Server.pm cp lib/Apache/RPC/Server.pm blib/lib/Apache/RPC/Server.pm cp methods/multicall.xpl blib/lib/RPC/XML/multicall.xpl cp lib/Apache/RPC/status.xpl blib/lib/Apache/RPC/status.xpl cp lib/RPC/XML.pm blib/lib/RPC/XML.pm cp methods/listMethods.xpl blib/lib/RPC/XML/listMethods.xpl cp lib/RPC/XML/Client.pm blib/lib/RPC/XML/Client.pm cp methods/methodSignature.xpl blib/lib/RPC/XML/methodSignature.xpl cp lib/RPC/XML/ParserFactory.pm blib/lib/RPC/XML/ParserFactory.pm cp lib/RPC/XML/Parser/XMLParser.pm blib/lib/RPC/XML/Parser/XMLParser.pm cp etc/make_method blib/script/make_method /usr/bin/perl -MExtUtils::MY -e 'MY-fixin(shift)' -- blib/script/make_method PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00_load.t . ok t/10_data.t . ok t/11_base64_fh.t ok t/12_nil.t .. ok t/13_no_deep_recursion.t ok t/14_datetime_iso8601.t . ok t/15_serialize.t ok t/20_xml_parser.t ... ok t/21_xml_libxml.t ... ok t/25_parser_negative.t .. ok t/29_parserfactory.t ok t/30_method.t ... ok t/35_namespaces.t ... ok t/40_server.t ... ok t/40_server_xmllibxml.t . ok t/41_server_hang.t .. ok t/50_client.t ... ok t/51_client_with_host_header.t .. ok # Failed test 'system.identity matches $srv-product_tokens' # at t/60_net_server.t line 60. # got: undef # expected: 'RPC::XML::Server/1.68' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 68. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 80. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned ARRAY ref' # at t/60_net_server.t line 90. # got: '' # expected: 'ARRAY' # Failed test 'system.listMethods returned HASH ref' # at t/60_net_server.t line 100. # got: '' # expected: 'HASH' # Failed test 'system.methodHelp returned correct string' # at t/60_net_server.t line 110. # got: undef # expected: 'Return the server name and version as a string' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 116. # got: '' # expected: 'ARRAY' # Failed test 'system.methodHelp (bad arg) response isa RPC::XML::fault' # at t/60_net_server.t line 127. # system.methodHelp (bad arg) response isn't a 'RPC::XML::fault' it's a '' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 136. # got: '' # expected: 'ARRAY' # Failed test 'system.methodSignature (bad arg) response isa RPC::XML::fault' # at t/60_net_server.t line 146. # system.methodSignature (bad arg) response isn't a 'RPC::XML::fault' it's a '' # Failed test 'system.methodHelp returned ARRAY ref' # at t/60_net_server.t line 193. # got: '' # expected: 'ARRAY' # Looks like you planned 30 tests but ran 29. # Looks like you failed 11 tests of 29 run. t/60_net_server.t ... Dubious, test returned 11 (wstat 2816, 0xb00) Failed 12/30 subtests (less 16 skipped subtests: 2 okay) t/70_compression_detect.t ... ok
Processed: Re: Bug#678767: librpc-xml-perl: FTBFS: tests failed
Processing commands for cont...@bugs.debian.org: tags 678767 + confirmed Bug #678767 [src:librpc-xml-perl] librpc-xml-perl: FTBFS: tests failed Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 678767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678767 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#678757: marked as done (cantor: FTBFS: build-dependency not installable: kalgebra-dev)
Your message dated Sun, 24 Jun 2012 13:48:15 +0200 with message-id 201206241348.15552.s...@debian.org and subject line Re: Bug#678757: cantor: FTBFS: build-dependency not installable: kalgebra-dev has caused the Debian Bug report #678757, regarding cantor: FTBFS: build-dependency not installable: kalgebra-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 678757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cantor Version: 4:4.7.4-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install cantor build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-cantor-dummy : Depends: kalgebra-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/cantor_4.7.4-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Version: 4:4.8.4-1 The package should build now /Sune On Sunday 24 June 2012 11:33:23 Lucas Nussbaum wrote: Source: cantor Version: 4:4.7.4-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌ ──┐ │ Install cantor build dependencies (apt-based resolver) │ └─── ───┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-cantor-dummy : Depends: kalgebra-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/cantor_4.7.4-3_unstable.lo g A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Do you know how may I open the GPU? From Netscape you can never disable the FPU in order to save a firewall. ---End Message---
Bug#678785: marked as done (kalgebra: FTBFS: cp: cannot stat `debian/tmp/usr/lib/libanalitza.so.4.7.0': No such file or directory)
Your message dated Sun, 24 Jun 2012 13:47:42 +0200 with message-id 201206241347.42681.s...@debian.org and subject line Re: Bug#678785: kalgebra: FTBFS: cp: cannot stat `debian/tmp/usr/lib/libanalitza.so.4.7.0': No such file or directory has caused the Debian Bug report #678785, regarding kalgebra: FTBFS: cp: cannot stat `debian/tmp/usr/lib/libanalitza.so.4.7.0': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 678785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kalgebra Version: 4:4.7.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make[3]: Nothing to be done for `preinstall'. make[3]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: Debian -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/index.cache.bz2 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/commands.docbook -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/index.docbook -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/doc/kde/HTML/en/kalgebra/kalgebra-main-window.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitza.so.4.8.0 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitza.so.4 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitza.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/abstractlexer.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/analitzaexport.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/analyzer.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/analitzautils.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/expression.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/object.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/operations.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/operator.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/value.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/variables.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/expressiontype.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitza/builtinmethods.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/cmake/modules/FindAnalitza.cmake -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so.4.8.0 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so.4 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/libanalitzagui.so.4.8.0 -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/algebrahighlighter.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/analitzaguiexport.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/operatorsmodel.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/analitzagui/variablesmodel.h -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebra -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebra -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/applications/kde4/kalgebra.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/apps/katepart/syntax/kalgebra.xml -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/128x128/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/64x64/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/16x16/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/48x48/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/icons/hicolor/32x32/apps/./kalgebra.png -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/plasma_applet_kalgebra.so -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/plasma_applet_kalgebra.so -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/kde4/services/kalgebraplasmoid.desktop -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebramobile -- Removed runtime path from /«PKGBUILDDIR»/debian/tmp/usr/bin/kalgebramobile
Bug#678765: marked as done (activemq: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error (java.lang.UnsupportedClassVersionError) and may be out-of-date.)
Your message dated Sun, 24 Jun 2012 14:15:23 +0200
with message-id 4fe704db.3090...@thykier.net
and subject line Re: Bug#678765: activemq: FTBFS:
org.apache.felix.obrplugin.ObrInstall#execute() caused a linkage error
(java.lang.UnsupportedClassVersionError) and may be out-of-date.
has caused the Debian Bug report #678765,
regarding activemq: FTBFS: org.apache.felix.obrplugin.ObrInstall#execute()
caused a linkage error (java.lang.UnsupportedClassVersionError) and may be
out-of-date.
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.)
--
678765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: activemq
Version: 5.6.0+dfsg-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120624 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
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh
/«BUILDDIR»/activemq-5.6.0+dfsg/debian
mh_patchpoms -plibactivemq-java --debian-build --keep-pom-version
--maven-repo=/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo install
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] ActiveMQ
[INFO] ActiveMQ :: KahaDB
[INFO] ActiveMQ :: JAAS
[INFO] ActiveMQ :: jmdns 1.0
[INFO] ActiveMQ :: Core
[INFO] ActiveMQ :: Console
[INFO] ActiveMQ :: File Server
[INFO] ActiveMQ :: RA
[INFO] ActiveMQ :: Pool
[INFO] ActiveMQ :: Run Jar
[INFO] ActiveMQ :: Spring
[INFO]
[INFO] Building ActiveMQ
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [bundle:cleanVersions {execution: cleanVersions}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /«BUILDDIR»/activemq-5.6.0+dfsg/pom.xml to
/«BUILDDIR»/activemq-5.6.0+dfsg/debian/maven-repo/org/apache/activemq/activemq-parent/5.6.0/activemq-parent-5.6.0.pom
[INFO]
[INFO] Building ActiveMQ :: KahaDB
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [bundle:cleanVersions {execution: cleanVersions}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 50 source files to
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/target/classes
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[58,48]
unmappable character for encoding ASCII
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[58,49]
unmappable character for encoding ASCII
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[67,52]
unmappable character for encoding ASCII
[WARNING]
/«BUILDDIR»/activemq-5.6.0+dfsg/kahadb/src/main/java/org/apache/kahadb/index/BTreeIndex.java:[67,53]
unmappable character for encoding ASCII
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Not compiling test sources
Bug#677487: marked as done (Multiple security issues)
Your message dated Sun, 24 Jun 2012 13:04:57 +
with message-id e1simur-0005ie...@franck.debian.org
and subject line Bug#677487: fixed in openjdk-6 6b24-1.11.3-1
has caused the Debian Bug report #677487,
regarding Multiple security issues
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.)
--
677487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: openjdk-6
Version: Multiple security issues
Severity: grave
Tags: security
Multiple security issues have been fixed in the latest Java update round:
http://www.oracle.com/technetwork/topics/security/javacpujun2012-1515912.html#PatchTable
Cheers,
Moritz
---End Message---
---BeginMessage---
Source: openjdk-6
Source-Version: 6b24-1.11.3-1
We believe that the bug you reported is fixed in the latest version of
openjdk-6, which is due to be installed in the Debian FTP archive:
icedtea-6-jre-cacao_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/icedtea-6-jre-cacao_6b24-1.11.3-1_amd64.deb
icedtea-6-jre-jamvm_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/icedtea-6-jre-jamvm_6b24-1.11.3-1_amd64.deb
openjdk-6-dbg_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/openjdk-6-dbg_6b24-1.11.3-1_amd64.deb
openjdk-6-demo_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/openjdk-6-demo_6b24-1.11.3-1_amd64.deb
openjdk-6-doc_6b24-1.11.3-1_all.deb
to main/o/openjdk-6/openjdk-6-doc_6b24-1.11.3-1_all.deb
openjdk-6-jdk_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/openjdk-6-jdk_6b24-1.11.3-1_amd64.deb
openjdk-6-jre-headless_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/openjdk-6-jre-headless_6b24-1.11.3-1_amd64.deb
openjdk-6-jre-lib_6b24-1.11.3-1_all.deb
to main/o/openjdk-6/openjdk-6-jre-lib_6b24-1.11.3-1_all.deb
openjdk-6-jre-zero_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/openjdk-6-jre-zero_6b24-1.11.3-1_amd64.deb
openjdk-6-jre_6b24-1.11.3-1_amd64.deb
to main/o/openjdk-6/openjdk-6-jre_6b24-1.11.3-1_amd64.deb
openjdk-6-source_6b24-1.11.3-1_all.deb
to main/o/openjdk-6/openjdk-6-source_6b24-1.11.3-1_all.deb
openjdk-6_6b24-1.11.3-1.diff.gz
to main/o/openjdk-6/openjdk-6_6b24-1.11.3-1.diff.gz
openjdk-6_6b24-1.11.3-1.dsc
to main/o/openjdk-6/openjdk-6_6b24-1.11.3-1.dsc
openjdk-6_6b24-1.11.3.orig.tar.gz
to main/o/openjdk-6/openjdk-6_6b24-1.11.3.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 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@ubuntu.com (supplier of updated openjdk-6 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, 23 Jun 2012 14:59:42 +0200
Source: openjdk-6
Binary: openjdk-6-jdk openjdk-6-jre-headless openjdk-6-jre openjdk-6-jre-lib
openjdk-6-demo openjdk-6-source openjdk-6-doc openjdk-6-dbg icedtea-6-jre-cacao
icedtea-6-jre-jamvm openjdk-6-jre-zero
Architecture: source amd64 all
Version: 6b24-1.11.3-1
Distribution: unstable
Urgency: low
Maintainer: OpenJDK Team open...@lists.launchpad.net
Changed-By: Matthias Klose d...@ubuntu.com
Description:
icedtea-6-jre-cacao - Alternative JVM for OpenJDK, using Cacao
icedtea-6-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
openjdk-6-dbg - Java runtime based on OpenJDK (debugging symbols)
openjdk-6-demo - Java runtime based on OpenJDK (demos and examples)
openjdk-6-doc - OpenJDK Development Kit (JDK) documentation
openjdk-6-jdk - OpenJDK Development Kit (JDK)
openjdk-6-jre - OpenJDK Java runtime, using ${vm:Name}
openjdk-6-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
openjdk-6-jre-lib - OpenJDK Java runtime (architecture independent libraries)
openjdk-6-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
openjdk-6-source - OpenJDK Development Kit (JDK) source files
Closes: 677487
Changes:
openjdk-6 (6b24-1.11.3-1) unstable; urgency=low
.
* IcedTea 1.11.3 release.
* Security fixes. Closes: #677487.
- S7079902, CVE-2012-1711: Refine CORBA data models.
- S7110720: Issue with vm config file loadingIssue with vm config file
loading.
- S7143606, CVE-2012-1717: File.createTempFile should be improved for
temporary files created by the platform.
- S7143614, CVE-2012-1716: SynthLookAndFeel
Bug#676717: dh_installcatalogs transition and w3c-dtd-xhtml removal bugs
Hi, On Sun, Jun 24, 2012 at 12:46:20PM +0200, Helmut Grohne wrote: As laid out above and as can be seen by searching update-catalog for '$quiet' the --quiet switch never suppresses messages for failures that result in a non-zero exit. So your proposed solution just prints the error twice (assuming idempotency) plus some additional messages. Thanks. I see I was raising non-issue. --quiet seems good to me. Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678791: libsvn-notify-mirror-perl: FTBFS: tests failed
Only downgrading libsvn1 and subversion to 1.6.17dfsg-4 let's the tests succeed again. Regards, Salvatore signature.asc Description: Digital signature
Processed: bug 678791 is forwarded to http://rt.cpan.org/Public/Bug/Display.html?id=77990
Processing commands for cont...@bugs.debian.org: forwarded 678791 http://rt.cpan.org/Public/Bug/Display.html?id=77990 Bug #678791 [src:libsvn-notify-mirror-perl] libsvn-notify-mirror-perl: FTBFS: tests failed Set Bug forwarded-to-address to 'http://rt.cpan.org/Public/Bug/Display.html?id=77990'. thanks Stopping processing here. Please contact me if you need assistance. -- 678791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678791 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#678780: unburden-home-dir: FTBFS: tests failed
Hi, Lucas Nussbaum wrote: Source: unburden-home-dir Version: 0.3 [...] During a rebuild of all packages in sid, your package failed to build on amd64. [...] prove t/*.t # Failed test 'Check command STDERR output' Thanks for the report. Cause is a missing build-dependency on lsof which causes unburden-home-dir to issue a warning on STDERR that lsof is not found and some feature are hence not used -- which is not expected to happen in the test suite. Adding a build-dependency on lsof though would cause the package to be unbuildable on kfreebsd-any due to http://bugs.debian.org/589103 while still being usable on kfreebsd-any, just not all features -- lsof is just a Recommends in the binary package So one solution would be to add a B-D on lsof [!kfreebsd-any] and disable the test suite on kfreebsd-any until lsof is available on kfreebsd again. Another solution would be to change to test suite to work only without lsof being installed or to make the test suite detect if lsof is installed or not and behave differently depending on the availability of lsof. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678789: [Openstack-devel] Bug#678789: glance: FTBFS: E271 multiple spaces after keyword
On Sun Jun 24 2012 05:28:38 PM CST, Lucas Nussbaum lu...@lucas-nussbaum.net wrote: Source: glance Version: 2012.1-3.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Hi, FYI, this was fixed in version 2012.1-4. I will tag accordingly. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676874: Bug#676970: ghc fails to configure after install (update-alternatives priority out of range)
On 2012-06-15 11:13, Andreas Beckmann wrote: Once one of these bugs is fixed in sid I'll reschedule a full piuparts check of sid to look for more impact of this bug, so please drop me a notice how the new warning looks like. After I rechecked sid/amd64 with piuparts and dpkg 1.16.4.* I didn't find any further occurrence of this error/warning. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677700: [pkg-bacula-devel] Bug#677700: bacula-director-mysql: fails to upgrade from testing - Table 'bacula.Version' doesn't exist
affects 677057 + bacula usertags 677700 + debian-packaging thanks Hi Andreas! IMHO bacula-director-mysql_5.2.6+dfsg-1 is not broken at all, but leaving Severity: to serious and Cc:ing debian-release@ for an advice. On Sat, 16 Jun 2012 11:49:34 +0200, Andreas Beckmann wrote: during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails. Actually, I was not able to install bacula-director-mysql_5.0.3-1+b1 on a clean wheezy (CD-1_20120618-04:55; d-i_20120508) with the default mysql-server, i.e. 5.5: = root@debian:~# apt-get update [...] root@debian:~# apt-cache policy bacula-director-mysql bacula-director-mysql: Installed: (none) Candidate: 5.0.3-1+b1 Version table: 5.0.3-1+b1 0 500 http://cdn.debian.net/debian/ wheezy/main amd64 Packages root@debian:~# apt-get install bacula-director-mysql [...] The following NEW packages will be installed: bacula-common bacula-common-mysql bacula-director-common bacula-director-mysql dbconfig-common libaio1 libdbd-mysql-perl libdbi-perl libhtml-template-perl libmysqlclient16 libmysqlclient18 libnet-daemon-perl libplrpc-perl libpython2.7 mysql-client mysql-client-5.5 mysql-common mysql-server mysql-server-5.5 mysql-server-core-5.5 [...] Setting up mysql-client-5.5 (5.5.24+dfsg-3) ... Setting up mysql-client (5.5.24+dfsg-3) ... Setting up bacula-director-mysql (5.0.3-1+b1) ... dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2). unable to connect to mysql server. error encountered creating user: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) = This is caused by the fact that there is no MySQL server running yet. While this could be solved via a Pre-Depends: in bacula-director-mysql, this is actually not possible because the MySQL server could be on a remote location. BTW, this happens to bacula-director-pgsql, too. The story is not finished, given that even installing the MySQL server *beforehand* does not result in a correct installation of bacula-director-mysql: = root@debian:~# dpkg-query -W \*mysql\* libdbd-mysql-perl 4.021-1+b1 libmysqlclient-dev libmysqlclient18:amd64 5.5.24+dfsg-3 mysql-client mysql-client-5.0 mysql-client-5.1 mysql-client-5.55.5.24+dfsg-3 mysql-common5.5.24+dfsg-3 mysql-server5.5.24+dfsg-3 mysql-server-5.0 mysql-server-5.1 mysql-server-5.55.5.24+dfsg-3 mysql-server-core mysql-server-core-5.0 mysql-server-core-5.1 mysql-server-core-5.5 5.5.24+dfsg-3 rsyslog-mysql virtual-mysql-client virtual-mysql-server root@debian:~# apt-get update [...] root@debian:~# apt-get install bacula-director-mysql [...] The following NEW packages will be installed: bacula-common bacula-common-mysql bacula-director-common bacula-director-mysql dbconfig-common libmysqlclient16 libpython2.7 [...] Setting up libmysqlclient16 (5.1.62-1) ... Setting up bacula-common-mysql (5.0.3-1+b1) ... Setting up bacula-director-common (5.0.3-1+b1) ... Setting up dbconfig-common (1.8.47+nmu1) ... Creating config file /etc/dbconfig-common/config with new version Setting up bacula-director-mysql (5.0.3-1+b1) ... Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version granting access to database bacula for bacula@localhost: success. verifying access for bacula@localhost: success. creating database bacula: success. verifying database bacula exists: success. populating database via sql... error encountered populating database: mysql said: ERROR 1064 (42000) at line 316: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MaxValue INTEGER DEFAULT 0, CurrentValue INTEGER DEFAULT 0, WrapCounter TI' at line 4 dbconfig-common: bacula-director-mysql configure: ignoring errors from here forwards done. dbconfig-common: flushing administrative password dbconfig-common: bacula-director-mysql configure: ignoring errors from here forwards dbconfig-common: bacula-director-mysql configure: ignoring errors from here forwards Processing configuration...Ok. [.ok.] Starting Bacula Director...:. = I could not test the above with mysql-server-5.1, since it is actually not installable as you have already reported: http://bugs.debian.org/677057 I do not know how to solve this bug, given that IMHO it is not a bug at all: 5.0.3-1+b1 is no more installable on wheezy and 5.2.6+dfsg-1 solves this (the latter installs fine with mysql-server-5.5_5.5.24+dfsg-3). From the attached log (scroll to the bottom...): Setting up bacula-director-mysql (5.2.6+dfsg-1) ... Installing
Bug#678644: Outdated version of Zoph in Debian
On 24-06-12 02:59, Laszlo Boszormenyi (GCS) wrote: I'm asking for advice. To be honest, #556573 [1] needs some luck to be fixed for Wheezy. There's an usability bug, as one dependency of Zoph is not even packaged. As I see, the NEW queue is long, even if I package that, may not reach testing and then stable. Without that, the very first step, importing photos won't work. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556573 As of version 0.8.2 Zoph no longer uses Perl and therefore the dependency on Perl modules is no longer an issue. Jeroen -- Zoph Organizes PHotos http://www.zoph.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: [pkg-bacula-devel] Bug#677700: bacula-director-mysql: fails to upgrade from testing - Table 'bacula.Version' doesn't exist
Processing commands for cont...@bugs.debian.org: affects 677057 + bacula Bug #677057 [mysql-client-5.1] mysql-client-5.1: uninstallable because mysql-common Breaks: mysql-client-5.1 ( 5.5) Added indication that 677057 affects bacula usertags 677700 + debian-packaging Bug#677700: bacula-director-mysql: fails to upgrade from testing - Table 'bacula.Version' doesn't exist User is l...@pca.it There were no usertags set. Usertags are now: debian-packaging. thanks Stopping processing here. Please contact me if you need assistance. -- 677057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677057 677700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677700 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#677261: vsftpd: FTBFS[kfreebsd-amd64 mips{,el}]
reopen 677261 thanks Hello, The problem aren't the hardening flags, but the flags set in Makefile. 3.0.0-2 still fails to build on amd64 and other systems (in fact it worked before on amd64 because +all and thus +pie was used). This issue should be reported to upstream. The attached patches should fix the build failure by removing the hardcoded flags in Makefile and applying all flags which are supported on the system (+all automatically disables +pie on freebsd and other systems). Btw. some patches apply with offsets and should be refreshed. Regards, Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 Description: Don't set the hardening flags manually. Instead take them from dpkg-buildflags which automatically disables unsupported flags on the current architecture. . Prevents build failure on e.g. kfreebsd. Author: Simon Ruderich si...@ruderich.org Last-Update: 2012-06-24 --- vsftpd-3.0.0.orig/Makefile +++ vsftpd-3.0.0/Makefile @@ -3,14 +3,13 @@ CC = gcc INSTALL = install IFLAGS = -idirafter dummyinc #CFLAGS = -g -CFLAGS = -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 \ +CFLAGS += -O2 \ -Wall -W -Wshadow -Werror -Wformat-security \ -D_FORTIFY_SOURCE=2 \ #-pedantic -Wconversion LIBS = `./vsf_findlibs.sh` LINK = -Wl,-s -LDFLAGS = -fPIE -pie -Wl,-z,relro -Wl,-z,now OBJS = main.o utility.o prelogin.o ftpcmdio.o postlogin.o privsock.o \ tunables.o ftpdataio.o secbuf.o ls.o \ diff -Nru vsftpd-3.0.0/debian/rules vsftpd-3.0.0/debian/rules --- vsftpd-3.0.0/debian/rules 2012-06-12 18:32:34.0 +0200 +++ vsftpd-3.0.0/debian/rules 2012-06-24 15:56:27.0 +0200 @@ -1,6 +1,6 @@ #!/usr/bin/make -f -export DEB_BUILD_MAINT_OPTIONS = hardening=-all +export DEB_BUILD_MAINT_OPTIONS = hardening=+all DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) signature.asc Description: Digital signature
Processed: vsftpd: FTBFS[kfreebsd-amd64 mips{,el}]
Processing commands for cont...@bugs.debian.org:
reopen 677261
Bug #677261 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[src:vsftpd] vsftpd: FTBFS[kfreebsd-amd64 mips{,el}]: relocation R_X86_64_32
against `.rodata.str1.1' can not be used when making a shared object; recompile
with -fPIC
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions vsftpd/3.0.0-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
677261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677261
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#678523: evolution: Evolution crashes without network-manager
Greetings, On 23/06/12 11:58, Nikolai Lusan wrote: Hi On 22/06/12 23:35, Mehdi Dogguy wrote: According to a tester, this error message doesn't seem the root of the problem. Could you please provide a backtrace leading to a crash? I have attached a file with the full gdb session for my backtrace. The problem is occurring on multiple amd64 systems and has only become evident in the last 2 days. Further to this I purged all my Evolution configurations and started from scratch. The problem seems limited to the calendar function. I am using a caldav server for my contacts and calendars. Hence I am closing this bug and opening one against evolution-data-server. -- Nikolai signature.asc Description: OpenPGP digital signature
Bug#678807: ttf-root-installer: post installation fails
Hi Robert, Thanks for report. The upstream web/ftp server is offline in last a few days due to security issues (the upstream claims that it's the first 1 days outage in 16 years). Although the web server is recovered today, the ftp port is still blocked, which causes the failure of postinst script. At the moment you can fix it by replacing ftp://root.cern.ch/root/ttf/; with http://root.cern.ch/download/ttf/; in the postinst script. I would add error-handling in version 5.34.00-2. Thanks, Lifeng On 14:36 Sun 06/24/12 Jun , Robert Luberda wrote: Package: ttf-root-installer Upgrade of ttf-root-installer fails: Setting up ttf-root-installer (5.34.00~rc1-1) ... dpkg: error processing ttf-root-installer (--configure): subprocess installed post-installation script returned error exit status 4 When I add set -x into /var/lib/dpkg/info/ttf-root-installer.postinst, it is visible that the last command the script tries to download something with wget: + test -z + wget --continue --tries=1 --dns-timeout=10 --connect-timeout=5 --read-timeout=300 -q --directory-prefix . -c ftp://root.cern.ch/root/ttf/ttf_fonts.tar.gz dpkg: error processing ttf-root-installer (--configure): subprocess installed post-installation script returned error exit status 4 but it fails to do any error-handling in case of any downloads issues. -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 678780, tagging 678630
Processing commands for cont...@bugs.debian.org: tags 678780 + pending Bug #678780 [src:unburden-home-dir] unburden-home-dir: FTBFS: tests failed Added tag(s) pending. tags 678630 + pending Bug #678630 [unburden-home-dir] unburden-home-dir: README.md is confusing Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 678630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678630 678780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678780 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#678523: marked as done (evolution: Evolution crashes without network-manager)
Your message dated Mon, 25 Jun 2012 00:10:34 +1000 with message-id 4fe71fda.80...@lusan.id.au and subject line Close #678523 has caused the Debian Bug report #678523, regarding evolution: Evolution crashes without network-manager 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.) -- 678523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: evolution Version: 3.4.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, Evolution currently crashes with: evolution-network-manager-WARNING **: network_manager_query_state: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Network-Manager is currently only a Suggested package, and this error would seem to suggest otherwise. IMHO it Network-Manager should not be required to run this software as there are a number of other ways in which a machine may have it's network configured. This issue also prevents users running non GNOME desktops from using Evolution. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.3.7-donetsk (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages evolution depends on: ii dbus 1.6.0-1 ii debconf [debconf-2.0]1.5.44 ii evolution-common 3.4.3-1 ii evolution-data-server3.4.3-1 ii gconf-service3.2.5-1 ii gconf2 3.2.5-1 ii gnome-icon-theme 3.4.0-2 ii libatk1.0-0 2.4.0-2 ii libc62.13-33 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcamel-1.2-33 3.4.3-1 ii libclutter-gtk-1.0-0 1.2.0-2 ii libdbus-glib-1-2 0.98-1 ii libebackend-1.2-23.4.3-1 ii libebook-1.2-13 3.4.3-1 ii libecal-1.2-11 3.4.3-1 ii libedataserver-1.2-163.4.3-1 ii libedataserverui-3.0-1 3.4.3-1 ii libenchant1c2a 1.6.0-7 ii libevolution 3.4.3-1 ii libgail-3-0 3.4.2-1 ii libgconf-2-4 3.2.5-1 ii libgdata13 0.12.0-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgtk-3-0 3.4.2-1 ii libgtkhtml-4.0-0 4.4.3-1 ii libgtkhtml-editor-4.0-0 4.4.3-1 ii libgweather-3-0 3.4.1-1 ii libical0 0.48-2 ii libmx-1.0-2 1.4.6-1 ii libnotify4 0.7.5-1 ii libnspr4 2:4.9.1-1 ii libnspr4-0d 2:4.9.1-1 ii libnss3 2:3.13.5-1 ii libnss3-1d 2:3.13.5-1 ii libpango1.0-01.30.0-1 ii libsoup2.4-1 2.38.1-2 ii libsqlite3-0 3.7.13-1 ii libxml2 2.8.0+dfsg1-4 ii psmisc 22.19-1 Versions of packages evolution recommends: pn bogofilter | spamassassin none ii evolution-plugins 3.4.3-1 pn evolution-webcal none ii yelp 3.4.2-1 Versions of packages evolution suggests: pn evolution-dbg none pn evolution-exchange none ii evolution-plugins-experimental 3.4.3-1 ii gnupg 1.4.12-4 pn network-manager none -- debconf information excluded ---End Message--- ---BeginMessage--- Close #678523 Problem is with the data-server -- Nikolai signature.asc Description: OpenPGP digital signature ---End Message---
Bug#676050: marked as done (ucto: FTBFS: build-dependency not installable: libfolia1-dev (= 0.9))
Your message dated Sun, 24 Jun 2012 16:19:34 +0200 with message-id 4fe721f6.9070...@gmx.at and subject line Built on all buildds has caused the Debian Bug report #676050, regarding ucto: FTBFS: build-dependency not installable: libfolia1-dev (= 0.9) 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.) -- 676050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ucto Version: 0.5.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install ucto build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-ucto-dummy : Depends: libfolia1-dev (= 0.9) but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/ucto_0.5.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Version: 0.5.2-2 ucto 0.5.2-2 built on all buildds and locally, so I'm closing this bug. Kind regards -- Sebastian Ramacher signature.asc Description: OpenPGP digital signature ---End Message---
Processed: bug 678767 is forwarded to http://rt.cpan.org/Public/Bug/Display.html?id=77992
Processing commands for cont...@bugs.debian.org: forwarded 678767 http://rt.cpan.org/Public/Bug/Display.html?id=77992 Bug #678767 [src:librpc-xml-perl] librpc-xml-perl: FTBFS: tests failed Set Bug forwarded-to-address to 'http://rt.cpan.org/Public/Bug/Display.html?id=77992'. thanks Stopping processing here. Please contact me if you need assistance. -- 678767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678767 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
