Bug#551254: texmacs: FTBFS: ERROR: installing Rd objects failed for package 'TeXmacs'
> raju, do you know R? Or do you have time to ask this problem > in texmacs ML? > If not I'll ask this problem in debian-devel. > I do not know R. I am kinda busy with personal things at this moment. Could you please do the needful? raju -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562367: canna: FTBFS: ! LaTeX Error: File `fancyvrb.sty' not found.
Quoting Lucas Nussbaum (lu...@lucas-nussbaum.net): > Source: canna > Version: 3.7p3-6.2 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091213 qa-ftbfs > Justification: FTBFS on amd64 Merci encore, Lucas, for these very useful automated builds. I hope you'll have access to Grid500 forever..:-) Being the last NMUer for this package, I was still subscribed to its PTS. I had a quick look at this FTBFS: > > (/usr/share/texmf-texlive/tex/latex/graphics/dvips.def))) > > > > ! LaTeX Error: File `fancyvrb.sty' not found. Even though I know nothing to TeXlive packages, I saw many changes to these packages. My rough guess is that the package that provides this file (texlive-latex-recommended) was formerly installed as a dependency of another build dependency and is not anymore. So, just adding texlive-latex-recommended to build dependencies is probably the way to fix this, which is what I'll try. signature.asc Description: Digital signature
Bug#551254: texmacs: FTBFS: ERROR: installing Rd objects failed for package 'TeXmacs'
Hi all, On Mon, 14 Dec 2009 10:32:39 +0900, Nobuhiro Iwamatsu wrote: >>> Warning: ./man/TeXmacs.Rd:44: unexpected UNKNOWN '\eof' >>> Warning: ./man/TeXmacs.Rd:84: unexpected UNKNOWN '\eof' >>> Warning: ./man/TeXmacs.Rd:23: All text must be in a section (snip) > I built this package on pbuilder / i386. > I had same bug. (snip) > Could you confirm it again? confirmed. I don't speak R but it looks to me that man/TeXmacs.Rd might be wrong (written in obsolete style?). If I splitted TeXmacs.Rd in two files in line #44 and removed unnecessary \eof then I can build the package successfully. raju, do you know R? Or do you have time to ask this problem in texmacs ML? If not I'll ask this problem in debian-devel. Thanks for reporting the problem and sorry for delay. Regards, 2009-12-25(Fri) -- Debian Developer - much more I18N of Debian Atsuhito Kohda Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562358: mlpost: FTBFS: mkdir -p img/ fails?
Norbert Preining a écrit : >> Do texlive-metapost maintainers have a clue? > > Do *not* set > tracing_choices := 1; > that is the reason 1 is returned. I will ask Taco if that is intended, > but an easy fix for you is simply do NOT include the above line. This is generated code. Is it always safe to remove it? How is it the exit code is 0 if one removes code for figures 2..19 (i.e. only 1 remaining), but keeps the tracing_choices directive? Cheers, -- Stéphane PS: for the mlpost authors I've bcc'ed: see the full bugreport at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562358 PS₂: Happy Christmas! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561631: marked as done (ttf-mathematica4.1: Download fails (301 Moved Permanently))
Your message dated Fri, 25 Dec 2009 12:48:12 +0900 (JST) with message-id <20091225.124812.250322035.ko...@pm.tokushima-u.ac.jp> and subject line Re: Bug#561631: ttf-mathematica4.1: Download fails (301 Moved Permanently) has caused the Debian Bug report #561631, regarding ttf-mathematica4.1: Download fails (301 Moved Permanently) 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.) -- 561631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ttf-mathematica4.1 Version: 6 Severity: grave Justification: renders package unusable Font download from wolfram.com fails, see output below (I'm afraid it's in German though it should be obvious what happens, but please contact me in case of questions) . Regards Jan j...@x30:~$ sudo dpkg-reconfigure ttf-mathematica4.1 [sudo] password for jan: --2009-12-18 22:35:00-- http://support.wolfram.com/mathematica/systems/windows/general/files/MathFonts_TrueType_41.exe Auflösen des Hostnamen »support.wolfram.com« 140.177.205.40 Verbindungsaufbau zu support.wolfram.com|140.177.205.40|:80... verbunden. HTTP Anforderung gesendet, warte auf Antwort... 301 Moved Permanently Platz: http://support.wolfram.com/[folge] --2009-12-18 22:35:01-- http://support.wolfram.com/ Verbindungsaufbau zu support.wolfram.com|140.177.205.40|:80... verbunden. HTTP Anforderung gesendet, warte auf Antwort... 200 OK Länge: nicht spezifiziert [text/html] In »./index.html« speichern. [ <=> ] 29.777 52,0K/s in 0,6s 2009-12-18 22:35:03 (52,0 KB/s) - »./index.html« gespeichert [29777] checking MathFonts_TrueType_41.exe Downloaded file looks corrupted! -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ttf-mathematica4.1 depends on: ii debconf [debconf-2.0]1.5.24 Debian configuration management sy ii defoma 0.11.10-0.2 Debian Font Manager -- automatic f ii unzip5.52-12 De-archiver for .zip files Versions of packages ttf-mathematica4.1 recommends: ii latex-xft-fonts 0.1-8 Xft-compatible versions of some La ii xfonts-mathml 2 Type1 Symbol font for MathML ttf-mathematica4.1 suggests no packages. -- debconf information excluded --- End Message --- --- Begin Message --- Hi Jan, sorry for delay. On Fri, 18 Dec 2009 22:41:03 +0100, Jan Heitkötter wrote: > Font download from wolfram.com fails, see output below (I'm afraid it's > in German though it should be obvious what happens, but please contact > me in case of questions) . ttf-mathematica4.1 is obsolete now. It is very unfortunate that lenny was released at the time wolfram removed their fonts from the web site. But note mathematica fonts are no more necessary for MathML but stix fonts (otf-stix package) are necessary instead. So if you need mathematica fonts for displaying MathML, please simply remove ttf-mathematica4.1 and install otf-stix (in testing perhaps). If you need mathematica fonts for using Mathematica from remote machine, for example, please install mathematica-fonts (in testing) which will install mathematica fonts without problem at the moment. Regards, 2009-12-25(Fri) -- Debian Developer - much more I18N of Debian Atsuhito Kohda Department of Math., Univ. of Tokushima --- End Message ---
Bug#561631: ttf-mathematica4.1: Download fails (301 Moved Permanently)
Hi Jan, sorry for delay. On Fri, 18 Dec 2009 22:41:03 +0100, Jan Heitkötter wrote: > Font download from wolfram.com fails, see output below (I'm afraid it's > in German though it should be obvious what happens, but please contact > me in case of questions) . ttf-mathematica4.1 is obsolete now. It is very unfortunate that lenny was released at the time wolfram removed their fonts from the web site. But note mathematica fonts are no more necessary for MathML but stix fonts (otf-stix package) are necessary instead. So if you need mathematica fonts for displaying MathML, please simply remove ttf-mathematica4.1 and install otf-stix (in testing perhaps). If you need mathematica fonts for using Mathematica from remote machine, for example, please install mathematica-fonts (in testing) which will install mathematica fonts without problem at the moment. Regards, 2009-12-25(Fri) -- Debian Developer - much more I18N of Debian Atsuhito Kohda Department of Math., Univ. of Tokushima
Bug#559989: marked as done (FTBFS [hppa] - spinning waf process)
Your message dated Fri, 25 Dec 2009 03:18:38 + with message-id and subject line Bug#559989: fixed in midori 0.2.2-1 has caused the Debian Bug report #559989, regarding FTBFS [hppa] - spinning waf process 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.) -- 559989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: midori Version: 0.2.0-1 Severity: serious User: debian-h...@lists.debian.org Usertags: hppa midori reliably fails to build on hppa: https://buildd.debian.org/build.php?&pkg=midori&ver=0.2.0-1&arch=hppa&file=log >From the most recent build attempt: [...] [ 13/106] cc: katze/katze-utils.c ->_build_/default/katze/katze-utils_1.o [ 14/106] cc: _build_/default/midori/marshal.c -> _build_/default/midori/marshal_1.o [ 15/106] cc: midori/compat.c -> _build_/default/midori/compat_1.o [ 16/106] cc: midori/gtkiconentry.c -> _build_/default/midori/gtkiconentry_1.o [ 17/106] cc: midori/midori-app.c -> _build_/default/midori/midori-app_1.o [ 18/106] cc: midori/midori-array.c -> _build_/default/midori/midori-array_1.o [ 19/106] cc: midori/midori-browser.c -> _build_/default/midori/midori-browser_1.o [ 20/106] cc: midori/midori-extension.c -> _build_/default/midori/midori-extension_1.o [ 21/106] cc: midori/midori-locationaction.c -> _build_/default/midori/midori-locationaction_1.o [ 22/106] cc: midori/midori-locationentry.c -> _build_/default/midori/midori-locationentry_1.o The build stalled here for 2.5 hours before I killed it. While the build was stalled, I noticed that the 'python ./waf' process was consuming the entire CPU. strace showed no system calls being made. --- End Message --- --- Begin Message --- Source: midori Source-Version: 0.2.2-1 We believe that the bug you reported is fixed in the latest version of midori, which is due to be installed in the Debian FTP archive: midori-dbg_0.2.2-1_i386.deb to main/m/midori/midori-dbg_0.2.2-1_i386.deb midori_0.2.2-1.diff.gz to main/m/midori/midori_0.2.2-1.diff.gz midori_0.2.2-1.dsc to main/m/midori/midori_0.2.2-1.dsc midori_0.2.2-1_i386.deb to main/m/midori/midori_0.2.2-1_i386.deb midori_0.2.2.orig.tar.gz to main/m/midori/midori_0.2.2.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 559...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ryan Niebur (supplier of updated midori 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: Thu, 24 Dec 2009 18:30:46 -0800 Source: midori Binary: midori midori-dbg Architecture: source i386 Version: 0.2.2-1 Distribution: unstable Urgency: low Maintainer: Ryan Niebur Changed-By: Ryan Niebur Description: midori - fast, lightweight graphical web browser midori-dbg - fast, lightweight graphical web browser (debug symbols) Closes: 514435 538327 545251 547584 550844 556184 558339 559989 560866 561451 562501 Changes: midori (0.2.2-1) unstable; urgency=low . * New Upstream Version (Closes: #556184, #558339) - fixes local uri handling (Closes: #560866, #550844) - move libnotify from Recommends to Build-Deps to follow upstream - update debian/copyright to match upstream changes - fixes handling of URLs like "some.url?%00" (Closes: #561451) - running twice doesn't crash the browser (Closes: #514435) - Ctrl-w on last tab now closes it but still not the browser (Closes: #545251) - Ctrl-u in urlbar with emacs key binding theme works (Closes: #538327) * move libjs-mootools to Recommends, it's not required (Closes: #547584) * tell the user to report the bug against libwebkit-1.0-2 if they reproduce it in the Webkit test browser. Figure out the package name and the path to GtkLauncher automagically during build. (Closes: #562501) * switch to system waf - the FTBFS #559989 is no longer the fault of anything in my package, and I've set #561130 in the BTS to affect midori, so (Closes: #559989) * refresh patch Checksums-Sha1: 845152eac802c04c53edf61fb435d5fd6067e467 1493 midori_0.2.2-1.dsc 6e1dff0f35b3ca459c205efdf8208fb7568f6e41 903075 midori_0.2.2.orig.tar.gz 2cefe04d97c0c7a91c584423276f7bc07f8a7914
Bug#526671: marked as done (FTBFS with GCC 4.4: dereferencing pointer breaks strict-aliasing rules)
Your message dated Fri, 25 Dec 2009 03:18:57 + with message-id and subject line Bug#526671: fixed in remotefs 0.11+debian-3 has caused the Debian Bug report #526671, regarding FTBFS with GCC 4.4: dereferencing pointer breaks strict-aliasing rules 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.) -- 526671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: remotefs Version: 0.11+debian-1 User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.4 Your package fails to build with GCC 4.4. You can reproduce this problem with gcc-4.4/g++-4.4 from unstable. > Automatic build of remotefs_0.11+debian-1 on em64t by sbuild/amd64 0.53 ... > Compile src/server.o > cc1: warnings being treated as errors > src/server.c: In function 'handle_connection': > src/server.c:240: error: dereferencing pointer 'client_addr.26' does break > strict-aliasing rules > src/server.c:240: note: initialized from here > make[3]: *** [src/server.o] Error 1 > make[3]: Leaving directory `/build/tbm/remotefs-0.11+debian' -- Martin Michlmayr http://www.cyrius.com/ --- End Message --- --- Begin Message --- Source: remotefs Source-Version: 0.11+debian-3 We believe that the bug you reported is fixed in the latest version of remotefs, which is due to be installed in the Debian FTP archive: remotefs_0.11+debian-3.diff.gz to main/r/remotefs/remotefs_0.11+debian-3.diff.gz remotefs_0.11+debian-3.dsc to main/r/remotefs/remotefs_0.11+debian-3.dsc rfs-client_0.11+debian-3_i386.deb to main/r/remotefs/rfs-client_0.11+debian-3_i386.deb rfs-server_0.11+debian-3_i386.deb to main/r/remotefs/rfs-server_0.11+debian-3_i386.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 526...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barry deFreese (supplier of updated remotefs 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: Thu, 24 Dec 2009 20:16:28 -0500 Source: remotefs Binary: rfs-client rfs-server Architecture: source i386 Version: 0.11+debian-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Barry deFreese Description: rfs-client - simple user-space network file system for embedded systems (clien rfs-server - simple user-space network file system for embedded systems (serve Closes: 526671 Changes: remotefs (0.11+debian-3) unstable; urgency=low . * QA upload. * Add quilt patch system. * 01_gcc_44.diff - Fix aliasing with gcc-4.4. (Closes: #526671). + Patch taken from David Sugar at Ubuntu, thanks. * Update init to check if file exists. (Policy 9.3.2). * Add watch file. Checksums-Sha1: d5be9efcad936c26eca853bfb4df69d1e9073b89 1097 remotefs_0.11+debian-3.dsc b4e086277e09cca16b5d944aa97e3ee1d3dd1e8b 4492 remotefs_0.11+debian-3.diff.gz 7b3b40225aaa56f100c176117474158c24f40470 36424 rfs-client_0.11+debian-3_i386.deb 66d1d60d0e61ba22890b22678e4228819ff0508d 36206 rfs-server_0.11+debian-3_i386.deb Checksums-Sha256: ee51fe4782ec76e687d34c2d1933dd10503db28994aa93483297b7979b84a3e6 1097 remotefs_0.11+debian-3.dsc 8b3034cc3ac6b2b634b460ea2ff1758cca2b732a0ab6238d88011bc1ddf27565 4492 remotefs_0.11+debian-3.diff.gz 511b7770269501fdf57a568cf2f004a9c53ac857abbdf54d4e474c3a1a7a67dd 36424 rfs-client_0.11+debian-3_i386.deb fd42bd49e6a764c1ccc598ddab3a0a30623c7f7320e63a4616ba3c960dbeb699 36206 rfs-server_0.11+debian-3_i386.deb Files: cedab4915bc91a140e3e12c8b274418c 1097 net optional remotefs_0.11+debian-3.dsc 100b192cd8dc8bc82d7f895065fbf685 4492 net optional remotefs_0.11+debian-3.diff.gz c776169fdf165e4f46623ae1ab3d953d 36424 net optional rfs-client_0.11+debian-3_i386.deb 9f0de34b4b68cac919d254bbfe481efb 36206 net optional rfs-server_0.11+debian-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAks0IvYACgkQ5ItltUs5T34ctACdHt+/EUjVLyjUMpzUrQJtDSS6 HRUAmgKfrJDE3t20gO9JwDoJYIaYabUA =cJeO -END PGP SIGNATURE- --- End Message ---
Bug#561491: FTBFS: IF_MASK undeclared
tag 561491 + patch thanks. -- Elías Alejandro Index: zhcon-0.2.6/src/display/lrmi.c === --- zhcon-0.2.6.orig/src/display/lrmi.c 2009-12-24 22:05:43.0 -0500 +++ zhcon-0.2.6/src/display/lrmi.c 2009-12-24 22:06:35.0 -0500 @@ -33,6 +33,13 @@ #include "lrmi.h" +#if defined(__linux__) && !defined(TF_MASK) + #define TF_MASK X86_EFLAGS_TF + #define IF_MASK X86_EFLAGS_IF + #define VIF_MASK X86_EFLAGS_VIF + #define IOPL_MASK X86_EFLAGS_IOPL +#endif + #define REAL_MEM_BASE ((void *)0x1) #define REAL_MEM_SIZE 0x1 #define REAL_MEM_BLOCKS 0x100
Processed: tagpending
Processing commands for cont...@bugs.debian.org: > #midori (0.2.2-1) UNRELEASED; urgency=low > # > # * move libjs-mootools to Recommends, it's not required (Closes: > ##547584) > # * tell the user to report the bug against libwebkit-1.0-2 if they > #reproduce it in the Webkit test browser. Figure out the package name > #and the path to GtkLauncher automagically during build. (Closes: > ##562501) > # * switch to system waf > #- the FTBFS #559989 is no longer the fault of anything in my package, > # and I've set #561130 in the BTS to affect midori, so (Closes: #559989) > # > limit source midori Limiting to bugs with field 'source' containing at least one of 'midori' Limit currently set to 'source':'midori' > tags 562501 + pending confirmed Bug #562501 [midori] midori: reportbug information is kind of misleading Added tag(s) confirmed and pending. > tags 547584 + pending confirmed Bug #547584 [midori] midori: look into libjs-mootools dependency Added tag(s) confirmed and pending. > tags 559989 + pending confirmed Bug #559989 [midori] FTBFS [hppa] - spinning waf process Added tag(s) confirmed and pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
Lucas Nussbaum wrote:
> On 24/12/09 at 13:02 -0500, Jeremy T. Bouse wrote:
>> Lucas Nussbaum wrote:
>>> On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote:
I suggest there might be something wrong with the amd64 build box
you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built
successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version
from the mirrors and rebuilt under a pbuilder chroot and it built
successfully as well. The -4 version of the package had a problem in the
debian/rules that caused this behavior but it was fixed in the -5 release.
>>> Could you please diff your log with mine, to see if the problem was
>>> possibly caused by different build-dep versions ?
>>>
>> I'm building on i386 as my amd64 boxes are currently still offline
>> along with my hppa and alpha machines. The official amd64 buildd I sent
>> the URL that was available for the log. When looking through it I didn't
>> see any failures. However that log format and your log format are
>> completely different and do not lend themselves to diff comparison.
>
> I'm talking about a build in an up-to-date sid chroot, not something
> that happened 10 days ago.
Here's the build for me... The source is from the mirror using dget and
not from the git repo [1] that it was originally built and submitted to
the mirror from. Prior to the build I did a 'pbuilder update' for
DIST=sid to ensure it was current.
Jeremy
[1] git://git.debian.org/collab-maint/libgcgi.git
I: using fakeroot in build.
I: Current time: Thu Dec 24 19:51:17 EST 2009
I: pbuilder-time-stamp: 1261702277
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/sid-i386-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: i386
Maintainer: Debian Pbuilder Team
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder and should
Depends: debhelper (>= 7), libssl-dev, dpatch
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in
`/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Reading package lists...
Building dependency tree...
Reading state information...
aptitude is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Selecting previously deselected package pbuilder-satisfydepends-dummy.
(Reading database ... 11014 files and directories currently installed.)
Unpacking pbuilder-satisfydepends-dummy (from
.../pbuilder-satisfydepends-dummy.deb) ...
dpkg: dependency problems prevent configuration of
pbuilder-satisfydepends-dummy:
pbuilder-satisfydepends-dummy depends on debhelper (>= 7); however:
Package debhelper is not installed.
pbuilder-satisfydepends-dummy depends on libssl-dev; however:
Package libssl-dev is not installed.
pbuilder-satisfydepends-dummy depends on dpatch; however:
Package dpatch is not installed.
dpkg: error processing pbuilder-satisfydepends-dummy (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pbuilder-satisfydepends-dummy
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
The following NEW packages will be installed:
bsdmainutils{a} debhelper{a} dpatch{a} file{a} gettext{a} gettext-base{a}
groff-base{a} html2text{a} intltool-debian{a} libcroco3{a}
libglib2.0-0{a} libmagic1{a} libpcre3{a} libssl-dev{a} libssl0.9.8{a}
libxml2{a} man-db{a} po-debconf{a} zlib1g-dev{a}
The following partially installed packages will be configured:
pbuilder-satisfydepends-dummy
0 packages upgraded, 19 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/13.8MB of archives. After unpacking 38.5MB will be used.
Writing extended state information...
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously deselected package libmagic1.
(Reading database ... 11014 files and directories currently installed.)
Unpacking libmagic1 (from .../libmagic1_5.03-5_i386.deb) ...
Selecting previously deselected package file.
Unpacking file (from .../archives/file_5.03-5_i386.deb) ...
Selecting previously deselected package html2text.
Unpacking html2text (from .../html2text_1.3.2a-14_i386.deb) ...
Selecting previously deselected package libpcre3.
Unpacking libpcre3 (from .../libpcre3_7.8-3_i386.deb) ...
Selecting previously deselected package libglib2.0-0.
Unpacking libglib2.0-0 (from .../libglib2.0-0_2.22.3-2_i386.deb) ...
Selecting previously deselected package libxml2.
Unpackin
Processed: Re: Bug#562292: ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef
Processing commands for cont...@bugs.debian.org: > tags 562292 -unreproducible -moreinfo Bug #562292 [src:ltp] ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef Removed tag(s) unreproducible. Bug #562292 [src:ltp] ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef Removed tag(s) moreinfo. > severity 562292 normal Bug #562292 [src:ltp] ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef Severity set to 'normal' from 'serious' > retitle 562292 parallel build is broken Bug #562292 [src:ltp] ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef Changed Bug title to 'parallel build is broken' from 'ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562358: mpost returns 1 on successful run?
Hi Taco,
on the Debian side we got a bug report that with the switch from
TL2007 mpost to TL2009 mpost the same file suddenly makes mpost
return 1 (failure in shell) instead of 0.
On Do, 24 Dez 2009, Stéphane Glondu wrote:
> This is because of mpost. With the attached file, mpost exists with code
> 1; however, I don't see any error:
>
> r...@korell:/tmp# mpost -interaction="nonstopmode" img_doc.mp end
> This is MetaPost, version 1.208 (kpathsea version 5.0.0)
> (./img_doc.mp (/usr/share/texmf/metapost/context/base/mp-tool.mp)
> (/usr/share/texmf/metapost/context/base/mp-spec.mp) [19] [18] [17] [16] [15]
> [14] [13] [12] [11] [10] [9] [8] [7] [6] [5] [4] [3] [2] [1])
> (see the transcript file for additional information)
> 19 output files written: img_doc.1 .. img_doc.19
> Transcript written on img_doc.log.
> r...@korell:/tmp# echo $?
> 1
>
> The version in testing exits with code 0 on the same file.
Version in testing is 2007.
It turned out that the the following line
tracingchoices := 1;
seems to made the difference. When I comment that mpost returns 0,
otherwise on. The following minimal mp file exhibits this point:
tracingchoices := 1;
beginfig(1)
path pathb ;
pathb = ((0, 0) .. (40, 25));
endfig;
end.
With tracingchoices == 1 mpost returns 1, otherwise 0.
Simple question: Is that intended or a bug? I checked the current
mpman but there is nothing mentioned about return values around
the tracing* pages.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
WIKE (vb.)
To rip a piece of sticky plaster off your skin as fast as possible in
the hope that it will (a) show how brave you are, and (b) not hurt.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562358: mlpost: FTBFS: mkdir -p img/ fails?
On Do, 24 Dez 2009, Stéphane Glondu wrote:
> Do texlive-metapost maintainers have a clue?
Do *not* set
tracing_choices := 1;
that is the reason 1 is returned. I will ask Taco if that is intended,
but an easy fix for you is simply do NOT include the above line.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
ARDSCALPSIE (n.)
Excuse made by rural Welsh hairdresser for completely massacring your
hair.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562364: transfig: FTBFS: ! LaTeX Error: File `_fig2mpdfoverlay-sample-4_inp000' not found.
On Thu, 24 Dec 2009, Lucas Nussbaum wrote: > Source: transfig > Version: 1:3.2.5.a-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091213 qa-ftbfs > Justification: FTBFS on amd64 > During a rebuild of all packages in sid, your package failed to > build on amd64. After some debugging I found out that this seems to be caused by a broken behavior of epstopdf (it cannot be used as a filter in the current sid version but returns an error). See my bug report #562497 about this issue. I hope that this bug will be fixed soon, otherwise I'll have to write a workaround for transfig to use a temporary file instead of using the pipe, which I'd like to avoid. Tscho Roland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#558981: marked as done (FTBFS [hppa] - Test 'basic_watch_info' failed)
Your message dated Thu, 24 Dec 2009 23:17:10 + with message-id and subject line Bug#558981: fixed in inotify-tools 3.13-3 has caused the Debian Bug report #558981, regarding FTBFS [hppa] - Test 'basic_watch_info' failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 558981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: inotify-tools Version: 3.13-2 Severity: serious User: debian-h...@lists.debian.org Usertags: hppa inotify-tools_3.13-2 reliably fails to build on hppa: https://buildd.debian.org/build.php?&pkg=inotify-tools&ver=3.13-2&arch=hppa&file=log >From the most recent build attempt: [...] creating test make[5]: Leaving directory `/build/buildd/inotify-tools-3.13/libinotifytools/src' make check-TESTS make[5]: Entering directory `/build/buildd/inotify-tools-3.13/libinotifytools/src' make[6]: Entering directory `/build/buildd/inotify-tools-3.13' make[6]: Leaving directory `/build/buildd/inotify-tools-3.13' test.c:173 Test 'basic_watch_info' failed: Actual (inotifytools_wd_from_filename( "/" )): 1, Expected (2): 2 If you want to do a malloc trace, set MALLOC_TRACE to a path for logging. event_to_str: test begin event_to_str: test end event_to_str_sep: test begin event_to_str_sep: test end str_to_event: test begin str_to_event: test end str_to_event_sep: test begin str_to_event_sep: test end basic_watch_info: test begin watch_limit: test begin watch_limit: Warning, this test may take a while watch_limit: test end tst_inotifytools_snprintf: test begin tst_inotifytools_snprintf: test end Out of 362951 tests, 362950 succeeded and 1 failed. FAIL: test = 1 of 1 tests failed Please report to ro...@mcgovern.id.au = make[5]: *** [check-TESTS] Error 1 make[5]: Leaving directory `/build/buildd/inotify-tools-3.13/libinotifytools/src' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/build/buildd/inotify-tools-3.13/libinotifytools/src' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/build/buildd/inotify-tools-3.13/libinotifytools/src' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/build/buildd/inotify-tools-3.13/libinotifytools' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/build/buildd/inotify-tools-3.13' dh_auto_test: make -j1 check returned exit code 2 make: *** [build] Error 9 dpkg-buildpackage: error: debian/rules build gave error exit status 2 --- End Message --- --- Begin Message --- Source: inotify-tools Source-Version: 3.13-3 We believe that the bug you reported is fixed in the latest version of inotify-tools, which is due to be installed in the Debian FTP archive: inotify-tools_3.13-3.diff.gz to main/i/inotify-tools/inotify-tools_3.13-3.diff.gz inotify-tools_3.13-3.dsc to main/i/inotify-tools/inotify-tools_3.13-3.dsc inotify-tools_3.13-3_i386.deb to main/i/inotify-tools/inotify-tools_3.13-3_i386.deb libinotifytools0-dev_3.13-3_i386.deb to main/i/inotify-tools/libinotifytools0-dev_3.13-3_i386.deb libinotifytools0_3.13-3_i386.deb to main/i/inotify-tools/libinotifytools0_3.13-3_i386.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 558...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ryan Niebur (supplier of updated inotify-tools 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: Thu, 24 Dec 2009 13:31:36 -0800 Source: inotify-tools Binary: libinotifytools0 libinotifytools0-dev inotify-tools Architecture: source i386 Version: 3.13-3 Distribution: unstable Urgency: low Maintainer: Ryan Niebur Changed-By: Ryan Niebur Description: inotify-tools - command-line programs providing a simple interface to inotify libinotifytools0 - utility wrapper around inotify libinotifytools0-dev - Development library and header files for libinotifytools0 Closes: 558981 Changes: inotify-tools (3.13-3) unstable; urgency=low . * fix FTBFS by fixing the tests to not make bad assumptions (Closes: #558981) * prevent segfault in csv mode when there's no filename associated with the watch descriptor (LP: #408805) * update
Processed: tagging 561629
Processing commands for cont...@bugs.debian.org: > tags 561629 + patch Bug #561629 [gnome-office] gnome-office: uninstallable in sid Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561629: gnome-office: uninstallable in sid
On Fri, Dec 18, 2009 at 09:50:44PM +0100, Laurent Bonnaud wrote: > The following packages have unmet dependencies: > gnome-office: Depends: abiword-plugin-goffice (>= 2.6) but it is not > installable Sorry for not giving an advance notice. The goffice plugin is now shipped in the "abiword" binary package, so you should probably just depend on abiword (>= 2.8) instead. Kind regards, Patrik Fimml (abiword maintainer) signature.asc Description: Digital signature
Bug#562292: ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef
On 24/12/09 at 22:09 +0100, Jiří Paleček wrote: > On Thu, 24 Dec 2009 18:43:13 +0100, Lucas Nussbaum > wrote: > > >On 24/12/09 at 16:38 +0100, Jiří Paleček wrote: > >>tags 562292 +moreinfo +unreproducible > >> > >>On Thu, 24 Dec 2009 11:25:35 +0100, Lucas Nussbaum > >> wrote: > >> > >>>Source: ltp > >>>Version: 20091031+dfsg-2 > >>>Severity: serious > >>>User: debian...@lists.debian.org > >>>Usertags: qa-ftbfs-20091213 qa-ftbfs > >>>Justification: FTBFS on amd64 > >>> > >>>Hi, > >>> > >>>During a rebuild of all packages in sid, your package failed to > >>build on > >>>amd64. > >>> > >>>Relevant part: > cc -g -O2 -g -Wall -O2 -g -O2 -fno-strict-aliasing -pipe -Wall > -I/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include > -I../../../../include -I../../../../include -c -o netsync.o > netsync.c > In file included from libcpuset.c:51: > /build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:32:1: > error: unterminated #ifdef > /build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:13:1: > error: unterminated #ifndef > OK! > make[6]: *** [libcpuset.o] Error 1 > >>> > >>>The full build log is available from: > >>> > >>> http://people.debian.org/~lucas/logs/2009/12/13/ltp_20091031+dfsg-2_lsid64.buildlog > >>> > >>>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. > >>> > >> > >>Could you please upload the file in question or the whole build tree > >>after a failed build somewhere? I can't figure out what's the > >>problem, and the official buildds seem to handle it: > >>https://buildd.debian.org/fetch.cgi?pkg=ltp&arch=amd64&ver=20091031%2Bdfsg-2&stamp=1261520305&file=log&as=raw > > > >Have you tried building it before saying it's unreproducible? > > Well, since I have no amd64 machine, no. > > >Could you please provide a diff of your log with mine, to exclude a > >problem with build-dependencies? > > Well, I think you could make one yourself (it's not "my log", it's > the official buildd log). I'm looking at it in xxdiff and (apart > from loads of different directory names etc.) it seems your log has > libpcre3 installed (not sure how this could hurt), and the official > buildd has this: > > In file "/tmp/fetch.log": > -- > 42: The following packages were automatically installed and are no > longer required: > 43: libkrb5-3 libk5crypto3 ttf-dejavu-extra libdes425-3 > ttf-dejavu-core g++-4.3 > 44: libfreetype6 libexpat1 libkrb53 fontconfig libkrb5support0 > fontconfig-config > 45: libkeyutils1 ucf libstdc++6-4.3-dev ttf-dejavu libfontconfig1 > 46: libgssapi-krb5-2 perl-doc > 47: Use 'apt-get autoremove' to remove them. > > However, from your log, it seems you were doing a parallel build. > Tell me if this is the case, and if yes, tell me parallel=how_much > did you use. (I did test with parallel=3 and never came across > this). > > It could be the case that parallel build is broken. parallel=8. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagpending
Processing commands for cont...@bugs.debian.org: > #inotify-tools (3.13-3) UNRELEASED; urgency=low > # > # * fix FTBFS by fixing the tests to not make bad assumptions (Closes: > ##558981) > # > limit source inotify-tools Limiting to bugs with field 'source' containing at least one of 'inotify-tools' Limit currently set to 'source':'inotify-tools' > tags 558981 + pending confirmed Bug #558981 [inotify-tools] FTBFS [hppa] - Test 'basic_watch_info' failed Added tag(s) confirmed and pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499740: marked as done (libwx-perl - FTBFS: Failed 2/4 test scripts. 6/9 subtests failed.)
Your message dated Thu, 24 Dec 2009 21:18:54 + with message-id and subject line Bug#499740: fixed in libwx-perl 0.94-1 has caused the Debian Bug report #499740, regarding libwx-perl - FTBFS: Failed 2/4 test scripts. 6/9 subtests failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 499740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwx-perl Version: 0.86-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of libwx-perl_0.86-1 on lxdebian.bfinv.de by sbuild/s390 98 [...] > make[4]: Entering directory > `/build/buildd/libwx-perl-0.86/ext/pperl/splashfast' > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, '../../../blib/lib', '../../../blib/arch')" t/*.t > t/01_loadok > t/02_use.dubious > Test returned status 0 (wstat 11, 0xb) > DIED. FAILED test 1 > Failed 1/1 tests, 0.00% okay > t/03_new.ok > t/04_app.dubious > Test returned status 0 (wstat 11, 0xb) > DIED. FAILED tests 1-5 > Failed 5/5 tests, 0.00% okay > Failed Test Stat Wstat Total Fail List of Failed > --- > t/02_use.t 011 12 1 > t/04_app.t 011 5 10 1-5 > Failed 2/4 test scripts. 6/9 subtests failed. > Files=4, Tests=9, 7 wallclock secs ( 4.67 cusr + 0.19 csys = 4.86 CPU) > Failed 2/4 test programs. 6/9 subtests failed. > make[4]: *** [test_dynamic] Error 255 > make[4]: Leaving directory > `/build/buildd/libwx-perl-0.86/ext/pperl/splashfast' > make[3]: *** [subdirs-test] Error 2 > make[3]: Leaving directory `/build/buildd/libwx-perl-0.86/ext/pperl' > make[2]: *** [subdirs-test] Error 2 > make[2]: Leaving directory `/build/buildd/libwx-perl-0.86/ext' > make[1]: *** [subdirs-test] Error 2 > make[1]: Leaving directory `/build/buildd/libwx-perl-0.86' > make: *** [build-stamp] Error 2 > dpkg-buildpackage: failure: debian/rules build gave error exit status 2 > ** > Build finished at 20080918-1433 > FAILED [dpkg-buildpackage died] --- End Message --- --- Begin Message --- Source: libwx-perl Source-Version: 0.94-1 We believe that the bug you reported is fixed in the latest version of libwx-perl, which is due to be installed in the Debian FTP archive: libwx-perl_0.94-1.diff.gz to main/libw/libwx-perl/libwx-perl_0.94-1.diff.gz libwx-perl_0.94-1.dsc to main/libw/libwx-perl/libwx-perl_0.94-1.dsc libwx-perl_0.94-1_i386.deb to main/libw/libwx-perl/libwx-perl_0.94-1_i386.deb libwx-perl_0.94.orig.tar.gz to main/libw/libwx-perl/libwx-perl_0.94.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 499...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ryan Niebur (supplier of updated libwx-perl 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: Thu, 24 Dec 2009 12:23:28 -0800 Source: libwx-perl Binary: libwx-perl Architecture: source i386 Version: 0.94-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group Changed-By: Ryan Niebur Description: libwx-perl - interface to wxWidgets cross-platform GUI toolkit Closes: 499740 Changes: libwx-perl (0.94-1) unstable; urgency=low . [ Roberto C. Sanchez ] * New upstream release . [ Ryan Niebur ] * remove wrap_get_raw_keycode.patch, applied upstream * skip the failing tests (Closes: #499740) Checksums-Sha1: 0caf11de348031ceb4b51881f3be1d8cbe032a3e 1481 libwx-perl_0.94-1.dsc b1f73eef0caf477db62c016e4463baa2f7e4e601 353476 libwx-perl_0.94.orig.tar.gz 236a2927ff84e89ca1b89b7f0d73027856d725cb 4114 libwx-perl_0.94-1.diff.gz a24171c8df642c3b6b38c8aeca031a023412cff9 1821594 libwx-perl_0.94-1_i386.deb Checksums-Sha256: 8e2bf4f81318f644ee4bd2f073a49d2cdb67a2f48152747fac75c0d70e5d495c 1481 libwx-perl_0.94-1.dsc fb610f64f12c80b482257ce0ed346f7506695d83e13b344481546a5170059153 353476 libwx-perl_0.94.orig.tar.gz 6b9490c3ff676ecc6668a3790d52cb5ec11d736a3f8e05387ba2246390aa7547 4114 libwx-perl_0.94-1.diff.gz 7ca40ecf020c82640059a7fd01b4ce3d70c22b65c5f26
Bug#561946: marked as done (ERROR: No suitable version found for Drupal 6 (level>=recommended))
Your message dated Thu, 24 Dec 2009 21:17:24 + with message-id and subject line Bug#561946: fixed in dh-make-drupal 0.5-1 has caused the Debian Bug report #561946, regarding ERROR: No suitable version found for Drupal 6 (level>=recommended) 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.) -- 561946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dh-make-drupal Version: 0.4-2 Severity: grave Justification: renders package unusable When I run dh-make-drupal on any of about a dozen modules, I get the error message from the subject above. In fact, I'm currently not aware of a module that still works. The script used to work just fine on this very same system (same configuration, same version), so I suspect the drupal website / HTML changed, and then the dh-make-drupal parser fails to find the metainfo. Example packages include "bot" and "cck". -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (996, 'stable'), (991, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dh-make-drupal depends on: ii libcommandline-ruby 0.7.10-10 Ruby library to write command-line ii libhpricot-ruby 0.6-2 A fast, enjoyable HTML parser ii libruby 4.2Libraries necessary to run Ruby 1. ii ruby 4.2An interpreter of object-oriented dh-make-drupal recommends no packages. Versions of packages dh-make-drupal suggests: ii drupal6 6.6-3lenny3 a fully-featured content managemen -- no debconf information --- End Message --- --- Begin Message --- Source: dh-make-drupal Source-Version: 0.5-1 We believe that the bug you reported is fixed in the latest version of dh-make-drupal, which is due to be installed in the Debian FTP archive: dh-make-drupal_0.5-1.diff.gz to main/d/dh-make-drupal/dh-make-drupal_0.5-1.diff.gz dh-make-drupal_0.5-1.dsc to main/d/dh-make-drupal/dh-make-drupal_0.5-1.dsc dh-make-drupal_0.5-1_all.deb to main/d/dh-make-drupal/dh-make-drupal_0.5-1_all.deb dh-make-drupal_0.5.orig.tar.gz to main/d/dh-make-drupal/dh-make-drupal_0.5.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 561...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Wolf (supplier of updated dh-make-drupal 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: Thu, 24 Dec 2009 13:50:05 -0600 Source: dh-make-drupal Binary: dh-make-drupal Architecture: source all Version: 0.5-1 Distribution: unstable Urgency: low Maintainer: Gunnar Wolf Changed-By: Gunnar Wolf Description: dh-make-drupal - Create Debian packages from Drupal modules and themes Closes: 561946 Changes: dh-make-drupal (0.5-1) unstable; urgency=low . * New upstream release (Closes: #561946) Checksums-Sha1: 5f65775d72fe296574cc7621c7d57b27bcfcb285 1841 dh-make-drupal_0.5-1.dsc e627fd33d1fc69c5b8a9c5bcd01691e0d5241342 24868 dh-make-drupal_0.5.orig.tar.gz 6fd1106e266b7aea9e61ec5c26141203408ef820 1850 dh-make-drupal_0.5-1.diff.gz 578bfe3fda9eb334874688844934cc67d585167c 17956 dh-make-drupal_0.5-1_all.deb Checksums-Sha256: 7a452d69a5213407f0d6398d05c7c381a72ca3e65df26a5b2dd77d2392600a08 1841 dh-make-drupal_0.5-1.dsc 01c3294a511d969854adde72d7624ba30e28560fcfd79bf8ec1a3c0e181b5d59 24868 dh-make-drupal_0.5.orig.tar.gz 1a5208fc55911465ff985725d18120e848cfd0785577f77203d3686b1d7966ed 1850 dh-make-drupal_0.5-1.diff.gz b6198797386547ad48e3f03ca1007a58bed09b9df45d625e095dfd1079523f3a 17956 dh-make-drupal_0.5-1_all.deb Files: 7dd956bc9eec943312bbc5a72871f42d 1841 web extra dh-make-drupal_0.5-1.dsc a36c1bb2827e84f32cdc78ca82f76c08 24868 web extra dh-make-drupal_0.5.orig.tar.gz 3043f1ec45dda759303e968e9fdb53e8 1850 web extra dh-make-drupal_0.5-1.diff.gz 95bb89628bbf7a4afd0baa8af5eb7d31 17956 web extra dh-make-drupal_0.5-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJLM8a8AAoJEGc6A+TB25IfJiMP/36hLxa2M
Bug#562492: zhone: Package is not installable
Package: zhone Version: 0-git20090610-5 Severity: serious Justification: Not installable Zhone depends on libevas-svn-03-engines-x which is not available anymore. Updating zhone to depend on libevas-svn-05-engines-x instead should solve this problem. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30.5 Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Bug in libwx-perl fixed in revision 49344
Processing commands for cont...@bugs.debian.org: > tag 499740 + pending Bug #499740 [libwx-perl] libwx-perl - FTBFS: Failed 2/4 test scripts. 6/9 subtests failed. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499740: Bug in libwx-perl fixed in revision 49344
tag 499740 + pending thanks Some bugs are closed in revision 49344 by Ryan Niebur (ryan) Commit message: skip the failing tests (Closes: #499740) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562292: ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef
On Thu, 24 Dec 2009 18:43:13 +0100, Lucas Nussbaum wrote: On 24/12/09 at 16:38 +0100, Jiří Paleček wrote: tags 562292 +moreinfo +unreproducible On Thu, 24 Dec 2009 11:25:35 +0100, Lucas Nussbaum wrote: >Source: ltp >Version: 20091031+dfsg-2 >Severity: serious >User: debian...@lists.debian.org >Usertags: qa-ftbfs-20091213 qa-ftbfs >Justification: FTBFS on amd64 > >Hi, > >During a rebuild of all packages in sid, your package failed to build on >amd64. > >Relevant part: >>cc -g -O2 -g -Wall -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include >>-I../../../../include -I../../../../include -c -o netsync.o >>netsync.c >>In file included from libcpuset.c:51: >>/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:32:1: >>error: unterminated #ifdef >>/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:13:1: >>error: unterminated #ifndef >>OK! >>make[6]: *** [libcpuset.o] Error 1 > >The full build log is available from: > http://people.debian.org/~lucas/logs/2009/12/13/ltp_20091031+dfsg-2_lsid64.buildlog > >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. > Could you please upload the file in question or the whole build tree after a failed build somewhere? I can't figure out what's the problem, and the official buildds seem to handle it: https://buildd.debian.org/fetch.cgi?pkg=ltp&arch=amd64&ver=20091031%2Bdfsg-2&stamp=1261520305&file=log&as=raw Have you tried building it before saying it's unreproducible? Well, since I have no amd64 machine, no. Could you please provide a diff of your log with mine, to exclude a problem with build-dependencies? Well, I think you could make one yourself (it's not "my log", it's the official buildd log). I'm looking at it in xxdiff and (apart from loads of different directory names etc.) it seems your log has libpcre3 installed (not sure how this could hurt), and the official buildd has this: In file "/tmp/fetch.log": -- 42: The following packages were automatically installed and are no longer required: 43: libkrb5-3 libk5crypto3 ttf-dejavu-extra libdes425-3 ttf-dejavu-core g++-4.3 44: libfreetype6 libexpat1 libkrb53 fontconfig libkrb5support0 fontconfig-config 45: libkeyutils1 ucf libstdc++6-4.3-dev ttf-dejavu libfontconfig1 46: libgssapi-krb5-2 perl-doc 47: Use 'apt-get autoremove' to remove them. However, from your log, it seems you were doing a parallel build. Tell me if this is the case, and if yes, tell me parallel=how_much did you use. (I did test with parallel=3 and never came across this). It could be the case that parallel build is broken. Regards Jiri Palecek -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526155: subtitleeditor: diff for NMU version 0.30.0-1.1
Hi again. Of course the upload depend of I could find an sponsor for upload the package. Unfortunately I'm a simple mantainer. Could be more time. Regards. >> I was preparing a upload with the new releasese 0.34 for this weekend. >> I would like to wait for the new package instead this NMU. > > cool! I've canceled the upload -- Anibal Avelar (FixXxeR) http://fixxxer.cc GPG: 83B64656 - C143 4AD8 B017 53FA B742 D6AA CEEA F9F3 83B6 4656 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548434: [Fdutils] Cannot format floppies under kernel 2.6.*?
I have the same problem. And my guess is that it has to do something with the new south bridge over PCI floppy controllers. It's the same problem with the onboard PCI ac97 sound support. I think that the hardware and kernel resources gets overloaded or miss configured. Maybe there are also BIOS bugs in the ACPI support. It's a new thing for the motherboard envelopers and BIOS programmers (about only 6 or 8 years). So on some motherboards it could work well. So I think the kernel should get a ACPI correction layer so an AML, ASL debugger. ACPI wiki: http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface or more detailed in german: http://de.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface I did test it with fdformat and superformat on different drives also with jumpers and both prints different errors. Sometimes fdformat did get 1% formated and did break then with an ioctl error. I also think and it seams so too that data reaches the drive in a non continous way with very large delays between. Maybe a buffered DMA to PCI support for the controller could solve this problem and the module don't have to write to the drive directly, only to that buffer. Reading is no problem, the system does mount FDs and files can also be opened but writing to FDs fails. Datasheet for the Southbridge AMD SB600 is at: http://support.amd.com/us/Embedded_TechDocs/42119_sb600_ds_pub_3.07.pdf And how to handle it (should be handled from BIOS) is at: http://support.amd.com/us/Embedded_TechDocs/46157_sb600_bdg_pub.3.00.pdf like many other resources also at: http://www.coreboot.org/Datasheets It's ironic, because I just wanted to make a BIOS update because of its ACPI errors and the only way it works for me is the floppy drive (BIOS internal burn programm). Now it could be the BIOS ACPI setup itself why it doesn't work. Damn! Bastl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562282: marked as done (mono-debugger: FTBFS: /bin/bash: /usr/bin/csc: No such file or directory)
Your message dated Thu, 24 Dec 2009 18:48:11 + with message-id and subject line Bug#562282: fixed in mono-debugger 2.4.3-1 has caused the Debian Bug report #562282, regarding mono-debugger: FTBFS: /bin/bash: /usr/bin/csc: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 562282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mono-debugger Version: 2.4.2-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091213 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. >From mono-devel's changelog: + Dropped /usr/bin/csc as it was causing a file conflict with the chicken compiler from the chicken-bin package. Most source packages were transitioned to use /usr/bin/mono-csc or /usr/bin/cli-csc instead. (Closes: #509367, #518106) Relevant part: > make[4]: Entering directory > `/build/user-mono-debugger_2.4.2-2-amd64-O1gXSt/mono-debugger-2.4.2/test/src' > gcc -DHAVE_CONFIG_H -I. -I../.. -DTEST_SRCDIR=\"../../test/src\" > -DTEST_BUILDDIR=\"`pwd`\" -g -O0 -MT testnativefork.o -MD -MP -MF > .deps/testnativefork.Tpo -c -o testnativefork.o testnativefork.c > mv -f .deps/testnativefork.Tpo .deps/testnativefork.Po > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O0-o > testnativefork testnativefork.o > libtool: link: gcc -g -O0 -o testnativefork testnativefork.o > gcc -DHAVE_CONFIG_H -I. -I../.. -DTEST_SRCDIR=\"../../test/src\" > -DTEST_BUILDDIR=\"`pwd`\" -g -O0 -MT testnativeexec.o -MD -MP -MF > .deps/testnativeexec.Tpo -c -o testnativeexec.o testnativeexec.c > mv -f .deps/testnativeexec.Tpo .deps/testnativeexec.Po > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O0-o > testnativeexec testnativeexec.o > libtool: link: gcc -g -O0 -o testnativeexec testnativeexec.o > gcc -DHAVE_CONFIG_H -I. -I../.. -DTEST_SRCDIR=\"../../test/src\" > -DTEST_BUILDDIR=\"`pwd`\" -g -O0 -MT testnativechild.o -MD -MP -MF > .deps/testnativechild.Tpo -c -o testnativechild.o testnativechild.c > mv -f .deps/testnativechild.Tpo .deps/testnativechild.Po > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O0-o > testnativechild testnativechild.o > libtool: link: gcc -g -O0 -o testnativechild testnativechild.o > gcc -DHAVE_CONFIG_H -I. -I../.. -DTEST_SRCDIR=\"../../test/src\" > -DTEST_BUILDDIR=\"`pwd`\" -g -O0 -MT testnativeattach.o -MD -MP -MF > .deps/testnativeattach.Tpo -c -o testnativeattach.o testnativeattach.c > mv -f .deps/testnativeattach.Tpo .deps/testnativeattach.Po > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O0-o > testnativeattach testnativeattach.o > libtool: link: gcc -g -O0 -o testnativeattach testnativeattach.o > gcc -DHAVE_CONFIG_H -I. -I../.. -DTEST_SRCDIR=\"../../test/src\" > -DTEST_BUILDDIR=\"`pwd`\" -g -O0 -MT testnativetypes.o -MD -MP -MF > .deps/testnativetypes.Tpo -c -o testnativetypes.o testnativetypes.c > mv -f .deps/testnativetypes.Tpo .deps/testnativetypes.Po > /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O0-o > testnativetypes testnativetypes.o > libtool: link: gcc -g -O0 -o testnativetypes testnativetypes.o > /usr/bin/csc -debug -unsafe -out:TestManagedTypes.exe TestManagedTypes.cs > /bin/bash: /usr/bin/csc: No such file or directory > make[4]: *** [TestManagedTypes.exe] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/13/mono-debugger_2.4.2-2_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: mono-debugger Source-Version: 2.4.3-1 We believe that the bug you reported is fixed in the latest version of mono-debugger, which is due to be installed in the Debian FTP archive: mono-debugger_2.4.3-1.diff.gz to main/m/mono-debugger/mono-debugger_2.4.3-1.diff.gz mono-debugger_2.4.3-1.dsc to main/m/mono-debugger/mono-debugger_2.4.3-1.dsc mono-debugger_2.4.3-1_amd64.deb to main/m/mono-debugger/mono-debugger_2.4.3-1_amd64.deb mono-debugger_2.4.3.orig.tar.gz to main/m/mono-debugge
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
On 24/12/09 at 13:02 -0500, Jeremy T. Bouse wrote: > Lucas Nussbaum wrote: > > On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: > >>I suggest there might be something wrong with the amd64 build box > >> you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built > >> successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version > >> from the mirrors and rebuilt under a pbuilder chroot and it built > >> successfully as well. The -4 version of the package had a problem in the > >> debian/rules that caused this behavior but it was fixed in the -5 release. > > > > Could you please diff your log with mine, to see if the problem was > > possibly caused by different build-dep versions ? > > > I'm building on i386 as my amd64 boxes are currently still offline > along with my hppa and alpha machines. The official amd64 buildd I sent > the URL that was available for the log. When looking through it I didn't > see any failures. However that log format and your log format are > completely different and do not lend themselves to diff comparison. I'm talking about a build in an up-to-date sid chroot, not something that happened 10 days ago. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | signature.asc Description: Digital signature
Bug#561131: marked as done (require 'csnd' fails, missing extern "C")
Your message dated Thu, 24 Dec 2009 18:32:31 + with message-id and subject line Bug#561131: fixed in csound 1:5.11.1~dfsg-3 has caused the Debian Bug report #561131, regarding require 'csnd' fails, missing extern "C" 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.) -- 561131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: liblua5.1-csnd Version: 1:5.11.1~dfsg-2 Severity: grave ta...@birba:/tmp$ lua Lua 5.1.4 Copyright (C) 1994-2008 Lua.org, PUC-Rio > require 'csnd' error loading module 'csnd' from file '/usr/lib/lua/5.1/csnd.so': /usr/lib/lua/5.1/csnd.so: undefined symbol: luaopen_csnd stack traceback: [C]: ? [C]: in function 'require' stdin:1: in main chunk [C]: ? > If we look at objdump: ta...@birba:/tmp$ objdump -T /usr/lib/lua/5.1/csnd.so | grep luaopen 00017880 gDF .text 00b7 Base _Z20luaopen_luaCsnd_userP9lua_State 002a0a60 gDO .data 0008 Base luaopen_luaCsnd_luacode 00019560 gDF .text 0dc4 Baseluaopen_luaCsnd It seems some extern "C" directives are missing, since symbols names are mangled according to C++ conventions, while Lua expects the entrypoint to be called luaopen_csnd. Cheers -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liblua5.1-csnd depends on: ii libc62.10.2-2GNU C Library: Shared libraries ii libcsnd5.2 1:5.11.1~dfsg-2 C++ bindings for the Csound API ii libcsound64-5.2 1:5.11.1~dfsg-2 main library for Csound ii libgcc1 1:4.4.2-5 GCC support library ii liblua5.1-0 5.1.4-6 Simple, extensible, embeddable pro ii libstdc++6 4.4.2-5 The GNU Standard C++ Library v3 liblua5.1-csnd recommends no packages. liblua5.1-csnd suggests no packages. -- no debconf information -- Enrico Tassi --- End Message --- --- Begin Message --- Source: csound Source-Version: 1:5.11.1~dfsg-3 We believe that the bug you reported is fixed in the latest version of csound, which is due to be installed in the Debian FTP archive: csladspa_5.11.1~dfsg-3_amd64.deb to main/c/csound/csladspa_5.11.1~dfsg-3_amd64.deb csound-gui_5.11.1~dfsg-3_amd64.deb to main/c/csound/csound-gui_5.11.1~dfsg-3_amd64.deb csound-utils_5.11.1~dfsg-3_amd64.deb to main/c/csound/csound-utils_5.11.1~dfsg-3_amd64.deb csound_5.11.1~dfsg-3.debian.tar.gz to main/c/csound/csound_5.11.1~dfsg-3.debian.tar.gz csound_5.11.1~dfsg-3.dsc to main/c/csound/csound_5.11.1~dfsg-3.dsc csound_5.11.1~dfsg-3_amd64.deb to main/c/csound/csound_5.11.1~dfsg-3_amd64.deb libcsnd-dev_5.11.1~dfsg-3_all.deb to main/c/csound/libcsnd-dev_5.11.1~dfsg-3_all.deb libcsnd-java_5.11.1~dfsg-3_amd64.deb to main/c/csound/libcsnd-java_5.11.1~dfsg-3_amd64.deb libcsnd5.2_5.11.1~dfsg-3_amd64.deb to main/c/csound/libcsnd5.2_5.11.1~dfsg-3_amd64.deb libcsound64-5.2_5.11.1~dfsg-3_amd64.deb to main/c/csound/libcsound64-5.2_5.11.1~dfsg-3_amd64.deb libcsound64-dev_5.11.1~dfsg-3_all.deb to main/c/csound/libcsound64-dev_5.11.1~dfsg-3_all.deb libcsound64-doc_5.11.1~dfsg-3_all.deb to main/c/csound/libcsound64-doc_5.11.1~dfsg-3_all.deb libcsoundac-dev_5.11.1~dfsg-3_all.deb to main/c/csound/libcsoundac-dev_5.11.1~dfsg-3_all.deb libcsoundac5.2_5.11.1~dfsg-3_amd64.deb to main/c/csound/libcsoundac5.2_5.11.1~dfsg-3_amd64.deb liblua5.1-luacsnd5.2_5.11.1~dfsg-3_amd64.deb to main/c/csound/liblua5.1-luacsnd5.2_5.11.1~dfsg-3_amd64.deb pd-csound_5.11.1~dfsg-3_amd64.deb to main/c/csound/pd-csound_5.11.1~dfsg-3_amd64.deb python-csound_5.11.1~dfsg-3_amd64.deb to main/c/csound/python-csound_5.11.1~dfsg-3_amd64.deb python-csoundac_5.11.1~dfsg-3_amd64.deb to main/c/csound/python-csoundac_5.11.1~dfsg-3_amd64.deb tclcsound_5.11.1~dfsg-3_amd64.deb to main/c/csound/tclcsound_5.11.1~dfsg-3_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 561...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaar
Bug#526155: subtitleeditor: diff for NMU version 0.30.0-1.1
On Thu, Dec 24, 2009 at 12:02:18PM -0600, Anibal Avelar wrote: > Hi. > > I was preparing a upload with the new releasese 0.34 for this weekend. > I would like to wait for the new package instead this NMU. cool! I've canceled the upload enjoy, filippo -- Filippo Giunchedi - http://esaurito.net - 0x6B79D401 When I was young I observed that nine out of every ten things I did were failures, so I did ten times more work. -- George Bernard Shaw -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562444: monkeysphere: FTBFS: ./tests/basic: line 202: cpio: command not found
On Thu, Dec 24, 2009 at 05:39:59PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. Thank you very much for this report, Lucas. I have added cpio to the Build-Depends, so this should be resolved on the next upload. jamie. signature.asc Description: Digital signature
Bug#526155: subtitleeditor: diff for NMU version 0.30.0-1.1
Hi. I was preparing a upload with the new releasese 0.34 for this weekend. I would like to wait for the new package instead this NMU. Thank you. Regards. On Thu, Dec 24, 2009 at 7:49 AM, Filippo Giunchedi wrote: > tag 526155 + pending > thanks > > Dear maintainer, > > I've prepared an NMU for subtitleeditor (versioned as 0.30.0-1.1) and > uploaded it to DELAYED/4. Please feel free to tell me if I > should delay it longer. > > Regards. > > filippo > -- > Filippo Giunchedi - http://esaurito.net - 0x6B79D401 > > Frustra fit per plura, quod fieri potest per pauciora. > It is vain to do with more what can be done with less. > -- W. of Ockham > -- Anibal Avelar (FixXxeR) http://fixxxer.cc GPG: 83B64656 - C143 4AD8 B017 53FA B742 D6AA CEEA F9F3 83B6 4656 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
Lucas Nussbaum wrote: > On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: >> I suggest there might be something wrong with the amd64 build box >> you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built >> successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version >> from the mirrors and rebuilt under a pbuilder chroot and it built >> successfully as well. The -4 version of the package had a problem in the >> debian/rules that caused this behavior but it was fixed in the -5 release. > > Could you please diff your log with mine, to see if the problem was > possibly caused by different build-dep versions ? > I'm building on i386 as my amd64 boxes are currently still offline along with my hppa and alpha machines. The official amd64 buildd I sent the URL that was available for the log. When looking through it I didn't see any failures. However that log format and your log format are completely different and do not lend themselves to diff comparison. Jeremy signature.asc Description: OpenPGP digital signature
Bug#562447: missing dependency of rubygems; failed to start
At least --help works, but providing a man-page would be nice as per policy 12.1. -- pub 4096R/0E4BD0AB -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: > > I suggest there might be something wrong with the amd64 build box > you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built > successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version > from the mirrors and rebuilt under a pbuilder chroot and it built > successfully as well. The -4 version of the package had a problem in the > debian/rules that caused this behavior but it was fixed in the -5 release. Could you please diff your log with mine, to see if the problem was possibly caused by different build-dep versions ? Thanks Lucas signature.asc Description: Digital signature
Bug#562292: ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef
On 24/12/09 at 16:38 +0100, Jiří Paleček wrote: > tags 562292 +moreinfo +unreproducible > > On Thu, 24 Dec 2009 11:25:35 +0100, Lucas Nussbaum > wrote: > > >Source: ltp > >Version: 20091031+dfsg-2 > >Severity: serious > >User: debian...@lists.debian.org > >Usertags: qa-ftbfs-20091213 qa-ftbfs > >Justification: FTBFS on amd64 > > > >Hi, > > > >During a rebuild of all packages in sid, your package failed to build on > >amd64. > > > >Relevant part: > >>cc -g -O2 -g -Wall -O2 -g -O2 -fno-strict-aliasing -pipe -Wall > >>-I/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include > >>-I../../../../include -I../../../../include -c -o netsync.o > >>netsync.c > >>In file included from libcpuset.c:51: > >>/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:32:1: > >>error: unterminated #ifdef > >>/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:13:1: > >>error: unterminated #ifndef > >>OK! > >>make[6]: *** [libcpuset.o] Error 1 > > > >The full build log is available from: > > > > http://people.debian.org/~lucas/logs/2009/12/13/ltp_20091031+dfsg-2_lsid64.buildlog > > > >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. > > > > Could you please upload the file in question or the whole build tree > after a failed build somewhere? I can't figure out what's the > problem, and the official buildds seem to handle it: > https://buildd.debian.org/fetch.cgi?pkg=ltp&arch=amd64&ver=20091031%2Bdfsg-2&stamp=1261520305&file=log&as=raw Have you tried building it before saying it's unreproducible? Could you please provide a diff of your log with mine, to exclude a problem with build-dependencies? Thanks Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552968: marked as done (poker-engine: FTBFS: tests failed)
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #552968, regarding poker-engine: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: poker-engine Version: 1.3.4-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory > `/build/user-poker-engine_1.3.4-1-amd64-gx2O2c/poker-engine-1.3.4/tests' > PASS: coverage-reset > ERROR history2messages ignored empty showdown_stack > -- > Ran 135 tests in 83.393s > > OK > PASS: test-game.py > -- > Ran 16 tests in 0.019s > > OK > PASS: test-gamehistory.py > -- > Ran 4 tests in 0.346s > > OK > PASS: test-i18n.py > -- > Ran 18 tests in 0.004s > > OK > PASS: test-pokercards.py > -- > Ran 13 tests in 0.005s > > OK > PASS: test-pokerchips.py > -- > Ran 15 tests in 0.036s > > OK > PASS: test-pokerengineconfig.py > -- > Ran 17 tests in 0.006s > > OK > PASS: test-pokerplayer.py > -- > Ran 3 tests in 0.012s > > OK > PASS: test-pokerprizes.py > -- > Ran 2 tests in 0.001s > > OK > PASS: test-pokerrake.py > -- > Ran 25 tests in 4.384s > > OK > PASS: test-pokertournament.py > -- > Ran 15 tests in 0.006s > > OK > PASS: test-version.py > -- > Ran 2 tests in 0.174s > > OK > PASS: history.py > -- > Ran 1 test in 0.063s > > OK > PASS: deal.py > -- > Ran 2 tests in 0.522s > > OK > PASS: positions.py > -- > Ran 11 tests in 20.448s > > OK > PASS: tournament.py > -- > Ran 9 tests in 0.129s > > OK > PASS: allin.py > -- > Ran 2 tests in 0.005s > > OK > PASS: chips.py > -- > Ran 13 tests in 17.543s > > OK > PASS: blinds.py > -- > Ran 2 tests in 0.140s > > OK > PASS: sit.py > sending incremental file list > ./ > poker..01-.02-no-limit.xml > poker..01-.02-pot-limit.xml > poker..02-.04-limit.xml > poker..02-.04-no-limit.xml > poker..02-.04-pot-limit.xml > poker..02..04-limit.xml > poker..05-.10-limit.xml > poker..05-.10-no-limit.xml > poker..05-.10-pot-limit.xml > poker..05..10-limit.xml > poker..10-.25-limit.xml > poker..10-.25-no-limit.xml > poker..10-.25-pot-limit.xml > poker..25-.50-limit.xml > poker..25-.50-no-limit.xml > poker..25-.50-pot-limit.xml > poker..25..50-limit.xml > poker..50-1-limit.xml > poker..50-1-no-limit.xml > poker..50-1-pot-limit.xml > poker..50.1-limit.xml > poker.0-0-limit.xml > poker.1-2-limit.xml > poker.1-2-no-limit.xml > poker.1-2-pot-limit.xml > poker.10-15-limit.xml > poker.10-15-pot-limit.xml > poker.10-20-limit.xml > poker.10-20-no-limit.xml > poker.10-20-pot-limit.xml > poker.100-200-limit.xml > poker.100-200-no-limit.xml > poker.100-200-pot-limit.xml > poker.15-30-limit.xml > poker.150-300-limit.xml > poker.2-4-limit.xml > poker.2-4-no-limit.xml > poker.2-4-pot-limit.xml > poker.200-400-limit.xml > poker.3-6-limit.xml > poker.3-6-no-limit.xml > poker.3-6-pot-limit.xml > poker.30-60-limit.xml > poker.30-60-no-limit.xml > poker.30-60-pot-limit.xml > poker.4-8-limit.xml > poker.5-10-limit.xml > poker.
Bug#552838: marked as done (icom: FTBFS: icom.c:37: error: conflicting types for 'getline')
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #552838, regarding icom: FTBFS: icom.c:37: error: conflicting types for 'getline' 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.) -- 552838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: icom Version: 20040912-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. In eglibc <= 2.9, getline was only defined if _GNU_SOURCE was defined. In eglibc 2.10, getline is always defined (since it became a standard in POSIX2008). The problem is that your package already has a function named getline(), which now conflicts with glibc's. You need to rename your function to something else. Ubuntu already fixed many occurences of your problem, so it is possible that an Ubuntu patch is available for your package. Look at the PTS to find out. Relevant part: > gcc -O -I../include -c -o icom.o icom.c > icom.c:37: error: conflicting types for 'getline' > /usr/include/stdio.h:651: error: previous declaration of 'getline' was here > icom.c: In function 'main': > icom.c:1261: warning: incompatible implicit declaration of built-in function > 'modf' > make[1]: *** [icom.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/icom_20040912-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message ---
Bug#560545: marked as done (lpe: FTBFS: (.text+0x8cd1): undefined reference to `fmod')
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #560545, regarding lpe: FTBFS: (.text+0x8cd1): undefined reference to `fmod' 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.) -- 560545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lpe Version: 1.2.6.13-0.1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o):(.text+0x63d1): > more undefined references to `pow' follow > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `double_double_scalar_bin_op': > (.text+0x8cd1): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `_pSLarith_bin_op': > (.text+0x9004): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `_pSLarith_bin_op': > (.text+0x9135): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `_pSLarith_bin_op': > (.text+0x9213): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `double_double_bin_op': > (.text+0x9721): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `double_double_bin_op': > (.text+0x9881): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `double_double_bin_op': > (.text+0x98ff): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `double_double_bin_op': > (.text+0x9992): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `double_double_bin_op': > (.text+0x9e18): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `double_double_bin_op': > (.text+0x9f09): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `float_float_bin_op': > (.text+0xa394): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `float_float_bin_op': > (.text+0xa4fc): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `float_float_bin_op': > (.text+0xa579): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `float_float_bin_op': > (.text+0xa608): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `float_float_bin_op': > (.text+0xaa7f): undefined reference to `fmod' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slarith.o): In > function `float_float_bin_op': > (.text+0xab84): undefined reference to `pow' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slstrops.o): > In function `SLdo_sprintf': > (.text+0x2c5c): undefined reference to `log10' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slfpu.o): In > function `SLfpu_test_except_bits': > (.text+0x9): undefined reference to `fetestexcept' > /usr/lib/gcc/x86_64-linux-gnu/4.4.2/../../../../lib/libslang.a(slfpu.o): In > function `SLfpu_clear_except_bits': > (.text+0x56): undefined reference to `feclearexcept' > collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/lpe_1.2.6.13-0.1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- ---
Bug#549848: marked as done (denyhosts: FTBFS: mv: cannot move `/build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts//usr/sbin/daemon-control-dist' to `/build/user-denyhosts_2.6-6-a
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #549848, regarding denyhosts: FTBFS: mv: cannot move `/build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts//usr/sbin/daemon-control-dist' to `/build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts//usr/share/denyhosts/denyhosts_ctl.py': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 549848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: denyhosts Version: 2.6-6 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091005 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/bin/fakeroot debian/rules binary > test -x debian/rules > dh_testroot > dh_clean -k > dh_installdirs -A > mkdir -p "." > mkdir -p debian/python-module-stampdir > cd . && python setup.py build > --build-base="/build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/./build" > running build > running build_py > running build_scripts > touch debian/python-module-stampdir/denyhosts > dh_installdirs -pdenyhosts var/lib/denyhosts > cd . && python setup.py install > --root=/build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/ > \ > --install-lib=/usr/lib/python2.5/site-packages/ --no-compile > -O0 --force --install-scripts=/usr/sbin --install-purelib=/usr/share/denyhosts > running install > running build > running build_py > running build_scripts > running install_lib > creating > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr > creating > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib > creating > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5 > creating > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages > creating > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/prefs.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/report.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/lockfile.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/__init__.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/plugin.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/counter.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/old-daemon.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/util.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/daemon.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/python_version.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/allowedhosts.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/filetracker.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/loginattempt.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/restricted.py -> > /build/user-denyhosts_2.6-6-amd64-AwbxZH/denyhosts-2.6/debian/denyhosts/usr/lib/python2.5/site-packages/DenyHosts > copying build/lib/DenyHosts/purgecounter.
Bug#560602: marked as done (libschedule-cron-perl: FTBFS: tests blocked)
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #560602, regarding libschedule-cron-perl: FTBFS: tests blocked 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.) -- 560602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libschedule-cron-perl Version: 0.99-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-libschedule-cron-perl_0.99-1-amd64-VxSF30/libschedule-cron-perl-0.99' > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > t/after_job.t ... ok > t/callbackreschedule.t .. ok > t/dst_back.t ok > t/entry.t ... ok > t/execution_time.t .. ok > t/kwalitee.t ok > t/load_crontab.t ok > make: *** [build-stamp] Terminated > E: Caught signal 'Terminated': terminating immediately > make[1]: *** [test_dynamic] Terminated > Build killed with signal TERM after 60 minutes of inactivity > > Build finished at 20091211-0203 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/libschedule-cron-perl_0.99-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message ---
Bug#552918: marked as done (zope.sendmail: FTBFS: mv: cannot stat `debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.sendmail-*-py2.4.egg-info': No such file or directory)
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #552918, regarding zope.sendmail: FTBFS: mv: cannot stat `debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.sendmail-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.sendmail Version: 3.6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.sendmail_3.6.0-1-amd64-AAyNTz/zope.sendmail-3.6.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.sendmail > --install-data=usr/lib/python-zope.sendmail > running install > running build > running build_py > running egg_info > writing requirements to src/zope.sendmail.egg-info/requires.txt > writing src/zope.sendmail.egg-info/PKG-INFO > writing namespace_packages to > src/zope.sendmail.egg-info/namespace_packages.txt > writing top-level names to src/zope.sendmail.egg-info/top_level.txt > writing dependency_links to src/zope.sendmail.egg-info/dependency_links.txt > reading manifest file 'src/zope.sendmail.egg-info/SOURCES.txt' > writing manifest file 'src/zope.sendmail.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/sendmail/event.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/__init__.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/interfaces.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/mailer.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/maildir.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/zcml.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/delivery.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/vocabulary.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail > copying zope/sendmail/tests/test_directives.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail/tests > copying zope/sendmail/tests/test_vocabulary.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail/tests > copying zope/sendmail/tests/__init__.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail/tests > copying zope/sendmail/tests/test_event.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail/tests > copying zope/sendmail/tests/test_delivery.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail/tests > copying zope/sendmail/tests/test_maildir.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail/tests > copying zope/sendmail/tests/test_mailer.py -> > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope/sendmail/tests > running install_egg_info > Copying src/zope.sendmail.egg-info to > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.sendmail-3.6.0.egg-info > Installing > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.sendmail-3.6.0-nspkg.pth > running install_scripts > mv > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.sendmail-*-py2.4.egg-info > \ > > debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.sendmail.egg-info > > mv: cannot stat > `debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.sendmail-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.sendmail_3.6.0-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contri
Bug#560605: marked as done (plee-the-bear: FTBFS: CMake: It seems that libclaw is not installed on your system.)
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #560605, regarding plee-the-bear: FTBFS: CMake: It seems that libclaw is not installed on your system. 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.) -- 560605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plee-the-bear Version: 0.4.1-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/bin/fakeroot debian/rules clean > dh_testdir > dh_testroot > QUILT_PATCHES=debian/patches quilt pop -a -R || test $? = 2 > No patch removed > rm -f build-stamp configure-stamp > if [ -d > /build/user-plee-the-bear_0.4.1-3-amd64-w_8YFN/plee-the-bear-0.4.1/build-tree > ]; then cd > /build/user-plee-the-bear_0.4.1-3-amd64-w_8YFN/plee-the-bear-0.4.1/build-tree; > /usr/bin/make clean; fi > rm -fr > /build/user-plee-the-bear_0.4.1-3-amd64-w_8YFN/plee-the-bear-0.4.1/build-tree > rm -f debian/running-bear.6 > rm -f debian/plee-the-bear.6 > rm -fr .pc > for f in debian/*.menu; do if [ -L $f ]; then unlink $f; fi; done > dh_clean > dpkg-source -b plee-the-bear-0.4.1 > dpkg-source: info: using source format `1.0' > dpkg-source: info: building plee-the-bear using existing > plee-the-bear_0.4.1.orig.tar.gz > dpkg-source: info: building plee-the-bear in plee-the-bear_0.4.1-3.diff.gz > dpkg-source: info: building plee-the-bear in plee-the-bear_0.4.1-3.dsc > debian/rules build > dh_testdir > QUILT_PATCHES=debian/patches quilt push -a || test $? = 2 > Applying patch do-not-install-authors-files.diff > patching file plee-the-bear/data/CMakeLists.txt > > Applying patch rpath-editors.diff > patching file bear-factory/animation-editor/src/bf/CMakeLists.txt > patching file bear-factory/level-editor/src/bf/CMakeLists.txt > patching file bear-factory/model-editor/src/bf/CMakeLists.txt > patching file bear-factory/bear-editor/src/bf/CMakeLists.txt > > Applying patch editors-default-dir.diff > patching file bear-factory/bear-editor/src/bf/code/path_configuration.cpp > > Applying patch rpath-game.diff > patching file bear-engine/core/src/audio/CMakeLists.txt > patching file bear-engine/core/src/communication/CMakeLists.txt > patching file bear-engine/core/src/debug/CMakeLists.txt > patching file bear-engine/core/src/engine/CMakeLists.txt > patching file bear-engine/core/src/gui/CMakeLists.txt > patching file bear-engine/core/src/input/CMakeLists.txt > patching file bear-engine/core/src/time/CMakeLists.txt > patching file bear-engine/core/src/universe/CMakeLists.txt > patching file bear-engine/core/src/visual/CMakeLists.txt > patching file bear-engine/running_bear/CMakeLists.txt > patching file bear-engine/lib/src/generic_items/CMakeLists.txt > patching file plee-the-bear/src/ptb/CMakeLists.txt > Hunk #1 succeeded at 146 (offset 1 line). > > Applying patch editors-menu-section.diff > patching file bear-factory/desktop/menu/bf-animation-editor > patching file bear-factory/desktop/menu/bf-level-editor > patching file bear-factory/desktop/menu/bf-model-editor > > Now at patch editors-menu-section.diff > # Perform an out-of-tree build to keep a clean source tree > mkdir > /build/user-plee-the-bear_0.4.1-3-amd64-w_8YFN/plee-the-bear-0.4.1/build-tree > cd > /build/user-plee-the-bear_0.4.1-3-amd64-w_8YFN/plee-the-bear-0.4.1/build-tree; > cmake .. \ > -DCMAKE_INSTALL_PREFIX:STRING="/usr" \ > -DCMAKE_C_FLAGS:STRING="-g -O2 -DNDEBUG" \ > > -DBEAR_ENGINE_INSTALL_LIBRARY_DIR:STRING="lib/games/plee-the-bear" \ > -DBEAR_ENGINE_INSTALL_EXECUTABLE_DIR:STRING="games" \ > -DBEAR_FACTORY_INSTALL_LIBRARY_DIR:STRING="lib/bear-factory" \ > -DBEAR_FACTORY_INSTALL_EXECUTABLE_DIR:STRING="games" \ > -DCMAKE_SHARED_LINKER_FLAGS:STRING="-Wl,--as-needed" \ > -DCMAKE_EXE_LINKER_FLAGS:STRING="-Wl,--as-needed" \ > -DPTB_INSTALL_DATA_DIR:STRING="share/games/plee-the-bear" \ > > -DPTB_INSTALL_CUSTOM_LIBRARY_DIR:STRING="lib/games/plee-the-bear" \ > -DPTB_INSTALL_EXECUTABLE_DIR:STRING="games" > -- The C compiler identification is GNU > -- The CXX compiler identification is GNU > -- Check for working C compiler: /usr/bin/gcc > -- Check for working C compiler: /usr/bin/gcc -- wo
Bug#549746: marked as done (tar: FTBFS: tests failed)
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #549746, regarding tar: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 549746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tar Version: 1.22-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091005 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory > `/build/user-tar_1.22-2-amd64-LL4L1q/tar-1.22/tests' > /bin/bash /build/user-tar_1.22-2-amd64-LL4L1q/tar-1.22/build-aux/missing > --run autom4te --language=autotest -I . testsuite.at -o testsuite.tmp > mv testsuite.tmp testsuite > /bin/bash ./testsuite > ## ## > ## GNU tar 1.22 test suite. ## > ## ## > 1: tar version ok > 2: decompressing from stdinok > 3: mixing options ok > 4: interspersed optionsok > 5: files-from: empty entries ok > 6: files-from: 0-separated file without -0 ok > 7: tar --index-file=FILE --file=- ok > 8: tar cvf - ok > 9: append ok > 10: appending files with long names ok > 11: append vs. create ok > 12: exclude ok > 13: deleting a member after a big one ok > 14: deleting a member from stdin archiveok > 15: deleting members with long namesok > 16: deleting a large last memberok > 17: deleting non-existing memberok > 18: extract over an existing directory ok > 19: extracting symlinks over an existing file ok > 20: extraction loopsok > 21: extract + fnmatch ok > 22: extracting selected members from paxok > 23: mode of extracted directories ok > 24: extracting symlinks to a read-only dir ok > 25: gzipok > 26: incremental ok > 27: restore broken symlinks from incrementalok > 28: restoring timestamps from incremental ok > 29: --listed for individual files ok > 30: working --listedok > 31: renamed files in incrementals ok > 32: proper icontents initialization ok > 33: renamed dirs in incrementalsok > 34: move between hierarchiesok > 35: cyclic renames ok > 36: renamed directory containing subdirectories ok > 37: renamed subdirectories ok > 38: changed file types in incrementals ok > 39: ignfail ok > 40: link count gt 2 ok > 41: preserve hard links with --remove-files ok > 42: working -l with --remove-files ok > 43: long names in V7 archives ok > 44: long file names divisible by block size ok > 45: ustar: unsplittable file name ok > 46: ustar: unsplittable path name ok > 47: ustar: splitting long names ok > 48: multivolume dumps from pipesok > 49: skipping a straddling memberok > 50: MV archive & long filenames ok > 51: split directory members in a MV archive ok > 52: Restoring after an out of sync volume ok > 53: Multivolumes with L=record_size ok > 54: old archivesok > 55: recurse ok > 56: working -C with --same-orderok > 57: multiple -C options ok > 58: short records ok > 59: sparse filesok > 60: extracting sparse file over a pipe ok > 61: storing sparse files > 8G ok > 62: sp
Bug#549777: marked as done (libfso-glib: FTBFS: freesmartphone.c:19414: error: expected expression before '{' token)
Your message dated Thu, 24 Dec 2009 18:37:08 +0100
with message-id <20091224173708.ga30...@xanadu.blop.info>
and subject line no longer fails, closing.
has caused the Debian Bug report #549777,
regarding libfso-glib: FTBFS: freesmartphone.c:19414: error: expected
expression before '{' token
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.)
--
549777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfso-glib
Version: 0.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091005 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> /bin/bash ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I..
> -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -include ../config.h -g -O2 -g -Wall -O2 -c -o
> freesmartphone.lo freesmartphone.c
> libtool: compile: cc -DHAVE_CONFIG_H -I. -I.. -pthread
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
> -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -include ../config.h -g -O2 -g -Wall -O2 -c
> freesmartphone.c -fPIC -DPIC -o .libs/freesmartphone.o
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_music_player_playing_changed':
> freesmartphone.c:4157: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_music_player_playlist_added':
> freesmartphone.c:4174: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_music_player_playlist_removed':
> freesmartphone.c:4191: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_music_player_progress':
> freesmartphone.c:4208: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_music_player_state':
> freesmartphone.c:4225: warning: unused variable 'reply'
> freesmartphone.c: In function '_dbus_handle_free_smartphone_phone_incoming':
> freesmartphone.c:6971: warning: unused variable 'reply'
> freesmartphone.c: In function '_dbus_free_smartphone_resource_enable':
> freesmartphone.c:7390: warning: passing argument 2 of
> 'free_smartphone_resource_enable' from incompatible pointer type
> freesmartphone.c: In function '_dbus_free_smartphone_resource_enable_ready':
> freesmartphone.c:7404: warning: passing argument 1 of
> 'free_smartphone_resource_enable_finish' from incompatible pointer type
> freesmartphone.c: In function '_dbus_free_smartphone_resource_disable':
> freesmartphone.c:7533: warning: passing argument 2 of
> 'free_smartphone_resource_disable' from incompatible pointer type
> freesmartphone.c: In function '_dbus_free_smartphone_resource_disable_ready':
> freesmartphone.c:7547: warning: passing argument 1 of
> 'free_smartphone_resource_disable_finish' from incompatible pointer type
> freesmartphone.c: In function '_dbus_free_smartphone_resource_suspend':
> freesmartphone.c:7682: warning: passing argument 2 of
> 'free_smartphone_resource_suspend' from incompatible pointer type
> freesmartphone.c: In function '_dbus_free_smartphone_resource_suspend_ready':
> freesmartphone.c:7696: warning: passing argument 1 of
> 'free_smartphone_resource_suspend_finish' from incompatible pointer type
> freesmartphone.c: In function '_dbus_free_smartphone_resource_resume':
> freesmartphone.c:7831: warning: passing argument 2 of
> 'free_smartphone_resource_resume' from incompatible pointer type
> freesmartphone.c: In function '_dbus_free_smartphone_resource_resume_ready':
> freesmartphone.c:7845: warning: passing argument 1 of
> 'free_smartphone_resource_resume_finish' from incompatible pointer type
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_phone_call_incoming':
> freesmartphone.c:9342: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_phone_call_outgoing':
> freesmartphone.c:9353: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_phone_call_released':
> freesmartphone.c:9364: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_handle_free_smartphone_phone_call_activated':
> freesmartphone.c:9375: warning: unused variable 'reply'
> freesmartphone.c: In function
> '_dbus_free_smartphone_preferences_get_services':
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
I suggest there might be something wrong with the amd64 build box
you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built
successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version
from the mirrors and rebuilt under a pbuilder chroot and it built
successfully as well. The -4 version of the package had a problem in the
debian/rules that caused this behavior but it was fixed in the -5 release.
Jeremy
[1]https://buildd.debian.org/fetch.cgi?pkg=libgcgi;ver=0.9.5.dfsg-5;arch=amd64;stamp=1260598069
Lucas Nussbaum wrote:
> Source: libgcgi
> Version: 0.9.5.dfsg-5
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20091223 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part:
>> /usr/bin/fakeroot debian/rules clean
>> dh_testdir
>> dh_testroot
>> dh_auto_clean
>> dh_clean
>> find . \( -type d -a -name .deps -prune -exec rm -rf {} \; \)
>> dpatch deapply-all
>> 01_update_libtool not applied to ./ .
>> rm -rf patch-stamp patch-stampT debian/patched
>> dpkg-source -b libgcgi-0.9.5.dfsg
>> dpkg-source: info: using source format `1.0'
>> dpkg-source: info: building libgcgi using existing
>> libgcgi_0.9.5.dfsg.orig.tar.gz
>> dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.diff.gz
>> dpkg-source: warning: executable mode 0755 of
>> 'debian/patches/01_update_libtool.dpatch' will not be represented in diff
>> dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.dsc
>> debian/rules build
>> test -d debian/patched || install -d debian/patched
>> dpatch apply-all
>> applying patch 01_update_libtool to ./ ... ok.
>> dpatch cat-all >>patch-stampT
>> mv -f patch-stampT patch-stamp
>> dh_testdir
>> find . \( -type f -a -name "Makefile.*" -prune -exec touch {} \; \)
>> # Add here commands to configure the package.
>> CFLAGS="-Wall -g -O2" ./configure --host=x86_64-linux-gnu
>> --build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man
>> --infodir=\${prefix}/share/info --with-openssl
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> /build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing:
>> Unknown `--run' option
>> Try
>> `/build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing
>> --help' for more information
>> configure: WARNING: `missing' script is too old or missing
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... no
>> checking for mawk... mawk
>> checking whether make sets $(MAKE)... yes
>> checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-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 x86_64-linux-gnu-gcc accepts -g... yes
>> checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
>> checking for style of include used by make... GNU
>> checking dependency style of x86_64-linux-gnu-gcc... gcc3
>> checking how to run the C preprocessor... x86_64-linux-gnu-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 whether make sets $(MAKE)... (cached) yes
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking for a sed that does not truncate output... /bin/sed
>> checking for fgrep... /bin/grep -F
>> checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld
>> checking if the linker (/usr/bin/ld) is GNU ld... yes
>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>> checking whether ln -s works... yes
>> checking the maximum length of command line arguments... 3458764513820540925
>> checking whether the shell understands some XSI constructs... yes
>> checking whether the shell understands "+="... yes
>> checking for /usr/bin/ld option to reload object files... -r
>> checking for x86_64-linux-gnu-objdump... no
>> checking for objdump... objdump
>> checking how to recognize dependent libraries... pass_all
>> checking for x86_64-linux-gnu-ar... no
>> checking for ar... ar
>> checking for x86_64-linux-gnu-strip... no
>> checking for strip... strip
>> checking for x86_64-linux-gnu-ranlib... no
>> checking for ranlib... ranlib
>> checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc
>> object... ok
>> 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
>>
Bug#560649: marked as done (ruby1.9.1: FTBFS: FAIL 1/945 tests failed)
Your message dated Thu, 24 Dec 2009 18:37:08 +0100 with message-id <20091224173708.ga30...@xanadu.blop.info> and subject line no longer fails, closing. has caused the Debian Bug report #560649, regarding ruby1.9.1: FTBFS: FAIL 1/945 tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 560649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby1.9.1 Version: 1.9.1.376-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-ruby1.9.1_1.9.1.376-1-amd64-GaGles/ruby1.9.1-1.9.1.376' > > sample/test.rb:assignment > > sample/test.rb:condition .. > sample/test.rb:if/unless ... > sample/test.rb:case . > sample/test.rb:while/until > sample/test.rb:exception .. > sample/test.rb:array ... > sample/test.rb:hash ... > sample/test.rb:iterator > ... > sample/test.rb:float > > sample/test.rb:bignum ... > sample/test.rb:string & char > .. > sample/test.rb:assignment .. > sample/test.rb:call .. > sample/test.rb:proc . > sample/test.rb:signal .. > sample/test.rb:eval . > sample/test.rb:system . > sample/test.rb:const . > sample/test.rb:clone . > sample/test.rb:marshal > sample/test.rb:pack > sample/test.rb:math .. > sample/test.rb:struct .. > sample/test.rb:variable ... > sample/test.rb:trace ... > sample/test.rb:defined? > sample/test.rb:alias .. > sample/test.rb:path ... > sample/test.rb:gc > test succeeded > > test_thread.rb #1 test_thread.rb:3:in `' > .#2 test_thread.rb:8:in `' > .#3 test_thread.rb:13:in `' > .#4 test_thread.rb:24:in `' > .#5 test_thread.rb:34:in `' > .#6 test_thread.rb:44:in `' > .#7 test_thread.rb:52:in `' > .#8 test_thread.rb:57:in `' > .#9 test_thread.rb:62:in `' > .#10 test_thread.rb:71:in `' > .#11 test_thread.rb:85:in `' > .#12 test_thread.rb:98:in `' > .#13 test_thread.rb:111:in `' > .#14 test_thread.rb:124:in `' > .#15 test_thread.rb:132:in `' > .#16 test_thread.rb:141:in `' > .#17 test_thread.rb:148:in `' > .#18 test_thread.rb:155:in `' > .#19 test_thread.rb:165:in `' > .#20 test_thread.rb:172:in `' > .#21 test_thread.rb:183:in `' > .#22 test_thread.rb:191:in `' > .#23 test_thread.rb:206:in `' > .#24 test_thread.rb:219:in `' > .#25 test_thread.rb:235:in `' > .#26 test_thread.rb:241:in `' > .#27 test_thread.rb:254:in `' > .#28 test_thread.rb:266:in `' > .#29 test_thread.rb:268:in `' > .#30 test_thread.rb:287:in `' > .#31 test_thread.rb:292:in `' > .#32 test_thread.rb:297:in `' > .#33 test_thread.rb:302:in `' > .#34 test_thread.rb:307:in `' > .#35 test_thread.rb:312:in `' > .#36 test_thread.rb:316:in `' > .#37 test_thread.rb:320:in `' > .#38 test_thread.rb:322:in `' > .#39 test_thread.rb:332:in `' > .#40 test_thread.rb:343:in `' > .#41 test_thread.rb:349:in `' > .#42 test_thread.rb:355:in `' > .#43 test_thread.rb:361:in `' > .#44 test_thread.rb:368:in `' > .#45 test_thread.rb:375:in `' > .#46 test_thread.rb:381:in `' > . > test_syntax.rb #47 test_syntax.rb:1:in `' > .#48 test_syntax.rb:2:in `' > .#49 test_syntax.rb:3:in `' > .#50 test_syntax.rb:4:in `' > .#51 test_syntax.rb:5:in `' > .#52 test_syntax.rb:6:in `' > .#53 test_syntax.rb:7:in `' > .#54 test_syntax.rb:8:in `' > .#55 test_syntax.rb:9:in `' > .#56 test_syntax.rb:10:in `' > .#57 test_syntax.rb:11:in `' > .#58 test_syntax.rb:16:in `' > .#59 test_syntax.rb:27:in `' > .#60 test_syntax.rb:39:in `' > .#61 test_syntax.rb:51:in `' > .#62 test_syntax.rb:57:in `' > .#63 test_syntax.rb:65:in `' > .#64 test_syntax.rb:75:in `' > .#65 test_syntax.rb:85:in `' > .#66 test_syntax.rb:95:in `' > .#67 test_synt
Bug#504900: marked as done (FTBFS with GCC 4.4: missing #include)
Your message dated Thu, 24 Dec 2009 17:32:24 +
with message-id
and subject line Bug#504900: fixed in pan 0.133-1.1
has caused the Debian Bug report #504900,
regarding FTBFS with GCC 4.4: missing #include
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.)
--
504900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pan
Version: 0.132-3.1
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.4
Tags: patch
Your package fails to build with the upcoming GCC 4.4. Version 4.4
has not been released yet but I'm building with a snapshot in order
to find errors and give people an advance warning.
GCC 4.4 cleaned up some more C++ headers. You always have to #include
headers directly and cannot rely for things to be included indirectly.
You can reproduce this problem with gcc-snapshot from unstable.
> Automatic build of pan_0.132-3.1 on em64t by sbuild/amd64 0.53
...
> if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../..
> -D_LARGEFILE64_SOURCE -I/usr/include/gmime-2.0 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -g -O2 -MT log.o -MD -MP -MF
> ".deps/log.Tpo" -c -o log.o log.cc; \
> then mv -f ".deps/log.Tpo" ".deps/log.Po"; else rm -f ".deps/log.Tpo";
> exit 1; fi
> log.cc: In member function 'void pan::Log::add_va(pan::Log::Severity, const
> char*, ...)':
> log.cc:82: error: 'vsnprintf' was not declared in this scope
> log.cc: In static member function 'static void pan::Log::add_info_va(const
> char*, ...)':
> log.cc:94: error: 'vsnprintf' was not declared in this scope
> log.cc: In static member function 'static void pan::Log::add_err_va(const
> char*, ...)':
> log.cc:106: error: 'vsnprintf' was not declared in this scope
> log.cc: In static member function 'static void pan::Log::add_urgent_va(const
> char*, ...)':
> log.cc:118: error: 'vsnprintf' was not declared in this scope
> make[4]: *** [log.o] Error 1
> make[4]: Leaving directory `/build/tbm/pan-0.132/pan/general'
> make[3]: *** [all-recursive] Error 1
--- pan/general/log.cc~ 2008-11-07 20:32:24.0 +
+++ pan/general/log.cc 2008-11-07 20:32:31.0 +
@@ -20,6 +20,7 @@
#include
#include
#include
+#include
#include "log.h"
using namespace pan;
--- pan/general/progress.cc~2008-11-07 20:33:09.0 +
+++ pan/general/progress.cc 2008-11-07 20:33:15.0 +
@@ -19,6 +19,7 @@
#include
#include
+#include
#include "progress.h"
#include "string-view.h"
--- pan/tasks/nntp.cc~ 2008-11-07 20:36:27.0 +
+++ pan/tasks/nntp.cc 2008-11-07 20:36:32.0 +
@@ -20,6 +20,7 @@
#include
#include
#include
+#include
extern "C" {
#include
#include
--- pan/tasks/nntp-pool.cc~ 2008-11-07 20:37:30.0 +
+++ pan/tasks/nntp-pool.cc 2008-11-07 20:37:42.0 +
@@ -18,6 +18,7 @@
*/
#include
+#include
#include
#include
#include
--- pan/usenet-utils/numbers.cc~2008-11-07 20:33:56.0 +
+++ pan/usenet-utils/numbers.cc 2008-11-07 20:34:02.0 +
@@ -19,6 +19,7 @@
#include
#include
+#include
#include
#include
#include "numbers.h"
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: pan
Source-Version: 0.133-1.1
We believe that the bug you reported is fixed in the latest version of
pan, which is due to be installed in the Debian FTP archive:
pan_0.133-1.1.diff.gz
to main/p/pan/pan_0.133-1.1.diff.gz
pan_0.133-1.1.dsc
to main/p/pan/pan_0.133-1.1.dsc
pan_0.133-1.1_amd64.deb
to main/p/pan/pan_0.133-1.1_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 504...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lucas Nussbaum (supplier of updated pan package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 21 Dec 2009 17:45:48 +0100
Source: pan
Binary: pan
Architecture: source amd64
Version: 0.133-1.1
Distribution: unstable
Urgency: high
Maintainer: Mario Iseli
Changed-By: Lucas Nussbaum
Description:
pan- A Newsreader based on GTK2, whi
Bug#562446: marked as pending
tag 562446 pending thanks Hello, Bug #562446 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=collab-maint/quilt.git;a=commitdiff;h=3c0647c --- commit 3c0647c0bfb21386b5e956d163928b377016677f Author: Raphaël Hertzog Date: Thu Dec 24 18:22:25 2009 +0100 Add "ed" to Build-Depends-Indep as it's used by the test-suite. Closes: #562446 diff --git a/debian/changelog b/debian/changelog index 335f601..58d4df2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +quilt (0.48-4) UNRELEASED; urgency=low + + * Add "ed" to Build-Depends-Indep as it's used by the test-suite. +Closes: #562446 + + -- Raphaël Hertzog Thu, 24 Dec 2009 18:20:40 +0100 + quilt (0.48-3) unstable; urgency=low * Stop creating files with 000 mode in the .pc directory. Upstream -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560498: marked as done (goplay: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope)
Your message dated Thu, 24 Dec 2009 18:14:57 +0100 with message-id <20091224171457.ga30...@xanadu.blop.info> and subject line Re: Bug#560498: goplay: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope has caused the Debian Bug report #560498, regarding goplay: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope 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.) -- 560498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: goplay Version: 0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I.. > -I/usr/include/tagcoll-2.0.11 `fltk-config --cxxflags --use-images` -Wall > -Werror -ggdb-g -O2 -MT Engine.o -MD -MP -MF .deps/Engine.Tpo -c -o > Engine.o Engine.cpp > In file included from /usr/include/wibble/test.h:3, > from /usr/include/wibble/exception.h:25, > from /usr/include/ept/apt/apt.h:27, > from Engine.h:24, > from Engine.cpp:21: > /usr/include/wibble/string.h: In function 'std::string > wibble::str::fmt(std::string, ...)': > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in this > scope > make[3]: *** [Engine.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/goplay_0.3-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- no longer fails, closing On 11/12/09 at 09:14 +0100, Lucas Nussbaum wrote: > Source: goplay > Version: 0.3-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091210 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part: > > x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I.. > > -I/usr/include/tagcoll-2.0.11 `fltk-config --cxxflags --use-images` -Wall > > -Werror -ggdb-g -O2 -MT Engine.o -MD -MP -MF .deps/Engine.Tpo -c -o > > Engine.o Engine.cpp > > In file included from /usr/include/wibble/test.h:3, > > from /usr/include/wibble/exception.h:25, > > from /usr/include/ept/apt/apt.h:27, > > from Engine.h:24, > > from Engine.cpp:21: > > /usr/include/wibble/string.h: In function 'std::string > > wibble::str::fmt(std::string, ...)': > > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in > > this scope > > make[3]: *** [Engine.o] Error 1 > > The full build log is available from: > > http://people.debian.org/~lucas/logs/2009/12/10/goplay_0.3-1_lsid64.buildlog > > 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. > > -- > | Lucas Nussbaum > | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | > | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | > > > -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message ---
Bug#560505: marked as done (debtags: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope)
Your message dated Thu, 24 Dec 2009 18:15:52 +0100 with message-id <20091224171552.ga30...@xanadu.blop.info> and subject line Re: Bug#560505: debtags: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope has caused the Debian Bug report #560505, regarding debtags: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope 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.) -- 560505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debtags Version: 1.7.9 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include/tagcoll-2.0.11 > -DSCRIPTDIR=\"/usr/share/debtags\"-g -O2 -g -Wall -O2 -c -o Environment.o > Environment.cc > In file included from /usr/include/wibble/test.h:3, > from /usr/include/wibble/exception.h:25, > from /usr/include/ept/apt/apt.h:27, > from Environment.cc:23: > /usr/include/wibble/string.h: In function 'std::string > wibble::str::fmt(std::string, ...)': > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in this > scope > make[3]: *** [Environment.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/debtags_1.7.9_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- no longer fails, closing On 11/12/09 at 09:12 +0100, Lucas Nussbaum wrote: > Source: debtags > Version: 1.7.9 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091210 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part: > > g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include/tagcoll-2.0.11 > > -DSCRIPTDIR=\"/usr/share/debtags\"-g -O2 -g -Wall -O2 -c -o > > Environment.o Environment.cc > > In file included from /usr/include/wibble/test.h:3, > > from /usr/include/wibble/exception.h:25, > > from /usr/include/ept/apt/apt.h:27, > > from Environment.cc:23: > > /usr/include/wibble/string.h: In function 'std::string > > wibble::str::fmt(std::string, ...)': > > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in > > this scope > > make[3]: *** [Environment.o] Error 1 > > The full build log is available from: > > http://people.debian.org/~lucas/logs/2009/12/10/debtags_1.7.9_lsid64.buildlog > > 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. > > -- > | Lucas Nussbaum > | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | > | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | > > > -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message ---
Bug#560506: marked as done (debtags-edit: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope)
Your message dated Thu, 24 Dec 2009 18:16:13 +0100 with message-id <20091224171613.ga30...@xanadu.blop.info> and subject line Re: Bug#560506: debtags-edit: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope has caused the Debian Bug report #560506, regarding debtags-edit: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope 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.) -- 560506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debtags-edit Version: 1.5 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/tagcoll-2.0.11 -D_REENTRANT > -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include > -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include > -I/usr/include/giomm-2.4 -I/usr/lib/giomm-2.4/include > -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include > -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 > -I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 > -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 > -I/usr/lib/glibmm-2.4/include -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/cairomm-1.0 > -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -Wall -g -O2 -g -Wall > -O2 -c -o DebtagsDocument.o DebtagsDocument.cc > In file included from /usr/include/wibble/test.h:3, > from /usr/include/wibble/exception.h:25, > from /usr/include/ept/apt/apt.h:27, > from DebtagsDocument.h:26, > from DebtagsDocument.cc:23: > /usr/include/wibble/string.h: In function 'std::string > wibble::str::fmt(std::string, ...)': > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in this > scope > make[3]: *** [DebtagsDocument.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/debtags-edit_1.5_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- no longer fails, closing On 11/12/09 at 09:12 +0100, Lucas Nussbaum wrote: > Source: debtags-edit > Version: 1.5 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091210 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part: > > g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/tagcoll-2.0.11 -D_REENTRANT > > -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include > > -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include > > -I/usr/include/giomm-2.4 -I/usr/lib/giomm-2.4/include > > -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include > > -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 > > -I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 > > -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 > > -I/usr/lib/glibmm-2.4/include -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -I/usr/include/cairomm-1.0 > > -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > > -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 > > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -Wall -g -O2 -g > > -Wall -O2 -c -o DebtagsDocument.o DebtagsDocument.cc > > In file included from /usr/include/wibble/test.h:3, > > from /usr/include/wibble/exception.h:25, > > from /usr/include/ept/apt/apt.h:27, > > from DebtagsDocument.h:26, > > from DebtagsDocument.cc:23: > > /usr/include/wibble/string.h: In function 'std::string > > wibble::str::fmt(std::string, ...)': > > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in > > this scope > > make[3]: *** [DebtagsDocument.o] Error 1 > > The full build
Bug#562447: missing dependency of rubygems; failed to start
Package: god Version: 0.7.13-2 Severity: serious Justification: renders package unusable Hello, $ god /usr/bin/god:7:in `require': no such file to load -- rubygems (LoadError) from /usr/bin/god:7 Installing rubygems fixes that, but then again nothing seems to happen if I try to run it. Is there anything divine, I'm missing here? -- pub 4096R/0E4BD0AB -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#554584: marked as done (eclipse: FTBFS: timeout during build (on various archs))
Your message dated Thu, 24 Dec 2009 18:18:32 +0100 with message-id <20091224171832.ga30...@xanadu.blop.info> and subject line Re: Bug#476067: eclipse: FTBFS: build takes a very, very long time (or just blocks?) has caused the Debian Bug report #476067, regarding eclipse: FTBFS: timeout during build (on various archs) 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.) -- 476067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: eclipse Version: 3.4.1-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of eclipse_3.4.1-1 on caballero by sbuild/ia64 98 > Build started at 20091105-0105 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>> 4.2), dpatch (>= 2.0), lsb-release, bzip2, zip, > openjdk-6-jdk, ecj (>= 3.4.0), liblucene-java (>= 1.4.2), junit (>= 3.8), > junit4, libicu4j-java, libgtk2.0-dev (>= 2.4), libcairo2-dev, pkg-config, > ant-optional (>= 1.6.5-3), xulrunner-dev [...] > [exec] eclipse/plugins/org.objectweb.asm_3.1.0.v200803061910.jar > [exec] eclipse/plugins/org.objectweb.asm.source_3.1.0.v200803061910.jar > > gzipResults: > [move] Moving 1 file to > /build/buildd/eclipse-3.4.1/source-tree/tmp/eclipse > [gzip] Building: > /build/buildd/eclipse-3.4.1/source-tree/result/org.eclipse.sdk-M20080911-1700-linux.gtk.ia64.tar.gz > > build.doc.plugins: > > install.eclipse.tar: > [mkdir] Created dir: > /build/buildd/eclipse-3.4.1/source-tree/tmp/eclipse/plugins > make: *** wait: No child processes. Stop. > make: *** Waiting for unfinished jobs > make: *** wait: No child processes. Stop. > Build killed with signal 15 after 300 minutes of inactivity A full build log can be found at: http://buildd.debian.org/build.php?arch=ia64&pkg=eclipse&ver=3.4.1-1 --- End Message --- --- Begin Message --- Version: 3.4.1-1 No longer fails, closing On 14/04/08 at 13:32 +0200, Lucas Nussbaum wrote: > Package: eclipse > Version: 3.2.2-5 > Severity: important > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20080413 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > I haven't managed to build eclipse recently. I build on a quad-opteron, > so I wouldn't expect it to take more than 8 hours (which it does). > > Is there something that could be done to make it faster to build, or > should I just exclude eclipse from my rebuilds? > > In the past, I could build eclipse in less than 1 hour. > > Thank you, > > Relevant part: > > main: > > [mkdir] Created dir: /build/user/eclipse-3.2.2/source-tree/tmp > > [copy] Copying 8 files to > > /build/user/eclipse-3.2.2/source-tree/tmp/eclipse/plugins/com.ibm.icu.source_3.4.5.20061213 > > [copy] Copying 1 file to > > /build/user/eclipse-3.2.2/source-tree/tmp/eclipse/plugins > > [copy] Copying 1 file to > > /build/user/eclipse-3.2.2/source-tree/tmp/eclipse/plugins > > > > jarUp: > > > > jarIng: > > > > jarUp: > > > > jarIng: > > [exec] eclipse/ > > [exec] eclipse/plugins/ > > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/ > > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/META-INF/ > > [exec] > > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/META-INF/MANIFEST.MF > > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/ > > [exec] > > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/ > > [exec] > > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about_files/ > > [exec] > > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about_files/license.html > > [exec] > > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about_files/ucdterms.txt > > [exec] > > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/src.zip > > [exec] eclipse/plugins/com.ibm.iE: Caught signal 'Terminated': > > terminating immediately > > > > Session terminated, killing > > shell...cu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about.html > > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/about.html > > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/plugin.xml > > [exec] > > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/plugin.properties > > [exec] eclipse/plugins/com.ibm.icu_3.4.5.20061213.jar > > [exec] eclipse/plugins/com.jcraft.jsch_0.1.28.jar > > > > gzipResults: > >
Bug#476067: marked as done (eclipse: FTBFS: timeout during build (on various archs))
Your message dated Thu, 24 Dec 2009 18:18:32 +0100 with message-id <20091224171832.ga30...@xanadu.blop.info> and subject line Re: Bug#476067: eclipse: FTBFS: build takes a very, very long time (or just blocks?) has caused the Debian Bug report #476067, regarding eclipse: FTBFS: timeout during build (on various archs) 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.) -- 476067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: eclipse Version: 3.2.2-5 Severity: important User: debian...@lists.debian.org Usertags: qa-ftbfs-20080413 qa-ftbfs Justification: FTBFS on i386 Hi, I haven't managed to build eclipse recently. I build on a quad-opteron, so I wouldn't expect it to take more than 8 hours (which it does). Is there something that could be done to make it faster to build, or should I just exclude eclipse from my rebuilds? In the past, I could build eclipse in less than 1 hour. Thank you, Relevant part: > main: > [mkdir] Created dir: /build/user/eclipse-3.2.2/source-tree/tmp > [copy] Copying 8 files to > /build/user/eclipse-3.2.2/source-tree/tmp/eclipse/plugins/com.ibm.icu.source_3.4.5.20061213 > [copy] Copying 1 file to > /build/user/eclipse-3.2.2/source-tree/tmp/eclipse/plugins > [copy] Copying 1 file to > /build/user/eclipse-3.2.2/source-tree/tmp/eclipse/plugins > > jarUp: > > jarIng: > > jarUp: > > jarIng: > [exec] eclipse/ > [exec] eclipse/plugins/ > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/ > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/META-INF/ > [exec] > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/META-INF/MANIFEST.MF > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/ > [exec] > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/ > [exec] > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about_files/ > [exec] > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about_files/license.html > [exec] > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about_files/ucdterms.txt > [exec] > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/src.zip > [exec] eclipse/plugins/com.ibm.iE: Caught signal 'Terminated': > terminating immediately > > Session terminated, killing > shell...cu.source_3.4.5.20061213/src/com.ibm.icu_3.4.5.20061213/about.html > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/about.html > [exec] eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/plugin.xml > [exec] > eclipse/plugins/com.ibm.icu.source_3.4.5.20061213/plugin.properties > [exec] eclipse/plugins/com.ibm.icu_3.4.5.20061213.jar > [exec] eclipse/plugins/com.jcraft.jsch_0.1.28.jar > > gzipResults: > [move] Moving 1 file to /build/user/eclipse-3.2.2/source-tree/tmp/eclipse > [gzip] Building: > /build/user/eclipse-3.2.2/source-tree/result/org.eclipse.sdk-M20070212-1330-linux.gtk.x86.tar.gz > > build.doc.plugins: > > install.eclipse.tar: > [mkdir] Created dir: > /build/user/eclipse-3.2.2/source-tree/tmp/eclipse/plugins > sbuild received SIGTERM -- shutting down > Killing dpkg-buildpackage subprocess 16883 > ** > Finished at 20080414-0634 > Build needed 00:00:00, 0k disk space > ...killed. > DC-Build-Status: Failed 27805.127637s > DC-Time-Estimation: 27805.127637 versus expected 3379 (r/m: 7.22880368067476 > ; m: 3379.0) The full build log is available from: http://people.debian.org/~lucas/logs/2008/04/13 -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Version: 3.4.1-1 No longer fails, closing On 14/04/08 at 13:32 +0200, Lucas Nussbaum wrote: > Package: eclipse > Version: 3.2.2-5 > Severity: important > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20080413 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > I haven't managed to build eclipse recently. I build on a quad-opteron, > so I wouldn't expect it to take more than 8 hours (which it does). > > Is there something that could be done to make it faster to build, or > should I just exclude eclipse from my rebuilds? > > In the past, I could build eclipse in less than 1 hour. > > Thank you, > > Relevant part: > > main: > >
Bug#560500: marked as done (tagcoll2: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope)
Your message dated Thu, 24 Dec 2009 18:15:19 +0100 with message-id <20091224171519.ga30...@xanadu.blop.info> and subject line Re: Bug#560500: tagcoll2: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope has caused the Debian Bug report #560500, regarding tagcoll2: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope 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.) -- 560500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tagcoll2 Version: 2.0.11-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -g -O2 -g -Wall -O2 -Wall -c > TagexprParser.cc -fPIC -DPIC -o TagexprParser.o > In file included from /usr/include/wibble/test.h:3, > from /usr/include/wibble/exception.h:25, > from TagexprParser.cc:26: > /usr/include/wibble/string.h: In function 'std::string > wibble::str::fmt(std::string, ...)': > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in this > scope > make[4]: *** [TagexprParser.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/tagcoll2_2.0.11-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- no longer fails, closing On 11/12/09 at 09:18 +0100, Lucas Nussbaum wrote: > Source: tagcoll2 > Version: 2.0.11-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091210 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part: > > g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -g -O2 -g -Wall -O2 -Wall -c > > TagexprParser.cc -fPIC -DPIC -o TagexprParser.o > > In file included from /usr/include/wibble/test.h:3, > > from /usr/include/wibble/exception.h:25, > > from TagexprParser.cc:26: > > /usr/include/wibble/string.h: In function 'std::string > > wibble::str::fmt(std::string, ...)': > > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in > > this scope > > make[4]: *** [TagexprParser.lo] Error 1 > > The full build log is available from: > > http://people.debian.org/~lucas/logs/2009/12/10/tagcoll2_2.0.11-1_lsid64.buildlog > > 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. > > -- > | Lucas Nussbaum > | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | > | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | > > > -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message ---
Processed: Bug#562446 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 562446 pending Bug #562446 [src:quilt] quilt: FTBFS: sh: /bin/ed: not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560492: marked as done (buffy: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope)
Your message dated Thu, 24 Dec 2009 18:14:23 +0100 with message-id <20091224171423.ga30...@xanadu.blop.info> and subject line Re: Bug#560492: buffy: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope has caused the Debian Bug report #560492, regarding buffy: FTBFS: string.h:63: error: 'vasprintf' was not declared in this scope 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.) -- 560492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: buffy Version: 1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > g++ -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb > -I/usr/include/libpng12 -I/usr/include/sigc++-2.0 > -I/usr/lib/sigc++-2.0/include -I/usr/include/gtkmm-2.4 > -I/usr/lib/gtkmm-2.4/include -I/usr/include/giomm-2.4 > -I/usr/lib/giomm-2.4/include -I/usr/include/pangomm-1.4 > -I/usr/lib/pangomm-1.4/include -I/usr/include/gtk-unix-print-2.0 > -I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 > -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 > -I/usr/lib/glibmm-2.4/include -I/usr/include/cairomm-1.0 > -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include > -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 > -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 > -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -g -O2 -g -Wall -O2 -Wall -c -o > buffy-Environment.o `test -f 'Environment.cc' || echo './'`Environment.cc > In file included from /usr/include/wibble/test.h:3, > from /usr/include/wibble/exception.h:25, > from Environment.cc:24: > /usr/include/wibble/string.h: In function 'std::string > wibble::str::fmt(std::string, ...)': > /usr/include/wibble/string.h:63: error: 'vasprintf' was not declared in this > scope > Environment.cc: In member function 'void Environment::spawnCommand(const > std::string&)': > Environment.cc:122: warning: missing sentinel in function call > make[3]: *** [buffy-Environment.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/buffy_1.0-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- no longer fails, closing On 11/12/09 at 09:12 +0100, Lucas Nussbaum wrote: > Source: buffy > Version: 1.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091210 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part: > > g++ -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 > > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo > > -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 > > -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/sigc++-2.0 > > -I/usr/lib/sigc++-2.0/include -I/usr/include/gtkmm-2.4 > > -I/usr/lib/gtkmm-2.4/include -I/usr/include/giomm-2.4 > > -I/usr/lib/giomm-2.4/include -I/usr/include/pangomm-1.4 > > -I/usr/lib/pangomm-1.4/include -I/usr/include/gtk-unix-print-2.0 > > -I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 > > -I/usr/lib/gdkmm-2.4/include -I/usr/include/glibmm-2.4 > > -I/usr/lib/glibmm-2.4/include -I/usr/include/cairomm-1.0 > > -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include > > -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 > > -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 > > -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -g -O2 -g -Wall -O2 -Wall -c -o buffy > -Environment.o `test -f 'Envir
Bug#560238: netbase: broke dwww & lighttpd (localhost)
Package: netbase Version: 4.40 Severity: normal HTTP connections to localhost for dwww & lighttpd were refused after netbase transitioned from 4.37 -> 4.40. Changing net.ipv6.bindv6only = 1 to net.ipv6.bindv6only = 0 in /etc/sysctl.d/bindv6only.conf and rebooting resolved the issue. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages netbase depends on: ii initscripts 2.87dsf-8 scripts for initializing and shutt ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip Versions of packages netbase recommends: ii ifupdown 0.6.9 high level tools to configure netw netbase suggests no packages. -- debconf information: netbase/upgrade-note/etc-network-interfaces-pre-3.17-1: netbase/upgrade-note/init.d-split-pre-3.16-1: netbase/upgrade-note/radius-ports-pre-3.05: netbase/upgrade-note/portmap-restart-pre-3.11-2: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562358: mlpost: FTBFS: mkdir -p img/ fails?
Stéphane Glondu a écrit :
> Lucas Nussbaum a écrit :
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64.
>> [...]
>>> mkdir -p img/ && cd img/ && ../customdoc/img_doc.byte >> /dev/null && cd ..
>>> + mkdir -p img/ && cd img/ && ../customdoc/img_doc.byte >> /dev/null && cd
>>> ..
>>> Command exited with code 1.
>>> make[1]: *** [doc] Error 10
>
> The package builds fine in a clean squeeze chroot, but doesn't in sid. I
> am investigating.
This is because of mpost. With the attached file, mpost exists with code
1; however, I don't see any error:
r...@korell:/tmp# mpost -interaction="nonstopmode" img_doc.mp end
This is MetaPost, version 1.208 (kpathsea version 5.0.0)
(./img_doc.mp (/usr/share/texmf/metapost/context/base/mp-tool.mp)
(/usr/share/texmf/metapost/context/base/mp-spec.mp) [19] [18] [17] [16] [15]
[14] [13] [12] [11] [10] [9] [8] [7] [6] [5] [4] [3] [2] [1])
(see the transcript file for additional information)
19 output files written: img_doc.1 .. img_doc.19
Transcript written on img_doc.log.
r...@korell:/tmp# echo $?
1
The version in testing exits with code 0 on the same file.
Do texlive-metapost maintainers have a clue?
Cheers,
--
Stéphane
input mp-tool ; % some initializations and auxiliary macros
input mp-spec ; % macros that support special features
%redefinition
def doexternalfigure (expr filename) text transformation =
begingroup ; save p, t ; picture p ; transform t ;
p := nullpicture ; t := identity transformation ;
flush_special(10, 9,
dddecimal (xxpart t, yxpart t, xypart t) & " " &
dddecimal (yypart t, xpart t, ypart t) & " " & filename) ;
addto p contour unitsquare transformed t ;
setbounds p to unitsquare transformed t ;
_color_counter_ := _color_counter_ + 1 ;
draw p withcolor
(_special_signal_/_special_div_,_color_counter_/_special_div_,_special_counter_/_special_div_)
;
endgroup ;
enddef ;
vardef reset_extra_specials =
enddef ;
tracingchoices := 1;
prologues := 0;
mpprocset := 0;
verbatimtex
%&latex
\documentclass{article}
\usepackage[T1]{fontenc}
\begin{document}
etex
beginfig(19)
path pathb ;
pathb = ((0, 0) .. (40, 25));
numeric numb ;
numb = length (pathb);
numeric numc ;
numc = (1 * numb);
pair potb ;
potb = (point numc of (pathb));
pair potc ;
potc = (direction numc of (pathb));
numeric numd ;
numd = (xpart potc ++ ypart potc);
pair potd ;
potd = ((-1 * (4 * (if (numd = 0): 0 else: (1 / numd) fi))) * potc
);
pair pote ;
pote = (potb + (potd rotated 30));
pair potf ;
potf = (potb + (potd rotated -30)
);
draw ((pathb) shifted ((0 * (direction (0.5 * numb) of (pathb))) rotated 90
)) cutafter ((pote -- potf)) ;
fill pote -- potb --
potf -- cycle;
dotlabel.top(btex {\footnotesize pt} etex, (40, 25));
path pathc ;
pathc = (((4.5, -4.5) -- (4.5, 4.5) -- (-4.5, 4.5) -- (-4.5, -4.5
) -- cycle) shifted (0, 0)
);
draw pathc withcolor 0 * white ;
draw ((pathc) shifted (40, 25)) withcolor 0 * white ;
endfig;
beginfig(18)
picture picl, picb ;
picl = currentpicture;
currentpicture := nullpicture;
numeric nume ;
nume = (1 / numd);
pair potg ;
potg = ((-1 * (4 * (if (numd = 0): 0 else: nume fi))) * potc
);
pair poth ;
poth = (potb + (potg rotated 30));
pair poti ;
poti = (potb + (potg rotated -30)
);
path pathd ;
pathd = ((pathb) shifted ((0 * (direction (0.5 * numb) of (pathb))) rotated
90));
path pathe ;
pathe = pathd cutafter ((poth -- poti))
;
draw pathe;
path pathf ;
pathf = poth -- potb --
poti -- cycle;
fill pathf;
picture picc;
picc := btex {\footnotesize pt} etex;
dotlabel.top(picc, (40, 25));
picture picd;
picd := btex {\footnotesize (0,0)} etex;
dotlabel.bot(picd, (0, 0));
picb = currentpicture;
currentpicture := picl;
picture picm, pice ;
picm = currentpicture;
currentpicture := nullpicture;
draw pathe;
fill pathf;
dotlabel.top(picc, (40, 25));
dotlabel.bot(picd, (0, 0));
pice = currentpicture;
currentpicture := picm;
pair potj ;
potj = (urcorner pice);
pair potk ;
potk = ((0.5 * (llcorner picb)) + (0.5 * potj)
);
numeric numf ;
numf = ypart potk;
numeric numg ;
numg = (numf - numf
);
numeric numh ;
numh = xpart potk;
picture picn, picf ;
picn = currentpicture;
currentpicture := nullpicture;
draw pathe;
fill pathf;
dotlabel.top(picc, (40, 25));
dotlabel.bot(picd, (0, 0));
picf = currentpicture;
currentpicture := picn;
numeric numi ;
numi = max( 0, (xpart (potj - (ulcorner picf)) + 4)
);
numeric numj ;
numj = (numi / 2);
numeric numk ;
numk = (numh - numj
);
picture pico, picg ;
pico = currentpicture;
currentpicture := nullpicture;
draw pathe;
fill pathf;
dotlabel.top(picc, (40, 25));
dotlabel.bot(picd, (0, 0));
picg = currentpicture;
currentpicture := pico;
draw picg) shifted (((numk + numj) - numh), numg))) shifted (0, (numf -
(numg + numf)))
);
picture picp, pich ;
pic
Bug#562434: zzuf: FTBFS: tests failed
Source: zzuf Version: 0.12-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory `/build/user-zzuf_0.12-1-amd64-h5xfZ6/zzuf-0.12' > make[3]: Leaving directory `/build/user-zzuf_0.12-1-amd64-h5xfZ6/zzuf-0.12' > make[2]: Leaving directory `/build/user-zzuf_0.12-1-amd64-h5xfZ6/zzuf-0.12' > make[1]: Leaving directory `/build/user-zzuf_0.12-1-amd64-h5xfZ6/zzuf-0.12' > ./test/testsuite.sh > *** running zzuf test suite with seed 33011212 *** > > *** check #1: random number generator *** > *** 20 MiB of zeroes, ratio 0.1 *** > expected ... 0 > try 0 .. 0 > try 1 .. 0 > try 2 .. 0 > try 3 .. 0 > try 4 .. 0 > try 5 .. 0 > try 6 .. 0 > try 7 .. 0 > try 8 .. 0 > try 9 .. 0 > min/avg/max 0/0/0 .. ok > *** 20 MiB of zeroes, ratio 0.0001 *** > expected ... 1 > try 0 .. 1 > try 1 .. 0 > try 2 .. 1 > try 3 .. 0 > try 4 .. 3 > try 5 .. 1 > try 6 .. 1 > try 7 .. 3 > try 8 .. 1 > try 9 .. 2 > min/avg/max 0/1/3 .. ok > *** 20 MiB of zeroes, ratio 0.001 *** > expected ... 16 > try 0 .. 17 > try 1 .. 15 > try 2 .. 19 > try 3 .. 10 > try 4 .. 12 > try 5 .. 9 > try 6 .. 18 > try 7 .. 12 > try 8 .. 18 > try 9 .. 20 > min/avg/max 9/15/20 .. ok > *** 20 MiB of zeroes, ratio 0.01 *** > expected ... 167 > try 0 .. 169 > try 1 .. 164 > try 2 .. 189 > try 3 .. 155 > try 4 .. 187 > try 5 .. 171 > try 6 .. 143 > try 7 .. 153 > try 8 .. 169 > try 9 .. 173 > min/avg/max 143/167/189 .. ok > *** 20 MiB of zeroes, ratio 0.1 *** > expected ... 1677 > try 0 .. 1648 > try 1 .. 1717 > try 2 .. 1684 > try 3 .. 1651 > try 4 .. 1685 > try 5 .. 1663 > try 6 .. 1654 > try 7 .. 1642 > try 8 .. 1621 > try 9 .. 1666 > min/avg/max 1621/1663/1717 .. ok > *** 20 MiB of zeroes, ratio 0.0001 *** > expected ... 16775 > try 0 .. 16856 > try 1 .. 16834 > try 2 .. 16770 > try 3 .. 16810 > try 4 .. 16830 > try 5 .. 16834 > try 6 .. 16714 > try 7 .. 16728 > try 8 .. 16786 > try 9 .. 16776 > min/avg/max 16714/16794/16856 .. ok > *** 20 MiB of zeroes, ratio 0.001 *** > expected ... 167604 > try 0 .. 167754 > try 1 .. 167715 > try 2 .. 167592 > try 3 .. 167657 > try 4 .. 167592 > try 5 .. 167586 > try 6 .. 167592 > try 7 .. 167547 > try 8 .. 167563 > try 9 .. 167552 > min/avg/max 167547/167615/167754 .. ok > *** 20 MiB of zeroes, ratio 0.01 *** > expected ... 1661055 > try 0 .. 1661424 > try 1 .. 1661089 > try 2 .. 1661268 > try 3 .. 1661284 > try 4 .. 1661214 > try 5 .. 1661228 > try 6 .. 1661510 > try 7 .. 1660887 > try 8 .. 1661530 > try 9 .. 1661189 > min/avg/max 1660887/1661262/1661530 .. ok > *** 20 MiB of zeroes, ratio 0.1 *** > expected ... 15205967 > try 0 .. 15206658 > try 1 .. 15208821 > try 2 .. 15209196 > try 3 .. 15210393 > try 4 .. 15209025 > try 5 .. 15208282 > try 6 .. 15203658 > try 7 .. 15207670 > try 8 .. 15205468 > try 9 .. 15209141 > min/avg/max 15203658/15207831/15210393 .. ok > > *** check #2: libc functions coverage *** > *** file ./test/file-00, ratio 0.0 *** > *** should be bb7df04e1b0a2570657527a7e108ae23 *** > zzuf . ok > zzcat 1 .. ok > zzcat 2 .. ok > zzcat 3 .. ok > cat .. ok > |cat . ok > dd(bs=65536) . ok > dd(bs=) .. ok > dd(bs=1024) .. ok > dd(bs=1) . ok > *** file ./test/file-ff, ratio 0.0 *** > zzuf . 3df7b33399422731e8e5615785c0536d > zzcat 1 .. ok > zzcat 2 .. ok > zzcat 3 .. ok > cat .. ok > |cat . ok > dd(bs=65536) . ok > dd(bs=) .. ok > dd(bs=1024) .. ok > dd(bs=1) . ok > *** file ./test/file-text, ratio 0.0 *** > zzuf . 899fe000acdebed7440b1fc1e1ad8727 > zzcat 1 .. ok > zzcat 2 .. ok > zzcat 3 .. ok > cat .. ok > |cat . ok > dd(bs=65536) . ok > dd(bs=) .. ok > dd(bs=1024) .. ok > dd(bs=1) . ok > head -n ...
Bug#560576: ibm-3270: FTBFS: configure: error: 'Cannot find xmkmf'
reopen 560576 reassign 560576 ftp.debian.org severity 560576 normal retitle 560576 RM: ibm-3270/main -- RoQA: superseded by package in non-free thanks Hi Ftpmasters, ibm-3270 is still available in unstable on hurd-i386, but was superseded by a package in non-free on every other arch. Could you please remove it from unstable/main and keep it in unstable/non-free? Thank you, Lucas On 14/12/09 at 12:41 +0100, Bastian Blank wrote: > On Fri, Dec 11, 2009 at 10:09:49AM +0100, Lucas Nussbaum wrote: > > Source: ibm-3270 > > Version: 3.3.4p6-3.2 > > This package is from oldstable. > > Bastian > > -- > There's coffee in that nebula! > -- Capt. Kathryn Janeway, Star Trek: Voyager, "The Cloud" > -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 504972 is serious
Processing commands for cont...@bugs.debian.org: > severity 504972 serious Bug #504972 [ggz-server] FTBFS with GCC 4.4: missing #include Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562440: dvipsk-ja: FTBFS: dpkg-shlibdeps: error: couldn't find library libkpathsea.so.4 needed by debian/dvipsk-ja/usr/bin/dvips (ELF format: 'elf64-x86-64'; RPATH: '').
Source: dvipsk-ja Version: 5.96+jp1.7a-3.1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory > `/build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/dvipsk' > /bin/sh ./../mkinstalldirs > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/bin > for p in afm2tfm dvips; do /bin/sh ../libtool --mode=install /usr/bin/install > -c $p > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/bin; > done > libtool: install: warning: `../kpathsea/libkpathsea.la' has not been > installed in `/usr/lib' > /usr/bin/install -c .libs/afm2tfm > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/bin/afm2tfm > libtool: install: warning: `../kpathsea/libkpathsea.la' has not been > installed in `/usr/lib' > /usr/bin/install -c .libs/dvips > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/bin/dvips > rm -f > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/bin/odvips > ln -s dvips > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/bin/odvips > /bin/sh ./../mkinstalldirs > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/man/man1 > > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/info > > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/dvips/base > mkdir > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/dvips > mkdir > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/dvips/base > for h in tex.pro texps.pro texc.pro special.pro finclude.pro color.pro > crop.pro hps.pro; do /usr/bin/install -c -m 644 $h > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/dvips/base/$h; > done > /usr/bin/install -c -d > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/dvips/config > /usr/bin/install -c -m 644 ./config.ps > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/dvips/config/config.ps > /usr/bin/install -c -d > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/fonts/map/dvips/ptex > /usr/bin/install -c -m 644 ./psfonts_jp.map > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/texmf/fonts/map/dvips/ptex/psfonts_jp.map > cd . && for i in dvips.i*; do \ > /usr/bin/install -c -m 644 $i > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/info/$i; > done > /usr/bin/install -c -m 644 ./dvips.1 > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/man/man1/dvips.1 > rm -f > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/man/man1/odvips.1 > ln -s dvips.1 > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/man/man1/odvips.1 > /usr/bin/install -c -m 644 ./afm2tfm.1 > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/man/man1/afm2tfm.1 > if /bin/sh -c 'install-info --version' >/dev/null 2>&1; then \ > install-info > --info-dir=/build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/info > > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/info/dvips.info; > \ > else true; fi > install-info: warning: nothing done since /usr/bin/install-info doesn't exist, > install-info: warning: you might want to install an info-browser package. > make[2]: Leaving directory > `/build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/dvipsk' > make[1]: Leaving directory > `/build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a' > # A portion of this package may overlap with the texlive-* packages, > # so we have to move or remove them beforehand. > cd > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/bin > && \ > rm -rf access afm2tfm dvipos kpseaccess kpsereadlink kpsestat > kpsewhich mktexlsr mktexmf mktexpk \ > mktextfm odvips readlink > cd > /build/user-dvipsk-ja_5.96+jp1.7a-3.1-amd64-w7WMix/dvipsk-ja-5.96+jp1.7a/debian/dvipsk-ja/usr/share/man/man1 > &&
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
Source: libgcgi
Version: 0.9.5.dfsg-5
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091223 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> dh_auto_clean
> dh_clean
> find . \( -type d -a -name .deps -prune -exec rm -rf {} \; \)
> dpatch deapply-all
> 01_update_libtool not applied to ./ .
> rm -rf patch-stamp patch-stampT debian/patched
> dpkg-source -b libgcgi-0.9.5.dfsg
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building libgcgi using existing
> libgcgi_0.9.5.dfsg.orig.tar.gz
> dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.diff.gz
> dpkg-source: warning: executable mode 0755 of
> 'debian/patches/01_update_libtool.dpatch' will not be represented in diff
> dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.dsc
> debian/rules build
> test -d debian/patched || install -d debian/patched
> dpatch apply-all
> applying patch 01_update_libtool to ./ ... ok.
> dpatch cat-all >>patch-stampT
> mv -f patch-stampT patch-stamp
> dh_testdir
> find . \( -type f -a -name "Makefile.*" -prune -exec touch {} \; \)
> # Add here commands to configure the package.
> CFLAGS="-Wall -g -O2" ./configure --host=x86_64-linux-gnu
> --build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man
> --infodir=\${prefix}/share/info --with-openssl
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing:
> Unknown `--run' option
> Try
> `/build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing
> --help' for more information
> configure: WARNING: `missing' script is too old or missing
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-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 x86_64-linux-gnu-gcc accepts -g... yes
> checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of x86_64-linux-gnu-gcc... gcc3
> checking how to run the C preprocessor... x86_64-linux-gnu-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 whether make sets $(MAKE)... (cached) yes
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for fgrep... /bin/grep -F
> checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for x86_64-linux-gnu-objdump... no
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for x86_64-linux-gnu-ar... no
> checking for ar... ar
> checking for x86_64-linux-gnu-strip... no
> checking for strip... strip
> checking for x86_64-linux-gnu-ranlib... no
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc
> object... ok
> 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 dlfcn.h... yes
> checking for objdir... .libs
> checking if x86_64-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
> checking for x86_64-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
> checking if x86_64-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
> checking if x86_64-linux-gnu-gcc static flag -static works... yes
> checking if x86_64-linux-gnu-gcc supports -c -o file.o... yes
> checking if x86_64-linux-gnu-gcc supports -c -o file.o... (cached) yes
> checking whether the x86_64-linux-gnu-gcc linker (/usr/bin/ld -m elf_x86_64)
> supports shared librarie
Bug#562444: monkeysphere: FTBFS: ./tests/basic: line 202: cpio: command not found
Source: monkeysphere Version: 0.26-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26' > MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/keytrans > ## > ### generating openpgp key... > gpg: keyring > `/build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26/tests/tmp/monkeyspheretest.Qhwqj5G/secring.gpg' > created > gpg: keyring > `/build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26/tests/tmp/monkeyspheretest.Qhwqj5G/pubring.gpg' > created > + > + > gpg: > /build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26/tests/tmp/monkeyspheretest.Qhwqj5G/trustdb.gpg: > trustdb created > gpg: key C1ADE1DA marked as ultimately trusted > gpg: done > ## > ### retrieving key timestamp... > gpg: checking the trustdb > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u > ## > ### exporting key to ssh file... > ## > ### reconvert key, and compare to key in gpg keyring... > conversions look good! > Now working with key 45DB037CC1ADE1DA at time 1261606897 > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u > /build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26/tests/tmp/monkeyspheretest.Qhwqj5G/pubring.gpg > - > pub 1024R/C1ADE1DA 2009-12-23 > uid [ultimate] testtest > > ## > ### test User ID addition... > gpg: key C1ADE1DA: "monkeymonkey" 1 new user ID > gpg: key C1ADE1DA: "monkeymonkey" 1 new signature > gpg: Total number processed: 1 > gpg: new user IDs: 1 > gpg: new signatures: 1 > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u > /build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26/tests/tmp/monkeyspheretest.Qhwqj5G/pubring.gpg > - > pub 1024R/C1ADE1DA 2009-12-23 > uid [ultimate] monkeymonkey > uid [ultimate] testtest > > ## > ### test User ID revocation ... > gpg: key C1ADE1DA: "monkeymonkey" 1 new signature > gpg: Total number processed: 1 > gpg: new signatures: 1 > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u > /build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26/tests/tmp/monkeyspheretest.Qhwqj5G/pubring.gpg > - > pub 1024R/C1ADE1DA 2009-12-23 > uid [ultimate] monkeymonkey > uid [ revoked] testtest > > ## > Monkeysphere keytrans test completed successfully! > ## > ### removing temp dir... > MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/basic > improper group writability on '/build' > > !!!WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING!!! > Permissions on testing directory > '/build/user-monkeysphere_0.26-1-amd64-Xb2E7q/monkeysphere-0.26/tests/tmp/monkeyspheretest.FKowpKO' > are > too loose to do proper strict permissions checking. Some tests > will be disabled or ignored. > > To avoid this warning (and to make sure that all tests are run > properly), please run these tests within a directory that meets > sshd's standards for "StrictModes yes" -- the directory (and every > one of its parents) should be owned only be the user running this > test or root, and should not be writable by group or other. > !!!WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING!!! > > > ## > ### configuring testuser home... > ./tests/basic: line 202: cpio: command not found > FAILED! > ### removing temp dir... > make[1]: *** [test] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/monkeysphere_0.26-1_lsid64.buildlog 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 cle
Bug#562445: ilisp: FTBFS: You don't have a working TeX binary installed
Source: ilisp Version: 5.12.0+cvs.2004.12.26-5 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory > `/build/user-ilisp_5.12.0+cvs.2004.12.26-5-amd64-fbBVfM/ilisp-5.12.0+cvs.2004.12.26/docs' > makeinfo ilisp.texi -o ilisp.info > texi2dvi ilisp.texi > You don't have a working TeX binary installed, but the texi2dvi script > can't proceed without it. If you want to use this script, you have to > install some kind of TeX, for example TeX Live Debian packages. You can do > that with this command: >apt-get install texlive > make[2]: *** [ilisp.dvi] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/ilisp_5.12.0+cvs.2004.12.26-5_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562436: afflib: FTBFS: CANNOT CREATE /tmp/blanke.aff
Source: afflib Version: 3.5.4+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory > `/build/user-afflib_3.5.4+dfsg-1-amd64-yETb52/afflib-3.5.4+dfsg/tools' > === MAKING THE TEST FILES === > Making the random ISO rawevidence.iso > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 rawevidence.iso > MD5(rawevidence.iso)= 5bd7e437809fd79c793de093eab1fcf2 > AFSIGN TEST === > Making X.509 keys > Generating a 1024 bit RSA private key > ...++ > ++ > writing new private key to 'agent.pem' > - > Generating a 1024 bit RSA private key > .++ > ..++ > writing new private key to 'analyst.pem' > - > Generating a 1024 bit RSA private key > ++ > ...++ > writing new private key to 'archives.pem' > - > Making an AFF file to sign > TERM environment variable not set. > Initial AFF file > TERM environment variable not set. > FAIL: test_signing.sh > AFRECOVERY TEST === > Make an X509 key > Generating a 1024 bit RSA private key > ..++ > .++ > writing new private key to '/tmp/recovery.pem' > - > Making the random ISO /tmp/recovery.iso > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 /tmp/recovery.iso > MD5(/tmp/recovery.iso)= b1d1e59edded9a645bbb514ce1b7e3da > SIGNING /tmp/recovery.iso > -rw--- 1 user sbuild 16784355 Dec 23 23:27 /tmp/recovery.afm > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 /tmp/recovery.iso > VERIFYING SIGNATURE > expat error: no element found at line 67 > > Filename: /tmp/recovery.afm > # Segments signed and Verified: 13 > # Segments unsigned: 0 > # Segments with corrupted signatures: 0 > > SIGNING CERTIFICATE : >Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com >Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > > Number of custody chains: 1 > - > Signed Bill of Material #1: > > SIGNING CERTIFICATE : >Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com >Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > Date: 2009-12-23T23:27:05 > Notes: > > - > > EVIDENCE FILE VERIFIES. > CORRUPTING FILE recovery.iso > 0+1 records in > 0+1 records out > 8 bytes (8 B) copied, 7.62527 s, 0.0 kB/s > ATTEMPTING RECOVERY > /tmp/recovery.afm has a bad signature > Attempting to repair page0 > Page page0 successfully repaired > expat error: no element found at line 67 > > Filename: /tmp/recovery.afm > # Segments signed and Verified: 13 > # Segments unsigned: 0 > # Segments with corrupted signatures: 0 > > SIGNING CERTIFICATE : >Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com >Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > > Number of custody chains: 1 > - > Signed Bill of Material #1: > > SIGNING CERTIFICATE : >Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com >Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > Date: 2009-12-23T23:27:05 > Notes: > > - > > EVIDENCE FILE VERIFIES. > MAKING SURE THAT THE MD5 HAS NOT CHANGED > ALL TESTS PASS > PASS: test_recovery.sh > === MAKING THE TEST FILES == > Making the random ISO /tmp/blank.iso > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 /tmp/blank.iso > MD5(/tmp/blank.iso)= a7edb11e279bd6c78893b4edc053dd1c > TERM environment variable not set. > TERM environment variable not set. > CANNOT CREATE /tmp/blanke.aff > Permission error prevents test from continuing. > PASS: test_passphrase.sh > === Putting a new metadata segment into blank.aff === > /tmp/blank.aff: 536 bytes transfered in 0.00 seconds. xfer rate: 35.73 > MBytes/sec > afsegment worked! > PASS: test_afsegment.sh > PASS: test_crypto.sh > make[3]: *** [check-TESTS] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/afflib_3.5.4+dfsg-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562435: cupsddk: FTBFS: (.text+0x12c4): undefined reference to `avahi_simple_poll_new'
Source: cupsddk Version: 1.2.3-5 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > Linking ppdc-static... > /usr/lib/libcups.a(http-support.o): In function `_httpResolveURI': > (.text+0x12c4): undefined reference to `avahi_simple_poll_new' > /usr/lib/libcups.a(http-support.o): In function `_httpResolveURI': > (.text+0x12dc): undefined reference to `avahi_simple_poll_get' > /usr/lib/libcups.a(http-support.o): In function `_httpResolveURI': > (.text+0x12f7): undefined reference to `avahi_client_new' > /usr/lib/libcups.a(http-support.o): In function `_httpResolveURI': > (.text+0x134b): undefined reference to `avahi_service_resolver_new' > /usr/lib/libcups.a(http-support.o): In function `_httpResolveURI': > (.text+0x1366): undefined reference to `avahi_simple_poll_loop' > /usr/lib/libcups.a(http-support.o): In function `_httpResolveURI': > (.text+0x1379): undefined reference to `avahi_client_free' > /usr/lib/libcups.a(http-support.o): In function `_httpResolveURI': > (.text+0x1383): undefined reference to `avahi_simple_poll_free' > /usr/lib/libcups.a(http-support.o): In function `httpAssembleURI': > (.text+0x1bd7): undefined reference to `avahi_string_list_find' > /usr/lib/libcups.a(http-support.o): In function `httpAssembleURI': > (.text+0x1bf9): undefined reference to `avahi_string_list_get_pair' > /usr/lib/libcups.a(http-support.o): In function `httpAssembleURI': > (.text+0x1c3d): undefined reference to `avahi_address_snprint' > /usr/lib/libcups.a(http-support.o): In function `httpAssembleURI': > (.text+0x1c69): undefined reference to `avahi_simple_poll_quit' > /usr/lib/libcups.a(http-support.o): In function `httpAssembleURI': > (.text+0x1cd1): undefined reference to `avahi_service_resolver_free' > /usr/lib/libcups.a(http-support.o): In function `httpAssembleURI': > (.text+0x1cd9): undefined reference to `avahi_simple_poll_quit' > /usr/lib/libcups.a(http-support.o): In function `httpEncode64_2': > (.text+0x394): undefined reference to `avahi_simple_poll_quit' > collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/cupsddk_1.2.3-5_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562437: jakarta-ecs: FTBFS: java errors
Source: jakarta-ecs
Version: 1.4.2-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091223 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory
> `/build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2'
> make[1]: Nothing to be done for `update-config'.
> make[1]: Leaving directory
> `/build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2'
> cd . && /usr/lib/jvm/default-java/bin/java -classpath
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/lib/jvm/default-java/lib/tools.jar
> -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true
> -Dcompile.optimize=true -buildfile build/build-ecs.xml jar
> Buildfile: build/build-ecs.xml
>
> env:
> [echo] build.compiler = classic
> [echo] java.home = /usr/lib/jvm/java-6-openjdk/jre
> [echo] user.home = /home/user
> [echo] java.class.path =
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/lib/jvm/default-java/lib/tools.jar
> [echo]
>
> prepare:
> [mkdir] Created dir:
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin
> [mkdir] Created dir:
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/classes
> [mkdir] Created dir:
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src
> [copy] Copying 387 files to
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org
>
> compile:
> [javac] Compiling 381 source files to
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/classes
> [javac] This version of java does not support the classic compiler;
> upgrading to modern
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:62:
> package org.apache.regexp does not exist
> [javac] import org.apache.regexp.RE;
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:63:
> package org.apache.regexp does not exist
> [javac] import org.apache.regexp.RESyntaxException;
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:124:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = (RE)enumerate.nextElement();
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:124:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = (RE)enumerate.nextElement();
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:142:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = new RE(expression);
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:142:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = new RE(expression);
> [javac]^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:145:
> cannot find symbol
> [javac] symbol : class RESyntaxException
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] catch (RESyntaxException e) {
> [javac]^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:160:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = new RE(expression);
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:160:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = new RE(expression);
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:177:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.a
Bug#562446: quilt: FTBFS: sh: /bin/ed: not found
Source: quilt Version: 0.48-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/build/user-quilt_0.48-3-amd64-AT2s_g/quilt-0.48' > [add-filename-check.test] > [1] $ rm -rf d -- ok > [2] $ mkdir -p d/patches -- ok > [3] $ cd d -- ok > [4] $ quilt new test.diff -- ok > [7] $ echo foo > foo -- ok > [8] $ quilt add foo -- ok > [11] $ quilt add patches/bar -- ok > [14] $ quilt add .pc/baz -- ok > [17] $ cd .. -- ok > [18] $ rm -rf d -- ok > 10 commands (10 passed, 0 failed) > [annotate.test] > [1] $ rm -rf d -- ok > [2] $ mkdir -p d/patches -- ok > [3] $ cd d -- ok > [5] $ cat > foo -- ok > [10] $ quilt new patch -- ok > [13] $ quilt add foo -- ok > [16] $ sed -e 's:b:B:' foo > foo.new -- ok > [17] $ mv foo.new foo -- ok > [18] $ quilt refresh -- ok > [21] $ quilt annotate foo -- failed > sh: /bin/ed: not found!= foo > patch: /bin/ed FAILED!= 1Bar > foo != 1 Baz > Bar != > Baz != 1 patches/patch > != ~ > 1 patches/patch != ~ > [28] $ quilt new patch2 -- ok > [31] $ quilt add foo -- ok > [34] $ sed -e 's:Baz:baz:' foo > foo.new -- ok > [35] $ mv foo.new foo -- ok > [36] $ quilt refresh -- ok > [39] $ quilt annotate foo -- failed > sh: /bin/ed: not found!= foo > patch: /bin/ed FAILED!= 1Bar > foo != 2 baz > Bar != > baz != 1 patches/patch > != 2patches/patch2 > 1 patches/patch != ~ > 2 patches/patch2 != ~ > [47] $ quilt new patch3 -- ok > [50] $ quilt add foo -- ok > [53] $ sed -e '/Bar/d' foo > foo.new -- ok > [54] $ mv foo.new foo -- ok > [55] $ quilt refresh -- ok > [58] $ quilt annotate foo -- failed > sh: /bin/ed: not found!= foo > foo != 2 baz > baz != >!= 1 patches/patch > != 2patches/patch2 > 1 patches/patch != 3patches/patch3 > 2 patches/patch2 != ~ > 3 patches/patch3 != ~ > [66] $ quilt annotate -P patch3 foo -- failed > sh: /bin/ed: not found!= foo > patch: /bin/ed FAILED!= 2baz > foo != > baz != 1 patches/patch >!= 2 patches/patch2 > != 3patches/patch3 > 1 patches/patch != ~ > 2 patches/patch2 != ~ > 3 patches/patch3 != ~ > [74] $ quilt annotate -P patch2 foo -- failed > sh: /bin/ed: not found!= foo > patch: /bin/ed FAILED!= 1Bar > foo != 2 baz > Bar != > baz != 1 patches/patch > != 2patches/patch2 > 1 patches/patch != ~ > 2 patches/patch2 != ~ > [82] $ quilt annotate -P patch foo -- failed > sh: /bin/ed: not found!= foo > patch: /bin/ed FAILED!= 1Bar > foo != 1 Baz > Bar != > Baz != 1 patches/patch > != ~ > 1 patches/patch != ~ > [89] $ quilt new patch4 -- ok > [92] $ cat > jkl -- ok > [96] $ quilt add jkl wrz -- ok > [100] $ rm -f jkl -- ok > [101] $ cat > wrz -- ok > [105] $ quilt refresh -- ok > [108] $ quilt annotate jkl -- failed > sh: /bin/ed: not found!= > patch: /bin/ed FAILED!= 1patches/patch4 >!= ~ >!= ~ > != ~ > 1 patches/patch4 != ~ > [112] $ quilt annotate wrz -- failed > sh: /bin/ed: not found!= 1one > != 1two > 1 patches/patch4 != > ~ != 1patches/patch4 > [118] $ cd .. -- ok > make[1]: *** [test/.annotate.ok] Error 8 The full b
Bug#562328: marked as done (coinor-dylp: FTBFS: cp: cannot stat `DyLP/doc/dylp.pdf': No such file or directory)
Your message dated Thu, 24 Dec 2009 16:47:26 + with message-id and subject line Bug#562328: fixed in coinor-dylp 1.5.0-3 has caused the Debian Bug report #562328, regarding coinor-dylp: FTBFS: cp: cannot stat `DyLP/doc/dylp.pdf': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 562328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coinor-dylp Version: 1.5.0-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091213 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory > `/build/user-coinor-dylp_1.5.0-2-amd64-TaXvLl/coinor-dylp-1.5.0' > make[3]: Nothing to be done for `install-exec-am'. > make[3]: Nothing to be done for `install-data-am'. > make[3]: Leaving directory > `/build/user-coinor-dylp_1.5.0-2-amd64-TaXvLl/coinor-dylp-1.5.0' > make[2]: Leaving directory > `/build/user-coinor-dylp_1.5.0-2-amd64-TaXvLl/coinor-dylp-1.5.0' > make[1]: Leaving directory > `/build/user-coinor-dylp_1.5.0-2-amd64-TaXvLl/coinor-dylp-1.5.0' > dh_installdirs -pcoinor-libdylp-doc > dh_installdocs -pcoinor-libdylp-doc ./README > cp: cannot stat `DyLP/doc/dylp.pdf': No such file or directory > dh_installdocs: cp -a DyLP/doc/dylp.pdf > debian/coinor-libdylp-doc/usr/share/doc/coinor-libdylp-doc returned exit code > 1 > make: *** [binary-install/coinor-libdylp-doc] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/13/coinor-dylp_1.5.0-2_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: coinor-dylp Source-Version: 1.5.0-3 We believe that the bug you reported is fixed in the latest version of coinor-dylp, which is due to be installed in the Debian FTP archive: coinor-dylp_1.5.0-3.diff.gz to main/c/coinor-dylp/coinor-dylp_1.5.0-3.diff.gz coinor-dylp_1.5.0-3.dsc to main/c/coinor-dylp/coinor-dylp_1.5.0-3.dsc coinor-libdylp-dev_1.5.0-3_amd64.deb to main/c/coinor-dylp/coinor-libdylp-dev_1.5.0-3_amd64.deb coinor-libdylp-doc_1.5.0-3_all.deb to main/c/coinor-dylp/coinor-libdylp-doc_1.5.0-3_all.deb coinor-libdylp0-dbg_1.5.0-3_amd64.deb to main/c/coinor-dylp/coinor-libdylp0-dbg_1.5.0-3_amd64.deb coinor-libdylp0_1.5.0-3_amd64.deb to main/c/coinor-dylp/coinor-libdylp0_1.5.0-3_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 562...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Soeren Sonnenburg (supplier of updated coinor-dylp 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: Thu, 24 Dec 2009 17:09:04 +0100 Source: coinor-dylp Binary: coinor-libdylp0 coinor-libdylp-dev coinor-libdylp-doc coinor-libdylp0-dbg Architecture: source all amd64 Version: 1.5.0-3 Distribution: unstable Urgency: low Maintainer: Soeren Sonnenburg Changed-By: Soeren Sonnenburg Description: coinor-libdylp-dev - Linear programming solver using of the dynamic simplex algorithm coinor-libdylp-doc - Linear programming solver using of the dynamic simplex algorithm coinor-libdylp0 - Linear programming solver using the dynamic simplex algorithm coinor-libdylp0-dbg - Linear programming solver using of the dynamic simplex algorithm Closes: 562328 Changes: coinor-dylp (1.5.0-3) unstable; urgency=low . * Build depend on texlive-latex-extra and texlive-font-utils (Closes: #562328) Checksums-Sha1: 8fcd7e472646737f814869c3cbb1c34420c99a5c 2085 coinor-dylp_1.5.0-3.dsc ce75499b48e8fc0823a5ed49f7efa455fa06d7f1 8194 coinor-dylp_1.5.0-3.diff.gz b3b01189e2f318f310d821256011bc5de86d7781 1500650 coinor-libdylp-doc_1.5.0-3_all.deb 85a1284
Bug#562438: compiz: FTBFS: compiz-window-manager.c:30:32: error: gconf/gconf-client.h: No such file or directory
Source: compiz Version: 0.8.2-6 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > if /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I. -I../.. -D_REENTRANT -I/usr/include/gnome-window-settings-2.0 > -I/usr/include/gtk-2.0 -I/usr/include/gnome-desktop-2.0 > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 > -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/startup-notification-1.0 > -DMETACITY_THEME_DIR=\""/usr/share/themes"\" > -DLOCALEDIR="\"/usr/share/locale"\"-Wall -g -O2 -Wpointer-arith > -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations > -Wnested-externs -D_FORTIFY_SOURCE=2 -MT compiz-window-manager.lo -MD -MP -MF > ".deps/compiz-window-manager.Tpo" -c -o compiz-window-manager.lo > compiz-window-manager.c; \ > then mv -f ".deps/compiz-window-manager.Tpo" > ".deps/compiz-window-manager.Plo"; else rm -f > ".deps/compiz-window-manager.Tpo"; exit 1; fi > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -D_REENTRANT > -I/usr/include/gnome-window-settings-2.0 -I/usr/include/gtk-2.0 > -I/usr/include/gnome-desktop-2.0 -I/usr/lib/gtk-2.0/include > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb > -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -I/usr/include/startup-notification-1.0 > -DMETACITY_THEME_DIR=\"/usr/share/themes\" -DLOCALEDIR=\"/usr/share/locale\" > -Wall -g -O2 -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes > -Wmissing-declarations -Wnested-externs -D_FORTIFY_SOURCE=2 -MT > compiz-window-manager.lo -MD -MP -MF .deps/compiz-window-manager.Tpo -c > compiz-window-manager.c -fPIC -DPIC -o .libs/compiz-window-manager.o > compiz-window-manager.c:30:32: error: gconf/gconf-client.h: No such file or > directory > In file included from /usr/include/gtk-2.0/gtk/gtk.h:228, > from > /usr/include/gnome-desktop-2.0/libgnome/gnome-desktop-item.h:35, > from > /usr/include/gnome-window-settings-2.0/gnome-window-manager.h:31, > from compiz-window-manager.h:6, > from compiz-window-manager.c:33: > /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47: warning: function declaration > isn't a prototype > compiz-window-manager.c:91: error: expected specifier-qualifier-list before > 'GConfClient' > compiz-window-manager.c:98: error: expected ')' before '*' token > compiz-window-manager.c: In function 'compiz_change_settings': > compiz-window-manager.c:137: warning: implicit declaration of function > 'gconf_client_set_string' > compiz-window-manager.c:137: warning: nested extern declaration of > 'gconf_client_set_string' > compiz-window-manager.c:137: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c:142: warning: implicit declaration of function > 'gconf_client_set_bool' > compiz-window-manager.c:142: warning: nested extern declaration of > 'gconf_client_set_bool' > compiz-window-manager.c:142: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c:148: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c:153: warning: implicit declaration of function > 'gconf_client_set_int' > compiz-window-manager.c:153: warning: nested extern declaration of > 'gconf_client_set_int' > compiz-window-manager.c:153: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c:162: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c:169: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c:189: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c: In function 'compiz_get_settings': > compiz-window-manager.c:211: warning: implicit declaration of function > 'gconf_client_get_string' > compiz-window-manager.c:211: warning: nested extern declaration of > 'gconf_client_get_string' > compiz-window-manager.c:211: error: 'CompizWindowManagerPrivate' has no > member named 'gconf' > compiz-window-manager.c:218: error: 'CompizWindowManagerPrivate' has no > member named 'font' > compiz-window-manager.c:219: error: 'CompizWindowManagerPrivate' has no > member named 'font' > compiz-window-manager.c:221: error: 'CompizWindowManagerPrivate' has no > member named 'font' > compiz-window-manager.c:223: error: 'CompizWindowManagerPrivate' has no > member named 'font' > compiz-window-manager.c:231: warning: implicit declaration of function > 'gconf_client_get_bool' >
Bug#562441: l7-filter-userspace: FTBFS: l7-conntrack.cpp:129: error: 'nfct_sprintf_protocol' was not declared in this scope
Source: l7-filter-userspace Version: 0.11-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > g++ -DHAVE_CONFIG_H -I. -g -O2 -c -o l7-conntrack.o l7-conntrack.cpp > l7-conntrack.cpp: In function 'int sprintf_conntrack_key(char*, > nfct_conntrack*, unsigned int)': > l7-conntrack.cpp:129: error: 'nfct_sprintf_protocol' was not declared in this > scope > l7-conntrack.cpp:130: error: invalid use of incomplete type 'struct > nfct_conntrack' > l7-conntrack.h:53: error: forward declaration of 'struct nfct_conntrack' > l7-conntrack.cpp:130: error: 'nfct_sprintf_address' was not declared in this > scope > l7-conntrack.cpp:131: error: invalid use of incomplete type 'struct > nfct_conntrack' > l7-conntrack.h:53: error: forward declaration of 'struct nfct_conntrack' > l7-conntrack.cpp:131: error: 'nfct_sprintf_proto' was not declared in this > scope > l7-conntrack.cpp: In function 'int l7_handle_conntrack_event(void*, unsigned > int, int, void*)': > l7-conntrack.cpp:159: error: invalid use of incomplete type 'struct > nfct_conntrack' > l7-conntrack.h:53: error: forward declaration of 'struct nfct_conntrack' > l7-conntrack.cpp:160: error: invalid use of incomplete type 'struct > nfct_conntrack' > l7-conntrack.h:53: error: forward declaration of 'struct nfct_conntrack' > l7-conntrack.cpp:162: error: 'NFCT_MSG_DESTROY' was not declared in this scope > l7-conntrack.cpp:163: error: 'NFCT_MSG_NEW' was not declared in this scope > l7-conntrack.cpp:164: error: 'NFCT_MSG_UPDATE' was not declared in this scope > l7-conntrack.cpp:165: error: 'NFCT_MSG_UNKNOWN' was not declared in this scope > l7-conntrack.cpp:168: error: 'NFCT_MSG_NEW' was not declared in this scope > l7-conntrack.cpp:182: error: 'NFCT_MSG_DESTROY' was not declared in this scope > l7-conntrack.cpp: In destructor 'l7_conntrack::~l7_conntrack()': > l7-conntrack.cpp:196: error: 'nfct_conntrack_free' was not declared in this > scope > l7-conntrack.cpp: In member function 'void l7_conntrack::start()': > l7-conntrack.cpp:233: error: 'nfct_register_callback' was not declared in > this scope > l7-conntrack.cpp:234: error: 'nfct_event_conntrack' was not declared in this > scope > l7-conntrack.cpp:237: error: 'nfct_conntrack_free' was not declared in this > scope > make[2]: *** [l7-conntrack.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/l7-filter-userspace_0.11-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562433: ecl: FTBFS: rm: cannot remove `/build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info/dir': No such file or directory
Source: ecl Version: 9.10.2-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory > `/build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/build/doc' > /bin/bash > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/src/gc/mkinstalldirs > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info > mkdir -p -- > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info > for k in ecl.info ecldev.info clx.info; do \ > /usr/bin/install -c -m 644 $k > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info; \ > if [ -x /usr/sbin/install-info ]; then \ > /usr/sbin/install-info > --info-dir=/build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info > $k; \ > fi; \ > done > install-info: warning: don't call programs like install-info with an absolute > path, > install-info: warning: /usr/sbin/install-info provided by dpkg is deprecated > and will go away soon; > install-info: warning: its replacement lives in /usr/bin/. > install-info: warning: nothing done since /usr/bin/install-info doesn't exist, > install-info: warning: you might want to install an info-browser package. > install-info: warning: don't call programs like install-info with an absolute > path, > install-info: warning: /usr/sbin/install-info provided by dpkg is deprecated > and will go away soon; > install-info: warning: its replacement lives in /usr/bin/. > install-info: warning: nothing done since /usr/bin/install-info doesn't exist, > install-info: warning: you might want to install an info-browser package. > install-info: warning: don't call programs like install-info with an absolute > path, > install-info: warning: /usr/sbin/install-info provided by dpkg is deprecated > and will go away soon; > install-info: warning: its replacement lives in /usr/bin/. > install-info: warning: nothing done since /usr/bin/install-info doesn't exist, > install-info: warning: you might want to install an info-browser package. > /bin/bash > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/src/gc/mkinstalldirs > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/doc/ > mkdir -p -- > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/doc/ > for i in Copyright LGPL; do \ > /usr/bin/install -c -m 644 > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/src/../$i > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/doc/; \ > done > /bin/bash > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/src/gc/mkinstalldirs > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/man/man1 > /usr/bin/install -c -m 644 ecl.man > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/man/man1/ecl.1 > /usr/bin/install -c -m 644 ecl-config.man > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/man/man1/ecl-config.1 > make[3]: Leaving directory > `/build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/build/doc' > make[2]: Leaving directory > `/build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/build' > make[1]: Leaving directory `/build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2' > rm > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/doc/LGPL > rm > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/doc/Copyright > rm > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info/ecl.info > \ > > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info/clx.info > \ > > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info/ecldev.info > rm > /build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info/dir > rm: cannot remove > `/build/user-ecl_9.10.2-1-amd64-a6cqjl/ecl-9.10.2/debian/ecl/usr/share/info/dir': > No such file or directory > make: *** [install] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/ecl_9.10.2-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562439: ldap-haskell: FTBFS: make: dh_haskell: Command not found
Source: ldap-haskell Version: 0.6.5-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/bin/fakeroot debian/rules binary > dh_testdir > #make test-hugs > dh_testdir > dh_testroot > dh_clean -k > dh_clean: Compatibility levels before 5 are deprecated. > dh_installdirs -i > dh_installdirs: Compatibility levels before 5 are deprecated. > make: dh_haskell: Command not found > make: *** [installdocs] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/ldap-haskell_0.6.5-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 504873 is serious
Processing commands for cont...@bugs.debian.org: > severity 504873 serious Bug #504873 [im-sdk] FTBFS with GCC 4.4: missing #include Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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#560576: ibm-3270: FTBFS: configure: error: 'Cannot find xmkmf'
Processing commands for cont...@bugs.debian.org:
> reopen 560576
Bug #560576 {Done: Bastian Blank } [src:ibm-3270] ibm-3270:
FTBFS: configure: error: 'Cannot find xmkmf'
> reassign 560576 ftp.debian.org
Bug #560576 [src:ibm-3270] ibm-3270: FTBFS: configure: error: 'Cannot find
xmkmf'
Bug reassigned from package 'src:ibm-3270' to 'ftp.debian.org'.
Bug No longer marked as found in versions ibm-3270/3.3.4p6-3.2.
> severity 560576 normal
Bug #560576 [ftp.debian.org] ibm-3270: FTBFS: configure: error: 'Cannot find
xmkmf'
Severity set to 'normal' from 'serious'
> retitle 560576 RM: ibm-3270/main -- RoQA: superseded by package in non-free
Bug #560576 [ftp.debian.org] ibm-3270: FTBFS: configure: error: 'Cannot find
xmkmf'
Changed Bug title to 'RM: ibm-3270/main -- RoQA: superseded by package in
non-free' from 'ibm-3270: FTBFS: configure: error: 'Cannot find xmkmf''
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reopening 560511
Processing commands for cont...@bugs.debian.org:
> reopen 560511
Bug #560511 {Done: Ben Hutchings } [src:ion3] ion3:
FTBFS: dock.c:36:34: error: X11/extensions/shape.h: No such file or directory
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 539948 is serious
Processing commands for cont...@bugs.debian.org: > # I can also reproduce the failure in an amd64 chroot > severity 539948 serious Bug #539948 [haskell-testpack] FTBFS: Irrefutable pattern failed for pattern Data.Maybe.Just cpphsProg Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560511: ion3: FTBFS: dock.c:36:34: error: X11/extensions/shape.h: No such file or directory
severity 560511 normal reassign 560511 ftp.debian.org retitle 560511 RM: ion3/main [hurd-i386,source] -- RoQA; superseded by version in non-free thanks Hi FTPMasters, ion3 is now in non-free, but there's still a package (with the ancient version 20070318-2) in main, only on hurd-i386. Could you please remove it? (but of course keep the other versions in non-free). rmadison says: ion3 | 20070318-2 | unstable | source, hurd-i386 Thank you, Lucas On 13/12/09 at 00:46 +, Ben Hutchings wrote: > On Fri, 2009-12-11 at 09:29 +0100, Lucas Nussbaum wrote: > > Source: ion3 > > Version: 20070318-2 > > This version is ancient and is not part of any release. It was the last > version uploaded to main (ion3 is now in non-free) but I have no idea > why you are trying to build it or where you got it from. Hi, It's still available on hurd-i386, and shows up in Sources. Let's ask ftpmasters to remove it. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- 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#560511: ion3: FTBFS: dock.c:36:34: error: X11/extensions/shape.h: No such file or directory
Processing commands for cont...@bugs.debian.org: > severity 560511 normal Bug #560511 [src:ion3] ion3: FTBFS: dock.c:36:34: error: X11/extensions/shape.h: No such file or directory Severity set to 'normal' from 'serious' > reassign 560511 ftp.debian.org Bug #560511 [src:ion3] ion3: FTBFS: dock.c:36:34: error: X11/extensions/shape.h: No such file or directory Bug reassigned from package 'src:ion3' to 'ftp.debian.org'. Bug No longer marked as found in versions ion3/20070318-2. > retitle 560511 RM: ion3/main [hurd-i386,source] -- RoQA; superseded by > version in non-free Bug #560511 [ftp.debian.org] ion3: FTBFS: dock.c:36:34: error: X11/extensions/shape.h: No such file or directory Changed Bug title to 'RM: ion3/main [hurd-i386,source] -- RoQA; superseded by version in non-free' from 'ion3: FTBFS: dock.c:36:34: error: X11/extensions/shape.h: No such file or directory' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560710: marked as done (tgt-admin depeds on libconfig-general-perl)
Your message dated Thu, 24 Dec 2009 16:02:44 + with message-id and subject line Bug#560710: fixed in tgt 1:1.0.0-1 has caused the Debian Bug report #560710, regarding tgt-admin depeds on libconfig-general-perl 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.) -- 560710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tgt Version: 1:0.9.11-1 Severity: normal tgt-admin use Config::General to analyze its configuration files /etc/tgt/targets.conf, without libconfig-general-perl installed, tgt-admin will throw error: Can't locate Config/General.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/sbin/tgt-admin line 13. BEGIN failed--compilation aborted at /usr/sbin/tgt-admin line 13. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tgt depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries tgt recommends no packages. tgt suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tgt Source-Version: 1:1.0.0-1 We believe that the bug you reported is fixed in the latest version of tgt, which is due to be installed in the Debian FTP archive: tgt_1.0.0-1.debian.tar.gz to main/t/tgt/tgt_1.0.0-1.debian.tar.gz tgt_1.0.0-1.dsc to main/t/tgt/tgt_1.0.0-1.dsc tgt_1.0.0-1_amd64.deb to main/t/tgt/tgt_1.0.0-1_amd64.deb tgt_1.0.0.orig.tar.gz to main/t/tgt/tgt_1.0.0.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 560...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frederik Schüler (supplier of updated tgt 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: Thu, 24 Dec 2009 16:34:17 +0100 Source: tgt Binary: tgt Architecture: source amd64 Version: 1:1.0.0-1 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team Changed-By: Frederik Schüler Description: tgt- Linux SCSI target user-space tools Closes: 560710 Changes: tgt (1:1.0.0-1) unstable; urgency=low . * New upstream release. - Drop GPL digest patch, upstream has other implementation. * Add dependency on libconfig-general-perl. (Closes: #560710) * Build iSER driver, too. Checksums-Sha1: b00bc501b3737deec18f56f0381c486b083e9697 1103 tgt_1.0.0-1.dsc 14ffbd426d2bd9e20b8cd05dbfd68f68eb6e63e2 303689 tgt_1.0.0.orig.tar.gz 43d1c082b4b924b5021fead47252d3dee858983c 4615 tgt_1.0.0-1.debian.tar.gz 15fe6d6bbea77fe080198b4475e2fe1326f4555f 193328 tgt_1.0.0-1_amd64.deb Checksums-Sha256: 9c2936503556ba3474e853accb2281f95105f3d8d84acd939e53b17c3929a644 1103 tgt_1.0.0-1.dsc a3291ac57c348363c08abaa3caf98ab7117bdd2d2121e78a345611203f679da1 303689 tgt_1.0.0.orig.tar.gz 588dc1cfbe88711eee8429efc0595ed380c444b695503c5c30ea43313ccc81d9 4615 tgt_1.0.0-1.debian.tar.gz db3bbcfea7fc42357269b58e1396982df8950ffd101997f6790b5ef5d600fbcc 193328 tgt_1.0.0-1_amd64.deb Files: f3860e3484cb61ccf193a44e474d3f86 1103 net optional tgt_1.0.0-1.dsc c83f05eda1e49f20cb714ea2a44eef2e 303689 net optional tgt_1.0.0.orig.tar.gz 19708573a0e276fad0d2a46747f611e4 4615 net optional tgt_1.0.0-1.debian.tar.gz d2b2002678e48bac91d40af7f2f704f8 193328 net optional tgt_1.0.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkszjMcACgkQ6n7So0GVSSBxfACghxOMzGUk8OjGYEDc/d4TsIUN tMMAn1lNFjRmQ0Ov0fAEenL/HuOtWtg1 =QZHe -END PGP SIGNATURE- --- End Message ---
Bug#562358: mlpost: FTBFS: mkdir -p img/ fails?
Lucas Nussbaum a écrit : > During a rebuild of all packages in sid, your package failed to build on > amd64. > [...] >> mkdir -p img/ && cd img/ && ../customdoc/img_doc.byte >> /dev/null && cd .. >> + mkdir -p img/ && cd img/ && ../customdoc/img_doc.byte >> /dev/null && cd .. >> Command exited with code 1. >> make[1]: *** [doc] Error 10 The package builds fine in a clean squeeze chroot, but doesn't in sid. I am investigating. -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 560710
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 560710 + pending Bug #560710 [tgt] tgt-admin depeds on libconfig-general-perl Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562314: marked as done (ccfits: FTBFS: make[1]: *** [refman.pdf] Error 1)
Your message dated Thu, 24 Dec 2009 15:32:57 + with message-id and subject line Bug#562314: fixed in ccfits 2.2-2 has caused the Debian Bug report #562314, regarding ccfits: FTBFS: make[1]: *** [refman.pdf] Error 1 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.) -- 562314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ccfits Version: 2.2-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091213 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-ccfits_2.2-1-amd64-6SLJTS/ccfits-2.2/latex' > rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out refman.pdf > pdflatex refman.tex > This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) > restricted \write18 enabled. > entering extended mode > (./refman.tex > LaTeX2e <2009/09/24> > Babel and hyphenation patterns for english, usenglishmax, dumylang, > noh > yphenation, loaded. > > make[1]: *** [refman.pdf] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/13/ccfits_2.2-1_lsid64.buildlog 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. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: ccfits Source-Version: 2.2-2 We believe that the bug you reported is fixed in the latest version of ccfits, which is due to be installed in the Debian FTP archive: ccfits_2.2-2.diff.gz to main/c/ccfits/ccfits_2.2-2.diff.gz ccfits_2.2-2.dsc to main/c/ccfits/ccfits_2.2-2.dsc libccfits-dev_2.2-2_amd64.deb to main/c/ccfits/libccfits-dev_2.2-2_amd64.deb libccfits-doc_2.2-2_all.deb to main/c/ccfits/libccfits-doc_2.2-2_all.deb libccfits0_2.2-2_amd64.deb to main/c/ccfits/libccfits0_2.2-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 562...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno (supplier of updated ccfits 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: Thu, 24 Dec 2009 15:25:49 +0100 Source: ccfits Binary: libccfits0 libccfits-dev libccfits-doc Architecture: source amd64 all Version: 2.2-2 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno Changed-By: Aurelien Jarno Description: libccfits-dev - static library for I/O with FITS format data files libccfits-doc - documentation for CCfits libccfits0 - shared library for I/O with FITS format data files Closes: 562314 Changes: ccfits (2.2-2) unstable; urgency=low . * Build-depends on texlive-font-utils to get epstopdf (closes: bug#562314). Checksums-Sha1: e99979e5a8e25617a1e6e8ecc1cab83267a1d0cc 1148 ccfits_2.2-2.dsc 58ba3b77ced171bb1c355450d92b51b527572235 5443 ccfits_2.2-2.diff.gz 9a665681a59d9a4d9ef27b05841df3235802d6b5 275978 libccfits0_2.2-2_amd64.deb d28638385a5b3f2f6f02bf19f7e309b9f076f418 434998 libccfits-dev_2.2-2_amd64.deb 8fb4576d3de855c1eb95477535e03634b9cd6533 927506 libccfits-doc_2.2-2_all.deb Checksums-Sha256: 61fb056b9d4e2f0a348774c7059d2edd6363f0543674ddbd4168d6c91e4be45d 1148 ccfits_2.2-2.dsc 5d2fac4046d727a6a3b6067e160a92aa2a23c25fa7ce1a5e93575f7fe4993d5c 5443 ccfits_2.2-2.diff.gz 04a1e6b7ee602569a11b9f859ae361f68102d5e4ecc00860b455c2967bb6e9b6 275978 libccfits0_2.2-2_amd64.deb 662eb50687113180cbe7e2c2da854ab7cf1a6bd945266ec0a00b802d0b130ce7 434998 libccfits-dev_2.2-2_amd64.deb 794eff91b9db32e19daf6b01b421fe3708e2c861fc2238c47dd6b7d098628c12 927506 libccfits-doc_2.2-2_all.deb Files: bb8dc606e1e18f99ae85c2f577419aa2 1148 libs optional ccfits_2.2-2.dsc 1c2b8716a5c3b45a218dfdd6b14f3ae6 5443 libs optional ccfits_2.2-2.diff.gz 315efd8a9da33db34f81cfb207f91a53 275978 libs optional libccfits0_
Processed: tagging 562339
Processing commands for cont...@bugs.debian.org: > tags 562339 + confirmed Bug #562339 [src:ripperx] ripperx: FTBFS: configure: error: libid3 not found Added tag(s) confirmed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560940: CVE-2009-3560 and CVE-2009-3720 denial-of-services
> > Patched package available at: > > http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=tla The fixed version is up. $ interdiff tla1.diff tla2.diff | diffstat patches/06-disable_builtin_expat.dpatch | 50 +++- rules |5 +-- 2 files changed, 34 insertions(+), 21 deletions(-) diff -u tla-1.3.5+dfsg/debian/rules tla-1.3.5+dfsg/debian/rules --- tla-1.3.5+dfsg/debian/rules +++ tla-1.3.5+dfsg/debian/rules @@ -56,8 +56,9 @@ # Disable builtin expat # See also patches/06-disable_builtin_expat.dpatch - rm -f src/expat/PLUGIN/AUTOCONF - rm -f src/expat/PLUGIN/REQ + #rm -f src/expat/PLUGIN/AUTOCONF + #rm -f src/expat/PLUGIN/REQ + rm -rf src/expat/ # Let's play safe rm -f src/libneon/PLUGIN/REQ # Cleaning package diff -u tla-1.3.5+dfsg/debian/patches/06-disable_builtin_expat.dpatch tla-1.3.5+dfsg/debian/patches/06-disable_builtin_expat.dpatch --- tla-1.3.5+dfsg/debian/patches/06-disable_builtin_expat.dpatch +++ tla-1.3.5+dfsg/debian/patches/06-disable_builtin_expat.dpatch @@ -2,22 +2,12 @@ ## 06-disable_builtin_expat.dpatch by Sylvain Beucler ## ## All lines beginning with `## DP:' are a description of the patch. -## DP: use system expat to address CVE-2009-3560 and CVE-2009-3720 DoS -## DP: see also debian/rules, target 'clean' +## DP: No description. tla-1.3.5+dfsg.orig/src/tla/tla/Makefile.in -+++ tla-1.3.5+dfsg/src/tla/tla/Makefile.in -@@ -21,7 +21,7 @@ - endif - - $(programs):%$(cfg__exec_suffix):%.o $(thelib) $(filter-out -L%, $(filter-out -l%, $(libs))) -- $(SHELL) $(objroot)/libneon/libtool --mode=link $(CC) $(CFLAGS) -L../../expat -o $@ $< $(thelib) $(libs) -+ $(SHELL) $(objroot)/libneon/libtool --mode=link $(CC) $(CFLAGS) -o $@ $< $(thelib) $(libs) - - clean: clean-prog - tla-1.3.5+dfsg.orig/src/libneon/Makefile.in -+++ tla-1.3.5+dfsg/src/libneon/Makefile.in +...@dpatch@ +diff -urNad tla-1.3.5+dfsg~/src/libneon/Makefile.in tla-1.3.5+dfsg/src/libneon/Makefile.in +--- tla-1.3.5+dfsg~/src/libneon/Makefile.in2009-12-24 12:30:27.0 +0100 tla-1.3.5+dfsg/src/libneon/Makefile.in 2009-12-24 12:30:41.0 +0100 @@ -33,7 +33,7 @@ @SET_MAKE@ @@ -30,11 +20,33 @@ tla-1.3.5+dfsg.orig/src/libneon/src/Makefile.in -+++ tla-1.3.5+dfsg/src/libneon/src/Makefile.in -@@ -26,7 +26,7 @@ +diff -urNad tla-1.3.5+dfsg~/src/libneon/src/Makefile.in tla-1.3.5+dfsg/src/libneon/src/Makefile.in +--- tla-1.3.5+dfsg~/src/libneon/src/Makefile.in2009-12-24 12:30:27.0 +0100 tla-1.3.5+dfsg/src/libneon/src/Makefile.in 2009-12-24 12:31:28.0 +0100 +@@ -25,14 +25,14 @@ + # Flags CPPFLAGS = @DEFS@ @CPPFLAGS@ - CFLAGS = @CFLAGS@ -I$(top_builddir) -I$(top_srcdir)/../expat/lib @NEON_CFLAGS@ +-CFLAGS = @CFLAGS@ -I$(top_builddir) -I$(top_srcdir)/../expat/lib @NEON_CFLAGS@ -LDFLAGS = -L$(top_builddir)/../expat @LDFLAGS@ ++CFLAGS = @CFLAGS@ -I$(top_builddir) @NEON_CFLAGS@ +LDFLAGS = @LDFLAGS@ NEON_LINK_FLAGS = @NEON_LINK_FLAGS@ # Note: don't substitute @LIBS@ in here; during a bundled # build of this directory, @LIBS@ may include -lneon. + LIBS = @NEON_LIBS@ @NEON_LTLIBS@ + +-COMPILE = $(CC) $(CPPFLAGS) $(CFLAGS) -I$(top_builddir) -I$(top_srcdir)/../expat/lib @NEON_CFLAGS@ ++COMPILE = $(CC) $(CPPFLAGS) $(CFLAGS) -I$(top_builddir) @NEON_CFLAGS@ + LINK = $(LIBTOOL) --quiet --mode=link $(CC) $(LDFLAGS) + + NEON_BASEOBJS = ne_reque...@neon_objext@ ne_sessi...@neon_objext@ \ +diff -urNad tla-1.3.5+dfsg~/src/tla/tla/Makefile.in tla-1.3.5+dfsg/src/tla/tla/Makefile.in +--- tla-1.3.5+dfsg~/src/tla/tla/Makefile.in2009-12-24 12:30:27.0 +0100 tla-1.3.5+dfsg/src/tla/tla/Makefile.in 2009-12-24 12:30:41.0 +0100 +@@ -21,7 +21,7 @@ + endif + + $(programs):%$(cfg__exec_suffix):%.o $(thelib) $(filter-out -L%, $(filter-out -l%, $(libs))) +- $(SHELL) $(objroot)/libneon/libtool --mode=link $(CC) $(CFLAGS) -L../../expat -o $@ $< $(thelib) $(libs) ++ $(SHELL) $(objroot)/libneon/libtool --mode=link $(CC) $(CFLAGS) -o $@ $< $(thelib) $(libs) + + clean: clean-prog + signature.asc Description: Digital signature
Processed: tagging 562384
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 562384 + confirmed Bug #562384 [src:libcoat-persistent-perl] libcoat-persistent-perl: FTBFS: tests failed Added tag(s) confirmed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 562347
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 562347 + confirmed Bug #562347 [src:libnet-google-code-perl] libnet-google-code-perl: FTBFS: test failed Added tag(s) confirmed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Re: Bug#562292: ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef
Processing commands for cont...@bugs.debian.org: > tags 562292 +moreinfo +unreproducible Bug #562292 [src:ltp] ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef Added tag(s) moreinfo. Bug #562292 [src:ltp] ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef Added tag(s) unreproducible. > On Thu, 24 Dec 2009 11:25:35 +0100, Lucas Nussbaum Unknown command or malformed arguments to command. > wrote: Unknown command or malformed arguments to command. > > Source: ltp Unknown command or malformed arguments to command. > > Version: 20091031+dfsg-2 Unknown command or malformed arguments to command. > > Severity: serious Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562292: ltp: FTBFS: linux_syscall_numbers.h:32:1: error: unterminated #ifdef
tags 562292 +moreinfo +unreproducible On Thu, 24 Dec 2009 11:25:35 +0100, Lucas Nussbaum wrote: Source: ltp Version: 20091031+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091213 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: cc -g -O2 -g -Wall -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I/build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include -I../../../../include -I../../../../include -c -o netsync.o netsync.c In file included from libcpuset.c:51: /build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:32:1: error: unterminated #ifdef /build/user-ltp_20091031+dfsg-2-amd64-Wo1MGi/ltp-20091031+dfsg/testcases/kernel/include/linux_syscall_numbers.h:13:1: error: unterminated #ifndef OK! make[6]: *** [libcpuset.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/13/ltp_20091031+dfsg-2_lsid64.buildlog 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. Could you please upload the file in question or the whole build tree after a failed build somewhere? I can't figure out what's the problem, and the official buildds seem to handle it: https://buildd.debian.org/fetch.cgi?pkg=ltp&arch=amd64&ver=20091031%2Bdfsg-2&stamp=1261520305&file=log&as=raw Regards Jiri Palecek -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562425: lingot - Cancel in options dialog leads to endless loop
Package: lingot Version: 0.7.4-2 Severity: grave Using the cancel button in the options menu leads to an endless loop and breaks the application. Bastian -- Change is the essential process of all existence. -- Spock, "Let That Be Your Last Battlefield", stardate 5730.2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560910: marked as done (iptables ignores mask on source ip address: 1.2.3.4/16 treated as 1.2.3.4/0)
Your message dated Thu, 24 Dec 2009 09:21:49 -0500 with message-id and subject line iptables ignores mask on source ip address has caused the Debian Bug report #560910, regarding iptables ignores mask on source ip address: 1.2.3.4/16 treated as 1.2.3.4/0 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.) -- 560910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iptables Version: 1.4.4-2 Severity: critical Justification: breaks unrelated software iptables verson 1.4.5-1 for amd64 ignores the address mask on source address arguments. "-s 192.168.1.0/24" is treated as "-s 192.168.1.0/0" both as reported by "iptables -L -n -v" and as seen in firewall logs. Version 1.4.4-2 function correctly. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.2-a (PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iptables depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries iptables recommends no packages. iptables suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.4.5-1 Fixed upstream. --- End Message ---
Bug#562423: lingot - Fails silent if only ALSA is availabe
Package: lingot Version: 0.7.4-2 Severity: grave lingot only supports OSS and fails silent (at least for a X application) if /dev/dsp is unavailable. OSS support is not longer included in the current kernels, so it is defacto (without the help of other tools) unusable. Bastian -- Not one hundred percent efficient, of course ... but nothing ever is. -- Kirk, "Metamorphosis", stardate 3219.8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562325: maint-guide: FTBFS: debiandoc2latexps: ERROR: maint-guide.fr.dvi could not be generated properly
On Thu, Dec 24, 2009 at 02:08:16PM +0100, W. Martin Borgert wrote: > Quoting "Osamu Aoki" : >> If no one comes up to help, I will simply drop these problematic build >> and just do html and plain text. While doing it, I will change source >> to UTF-8 for more practical gain. > > How about moving the guide from debiandoc-sgml to e.g. DocBook XML? That should be next step which should be done with PO migration and really needed. I also wish to update its content by someone who know well when this is done. New dh syntax, wide use of cdbs, deprecating dpatch, ... many context revision is needed. Any volunteer? (I spent enough time for updating Debian Reference ...) Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562395: latex-cjk-chinese-arphic: FTBFS: No Sub Font Definition file
Hi Lucas 2009/12/24 Lucas Nussbaum : > Source: latex-cjk-chinese-arphic > Version: 1.20 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091213 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. Thanks for the bug report. I suspect that it is because of the new TeXLive2009 packages; I haven't yet tried them against these latest packages. Best regards -- Danai -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562347: Coat::Persistent and Net::Google::Code FTBFS
Lucas, Thanks for these reports. Unfortunately, both of these have new versions (which may or may not fix these FTBFS), except they are themselves failing to build (which is why I haven't uploaded them yet). Now that this affects packages currently in the repository, we'll prioritize them and look closer and trying to get them to build. Cheers, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
