Bug#665067: live-manual: FTBFS: wc: live-manual.ssm.sst: No such file or directory
forcemerge 662227 665067 retitle 662227 FTBFS in non-UTF-8 locales (such as C) retitle 665067 FTBFS in non-UTF-8 locales (such as C) tag 662227 pending tag 665067 pending thanks On 03/30/2012 01:21 AM, Ralph Amissah wrote: I Hope I claimed this bug too quickly. thanks, however, like said earlier, this is just a dupe of #665067 which is not per se a bug in sisu Unless otherwise directed I will not obstruct the transition of sisu 3.2.0 to testing. to repeat what i've already said on irc, for the moment you don't need to care about live-manual, we need to weed out our own introduced bugs first ;) -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#665067: live-manual: FTBFS: wc: live-manual.ssm.sst: No such file or directory
Processing commands for cont...@bugs.debian.org: forcemerge 662227 665067 Bug #662227 [src:live-manual] src:live-manual: FTBFS in non-UTF-8 locales (such as C) Bug #665067 [src:live-manual] live-manual: FTBFS: wc: live-manual.ssm.sst: No such file or directory Added tag(s) patch. Bug #662227 [src:live-manual] src:live-manual: FTBFS in non-UTF-8 locales (such as C) Added tag(s) sid and wheezy. Merged 662227 665067 retitle 662227 FTBFS in non-UTF-8 locales (such as C) Bug #662227 [src:live-manual] src:live-manual: FTBFS in non-UTF-8 locales (such as C) Bug #665067 [src:live-manual] live-manual: FTBFS: wc: live-manual.ssm.sst: No such file or directory Changed Bug title to 'FTBFS in non-UTF-8 locales (such as C)' from 'src:live-manual: FTBFS in non-UTF-8 locales (such as C)' Changed Bug title to 'FTBFS in non-UTF-8 locales (such as C)' from 'live-manual: FTBFS: wc: live-manual.ssm.sst: No such file or directory' retitle 665067 FTBFS in non-UTF-8 locales (such as C) Bug #665067 [src:live-manual] FTBFS in non-UTF-8 locales (such as C) Bug #662227 [src:live-manual] FTBFS in non-UTF-8 locales (such as C) Ignoring request to change the title of bug#665067 to the same title Ignoring request to change the title of bug#662227 to the same title tag 662227 pending Bug #662227 [src:live-manual] FTBFS in non-UTF-8 locales (such as C) Bug #665067 [src:live-manual] FTBFS in non-UTF-8 locales (such as C) Added tag(s) pending. Added tag(s) pending. tag 665067 pending Bug #665067 [src:live-manual] FTBFS in non-UTF-8 locales (such as C) Bug #662227 [src:live-manual] FTBFS in non-UTF-8 locales (such as C) Ignoring request to alter tags of bug #665067 to the same tags previously set Ignoring request to alter tags of bug #662227 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 662227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662227 665067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665067 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#666268: calendar-timezones: Missing link for iceowl
Package: calendar-timezones Version: 10.0.3-3 Severity: critical Justification: breaks unrelated software Dear Maintainer, After bump to version 10.x a link provided to iceowl is lost in which case iceowl is broken. A quick fix is to reintroduce a link similar to the link for icedove and thunderbird. Eg. /usr/lib/iceowl/extensions/calendar-timezo...@mozilla.org -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666269: mediawiki: security release CVE-2012-1578/CVE-2012-1579/CVE-2012-1580/CVE-2012-1581/CVE-2012-1582
Package: mediawiki Version: 1.18.1-1 Severity: critical Tags: security Release announcement: http://lists.wikimedia.org/pipermail/wikitech-l/2012-March/059230.html Requested CVE-identifiers in here: http://seclists.org/oss-sec/2012/q1/728 CVE-identifiers assigned in here: http://seclists.org/oss-sec/2012/q1/745 CVE-2012-1578 https://bugzilla.wikimedia.org/show_bug.cgi?id=34212 CVE-2012-1579 https://bugzilla.wikimedia.org/show_bug.cgi?id=34907 CVE-2012-1580 https://bugzilla.wikimedia.org/show_bug.cgi?id=35317 CVE-2012-1581 https://bugzilla.wikimedia.org/show_bug.cgi?id=35078 CVE-2012-1582 https://bugzilla.wikimedia.org/show_bug.cgi?id=35315 - Henri Salo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 649068 in rgmanager/3.0.12-3.1
Processing commands for cont...@bugs.debian.org: found 649068 rgmanager/3.0.12-3.1 Bug #649068 [resource-agents,rgmanager] rgmanager and resource-agents: error when trying to install together The source rgmanager and version 3.0.12-3.1 do not appear to match any binary packages Marked as found in versions rgmanager/3.0.12-3.1. thanks Stopping processing here. Please contact me if you need assistance. -- 649068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649068 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#666237: typo3-dummy: prompting due to modified conffiles which where not modified by the user
severity 666237 important thanks Hi Andreas, thanks for your bugreport, as usual! :-) Much appreciated! On Donnerstag, 29. März 2012, Andreas Beckmann wrote: during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... while I agree with this (those are my words after all ;) I'm lowering the severity to important to make sure the fix for #666074 reaches wheezy (and stable-backports) fast. Once this happened (tomorrow or sunday) I will raise the severity again. cheers. Holger -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#666237: typo3-dummy: prompting due to modified conffiles which where not modified by the user
Processing commands for cont...@bugs.debian.org: severity 666237 important Bug #666237 [typo3-dummy] typo3-dummy: prompting due to modified conffiles which where not modified by the user Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 666237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666237 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#666188: marked as done (Ships the icon cache, package now 83M installed-size)
Your message dated Fri, 30 Mar 2012 07:35:41 + with message-id e1sdwn3-0001am...@franck.debian.org and subject line Bug#666188: fixed in gnome-themes-standard 3.4.0-2 has caused the Debian Bug report #666188, regarding Ships the icon cache, package now 83M installed-size 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.) -- 666188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-themes-standard Version: 3.4.0-1 Severity: serious $ dpkg -L gnome-themes-standard | grep cache /usr/share/icons/HighContrast/icon-theme.cache $ ls -l /usr/share/icons/HighContrast/icon-theme.cache -rw-r--r-- 1 root root 77002092 Mar 29 15:16 /usr/share/icons/HighContrast/icon-theme.cache We should probably continue to generate this at package install time instead of shipping it. :) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-themes-standard depends on: ii gconf2 3.2.3-4 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-27 ii libcairo-gobject2 1.10.2-7 ii libcairo2 1.10.2-7 ii libgdk-pixbuf2.0-0 2.26.0-1 ii libglib2.0-02.32.0-1 ii libgtk-3-0 3.4.0-1 ii libpango1.0-0 1.29.4-3+b1 ii librsvg2-2 2.36.0-1 Versions of packages gnome-themes-standard recommends: ii gtk2-engines 1:2.20.2-2 gnome-themes-standard suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: gnome-themes-standard Source-Version: 3.4.0-2 We believe that the bug you reported is fixed in the latest version of gnome-themes-standard, which is due to be installed in the Debian FTP archive: gnome-themes-standard_3.4.0-2.debian.tar.gz to main/g/gnome-themes-standard/gnome-themes-standard_3.4.0-2.debian.tar.gz gnome-themes-standard_3.4.0-2.dsc to main/g/gnome-themes-standard/gnome-themes-standard_3.4.0-2.dsc gnome-themes-standard_3.4.0-2_amd64.deb to main/g/gnome-themes-standard/gnome-themes-standard_3.4.0-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 666...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated gnome-themes-standard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 30 Mar 2012 09:07:09 +0200 Source: gnome-themes-standard Binary: gnome-themes-standard Architecture: source amd64 Version: 3.4.0-2 Distribution: experimental Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: gnome-themes-standard - Standard gnome themes Closes: 666188 Changes: gnome-themes-standard (3.4.0-2) experimental; urgency=low . * Remove icon-theme.cache file. We don't want to ship this file in the package but rather generate it at installation time. Closes: #666188 Checksums-Sha1: 24d467ed464cfcbd5c19390ef02c7a1bada492d2 2314 gnome-themes-standard_3.4.0-2.dsc dbc09c78f46c4048788a14eb0f9d944e2d76547b 3996 gnome-themes-standard_3.4.0-2.debian.tar.gz 5d4dfce5933c154f79d6d8b7c6d8571112ad89af 3409762 gnome-themes-standard_3.4.0-2_amd64.deb Checksums-Sha256: 39ebdf37484d0c9665378cdaac75155400c99aa0459a8ee6bdad58ba039fc82e 2314 gnome-themes-standard_3.4.0-2.dsc 1ca9056dab6d1a54c9674b6b0e3080759845b6f9eaa06dafff7b8fc8e1c74760 3996 gnome-themes-standard_3.4.0-2.debian.tar.gz 9b712d94b3b4bfc08e87a2c9be66fc8f33a5a69131784a2bf57ed1afca22cc23 3409762 gnome-themes-standard_3.4.0-2_amd64.deb Files: e2ae2c3ee24cedaf939ce419fe9067f1 2314 gnome optional gnome-themes-standard_3.4.0-2.dsc 850d2416b7c74b406d50dc238ba8efd5 3996 gnome optional gnome-themes-standard_3.4.0-2.debian.tar.gz c3d8f3ad8e9c8f4d273493f44b68655f 3409762 gnome optional gnome-themes-standard_3.4.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux)
Bug#612574: fixed in tortoisehg 2.1.4-1
I've contributed a patch upstream for a gtk/nautilus3 port of the extension, and they've pushed it into the mercurial repository (https://bitbucket.org/tortoisehg/thg/changeset/7017a49b612b). Could this be reopened now that there's a chance of a real fix? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 666144
Processing commands for cont...@bugs.debian.org: affects 666144 + mecab mecab-utils libmecab-dev Bug #666144 [libmecab1,libmecab2] libmecab2 and libmecab1: error when trying to install together Added indication that 666144 affects mecab, mecab-utils, and libmecab-dev thanks Stopping processing here. Please contact me if you need assistance. -- 666144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666144 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#666218: udeb broken: micro-evtd.command: line 10: syntax error: bad function name
* Ryan Tandy r...@nardis.ca [2012-03-29 22:50]: Your patch is correct but insufficient. Apparently in the 3.4 release upstream worked around the bashisms in /usr/sbin/micro-evtd.event and /usr/sbin/microapl by changing the shebang to /bin/bash; it was /bin/sh in both in 3.3.3. I feel pretty stupid for missing all of this; I was sure I tested installing from the 3.4-1 udeb before uploading but I don't see how that could have worked, unless d-i included a /bin/bash at some point. I will have to patch out the remaining bashisms in the scripts. I won't be able to work on that before this weekend. Thanks again for bringing this to my attention. My patch fixed the problem I saw - the error message from micro-evtd.command when starting d-i on a non-Buffalo machine. Thanks for checking the code and finding more problems. I'm happy to sponsor your upload when you have a complete fix. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: glib 2.32 uploaded to unstable
Processing commands for cont...@bugs.debian.org: severity 665677 serious Bug #665677 [src:gsmartcontrol] gsmartcontrol: FTBFS with glib 2.32 Severity set to 'serious' from 'important' severity 665679 serious Bug #665679 [src:qtwebkit] qtwebkit: FTBFS with glib 2.32 Severity set to 'serious' from 'important' severity 665666 serious Bug #665666 [src:openjdk-7] openjdk-7: FTBFS with glib 2.32: undefined references Severity set to 'serious' from 'important' severity 665670 serious Bug #665670 [src:gxneur] gxneur: FTBFS with glib 2.32 due to -Werror=deprecated-declarations Severity set to 'serious' from 'important' severity 665671 serious Bug #665671 [src:libgconf-bridge] libgconf-bridge: FTBFS with glib 2.32 due to -Werror=deprecated-declarations Severity set to 'serious' from 'important' severity 665672 serious Bug #665672 [src:pidgin-sipe] pidgin-sipe: FTBFS with glib 2.32 due to -Werror=deprecated-declarations Severity set to 'serious' from 'important' severity 665675 serious Bug #665675 [src:amanda] amanda: FTBFS with glib 2.32 Severity set to 'serious' from 'important' severity 665676 serious Bug #665676 [src:fotoxx] fotoxx: FTBFS with glib 2.32 Severity set to 'serious' from 'important' severity 665678 serious Bug #665678 [src:lua-gtk] lua-gtk: FTBFS with glib 2.32 Severity set to 'serious' from 'important' severity 665673 serious Bug #665673 [src:qof] qof: FTBFS with glib 2.32 due to -Werror=deprecated-declarations Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 665666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665666 665670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665670 665671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665671 665672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665672 665673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665673 665675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665675 665676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665676 665677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665677 665678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665678 665679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665679 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#665673: fixed upstream
tag 665673 fixed-upstream quit Just to make it clear in the bug report for people reviewing RC bugs, I do have a fix for this in upstream SVN: http://anonscm.debian.org/viewvc/qof/trunk/qof/qof/qofutil.c?r1=1328r2=1327pathrev=1328 A new upstream release will be made this weekend with a corresponding upload to Debian. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpSyfw62t2MI.pgp Description: PGP signature
Processed: fixed upstream
Processing commands for cont...@bugs.debian.org: tag 665673 fixed-upstream Bug #665673 [src:qof] qof: FTBFS with glib 2.32 due to -Werror=deprecated-declarations Added tag(s) fixed-upstream. quit Stopping processing here. Please contact me if you need assistance. -- 665673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665673 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#666269: [Pkg-mediawiki-commits] r310 - in mediawiki/sid-sec/debian: . patches
Author: tg
Date: 2012-03-30 08:43:27 + (Fri, 30 Mar 2012)
New Revision: 310
Added:
mediawiki/sid-sec/debian/patches/CVE-2012-1582.patch
Modified:
mediawiki/sid-sec/debian/changelog
mediawiki/sid-sec/debian/patches/series
Log:
first cut at #666269 for sid-security:
?\226?\128?\162 three do not seem to affect us: the code doesn?\226?\128?\153t
even appear to be in 1.15
?\226?\128?\162 one, I attempted to backport the fix (not yet tested)
?\226?\128?\162 one I cannot access?\226?\128?\166 wait for that to be disclosed
Modified: mediawiki/sid-sec/debian/changelog
===
--- mediawiki/sid-sec/debian/changelog 2012-03-20 10:15:18 UTC (rev 309)
+++ mediawiki/sid-sec/debian/changelog 2012-03-30 08:43:27 UTC (rev 310)
@@ -1,3 +1,14 @@
+mediawiki (1:1.15.5-9) UNRELEASED; urgency=high
+
+ * Address MW security release 1.18.1-1 (Closes: #666269)
+- CVE-2012-1578 MW#34212: doesn’t affect 1.15
+- CVE-2012-1579 MW#34907: doesn’t affect 1.15
+- CVE-2012-1580 MW#35317: doesn’t affect 1.15
+- CVE-2012-1581 MW#35078: (can’t access bugreport)
+- CVE-2012-1582 MW#35315: fix backported
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 30 Mar 2012 10:41:58 +0200
+
mediawiki (1:1.15.5-8) unstable; urgency=low
* Fix reversing IPv4 address for SORBS blacklist; patch from
Added: mediawiki/sid-sec/debian/patches/CVE-2012-1582.patch
===
--- mediawiki/sid-sec/debian/patches/CVE-2012-1582.patch
(rev 0)
+++ mediawiki/sid-sec/debian/patches/CVE-2012-1582.patch2012-03-30
08:43:27 UTC (rev 310)
@@ -0,0 +1,150 @@
+Description: Fixed a few strip tag exposed bugs.
+Author: Tim Starling (r114231)
+Bug: https://bugzilla.wikimedia.org/show_bug.cgi?id=35315
+
+Index: mediawiki-1.15.5/includes/parser/CoreParserFunctions.php
+===
+--- mediawiki-1.15.5.orig/includes/parser/CoreParserFunctions.php
2012-03-30 10:28:12.0 +0200
mediawiki-1.15.5/includes/parser/CoreParserFunctions.php 2012-03-30
10:32:57.0 +0200
+@@ -120,7 +120,8 @@
+ }
+
+ static function urlencode( $parser, $s = '' ) {
+- return urlencode( $s );
++ $func = 'urlencode';
++ return $parser-markerSkipCallback( $s, $func );
+ }
+
+ static function lcfirst( $parser, $s = '' ) {
+@@ -135,20 +136,12 @@
+
+ static function lc( $parser, $s = '' ) {
+ global $wgContLang;
+- if ( is_callable( array( $parser, 'markerSkipCallback' ) ) ) {
+- return $parser-markerSkipCallback( $s, array(
$wgContLang, 'lc' ) );
+- } else {
+- return $wgContLang-lc( $s );
+- }
++ return $parser-markerSkipCallback( $s, array( $wgContLang,
'lc' ) );
+ }
+
+ static function uc( $parser, $s = '' ) {
+ global $wgContLang;
+- if ( is_callable( array( $parser, 'markerSkipCallback' ) ) ) {
+- return $parser-markerSkipCallback( $s, array(
$wgContLang, 'uc' ) );
+- } else {
+- return $wgContLang-uc( $s );
+- }
++ return $parser-markerSkipCallback( $s, array( $wgContLang,
'uc' ) );
+ }
+
+ static function localurl( $parser, $s = '', $arg = null ) { return
self::urlFunction( 'getLocalURL', $s, $arg ); }
+@@ -180,15 +173,17 @@
+ }
+ }
+
+- static function formatNum( $parser, $num = '', $raw = null) {
+- if ( self::israw( $raw ) ) {
+- return
$parser-getFunctionLang()-parseFormattedNumber( $num );
++ static function formatnum( $parser, $num = '', $raw = null) {
++ if ( self::isRaw( $raw ) ) {
++ $func = array( $parser-getFunctionLang(),
'parseFormattedNumber' );
+ } else {
+- return $parser-getFunctionLang()-formatNum( $num );
++ $func = array( $parser-getFunctionLang(), 'formatNum'
);
+ }
++ return $parser-markerSkipCallback( $num, $func );
+ }
+
+ static function grammar( $parser, $case = '', $word = '' ) {
++ $word = $parser-killMarkers( $word );
+ return $parser-getFunctionLang()-convertGrammar( $word, $case
);
+ }
+
+@@ -495,7 +490,8 @@
+ /**
+* Unicode-safe str_pad with the restriction that $length is forced to
be = 500
+*/
+- static function pad( $string, $length, $padding = '0', $direction =
STR_PAD_RIGHT ) {
++ static function pad( $parser, $string, $length, $padding = '0',
$direction = STR_PAD_RIGHT ) {
++ $padding = $parser-killMarkers( $padding );
+ $lengthOfPadding = mb_strlen( $padding );
+
Bug#661658: cctools: FTBFS on kfreebsd
On Tue, Mar 27, 2012 at 09:44:01PM +0200, Julien Cristau wrote: On Tue, Mar 27, 2012 at 09:50:14 +0200, Michael Hanke wrote: Maybe a simple rebuild attempt would fix it (CC'ing the wb-team)? gb cctools_3.4.2-1 . kfreebsd-amd64 kfreebsd-i386 Done. Error remains the same -- need to look more closely. Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666276: librsvg2-bin: /usr/bin/rsvg is not shipped anymore
Package: librsvg2-bin Version: 2.36.0-1 Severity: critical Justification: breaks unrelated software $ convert iceweasel/debian/branding/iceweasel_logo.svg /tmp/test.png sh: 1: rsvg: not found convert: delegate failed `rsvg %i %o' @ error/delegate.c/InvokeDelegate/1058. convert: unable to open image `/tmp/magick-OAoLiTCX': @ error/blob.c/OpenBlob/2587. convert: unable to open file `/tmp/magick-OAoLiTCX': @ error/constitute.c/ReadImage/571. convert: missing an image filename `/tmp/test.png' @ error/convert.c/ConvertImageCommand/3011. This worked properly in 2.34.2-3, and breaks in 2.36.0-1. This FTBFSes iceweasel. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages librsvg2-bin depends on: ii libc6 2.13-27 ii libcairo2 1.10.2-7 ii libglib2.0-0 2.30.2-6 ii libgtk-3-03.2.3-1 ii librsvg2-22.36.0-1 librsvg2-bin recommends no packages. librsvg2-bin suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666277: openblas: FTBFS: cp: cannot stat `debian/tmp/libopenblas.so.0': No such file or directory
Source: openblas Version: 0.1alpha2.2-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p . Adding cdbs dependencies to debian/libopenblas-base.substvars dh_installdirs -plibopenblas-base Adding cdbs dependencies to debian/libopenblas-dev.substvars dh_installdirs -plibopenblas-dev dh_installdocs -plibopenblas-base ./README dh_installexamples -plibopenblas-base dh_installman -plibopenblas-base dh_installinfo -plibopenblas-base dh_installmenu -plibopenblas-base dh_installcron -plibopenblas-base dh_installinit -plibopenblas-base dh_installdebconf -plibopenblas-base dh_installemacsen -plibopenblas-base dh_installcatalogs -plibopenblas-base dh_installpam -plibopenblas-base dh_installlogrotate -plibopenblas-base dh_installlogcheck -plibopenblas-base dh_installchangelogs -plibopenblas-base dh_installudev -plibopenblas-base dh_lintian -plibopenblas-base dh_bugfiles -plibopenblas-base dh_install -plibopenblas-base cp: cannot stat `debian/tmp/libopenblas.so.0': No such file or directory dh_install: cp -a debian/tmp/libopenblas.so.0 debian/libopenblas-base/usr/lib/openblas-base// returned exit code 1 make: *** [binary-install/libopenblas-base] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/openblas_0.1alpha2.2-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666278: polybori: FTBFS: mv: cannot stat `debian/python-polybori2.7/*': No such file or directory
Source: polybori Version: 0.5~rc1-2.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_clean -k dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p . mkdir -p debian/tmp/ mv debian/python-polybori2.7/* debian/tmp/ mv: cannot stat `debian/python-polybori2.7/*': No such file or directory make: *** [common-install-impl] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/polybori_0.5~rc1-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666279: ulogd: FTBFS: cp: cannot stat `./debian/tmp/usr/lib/ulogd/ulogd_SQLITE3.so': No such file or directory
Source: ulogd Version: 1.24-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/pcap' /usr/bin/install -c -m 755 -d /«PKGBUILDDIR»/debian/tmp//usr/lib/ulogd /usr/bin/install -c -m 755 *.so /«PKGBUILDDIR»/debian/tmp//usr/lib/ulogd make[2]: Leaving directory `/«PKGBUILDDIR»/pcap' /usr/bin/install -c -D -m 755 ulogd /«PKGBUILDDIR»/debian/tmp//usr/sbin/ulogd make[1]: Leaving directory `/«PKGBUILDDIR»' touch debian/stamp-makefile-install Adding cdbs dependencies to debian/ulogd.substvars dh_installdirs -pulogd Adding cdbs dependencies to debian/ulogd-mysql.substvars dh_installdirs -pulogd-mysql Adding cdbs dependencies to debian/ulogd-pgsql.substvars dh_installdirs -pulogd-pgsql Adding cdbs dependencies to debian/ulogd-pcap.substvars dh_installdirs -pulogd-pcap Adding cdbs dependencies to debian/ulogd-sqlite3.substvars dh_installdirs -pulogd-sqlite3 dh_installdocs -pulogd ./README ./TODO ./AUTHORS dh_installexamples -pulogd dh_installman -pulogd dh_installinfo -pulogd dh_installmenu -pulogd dh_installcron -pulogd dh_installinit -pulogd dh_installdebconf -pulogd dh_installemacsen -pulogd dh_installcatalogs -pulogd dh_installpam -pulogd dh_installlogrotate -pulogd dh_installlogcheck -pulogd dh_installchangelogs -pulogd Changes dh_installudev -pulogd dh_lintian -pulogd dh_bugfiles -pulogd dh_install -pulogd dh_link -pulogd dh_installmime -pulogd dh_installgsettings -pulogd dh_installdocs -pulogd-mysql ./README ./TODO ./AUTHORS dh_installexamples -pulogd-mysql dh_installman -pulogd-mysql dh_installinfo -pulogd-mysql dh_installmenu -pulogd-mysql dh_installcron -pulogd-mysql dh_installinit -pulogd-mysql dh_installdebconf -pulogd-mysql dh_installemacsen -pulogd-mysql dh_installcatalogs -pulogd-mysql dh_installpam -pulogd-mysql dh_installlogrotate -pulogd-mysql dh_installlogcheck -pulogd-mysql dh_installchangelogs -pulogd-mysql Changes dh_installudev -pulogd-mysql dh_lintian -pulogd-mysql dh_bugfiles -pulogd-mysql dh_install -pulogd-mysql dh_link -pulogd-mysql dh_installmime -pulogd-mysql dh_installgsettings -pulogd-mysql dh_installdocs -pulogd-pgsql ./README ./TODO ./AUTHORS dh_installexamples -pulogd-pgsql dh_installman -pulogd-pgsql dh_installinfo -pulogd-pgsql dh_installmenu -pulogd-pgsql dh_installcron -pulogd-pgsql dh_installinit -pulogd-pgsql dh_installdebconf -pulogd-pgsql dh_installemacsen -pulogd-pgsql dh_installcatalogs -pulogd-pgsql dh_installpam -pulogd-pgsql dh_installlogrotate -pulogd-pgsql dh_installlogcheck -pulogd-pgsql dh_installchangelogs -pulogd-pgsql Changes dh_installudev -pulogd-pgsql dh_lintian -pulogd-pgsql dh_bugfiles -pulogd-pgsql dh_install -pulogd-pgsql dh_link -pulogd-pgsql dh_installmime -pulogd-pgsql dh_installgsettings -pulogd-pgsql dh_installdocs -pulogd-pcap ./README ./TODO ./AUTHORS dh_installexamples -pulogd-pcap dh_installman -pulogd-pcap dh_installinfo -pulogd-pcap dh_installmenu -pulogd-pcap dh_installcron -pulogd-pcap dh_installinit -pulogd-pcap dh_installdebconf -pulogd-pcap dh_installemacsen -pulogd-pcap dh_installcatalogs -pulogd-pcap dh_installpam -pulogd-pcap dh_installlogrotate -pulogd-pcap dh_installlogcheck -pulogd-pcap dh_installchangelogs -pulogd-pcap Changes dh_installudev -pulogd-pcap dh_lintian -pulogd-pcap dh_bugfiles -pulogd-pcap dh_install -pulogd-pcap dh_link -pulogd-pcap dh_installmime -pulogd-pcap dh_installgsettings -pulogd-pcap dh_installdocs -pulogd-sqlite3 ./README ./TODO ./AUTHORS dh_installexamples -pulogd-sqlite3 dh_installman -pulogd-sqlite3 dh_installinfo -pulogd-sqlite3 dh_installmenu -pulogd-sqlite3 dh_installcron -pulogd-sqlite3 dh_installinit -pulogd-sqlite3 dh_installdebconf -pulogd-sqlite3 dh_installemacsen -pulogd-sqlite3 dh_installcatalogs -pulogd-sqlite3 dh_installpam -pulogd-sqlite3 dh_installlogrotate -pulogd-sqlite3 dh_installlogcheck -pulogd-sqlite3 dh_installchangelogs -pulogd-sqlite3 Changes dh_installudev -pulogd-sqlite3 dh_lintian -pulogd-sqlite3 dh_bugfiles -pulogd-sqlite3 dh_install -pulogd-sqlite3 cp: cannot stat `./debian/tmp/usr/lib/ulogd/ulogd_SQLITE3.so': No such file or directory dh_install: cp -a ./debian/tmp/usr/lib/ulogd/ulogd_SQLITE3.so debian/ulogd-sqlite3/usr/lib/ulogd/ returned exit code 1 make: *** [binary-install/ulogd-sqlite3] Error 2 The full build
Bug#666280: jlint: FTBFS: jlint.cc:299:50: error: invalid conversion from 'const char*' to 'char*' [-fpermissive]
Source: jlint Version: 3.0-4.4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: g++ -c -Wall -O2 -g jlint.cc jlint.cc: In function 'void format_message(int, const utf_string, int, __va_list_tag*)': jlint.cc:185:29: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] jlint.cc:197:31: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] jlint.cc:240:68: warning: field precision specifier '.*' expects argument of type 'int', but argument 3 has type 'long int' [-Wformat] jlint.cc: In function 'void set_class_source_path(class_desc*)': jlint.cc:299:50: error: invalid conversion from 'const char*' to 'char*' [-fpermissive] jlint.cc: In function 'bool parse_class_file(byte*)': jlint.cc:431:9: warning: unused variable 'desc_index' [-Wunused-variable] jlint.cc:496:13: warning: unused variable 'max_stack' [-Wunused-variable] jlint.cc:325:7: warning: unused variable 'minor_version' [-Wunused-variable] jlint.cc:327:7: warning: unused variable 'major_version' [-Wunused-variable] jlint.cc: In function 'int main(int, char**)': jlint.cc:1086:50: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] make[1]: *** [jlint.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/jlint_3.0-4.4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666281: unison2.32.52: FTBFS: make: rsvg: Command not found
Source: unison2.32.52 Version: 2.32.52-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»' etags *.mli */*.mli *.ml */*.ml */*.m *.c */*.c *.txt /bin/sh: 1: etags: not found make[2]: [tags] Error 127 (ignored) make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' mv '/«PKGBUILDDIR»/unison' '/«PKGBUILDDIR»/unison-2.32.52' rsvg -f png -w 32 -h 32 debian/unison-gtk.svg.in debian/unison2.32.52-gtk.png make: rsvg: Command not found make: *** [debian/unison2.32.52-gtk.png] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/unison2.32.52_2.32.52-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666282: pentobi: FTBFS: sh: 1: rsvg: not found
Source: pentobi Version: 1.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' convert -scale 32x32 src/pentobi/pentobi.svg src/pentobi/pentobi.xpm sh: 1: rsvg: not found convert: delegate failed `rsvg %i %o' @ error/delegate.c/InvokeDelegate/1058. convert: unable to open image `/tmp/magick-zSpNOFQI': @ error/blob.c/OpenBlob/2587. convert: unable to open file `/tmp/magick-zSpNOFQI': @ error/constitute.c/ReadImage/571. convert: missing an image filename `src/pentobi/pentobi.xpm' @ error/convert.c/ConvertImageCommand/3011. make[1]: *** [override_dh_auto_build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/pentobi_1.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666283: proftpd-mod-msg: FTBFS: mod_msg.c:314:5: error: format not a string literal and no format arguments [-Werror=format-security]
Source: proftpd-mod-msg Version: 0.4.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' DESTDIR=/«PKGBUILDDIR»/debian/proftpd-mod-msg prxs -c mod_msg.c libtool --mode=compile gcc -DLINUX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_msg.c libtool: compile: gcc -DLINUX -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_msg.c -fPIC -DPIC -o .libs/mod_msg.o mod_msg.c: In function 'msg_post_any': mod_msg.c:314:5: error: format not a string literal and no format arguments [-Werror=format-security] mod_msg.c: In function 'msg_post_err_any': mod_msg.c:346:5: error: format not a string literal and no format arguments [-Werror=format-security] mod_msg.c: In function 'msg_handle_msg': mod_msg.c:713:11: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'char *' [-Wformat] mod_msg.c:713:11: warning: format '%s' expects argument of type 'char *', but argument 5 has type 'pid_t' [-Wformat] mod_msg.c:713:11: warning: too many arguments for format [-Wformat-extra-args] cc1: some warnings being treated as errors prxs: error executing command (1) make[1]: *** [override_dh_auto_build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/proftpd-mod-msg_0.4.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666284: avbin: FTBFS: make[1]: *** No rule to make target `Makefile.'. Stop.
Source: avbin Version: 7-1.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh build-arch dh_testdir -a dh_auto_configure -a dh_auto_build -a make[1]: Entering directory `/«PKGBUILDDIR»' Makefile:16: Makefile.: No such file or directory make[1]: *** No rule to make target `Makefile.'. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/avbin_7-1.2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666285: garlic: FTBFS: cp: cannot stat `./garlic': No such file or directory
Source: garlic Version: 1.6-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_clean -k dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p . Adding cdbs dependencies to debian/garlic.substvars dh_installdirs -pgarlic dh_installdocs -pgarlic ./README ./TODO ./BUGS dh_installexamples -pgarlic dh_installman -pgarlic dh_installinfo -pgarlic dh_installmenu -pgarlic dh_installcron -pgarlic dh_installinit -pgarlic dh_installdebconf -pgarlic dh_installemacsen -pgarlic dh_installcatalogs -pgarlic dh_installpam -pgarlic dh_installlogrotate -pgarlic dh_installlogcheck -pgarlic dh_installchangelogs -pgarlic dh_installudev -pgarlic dh_lintian -pgarlic dh_bugfiles -pgarlic dh_install -pgarlic cp: cannot stat `./garlic': No such file or directory dh_install: cp -a ./garlic debian/garlic/usr/bin// returned exit code 1 make: *** [binary-install/garlic] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/garlic_1.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666286: yasr: FTBFS: yasr.h:312:12: error: conflicting types for 'openpty'
Source: yasr Version: 0.6.9-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: gcc -DPACKAGE_DATA_DIR=\/usr/share/yasr\ -DLOCALEDIR=\/usr/share/locale\ -DHAVE_CONFIG_H -I. -I.. -g -O2 -Wall -c config.c In file included from config.c:19:0: yasr.h:312:12: error: conflicting types for 'openpty' /usr/include/pty.h:34:12: note: previous declaration of 'openpty' was here yasr.h:321:12: error: conflicting types for 'forkpty' /usr/include/pty.h:40:12: note: previous declaration of 'forkpty' was here config.c: In function 'readconf': config.c:82:5: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result [-Wunused-result] make[3]: *** [config.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/yasr_0.6.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666287: vdr-plugin-infosatepg: FTBFS: infosatepg.cpp:193:28: error: 'class cEITScanner' has no member named 'UsesDevice'
Source: vdr-plugin-infosatepg Version: 0.0.11-6 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: g++ -g -Wall -Woverloaded-virtual -Wno-parentheses -O2 -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='infosatepg' -I/usr/include/dvb-s2api-liplianin -I/usr/include/vdr/include infosatepg.cpp In file included from infosatepg.h:13:0, from infosatepg.cpp:17: /usr/include/vdr/include/vdr/status.h:33:16: warning: 'virtual void cStatus::ChannelSwitch(const cDevice*, int, bool)' was hidden [-Woverloaded-virtual] status.h:23:16: warning: by 'virtual void cStatusInfosatepg::ChannelSwitch(const cDevice*, int)' [-Woverloaded-virtual] infosatepg.cpp: In member function 'virtual void cPluginInfosatepg::MainThreadHook()': infosatepg.cpp:193:28: error: 'class cEITScanner' has no member named 'UsesDevice' make[2]: *** [infosatepg.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/vdr-plugin-infosatepg_0.0.11-6_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666288: uw-imap: FTBFS: install: cannot stat `c-client.a': No such file or directory
Source: uw-imap Version: 8:2007e~dfsg-3.3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch sed -e 's/__LIBVER__/2007e/g' -e 's/__LIBFULLVER__/2007e.0/g' -e 's/__VER__/2007e/g' debian/control.in.in debian/control.in test -x debian/rules dh_testroot dh_clean -k dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p . echo sed -e 's/__LIBVER__/2007e/g' -e 's/__LIBFULLVER__/2007e.0/g' -e 's/__VER__/2007e/g' debian/control.in.in | diff -u debian/control.in - sed -e 's/__LIBVER__/2007e/g' -e 's/__LIBFULLVER__/2007e.0/g' -e 's/__VER__/2007e/g' debian/control.in.in | diff -u debian/control.in - for file in `find debian -maxdepth 2 -type f -name '*.in' -not -name control.in -not -name control.in.in -not -name POTFILES.in`; do \ targetfile=`echo $file | sed -e 's/__VER__/2007e/g' -e 's/\\.in$//'`; \ sed -e 's/__LIBVER__/2007e/g' -e 's/__LIBFULLVER__/2007e.0/g' -e 's/__VER__/2007e/g' $file $targetfile; \ done for file in `find debian -maxdepth 2 -type f -name '*._in'`; do \ targetfile=`echo $file | sed -e 's/\\._in$//' -e 's/__PKG__/uw-imapd/g'`; \ sed -e 's/__LIBVER__/2007e/g' -e 's/__LIBFULLVER__/2007e.0/g' -e 's/__VER__/2007e/g' -e 's/__PKG__/uw-imapd/g' -e 's/__CERT__/imapd/g' -e 's/__PAMSERVICE__/imap/g' -e 's/__DESC__/University of Washington IMAP daemon/g' -e 's/__DAEMONSETS__/imap2:imapd imap3:imapd imaps:imapd/g' $file $targetfile; \ done for file in `find debian -maxdepth 2 -type f -name '*._in'`; do \ targetfile=`echo $file | sed -e 's/\\._in$//' -e 's/__PKG__/ipopd/g'`; \ sed -e 's/__LIBVER__/2007e/g' -e 's/__LIBFULLVER__/2007e.0/g' -e 's/__VER__/2007e/g' -e 's/__PKG__/ipopd/g' -e 's/__CERT__/ipop3d/g' -e 's/__PAMSERVICE__/pop/g' -e 's/__DESC__/University of Washington POP3 daemon/g' -e 's/__DAEMONSETS__/pop2:ipop2d pop3:ipop3d pop3s:ipop3d/g' $file $targetfile; \ done dh_buildinfo touch debian/stamp-buildinfo mkdir -p debian/tmp/usr/lib install -m 0644 c-client.a debian/tmp/usr/lib/libc-client.a install: cannot stat `c-client.a': No such file or directory make: *** [common-install-arch] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/uw-imap_82007e~dfsg-3.3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666289: espeakedit: FTBFS: cp: cannot stat `debian/tmp/src/espeakedit': No such file or directory
Source: espeakedit Version: 1.46.02-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch dh binary-arch dh_testroot -a dh_prep -a dh_installdirs -a dh_auto_install -a dh_install -a cp: cannot stat `debian/tmp/src/espeakedit': No such file or directory dh_install: cp -a debian/tmp/src/espeakedit debian/espeakedit//usr/bin/ returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/espeakedit_1.46.02-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666290: xml2: FTBFS: gcc: error: unrecognized option '-V'
Source: xml2
Version: 0.4-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a newer dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
gcc version 4.6.3 (Debian 4.6.3-1)
configure:2536: $? = 0
configure:2543: gcc -V 5
gcc: error: unrecognized option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:2546: $? = 4
configure:2569: checking for C compiler default output file name
configure:2596: gccconftest.c 5
configure:2599: $? = 0
configure:2637: result: a.out
configure:2654: checking whether the C compiler works
configure:2664: ./a.out
configure:2667: $? = 0
configure:2684: result: yes
configure:2691: checking whether we are cross compiling
configure:2693: result: no
configure:2696: checking for suffix of executables
configure:2703: gcc -o conftestconftest.c 5
configure:2706: $? = 0
configure:2730: result:
configure:2736: checking for suffix of object files
configure:2762: gcc -c conftest.c 5
configure:2765: $? = 0
configure:2788: result: o
configure:2792: checking whether we are using the GNU C compiler
configure:2821: gcc -c conftest.c 5
configure:2827: $? = 0
configure:2844: result: yes
configure:2849: checking whether gcc accepts -g
configure:2879: gcc -c -g conftest.c 5
configure:2885: $? = 0
configure:2984: result: yes
configure:3001: checking for gcc option to accept ISO C89
configure:3075: gcc -c -g -O2 conftest.c 5
configure:3081: $? = 0
configure:3104: result: none needed
configure:3133: checking for style of include used by make
configure:3161: result: GNU
configure:3189: checking dependency style of gcc
configure:3279: result: none
configure:3347: checking for pkg-config
configure:3365: found /usr/bin/pkg-config
configure:3377: result: /usr/bin/pkg-config
configure:3406: checking pkg-config is at least version 0.9.0
configure:3409: result: yes
configure:3420: checking for XML
configure:3428: $PKG_CONFIG --exists --print-errors libxml
Package libxml was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml' found
configure:3431: $? = 1
configure:3446: $PKG_CONFIG --exists --print-errors libxml
Package libxml was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml' found
configure:3449: $? = 1
No package 'libxml' found
configure:3487: error: Package requirements (libxml) were not met:
No package 'libxml' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables XML_CFLAGS
and XML_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
## ##
## Cache variables. ##
## ##
ac_cv_c_compiler_gnu=yes
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_PKG_CONFIG_set=
ac_cv_env_PKG_CONFIG_value=
ac_cv_env_XML_CFLAGS_set=
ac_cv_env_XML_CFLAGS_value=
ac_cv_env_XML_LIBS_set=
ac_cv_env_XML_LIBS_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-linux-gnu
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_objext=o
ac_cv_path_ac_pt_PKG_CONFIG=/usr/bin/pkg-config
ac_cv_path_install='/usr/bin/install -c'
ac_cv_prog_AWK=mawk
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_cc_c89=
ac_cv_prog_cc_g=yes
ac_cv_prog_make_make_set=yes
am_cv_CC_dependencies_compiler_type=none
## - ##
## Output variables. ##
## - ##
ACLOCAL='${SHELL} /«PKGBUILDDIR»/missing --run aclocal-1.9'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE='#'
AMTAR='${SHELL} /«PKGBUILDDIR»/missing --run tar'
AUTOCONF='${SHELL} /«PKGBUILDDIR»/missing --run autoconf'
AUTOHEADER='${SHELL} /«PKGBUILDDIR»/missing --run autoheader'
AUTOMAKE='${SHELL} /«PKGBUILDDIR»/missing --run automake-1.9'
AWK='mawk'
CC='gcc'
CCDEPMODE='depmode=none'
CFLAGS='-g -O2'
CPP=''
CPPFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR='.deps'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
GREP=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL
Bug#666291: infon: FTBFS: infond.c:27:23: fatal error: daemonize.h: No such file or directory
Source: infon Version: 0~r198-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: cc -Wall -g -DDAEMONIZING -DNO_CONSOLE_CLIENT -DRENDERER_PATH=\/usr/lib/infon-viewer/\ -O2 -pedantic -std=gnu99 -Wall -DREVISION=\\ -ggdb -DPREFIX=\/usr/share/infon-server/\ -Ilua-5.1.2/src/ infond.c -c -o infond.o infond.c:27:23: fatal error: daemonize.h: No such file or directory compilation terminated. make[1]: *** [infond.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/infon_0~r198-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666292: libmecab-perl: FTBFS: MeCab_wrap.cxx:1826:16: error: 'mecab_node_t' has no member named 'sentence_length'
Source: libmecab-perl
Version: 0.98-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a newer dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
g++ -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -O2 -g -DVERSION=\0.993\ -DXS_VERSION=\0.993\
-fPIC -I/usr/lib/perl/5.14/CORE MeCab_wrap.cxx
MeCab_wrap.cxx: In function 'const mecab_node_t*
mecab_node_t_begin_node_list(mecab_node_t*, size_t)':
MeCab_wrap.cxx:1826:16: error: 'mecab_node_t' has no member named
'sentence_length'
MeCab_wrap.cxx:1828:17: error: 'mecab_node_t' has no member named
'begin_node_list'
MeCab_wrap.cxx:1829:19: error: 'mecab_node_t' has no member named
'begin_node_list'
MeCab_wrap.cxx: In function 'const mecab_node_t*
mecab_node_t_end_node_list(mecab_node_t*, size_t)':
MeCab_wrap.cxx:1834:16: error: 'mecab_node_t' has no member named
'sentence_length'
MeCab_wrap.cxx:1836:17: error: 'mecab_node_t' has no member named
'end_node_list'
MeCab_wrap.cxx:1837:19: error: 'mecab_node_t' has no member named
'end_node_list'
MeCab_wrap.cxx: In function 'void _wrap_Token_lcAttr_get(PerlInterpreter*,
CV*)':
MeCab_wrap.cxx:2516:5: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:2516:20: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:2516:43: error: expected primary-expression before ')' token
MeCab_wrap.cxx:2516:45: error: expected ';' before numeric constant
MeCab_wrap.cxx:2530:30: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:2530:30: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:2530:30: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:2530:46: error: expected primary-expression before '' token
MeCab_wrap.cxx:2530:54: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'void _wrap_Token_rcAttr_get(PerlInterpreter*,
CV*)':
MeCab_wrap.cxx:2544:5: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:2544:20: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:2544:43: error: expected primary-expression before ')' token
MeCab_wrap.cxx:2544:45: error: expected ';' before numeric constant
MeCab_wrap.cxx:2558:30: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:2558:30: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:2558:30: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:2558:46: error: expected primary-expression before '' token
MeCab_wrap.cxx:2558:54: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'void _wrap_Token_posid_get(PerlInterpreter*,
CV*)':
MeCab_wrap.cxx:2572:5: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:2572:20: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:2572:43: error: expected primary-expression before ')' token
MeCab_wrap.cxx:2572:45: error: expected ';' before numeric constant
MeCab_wrap.cxx:2586:30: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:2586:30: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:2586:30: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:2586:46: error: expected primary-expression before '' token
MeCab_wrap.cxx:2586:54: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'void _wrap_Token_wcost_get(PerlInterpreter*,
CV*)':
MeCab_wrap.cxx:2600:5: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:2600:20: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:2600:43: error: expected primary-expression before ')' token
MeCab_wrap.cxx:2600:45: error: expected ';' before numeric constant
MeCab_wrap.cxx:2614:30: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:2614:30: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:2614:30: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:2614:46: error: expected primary-expression before '' token
MeCab_wrap.cxx:2614:54: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'void _wrap_Token_feature_get(PerlInterpreter*,
CV*)':
MeCab_wrap.cxx:2628:5: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:2628:20: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:2628:43: error: expected primary-expression before ')' token
MeCab_wrap.cxx:2628:45: error: expected ';' before numeric constant
MeCab_wrap.cxx:2642:30: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:2642:30: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx
Bug#666293: dvi2ps: FTBFS: dvi2.c:120: undefined reference to `kpse_set_progname'
Source: dvi2ps Version: 4.1j-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: gcc -o dvi2ps dvi2.o dviconv.o dfdcom.o fontcom.o set.o rfset.o vfset.o dconv.o run.o mag.o fontdesc.o scanfont.o virfont.o vfdcom.o pkfont.o gffont.o rastfont.o bifont.o type1font.o wlfont.o ttfont.o vflfont.o mmfont.o compfont.o decompfont.o execfont.o funcfont.o kpse.o kanji.o open.o io.o util.o xxstdio.o version.o ps.o psrast.o psbi.o pstfm.o pstype1.o pswl.o pstt.o pstt2t1.o psvfl.o pst1form.o writet1.o psspecial.o pscolor.o psifont.o psio.o -L/usr/lib -lVFlib3 -L/usr/lib -lfreetype -L/usr/lib -lkpathsea -lm dvi2.o: In function `main': /«PKGBUILDDIR»/dvi2.c:120: undefined reference to `kpse_set_progname' collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/dvi2ps_4.1j-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666294: octave-miscellaneous: FTBFS: /bin/bash: lex: command not found
Source: octave-miscellaneous
Version: 1.0.11-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a recent dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
fakeroot debian/rules binary-arch
test -x debian/rules
dh_testroot
dh_prep
dh_installdirs -A
mkdir -p .
Adding cdbs dependencies to debian/octave-miscellaneous.substvars
dh_installdirs -poctave-miscellaneous
Checking the Octave version... ok
mkdir -p /«PKGBUILDDIR»/debian/octave-miscellaneous/usr/share/octave/packages
\
/«PKGBUILDDIR»/debian/octave-miscellaneous/usr/lib/x86_64-linux-gnu/octave/packages
[ -e PKG_ADD ] mv PKG_ADD PKG_ADD.bak
make: [install-pkg] Error 1 (ignored)
/usr/bin/octave --no-history --silent --no-init-file --eval
\
pkg ('prefix',
[pwd(),'/debian/octave-miscellaneous/usr/share/octave/packages'],
\
[pwd(),'/debian/octave-miscellaneous/usr/lib/x86_64-linux-gnu/octave/packages']);
\
pkg ('local_list', [pwd(),'/local-list']); \
pkg ('global_list', [pwd(),'/global-list']); \
if (exist ('PKG_ADD.bak') == 2), \
movefile ('PKG_ADD.bak', 'PKG_ADD'); \
endif; \
pkg -verbose -nodeps install .
warning: X11 DISPLAY environment variable not set
mkdir (/tmp/oct-KyiN0W)
Copying directory (., /tmp/oct-KyiN0W)
warning: X11 DISPLAY environment variable not set
warning: X11 DISPLAY environment variable not set
warning: X11 DISPLAY environment variable not set
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 mkoctfile... /usr/bin/mkoctfile
retrieving compile and link flags from /usr/bin/mkoctfile
checking for F77_FUNC... yes
checking for octave... /usr/bin/octave
checking for OCTAVE_VERSION in Octave... 3.6.1
checking for octave_config_info('canonical_host_type') in Octave...
x86_64-pc-linux-gnu
checking for octave_config_info('SHLEXT') in Octave... so
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for strip... strip
checking for fork... yes
checking for socklen_t... yes
checking for octave_function(void)... 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 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 term.h usability... yes
checking term.h presence... yes
checking for term.h... yes
checking termcap.h usability... yes
checking termcap.h presence... yes
checking for termcap.h... yes
checking for tgetnum in -ltermcap... yes
configure: creating ./config.status
config.status: creating Makeconf
$prefix is
/«PKGBUILDDIR»/debian/octave-miscellaneous/usr/share/octave/packages/miscellaneous-1.0.11
$exec_prefix is ${prefix}
octave commands will install into the following directories:
m-files: /usr/share/octave/3.6.1/site/m/octave-forge
oct-files:
/usr/lib/x86_64-linux-gnu/octave/3.6.1/site/oct/x86_64-pc-linux-gnu/octave-forge
binaries:
/usr/lib/x86_64-linux-gnu/octave/3.6.1/site/exec/x86_64-pc-linux-gnu
alternatives:
m-files: /usr/share/octave/3.6.1/site/octave-forge-alternatives/m
oct-files:
/usr/lib/x86_64-linux-gnu/octave/3.6.1/site/octave-forge-alternatives/oct/x86_64-pc-linux-gnu
shell commands will install into the following directories:
binaries: ${exec_prefix}/bin
man pages: ${datarootdir}/man
libraries: ${exec_prefix}/lib
headers: ${prefix}/include
octave-forge is configured with
octave: /usr/bin/octave (version 3.6.1)
mkoctfile: /usr/bin/mkoctfile for Octave 1
have term.h or termcap.h: yes
find . -name NOINSTALL -print# shows which toolboxes won't be installed
/bin/bash: lex: command not found
make[1]: *** [xmltree_read.c
Bug#666295: scotch: FTBFS: cp: cannot stat `debian/tmp/int/bin/scotch_esmumps': No such file or directory
Source: scotch Version: 5.1.12b.dfsg-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch QUILT_PATCHES=debian/patches quilt push -a || test $? = 2 Applying patch build-fixes.patch patching file src/Makefile patching file src/libscotchmetis/Makefile patching file src/libscotch/Makefile patching file src/esmumps/Makefile patching file src/scotch/Makefile Applying patch metis-header.patch patching file src/libscotchmetis/metis.h Now at patch metis-header.patch touch patch-stamp for v in int int32 int64 long; do \ (cd $v/lib ln -s libscotchmetis.a libmetis.a); \ (cd $v/lib ln -s libscotchmetis.so libmetis.so); \ (cd $v/lib ln -s libptscotchparmetis.a libparmetis.a); \ (cd $v/lib ln -s libptscotchparmetis.so libparmetis.so); \ done for file in acpl amk_ccc amk_fft2 amk_grf amk_hy amk_m2 amk_p2 atst gcv gmap gmk_hy gmk_m2 gmk_m3 gmk_msh gmk_ub2 gmtst gord gotst gout gpart gscat gtst mcv mmk_m2 mmk_m3 mord mtst scotch_gbase; do \ (cd int32/bin mv $file $file-int32); \ done for file in acpl amk_ccc amk_fft2 amk_grf amk_hy amk_m2 amk_p2 atst gcv gmap gmk_hy gmk_m2 gmk_m3 gmk_msh gmk_ub2 gmtst gord gotst gout gpart gscat gtst mcv mmk_m2 mmk_m3 mord mtst scotch_gbase; do \ (cd int64/bin mv $file $file-int64); \ done for file in acpl amk_ccc amk_fft2 amk_grf amk_hy amk_m2 amk_p2 atst gcv gmap gmk_hy gmk_m2 gmk_m3 gmk_msh gmk_ub2 gmtst gord gotst gout gpart gscat gtst mcv mmk_m2 mmk_m3 mord mtst scotch_gbase; do \ (cd long/bin mv $file $file-long); \ done cp -f debian/dgscat.1 int/share/man/man1 cp -f debian/gout.1 int/share/man/man1 perl -pi -e 's|\.\|\.\\\|' int/share/man/man1/*.1 mv int/share/man/man1/gbase.1 int/share/man/man1/scotch_gbase.1 cp debian/scotch_esmumps.1 int/share/man/man1 cp debian/ptscotch_esmumps.1 int/share/man/man1 for file in acpl amk_ccc amk_fft2 amk_grf amk_hy amk_m2 amk_p2 atst gcv gmap gmk_hy gmk_m2 gmk_m3 gmk_msh gmk_ub2 gmtst gord gotst gout gpart gscat gtst mcv mmk_m2 mmk_m3 mord mtst scotch_gbase; do \ (cd int/share/man/man1 gzip -9 $file.1); \ done gzip: gscat.1: No such file or directory for file in acpl amk_ccc amk_fft2 amk_grf amk_hy amk_m2 amk_p2 atst gcv gmap gmk_hy gmk_m2 gmk_m3 gmk_msh gmk_ub2 gmtst gord gotst gout gpart gscat gtst mcv mmk_m2 mmk_m3 mord mtst scotch_gbase; do \ (cd int/share/man/man1 ln -sf $file.1.gz $file-int32.1.gz); \ (cd int/share/man/man1 ln -sf $file.1.gz $file-int64.1.gz); \ (cd int/share/man/man1 ln -sf $file.1.gz $file-long.1.gz); \ done dh_testdir -a dh_testroot -a dh_installdirs -a dh_install -a cp: cannot stat `debian/tmp/int/bin/scotch_esmumps': No such file or directory dh_install: cp -a debian/tmp/int/bin/scotch_esmumps debian/scotch//usr/bin/ returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/scotch_5.1.12b.dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666296: scmxx: FTBFS: cp: cannot stat `debian/debian_provider_logo.bmp': No such file or directory
Source: scmxx Version: 0.9.0-2.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/docs' /usr/bin/install -c -d /«PKGBUILDDIR»/debian/scmxx//usr/share/man/de/man1; \ /usr/bin/install -c -m 644 scmxx.de.1 /«PKGBUILDDIR»/debian/scmxx//usr/share/man/de/man1/scmxx.1; \ /usr/bin/install -c -d /«PKGBUILDDIR»/debian/scmxx//usr/share/man/man1; \ /usr/bin/install -c -m 644 scmxx.en.1 /«PKGBUILDDIR»/debian/scmxx//usr/share/man/man1/scmxx.1; \ /usr/bin/install -c -d /«PKGBUILDDIR»/debian/scmxx//usr/share/man/it/man1; \ /usr/bin/install -c -m 644 scmxx.it.1 /«PKGBUILDDIR»/debian/scmxx//usr/share/man/it/man1/scmxx.1; \ /usr/bin/install -c -d /«PKGBUILDDIR»/debian/scmxx//usr/share/man/ru/man1; \ /usr/bin/install -c -m 644 scmxx.ru.1 /«PKGBUILDDIR»/debian/scmxx//usr/share/man/ru/man1/scmxx.1; \ make[2]: Leaving directory `/«PKGBUILDDIR»/docs' make[1]: Leaving directory `/«PKGBUILDDIR»' touch debian/stamp-makefile-install Adding cdbs dependencies to debian/scmxx.substvars dh_installdirs -pscmxx dh_installdirs: Compatibility levels before 5 are deprecated (level 4 in use) dh_installdocs -pscmxx ./README ./TODO ./BUGS ./AUTHORS dh_installdocs: Compatibility levels before 5 are deprecated (level 4 in use) dh_installexamples -pscmxx dh_installexamples: Compatibility levels before 5 are deprecated (level 4 in use) cp: cannot stat `debian/debian_provider_logo.bmp': No such file or directory dh_installexamples: cp -a debian/debian_provider_logo.bmp debian/scmxx/usr/share/doc/scmxx/examples returned exit code 1 make: *** [binary-install/scmxx] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/scmxx_0.9.0-2.2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666297: openexr: FTBFS: configure:1559: error: cannot run /bin/bash ./config.sub
Source: openexr
Version: 1.6.1-4.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a newer dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
make[1]: Entering directory `/«PKGBUILDDIR»'
dh_auto_configure -- --with-openexr-prefix=/usr
configure: error: cannot run /bin/bash ./config.sub
== config.log ==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by OpenEXR configure 1.6.1, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./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/openexr --disable-maintainer-mode
--disable-dependency-tracking --with-openexr-prefix=/usr
## - ##
## Platform. ##
## - ##
hostname = ip-10-248-229-98
uname -m = x86_64
uname -r = 2.6.32-5-xen-amd64
uname -s = Linux
uname -v = #1 SMP Mon Jan 16 20:48:30 UTC 2012
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
## --- ##
## Core tests. ##
## --- ##
configure:1559: error: cannot run /bin/bash ./config.sub
## ##
## Cache variables. ##
## ##
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_PKG_CONFIG_set=
ac_cv_env_PKG_CONFIG_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-linux-gnu
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
## - ##
## Output variables. ##
## - ##
ACLOCAL=''
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR=''
AM_CFLAGS=''
AM_CXXFLAGS=''
AR=''
AUTOCONF=''
AUTOHEADER=''
AUTOMAKE=''
AWK=''
BUILD_IMFEXAMPLES_FALSE=''
BUILD_IMFEXAMPLES_TRUE=''
BUILD_IMFFUZZTEST_FALSE=''
BUILD_IMFFUZZTEST_TRUE=''
CC=''
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W=''
DEFS=''
DEPDIR=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77=''
FFLAGS=''
ILMBASE_CXXFLAGS=''
ILMBASE_LDFLAGS=''
ILMBASE_LIBS=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
INSTALL_STRIP_PROGRAM=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIBTOOL_VERSION=''
LN_S=''
LTLIBOBJS=''
MAINT=''
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE=''
MAKEINFO=''
OBJEXT=''
OPENEXR_VERSION='1.6.1'
PACKAGE=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME='OpenEXR'
PACKAGE_STRING='OpenEXR 1.6.1'
PACKAGE_TARNAME='openexr'
PACKAGE_VERSION='1.6.1'
PATH_SEPARATOR=':'
PKG_CONFIG=''
PTHREAD_CC=''
PTHREAD_CFLAGS=''
PTHREAD_LIBS=''
RANLIB=''
SET_MAKE=''
SHELL='/bin/bash'
STRIP=''
VERSION=''
ac_ct_AR=''
ac_ct_CC=''
ac_ct_CXX=''
ac_ct_F77=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
acx_pthread_config=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__leading_dot=''
am__quote=''
am__tar=''
am__untar=''
bindir='${exec_prefix}/bin'
build='x86_64-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='${prefix}/share'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh=''
libdir='${exec_prefix}/lib'
libexecdir='${prefix}/lib/openexr'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p=''
oldincludedir='/usr/include'
prefix='/usr'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
#define
Bug#666298: qmk-groundstation: FTBFS: cp: cannot stat `debian/tmp/Images/QMK-Groundstation.xpm': No such file or directory
Source: qmk-groundstation Version: 1.0.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: Nothing to be done for `install'. make[1]: Leaving directory `/«PKGBUILDDIR»' touch debian/stamp-makefile-install Adding cdbs dependencies to debian/qmk-groundstation.substvars dh_installdirs -pqmk-groundstation dh_installdocs -pqmk-groundstation dh_installexamples -pqmk-groundstation dh_installman -pqmk-groundstation dh_installinfo -pqmk-groundstation dh_installmenu -pqmk-groundstation dh_installcron -pqmk-groundstation dh_installinit -pqmk-groundstation dh_installdebconf -pqmk-groundstation dh_installemacsen -pqmk-groundstation dh_installcatalogs -pqmk-groundstation dh_installpam -pqmk-groundstation dh_installlogrotate -pqmk-groundstation dh_installlogcheck -pqmk-groundstation dh_installchangelogs -pqmk-groundstation dh_installudev -pqmk-groundstation dh_lintian -pqmk-groundstation dh_bugfiles -pqmk-groundstation dh_install -pqmk-groundstation cp: cannot stat `debian/tmp/Images/QMK-Groundstation.xpm': No such file or directory dh_install: cp -a debian/tmp/Images/QMK-Groundstation.xpm debian/qmk-groundstation/usr/share/pixmaps// returned exit code 1 make: *** [binary-install/qmk-groundstation] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/qmk-groundstation_1.0.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666299: loadlin: FTBFS: cp: cannot stat `initrd.tgz': No such file or directory
Source: loadlin Version: 1.6e-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_clean -k dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p . Adding cdbs dependencies to debian/loadlin.substvars dh_installdirs -ploadlin dh_installdocs -ploadlin dh_installexamples -ploadlin cp: cannot stat `initrd.tgz': No such file or directory dh_installexamples: cp -a initrd.tgz debian/loadlin/usr/share/doc/loadlin/examples returned exit code 1 make: *** [binary-install/loadlin] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/loadlin_1.6e-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666300: mendexk: FTBFS: kp.c:(.text+0xa): undefined reference to `kpse_set_progname'
Source: mendexk Version: 2.6e-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: cc main.o convert.o sort.o fread.o fwrite.o styfile.o pageread.o kp.o -o mendex /usr/lib/libkpathsea.a kp.o: In function `KP_init': kp.c:(.text+0xa): undefined reference to `kpse_set_progname' collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/mendexk_2.6e-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666302: gurlchecker: FTBFS: cp: cannot stat `debian/tmp/ui/gurlchecker.xpm': No such file or directory
Source: gurlchecker Version: 0.13.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[4]: Entering directory `/«PKGBUILDDIR»' make[4]: Nothing to be done for `install-exec-am'. test -z /usr/share/applications || /bin/mkdir -p /«PKGBUILDDIR»/debian/gurlchecker/usr/share/applications /usr/bin/install -c -m 644 gurlchecker.desktop '/«PKGBUILDDIR»/debian/gurlchecker/usr/share/applications' test -z /usr/share/doc/gurlchecker || /bin/mkdir -p /«PKGBUILDDIR»/debian/gurlchecker/usr/share/doc/gurlchecker test -z /usr/share/man/man1 || /bin/mkdir -p /«PKGBUILDDIR»/debian/gurlchecker/usr/share/man/man1 /usr/bin/install -c -m 644 gurlchecker.1 '/«PKGBUILDDIR»/debian/gurlchecker/usr/share/man/man1' make[4]: Leaving directory `/«PKGBUILDDIR»' make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' dh_install -a -O--parallel cp: cannot stat `debian/tmp/ui/gurlchecker.xpm': No such file or directory dh_install: cp -a debian/tmp/ui/gurlchecker.xpm debian/gurlchecker/usr/share/pixmaps// returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/gurlchecker_0.13.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666303: darnwdl: FTBFS: sh: 1: rsvg: not found
Source: darnwdl Version: 0.5-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' xsltproc -''-nonet -''-param man.charmap.use.subset 0 /usr/share/sgml/docbook/stylesheet/xsl/docbook-xsl/manpages/docbook.xsl debian/darnwdl.xml I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd debian/darnwdl.xml:62: warning: failed to load external entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; ] ^ Note: Writing darnwdl.1 convert -background transparent pixmaps/darnwdlicon.svg darnwdlicon.xpm sh: 1: rsvg: not found convert: delegate failed `rsvg %i %o' @ error/delegate.c/InvokeDelegate/1058. convert: unable to open image `/tmp/magick-Jl7JZZQw': @ error/blob.c/OpenBlob/2587. convert: unable to open file `/tmp/magick-Jl7JZZQw': @ error/constitute.c/ReadImage/571. convert: missing an image filename `darnwdlicon.xpm' @ error/convert.c/ConvertImageCommand/3011. make[1]: *** [darnwdlicon.xpm] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/darnwdl_0.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666304: ruby-mecab: FTBFS: MeCab_wrap.cpp:2085:16: error: 'mecab_node_t' has no member named 'sentence_length'
Source: ruby-mecab
Version: 0.98-5
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a newer dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
g++ -I. -I. -I/usr/lib/ruby/1.8/x86_64-linux -I. -DHAVE_MECAB_H-fPIC
-fno-strict-aliasing -g -g -O2 -fPIC -c MeCab_wrap.cpp
MeCab_wrap.cpp: In function 'const mecab_node_t*
mecab_node_t_begin_node_list(mecab_node_t*, size_t)':
MeCab_wrap.cpp:2085:16: error: 'mecab_node_t' has no member named
'sentence_length'
MeCab_wrap.cpp:2087:17: error: 'mecab_node_t' has no member named
'begin_node_list'
MeCab_wrap.cpp:2088:19: error: 'mecab_node_t' has no member named
'begin_node_list'
MeCab_wrap.cpp: In function 'const mecab_node_t*
mecab_node_t_end_node_list(mecab_node_t*, size_t)':
MeCab_wrap.cpp:2093:16: error: 'mecab_node_t' has no member named
'sentence_length'
MeCab_wrap.cpp:2095:17: error: 'mecab_node_t' has no member named
'end_node_list'
MeCab_wrap.cpp:2096:19: error: 'mecab_node_t' has no member named
'end_node_list'
MeCab_wrap.cpp: In function 'VALUE _wrap_Token_lcAttr_get(int, VALUE*,
VALUE)':
MeCab_wrap.cpp:2643:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cpp:2643:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cpp:2643:41: error: expected primary-expression before ')' token
MeCab_wrap.cpp:2643:43: error: expected ';' before numeric constant
MeCab_wrap.cpp:2656:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cpp:2656:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cpp:2656:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cpp:2656:44: error: expected primary-expression before '' token
MeCab_wrap.cpp:2656:52: error: expected ')' before ';' token
MeCab_wrap.cpp: In function 'VALUE _wrap_Token_rcAttr_get(int, VALUE*,
VALUE)':
MeCab_wrap.cpp:2667:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cpp:2667:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cpp:2667:41: error: expected primary-expression before ')' token
MeCab_wrap.cpp:2667:43: error: expected ';' before numeric constant
MeCab_wrap.cpp:2680:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cpp:2680:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cpp:2680:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cpp:2680:44: error: expected primary-expression before '' token
MeCab_wrap.cpp:2680:52: error: expected ')' before ';' token
MeCab_wrap.cpp: In function 'VALUE _wrap_Token_posid_get(int, VALUE*, VALUE)':
MeCab_wrap.cpp:2691:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cpp:2691:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cpp:2691:41: error: expected primary-expression before ')' token
MeCab_wrap.cpp:2691:43: error: expected ';' before numeric constant
MeCab_wrap.cpp:2704:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cpp:2704:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cpp:2704:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cpp:2704:44: error: expected primary-expression before '' token
MeCab_wrap.cpp:2704:52: error: expected ')' before ';' token
MeCab_wrap.cpp: In function 'VALUE _wrap_Token_wcost_get(int, VALUE*, VALUE)':
MeCab_wrap.cpp:2715:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cpp:2715:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cpp:2715:41: error: expected primary-expression before ')' token
MeCab_wrap.cpp:2715:43: error: expected ';' before numeric constant
MeCab_wrap.cpp:2728:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cpp:2728:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cpp:2728:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cpp:2728:44: error: expected primary-expression before '' token
MeCab_wrap.cpp:2728:52: error: expected ')' before ';' token
MeCab_wrap.cpp: In function 'VALUE _wrap_Token_feature_get(int, VALUE*,
VALUE)':
MeCab_wrap.cpp:2739:3: error: 'mecab_token_t' was not declared in this scope
/usr/lib/ruby/vendor_ruby/1.8/rubygems/ext/builder.rb:37:in `make': make
failed: (Gem::InstallError)
/usr/bin/ruby1.8 extconf.rbchecking for main() in -lmecab... yes
checking for main() in -lstdc++... yes
checking for mecab.h... yes
creating Makefile
makemake[1]: Entering directory `/«PKGBUILDDIR»'
g++ -I. -I. -I/usr/lib/ruby/1.8/x86_64-linux -I. -DHAVE_MECAB_H-fPIC
-fno-strict-aliasing -g -g -O2 -fPIC -c MeCab_wrap.cpp
MeCab_wrap.cpp: In function 'const mecab_node_t
Bug#666305: python-mecab: FTBFS: MeCab_wrap.cxx:3079:16: error: 'mecab_node_t' has no member named 'sentence_length'
Source: python-mecab
Version: 0.98-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a newer dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC -I/usr/include -I/usr/include/python2.6 -c
MeCab_wrap.cxx -o build/temp.linux-x86_64-2.6/MeCab_wrap.o
cc1plus: warning: command line option '-Wstrict-prototypes' is valid for
Ada/C/ObjC but not for C++ [enabled by default]
MeCab_wrap.cxx: In function 'const mecab_node_t*
mecab_node_t_begin_node_list(mecab_node_t*, size_t)':
MeCab_wrap.cxx:3079:16: error: 'mecab_node_t' has no member named
'sentence_length'
MeCab_wrap.cxx:3081:17: error: 'mecab_node_t' has no member named
'begin_node_list'
MeCab_wrap.cxx:3082:19: error: 'mecab_node_t' has no member named
'begin_node_list'
MeCab_wrap.cxx: In function 'const mecab_node_t*
mecab_node_t_end_node_list(mecab_node_t*, size_t)':
MeCab_wrap.cxx:3087:16: error: 'mecab_node_t' has no member named
'sentence_length'
MeCab_wrap.cxx:3089:17: error: 'mecab_node_t' has no member named
'end_node_list'
MeCab_wrap.cxx:3090:19: error: 'mecab_node_t' has no member named
'end_node_list'
MeCab_wrap.cxx: In function 'PyObject* _wrap_Token_lcAttr_get(PyObject*,
PyObject*)':
MeCab_wrap.cxx:3668:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:3668:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:3668:41: error: expected primary-expression before ')' token
MeCab_wrap.cxx:3668:43: error: expected ';' before numeric constant
MeCab_wrap.cxx:3679:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:3679:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:3679:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:3679:44: error: expected primary-expression before '' token
MeCab_wrap.cxx:3679:52: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'PyObject* _wrap_Token_rcAttr_get(PyObject*,
PyObject*)':
MeCab_wrap.cxx:3690:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:3690:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:3690:41: error: expected primary-expression before ')' token
MeCab_wrap.cxx:3690:43: error: expected ';' before numeric constant
MeCab_wrap.cxx:3701:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:3701:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:3701:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:3701:44: error: expected primary-expression before '' token
MeCab_wrap.cxx:3701:52: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'PyObject* _wrap_Token_posid_get(PyObject*,
PyObject*)':
MeCab_wrap.cxx:3712:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:3712:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:3712:41: error: expected primary-expression before ')' token
MeCab_wrap.cxx:3712:43: error: expected ';' before numeric constant
MeCab_wrap.cxx:3723:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:3723:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:3723:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:3723:44: error: expected primary-expression before '' token
MeCab_wrap.cxx:3723:52: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'PyObject* _wrap_Token_wcost_get(PyObject*,
PyObject*)':
MeCab_wrap.cxx:3734:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:3734:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:3734:41: error: expected primary-expression before ')' token
MeCab_wrap.cxx:3734:43: error: expected ';' before numeric constant
MeCab_wrap.cxx:3745:28: error: expected type-specifier before 'mecab_token_t'
MeCab_wrap.cxx:3745:28: error: expected '' before 'mecab_token_t'
MeCab_wrap.cxx:3745:28: error: expected '(' before 'mecab_token_t'
MeCab_wrap.cxx:3745:44: error: expected primary-expression before '' token
MeCab_wrap.cxx:3745:52: error: expected ')' before ';' token
MeCab_wrap.cxx: In function 'PyObject* _wrap_Token_feature_get(PyObject*,
PyObject*)':
MeCab_wrap.cxx:3756:3: error: 'mecab_token_t' was not declared in this scope
MeCab_wrap.cxx:3756:18: error: 'arg1' was not declared in this scope
MeCab_wrap.cxx:3756:41: error: expected primary-expression before ')' token
MeCab_wrap.cxx:3756:43: error: expected ';' before numeric constant
MeCab_wrap.cxx:3767:28: error: expected type-specifier before 'mecab_token_t
Bug#666306: canna: FTBFS: /bin/sh: 1: platex: not found
Source: canna Version: 3.7p3-8 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/doc/man/guide/tex' (echo s%@(cannaBinDir)%/usr//bin%g; \ echo s%@(cannaLibDir)%/etc/canna%g; \ echo s%@(cannaIncDir)%/usr//include/canna%g; \ echo s%@(UnixSockDir)%/tmp/.iroha_unix%g; \ echo s%@(UnixSockName)%IROHA%g; \ echo s%@(AccessFile)%/etc/hosts.canna%g; \ echo s%@(DicDir)%/var/lib/canna/dic%g; \ echo s%@(ErrDir)%/var/log/canna%g) ../../../../misc/manual.sed sed -f ../../../../misc/manual.sed canna-dist.tex canna.tex gcc -g -O2 -fno-strict-aliasing-I../../../../include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DFUNCPROTO=15 -DNARROWPROTO -c -o cannaindex.o cannaindex.c rm -f cannaindex gcc -o cannaindex -g -O2 -fno-strict-aliasing cannaindex.o echo 'DUMMY' candex.tex platex canna.tex /bin/sh: 1: platex: not found make[2]: *** [canna.dvi] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/canna_3.7p3-8_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666307: htp: FTBFS: snprintf.c:856:2: error: incompatible types when assigning to type 'va_list' from type 'struct __va_list_tag *'
Source: htp Version: 1.16-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: gcc -c -Wall -O2 -DHAVE_SNPRINTF -DHAVE_PIPE -DHAVE_STPCPY -D_GNU_SOURCE=1 -o snprintf.o snprintf.c snprintf.c: In function 'vasprintf': snprintf.c:856:2: error: incompatible types when assigning to type 'va_list' from type 'struct __va_list_tag *' snprintf.c:864:2: error: incompatible types when assigning to type 'va_list' from type 'struct __va_list_tag *' make[2]: *** [snprintf.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/htp_1.16-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666308: qpdf: FTBFS: libqpdf/PCRE.cc:147:46: error: 'pcre_info' was not declared in this scope
Source: qpdf Version: 2.3.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: /bin/sh ./libtool --quiet --mode=compile g++ -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -Wall -MD -MF libqpdf/build/PCRE.tdep -MP -Iinclude -Ilibqpdf -c libqpdf/PCRE.cc -o libqpdf/build/PCRE.o; sed -e 's/\.o:/.lo:/' libqpdf/build/PCRE.tdep libqpdf/build/PCRE.dep libqpdf/PCRE.cc: In constructor 'PCRE::PCRE(const char*, int)': libqpdf/PCRE.cc:147:46: error: 'pcre_info' was not declared in this scope /bin/sh: 1: cannot open libqpdf/build/PCRE.tdep: No such file make[1]: *** [libqpdf/build/PCRE.lo] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/qpdf_2.3.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663673: marked as done (libalog0.4.1-{full,base}-dev: static library contains position-independent code)
Your message dated Fri, 30 Mar 2012 09:25:01 +
with message-id e1sdy4r-0006gq...@franck.debian.org
and subject line Bug#663673: fixed in libalog 0.4.1-2
has caused the Debian Bug report #663673,
regarding libalog0.4.1-{full,base}-dev: static library contains
position-independent code
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.)
--
663673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libalog0.4.1-full-dev
Version: 0.4.1-1
Severity: serious
Violation of Debian Policy 10.2: the static version [of a library]
must not
be compiled with the -fPIC flag.
Please rearrange debian/rules and the .gpr files so that they recompile
the
object files in two different object directories: -fPIC for the shared
library
and no -fPIC for the static library. You may want to look at other
packages
for inspiration on how to do this.
This bug also applies to package libalog0.4.1-base-dev, built from the
same
package.
--
Ludovic Brenta.
---End Message---
---BeginMessage---
Source: libalog
Source-Version: 0.4.1-2
We believe that the bug you reported is fixed in the latest version of
libalog, which is due to be installed in the Debian FTP archive:
libalog0.4.1-base-dbg_0.4.1-2_amd64.deb
to main/liba/libalog/libalog0.4.1-base-dbg_0.4.1-2_amd64.deb
libalog0.4.1-base-dev_0.4.1-2_amd64.deb
to main/liba/libalog/libalog0.4.1-base-dev_0.4.1-2_amd64.deb
libalog0.4.1-base_0.4.1-2_amd64.deb
to main/liba/libalog/libalog0.4.1-base_0.4.1-2_amd64.deb
libalog0.4.1-full-dbg_0.4.1-2_amd64.deb
to main/liba/libalog/libalog0.4.1-full-dbg_0.4.1-2_amd64.deb
libalog0.4.1-full-dev_0.4.1-2_amd64.deb
to main/liba/libalog/libalog0.4.1-full-dev_0.4.1-2_amd64.deb
libalog0.4.1-full_0.4.1-2_amd64.deb
to main/liba/libalog/libalog0.4.1-full_0.4.1-2_amd64.deb
libalog_0.4.1-2.debian.tar.gz
to main/liba/libalog/libalog_0.4.1-2.debian.tar.gz
libalog_0.4.1-2.dsc
to main/liba/libalog/libalog_0.4.1-2.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 663...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Reto Buerki r...@codelabs.ch (supplier of updated libalog 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, 30 Mar 2012 09:43:30 +0200
Source: libalog
Binary: libalog0.4.1-base libalog0.4.1-full libalog0.4.1-base-dev
libalog0.4.1-full-dev libalog0.4.1-base-dbg libalog0.4.1-full-dbg
Architecture: source amd64
Version: 0.4.1-2
Distribution: unstable
Urgency: low
Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch
Changed-By: Reto Buerki r...@codelabs.ch
Description:
libalog0.4.1-base - Logging framework for Ada (base)
libalog0.4.1-base-dbg - Logging framework for Ada (debug)
libalog0.4.1-base-dev - Logging framework for Ada (development)
libalog0.4.1-full - Logging framework for Ada (full)
libalog0.4.1-full-dbg - Logging framework for Ada (debug)
libalog0.4.1-full-dev - Logging framework for Ada (development)
Closes: 663673
Changes:
libalog (0.4.1-2) unstable; urgency=low
.
* Add project specific git-buildpackage configuration
* Build dynamic/static libs in separate Obj/Lib dirs (Closes: #663673)
* Disable tracebacks in Exception occurrences.
See Debian bug #666106; tracebacks are only disabled on kfreebsd-i386.
Quilt's guards tool is used to apply this architecture specific patch.
Checksums-Sha1:
69f1f9a9072e5c3ffd68bb563ddb5d4d342001e2 2300 libalog_0.4.1-2.dsc
1ac60408fab1631e482cf9aae65c19e7b9256c67 6265 libalog_0.4.1-2.debian.tar.gz
df4e44d1fab3268db2c9459229db2dbf6cee587c 115700
libalog0.4.1-base_0.4.1-2_amd64.deb
04c1c9e21978fb5df9476fc2193798e3c41d8d86 135790
libalog0.4.1-full_0.4.1-2_amd64.deb
9a4f2eaf48a1b2853f3aed684cf61dcf35a64547 332726
libalog0.4.1-base-dev_0.4.1-2_amd64.deb
9aac6d7ef77c72e3be129741733509adc81372e9 366096
libalog0.4.1-full-dev_0.4.1-2_amd64.deb
4df34d019889ae93af4be69c95aa8f02a6af2083 160238
libalog0.4.1-base-dbg_0.4.1-2_amd64.deb
7c086a5ba6801e4f95db552a119d0a3f6c63c762 191996
libalog0.4.1-full-dbg_0.4.1-2_amd64.deb
Checksums-Sha256:
a3f52ef789721d5814d14d926cfe218413bf5b2d0b09f554ee3e3ae4564861ae 2300
libalog_0.4.1-2.dsc
Bug#666309: service-wrapper-java: FTBFS: cp: cannot stat `./lib/daemon.sh': No such file or directory
Source: service-wrapper-java Version: 3.5.3-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch # Create the package here dh_testdir dh_testroot dh_prep -k dh_install -a cp: cannot stat `./lib/daemon.sh': No such file or directory dh_install: cp -a ./lib/daemon.sh debian/service-wrapper/usr/share/wrapper// returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/service-wrapper-java_3.5.3-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666310: dsdp: FTBFS: cp: cannot stat `./bin/dsdp5': No such file or directory
Source: dsdp Version: 5.8-9 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_clean -k dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p . Adding cdbs dependencies to debian/dsdp.substvars dh_installdirs -pdsdp Adding cdbs dependencies to debian/libdsdp-dev.substvars dh_installdirs -plibdsdp-dev Adding cdbs dependencies to debian/libdsdp-5.8gf.substvars dh_installdirs -plibdsdp-5.8gf dh_installdocs -pdsdp dh_installexamples -pdsdp dh_installman -pdsdp dh_installinfo -pdsdp dh_installmenu -pdsdp dh_installcron -pdsdp dh_installinit -pdsdp dh_installdebconf -pdsdp dh_installemacsen -pdsdp dh_installcatalogs -pdsdp dh_installpam -pdsdp dh_installlogrotate -pdsdp dh_installlogcheck -pdsdp dh_installchangelogs -pdsdp dh_installudev -pdsdp dh_lintian -pdsdp dh_bugfiles -pdsdp dh_install -pdsdp cp: cannot stat `./bin/dsdp5': No such file or directory dh_install: cp -a ./bin/dsdp5 debian/dsdp/usr/bin/ returned exit code 1 make: *** [binary-install/dsdp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/dsdp_5.8-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666311: freeradius: FTBFS: libfreeradius-radius-2.1.10.so: could not read symbols: Invalid operation
Source: freeradius Version: 2.1.10+dfsg-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: /usr/bin/ld: note: 'fr_perror' is defined in DSO /«BUILDDIR»/freeradius-2.1.10+dfsg/src/lib/.libs/libfreeradius-radius-2.1.10.so so try adding it to the linker command line /«BUILDDIR»/freeradius-2.1.10+dfsg/src/lib/.libs/libfreeradius-radius-2.1.10.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/freeradius_2.1.10+dfsg-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666312: unison: FTBFS: make: rsvg: Command not found
Source: unison Version: 2.40.63-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»' if [ -f `which etags` ]; then \ etags *.mli */*.mli *.ml */*.ml */*.m *.c */*.c *.txt \ ; fi /bin/sh: 2: etags: not found make[2]: [tags] Error 127 (ignored) make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' mv '/«PKGBUILDDIR»/unison' '/«PKGBUILDDIR»/unison-2.40.63' rsvg -f png -w 32 -h 32 debian/unison-gtk.svg.in debian/unison-gtk.png make: rsvg: Command not found make: *** [debian/unison-gtk.png] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/unison_2.40.63-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666313: etherpuppet: FTBFS: cp: cannot stat `./etherpuppet': No such file or directory
Source: etherpuppet Version: 0.3-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_clean -k dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p . Adding cdbs dependencies to debian/etherpuppet.substvars dh_installdirs -petherpuppet dh_installdocs -petherpuppet dh_installexamples -petherpuppet dh_installman -petherpuppet debian/etherpuppet.1 dh_installinfo -petherpuppet dh_installmenu -petherpuppet dh_installcron -petherpuppet dh_installinit -petherpuppet dh_installdebconf -petherpuppet dh_installemacsen -petherpuppet dh_installcatalogs -petherpuppet dh_installpam -petherpuppet dh_installlogrotate -petherpuppet dh_installlogcheck -petherpuppet dh_installchangelogs -petherpuppet dh_installudev -petherpuppet dh_lintian -petherpuppet dh_bugfiles -petherpuppet dh_install -petherpuppet cp: cannot stat `./etherpuppet': No such file or directory dh_install: cp -a ./etherpuppet debian/etherpuppet/usr/bin/ returned exit code 1 make: *** [binary-install/etherpuppet] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/etherpuppet_0.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666314: unison2.27.57: FTBFS: make: rsvg: Command not found
Source: unison2.27.57 Version: 2.27.57-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»' etags *.mli */*.mli *.ml */*.ml */*.m *.c */*.c *.txt /bin/sh: 1: etags: not found make[2]: [tags] Error 127 (ignored) make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' mv '/«PKGBUILDDIR»/unison' '/«PKGBUILDDIR»/unison-2.27.57' rsvg -f png -w 32 -h 32 debian/unison-gtk.svg.in debian/unison2.27.57-gtk.png make: rsvg: Command not found make: *** [debian/unison2.27.57-gtk.png] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/unison2.27.57_2.27.57-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666315: nwchem: FTBFS: cp: cannot stat `debian/tmp/doc/user/userpdf.pdf': No such file or directory
Source: nwchem Version: 6.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch dh binary-arch dh_testroot -a dh_prep -a dh_installdirs -a dh_auto_install -a dh_install -a cp: cannot stat `debian/tmp/doc/user/userpdf.pdf': No such file or directory dh_install: cp -a debian/tmp/doc/user/userpdf.pdf debian/nwchem/usr/share/doc/nwchem/ returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/nwchem_6.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666316: vdr-plugin-epgsearch: FTBFS: conflictcheck.h:262:32: error: 'class cSetup' has no member named 'PrimaryLimit'
Source: vdr-plugin-epgsearch Version: 1.0.0-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: g++ -g -Wall -Woverloaded-virtual -Wno-parentheses -O2 -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DSENDMAIL='/usr/sbin/sendmail' -DPLUGIN_NAME_I18N='epgsearch' -I/usr/include/dvb-s2api-liplianin -I/usr/include/vdr/include -I../../../../DVB/include conflictcheck.c In file included from conflictcheck.c:26:0: conflictcheck.h: In member function 'bool cConflictCheckDevice::ProvidesChannel(const cChannel*, int, bool*) const': conflictcheck.h:262:32: error: 'class cSetup' has no member named 'PrimaryLimit' conflictcheck.h:267:57: error: 'class cSetup' has no member named 'PrimaryLimit' make[2]: *** [conflictcheck.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/vdr-plugin-epgsearch_1.0.0-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666317: m-tx: FTBFS: ! LaTeX Error: File `a4wide.sty' not found.
Source: m-tx
Version: 0.60d-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a recent dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
make[2]: Entering directory `/«PKGBUILDDIR»/doc'
./prepmx mozart0
== This is M-Tx 0.60d (Music from TeXt) 11 October 2008
== Input from file mozart0.mtx
Writing to mozart0.pmx
No STYLE supplied: WARNING in preamble
I guess this piece is a Duet for strings in C major.
Why not provide a STYLE in the setup paragraph to make sure?
You have not defined Meter, assuming C : WARNING in preamble
PrePMX done. Now run PMX.
# the next two (2!) lines work around a bug in m-tx
sed -e s/a4 a4 { \[h d8 { u d8+ \] \//a4 a4 { \[h d8 {u d8+ \] \//
mozart0.pmx mozart0.pmx.tmp
mv mozart0.pmx.tmp mozart0.pmx
pmxab mozart0
This is PMX, Version 2618 , 19 Mar 12
Opening mozart0.pmx
Starting first PMX pass
Bar 1 Bar 2
WARNING:
Last non-blank character is , not /,%
ASCII code: 0
appending blank/
Done with first pass
Removing last line of blankblank/
Starting second PMX pass
Bar 1 Bar 2
Writing ./mozart0.tex
Done with second PMX pass.
rm mozart0.pml mozart0.pmx pmxaerr.dat
./prepmx mozart
== This is M-Tx 0.60d (Music from TeXt) 11 October 2008
== Input from file mozart.mtx
Writing to mozart.pmx
You have not defined Meter, assuming C : WARNING in preamble
PrePMX done. Now run PMX.
# the next two (2!) lines work around a bug in m-tx
sed -e s/a4 a4 { \[h d8 { u d8+ \] \//a4 a4 { \[h d8 {u d8+ \] \//
mozart.pmx mozart.pmx.tmp
mv mozart.pmx.tmp mozart.pmx
pmxab mozart
This is PMX, Version 2618 , 19 Mar 12
Opening mozart.pmx
Starting first PMX pass
Bar 1 Bar 2
WARNING:
Last non-blank character is , not /,%
ASCII code: 0
appending blank/
Done with first pass
Removing last line of blankblank/
Starting second PMX pass
Bar 1 Bar 2
Writing ./mozart.tex
Done with second PMX pass.
rm mozart.pml mozart.pmx pmxaerr.dat
./prepmx netfirst
== This is M-Tx 0.60d (Music from TeXt) 11 October 2008
== Input from file netfirst.mtx
Writing to netfirst.pmx
PrePMX done. Now run PMX.
# the next two (2!) lines work around a bug in m-tx
sed -e s/a4 a4 { \[h d8 { u d8+ \] \//a4 a4 { \[h d8 {u d8+ \] \//
netfirst.pmx netfirst.pmx.tmp
mv netfirst.pmx.tmp netfirst.pmx
pmxab netfirst
This is PMX, Version 2618 , 19 Mar 12
Opening netfirst.pmx
Starting first PMX pass
Bar 1 Bar 2 Bar 3 Bar 4 Bar 5 Bar 6 Bar 7 Bar 8
Done with first pass
Starting second PMX pass
Bar 1 Bar 2 Bar 3 Bar 4 Bar 5 Bar 6 Bar 7 Bar 8
Writing ./netfirst.tex
Done with second PMX pass.
rm netfirst.pml netfirst.pmx pmxaerr.dat
./prepmx meter
== This is M-Tx 0.60d (Music from TeXt) 11 October 2008
== Input from file meter.mtx
Writing to meter.pmx
PrePMX done. Now run PMX.
# the next two (2!) lines work around a bug in m-tx
sed -e s/a4 a4 { \[h d8 { u d8+ \] \//a4 a4 { \[h d8 {u d8+ \] \//
meter.pmx meter.pmx.tmp
mv meter.pmx.tmp meter.pmx
pmxab meter
This is PMX, Version 2618 , 19 Mar 12
Opening meter.pmx
Starting first PMX pass
Bar 1 Bar 2 Bar 3
Done with first pass
Starting second PMX pass
Bar 1 Bar 2 Bar 3
Writing ./meter.tex
Done with second PMX pass.
rm meter.pml meter.pmx pmxaerr.dat
./prepmx dertod
== This is M-Tx 0.60d (Music from TeXt) 11 October 2008
== Input from file dertod.mtx
Writing to dertod.pmx
PrePMX done. Now run PMX.
# the next two (2!) lines work around a bug in m-tx
sed -e s/a4 a4 { \[h d8 { u d8+ \] \//a4 a4 { \[h d8 {u d8+ \] \//
dertod.pmx dertod.pmx.tmp
mv dertod.pmx.tmp dertod.pmx
pmxab dertod
This is PMX, Version 2618 , 19 Mar 12
Opening dertod.pmx
Starting first PMX pass
Bar 1 Bar 2 Bar 3 Bar 4 Bar 5 Bar 6 Bar 7
WARNING:
Last non-blank character is , not /,%
ASCII code: 0
appending blank/
Done with first pass
Removing last line of blankblank/
Starting second PMX pass
Bar 1 Bar 2 Bar 3 Bar 4 Bar 5 Bar 6 Bar 7
Writing ./dertod.tex
Done with second PMX pass.
rm dertod.pml dertod.pmx pmxaerr.dat
./prepmx volta
== This is M-Tx 0.60d (Music from TeXt) 11 October 2008
== Input from file volta.mtx
Writing to volta.pmx
PrePMX done. Now run PMX.
# the next two (2!) lines work around a bug in m-tx
sed -e s/a4 a4
Bug#666318: imlib2: FTBFS: ld: cannot find -lICE
Source: imlib2 Version: 1.4.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [enabled by default] configure:9833: $? = 0 configure:9846: result: no configure:9866: checking for gcc option to produce PIC configure:10138: result: -fPIC -DPIC configure:10150: checking if gcc PIC flag -fPIC -DPIC works configure:10168: gcc -c -g -O2 -fPIC -DPIC -DPIC conftest.c 5 configure:10172: $? = 0 configure:10185: result: yes configure:10209: checking if gcc static flag -static works configure:10237: result: yes configure:10252: checking if gcc supports -c -o file.o configure:10273: gcc -c -g -O2 -o out/conftest2.o conftest.c 5 configure:10277: $? = 0 configure:10299: result: yes configure:10307: checking if gcc supports -c -o file.o configure:10354: result: yes configure:10387: checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries configure:11461: result: yes configure:11498: checking whether -lc should be explicitly linked in configure:11503: gcc -c -g -O2 conftest.c 5 configure:11506: $? = 0 configure:11521: gcc -shared conftest.o -v -Wl,-soname -Wl,conftest -o conftest 2\\1 \| /bin/grep -lc \/dev/null 2\\1 configure:11524: $? = 0 configure:11536: result: no configure:11700: checking dynamic linker characteristics configure:12143: gcc -o conftest -g -O2 -Wl,-rpath -Wl,/foo conftest.c 5 configure:12150: $? = 0 configure:12386: result: GNU/Linux ld.so configure:12488: checking how to hardcode library paths into programs configure:12513: result: immediate configure:13346: checking whether stripping libraries is possible configure:13351: result: yes configure:13386: checking if libtool supports shared libraries configure:13388: result: yes configure:13391: checking whether to build shared libraries configure:13412: result: yes configure:13415: checking whether to build static libraries configure:13419: result: yes configure:13461: checking whether gcc accepts -std=gnu99 configure:13487: gcc -c -g -O2 -std=gnu99 conftest.c 5 configure:13494: $? = 0 configure:13508: result: yes configure:13554: checking whether to enable x86 mmx support configure:13563: result: no configure:13574: checking whether to enable amd64 asm support configure:13583: result: yes configure:13604: checking for freetype-config configure:13622: found /usr/bin/freetype-config configure:13635: result: /usr/bin/freetype-config configure:13651: checking for X configure:13766: gcc -E -std=gnu99 conftest.c configure:13773: $? = 0 configure:13822: gcc -o conftest -g -O2 -std=gnu99 conftest.c -lX11 5 configure:13829: $? = 0 configure:13891: result: libraries , headers configure:14072: gcc -o conftest -g -O2 -std=gnu99 conftest.c -lX11 5 configure:14079: $? = 0 configure:14247: checking for gethostbyname configure:14303: gcc -o conftest -g -O2 -std=gnu99 conftest.c 5 configure:14310: $? = 0 configure:14330: result: yes configure:14483: checking for connect configure:14539: gcc -o conftest -g -O2 -std=gnu99 conftest.c 5 configure:14546: $? = 0 configure:14566: result: yes configure:14642: checking for remove configure:14698: gcc -o conftest -g -O2 -std=gnu99 conftest.c 5 configure:14705: $? = 0 configure:14725: result: yes configure:14801: checking for shmat configure:14857: gcc -o conftest -g -O2 -std=gnu99 conftest.c 5 configure:14864: $? = 0 configure:14884: result: yes configure:14969: checking for IceConnectionNumber in -lICE configure:15004: gcc -o conftest -g -O2 -std=gnu99 conftest.c -lICE 5 /usr/bin/ld: cannot find -lICE collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/imlib2_1.4.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666319: wise: FTBFS: sqio.c:232:1: error: conflicting types for 'getline'
Source: wise Version: 2.4.1-9 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: cc -c -O3-c sqio.c sqio.c:232:1: error: conflicting types for 'getline' /usr/include/stdio.h:671:20: note: previous declaration of 'getline' was here make[2]: *** [sqio.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/wise_2.4.1-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666320: lilo: FTBFS: ! LaTeX Error: File `url.sty' not found.
Source: lilo Version: 1:23.2-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/doc' ./rlatex user This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2012/dev/Debian) restricted \write18 enabled. entering extended mode (./user.tex LaTeX2e 2011/06/27 Babel v3.8m and hyphenation patterns for english, dumylang, nohyphenation, lo aded. (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2007/10/19 v1.4h Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/ae/ae.sty (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def) (/usr/share/texlive/texmf-dist/tex/latex/ae/t1aer.fd))) (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty)) (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty) (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty) (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def) (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg) ! LaTeX Error: File `url.sty' not found. Type X to quit or RETURN to proceed, or enter new name. (Default extension: sty) Enter file name: ! Emergency stop. read * l.4633 \let \HyOrg@url\url^^M No pages of output. Transcript written on user.log. make[2]: *** [user.dvi] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/lilo_123.2-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666321: wkhtmltopdf: FTBFS: gzip: wkhtmltopdf.1.gz: No such file or directory
Source: wkhtmltopdf Version: 0.9.9-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' # make install is buggy echo make[1]: Leaving directory `/«PKGBUILDDIR»' dh_install -a dh_installdocs -a dh_installchangelogs -a dh_installexamples -a dh_installman -a gzip: wkhtmltopdf.1.gz: No such file or directory gzip: wkhtmltopdf.1.gz: No such file or directory dh_installman: zcat wkhtmltopdf\.1\.gz debian\/wkhtmltopdf\/usr\/share\/man\/man1\/wkhtmltopdf\.1 returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/wkhtmltopdf_0.9.9-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666322: python-prctl: FTBFS: cp: cannot stat `docs/_build/html/index.html': No such file or directory
Source: python-prctl Version: 1.1.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: fakeroot debian/rules binary-arch dh binary-arch dh_testroot -a dh_prep -a dh_installdirs -a dh_auto_install -a running install running build running build_py running build_ext running install_lib creating /«PKGBUILDDIR»/debian/python-prctl/usr creating /«PKGBUILDDIR»/debian/python-prctl/usr/lib creating /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.6 creating /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.6/dist-packages copying build/lib.linux-x86_64-2.6/_prctl.so - /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.6/dist-packages copying build/lib.linux-x86_64-2.6/prctl.py - /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.6/dist-packages running install_egg_info Writing /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.6/dist-packages/python_prctl-1.1.1.egg-info running install running build running build_py running build_ext running install_lib creating /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.7 creating /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.7/dist-packages copying build/lib.linux-x86_64-2.7/_prctl.so - /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.7/dist-packages copying build/lib.linux-x86_64-2.7/prctl.py - /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.7/dist-packages running install_egg_info Writing /«PKGBUILDDIR»/debian/python-prctl/usr/lib/python2.7/dist-packages/python_prctl-1.1.1.egg-info dh_install -a dh_installdocs -a cp: cannot stat `docs/_build/html/index.html': No such file or directory dh_installdocs: cp -a docs/_build/html/index.html debian/python-prctl/usr/share/doc/python-prctl returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/python-prctl_1.1.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666323: mp3splt-gtk: FTBFS: xmms_control.c:(.text+0x89): undefined reference to `audacious_remote_get_info'
Source: mp3splt-gtk Version: 0.5.6-1.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: gcc -Wall -I../libmp3splt/include/ -I../../libmp3splt/include/ -I../libmp3splt/include/libmp3splt/ -I../../libmp3splt/include/libmp3splt/ -L../libmp3splt/src -L../libmp3splt/src/.libs -L../../libmp3splt/src/.libs/ -L../../libmp3splt/src/ -o mp3splt-gtk tree_tab.o main_win.o xmms_control.o gstreamer_control.o player.o player_tab.o preferences_tab.o utilities.o split_files.o freedb_tab.o cddb_cue.o snackamp_control.o special_split.o mp3splt-gtk.o -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lgthread-2.0 -lmp3splt -laudcore -laudgui -pthread -lgstbase-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -lxml2 -lgthread-2.0 -lrt -lglib-2.0 xmms_control.o: In function `myxmms_get_song_infos': xmms_control.c:(.text+0x89): undefined reference to `audacious_remote_get_info' xmms_control.o: In function `myxmms_get_filename': xmms_control.c:(.text+0x1d5): undefined reference to `audacious_remote_get_playlist_pos' xmms_control.c:(.text+0x1ec): undefined reference to `audacious_remote_get_playlist_file' xmms_control.o: In function `myxmms_get_playlist_number': xmms_control.c:(.text+0x237): undefined reference to `audacious_remote_get_playlist_length' xmms_control.o: In function `myxmms_get_title_song': xmms_control.c:(.text+0x250): undefined reference to `audacious_remote_get_playlist_pos' xmms_control.c:(.text+0x267): undefined reference to `audacious_remote_get_playlist_title' xmms_control.o: In function `myxmms_get_time_elapsed': xmms_control.c:(.text+0x284): undefined reference to `audacious_remote_get_output_time' xmms_control.o: In function `myxmms_start': xmms_control.c:(.text+0x2ec): undefined reference to `audacious_remote_is_running' xmms_control.o: In function `myxmms_select_last_file': xmms_control.c:(.text+0x330): undefined reference to `audacious_remote_get_playlist_length' xmms_control.c:(.text+0x34c): undefined reference to `audacious_remote_set_playlist_pos' xmms_control.o: In function `myxmms_play_last_file': xmms_control.c:(.text+0x36b): undefined reference to `audacious_remote_play' xmms_control.o: In function `myxmms_add_files': xmms_control.c:(.text+0x401): undefined reference to `audacious_remote_playlist_add' xmms_control.o: In function `myxmms_set_volume': xmms_control.c:(.text+0x422): undefined reference to `audacious_remote_set_main_volume' xmms_control.o: In function `myxmms_get_volume': xmms_control.c:(.text+0x437): undefined reference to `audacious_remote_get_main_volume' xmms_control.o: In function `myxmms_is_running': xmms_control.c:(.text+0x47c): undefined reference to `dbus_g_bus_get' xmms_control.c:(.text+0x4ad): undefined reference to `dbus_g_proxy_new_for_name' xmms_control.c:(.text+0x4c3): undefined reference to `audacious_remote_is_running' xmms_control.o: In function `myxmms_is_paused': xmms_control.c:(.text+0x4e8): undefined reference to `audacious_remote_is_paused' xmms_control.o: In function `myxmms_play': xmms_control.c:(.text+0x50d): undefined reference to `audacious_remote_play' xmms_control.o: In function `myxmms_stop': xmms_control.c:(.text+0x522): undefined reference to `audacious_remote_stop' xmms_control.o: In function `myxmms_pause': xmms_control.c:(.text+0x537): undefined reference to `audacious_remote_pause' xmms_control.o: In function `myxmms_next': xmms_control.c:(.text+0x54c): undefined reference to `audacious_remote_playlist_next' xmms_control.o: In function `myxmms_prev': xmms_control.c:(.text+0x561): undefined reference to `audacious_remote_playlist_prev' xmms_control.o: In function `myxmms_jump': xmms_control.c:(.text+0x582): undefined reference to `audacious_remote_jump_to_time' xmms_control.o: In function `myxmms_get_total_time': xmms_control.c:(.text+0x59b): undefined reference to `audacious_remote_get_playlist_pos' xmms_control.c:(.text+0x5b2): undefined reference to `audacious_remote_get_playlist_time' xmms_control.o: In function `myxmms_is_playing': xmms_control.c:(.text+0x5c7): undefined reference to `audacious_remote_is_playing' xmms_control.o: In function `myxmms_quit': xmms_control.c:(.text+0x5ec): undefined reference to `audacious_remote_quit' collect2: ld returned 1 exit status The full build log is available from
Bug#666324: libgfshare: FTBFS: ! LaTeX Error: File `url.sty' not found.
Source: libgfshare
Version: 1.0.5-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a recent dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
make[3]: Entering directory `/«PKGBUILDDIR»'
gcc -DHAVE_CONFIG_H -I.-I./include -g -O2 -c -o src/gfshare_maketable.o
src/gfshare_maketable.c
/bin/bash ./libtool --tag=CC --mode=link gcc -I./include -g -O2 -Wl,-O1 -o
gfshare_maketable src/gfshare_maketable.o
libtool: link: gcc -I./include -g -O2 -Wl,-O1 -o gfshare_maketable
src/gfshare_maketable.o
./gfshare_maketable libgfshare_tables.h
/bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I./include -g -O2 -c -o src/libgfshare.lo src/libgfshare.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./include -g -O2 -c
src/libgfshare.c -fPIC -DPIC -o src/.libs/libgfshare.o
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./include -g -O2 -c
src/libgfshare.c -o src/libgfshare.o /dev/null 21
/bin/bash ./libtool --tag=CC --mode=link gcc -I./include -g -O2
-version-info 1:5:0 -Wl,-O1 -o libgfshare.la -rpath /usr/lib/x86_64-linux-gnu
src/libgfshare.lo
libtool: link: gcc -shared src/.libs/libgfshare.o-Wl,-O1 -Wl,-soname
-Wl,libgfshare.so.1 -o .libs/libgfshare.so.1.0.5
libtool: link: (cd .libs rm -f libgfshare.so.1 ln -s
libgfshare.so.1.0.5 libgfshare.so.1)
libtool: link: (cd .libs rm -f libgfshare.so ln -s
libgfshare.so.1.0.5 libgfshare.so)
libtool: link: ar cru .libs/libgfshare.a src/libgfshare.o
libtool: link: ranlib .libs/libgfshare.a
libtool: link: ( cd .libs rm -f libgfshare.la ln -s
../libgfshare.la libgfshare.la )
gcc -DHAVE_CONFIG_H -I.-I./include -g -O2 -c -o tools/gfsplit.o
tools/gfsplit.c
/bin/bash ./libtool --tag=CC --mode=link gcc -I./include -g -O2 -Wl,-O1 -o
gfsplit tools/gfsplit.o libgfshare.la
libtool: link: gcc -I./include -g -O2 -Wl,-O1 -o .libs/gfsplit
tools/gfsplit.o ./.libs/libgfshare.so
gcc -DHAVE_CONFIG_H -I.-I./include -g -O2 -c -o tools/gfcombine.o
tools/gfcombine.c
/bin/bash ./libtool --tag=CC --mode=link gcc -I./include -g -O2 -Wl,-O1 -o
gfcombine tools/gfcombine.o libgfshare.la
libtool: link: gcc -I./include -g -O2 -Wl,-O1 -o .libs/gfcombine
tools/gfcombine.o ./.libs/libgfshare.so
make[3]: Leaving directory `/«PKGBUILDDIR»'
make[2]: Leaving directory `/«PKGBUILDDIR»'
install -d pdf html
cd pdf pdflatex ../doc/theory.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2012/dev/Debian)
restricted \write18 enabled.
entering extended mode
(../doc/theory.tex
LaTeX2e 2011/06/27
Babel v3.8m and hyphenation patterns for english, dumylang, nohyphenation,
lo
aded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))
! LaTeX Error: File `url.sty' not found.
Type X to quit or RETURN to proceed,
or enter new name. (Default extension: sty)
Enter file name:
! Emergency stop.
read *
l.4 \begin
{document}^^M
! == Fatal error occurred, no output PDF file produced!
Transcript written on theory.log.
make[1]: *** [override_dh_auto_build] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/30/libgfshare_1.0.5-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666325: uudeview: FTBFS: ! LaTeX Error: File `a4wide.sty' not found.
Source: uudeview
Version: 0.5.20-3.2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a recent dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
make[1]: Entering directory `/«PKGBUILDDIR»/doc'
fig2dev -L latex structure.fig structure.tex
fig2dev -L latex binhex.fig binhex.tex
latex library.ltx
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2012/dev/Debian)
restricted \write18 enabled.
entering extended mode
(./library.ltx
LaTeX2e 2011/06/27
Babel v3.8m and hyphenation patterns for english, dumylang, nohyphenation,
lo
aded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/epsfig.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/dvips.def
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty)
! LaTeX Error: File `a4wide.sty' not found.
Type X to quit or RETURN to proceed,
or enter new name. (Default extension: sty)
Enter file name:
! Emergency stop.
read *
l.6 \author
{Frank Pilhofer}^^M
No pages of output.
Transcript written on library.log.
make[1]: *** [library.dvi] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/30/uudeview_0.5.20-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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666326: ilmbase: FTBFS: configure:1544: error: cannot run /bin/bash ./config.sub
Source: ilmbase
Version: 1.0.1-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a newer dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
make[1]: Entering directory `/«PKGBUILDDIR»'
PTHREAD_LIBS=-lpthread dh_auto_configure
configure: error: cannot run /bin/bash ./config.sub
== config.log ==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by IlmBase configure 1.0.1, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./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/ilmbase --disable-maintainer-mode
--disable-dependency-tracking
## - ##
## Platform. ##
## - ##
hostname = ip-10-251-43-162
uname -m = x86_64
uname -r = 2.6.32-5-xen-amd64
uname -s = Linux
uname -v = #1 SMP Mon Jan 16 20:48:30 UTC 2012
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
## --- ##
## Core tests. ##
## --- ##
configure:1544: error: cannot run /bin/bash ./config.sub
## ##
## Cache variables. ##
## ##
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-linux-gnu
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
## - ##
## Output variables. ##
## - ##
ACLOCAL=''
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR=''
AM_CFLAGS=''
AM_CXXFLAGS=''
AR=''
AUTOCONF=''
AUTOHEADER=''
AUTOMAKE=''
AWK=''
CC=''
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W=''
DEFS=''
DEPDIR=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77=''
FFLAGS=''
ILMBASE_VERSION='1.0.1'
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
INSTALL_STRIP_PROGRAM=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIBTOOL_VERSION=''
LN_S=''
LTLIBOBJS=''
MAINT=''
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE=''
MAKEINFO=''
OBJEXT=''
PACKAGE=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME='IlmBase'
PACKAGE_STRING='IlmBase 1.0.1'
PACKAGE_TARNAME='ilmbase'
PACKAGE_VERSION='1.0.1'
PATH_SEPARATOR=':'
PTHREAD_CC=''
PTHREAD_CFLAGS=''
PTHREAD_LIBS='-lpthread'
RANLIB=''
SET_MAKE=''
SHELL='/bin/bash'
STRIP=''
VERSION=''
ac_ct_AR=''
ac_ct_CC=''
ac_ct_CXX=''
ac_ct_F77=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
acx_pthread_config=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__leading_dot=''
am__quote=''
am__tar=''
am__untar=''
bindir='${exec_prefix}/bin'
build='x86_64-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='${prefix}/share'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh=''
libdir='${exec_prefix}/lib'
libexecdir='${prefix}/lib/ilmbase'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p=''
oldincludedir='/usr/include'
prefix='/usr'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
#define PACKAGE_BUGREPORT
#define PACKAGE_NAME IlmBase
#define PACKAGE_STRING IlmBase 1.0.1
#define PACKAGE_TARNAME ilmbase
#define PACKAGE_VERSION 1.0.1
configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include
Bug#666327: libmecab-java: FTBFS: MeCab_wrap.cxx:304:16: error: 'mecab_node_t' has no member named 'sentence_length'
Source: libmecab-java Version: 0.98-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: c++ -O3 -c -fpic MeCab_wrap.cxx `mecab-config --cflags` -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux MeCab_wrap.cxx: In function 'const mecab_node_t* mecab_node_t_begin_node_list(mecab_node_t*, size_t)': MeCab_wrap.cxx:304:16: error: 'mecab_node_t' has no member named 'sentence_length' MeCab_wrap.cxx:306:17: error: 'mecab_node_t' has no member named 'begin_node_list' MeCab_wrap.cxx:307:19: error: 'mecab_node_t' has no member named 'begin_node_list' MeCab_wrap.cxx: In function 'const mecab_node_t* mecab_node_t_end_node_list(mecab_node_t*, size_t)': MeCab_wrap.cxx:312:16: error: 'mecab_node_t' has no member named 'sentence_length' MeCab_wrap.cxx:314:17: error: 'mecab_node_t' has no member named 'end_node_list' MeCab_wrap.cxx:315:19: error: 'mecab_node_t' has no member named 'end_node_list' MeCab_wrap.cxx: In function 'jint Java_org_chasen_mecab_MeCabJNI_Token_1lcAttr_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:600:3: error: 'mecab_token_t' was not declared in this scope MeCab_wrap.cxx:600:18: error: 'arg1' was not declared in this scope MeCab_wrap.cxx:600:41: error: expected primary-expression before ')' token MeCab_wrap.cxx:600:43: error: expected ';' before numeric constant MeCab_wrap.cxx:606:28: error: expected primary-expression before ')' token MeCab_wrap.cxx: In function 'jint Java_org_chasen_mecab_MeCabJNI_Token_1rcAttr_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:615:3: error: 'mecab_token_t' was not declared in this scope MeCab_wrap.cxx:615:18: error: 'arg1' was not declared in this scope MeCab_wrap.cxx:615:41: error: expected primary-expression before ')' token MeCab_wrap.cxx:615:43: error: expected ';' before numeric constant MeCab_wrap.cxx:621:28: error: expected primary-expression before ')' token MeCab_wrap.cxx: In function 'jint Java_org_chasen_mecab_MeCabJNI_Token_1posid_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:630:3: error: 'mecab_token_t' was not declared in this scope MeCab_wrap.cxx:630:18: error: 'arg1' was not declared in this scope MeCab_wrap.cxx:630:41: error: expected primary-expression before ')' token MeCab_wrap.cxx:630:43: error: expected ';' before numeric constant MeCab_wrap.cxx:636:28: error: expected primary-expression before ')' token MeCab_wrap.cxx: In function 'jshort Java_org_chasen_mecab_MeCabJNI_Token_1wcost_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:645:3: error: 'mecab_token_t' was not declared in this scope MeCab_wrap.cxx:645:18: error: 'arg1' was not declared in this scope MeCab_wrap.cxx:645:41: error: expected primary-expression before ')' token MeCab_wrap.cxx:645:43: error: expected ';' before numeric constant MeCab_wrap.cxx:651:28: error: expected primary-expression before ')' token MeCab_wrap.cxx: In function 'jlong Java_org_chasen_mecab_MeCabJNI_Token_1feature_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:660:3: error: 'mecab_token_t' was not declared in this scope MeCab_wrap.cxx:660:18: error: 'arg1' was not declared in this scope MeCab_wrap.cxx:660:41: error: expected primary-expression before ')' token MeCab_wrap.cxx:660:43: error: expected ';' before numeric constant MeCab_wrap.cxx:666:28: error: expected primary-expression before ')' token MeCab_wrap.cxx: In function 'jlong Java_org_chasen_mecab_MeCabJNI_Token_1compound_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:675:3: error: 'mecab_token_t' was not declared in this scope MeCab_wrap.cxx:675:18: error: 'arg1' was not declared in this scope MeCab_wrap.cxx:675:41: error: expected primary-expression before ')' token MeCab_wrap.cxx:675:43: error: expected ';' before numeric constant MeCab_wrap.cxx:681:28: error: expected primary-expression before ')' token MeCab_wrap.cxx: In function 'jlong Java_org_chasen_mecab_MeCabJNI_Node_1sentence_1length_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:937:36: error: 'mecab_node_t' has no member named 'sentence_length' MeCab_wrap.cxx: In function 'jlong Java_org_chasen_mecab_MeCabJNI_Node_1token_1get(JNIEnv*, jclass, jlong, jobject)': MeCab_wrap.cxx:1034:3: error: 'mecab_token_t' was not declared in this scope MeCab_wrap.cxx:1034:18: error: 'result' was not declared in this scope MeCab_wrap.cxx:1040:28: error: expected primary-expression before ')' token MeCab_wrap.cxx:1040:39: error: 'mecab_node_t' has no member named 'token
Bug#666328: dulwich: FTBFS: test failed
Source: dulwich Version: 0.8.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»' python setup.py build running build running build_py running build_ext running build_scripts python setup.py build_ext -i running build_ext building 'dulwich._objects' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c dulwich/_objects.c -o build/temp.linux-x86_64-2.7/dulwich/_objects.o gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-x86_64-2.7/dulwich/_objects.o -o /«PKGBUILDDIR»/dulwich/_objects.so building 'dulwich._pack' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c dulwich/_pack.c -o build/temp.linux-x86_64-2.7/dulwich/_pack.o gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-x86_64-2.7/dulwich/_pack.o -o /«PKGBUILDDIR»/dulwich/_pack.so building 'dulwich._diff_tree' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c dulwich/_diff_tree.c -o build/temp.linux-x86_64-2.7/dulwich/_diff_tree.o gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-x86_64-2.7/dulwich/_diff_tree.o -o /«PKGBUILDDIR»/dulwich/_diff_tree.so PYTHONPATH=.: python -m unittest dulwich.tests.test_suite s..F.s..s..s == FAIL: test_nonempty (dulwich.tests.test_index.BuildIndexTests) -- Traceback (most recent call last): File dulwich/tests/test_index.py, line 311, in test_nonempty None)) File dulwich/tests/test_index.py, line 220, in assertReasonableIndexEntry self.assertEquals(index_entry[0], index_entry[1]) # ctime and atime AssertionError: Tuples differ: (1333062402, 341015338) != (1333062402, 329015493) First differing element 1: 341015338 329015493 - (1333062402, 341015338) ? ^^-- + (1333062402, 329015493) ? ^^ ++ -- Ran 684 tests in 35.016s FAILED (failures=1, skipped=4) make[2]: *** [check] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/dulwich_0.8.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666329: c-icap: FTBFS: cp: cannot stat `debian/tmp/etc/c-icap/c-icap.conf': No such file or directory
Source: c-icap Version: 1:0.1.6-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' /usr/bin/chrpath -d debian/tmp/usr/bin/c-icap /usr/bin/chrpath -d debian/tmp/usr/bin/c-icap-client /usr/bin/chrpath -d debian/tmp/usr/bin/c-icap-mkbdb dh_install cp: cannot stat `debian/tmp/etc/c-icap/c-icap.conf': No such file or directory dh_install: cp -a debian/tmp/etc/c-icap/c-icap.conf debian/c-icap//etc/c-icap/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/c-icap_10.1.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666330: suricata: FTBFS: cp: cannot stat `debian/tmp/suricata-debian.yaml': No such file or directory
Source: suricata Version: 1.2.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' dh_install -a cp -a debian/tmp/suricata-debian.yaml debian/suricata//etc/suricata/ cp: cannot stat `debian/tmp/suricata-debian.yaml': No such file or directory dh_install: cp -a debian/tmp/suricata-debian.yaml debian/suricata//etc/suricata/ returned exit code 1 make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/suricata_1.2.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666331: libdbi-drivers: FTBFS: configure: error: Invalid SQLite3 directory - libraries not found.
Source: libdbi-drivers Version: 0.8.3-1+s-2.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build test -d debian/patched || install -d debian/patched dpatch apply-all applying patch 001_test_dbi.c to ./ ... ok. dpatch cat-all patch-stampT mv -f patch-stampT patch-stamp dh_testdir dh_autoreconf configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... configure.in:98: the top level configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... configure.in:98: the top level libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... configure.in:98: the top level configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... configure.in:98: the top level configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... configure.in:98: the top level configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... configure.in:98: the top level configure.in:7: installing `./config.guess' configure.in:7: installing `./config.sub' drivers/firebird/Makefile.am:10: docdir was already defined in condition TRUE, which includes condition BUILDDOCS and HAVE_FIREBIRD_INTERBASE ... configure.in:2: ... `docdir' previously defined here drivers/firebird/Makefile.am:11: htmldir was already defined in condition TRUE, which includes condition BUILDDOCS and HAVE_FIREBIRD_INTERBASE ... configure.in:2: ... `htmldir' previously defined here drivers/firebird/Makefile.am:15: docdir was already defined in condition TRUE, which includes condition !BUILDDOCS and HAVE_FIREBIRD_INTERBASE ... configure.in:2: ... `docdir' previously defined here drivers/firebird/Makefile.am:16: htmldir was already defined in condition TRUE, which includes condition !BUILDDOCS and HAVE_FIREBIRD_INTERBASE ... configure.in:2: ... `htmldir' previously defined here drivers/freetds/Makefile.am:7: docdir was already defined in condition TRUE, which includes condition BUILDDOCS and HAVE_FREETDS ... configure.in:2: ... `docdir' previously defined here drivers/freetds/Makefile.am:8: htmldir was already defined in condition TRUE, which includes condition BUILDDOCS and HAVE_FREETDS ... configure.in:2: ... `htmldir' previously defined here drivers/freetds/Makefile.am:12: docdir was already defined in condition TRUE, which includes condition !BUILDDOCS and HAVE_FREETDS ... configure.in:2: ... `docdir
Bug#666332: hyperestraier: FTBFS: cp: cannot stat `estraierpure.jar': No such file or directory
Source: hyperestraier Version: 1.4.13-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»/javapure' mkdir -p /«PKGBUILDDIR»/debian/libestraier-java/usr/share/hyperestraier cp -Rf estraierpure.jar /«PKGBUILDDIR»/debian/libestraier-java/usr/share/hyperestraier cp: cannot stat `estraierpure.jar': No such file or directory make[1]: *** [install] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/hyperestraier_1.4.13-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666333: libxslt: FTBFS: sed: can't read debian/tmp/usr/lib/*.la: No such file or directory
Source: libxslt Version: 1.1.26-8 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' dh_auto_install --builddirectory=build/main # Properly install documentation in /usr/share/doc/libxslt1-dev install -d debian/tmp/usr/share/doc/libxslt1-dev/EXSLT install -m 644 \ doc/*.html \ doc/*.gif \ doc/libxslt-*.xml debian/tmp/usr/share/doc/libxslt1-dev install -m 644 \ doc/EXSLT/*.html \ doc/EXSLT/libexslt-*.xml debian/tmp/usr/share/doc/libxslt1-dev cp -a \ doc/html \ doc/tutorial \ doc/tutorial2 debian/tmp/usr/share/doc/libxslt1-dev cp -a \ doc/EXSLT/html debian/tmp/usr/share/doc/libxslt1-dev/EXSLT sed -i /dependency_libs/ s/'.*'/''/ debian/tmp/usr/lib/*.la sed: can't read debian/tmp/usr/lib/*.la: No such file or directory make[1]: *** [install-main] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/libxslt_1.1.26-8_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666334: gnustep-back: FTBFS: CairoFontEnumerator.m:152: undefined reference to `FcPatternCreate'
Source: gnustep-back Version: 0.20.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: gcc-4.6 -shared -rdynamic -Wl,-z,defs -Wl,--as-needed -shared-libgcc -fexceptions -o ./libgnustep-cairo-020.bundle/./libgnustep-cairo-020 ./obj/libgnustep-cairo-020.obj/GSBackend.m.o ./gsc/obj/subproject.o ./x11/obj/subproject.o ./cairo/obj/subproject.o -L/usr/local/lib -L/usr/lib -lcairo -lfreetype -lXrender -lcairo -lX11 -lXft-lXmu -lXt -lXext -lX11 -lGL -lgnustep-gui-lgnustep-base -lpthread -lobjc -lm ./cairo/obj/subproject.o: In function `-[CairoFontEnumerator enumerateFontsAndFamilies]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:152: undefined reference to `FcPatternCreate' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:153: undefined reference to `FcObjectSetBuild' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:155: undefined reference to `FcFontList' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:157: undefined reference to `FcPatternDestroy' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:158: undefined reference to `FcObjectSetDestroy' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:164: undefined reference to `FcPatternGetString' ./cairo/obj/subproject.o: In function `faFromFc': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:73: undefined reference to `FcPatternGetInteger' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:74: undefined reference to `FcPatternGetInteger' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:75: undefined reference to `FcPatternGetString' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:79: undefined reference to `FcPatternGetInteger' ./cairo/obj/subproject.o: In function `-[CairoFontEnumerator enumerateFontsAndFamilies]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:198: undefined reference to `FcFontSetDestroy' ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet initWithFontconfigCharSet:]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:246: undefined reference to `FcCharSetCopy' ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet dealloc]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:259: undefined reference to `FcCharSetDestroy' ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet characterIsMember:]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:270: undefined reference to `FcCharSetHasChar' ./cairo/obj/subproject.o: In function `-[FontconfigCharacterSet longCharacterIsMember:]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFontEnumerator.m:275: undefined reference to `FcCharSetHasChar' ./cairo/obj/subproject.o: In function `-[CairoFaceInfo initWithfamilyName:weight:traits:pattern:]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:44: undefined reference to `FcPatternReference' ./cairo/obj/subproject.o: In function `-[CairoFaceInfo dealloc]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:59: undefined reference to `FcPatternDestroy' ./cairo/obj/subproject.o: In function `-[CairoFaceInfo fontFace]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:107: undefined reference to `FcConfigSubstitute' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:108: undefined reference to `FcDefaultSubstitute' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:109: undefined reference to `FcFontMatch' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:112: undefined reference to `FcPatternDestroy' ./cairo/obj/subproject.o: In function `-[CairoFaceInfo characterSet]': /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:134: undefined reference to `FcConfigSubstitute' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:135: undefined reference to `FcDefaultSubstitute' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:136: undefined reference to `FcFontMatch' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:138: undefined reference to `FcPatternGetCharSet' /«PKGBUILDDIR»/build-cairo/Source/cairo/CairoFaceInfo.m:149: undefined reference to `FcPatternDestroy' collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/gnustep-back_0.20.1-2_unstable.log A list of current common problems and possible solutions is available at http
Bug#666335: iptables: FTBFS: make[2]: *** No rule to make target `check'. Stop.
Source: iptables Version: 1.4.13-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/utils' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/«PKGBUILDDIR»/utils' Making check in extensions make[2]: Entering directory `/«PKGBUILDDIR»/extensions' make[2]: *** No rule to make target `check'. Stop. make[2]: Leaving directory `/«PKGBUILDDIR»/extensions' make[1]: *** [check-recursive] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/iptables_1.4.13-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666336: tcng: FTBFS: ! LaTeX Error: File `url.sty' not found.
Source: tcng Version: 10b-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/doc' fig2dev -L eps build.fig build.eps fig2dev -L eps dlb.fig dlb.eps fig2dev -L eps incoming.fig incoming.eps fig2dev -L eps multi.fig multi.eps fig2dev -L eps phtcc.fig phtcc.eps fig2dev -L eps phtcsim.fig phtcsim.eps fig2dev -L eps slb.fig slb.eps fig2dev -L eps srtcm.fig srtcm.eps fig2dev -L eps tccsys.fig tccsys.eps fig2dev -L eps tcsimsys.fig tcsimsys.eps fig2dev -L eps trtcm.fig trtcm.eps ../scripts/rlatex tcng.tex This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2012/dev/Debian) restricted \write18 enabled. entering extended mode (./tcng.tex LaTeX2e 2011/06/27 Babel v3.8m and hyphenation patterns for english, dumylang, nohyphenation, lo aded. (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls Document Class: book 2007/10/19 v1.4h Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo)) ! LaTeX Error: File `url.sty' not found. Type X to quit or RETURN to proceed, or enter new name. (Default extension: sty) Enter file name: ! Emergency stop. read * l.13 ^^M No pages of output. Transcript written on tcng.log. make[2]: *** [tcng.dvi] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/tcng_10b-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666337: euler: FTBFS: gcc: error: unrecognized option '-V'
Source: euler Version: 1.61.0-8 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: gcc version 4.6.3 (Debian 4.6.3-1) configure:2329: $? = 0 configure:2331: gcc -V /dev/null 5 gcc: error: unrecognized option '-V' gcc: fatal error: no input files compilation terminated. configure:2334: $? = 4 configure:2357: checking for C compiler default output file name configure:2360: gccconftest.c 5 configure:2363: $? = 0 configure:2409: result: a.out configure:2414: checking whether the C compiler works configure:2420: ./a.out configure:2423: $? = 0 configure:2440: result: yes configure:2447: checking whether we are cross compiling configure:2449: result: no configure:2452: checking for suffix of executables configure:2454: gcc -o conftestconftest.c 5 configure:2457: $? = 0 configure:2482: result: configure:2488: checking for suffix of object files configure:2509: gcc -c conftest.c 5 configure:2512: $? = 0 configure:2534: result: o configure:2538: checking whether we are using the GNU C compiler configure:2562: gcc -c conftest.c 5 configure:2568: $? = 0 configure:2572: test -z || test ! -s conftest.err configure:2575: $? = 0 configure:2578: test -s conftest.o configure:2581: $? = 0 configure:2594: result: yes configure:2600: checking whether gcc accepts -g configure:2621: gcc -c -g conftest.c 5 configure:2627: $? = 0 configure:2631: test -z || test ! -s conftest.err configure:2634: $? = 0 configure:2637: test -s conftest.o configure:2640: $? = 0 configure:2651: result: yes configure:2668: checking for gcc option to accept ANSI C configure:2738: gcc -c -g -O2 conftest.c 5 configure:2744: $? = 0 configure:2748: test -z || test ! -s conftest.err configure:2751: $? = 0 configure:2754: test -s conftest.o configure:2757: $? = 0 configure:2775: result: none needed configure:2793: gcc -c -g -O2 conftest.c 5 conftest.c:2:3: error: unknown type name 'choke' conftest.c:2:3: error: expected '=', ',', ';', 'asm' or '__attribute__' at end of input configure:2799: $? = 1 configure: failed program was: | #ifndef __cplusplus | choke me | #endif configure:2934: checking dependency style of gcc configure:3024: result: none configure:3042: checking for library containing strerror configure:3072: gcc -o conftest -g -O2 conftest.c 5 configure:3078: $? = 0 configure:3082: test -z || test ! -s conftest.err configure:3085: $? = 0 configure:3088: test -s conftest configure:3091: $? = 0 configure:3161: result: none required configure:3216: checking for gcc configure:3242: result: gcc configure:3486: checking for C compiler version configure:3489: gcc --version /dev/null 5 gcc (Debian 4.6.3-1) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3492: $? = 0 configure:3494: gcc -v /dev/null 5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.6.3-1' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-objc-gc --with-arch-32=i586 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.6.3 (Debian 4.6.3-1) configure:3497: $? = 0 configure:3499: gcc -V /dev/null 5 gcc: error: unrecognized option '-V' gcc: fatal error: no input files compilation terminated. configure:3502: $? = 4 configure:3505: checking whether we are using the GNU C compiler configure:3561: result: yes configure:3567: checking whether gcc accepts -g configure:3618: result: yes configure:3635: checking for gcc option to accept ANSI C configure:3742: result: none needed configure:3760: gcc -c conftest.c 5 conftest.c:2:3: error: unknown type name 'choke' conftest.c:2:3: error: expected
Bug#666338: wp2x: FTBFS: make[2]: *** No rule to make target `/usr/include/sys/cdefs.h', needed by `wp2x.o'. Stop.
Source: wp2x Version: 2.5-mhi-10 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh build-arch dh_testdir -a dh_auto_configure -a dh_auto_build -a make[1]: Entering directory `/«PKGBUILDDIR»' cd src make wp2x WP2X_DIR=/usr/local/lib/wp2x VERSION=2.5 make[2]: Entering directory `/«PKGBUILDDIR»/src' make[2]: *** No rule to make target `/usr/include/sys/cdefs.h', needed by `wp2x.o'. Stop. make[2]: Leaving directory `/«PKGBUILDDIR»/src' make[1]: *** [wp2x] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/wp2x_2.5-mhi-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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666339: tcptrace: FTBFS: cp: cannot stat `debian/tmp/tcptrace': No such file or directory
Source: tcptrace
Version: 6.6.7-4
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a recent dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
fakeroot debian/rules binary-arch
dh_testdir
CFLAGS=-D_BSD_SOURCE ./configure --prefix=/usr --sysconfdir=/etc
--mandir=/usr/share/man
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking gcc version... 4
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking whether make sets ${MAKE}... yes
checking for flex... no
checking for lex... no
checking for yywrap in -lfl... no
checking for yywrap in -ll... no
checking for bison... no
checking for byacc... no
checking for main in -lm... yes
checking how to run the C preprocessor... gcc -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 for unsigned long long int... yes
checking size of unsigned long long int... 8
checking for unsigned long int... yes
checking size of unsigned long int... 8
checking for unsigned int... yes
checking size of unsigned int... 4
checking for unsigned short... yes
checking size of unsigned short... 2
checking for gethostbyname... yes
checking for socket... yes
checking for putmsg in -lstr... no
checking for fpurge... no
checking for mkstemp... yes
checking for valloc... yes
checking for memalign... yes
checking for inet_pton... yes
checking how to print unsigned long long... %llu
configure: creating ./config.status
config.status: creating Makefile
touch config-stamp
touch build-indep-stamp
touch build-stamp
dh_testdir
dh_testroot
dh_installdirs
dh_install
cp: cannot stat `debian/tmp/tcptrace': No such file or directory
dh_install: cp -a debian/tmp/tcptrace debian/tcptrace/usr/bin/ returned exit
code 1
make: *** [binary-arch] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/30/tcptrace_6.6.7-4_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666341: vgrabbj: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: vgrabbj Version: 0.9.6-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir # Add here commands to compile the package. /usr/bin/make CFLAGS=-g -Wall -O2 make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/vgrabbj_0.9.6-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666342: cproto: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: cproto Version: 4.7j-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/cproto_4.7j-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666343: cairo-5c: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: cairo-5c Version: 1.6 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/cairo-5c_1.6_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666344: dieharder: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: dieharder Version: 3.31.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/dieharder_3.31.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666345: drbd8: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: drbd8 Version: 2:8.3.11-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-arch-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/drbd8_28.3.11-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666346: openjade: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: openjade Version: 1.4devel1-20 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir jade /usr/bin/make SUBDIRS=grove spgrove style make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/openjade_1.4devel1-20_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666347: toshset: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: toshset Version: 1.76-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/toshset_1.76-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666348: cabextract: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: cabextract Version: 1.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/cabextract_1.4-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666349: openais: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: openais Version: 1.1.4-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/openais_1.1.4-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666350: mpg321: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: mpg321 Version: 0.3.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/mpg321_0.3.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666351: openr2: FTBFS: dh_install: libopenr2-bin missing files (etc/openr2/*.conf), aborting
Source: openr2 Version: 1.3.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[3]: Entering directory `/«PKGBUILDDIR»' test -z /etc || mkdir -p -- /«PKGBUILDDIR»/debian/tmp/etc /usr/bin/install -c -m 644 'doc/r2proto.conf' '/«PKGBUILDDIR»/debian/tmp/etc/r2proto.conf' /usr/bin/install -c -m 644 'doc/r2test.conf' '/«PKGBUILDDIR»/debian/tmp/etc/r2test.conf' test -z /usr/share/man/man5 || mkdir -p -- /«PKGBUILDDIR»/debian/tmp/usr/share/man/man5 /usr/bin/install -c -m 644 './r2test.conf.5' '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man5/r2test.conf.5' test -z /usr/share/man/man8 || mkdir -p -- /«PKGBUILDDIR»/debian/tmp/usr/share/man/man8 /usr/bin/install -c -m 644 './r2test.8' '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/r2test.8' make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' dh_install -a dh_install: libopenr2-bin missing files (etc/openr2/*.conf), aborting make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/openr2_1.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666352: ncftp: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: ncftp Version: 2:3.2.5-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/ncftp_23.2.5-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666353: xosview: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: xosview Version: 1.9.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/xosview_1.9.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666354: sopwith: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: sopwith Version: 1.7.4-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/sopwith_1.7.4-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666355: binutils-z80: FTBFS: /bin/sh: 1: cd: can't cd to build
Source: binutils-z80 Version: 2.22-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir cd build /usr/bin/make /bin/sh: 1: cd: can't cd to build make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/binutils-z80_2.22-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666357: yubiserver: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: yubiserver Version: 0.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/yubiserver_0.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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666358: tnef: FTBFS: dh: Unknown sequence --with (options should not come before the sequence)
Source: tnef Version: 1.4.8-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh --with quilt build-arch dh: Unknown sequence --with (options should not come before the sequence) make: *** [build-arch] Error 25 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/tnef_1.4.8-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666356: nickle: FTBFS: make[1]: *** No targets specified and no makefile found. Stop.
Source: nickle Version: 2.74-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch dh_testdir /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/nickle_2.74-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666359: haskell-cabal-install: FTBFS: missing dependencies
Source: haskell-cabal-install Version: 0.10.2-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: debian/rules build-arch 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/cabal-install-0.10.2/ \ --htmldir=/usr/share/doc/libghc-cabal-install-doc/html/ \ Configuring cabal-install-0.10.2... hlibrary.setup: At least the following dependencies are missing: Cabal =1.10.1 1.11, base =2.0 2.2, filepath =1.0 1.3, time =1.1 1.3, unix =1.0 2.5 make: *** [dist-ghc] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/haskell-cabal-install_0.10.2-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666361: epix: FTBFS: latex fails
Source: epix Version: 1.2.9-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/samples' touch sample-stamp tar -cf sample_src.tar R_demo.xp S2_harmonics.xp artifacts.xp bowl.xp butterfly.xp calculus.xp clipping.xp color_sep.xp conic.xp contour.xp coord_tricks.xp cropplot.xp dataplot.xp decorate.xp demoivre.xp denom.xp densityplot.xp dipole.xp extract.xp geomsum.xp golden_rect.xp hello.xp histogram.xp hyperboloid.xp inverse.xp koch.xp label_debug.xp layout.xp layout2.xp legend.xp levelset.xp levelset2.xp levelset3.xp line_debug.xp lissajous.xp log.xp lorenz.xp medians.xp minkowski.xp newton.xp objects.xp oscillator.xp parabola.xp pascal.xp planes.xp plotting.xp plotting2.xp plotting3.xp polar.xp pole.xp polyhedra.xp saddle.xp semicirc.xp shadeplot.xp slopefield.xp sphere.xp spherical.xp sqrt.xp sqrt2.xp std_F.xp surface_shade.xp symmetries.xp tori.xp torus.xp twisted_cubic.xp uppersum.xp vfield.xp weierstrass.xp wheel.xp cube.flx helicoid.flx house.flx lighting.flx mirrorball.flx pendulum.flx riemann.flx steiner.flx steiner2.flx stereo_proj.flx trig.flx \ README binom.cc lighting.h std_F.cc std_F.h gzip -9 sample_src.tar make[2]: Leaving directory `/«PKGBUILDDIR»/samples' Making all in doc make[2]: Entering directory `/«PKGBUILDDIR»/doc' latex -interaction=batchmode manual 21 /dev/null make[2]: *** [manual-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/epix_1.2.9-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
