Bug#725470: incompatible licenses: BSD with advertising clause + GPL library
Package: iputils Version: 3:20121221-1 Severity: serious Hello, afaiui ping6.c is released under BSD 4 clause license with advertising clause. OTOH it is using at least one GPL library (gnutls-openssl): gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -O3 -Wstrict-prototypes -Wall -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -c ping6.c -DCAPABILITIES-DUSE_GNUTLS -o ping6.o gcc -Wl,-z,relro ping6.o ping_common.o -lcap -lresolv -lgnutls-openssl -o ping6 Since these two licenses are incompatible the resulting binary is not distributable. cu Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725440: marked as done (javahelper: jh_manifest error causes FTBFS in db, db5.3, db6.0)
Your message dated Sun, 06 Oct 2013 07:03:19 +
with message-id e1vsin5-0007lk...@franck.debian.org
and subject line Bug#725440: fixed in javatools 0.45
has caused the Debian Bug report #725440,
regarding javahelper: jh_manifest error causes FTBFS in db, db5.3, db6.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
725440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: javahelper
Version: 0.44
Severity: serious
For example, from my pbuilder log for db:
...
make[1]: Leaving directory `/tmp/buildd/db-5.1.29'
jh_classpath
jh_manifest
find debian/db5.1-doc '!' \( $dh{EXCLUDE_FIND} \) -a -name '*.jar'
find: paths must precede expression: {EXCLUDE_FIND}
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec]
[path...] [expression]
Can't close(GLOB(0x1c65300)) filehandle: '' at /usr/bin/jh_manifest line 187
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
--
Daniel Schepler
---End Message---
---BeginMessage---
Source: javatools
Source-Version: 0.45
We believe that the bug you reported is fixed in the latest version of
javatools, which is due to be installed in the Debian FTP archive.
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 725...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Niels Thykier ni...@thykier.net (supplier of updated javatools 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...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 06 Oct 2013 08:44:51 +0200
Source: javatools
Binary: jarwrapper javahelper java-propose-classpath
Architecture: source all
Version: 0.45
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers
pkg-java-maintain...@lists.alioth.debian.org
Changed-By: Niels Thykier ni...@thykier.net
Description:
jarwrapper - Run executable Java .jar files
java-propose-classpath - Helper script to suggest a classpath for jar files
javahelper - Helper scripts for packaging Java programs
Closes: 725335 725440
Changes:
javatools (0.45) unstable; urgency=low
.
* jh_manifest: Fix bug where EXCLUDE_FIND was not
properly expanded (regression introduced in 0.44).
Thanks to Daniel Schepler for reporting it.
(Closes: #725440)
* d/control: Fix typo of and. Thanks to Pascal
De Vuyst for reporting it. (Closes: #725335)
Checksums-Sha1:
a80f1116a3378739f452689e2417018ede061cd5 1962 javatools_0.45.dsc
fea570f32986d5317bace16e3a337714d5621d7e 58810 javatools_0.45.tar.gz
81e7b87e585676cb0f20c2ca935b7badce740647 16056 jarwrapper_0.45_all.deb
9ae29a786d3d215f29067dd37faa975abc80296d 83160 javahelper_0.45_all.deb
6594793d658ed768f62400cf9cf010a502834d80 13128
java-propose-classpath_0.45_all.deb
Checksums-Sha256:
62aaf0018b701daa813227b75452c0ba846a5c05e018d9bae0a4044f51792a38 1962
javatools_0.45.dsc
7e55c3b3c64a5d7b1aa3bb3df8dc0722d2b4dc81c0d74cf5ca713d2ccc827c29 58810
javatools_0.45.tar.gz
8ea188215908a0c3f79d0dd061fe5b9b2aa712286bd489a1945d4fd8df4a02a1 16056
jarwrapper_0.45_all.deb
6fe9d657a217e11147467c9adfe916a6db64f8140d69ae4f1a00828827155828 83160
javahelper_0.45_all.deb
202d9e9b7590887e931f3a32305f43025ff10a9b560c94f66306da00dcf8d381 13128
java-propose-classpath_0.45_all.deb
Files:
dcc97d7e1522e94849b7e457dd014aa9 1962 java optional javatools_0.45.dsc
110abff9d0e1775b409412b0a0243ddb 58810 java optional javatools_0.45.tar.gz
287b37688a2261cd83b4ac3367651993 16056 java optional jarwrapper_0.45_all.deb
19392c7bcc7224040ff930d9625e9e3e 83160 java optional javahelper_0.45_all.deb
cef90484271ae84e561fed4843d6db6c 13128 java optional
java-propose-classpath_0.45_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iQIcBAEBCAAGBQJSUQeZAAoJEAVLu599gGRCz2IP/1YAD61Yn4VwfBXVHqcAL3kn
wKEdqypUG6xj40E8T8L/SnRrAqpx8Wuw/zUYgHnPj7ZG2aT79MunaXGYGXfdsZCe
EpaMuLsr8iqD51ScEEIRmE+m7FM4KRIcFy8s1Vtr5h4lYhCii/mG3BfsJN8u0n25
HwPQi5zjffv4BZ1DF/jmmEfzMR/3ms6Zw5fm/QLTn4xunX+hzwzq7wPgt7HZseKv
HGiE8f1NHssvELjZRN2zdV5aEMXVyJizzHHzYs5rjqNJDbf2Bp1LMY7Kz+IHZRGa
SA6S75vz2oZyExSbDwvMpvuxXd2aZF3tj8tQjJ8N/LTbrNncG1Yy6gc8MgUJ7krh
Bug#683042: Blender: debian/copyright: No information of embedded external libraries
Hi Ross! Il 06/ott/2013 00:33 Ross Gammon rossgam...@mail.dk ha scritto: Wow - is there a license that isn't used in the Blender package! I have attached a patch with an updated copyright file where I have included all copyrights/licenses found in the package. Thanks a lot for your massive work! ;-) Gonna give it a look tomorrow and then merge it in git repository, eventually. Thanks a lot for your efforts with this issue. Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A
Bug#725383: FTBFS on kfreebsd-*: SYS_gettid is Linux-specific
I think you can avoid this by using the primitive: lwpid_t tid; syscall (SYS_thr_self, tid); There is a mess in kernel interfaces, the right one is long tid; syscall (SYS_thr_self, tid); But it holds only for current pthread implementation, it can be changed anytime. Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Downgrade
Processing commands for cont...@bugs.debian.org: severity 591969 important Bug #591969 [src:typo3-src] typo3-src: does not build .swf files from source Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 591969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591969 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#707442:
Hi All, The issue is caused by upstream version checking problem [1]. Applying this patch can solved the problem. I just pack a new scim-chewing in [2] with latest release, please help to commit to official repository if there is no problem in it, thanks. [1] https://github.com/chewing/scim-chewing/commit/545279e49f712172715501f0f9873b4d3dfabc34 [2] https://github.com/czchen/debian-scim-chewing -- ChangZhuo Chen (陳昌倬) czc...@gmail.com Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: python2.7: renders python2.7-dbg ( 2.7.3.1) unusable, causes FTBFS
Processing commands for cont...@bugs.debian.org:
# has been OK for quite some time
fixed 700809 2.7.3-15
Bug #700809 {Done: Matthias Klose d...@debian.org} [python2.7] python2.7:
renders python2.7-dbg ( 2.7.3.1) unusable, causes FTBFS
Marked as fixed in versions python2.7/2.7.3-15.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
700809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700809
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#725406: marked as done (FTBFS: build-depend on unavailable python2.6-dev)
Your message dated Sun, 06 Oct 2013 09:18:56 + with message-id e1vskuk-0007eo...@franck.debian.org and subject line Bug#725406: fixed in python-falcon 0.1.7-3 has caused the Debian Bug report #725406, regarding FTBFS: build-depend on unavailable python2.6-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 725406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-falcon Version: 0.1.7-2 Severity: serious Justification: FTBFS Hello, python2.6-dev is no more in sid, python-falcon thus now FTBFS since it build-depends on it. Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel ...[Linux's] capacity to talk via any medium except smoke signals. (By Dr. Greg Wettstein, Roger Maris Cancer Center) ---End Message--- ---BeginMessage--- Source: python-falcon Source-Version: 0.1.7-3 We believe that the bug you reported is fixed in the latest version of python-falcon, which is due to be installed in the Debian FTP archive. 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 725...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated python-falcon 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 09:01:47 + Source: python-falcon Binary: python-falcon python3-falcon Architecture: source amd64 Version: 0.1.7-3 Distribution: unstable Urgency: low Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: python-falcon - supersonic micro-framework for building cloud APIs - Python 2.x python3-falcon - supersonic micro-framework for building cloud APIs - Python 3.x Closes: 725406 Changes: python-falcon (0.1.7-3) unstable; urgency=low . * Reverts the order in the build-depends of python-dev to fix FTBFS. Any backport will have to revert the other way (Closes: #725406). Checksums-Sha1: d4a324cc04c03e0642700a3dd0f0aec89ae08c2c 1738 python-falcon_0.1.7-3.dsc 11be62fbab42f71b2d79589e3a2f6245181ca614 3214 python-falcon_0.1.7-3.debian.tar.gz fdb704dac8d99e84bed9f0264f0e31ee8df2894c 162694 python-falcon_0.1.7-3_amd64.deb 2442d7b1772517cab002b503af2ee03e59e3ae16 34296 python3-falcon_0.1.7-3_amd64.deb Checksums-Sha256: fc483fcb479b5a57895f2a52c0579a3d4cc207dc9cd382fc3d70a245a081d45d 1738 python-falcon_0.1.7-3.dsc 29e664ad0a7cefb309577c5b3e4b8f61000381c2e8ab4cd17b9c67f50bb7a432 3214 python-falcon_0.1.7-3.debian.tar.gz 29db0c26f8eb5d02497e0bc663958bf2c503f35d11be0c0e43a8d23c5352af6f 162694 python-falcon_0.1.7-3_amd64.deb 4fa3ef4981bc3d23d55356db1a0f4663861f5cf284f4ef3630c78dba055a8d59 34296 python3-falcon_0.1.7-3_amd64.deb Files: a53a47a7cec98cc43da7d5a5f34aab54 1738 python optional python-falcon_0.1.7-3.dsc eba2afde7e7ac75617861f1cdc85f21f 3214 python optional python-falcon_0.1.7-3.debian.tar.gz 403178133c1ccee8e78e39ad140aff54 162694 python optional python-falcon_0.1.7-3_amd64.deb 60e2f345b05c09ec891818fc6de1383c 34296 python optional python3-falcon_0.1.7-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlJRJ6IACgkQl4M9yZjvmkl9GgCfT3bJDhU0viCm9kgtMR81resI O28An0pZqGL+KMdGTyHoJTh9E0MHTYSk =6bdR -END PGP SIGNATUREEnd Message---
Bug#725476: ipmitool: FTBFS on kfreebsd
package: ipmitool version: 1.8.13-1 severity: serious Luk, The latest ipmitool upload (1.8.13-1) FTBFS on kfreebsd, preventing migration to testing. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707996: marked as done (util-linux: Needs rebuild against new glibc; causes other packages to FTBFS)
Your message dated Sun, 6 Oct 2013 11:51:45 +0200 with message-id 20131006095143.ga27...@ugent.be and subject line Re: Re: Bug#701385: Block has caused the Debian Bug report #707996, regarding util-linux: Needs rebuild against new glibc; causes other packages to FTBFS 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.) -- 707996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: util-linux Version: 2.20.1-5.4 Severity: serious Justification: ftbfs From the e2fsprogs build: make[1]: Entering directory `/«PKGBUILDDIR»/debian/BUILD-STD/e2fsck' gcc -Wl,-z,relro -static -o e2fsck.static crc32.o dict.o unix.o e2fsck.o super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o b adblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o quota.o recovery.o region.o revoke.o ea_refcount.o rehash.o profile.o prof_err.o logfile.o sigcatcher.o ../lib/libquota.a ../lib/libext2fs.a ../lib/libcom_err.a -lpthread -lblkid -luuid -luuid-luuid ../lib/libe2p.a logfile.o: In function `expand_percent_expression': /«PKGBUILDDIR»/e2fsck/logfile.c:133: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries f rom the glibc version used for linking /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/libblkid.a(env.o): In function `safe_getenv': (.text+0x1be): undefined reference to `__secure_getenv' collect2: error: ld returned 1 exit status make[1]: *** [e2fsck.static] Error 1 This is due to util-linux having libblkid.a built against the old glibc and this is no longer compatible with the new glibc. It just needs a rebuild. According to jcristau this needs a sourceful upload, i.e. not a binNMU, due to it being m-a: same. Regards, Roger -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (550, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages util-linux depends on: ii debconf [debconf-2.0] 1.5.50 ii dpkg 1.16.10 ii initscripts2.88dsf-41+jessie1 ii install-info 5.1.dfsg.1-3 ii libblkid1 2.20.1-5.4 ii libc6 2.17-1 ii libncurses55.9+20130504-1 ii libselinux12.1.13-1 ii libslang2 2.2.4-15 ii libtinfo5 5.9+20130504-1 ii libuuid1 2.20.1-5.4 ii lsb-base 4.1+Debian9 ii tzdata 2013b-2 ii zlib1g 1:1.2.8.dfsg-1 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 3.0.16-2 ii kbd 1.15.5-1 ii util-linux-locales 2.20.1-5.4 -- debconf information excluded ---End Message--- ---BeginMessage--- Version: 2.20.1-5.5 Hi, On Tue, Sep 03, 2013 at 04:52:26PM +0200, Balint Reczey wrote: e2fsprogs built fine for all supported architectures and fails for only powerpcspe from ports [1]. Could we consider this RC bug closed for util-linux? There was another NMU of util-linux (for unrelated reasons), which seems to have fixed the issue (by triggering a rebuild). Cheers, Ivo---End Message---
Processed: fix version for 707996
Processing commands for cont...@bugs.debian.org:
# found version seems to be wrong
notfound 707996 2.20.1-5.5
Bug #707996 {Done: Ivo De Decker ivo.dedec...@ugent.be} [util-linux]
util-linux: Needs rebuild against new glibc; causes other packages to FTBFS
No longer marked as found in versions util-linux/2.20.1-5.5.
notfound 707996 util-linux/2.20.1-5.5
Bug #707996 {Done: Ivo De Decker ivo.dedec...@ugent.be} [util-linux]
util-linux: Needs rebuild against new glibc; causes other packages to FTBFS
Ignoring request to alter found versions of bug #707996 to the same values
previously set
found 707996 2.20.1-5.4
Bug #707996 {Done: Ivo De Decker ivo.dedec...@ugent.be} [util-linux]
util-linux: Needs rebuild against new glibc; causes other packages to FTBFS
Marked as found in versions util-linux/2.20.1-5.4.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
707996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707996
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#701814: Re: Bug#701814: os-prober: damages XFS exported via iSCSI but not mounted locally; potential data loss
Hi, On Sun, May 19, 2013 at 12:11:30AM +0100, Colin Watson wrote: On Sun, Mar 24, 2013 at 01:29:54PM +0100, Ivo De Decker wrote: Is there still a reason to keep trying the regular mount? Are there cases where grub-mount is expected to fail? Maybe only trying grub-mount could be the default. grub-mount is only available on architectures where GRUB has been ported; that's quite a few nowadays, but not all. Furthermore os-prober is used on some other distributions and I don't know if they all have grub-mount available. But it's true that to some extent I was mostly being conservative in falling back to mount, and maybe we could do something better in terms of working out whether grub-mount can reasonably be expected to be available. I had a talk about this with Colin at debconf, and it seems that there aren't that many cases left where grub-mount is not available. It might be best to disable the probing (by default) on all architectures where grub-mount is available. On the architectures where grub-mount isn't available (currently mips, arm* and s390*), the question is whether it makes sense to try to randomly mount other filesystems by default in the hope of finding another OS installation, knowing this might break something. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724226: [Pkg-ime-devel] Bug#724226: input-pad = 1.0.2-1 breaks ibus-input-pad
Hi, On Sat, Oct 05, 2013 at 07:35:42PM +0200, Pino Toscano wrote: ... ... because both input-pad and ibus-input-pad must use the *same* gtk version, be it gtk2 or gtk3, to avoid this clash. Thanks for kind explanation. With the recent upload of ibus-input-pad, I hope I fixed this bug. diff --git a/debian/control b/debian/control index 8d1f110..7bcbbf0 100644 --- a/debian/control +++ b/debian/control @@ -8,9 +8,9 @@ Build-Depends: automake, autotools-dev, intltool (= 0.40.0), - libgtk2.0-dev, + libgtk-3-dev, libibus-1.0-dev, - libinput-pad-dev (= 1.0.0), + libinput-pad-dev (= 1.0.2-2~), libxkbfile-dev, libxklavier-dev (= 4.0), libxml2-dev (= 2.0), diff --git a/debian/rules b/debian/rules index 53c072c..5ba69eb 100755 --- a/debian/rules +++ b/debian/rules @@ -3,4 +3,4 @@ dh $@ override_dh_auto_configure: - dh_auto_configure -- --libexecdir=/usr/lib/ibus + dh_auto_configure -- --libexecdir=/usr/lib/ibus --with-gtk=3.0 Now cleanly with-gtk=3.0. I can input :-) ↛↜↝↡↢↣‰‱⁑℉㍱㎑㎒㎓ Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713617: Bug #713617 presage: FTBFS: ld: ./.libs/libscintilla.a(libscintilla_la-PlatGTK.o): undefined reference to symbol 'lroundf@@GLIBC_2.2.5'
Hi, I've uploaded an updated version of my package presage that fixes this FTBFS bug, as well as updating to a new upstream release and the latest standards version. presage (0.8.9-1) unstable; urgency=low * New upstream release. * Fix FTBFS caused by changes in GTK and Glibc. Closes: #713617 * Fix out-of-date-standards-version lintian warning. * Added missing build dependency. -- Matteo Vescovi matteo.vesc...@yahoo.co.uk Wed, 02 OCt 2013 18:23:01 +0100 To access further information about this package, please visit the following URL: http://mentors.debian.net/package/presage Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/presage/presage_0.8.9-1.dsc I would be grateful if you could upload this for me. Regards, Matteo Vescovi signature.asc Description: OpenPGP digital signature
Bug#701286: upload package to delayed-5 queue
Hi, I've uploaded updated package with fix RC bugs for your package to delayed-5 queue. If something with it, please tell me, then I'll cancel it. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724103: libgtk3-perl: FTBFS: Tests failures
The following link makes me think that the build host has an issue: http://www.torkwrench.com/2011/12/16/d-bus-library-appears-to-be-incorrectly-set-up-failed-to-read-machine-uuid-failed-to-open-varlibdbusmachine-id/ Reading dbus-uuidgen man page, I think the right solution is to run dbus-uuidgen --ensure on the build host (or re-install dbus). HTH -- https://github.com/dod38fr/config-model/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/-o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 721092
Processing commands for cont...@bugs.debian.org: tags 721092 + wheezy Bug #721092 [xul-ext-pentadactyl] xul-ext-pentadactyl: incompatible with iceweasel 17.0.8 Added tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 721092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721092 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#666525: trying to disable ccache locally, failing
Control: severity -1 important
Hi,
First of all: ccache is no longer the default, so this bug should not be RC.
To reproduce the issue, add the following entries to /etc/pbuilderrc and
rebuild the base tarball (it's only easy to reproduce if ccache is in the base
tarball, and not installed afterwards).
CCACHEDIR=/var/cache/pbuilder/ccache
EXTRAPACKAGES=ccache
On Mon, Sep 02, 2013 at 10:48:15PM +0200, Yann Dirson wrote:
Well, here is one that, although arguably kludgy, does works for me:
simply forcing the dpkg-architecture run to write somewhere else.
The main issue is that the ccache dir is owned by the build user, but that it
is enabled for all commands, even those running as root. The real solution is
to make sure that ccache is only used when running as the build user. In that
case this issue goes away.
The attached patch should fix that by adding the CCACHE_DIR environment to the
SUTOUSER command. This means that all other commands (including the
dpkg-architecture which is called by pbuilder-satisfydepends) don't run
ccache.
Cheers,
Ivo
diff --git a/debian/changelog b/debian/changelog
index 295f934..ea52701 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+pbuilder (0.215+nmu1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Only set CCACHE_DIR when running as build user. (closes: #666525)
+
+ -- Ivo De Decker ivo.dedec...@ugent.be Sun, 06 Oct 2013 13:57:31 +0200
+
pbuilder (0.215) unstable; urgency=low
* Do not try to use /dev/shm if /run/shm is not present. (closes: #702811, #702102)
diff --git a/pbuilder-buildpackage b/pbuilder-buildpackage
index 45b1177..fbe2213 100755
--- a/pbuilder-buildpackage
+++ b/pbuilder-buildpackage
@@ -38,7 +38,7 @@ if [ -n $BUILDUSERNAME -a -n $BUILDUSERID ]; then
# should be running later, so it shouldn't matter.
# LOGNAME: set this to shut up some tools.
# su -p : switch to user preserving env vars, we need most of them.
-SUTOUSER=env LD_PRELOAD= LOGNAME=$BUILDUSERNAME su -p $BUILDUSERNAME
+SUTOUSER=LD_PRELOAD= LOGNAME=$BUILDUSERNAME su -p $BUILDUSERNAME
DEBBUILDOPTS=${DEBBUILDOPTS:+$DEBBUILDOPTS }-rfakeroot
EXTRAPACKAGES=${EXTRAPACKAGES} fakeroot
log I: using fakeroot in build.
@@ -92,7 +92,11 @@ fi
recover_aptcache
createbuilduser
+
+CCACHE_ENV=
setup_ccache
+SUTOUSER=env $CCACHE_ENV $SUTOUSER
+
log I: Installing the build-deps
executehooks D
trap saveaptcache_umountproc_cleanbuildplace_trap exit sighup sigpipe
diff --git a/pbuilder-buildpackage-funcs b/pbuilder-buildpackage-funcs
index 3083f03..d480177 100644
--- a/pbuilder-buildpackage-funcs
+++ b/pbuilder-buildpackage-funcs
@@ -109,6 +109,6 @@ function setup_ccache() {
chown -R $BUILDUSERID:$BUILDUSERID $BUILDPLACE/$CCACHEDIR
# Unfortunate difference between pbuilder-style and ccache-style config
# env vars :-/
-export CCACHE_DIR=$CCACHEDIR
+CCACHE_ENV=CCACHE_DIR=$CCACHEDIR
fi
}
Processed: Re: Bug#666525: trying to disable ccache locally, failing
Processing control commands: severity -1 important Bug #666525 [pbuilder] pbuilder fails to create directory under ccache when run with sudo Bug #670651 [pbuilder] pbuilder: Ccache setup likely to fail when starting a pbuilder while another is building Bug #675691 [pbuilder] Cannot remove ccache from pbuilder Bug #675843 [pbuilder] bad umask for CCACHEDIR Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' -- 666525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666525 670651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670651 675691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675691 675843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675843 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#713715: marked as done (lv2proc: FTBFS: ld: main.o: undefined reference to symbol 'logf@@GLIBC_2.2.5')
Your message dated Sun, 6 Oct 2013 13:32:41 +0100 with message-id CAMHuwowhd1CGyR1ruusB0qeCn=taqh54curoj_z3tjr8_bl...@mail.gmail.com and subject line has caused the Debian Bug report #713715, regarding lv2proc: FTBFS: ld: main.o: undefined reference to symbol 'logf@@GLIBC_2.2.5' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lv2proc Version: 0.4.0-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add explicitly the offending lib to LD flags. Relevant part: gcc -pedantic -Wall -Werror -I/usr/include/serd-0 -I/usr/include/sord-0 -I/usr/include/sratom-0 -I/usr/include/lilv-0 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=gnu99 -Wl,--as-needed -Wl,--as-needed -o lv2proc main.o -lsndfile -llilv-0 -ldl -lsratom-0 -lsord-0 -lserd-0 /usr/bin/ld: main.o: undefined reference to symbol 'logf@@GLIBC_2.2.5' /lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/lv2proc_0.4.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. ---End Message--- ---BeginMessage--- Version: 0.5.0-2 -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A---End Message---
Bug#718165: marked as done (din: FTBFS: chmod: cannot access 'debian/din/usr/share/din/m00': No such file or directory)
Your message dated Sun, 06 Oct 2013 12:33:10 + with message-id e1vsnwi-0007ey...@franck.debian.org and subject line Bug#718165: fixed in din 5.2.1-2 has caused the Debian Bug report #718165, regarding din: FTBFS: chmod: cannot access 'debian/din/usr/share/din/m00': 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.) -- 718165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: din Version: 5.2.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130726 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules binary dh binary --parallel --with autoreconf dh_testroot -O--parallel dh_prep -O--parallel dh_auto_install -O--parallel debian/rules override_dh_install make[1]: Entering directory `/«PKGBUILDDIR»' dh_install chmod a+x debian/din/usr/share/din/m00 chmod: cannot access 'debian/din/usr/share/din/m00': No such file or directory make[1]: *** [override_dh_install] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/07/26/din_5.2.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: din Source-Version: 5.2.1-2 We believe that the bug you reported is fixed in the latest version of din, which is due to be installed in the Debian FTP archive. 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 718...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated din 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 13:08:36 +0100 Source: din Binary: din Architecture: source amd64 Version: 5.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: din- digital audio synthesizer Closes: 718165 Changes: din (5.2.1-2) unstable; urgency=medium . [ Margarita Manterola ] * Apply fix to data/Makefile.am to make it work correctly with dh_auto_install (Closes: #718165). * Also fix some minor issues in debian/rules. Checksums-Sha1: e5d281aedf4dc4d1c1123a9602465283c06ad15e 2035 din_5.2.1-2.dsc 38c92e932408f040626e69aa6d2fc682f04c6ed1 3862 din_5.2.1-2.debian.tar.gz 46a72c2953b8fa122cb86ce0ddaa0032d596160e 261288 din_5.2.1-2_amd64.deb Checksums-Sha256: 08260f7e3b215d9e1085671265b88610d49287279d2439d39102e0e18e1e562a 2035 din_5.2.1-2.dsc 2d4e8311b34a2922e570852349aa340e2d0e39a91fcf2f88c53a1843f1d58ba7 3862 din_5.2.1-2.debian.tar.gz cdf236ac5b424f3d8d276682ce4fc50edcf833f6e6d06d862e3e1fe404d2c338 261288 din_5.2.1-2_amd64.deb Files: 41ed60ee63b35e50149cfb8443efc3da 2035 sound optional din_5.2.1-2.dsc d6b30b40b84ce52ccdb57fabddace1d2 3862 sound optional din_5.2.1-2.debian.tar.gz 60dd29b9e66796d28881acd07014ca33 261288 sound optional din_5.2.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJSUVP9AAoJEOikiuUxHXZa5FsP/0sIy5kJBtDVDQDYNPCieCC7 FFLkzsLahY7KxPH3NNLXeU1MrvqRSQ2y3JVfp4FDkM4ZhJDm6QV/ht0whQuiy1AP Pp17DNRMla4Ur3v2/p9pxxUyzo223ubHnqSVHv3/CtVP4z4IiuFH8kWO7XDCOFD5 LXGZLLdV3MA8ejV5XP3e0radDMzXXOMiSZlAAV9sxkE/IShED2QHUXQ0BBhrkN07 fnZM3HmLuVwUXLMGupl4tPwnuQRR15JwZgh8D0GoX2pYxzU0epjHFFZiAXmgFgMN nq7wAXCbm8LhmRvL1ZjX+Nz/YS2iK8U3fulkqNzf3fFof8+Z5eo5O2VAmLLMZ3zJ 0/TnfNE5EYAXOuFPtFC56aqm4EP/D4alEczESP/k/aBb7YW8HuH8aVjB6DUWQ7Vg JiWoJk9N666XObO/1NPiS9VuSjEw0XiJMOIf0CrT/lp5YNxjBwq/EttForIjWYGz f0S/mWsQwezQliw7pit5AAElsoNbTfrQMfSZNbIv2bQOVB8Z66ui71FUnugQ3k8N 13lUOZskg+HFMs+MtZUqmiKltM7iGTB51XSfby7e2Jjo0ZmOvtv+/ncJ2dbPDe5b
Bug#705053: marked as done (jack-rack does not link with -lm)
Your message dated Sun, 06 Oct 2013 12:48:27 + with message-id e1vsnl5-00010o...@franck.debian.org and subject line Bug#713468: fixed in jack-rack 1.4.8~rc1-2 has caused the Debian Bug report #713468, regarding jack-rack does not link with -lm 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.) -- 713468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jack-rack Version: 1.4.8~rc1-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring ubuntu-patch jack-rack FTBFS in Ubuntu because it does not explicitly link with -lm. There's a patch for this already, but it doesn't include -lm even though the upstream bug does include it. So I updated the patch (below). This succeeds in Debian right now because the linker isn't as pedantic as Ubuntu's, but you might want to update this for the future. Thanks diff -Nru jack-rack-1.4.8~rc1/debian/patches/02-gcc45_binutils_gold.patch jack-rack-1.4.8~rc1/debian/patches/02-gcc45_binutils_gold.patch --- jack-rack-1.4.8~rc1/debian/patches/02-gcc45_binutils_gold.patch 2011-05-29 09:11:30.0 + +++ jack-rack-1.4.8~rc1/debian/patches/02-gcc45_binutils_gold.patch 2013-04-09 14:18:14.0 + @@ -1,21 +1,25 @@ Description: Fix FTBFS with newest GCC4.5 and linker. + Updated 2013-04-09 by Robie Basak robie.ba...@canonical.com: + * Added -lm; this is already in the upstream bug. Author: Alessio Treglia ales...@debian.org Forwarded: https://sourceforge.net/apps/trac/jack-rack/ticket/1 Also forwarded to torb...@gmx.de, leslie.pol...@gmx.net, adamsamp...@users.sourceforge.net +Last-Update: 2013-04-09 --- src/Makefile.am |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) jack-rack.orig/src/Makefile.am -+++ jack-rack/src/Makefile.am -@@ -61,7 +61,8 @@ jack_rack_CFLAGS = \ +--- a/src/Makefile.am b/src/Makefile.am +@@ -61,7 +61,9 @@ -DGNOME_DISABLE_DEPRECATED=1 -jack_rack_LDFLAGS = \ +LIBS = \ + -ldl \ ++ -lm \ $(JACK_LIBS) \ $(GTK_LIBS) \ $(GNOMEUI_LIBS) \ ---End Message--- ---BeginMessage--- Source: jack-rack Source-Version: 1.4.8~rc1-2 We believe that the bug you reported is fixed in the latest version of jack-rack, which is due to be installed in the Debian FTP archive. 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 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated jack-rack 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 13:20:07 +0100 Source: jack-rack Binary: jack-rack Architecture: source amd64 Version: 1.4.8~rc1-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: jack-rack - LADSPA effects rack for JACK Closes: 605782 713468 Changes: jack-rack (1.4.8~rc1-2) unstable; urgency=low . [ Alessio Treglia ] * Add jack-rack-patches by Marcos Guglielmetti. * Install jack-rack patches (Closes: #605782). * Update debian/copyright. * Use canonical form for VCS urls. * Bump Standards. * Refresh debian/copyright, meet copyrigh 1.0 format. . [ Jaromír Mikeš ] * Added myself as uploader . [ Sebastian Ramacher ] * Link against -lm since symbols are used from there. Thanks to Robie Basak for the patch (Closes: #713468) Checksums-Sha1: 3934c4ed02a5497650a831561cb57b749b586295 2144 jack-rack_1.4.8~rc1-2.dsc a731575a299fa9acce5568cefdc0384390286229 15905 jack-rack_1.4.8~rc1-2.debian.tar.gz f0388a8f32d5a41a162a8a4a44e524c361800bfe 79998 jack-rack_1.4.8~rc1-2_amd64.deb Checksums-Sha256: 6befbb3f8bcb0bd259a847898f46f98a7be117186529b5f77d18307cea5872db 2144 jack-rack_1.4.8~rc1-2.dsc db84c28a597ab395b3784844245abb03f0990fa631640990ea7fa7ff4fbf5c60 15905 jack-rack_1.4.8~rc1-2.debian.tar.gz 98b8d90873b1abfdb834f6b98056e305e8cdcf4fac5e603b7aea1a513360a255 79998 jack-rack_1.4.8~rc1-2_amd64.deb Files: 7628fc19c8a52840160577964a27f4b6 2144 sound optional jack-rack_1.4.8~rc1-2.dsc
Bug#713468: marked as done (jack-rack: FTBFS: ld: jack_rack-midi_control.o: undefined reference to symbol 'exp@@GLIBC_2.2.5')
Your message dated Sun, 06 Oct 2013 12:48:27 + with message-id e1vsnl5-00010o...@franck.debian.org and subject line Bug#713468: fixed in jack-rack 1.4.8~rc1-2 has caused the Debian Bug report #713468, regarding jack-rack: FTBFS: ld: jack_rack-midi_control.o: undefined reference to symbol 'exp@@GLIBC_2.2.5' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jack-rack Version: 1.4.8~rc1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add explicitly the offending lib to LD flags. Relevant part: gcc -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/libdrm -I/usr/include/harfbuzz -I/usr/include/alsa -I/usr/include/libxml2 -DPKGDATADIR=\/usr/share/jack-rack\ -DPIXMAPDIR=\/usr/share/pixmaps\ -DDTDDIR=\/usr/share/dtds\ -DG_DISABLE_DEPRECATED=1 -DGTK_DISABLE_DEPRECATED=1 -DGDK_DISABLE_DEPRECATED=1 -DGDK_PIXBUF_DISABLE_DEPRECATED=1 -DGNOME_DISABLE_DEPRECATED=1 -g -O2 -o jack-rack jack_rack-midi_window.o jack_rack-midi_control.o jack_rack-wet_dry_controls.o jack_rack-file.o jack_rack-midi.o jack_rack-util.o jack_rack-plugin_settings.o jack_rack-process.o jack_rack-plugin_desc.o jack_rack-plugin_mgr.o jack_rack-ui.o jack_rack-plugin.o jack_rack-port_controls.o jack_rack-plugin_slot.o jack_rack-jack_rack.o jack_rack-lock_free_fifo.o jack_rack-ui_callbacks.o jack_rack-plugin_slot_callbacks.o jack_rack-control_callbacks.o jack_rack-main.o -ldl -ljack -lpthread -lrt -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -llrdf -lasound -lxml2 /usr/bin/ld: jack_rack-midi_control.o: undefined reference to symbol 'exp@@GLIBC_2.2.5' /lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/jack-rack_1.4.8~rc1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: jack-rack Source-Version: 1.4.8~rc1-2 We believe that the bug you reported is fixed in the latest version of jack-rack, which is due to be installed in the Debian FTP archive. 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 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated jack-rack 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 13:20:07 +0100 Source: jack-rack Binary: jack-rack Architecture: source amd64 Version: 1.4.8~rc1-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: jack-rack - LADSPA effects rack for JACK Closes: 605782 713468 Changes: jack-rack (1.4.8~rc1-2) unstable; urgency=low . [ Alessio Treglia ] * Add jack-rack-patches by Marcos Guglielmetti. * Install jack-rack patches (Closes: #605782). * Update debian/copyright. * Use canonical form for VCS urls. * Bump Standards. * Refresh debian/copyright, meet copyrigh 1.0 format. . [ Jaromír Mikeš ]
Processed: tagging 714879
Processing commands for cont...@bugs.debian.org: tags 714879 + pending Bug #714879 [src:webalizer] webalizer: build-depends on obsolete libgd2-noxpm Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 714879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714879 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#713614: marked as done (mp3fs: FTBFS: transcode.c:252:38: error: expected ')' before 'PRIu64')
Your message dated Sun, 06 Oct 2013 13:18:36 + with message-id e1vsoeg-0005up...@franck.debian.org and subject line Bug#713614: fixed in mp3fs 0.32-53-gdc59a10-1 has caused the Debian Bug report #713614, regarding mp3fs: FTBFS: transcode.c:252:38: error: expected ')' before 'PRIu64' 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.) -- 713614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mp3fs Version: 0.31-28-g7b30a54-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 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»/src' CC mp3fs.o CC fuseops.o CC transcode.o transcode.c: In function 'meta_cb': transcode.c:252:38: error: expected ')' before 'PRIu64' snprintf(tmpstr, 10, % PRIu64, ^ transcode.c:253:17: warning: spurious trailing '%' in format [-Wformat=] info.total_samples*1000/info.sample_rate); ^ transcode.c:253:17: warning: spurious trailing '%' in format [-Wformat=] make[2]: *** [transcode.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/mp3fs_0.31-28-g7b30a54-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: mp3fs Source-Version: 0.32-53-gdc59a10-1 We believe that the bug you reported is fixed in the latest version of mp3fs, which is due to be installed in the Debian FTP archive. 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 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated mp3fs 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 13:53:05 +0100 Source: mp3fs Binary: mp3fs Architecture: source amd64 Version: 0.32-53-gdc59a10-1 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: mp3fs - FUSE filesystem for transcoding FLAC to MP3 on the fly Closes: 713614 Changes: mp3fs (0.32-53-gdc59a10-1) unstable; urgency=low . * New upstream snapshot: - Use C++ idiom for string formatting. (Closes: #713614) * Add build-dep on libflac++-dev. * Bump Standards. Checksums-Sha1: cf66c68d59f2a20ebd6d2629f71ae5ce61bc70de 2112 mp3fs_0.32-53-gdc59a10-1.dsc 6264e0c7dad66aeeebfc6eba9b4550faf0661b3b 241291 mp3fs_0.32-53-gdc59a10.orig.tar.bz2 e9a09611e8db6bb8dea5c387f175a31d7e1300a0 2258 mp3fs_0.32-53-gdc59a10-1.debian.tar.gz 784fe892bd7a0761a1b31b43485832ef9e6f9dc4 23768 mp3fs_0.32-53-gdc59a10-1_amd64.deb Checksums-Sha256: d3138d31e99e2da540211eac994136bf8c13d31b266db87303d21901ef677c22 2112 mp3fs_0.32-53-gdc59a10-1.dsc 0503bae6bfa85d005acaf1ef53372e97bbc90b3e6e93b1a6fbbe317c681e515f 241291 mp3fs_0.32-53-gdc59a10.orig.tar.bz2 da3fe1f06dc9f0bc389029ed22b31d3f708852128f810c534a46b9b0713a5b1b 2258 mp3fs_0.32-53-gdc59a10-1.debian.tar.gz b4e29e1204f14325aaba36961b9e7dd41177291aa941b6103a6b76b54db0cc5a 23768 mp3fs_0.32-53-gdc59a10-1_amd64.deb Files: 0cb171eee312d261859ebe1be46990cf 2112 utils optional mp3fs_0.32-53-gdc59a10-1.dsc b9665e96620fbe90c44431e84fc464ef 241291 utils optional mp3fs_0.32-53-gdc59a10.orig.tar.bz2 39aeaa5649552ed5ae33760e2a8a6cf5 2258 utils optional mp3fs_0.32-53-gdc59a10-1.debian.tar.gz cd1474ad45027f09beae48e387b0b9db 23768 utils optional mp3fs_0.32-53-gdc59a10-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJSUWByAAoJEOikiuUxHXZar34QAI5RH0zG/tM8eD17RRsEqTfu
Processed: tagging 710784
Processing commands for cont...@bugs.debian.org: tags 710784 + pending Bug #710784 [webalizer] webalizer: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/webalizer/examples/sample.conf.gz Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 710784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710784 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#713592: marked as done (timemachine: FTBFS: ld: main.o: undefined reference to symbol 'pow@@GLIBC_2.2.5')
Your message dated Sun, 06 Oct 2013 13:33:41 + with message-id e1vsosr-0007ic...@franck.debian.org and subject line Bug#713592: fixed in timemachine 0.3.3-2 has caused the Debian Bug report #713592, regarding timemachine: FTBFS: ld: main.o: undefined reference to symbol 'pow@@GLIBC_2.2.5' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: timemachine Version: 0.3.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Maybe you need to add explicitly the offending lib to LD flags. Relevant part: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -Wl,--as-needed -o timemachine main.o support.o interface.o callbacks.o gtkmeter.o gtkmeterscale.o meters.o threads.o -g -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -ljack -lpthread -lrt-lsndfile-lpthread -lreadline -lcurses /usr/bin/ld: main.o: undefined reference to symbol 'pow@@GLIBC_2.2.5' /lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/timemachine_0.3.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: timemachine Source-Version: 0.3.3-2 We believe that the bug you reported is fixed in the latest version of timemachine, which is due to be installed in the Debian FTP archive. 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 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated timemachine 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 14:13:24 +0100 Source: timemachine Binary: timemachine Architecture: source amd64 Version: 0.3.3-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: timemachine - JACK audio recorder for spontaneous and conservatory use Closes: 713592 Changes: timemachine (0.3.3-2) unstable; urgency=low . * Team upload. * Fix missing linking libraries to prevent FTBFS. (Closes: #713592) * Remove myself from the Uploaders field. Checksums-Sha1: a335e0e136858575f4de14b5f42247c7cf23d819 2100 timemachine_0.3.3-2.dsc c6038e56ef3ddf446af8cba86965f0998db4666b 6182 timemachine_0.3.3-2.debian.tar.gz 87f07b986e629c75d56b286cf4a7e72e9d292152 85720 timemachine_0.3.3-2_amd64.deb Checksums-Sha256: 8587db50c9e92a67de8d5b50c80e3c10c0936bb12a4993563d57b6996db84ee3 2100 timemachine_0.3.3-2.dsc 532d22bde3eb77c89dc1f9109c1c362bb1b41e2a00678f2e472e26f7703dc4fe 6182 timemachine_0.3.3-2.debian.tar.gz 55026a359d6372e22db9ab33123fd19fccc49ac193b5a5763273365dcf5b9c92 85720 timemachine_0.3.3-2_amd64.deb Files: ddea94c914bd4fdd6cbac905bd675e34 2100 sound optional timemachine_0.3.3-2.dsc 50810148220b5bbf33c78ba7fccebe3e 6182 sound optional timemachine_0.3.3-2.debian.tar.gz c45bb3c69288a916c1f15055bc43b872 85720 sound optional timemachine_0.3.3-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJSUWK0AAoJEOikiuUxHXZaDLkP/080baBFfFTlY+8FC8xWb/nb LpCSBwb5osTNF4qx6ewY68q0K49Vz33lZLMyPJ1dmgj7rZOQvTovxBB1c1kgniLg TBtLggRexSDQxH9t17firsVa2cWzWbWZq4X3NJ+M8Nia/bYxDkjkKY/i/yXpl7M7
Processed: Re: Bug#692628: non-free files in upstream tarball (The Software shall be used for Good, not Evil)
Processing commands for cont...@bugs.debian.org: tags 692628 +upstream +pending Bug #692628 [src:parser] non-free files in upstream tarball (The Software shall be used for Good, not Evil) Added tag(s) upstream. Bug #692628 [src:parser] non-free files in upstream tarball (The Software shall be used for Good, not Evil) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 692628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692628 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#692628: non-free files in upstream tarball (The Software shall be used for Good, not Evil)
tags 692628 +upstream +pending thanks On Thu, Nov 8, 2012 at 2:16 AM, Ansgar Burchardt ans...@debian.org wrote: The upstream tarball contains files under the non-free JSON license: % rgrep -l 'The Software shall be used for Good, not Evil.' . ./src/lib/json/JSON_parser.C Fix is available in the upstream cvs: http://cvsview.parser.ru/cgi/viewcvs.cgi/parser3/src/lib/json/ This will be part of upcoming 3.4.3 release (in ~2 weeks). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713104: upload package to delayed-5 queue
On Sun, Oct 06, 2013 at 07:27:11PM +0900, Hideki Yamane wrote: Hi, I've uploaded updated package with fix RC bugs for your package to delayed-5 queue. If something with it, please tell me, then I'll cancel it. Thanks for the NMU. Au contrare, I'm happy for it to go in right now. I'll reschedule your NMU. Sorry for blocking on this; I thought that unnamed developer was uploading the fix. Do you think you could push your NMU to git? It should be writable by all DDs. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: Digital signature
Bug#725383: FTBFS on kfreebsd-*: SYS_gettid is Linux-specific
Petr Salinger: I think you can avoid this by using the primitive: lwpid_t tid; syscall (SYS_thr_self, tid); There is a mess in kernel interfaces, the right one is long tid; syscall (SYS_thr_self, tid); Is there any lwpid_t which isn't long and defined by kernel headers? -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725491: python-uno: ImportError().with_traceback doesn't exists in Python2
Package: python-uno Version: 1:4.1.2-1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, In line 335 of uno.py, exception ImportError() use the method .with_traceback() which is not available in Python2.x but only in Python3.x. This lead to an AttributeError() exception and line 338 will never be reached to raise the correct exception ImportError(). Removing the .with_traceback... part solve the problem. This is the code as it look now: /usr/share/pyshared/uno.py 333: uno_import_exc = ImportError( 334: %s (or '%s.%s' is unknown) % (py_import_exc, name, x) 335: ) Thank you. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-uno depends on: ii libc6 2.17-93 ii libgcc1 1:4.8.1-10 ii libpython2.7 2.7.5-8 ii libreoffice-core 1:4.1.2-1 ii libstdc++64.8.1-10 ii python2.7.5-5 ii uno-libs3 4.1.2-1 ii ure 4.1.2-1 python-uno recommends no packages. python-uno 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
Processed: Re: Bug#725491: python-uno: ImportError().with_traceback doesn't exists in Python2
Processing commands for cont...@bugs.debian.org: found 725491 1:4.1.1~rc1-1 Bug #725491 [python-uno] python-uno: ImportError().with_traceback doesn't exists in Python2 Marked as found in versions libreoffice/1:4.1.1~rc1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 725491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725491 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#725491: python-uno: ImportError().with_traceback doesn't exists in Python2
found 725491 1:4.1.1~rc1-1 thanks Hi, On Sun, Oct 06, 2013 at 04:27:05PM +0200, Tecnosegugio wrote: Package: python-uno Version: 1:4.1.2-1 No... There's no uno.py change between 4.1.1 and 4.1.2. (Diffing in git says says it was introduced in between 4.1.0 and 4.1.1) Severity: grave Tags: patch Justification: renders package unusable Seriously? Why? Yes, it fails when there's a ImportError to throw, but it should work otherwise? I mean, it's there since months now and you only report this now, so it can't be that critical, no? Should be fixed nevertheless, yes. (And be it by phasing out python2 support) In line 335 of uno.py, exception ImportError() use the method .with_traceback() which is not available in Python2.x but only in Python3.x. This lead to an AttributeError() exception and line 338 will never be reached to raise the correct exception ImportError(). Removing the .with_traceback... part solve the problem. Will forward upstream. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#725491: python-uno: ImportError().with_traceback doesn't exists in Python2
Processing commands for cont...@bugs.debian.org: tag 725491 + upstream Bug #725491 [python-uno] python-uno: ImportError().with_traceback doesn't exists in Python2 Added tag(s) upstream. forwarded 725491 https://bugs.freedesktop.org/show_bug.cgi?id=70196 Bug #725491 [python-uno] python-uno: ImportError().with_traceback doesn't exists in Python2 Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=70196'. thanks Stopping processing here. Please contact me if you need assistance. -- 725491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725491 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#725491: python-uno: ImportError().with_traceback doesn't exists in Python2
tag 725491 + upstream forwarded 725491 https://bugs.freedesktop.org/show_bug.cgi?id=70196 thanks Hi, On Sun, Oct 06, 2013 at 04:37:01PM +0200, Rene Engelhard wrote: Will forward upstream. https://bugs.freedesktop.org/show_bug.cgi?id=70196 Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713104: marked as done (f-spot: FTBFS: ./FSpot/GroupSelector.cs(434,57): error CS0170: Use of possibly unassigned field `bounds')
Your message dated Sun, 06 Oct 2013 15:19:19 + with message-id e1vsq75-0004s6...@franck.debian.org and subject line Bug#713104: fixed in f-spot 0.8.2-5.1 has caused the Debian Bug report #713104, regarding f-spot: FTBFS: ./FSpot/GroupSelector.cs(434,57): error CS0170: Use of possibly unassigned field `bounds' 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.) -- 713104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: f-spot Version: 0.8.2-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 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[5]: Entering directory `/«PKGBUILDDIR»/src/Clients/MainApp' MCS ../../../bin/f-spot.exe ./FSpot.UI.Dialog/TagSelectionDialog.cs(20,16): warning CS0108: `FSpot.UI.Dialog.TagSelectionDialog.Run()' hides inherited member `Gtk.Dialog.Run()'. Use the new keyword if hiding was intended /usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll (Location of the symbol related to previous warning) ./FSpot.UI.Dialog/TagSelectionDialog.cs(29,15): warning CS0108: `FSpot.UI.Dialog.TagSelectionDialog.Hide()' hides inherited member `Gtk.Widget.Hide()'. Use the new keyword if hiding was intended /usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll (Location of the symbol related to previous warning) ./FSpot.Widgets/MetadataDisplay.cs(157,22): warning CS0108: `FSpot.Widgets.MetadataDisplayWidget.Visible' hides inherited member `Gtk.Widget.Visible'. Use the new keyword if hiding was intended /usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll (Location of the symbol related to previous warning) ./FSpot.Widgets/PreviewPopup.cs(41,18): warning CS0109: The member `FSpot.PreviewPopup.Item' does not hide an inherited member. The new keyword is not required ./FSpot/SingleView.cs(618,23): warning CS0108: `FSpot.SingleView.PreferenceDialog.Show()' hides inherited member `Gtk.Widget.Show()'. Use the new keyword if hiding was intended /usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll (Location of the symbol related to previous warning) ./FSpot.Widgets/FolderTreeView.cs(148,35): warning CS0618: `FSpot.DragDropTargets.UriListEntry' is obsolete: `Use gtk_target_list_add_uri_target' ./FSpot.Widgets/FolderTreeView.cs(149,35): warning CS0618: `FSpot.DragDropTargets.PlainTextEntry' is obsolete: `better use gtk_target_list_add_text_targets' ./FSpot.Widgets/FolderTreeView.cs(140,21): warning CS0618: `FSpot.DragDropTargets.UriListEntry' is obsolete: `Use gtk_target_list_add_uri_target' ./FSpot.Widgets/FolderTreeView.cs(141,21): warning CS0618: `FSpot.DragDropTargets.PlainTextEntry' is obsolete: `better use gtk_target_list_add_text_targets' ./FSpot.Widgets/InfoBox.cs(705,9): warning CS0612: `Gtk.Object.SetData(string, System.IntPtr)' is obsolete ./FSpot.Widgets/InfoBox.cs(714,9): warning CS0612: `Gtk.Object.SetData(string, System.IntPtr)' is obsolete ./FSpot.Widgets/InfoBox.cs(723,9): warning CS0612: `Gtk.Object.SetData(string, System.IntPtr)' is obsolete ./FSpot.Widgets/InfoBox.cs(732,9): warning CS0612: `Gtk.Object.SetData(string, System.IntPtr)' is obsolete ./FSpot.Widgets/InfoBox.cs(741,9): warning CS0612: `Gtk.Object.SetData(string, System.IntPtr)' is obsolete ./FSpot.Widgets/InfoBox.cs(750,9): warning CS0612: `Gtk.Object.SetData(string, System.IntPtr)' is obsolete ./FSpot.Widgets/InfoBox.cs(759,9): warning CS0612: `Gtk.Object.SetData(string, System.IntPtr)' is obsolete ./FSpot.Widgets/InfoBox.cs(764,46): warning CS0612: `Gtk.Object.GetData(string)' is obsolete ./FSpot.Widgets/MetadataDisplay.cs(64,8): warning CS0108: `FSpot.Widgets.MetadataDisplayWidget.State' hides inherited member `Gtk.Widget.State'. Use the new keyword if hiding was intended /usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll (Location of the symbol related to previous warning) ./FSpot.Widgets/PhotoImageView.cs(238,27): warning CS0618: `FSpot.PhotoLoader' is obsolete: `nuke or rename this' ./FSpot.Widgets/PreviewPopup.cs(115,33): warning CS0618: `FSpot.PhotoLoader' is obsolete: `nuke or rename this' ./FSpot.Widgets/TagEntry.cs(103,5): warning CS0612: `Gtk.Entry.AppendText(string)' is obsolete ./FSpot/App.cs(265,30): warning CS0618: `FSpot.PhotoStore.Query(FSpot.Core.Tag[])' is obsolete: `drop this, use IQueryCondition correctly instead' ./FSpot/App.cs(267,30): warning
Bug#725470: incompatible licenses: BSD with advertising clause + GPL library
On October 6, 2013 at 8:44AM +0200, ametzler (at bebt.de) wrote: afaiui ping6.c is released under BSD 4 clause license with advertising clause. If the copyright holder is the University of California, Berkeley, the advertising clause can be deleted. See also ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change | July 22, 1999 | | To All Licensees, Distributors of Any Version of BSD: | | As you know, certain of the Berkeley Software Distribution (BSD) source | code files require that further distributions of products containing all or | portions of the software, acknowledge within their advertising materials | that such products contain software developed by UC Berkeley and its | contributors. | | Specifically, the provision reads: | | * 3. All advertising materials mentioning features or use of this software | *must display the following acknowledgement: | *This product includes software developed by the University of | *California, Berkeley and its contributors. | | Effective immediately, licensees and distributors are no longer required to | include the acknowledgement within advertising materials. Accordingly, the | foregoing paragraph of those BSD Unix files containing it is hereby deleted | in its entirety. | | William Hoskins | Director, Office of Technology Licensing | University of California, Berkeley Thanks, -- Tatsuya Kinoshita pgpaWMr0NSLoO.pgp Description: PGP signature
Bug#716759: openshot: mlt 0.9.0-1 renames python-mlt5 = python-mlt
Package: openshot Version: 1.4.3-1 Followup-For: Bug #716759 Dear Maintainer, I've got same issue as describe on my Debian Jessie/Testing. Updating openshot .deb package as describe allow software installation. But after, software is affected by this other bug : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698321#10 Best regrads -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) 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 openshot depends on: ii fontconfig 2.10.2-2 ii gtk2-engines-pixbuf 2.24.21-1 ii librsvg2-common 2.36.4-2 ii melt 0.9.0-1 ii python 2.7.5-5 ii python-gtk2 2.24.0-3+b1 ii python-httplib2 0.8-2 ii python-imaging 1.1.7-4 ii python-mlt 0.9.0-1 ii python-pygoocanvas 0.14.1-1+b3 ii python-support 1.0.15 ii python-xdg 0.25-3 Versions of packages openshot recommends: pn frei0r-plugins none pn openshot-docnone Versions of packages openshot suggests: pn blender none pn inkscape none -- 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#725361: openshot is not installable
Package: openshot Version: 1.4.3-1 Followup-For: Bug #725361 Dear Maintainer, this is look like that this bug is the same as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716759 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) 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 openshot depends on: ii fontconfig 2.10.2-2 ii gtk2-engines-pixbuf 2.24.21-1 ii librsvg2-common 2.36.4-2 ii melt 0.9.0-1 ii python 2.7.5-5 ii python-gtk2 2.24.0-3+b1 ii python-httplib2 0.8-2 ii python-imaging 1.1.7-4 ii python-mlt 0.9.0-1 ii python-pygoocanvas 0.14.1-1+b3 ii python-support 1.0.15 ii python-xdg 0.25-3 Versions of packages openshot recommends: pn frei0r-plugins none pn openshot-docnone Versions of packages openshot suggests: pn blender none pn inkscape none -- 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
Processed: tagging 613166
Processing commands for cont...@bugs.debian.org: tags 613166 - pending Bug #613166 [wmbattery] Please stop using HAL Bug #724609 [wmbattery] wmbattery stopped working with kernel 3.10-3 Removed tag(s) pending. Removed tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 613166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613166 724609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724609 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: update found versions for 722664
Processing commands for cont...@bugs.debian.org:
# version tracking is confused by the multiple packages
# this bug is fixed in the other one, so removing this one from found
notfound 722664 ion/3.1.3~dfsg1-1
Bug #722664 {Done: Daniel Pocock dan...@pocock.com.au}
[libion-dev,libmama-dev] libmama-dev and libion-dev: error when trying to
install together
No longer marked as found in versions ion/3.1.3~dfsg1-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
722664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722664
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#713670: marked as done (supercollider: FTBFS: sndfile_backend_test.cpp:46:34: error: expected unqualified-id before numeric constant)
Your message dated Sun, 06 Oct 2013 17:53:05 +0100
with message-id 52519571.60...@pyro.eu.org
and subject line Re: Bug#713670: supercollider: FTBFS:
sndfile_backend_test.cpp:46:34: error: expected unqualified-id before numeric
constant
has caused the Debian Bug report #713670,
regarding supercollider: FTBFS: sndfile_backend_test.cpp:46:34: error: expected
unqualified-id before numeric constant
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.)
--
713670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: supercollider
Version: 1:3.5.3~repack-3
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_progress_report
/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles
[100%] Building CXX object
testsuite/supernova/CMakeFiles/sndfile_backend_test.dir/sndfile_backend_test.cpp.o
cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/testsuite/supernova /usr/bin/g++
-DSC_DATA_DIR=\/usr/share/SuperCollider\ -DSC_LINUX -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security
-Wall -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -I/«PKGBUILDDIR»/include/common
-I/«PKGBUILDDIR»/include/plugin_interface -I/«PKGBUILDDIR»/include/server
-I/«PKGBUILDDIR»/server/supernova
-I/«PKGBUILDDIR»/external_libraries/boost
-I/«PKGBUILDDIR»/external_libraries/boost_endian
-I/«PKGBUILDDIR»/external_libraries/boost_lockfree
-I/«PKGBUILDDIR»/external_libraries/boost_move
-I/«PKGBUILDDIR»/external_libraries/oscpack
-I/«PKGBUILDDIR»/external_libraries
-I/«PKGBUILDDIR»/external_libraries/nova-tt
-I/«PKGBUILDDIR»/external_libraries/TLSF-2.4.6/src-fschedule-insns2
-fomit-frame-pointer -Wreturn-type -fvisibility=hidden -pthread -o
CMakeFiles/sndfile_backend_test.dir/sndfile_backend_test.cpp.o -c
/«PKGBUILDDIR»/testsuite/supernova/sndfile_backend_test.cpp
In file included from /usr/include/pthread.h:24:0,
from
/usr/include/x86_64-linux-gnu/c++/4.8/bits/gthr-default.h:35,
from /usr/include/x86_64-linux-gnu/c++/4.8/bits/gthr.h:148,
from /usr/include/c++/4.8/ext/atomicity.h:33,
from /usr/include/c++/4.8/bits/ios_base.h:39,
from /usr/include/c++/4.8/ios:42,
from /usr/include/c++/4.8/istream:38,
from /usr/include/c++/4.8/sstream:38,
from /usr/include/boost/test/utils/wrap_stringstream.hpp:26,
from /usr/include/boost/test/predicate_result.hpp:20,
from /usr/include/boost/test/test_tools.hpp:19,
from /usr/include/boost/test/unit_test.hpp:19,
from
/«PKGBUILDDIR»/testsuite/supernova/sndfile_backend_test.cpp:1:
/«PKGBUILDDIR»/testsuite/supernova/sndfile_backend_test.cpp: In member
function 'void sndfile_backend_test_1::test_method()':
/«PKGBUILDDIR»/testsuite/supernova/sndfile_backend_test.cpp:46:34: error:
expected unqualified-id before numeric constant
boost::xtime_get(xt, boost::TIME_UTC);
^
In file included from
/«PKGBUILDDIR»/external_libraries/nova-tt/nova-tt/semaphore.hpp:31:0,
from
/«PKGBUILDDIR»/server/supernova/audio_backend/sndfile_backend.hpp:31,
from
/«PKGBUILDDIR»/testsuite/supernova/sndfile_backend_test.cpp:4:
/«PKGBUILDDIR»/external_libraries/nova-tt/nova-tt/semaphore_posix.hpp: In
instantiation of 'void nova::nova_tt::semaphorehas_timed_wait::post() [with
bool has_timed_wait = false]':
/«PKGBUILDDIR»/server/supernova/audio_backend/sndfile_backend.hpp:142:30:
required from 'void nova::sndfile_backendengine_functor, sample_type,
blocking::deactivate_audio() [with engine_functor =
{anonymous}::engine_functor; sample_type = float; bool blocking = false]'
/«PKGBUILDDIR»/testsuite/supernova/sndfile_backend_test.cpp:50:25: required
from here
/«PKGBUILDDIR»/external_libraries/nova-tt/nova-tt/semaphore_posix.hpp:53:13:
warning: unused variable 'status' [-Wunused-variable]
int status = sem_post(sem);
^
/«PKGBUILDDIR»/external_libraries/nova-tt/nova-tt/semaphore_posix.hpp: In
instantiation of 'void nova::nova_tt::semaphorehas_timed_wait::wait() [with
bool has_timed_wait = false]':
Processed: Bug #723733 is a primus bug in Debian (not upstream)
Processing commands for cont...@bugs.debian.org: reassign 723733 primus 0~20130805-1 Bug #723733 [bumblebee] bumblebee: optirun/primusrun don't work - nConfigOptions does not match Bug reassigned from package 'bumblebee' to 'primus'. No longer marked as found in versions bumblebee/3.2.1-4. Ignoring request to alter fixed versions of bug #723733 to the same values previously set Bug #723733 [primus] bumblebee: optirun/primusrun don't work - nConfigOptions does not match Marked as found in versions primus/0~20130805-1. affects 723733 bumblebee Bug #723733 [primus] bumblebee: optirun/primusrun don't work - nConfigOptions does not match Added indication that 723733 affects bumblebee severity 723733 serious Bug #723733 [primus] bumblebee: optirun/primusrun don't work - nConfigOptions does not match Severity set to 'serious' from 'important' notforwarded 723733 Bug #723733 [primus] bumblebee: optirun/primusrun don't work - nConfigOptions does not match Unset Bug forwarded-to-address tags 723733 - upstream Bug #723733 [primus] bumblebee: optirun/primusrun don't work - nConfigOptions does not match Removed tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 723733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723733 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: Bug#713574: aghermann: FTBFS: configure: error: Package requirements
Processing commands for cont...@bugs.debian.org:
# Bug was apparently not in this package;
# must unmark it, otherwise version tracking thinks it is still affected
notfound 713574 aghermann/0.9.0.4-1
Bug #713574 {Done: David Suárez david.sephi...@gmail.com} [src:aghermann]
aghermann: FTBFS: configure: error: Package requirements
No longer marked as found in versions aghermann/0.9.0.4-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
713574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713574
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#725383: FTBFS on kfreebsd-*: SYS_gettid is Linux-specific
Is there any lwpid_t which isn't long and defined by kernel headers?
See upstream sources:
http://svnweb.freebsd.org/base/head/sys/sys/_types.h?revision=255219view=markup
typedef __int32_t __lwpid_t; /* Thread ID (a.k.a. LWP) */
And compare with
http://svnweb.freebsd.org/base/head/sys/kern/syscalls.master?revision=255708view=markup
432 AUE_NULL STD { int thr_self(long *id); }
Petr
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#713565: gwyddion: FTBFS: ../libdraw/gwyrgba.h:24:23: fatal error: gdk/gdkgc.h: No such file or directory
Processing commands for cont...@bugs.debian.org:
# Bug was apparently not in this package;
# must unmark it, otherwise version tracking thinks it is still affected
notfound 713565 gwyddion/2.28-2
Bug #713565 {Done: David Suárez david.sephi...@gmail.com} [src:gwyddion]
gwyddion: FTBFS: ../libdraw/gwyrgba.h:24:23: fatal error: gdk/gdkgc.h: No such
file or directory
No longer marked as found in versions gwyddion/2.28-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
713565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713565
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#712004: marked as done (/usr/lib/apache2/modules/mod_dav_svn.so: undefined symbol: ap_log_perror_)
Your message dated Sun, 06 Oct 2013 17:00:12 + with message-id e1vsrgi-0007kw...@franck.debian.org and subject line Bug#712004: fixed in subversion 1.7.9-1+nmu5 has caused the Debian Bug report #712004, regarding /usr/lib/apache2/modules/mod_dav_svn.so: undefined symbol: ap_log_perror_ 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.) -- 712004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libapache2-svn Version: 1.7.9-1+nmu2 Severity: grave Justification: renders package unusable After libapache2-svn upgrade to 1.7.9-1+nmu2, apache no longer starts if the dav_svn module is enabled: # /etc/init.d/apache2 start [] Starting web server: apache2apache2: Syntax error on line 244 of /etc/apache2/apache2.conf: Syntax error on line 2 of /etc/apache2/mods-enabled/dav_svn.load: Cannot load /usr/lib/apache2/modules/mod_dav_svn.so into server: /usr/lib/apache2/modules/mod_dav_svn.so: undefined symbol: ap_log_perror_ Action 'start' failed. The Apache error log may have more information. failed! A workaround is to disable dav_svn, but this means that libapache2-svn becomes unusable. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libapache2-svn depends on: ii apache2.2-common 2.2.22-13 ii libc6 2.17-5 ii libsvn1 1.7.9-1+nmu2 libapache2-svn recommends no packages. Versions of packages libapache2-svn suggests: pn db5.1-util none -- no debconf information ---End Message--- ---BeginMessage--- Source: subversion Source-Version: 1.7.9-1+nmu5 We believe that the bug you reported is fixed in the latest version of subversion, which is due to be installed in the Debian FTP archive. 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 712...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy james...@debian.org (supplier of updated subversion 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 30 Sep 2013 19:02:34 -0400 Source: subversion Binary: subversion libsvn1 libsvn-dev libsvn-doc libapache2-mod-svn libapache2-svn python-subversion subversion-tools libsvn-java libsvn-perl ruby-svn libsvn-ruby1.8 libsvn-ruby Architecture: source all amd64 Version: 1.7.9-1+nmu5 Distribution: unstable Urgency: low Maintainer: Peter Samuelson pe...@p12n.org Changed-By: James McCoy james...@debian.org Description: libapache2-mod-svn - Apache Subversion server modules for Apache httpd libapache2-svn - Apache Subversion server modules for Apache httpd (dummy package) libsvn-dev - Development files for Apache Subversion libraries libsvn-doc - Developer documentation for libsvn libsvn-java - Java bindings for Apache Subversion libsvn-perl - Perl bindings for Apache Subversion libsvn-ruby - Ruby bindings for Apache Subversion (dummy package) libsvn-ruby1.8 - Ruby bindings for Apache Subversion (dummy package) libsvn1- Shared libraries used by Apache Subversion python-subversion - Python bindings for Apache Subversion ruby-svn - Ruby bindings for Apache Subversion subversion - Advanced version control system subversion-tools - Assorted tools related to Apache Subversion Closes: 712004 725028 Changes: subversion (1.7.9-1+nmu5) unstable; urgency=low . * Non-maintainer upload. * Re-enable libapache2-svn build (Closes: #725028) * Adjust packaging for Apache 2.4 compatibility (Closes: #712004) - Rename libapache2-svn to libapache2-mod-svn and add a transitional package - Add apache2-dev dh-apache2 to Build-Depends - Add apache2-api-20120211 as a Depends for libapache2-mod-svn - Update maintainer scripts to use apache2-maintscript-helper Checksums-Sha1: 25cf757def51a45823d704a0df09300c5e58827a 2332 subversion_1.7.9-1+nmu5.dsc e42d20dc89023a8e48a97451bd4a9495f5c98ce3 233489 subversion_1.7.9-1+nmu5.diff.gz
Bug#713078: marked as done (mrtrix: FTBFS: Package pangox was not found in the pkg-config search path.)
Your message dated Sun, 06 Oct 2013 18:17:40 +0100 with message-id 52519b34.1010...@pyro.eu.org and subject line Bug#713078: mrtrix: FTBFS: Package pangox was not found in the pkg-config search path. has caused the Debian Bug report #713078, regarding mrtrix: FTBFS: Package pangox was not found in the pkg-config search 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.) -- 713078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mrtrix Version: 0.2.10-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' ./build -verbose -debug -system=linux Package pangox was not found in the pkg-config search path. Perhaps you should add the directory containing `pangox.pc' to the PKG_CONFIG_PATH environment variable Package 'pangox', required by 'GdkGLExt', not found WARNING: unable to find gtkmm-2.4 configuration Package pangox was not found in the pkg-config search path. Perhaps you should add the directory containing `pangox.pc' to the PKG_CONFIG_PATH environment variable Package 'pangox', required by 'GdkGLExt', not found Traceback (most recent call last): File ./build, line 220, in module print ' GTK/GL cflags:', ' '.join (cflags_gtkgl) TypeError WARNING: unable to find gtkmm-2.4 configuration Settings: GLib cflags: -pthread -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include GTK cflags:-pthread -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 -I/usr/include/atk-1.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/harfbuzz -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/atkmm-1.6 -I/usr/include/pangomm-1.4 -I/usr/lib/pangomm-1.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/cairomm-1.0/include GTK/GL cflags: make[1]: *** [override_dh_auto_build] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/mrtrix_0.2.10-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--- ---BeginMessage--- Source-Version: 0.2.11-1 New upstream release seems to have fixed this as it is built now.---End Message---
Bug#660939: marked as done (mini-buildd-common: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too)
Your message dated Sun, 06 Oct 2013 17:18:20 + with message-id e1vsryg-0001vf...@franck.debian.org and subject line Bug#660939: fixed in mini-buildd 1.0.0~gamma.1 has caused the Debian Bug report #660939, regarding mini-buildd-common: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too 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.) -- 660939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mini-buildd-common Version: 0.9.6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails From the attached log (scroll to the bottom...): 0m32.0s ERROR: FAIL: Package purging left files on system: /home/mini-buildd not owned This looks very much like a non-system user being created. As putting files into /home is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. cheers, Andreas mini-buildd-common_0.9.6.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: mini-buildd Source-Version: 1.0.0~gamma.1 We believe that the bug you reported is fixed in the latest version of mini-buildd, which is due to be installed in the Debian FTP archive. 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 660...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephan Sürken abs...@debian.org (supplier of updated mini-buildd 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 18:55:09 +0200 Source: mini-buildd Binary: python-mini-buildd mini-buildd mini-buildd-common Architecture: source all Version: 1.0.0~gamma.1 Distribution: unstable Urgency: low Maintainer: Stephan Sürken abs...@debian.org Changed-By: Stephan Sürken abs...@debian.org Description: mini-buildd - Minimal Debian build daemon mini-buildd-common - minimal Debian build daemon - 08x upgrade dummy package python-mini-buildd - Minimal Debian build daemon: python library and user tool Closes: 607189 612310 617673 632955 633074 638301 656746 660939 677618 Changes: mini-buildd (1.0.0~gamma.1) unstable; urgency=low . Initial gamma release; initial upload to unstable. * [3e16e55] html, port[ext]: Use generic templatetag for options; narrow list of dists based on context. * [486afc3] [devel: sed s/echo/printf/g] * [6300acc] [devel: Add some basic mini-buildd-tool calls to standard check] * [4764a21] html(api_show): Improve rollbacks display. * [84534fc] html(home): Minor design fixes. * [8650b81] doc: Finish up the introduction. * [33b237f] notify: Add subject prefix [mini-buildd-ID]. * [9659806] subscriptions: Minor display cosmetics. * [f829bb3] api(subscriptions): Use 'choices' list for actions (Fixes auto-complete). * [58ed076] gnupg: Fixup some implementation kludges. * [1a27e9d] api: Add 'printuploaders' command. * [c723e66] html(log, api_show): Cosmetic fixes. * [fd54987] python-keyring: Workaround the 'No handlers could be found for logger keyring' console warning. * [135c584] mini-buildd-tool: Add note to usage that we use python-keyring. * Closing bugs for good due to the upload to unstable: * Bug fix: fails to install, thanks to Holger Levsen (Closes: #632955). * Bug fix: fails to install, thanks to Holger Levsen (Closes: #656746). * Bug fix: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too, thanks to Andreas Beckmann (Closes: #660939). * Bug fix: creates system user in /home, thanks to Andreas Beckmann (Closes: #677618). * Bug fix: When removing distributions, LVM volumes are not removed, thanks to Stephan Sürken (Closes: #617673). * Bug fix: no space left on device if build needs mor then 4GB disk space, thanks to Ulrich Goettlich (Closes: #607189). * Bug fix: Please add option not to use LVM with schroot, thanks to
Bug#677618: marked as done (mini-buildd-common: creates system user in /home)
Your message dated Sun, 06 Oct 2013 17:18:20 + with message-id e1vsryg-0001vm...@franck.debian.org and subject line Bug#677618: fixed in mini-buildd 1.0.0~gamma.1 has caused the Debian Bug report #677618, regarding mini-buildd-common: creates system user in /home 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.) -- 677618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mini-buildd-common Version: 0.8.20 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package creates a system user with a home directory in /home/$SYSUSER, which is a policy violation. The FHS (which is part of the policy) states: /home : User home directories (optional) /home is a fairly standard concept, but it is clearly a site-specific filesystem. The setup will differ from host to host. Therefore, no program should rely on this location. http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#HOMEUSERHOMEDIRECTORIES System users are usually placed in /var/lib. Possible problems that can arise in case /home is a remote file system: * the local root user may not be allowed to write to /home * $SYSUSER may have different UIDs on different hosts For that particular piuparts test /home has been made unusable. From the attached log (scroll to the bottom...): Selecting previously unselected package mini-buildd-common. (Reading database ... 11674 files and directories currently installed.) Unpacking mini-buildd-common (from .../mini-buildd-common_0.8.20_all.deb) ... Setting up mini-buildd-common (0.8.20) ... Adding system user `mini-buildd' (UID 103) ... Adding new user `mini-buildd' (UID 103) with group `sbuild' ... Creating home directory `/home/mini-buildd' ... Stopped: Couldn't create home directory `/home/mini-buildd': File exists. Removing directory `/home/mini-buildd' ... Removing user `mini-buildd' ... dpkg: error processing mini-buildd-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: mini-buildd-common cheers, Anderas mini-buildd-common_0.8.20.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: mini-buildd Source-Version: 1.0.0~gamma.1 We believe that the bug you reported is fixed in the latest version of mini-buildd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephan Sürken abs...@debian.org (supplier of updated mini-buildd 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 18:55:09 +0200 Source: mini-buildd Binary: python-mini-buildd mini-buildd mini-buildd-common Architecture: source all Version: 1.0.0~gamma.1 Distribution: unstable Urgency: low Maintainer: Stephan Sürken abs...@debian.org Changed-By: Stephan Sürken abs...@debian.org Description: mini-buildd - Minimal Debian build daemon mini-buildd-common - minimal Debian build daemon - 08x upgrade dummy package python-mini-buildd - Minimal Debian build daemon: python library and user tool Closes: 607189 612310 617673 632955 633074 638301 656746 660939 677618 Changes: mini-buildd (1.0.0~gamma.1) unstable; urgency=low . Initial gamma release; initial upload to unstable. * [3e16e55] html, port[ext]: Use generic templatetag for options; narrow list of dists based on context. * [486afc3] [devel: sed s/echo/printf/g] * [6300acc] [devel: Add some basic mini-buildd-tool calls to standard check] * [4764a21] html(api_show): Improve rollbacks display. * [84534fc] html(home): Minor design fixes. * [8650b81] doc: Finish up the introduction. * [33b237f] notify: Add subject prefix [mini-buildd-ID]. * [9659806] subscriptions: Minor display cosmetics. * [f829bb3] api(subscriptions): Use 'choices' list for actions (Fixes auto-complete). * [58ed076] gnupg: Fixup some implementation kludges. * [1a27e9d] api: Add 'printuploaders' command. * [c723e66] html(log,
Processed: fix version for 723607
Processing commands for cont...@bugs.debian.org:
# version tracking doesn't work with found versions in multiple packages
# this bug was fixed in opencaster, remove the found version for tstools
notfound 723607 tstools/1.11-1
Bug #723607 {Done: Thorsten Alteholz deb...@alteholz.de} [opencaster,tstools]
tstools and opencaster: error when trying to install together
No longer marked as found in versions tstools/1.11-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
723607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723607
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 725456
Processing commands for cont...@bugs.debian.org: tags 725456 + confirmed Bug #725456 [src:c3p0] c3p0: FTBFS: Testsuite hangs Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 725456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725456 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#725509: yorick-mpeg: FTBFS: No rule to make target `check.i', needed by `check-dll'
Source: yorick-mpeg Version: 0.1-2 Severity: serious From my pbuilder build log: ... /usr/lib/yorick/lib/codger w mpeg mpeg.i found mpeg.i in current directory cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Ilibavcodec -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -D_FORTIFY_SOURCE=2 -c -o ywrap.o ywrap.c cc -Wl,-z,relro -fPIC -shared -o mpeg.so ympeg.o ywrap.o -Llibavcodec -lavcodec -lm make[2]: Leaving directory `/tmp/buildd/yorick-mpeg-0.1' make[1]: Leaving directory `/tmp/buildd/yorick-mpeg-0.1' dh_auto_test make[1]: Entering directory `/tmp/buildd/yorick-mpeg-0.1' make[1]: *** No rule to make target `check.i', needed by `check-dll'. Stop. make[1]: Leaving directory `/tmp/buildd/yorick-mpeg-0.1' dh_auto_test: make -j1 check returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725510: yorick-gy: FTBFS: No rule to make target `/Make'
Source: yorick-gy Version: 0.0.3-1 Severity: serious From my pbuilder build log: ... fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean make[1]: Entering directory `/tmp/buildd/yorick-gy-0.0.3' Makefile:53: /Make.cfg: No such file or directory Makefile:54: /Makepkg: No such file or directory Makefile:55: /Make: No such file or directory make[1]: *** No rule to make target `/Make'. Stop. make[1]: Leaving directory `/tmp/buildd/yorick-gy-0.0.3' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725511: yorick-gl: FTBFS: No rule to make target `check.i', needed by `check-dll'
Source: yorick-gl Version: 1.1+cvs20070922+dfsg-6 Severity: serious From my pbuilder build log: ... /usr/lib/yorick/lib/codger w yorgl cntrfunc.i glfunc.i found cntrfunc.i in current directory found glfunc.i in current directory cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -D_FORTIFY_SOURCE=2 -c -o ywrap.o ywrap.c cc -Wl,-z,relro -fPIC -shared -o yorgl.so ContourTets3D.o Gradient3D.o isotree.o slicetree.o glPolys.o glStrips.o gltexture.o glcode.o glfunc.o glMouse.o glx11view.o glx11setup.o TriUtil.o dlist3d.o glTarray.o gltexsubs.o glustub.o glGlyph.o oglx.o ywrap.o -lGL -lXext -lX11 -lm make[2]: Leaving directory `/tmp/buildd/yorick-gl-1.1+cvs20070922+dfsg' make[1]: Leaving directory `/tmp/buildd/yorick-gl-1.1+cvs20070922+dfsg' dh_auto_test make[1]: Entering directory `/tmp/buildd/yorick-gl-1.1+cvs20070922+dfsg' make[1]: *** No rule to make target `check.i', needed by `check-dll'. Stop. make[1]: Leaving directory `/tmp/buildd/yorick-gl-1.1+cvs20070922+dfsg' dh_auto_test: make -j1 check returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725513: xprintidle: FTBFS: required file './compile' not found
Source: xprintidle Version: 0.2-7 Severity: serious From my pbuilder build log: ... fakeroot debian/rules clean dh_testdir set -e; for f in aclocal.m4 configure Makefile.in; do if [ ! -f $ff.upstream ]; then cp $f $f.upstream; fi; done autoreconf configure.ac:10: error: required file './compile' not found configure.ac:10: 'automake --add-missing' can install 'compile' autoreconf: automake failed with exit status: 1 make: *** [configure-stamp] Error 1 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725514: xpdf: FTBFS: Unsatisfiable Build-Conflicts on binutils-gold provided by binutils
Source: xpdf
Version: 3.03-11
Severity: serious
From my pbuilder build log:
...
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 9), pkg-config, libxt-dev, libx11-dev, libmotif-dev,
libpoppler-private-dev (= 0.16)
Conflicts: binutils-gold
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in
`/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
dpkg: regarding .../pbuilder-satisfydepends-dummy.deb containing
pbuilder-satisfydepends-dummy:
pbuilder-satisfydepends-dummy conflicts with binutils-gold
binutils provides binutils-gold and is present and installed.
dpkg: warning: ignoring conflict, may proceed anyway!
(Reading database ... 12114 files and directories currently installed.)
Unpacking pbuilder-satisfydepends-dummy (from
.../pbuilder-satisfydepends-dummy.deb) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on debhelper (= 9); however:
Package debhelper is not installed.
pbuilder-satisfydepends-dummy depends on pkg-config; however:
Package pkg-config is not installed.
pbuilder-satisfydepends-dummy depends on libxt-dev; however:
Package libxt-dev is not installed.
pbuilder-satisfydepends-dummy depends on libx11-dev; however:
Package libx11-dev is not installed.
pbuilder-satisfydepends-dummy depends on libmotif-dev; however:
Package libmotif-dev is not installed.
pbuilder-satisfydepends-dummy depends on libpoppler-private-dev (= 0.16);
however:
Package libpoppler-private-dev is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
The following NEW packages will be installed:
bsdmainutils{a} debhelper{a} file{a} fontconfig-config{a}
fonts-dejavu-core{a} gettext{a} gettext-base{a} groff-base{a}
intltool-debian{a} libasprintf0c2{a} libcroco3{a} libexpat1{a} libffi6{a}
libfontconfig1{a} libfreetype6{a} libglib2.0-0{a} libice-dev{a}
libice6{a} libjbig0 libjpeg8{a} liblcms1{a} libmagic1{a}
libmotif-common{a} libmotif-dev{a} libmrm4{a} libopenjpeg2{a}
libpipeline1{a} libpng12-0{a} libpoppler-dev{a} libpoppler-private-dev{a}
libpoppler19{a} libpopt0{a} libpthread-stubs0-dev{a} libsm-dev{a}
libsm6{a} libtiff4{a} libuil4{a} libunistring0{a} libx11-6{a}
libx11-data{a} libx11-dev{a} libxau-dev{a} libxau6{a} libxcb1{a}
libxcb1-dev{a} libxdmcp-dev{a} libxdmcp6{a} libxext6{a} libxft2{a}
libxm4{a} libxml2{a} libxmu6{a} libxrender1{a} libxt-dev{a} libxt6{a}
man-db{a} pkg-config{a} po-debconf{a} ttf-dejavu-core{a} ucf{a} uil{a}
x11-common{a} x11proto-core-dev{a} x11proto-input-dev{a}
x11proto-kb-dev{a} xorg-sgml-doctools{a} xtrans-dev{a}
The following packages are RECOMMENDED but will NOT be installed:
autopoint curl libasprintf-dev libgettextpo-dev libglib2.0-data
libmail-sendmail-perl libx11-doc lynx-cur poppler-data shared-mime-info
wget xml-core
0 packages upgraded, 67 newly installed, 0 to remove and 0 not upgraded.
Need to get 147 kB/22.0 MB of archives. After unpacking 65.8 MB will be used.
The following packages have unmet dependencies:
pbuilder-satisfydepends-dummy : Conflicts: binutils-gold which is a virtual
package.
Unable to resolve dependencies! Giving up...
The following NEW packages will be installed:
bsdmainutils{a} debhelper{a} file{a} fontconfig-config{a}
fonts-dejavu-core{a} gettext{a} gettext-base{a} groff-base{a}
intltool-debian{a} libasprintf0c2{a} libcroco3{a} libexpat1{a} libffi6{a}
libfontconfig1{a} libfreetype6{a} libglib2.0-0{a} libice-dev{a}
libice6{a} libjbig0 libjpeg8{a} liblcms1{a} libmagic1{a}
libmotif-common{a} libmotif-dev{a} libmrm4{a} libopenjpeg2{a}
libpipeline1{a} libpng12-0{a} libpoppler-dev{a} libpoppler-private-dev{a}
libpoppler19{a} libpopt0{a} libpthread-stubs0-dev{a} libsm-dev{a}
libsm6{a} libtiff4{a} libuil4{a} libunistring0{a} libx11-6{a}
libx11-data{a} libx11-dev{a} libxau-dev{a} libxau6{a} libxcb1{a}
libxcb1-dev{a} libxdmcp-dev{a} libxdmcp6{a} libxext6{a} libxft2{a}
libxm4{a} libxml2{a} libxmu6{a} libxrender1{a} libxt-dev{a} libxt6{a}
man-db{a} pkg-config{a} po-debconf{a} ttf-dejavu-core{a} ucf{a} uil{a}
x11-common{a} x11proto-core-dev{a} x11proto-input-dev{a}
x11proto-kb-dev{a} xorg-sgml-doctools{a} xtrans-dev{a}
The following packages are RECOMMENDED but will NOT be installed:
autopoint curl libasprintf-dev libgettextpo-dev libglib2.0-data
libmail-sendmail-perl libx11-doc lynx-cur poppler-data shared-mime-info
Bug#722662: marked as done (yorick and gist: error when trying to install together)
Your message dated Sun, 06 Oct 2013 18:18:16 + with message-id e1vssug-0001z5...@franck.debian.org and subject line Bug#722662: fixed in gist 4.1.1-2 has caused the Debian Bug report #722662, regarding yorick and gist: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 722662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gist,yorick Version: gist/4.0.3-2 Version: yorick/2.2.02+dfsg-6+b1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-09-13 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libffi6 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libyaml-0-2 libruby1.9.1 ruby1.9.1 ruby ruby-json gist yorick-data yorick Authentication warning overridden. Selecting previously unselected package libffi6:amd64. (Reading database ... 10882 files and directories currently installed.) Unpacking libffi6:amd64 (from .../libffi6_3.0.13-4_amd64.deb) ... Selecting previously unselected package libxau6:amd64. Unpacking libxau6:amd64 (from .../libxau6_1%3a1.0.8-1_amd64.deb) ... Selecting previously unselected package libxdmcp6:amd64. Unpacking libxdmcp6:amd64 (from .../libxdmcp6_1%3a1.1.1-1_amd64.deb) ... Selecting previously unselected package libxcb1:amd64. Unpacking libxcb1:amd64 (from .../libxcb1_1.9.1-3_amd64.deb) ... Selecting previously unselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.6.1-1_all.deb) ... Selecting previously unselected package libx11-6:amd64. Unpacking libx11-6:amd64 (from .../libx11-6_2%3a1.6.1-1_amd64.deb) ... Selecting previously unselected package libyaml-0-2:amd64. Unpacking libyaml-0-2:amd64 (from .../libyaml-0-2_0.1.4-2_amd64.deb) ... Selecting previously unselected package libruby1.9.1. Unpacking libruby1.9.1 (from .../libruby1.9.1_1.9.3.448-1_amd64.deb) ... Selecting previously unselected package ruby1.9.1. Unpacking ruby1.9.1 (from .../ruby1.9.1_1.9.3.448-1_amd64.deb) ... Selecting previously unselected package ruby. Unpacking ruby (from .../ruby_1%3a1.9.3_all.deb) ... Selecting previously unselected package ruby-json. Unpacking ruby-json (from .../ruby-json_1.8.0-1_amd64.deb) ... Selecting previously unselected package gist. Unpacking gist (from .../archives/gist_4.0.3-2_all.deb) ... Selecting previously unselected package yorick-data. Unpacking yorick-data (from .../yorick-data_2.2.02+dfsg-6_all.deb) ... Selecting previously unselected package yorick. Unpacking yorick (from .../yorick_2.2.02+dfsg-6+b1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/yorick_2.2.02+dfsg-6+b1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/gist.1.gz', which is also in package gist 4.0.3-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Processing triggers for install-info ... Errors were encountered while processing: /var/cache/apt/archives/yorick_2.2.02+dfsg-6+b1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/gist /usr/share/man/man1/gist.1.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage---
Bug#701400: marked as done (lbzip2: ftbfs with eglibc-2.17)
Your message dated Sun, 06 Oct 2013 19:30:59 +0100 with message-id 5251ac63.9000...@pyro.eu.org and subject line Bug#701400: lbzip2: ftbfs with eglibc-2.17 has caused the Debian Bug report #701400, regarding lbzip2: ftbfs with eglibc-2.17 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.) -- 701400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:lbzip2 Version: 2.2-2 Severity: important Tags: sid jessie User: debian-gl...@lists.debian.org Usertags: ftbfs-glibc-2.17 The package fails to build in a test rebuild on at least amd64 with eglibc-2.17, but succeeds to build with eglibc-2.13. The severity of this report may be raised before the jessie release. The test rebuild was done together with GCC-4.8, so some issues might be caused by the updated GCC as well. ./stdio.h:1029:1: error: 'gets' undeclared here (not in a function) The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/lbzip2_2.2-2_unstable_gcc48.log The last lines of the build log are at the end of this report. To install eglibc from experimental, apt-get -t experimental install libc6-dev To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev [...] config.status: creating Makefile config.status: creating src/Makefile config.status: creating lib/Makefile config.status: creating man/Makefile config.status: creating tests/Makefile config.status: creating lib/config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build -a make -j1 make[1]: Entering directory `/«PKGBUILDDIR»' Making all in lib make[2]: Entering directory `/«PKGBUILDDIR»/lib' GENalloca.h GENc++defs.h GENarg-nonnull.h GENwarn-on-use.h GENfcntl.h GENinttypes.h GENmath.h GENstdio.h GENstdlib.h GENstring.h GENsys/stat.h GENsys/time.h GENtime.h GENunistd.h GENwchar.h make all-recursive make[3]: Entering directory `/«PKGBUILDDIR»/lib' make[4]: Entering directory `/«PKGBUILDDIR»/lib' CC dtotimespec.o CC fseterr.o In file included from fseterr.h:20:0, from fseterr.c:20: ./stdio.h:1029:1: error: 'gets' undeclared here (not in a function) _GL_WARN_ON_USE (gets, gets is a security hole - use fgets instead); ^ make[4]: *** [fseterr.o] Error 1 make[4]: Leaving directory `/«PKGBUILDDIR»/lib' make[3]: *** [all-recursive] Error 1 make[2]: *** [all] Error 2 make[3]: Leaving directory `/«PKGBUILDDIR»/lib' make[2]: Leaving directory `/«PKGBUILDDIR»/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Version: 2.2-2 This was a problem in dependency gnulib, since fixed.---End Message---
Bug#725516: lbzip2: FTBFS: problems running testsuite
Package: lbzip2 Version: 2.2-2 Tags: jessie sid Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, There seem to be some problems running the testsuite during build, which I don't think are specific to my architecture (kfreebsd-amd64) : make check-TESTS make[2]: Entering directory `/home/steven/lbzip2-2.2/tests' make[3]: Entering directory `/home/steven/lbzip2-2.2/tests' ./Tester: line 27: tmp./bin/bash.1.21252: No such file or directory ./Tester: line 28: tmp./bin/bash.2.21252: No such file or directory ./Tester: line 27: tmp./bin/bash.1.21266: No such file or directory ./Tester: line 28: tmp./bin/bash.2.21266: No such file or directory ./Tester: line 27: tmp./bin/bash.1.21280: No such file or directory Tester tries to use '$1' to uniquely identify the test that is running, but the invocation seems to be: /bin/bash ./Tester /bin/bash ../build-aux/test-driver --test-name $f Even if I omit using the $bn part, it still fails for another unexplained reason: make[4]: Leaving directory `/home/steven/lbzip2-2.2/tests' fatal: making test-suite.log: failed to create 32767.bz2.trs fatal: making test-suite.log: failed to create 32767.bz2.log fatal: making test-suite.log: failed to create ch255.bz2.trs fatal: making test-suite.log: failed to create ch255.bz2.log fatal: making test-suite.log: failed to create concat.bz2.trs -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#701400: lbzip2: ftbfs with eglibc-2.17
Processing commands for cont...@bugs.debian.org:
notfixed 701400 2.2-2
Bug #701400 {Done: Steven Chamberlain ste...@pyro.eu.org} [src:lbzip2]
lbzip2: ftbfs with eglibc-2.17
No longer marked as fixed in versions 2.2-2.
notfound 701400 lbzip2/2.2-2
Bug #701400 {Done: Steven Chamberlain ste...@pyro.eu.org} [src:lbzip2]
lbzip2: ftbfs with eglibc-2.17
No longer marked as found in versions lbzip2/2.2-2.
fixed 701400 lbzip2/2.2-2
Bug #701400 {Done: Steven Chamberlain ste...@pyro.eu.org} [src:lbzip2]
lbzip2: ftbfs with eglibc-2.17
Marked as fixed in versions lbzip2/2.2-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
701400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701400
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: #724102: pandoc misses recommends on pandoc-data (was: Re: Bug#724102: umegaya: FTBFS: pandoc ...)
Processing commands for cont...@bugs.debian.org: affects 724102 purity-ng gally Bug #724102 [pandoc] Please have pandoc depend on pandoc-data Added indication that 724102 affects purity-ng and gally block 724092 with 724102 Bug #724092 [src:flashcache] flashcache: FTBFS: pandoc: /usr/share/pandoc/data/templates/default.man: openBinaryFile: does not exist (No such file or directory) 724092 was not blocked by any bugs. 724092 was not blocking any bugs. Added blocking bug(s) of 724092: 724102 block 724129 with 724102 Bug #724129 [src:flvmeta] flvmeta: FTBFS: pandoc: /usr/share/pandoc/data/templates/default.man: openBinaryFile: does not exist (No such file or directory) 724129 was not blocked by any bugs. 724129 was not blocking any bugs. Added blocking bug(s) of 724129: 724102 block 723876 with 724102 Bug #723876 [git-ftp] git-ftp: FTBFS: pandoc error 723876 was not blocked by any bugs. 723876 was not blocking any bugs. Added blocking bug(s) of 723876: 724102 block 724114 with 724102 Bug #724114 [src:rhinote] rhinote: FTBFS: pandoc: /usr/share/pandoc/data/templates/default.man: openBinaryFile: does not exist (No such file or directory) 724114 was not blocked by any bugs. 724114 was not blocking any bugs. Added blocking bug(s) of 724114: 724102 block 724107 with 724102 Bug #724107 [src:sshuttle] sshuttle: FTBFS: pandoc: /usr/share/pandoc/data/templates/default.man: openBinaryFile: does not exist (No such file or directory) 724107 was not blocked by any bugs. 724107 was not blocking any bugs. Added blocking bug(s) of 724107: 724102 block 724088 with 724102 Bug #724088 [src:tempest-for-eliza] tempest-for-eliza: FTBFS: pandoc: /usr/share/pandoc/data/templates/default.man: openBinaryFile: does not exist (No such file or directory) 724088 was not blocked by any bugs. 724088 was not blocking any bugs. Added blocking bug(s) of 724088: 724102 thanks Stopping processing here. Please contact me if you need assistance. -- 723876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723876 724088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724088 724092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724092 724102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724102 724107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724107 724114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724114 724129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724129 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: severity of 725496 is grave
Processing commands for cont...@bugs.debian.org: severity 725496 grave Bug #725496 [apt-listbugs] de/LC_MESSAGES/apt-listbugs.mo: unknown encoding name - utf8 (ArgumentError) Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 725496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725496 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#713205: marked as done (transmageddon: FTBFS: aclocal: error: couldn't open directory 'm4': No such file or directory)
Your message dated Sun, 06 Oct 2013 19:03:26 + with message-id e1vstby-000881...@franck.debian.org and subject line Bug#713205: fixed in transmageddon 0.25-2 has caused the Debian Bug report #713205, regarding transmageddon: FTBFS: aclocal: error: couldn't open directory 'm4': 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.) -- 713205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: transmageddon Version: 0.25-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 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 build --with autoreconf,python3 dh_testdir dh_autoreconf aclocal: error: couldn't open directory 'm4': No such file or directory autoreconf: aclocal failed with exit status: 1 dh_autoreconf: autoreconf -f -i returned exit code 1 make: *** [build] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/transmageddon_0.25-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: transmageddon Source-Version: 0.25-2 We believe that the bug you reported is fixed in the latest version of transmageddon, which is due to be installed in the Debian FTP archive. 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 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated transmageddon 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Oct 2013 19:55:07 +0100 Source: transmageddon Binary: transmageddon Architecture: source all Version: 0.25-2 Distribution: unstable Urgency: low Maintainer: Alessio Treglia ales...@debian.org Changed-By: Alessio Treglia ales...@debian.org Description: transmageddon - video transcoder for Linux and Unix systems built using GStreamer Closes: 713205 Changes: transmageddon (0.25-2) unstable; urgency=low . * Set priority to extra (as per Debian Policy 2.5). * Create m4 directory if it doesn't exist before calling dh_autoreconf. (Closes: #713205) Checksums-Sha1: 7a225e953f2a93fa441e804dfafeea55b1ce429f 2074 transmageddon_0.25-2.dsc 2e9a028e30a7e2ea77e9fdfe31b0022725fbd0c4 4604 transmageddon_0.25-2.debian.tar.gz d96d3e2687a110568b1854f9aded532a47eb4192 76044 transmageddon_0.25-2_all.deb Checksums-Sha256: 81b3269ba09c4c05da6e95d688585368c162abd495ecf242e2a00f39407fb013 2074 transmageddon_0.25-2.dsc 0fa87c0a3bae9d8f251da05eb29fc80c077b1e5f36bd787d0b5d0a0e47a46609 4604 transmageddon_0.25-2.debian.tar.gz a6c9bb30bd18dda8980ac19ea799d406f8f1599ed1887b8b44c24c48a183d042 76044 transmageddon_0.25-2_all.deb Files: 480cbb302cb92e884621a907347f20fa 2074 video extra transmageddon_0.25-2.dsc 2307b68f043c8adf8b4316de744b3d11 4604 video extra transmageddon_0.25-2.debian.tar.gz 33ee3a335b3d0354bb39e5b6d9fd6d16 76044 video extra transmageddon_0.25-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJSUbMcAAoJEOikiuUxHXZamYsP/0EDr1X6dg4lF2+Eq+iq70s7 yrW5yJ+MxGv57kjdzLVRvdqMAcsEpZac/Q3WZvEA/8UJEpZXXjldbPj3EgIV2fzi ytRyWh3nDaOKgJAa31msprNZ2Q2tgIiQqcoZaz1feov1g12LiqZGAxI6w3XbaNWm bWe4GR/9o2eWyspDxTttRcSPp2l0jt755xJnOR1tPvdxKsfLKabsqEQN+uDWK9eT WL5RboozrUriQu/ePjbNfhJ9ODiiG7FHgqhJsNr2XUKTFiyRZFK/Y457eFyvS+Xj yncLNdAiAms1qbX3NovwOlIkJaxFPEL7N081IvkPxsWR++wQCq3PgccjLjri1KR3 Psyxov9MnqnskaRdc/LJGeOqvprkmNAk/45VYSSWMUSURG+/gE4qkZtTl2T/x/bb 61o+Pf2Rwt3lnher/M7UKtoODQ2NJErXYwfD2AV6WVnCFVO3biICAxo4BDkvSp6K I6VKecIYKZIKKPHGC470DXnWiJKo1ML41g6pcLtN/aeoRKkrPGPa1cHSP4D2UOjV L+OlT00xU/UOGDl5Awh/uvVgeoS6Pqx+wPnOyIJAH6hRWjAoCU6CT6p9H3tAe2hQ
Bug#723034: marked as done (davfs2: CVE-2013-4362: Unsecure use of system())
Your message dated Sun, 06 Oct 2013 19:02:04 +
with message-id e1vstae-0007gb...@franck.debian.org
and subject line Bug#723034: fixed in davfs2 1.4.6-1.1+deb7u1
has caused the Debian Bug report #723034,
regarding davfs2: CVE-2013-4362: Unsecure use of system()
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
723034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: davfs2
Version: 1.4.6-1.1
Severity: critical
Tags: patch, security, upstream
davfs2 calls function system several times. Because davfs2 is setuid
root in many cases this will allow for privilege escalation.
Appended are patches for version 1.4.6 and 1.4.7 that will fix this bug.
Note: as a consequence davfs2 will no longer try to insert required
kernel modules or create device special files /dev/fuse or /dev/codaX.
So the user has to make sure that one of these devices exists before
mounting a davfs2 file system. As far as I can see /dev/fuse is created
by default on Debian systems. davfs2 uses /dev/fuse by default (and
not /dev/codaX). So this bug fix should not cause any problem on Debian
systems.
Werner (upstream maintainer)
diff -ur davfs2-1.4.6/ChangeLog davfs2-1.4.6.new/ChangeLog
--- davfs2-1.4.6/ChangeLog 2010-04-30 21:17:15.0 +0200
+++ davfs2-1.4.6.new/ChangeLog 2013-09-15 11:05:42.0 +0200
@@ -1,6 +1,11 @@
ChangeLog for davfs2
+2013-09-08 Werner Baumann (werner.baum...@onlinehome.de)
+* kernel_interface.c, mount_davfs.c:
+ Don't create /dev/coda and /dev/fuse.
+ Remove insecure calls of system().
+
2010-04-30 Werner Baumann (werner.baum...@onlinehome.de)
* Released version 1.4.6
Nur in davfs2-1.4.6.new: ChangeLog~.
diff -ur davfs2-1.4.6/src/kernel_interface.c davfs2-1.4.6.new/src/kernel_interface.c
--- davfs2-1.4.6/src/kernel_interface.c 2010-02-16 20:29:54.0 +0100
+++ davfs2-1.4.6.new/src/kernel_interface.c 2013-09-15 11:07:07.0 +0200
@@ -168,27 +168,6 @@
}
if (*dev = 0) {
-system(/sbin/modprobe coda /dev/null);
-minor = 0;
-while (*dev = 0 minor MAX_CODADEVS) {
-char *path;
-if (asprintf(path, %s/%s%i,
- DAV_DEV_DIR, CODA_DEV_NAME, minor) 0)
-abort();
-*dev = open(path, O_RDWR | O_NONBLOCK);
-if (*dev = 0) {
-if (mknod(path, S_IFCHR, makedev(CODA_MAJOR, minor)) == 0) {
-chown(path, 0, 0);
-chmod(path, S_IRUSR | S_IWUSR);
-*dev = open(path, O_RDWR | O_NONBLOCK);
-}
-}
-free(path);
-++minor;
-}
-}
-
-if (*dev = 0) {
error(0, 0, _(no free coda device to mount));
return -1;
}
@@ -223,24 +202,6 @@
abort();
*dev = open(path, O_RDWR | O_NONBLOCK);
-if (*dev = 0) {
-system(/sbin/modprobe fuse /dev/null);
-*dev = open(path, O_RDWR | O_NONBLOCK);
-}
-if (*dev = 0) {
-if (mknod(path, S_IFCHR, makedev(FUSE_MAJOR, FUSE_MINOR)) == 0) {
-chown(path, 0, 0);
-chmod(path, S_IRUSR | S_IWUSR);
-*dev = open(path, O_RDWR | O_NONBLOCK);
-}
-}
-
-free(path);
-if (*dev = 0) {
-error(0, 0, _(can't open fuse device));
-return -1;
-}
-
if (*buf_size (FUSE_MIN_READ_BUFFER + 4096)) {
*buf_size = FUSE_MIN_READ_BUFFER + 4096;
}
Nur in davfs2-1.4.6.new/src: kernel_interface.c~.
diff -ur davfs2-1.4.6/src/mount_davfs.c davfs2-1.4.6.new/src/mount_davfs.c
--- davfs2-1.4.6/src/mount_davfs.c 2010-01-21 19:50:15.0 +0100
+++ davfs2-1.4.6.new/src/mount_davfs.c 2013-09-15 11:13:18.0 +0200
@@ -170,6 +170,9 @@
static int
arg_to_int(const char *arg, int base, const char *opt);
+static void
+cp_file(const char *src, const char *dest);
+
static int
debug_opts(const char *s);
@@ -533,10 +536,7 @@
char *file_name = ne_concat(path, /, DAV_CONFIG, NULL);
if (access(file_name, F_OK) != 0) {
char *template = ne_concat(DAV_DATA_DIR, /, DAV_CONFIG, NULL);
-char *command = ne_concat(cp , template, , file_name,
- NULL);
-system(command);
-free(command);
+cp_file(template, file_name);
free(template);
}
free(file_name);
@@ -545,11 +545,7 @@
if (access(file_name, F_OK)
Bug#701386: acct: ftbfs with eglibc-2.17
Hi, On Wed, 10 Jul 2013 20:58:02 +0200, gregor herrmann wrote: The patch (debian/patches/gnulib-c11-compat.patch) fixes #701386, but What/where is that patch? I notice the build doesn't get that far any more without first doing: $ fakeroot debian/rules config.status $ automake --add-missing I'm not sure if the texinfo problem still happens. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725524: acl2: FTBFS: Segmentation fault
Source: acl2 Version: 6.3-1 Severity: serious Justification: FTBFS Hi, your package FTBFS on all archs: | make[2]: Leaving directory `/«PKGBUILDDIR»' | make[1]: Leaving directory `/«PKGBUILDDIR»' | mv *saved_acl2.gcl saved_acl2 | /usr/bin/make mini-proveall | make[1]: Entering directory `/«PKGBUILDDIR»' | Segmentation fault | make[1]: *** [mini-proveall] Error 139 mipsel additionally logs stuff about rlimit: | /usr/bin/make mini-proveall | make[1]: Entering directory `/«PKGBUILDDIR»' | Cannot set stack rlimit | /bin/sh: line 1: 20333 Doneecho '(value :q) (lp) (mini-proveall)' | 20334 Segmentation fault | ./saved_acl2 mini-proveall.out | make[1]: *** [mini-proveall] Error 139 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725525: gmic: FTBFS due to harcoded compiler flags: '-mtune=generic'
Source: gmic Version: 1.5.7.1-1 Severity: serious Justification: FTBFS Hi, your package FTBFS on all non x86 architectures with messages like: | g++: error: unrecognized argument in option '-mtune=generic' (slight various across architectures) Build logs: https://buildd.debian.org/status/package.php?p=gmicsuite=sid Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725529: viking: FTBFS: automake-1.13: command not found
Source: viking Version: 1.4.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' Making all in src make[2]: Entering directory `/«PKGBUILDDIR»/src' cd .. automake-1.13 --gnu src/Makefile /bin/bash: line 10: automake-1.13: command not found make[2]: *** [Makefile.in] Error 127 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/viking_1.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#725527: nomnom: FTBFS: automake errors
Source: nomnom Version: 0.3.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh build --with autoreconf dh_testdir dh_autoreconf configure.ac:17: installing 'config.aux/compile' automake: warnings are treated as errors src/Makefile.am:75: warning: source file 'about/naboutdialog.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. src/Makefile.am:75: warning: source file 'detect/ndetectdialog.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'detect/ndetect.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'errorwhile/nerrorwhiledialog.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'feed/nfeeddialog_properties.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'feed/nfeedprogressdialog.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'feed/nfeeddialog_items.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'feed/nfeeddialog.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'feed/nfeed.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'lang/nlang.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'log/nlogdialog_recent.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'log/nrecentmutator.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'log/nrecententry.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'log/nlogdialog.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog_options_appearance.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog_options_behaviour.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog_options_systray.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog_commands.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog_download.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog_options.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog_proxy.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsmutator.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettingsdialog.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'settings/nsettings.cpp' is in a subdirectory, src/Makefile.am:75: but option 'subdir-objects' is disabled src/Makefile.am:75: warning: source file 'systray/nsystray.cpp' is in a subdirectory, src
Bug#725526: getdata: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
Source: getdata Version: 0.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules clean test -x debian/rules rm -f debian/stamp-makefile-build debian/stamp-makefile-install /usr/bin/make -C . CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-z,relro -k clean make[1]: Entering directory `/«PKGBUILDDIR»' rm --force getData.1 getData.txt make[1]: Leaving directory `/«PKGBUILDDIR»' dh_clean dpkg-source -b getdata-0.1 dpkg-source: warning: unknown information field 'Dm-Upload-Allowed' in input data in general section of control info file dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision dpkg-buildpackage: error: dpkg-source -b getdata-0.1 gave error exit status 255 Build finished at 20131005-1255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/getdata_0.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725530: gpe-expenses: FTBFS: configure.ac:12: error: required file './compile' not found
Source: gpe-expenses Version: 0.1.9-3 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build test -x debian/rules mkdir -p . autoreconf -fs configure.ac:34: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see: configure.ac:34: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation configure.ac:319: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged. configure.ac:319: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead, configure.ac:319: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files. configure.ac:12: error: required file './compile' not found configure.ac:12: 'automake --add-missing' can install 'compile' Makefile.am:11: warning: shell [ ! -f src/translate.h ] ./src/translate.sh: non-POSIX variable name Makefile.am:11: (probably a GNU make extension) autoreconf: automake failed with exit status: 1 make: *** [makebuilddir] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/gpe-expenses_0.1.9-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on 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#725534: gummi: FTBFS: automake errors
Source: gummi Version: 0.6.5-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' dh_autoreconf --as-needed automake: warnings are treated as errors src/Makefile.am:11: warning: source file 'compile/texlive.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. src/Makefile.am:11: warning: source file 'compile/latexmk.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'compile/rubber.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-menu.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-tabmanager.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-import.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-main.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-prefs.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-preview.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-search.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-snippets.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-infoscreen.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'gui/gui-project.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'syncTeX/synctex_parser.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled src/Makefile.am:11: warning: source file 'syncTeX/synctex_parser_utils.c' is in a subdirectory, src/Makefile.am:11: but option 'subdir-objects' is disabled autoreconf: automake failed with exit status: 1 dh_autoreconf: autoreconf -f -i returned exit code 1 make[1]: *** [override_dh_autoreconf] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/gummi_0.6.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#725532: ruby-augeas: FTBFS: ERROR: Test ruby1.9.1 failed.
Source: ruby-augeas Version: 0.5.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): 76: 77: def test_transform = 78: aug = aug_open(Augeas::NO_LOAD) 79: aug.clear_transforms 80: aug.transform(:lens = Hosts.lns, 81: :incl = /etc/hosts) === Finished in 0.084067617 seconds. 21 tests, 1 assertions, 0 failures, 20 errors, 0 pendings, 0 omissions, 0 notifications 4.7619% passed 249.80 tests/s, 11.90 assertions/s ERROR: Test ruby1.9.1 failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-augeas_0.5.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#725533: opencolorio: FTBFS: ptr.h:10:32: fatal error: boost/shared_ptr.hpp: No such file or directory
Source: opencolorio Version: 1.0.8~dfsg0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[3]: Entering directory `/«PKGBUILDDIR»/debian/cmake' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/debian/cmake/CMakeFiles [ 0%] Building CXX object src/core/CMakeFiles/OpenColorIO.dir/FileTransform.cpp.o cd /«PKGBUILDDIR»/debian/cmake/src/core /usr/bin/c++ -DOpenColorIO_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -O2 -g -DNDEBUG -fPIC -I/«PKGBUILDDIR»/export -I/«PKGBUILDDIR»/debian/cmake/export -I/«PKGBUILDDIR»/debian/cmake/ext/dist/include -I/«PKGBUILDDIR»/ext/oiio/src/include-DTIXML_USE_STL -fPIC -fvisibility-inlines-hidden -fvisibility=hidden -o CMakeFiles/OpenColorIO.dir/FileTransform.cpp.o -c /«PKGBUILDDIR»/src/core/FileTransform.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/debian/cmake/CMakeFiles 1 [ 1%] Building CXX object src/core/CMakeFiles/OpenColorIO.dir/Lut3DOp.cpp.o cd /«PKGBUILDDIR»/debian/cmake/src/core /usr/bin/c++ -DOpenColorIO_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -O2 -g -DNDEBUG -fPIC -I/«PKGBUILDDIR»/export -I/«PKGBUILDDIR»/debian/cmake/export -I/«PKGBUILDDIR»/debian/cmake/ext/dist/include -I/«PKGBUILDDIR»/ext/oiio/src/include-DTIXML_USE_STL -fPIC -fvisibility-inlines-hidden -fvisibility=hidden -o CMakeFiles/OpenColorIO.dir/Lut3DOp.cpp.o -c /«PKGBUILDDIR»/src/core/Lut3DOp.cpp /«PKGBUILDDIR»/src/core/Lut3DOp.cpp: In member function 'std::string OpenColorIO::v1::Lut3D::getCacheID() const': /«PKGBUILDDIR»/src/core/Lut3DOp.cpp:71:59: warning: conversion to 'int' from 'long unsigned int' may alter its value [-Wconversion] md5_append(state, (const md5_byte_t *)from_min, 3*sizeof(float)); ^ /«PKGBUILDDIR»/src/core/Lut3DOp.cpp:72:59: warning: conversion to 'int' from 'long unsigned int' may alter its value [-Wconversion] md5_append(state, (const md5_byte_t *)from_max, 3*sizeof(float)); ^ /«PKGBUILDDIR»/src/core/Lut3DOp.cpp:73:55: warning: conversion to 'int' from 'long unsigned int' may alter its value [-Wconversion] md5_append(state, (const md5_byte_t *)size, 3*sizeof(int)); ^ /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/debian/cmake/CMakeFiles 2 [ 2%] Building CXX object src/core/CMakeFiles/OpenColorIO.dir/GpuShaderUtils.cpp.o cd /«PKGBUILDDIR»/debian/cmake/src/core /usr/bin/c++ -DOpenColorIO_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -O2 -g -DNDEBUG -fPIC -I/«PKGBUILDDIR»/export -I/«PKGBUILDDIR»/debian/cmake/export -I/«PKGBUILDDIR»/debian/cmake/ext/dist/include -I/«PKGBUILDDIR»/ext/oiio/src/include-DTIXML_USE_STL -fPIC -fvisibility-inlines-hidden -fvisibility=hidden -o CMakeFiles/OpenColorIO.dir/GpuShaderUtils.cpp.o -c /«PKGBUILDDIR»/src/core/GpuShaderUtils.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/debian/cmake/CMakeFiles 3 [ 3%] Building CXX object src/core/CMakeFiles/OpenColorIO.dir/Transform.cpp.o cd /«PKGBUILDDIR»/debian/cmake/src/core /usr/bin/c++ -DOpenColorIO_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -O2 -g -DNDEBUG -fPIC -I/«PKGBUILDDIR»/export -I/«PKGBUILDDIR»/debian/cmake/export -I/«PKGBUILDDIR»/debian/cmake/ext/dist/include -I/«PKGBUILDDIR»/ext/oiio/src/include-DTIXML_USE_STL -fPIC -fvisibility-inlines-hidden -fvisibility=hidden -o CMakeFiles/OpenColorIO.dir/Transform.cpp.o -c /«PKGBUILDDIR»/src/core/Transform.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/debian/cmake/CMakeFiles 4 [ 4%] Building CXX object src/core/CMakeFiles/OpenColorIO.dir/FileFormatIridasLook.cpp.o cd /«PKGBUILDDIR»/debian/cmake/src/core /usr/bin/c++ -DOpenColorIO_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -O2 -g -DNDEBUG -fPIC -I/«PKGBUILDDIR»/export -I/«PKGBUILDDIR»/debian/cmake/export -I/«PKGBUILDDIR»/debian/cmake/ext/dist/include -I/«PKGBUILDDIR»/ext/oiio/src/include-DTIXML_USE_STL -fPIC -fvisibility-inlines-hidden -fvisibility=hidden -o CMakeFiles
Bug#725531: aptdaemon: FTBFS: Tests failed
Source: aptdaemon
Version: 1.1.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
==
ERROR: test (tests.test_pep8.AptDaemonPep8TestCase)
Check if the source code matches the PEP8 style conventions.
--
Traceback (most recent call last):
File /«PKGBUILDDIR»/tests/test_pep8.py, line 35, in test
aptdaemon, tests])
File /usr/lib/python3.3/subprocess.py, line 547, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['pep8', '--statistics',
'--show-source', '--show-pep8', '--exclude', 'pkenums.py', 'aptdaemon',
'tests']' returned non-zero exit status 1
==
FAIL: test_install_file (tests.test_worker.WorkerTestCase)
Test the installation of a local package file.
--
Traceback (most recent call last):
File /«PKGBUILDDIR»/tests/test_worker.py, line 342, in test_install_file
trans.error.details)
nose.proxy.AssertionError: False is not true : Lintian check results for
/«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:
'False is not true : Lintian check results for
/«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n'
= self._formatMessage('False is not true : Lintian check results for
/«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n',
%s is not true % safe_repr(False))
raise self.failureException('False is not true : Lintian check results
for
/«PKGBUILDDIR»/tests/repo/silly-depend-base-lintian-broken_0.1-0_all.deb:\n')
--
Ran 78 tests in 136.860s
FAILED (failures=1, errors=1, skipped=4)
make[1]: *** [test-python3.3] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/aptdaemon_1.1.1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on 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#725535: mpd: FTBFS: src/decoder/modplug_decoder_plugin.c:25:21: fatal error: modplug.h: No such file or directory
Source: mpd Version: 0.17.5-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652139 One need to #include libmodplug/modplug.h Relevant part (hopefully): gcc -std=gnu99 -DHAVE_CONFIG_H -I. -DNDEBUG -I./src -pthread -isystem /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include -DSYSTEM_CONFIG_FILE_LOCATION='/etc/mpd.conf' -D_REENTRANT -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_GNU_SOURCE -Wall -Wextra -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wcast-qual -Wwrite-strings -pedantic -MT src/decoder/libmodplug_decoder_plugin_a-modplug_decoder_plugin.o -MD -MP -MF src/decoder/.deps/libmodplug_decoder_plugin_a-modplug_decoder_plugin.Tpo -c -o src/decoder/libmodplug_decoder_plugin_a-modplug_decoder_plugin.o `test -f 'src/decoder/modplug_decoder_plugin.c' || echo './'`src/decoder/modplug_decoder_plugin.c src/decoder/modplug_decoder_plugin.c:25:21: fatal error: modplug.h: No such file or directory #include modplug.h ^ compilation terminated. make[3]: *** [src/decoder/libmodplug_decoder_plugin_a-modplug_decoder_plugin.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/mpd_0.17.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#725539: sqlite: FTBFS: /bin/sh: 1: aclocal-1.13: not found
Source: sqlite Version: 2.8.17-8 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): cd . libtoolize -c -f libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: You should add the contents of the following files to `aclocal.m4': libtoolize: `/usr/share/aclocal/libtool.m4' libtoolize: `/usr/share/aclocal/ltoptions.m4' libtoolize: `/usr/share/aclocal/ltversion.m4' libtoolize: `/usr/share/aclocal/ltsugar.m4' libtoolize: `/usr/share/aclocal/lt~obsolete.m4' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT' cd . aclocal-1.13 -I m4 /bin/sh: 1: aclocal-1.13: not found make: *** [debian/stamp-autotools-files] Error 127 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/sqlite_2.8.17-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#725537: photoprint: FTBFS: configure.ac:12: error: required file 'scripts/compile' not found
Source: photoprint Version: 0.4.2~pre2-2.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh_testdir libtoolize --copy --force libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `scripts'. libtoolize: copying file `scripts/ltmain.sh' libtoolize: You should add the contents of the following files to `aclocal.m4': libtoolize: `/usr/share/aclocal/libtool.m4' libtoolize: `/usr/share/aclocal/ltoptions.m4' libtoolize: `/usr/share/aclocal/ltversion.m4' libtoolize: `/usr/share/aclocal/ltsugar.m4' libtoolize: `/usr/share/aclocal/lt~obsolete.m4' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. autoreconf configure.ac:12: error: required file 'scripts/compile' not found configure.ac:12: 'automake --add-missing' can install 'compile' autoreconf: automake failed with exit status: 1 make: *** [configure-stamp] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/photoprint_0.4.2~pre2-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#725541: gpac: FTBFS: make[1]: *** No rule to make target `config.mak'. Stop.
Source: gpac Version: 0.5.0+svn4288~dfsg1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules clean dh clean --parallel dh_testdir -O--parallel dh_auto_clean -O--parallel make[1]: Entering directory `/«BUILDDIR»/gpac-0.5.0+svn4288~dfsg1' Makefile:4: config.mak: No such file or directory make[1]: *** No rule to make target `config.mak'. Stop. make[1]: Leaving directory `/«BUILDDIR»/gpac-0.5.0+svn4288~dfsg1' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/gpac_0.5.0+svn4288~dfsg1-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#725542: php-horde-ansel: FTBFS: Cannot download non-local package ./ansel-3.0.0/package.xml
Source: php-horde-ansel Version: 3.0.0+debian0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): This package contains role horde and requires package horde/Role to be used File config/conf.xml in directory dir name=/ has invalid role horde, should be one of cfg, data, doc, php, script, test, www This package contains role horde and requires package horde/Role to be used Parsing of package.xml from file ./ansel-3.0.0/package.xml failed Cannot download non-local package ./ansel-3.0.0/package.xml install failed dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d doc_dir=/usr/share/doc/php-horde-ansel -d test_dir=/usr/share/php/tests install --offline --nodeps -P /«BUILDDIR»/php-horde-ansel-3.0.0+debian0/debian/php-horde-ansel ./ansel-3.0.0/package.xml returned exit code 1 make: *** [binary] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/php-horde-ansel_3.0.0+debian0-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#725540: pork: FTBFS: configure.ac:12: error: required file './compile' not found
Source: pork Version: 0.99.8.1-2.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh_testdir # Fix location of porkrc cp -vf /usr/share/misc/config.sub /usr/share/misc/config.guess . '/usr/share/misc/config.sub' - './config.sub' '/usr/share/misc/config.guess' - './config.guess' aclocal autoconf automake configure.ac:4: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see: configure.ac:4: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation configure.ac:12: error: required file './compile' not found configure.ac:12: 'automake --add-missing' can install 'compile' src/missing/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/protocols/Makefile.am:5: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/protocols/aim/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/admin.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/adverts.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/auth.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/bart.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/bos.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/bstream.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/buddylist.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/chat.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/chatnav.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/conn.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/email.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/ft.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/icq.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/im.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/invite.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/locate.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/md5.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim/misc.c' is in a subdirectory, src/protocols/aim/Makefile.am:6: but option 'subdir-objects' is disabled src/protocols/aim/Makefile.am:6: warning: source file 'libfaim
Bug#725536: libapache2-mod-authn-yubikey: FTBFS: make[1]: *** No rule to make target `../../apache228-install/build/special.mk'. Stop.
Source: libapache2-mod-authn-yubikey Version: 1.0-1.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules clean dh clean --with apache2 dh_testdir dh_auto_clean make[1]: Entering directory `/«PKGBUILDDIR»' Makefile:9: ../../apache228-install/build/special.mk: No such file or directory make[1]: *** No rule to make target `../../apache228-install/build/special.mk'. Stop. make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_clean: make -j1 distclean returned exit code 2 make: *** [clean] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/libapache2-mod-authn-yubikey_1.0-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725548: ruby-color-tools: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError)
Source: ruby-color-tools Version: 1.4.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting Encoding.default_external /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:31: warning: method redefined; discarding old visit_String /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:4: warning: previous definition of visit_String was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:39: warning: method redefined; discarding old register /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:12: warning: previous definition of register was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:43: warning: method redefined; discarding old format_time /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:16: warning: previous definition of format_time was here /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:115: warning: method redefined; discarding old to_s /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:44: warning: previous definition of to_s was here Entering dh_ruby --install install -d /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby install -D -m644 /«PKGBUILDDIR»/lib/color/yiq.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/yiq.rb install -D -m644 /«PKGBUILDDIR»/lib/color/palette/adobecolor.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/palette/adobecolor.rb install -D -m644 /«PKGBUILDDIR»/lib/color/palette/gimp.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/palette/gimp.rb install -D -m644 /«PKGBUILDDIR»/lib/color/palette/monocontrast.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/palette/monocontrast.rb install -D -m644 /«PKGBUILDDIR»/lib/color/hsl.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/hsl.rb install -D -m644 /«PKGBUILDDIR»/lib/color/palette.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/palette.rb install -D -m644 /«PKGBUILDDIR»/lib/color/cmyk.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/cmyk.rb install -D -m644 /«PKGBUILDDIR»/lib/color/grayscale.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/grayscale.rb install -D -m644 /«PKGBUILDDIR»/lib/color/css.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/css.rb install -D -m644 /«PKGBUILDDIR»/lib/color/rgb-colors.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/rgb-colors.rb install -D -m644 /«PKGBUILDDIR»/lib/color/rgb/metallic.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/rgb/metallic.rb install -D -m644 /«PKGBUILDDIR»/lib/color/rgb.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color/rgb.rb install -D -m644 /«PKGBUILDDIR»/lib/color.rb /«PKGBUILDDIR»/debian/ruby-color-tools/usr/lib/ruby/vendor_ruby/color.rb /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/test/test_adobecolor.rb:1:in `top (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 -e:1:in `block in main' from -e:1:in `each' from -e:1:in `main' ERROR: Test ruby1.9.1 failed: dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-color-tools returned exit code 1 make: *** [binary] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-color-tools_1.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#725551: jclassinfo: FTBFS: configure.ac:25: error: required file './compile' not found
Source: jclassinfo Version: 0.19.1-6 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' libtoolize -f libtoolize: putting auxiliary files in `.'. libtoolize: linking file `./ltmain.sh' libtoolize: You should add the contents of the following files to `aclocal.m4': libtoolize: `/usr/share/aclocal/libtool.m4' libtoolize: `/usr/share/aclocal/ltoptions.m4' libtoolize: `/usr/share/aclocal/ltversion.m4' libtoolize: `/usr/share/aclocal/ltsugar.m4' libtoolize: `/usr/share/aclocal/lt~obsolete.m4' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. aclocal automake configure.ac:25: error: required file './compile' not found configure.ac:25: 'automake --add-missing' can install 'compile' jclass/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') jclassinfo/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') make[1]: *** [override_dh_auto_configure] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/jclassinfo_0.19.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#725552: min12xxw: FTBFS: configure.ac:11: error: required file './compile' not found
Source: min12xxw Version: 0.0.9-6 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build aclocal autoheader autoconf automake configure.ac:11: error: required file './compile' not found configure.ac:11: 'automake --add-missing' can install 'compile' make: *** [configure] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/min12xxw_0.0.9-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#725544: ruby-merb-assets: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- spec_helper (LoadError)
Source: ruby-merb-assets Version: 1.1.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting Encoding.default_external /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:31: warning: method redefined; discarding old visit_String /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:4: warning: previous definition of visit_String was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:39: warning: method redefined; discarding old register /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:12: warning: previous definition of register was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:43: warning: method redefined; discarding old format_time /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:16: warning: previous definition of format_time was here /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:115: warning: method redefined; discarding old to_s /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:44: warning: previous definition of to_s was here Entering dh_ruby --install install -d /«PKGBUILDDIR»/debian/ruby-merb-assets/usr/lib/ruby/vendor_ruby install -D -m644 /«PKGBUILDDIR»/lib/merb-assets.rb /«PKGBUILDDIR»/debian/ruby-merb-assets/usr/lib/ruby/vendor_ruby/merb-assets.rb install -D -m644 /«PKGBUILDDIR»/lib/merb-assets/assets_mixin.rb /«PKGBUILDDIR»/debian/ruby-merb-assets/usr/lib/ruby/vendor_ruby/merb-assets/assets_mixin.rb install -D -m644 /«PKGBUILDDIR»/lib/merb-assets/assets.rb /«PKGBUILDDIR»/debian/ruby-merb-assets/usr/lib/ruby/vendor_ruby/merb-assets/assets.rb install -D -m644 /«PKGBUILDDIR»/lib/merb-assets/version.rb /«PKGBUILDDIR»/debian/ruby-merb-assets/usr/lib/ruby/vendor_ruby/merb-assets/version.rb /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- spec_helper (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/spec/merb-assets_spec.rb:1:in `top (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 debian/ruby-tests.rb:3:in `block in main' from debian/ruby-tests.rb:3:in `each' from debian/ruby-tests.rb:3:in `main' ERROR: Test ruby1.9.1 failed: dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit code 1 make: *** [binary] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-merb-assets_1.1.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725545: ruby-ramaze: FTBFS: ERROR: Test ruby1.9.1 failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- innate (LoadError)
Source: ruby-ramaze Version: 2012.12.08-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Rewriting shebang line of /«PKGBUILDDIR»/debian/ruby-ramaze/usr/bin/ramaze /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- innate (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /«PKGBUILDDIR»/debian/ruby-ramaze/usr/lib/ruby/vendor_ruby/ramaze.rb:16:in `module:Ramaze' from /«PKGBUILDDIR»/debian/ruby-ramaze/usr/lib/ruby/vendor_ruby/ramaze.rb:12:in `top (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 debian/ruby-tests.rb:21:in `main' ERROR: Test ruby1.9.1 failed: dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit code 1 make: *** [binary] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-ramaze_2012.12.08-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#725550: python-falcon: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 586: ordinal not in range(128)
Source: python-falcon
Version: 0.1.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
running install_egg_info
Copying falcon.egg-info to
/«PKGBUILDDIR»/debian/python-falcon/usr/lib/python2.7/dist-packages/falcon-0.1.7.egg-info
running install_scripts
Installing falcon-bench script to /«PKGBUILDDIR»/debian/python-falcon/usr/bin
set -e for pyvers in 3.3; do \
python$pyvers setup.py install --install-layout=deb \
--root /«PKGBUILDDIR»/debian/python3-falcon; \
done
WARNING: Cython not installed. Falcon modules WILL NOT be compiled with
Cython.
Traceback (most recent call last):
File setup.py, line 56, in module
long_description=open('README.rst', 'r').read(),
File /usr/lib/python3.3/encodings/ascii.py, line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 586:
ordinal not in range(128)
make[1]: *** [override_dh_auto_install] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/python-falcon_0.1.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#725549: yorick-gl: FTBFS: make[1]: *** No rule to make target `check.i', needed by `check-dll'
Source: yorick-gl Version: 1.1+cvs20070922+dfsg-6 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): glTarray.c: In function 'yglTarrayAlpha': glTarray.c:162:3: warning: incompatible implicit declaration of built-in function 'sprintf' [enabled by default] sprintf(msg, in yglTarrayAlpha, alpha_pass is %d\n, alpha_pass); ^ cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -D_FORTIFY_SOURCE=2 -c -o gltexsubs.o gltexsubs.c cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -D_FORTIFY_SOURCE=2 -c -o glustub.o glustub.c cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -D_FORTIFY_SOURCE=2 -c -o glGlyph.o glGlyph.c cc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -DUSE_MESA_PIXMAPS -o oglx.o -c oglx.c /usr/lib/yorick/lib/codger w yorgl cntrfunc.i glfunc.i found cntrfunc.i in current directory found glfunc.i in current directory cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -DPLUG_IN -I. -I/usr/lib/yorick/include -D_FORTIFY_SOURCE=2 -c -o ywrap.o ywrap.c cc -Wl,-z,relro -fPIC -shared -o yorgl.so ContourTets3D.o Gradient3D.o isotree.o slicetree.o glPolys.o glStrips.o gltexture.o glcode.o glfunc.o glMouse.o glx11view.o glx11setup.o TriUtil.o dlist3d.o glTarray.o gltexsubs.o glustub.o glGlyph.o oglx.o ywrap.o -lGL -lXext -lX11 -lm make[2]: Leaving directory `/«BUILDDIR»/yorick-gl-1.1+cvs20070922+dfsg' make[1]: Leaving directory `/«BUILDDIR»/yorick-gl-1.1+cvs20070922+dfsg' dh_auto_test make[1]: Entering directory `/«BUILDDIR»/yorick-gl-1.1+cvs20070922+dfsg' make[1]: *** No rule to make target `check.i', needed by `check-dll'. Stop. make[1]: Leaving directory `/«BUILDDIR»/yorick-gl-1.1+cvs20070922+dfsg' dh_auto_test: make -j1 check returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/yorick-gl_1.1+cvs20070922+dfsg-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#725543: asterisk-flite: FTBFS: app_flite.c:168:13: error: dereferencing pointer to incomplete type
Source: asterisk-flite Version: 2.1-1.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -pipe -fPIC -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -D_REENTRANT -D_GNU_SOURCE -g -O2 -c -o app_flite.o app_flite.c app_flite.c: In function 'flite_exec': app_flite.c:168:13: error: dereferencing pointer to incomplete type if (chan-_state != AST_STATE_UP) ^ app_flite.c:170:47: error: dereferencing pointer to incomplete type res = ast_streamfile(chan, cachefile, chan-language); ^ app_flite.c:173:12: error: dereferencing pointer to incomplete type chan-name); ^ app_flite.c:239:10: error: dereferencing pointer to incomplete type if (chan-_state != AST_STATE_UP) ^ app_flite.c:241:43: error: dereferencing pointer to incomplete type res = ast_streamfile(chan, tmp_name, chan-language); ^ app_flite.c:243:66: error: dereferencing pointer to incomplete type ast_log(LOG_ERROR, Flite: ast_streamfile failed on %s\n, chan-name); ^ make[1]: *** [app_flite.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/asterisk-flite_2.1-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on 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#725547: ruby-hiera: FTBFS: ERROR: Test ruby1.9.1 failed.
Source: ruby-hiera Version: 1.0.0~rc3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Finished in 0.12908 seconds 80 examples, 8 failures Failed examples: rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should return the answer from the backend rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should retain the datatypes as returned by the backend rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should call to all backends till an answer is found rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should parse the answers based on resolution_type rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should return the default with variables parsed if nothing is found rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should correctly handle string default data rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should correctly handle array default data rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should correctly handle hash default data /usr/bin/ruby1.9.1 -S rspec spec/unit/backend/yaml_backend_spec.rb spec/unit/backend_spec.rb spec/unit/config_spec.rb spec/unit/console_logger_spec.rb spec/unit/hiera_spec.rb --format s --colour --backtrace failed ERROR: Test ruby1.9.1 failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-hiera_1.0.0~rc3-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#725546: numptyphysics: FTBFS: configure.in:6: error: required file './compile' not found
Source: numptyphysics Version: 0.2+svn156-1.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«BUILDDIR»/numptyphysics-0.2+svn156' autoreconf aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:3: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see: configure.in:3: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation configure.in:6: error: required file './compile' not found configure.in:6: 'automake --add-missing' can install 'compile' automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' autoreconf: automake failed with exit status: 1 make[1]: *** [override_dh_auto_configure] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/numptyphysics_0.2+svn156-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725563: python-naturalsort: FTBFS: ImportError: No module named setuptools
Source: python-naturalsort Version: 1.0.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): fakeroot debian/rules clean dh clean --with python2 dh_testdir dh_auto_clean pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions Traceback (most recent call last): File setup.py, line 4, in module from setuptools import setup ImportError: No module named setuptools dh_auto_clean: python setup.py clean -a returned exit code 1 make: *** [clean] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/python-naturalsort_1.0.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on 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#725558: rlvm: FTBFS: Boost version = 1.40 needed to compile rlvm!
Source: rlvm Version: 0.12-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh build dh_testdir dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory `/«PKGBUILDDIR»' scons --release build/rlvm build/locale scons: Reading SConscript files ... Checking for Boost version = 1.40... no Boost version = 1.40 needed to compile rlvm! make[1]: *** [override_dh_auto_build] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/rlvm_0.12-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#725554: pimd: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
Source: pimd
Version: 2.1.8-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
make[1]: Entering directory `/«PKGBUILDDIR»'
make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_clean
rm -f debian/pimd.substvars
rm -f debian/pimd.*.debhelper
rm -rf debian/pimd/
rm -f debian/*.debhelper.log
rm -f debian/files
find . \( \( -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
\)
rm -f *-stamp
dpkg-source -b pimd-2.1.8
dpkg-source: error: can't build with source format '3.0 (native)': native
package version may not have a revision
dpkg-buildpackage: error: dpkg-source -b pimd-2.1.8 gave error exit status 255
Build finished at 20131005-1249
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/pimd_2.1.8-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#725561: ruby-em-socksify: FTBFS: ERROR: Test ruby2.0 failed: /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- rubyeventmachine (LoadError)
Source: ruby-em-socksify Version: 0.2.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs ruby2-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory `/«PKGBUILDDIR»' chmod +x debian/start_webrick_hpsockd_and_auto_install.sh debian/start_webrick_hpsockd_and_auto_install.sh Sleeping 5 seconds for WEBrick to start... /usr/lib/ruby/vendor_ruby/gem2deb.rb:17: warning: setting Encoding.default_external /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:31: warning: method redefined; discarding old visit_String /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:4: warning: previous definition of visit_String was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:39: warning: method redefined; discarding old register /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:12: warning: previous definition of register was here /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:43: warning: method redefined; discarding old format_time /usr/lib/ruby/1.9.1/rubygems/psych_tree.rb:16: warning: previous definition of format_time was here /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:115: warning: method redefined; discarding old to_s /usr/lib/ruby/1.9.1/rubygems/syck_hack.rb:44: warning: previous definition of to_s was here Entering dh_ruby --install install -d /«PKGBUILDDIR»/debian/ruby-em-socksify/usr/lib/ruby/vendor_ruby install -D -m644 /«PKGBUILDDIR»/lib/em-socksify/version.rb /«PKGBUILDDIR»/debian/ruby-em-socksify/usr/lib/ruby/vendor_ruby/em-socksify/version.rb install -D -m644 /«PKGBUILDDIR»/lib/em-socksify/socksify.rb /«PKGBUILDDIR»/debian/ruby-em-socksify/usr/lib/ruby/vendor_ruby/em-socksify/socksify.rb install -D -m644 /«PKGBUILDDIR»/lib/em-socksify/socks5.rb /«PKGBUILDDIR»/debian/ruby-em-socksify/usr/lib/ruby/vendor_ruby/em-socksify/socks5.rb install -D -m644 /«PKGBUILDDIR»/lib/em-socksify/errors.rb /«PKGBUILDDIR»/debian/ruby-em-socksify/usr/lib/ruby/vendor_ruby/em-socksify/errors.rb install -D -m644 /«PKGBUILDDIR»/lib/em-socksify.rb /«PKGBUILDDIR»/debian/ruby-em-socksify/usr/lib/ruby/vendor_ruby/em-socksify.rb /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /usr/bin/ruby1.9.1 -S rspec ./spec/socksify_spec.rb . Finished in 0.00743 seconds 1 example, 0 failures /usr/bin/ruby2.0 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb /usr/bin/ruby2.0 -S rspec ./spec/socksify_spec.rb Unable to load the EventMachine C extension; To use the pure-ruby reactor, require 'em/pure_ruby' /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require': cannot load such file -- rubyeventmachine (LoadError) from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require' from /usr/lib/ruby/vendor_ruby/eventmachine.rb:8:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require' from /«PKGBUILDDIR»/lib/em-socksify.rb:1:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require' from /«PKGBUILDDIR»/spec/helper.rb:4:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:51:in `require' from /«PKGBUILDDIR»/spec/socksify_spec.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:22:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in autorun' /usr/bin/ruby2.0 -S rspec ./spec/socksify_spec.rb failed ERROR: Test ruby2.0 failed: dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-em-socksify returned exit code 1 make[1]: *** [override_dh_auto_install] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-em-socksify_0.2.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on 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
Bug#725553: ruby-graffiti: FTBFS: ERROR: Test ruby1.9.1 failed.
Source: ruby-graffiti Version: 2.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb Run options: # Running tests: ...F.. Finished tests in 0.203351s, 49.1759 tests/s, 236.0445 assertions/s. 1) Failure: test_query_assert(TC_Storage) [/«PKGBUILDDIR»/test/ts_graffiti.rb:123]: 5 expected but was 7. 10 tests, 48 assertions, 1 failures, 0 errors, 0 skips ERROR: Test ruby1.9.1 failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-graffiti_2.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#725555: ufiformat: FTBFS: configure.in:11: error: required file './compile' not found
Source: ufiformat Version: 0.9.8-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh_testdir aclocal aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' autoheader automake automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:11: error: required file './compile' not found configure.in:11: 'automake --add-missing' can install 'compile' automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' make: *** [configure] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ufiformat_0.9.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
