Processed: reassign 676061 to dpkg, forcibly merging 675613 676061

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 676061 dpkg
Bug #676061 [src:doc-base] doc-base: FTBFS: nsgmls:_build/doc-base.sgml:5:0:E: 
reference to entity "DEBIANDOC" for which no system identifier could be 
generated
Bug reassigned from package 'src:doc-base' to 'dpkg'.
No longer marked as found in versions doc-base/0.10.3.
Ignoring request to alter fixed versions of bug #676061 to the same values 
previously set
> forcemerge 675613 676061
Bug #675613 [dpkg] debiandoc-sgml: Does not register itself in /etc/sgml/catalog
Bug #676107 [dpkg] debian-faq: FTBFS: nsgmls:0:6:0:E: reference to entity 
"DEBIANDOC" for which no system identifier could be generated
Bug #676122 [dpkg] debian-history: FTBFS: nsgmls:0:1:26:E: reference to 
entity "DEBIANDOC" for which no system identifier could be generated
Bug #676061 [dpkg] doc-base: FTBFS: nsgmls:_build/doc-base.sgml:5:0:E: 
reference to entity "DEBIANDOC" for which no system identifier could be 
generated
Added indication that 676061 affects 
docbook-simple,python-docutils,xml-core,debiandoc-sgml,sgml2x,docbook-mathml,sgml-data,docbook,docbook-xml,libcommons-validator-java,docbook-website,docbook-dsssl,docbook-html-forms,docbook-slides,dtd-ead,docbook-ebnf,w3c-dtd-xhtml
Bug #676107 [dpkg] debian-faq: FTBFS: nsgmls:0:6:0:E: reference to entity 
"DEBIANDOC" for which no system identifier could be generated
Bug #676122 [dpkg] debian-history: FTBFS: nsgmls:0:1:26:E: reference to 
entity "DEBIANDOC" for which no system identifier could be generated
Merged 675613 676061 676107 676122
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675613
676061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676061
676107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676107
676122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#675991: marked as done (openbox 3.5 crashes xorg server with gtk3 apps)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 06:02:51 +
with message-id 
and subject line Bug#675991: fixed in openbox 3.5.0-4
has caused the Debian Bug report #675991,
regarding openbox 3.5 crashes xorg server with gtk3 apps
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.)


-- 
675991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openbox
Version: 3.5.0-3
Severity: grave
Tags: patch
Justification: causes non-serious data loss

Hi,

I'm suffering from constant but hard to reproduce crashes with version 3.5 of 
openbox. This is a known upstream bug which is triggered by gtk3 apps.

More details of upstream bug and patch:
https://bugzilla.icculus.org/show_bug.cgi?id=5460

Other bug reports for Ubuntu and Fedora on the same bug:
https://bugzilla.redhat.com/show_bug.cgi?id=827800
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/997212 

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (750, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39.14-botto-toi-kdb-pax (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openbox depends on:
ii  dpkg  1.16.3
ii  libc6 2.13-32
ii  libglib2.0-0  2.32.3-1
ii  libice6   2:1.0.8-2
ii  libobrender27 3.5.0-3
ii  libobt0   3.5.0-3
ii  libsm62:1.2.1-2
ii  libstartup-notification0  0.12-1
ii  libx11-6  2:1.4.99.901-2
ii  libxau6   1:1.0.7-1
ii  libxext6  2:1.3.1-2
ii  libxinerama1  2:1.1.2-1
ii  libxml2   2.7.8.dfsg-9.1
ii  libxrandr22:1.3.2-2
ii  libxrender1   1:0.9.7-1

Versions of packages openbox recommends:
ii  obconf  1:2.0.3+20110805+debian-1
ii  openbox-themes  1.0.2

Versions of packages openbox suggests:
ii  libxml2-dev  2.7.8.dfsg-9.1
ii  menu 2.1.46
ii  python   2.7.2-10
ii  ttf-dejavu   2.33-2

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: openbox
Source-Version: 3.5.0-4

We believe that the bug you reported is fixed in the latest version of
openbox, which is due to be installed in the Debian FTP archive:

gnome-panel-control_3.5.0-4_amd64.deb
  to main/o/openbox/gnome-panel-control_3.5.0-4_amd64.deb
libobrender27_3.5.0-4_amd64.deb
  to main/o/openbox/libobrender27_3.5.0-4_amd64.deb
libobt0_3.5.0-4_amd64.deb
  to main/o/openbox/libobt0_3.5.0-4_amd64.deb
openbox-dev_3.5.0-4_amd64.deb
  to main/o/openbox/openbox-dev_3.5.0-4_amd64.deb
openbox_3.5.0-4.debian.tar.gz
  to main/o/openbox/openbox_3.5.0-4.debian.tar.gz
openbox_3.5.0-4.dsc
  to main/o/openbox/openbox_3.5.0-4.dsc
openbox_3.5.0-4_amd64.deb
  to main/o/openbox/openbox_3.5.0-4_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 675...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nico Golde  (supplier of updated openbox package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 05 Jun 2012 07:18:19 +0200
Source: openbox
Binary: openbox gnome-panel-control libobt0 libobrender27 openbox-dev
Architecture: source amd64
Version: 3.5.0-4
Distribution: unstable
Urgency: low
Maintainer: Nico Golde 
Changed-By: Nico Golde 
Description: 
 gnome-panel-control - command line utility to invoke GNOME panel run 
dialog/menu
 libobrender27 - rendering library for openbox themes
 libobt0- parsing library for openbox
 openbox- standards compliant, fast, light-weight, extensible window manage
 openbox-dev - development files for the openbox window manager
Closes: 76 675991
Changes: 
 openbox (3.5.0-4) unstable; urgency=low
 .
   * Fix crash on unexpected NET_WM_MOVERESIZE_CANCEL messages
 (675991_fix_crash_from_gtk3_apps.patch; Closes: #675991).
   * Make undecorated windows place according to their undecorated
 state (76_wrong_undecorated_window_placement.patch; Closes: #76)
Checksums-Sha1: 
 9494c6cdabd4cc60f7ea3e5de320c5116

Bug#676067: marked as done (uruk: FTBFS: configure: error: cannot find zoem ( http://micans.org/zoem ) in your PATH)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 06:03:31 +
with message-id 
and subject line Bug#676067: fixed in uruk 20120605-1
has caused the Debian Bug report #676067,
regarding uruk: FTBFS: configure: error: cannot find zoem ( 
http://micans.org/zoem ) in your PATH
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.)


-- 
676067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uruk
Version: 20120530-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> test -f debian/rules
> ./configure --prefix=/usr --mandir=\${prefix}/share/man \
>   --sysconfdir=/etc --localstatedir=/var
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for zoem... no
> configure: error: cannot find zoem ( http://micans.org/zoem ) in your PATH 
> make: *** [build-indep] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/uruk_20120530-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
Source: uruk
Source-Version: 20120605-1

We believe that the bug you reported is fixed in the latest version of
uruk, which is due to be installed in the Debian FTP archive:

uruk_20120605-1.debian.tar.gz
  to main/u/uruk/uruk_20120605-1.debian.tar.gz
uruk_20120605-1.dsc
  to main/u/uruk/uruk_20120605-1.dsc
uruk_20120605-1_all.deb
  to main/u/uruk/uruk_20120605-1_all.deb
uruk_20120605.orig.tar.gz
  to main/u/uruk/uruk_20120605.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 676...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joost van Baal-Ilić  (supplier of updated uruk 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: Tue, 05 Jun 2012 07:50:23 +0200
Source: uruk
Binary: uruk
Architecture: source all
Version: 20120605-1
Distribution: unstable
Urgency: low
Maintainer: Joost van Baal-Ilić 
Changed-By: Joost van Baal-Ilić 
Description: 
 uruk   - Very small firewall script, for configuring iptables
Closes: 676067
Changes: 
 uruk (20120605-1) unstable; urgency=low
 .
   * New upstream release:
 - no longer die if programs zoem, col and/or groff are not found.  (Thanks
   Lucas Nussbaum for reporting the issue.)  Closes: #676067
Checksums-Sha1: 
 79b4056bd8c4aa27bd45bd15c1a802c24dcbd93c 1303 uruk_20120605-1.dsc
 2e56ebff49a63631690268bdba1972baaa4617d6 166950 uruk_20120605.orig.tar.gz
 5439494e3534c6790005ae54378b8e954c47bde1 9020 uruk_20120605-1.debian.tar.gz
 41b52409d6e1dc87243a60d13df47fe9fc747582 75462 uruk_20120605-1_all.deb
Checksums-Sha256: 
 5c8b7e00eb8adb0288fc57c0b73624203a4caaea114ebd724a3a393152b640ba 1303 
uruk_20120605-1.dsc
 cb1394ac4d35e8d4ea4beb5d5ed4cad62329e89344eaac729258280561c8c051 166950 
uruk_20120605.orig.tar.gz
 a961361c57f75601a52f081b0a604e947881ff3ed3bbc46b2f5031f8b6fc9610 9020 
uruk_20120605-1.debian.tar.gz
 ed1050a9192aaa7600d8f9e457b528665a66fbcf6d26a4b832c3ccf8f75c5b52 75462 
uruk_20120605-1_all.deb
Files: 
 9ae4222a79818af61ce8ac62267a0b7d 1303 net optional uruk_20120605-1.dsc
 5dd91b19f88f4310566c275593189e25 166950 net optional uruk_20120605.orig.tar.gz
 049218a579d47b291ec87f7064f5cffa 9020 net optional 
uruk_20120605-1.debian.tar.gz
 d8c1dd1407d431d7e9533c667de84418 75462 net optional uruk_20120605-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBCAAGBQJPzZ7L

Bug#675222: marked as done (Maintainer or uploader address bounces)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 06:03:48 +
with message-id 
and subject line Bug#675222: fixed in viewpdf.app 1:0.2dfsg1-4
has caused the Debian Bug report #675222,
regarding Maintainer or uploader address bounces
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.)


-- 
675222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: viewpdf.app
Version: 1:0.2dfsg1-3.1
Severity: serious

Hi!

It seems that an E-Mail address listed in the maintainer or uploaders field 
bounces.


Best regards,
  Alexander

- Forwarded message from Mail Delivery System 
 -

From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
To: envel...@ftp-master.debian.org
Date: Wed, 30 May 2012 15:01:31 +
Message-Id: 

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  gur...@linuks.mine.nu
Unrouteable address

-- This is a copy of the message, including all the headers. --

Return-path: 
Received: from dak by franck.debian.org with local (Exim 4.72)
(envelope-from )
id 1SZkMy-mb-0f; Wed, 30 May 2012 14:59:28 +
Date: Wed, 30 May 2012 14:59:28 +
Message-Id: 
From: Debian FTP Masters 
To: gregor herrmann , =?utf-8?b?R8O8cmthbiBTZW5nw7xu?= 

X-DAK: dak process-upload
X-Debian: DAK
X-Debian-Package: textedit.app
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Subject: textedit.app_4.0+20061029-3.2_amd64.changes ACCEPTED into unstable
Sender: Archive Administrator 




Accepted:
textedit.app_4.0+20061029-3.2.diff.gz
  to main/t/textedit.app/textedit.app_4.0+20061029-3.2.diff.gz
textedit.app_4.0+20061029-3.2.dsc
  to main/t/textedit.app/textedit.app_4.0+20061029-3.2.dsc
textedit.app_4.0+20061029-3.2_amd64.deb
  to main/t/textedit.app/textedit.app_4.0+20061029-3.2_amd64.deb


Changes:
textedit.app (4.0+20061029-3.2) unstable; urgency=low
 .
  * Non-maintainer upload.
  * Fix "FTBFS with GCC-4.7": apply patch from Yavor Doganov.
(Closes: #667886)


Override entries for your package:
textedit.app_4.0+20061029-3.2.dsc - source gnustep
textedit.app_4.0+20061029-3.2_amd64.deb - optional gnustep

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 667886 


Thank you for your contribution to Debian.


- End forwarded message -


--- End Message ---
--- Begin Message ---
Source: viewpdf.app
Source-Version: 1:0.2dfsg1-4

We believe that the bug you reported is fixed in the latest version of
viewpdf.app, which is due to be installed in the Debian FTP archive:

viewpdf.app_0.2dfsg1-4.debian.tar.gz
  to main/v/viewpdf.app/viewpdf.app_0.2dfsg1-4.debian.tar.gz
viewpdf.app_0.2dfsg1-4.dsc
  to main/v/viewpdf.app/viewpdf.app_0.2dfsg1-4.dsc
viewpdf.app_0.2dfsg1-4_amd64.deb
  to main/v/viewpdf.app/viewpdf.app_0.2dfsg1-4_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 675...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated viewpdf.app 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, 31 May 2012 23:31:20 +0300
Source: viewpdf.app
Binary: viewpdf.app
Architecture: source amd64
Version: 1:0.2dfsg1-4
Distribution: unstable
Urgency: low
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Description: 
 viewpdf.app - Portable Document Format (PDF) viewer for GNUstep
Closes: 453437 615353 619258 675222
Changes: 
 viewpdf.app (1:0.2dfsg1-4) unstable; urgency=low
 .
   * debian/control (Maintainer, Uploaders): Adopt package, make the
 GNUstep team maintainer (Closes: #453437).  Move Gürkan to Uploaders
 and change his email address (Closes: #675222).  Add myself.
 (Build-Depends): Require debhelper >= 8, add dpkg-dev (>= 1.16.1~) for
 hardening support.  Remove version requirements for libgnustep-gui-dev
 and libpopplerkit-dev.  Drop gnustep-make.
 (Section): Change to `gnustep'.
 (Depends): Add ${misc:Depends}.
 (Vcs-Git, Vcs-Browser): New field

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 666583 3.1.0+dfsg-1
Bug #666583 [src:sdcc] sdcc: FTBFS: ../../../src/support/Systemcall.cpp(270): 
Systemcall: 'latex "sdccman.tex"' finished with exit code 1
Marked as fixed in versions sdcc/3.1.0+dfsg-1.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
666583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Revert closing wrong bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 675276
Bug #675276 {Done: Andreas Tille } [wnpp] ITP: quazip -- 
Qt/C++ wrapper for ZIP/UNZIP package
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions freemedforms-project/0.7.4-1.
> close 675435
Bug #675435 [src:freemedforms-project] CC-BY-SA-2.0 license not suitable for 
main
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675276
675435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#667867: marked as done (cynthiune.app: FTBFS with GCC-4.7)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 05:47:51 +
with message-id 
and subject line Bug#667867: fixed in cynthiune.app 0.9.5-14
has caused the Debian Bug report #667867,
regarding cynthiune.app: FTBFS with GCC-4.7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
667867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cynthiune.app
Version: 0.9.5-13.1
Severity: important
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.7

The package fails to build in a test rebuild on at least i386 with
gcc-4.7/gobjc-4.7, but succeeds to build with gcc-4.6/gobjc-4.6. The
severity of this report may be raised before the wheezy release.

gcc-4.7 -shared  -rdynamic  
-L../../Frameworks/Cynthiune/Cynthiune.framework/Versions/Current -lCynthiune   
  -Wl,-z,defs -Wl,--as-needed -Wl,-rpath,/usr/lib/cynthiune.app -shared-libgcc 
-fexceptions -o ./MP3.format/./MP3 ./obj/MP3.obj/xing.c.o ./obj/MP3.obj/MP3.m.o 
 -L/usr/local/lib -L/usr/lib   -lmad   -lid3tag -lz  -lgnustep-gui
-lgnustep-base   -lpthread -lobjc   -lm
/usr/bin/ld: cannot find -lCynthiune
collect2: error: ld returned 1 exit status


--- End Message ---
--- Begin Message ---
Source: cynthiune.app
Source-Version: 0.9.5-14

We believe that the bug you reported is fixed in the latest version of
cynthiune.app, which is due to be installed in the Debian FTP archive:

cynthiune.app_0.9.5-14.debian.tar.gz
  to main/c/cynthiune.app/cynthiune.app_0.9.5-14.debian.tar.gz
cynthiune.app_0.9.5-14.dsc
  to main/c/cynthiune.app/cynthiune.app_0.9.5-14.dsc
cynthiune.app_0.9.5-14_amd64.deb
  to main/c/cynthiune.app/cynthiune.app_0.9.5-14_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 667...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated cynthiune.app 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, 04 Jun 2012 14:08:37 +0300
Source: cynthiune.app
Binary: cynthiune.app
Architecture: source amd64
Version: 0.9.5-14
Distribution: unstable
Urgency: low
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Description: 
 cynthiune.app - Music player for GNUstep
Closes: 633543 656604 667867
Changes: 
 cynthiune.app (0.9.5-14) unstable; urgency=low
 .
   * debian/patches/gcc-4.7.patch: New; fixes FTBFS with GCC-4.7 (Closes:
 #667867).
   * debian/patches/libmusicbrainz5.patch: New; port to libmusicbrainz5
 (Closes: #656604).
   * debian/patches/link-libs.patch: Fix FTBFS with ld --as-needed, thanks
 Colin Watson (Closes: #633543).
   * debian/patches/series: Update.
   * debian/source/format: Switch to 3.0 (quilt).
   * debian/README.source: Delete; redundant.
   * debian/control (Build-Depends): Remove quilt.  Replace
 libmusicbrainz4-dev with libmusicbrainz5-dev.  Add dpkg-dev (>=
 1.16.1~), for hardening support.
 (Vcs-Arch, Vcs-Git, Vcs-Browser): Switch from Arch to Git.
 (Standards-Version): Bump to 3.9.3; no changes needed.
   * debian/rules: Don't include /usr/share/quilt/quilt.make, eliminate
 patch/unpatch dependencies.  Enable hardening.
 (binary-arch): Remove GS_USE_FHS conditional.  Invoke dh_lintian.
   * debian/preinst: Delete; no longer needed.
   * debian/lintian-overrides: New file, override some hardening false
 positives.
Checksums-Sha1: 
 1afd2c93264f5b25c222727440ea81db50e5b332 1664 cynthiune.app_0.9.5-14.dsc
 edf48c23e0526249b941357a59d7482f8c4df761 21313 
cynthiune.app_0.9.5-14.debian.tar.gz
 4d2d68f5a1c5d65954270dd7a5dffe1cdf25506f 459770 
cynthiune.app_0.9.5-14_amd64.deb
Checksums-Sha256: 
 7ea10316c228c4af69f5cff01b00b1c28a7275fdcb1908d7a060342a81220e1a 1664 
cynthiune.app_0.9.5-14.dsc
 bb6f9961cdbf5c34585f08ef8105a53aa5fef55f6fd1cb3b4f21db5b9f263608 21313 
cynthiune.app_0.9.5-14.debian.tar.gz
 7a59da2d1f7f51f46f4b367729586f5c54ab2ef84681de8f81295ff4beff07d7 459770 
cynthiune.app_0.9.5-14_amd64.deb
Files: 
 c7073fcf40f3484ef78376e2ded482d5 1664 gnustep optional 
cynthiune.app_0.9.5-14.dsc
 a2752c3b147b8d27cdaf3a3daa0200c1 21313 gnustep optional 
cynthiune.app_0.9.5-14.debian.tar.gz
 f18dd1e7f69f9865f7499aa6a04a9e3c 45977

Bug#597933: marked as done (Non-free files distributed in sdcc)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 05:48:59 +
with message-id 
and subject line Bug#597933: fixed in sdcc 3.1.0+dfsg-1
has caused the Debian Bug report #597933,
regarding Non-free files distributed in sdcc
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.)


-- 
597933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sdcc
Version: 2.9.0-5
Severity: serious

Since the 2.9.0 release sdcc is in the process of changing the lbrary
license to GPL+LE. The process is mostly complete. While doing so, some
files of unclear license status were found. Rights holders have been
contacted and, with one exception (), agreed to license their files
under GPL+LE.
This exception is Microchip Technology Inc. They insist on a "the file
can be used only with authentic Microchip devices" condition, which
clearly violates DFSG §6.

The problem affects the pic and pic16 ports only.

All problematic header files live in the include/pic and include/pic16
directories. In the Debian package these are installed into the
/usr/share/sdcc/include/pic and /usr/share/sdcc/include/pic16 directories.
The problematic source files live in the device/pic and device/pic16.

For the upcoming 3.0.0 release we intend to clearly separate the
problematic files from the rest of sdcc.

Philipp


--- End Message ---
--- Begin Message ---
Source: sdcc
Source-Version: 3.1.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
sdcc, which is due to be installed in the Debian FTP archive:

sdcc-doc_3.1.0+dfsg-1_all.deb
  to main/s/sdcc/sdcc-doc_3.1.0+dfsg-1_all.deb
sdcc-libraries_3.1.0+dfsg-1_all.deb
  to main/s/sdcc/sdcc-libraries_3.1.0+dfsg-1_all.deb
sdcc-ucsim_3.1.0+dfsg-1_sparc.deb
  to main/s/sdcc/sdcc-ucsim_3.1.0+dfsg-1_sparc.deb
sdcc_3.1.0+dfsg-1.debian.tar.gz
  to main/s/sdcc/sdcc_3.1.0+dfsg-1.debian.tar.gz
sdcc_3.1.0+dfsg-1.dsc
  to main/s/sdcc/sdcc_3.1.0+dfsg-1.dsc
sdcc_3.1.0+dfsg-1_sparc.deb
  to main/s/sdcc/sdcc_3.1.0+dfsg-1_sparc.deb
sdcc_3.1.0+dfsg.orig.tar.gz
  to main/s/sdcc/sdcc_3.1.0+dfsg.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 597...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gudjon I. Gudjonsson  (supplier of updated sdcc 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: SHA512

Format: 1.8
Date: Mon, 04 Jun 2012 09:29:53 +
Source: sdcc
Binary: sdcc sdcc-libraries sdcc-ucsim sdcc-doc
Architecture: source sparc all
Version: 3.1.0+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Gudjon I. Gudjonsson 
Changed-By: Gudjon I. Gudjonsson 
Description: 
 sdcc   - Small Device C Compiler
 sdcc-doc   - Small Device C Compiler (documentation)
 sdcc-libraries - Small Device C Compiler (libraries)
 sdcc-ucsim - Micro-controller simulator for SDCC
Closes: 459877 597933 647036 658188
Changes: 
 sdcc (3.1.0+dfsg-1) unstable; urgency=low
 .
   * New upstream release (Closes: #647036)
   * Switch to dpkg-source 3.0 (quilt) format
   * Remove lk_readnl fix from rules file
   * Bump standards version to 3.9.3
   * Change Conflicts to Breaks in control file
   * Suggest python for sdcc
   * Add arch-dependent-file-in-usr-share to overrides file
   * Add recommended target build arch (Closes: #459877)
   * Fix whatis entry for as2.1 manpage
   * Add manpage for as2gbmap
   * Add a get-orig-source target to rules file
   * Exclude non-free sources from source package (Closes: #597933)
   * Add +dfsg to source package name
   * Add version mangling to watch file
   * Add Vcs fields
   * Change all references to asranlib to sdranlib
   * Remove patches 01_fix_getline  02_result_type_gptr  03_fix_cmdlex
   * Remove sim/ucsim/libltdl in get-orig-source
   * Remove patch 04_libtool_fix
   * Rename other patches from 05, 06 to 01, 02
   * Add GPL+LE to copyright file
   * Fix sdcc manpage (Closes: #658188)
   * Bump compat to 8
   * Add build dependency on libboost-dev
   * Change texlive dependency to texlive-full. I clould not find minimum set
 of texlive packages needed to compile the package.
   * Remove go.bat from sdcc-doc
   * Add Build-Depends-Indep field (Thanks to Aron Xu)
   * Fix build/install arch/ind

Bug#676073: marked as done (java-gnome: FTBFS: /usr/bin/env: python: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 04:47:37 +
with message-id 
and subject line Bug#676073: fixed in java-gnome 4.1.1-3
has caused the Debian Bug report #676073,
regarding java-gnome: FTBFS: /usr/bin/env: python: 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.)


-- 
676073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: java-gnome
Version: 4.1.1-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> touch debian/stamp-autotools-files
> chmod a+x /«PKGBUILDDIR»/./configure
> mkdir -p .
> cd . &&   CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall" CXXFLAGS="" CPPFLAGS="-D_FORTIFY_SOURCE=2" 
> LDFLAGS="-Wl,-z,relro" /«PKGBUILDDIR»/./configure --build=x86_64-linux-gnu  
> --prefix=/usr --includedir="\${prefix}/include" 
> --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
> --sysconfdir=/etc --localstatedir=/var 
> --libexecdir="\${prefix}/lib/java-gnome" --srcdir=. --disable-maintainer-mode 
> --disable-dependency-tracking --disable-silent-rules   --libdir=/usr/lib/jni 
> jdk=/usr/lib/jvm/default-java 
> 
> equivalence, v0.2
> ...configuring Java projects to build and run on Linux & Unix
> 
> Identify operating system: Debian
> 
> Check for required jar files:
>  - JUnit test frameworkfound
> 
> Check for required system libraries:
>  - Cairo   found
>  - GLibfound
>  - GTK+found
>  - Pango   found
>  - RSVGfound
>  - ATK found
>  - GtkSourceView   found
>  - LibNotify   found
>  - Enchant found
>  - LibUnique   found
> 
> Check Java compilers:
>  - Specified javac works
>  - Specified javah found
>  - Specified jar   works
>  - Specified javadoc   found
>  - System javadoc  found
> 
> Check Java virtual machines:
>  - Specified java VM   works
> 
> Check native compiler:
>  - GNU gcc works
> 
> Select compiler:   javac
> Select runtime:java
> 
> Output:
>  - configuration data  ok
>  - native library location ok
> 
> touch debian/stamp-autotools
> DISPLAY=":99" /usr/bin/make  -C .  doc
> make[1]: Entering directory `/«PKGBUILDDIR»'
> /usr/bin/env: python: No such file or directory
> make[1]: *** [doc] Error 127

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/java-gnome_4.1.1-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
Source: java-gnome
Source-Version: 4.1.1-3

We believe that the bug you reported is fixed in the latest version of
java-gnome, which is due to be installed in the Debian FTP archive:

java-gnome_4.1.1-3.debian.tar.gz
  to main/j/java-gnome/java-gnome_4.1.1-3.debian.tar.gz
java-gnome_4.1.1-3.dsc
  to main/j/java-gnome/java-gnome_4.1.1-3.dsc
libjava-gnome-java-doc_4.1.1-3_all.deb
  to main/j/java-gnome/libjava-gnome-java-doc_4.1.1-3_all.deb
libjava-gnome-java_4.1.1-3_all.deb
  to main/j/java-gnome/libjava-gnome-java_4.1.1-3_all.deb
libjava-gnome-jni_4.1.1-3_amd64.deb
  to main/j/java-gnome/libjava-gnome-jni_4.1.1-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 676...@bugs.debian.org,
and the ma

Bug#671271: folder '.' could not be created / 'Empty mailbox name'

[Dmitrijs Ledkovs]

Dear Stefano,

>  *** Processing account Upsilon
>   Establishing connection to upsilon.:993
>   Creating folder .[UpsilonImaps]
>   ERROR: Creating folder on repository UpsilonImaps
> Folder '.'[UpsilonImaps] could not be created. Server responded: ('NO',
> ['Empty mailbox name.'])
>   ERROR: Folder '.'[UpsilonImaps] could not be created. Server responded: 
> ('NO',
> ['Empty mailbox name.'])
>   *** Finished account 'Upsilon' in 0:02

The newly uploaded 6.5.4 has a new option, which may be applicable in
your case. From the docs:

> createfolders
> -
> 
> By default OfflineImap propagates new folders in both
> directions. Sometimes this is not what you want. E.g. you might want
> new folders on your IMAP server to propagate to your local MailDir,
> but not the other way around. The 'readonly' setting on a repository
> will not help here, as it prevents any change from occuring on that
> repository. This is what the `createfolders` setting is for. By
> default it is `True`, meaning that new folders can be created on this
> repository. To prevent folders from ever being created on a
> repository, set this to `False`. If you set this to False on the
> REMOTE repository, you will not have to create the `Reverse
> nametrans`_ rules on the LOCAL repository.

From above error message, I recommend you try adding disabling
createfolders on the remote UpsilonImaps repository like so:

[Repository UpsilonImaps]
createfolders = False

Please let me know if this fixes it for you.

-- 
Regards,
Dmitrijs.




signature.asc
Description: OpenPGP digital signature

Processed: Reassigning 676041 to python-pip 1.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 676041 python-pip 1.1-1
Bug #676041 [src:zope2.12] zope2.12: FTBFS: ImportError: No module named pip.req
Bug reassigned from package 'src:zope2.12' to 'python-pip'.
No longer marked as found in versions zope2.12/2.12.22-1.
Ignoring request to alter fixed versions of bug #676041 to the same values 
previously set
Bug #676041 [python-pip] zope2.12: FTBFS: ImportError: No module named pip.req
Marked as found in versions python-pip/1.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676055: marked as done (mighttpd2: FTBFS: Mighty.hs:117:31: Not in scope: data constructor `HostAny')

[Debian Bug Tracking System]

Your message dated Tue, 5 Jun 2012 03:23:15 +
with message-id <20120605032315.ga20...@scru.org>
and subject line ftbfs
has caused the Debian Bug report #676055,
regarding mighttpd2: FTBFS: Mighty.hs:117:31: Not in scope: data constructor 
`HostAny'
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.)


-- 
676055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mighttpd2
Version: 2.5.6-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> ghc Setup.hs -o debian/mighttpd2.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/mighttpd2.setup ...
> test -f debian/rules
> debian/mighttpd2.setup configure --prefix=/usr \
> --enable-tests
> Configuring mighttpd2-2.5.6...
> touch stamp-configure
> test -f debian/rules
> debian/mighttpd2.setup build
> Building mighttpd2-2.5.6...
> Preprocessing test suite 'test' for mighttpd2-2.5.6...
> [1 of 6] Compiling Paths_mighttpd2  ( dist/build/autogen/Paths_mighttpd2.hs, 
> dist/build/test/test-tmp/Paths_mighttpd2.o )
> [2 of 6] Compiling Parser   ( Parser.hs, 
> dist/build/test/test-tmp/Parser.o )
> [3 of 6] Compiling Types( Types.hs, 
> dist/build/test/test-tmp/Types.o )
> [4 of 6] Compiling Route( Route.hs, 
> dist/build/test/test-tmp/Route.o )
> [5 of 6] Compiling Config.Internal  ( Config/Internal.hs, 
> dist/build/test/test-tmp/Config/Internal.o )
> [6 of 6] Compiling Main ( test/Test.hs, 
> dist/build/test/test-tmp/Main.o )
> Loading package ghc-prim ... linking ... done.
> Loading package integer-gmp ... linking ... done.
> Loading package base ... linking ... done.
> Loading package bytestring-0.9.2.1 ... linking ... done.
> Loading package array-0.4.0.0 ... linking ... done.
> Loading package deepseq-1.3.0.0 ... linking ... done.
> Loading package text-0.11.2.0 ... linking ... done.
> Loading package blaze-builder-0.3.1.0 ... linking ... done.
> Loading package containers-0.4.2.1 ... linking ... done.
> Loading package base-unicode-symbols-0.2.2.3 ... linking ... done.
> Loading package transformers-0.3.0.0 ... linking ... done.
> Loading package transformers-base-0.4.1 ... linking ... done.
> Loading package monad-control-0.3.1.3 ... linking ... done.
> Loading package lifted-base-0.1.1 ... linking ... done.
> Loading package resourcet-0.3.2.1 ... linking ... done.
> Loading package semigroups-0.8.3.2 ... linking ... done.
> Loading package void-0.5.5.1 ... linking ... done.
> Loading package conduit-0.4.2 ... linking ... done.
> Loading package blaze-builder-conduit-0.4.0.2 ... linking ... done.
> Loading package hashable-1.1.2.3 ... linking ... done.
> Loading package case-insensitive-0.4.0.1 ... linking ... done.
> Loading package http-types-0.6.11 ... linking ... done.
> Loading package mtl-2.1.1 ... linking ... done.
> Loading package parsec-3.1.2 ... linking ... done.
> Loading package unix-2.5.1.0 ... linking ... done.
> Loading package network-2.3.0.13 ... linking ... done.
> Loading package network-conduit-0.4.0.1 ... linking ... done.
> Loading package simple-sendfile-0.2.3 ... linking ... done.
> Loading package unix-compat-0.3.0.1 ... linking ... done.
> Loading package unordered-containers-0.2.1.0 ... linking ... done.
> Loading package vault-0.2.0.0 ... linking ... done.
> Loading package wai-1.2.0.2 ... linking ... done.
> Loading package warp-1.2.1.1 ... linking ... done.
> Loading package filepath-1.3.0.0 ... linking ... done.
> Loading package old-locale-1.0.0.4 ... linking ... done.
> Loading package old-time-1.1.0.0 ... linking ... done.
> Loading package directory-1.1.0.2 ... linking ... done.
> Loading package fast-logger-0.0.2 ... linking ... done.
> Loading package byteorder-1.0.3 ... linking ... done.
> Loading package time-1.4 ... linking ... done.
> Loading package wai-logger-0.1.4 ... linking ... done.
> Loading package wai-logger-prefork-0.1.3 ... linking ... done.
> Loading package attoparsec-0.10.1.1 ... linking ... done.
> Loading package attoparsec-conduit-0.4.0.1 ... linking ... done.
> Loading packa

Bug#676041: zope2.12: FTBFS: ImportError: No module named pip.req

[Arnaud Fontaine]

reassign 676041 python-pip 1.1-1
thanks

Hello,

Lucas Nussbaum  writes:

> During a rebuild of all packages  in sid, your package failed to build
> on amd64.
>
> Relevant part:
>> make[2]: Entering directory `/«PKGBUILDDIR»'
>> Cleaning...
>> rm -rf ./build
>> find ./source/ -maxdepth 2 -type d -name "build" -exec rm -rf {} \;
>> Building Zope2 2.12...
>> Traceback (most recent call last):
>>   File "./debian/build-scripts/build.py", line 249, in 
>> main()
>>   File "./debian/build-scripts/build.py", line 230, in main
>> base_build_dir=tmp_install_area)
>>   File "./debian/build-scripts/build.py", line 79, in install_dist
>> from pip.req import InstallRequirement
>> ImportError: No module named pip.req
>> make[2]: *** [build] Error 1
>
> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2012/06/04/zope2.12_2.12.22-1_unstable.log

Thanks  for the  bug  report.  I'm reassigning  this  bug to  python-pip
because since 1.1-1,  python-pip bumped X-Python-Version to  >= 2.7, and
Zope 2.12 uses Python 2.6, thus the error message.

This change  seems a bit  suspicious to me, especially  considering that
the  upstream  states  to  support  >= 2.4  (according  to  setup.py  at
least)  and that  I  could not  find  any reference  to  this change  in
debian/changelog unless I missed something of course ;-).

Cheers,
-- 
Arnaud Fontaine



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#669246: marked as done (zfs-fuse: fails to install due to insserv rejecting the script header)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 03:02:32 +
with message-id 
and subject line Bug#669246: fixed in zfs-fuse 0.7.0-8
has caused the Debian Bug report #669246,
regarding zfs-fuse: fails to install due to insserv rejecting the script header
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
669246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zfs-fuse
Version: 0.7.0-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install due
to insserv rejecting the script header. Some notes are
available from at http://wiki.debian.org/LSBInitScripts

>From the attached log (scroll to the bottom...):

  Setting up zfs-fuse (0.7.0-6) ...
  invoke-rc.d: policy-rc.d denied execution of restart.
  insserv: Service fuse has to be enabled to start service zfs-fuse
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing zfs-fuse (--configure):
   subprocess installed post-installation script returned error exit status 1

This problem has just appeared without zfs-fuse being updated in the
archive ... so probably the fuse dependency was indirectly satisfied
before, but changes to other packages may have removed that indirect
dependency inbetween.


cheers,

Andreas


libguestfs0_1:1.16.18-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: zfs-fuse
Source-Version: 0.7.0-8

We believe that the bug you reported is fixed in the latest version of
zfs-fuse, which is due to be installed in the Debian FTP archive:

zfs-fuse_0.7.0-8.debian.tar.gz
  to main/z/zfs-fuse/zfs-fuse_0.7.0-8.debian.tar.gz
zfs-fuse_0.7.0-8.dsc
  to main/z/zfs-fuse/zfs-fuse_0.7.0-8.dsc
zfs-fuse_0.7.0-8_i386.deb
  to main/z/zfs-fuse/zfs-fuse_0.7.0-8_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 669...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Asias He  (supplier of updated zfs-fuse package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 05 Jun 2012 09:34:39 +0800
Source: zfs-fuse
Binary: zfs-fuse
Architecture: source i386
Version: 0.7.0-8
Distribution: unstable
Urgency: low
Maintainer: Asias He 
Changed-By: Asias He 
Description: 
 zfs-fuse   - ZFS on FUSE
Closes: 669246
Changes: 
 zfs-fuse (0.7.0-8) unstable; urgency=low
 .
   * Fix "fails to install due to insserv rejecting the script header"
 Drop fuse in /etc/init.d/zfs-fuse (Closes: #669246)
Checksums-Sha1: 
 679e41ccc93baeef755d3d99ce33d5b091676e04 1968 zfs-fuse_0.7.0-8.dsc
 2e3e96abb890a583e12a671c60e2720f4f022ac7 19359 zfs-fuse_0.7.0-8.debian.tar.gz
 3c8bb08073cbe62af477a95a25fd8c67fed6f805 1360286 zfs-fuse_0.7.0-8_i386.deb
Checksums-Sha256: 
 78b1727f402251eb19c477facc55845ad8dabfd6133be2549b1f4666543c74a8 1968 
zfs-fuse_0.7.0-8.dsc
 69eaaa0c1b74620c1e387164e7e7dd12f89689ced1ad00a92bd96a802acef4bf 19359 
zfs-fuse_0.7.0-8.debian.tar.gz
 5a410fa8c1a5d9be198b7ae92d1d261eb3b5738b9273c66f3b724db37ff42311 1360286 
zfs-fuse_0.7.0-8_i386.deb
Files: 
 327f7d60978b5b9cf37bdd9749cb724a 1968 otherosfs optional zfs-fuse_0.7.0-8.dsc
 1888966692a21bfd12e9488d8d662da5 19359 otherosfs optional 
zfs-fuse_0.7.0-8.debian.tar.gz
 c3329b4c51f5740f77d21871c56e9c13 1360286 otherosfs optional 
zfs-fuse_0.7.0-8_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJPzWgkAAoJEK7JmSstf/GAuPwQAIussB7PMXuQprtt7yikqyqC
KxsxSAUYpGGCKaEEt4mdcF0HFzaq3NiCMs1Y3XwtkKjdXSM966HedBWIq40qDtd5
ymqkAvu5LEgrq6+Lx7J/N1YJZngHjzNMvIGwOd+DvF7DhFyW4UQ6TRkjEDl/rUTm
FywPBmo+HwmJFgwbZnu04JSei7+sEjDZao1SRv8NMP0m46VrmvSJuqzlUeLmYz4T
EkaOK3f15zuqOfYtIusIsZ8XDeDqwDyWCG22W58R9jB/89/EhSLq0elYa6ZYNynI
WC8W6Nw/HU07GGKHd377BIYYOYACCTRuoiPPI3wGXI0lImaIg8+Xu8aKJ0jA9YZl
QpbQyTQnWa7HR48Q02ap21kvNGv/1zgCaIW4DnuJcpC8Frgv+3GAfEePvQxrQiiD
Z4N05dutScEyeCQ6Nv+Ge0paF5avbzwnDdcOQXpzNI0utQrJc1arKEmMmEJ/yzqR
wNFgrrQlM1Nb7ib7Y3G3vL9/0yVa0R5N0uwO+U9ew5b1QJyg1sqT/+uTRvbwnA4C
/S4MKrwtastnoEuBWWZ6F3tQ8AXxOXGkUgzWejq/Do9xznaIbyuhm1/KjoQ4kFy4
lMik0QdWaMDmlSIv7mTk4H5s2wr2BnxHmPkyuEwpwI1yqKqaRfuncSYDP2yqsy9p
YEJ6jJ/Qdg1ZxUBJtEre
=qiW1

Bug#676148: ruby-romkan: needs encoding header for Ruby 1.9

[Kenshi Muto]

Package: ruby-romkan
Version: 0.4-8
Severity: grave
Tags: patch

Dear Maintainer,

romkan.rb seems need encoding header for Ruby 1.9 series.

# ruby -rromkan -e "nil"
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': 
/usr/lib/ruby/vendor_ruby/romkan.rb:29: invalid multibyte char (US-ASCII) 
(SyntaxError)
/usr/lib/ruby/vendor_ruby/romkan.rb:28: invalid multibyte char (US-ASCII)
/usr/lib/ruby/vendor_ruby/romkan.rb:28: syntax error, unexpected $end, 
expecting keyword_end

I believe adding following line to romkan.rb will fix this bug.
# -*- encoding: euc-jp -*-

This bug prevents to update migemo package.

Thanks,
-- 
Kenshi Muto
km...@debian.org



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676112: FTBFS bugs with Ruby 1.9 as /usr/bin/ruby

[Dirk Eddelbuettel]

On 4 June 2012 at 22:33, Antonio Terceiro wrote:
| Hi,
| 
| All these `cannot load such file -- mkmf` bugs are caused by
| ruby-pkg-tools calling /usr/bin/ruby instead of /usr/bin/ruby1.8
| explicitly. I've just uploaded a fixed version to unstable.

Darn. I just fixed mine by no longer relying on 'ruby, ruby1.8, ruby1.8-dev'
but just ruby1.8, ruby1.8-dev as I (mistakenly ?) concluded the package would
not build under ruby 1.9.

Dirk

-- 
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com  



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #http://mentors.debian.net/debian/pool/main/e/excellent-bifurcation/excellent-bifurcation_0.0.20071015-5.dsc
> tag 676026 + pending
Bug #676026 [src:excellent-bifurcation] excellent-bifurcation: FTBFS: ld: 
cannot find -lalleg-4.2.2
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: ecore: FTBFS[kfreebsd] testsuite failure

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # since the bug is intermittent on reporter's system and unreproducible
> # elsewhere, the package is still usable
> severity 673176 important
Bug #673176 {Done: Albin Tonnerre } [chromium] chromium: 
Chromium is locking up entire Gnome-Shell regularly
Severity set to 'important' from 'critical'
> reopen 673176
Bug #673176 {Done: Albin Tonnerre } [chromium] chromium: 
Chromium is locking up entire Gnome-Shell regularly
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ecore/1.2.0-2.
> tags 673176 - upstream
Bug #673176 [chromium] chromium: Chromium is locking up entire Gnome-Shell 
regularly
Removed tag(s) upstream.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
673176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676112: marked as done (quantlib-swig: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError))

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 01:34:34 +
with message-id 
and subject line Bug#676112: fixed in quantlib-swig 1.2-2
has caused the Debian Bug report #676112,
regarding quantlib-swig: FTBFS: 
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
such file -- mkmf (LoadError)
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.)


-- 
676112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quantlib-swig
Version: 1.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> *** Running on arch amd64 and cpu x86_64
> ./configure   --prefix=/usr   \
>   --build amd64
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking system... Linux
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... none
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... none
> checking whether g++ accepts warning flags... yes
> checking for QuantLib... 1.2
> checking for swig... no
> checking for python... /usr/bin/python
> checking for perl... /usr/bin/perl
> checking for ruby... /usr/bin/ruby
> checking for mzscheme... no
> checking for guile... no
> checking for gmcs... no
> checking for mcs... no
> checking for gmcs2... no
> checking for ocamlc... no
> checking for R... no
> checking for javac... no
> checking for jar... no
> checking for java... no
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating CSharp/Makefile
> config.status: creating Guile/Makefile
> config.status: creating Java/Makefile
> config.status: creating MzScheme/Makefile
> config.status: creating OCaml/Makefile
> config.status: creating Perl/Makefile
> config.status: creating Python/Makefile
> config.status: creating R/Makefile
> config.status: creating Ruby/Makefile
> config.status: executing depfiles commands
> (cd Python && \
>   CC="g++"\
>   CXX="g++"   \
>   CFLAGS="-O2 -Wall -Wno-strict-aliasing" 
> \
>   CXXFLAGS="-O2 -Wall -Wno-strict-aliasing"   
> \
>   python2.7 setup.py build)
> running build
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/QuantLib
> copying QuantLib/__init__.py -> build/lib.linux-x86_64-2.7/QuantLib
> copying QuantLib/QuantLib.py -> build/lib.linux-x86_64-2.7/QuantLib
> running build_ext
> building 'QuantLib._QuantLib' extension
> creating build/temp.linux-x86_64-2.7
> creating build/temp.linux-x86_64-2.7/QuantLib
> g++ -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
> -O2 -Wall -Wno-strict-aliasing -fPIC -I/usr/include/python2.7 -I/usr/include 
> -c QuantLib/quantlib_wrap.cpp -o 
> build/temp.linux-x86_64-2.7/QuantLib/quantlib_wrap.o -Wno-unused -O2 -Wall 
> -Wno-strict-aliasing
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++ [enabled by default]
> QuantLib/quantlib_wrap.cpp: In member fun

Bug#676076: FTBFS bugs with Ruby 1.9 as /usr/bin/ruby

[Antonio Terceiro]

Hi,

All these `cannot load such file -- mkmf` bugs are caused by
ruby-pkg-tools calling /usr/bin/ruby instead of /usr/bin/ruby1.8
explicitly. I've just uploaded a fixed version to unstable.

Many of the other bugs associated with the switch to Ruby 1.9 [1] may
also be caused by this.

[1] 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=default19;users=debian-r...@lists.debian.org

Lucas, can you please retry building all of them to see how many still
FTBFS with ruby-pkg-tools 0.18?

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Bug#676005: marked as done (zomg: FTBFS: ld: cannot find -lz)

[Debian Bug Tracking System]

Your message dated Tue, 5 Jun 2012 01:33:24 +
with message-id <20120605013324.ga17...@scru.org>
and subject line Re: Bug#676005: zomg: FTBFS: ld: cannot find -lz
has caused the Debian Bug report #676005,
regarding zomg: FTBFS: ld: cannot find -lz
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.)


-- 
676005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zomg
Version: 0.5.14-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> gcc -g -O2 -I/usr/include/libxml2 -g -O2  -lxml2 -lz -lm  -o zomghelper-xspf 
> zomghelper_xspf-zomghelper-xspf.o  -lvorbisfile -lm 
> /usr/bin/ld: cannot find -lz
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/zomg_0.5.14-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
On Mon, Jun 04, 2012 at 11:55:24PM +0200, Lucas Nussbaum wrote:
> > gcc -g -O2 -I/usr/include/libxml2 -g -O2  -lxml2 -lz -lm  -o 
> > zomghelper-xspf zomghelper_xspf-zomghelper-xspf.o  -lvorbisfile -lm 
> > /usr/bin/ld: cannot find -lz

This is #675682, fixed in libxml2 2.8.0+dfsg1-3.

--- End Message ---

Bug#675204: marked as done (asterisk: AST-2012-007 (CVE-2012-2947): crash on IAX receiving HOLD without MOH class)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 01:17:16 +
with message-id 
and subject line Bug#675204: fixed in asterisk 1:1.8.13.0~dfsg-1
has caused the Debian Bug report #675204,
regarding asterisk: AST-2012-007 (CVE-2012-2947): crash on IAX receiving HOLD 
without MOH class
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.)


-- 
675204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asterisk
Version: 1:1.8.11.1~dfsg-1
Severity: grave
Tags: upstream patch security
Justification: user security hole

A remotely exploitable crash vulnerability exists in the IAX2 channel
driver if an established call is placed on hold without a suggested
music class. For this to occur, the following must take place:

1. The setting mohinterpret=passthrough must be set on the end placing
   the call on hold.

2. A call must be established.

3. The call is placed on hold without a suggested music-on-hold class name.


When these conditions are true, Asterisk will attempt to use an invalid
pointer to a music-on-hold class name. Use of the invalid pointer will
either cause a crash or the music-on-hold class name will be garbage.

Issue applies to version in Stable (1.6.2.9) as well.

In the default settings used by the Debian package, on-hold music will be
defined if available (e.g. if any asterisk-moh-opsound package is
installed).

-- System Information:
Debian Release: wheezy/sid
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages asterisk depends on:
ii  adduser   3.113+nmu2
ii  asterisk-config   1:1.8.12.0~rc3~dfsg-0.9674
ii  asterisk-core-sounds-en [asterisk-prompt-en]  1.4.21-2
ii  asterisk-modules  1:1.8.12.0~rc3~dfsg-0.9674
ii  asterisk-sounds-main [asterisk-prompt-en] 1:1.8.3.3-0.8891
ii  libc6 2.13-32
ii  libcap2   1:2.22-1
ii  libgcc1   1:4.7.0-8
ii  libssl1.0.0   1.0.1c-1
ii  libstdc++64.7.0-8
ii  libtinfo5 5.9-7
ii  libxml2   2.7.8.dfsg-9.1

Versions of packages asterisk recommends:
ii  asterisk-moh-opsound-gsm 2.03-1
ii  asterisk-voicemail [asterisk-voicemail-storage]  1:1.8.12.0~rc3~dfsg-0.9674
ii  sox  14.3.2-3

Versions of packages asterisk suggests:
pn  asterisk-dahdi   1:1.8.12.0~rc3~dfsg-0.9674
pn  asterisk-dev 1:1.8.12.0~rc3~dfsg-0.9674
pn  asterisk-doc 1:1.8.12.0~rc3~dfsg-0.9674
pn  asterisk-ooh323  

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: asterisk
Source-Version: 1:1.8.13.0~dfsg-1

We believe that the bug you reported is fixed in the latest version of
asterisk, which is due to be installed in the Debian FTP archive:

asterisk-config_1.8.13.0~dfsg-1_all.deb
  to main/a/asterisk/asterisk-config_1.8.13.0~dfsg-1_all.deb
asterisk-dahdi_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-dahdi_1.8.13.0~dfsg-1_amd64.deb
asterisk-dbg_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-dbg_1.8.13.0~dfsg-1_amd64.deb
asterisk-dev_1.8.13.0~dfsg-1_all.deb
  to main/a/asterisk/asterisk-dev_1.8.13.0~dfsg-1_all.deb
asterisk-doc_1.8.13.0~dfsg-1_all.deb
  to main/a/asterisk/asterisk-doc_1.8.13.0~dfsg-1_all.deb
asterisk-mobile_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-mobile_1.8.13.0~dfsg-1_amd64.deb
asterisk-modules_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-modules_1.8.13.0~dfsg-1_amd64.deb
asterisk-mp3_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-mp3_1.8.13.0~dfsg-1_amd64.deb
asterisk-mysql_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-mysql_1.8.13.0~dfsg-1_amd64.deb
asterisk-ooh323_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-ooh323_1.8.13.0~dfsg-1_amd64.deb
asterisk-voicemail-imapstorage_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-voicemail-imapstorage_1.8.13.0~dfsg-1_amd64.deb
asterisk-voicemail-odbcstorage_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-voicemail-odbcstorage_1.8.13.0~dfsg-1_amd64.deb
asterisk-voicemail_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-voicemail_1.8.13.0~dfsg-1_amd64.deb
asterisk_1.8.13.0~dfsg-1.debian.tar.gz
  to main/a/ast

Bug#606959: marked as done (logrotate script should set correct owner/group)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jun 2012 01:17:16 +
with message-id 
and subject line Bug#606959: fixed in asterisk 1:1.8.13.0~dfsg-1
has caused the Debian Bug report #606959,
regarding logrotate script should set correct owner/group
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.)


-- 
606959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asterisk
Severity: serious
Version: 1:1.6.2.9-2

Hi,

It looks like the logrotate script is not setting owner/group on the
log files.

This causes nothing to be logged at all and/or prevent the daemon from
restarting.

Cheers

Laurent Bigonville


--- End Message ---
--- Begin Message ---
Source: asterisk
Source-Version: 1:1.8.13.0~dfsg-1

We believe that the bug you reported is fixed in the latest version of
asterisk, which is due to be installed in the Debian FTP archive:

asterisk-config_1.8.13.0~dfsg-1_all.deb
  to main/a/asterisk/asterisk-config_1.8.13.0~dfsg-1_all.deb
asterisk-dahdi_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-dahdi_1.8.13.0~dfsg-1_amd64.deb
asterisk-dbg_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-dbg_1.8.13.0~dfsg-1_amd64.deb
asterisk-dev_1.8.13.0~dfsg-1_all.deb
  to main/a/asterisk/asterisk-dev_1.8.13.0~dfsg-1_all.deb
asterisk-doc_1.8.13.0~dfsg-1_all.deb
  to main/a/asterisk/asterisk-doc_1.8.13.0~dfsg-1_all.deb
asterisk-mobile_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-mobile_1.8.13.0~dfsg-1_amd64.deb
asterisk-modules_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-modules_1.8.13.0~dfsg-1_amd64.deb
asterisk-mp3_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-mp3_1.8.13.0~dfsg-1_amd64.deb
asterisk-mysql_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-mysql_1.8.13.0~dfsg-1_amd64.deb
asterisk-ooh323_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-ooh323_1.8.13.0~dfsg-1_amd64.deb
asterisk-voicemail-imapstorage_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-voicemail-imapstorage_1.8.13.0~dfsg-1_amd64.deb
asterisk-voicemail-odbcstorage_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-voicemail-odbcstorage_1.8.13.0~dfsg-1_amd64.deb
asterisk-voicemail_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk-voicemail_1.8.13.0~dfsg-1_amd64.deb
asterisk_1.8.13.0~dfsg-1.debian.tar.gz
  to main/a/asterisk/asterisk_1.8.13.0~dfsg-1.debian.tar.gz
asterisk_1.8.13.0~dfsg-1.dsc
  to main/a/asterisk/asterisk_1.8.13.0~dfsg-1.dsc
asterisk_1.8.13.0~dfsg-1_amd64.deb
  to main/a/asterisk/asterisk_1.8.13.0~dfsg-1_amd64.deb
asterisk_1.8.13.0~dfsg.orig.tar.gz
  to main/a/asterisk/asterisk_1.8.13.0~dfsg.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 606...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tzafrir Cohen  (supplier of updated asterisk 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: Wed, 16 May 2012 18:43:18 +0300
Source: asterisk
Binary: asterisk asterisk-modules asterisk-dahdi asterisk-voicemail 
asterisk-voicemail-imapstorage asterisk-voicemail-odbcstorage asterisk-ooh323 
asterisk-mp3 asterisk-mysql asterisk-mobile asterisk-doc asterisk-dev 
asterisk-dbg asterisk-config
Architecture: source all amd64
Version: 1:1.8.13.0~dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Debian VoIP Team 
Changed-By: Tzafrir Cohen 
Description: 
 asterisk   - Open Source Private Branch Exchange (PBX)
 asterisk-config - Configuration files for Asterisk
 asterisk-dahdi - DAHDI devices support for the Asterisk PBX
 asterisk-dbg - Debugging symbols for Asterisk
 asterisk-dev - Development files for Asterisk
 asterisk-doc - Source code documentation for Asterisk
 asterisk-mobile - Bluetooth phone support for the Asterisk PBX
 asterisk-modules - loadable modules for the Asterisk PBX
 asterisk-mp3 - MP3 playback support for the Asterisk PBX
 asterisk-mysql - MySQL database protocol support for the Asterisk PBX
 asterisk-ooh323 - H.323 protocol support for the Asterisk PBX - ooH323c
 asterisk-voicemail - simple voicemail support for the Asterisk PBX
 asterisk-voicemail-imapstorage - IMAP voicemail storage support for the 
Asterisk PBX
 asterisk-voicemail-odbcstorage - ODBC voic

Bug#676142: smartmontools: FTBFS on GNU/kFreeBSD

[Petr Salinger]

Package: smartmontools
Version: 5.42+svn3539-1
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd


Hi,

the current version fails to build on GNU/kFreeBSD.

It needs extra includes, see bellow.

Thanks in advance

Petr

--- smartmontools-5.42+svn3539.orig/cciss.cpp
+++ smartmontools-5.42+svn3539/cciss.cpp
@@ -24,6 +24,10 @@
 #  define _HAVE_CCISS
 #elif defined(__FreeBSD_kernel__)
 #  include 
+#  ifdef __GLIBC__
+#  include 
+#  include 
+#  endif
 #  include CISS_LOCATION
 #  define _HAVE_CCISS
 #endif




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676141: rt4-extension-assettracker: fails to upgrade from wheezy: updating database schema for 1.2.4...command failed with code 2

[Andreas Beckmann]

Package: rt4-extension-assettracker
Version: 2.0.0~b2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'sid' fails.

>From the attached log (scroll to the bottom...):

  Setting up rt4-extension-assettracker (2.0.0~b2-4) ...
  upgrading the RT database for Asset Tracker
  updating database schema for 1.2.4...command failed with code 2
  postinst script aborted
  dpkg: error processing rt4-extension-assettracker (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   rt4-extension-assettracker


cheers,

Andreas


rt4-extension-assettracker_2.0.0~b2-4.log.gz
Description: GNU Zip compressed data

Processed: oops ... closed by mistake

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 593139
Bug #593139 {Done: Antonio Terceiro } [src:ruby1.9.1] 
ruby1.9.1: FTBFS on kfreebsd: test suite segfaults
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ruby1.9.1/1.9.3.194-1.
> reopen 593141
Bug #593141 {Done: Antonio Terceiro } [src:ruby1.9.1] 
ruby1.9.1: FTBFS on ia64: test suite segfaults
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ruby1.9.1/1.9.3.194-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
593139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593139
593141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#593141: oops ... closed by mistake

[Antonio Terceiro]

reopen 593139
reopen 593141
thanks

These bugs have been closed by mistake. The test suite is disabled on
ia64 and kfreebsd, so before closing these bugs we need to try building
with the test suite enabled.

Sorry for the noise.

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Processed: severity of 675921 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 675921 normal
Bug #675921 [mc] mc: FTP shows bad filenames, and they are not accessible
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: limit source to eris, tagging 675291

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #eris (1.3.19-4) unstable; urgency=low
> #
> #  * fixed symbols for GCC 4.7 (closes: #671950) (closes: #675291)
> #- incorporates and acknowledges NMU from Matthias Klose
> #
> limit source eris
Limiting to bugs with field 'source' containing at least one of 'eris'
Limit currently set to 'source':'eris'

> tags 675291 + pending
Bug #675291 [src:eris] FTBFS: symbols errors on any-i386
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676137: creates applications.menu instead of gnome-applications.menu

[Michael Biebl]

Package: alacarte
Version: 0.13.4-1
Severity: serious

Alacarte is supposed to edit ~/.config/menu/gnome-applications.menu when
running under GNOME but the latest update uses
~/.config/menu/applications.menu


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages alacarte depends on:
ii  gir1.2-gdkpixbuf-2.0  2.26.1-1
ii  gir1.2-glib-2.0   1.32.1-1
ii  gir1.2-gmenu-3.0  3.4.2-1
ii  gir1.2-gtk-3.03.4.3-1~local0
ii  python2.7.2-10

Versions of packages alacarte recommends:
ii  gnome-panel  3.4.2.1-2

alacarte suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676134: /usr/bin/evolution: Evolution does not start at all

[Petri Kaurinkoski]

Package: evolution
Version: 3.2.2-1+b1
Severity: grave
File: /usr/bin/evolution
Justification: renders package unusable

Dear Maintainer,

I run into problems a couple of weeks ago when my Debian testing  
system was

updated. After that evolution has not started at all. The only reopnse I
can get is when I try to start it from commandline. The response is then
"Segmentation fault". Ever since I have been unable to read my e- 
mails with

evollution, so in my opinion it is a pretty grave problem.

Best regards,

Petri Kaurinkoski

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15  
(charmap=ISO-8859-15\

)
Shell: /bin/sh linked to /bin/bash

Versions of packages evolution depends on:
ii  dbus 1.5.12-1
ii  debconf [debconf-2.0]1.5.43
ii  evolution-common 3.2.2-1
ii  evolution-data-server3.2.2-3
ii  gconf-service3.2.5-1
ii  gconf2   3.2.5-1
ii  gnome-icon-theme 3.4.0-2
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-32
ii  libcairo-gobject21.12.2-1
ii  libcairo21.12.2-1
ii  libcamel-1.2-29  3.2.2-3
ii  libcanberra-gtk3-0   0.28-4
ii  libcanberra0 0.28-4
ii  libclutter-1.0-0 1.10.4-3
ii  libclutter-gtk-1.0-0 1.2.0-2
ii  libcogl-pango0   1.10.2-3
ii  libcogl9 1.10.2-3
ii  libebackend-1.2-13.2.2-3
ii  libebook-1.2-12  3.2.2-3
ii  libecal-1.2-10   3.2.2-3
ii  libedataserver-1.2-153.2.2-3
ii  libedataserverui-3.0-1   3.2.2-3
ii  libenchant1c2a   1.6.0-7
ii  libevolution 3.2.2-1+b1
ii  libgail-3-0  3.4.2-1
ii  libgconf-2-4 3.2.5-1
ii  libgdata13   0.12.0-1
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libglib2.0-0 2.32.3-1
ii  libgnome-desktop-3-2 3.4.2-1
ii  libgtk-3-0   3.4.2-1
iigtkhtml-4.0-0 4.2.2-14.0-2
iigtkhtml-editor-4.0-0  4.2.2-113-32
iigweather-3-0  3.4.1-1
iiical0 0.48-2
iijson-glib-1.0-0   0.14.2-1.2-3
iimx-1.0-2  1.4.6-128-4
iinotify4   0.7.5-128-4
iinspr4-0d  2:4.9-3
iinss3-1d   2:3.13.4-3-2
iipango1.0-01.30.0-10.2-3
iisoup-gnome2.4-1   2.38.1-20.2-3
iisoup2.4-1 2.38.1-2.2-3
iisqlite3-0 3.7.12.1-1-3
iix11-6 2:1.4.99.901-2
iixcomposite1   1:0.4.3-22-3
iixdamage1  1:1.1.3-22-3
iixext6 2:1.3.1-20-7
iixfixes3   1:5.0-4
iixi6   2:1.6.1-12-1
iixml2  2.7.8.dfsg-9.1
ii  psmisc   22.16-1

Versions of packages evolution recommends:
ii  bogofilter 1.2.2+dfsg1-1+b1
ii  evolution-plugins  
iigtevolution-webcal   2.32.0-2+b1
iigtyelp   3.4.2-1

Versions of packages evolution suggests:
iijsevolution-dbg   3.2.2-1+b1
iimxevolution-exchange  3.2.1-2
iinoevolution-plugins-experimental  
iinsgnupg   1.4.12-4
iinsnetwork-manager 0.9.4.0-4

-- debconf information:
  evolution/needs_shutdown:
  evolution/kill_processes:




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676115: autogen: FTBFS: make[2]: *** No rule to make target `invoke-xml2ag.texi'. Stop.

[Bruce Korb]

On 06/04/12 15:24, Lucas Nussbaum wrote:

Source: autogen
Version: 1:5.12-0.1
Severity: serious


Going out on a limb, I am going to guess that when the ia64 issue is fixed,
this will be fixed, too:

https://sourceforge.net/tracker/?func=detail&atid=103593&aid=3531608&group_id=3593

autogen 5.16 FTBFS on ia64: 
https://buildd.debian.org/status/fetch.php?pkg=autogen&arch=ia64&ver=1%3A5.16-1&stamp=1338699057


Somewhere buried in there should be a little more information about:


MAKE="/usr/bin/make" ./mk-agen-texi.sh
mk-agen-texi FAILED: MAKE of /«PKGBUILDDIR»/xml2ag/invoke-xml2ag.texi 
failed.


and that will reveal what actually failed.  But let's avoid tail chasing
and wait until we know the exact cause of the ia64 failure.  (but you could
add a "set -x" command early in the mk-agen-texi.sh script, if you like.)



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676019: marked as done (gnome-python-desktop: FTBFS: metacity.c:957:112: error: 'META_FOCUS_MODE_CLICK' undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Mon, 04 Jun 2012 23:34:54 +
with message-id 
and subject line Bug#676019: fixed in gnome-python-desktop 2.32.0+dfsg-2
has caused the Debian Bug report #676019,
regarding gnome-python-desktop: FTBFS: metacity.c:957:112: error: 
'META_FOCUS_MODE_CLICK' undeclared (first use in this function)
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.)


-- 
676019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-python-desktop
Version: 2.32.0+dfsg-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I/«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./metacity -I.. 
> -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread 
> -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 
> -I/usr/include/libpng12 -I/usr/include/pygtk-2.0-D_FORTIFY_SOURCE=2 
> -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/metacity-1   
> -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall -std=c9x -fno-strict-aliasing -c -o 
> metacity_la-metacity.lo `test -f 'metacity.c' || echo 
> '/«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./metacity/'`metacity.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. 
> -I/«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./metacity -I.. 
> -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread 
> -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 
> -I/usr/include/libpng12 -I/usr/include/pygtk-2.0 -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/metacity-1 -g 
> -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall -std=c9x -fno-strict-aliasing -c metacity.c  
> -fPIC -DPIC -o .libs/metacity_la-metacity.o
> metacity.c: In function 'pymetacity_add_constants':
> metacity.c:957:112: error: 'META_FOCUS_MODE_CLICK' undeclared (first use in 
> this function)
> metacity.c:957:112: note: each undeclared identifier is reported only once 
> for each function it appears in
> metacity.c:958:113: error: 'META_FOCUS_MODE_SLOPPY' undeclared (first use in 
> this function)
> metacity.c:959:112: error: 'META_FOCUS_MODE_MOUSE' undeclared (first use in 
> this function)
> metacity.c:960:124: error: 'META_ACTION_TITLEBAR_TOGGLE_SHADE' undeclared 
> (first use in this function)
> metacity.c:961:127: error: 'META_ACTION_TITLEBAR_TOGGLE_MAXIMIZE' undeclared 
> (first use in this function)
> metacity.c:962:120: error: 'META_ACTION_TITLEBAR_MINIMIZE' undeclared (first 
> use in this function)
> metacity.c:963:116: error: 'META_ACTION_TITLEBAR_NONE' undeclared (first use 
> in this function)
> metacity.c:964:117: error: 'META_ACTION_TITLEBAR_LOWER' undeclared (first use 
> in this function)
> metacity.c:965:116: error: 'META_ACTION_TITLEBAR_MENU' undeclared (first use 
> in this function)
> metacity.c:966:116:

Bug#676011: marked as done (ramond: FTBFS: ld: cannot find -lz)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jun 2012 23:38:28 +
with message-id 
and subject line Bug#676011: fixed in ramond 0.5-4
has caused the Debian Bug report #676011,
regarding ramond: FTBFS: ld: cannot find -lz
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.)


-- 
676011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ramond
Version: 0.5-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /usr/bin/gcc log.o xmlparser.o main.o -o ramond -fPIE -pie -Wl,-z,relro 
> -Wl,-z,now -lpcap `apr-1-config --link-ld --libs ` `xml2-config --libs`
> /usr/bin/ld: cannot find -lz
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/ramond_0.5-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--- End Message ---
--- Begin Message ---
Source: ramond
Source-Version: 0.5-4

We believe that the bug you reported is fixed in the latest version of
ramond, which is due to be installed in the Debian FTP archive:

ramond_0.5-4.debian.tar.gz
  to main/r/ramond/ramond_0.5-4.debian.tar.gz
ramond_0.5-4.dsc
  to main/r/ramond/ramond_0.5-4.dsc
ramond_0.5-4_amd64.deb
  to main/r/ramond/ramond_0.5-4_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 676...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Dandrimont  (supplier of updated ramond 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 05 Jun 2012 01:18:59 +0200
Source: ramond
Binary: ramond
Architecture: source amd64
Version: 0.5-4
Distribution: sid
Urgency: low
Maintainer: Nicolas Dandrimont 
Changed-By: Nicolas Dandrimont 
Description: 
 ramond - IPv6 Router Advertisement MONitoring Daemon
Closes: 676011
Changes: 
 ramond (0.5-4) unstable; urgency=low
 .
   * Add explicit build-depends on zlib1g-dev (Closes: #676011)
 - Thanks to Lucas Nussbaum for the report and rebuilds
Checksums-Sha1: 
 720aac321a3fc2a44faedc9af590a97b0fdf3d0f 1914 ramond_0.5-4.dsc
 f8abf03b836284e41cc42c0465f7a8621f7cb8ad 8949 ramond_0.5-4.debian.tar.gz
 c2da31beca9457ac8688e80f0dc5697486e57ff9 23810 ramond_0.5-4_amd64.deb
Checksums-Sha256: 
 3d1bfb5c5125d7710990b9c6b7829dd7401ae89e9d0a0ff91194a981386fdc24 1914 
ramond_0.5-4.dsc
 bf24f90d44b07617f5042d0d8d4a8734bde51b22a1c51e1b9df419c48eca2529 8949 
ramond_0.5-4.debian.tar.gz
 98590f2ab2bddb671f75712526903ffa5ef699322cbd086cb15f1a310d7f3afa 23810 
ramond_0.5-4_amd64.deb
Files: 
 e06a52edad1f48c3fc72cdb6d63fe0a1 1914 net extra ramond_0.5-4.dsc
 e7573a9219a2b2f2fe7edf3bc997ee80 8949 net extra ramond_0.5-4.debian.tar.gz
 4c191acf3aab03cf2a73fe5884fdfb72 23810 net extra ramond_0.5-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJPzUSbAAoJEOwFizKNvp3qRLoP/j1tOh9abm+yBD4jQbdav+wc
okIApKC4H1fOVfGIVf7bKl3/MDglp84f6ugIRhQ27gYFyojYxRLAgg7oWofUj2ml
qPOMcYkzORFCxdtZDlN7ViZ6+KAzhrO3k9CLXI/ZnhbhK7LimwLji0hWfTODKDSm
Yhr2sJhNDxucCoCGleP2pfgciMETlXOHugLVcAznPHTC8Lc6YL/kKYL21x2m56k9
QbHr81ik4WSJ5fE9G0/qKrVFhMbzEZo2lGdOzp0UD4YRQ7GYrTcbuoAMscjXaxRK
6Js6MiegomO0a7+jASdLhPcTRPz7P+NtMZ4j69SVKHZIII3Ew+ZBAb27QCreTCq9
9ecaLqwraeJCQSwWoYJ1ytMiUl6AtEAp2xwQsdM3X3ojL4OwwqdWbGFstNxzo8Uq
eQJU7ehdWaEY91Z3hzJckN0bKm9IoVsP/SKP9FjkLUKDko3pe5jVHn8eKzoKYNUp
cQtpPUSQGOrxPjPt9bQRWMBTTTEc3489Woa2BdN6Pnuz6Za+rIggcqRYmeZzbwUo
relQe0RtktIea4nQEyrAPKKFZlm671EEMtHfPKglpvhMu/Bh09jVFlqTPhskvcja
U9qt2njNBMhjnIaR0kjsiP3JZI5iibIXfuDWR5gJjgbwpBJ1ecUh+m1cK4h7TlNG
gDlPT8E3f/g9URxaTdll
=DhkF
-END PGP SIGNATURE-


--- End Message ---

Bug#673167: ecore: FTBFS[kfreebsd] testsuite failure

[Cyril Brulebois]

Cyril Brulebois  (05/06/2012):
> That should help get ecore and friends into testing (graphviz dependency
> graph attached).

For real now.

Mraw,
KiBi.


15.dot
Description: MS-Word document


signature.asc
Description: Digital signature

Bug#673167: marked as done (ecore: FTBFS[kfreebsd] testsuite failure)

[Debian Bug Tracking System]

Your message dated Tue, 5 Jun 2012 01:32:38 +0200
with message-id <20120604233238.gg20...@mraw.org>
and subject line Re: Bug#673167: ecore: FTBFS[kfreebsd] testsuite failure
has caused the Debian Bug report #673167,
regarding ecore: FTBFS[kfreebsd] testsuite failure
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.)


-- 
673167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ecore
Version: 1.2.0-1
Severity: serious
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the kfreebsd-* buildds:

make[3]: Entering directory 
`/build/buildd-ecore_1.2.0-1-kfreebsd-amd64-OoyIwT/ecore-1.2.0'
Running suite(s): Ecore
ERR<42194>:ecore ecore_main.c:1422 _ecore_main_fd_handlers_bads_rem() Removing 
bad fds
ERR<42194>:ecore ecore_main.c:1431 _ecore_main_fd_handlers_bads_rem() Found bad 
fd at index 7
ERR<42194>:ecore ecore_main.c:1450 _ecore_main_fd_handlers_bads_rem() 
Problematic fd found at 7! setting it for delete
Client with ip ::1, port 39285, connected = 1!
Lost client with ip ::1!
Client was connected for 129936.601 seconds.
91%: Checks: 12, Failures: 1, Errors: 0
ecore_test_ecore_con.c:88:F:Ecore_Con:ecore_test_ecore_con_server:0: Failed
make[3]: *** [check-local] Error 255

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=ecore&arch=kfreebsd-amd64&ver=1.2.0-1&stamp=1337049873

Regards

Christoph

If you have further questions please mail debian-...@lists.debian.org

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer


--- End Message ---
--- Begin Message ---
Version: 1.2.0-2

Christoph Egger  (16/05/2012):
> Package: src:ecore
> Version: 1.2.0-1
> Severity: serious
> Tags: sid wheezy
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
> X-Debbugs-Cc: debian-...@lists.debian.org
> Justification: fails to build from source (but built successfully in the past)

Fixed with a typo in the changelog (see below). I'm Cc-ing the other bug
(that got closed) for information, letting Albin or the chromium
maintainers do the actual work. ;p

That should help get ecore and friends into testing (graphviz dependency
graph attached).

Extract from :
| Closes: 673176
| Changes: 
|  ecore (1.2.0-2) unstable; urgency=low
|  .
|* Use the new '-indep' targets of dh and update Build-Deps
|* accordingly
|* Move to dh compat level 9
|* debian/control: bump Standards-Version to 3.9.3
|* Disable the testsuite for now, it has too many issues (Closes:
|* #673176)

Mraw,
KiBi.


signature.asc
Description: Digital signature
--- End Message ---

Bug#673176: Bug#673167: ecore: FTBFS[kfreebsd] testsuite failure

[Cyril Brulebois]

Version: 1.2.0-2

Christoph Egger  (16/05/2012):
> Package: src:ecore
> Version: 1.2.0-1
> Severity: serious
> Tags: sid wheezy
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
> X-Debbugs-Cc: debian-...@lists.debian.org
> Justification: fails to build from source (but built successfully in the past)

Fixed with a typo in the changelog (see below). I'm Cc-ing the other bug
(that got closed) for information, letting Albin or the chromium
maintainers do the actual work. ;p

That should help get ecore and friends into testing (graphviz dependency
graph attached).

Extract from :
| Closes: 673176
| Changes: 
|  ecore (1.2.0-2) unstable; urgency=low
|  .
|* Use the new '-indep' targets of dh and update Build-Deps
|* accordingly
|* Move to dh compat level 9
|* debian/control: bump Standards-Version to 3.9.3
|* Disable the testsuite for now, it has too many issues (Closes:
|* #673176)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#655245: marked as done (vim-addon-manager: Does not work with Ruby 1.9 as default)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jun 2012 23:25:44 +
with message-id 
and subject line Bug#655245: fixed in vim-addon-manager 0.5.0
has caused the Debian Bug report #655245,
regarding vim-addon-manager: Does not work with Ruby 1.9 as default
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.)


-- 
655245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim-addon-manager
Version: 0.4.4
Severity: important
Tags: patch

$ dpkg -l vim-addon-manager
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NomeVersão Descrição
+++-===-===-==
ii  vim-addon-manager   0.4.4   manager of 
addons for the Vim editor
$ readlink -f /usr/bin/ruby
/usr/bin/ruby1.9.1
$ vim-addons list
/usr/bin/vim-addons:241: warning: (...) interpreted as grouped expression
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
such file -- vim/addon-manager (LoadError)
  from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
  from /usr/bin/vim-addons:157:in `'

I migrated vim-addon-manager to use gem2deb, our new Ruby packaging helper.
This includes support for both Ruby 1.8 and 1.9, and required modifying
vim-addon-manager sources to use the standard Ruby layout (library code in
lib/, programs in bin/). You can check the patches by fetching from
http://alioth.debian.org/~terceiro/vim-addon-manager.git/
(master branch)

The patches, in chronological order, are:

9b466a8 Turning vim-addon-manager in a proper Ruby project
876ff66 Add new changelog entry
f8c70a6 move Makefile to doc/
57e7277 Bump standards version and debhelper dependency
ba7ea69 Add missing debian/source/format
233e57b Minimal build-time testing
c98aa49 Install only *.txt at /usr/share/doc
5a30b7a Fix indentation

(the last is a bonus ;-))

After this bug gets a number, I will add another patch that includes
this bug number in the changelog.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim-addon-manager depends on:
ii  ruby4.8
ii  ruby1.8 [ruby]  1.8.7.352-2
ii  vim-common  2:7.3.363-1

Versions of packages vim-addon-manager recommends:
ii  vim2:7.3.363-1
ii  vim-gtk [vim]  2:7.3.363-1

vim-addon-manager suggests no packages.

-- no debconf information

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: vim-addon-manager
Source-Version: 0.5.0

We believe that the bug you reported is fixed in the latest version of
vim-addon-manager, which is due to be installed in the Debian FTP archive:

vim-addon-manager_0.5.0.dsc
  to main/v/vim-addon-manager/vim-addon-manager_0.5.0.dsc
vim-addon-manager_0.5.0.tar.gz
  to main/v/vim-addon-manager/vim-addon-manager_0.5.0.tar.gz
vim-addon-manager_0.5.0_all.deb
  to main/v/vim-addon-manager/vim-addon-manager_0.5.0_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 655...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated vim-addon-manager 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 22 Jan 2012 20:20:04 -0200
Source: vim-addon-manager
Binary: vim-addon-manager
Architecture: source all
Version: 0.5.0
Distribution: unstable
Urgency: low
Maintainer: Debian Vim Maintainers 
Changed-By: Antonio Terceiro 
Description: 
 vim-addon-manager - manager of addons for the Vim editor
Closes: 655245
Changes: 
 vim-addon-manager (0.5.0) unstable; urgency=low
 .
   * Addons now can now use a new layout: instead of having its files symlinked
 into the target dir,

Bug#675986: marked as done (vim-addon-manager: fatal Ruby error)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jun 2012 23:25:44 +
with message-id 
and subject line Bug#655245: fixed in vim-addon-manager 0.5.0
has caused the Debian Bug report #655245,
regarding vim-addon-manager: fatal Ruby error
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.)


-- 
655245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim-addon-manager
Version: 0.4.4
Severity: grave
Justification: renders package unusable

As of 0.4.4, invoking vim-addon-manager produces a fatal Ruby error, e.g.:

$ vim-addons install latex-suite
/usr/bin/vim-addons:241: warning: (...) interpreted as grouped expression
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load
such file -- vim/addon-manager (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/bin/vim-addons:157:in `'

The same error is produced no matter what argument is supplied (e.g., vim-
addons -h).

I was able to reproduce an identical error message on an i386 machine (running
sid) as well.

Using rbenv and ruby-build, I changed my global Ruby version from 1.9.3 to
1.8.7, but the error persisted.



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim-addon-manager depends on:
ii  ruby4.9
ii  ruby1.8 [ruby]  1.8.7.358-4
ii  vim-common  2:7.3.524-1

Versions of packages vim-addon-manager recommends:
ii  vim  2:7.3.524-1
ii  vim-gnome [vim]  2:7.3.524-1

vim-addon-manager suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: vim-addon-manager
Source-Version: 0.5.0

We believe that the bug you reported is fixed in the latest version of
vim-addon-manager, which is due to be installed in the Debian FTP archive:

vim-addon-manager_0.5.0.dsc
  to main/v/vim-addon-manager/vim-addon-manager_0.5.0.dsc
vim-addon-manager_0.5.0.tar.gz
  to main/v/vim-addon-manager/vim-addon-manager_0.5.0.tar.gz
vim-addon-manager_0.5.0_all.deb
  to main/v/vim-addon-manager/vim-addon-manager_0.5.0_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 655...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated vim-addon-manager 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 22 Jan 2012 20:20:04 -0200
Source: vim-addon-manager
Binary: vim-addon-manager
Architecture: source all
Version: 0.5.0
Distribution: unstable
Urgency: low
Maintainer: Debian Vim Maintainers 
Changed-By: Antonio Terceiro 
Description: 
 vim-addon-manager - manager of addons for the Vim editor
Closes: 655245
Changes: 
 vim-addon-manager (0.5.0) unstable; urgency=low
 .
   * Addons now can now use a new layout: instead of having its files symlinked
 into the target dir, they can install all their files into a single
 directory that will be installed in the target dir and added to the vim
 runtimepath. This feature is not complete yet, and will be finished with
 the next release.
   * New maintainer = myself.
   * Turn vim-addon-manager into a proper Ruby package. This should have no
 impact on end users, though. The source layout was changed to:
 + library code in lib/
 + main program in bin/
 + src/Makefile moved to doc/Makefile; debian/rules and the Makefile itself
   changed accordingly.
   * Migrate to gem2deb. This adds support for having Ruby 1.9 as /usr/bin/ruby
 (Closes: #655245)
   * Bumped Standards-Version to 3.9.2. No changes needed.
   * Avoid installing manpage sources into /usr/share/doc. Only install
 doc/*.txt instead.
Checksums-Sha1: 
 310901af43ef61f5b04bdb0bb93dec48ae72b15b 1116 vim-addon-manager_0.5.0.dsc
 05760d837d55039d6dfff172c15e9ed417ad2d36 21248 vim-addon-manager_0.5.0.tar.gz
 91e785f81b9c9b4b3d92a8cd5be8eb33e553cc35 17806 vim-addon-manager_0.5.0_all.deb
Checksums-Sha256: 
 4dcb70c1e914733299a1eb4d051501e89da86e3d45d9

Bug#676056: marked as done (ices2: FTBFS: configure: error: Unable to link with libxml)

[Debian Bug Tracking System]

Your message dated Tue, 5 Jun 2012 01:21:05 +0200
with message-id <20120604232105.go9...@jones.dk>
and subject line Re: Bug#676056: ices2: FTBFS: configure: error: Unable to link 
with libxml
has caused the Debian Bug report #676056,
regarding ices2: FTBFS: configure: error: Unable to link with libxml
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.)


-- 
676056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ices2
Version: 2.0.1-11
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING:  DEB_COMPRESS_EXCLUDE is a 
> deprecated variable
> 
> WARNING: copyright-check disabled - licensecheck (from devscripts package) is 
> missing.
> 
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> if test -e /usr/share/misc/config.guess ; then \
>   for i in ./config.guess ; do \
>   if ! test -e $i.cdbs-orig ; then \
>   mv $i $i.cdbs-orig ; \
>   cp --remove-destination 
> /usr/share/misc/config.guess $i ; \
>   fi ; \
>   done ; \
>   fi
> if test -e /usr/share/misc/config.sub ; then \
>   for i in ./config.sub ; do \
>   if ! test -e $i.cdbs-orig ; then \
>   mv $i $i.cdbs-orig ; \
>   cp --remove-destination 
> /usr/share/misc/config.sub $i ; \
>   fi ; \
>   done ; \
>   fi
> cd . && libtoolize -c -f
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> cd . && aclocal-1.10 -I m4
> if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . && `which 
> autoconf2.60 || which autoconf`; fi
> if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . && `which 
> autoheader2.60 || which autoheader` ; fi
> if [ -e ./Makefile.am ]; then cd . && automake-1.10  ; fi
> touch debian/stamp-autotools-files
> chmod a+x /«PKGBUILDDIR»/./configure
> mkdir -p .
> cd . &&   CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall" CXXFLAGS="" CPPFLAGS="-D_FORTIFY_SOURCE=2" 
> LDFLAGS="-Wl,-z,relro" /«PKGBUILDDIR»/./configure --build=x86_64-linux-gnu  
> --prefix=/usr --includedir="\${prefix}/include" 
> --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
> --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/ices2" 
> --srcdir=. --disable-maintainer-mode --disable-dependency-tracking 
> --disable-silent-rules   --program-transform-name="s/ices$/ices2/" 
> configure: WARNING: unrecognized options: --disable-silent-rules
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C

Processed: limit source to ramond, tagging 676011

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #ramond (0.5-4) unstable; urgency=low
> #
> #  * Add explicit build-depends on zlib1g-dev (Closes: #676011)
> #- Thanks to Lucas Nussbaum for the report and rebuilds
> #
> limit source ramond
Limiting to bugs with field 'source' containing at least one of 'ramond'
Limit currently set to 'source':'ramond'

> tags 676011 + pending
Bug #676011 [src:ramond] ramond: FTBFS: ld: cannot find -lz
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#675955: mumble-server: Error launching mumble-server 1.2.3-348

[Natanaël Glacet]

Hello.

I came from the 1.2.3-313-ge5c4657-1 version and go to the
1.2.3-348-g317f5a0-1.
I tried to install it on 3 differents debian wheezy and I've the same error
message.

I tried : upgrade from 1.2.3-313-ge5c4657-1 to 1.2.3-348-g317f5a0-1
install mumble-server on a fresh debian wheezy install ( 1VM && 1 desktop).

I don't know if it's all you need ?

Cheers,
Natanaël



2012/6/4 Ron 

>
> Hi,
>
> Do you know what version of this you were using before the upgrade?
>
> This isn't a symbol directly used in the mumble code itself, so my first
> guess is that the-me blindly enabled the hardening wrappers and -z now,
> and didn't actually test it to find out this screwed with some plugin.
>
> That was a little while ago now though, so I'm a bit surprised nobody
> else has noticed it yet if that is really the case.
>
> Knowing which version you came from (or which version you need to go
> back to before it works again) would help narrow this down though.
>
>  Cheers,
>  Ron
>
>
> On Mon, Jun 04, 2012 at 04:24:14PM +0200, nglacet wrote:
> > Package: mumble-server
> > Version: 1.2.3-348-g317f5a0-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > Dear Maintainer,
> >
> >
> >* What led up to the situation?
> >   I upgraded my system this morning. It updated my mumble-server.
> Since then, I've the following error message when I try to launch my
> mumble-server : /usr/sbin/murmurd: symbol lookup error: /usr/sbin/murmurd:
> undefined symbol: _ZN3Ice6upCastEPNS_10ConnectionE
> >
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> >   I tried to uninstall/reinstall mumble-server, the problem is still
> here.
> >   I tried to install mumble-server on another Debian Wheezy : it's
> the same result.
> >* What was the outcome of this action?
> >   The problem is still here, I can't launch mumble-server.
> >* What outcome did you expect instead?
> >   I expect that it allow me to start my mumble-server.
> >
> >
> > PS : sorry for my poor english
> >
> >
> > -- System Information:
> > Debian Release: wheezy/sid
> >   APT prefers testing
> >   APT policy: (990, 'testing')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core)
> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> >
> > Versions of packages mumble-server depends on:
> > ii  adduser3.113+nmu2
> > ii  dbus   1.5.12-1
> > ii  debconf [debconf-2.0]  1.5.43
> > ii  libavahi-client3   0.6.31-1
> > ii  libavahi-common3   0.6.31-1
> > ii  libavahi-compat-libdnssd1  0.6.31-1
> > ii  libc6  2.13-32
> > ii  libcap21:2.22-1
> > ii  libgcc11:4.7.0-8
> > ii  libiceutil34   3.4.2-7.2
> > ii  libprotobuf7   2.4.1-1
> > ii  libqt4-dbus4:4.8.1-1
> > ii  libqt4-network 4:4.8.1-1
> > ii  libqt4-sql 4:4.8.1-1
> > ii  libqt4-sql-sqlite  4:4.8.1-1
> > ii  libqt4-xml 4:4.8.1-1
> > ii  libqtcore4 4:4.8.1-1
> > ii  libssl1.0.01.0.1c-1
> > ii  libstdc++6 4.7.0-8
> > ii  libzeroc-ice34 3.4.2-7.2
> >
> > mumble-server recommends no packages.
> >
> > Versions of packages mumble-server suggests:
> > pn  mumble-django  
> > pn  mumble-server-web  
> >
> > -- debconf information:
> >   mumble-server/password: (password omitted)
> >   mumble-server/use_capabilities: false
> >   mumble-server/start_daemon: true
> >
> >
>



-- 
Glacet Natanaël

Processed: reassign 676107 to dpkg, reassign 676122 to dpkg, forcibly merging 675613 676107 676122

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 676107 dpkg
Bug #676107 [debiandoc-sgml] debian-faq: FTBFS: nsgmls:0:6:0:E: reference 
to entity "DEBIANDOC" for which no system identifier could be generated
Bug reassigned from package 'debiandoc-sgml' to 'dpkg'.
Ignoring request to alter found versions of bug #676107 to the same values 
previously set
Ignoring request to alter fixed versions of bug #676107 to the same values 
previously set
> reassign 676122 dpkg
Bug #676122 [debiandoc-sgml] debian-history: FTBFS: nsgmls:0:1:26:E: 
reference to entity "DEBIANDOC" for which no system identifier could be 
generated
Bug reassigned from package 'debiandoc-sgml' to 'dpkg'.
Ignoring request to alter found versions of bug #676122 to the same values 
previously set
Ignoring request to alter fixed versions of bug #676122 to the same values 
previously set
> forcemerge 675613 676107 676122
Bug #675613 [dpkg] debiandoc-sgml: Does not register itself in /etc/sgml/catalog
Bug #675613 [dpkg] debiandoc-sgml: Does not register itself in /etc/sgml/catalog
Added tag(s) sid and wheezy.
Bug #676122 [dpkg] debian-history: FTBFS: nsgmls:0:1:26:E: reference to 
entity "DEBIANDOC" for which no system identifier could be generated
Added indication that 676122 affects 
docbook-simple,python-docutils,xml-core,debiandoc-sgml,sgml2x,docbook-mathml,sgml-data,docbook,docbook-xml,libcommons-validator-java,docbook-website,docbook-dsssl,docbook-html-forms,docbook-slides,dtd-ead,docbook-ebnf,w3c-dtd-xhtml
Bug #676107 [dpkg] debian-faq: FTBFS: nsgmls:0:6:0:E: reference to entity 
"DEBIANDOC" for which no system identifier could be generated
Added indication that 676107 affects 
docbook-simple,python-docutils,xml-core,debiandoc-sgml,sgml2x,docbook-mathml,sgml-data,docbook,docbook-xml,libcommons-validator-java,docbook-website,docbook-dsssl,docbook-html-forms,docbook-slides,dtd-ead,docbook-ebnf,w3c-dtd-xhtml
Merged 675613 676107 676122
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675613
676107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676107
676122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): reassign 676107 to debiandoc-sgml, reassign 676122 to debiandoc-sgml ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 676107 debiandoc-sgml
Bug #676107 [src:debian-faq] debian-faq: FTBFS: nsgmls:0:6:0:E: reference 
to entity "DEBIANDOC" for which no system identifier could be generated
Bug reassigned from package 'src:debian-faq' to 'debiandoc-sgml'.
No longer marked as found in versions debian-faq/5.0.
Ignoring request to alter fixed versions of bug #676107 to the same values 
previously set
> reassign 676122 debiandoc-sgml
Bug #676122 [src:debian-history] debian-history: FTBFS: nsgmls:0:1:26:E: 
reference to entity "DEBIANDOC" for which no system identifier could be 
generated
Bug reassigned from package 'src:debian-history' to 'debiandoc-sgml'.
No longer marked as found in versions debian-history/2.16.
Ignoring request to alter fixed versions of bug #676122 to the same values 
previously set
> forcemerge 675613 676107 676122
Bug #675613 [dpkg] debiandoc-sgml: Does not register itself in /etc/sgml/catalog
Unable to merge bugs because:
package of #676122 is 'debiandoc-sgml' not 'dpkg'
package of #676107 is 'debiandoc-sgml' not 'dpkg'
Failed to forcibly merge 675613: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x33a7de0)', 
'requester', 'David Pr\x{c3}\x{a9}vot ', 'request_addr', 
'cont...@bugs.debian.org', 'request_msgid', 
'<1338851161-52-bts-taf...@debian.org>', 'request_subject', ...) called at 
/usr/lib/debbugs/service line 887
eval {...} called at /usr/lib/debbugs/service line 886

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675613
676107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676107
676122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Tagging patch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 676026 + patch
Bug #676026 [src:excellent-bifurcation] excellent-bifurcation: FTBFS: ld: 
cannot find -lalleg-4.2.2
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676026: excellent-bifurcation: FTBFS: ld: cannot find -lalleg-4.2.2

[Andreas Rönnquist]

To solve this, please link against -lalleg, instead of -lalleg-4.2.2 -
Simple patch against Makefile applied.

/Andreas
--- a/src/Makefile
+++ b/src/Makefile
@@ -3,7 +3,7 @@
 PKGCONFIG_FILES=libxdg-basedir
 PKGCONFIG_CFLAGS= `pkg-config $(PKGCONFIG_FILES) --cflags`
 PKGCONFIG_LDFLAGS= `pkg-config $(PKGCONFIG_FILES) --libs`
-LDFLAGS=-lalleg-4.2.2
+LDFLAGS=-lalleg
 SOURCES=$(shell find . -name "*.c")
 OBJECTS=$(SOURCES:.c=.o)
 EXECUTABLE=excellent-bifurcation

Bug#676128: god: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: god
Version: 0.7.18-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules clean
> /usr/share/cdbs/1/rules/buildcore.mk:63: parsing god_0.7.18.orig.tar.gz ...
> test -x debian/rules
> dh_testroot
> dh_clean 
> if [ ! -L debian-setup.rb ] ; then if [ -f debian-setup.rb ] ; then mv 
> debian-setup.rb debian-setup.rb.moved_away_by_debian_build ; fi ; ln -s 
> /usr/lib/ruby/1.8/setup.rb debian-setup.rb ; fi
> /usr/bin/ruby debian-setup.rb config --installdirs=std
> debian-setup.rb:789: Use RbConfig instead of obsolete and deprecated Config.
> ---> bin
> <--- bin
> ---> lib
> ---> lib/god
> ---> lib/god/conditions
> <--- lib/god/conditions
> ---> lib/god/cli
> <--- lib/god/cli
> ---> lib/god/contacts
> <--- lib/god/contacts
> ---> lib/god/behaviors
> <--- lib/god/behaviors
> ---> lib/god/system
> <--- lib/god/system
> ---> lib/god/event_handlers
> <--- lib/god/event_handlers
> <--- lib/god
> <--- lib
> ---> ext
> ---> ext/god
> /usr/bin/ruby1.9.1 /«PKGBUILDDIR»/ext/god/extconf.rb
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /«PKGBUILDDIR»/ext/god/extconf.rb:1:in `'
> debian-setup.rb:656:in `command': system("/usr/bin/ruby1.9.1" 
> "/«PKGBUILDDIR»/ext/god/extconf.rb") failed (RuntimeError)
>   from debian-setup.rb:661:in `ruby'
>   from debian-setup.rb:1239:in `extconf'
>   from debian-setup.rb:1231:in `config_dir_ext'
>   from debian-setup.rb:1533:in `block in traverse'
>   from debian-setup.rb:1550:in `dive_into'
>   from debian-setup.rb:1531:in `traverse'
>   from debian-setup.rb:1535:in `block (2 levels) in traverse'
>   from debian-setup.rb:1534:in `each'
>   from debian-setup.rb:1534:in `block in traverse'
>   from debian-setup.rb:1550:in `dive_into'
>   from debian-setup.rb:1531:in `traverse'
>   from debian-setup.rb:1525:in `block in exec_task_traverse'
>   from debian-setup.rb:1520:in `each'
>   from debian-setup.rb:1520:in `exec_task_traverse'
>   from debian-setup.rb:1224:in `exec_config'
>   from debian-setup.rb:992:in `exec_config'
>   from debian-setup.rb:827:in `invoke'
>   from debian-setup.rb:774:in `invoke'
>   from debian-setup.rb:1579:in `'
> make: *** [clean] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/god_0.7.18-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676127: ocamlviz: FTBFS: I can't open file `mp-tool'.

[Lucas Nussbaum]

Source: ocamlviz
Version: 1.01-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»'
> cd doc && mlpost -latex manual.tex -pdf fig.ml && pdflatex manual.tex
> This is MetaPost, version 1.504 (kpathsea version 6.1.0)
> (mpost.mp (/usr/share/texlive/texmf-dist/metapost/base/plain.mp
> Preloading the plain mem file, version 1.004)) (./mlpost9c9b7e.mp
> ! I can't open file `mp-tool'.
> l.1 input mp-tool
>   ; % some initializations and auxiliary macros
> Please type another input file name
> ! Emergency stop.
> l.1 input mp-tool
>   ; % some initializations and auxiliary macros
> Transcript written on mlpost9c9b7e.log.
> 
> make[2]: *** [doc/manual.pdf] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/ocamlviz_1.01-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676126: netsed: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- test_helper (LoadError)

[Lucas Nussbaum]

Source: netsed
Version: 1.00b-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh build
>dh_testdir
>dh_auto_configure
>dh_auto_build
> make[1]: Entering directory `/«PKGBUILDDIR»'
> cc -Wall -fomit-frame-pointernetsed.c   -o netsed
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>dh_auto_test
> make[1]: Entering directory `/«PKGBUILDDIR»'
> ruby test/ts_full.rb
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- test_helper (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from test/ts_full.rb:16:in `'
> make[1]: *** [test] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/netsed_1.00b-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676125: dh-make-drupal: FTBFS: help2man: can't get `--help' info from ./dh-make-drupal

[Lucas Nussbaum]

Source: dh-make-drupal
Version: 0.9-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> dh binary
>dh_testroot
>dh_prep
>dh_installdirs
>dh_auto_install
>debian/rules override_dh_install
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_install
> help2man -s 1 -N ./dh-make-drupal \
>   --name='Builds a Debian package for the requested Drupal 
> project' \
>   > 
> "/«PKGBUILDDIR»/debian/dh-make-drupal"/usr/share/man/man1/dh-make-drupal.1
> help2man: can't get `--help' info from ./dh-make-drupal
> Try `--no-discard-stderr' if option outputs to stderr
> make[1]: *** [override_dh_install] Error 255

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/dh-make-drupal_0.9-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676124: uima-as: FTBFS: /«PKGBUILDDIR»/uimaj-as-jms/src/main/java/org/apache/uima/adapter/jms/client/BaseUIMAAsynchronousEngineCommon_impl.java:[1883,31] cannot find symbol

[Lucas Nussbaum]

Source: uima-as
Version: 2.3.1-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> make[1]: Nothing to be done for `patch-poms'.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> cd uima-as/ && /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties 
> -Dclassworlds.conf=/etc/maven2/m2-debian.conf 
> org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml 
> -Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo  package
> [INFO] 
> NOTE: Maven is executing in offline mode. Any artifacts not already in your 
> local
> repository will be inaccessible.
> 
> [INFO] Scanning for projects...
> [INFO] Reactor build order: 
> [INFO]   UIMA-AS: uima-as-parent
> [INFO]   UIMA-AS: uimaj-as-core
> [INFO]   UIMA-AS: uimaj-as-jms
> [INFO]   UIMA-AS: uimaj-as-activemq
> [INFO]   UIMA AS: uimaj-as-osgi-runtime
> [INFO]   UIMA-AS Aggregate: aggregate-uima-as-eclipse-plugins
> [INFO]   UIMA-AS Aggregate: aggregate-uima-as
> [INFO]   UIMA-AS: uima-as
> [INFO] 
> 
> [INFO] Building UIMA-AS: uima-as-parent
> [INFO]task-segment: [package]
> [INFO] 
> 
> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> [INFO] 
> 
> [INFO] Building UIMA-AS: uimaj-as-core
> [INFO]task-segment: [package]
> [INFO] 
> 
> [INFO] [build-helper:parse-version {execution: parse-version}]
> [INFO] [resources:copy-resources {execution: setVersions}]
> [WARNING] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 1 resource
> [INFO] [build-helper:add-source {execution: addVersionSrc}]
> [INFO] Source directory: 
> /«PKGBUILDDIR»/uimaj-as-core/target/generated-sources/releaseVersion added.
> [INFO] [resources:resources {execution: default-resources}]
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 1 resource
> [INFO] [compiler:compile {execution: default-compile}]
> [INFO] Compiling 142 source files to 
> /«PKGBUILDDIR»/uimaj-as-core/target/classes
> [INFO] [resources:testResources {execution: default-testResources}]
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory 
> /«PKGBUILDDIR»/uimaj-as-core/src/test/resources
> [INFO] [compiler:testCompile {execution: default-testCompile}]
> [INFO] Not compiling test sources
> [INFO] [surefire:test {execution: default-test}]
> [INFO] Tests are skipped.
> [INFO] [jar:jar {execution: default-jar}]
> [INFO] Building jar: /«PKGBUILDDIR»/uimaj-as-core/target/uimaj-as-core.jar
> [INFO] 
> 
> [INFO] Building UIMA-AS: uimaj-as-jms
> [INFO]task-segment: [package]
> [INFO] 
> 
> [INFO] [resources:resources {execution: default-resources}]
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 1 resource
> [INFO] [compiler:compile {execution: default-compile}]
> [INFO] Compiling 12 source files to /«PKGBUILDDIR»/uimaj-as-jms/target/classes
> [INFO] 
> 
> [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
> 
> /«PKGBUILDDIR»/uimaj-as-jms/src/main/java/org/apache/uima/adapter/jms/client/ClientServiceDelegate.java:[21,16]
>  package javax.jms does not exist
> 
> /«PKGBUILDDIR»/uimaj-as-jms/src/main/java/org/apache/uima/adapter/jms/client/BaseUIMAAsynchronousEngineCommon_impl.java:[38,16]
>  package javax.jms does not exist
> 
> /«PKGBUILDDIR»/uimaj-as-jms/src/main/java/org/apache/uima/adapter/jms/client/BaseUIMAAsynchronousEngineCommon_impl.jav

Bug#676123: jed: FTBFS: UTF-8 mode not enabled-- test_search_char not run.

[Lucas Nussbaum]

Source: jed
Version: 1:0.99.19-2.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/src'
> ./test/runtests.sh /«PKGBUILDDIR»/src/objs/jed
> Running /«PKGBUILDDIR»/src/objs/jed -script ./test/test_cmode.sl
> Unable to open cmode.  Check the value of the S-Lang load path.

> /«PKGBUILDDIR»/src/test/test_cmode.sl:11:test_cmode:Open failed
>   Local variables for test_cmode:
>   String_Type file = "/«PKGBUILDDIR»/src/test/test_cmode.dat"
>   Undefined_Type failures = Undefined_Type
>   Undefined_Type col = Undefined_Type
>   Undefined_Type line = Undefined_Type
> /«PKGBUILDDIR»/src/test/test_cmode.sl:47::Open failed
> Running /«PKGBUILDDIR»/src/objs/jed -script ./test/test_expand.sl
> Running /«PKGBUILDDIR»/src/objs/jed -script ./test/test_links.sl
> Unable to open tmpfile.  Check the value of the S-Lang load path.

> /«PKGBUILDDIR»/src/test/test_links.sl:3::Open failed
> Running /«PKGBUILDDIR»/src/objs/jed -script ./test/test_narrow.sl
> Unable to open cmode.  Check the value of the S-Lang load path.

> /«PKGBUILDDIR»/src/test/test_narrow.sl:7:test_narrow:Open failed
>   Local variables for test_narrow:
>   String_Type str = "A single line"
>   String_Type narrow_str = "single"
>   Undefined_Type b = Undefined_Type
> /«PKGBUILDDIR»/src/test/test_narrow.sl:46::Open failed
> Running /«PKGBUILDDIR»/src/objs/jed -script ./test/test_replace.sl
> Running /«PKGBUILDDIR»/src/objs/jed -script ./test/test_search.sl
> UTF-8 mode not enabled-- test_search_char not run.
> make[1]: *** [runtests] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/jed_0.99.19-2.1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676122: debian-history: FTBFS: nsgmls:0:1:26:E: reference to entity "DEBIANDOC" for which no system identifier could be generated

[Lucas Nussbaum]

Source: debian-history
Version: 2.16
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»'
> po4a-gettextize -M UTF-8 -f sgml -m project-history.sgml -p 
> project-history.pot
> nsgmls:0:1:26:W: cannot generate system identifier for document type 
> "DEBIANDOC"
> nsgmls:0:1:26:E: reference to entity "DEBIANDOC" for which no system 
> identifier could be generated
> nsgmls:0:1:0: entity was defined here
> nsgmls:0:1:26:E: DTD did not contain element declaration for document 
> type name
> po4a::sgml: Error while running nsgmls -p.  Please check if nsgmls and the 
> DTD are installed.
> make[2]: *** [project-history.pot] Error 25

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/debian-history_2.16_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676121: tupi: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- qonf/test (LoadError)

[Lucas Nussbaum]

Source: tupi
Version: 0.1+git12-5
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
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 `/«BUILDDIR»/tupi-0.1+git12'
> # rebuild translations
> lupdate tupi.pro -locations none -silent -ts 
> src/shell/data/translations/tupi_ca.ts
> /usr/include/qt4/QtCore/qbytearray.h:618: circular inclusion of 
> /usr/include/qt4/QtCore/qstring.h
> /usr/include/qt4/QtCore/qstringbuilder.h:45: circular inclusion of 
> /usr/include/qt4/QtCore/qstring.h
> /usr/include/qt4/QtGui/qwmatrix.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qmatrix.h
> /usr/include/qt4/QtGui/qboxlayout.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qlayout.h
> /usr/include/qt4/QtGui/qgridlayout.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qlayout.h
> /usr/include/qt4/QtGui/qactiongroup.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qaction.h
> /«BUILDDIR»/tupi-0.1+git12/src/framework/tgui/kdatetable.cpp:77: Class 'Day' 
> lacks Q_OBJECT macro
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktbackground.h:41: circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktscene.h
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktframe.h:41: circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktsvgitem.h
> /«BUILDDIR»/tupi-0.1+git12/src/components/animation/ktviewcamera.h:43: 
> circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/components/animation/ktcamerastatus.h
> lupdate warning: TS files from command line prevent recursing into 
> /«BUILDDIR»/tupi-0.1+git12/src/shell/shell.pro.
> lrelease src/shell/data/translations/tupi_ca.ts
> Updating 'src/shell/data/translations/tupi_ca.qm'...
> Generated 333 translation(s) (256 finished and 77 unfinished)
> Ignored 353 untranslated source text(s)
> # rebuild translations
> lupdate tupi.pro -locations none -silent -ts 
> src/shell/data/translations/tupi_cs.ts
> /usr/include/qt4/QtCore/qbytearray.h:618: circular inclusion of 
> /usr/include/qt4/QtCore/qstring.h
> /usr/include/qt4/QtCore/qstringbuilder.h:45: circular inclusion of 
> /usr/include/qt4/QtCore/qstring.h
> /usr/include/qt4/QtGui/qwmatrix.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qmatrix.h
> /usr/include/qt4/QtGui/qboxlayout.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qlayout.h
> /usr/include/qt4/QtGui/qgridlayout.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qlayout.h
> /usr/include/qt4/QtGui/qactiongroup.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qaction.h
> /«BUILDDIR»/tupi-0.1+git12/src/framework/tgui/kdatetable.cpp:77: Class 'Day' 
> lacks Q_OBJECT macro
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktbackground.h:41: circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktscene.h
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktframe.h:41: circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktsvgitem.h
> /«BUILDDIR»/tupi-0.1+git12/src/components/animation/ktviewcamera.h:43: 
> circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/components/animation/ktcamerastatus.h
> lupdate warning: TS files from command line prevent recursing into 
> /«BUILDDIR»/tupi-0.1+git12/src/shell/shell.pro.
> lrelease src/shell/data/translations/tupi_cs.ts
> Updating 'src/shell/data/translations/tupi_cs.qm'...
> Generated 509 translation(s) (433 finished and 76 unfinished)
> Ignored 177 untranslated source text(s)
> # rebuild translations
> lupdate tupi.pro -locations none -silent -ts 
> src/shell/data/translations/tupi_de.ts
> /usr/include/qt4/QtCore/qbytearray.h:618: circular inclusion of 
> /usr/include/qt4/QtCore/qstring.h
> /usr/include/qt4/QtCore/qstringbuilder.h:45: circular inclusion of 
> /usr/include/qt4/QtCore/qstring.h
> /usr/include/qt4/QtGui/qwmatrix.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qmatrix.h
> /usr/include/qt4/QtGui/qboxlayout.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qlayout.h
> /usr/include/qt4/QtGui/qgridlayout.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qlayout.h
> /usr/include/qt4/QtGui/qactiongroup.h:45: circular inclusion of 
> /usr/include/qt4/QtGui/qaction.h
> /«BUILDDIR»/tupi-0.1+git12/src/framework/tgui/kdatetable.cpp:77: Class 'Day' 
> lacks Q_OBJECT macro
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktbackground.h:41: circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktscene.h
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktframe.h:41: circular inclusion of 
> /«BUILDDIR»/tupi-0.1+git12/src/store/ktsvgitem.h
> /«BUILDDIR»/tupi-0.1+git12/src/co

Bug#676120: treil: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: treil
Version: 1.8-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/ruby'
> mkdir -p x86_64-linux && cd x86_64-linux && /usr/bin/ruby ../extconf.rb && 
> /usr/bin/make LIBS='-lruby1.8 -ltreil'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from ../extconf.rb:17:in `'
> make[3]: *** [stamp-arch] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/treil_1.8-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676119: elinks: FTBFS: configure: error: Ruby not found

[Lucas Nussbaum]

Source: elinks
Version: 0.12~pre5-7
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> mkdir -p debian/patched
> for pfile in debian/patches/*.diff; do \
>   [ -f "$pfile" ] || continue; \
>   pname="$(basename $pfile .diff)"; \
>   [ ! -f "debian/patched/$pname.patched" ] || continue; \
>   echo "### Applying patch $pname"; \
>   patch -p1 -N < $pfile; \
>   cp -f "$pfile" "debian/patched/$pname.patched"; \
>   done
> ### Applying patch 01_setup-bugs-FSSTND
> patching file doc/elinks.1.txt
> patching file doc/html/elinks.conf.5.html
> patching file doc/man/man5/elinks.conf.5
> patching file src/document/html/parser/general.c
> patching file src/setup.h
> ### Applying patch 03_459467_ui.leds.enable_0
> patching file doc/html/elinks.conf.5.html
> patching file doc/man/man5/elinks.conf.5
> patching file src/bfu/leds.c
> ### Applying patch 04_436817_nostrip
> patching file Makefile.lib
> ### Applying patch 05_skip-xmlto-validation
> patching file doc/Makefile
> ### Applying patch 07-big-endian-64-bit
> patching file src/bfu/leds.c
> patching file src/bookmarks/bookmarks.c
> patching file src/config/cmdline.c
> patching file src/config/conf.c
> patching file src/config/dialogs.c
> patching file src/config/options.c
> patching file src/config/options.h
> patching file src/config/opttypes.c
> patching file src/cookies/cookies.c
> patching file src/dialogs/menu.c
> patching file src/dialogs/options.c
> patching file src/globhist/globhist.c
> patching file src/mime/backend/default.c
> patching file src/mime/backend/mailcap.c
> patching file src/mime/backend/mimetypes.c
> patching file src/mime/dialogs.c
> patching file src/mime/mime.c
> patching file src/protocol/nntp/nntp.c
> patching file src/protocol/rewrite/rewrite.c
> patching file src/protocol/user.c
> patching file src/scripting/lua/core.c
> patching file src/session/session.c
> patching file src/terminal/screen.c
> patching file src/viewer/text/search.c
> ### Applying patch 07_617713_cache_control
> patching file src/config/options.inc
> ### Applying patch 08-drop-deprecated-gnutls-functions
> patching file src/network/ssl/socket.c
> patching file src/network/ssl/ssl.c
> touch patch-stamp
> dh_testdir
> rm -f debian/elinks.conf
> cat debian/elinks.config | sed "s/%v/`dpkg-parsechangelog -ldebian/changelog 
> | grep 'Version: ' | sed 's/Version: //g'`/g" > debian/elinks.conf
> rm -f debian/elinks-lite.conf
> cat debian/elinks.config | sed "s/%v/`dpkg-parsechangelog -ldebian/changelog 
> | grep 'Version: ' | sed 's/Version: //g'`-lite/g" > debian/elinks-lite.conf
> # Add here commands to configure the package.
> [ ! -f config/config.sub ] || mv -f config/config.sub config/config.sub.ups
> cp -f /usr/share/misc/config.sub config/config.sub
> [ ! -f config/config.guess ] || mv -f config/config.guess 
> config/config.guess.ups
> cp -f /usr/share/misc/config.guess config/config.guess
> [ ! -f config.h ] || mv -f config.h config.h.ups
> [ ! -f Makefile.config ] || mv -f Makefile.config Makefile.config.ups
> [ ! -f doc/man/man1/elinks.1.in ] || cp -af doc/man/man1/elinks.1.in 
> doc/man/man1/elinks.1.in.ups
> [ ! -f doc/man/man5/elinks.conf.5 ] || cp -af doc/man/man5/elinks.conf.5 
> doc/man/man5/elinks.conf.5.ups
> [ ! -f doc/man/man5/elinkskeys.5 ] || cp -af doc/man/man5/elinkskeys.5 
> doc/man/man5/elinkskeys.5.ups
> touch save-stamp
> mkdir /«PKGBUILDDIR»/build-main && cd /«PKGBUILDDIR»/build-main && \
>   /«PKGBUILDDIR»/configure --host=x86_64-linux-gnu 
> --build=x86_64-linux-gnu \
>   --prefix=/usr --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc/elinks --without-lzma 
> --without-openssl --without-x --enable-finger --with-gnutls=/usr 
> --disable-nntp --enable-88-colors --enable-256-colors --enable-leds 
> --enable-html-highlight --enable-fsp --disable-smb --with-perl 
> --without-guile --without-python --with-ruby --with-gssapi --enable-cgi 
> --disable-exmode --disable-bittorrent --disable-debug --without-spidermonkey 
> CPPFLAGS="`dpkg-buildflags --get CPPFLAGS`" CFLAGS="-g `dpkg-buildflags --get 
> CFLAGS` -O2" LDFLAGS=""-Wl,-z,defs" `dpkg-buildflags --get LDFLAGS`"
> checking for aclocal... config/missing acloca

Bug#676118: sgml-base-doc: FTBFS: nsgmls:sgml_layout.sgml:1:26:E: reference to entity "DEBIANDOC" for which no system identifier could be generated

[Lucas Nussbaum]

Source: sgml-base-doc
Version: 1.99.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> nsgmls -wall -E20 -gues sgml_layout.sgml
> nsgmls:sgml_layout.sgml:1:26:W: cannot generate system identifier for 
> document type "DEBIANDOC"
> nsgmls:sgml_layout.sgml:1:26:E: reference to entity "DEBIANDOC" for which no 
> system identifier could be generated
> nsgmls:sgml_layout.sgml:1:0: entity was defined here
> nsgmls:sgml_layout.sgml:1:26:E: DTD did not contain element declaration for 
> document type name
> nsgmls:sgml_layout.sgml:3:10:E: element "DEBIANDOC" undefined
> nsgmls:sgml_layout.sgml:5:7:E: element "BOOK" undefined
> nsgmls:sgml_layout.sgml:5:7: open elements: DEBIANDOC
> nsgmls:sgml_layout.sgml:7:13:E: element "TITLEPAG" undefined
> nsgmls:sgml_layout.sgml:7:13: open elements: DEBIANDOC BOOK
> nsgmls:sgml_layout.sgml:8:12:E: element "TITLE" undefined
> nsgmls:sgml_layout.sgml:8:12: open elements: DEBIANDOC BOOK TITLEPAG
> nsgmls:sgml_layout.sgml:9:13:E: element "AUTHOR" undefined
> nsgmls:sgml_layout.sgml:9:13: open elements: DEBIANDOC BOOK TITLEPAG
> nsgmls:sgml_layout.sgml:10:6:E: element "NAME" undefined
> nsgmls:sgml_layout.sgml:10:6: open elements: DEBIANDOC BOOK TITLEPAG AUTHOR
> nsgmls:sgml_layout.sgml:11:7:E: element "EMAIL" undefined
> nsgmls:sgml_layout.sgml:11:7: open elements: DEBIANDOC BOOK TITLEPAG AUTHOR
> nsgmls:sgml_layout.sgml:13:14:E: element "VERSION" undefined
> nsgmls:sgml_layout.sgml:13:14: open elements: DEBIANDOC BOOK TITLEPAG
> nsgmls:sgml_layout.sgml:13:20:E: element "DATE" undefined
> nsgmls:sgml_layout.sgml:13:20: open elements: DEBIANDOC BOOK TITLEPAG VERSION
> nsgmls:sgml_layout.sgml:13:30:E: end tag for "DATE" omitted, but its 
> declaration does not permit this
> nsgmls:sgml_layout.sgml:13:15: start tag was here
> nsgmls:sgml_layout.sgml:13:30: open elements: DEBIANDOC BOOK TITLEPAG VERSION 
> DATE
> nsgmls:sgml_layout.sgml:14:15:E: element "ABSTRACT" undefined
> nsgmls:sgml_layout.sgml:14:15: open elements: DEBIANDOC BOOK TITLEPAG
> nsgmls:sgml_layout.sgml:17:41:E: element "EM" undefined
> nsgmls:sgml_layout.sgml:17:41: open elements: DEBIANDOC BOOK TITLEPAG ABSTRACT
> nsgmls:sgml_layout.sgml:18:26:E: element "EM" undefined
> nsgmls:sgml_layout.sgml:18:26: open elements: DEBIANDOC BOOK TITLEPAG ABSTRACT
> nsgmls:sgml_layout.sgml:19:43:E: element "TT" undefined
> nsgmls:sgml_layout.sgml:19:43: open elements: DEBIANDOC BOOK TITLEPAG ABSTRACT
> nsgmls:sgml_layout.sgml:23:16:E: element "COPYRIGHT" undefined
> nsgmls:sgml_layout.sgml:23:16: open elements: DEBIANDOC BOOK TITLEPAG
> nsgmls:sgml_layout.sgml:24:18:E: element "COPYRIGHTSUMMARY" undefined
> nsgmls:sgml_layout.sgml:24:18: open elements: DEBIANDOC BOOK TITLEPAG 
> COPYRIGHT
> nsgmls:sgml_layout.sgml:24:30:E: general entity "copy" not defined and no 
> default entity
> nsgmls:sgml_layout.sgml:24:30: open elements: DEBIANDOC BOOK TITLEPAG 
> COPYRIGHT COPYRIGHTSUMMARY
> nsgmls:sgml_layout.sgml:27:3:E: element "P" undefined
> nsgmls:sgml_layout.sgml:27:3: open elements: DEBIANDOC BOOK TITLEPAG COPYRIGHT
> nsgmls:I: maximum number of errors (20) reached; change with -E option
> make: *** [check-stamp] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/sgml-base-doc_1.99.1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676117: mustache.js: FTBFS: invalid byte sequence in US-ASCII

[Lucas Nussbaum]

Source: mustache.js
Version: 0.4.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> rake commonjs
> mkdir -p lib
> cat wrappers/commonjs/mustache.js.tpl.pre mustache.js   
> wrappers/commonjs/mustache.js.tpl.post > lib/mustache.js
> Packaging for CommonJS
> rake aborted!
> invalid byte sequence in US-ASCII
> 
> Tasks: TOP => commonjs
> (See full trace by running task with --trace)
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/mustache.js_0.4.2-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676116: mlpost: FTBFS: Command exited with code 1.

[Lucas Nussbaum]

Source: mlpost
Version: 0.8.1-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»'
> rm -f doc
> /usr/bin/ocamlbuild  -no-links -tag dtypes -tags cairo_yes,concrete_yes  
> -classic-display -log "build.log" doc/index.html
> cp mlpost_yeslablgtk.odocl mlpost.odocl
> /usr/bin/ocamldep -modules customdoc/img.ml > customdoc/img.ml.depends
> /usr/bin/ocamlc -c -I +ocamldoc -I +ocamldoc -dtypes -I customdoc -I gui -I 
> concrete -I backend -I dvi -o customdoc/img.cmo customdoc/img.ml
> cp contrib/dot/mlpost_dot.mli mlpost_dot.mli
> /usr/bin/ocamldep -modules mlpost_dot.mli > mlpost_dot.mli.depends
> cp contrib/lablgtk/mlpost_lablgtk.mli mlpost_lablgtk.mli
> /usr/bin/ocamldep -modules mlpost_lablgtk.mli > mlpost_lablgtk.mli.depends
> /usr/bin/ocamldoc -dump mlpost.odoc -hide Mlpost -g customdoc/img.cmo -I 
> /usr/lib/ocaml/lablgtk2 -I /usr/lib/ocaml/cairo -I /usr/lib/ocaml/cairo -pp 
> './myocamlmacroparser.byte  -D CAIRO -D CONCRETE' -I gui -I concrete -I 
> backend -I dvi mlpost.mli
> /usr/bin/ocamldoc -dump mlpost_dot.odoc -hide Mlpost -g customdoc/img.cmo -I 
> /usr/lib/ocaml/lablgtk2 -I gui -I concrete -I backend -I dvi mlpost_dot.mli
> /usr/bin/ocamldoc -dump mlpost_lablgtk.odoc -hide Mlpost -g customdoc/img.cmo 
> -I /usr/lib/ocaml/lablgtk2 -I gui -I concrete -I backend -I dvi 
> mlpost_lablgtk.mli
> + /usr/bin/ocamldoc -dump mlpost_lablgtk.odoc -hide Mlpost -g 
> customdoc/img.cmo -I /usr/lib/ocaml/lablgtk2 -I gui -I concrete -I backend -I 
> dvi mlpost_lablgtk.mli
> Warning: Class or class type GObj.widget not found
> rm -rf mlpost.docdir
> mkdir -p mlpost.docdir
> /usr/bin/ocamldoc -load mlpost.odoc -load mlpost_dot.odoc -load 
> mlpost_lablgtk.odoc -hide Mlpost -g customdoc/img.cmo -I 
> /usr/lib/ocaml/lablgtk2 -html -d mlpost.docdir
> + /usr/bin/ocamldoc -load mlpost.odoc -load mlpost_dot.odoc -load 
> mlpost_lablgtk.odoc -hide Mlpost -g customdoc/img.cmo -I 
> /usr/lib/ocaml/lablgtk2 -html -d mlpost.docdir
> Warning: Class or class type GObj.widget not found
> /usr/bin/ocamldep -modules customdoc/img_doc.ml > customdoc/img_doc.ml.depends
> /usr/bin/ocamlc -c -dtypes -I /usr/lib/ocaml/cairo -I 
> /usr/lib/ocaml/bitstring -I customdoc -I gui -I concrete -I backend -I dvi -o 
> customdoc/img_doc.cmo customdoc/img_doc.ml
> /usr/bin/ocamlc unix.cma bigarray.cma -I /usr/lib/ocaml/cairo cairo.cma -I 
> /usr/lib/ocaml/bitstring bitstring.cma dvi/dvi_util.cmo name.cmo 
> scan_prelude.cmo mlpost.cmo customdoc/img_doc.cmo -o customdoc/img_doc.byte
> 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[2]: *** [doc] Error 10

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/mlpost_0.8.1-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676115: autogen: FTBFS: make[2]: *** No rule to make target `invoke-xml2ag.texi'. Stop.

[Lucas Nussbaum]

Source: autogen
Version: 1:5.12-0.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/xml2ag'
> make[2]: *** No rule to make target `invoke-xml2ag.texi'.  Stop.
> make[2]: Leaving directory `/«PKGBUILDDIR»/xml2ag'
> leaving /«PKGBUILDDIR»/doc/ag-texi-19484.d in place
> make[1]: *** [agdoc.texi] Terminated
> make[1]: Leaving directory `/«PKGBUILDDIR»/doc'
> make: *** [build-stamp] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/autogen_5.12-0.1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676114: wordnet: FTBFS: debian/wn-for-goldendict.rb:465: invalid multibyte char (US-ASCII)

[Lucas Nussbaum]

Source: wordnet
Version: 1:3.0-27
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»'
> make[3]: Leaving directory `/«PKGBUILDDIR»'
> make[2]: Leaving directory `/«PKGBUILDDIR»'
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> touch debian/stamp-makefile-build
> DEB_MAKE_CHECK_TARGET unset, not running checks
> set -e; \
>   if dpkg-architecture -qDEB_BUILD_ARCH|grep -q 'mips\|arm\|s390'; then \
>   if test "$FORCE_GOLDENDICT_BUILD" -gt 0; then \
>   ruby debian/wn-for-goldendict.rb > 
> goldendict-wordnet.dsl; \
>   else \
>   echo "Building of goldendict-wordnet dictionary was 
> skipped"; \
>   echo "to build this package use environment variable"; \
>   echo "FORCE_GOLDENDICT_BUILD=1" ; \
>   touch goldendict-wordnet.dsl; \
>   fi; \
>   else \
>   ruby debian/wn-for-goldendict.rb > goldendict-wordnet.dsl; \
>   fi
> debian/wn-for-goldendict.rb:465: invalid multibyte char (US-ASCII)
> debian/wn-for-goldendict.rb:465: invalid multibyte char (US-ASCII)
> debian/wn-for-goldendict.rb:465: syntax error, unexpected $end, expecting ')'
> print_array(@words, 'Syn', "[c blue]•[/c]")
>   ^
> make: *** [goldendict-wordnet.dsl] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/wordnet_3.0-27_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676113: langscan: FTBFS: /usr/bin/install: cannot stat `./c.': No such file or directory

[Lucas Nussbaum]

Source: langscan
Version: 1.2+cvs20070125-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[5]: Entering directory `/«BUILDDIR»/langscan-1.2+cvs20070125/langscan/c'
> make[5]: Nothing to be done for `install-exec-am'.
> I. -I -c c.c
> /bin/bash: I.: command not found
> make[5]: [c.o] Error 127 (ignored)
> I. -I -c ctok.c
> /bin/bash: I.: command not found
> make[5]: [ctok.o] Error 127 (ignored)
> rm -f c.
> o c. c.o ctok.o 
> /bin/bash: o: command not found
> make[5]: [c.] Error 127 (ignored)
>  /bin/mkdir -p 
> '/«BUILDDIR»/langscan-1.2+cvs20070125/debian/liblangscan-ruby/usr/lib/ruby/1.9.1/x86_64-linux/langscan/c'
>  /usr/bin/install -c -m 644 ./c. 
> '/«BUILDDIR»/langscan-1.2+cvs20070125/debian/liblangscan-ruby/usr/lib/ruby/1.9.1/x86_64-linux/langscan/c'
> /usr/bin/install: cannot stat `./c.': No such file or directory
> make[5]: *** [install-rubyarchlibDATA] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/langscan_1.2+cvs20070125-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676112: quantlib-swig: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: quantlib-swig
Version: 1.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> *** Running on arch amd64 and cpu x86_64
> ./configure   --prefix=/usr   \
>   --build amd64
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking system... Linux
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... none
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... none
> checking whether g++ accepts warning flags... yes
> checking for QuantLib... 1.2
> checking for swig... no
> checking for python... /usr/bin/python
> checking for perl... /usr/bin/perl
> checking for ruby... /usr/bin/ruby
> checking for mzscheme... no
> checking for guile... no
> checking for gmcs... no
> checking for mcs... no
> checking for gmcs2... no
> checking for ocamlc... no
> checking for R... no
> checking for javac... no
> checking for jar... no
> checking for java... no
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating CSharp/Makefile
> config.status: creating Guile/Makefile
> config.status: creating Java/Makefile
> config.status: creating MzScheme/Makefile
> config.status: creating OCaml/Makefile
> config.status: creating Perl/Makefile
> config.status: creating Python/Makefile
> config.status: creating R/Makefile
> config.status: creating Ruby/Makefile
> config.status: executing depfiles commands
> (cd Python && \
>   CC="g++"\
>   CXX="g++"   \
>   CFLAGS="-O2 -Wall -Wno-strict-aliasing" 
> \
>   CXXFLAGS="-O2 -Wall -Wno-strict-aliasing"   
> \
>   python2.7 setup.py build)
> running build
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/QuantLib
> copying QuantLib/__init__.py -> build/lib.linux-x86_64-2.7/QuantLib
> copying QuantLib/QuantLib.py -> build/lib.linux-x86_64-2.7/QuantLib
> running build_ext
> building 'QuantLib._QuantLib' extension
> creating build/temp.linux-x86_64-2.7
> creating build/temp.linux-x86_64-2.7/QuantLib
> g++ -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
> -O2 -Wall -Wno-strict-aliasing -fPIC -I/usr/include/python2.7 -I/usr/include 
> -c QuantLib/quantlib_wrap.cpp -o 
> build/temp.linux-x86_64-2.7/QuantLib/quantlib_wrap.o -Wno-unused -O2 -Wall 
> -Wno-strict-aliasing
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++ [enabled by default]
> QuantLib/quantlib_wrap.cpp: In member function 'QuantLib::Real 
> UnaryFunction::operator()(QuantLib::Real) const':
> QuantLib/quantlib_wrap.cpp:6833:67: warning: deprecated conversion from 
> string constant to 'char*' [-Wwrite-strings]
> QuantLib/quantlib_wrap.cpp: In member function 'QuantLib::Real 
> UnaryFunction::derivative(QuantLib::Real) const':
> QuantLib/quantlib_wrap.cpp:6841:61: warning: deprecated conversion from 
> string constant to 'char*' [-Wwrite-strings]
> QuantLib/quantlib_wrap.cpp:6841:61: warning: deprecated conversion from 
> string constant to 'char*' [-Wwrite-strings]
> QuantLib/quantlib_wrap.cpp: In member function 'QuantLib::Real 
> BinaryFunction::operator()(QuantLib::Real, QuantLib::Real) const':
> QuantLib/quantlib_wrap.cpp:6873:70: warning: deprecated conversion from 
> string constant to 'char

Bug#676111: jblas: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- config/path (LoadError)

[Lucas Nussbaum]

Source: jblas
Version: 1.2.0-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> ./configure --libpath=/usr/lib:/usr/lib/atlas
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- config/path (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from config/configure.rb:35:in `'
> make: *** [debian/stamp-jblas-build] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/jblas_1.2.0-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676110: rhash: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: rhash
Version: 1.2.9-5
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/bindings/perl'
> cp Rhash.pm blib/lib/Rhash.pm
> /usr/bin/perl /usr/share/perl/5.14/ExtUtils/xsubpp  -typemap 
> /usr/share/perl/5.14/ExtUtils/typemap -typemap typemap  Rhash.xs > Rhash.xsc 
> && mv Rhash.xsc Rhash.c
> cc -c  -I/«PKGBUILDDIR»/debian/tmp -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
> -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -Wall   -DVERSION=\"0.01\" 
> -DXS_VERSION=\"0.01\" -fPIC "-I/usr/lib/perl/5.14/CORE"   Rhash.c
> Running Mkbootstrap for Rhash ()
> chmod 644 Rhash.bs
> rm -f blib/arch/auto/Rhash/Rhash.so
> LD_RUN_PATH="/«PKGBUILDDIR»/debian/tmp" cc  -shared -L/usr/local/lib 
> -fstack-protector Rhash.o  -o blib/arch/auto/Rhash/Rhash.so  \
>  -L/«PKGBUILDDIR»/debian/tmp -lrhash  \
> 
> chmod 755 blib/arch/auto/Rhash/Rhash.so
> cp Rhash.bs blib/arch/auto/Rhash/Rhash.bs
> chmod 644 blib/arch/auto/Rhash/Rhash.bs
> Manifying blib/man3/Rhash.3pm
> make[2]: Leaving directory `/«PKGBUILDDIR»/bindings/perl'
> ruby -C ruby extconf.rb
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from extconf.rb:1:in `'
> make[1]: *** [ruby/Makefile] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/rhash_1.2.9-5_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676109: zonecheck: FTBFS: installer.rb:183:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError)

[Lucas Nussbaum]

Source: zonecheck
Version: 3.0.3-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> dh_testdir
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs
> # Add here commands to install the package into debian/zonecheck.
> /usr/bin/ruby installer.rb -DCHROOT=/«PKGBUILDDIR»/debian/zonecheck \
>   -DPREFIX=/usr -DETCDIR=/etc -DETCDIST= \
>   -DLIBEXEC=/usr/share -DMANDIR=/usr/share/man 
> -DRUBY=/usr/bin/ruby \
>   common cli doc
> mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck
> cp -r zc /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck
> chmod 755 /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck/zc/zc.rb
> cp -r lib /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck
> cp -r test /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck
> cp -r locale /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck
> mkdir -p /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck
> cp etc/zonecheck/zc.conf /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck
> cp etc/zonecheck/rootservers /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck
> cp etc/zonecheck/default.profile etc/zonecheck/afnic.profile 
> etc/zonecheck/reverse.profile etc/zonecheck/de.profile 
> /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck
> chmod 755 /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck/zc/zc.rb
> mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/bin
> ln -sf /usr/share/zonecheck/zc/zc.rb 
> /«PKGBUILDDIR»/debian/zonecheck/usr/bin/zonecheck
> mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/share/man/man1
> install -c -m 0644 man/zonecheck.1 
> /«PKGBUILDDIR»/debian/zonecheck/usr/share/man/man1/zonecheck.1
> mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/share/doc/zonecheck
> install -c -m 0644 README TODO BUGS HISTORY CREDITS 
> /«PKGBUILDDIR»/debian/zonecheck/usr/share/doc/zonecheck
> ==> Installing core components
> 
> ==> Installing libraries
> 
> ==> Installing tests
> 
> ==> Installing locale
> 
> ==> Installing default configuration file
> 
> ==> Patching core components
> 
> ==> Installing CLI
> 
> ==> Installing documentation
> 
> ==> Info
> 
> !!! Before using ZoneCheck, please edit the file: zc.conf
> 
> # Patch the configuration file for Linux netkit ping
> /usr/bin/ruby -p -i \
>   -e 
> "\$_.gsub"\!"(/()/,
>  '\1ping  -n -q -w 5 -c 5 %s > /dev/null\2')" \
>   -e 
> "\$_.gsub"\!"(/()/,
>  '\1ping6 -n -q -w 5 -c 5 %s > /dev/null\2')" \
>   /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck/zc.conf
> # Add here commands to install the package into debian/zonecheck-cgi.
> /usr/bin/ruby installer.rb -DCHROOT=/«PKGBUILDDIR»/debian/zonecheck-cgi \
>-DPREFIX=/usr -DETCDIR=/etc -DETCDIST= \
>  -DCGIDIR=/usr/lib/cgi-bin/ -DLIBEXEC=/usr/share \
>  -DMANDIR=/usr/share/man -DWWWDIR=/usr/share/zonecheck-cgi \
>-DWWWCGIDIR=/cgi-bin -DRUBY=/usr/bin/ruby \
>   cgi
> mkdir -p /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi
> cp -r www/zonecheck.conf.in 
> /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi
> cp -r www/img /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi
> cp -r www/style /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi
> cp -r www/html /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi
> cp -r www/js /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi
> mkdir -p /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/lib/cgi-bin/
> ln -sf /usr/share/zonecheck/zc/zc.rb 
> /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/lib/cgi-bin//zc.cgi
> installer.rb:183:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError)
>   from installer.rb:183:in `block (2 levels) in patch_cgi'
>   from installer.rb:182:in `each'
>   from installer.rb:182:in `block in patch_cgi'
>   from installer.rb:180:in `each'
>   from installer.rb:180:in `patch_cgi'
>   from installer.rb:242:in `rule_cgi'
>   from installer.rb:287:in `block in '
>   from installer.rb:286:in `each'
>   from installer.rb:286:in `'
> ==> Installing HTML pages
> 
> ==> Installing CGI
> 
> ==> Patching HTML pages
> make: *** [install] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04

Bug#676108: migemo: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': /usr/lib/ruby/vendor_ruby/romkan.rb:29: invalid multibyte char (US-ASCII) (SyntaxError)

[Lucas Nussbaum]

Source: migemo
Version: 0.40-10
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> # Add here commands to configure the package.
> ln -sf /usr/share/automake/config.guess .
> ln -sf /usr/share/automake/config.sub .
> RUBY=/usr/bin/ruby ./configure --prefix=/usr
> creating cache ./config.cache
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... missing
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... missing
> checking for working makeinfo... missing
> checking for ruby... /usr/bin/ruby
> checking for emacs... /usr/bin/emacs
> checking where emacs files are in... /usr/share/emacs
> checking where .elc files should go... /usr/share/emacs/site-lisp
> checking where emacs files are in... 
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> checking where .rb files should go... /usr/local/lib/site_ruby
> checking Ruby/Bsearch... found
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': 
> /usr/lib/ruby/vendor_ruby/romkan.rb:29: invalid multibyte char (US-ASCII) 
> (SyntaxError)
> /usr/lib/ruby/vendor_ruby/romkan.rb:28: invalid multibyte char (US-ASCII)
> /usr/lib/ruby/vendor_ruby/romkan.rb:28: syntax error, unexpected $end, 
> expecting keyword_end
> ��xa  ��  a   ��  xi  ��  i   ��  xu
>   ^
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> checking Ruby/Romkan... not found
> Ruby/Romkan is available at <http://namazu.org/~satoru/ruby-romkan/>
> make: *** [configure-stamp] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/migemo_0.40-10_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676107: debian-faq: FTBFS: nsgmls:0:6:0:E: reference to entity "DEBIANDOC" for which no system identifier could be generated

[Lucas Nussbaum]

Source: debian-faq
Version: 5.0
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> echo "" > faqdynamic.ent
> if [ -f debian/changelog ]; then \
>   echo " '^Version: ' | sed 's/^Version: *//'`\">" >> faqdynamic.ent; \
> else \
>   echo "" >> faqdynamic.ent; \
> fi
> po4a --keep 0 --previous --rm-backups po4a/po4a.cfg # --localized-charset 
> UTF-8
> nsgmls:0:3:61:W: cannot generate system identifier for public text 
> "-//DebianDoc//DTD DebianDoc//EN"
> nsgmls:0:6:0:E: reference to entity "DEBIANDOC" for which no system 
> identifier could be generated
> nsgmls:0:3:0: entity was defined here
> nsgmls:0:6:0:E: DTD did not contain element declaration for document 
> type name
> po4a::sgml: Error while running nsgmls -p.  Please check if nsgmls and the 
> DTD are installed.
> make[1]: *** [po4a-translate] Error 25

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/debian-faq_5.0_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676106: gonzui: FTBFS: configure: error: langscan for ruby not found

[Lucas Nussbaum]

Source: gonzui
Version: 1.2+cvs20070129-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> dh_testdir
> # Add here commands to configure the package.
> ./autogen.sh \
>   --host=x86_64-linux-gnu --build=x86_64-linux-gnu \
>   --prefix=/usr --mandir=\${prefix}/share/man \
>   --infodir=\${prefix}/share/info --sysconfdir=/etc \
>   --localstatedir=/var/spool CFLAGS="-Wall -g -O2" \
>   --with-rubydir=/usr/lib/ruby/1.9.1 
> --with-rubyarchdir=/usr/lib/ruby/1.9.1/x86_64-linux
> Generating configure script and Makefiles for gonzui.
> Running aclocal ...
> Running automake ...
> configure.ac:2: installing `./install-sh'
> configure.ac:2: installing `./missing'
> Makefile.am: installing `./INSTALL'
> Makefile.am: installing `./COPYING' using GNU General Public License v3 file
> Makefile.am: Consider adding the COPYING file to the version control 
> system
> Makefile.am: for your code, to avoid questions about which license your 
> project uses.
> Running autoconf ...
> Configuring gonzui.
> Running ./configure --enable-maintainer-mode --host=x86_64-linux-gnu 
> --build=x86_64-linux-gnu --prefix=/usr --mandir=${prefix}/share/man 
> --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var/spool 
> CFLAGS=-Wall -g -O2 --with-rubydir=/usr/lib/ruby/1.9.1 
> --with-rubyarchdir=/usr/lib/ruby/1.9.1/x86_64-linux ...
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking 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... none
> checking whether make sets $(MAKE)... (cached) yes
> checking whether to enable maintainer-specific portions of Makefiles... yes
> checking for ruby... /usr/bin/ruby
> checking ruby version.. 1.9.3 found
> checking path to ruby library... /usr/lib/ruby/1.9.1
> checking path to ruby binary library... /usr/lib/ruby/1.9.1/x86_64-linux
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
> configure: error: langscan for ruby not found
> checking langscan for ruby.. not found
> langscan is available at <http://gonzui.sourceforge.net/langscan/>
> Now type 'make' to compile gonzui.
> touch configure-stamp
> dh_testdir
> # Add here commands to compile the package.
> /usr/bin/make
> make[1]: Entering directory `/«BUILDDIR»/gonzui-1.2+cvs

Bug#676105: rbbr: FTBFS: L10n is not supported on this environment.

[Lucas Nussbaum]

Source: rbbr
Version: 0.6.0-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> dh_testdir
> ruby install.rb config --prefix=/usr --site-ruby=/usr/lib/ruby/1.9.1
> install.rb:78: Use RbConfig instead of obsolete and deprecated Config.
> install.rb: entering config phase...
> ---> bin
> <--- bin
> ---> lib
> ---> lib/rbbr
> ---> lib/rbbr/ui
> ---> lib/rbbr/ui/gtk
> <--- lib/rbbr/ui/gtk
> <--- lib/rbbr/ui
> ---> lib/rbbr/doc
> <--- lib/rbbr/doc
> <--- lib/rbbr
> <--- lib
> ---> data
> ---> data/rbbr
> ---> data/rbbr/rd
> <--- data/rbbr/rd
> <--- data/rbbr
> <--- data
> install.rb: config done.
> ruby install.rb setup
> install.rb:78: Use RbConfig instead of obsolete and deprecated Config.
> install.rb: entering setup phase...
> L10n is not supported on this environment.
> make: *** [build-stamp] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/rbbr_0.6.0-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676104: liblastfm: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- admin/findsrc (LoadError)

[Lucas Nussbaum]

Source: liblastfm
Version: 0.4.0~git20090710-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> ./configure --release --prefix /usr --no-strip
> ==> Configuring liblastfm-0.4.0... 
> Using /usr/bin/qmake
> ==> Determining installation prefix 
> Will install to: /usr
> ==> Generating Build System 
> ==> Generating .qmake.env 
> ==> Running qpp... 
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- admin/findsrc (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from admin/qpp:7:in `'
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- admin/findsrc (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from admin/qpp:7:in `'
> ==> Configuring qmake... 
> ==> Generating Makefile... 
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- admin/platform.rb (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from admin/Makefile.rb:9:in `'
> 
> Good, your configure is finished! Now type: make
> touch config-stamp
> dh_testdir
> # Add here commands to compile the package.
> /usr/bin/make headers __src __fingerprint
> make[1]: Entering directory `/«PKGBUILDDIR»'
> make[1]: *** No rule to make target `headers'.  Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> make: *** [build-stamp] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/liblastfm_0.4.0~git20090710-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676103: sbcl: FTBFS: tests failed

[Lucas Nussbaum]

Source: sbcl
Version: 2:1.0.57.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory `/«PKGBUILDDIR»/contrib/asdf'
> make[2]: `asdf.fasl' is up to date.
> make[2]: Leaving directory `/«PKGBUILDDIR»/contrib/asdf'
> /«PKGBUILDDIR»/src/runtime/sbcl --noinform --core 
> /«PKGBUILDDIR»/output/sbcl.core --lose-on-corruption --disable-debugger 
> --no-sysinit --no-userinit --eval '(defvar *system* "sb-bsd-sockets")' --load 
> ../asdf-stub.lisp --eval '(exit)'
> STYLE-WARNING: Couldn't grovel for EAI_ADDRFAMILY (unknown to the C compiler).
> 
> ; compiling file "/«PKGBUILDDIR»/contrib/sb-bsd-sockets/sb-bsd-sockets.lisp" 
> (written 04 JUN 2012 04:17:42 PM):
> ; compiling (UNLESS (MEMBER "ASDF" ...) ...)
> ; compiling (LET (#) ...)
> 
> ; /«PKGBUILDDIR»/contrib/sb-bsd-sockets/sb-bsd-sockets.fasl written
> ; compilation finished in 0:00:00.004
> echo "(asdf:operate (quote asdf:load-op) :sb-bsd-sockets)" \
>"(asdf:operate (quote asdf:test-op) :sb-bsd-sockets)" | \
> /«PKGBUILDDIR»/src/runtime/sbcl --noinform --core 
> /«PKGBUILDDIR»/output/sbcl.core --lose-on-corruption --disable-debugger 
> --no-sysinit --no-userinit --eval '(load "../asdf/asdf")'
> * STYLE-WARNING: Couldn't grovel for EAI_ADDRFAMILY (unknown to the C 
> compiler).
> 
> #
> ((#
>   . #)
>  (#
>   . #)
>  (#
>   . #)
>  (#
>   . #)
>  (#
>   . #)
>  (#
>   . #)
>  (#
>   . #)
>  (#
>   . #)
>  (#
>   . #)
>  (# . #))
> * STYLE-WARNING: Couldn't grovel for SIGEMT (unknown to the C compiler).
> STYLE-WARNING: Couldn't grovel for S_IFWHT (unknown to the C compiler).
> STYLE-WARNING: Couldn't grovel for O_DIRECT (unknown to the C compiler).
> 
> ; compiling file "/«PKGBUILDDIR»/contrib/sb-bsd-sockets/tests.lisp" (written 
> 20 MAY 2012 06:55:39 PM):
> ; compiling (DEFPACKAGE "SB-BSD-SOCKETS-TEST" ...)
> ; compiling (IN-PACKAGE :SB-BSD-SOCKETS-TEST)
> ; compiling (DEFTEST MAKE-INET-ADDRESS ...)
> ; compiling (DEFTEST MAKE-INET-ADDRESS2 ...)
> ; compiling (DEFTEST GET-PROTOCOL-BY-NAME/TCP ...)
> ; compiling (DEFTEST GET-PROTOCOL-BY-NAME/UDP ...)
> ; compiling (DEFTEST GET-PROTOCOL-BY-NAME/ERROR ...)
> ; compiling (DEFTEST MAKE-INET-SOCKET ...)
> ; compiling (DEFTEST MAKE-INET-SOCKET-KEYWORD ...)
> ; compiling (DEFTEST MAKE-INET-SOCKET-WRONG ...)
> ; compiling (DEFTEST MAKE-INET-SOCKET-KEYWORD-WRONG ...)
> ; compiling (DEFTEST NON-BLOCK-SOCKET ...)
> ; compiling (DEFUN DO-GC-PORTABLY ...)
> ; compiling (DEFTEST INET-SOCKET-BIND ...)
> ; compiling (DEFTEST SIMPLE-SOCKOPT-TEST ...)
> ; compiling (DEFUN READ-BUF-NONBLOCK ...)
> ; compiling (DEFTEST SIMPLE-LOCAL-CLIENT ...)
> ; compiling (DEFUN HTTP-STREAM ...)
> ; compiling (DEFTEST SOCKET-OPEN-P-TRUE.1 ...)
> ; compiling (DEFTEST SOCKET-OPEN-P-FALSE ...)
> ; compiling (DEFUN UDP-SERVER ...)
> 
> ; /«PKGBUILDDIR»/contrib/sb-bsd-sockets/ASDF-TMP-tests.fasl written
> ; compilation finished in 0:00:00.030
> Doing 15 pending tests of 15 tests total.
>  SB-BSD-SOCKETS:MAKE-INET-ADDRESS SB-BSD-SOCKETS-TEST::MAKE-INET-ADDRESS2
> Test SB-BSD-SOCKETS-TEST::GET-PROTOCOL-BY-NAME/TCP failed
> Form: (INTEGERP (SB-BSD-SOCKETS:GET-PROTOCOL-BY-NAME "tcp"))
> Expected value: T
> Actual value: #.
> Test SB-BSD-SOCKETS-TEST::GET-PROTOCOL-BY-NAME/UDP failed
> Form: (INTEGERP (SB-BSD-SOCKETS:GET-PROTOCOL-BY-NAME "udp"))
> Expected value: T
> Actual value: #.
> Test SB-BSD-SOCKETS-TEST::GET-PROTOCOL-BY-NAME/ERROR failed
> Form: (HANDLER-CASE
>(SB-BSD-SOCKETS:GET-PROTOCOL-BY-NAME "nonexistent-protocol")
>(SB-BSD-SOCKETS:UNKNOWN-PROTOCOL NIL T) (:NO-ERROR NIL NIL))
> Expected value: T
> Actual value: #.
> Test SB-BSD-SOCKETS:MAKE-INET-SOCKET failed
> Form: (LET ((SB-BSD-SOCKETS-TEST::S
>  (MAKE-INSTANCE 'SB-BSD-SOCKETS:INET-SOCKET :TYPE :STREAM 
> :PROTOCOL
> (SB-BSD-SOCKETS:GET-PROTOCOL-BY-NAME "tcp"
> (AND
>  (> (SB-BSD-SOCKETS:SOCKET-FILE-DESCRIPTOR SB-BSD-SOCKETS-TEST::S) 1)
>  T))
> Expected value: T
> Actual value: #.
> Test SB-BSD-SOCKETS-TEST::MAKE-INET-SOCKET-KEYWORD failed
> Form: (LET ((SB-BSD-SOCKETS-TEST::S
>  (MAKE-INSTANCE 'SB-BSD-SOCKETS:INET-SOCKET :TYPE :STREAM 
> :PROTOCOL
> :TCP)))
> (AND
>  (> (SB-BSD-SOCKETS:SOCKET-FILE-D

Bug#676100: xmms2: FTBFS: dh_install: libxmmsclient-ruby1.8 missing files (usr/lib/ruby/1.8/*), aborting

[Lucas Nussbaum]

Source: xmms2
Version: 0.8+dfsg-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
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 `/«BUILDDIR»/xmms2-0.8+dfsg'
> mv _build_without_python_ _build_ && ./waf install 
> --destdir=/«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp --without-ldconfig && mv 
> _build_ _build_without_python_
> Waf: Entering directory `/«BUILDDIR»/xmms2-0.8+dfsg/_build_'
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_bindata.h 
> (from src/include/xmms/xmms_bindata.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_config.h 
> (from src/include/xmms/xmms_config.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_error.h 
> (from src/include/xmms/xmms_error.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_ipc.h (from 
> src/include/xmms/xmms_ipc.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_log.h (from 
> src/include/xmms/xmms_log.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_medialib.h 
> (from src/include/xmms/xmms_medialib.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_object.h 
> (from src/include/xmms/xmms_object.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_outputplugin.h
>  (from src/include/xmms/xmms_outputplugin.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_plugin.h 
> (from src/include/xmms/xmms_plugin.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_sample.h 
> (from src/include/xmms/xmms_sample.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_streamtype.h
>  (from src/include/xmms/xmms_streamtype.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_util.h 
> (from src/include/xmms/xmms_util.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmms/xmms_xformplugin.h
>  (from src/include/xmms/xmms_xformplugin.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_compiler.h
>  (from src/include/xmmsc/xmmsc_compiler.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_errorcodes.h
>  (from src/include/xmmsc/xmmsc_errorcodes.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_idnumbers.h
>  (from src/include/xmmsc/xmmsc_idnumbers.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_ipc_msg.h 
> (from src/include/xmmsc/xmmsc_ipc_msg.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_ipc_transport.h
>  (from src/include/xmmsc/xmmsc_ipc_transport.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_sockets.h 
> (from src/include/xmmsc/xmmsc_sockets.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_stdbool.h 
> (from src/include/xmmsc/xmmsc_stdbool.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_stdint.h 
> (from src/include/xmmsc/xmmsc_stdint.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_stringport.h
>  (from src/include/xmmsc/xmmsc_stringport.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_strlist.h 
> (from src/include/xmmsc/xmmsc_strlist.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_unistd.h 
> (from src/include/xmmsc/xmmsc_unistd.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_util.h 
> (from src/include/xmmsc/xmmsc_util.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsc_visualization.h
>  (from src/include/xmmsc/xmmsc_visualization.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsv.h (from 
> src/include/xmmsc/xmmsv.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsv_bitbuffer.h
>  (from src/include/xmmsc/xmmsv_bitbuffer.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsv_build.h 
> (from src/include/xmmsc/xmmsv_build.h)
> + install 
> /«BUILDDIR»/xmms2-0.8+dfsg/debian/tmp/usr/include/xmms2/xmmsc/xmmsv_coll.h 
> (from src/include/xmmsc/xmmsv_coll.h)
> + install 

Bug#676099: libfam-ruby: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: libfam-ruby
Version: 0.2.0-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh build
>dh_testdir
>debian/rules override_dh_auto_configure
> make[1]: Entering directory `/«PKGBUILDDIR»'
> ruby extconf.rb
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from extconf.rb:1:in `'
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/libfam-ruby_0.2.0-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676098: graphviz: FTBFS: cp: cannot stat `debian/tmp/usr/lib/graphviz/ruby/libgv_ruby.so': No such file or directory

[Lucas Nussbaum]

Source: graphviz
Version: 2.26.3-11
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»'
> make[3]: Nothing to be done for `install-exec-am'.
>  /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man7'
>  /usr/bin/install -c -m 644 graphviz.7 
> '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man7'
>  /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/include/graphviz'
>  /usr/bin/install -c -m 644 graphviz_version.h 
> '/«PKGBUILDDIR»/debian/tmp/usr/include/graphviz'
>  /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/share/graphviz/doc'
>  /usr/bin/install -c -m 644 AUTHORS COPYING ChangeLog NEWS cpl1.0.txt 
> '/«PKGBUILDDIR»/debian/tmp/usr/share/graphviz/doc'
> make[3]: Leaving directory `/«PKGBUILDDIR»'
> make[2]: Leaving directory `/«PKGBUILDDIR»'
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> # Remove .la files
> find -name '*.la' -delete
> # Strip the rpath on /usr/lib (at least on amd64), but not
> # on /usr/lib/graphviz (needed for the plugins), and bail
> # out if it is another case, while ignoring if there's no
> # RPATH at all (there are shell scripts under /usr/bin).
> for i in `find debian/tmp/usr/bin debian/tmp/usr/lib -type f` ; do \
>   case `chrpath -l -k $i` in \
>   *RPATH=/usr/lib/graphviz) ;; \
>   *RPATH=/usr/lib) chrpath -d $i ;; \
>   *RPATH=/usr/lib:/usr/lib/graphviz) chrpath -r 
> /usr/lib/graphviz $i ;; \
>   *RPATH=*) echo "Unknown RPATH: $i" ; exit 1 ;; \
>   *) ;; \
>   esac ; \
>   done
> `debian/tmp/usr/bin/dotty' probably isn't a 64-bit LSB-first ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/bin/lneato' probably isn't a 64-bit LSB-first ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/bin/vimdot' probably isn't a 64-bit LSB-first ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/graphviz/python/gv.py' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/graphviz/python27/gv.py' probably isn't a 64-bit 
> LSB-first ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/graphviz/python26/gv.py' probably isn't a 64-bit 
> LSB-first ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/graphviz/php/gv.php' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/graphviz/perl/gv.pm' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/graphviz/tcl/pkgIndex.tcl' probably isn't a 64-bit 
> LSB-first ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/pkgconfig/libgvpr.pc' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/pkgconfig/libgvc.pc' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/pkgconfig/libxdot.pc' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/pkgconfig/libpathplan.pc' probably isn't a 64-bit 
> LSB-first ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/pkgconfig/libcgraph.pc' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/pkgconfig/libgraph.pc' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> `debian/tmp/usr/lib/pkgconfig/libcdt.pc' probably isn't a 64-bit LSB-first 
> ELF file.
> elf_open: Exec format error
> # Compute the dependencies of the -dev package
> # NOTE: It is important to do that before splitting the files into
> # their respective packages, otherwise the symlinks are broken
> d-devlibdeps \
>   --override s/libpathplan4-dev// \
>   --override s/libgraph4-dev//\
>   --override s/libcdt4-dev//  \
>   --override s/libcgraph5-dev//   \
>   --override s/libgvpr4-dev//   \
>   --override s/libxdot4-dev//   \
>   /«PKGBUILDDIR»/debian/libgraphviz-dev.substvars \
>   /«PKGBUILDDIR»/debian/tmp/usr/lib/*.so
>  --> libexpat1-dev package exists.
>  --> zlib1g-dev package exists.
> # Move from debian

Bug#676097: sword: FTBFS: CMakeFiles/buildtest.dir/buildtest.cpp.o: could not read symbols: Bad value

[Lucas Nussbaum]

Source: sword
Version: 1.6.2+dfsg-4
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /usr/bin/ld: CMakeFiles/buildtest.dir/buildtest.cpp.o: relocation 
> R_X86_64_32S against `.rodata' can not be used when making a shared object; 
> recompile with -fPIC
> CMakeFiles/buildtest.dir/buildtest.cpp.o: could not read symbols: Bad value
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/sword_1.6.2+dfsg-4_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676096: scim-prime: FTBFS: scim_prime_imengine_setup.cpp:29:21: fatal error: gtk/gtk.h: No such file or directory

[Lucas Nussbaum]

Source: scim-prime
Version: 1.0.0-4
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. 
> -DSCIM_PRIME_LOCALEDIR=\"/usr/share/locale\" 
> -DSCIM_ICONDIR=\"/usr/share/scim/icons\" -I/usr/include/scim-1.0 -g -O2 -MT 
> prime_imengine_setup_la-scim_prime_imengine_setup.lo -MD -MP -MF 
> .deps/prime_imengine_setup_la-scim_prime_imengine_setup.Tpo -c 
> scim_prime_imengine_setup.cpp  -fPIC -DPIC -o 
> .libs/prime_imengine_setup_la-scim_prime_imengine_setup.o
> scim_prime_imengine_setup.cpp:29:21: fatal error: gtk/gtk.h: No such file or 
> directory
> compilation terminated.
> make[3]: *** [prime_imengine_setup_la-scim_prime_imengine_setup.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/scim-prime_1.0.0-4_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676095: comedilib: FTBFS: mv: cannot stat `debian/tmp/usr/lib/ruby/1.8/local/lib/site_ruby/1.8/comedi.rb': No such file or directory

[Lucas Nussbaum]

Source: comedilib
Version: 0.8.1-6
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory 
> `/«PKGBUILDDIR»/debian/libcomedi-dev/usr/share/doc/libcomedi-dev/demo'
> rm -f *.o
> rm -rf .libs
> make[1]: Leaving directory 
> `/«PKGBUILDDIR»/debian/libcomedi-dev/usr/share/doc/libcomedi-dev/demo'
> mv debian/tmp/usr/lib/ruby/1.8/local/lib/site_ruby/1.8/comedi.rb 
> debian/tmp/usr/lib/ruby/1.8
> mv: cannot stat 
> `debian/tmp/usr/lib/ruby/1.8/local/lib/site_ruby/1.8/comedi.rb': No such file 
> or directory
> make: *** [install] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/comedilib_0.8.1-6_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676094: geos: FTBFS: geos_wrap.cxx:856:18: fatal error: ruby.h: No such file or directory

[Lucas Nussbaum]

Source: geos
Version: 3.3.3-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -fpermissive 
> -DHAVE_CONFIG_H -I. -I../../include -I../../include/geos 
> -I/usr/lib/ruby/1.9.1/x86_64-linux -I../../capi  -DGEOS_INLINE  -pedantic 
> -Wall -ansi -Wno-long-long  -ffloat-store -g -O2 -MT geos_la-geos_wrap.lo -MD 
> -MP -MF .deps/geos_la-geos_wrap.Tpo -c -o geos_la-geos_wrap.lo `test -f 
> 'geos_wrap.cxx' || echo './'`geos_wrap.cxx
> libtool: compile:  g++ -fpermissive -DHAVE_CONFIG_H -I. -I../../include 
> -I../../include/geos -I/usr/lib/ruby/1.9.1/x86_64-linux -I../../capi 
> -DGEOS_INLINE -pedantic -Wall -ansi -Wno-long-long -ffloat-store -g -O2 -MT 
> geos_la-geos_wrap.lo -MD -MP -MF .deps/geos_la-geos_wrap.Tpo -c geos_wrap.cxx 
>  -fPIC -DPIC -o .libs/geos_la-geos_wrap.o
> geos_wrap.cxx:856:18: fatal error: ruby.h: No such file or directory
> compilation terminated.
> make[5]: *** [geos_la-geos_wrap.lo] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/geos_3.3.3-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676093: libzoom-ruby: FTBFS: make: /usr/bin/ruby1.8: Command not found

[Lucas Nussbaum]

Source: libzoom-ruby
Version: 0.4.1-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> Adding cdbs dependencies to debian/libzoom-ruby.substvars
> dh_installdirs -plibzoom-ruby 
> dh_installdocs -plibzoom-ruby ./README 
> dh_installexamples -plibzoom-ruby 
> dh_installman -plibzoom-ruby  
> dh_installinfo -plibzoom-ruby  
> dh_installmenu -plibzoom-ruby 
> dh_installcron -plibzoom-ruby 
> dh_installinit -plibzoom-ruby  
> dh_installdebconf -plibzoom-ruby 
> dh_installemacsen -plibzoom-ruby   
> dh_installcatalogs -plibzoom-ruby 
> dh_installpam -plibzoom-ruby 
> dh_installlogrotate -plibzoom-ruby 
> dh_installlogcheck -plibzoom-ruby 
> dh_installchangelogs -plibzoom-ruby  ./ChangeLog 
> dh_installudev -plibzoom-ruby 
> dh_lintian -plibzoom-ruby 
> dh_bugfiles -plibzoom-ruby 
> dh_install -plibzoom-ruby  
> dh_link -plibzoom-ruby  
> dh_installmime -plibzoom-ruby 
> dh_installgsettings -plibzoom-ruby 
> dh_strip -plibzoom-ruby  
> dh_compress -plibzoom-ruby  
> dh_fixperms -plibzoom-ruby  
> dh_makeshlibs -plibzoom-ruby  
> dh_installdeb -plibzoom-ruby 
> dh_perl -plibzoom-ruby 
> dh_shlibdeps -plibzoom-ruby
> dh_gencontrol -plibzoom-ruby  
> dh_md5sums -plibzoom-ruby 
> dh_builddeb -plibzoom-ruby 
> dpkg-deb: building package `libzoom-ruby' in 
> `../libzoom-ruby_0.4.1-2_all.deb'.
> Adding cdbs dependencies to debian/libzoom-ruby1.8.substvars
> make: ruby1.8: Command not found
> make: ruby1.8: Command not found
> cd . 
> [ ! -f Makefile ] || /usr/bin/make distclean
> /usr/bin/ruby1.8  src/extconf.rb 
> make: /usr/bin/ruby1.8: Command not found
> make: *** [install/libzoom-ruby1.8] Error 127

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/libzoom-ruby_0.4.1-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676092: libwebapp-ruby: FTBFS: cp: cannot stat `./debian/tmp/usr/lib/ruby/1.8/webapp.rb': No such file or directory

[Lucas Nussbaum]

Source: libwebapp-ruby
Version: 0.4-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> mkdir -p /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/1.9.1/webapp
> install -m 644 webapp.rb /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/1.9.1
> for f in webapp/cli.rb webapp/htmlform.rb webapp/manager.rb webapp/message.rb 
> webapp/querystring.rb webapp/urigen.rb webapp/webrick-servlet.rb; do \
>install -m 644 $f 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/1.9.1/webapp; \
>   done
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_testdir
> dh_testroot
> dh_installchangelogs 
> dh_installdocs
> dh_installexamples
> dh_install
> cp: cannot stat `./debian/tmp/usr/lib/ruby/1.8/webapp.rb': No such file or 
> directory
> dh_install: cp -a ./debian/tmp/usr/lib/ruby/1.8/webapp.rb 
> debian/libwebapp-ruby1.8//usr/lib/ruby/1.8/ returned exit code 1
> make: *** [binary-indep] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/libwebapp-ruby_0.4-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676091: shoes: FTBFS: ./shoes/app.h:14:18: fatal error: ruby.h: No such file or directory

[Lucas Nussbaum]

Source: shoes
Version: 0.r396-5.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> cleaning
> shoes build options:
> CC   = cc
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> RUBY = /usr
> OPTIONS  =
> ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
> CC shoes/app.c
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> In file included from shoes/app.c:5:0:
> ./shoes/app.h:14:18: fatal error: ruby.h: No such file or directory
> compilation terminated.
> make[1]: *** [shoes/app.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/shoes_0.r396-5.1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676090: liblockfile-ruby: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- ftools (LoadError)

[Lucas Nussbaum]

Source: liblockfile-ruby
Version: 1.4.3-2.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> dh install
>dh_testroot
>dh_prep
>dh_installdirs
>dh_auto_install
>dh_install
>dh_installdocs
>dh_installchangelogs
>dh_installexamples
>dh_installman
>dh_installcatalogs
>dh_installcron
>dh_installdebconf
>dh_installemacsen
>dh_installifupdown
>dh_installinfo
>dh_installinit
>dh_installmenu
>dh_installmime
>dh_installmodules
>dh_installlogcheck
>dh_installlogrotate
>dh_installpam
>dh_installppp
>dh_installudev
>dh_installwm
>dh_installxfonts
>dh_installgsettings
>dh_bugfiles
>dh_ucf
>dh_lintian
>dh_gconf
>dh_icons
>dh_perl
>dh_usrlocal
>dh_link
>dh_compress
>dh_fixperms
> ruby install.rb \
> --libdir `pwd`/debian/`dh_listpackages`/usr/lib/ruby/1.8 \
> --bindir `pwd`/debian/`dh_listpackages`/usr/bin
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- ftools (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from install.rb:4:in `'
> make: *** [install-stamp] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/liblockfile-ruby_1.4.3-2.1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676089: libpdf-writer-ruby: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': /«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: invalid multibyte char (US-ASCII

[Lucas Nussbaum]

Source: libpdf-writer-ruby
Version: 1.1.8+dfsg-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs -A 
> mkdir -p "."
> /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING:  DEB_COMPRESS_EXCLUDE is a 
> deprecated variable
> dh_installman --package=libpdf-writer-ruby1.8 debian/techbook.1
> Adding cdbs dependencies to debian/libpdf-writer-ruby.substvars
> dh_installdirs -plibpdf-writer-ruby 
> Adding cdbs dependencies to debian/libpdf-writer-ruby-doc.substvars
> dh_installdirs -plibpdf-writer-ruby-doc 
> # Build the documentation PDF
> /usr/bin/ruby -I  ./debian/libpdf-writer-ruby1.8/ ./bin/techbook -n manual.pwd
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': 
> /«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: invalid 
> multibyte char (US-ASCII) (SyntaxError)
> /«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: invalid 
> multibyte char (US-ASCII)
> /«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/writer.rb:712: syntax 
> error, unexpected $end, expecting keyword_end
> content = "%PDF-#{@version}\n%âãÏÓ\n"
> ^
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from 
> /«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/simpletable.rb:11:in ` (required)>'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from 
> /«BUILDDIR»/libpdf-writer-ruby-1.1.8+dfsg/lib/pdf/techbook.rb:12:in ` (required)>'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from ./bin/techbook:18:in `rescue in '
>   from ./bin/techbook:12:in `'
> make: *** [install/libpdf-writer-ruby-doc] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/libpdf-writer-ruby_1.1.8+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676088: posixlock: FTBFS: make: /usr/bin/ruby1.8: Command not found

[Lucas Nussbaum]

Source: posixlock
Version: 0.0.1-1.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_clean: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installdirs -A 
> dh_installdirs: Compatibility levels before 5 are deprecated (level 4 in use)
> mkdir -p "."
> /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING:  DEB_COMPRESS_EXCLUDE is a 
> deprecated variable
> Adding cdbs dependencies to debian/libposixlock-ruby.substvars
> dh_installdirs -plibposixlock-ruby 
> dh_installdirs: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installdocs -plibposixlock-ruby ./README 
> dh_installdocs: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installexamples -plibposixlock-ruby 
> dh_installexamples: Compatibility levels before 5 are deprecated (level 4 in 
> use)
> dh_installman -plibposixlock-ruby  
> dh_installman: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installinfo -plibposixlock-ruby  
> dh_installinfo: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installmenu -plibposixlock-ruby 
> dh_installmenu: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installcron -plibposixlock-ruby 
> dh_installcron: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installinit -plibposixlock-ruby  
> dh_installinit: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installdebconf -plibposixlock-ruby 
> dh_installdebconf: Compatibility levels before 5 are deprecated (level 4 in 
> use)
> dh_installemacsen -plibposixlock-ruby   
> dh_installemacsen: Compatibility levels before 5 are deprecated (level 4 in 
> use)
> dh_installcatalogs -plibposixlock-ruby 
> dh_installcatalogs: Compatibility levels before 5 are deprecated (level 4 in 
> use)
> dh_installpam -plibposixlock-ruby 
> dh_installpam: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installlogrotate -plibposixlock-ruby 
> dh_installlogrotate: Compatibility levels before 5 are deprecated (level 4 in 
> use)
> dh_installlogcheck -plibposixlock-ruby 
> dh_installlogcheck: Compatibility levels before 5 are deprecated (level 4 in 
> use)
> dh_installchangelogs -plibposixlock-ruby  
> dh_installchangelogs: Compatibility levels before 5 are deprecated (level 4 
> in use)
> dh_installudev -plibposixlock-ruby 
> dh_installudev: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_lintian -plibposixlock-ruby 
> dh_lintian: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_bugfiles -plibposixlock-ruby 
> dh_bugfiles: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_install -plibposixlock-ruby  
> dh_install: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_link -plibposixlock-ruby  
> dh_link: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installmime -plibposixlock-ruby 
> dh_installmime: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installgsettings -plibposixlock-ruby 
> dh_installgsettings: Compatibility levels before 5 are deprecated (level 4 in 
> use)
> dh_strip -plibposixlock-ruby  
> dh_strip: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_compress -plibposixlock-ruby -X .rb 
> dh_compress: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_fixperms -plibposixlock-ruby  
> dh_fixperms: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_makeshlibs -plibposixlock-ruby  
> dh_makeshlibs: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installdeb -plibposixlock-ruby 
> dh_installdeb: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_perl -plibposixlock-ruby 
> dh_perl: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_shlibdeps -plibposixlock-ruby
> dh_shlibdeps: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_gencontrol -plibposixlock-ruby  
> dh_gencontrol: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_md5sums -plibposixlock-ruby 
> dh_md5sums: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_builddeb -plibposixlock-ruby 
> dh_builddeb: Compatibility levels before 5 are deprecated (level 4 in use)
> dpkg-deb: building package `libposixlock-ruby' in 
> `../libposixlock-ruby_0.0.1-1.1_all.deb&#

Bug#676087: ruby-prof: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: ruby-prof
Version: 0.7.3-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> QUILT_PATCHES=debian/patches \
>   quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch dont-use-env.patch
> patching file bin/ruby-prof
> patching file lib/ruby-prof/task.rb
> 
> Now at patch dont-use-env.patch
> touch debian/stamp-patched
> dh build --until dh_auto_configure
> dh: The --until option is deprecated. Use override targets instead.
>dh_testdir
>dh_auto_configure
> (cd ext && ruby extconf.rb)
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from extconf.rb:1:in `'
> make: *** [build] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/ruby-prof_0.7.3-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676086: libnet-irc-ruby: FTBFS: /bin/sh: 2: cd: can't cd to /«PKGBUILDDIR»/debian/libnet-irc-ruby//usr/lib/ruby/1.9.1

[Lucas Nussbaum]

Source: libnet-irc-ruby
Version: 0.14-5
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> -e:1: Use RbConfig instead of obsolete and deprecated Config.
> dh_testdir
> dh_testroot
> dh_clean -k
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_clean: Compatibility levels before 5 are deprecated (level 4 in use)
> dh_installdirs
> dh_installdirs: Compatibility levels before 5 are deprecated (level 4 in use)
> tar cf - irc localize.rb | \
> (cd /«PKGBUILDDIR»/debian/libnet-irc-ruby//usr/lib/ruby/1.9.1 && tar 
> xvf -)
> /bin/sh: 2: cd: can't cd to 
> /«PKGBUILDDIR»/debian/libnet-irc-ruby//usr/lib/ruby/1.9.1
> make: *** [install] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/libnet-irc-ruby_0.14-5_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676085: qpid-cpp: FTBFS: cqpid.cpp:2244:38: error: format not a string literal and no format arguments [-Werror=format-security]

[Lucas Nussbaum]

Source: qpid-cpp
Version: 0.16-5
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> /bin/bash ../../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
> -I. -I../../../src -I../../../include -I../../../include -I../../../src 
> -I../../../src  -D_FORTIFY_SOURCE=2 -I../../../include -I../../../include 
> -I../../../src -I../../../src -I/usr/include/ruby-1.9.1 
> -I/usr/include/ruby-1.9.1/x86_64-linux -fno-strict-aliasing -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -Wno-error=cast-qual -Wno-error=cast-align -c -o cqpid_la-cqpid.lo `test -f 
> 'cqpid.cpp' || echo './'`cqpid.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src -I../../../include 
> -I../../../include -I../../../src -I../../../src -D_FORTIFY_SOURCE=2 
> -I../../../include -I../../../include -I../../../src -I../../../src 
> -I/usr/include/ruby-1.9.1 -I/usr/include/ruby-1.9.1/x86_64-linux 
> -fno-strict-aliasing -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -Wno-error=cast-qual -Wno-error=cast-align 
> -c cqpid.cpp  -fPIC -DPIC -o .libs/cqpid_la-cqpid.o
> cqpid.cpp: In function 'VALUE VariantToRb(const qpid::types::Variant*)':
> cqpid.cpp:2244:38: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_new_Address__SWIG_0(int, VALUE*, VALUE)':
> cqpid.cpp:2311:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_new_Address__SWIG_1(int, VALUE*, VALUE)':
> cqpid.cpp:2347:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_new_Address__SWIG_2(int, VALUE*, VALUE)':
> cqpid.cpp:2416:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_new_Address__SWIG_3(int, VALUE*, VALUE)':
> cqpid.cpp:2482:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_new_Address__SWIG_4(int, VALUE*, VALUE)':
> cqpid.cpp:2543:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_getName(int, VALUE*, VALUE)':
> cqpid.cpp:2660:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_setName(int, VALUE*, VALUE)':
> cqpid.cpp:2703:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_getSubject(int, VALUE*, VALUE)':
> cqpid.cpp:2736:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_setSubject(int, VALUE*, VALUE)':
> cqpid.cpp:2779:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_getOptions__SWIG_0(int, VALUE*, 
> VALUE)':
> cqpid.cpp:2812:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_getOptions__SWIG_1(int, VALUE*, 
> VALUE)':
> cqpid.cpp:2846:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_setOptions(int, VALUE*, VALUE)':
> cqpid.cpp:2922:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_getType(int, VALUE*, VALUE)':
> cqpid.cpp:2959:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_setType(int, VALUE*, VALUE)':
> cqpid.cpp:3002:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_Address_str(int, VALUE*, VALUE)':
> cqpid.cpp:3035:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In function 'VALUE _wrap_new_Duration(int, VALUE*, VALUE)':
> cqpid.cpp:3085:34: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cqpid.cpp: In 

Bug#676084: obexftp: FTBFS: ruby_wrap.c:1991:5: error: format not a string literal and no format arguments [-Werror=format-security]

[Lucas Nussbaum]

Source: obexftp
Version: 0.23-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[5]: Entering directory `/«PKGBUILDDIR»/swig/ruby'
> compiling ruby_wrap.c
> ruby_wrap.c: In function 'SWIG_Ruby_define_class':
> ruby_wrap.c:1420:9: warning: variable 'klass' set but not used 
> [-Wunused-but-set-variable]
> ruby_wrap.c: In function '_wrap_discover':
> ruby_wrap.c:1991:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_browsebt':
> ruby_wrap.c:2030:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_new_Client':
> ruby_wrap.c:2072:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_callback':
> ruby_wrap.c:2104:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c:2109:10: warning: assignment makes pointer from integer without a 
> cast [enabled by default]
> ruby_wrap.c: In function '_wrap_Client_discover':
> ruby_wrap.c:2131:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_connect':
> ruby_wrap.c:2173:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c:2179:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_connectpush':
> ruby_wrap.c:2211:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c:2217:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_connectsync':
> ruby_wrap.c:2249:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c:2255:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_disconnect':
> ruby_wrap.c:2282:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_chpath':
> ruby_wrap.c:2307:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_mkpath':
> ruby_wrap.c:2333:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_cdup':
> ruby_wrap.c:2358:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_cdtop':
> ruby_wrap.c:2382:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c: In function '_wrap_Client_get':
> ruby_wrap.c:2407:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c:2413:5: warning: pointer targets in passing argument 1 of 
> 'rb_str_new' differ in signedness [-Wpointer-sign]
> In file included from /usr/include/ruby-1.9.1/ruby/ruby.h:1382:0,
>  from /usr/include/ruby-1.9.1/ruby.h:32,
>  from ruby_wrap.c:804:
> /usr/include/ruby-1.9.1/ruby/intern.h:649:7: note: expected 'const char *' 
> but argument is of type 'uint8_t *'
> ruby_wrap.c:2397:9: warning: variable 'result' set but not used 
> [-Wunused-but-set-variable]
> ruby_wrap.c: In function '_wrap_Client_list':
> ruby_wrap.c:2440:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ruby_wrap.c:2448:5: warning: pointer targets in passing argument 1 of 
> 'rb_str_new' differ in signedness [-Wpointer-sign]
> In file included from /usr/include/ruby-1.9.1/ruby/ruby.h:1382:0,
>  from /usr/include/ruby-1.9.1/ruby.h:32,
>  from ruby_wrap.c:804:
> /usr/include/ruby-1.9.1/ruby/intern.h:649:7: note: expected 'const char *' 
> but argument is of type 'uint8_t *'
> ruby_wrap.c:2430:9: warning: variable 'result' set but not used 
> [-Wunused-but-set-variable]
> ruby_wrap.c: In function '_wrap_Client_get_capability':
> ruby_wrap.c:2475:5: error: forma

Bug#673164: hyperestraier: FTBFS[!linux]: /bin/bash: /usr/java/bin/javac: No such file or directory

[Satoru KURASHIKI]

hi,

On Wed, May 16, 2012 at 11:51 PM, Christoph Egger  wrote:
> Your package failed to build on the kfreebsd-* buildds:
>
> make[1]: Leaving directory 
> `/build/buildd-hyperestraier_1.4.13-4-kfreebsd-amd64-n8scIZ/hyperestraier-1.4.13/rubynative19'
> perl -p -i -e 's@^#! /usr/bin/ruby1\.8 -w@#! /usr/bin/ruby1.9.1 -w@' 
> rubynative19/estcmd.rb
> cd javapure && /usr/bin/make
> make[1]: Entering directory 
> `/build/buildd-hyperestraier_1.4.13-4-kfreebsd-amd64-n8scIZ/hyperestraier-1.4.13/javapure'
> /usr/java/bin/javac -d . Document.java Condition.java ResultDocument.java 
> NodeResult.java Node.java Utility.java Call.java
> /bin/bash: /usr/java/bin/javac: No such file or directory
> make[1]: *** [estraierpure.jar] Error 127
> make[1]: Leaving directory 
> `/build/buildd-hyperestraier_1.4.13-4-kfreebsd-amd64-n8scIZ/hyperestraier-1.4.13/javapure'
> make: *** [build-arch-stamp] Error 2
>
> Full build log at
> https://buildd.debian.org/status/fetch.php?pkg=hyperestraier&arch=kfreebsd-amd64&ver=1.4.13-4&stamp=1336822375

Upstream makefile had dropped support for gcj, so I will drop architectures
don't have openjdk from building java bindings.

http://anonscm.debian.org/gitweb/?p=collab-maint/hyperestraier.git;a=commit;h=34128c829714e52457e51d13453ef6a78d38668d

(This will be uploaded after dealing with hardening build flag issues.)

regards,
-- 
KURASHIKI Satoru



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676083: quickfix: FTBFS: QuickfixRuby.cpp:3904:20: fatal error: config.h: No such file or directory

[Lucas Nussbaum]

Source: quickfix
Version: 1.13.3+dfsg-4
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[5]: Entering directory `/«BUILDDIR»/quickfix-1.13.3+dfsg/src/ruby'
> compiling QuickfixRuby.cpp
> In file included from QuickfixRuby.cpp:3752:0:
> /usr/include/ruby-1.9.1/ruby/backward/rubyio.h:2:2: warning: #warning use 
> "ruby/io.h" instead of "rubyio.h" [-Wcpp]
> QuickfixRuby.cpp:3904:20: fatal error: config.h: No such file or directory
> compilation terminated.
> make[5]: *** [QuickfixRuby.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/quickfix_1.13.3+dfsg-4_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676082: ecasound: FTBFS: dh_install: ruby-ecasound missing files (usr/local/lib/site_ruby/1.8/*), aborting

[Lucas Nussbaum]

Source: ecasound
Version: 2.8.1-8
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»'
> make[3]: Nothing to be done for `install-exec-am'.
> sed -e "s%[@]VERSION[@]%2.8.1%" \
> -e "s%[@]prefix[@]%/usr%" \
> -e "s%[@]pkgdatadir[@]%/usr/share/ecasound%" \
> < ./ecasoundrc.in > ecasoundrc 
> /usr/bin/install -c -d /«PKGBUILDDIR»/debian/tmp/usr/share/ecasound
> /usr/bin/install -c -m 644 ./ecasoundrc 
> /«PKGBUILDDIR»/debian/tmp/usr/share/ecasound/ecasoundrc
> /usr/bin/install -c -m 644 ./effect_presets 
> /«PKGBUILDDIR»/debian/tmp/usr/share/ecasound/effect_presets
> /usr/bin/install -c -m 644 ./ecatools/ecasound.el 
> /«PKGBUILDDIR»/debian/tmp/usr/share/ecasound/ecasound.el
> /usr/bin/install -c -m 644 ./generic_oscillators 
> /«PKGBUILDDIR»/debian/tmp/usr/share/ecasound/generic_oscillators
> make[3]: Leaving directory `/«PKGBUILDDIR»'
> make[2]: Leaving directory `/«PKGBUILDDIR»'
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>dh_install -O--parallel
> dh_install: ruby-ecasound missing files (usr/local/lib/site_ruby/1.8/*), 
> aborting
> make: *** [binary] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/ecasound_2.8.1-8_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676081: rrdtool: FTBFS: main.c:102:5: error: format not a string literal and no format arguments [-Werror=format-security]

[Lucas Nussbaum]

Source: rrdtool
Version: 1.4.7-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»/bindings/ruby'
> compiling main.c
> main.c: In function 'string_arr_new':
> main.c:60:22: warning: format '%s' expects argument of type 'char *', but 
> argument 3 has type 'long int' [-Wformat]
> main.c:60:22: warning: format '%ld' expects argument of type 'long int', but 
> argument 4 has type 'int' [-Wformat]
> main.c: In function 'rrd_call':
> main.c:102:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_infocall':
> main.c:170:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_fetch':
> main.c:246:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_graph':
> main.c:291:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_last':
> main.c:319:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> main.c: In function 'rb_rrd_xport':
> main.c:340:5: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> make[1]: *** [main.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/06/04/rrdtool_1.4.7-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676080: ohcount: FTBFS: cp: cannot stat `ruby/ohcount.rb': No such file or directory

[Lucas Nussbaum]

Source: ohcount
Version: 3.0.0-6
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
>   rm -f debian/ohcount.substvars
>   rm -f debian/ohcount.*.debhelper
>   rm -rf debian/ohcount/
>   rm -f debian/ohcount-doc.substvars
>   rm -f debian/ohcount-doc.*.debhelper
>   rm -rf debian/ohcount-doc/
> dh_installdirs -A 
>   install -d debian/ohcount
>   install -d debian/ohcount-doc
> mkdir -p "."
> (cd doc && doxygen Doxyfile)
> warning: Tag `SHOW_DIRECTORIES' at line 462 of file Doxyfile has become 
> obsolete.
> To avoid this warning please remove this line from your configuration file or 
> upgrade it using "doxygen -u"
> warning: Tag `HTML_ALIGN_MEMBERS' at line 783 of file Doxyfile has become 
> obsolete.
> To avoid this warning please remove this line from your configuration file or 
> upgrade it using "doxygen -u"
> Searching for include files...
> Searching for example files...
> Searching for files in directory /«PKGBUILDDIR»/doc/examples
> Searching for images...
> Searching for dot files...
> Searching for msc files...
> Searching for files to exclude
> Searching for files to process...
> Searching for files in directory /«PKGBUILDDIR»/src
> Reading and parsing tag files
> Preprocessing /«PKGBUILDDIR»/src/detector.h...
> Parsing file /«PKGBUILDDIR»/src/detector.h...
> Preprocessing /«PKGBUILDDIR»/src/diff.h...
> Parsing file /«PKGBUILDDIR»/src/diff.h...
> Preprocessing /«PKGBUILDDIR»/src/languages.h...
> Parsing file /«PKGBUILDDIR»/src/languages.h...
> Preprocessing /«PKGBUILDDIR»/src/licenses.h...
> Parsing file /«PKGBUILDDIR»/src/licenses.h...
> Preprocessing /«PKGBUILDDIR»/src/loc.h...
> Parsing file /«PKGBUILDDIR»/src/loc.h...
> Preprocessing /«PKGBUILDDIR»/src/log.h...
> Parsing file /«PKGBUILDDIR»/src/log.h...
> Preprocessing /«PKGBUILDDIR»/src/ohcount.h...
> Parsing file /«PKGBUILDDIR»/src/ohcount.h...
> Preprocessing /«PKGBUILDDIR»/src/parsed_language.h...
> Parsing file /«PKGBUILDDIR»/src/parsed_language.h...
> Preprocessing /«PKGBUILDDIR»/src/parser.h...
> Parsing file /«PKGBUILDDIR»/src/parser.h...
> Preprocessing /«PKGBUILDDIR»/src/parser_macros.h...
> Parsing file /«PKGBUILDDIR»/src/parser_macros.h...
> Preprocessing /«PKGBUILDDIR»/src/sourcefile.h...
> Parsing file /«PKGBUILDDIR»/src/sourcefile.h...
> Preprocessing /«PKGBUILDDIR»/src/structs.h...
> Parsing file /«PKGBUILDDIR»/src/structs.h...
> Building group list...
> Building directory list...
> Building namespace list...
> Building file list...
> Building class list...
> Associating documentation with classes...
> Computing nesting relations for classes...
> Building example list...
> Searching for enumerations...
> Searching for documented typedefs...
> Searching for members imported via using declarations...
> Searching for included using directives...
> Searching for documented variables...
> Building member list...
> Searching for friends...
> Searching for documented defines...
> Computing class inheritance relations...
> Computing class usage relations...
> Flushing cached template relations that have become invalid...
> Creating members for template instances...
> Computing class relations...
> Add enum values to enums...
> Searching for member function documentation...
> Building page list...
> Search for main page...
> Computing page relations...
> Determining the scope of groups...
> Sorting lists...
> Freeing entry tree
> Determining which enums are documented
> Computing member relations...
> Building full member lists recursively...
> Adding members to member groups.
> Computing member references...
> Inheriting documentation...
> Generating disk names...
> Adding source references...
> Adding xrefitems...
> Sorting member lists...
> Computing dependencies between directories...
> Generating citations page...
> Counting data structures...
> Resolving user defined references...
> Finding anchors and sections in the documentation...
> Combining using relations...
> Adding members to index pages...
> Generating style sheet...
> Generating example documentation...
> Generating file sources...
> Generating code for file /«PKGBUILDDIR»/src/detector.h...
> Generating code for file /«PKGBUILDDIR»/src/diff.h...
> Generating code for file /«PKGBUILDDIR»/src/languages.h...
> Generating code for file /«PKGBUILD

Bug#676078: merb: FTBFS: rm: cannot remove `/«BUILDDIR»/merb-1.0.12+dfsg/debian/libmerb-slices-ruby1.8/usr/lib/ruby/1.8/generators/templates/common/LICENSE': No such file or directory

[Lucas Nussbaum]

Source: merb
Version: 1.0.12+dfsg-4
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> Adding cdbs dependencies to debian/merb-core.substvars
> dh_installdirs -pmerb-core 
> dh_installchangelogs
> dh_installdirs
> Adding cdbs dependencies to debian/merb-slices.substvars
> dh_installdirs -pmerb-slices 
> dh_installchangelogs
> dh_installdirs
> Adding cdbs dependencies to debian/libmerb-core-ruby.substvars
> dh_installdirs -plibmerb-core-ruby 
> Adding cdbs dependencies to debian/libmerb-core-ruby1.8.substvars
> dh_installdirs -plibmerb-core-ruby1.8 
> if [ ! -L merb-core/debian-setup.rb ] ; then if [ -f 
> merb-core/debian-setup.rb ] ; then mv merb-core/debian-setup.rb 
> merb-core/debian-setup.rb.moved_away_by_debian_build ; fi ; ln -s 
> /usr/lib/ruby/1.8/setup.rb merb-core/debian-setup.rb ; fi
> (cd merb-core && /usr/bin/ruby debian-setup.rb config --installdirs=std)
> debian-setup.rb:789: Use RbConfig instead of obsolete and deprecated Config.
> ---> bin
> <--- bin
> ---> lib
> ---> lib/merb-core
> ---> lib/merb-core/dispatch
> ---> lib/merb-core/dispatch/default_exception
> ---> lib/merb-core/dispatch/default_exception/views
> <--- lib/merb-core/dispatch/default_exception/views
> <--- lib/merb-core/dispatch/default_exception
> ---> lib/merb-core/dispatch/router
> <--- lib/merb-core/dispatch/router
> ---> lib/merb-core/dispatch/session
> <--- lib/merb-core/dispatch/session
> <--- lib/merb-core/dispatch
> ---> lib/merb-core/test
> ---> lib/merb-core/test/matchers
> <--- lib/merb-core/test/matchers
> ---> lib/merb-core/test/helpers
> <--- lib/merb-core/test/helpers
> ---> lib/merb-core/test/tasks
> <--- lib/merb-core/test/tasks
> ---> lib/merb-core/test/test_ext
> <--- lib/merb-core/test/test_ext
> <--- lib/merb-core/test
> ---> lib/merb-core/tasks
> <--- lib/merb-core/tasks
> ---> lib/merb-core/gem_ext
> <--- lib/merb-core/gem_ext
> ---> lib/merb-core/core_ext
> <--- lib/merb-core/core_ext
> ---> lib/merb-core/rack
> ---> lib/merb-core/rack/handler
> <--- lib/merb-core/rack/handler
> ---> lib/merb-core/rack/adapter
> <--- lib/merb-core/rack/adapter
> ---> lib/merb-core/rack/middleware
> <--- lib/merb-core/rack/middleware
> <--- lib/merb-core/rack
> ---> lib/merb-core/controller
> ---> lib/merb-core/controller/mixins
> <--- lib/merb-core/controller/mixins
> <--- lib/merb-core/controller
> <--- lib/merb-core
> <--- lib
> (cd merb-core && /usr/bin/ruby debian-setup.rb setup)
> debian-setup.rb:789: Use RbConfig instead of obsolete and deprecated Config.
> ---> bin
> updating shebang: merb
> updating shebang: merb-specs
> <--- bin
> ---> lib
> ---> lib/merb-core
> ---> lib/merb-core/dispatch
> ---> lib/merb-core/dispatch/default_exception
> ---> lib/merb-core/dispatch/default_exception/views
> <--- lib/merb-core/dispatch/default_exception/views
> <--- lib/merb-core/dispatch/default_exception
> ---> lib/merb-core/dispatch/router
> <--- lib/merb-core/dispatch/router
> ---> lib/merb-core/dispatch/session
> <--- lib/merb-core/dispatch/session
> <--- lib/merb-core/dispatch
> ---> lib/merb-core/test
> ---> lib/merb-core/test/matchers
> <--- lib/merb-core/test/matchers
> ---> lib/merb-core/test/helpers
> <--- lib/merb-core/test/helpers
> ---> lib/merb-core/test/tasks
> <--- lib/merb-core/test/tasks
> ---> lib/merb-core/test/test_ext
> <--- lib/merb-core/test/test_ext
> <--- lib/merb-core/test
> ---> lib/merb-core/tasks
> <--- lib/merb-core/tasks
> ---> lib/merb-core/gem_ext
> <--- lib/merb-core/gem_ext
> ---> lib/merb-core/core_ext
> <--- lib/merb-core/core_ext
> ---> lib/merb-core/rack
> ---> lib/merb-core/rack/handler
> <--- lib/merb-core/rack/handler
> ---> lib/merb-core/rack/adapter
> <--- lib/merb-core/rack/adapter
> ---> lib/merb-core/rack/middleware
> <--- lib/merb-core/rack/middleware
> <--- lib/merb-core/rack
> ---> lib/merb-core/controller
> ---> lib/merb-core/controller/mixins
> <--- lib/merb-core/controller/mixins
> <--- lib/merb-core/controller
> <--- lib/merb-core
> <--- lib
> (cd merb-core && /usr/bin/ruby 

Bug#676079: libimlib2-ruby: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: libimlib2-ruby
Version: 0.5.2-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh build
>dh_testdir
>debian/rules override_dh_auto_configure
> make[1]: Entering directory `/«PKGBUILDDIR»'
> ruby extconf.rb
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from extconf.rb:1:in `'
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/libimlib2-ruby_0.5.2-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676077: raspell: FTBFS: ext/raspell.c:76:9: error: format not a string literal and no format arguments [-Werror=format-security]

[Lucas Nussbaum]

Source: raspell
Version: 1.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> compiling ext/raspell.c
> ext/raspell.c: In function 'check_for_error':
> ext/raspell.c:76:9: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ext/raspell.c: In function 'set_option':
> ext/raspell.c:90:9: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ext/raspell.c:94:9: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ext/raspell.c: In function 'set_options':
> ext/raspell.c:109:9: warning: implicit declaration of function 'STR2CSTR' 
> [-Wimplicit-function-declaration]
> ext/raspell.c:109:9: warning: passing argument 2 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c:109:9: warning: passing argument 3 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c: In function 'get_checker':
> ext/raspell.c:135:9: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ext/raspell.c: In function 'get_wordregexp':
> ext/raspell.c:164:19: warning: initialization makes pointer from integer 
> without a cast [enabled by default]
> ext/raspell.c: In function 'aspell_s_new':
> ext/raspell.c:203:5: warning: passing argument 3 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c:205:5: warning: passing argument 3 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c:207:5: warning: passing argument 3 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c:209:5: warning: passing argument 3 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c:217:9: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ext/raspell.c: In function 'aspell_s_new1':
> ext/raspell.c:256:9: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> ext/raspell.c: In function 'aspell_set_option':
> ext/raspell.c:296:5: warning: passing argument 2 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c:296:5: warning: passing argument 3 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c: In function 'aspell_remove_option':
> ext/raspell.c:307:5: warning: passing argument 2 of 'aspell_config_remove' 
> makes pointer from integer without a cast [enabled by default]
> In file included from ext/raspell.h:6:0,
>  from ext/raspell.c:2:
> /usr/include/aspell.h:166:5: note: expected 'const char *' but argument is of 
> type 'int'
> ext/raspell.c: In function 'aspell_set_suggestion_mode':
> ext/raspell.c:317:5: warning: passing argument 3 of 'set_option' makes 
> pointer from integer without a cast [enabled by default]
> ext/raspell.c:87:13: note: expected 'char *' but argument is of type 'int'
> ext/raspell.c: In function 'aspell_suggest':
> ext/raspell.c:375:5: warning: passing argument 2 of 'aspell_speller_suggest' 
> makes pointer from integer without a cast [enabled by default]
> In file included from ext/raspell.h:6:0,
>  from ext/raspell.c:2:
> /usr/include/aspell.h:386:31: note: expected 'const char *' but argument is 
> of t

Bug#676076: rubyluabridge: FTBFS: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)

[Lucas Nussbaum]

Source: rubyluabridge
Version: 0.7.0-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
User: debian-r...@lists.debian.org
Usertags: default19
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> dh_testdir
> build/extconf_ubuntu.sh
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load 
> such file -- mkmf (LoadError)
>   from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
>   from extconf.rb:2:in `'
> make: *** [build-stamp] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/rubyluabridge_0.7.0-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: forcibly merging 655245 675986, severity of 675986 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 655245 675986
Bug #655245 [vim-addon-manager] vim-addon-manager: Does not work with Ruby 1.9 
as default
Bug #675986 [vim-addon-manager] vim-addon-manager: fatal Ruby error
Severity set to 'important' from 'grave'
Added tag(s) pending and patch.
Merged 655245 675986
> severity 675986 grave
Bug #675986 [vim-addon-manager] vim-addon-manager: fatal Ruby error
Bug #655245 [vim-addon-manager] vim-addon-manager: Does not work with Ruby 1.9 
as default
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
655245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655245
675986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#676073: java-gnome: FTBFS: /usr/bin/env: python: No such file or directory

[Lucas Nussbaum]

Source: java-gnome
Version: 4.1.1-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> touch debian/stamp-autotools-files
> chmod a+x /«PKGBUILDDIR»/./configure
> mkdir -p .
> cd . &&   CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall" CXXFLAGS="" CPPFLAGS="-D_FORTIFY_SOURCE=2" 
> LDFLAGS="-Wl,-z,relro" /«PKGBUILDDIR»/./configure --build=x86_64-linux-gnu  
> --prefix=/usr --includedir="\${prefix}/include" 
> --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
> --sysconfdir=/etc --localstatedir=/var 
> --libexecdir="\${prefix}/lib/java-gnome" --srcdir=. --disable-maintainer-mode 
> --disable-dependency-tracking --disable-silent-rules   --libdir=/usr/lib/jni 
> jdk=/usr/lib/jvm/default-java 
> 
> equivalence, v0.2
> ...configuring Java projects to build and run on Linux & Unix
> 
> Identify operating system: Debian
> 
> Check for required jar files:
>  - JUnit test frameworkfound
> 
> Check for required system libraries:
>  - Cairo   found
>  - GLibfound
>  - GTK+found
>  - Pango   found
>  - RSVGfound
>  - ATK found
>  - GtkSourceView   found
>  - LibNotify   found
>  - Enchant found
>  - LibUnique   found
> 
> Check Java compilers:
>  - Specified javac works
>  - Specified javah found
>  - Specified jar   works
>  - Specified javadoc   found
>  - System javadoc  found
> 
> Check Java virtual machines:
>  - Specified java VM   works
> 
> Check native compiler:
>  - GNU gcc works
> 
> Select compiler:   javac
> Select runtime:java
> 
> Output:
>  - configuration data  ok
>  - native library location ok
> 
> touch debian/stamp-autotools
> DISPLAY=":99" /usr/bin/make  -C .  doc
> make[1]: Entering directory `/«PKGBUILDDIR»'
> /usr/bin/env: python: No such file or directory
> make[1]: *** [doc] Error 127

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2012/06/04/java-gnome_4.1.1-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org