Processed: closing 619398
Processing commands for cont...@bugs.debian.org: close 619398 0.99.1-1 Bug#619398: libpulse0: license issue, compile client LGPL 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 0.99.1-1, send any further explanations to David Fries da...@fries.net thanks Stopping processing here. Please contact me if you need assistance. -- 619398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619398 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#624933: marked as done (posterazor: FTBFS: TranslationEnglish.h:262:33: error: uninitialized const 'english' [-fpermissive])
Your message dated Wed, 28 Sep 2011 06:28:55 + with message-id 20110928062855.ga28...@master.debian.org and subject line posterazor: FTBFS: TranslationEnglish.h:262:33: error: uninitialized const 'english' [-fpermissive] has caused the Debian Bug report #624933, regarding posterazor: FTBFS: TranslationEnglish.h:262:33: error: uninitialized const 'english' [-fpermissive] 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.) -- 624933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: posterazor Version: 1.5.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110502 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/build' [ 5%] Building CXX object CMakeFiles/PosteRazor.dir/ImageIOTypes.o [ 10%] Building CXX object CMakeFiles/PosteRazor.dir/PosteRazor.o [ 15%] Building CXX object CMakeFiles/PosteRazor.dir/PosteRazorImageIO.o [ 20%] Building CXX object CMakeFiles/PosteRazor.dir/PosteRazorPDFOutput.o [ 25%] Building CXX object CMakeFiles/PosteRazor.dir/UnitsOfLength.o /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/UnitsOfLength.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/UnitsOfLength.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/UnitsOfLength.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/UnitsOfLength.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/UnitsOfLength.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/UnitsOfLength.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] [ 30%] Building CXX object CMakeFiles/PosteRazor.dir/PaperFormats.o /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/PaperFormats.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/PaperFormats.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/PaperFormats.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/PaperFormats.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/PaperFormats.cpp:42:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] [ 35%] Building CXX object CMakeFiles/PosteRazor.dir/PaintCanvasBase.o [ 40%] Building CXX object CMakeFiles/PosteRazor.dir/Translations.o In file included from /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/Translations.cpp:25:0: /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/TranslationEnglish.h:262:33: error: uninitialized const 'english' [-fpermissive] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/TranslationEnglish.h:31:7: note: 'const class TranslationEnglish' has no user-provided default constructor In file included from /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/Translations.cpp:26:0: /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/TranslationGerman.h:264:32: error: uninitialized const 'german' [-fpermissive] /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/TranslationGerman.h:31:7: note: 'const class TranslationGerman' has no user-provided default constructor In file included from /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/Translations.cpp:27:0: /build/user-posterazor_1.5.1-1-amd64-OEfaiZ/posterazor-1.5.1/src/TranslationFrench.h:274:32: error: uninitialized const 'french' [-fpermissive]
Bug#619398: closing 619398
close 619398 0.99.1-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643622: leveldb: FTBFS: ./port/atomic_pointer.h:133:2: error: #error Please implement AtomicPointer for this platform.
Source: leveldb
Version: 0+20110901.git7263023-2
Severity: serious
Justification: fails to build from source
Tags: patch
Hi,
leveldb FTBFS some architecture.
https://buildd.debian.org/status/package.php?p=leveldbsuite=sid
http://buildd.debian-ports.org/status/package.php?p=leveldbsuite=sid
Because leveldb does not support these architecture.
-
dh_auto_configure -O--parallel
dh_auto_build -O--parallel
make[1]: Entering directory
`/build/buildd-leveldb_0+20110901.git7263023-2-ia64-gm7mku/leveldb-0+20110901.git7263023'
g++ -g -O2 -c -I. -I./include -fno-builtin-memcmp
-DLEVELDB_PLATFORM_POSIX -pthread -DOS_LINUX -O2 -DNDEBUG
-fPIC db/builder.cc -o db/builder.o
g++ -g -O2 -c -I. -I./include -fno-builtin-memcmp
-DLEVELDB_PLATFORM_POSIX -pthread -DOS_LINUX -O2 -DNDEBUG
-fPIC db/c.cc -o db/c.o
In file included from ./port/port_posix.h:28:0,
from ./port/port.h:14,
from ./db/filename.h:14,
from db/builder.cc:7:
./port/atomic_pointer.h:133:2: error: #error Please implement
AtomicPointer for this platform.
make[1]: *** [db/builder.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory
`/build/buildd-leveldb_0+20110901.git7263023-2-ia64-gm7mku/leveldb-0+20110901.git7263023'
dh_auto_build: make -j2 returned exit code 2
make: *** [build] Error 2
-
I created patch which revise this problem.
Could you check and apply these?
I tested on i386, amd64 and sh4.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
From 9257ab3a17963b043dbc6e53a094e13a5b54488c Mon Sep 17 00:00:00 2001
From: Nobuhiro Iwamatsu iwama...@debian.org
Date: Wed, 28 Sep 2011 12:25:23 +0900
Subject: [PATCH 1/9] Add ReadMemoryBarrier and WriteMemoryBarrier methods
Some CPUs differ in the order of the memory barrier of read and write.
For other CPUs, this adds the memory barrier method the memory barrier
for read and write metohds.
Signed-off-by: Nobuhiro Iwamatsu iwama...@debian.org
---
port/atomic_pointer.h | 31 +--
1 files changed, 25 insertions(+), 6 deletions(-)
diff --git a/port/atomic_pointer.h b/port/atomic_pointer.h
index c20b1bd..022a3a6 100644
--- a/port/atomic_pointer.h
+++ b/port/atomic_pointer.h
@@ -48,9 +48,17 @@ namespace port {
// http://msdn.microsoft.com/en-us/library/ms684208(v=vs.85).aspx
#define LEVELDB_HAVE_MEMORY_BARRIER
+#define ReadMemoryBarrier MemoryBarrier()
+#define WriteMemoryBarrier MemoryBarrier()
+
// Gcc on x86
#elif defined(ARCH_CPU_X86_FAMILY) defined(__GNUC__)
-inline void MemoryBarrier() {
+inline void ReadMemoryBarrier() {
+ // See http://gcc.gnu.org/ml/gcc/2003-04/msg01180.html for a discussion on
+ // this idiom. Also see http://en.wikipedia.org/wiki/Memory_ordering.
+ __asm__ __volatile__( : : : memory);
+}
+inline void WriteMemoryBarrier() {
// See http://gcc.gnu.org/ml/gcc/2003-04/msg01180.html for a discussion on
// this idiom. Also see http://en.wikipedia.org/wiki/Memory_ordering.
__asm__ __volatile__( : : : memory);
@@ -59,7 +67,12 @@ inline void MemoryBarrier() {
// Sun Studio
#elif defined(ARCH_CPU_X86_FAMILY) defined(__SUNPRO_CC)
-inline void MemoryBarrier() {
+inline void ReadMemoryBarrier() {
+ // See http://gcc.gnu.org/ml/gcc/2003-04/msg01180.html for a discussion on
+ // this idiom. Also see http://en.wikipedia.org/wiki/Memory_ordering.
+ asm volatile( : : : memory);
+}
+inline void WriteMemoryBarrier() {
// See http://gcc.gnu.org/ml/gcc/2003-04/msg01180.html for a discussion on
// this idiom. Also see http://en.wikipedia.org/wiki/Memory_ordering.
asm volatile( : : : memory);
@@ -68,7 +81,10 @@ inline void MemoryBarrier() {
// Mac OS
#elif defined(OS_MACOSX)
-inline void MemoryBarrier() {
+inline void ReadMemoryBarrier() {
+ OSMemoryBarrier();
+}
+inline void WriteMemoryBarrier() {
OSMemoryBarrier();
}
#define LEVELDB_HAVE_MEMORY_BARRIER
@@ -78,7 +94,10 @@ inline void MemoryBarrier() {
typedef void (*LinuxKernelMemoryBarrierFunc)(void);
LinuxKernelMemoryBarrierFunc pLinuxKernelMemoryBarrier __attribute__((weak)) =
(LinuxKernelMemoryBarrierFunc) 0x0fa0;
-inline void MemoryBarrier() {
+inline void ReadMemoryBarrier() {
+ pLinuxKernelMemoryBarrier();
+}
+inline void WriteMemoryBarrier() {
pLinuxKernelMemoryBarrier();
}
#define LEVELDB_HAVE_MEMORY_BARRIER
@@ -97,11 +116,11 @@ class AtomicPointer {
inline void NoBarrier_Store(void* v) { rep_ = v; }
inline void* Acquire_Load() const {
void* result = rep_;
-MemoryBarrier();
+ReadMemoryBarrier();
return result;
}
inline void Release_Store(void* v) {
-MemoryBarrier();
+WriteMemoryBarrier();
rep_ = v;
}
};
--
1.7.6.3
From 6805877f8913935071fb97c1b76e4f0ce992d8a6 Mon Sep 17 00:00:00 2001
From: Nobuhiro Iwamatsu iwama...@debian.org
Date: Wed, 28 Sep 2011 12:27:19 +0900
Subject: [PATCH 2/9] Add support PPC
Signed-off-by: Nobuhiro Iwamatsu iwama...@debian.org
---
Bug#642814: marked as done (jcc: FTBFS: Java JDK directory '/usr/lib/jvm/java-6-openjdk' does not exist.)
Your message dated Wed, 28 Sep 2011 07:18:15 + with message-id e1r8oph-0002hj...@franck.debian.org and subject line Bug#642814: fixed in jcc 2.11-1 has caused the Debian Bug report #642814, regarding jcc: FTBFS: Java JDK directory '/usr/lib/jvm/java-6-openjdk' does not exist. 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.) -- 642814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jcc Version: 2.9-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/jcc-NJQXCo/jcc-2.9' dh_auto_clean Traceback (most recent call last): File setup.py, line 80, in module ''' %(JDK[platform])) RuntimeError: Java JDK directory '/usr/lib/jvm/java-6-openjdk' does not exist. Please set the environment variable JCC_JDK to the correct location before running setup.py. dh_auto_clean: python2.7 setup.py clean -a returned exit code 1 make[1]: *** [override_dh_auto_clean] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/jcc_2.9-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: jcc Source-Version: 2.11-1 We believe that the bug you reported is fixed in the latest version of jcc, which is due to be installed in the Debian FTP archive: jcc_2.11-1.debian.tar.gz to main/j/jcc/jcc_2.11-1.debian.tar.gz jcc_2.11-1.dsc to main/j/jcc/jcc_2.11-1.dsc jcc_2.11-1_amd64.deb to main/j/jcc/jcc_2.11-1_amd64.deb jcc_2.11.orig.tar.gz to main/j/jcc/jcc_2.11.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 642...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovico Cavedon cave...@debian.org (supplier of updated jcc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 27 Sep 2011 23:51:41 -0700 Source: jcc Binary: jcc Architecture: source amd64 Version: 2.11-1 Distribution: unstable Urgency: low Maintainer: Ludovico Cavedon cave...@debian.org Changed-By: Ludovico Cavedon cave...@debian.org Description: jcc- code generator producing a Python extension from Java classes Closes: 642814 Changes: jcc (2.11-1) unstable; urgency=low . * New upstream release. * Change paths to openjdk libraries (for openjdk = 6b23~pre9-1~, Closes: #642814). Checksums-Sha1: e158c09821dc54ae09b704afc38769b316a3e24a 1849 jcc_2.11-1.dsc 280841f90a68f03f2200b9b108fc8e93378f214b 86519 jcc_2.11.orig.tar.gz d7d0dcf2a3612de3dccdd41df3d099c4bfe2ad27 4604 jcc_2.11-1.debian.tar.gz 1390d82441a35292130edfa4419192f936cf9e4d 356826 jcc_2.11-1_amd64.deb Checksums-Sha256: 71f265cbf3f7f216d3c9862e5aef9f55470881823e847e51046d08b1c15eb1f4 1849 jcc_2.11-1.dsc 10e2c768a876e1089df879203b49a16a9c220fc7223e98af53bc76070d0e5ab7 86519 jcc_2.11.orig.tar.gz 3df8822ebd43b85b6970d4e79478d65f6ae28b127d90f0a243c7f00e572459a5 4604 jcc_2.11-1.debian.tar.gz ff40fcc144d2f9a3dd084e6af43553addb830cae6bd438946aee0d168674aaeb 356826 jcc_2.11-1_amd64.deb Files: f24ad83ff50774bb4b6e443b3a2a29d2 1849 python extra jcc_2.11-1.dsc 5afffd174a11d657dbcce390f031fe5d 86519 python extra jcc_2.11.orig.tar.gz 7ade80c47c2b2ce22acb42f47b92b38b 4604 python extra jcc_2.11-1.debian.tar.gz 3bd5a56d1ccce5617293296fe0fdcbad 356826 python extra jcc_2.11-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJOgsnPAAoJEBPAtWZ6OLCwBvIQAKeLnJff9dh3uGpuWlXwP2w0 sFw3uPoq0AHgDyeqRMre3KdXjEpPPrhG8fR8RprB+olNJySbcNMuw7CV473bSTEb LR2BHDVzk/dX4gobiznQIe+/3VR6tumgLMm3bklEHMMpO6cXnbLQUlyv1ua78hRs HGIu1sNX25x5YLmwCyFH7Yrgg8N5FZnZ6/cOxUSaLbw1PNLKW8J5zS9IeF2C3Rcu
Bug#642817: pyxnat: FTBFS: tests failed
Hi, El dt 27 de 09 de 2011 a les 16:32 +0200, en/na Yannick SCHWARTZ va escriure: Hi, Does the build machine have an internet connection? My package needs to connect to a database server to perform its tests. Best, Yannick About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ^^ AFAIK, a package should be able to be built without Internet connection. Thanks for your work! Mònica -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643491: animal-sniffer: FTBFS without internet access
retitle 643491 animal-sniffer: FTBFS without internet access thanks Hi Didier, Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] MavenReportException: Error while creating archive:Error when invoking Maven, consult the invoker log file: /build/animal-sniffer-_h2Kf1/animal-sniffer-1.7/java-boot-classpath-detector/target/invoker/maven-javadoc-plugin698236679.txt thanks for this report! It seems that one of the maven plugins ignores maven's --offline parameter. I'll fix this issue soon. best regards, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: animal-sniffer: FTBFS without internet access
Processing commands for cont...@bugs.debian.org: retitle 643491 animal-sniffer: FTBFS without internet access Bug #643491 [src:animal-sniffer] animal-sniffer: FTBFS: Error while creating archive Changed Bug title to 'animal-sniffer: FTBFS without internet access' from 'animal-sniffer: FTBFS: Error while creating archive' thanks Stopping processing here. Please contact me if you need assistance. -- 643491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643491 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#639892: marked as done (libpulse-mainloop-glib0: symbols file define wrong package name (ie old libpulse-glib-mainloop0))
Your message dated Wed, 28 Sep 2011 07:34:17 + with message-id e1r8oen-0005eh...@franck.debian.org and subject line Bug#639892: fixed in pulseaudio 1.0-2 has caused the Debian Bug report #639892, regarding libpulse-mainloop-glib0: symbols file define wrong package name (ie old libpulse-glib-mainloop0) 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.) -- 639892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libpulse-mainloop-glib0 Version: 0.99.2-2 Severity: important Dear Maintainer, current experimental package shoips a symbols file: /var/lib/dpkg/info/libpulse-mainloop-glib0.symbols which stills points to the old package name from 0.9.23. THis breaks installing packages build against libpulse-mainloop-glib0 (here empathy 3.1.5) as the shlibs deps in the packages which depends upon libpulse-mainloop-glib0 substvars ends up pointing to libpulse-glib-mainloop0. Ie to fix this issue I replaced: libpulse-mainloop-glib.so.0 libpulse-glib-mainloop0 #MINVER# PULSE_0@PULSE_0 0.99.1 pa_glib_mainloop_free@PULSE_0 0.99.1 pa_glib_mainloop_get_api@PULSE_0 0.99.1 pa_glib_mainloop_new@PULSE_0 0.99.1 by: libpulse-mainloop-glib.so.0 libpulse-mainloop-glib0 #MINVER# PULSE_0@PULSE_0 0.99.1 pa_glib_mainloop_free@PULSE_0 0.99.1 pa_glib_mainloop_get_api@PULSE_0 0.99.1 pa_glib_mainloop_new@PULSE_0 0.99.1 in this symbols file. Best regards, Alban -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpulse-mainloop-glib0 depends on: ii libc6 2.13-18 ii libcap21:2.22-1 ii libglib2.0-0 2.28.6-2 ii libpulse0 0.99.2-2 ii multiarch-support 2.13-18 libpulse-mainloop-glib0 recommends no packages. libpulse-mainloop-glib0 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: pulseaudio Source-Version: 1.0-2 We believe that the bug you reported is fixed in the latest version of pulseaudio, which is due to be installed in the Debian FTP archive: libpulse-dev_1.0-2_amd64.deb to main/p/pulseaudio/libpulse-dev_1.0-2_amd64.deb libpulse-mainloop-glib0-dbg_1.0-2_amd64.deb to main/p/pulseaudio/libpulse-mainloop-glib0-dbg_1.0-2_amd64.deb libpulse-mainloop-glib0_1.0-2_amd64.deb to main/p/pulseaudio/libpulse-mainloop-glib0_1.0-2_amd64.deb libpulse0-dbg_1.0-2_amd64.deb to main/p/pulseaudio/libpulse0-dbg_1.0-2_amd64.deb libpulse0_1.0-2_amd64.deb to main/p/pulseaudio/libpulse0_1.0-2_amd64.deb pulseaudio-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-dbg_1.0-2_amd64.deb pulseaudio-esound-compat-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-esound-compat-dbg_1.0-2_amd64.deb pulseaudio-esound-compat_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-esound-compat_1.0-2_amd64.deb pulseaudio-module-bluetooth-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-bluetooth-dbg_1.0-2_amd64.deb pulseaudio-module-bluetooth_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-bluetooth_1.0-2_amd64.deb pulseaudio-module-gconf-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-gconf-dbg_1.0-2_amd64.deb pulseaudio-module-gconf_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-gconf_1.0-2_amd64.deb pulseaudio-module-jack-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-jack-dbg_1.0-2_amd64.deb pulseaudio-module-jack_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-jack_1.0-2_amd64.deb pulseaudio-module-lirc-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-lirc-dbg_1.0-2_amd64.deb pulseaudio-module-lirc_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-lirc_1.0-2_amd64.deb pulseaudio-module-raop-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-raop-dbg_1.0-2_amd64.deb pulseaudio-module-raop_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-raop_1.0-2_amd64.deb pulseaudio-module-x11-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-x11-dbg_1.0-2_amd64.deb pulseaudio-module-x11_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-x11_1.0-2_amd64.deb pulseaudio-module-zeroconf-dbg_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-zeroconf-dbg_1.0-2_amd64.deb pulseaudio-module-zeroconf_1.0-2_amd64.deb to main/p/pulseaudio/pulseaudio-module-zeroconf_1.0-2_amd64.deb
Processed: Re: Bug#643473: python-kinterbasdb: FTBFS: _configtest.c:7:3: error: unknown type name 'useconds_t'
Processing commands for cont...@bugs.debian.org: retitle 643473 python-kinterbasdb: FTBFS with firebird-dev (2.5) -- removed defines Bug #643473 [src:python-kinterbasdb] python-kinterbasdb: FTBFS: _configtest.c:7:3: error: unknown type name 'useconds_t' Changed Bug title to 'python-kinterbasdb: FTBFS with firebird-dev (2.5) -- removed defines' from 'python-kinterbasdb: FTBFS: _configtest.c:7:3: error: unknown type name 'useconds_t'' thanks Stopping processing here. Please contact me if you need assistance. -- 643473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643473 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#642310: overwrite error: /usr/share/man/man2/io_getevents.2.gz
reopen 642310 thanks Guillem Jover guil...@debian.org writes: On Wed, 2011-09-21 at 14:28:46 +0200, Goswin von Brederlow wrote: Package: libaio-dev Version: 0.3.109-1 Severity: serious Trying to upgarde libaio-dev fails with: Unpacking replacement libaio-dev ... dpkg: error processing /var/cache/apt/archives/libaio-dev_0.3.109-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man2/io_getevents.2.gz', which is also in package manpages-dev 3.28-1 This is a bug in manpages, which included those when libaio-dev has always provided them, fixed in manpages-dev 3.32-0.2, you should upgrade that one. (Bug #636704) thanks, guillem Upgrades have to work in any order or packages have to say otherwise (breaks, conflicts, replaces, ...) so that isn't really a solution. Also manpages-dev says: * debian/control: add Replace against libaio-dev, because of aio_init.3.gz and lio_listio.3.gz (Closes: #636704) That is only approriate when the files are moved from libaio-dev to manpages-dev and clearly libaio-dev has not droped those files. So one or both of the two packages are wrong. MfG Goswin -- 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#642310: overwrite error: /usr/share/man/man2/io_getevents.2.gz
Processing commands for cont...@bugs.debian.org:
reopen 642310
Bug #642310 {Done: Guillem Jover guil...@debian.org} [libaio-dev] overwrite
error: /usr/share/man/man2/io_getevents.2.gz
thanks
Stopping processing here.
Please contact me if you need assistance.
--
642310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642310
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#643628: pidgin: Pidgin crash on sending first message
Package: pidgin Version: 2.10.0-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, I run pidgin. Find a necessary contact. Write a message. Try to send a message. Pidgin is crashed on sending message. There is a backtrace from gdb: Starting program: /usr/bin/pidgin [Thread debugging using libthread_db enabled] [New Thread 0x4cbf52e0 (LWP 4200)] [New Thread 0x4d61f2e0 (LWP 4201)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x4d61f2e0 (LWP 4201)] (gdb) thread apply all bt Thread 3 (Thread 0x4d61f2e0 (LWP 4201)): #0 0x4ce0034c in ?? () #1 0x1abaab10 in orc_audio_convert_unpack_s16_swap (d1=optimized out, s1=optimized out, p1=optimized out, n=optimized out) at tmp-orc.c:693 #2 0x1f7af790 in g_realloc () from /lib/libglib-2.0.so.0 #3 0x1aba2804 in audio_convert_convert (ctx=0x21988190, src=optimized out, dst=0x4cc17d48, samples=1024, src_writable=1) at audioconvert.c:763 #4 0x1ab9e520 in gst_audio_convert_transform (base=0x21988020, inbuf=0x217f1320, outbuf=0x2182f320) at gstaudioconvert.c:1104 #5 0x1ea7d914 in gst_base_transform_handle_buffer (trans=0x21988020, inbuf=0x217f1320, outbuf=0x4d61e858) at gstbasetransform.c:2307 #6 0x1ea7e194 in gst_base_transform_chain (pad=optimized out, buffer=0x217f1320) at gstbasetransform.c:2424 #7 0x2030f394 in gst_pad_chain_data_unchecked (cache=0x4d61e8f0, data=0x217f1320, is_buffer=1, pad=0x2186a990) at gstpad.c:4247 #8 gst_pad_push_data (pad=optimized out, is_buffer=1, data=0x217f1320, cache=optimized out) at gstpad.c:4479 #9 0x20313528 in gst_pad_push (pad=0x2186b808, buffer=0x217f1320) at gstpad.c:4704 #10 0x202f8a78 in gst_proxy_pad_do_chain (pad=optimized out, buffer=optimized out) at gstghostpad.c:171 #11 0x2030f394 in gst_pad_chain_data_unchecked (cache=0x4d61e9a0, ---Type return to continue, or q return to quit--- data=0x217f1320, is_buffer=1, pad=0x2186b040) at gstpad.c:4247 #12 gst_pad_push_data (pad=optimized out, is_buffer=1, data=0x217f1320, cache=optimized out) at gstpad.c:4479 #13 0x20313528 in gst_pad_push (pad=0x2186a8c8, buffer=0x217f1320) at gstpad.c:4704 #14 0x1c3b5614 in gst_queue_push_one (queue=0x2186d0b8) at gstqueue.c:1155 #15 gst_queue_loop (pad=optimized out) at gstqueue.c:1263 #16 0x20341500 in gst_task_func (task=0x2182e6b0) at gsttask.c:318 #17 0x20342c74 in default_func (tdata=optimized out, pool=optimized out) at gsttaskpool.c:70 #18 0x1f7deae4 in ?? () from /lib/libglib-2.0.so.0 #19 0x1f7db6bc in ?? () from /lib/libglib-2.0.so.0 #20 0x203c07a0 in start_thread () from /lib/powerpc-linux-gnu/libpthread.so.0 #21 0x1f5629f0 in clone () from /lib/powerpc-linux-gnu/libc.so.6 Thread 2 (Thread 0x4cbf52e0 (LWP 4200)): #0 0x203c61ec in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/powerpc-linux-gnu/libpthread.so.0 #1 0x203416dc in gst_task_func (task=0x2182e050) at gsttask.c:303 #2 0x20342c74 in default_func (tdata=optimized out, pool=optimized out) at gsttaskpool.c:70 #3 0x1f7deae4 in ?? () from /lib/libglib-2.0.so.0 #4 0x1f7db6bc in ?? () from /lib/libglib-2.0.so.0 ---Type return to continue, or q return to quit--- #5 0x203c07a0 in start_thread () from /lib/powerpc-linux-gnu/libpthread.so.0 #6 0x1f5629f0 in clone () from /lib/powerpc-linux-gnu/libc.so.6 Thread 1 (Thread 0x480445d0 (LWP 4109)): #0 0x1f8d86b8 in g_type_check_instance_is_a () from /usr/lib/libgobject-2.0.so.0 #1 0x1febb7c8 in gtk_widget_get_visible () from /usr/lib/libgtk-x11-2.0.so.0 #2 0x1febd198 in gtk_widget_is_drawable () from /usr/lib/libgtk-x11-2.0.so.0 #3 0x1fdd5ab8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #4 0x1fd4d094 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #5 0x1f8a9df8 in ?? () from /usr/lib/libgobject-2.0.so.0 #6 0x1f8aba4c in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #7 0x1f8c1ac0 in ?? () from /usr/lib/libgobject-2.0.so.0 #8 0x1f8cb2e0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #9 0x1f8cb770 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #10 0x1febc344 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #11 0x1fca8f10 in gtk_container_propagate_expose () from /usr/lib/libgtk-x11-2.0.so.0 #12 0x1fc62650 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #13 0x1fca6f3c in gtk_container_forall () from /usr/lib/libgtk-x11-2.0.so.0 #14 0x1fca71f0 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #15 0x1fd4d094 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #16 0x1f8a9df8 in ?? () from /usr/lib/libgobject-2.0.so.0 ---Type return to continue, or q return to quit--- #17 0x1f8aba4c in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #18 0x1f8c1ac0 in ?? () from /usr/lib/libgobject-2.0.so.0 #19 0x1f8cb2e0 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #20 0x1f8cb770 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #21 0x1febc344 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #22 0x1fca8f10 in gtk_container_propagate_expose () from /usr/lib/libgtk-x11-2.0.so.0 #23 0x1fe4896c in ??
Bug#642705: marked as done (altos: FTBFS: altusmetrum.xsl:2483: element include: XInclude error : could not load release-notes-1.0.xsl, and no fallback was found)
Your message dated Wed, 28 Sep 2011 09:02:19 + with message-id e1r8q1z-0005op...@franck.debian.org and subject line Bug#642705: fixed in altos 1.0.2 has caused the Debian Bug report #642705, regarding altos: FTBFS: altusmetrum.xsl:2483: element include: XInclude error : could not load release-notes-1.0.xsl, and no fallback was found 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.) -- 642705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: altos Version: 1.0.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/build/altos-IeDkYX/altos-1.0.1/doc' xsltproc --stringparam section.autolabel 1 --xinclude -o altusmetrum.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl altusmetrum.xsl warning: failed to load external entity release-notes-1.0.xsl altusmetrum.xsl:2483: element include: XInclude error : could not load release-notes-1.0.xsl, and no fallback was found Element include in namespace 'http://www.w3.org/2001/XInclude' encountered in appendix, but no template matches. xsltproc --stringparam section.autolabel 1 --xinclude -o altos.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl altos.xsl xsltproc --stringparam section.autolabel 1 --xinclude -o telemetry.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl telemetry.xsl xsltproc --stringparam section.autolabel 1 --xinclude -o release-notes-0.7.1.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl release-notes-0.7.1.xsl xsltproc --stringparam section.autolabel 1 --xinclude -o release-notes-0.8.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl release-notes-0.8.xsl xsltproc --stringparam section.autolabel 1 --xinclude -o release-notes-0.9.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl release-notes-0.9.xsl xsltproc --stringparam section.autolabel 1 --xinclude -o release-notes-0.9.2.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl release-notes-0.9.2.xsl xsltproc --stringparam section.autolabel 1 --xinclude -o release-notes-1.0.1.html /usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl release-notes-1.0.1.xsl xsltproc --stringparam section.autolabel 1 --xinclude -o altusmetrum.fo /usr/share/xml/docbook/stylesheet/docbook-xsl/fo/docbook.xsl altusmetrum.xsl warning: failed to load external entity release-notes-1.0.xsl altusmetrum.xsl:2483: element include: XInclude error : could not load release-notes-1.0.xsl, and no fallback was found Making portrait pages on USletter paper (8.5inx11in) Element include in namespace 'http://www.w3.org/2001/XInclude' encountered in appendix, but no template matches. fop -fo altusmetrum.fo -pdf altusmetrum.pdf [warning] /usr/bin/fop: Unable to locate servlet-api in /usr/share/java Exception java.lang.IllegalArgumentException: Cannot open file sRGB.pf make[3]: *** [altusmetrum.pdf] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/altos_1.0.1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: altos Source-Version: 1.0.2 We believe that the bug you reported is fixed in the latest version of altos, which is due to be installed in the Debian FTP archive: altos_1.0.2.dsc to main/a/altos/altos_1.0.2.dsc altos_1.0.2.tar.gz to main/a/altos/altos_1.0.2.tar.gz altos_1.0.2_i386.deb to main/a/altos/altos_1.0.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 642...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bdale Garbee bd...@gag.com (supplier of updated altos 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
Bug#643473: python-kinterbasdb: FTBFS: _configtest.c:7:3: error: unknown type name 'useconds_t'
tags 643473 patch upstream thanks -=| Damyan Ivanov, 27.09.2011 18:16:17 +0300 |=- In fb2.1: #define isc_info_db_impl_isc_aisc_info_db_impl_isc_apl_68K #define isc_info_db_impl_isc_uisc_info_db_impl_isc_vax_ultr #define isc_info_db_impl_isc_visc_info_db_impl_isc_vms #define isc_info_db_impl_isc_sisc_info_db_impl_isc_sun_68k Just substituting the left side with the right in _kiservices.c should fix the FTBFS. It appears the defines are just aliases for the full names, which are provided, so just dropping the removed constants is the way to go. Patch available at http://anonscm.debian.org/gitweb/?p=collab-maint/python-kinterbasdb.git;a=blob;f=debian/patches/02_drop_removed_fb_defines.patch;hb=HEAD signature.asc Description: Digital signature
Processed: gcc ia64 work around
Processing commands for cont...@bugs.debian.org: severity 642313 important Bug #642313 [src:gcc-4.6] FTBFS on ia64: ../../../src/libgcc/../gcc/libgcc2.c:404:1: internal compiler error: Segmentation fault Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 642313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642313 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#643467: reprepro: FTBFS: ar.c:253:3: error: format not a string literal and no format arguments [-Werror=format-security]
package reprepro tags 643467 + pending thanks * Didier Raboud o...@debian.org [110927 14:43]: ar.c: In function 'ar_archivemember_read': ar.c:253:3: error: format not a string literal and no format arguments [-Werror=format-security] ar.c: In function 'ar_archivemember_open': ar.c:277:2: error: format not a string literal and no format arguments [-Werror=format-security] ar.c: In function 'ar_archivemember_close': ar.c:297:2: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors ieeks, why is -Wformat-security not part of -Wextra? Luckily those error messages only contain strerror, libz's error messages and the command line arguments given as external uncompressors, so fixing this in unstable should be enough and no security upload for stable should be necessary. Fixed in git, will be in the next version. Thus tagging pending. Bernhard R. Link -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): tag 643467 pending and reassign to binary package
Processing commands for cont...@bugs.debian.org: package src:reprepro Limiting to bugs with field 'package' containing at least one of 'src:reprepro' Limit currently set to 'package':'src:reprepro' tags 643467 + pending Bug #643467 [src:reprepro] reprepro: FTBFS: ar.c:253:3: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) pending. reassign 643467 reprepro 4.7.0-1 Bug #643467 [src:reprepro] reprepro: FTBFS: ar.c:253:3: error: format not a string literal and no format arguments [-Werror=format-security] Bug reassigned from package 'src:reprepro' to 'reprepro'. package: reprepro' does not match at least one of src:reprepro Failed to clear fixed versions and reopen on 643467: limit failed for bugs: 643467. thanks Stopping processing here. Please contact me if you need assistance. -- 643467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643467 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#643397: marked as done (gnurobbo: FTBFS: konstruktor.c:248:5: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Wed, 28 Sep 2011 09:35:00 + with message-id e1r8qxc-0001cl...@franck.debian.org and subject line Bug#643397: fixed in gnurobbo 0.66+dfsg-2 has caused the Debian Bug report #643397, regarding gnurobbo: FTBFS: konstruktor.c:248:5: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gnurobbo Version: 0.66+dfsg-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -pipe -Wall `sdl-config --cflags` -DPLATFORM_PC -DVERSION=\0.66\ -DPACKAGE_DATA_DIR=\/usr/share/games/gnurobbo\ -DHAVE_DESIGNER -c konstruktor.c -o konstruktor.o konstruktor.c: In function 'konstruktor_init': konstruktor.c:248:5: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c: In function 'konstruktor_click': konstruktor.c:689:3: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:746:3: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:784:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:786:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:886:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:905:8: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1029:3: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1036:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1038:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1059:3: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1082:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1085:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1088:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1091:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1100:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1103:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1106:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1117:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1120:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1123:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1126:10: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1133:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1158:8: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1168:7: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1188:8: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1196:4: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1198:4: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1210:5: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1213:5: error: format not a string literal and no format arguments [-Werror=format-security] konstruktor.c:1279:8: error: format not a string literal and no
Processed: block 622279 with 643458 643440
Processing commands for cont...@bugs.debian.org: block 622279 with 643458 643440 Bug #622279 [release.debian.org] transition: python-defaults (switching default: 2.6 - 2.7) Was blocked by: 628860 629085 628243 625676 633457 623587 622966 623578 629087 625171 606363 631800 622912 625153 632249 624917 631823 625040 624940 621879 638692 625880 639072 631820 640581 624824 625151 624901 634544 634452 626800 625520 632582 632367 618094 640626 599127 641346 608640 622976 628827 622154 633145 553961 625677 625108 629091 623418 622001 618055 622072 625722 625853 622070 642708 621992 555767 640564 634528 625137 606006 616364 639119 623165 605875 635356 626259 621402 628820 635498 625678 622978 618084 628826 624889 553930 621948 632225 628830 629122 624787 633461 628839 626199 629817 638247 623927 625707 624950 625115 554552 632228 629148 628852 631856 629145 624740 626421 618159 641637 631821 629090 641488 606681 622027 625011 624811 626416 624982 606642 625679 624597 625087 625135 610777 634454 632234 633408 628828 624429 621932 Added blocking bug(s) of 622279: 643458 and 643440 thanks Stopping processing here. Please contact me if you need assistance. -- 622279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622279 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#634405: Fixing RCs #634405 and #642756
Hi Thomas, it seems like neither you nor me can find a proper solution to solve the parallel building problems highlighted by bugs #634405 and #642756. Hence, I propose to simply drop parallel building support, with the attached patch. What do you think ? Cheers, -- OdyX From f2aa63bfa8d9dcd59bbc5ae3ff216f3f7cc96883 Mon Sep 17 00:00:00 2001 From: Didier Raboud o...@debian.org Date: Wed, 28 Sep 2011 11:33:47 +0200 Subject: [PATCH] Don't build in parallel at all as it repeatedly fails. Closes: #634405 Closes: #642756 --- debian/rules |5 - 1 files changed, 0 insertions(+), 5 deletions(-) diff --git a/debian/rules b/debian/rules index 228964f..a88be41 100755 --- a/debian/rules +++ b/debian/rules @@ -22,11 +22,6 @@ else TEST=test endif -ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) - NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) - SCONSFLAGS = -j $(NUMJOBS) -endif - SCONSOPTS = $(SCONSFLAGS) VERSION=$(VERSION) \ PREFIX=$(PREFIX) PREFIX_CONF=/etc \ CHMDOCS=0 \ -- 1.7.2.5 signature.asc Description: This is a digitally signed message part.
Bug#642952: libpam0g-dev: Move of static libraries results in static linking due to library order
Am Montag, den 26.09.2011, 00:17 -0700 schrieb Steve Langasek: On Mon, Sep 26, 2011 at 09:01:13AM +0200, Paul Menzel wrote: affects 642952 libpam-gnome-keyring thanks Am Sonntag, den 25.09.2011, 14:55 -0700 schrieb Russ Allbery: […] This, among other things, will cause a FTBFS for all PAM modules on platforms where shared module code has to be built PIC. See the build logs for libpam-krb5, for example. After upgrading to 1.1.3-3 and rebooting Evolution could not get any passwords from GNOME Keyring with the following error messages. Gkr-Message: received an invalid, unencryptable, or non-utf8 secret Gkr-Message: call to daemon returned an invalid response: (null).(null)() Gkr-Message: received an invalid, unencryptable, or non-utf8 secret Gkr-Message: call to daemon returned an invalid response: (null).(null)() (evolution:3945): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: Fehler bei der Kommunikation mit dem GNOME-Schlüsselbunddienst) Upgrading to 1.1.3-4, restarting GNOME Keyring daemon (`gnome-keyring-daemon --replace`) and then Evolution fixes the problem. No, that's not related to this bug. This bug only concerned the placement of .so files in the traditional vs. multiarch library path; that only impacts build-time linking software against libpam, it has no affect on the system at runtime. Can you think of a reason why this broke with 1.1.3-3 and was fixed by 1.1.3-4? Thanks, Paul signature.asc Description: This is a digitally signed message part
Bug#643495: marked as done (bridge-method-injector: FTBFS: Error building POM.)
Your message dated Wed, 28 Sep 2011 10:02:20 + with message-id e1r8qy4-0006zh...@franck.debian.org and subject line Bug#643495: fixed in bridge-method-injector 1.4-2 has caused the Debian Bug report #643495, regarding bridge-method-injector: FTBFS: Error building POM. 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.) -- 643495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bridge-method-injector Version: 1.4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Fri Sep 23 22:24:39 CEST 2011 [INFO] Final Memory: 15M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/bridge-method-injector_1.4-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: bridge-method-injector Source-Version: 1.4-2 We believe that the bug you reported is fixed in the latest version of bridge-method-injector, which is due to be installed in the Debian FTP archive: bridge-method-injector_1.4-2.debian.tar.gz to main/b/bridge-method-injector/bridge-method-injector_1.4-2.debian.tar.gz bridge-method-injector_1.4-2.dsc to main/b/bridge-method-injector/bridge-method-injector_1.4-2.dsc libbridge-method-injector-java-doc_1.4-2_all.deb to main/b/bridge-method-injector/libbridge-method-injector-java-doc_1.4-2_all.deb libbridge-method-injector-java_1.4-2_all.deb to main/b/bridge-method-injector/libbridge-method-injector-java_1.4-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Page james.p...@ubuntu.com (supplier of updated bridge-method-injector package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Sep 2011 09:46:23 +0100 Source: bridge-method-injector Binary: libbridge-method-injector-java libbridge-method-injector-java-doc Architecture: source all Version: 1.4-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: James Page james.p...@ubuntu.com Description: libbridge-method-injector-java - Evolve Java classes without breaking compatibility libbridge-method-injector-java-doc - Documentation for Bridge Method Injector Closes: 643495 Changes: bridge-method-injector (1.4-2) unstable; urgency=low . * Fix FTBFS with asm3 = 3.3 (LP: #851659): - d/maven.rules: Use asm-all instead of asm to align to restructure of jar files. * Fix FTBFS due to changes to maven-compiler-plugin (Closes: #643495): - d/control: Added libmaven-plugin-tools-java to Build-Deps-Indep. * debian/copyright: Tidied new lintian warnings. Checksums-Sha1: f80275f5d43f753dbb19fbd19876c9c5c317f1b4
Bug#643496: marked as done (build-helper-maven-plugin: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 10:02:33 + with message-id e1r8qyh-0006d5...@franck.debian.org and subject line Bug#643496: fixed in build-helper-maven-plugin 1.5-2 has caused the Debian Bug report #643496, regarding build-helper-maven-plugin: FTBFS: Error building POM 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.) -- 643496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: build-helper-maven-plugin Version: 1.5-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Sep 23 22:25:58 CEST 2011 [INFO] Final Memory: 5M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/build-helper-maven-plugin_1.5-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: build-helper-maven-plugin Source-Version: 1.5-2 We believe that the bug you reported is fixed in the latest version of build-helper-maven-plugin, which is due to be installed in the Debian FTP archive: build-helper-maven-plugin_1.5-2.debian.tar.gz to main/b/build-helper-maven-plugin/build-helper-maven-plugin_1.5-2.debian.tar.gz build-helper-maven-plugin_1.5-2.dsc to main/b/build-helper-maven-plugin/build-helper-maven-plugin_1.5-2.dsc libbuild-helper-maven-plugin-java-doc_1.5-2_all.deb to main/b/build-helper-maven-plugin/libbuild-helper-maven-plugin-java-doc_1.5-2_all.deb libbuild-helper-maven-plugin-java_1.5-2_all.deb to main/b/build-helper-maven-plugin/libbuild-helper-maven-plugin-java_1.5-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Schmitz matth...@sigxcpu.org (supplier of updated build-helper-maven-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Sep 2011 11:38:18 +0200 Source: build-helper-maven-plugin Binary: libbuild-helper-maven-plugin-java libbuild-helper-maven-plugin-java-doc Architecture: source all Version: 1.5-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Matthias Schmitz matth...@sigxcpu.org Description: libbuild-helper-maven-plugin-java - Build Helper Maven Plugin libbuild-helper-maven-plugin-java-doc - Documentation for Build Helper Maven Plugin Closes: 643496 Changes: build-helper-maven-plugin (1.5-2) unstable; urgency=low . * Add libmaven-plugin-tools-java to Build-Depends-Indep (Closes: #643496) Checksums-Sha1: ffbeeac1465ed9eb2f3e9654699b59b9703abd93 2466 build-helper-maven-plugin_1.5-2.dsc 42d75bd7de1dedc093e270267c0f3da2fc8c90e4 4026 build-helper-maven-plugin_1.5-2.debian.tar.gz 2d181ba60cc24848dd98e56b25b6c0f13c4a3a83 19884
Bug#642817: pyxnat: FTBFS: tests failed
Hi, The tests require an internet connection because the package is a Python module to communicate with a database platform on top of Web Services. To check that everything runs correctly, I test the functions against a public server. I know it's not ideal, but there is no other way. Regards, Yannick On 27/09/2011 17:50, Mehdi Dogguy wrote: On 27/09/2011 16:32, Yannick SCHWARTZ wrote: Hi, Does the build machine have an internet connection? My package needs to connect to a database server to perform its tests. Your pacakge is supposed to build just find, even if network is down. fine I think that accessing wild network is intentionally forbidden of ^^ on Grid'5000 when doing these archive rebuilds. sorry. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643643: error: conflicting declaration 'typedef long unsigned int intptr_t'
Package: vxl Version: 1.14.0-9 Severity: serious Tags: upstream Justification: fails to build from source vxl does not build on alpha. It fails with: Scanning dependencies of target Qv make[3]: Leaving directory `/build/buildd-vxl_1.14.0-9-alpha-ePSG6G/vxl-1.14.0/Build' make[3]: Entering directory `/build/buildd-vxl_1.14.0-9-alpha-ePSG6G/vxl-1.14.0/Build' [ 6%] Building CXX object v3p/Qv/CMakeFiles/Qv.dir/vecutil.o [ 6%] Building CXX object v3p/Qv/CMakeFiles/Qv.dir/QvLib.o In file included from /build/buildd-vxl_1.14.0-9-alpha-ePSG6G/vxl-1.14.0/v3p/Qv/QvLib.cxx:69: /build/buildd-vxl_1.14.0-9-alpha-ePSG6G/vxl-1.14.0/v3p/Qv/QvDict.cxx:12: error: conflicting declaration 'typedef long unsigned int intptr_t' /usr/include/unistd.h:268: error: 'intptr_t' has a previous declaration as 'typedef __intptr_t intptr_t' make[3]: *** [v3p/Qv/CMakeFiles/Qv.dir/QvLib.o] Error 1 make[2]: *** [v3p/Qv/CMakeFiles/Qv.dir/all] Error 2 make[3]: Leaving directory `/build/buildd-vxl_1.14.0-9-alpha-ePSG6G/vxl-1.14.0/Build' make[2]: Leaving directory `/build/buildd-vxl_1.14.0-9-alpha-ePSG6G/vxl-1.14.0/Build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-vxl_1.14.0-9-alpha-ePSG6G/vxl-1.14.0/Build' make: *** [debian/stamp-makefile-build] Error 2 -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642817: pyxnat: FTBFS: tests failed
On Wed, Sep 28, 2011 at 11:03:01 +0200, Yannick SCHWARTZ wrote: Hi, The tests require an internet connection because the package is a Python module to communicate with a database platform on top of Web Services. To check that everything runs correctly, I test the functions against a public server. I know it's not ideal, but there is no other way. Then either some dummy server should be available in the package to run tests against, or the tests should not be run at package build time. A connection to a non-local address is not ok. Cheers, Julien -- Julien Cristau julien.cris...@logilab.fr Logilab http://www.logilab.fr/ Informatique scientifique gestion de connaissances -- 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#632393: FTBFS with Python 2.7: Python.h: No such file or directory
Processing commands for cont...@bugs.debian.org:
severity 632393 serious
Bug #632393 {Done: Atsuhito KOHDA ko...@debian.org} [src:texworks] texworks:
FTBFS with Python 2.7: Python.h: No such file or directory
Severity set to 'serious' from 'important'
found 632393 0.5~svn939-1
Bug #632393 {Done: Atsuhito KOHDA ko...@debian.org} [src:texworks] texworks:
FTBFS with Python 2.7: Python.h: No such file or directory
Bug Marked as found in versions texworks/0.5~svn939-1; no longer marked as
fixed in versions texworks/0.5~svn939-1 and reopened.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
632393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632393
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#642436: marked as done (python-ldb: built only for Python 2.7)
Your message dated Wed, 28 Sep 2011 10:22:56 +
with message-id e1r8ri0-dh...@franck.debian.org
and subject line Bug#642436: fixed in ldb 1:1.1.2~git20110807-2
has caused the Debian Bug report #642436,
regarding python-ldb: built only for Python 2.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
642436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-ldb
Version: 1:1.1.2~git20110807-1
Severity: grave
Justification: renders package unusable
python-ldb ships only modules for Python 2.7, which is not the default
version in Debian.
BTW, contrary to what the changelog say, this packages doesn't use
dh_python2. From the build log:
|dh_gencontrol -a
| dpkg-gencontrol: warning: Depends field of package python-ldb: unknown
substitution variable ${python:Depends}
--
Jakub Wilk
---End Message---
---BeginMessage---
Source: ldb
Source-Version: 1:1.1.2~git20110807-2
We believe that the bug you reported is fixed in the latest version of
ldb, which is due to be installed in the Debian FTP archive:
ldb-tools_1.1.2~git20110807-2_amd64.deb
to main/l/ldb/ldb-tools_1.1.2~git20110807-2_amd64.deb
ldb_1.1.2~git20110807-2.debian.tar.gz
to main/l/ldb/ldb_1.1.2~git20110807-2.debian.tar.gz
ldb_1.1.2~git20110807-2.dsc
to main/l/ldb/ldb_1.1.2~git20110807-2.dsc
libldb-dev_1.1.2~git20110807-2_amd64.deb
to main/l/ldb/libldb-dev_1.1.2~git20110807-2_amd64.deb
libldb1-dbg_1.1.2~git20110807-2_amd64.deb
to main/l/ldb/libldb1-dbg_1.1.2~git20110807-2_amd64.deb
libldb1_1.1.2~git20110807-2_amd64.deb
to main/l/ldb/libldb1_1.1.2~git20110807-2_amd64.deb
python-ldb-dbg_1.1.2~git20110807-2_amd64.deb
to main/l/ldb/python-ldb-dbg_1.1.2~git20110807-2_amd64.deb
python-ldb-dev_1.1.2~git20110807-2_amd64.deb
to main/l/ldb/python-ldb-dev_1.1.2~git20110807-2_amd64.deb
python-ldb_1.1.2~git20110807-2_amd64.deb
to main/l/ldb/python-ldb_1.1.2~git20110807-2_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 642...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jelmer Vernooij jel...@debian.org (supplier of updated ldb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 27 Sep 2011 19:49:00 +0200
Source: ldb
Binary: libldb1 libldb1-dbg ldb-tools libldb-dev python-ldb python-ldb-dev
python-ldb-dbg
Architecture: source amd64
Version: 1:1.1.2~git20110807-2
Distribution: unstable
Urgency: low
Maintainer: Jelmer Vernooij jel...@debian.org
Changed-By: Jelmer Vernooij jel...@debian.org
Description:
ldb-tools - LDAP-like embedded database - tools
libldb-dev - LDAP-like embedded database - development files
libldb1- LDAP-like embedded database - shared library
libldb1-dbg - LDAP-like embedded database - debug symbols
python-ldb - Python bindings for LDB
python-ldb-dbg - Python bindings for LDB - debug extension
python-ldb-dev - LDB python bindings - development files
Closes: 642436
Changes:
ldb (1:1.1.2~git20110807-2) unstable; urgency=low
.
* Explicitly build with dh_python2.
* Build against system Python rather than specifically 2.7. Closes: #642436
Checksums-Sha1:
3b01545029436b4595e0d746172a8781ece9653b 1728 ldb_1.1.2~git20110807-2.dsc
18bb9344bbf9b0c71517a63bc93a0ac27017e394 11777
ldb_1.1.2~git20110807-2.debian.tar.gz
772853d9b6889c196d95459ee64df6d0c6fcef34 141802
libldb1_1.1.2~git20110807-2_amd64.deb
6899cc1d24a40478bfdae613ea7015bf6e426768 240918
libldb1-dbg_1.1.2~git20110807-2_amd64.deb
f7e8136daabc6452ed56b566c1c70c6df33e49f4 38296
ldb-tools_1.1.2~git20110807-2_amd64.deb
7405de992177c4c69961ed8c62b06b8a2d1b6e3e 276516
libldb-dev_1.1.2~git20110807-2_amd64.deb
534c851442c7a21a1d30cba063c64d79aed47f8c 35486
python-ldb_1.1.2~git20110807-2_amd64.deb
16ab8f58f7b95e01dd7d7841791dec4cd6ba2038 7724
python-ldb-dev_1.1.2~git20110807-2_amd64.deb
dc4793ef8b8b6a3f7eeb7b6095540f4afc391fc2 50840
python-ldb-dbg_1.1.2~git20110807-2_amd64.deb
Checksums-Sha256:
bf518008874ffd35f9b732ec5a65b12ad00f20d73f45a00a9b967af7676c899f 1728
ldb_1.1.2~git20110807-2.dsc
ac207e339175c832c6be04a8d30f08022634090fa744ffe6619922fd7b0eb4fc 11777
ldb_1.1.2~git20110807-2.debian.tar.gz
Bug#643440: Patches for -Werror=format-security issues in mailutils
tag 643440 + patch
kthxbye
Hi,
You'll find attached two patches that fix the mailutils FTBFS with the
hardening build flags:
The first patch, fix_FTBFS_with_format-security.diff fixes the actual
-Werror=format-security issues. A lot of those are GCC pedantry, but I
think some may be real issues (the writeline hunks, for instance).
The second patch, refresh_mh_fmtgram.diff refreshes mh/mh_fmtgram.c from
the updated mh/mh_fmtgram.y (changed in the previous patch).
The diff is quite noisy as the file was generated by upstream with an
older version of bison than that currently in sid.
Cheers,
--
Nicolas Dandrimont
Description: Fix FTBFS with -Werror=format-security
Author: Nicolas Dandrimont nicolas.dandrim...@crans.org
Bug-Debian: http://bugs.debian.org/643440
Last-Update: 2011-09-28
Index: mailutils-2.2+dfsg1/libproto/pop/pop3_sendline.c
===
--- mailutils-2.2+dfsg1.orig/libproto/pop/pop3_sendline.c 2011-09-28 12:03:00.0 +0200
+++ mailutils-2.2+dfsg1/libproto/pop/pop3_sendline.c 2011-09-28 12:04:41.0 +0200
@@ -112,7 +112,7 @@
{
if (line)
{
- int status = mu_pop3_writeline (pop3, line);
+ int status = mu_pop3_writeline (pop3, %s, line);
if (status)
return status;
}
Index: mailutils-2.2+dfsg1/libproto/nntp/nntp_sendline.c
===
--- mailutils-2.2+dfsg1.orig/libproto/nntp/nntp_sendline.c 2011-09-28 12:03:00.0 +0200
+++ mailutils-2.2+dfsg1/libproto/nntp/nntp_sendline.c 2011-09-28 12:04:41.0 +0200
@@ -112,7 +112,7 @@
{
if (line)
{
- int status = mu_nntp_writeline (nntp, line);
+ int status = mu_nntp_writeline (nntp, %s, line);
if (status)
return status;
}
Index: mailutils-2.2+dfsg1/mail/retain.c
===
--- mailutils-2.2+dfsg1.orig/mail/retain.c 2011-09-28 12:04:24.0 +0200
+++ mailutils-2.2+dfsg1/mail/retain.c 2011-09-28 12:04:41.0 +0200
@@ -33,7 +33,7 @@
if (argc == 1)
{
if (mu_list_is_empty (*list))
- fprintf (ofile, _(msg));
+ fprintf (ofile, %s, _(msg));
else
util_slist_print (*list, 1);
return 0;
Index: mailutils-2.2+dfsg1/mail/unset.c
===
--- mailutils-2.2+dfsg1.orig/mail/unset.c 2011-09-28 12:04:24.0 +0200
+++ mailutils-2.2+dfsg1/mail/unset.c 2011-09-28 12:04:41.0 +0200
@@ -38,7 +38,7 @@
char *buf = xmalloc ((7+strlen (argv[i])) * sizeof (char));
strcpy (buf, set no);
strcat (buf, argv[i]);
- if (!util_do_command (buf))
+ if (!util_do_command (%s, buf))
status = 1;
free (buf);
}
Index: mailutils-2.2+dfsg1/mh/mh_fmtgram.y
===
--- mailutils-2.2+dfsg1.orig/mh/mh_fmtgram.y 2011-09-28 12:04:24.0 +0200
+++ mailutils-2.2+dfsg1/mh/mh_fmtgram.y 2011-09-28 12:04:41.0 +0200
@@ -207,7 +207,7 @@
else
{
yyerror (_(undefined function));
- mu_error ($1);
+ mu_error (%s, $1);
YYERROR;
}
}
Index: mailutils-2.2+dfsg1/mh/mhn.c
===
--- mailutils-2.2+dfsg1.orig/mh/mhn.c 2011-09-28 12:04:24.0 +0200
+++ mailutils-2.2+dfsg1/mh/mhn.c 2011-09-28 12:04:41.0 +0200
@@ -1644,7 +1644,7 @@
int rc;
asprintf (p, _(File %s already exists. Rewrite), name);
- rc = mh_getyn (p);
+ rc = mh_getyn (%s, p);
free (p);
if (!rc)
{
Index: mailutils-2.2+dfsg1/imap4d/append.c
===
--- mailutils-2.2+dfsg1.orig/imap4d/append.c 2011-09-28 12:04:24.0 +0200
+++ mailutils-2.2+dfsg1/imap4d/append.c 2011-09-28 12:04:41.0 +0200
@@ -204,7 +204,7 @@
if (status == 0)
return util_finish (command, RESP_OK, Completed);
- return util_finish (command, RESP_NO, err_text);
+ return util_finish (command, RESP_NO, %s, err_text);
}
Index: mailutils-2.2+dfsg1/imap4d/status.c
===
--- mailutils-2.2+dfsg1.orig/imap4d/status.c 2011-09-28 12:04:24.0 +0200
+++ mailutils-2.2+dfsg1/imap4d/status.c 2011-09-28 12:04:41.0 +0200
@@ -148,7 +148,7 @@
if (count == 0)
return util_finish (command, RESP_BAD, Too few args (empty list));
else if (err_msg)
- return util_finish (command, RESP_BAD, err_msg);
+ return util_finish (command, RESP_BAD, %s, err_msg);
return util_finish (command, RESP_OK, Completed);
}
Index: mailutils-2.2+dfsg1/imap4d/delete.c
===
--- mailutils-2.2+dfsg1.orig/imap4d/delete.c 2011-09-28 12:04:24.0 +0200
+++ mailutils-2.2+dfsg1/imap4d/delete.c 2011-09-28 12:04:41.0 +0200
@@ -59,5 +59,5 @@
rc = RESP_NO;
msg
Processed: Patches for -Werror=format-security issues in mailutils
Processing commands for cont...@bugs.debian.org: tag 643440 + patch Bug #643440 [src:mailutils] mailutils: FTBFS: pop3_sendline.c:115:7: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) patch. kthxbye Stopping processing here. Please contact me if you need assistance. -- 643440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643440 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#643501: jenkins-crypto-util: FTBFS: Test failures
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The certificates that the test use have expired - and now the tests are failing. I will raise this upstream - -- James Page Ubuntu Server Developer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJOgvmvAAoJEL/srsug59jD7IAP/3Xa4g79QnUWQOgVDrsvGKc1 83tM4tAv2GGIAbnHbZiRPAk9IIgz9ATeppkYTr7x68byBUei6vWlleUovwhMTvRH YnGz0/v0Mu91+QIefJpAOx6rpiHCQtVAxc2vOVEPLnxa8/ZocOoYPFf4Q/cf7agk 9MCsZ7eW18+JnxiYol/hdb7UnUfmQUSobbtZCpjntM1W00icTLghnHu89ghTLnp6 2wbF3aUkHIhoQDzG46J4tTRbmhf1BPtTPumrzQbTByIG/wpUfISrltI3ASEMfkRi RUwncpcvvhkXQ6PmHso1oV3VZfiy+ZBzr+b+UTCCRG9LMjBUZJfrr1arj9BfHisU qtZPukv8AyVfrhBHwzStPGrIqs5Lafd2ENuvKzJZd+DkUmg/QEejcuCL6VRIHNS6 Inotb/U5iXBUPekzagQYeE4TvcFkmQwwJwKqY/x//ufCZrnMrfZtnHRrlUqfu9Lw ZygryqjnxkVIwA/VJFu7jPJYs09umA2r5wMJy1emUWo+3p8OpyCrMGE+N+KQBJdt 26G57zvcdEayZc+cXSp2ING7mZGNv/sqH1zcgW7Lr+mjKdXdjh4t+P9S7taFEUvE QYpz83n1PFxUbff+YUJDncFkdr0T54Srlp75R38bQ1eATVyvaO8DywInlMisM0gf YigIIzRe8CfCQ138wW9s =euPN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643648: CVE-2011-2834 and CVE-2011-2821
Package: libxml2 Severity: serious Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, two libxml2 issues were fixed in the latest chrome updates: CVE-2011-2821 Double free vulnerability in libxml2, as used in Google Chrome before 13.0.782.215, allows remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted XPath expression. Patch: http://git.gnome.org/browse/libxml2/commit/?id=fec31bcd452e77c10579467ca87a785b41115de6 CVE-2011-2834 Double free vulnerability in libxml2, as used in Google Chrome before 14.0.835.163, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to XPath handling. Patch: http://src.chromium.org/viewvc/chrome?view=revrevision=98359 Cheers, Giuseppe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6C/OYACgkQNxpp46476apt2ACdHKTvWjo4WoxEWsVD6Z7a9elU AFgAn2ml9iJvUDCXczdrJcVH1PIknJFT =EMJW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642817: pyxnat: FTBFS: tests failed
On 28/09/2011 11:03, Yannick SCHWARTZ wrote: Hi, The tests require an internet connection because the package is a Python module to communicate with a database platform on top of Web Services. To check that everything runs correctly, I test the functions against a public server. I guessed as much. I know it's not ideal, but there is no other way. ditto, from our side :) You can try to make tests check optional (iow, detect if you're compiling on a buildd machine). Kind regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.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 643402
Processing commands for cont...@bugs.debian.org: tags 643402 + pending Bug #643402 [src:gtetrinet] gtetrinet: FTBFS: tetrinet.c:235:46: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 643402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643402 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#642693: marked as done ([xul-ext-firetray] unusable in testing)
Your message dated Wed, 28 Sep 2011 11:17:32 + with message-id e1r8s8q-0007i2...@franck.debian.org and subject line Bug#642693: fixed in firetray 0.3.1-2 has caused the Debian Bug report #642693, regarding [xul-ext-firetray] unusable in testing 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.) -- 642693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xul-ext-firetray Version: 0.3.1-1 Severity: grave xul-ext-firetray 0.3.1-1 doesn't work with the current versions of iceweasel, icedove or iceape in testing, as well as unstable. As reported in #636848, icedove is too old for this version. iceape has the same problem. Since iceweasel 6 migrated to testing (today), this FireTray version is now too old for iceweasel, meaning FireTray is completely unusable. 0.3.2 at least would fix compatibility with iceweasel: http://code.google.com/p/firetray/downloads/detail?name=firetray-0.3.2.xpican=2q= --- System information. --- Architecture: i386 Kernel: Linux 3.0.0-1-686-pae Debian Release: wheezy/sid 990 testing security.debian.org 990 testing ftp.ca.debian.org 500 unstable ftp.ca.debian.org 1 experimental ftp.ca.debian.org --- Package information. --- Depends (Version) | Installed -+-== libc6 (= 2.3.6-6~) | 2.13-21 libgcc1 (= 1:4.1.1) | 1:4.6.1-4 libstdc++6 (= 4.4.0) | 4.6.1-4 Recommends (Version) | Installed ==-+- iceweasel (= 3.0) | 6.0.2-1 OR icedove (= 3.0) | 3.1.13-1 OR iceape (= 2.0~a1) | 2.0.14-7 Package's Suggests field is empty. ---End Message--- ---BeginMessage--- Source: firetray Source-Version: 0.3.1-2 We believe that the bug you reported is fixed in the latest version of firetray, which is due to be installed in the Debian FTP archive: firetray_0.3.1-2.debian.tar.gz to main/f/firetray/firetray_0.3.1-2.debian.tar.gz firetray_0.3.1-2.dsc to main/f/firetray/firetray_0.3.1-2.dsc xul-ext-firetray_0.3.1-2_i386.deb to main/f/firetray/xul-ext-firetray_0.3.1-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 642...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sascha Girrulat sas...@girrulat.de (supplier of updated firetray package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 26 Sep 2011 20:12:35 +0200 Source: firetray Binary: xul-ext-firetray Architecture: source i386 Version: 0.3.1-2 Distribution: unstable Urgency: low Maintainer: Debian Mozilla Extension Maintainers pkg-mozext-maintain...@lists.alioth.debian.org Changed-By: Sascha Girrulat sas...@girrulat.de Description: xul-ext-firetray - system tray extension for Thunderbird/Firefox alike apps Closes: 642693 Changes: firetray (0.3.1-2) unstable; urgency=low . * [eb0ae20] add increase-supported-versions.patch * rebuild for xulrunner 6 (Closes: 642693) * [1edecd8] remove whitespace Checksums-Sha1: 973e32a37f5dd7fcc613735045074b3674724d3c 1380 firetray_0.3.1-2.dsc e866f753385d26ce63513202218aeb1664ff3122 7386 firetray_0.3.1-2.debian.tar.gz 626bbaa07e3c27e1a9a6923dd1ca4d67b06dad0d 164630 xul-ext-firetray_0.3.1-2_i386.deb Checksums-Sha256: 32922ecda41309438f48cc0d623be22b1299eee35a6acbc9c6c53fea7a9584ac 1380 firetray_0.3.1-2.dsc 77c3dc23c9c6252a0c57090b57628517f051c01212858fe3af2e01e31057213f 7386 firetray_0.3.1-2.debian.tar.gz d9225b31e12b40ac95f68b834a4c98baedb6f80a70f9ed3be56388f2d5c98012 164630 xul-ext-firetray_0.3.1-2_i386.deb Files: 9839f7fd8e19f821ba201d4dd1edc77f 1380 web extra firetray_0.3.1-2.dsc bd0e7741f95c0064180c6edcb98b5565 7386 web extra firetray_0.3.1-2.debian.tar.gz 4932ec7bf350ea11f47db53268a14b12 164630 web extra xul-ext-firetray_0.3.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFOgv7on88szT8+ZCYRAsvJAJ4hQKM6dmupGkNSAmfMWP96MDa9jwCfaS06 dRV+HI1Ac/zKVRJr3G0NrmI= =JlE2 -END PGP SIGNATURE- ---End Message---
Bug#643464: radeontool: FTBFS: radeontool.c:42:5: error: format not a string literal and no format arguments [-Werror=format-security]
tags 643464 + upstream
quit
Hi,
Didier Raboud wrote:
radeontool.c: In function 'fatal':
radeontool.c:42:5: error: format not a string literal and no format
arguments [-Werror=format-security]
Yep, known. The patch below (excluding the hunk patching radeonreg
since radeonreg is not in sid yet) should fix it. I'd like to send a
batch of patches upstream soon addressing warnings including this one,
but maybe it's worth an upload to fix the build before then.
-- 8 --
Subject: avoid -Wformat-security warnings
fatal() is never called with a user-specified argument so it is safe
to pass its argument as an fprintf format string, but gcc doesn't know
that. Using fprintf(stderr, %s, arg) makes the intent clearer.
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
Thanks,
Jonathan
avivotool.c |2 +-
radeonreg.c |2 +-
radeontool.c |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/avivotool.c b/avivotool.c
index 240f523f..02b03bab 100644
--- a/avivotool.c
+++ b/avivotool.c
@@ -64,7 +64,7 @@ unsigned char * volatile fb_mem;
static void fatal(char *why)
{
-fprintf(stderr, why);
+fprintf(stderr, %s, why);
pci_system_cleanup();
}
diff --git a/radeonreg.c b/radeonreg.c
index 9948665c..5f1ab61d 100644
--- a/radeonreg.c
+++ b/radeonreg.c
@@ -47,7 +47,7 @@ unsigned char * volatile fb_mem;
static void fatal(char *why)
{
-fprintf(stderr, why);
+fprintf(stderr, %s, why);
pci_system_cleanup();
}
diff --git a/radeontool.c b/radeontool.c
index 6e269f1a..97b2c406 100644
--- a/radeontool.c
+++ b/radeontool.c
@@ -39,7 +39,7 @@ unsigned char * volatile ctrl_mem;
static void radeon_rom_legacy_mmio_table(unsigned char *bios, int offset);
static void fatal(char *why)
{
-fprintf(stderr,why);
+fprintf(stderr, %s, why);
pci_system_cleanup();
exit(-1);
}
--
1.7.7.rc1
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: radeontool: FTBFS: radeontool.c:42:5: error: format not a string literal and no format arguments [-Werror=format-security]
Processing commands for cont...@bugs.debian.org: tags 643464 + upstream Bug #643464 [src:radeontool] radeontool: FTBFS: radeontool.c:42:5: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) upstream. End of message, stopping processing here. Please contact me if you need assistance. -- 643464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643464 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#632393: FTBFS with Python 2.7: Python.h: No such file or directory
Hi Jakub, On Wed, 28 Sep 2011 12:18:27 +0200, Jakub Wilk wrote: It seems that this hunk of my patch was not applied. As a result, texworks FTBFS: H, it looks really so. I remembered to have applied texworks-pydefaults.diff but something might have went wrong. I'll soon upload a fixed package. Thanks for your report. Best regards, 2011-9-28(Wed) -- Debian Developer - much more I18N of Debian Atsuhito Kohda kohda AT debian.org Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642723: marked as done (leiningen: FTBFS: Could not find the main class: clojure.main. Program will exit.)
Your message dated Wed, 28 Sep 2011 12:20:25 + with message-id e1r8t7h-0007ra...@franck.debian.org and subject line Bug#642723: fixed in leiningen 1.6.1-2 has caused the Debian Bug report #642723, regarding leiningen: FTBFS: Could not find the main class: clojure.main. Program will exit. 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.) -- 642723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: leiningen Version: 1.6.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/leiningen-34BUDA/leiningen-1.6.1' cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/header.html doc/DEPLOY.html sed -i'' -e 's/@TITLE@/Deploying Libraries/g' doc/DEPLOY.html markdown doc/DEPLOY.md doc/DEPLOY.html cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/footer.html doc/DEPLOY.html cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/header.html doc/HACKING.html sed -i'' -e 's/@TITLE@/Hacking Leiningen/g' doc/HACKING.html markdown doc/HACKING.md doc/HACKING.html cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/footer.html doc/HACKING.html cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/header.html doc/PLUGINS.html sed -i'' -e 's/@TITLE@/Leiningen Plugins/g' doc/PLUGINS.html markdown doc/PLUGINS.md doc/PLUGINS.html cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/footer.html doc/PLUGINS.html cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/header.html doc/TUTORIAL.html sed -i'' -e 's/@TITLE@/Tutorial/g' doc/TUTORIAL.html markdown doc/TUTORIAL.md doc/TUTORIAL.html cat /build/leiningen-34BUDA/leiningen-1.6.1/debian/footer.html doc/TUTORIAL.html jar cvf lancet.jar -C src/lancet . added manifest adding: core.clj(in = 5404) (out= 2049)(deflated 62%) LEIN_ROOT=y CLASSPATH=/build/leiningen-34BUDA/leiningen-1.6.1/lancet.jar bin/lein compile :all, jar Exception in thread main java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at clojure.lang.RT.loadClassForName(RT.java:1578) at clojure.lang.RT.load(RT.java:399) at clojure.lang.RT.load(RT.java:381) at clojure.core$load$fn__4519.invoke(core.clj:4915) at clojure.core$load.doInvoke(core.clj:4914) at clojure.lang.RestFn.invoke(RestFn.java:408) at clojure.core__init.load(Unknown Source) at clojure.core__init.clinit(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at clojure.lang.RT.loadClassForName(RT.java:1578) at clojure.lang.RT.load(RT.java:399) at clojure.lang.RT.load(RT.java:381) at clojure.lang.RT.doInit(RT.java:416) at clojure.lang.RT.clinit(RT.java:302) at clojure.main.clinit(main.java:20) Caused by: java.lang.ClassNotFoundException: org/objectweb/asm/commons/Method at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at clojure.core_proxy__init.load(Unknown Source) at clojure.core_proxy__init.clinit(Unknown Source) ... 18 more Could not find the main class: clojure.main. Program will exit. make[1]: *** [override_jh_build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/leiningen_1.6.1-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: leiningen Source-Version: 1.6.1-2 We believe that the bug you reported is fixed in the latest version of leiningen, which is due to be installed in the Debian FTP archive: leiningen_1.6.1-2.debian.tar.gz to main/l/leiningen/leiningen_1.6.1-2.debian.tar.gz leiningen_1.6.1-2.dsc to main/l/leiningen/leiningen_1.6.1-2.dsc leiningen_1.6.1-2_all.deb to main/l/leiningen/leiningen_1.6.1-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to
Bug#634567: marked as done (gcc-mingw-w64: FTBFS: x86_64-w64-mingw32-strip: '/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/x86_64-w64-mingw32/lib/libiberty.a': No such file)
Your message dated Wed, 28 Sep 2011 12:34:23 +
with message-id e1r8tld-0001eo...@franck.debian.org
and subject line Bug#634567: fixed in gcc-mingw-w64 1
has caused the Debian Bug report #634567,
regarding gcc-mingw-w64: FTBFS: x86_64-w64-mingw32-strip:
'/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/x86_64-w64-mingw32/lib/libiberty.a':
No such file
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.)
--
634567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: gcc-mingw-w64
Version: 0.3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110718 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[3]: Entering directory
`/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/build/x86_64-w64-mingw32/lto-plugin'
test -z /usr/lib/gcc/x86_64-w64-mingw32/4.6.1 || /bin/mkdir -p
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/gcc/x86_64-w64-mingw32/4.6.1
/bin/bash ./libtool --tag=disable-static --mode=install /usr/bin/install -c
liblto_plugin.la
'/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/gcc/x86_64-w64-mingw32/4.6.1'
libtool: install: /usr/bin/install -c .libs/liblto_plugin.so.0.0.0
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/gcc/x86_64-w64-mingw32/4.6.1/liblto_plugin.so.0.0.0
libtool: install: (cd
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/gcc/x86_64-w64-mingw32/4.6.1
{ ln -s -f liblto_plugin.so.0.0.0 liblto_plugin.so.0 || { rm -f
liblto_plugin.so.0 ln -s liblto_plugin.so.0.0.0 liblto_plugin.so.0; }; })
libtool: install: (cd
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/gcc/x86_64-w64-mingw32/4.6.1
{ ln -s -f liblto_plugin.so.0.0.0 liblto_plugin.so || { rm -f
liblto_plugin.so ln -s liblto_plugin.so.0.0.0 liblto_plugin.so; }; })
libtool: install: /usr/bin/install -c .libs/liblto_plugin.lai
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/gcc/x86_64-w64-mingw32/4.6.1/liblto_plugin.la
libtool: install: warning: remember to run `libtool --finish
/usr/lib/gcc/x86_64-w64-mingw32/4.6.1'
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/build/x86_64-w64-mingw32/lto-plugin'
make[2]: Leaving directory
`/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/build/x86_64-w64-mingw32/lto-plugin'
make[1]: Leaving directory
`/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/build/x86_64-w64-mingw32'
# Remove files which conflict with other packages
# gcc-4.6-locales
rm -rf
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/share/locale
# binutils-dev
rm -f
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/libiberty.a
# libstdc++6-4.6-dbg (potentially)
rm -rf
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/share/gcc-*/python
# libstdc++6-4.6-dev
ls -1
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/include/c++/4.6/|grep
-v w64-mingw32|xargs -I{} rm -rf
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/include/c++/4.6/{}
# -doc packages
rm -rf
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/share/info
rm -rf
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/share/man/man7
# No need to ship empty manpages
rm -rf
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/share/man/man1
# Drop .la files
find /build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64 -name
\*.la -delete
# Move libraries to base directories and add version-specific links
for gnu_upstream_version in $(basename
debian/gcc-mingw-w64/usr/share/gcc-*|cut -d- -f2); do \
if [ $gnu_upstream_version != 4.6 ]; then \
[ -d
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/include/c++
] cd
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/include/c++
ln -s 4.6 $gnu_upstream_version || true; \
for target in i686-w64-mingw32 x86_64-w64-mingw32; do \
cd
/build/gcc-mingw-w64-8PdFvG/gcc-mingw-w64-0.3/debian/gcc-mingw-w64/usr/lib/gcc/$target
\
mv $gnu_upstream_version 4.6
Bug#643664: lilypond: FTBFS on i386 and kfreebsd-i386
Package: lilypond Version: 2.14.2-1 Severity: serious Justification: fails to build from source See https://buildd.debian.org/status/fetch.php?pkg=lilypondarch=kfreebsd-i386ver=2.14.2-1stamp=1317146914 and https://buildd.debian.org/status/fetch.php?pkg=lilypondarch=i386ver=2.14.2-1stamp=1317145924 job 0 terminated with signal: 11 error: Children (3 2 1 0) exited with errors. command failed: /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/out/bin/lilypond -I ./ -I ./out-test -I ../../input -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/snippets -I ../../input/regression/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/included/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures/./out-test -dbackend=eps --formats=ps -djob-count=4 -dseparate-log-files -dinclude-eps-fonts -dgs-load-lily-fonts --header=texidoc -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/included/ -ddump-profile -dcheck-internal-types -ddump-signatures -danti-alias-factor=1 -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/out/lybook-testdb -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression/out-test -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/snippets -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/included -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures/out-test --formats=eps -deps-box-padding=3.00 -dread-file-list -dno-strip-output-dir /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/out/lybook-testdb/snippet-names-1138864437.ly Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643667: Broken symlinks on upgrade due to plain c_rehash call
Package: ca-certificates Version: 20110502+nmu1 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oneiric ubuntu-patch Hi See also: https://bugs.launchpad.net/ubuntu/oneiric/+source/ca-certificates/+bug/854927 ca-certificates.postinst runs: # Call c_rehash when upgrading from older versions to that we # have both the old and new style of symlink if [ ! -z $2 ]; then if dpkg --compare-versions $2 le 20090814+nmu3; then c_rehash fi fi but a plain c_rehash call is wrong because at this point there might be a /etc/ssl/certs/ca-certificates.crt file with all certificates that c_rehash picks up and links to. Instead, this file should be removed, then c_rehash should be called after clearing all other symlinks, then ca-certificates.crt should be regenerated. update-ca-certificates --fresh is meant to do that, but didn't move /etc/ssl/certs/ca-certificates.crt away. The attached patch moves /etc/ssl/certs/ca-certificates.crt away (credit to Steve Langasek for fixing this), and removes the c_rehash upgrade snippet in favor. NB: The patch needs to be updated with this bug number and the uploaded version (see XXXs in patch). Cheers, -- Loïc Minier diff -Nru ca-certificates-20110502+nmu1/debian/changelog ca-certificates-20110502+nmu2/debian/changelog --- ca-certificates-20110502+nmu1/debian/changelog 2011-08-31 04:02:49.0 +0200 +++ ca-certificates-20110502+nmu2/debian/changelog 2011-09-28 15:45:59.0 +0200 @@ -1,3 +1,18 @@ +ca-certificates (20110502+nmu2) UNRELEASED; urgency=low + + [ Steve Langasek ] + * sbin/update-ca-certificates: move the ca-certificates.crt bundle out of +the way before calling c_rehash, so that symlinks don't accidentally get +pointed here, breaking openssl certificate verification. LP: #854927. + + [ Loïc Minier ] + * Drop bogus c_rehash on upgrades, which caused issue when +ca-certificates.crt was still in place; instead, call +update-ca-certificates --fresh on upgrades to this version, and +the usual update-ca-certificates otherwise; closes: #XXX. + + -- Loïc Minier l...@debian.org Wed, 28 Sep 2011 15:44:05 +0200 + ca-certificates (20110502+nmu1) unstable; urgency=high * Non-maintainer upload by the Security Team. diff -Nru ca-certificates-20110502+nmu1/debian/postinst ca-certificates-20110502+nmu2/debian/postinst --- ca-certificates-20110502+nmu1/debian/postinst 2011-04-21 19:37:20.0 +0200 +++ ca-certificates-20110502+nmu2/debian/postinst 2011-09-28 15:42:28.0 +0200 @@ -137,13 +137,12 @@ -e 's/^[[:space:]]*1[[:space:]]*/!/' \ /etc/ca-certificates.conf fi - update-ca-certificates - # Call c_rehash when upgrading from older versions to that we - # have both the old and new style of symlink - if [ ! -z $2 ]; then - if dpkg --compare-versions $2 le 20090814+nmu3; then - c_rehash - fi + # fix bogus symlink to ca-certificates.crt on upgrades; see + # Debian #XXX; drop after wheezy + if dpkg --compare-versions $2 lt-nl 20110502+nmu2+XXX; then + update-ca-certificates --fresh + else + update-ca-certificates fi ;; diff -Nru ca-certificates-20110502+nmu1/sbin/update-ca-certificates ca-certificates-20110502+nmu2/sbin/update-ca-certificates --- ca-certificates-20110502+nmu1/sbin/update-ca-certificates 2009-07-08 23:23:12.0 +0200 +++ ca-certificates-20110502+nmu2/sbin/update-ca-certificates 2011-09-28 15:43:57.0 +0200 @@ -127,8 +127,7 @@ done fi -chmod 0644 $TEMPBUNDLE -mv -f $TEMPBUNDLE $CERTBUNDLE +rm -f $CERTBUNDLE ADDED_CNT=$(wc -l $ADDED) REMOVED_CNT=$(wc -l $REMOVED) @@ -144,6 +143,9 @@ fi fi +chmod 0644 $TEMPBUNDLE +mv -f $TEMPBUNDLE $CERTBUNDLE + echo $ADDED_CNT added, $REMOVED_CNT removed; done. HOOKSDIR=/etc/ca-certificates/update.d
Bug#643643: error: conflicting declaration 'typedef long unsigned int intptr_t'
On 28/09/2011 12:11, Mathieu Malaterre wrote: Package: vxl Version: 1.14.0-9 Severity: serious Tags: upstream Justification: fails to build from source Why is this set to serious? alpha is not a release architecture anymore. You're the maintainer and you can decide that it is serious, but it is not mandatory. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643671: ns3: FTBFS on kfreebsd-amd64: error: NS_TEST_SOURCEDIR redefined [-Werror]
Source: ns3
Version: 3.12.1+dfsg1-4
Severity: serious
Justification: fails to build from source
ns3 failed to build from source on kfreebsd-amd64:
| [ 628/1196] cxx: src/network/model/address.cc -
build/debug/src/network/model/address_59.o
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| [ 629/1196] cxx: src/network/model/application.cc -
build/debug/src/network/model/application_60.o
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| [ 630/1196] cxx: src/network/model/buffer.cc -
build/debug/src/network/model/buffer_61.o
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| command-line:0:0: error: NS_TEST_SOURCEDIR redefined [-Werror]
| command-line:0:0: note: this is the location of the previous definition
| cc1plus: all warnings being treated as errors
|
| cc1plus: all warnings being treated as errors
|
| cc1plus: all warnings being treated as errors
|
| cc1plus: all warnings being treated as errors
|
| Waf: Leaving directory
`/build/buildd-ns3_3.12.1+dfsg1-4-kfreebsd-amd64-IzWf43/ns3-3.12.1+dfsg1/ns-3.12.1/build'
| Build failed:
| - task failed (err #1):
| {task: cxx address.cc - address_59.o}
| - task failed (err #1):
| {task: cxx buffer.cc - buffer_61.o}
| - task failed (err #1):
| {task: cxx trace-helper.cc - trace-helper_58.o}
| - task failed (err #1):
| {task: cxx application.cc - application_60.o}
| Traceback (most recent call last):
| File ./build.py, line 147, in module
| # Build NSC
| Entering directory `nsc-0.5.2'
| = /usr/bin/python scons.py
| # Build NSC: failure (ignoring NSC)
| Leaving directory `nsc-0.5.2'
| # Build NS-3
| Entering directory `./ns-3.12.1'
| Note: configuring ns-3 without NSC
| sys.exit(main(sys.argv))
| = /usr/bin/python waf configure --prefix=/usr --enable-static --enable-mpi
--with-pybindgen ../pybindgen-0.15.0.795
| = /usr/bin/python waf build
| File ./build.py, line 138, in main
| build_ns3(config, build_examples, build_tests, args, build_options)
| File ./build.py, line 61, in build_ns3
| run_command([sys.executable, waf, build] + build_options)
| File
/build/buildd-ns3_3.12.1+dfsg1-4-kfreebsd-amd64-IzWf43/ns3-3.12.1+dfsg1/util.py,
line 24, in run_command
| raise CommandError(Command %r exited with code %i % (argv, retval))
| util.CommandError: Command ['/usr/bin/python', 'waf', 'build'] exited with
code 1
| make[1]: *** [override_dh_auto_build] Error 1
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=ns3arch=kfreebsd-amd64ver=3.12.1%2Bdfsg1-4stamp=1317163419
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642952: libpam0g-dev: Move of static libraries results in static linking due to library order
On Wed, Sep 28, 2011 at 11:54:17AM +0200, Paul Menzel wrote: Upgrading to 1.1.3-4, restarting GNOME Keyring daemon (`gnome-keyring-daemon --replace`) and then Evolution fixes the problem. No, that's not related to this bug. This bug only concerned the placement of .so files in the traditional vs. multiarch library path; that only impacts build-time linking software against libpam, it has no affect on the system at runtime. Can you think of a reason why this broke with 1.1.3-3 and was fixed by 1.1.3-4? I think this is a red herring, and something else changed on your system in between. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Processed: Re: Bug#643628: pidgin: Pidgin crash on sending first message
Processing commands for cont...@bugs.debian.org: reassign 643628 liborc-0.4-0 Bug #643628 [pidgin] pidgin: Pidgin crash on sending first message Bug reassigned from package 'pidgin' to 'liborc-0.4-0'. Bug No longer marked as found in versions 2.10.0-1+b1. End of message, stopping processing here. Please contact me if you need assistance. -- 643628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643628 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: block 622279 with 643671
Processing commands for cont...@bugs.debian.org: # FTBFS: ns3 block 622279 with 643671 Bug #622279 [release.debian.org] transition: python-defaults (switching default: 2.6 - 2.7) Was blocked by: 628860 629085 643458 628243 625676 633457 623587 622966 623578 629087 625171 606363 622912 631800 643440 625153 632249 624917 625040 631823 624940 621879 625880 638692 639072 631820 640581 624824 625151 624901 634544 634452 626800 632582 625520 618094 632367 640626 599127 641346 622976 608640 622154 628827 553961 633145 625677 625108 629091 622001 623418 618055 625722 622072 625853 622070 621992 642708 640564 555767 606006 625137 634528 616364 639119 626259 635356 623165 605875 621402 628820 622978 625678 635498 618084 553930 624889 628826 621948 632225 628830 624787 629122 633461 626199 628839 638247 629817 624950 625707 623927 625115 554552 632228 629148 631856 628852 629145 624740 618159 626421 631821 641637 629090 641488 606681 624811 625011 622027 626416 606642 624982 625679 624597 625087 610777 625135 633408 632234 634454 628828 621932 624429 Added blocking bug(s) of 622279: 643671 thanks Stopping processing here. Please contact me if you need assistance. -- 622279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622279 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#639088: marked as done (vino-server is not autostarted even though 'Remote Desktop' is enabled)
Your message dated Wed, 28 Sep 2011 15:50:30 + with message-id e1r8wp0-95...@franck.debian.org and subject line Bug#639088: fixed in vino 3.2.0-1 has caused the Debian Bug report #639088, regarding vino-server is not autostarted even though 'Remote Desktop' is enabled 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.) -- 639088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: vino Version: 3.0.3-1 Severity: grave Justification: renders package unusable Remote Desktop is enabled, the remote desktop server is checked in 'System/Preferences/Startup Applications' but vino-server is not running and there is no indication that it was ever started (i.e. can't tell if gnome-session tried to spawn it and failed, or if vino-server crashed; .xsession-errors has no output from vino-server or gnome-session related to vino). Another machine running vino 2.28.2-3 behaves properly, i.e. just enabling it in 'vino-properties' caused '/usr/lib/vino/vino-server' to be launched. Instances of both 'gnome-settings-daemon' and 'dbus-daemon' are running for this desktop user. I noticed, however, that the 'vino-server.desktop' file was not present in '$HOME/.config/autostart'. This may be due to the new gnome-session handling as detailed in http://live.gnome.org/SessionManagement/NewGnomeSession Digging further, there are differences in the desktop file between 2.28.2-3 and 3.0.3-1, specifically the 'AutostartCondition', which changed from just checking the gconf database AutostartCondition=GNOME /desktop/gnome/remote_access/enabled to checking ??? in 3.0.3-1: AutostartCondition=GSettings org.gnome.Vino enabled Looks like some bizarre combination of gnome-settings-daemon and dbus. At any rate, a method of starting a process that was mildly and needlessly complex (but nevertheless worked and became clear after a little investigation), was changed to something even more complex, undocumented has that fails and gives no indication why. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vino depends on: ii dconf-gsettings-backend 0.7.5-3 simple configuration storage syste ii libavahi-client30.6.30-5 Avahi client library ii libavahi-common30.6.30-5 Avahi common library ii libavahi-glib1 0.6.30-5 Avahi glib integration library ii libc6 2.13-16 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6.1 The Cairo 2D vector graphics libra ii libdbus-glib-1-20.94-4 simple interprocess messaging syst ii libgcrypt11 1.4.6-9 LGPL Crypto library - runtime libr ii libglib2.0-02.28.6-1 The GLib library of C routines ii libgnome-keyring0 3.0.0-2 GNOME keyring services library ii libgnutls26 2.12.7-6 GNU TLS library - runtime library ii libgtk-3-0 3.0.11-1 GTK+ graphical user interface libr ii libice6 2:1.0.7-2X11 Inter-Client Exchange library ii libjpeg88c-2 Independent JPEG Group's JPEG runt ii libnotify4 0.7.3-2 sends desktop notifications to a n ii libsm6 2:1.2.0-2X11 Session Management library ii libsoup2.4-12.34.3-1 HTTP library implementation in C - ii libtelepathy-glib0 0.15.4-1 Telepathy framework - GLib library ii libx11-62:1.4.4-1X11 client-side library ii libxdamage1 1:1.1.3-2X11 damaged region extension libra ii libxext62:1.3.0-3X11 miscellaneous extension librar ii libxfixes3 1:5.0-4 X11 miscellaneous 'fixes' extensio ii libxtst62:1.2.0-3X11 Testing -- Record extension li ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages vino recommends: ii gvfs 1.6.4-3userspace virtual filesystem - ser Versions of packages vino suggests: ii gnome-user-guide 2.30.1-1 GNOME user's guide ii vinagre 2.30.3-1 remote desktop client for the
Processed: tags bugs as pending
Processing commands for cont...@bugs.debian.org: tags 633569 + pending Bug #633569 [src:libgmpada] ftbs in unstable Bug #633895 [src:libgmpada] libgmpada: FTBFS: no compiler specified for language Ada, ignoring all its sources Added tag(s) pending. Added tag(s) pending. tags 642588 + pending Bug #642588 [src:libtexttools] libtexttools: new upstream version 2.0.7 available Added tag(s) pending. tags 642642 + pending Bug #642642 [src:libgmpada] libgmpada: FTBFS: build-dependency not installable: gnat Added tag(s) pending. tags 642646 + pending Bug #642646 [src:libncursesada] libncursesada: FTBFS: build-dependency not installable: gnat Added tag(s) pending. tags 642648 + pending Bug #642648 [src:libtexttools] libtexttools: FTBFS: build-dependency not installable: gnat Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 642648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642648 642642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642642 642588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642588 633569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633569 642646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642646 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#639293: marked as done (librsl1: Shared library package includes files that will clash when the soname bumps)
Your message dated Wed, 28 Sep 2011 16:20:55 + with message-id e1r8wsr-0005cj...@franck.debian.org and subject line Bug#639293: fixed in librsl 1.42-2 has caused the Debian Bug report #639293, regarding librsl1: Shared library package includes files that will clash when the soname bumps 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.) -- 639293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: librsl1 Version: 1.42-1 Severity: wishlist The files in /usr/share/rsl/ will be a problem if you want to multi-arch this or have librsl2 (when that appears) co-installable with librsl1. SR -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: librsl Source-Version: 1.42-2 We believe that the bug you reported is fixed in the latest version of librsl, which is due to be installed in the Debian FTP archive: librsl-dev_1.42-2_i386.deb to main/libr/librsl/librsl-dev_1.42-2_i386.deb librsl-doc_1.42-2_all.deb to main/libr/librsl/librsl-doc_1.42-2_all.deb librsl1_1.42-2_i386.deb to main/libr/librsl/librsl1_1.42-2_i386.deb librsl_1.42-2.debian.tar.gz to main/libr/librsl/librsl_1.42-2.debian.tar.gz librsl_1.42-2.dsc to main/libr/librsl/librsl_1.42-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andy Spencer andy753...@gmail.com (supplier of updated librsl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 11 Sep 2011 23:42:06 + Source: librsl Binary: librsl1 librsl-dev librsl-doc Architecture: source i386 all Version: 1.42-2 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Andy Spencer andy753...@gmail.com Description: librsl-dev - Development files for RSL librsl-doc - HTML documentation for RSL librsl1- TRMM Radar Software Library Closes: 639293 Changes: librsl (1.42-2) unstable; urgency=low . * Add version to in /share folder name (Closes: #639293) * Remove duplicate changelog Checksums-Sha1: c1f5071fa929cff84408031c9994027a1f2d977b 1317 librsl_1.42-2.dsc 0ae4c0c2f916ab635c3eee8ae5f7f5e5cbb64817 8608 librsl_1.42-2.debian.tar.gz 2685e5767c6afbbabd7ac241a3cbfd28aeba4037 150878 librsl1_1.42-2_i386.deb d42324eb001b68c13c141900afe4dc7ca53c05d4 62298 librsl-dev_1.42-2_i386.deb 499a54d190a6cf85918d3954d8e0b975b422d17a 210804 librsl-doc_1.42-2_all.deb Checksums-Sha256: e6f8b95321cee0a698283cdf11b9bd3e8606c3a8fcdfae679de61be03a00eaaf 1317 librsl_1.42-2.dsc f3ac9e246b0df01abe9c28c425ba64b839844de923b19febdce6689cda5ccdd9 8608 librsl_1.42-2.debian.tar.gz 7110077a883f644970e1a0d8c56b5d45daeaabf45d2465b98cfc21fdeeeaacf2 150878 librsl1_1.42-2_i386.deb 5d12195ddb933dc30c491a79e4557cacb967ab3765cd5bd92e6f4c8d9de3ae59 62298 librsl-dev_1.42-2_i386.deb 8d5066f4051e51ca749291b6a90de71ca8ab457123148ff03b199dd9b6d5939c 210804 librsl-doc_1.42-2_all.deb Files: 8ca72cf5ab0cd5a38add6ada3c9ae8b6 1317 science extra librsl_1.42-2.dsc 33ef89b473a2bdd500d8e21bedb58bec 8608 science extra librsl_1.42-2.debian.tar.gz 8bd4280202601e6c931869b71748e93b 150878 science extra librsl1_1.42-2_i386.deb ca1a688c0ffa214ffae5eef1d4988a53 62298 libdevel extra librsl-dev_1.42-2_i386.deb d814a73133e3c66696af9895d250958d 210804 doc extra librsl-doc_1.42-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6DRYsACgkQiOXXM92JlhAeWwCeK1r0sUEdVLkE4ovfEbJAeojl H60An1I3VOW2xy4Jt6SITy9sUCzDl1KG =hho6 -END PGP SIGNATURE- ---End Message---
Bug#643512: marked as done (jajuk: FTBFS: JAVA_HOME not defined correctly.)
Your message dated Wed, 28 Sep 2011 16:19:59 + with message-id e1r8wrx-00052s...@franck.debian.org and subject line Bug#643512: fixed in jajuk 1:1.9.5-3 has caused the Debian Bug report #643512, regarding jajuk: FTBFS: JAVA_HOME not defined correctly. 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.) -- 643512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jajuk Version: 1:1.9.5-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-home Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules clean test -x debian/rules dh_testroot You must specify a valid JAVA_HOME or JAVACMD! make: *** [testsanity] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/jajuk_1:1.9.5-2_lsid64.buildlog This is probably due to the multiarch'ification of openjdk. Please coordinate with debian-j...@lists.debian.org. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: jajuk Source-Version: 1:1.9.5-3 We believe that the bug you reported is fixed in the latest version of jajuk, which is due to be installed in the Debian FTP archive: jajuk_1.9.5-3.debian.tar.gz to main/j/jajuk/jajuk_1.9.5-3.debian.tar.gz jajuk_1.9.5-3.dsc to main/j/jajuk/jajuk_1.9.5-3.dsc jajuk_1.9.5-3_all.deb to main/j/jajuk/jajuk_1.9.5-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damien Raude-Morvan draz...@debian.org (supplier of updated jajuk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Sep 2011 17:43:21 +0200 Source: jajuk Binary: jajuk Architecture: source all Version: 1:1.9.5-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Damien Raude-Morvan draz...@debian.org Description: jajuk - advanced jukebox and music organizer Closes: 643512 Changes: jajuk (1:1.9.5-3) unstable; urgency=low . * Fix FTBFS: JAVA_HOME not defined correctly., in debian/rules: Check for multi-arch openjdk (Closes: #643512). * d/control: Build-Depends on openjdk-6-jdk but Depends on openjdk-6-jre | java6-jre | java7-jre * d/jajuk.sh: Allow searching for java7. Checksums-Sha1: e1bb49678afe8f19616e7ffb9e06835349d72752 2636 jajuk_1.9.5-3.dsc 3208c5d830b928af734621f2563d5ab29df820f8 10821 jajuk_1.9.5-3.debian.tar.gz 9aec9aecc6f6dcdf89503c4a18ddfe8b8d0428e4 1998506 jajuk_1.9.5-3_all.deb Checksums-Sha256: dc99ce81fa022ac1982b92af7dcaab20777647d0241aaa454a0c2a76d9a528ba 2636 jajuk_1.9.5-3.dsc 6f4bfa49d037c0ebe46065e2c81094385932c27e4db0c9ae1d8c26173c3ec41c 10821 jajuk_1.9.5-3.debian.tar.gz 90bf017f39b2ab64589aa1f8f85b99adcc11bb8574ada2caeb0acb56b82d440f 1998506 jajuk_1.9.5-3_all.deb Files: cdabca656a85d41234443cfd1832130e 2636 sound optional jajuk_1.9.5-3.dsc c9188440681908e2a79549d37d3c2fba 10821 sound optional jajuk_1.9.5-3.debian.tar.gz 8a6749189f96f36867addd57d8d2530a 1998506 sound optional jajuk_1.9.5-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOg0LwAAoJEHXiDM0z50n8kxEP/ArjALORgpZ+piH08neiN3af gRlPTmAcbzF5DTSXr+VQgIFc3iazWpoillWDYpnotJeZ1eVgp5DYI3Gv91wnotWx A9irZa37nSjAwBmC0m6FHREXPUL1GKWNtSYA2nB/zXJ//ov4mIDj7Yd57I2Or5/u FnAmp77xYk2yq7Yxp9lbABt/s0bCbkOw2FlTD+LFTysWwq8LjGbqben1vig29Wv/ T1wxQOQj+c1JPGUTgot2vgnsgOa3BDc+mhNULNsnRoWk6jJk4b9nIfP3heoO/u3x nZKUVB6T3LWNYkJ46uoAK/L+pJ0YcJnVGd9iNiVF1rYkCaN9rHF4rOtaFg6YfB3T mBwcIkMFTjPGtqXOUNShHTBmWjqb93qCbHx6e8ZoLZbqZuOZ5+RXlF+oVU1gzwDB Yat+9FKWTSMnxegY1Z5F4cjkfeitVSAeEDxuw6FDCZrmUmY3iPaTSan5g+ZNA6fI Nsfg5kPa1eqBhRvZofZ49W4R7sUr4vsVG/09Z5J8XN3M0Xbd41vQ46WvKDqP4eey
Bug#642744: marked as done (ruby-gruff: FTBFS: ERROR: Test ruby1.8 failed. Exiting.)
Your message dated Wed, 28 Sep 2011 16:21:13 + with message-id e1r8wsj-0005gw...@franck.debian.org and subject line Bug#642744: fixed in ruby-gruff 0.3.6-5 has caused the Debian Bug report #642744, regarding ruby-gruff: FTBFS: ERROR: Test ruby1.8 failed. Exiting. 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.) -- 642744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-gruff Version: 0.3.6-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_installdirs -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Entering dh_ruby --install install -d /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby install -D -m644 lib/gruff.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff.rb install -D -m644 lib/gruff/scene.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/scene.rb install -D -m644 lib/gruff/stacked_mixin.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/stacked_mixin.rb install -D -m644 lib/gruff/stacked_area.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/stacked_area.rb install -D -m644 lib/gruff/area.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/area.rb install -D -m644 lib/gruff/base.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/base.rb install -D -m644 lib/gruff/accumulator_bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/accumulator_bar.rb install -D -m644 lib/gruff/pie.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/pie.rb install -D -m644 lib/gruff/net.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/net.rb install -D -m644 lib/gruff/side_stacked_bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/side_stacked_bar.rb install -D -m644 lib/gruff/stacked_bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/stacked_bar.rb install -D -m644 lib/gruff/photo_bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/photo_bar.rb install -D -m644 lib/gruff/dot.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/dot.rb install -D -m644 lib/gruff/deprecated.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/deprecated.rb install -D -m644 lib/gruff/bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/bar.rb install -D -m644 lib/gruff/spider.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/spider.rb install -D -m644 lib/gruff/line.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/line.rb install -D -m644 lib/gruff/bullet.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/bullet.rb install -D -m644 lib/gruff/mini/pie.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/mini/pie.rb install -D -m644 lib/gruff/mini/bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/mini/bar.rb install -D -m644 lib/gruff/mini/legend.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/mini/legend.rb install -D -m644 lib/gruff/mini/side_bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/mini/side_bar.rb install -D -m644 lib/gruff/bar_conversion.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/bar_conversion.rb install -D -m644 lib/gruff/side_bar.rb /build/ruby-gruff-z1kDki/ruby-gruff-0.3.6/debian/ruby-gruff/usr/lib/ruby/vendor_ruby/gruff/side_bar.rb /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby
Bug#642776: marked as done (ruby-ogginfo: FTBFS: sh: 1: oggenc: not found)
Your message dated Wed, 28 Sep 2011 16:21:29 + with message-id e1r8wsz-0005lp...@franck.debian.org and subject line Bug#642776: fixed in ruby-ogginfo 0.6.5-2 has caused the Debian Bug report #642776, regarding ruby-ogginfo: FTBFS: sh: 1: oggenc: not found 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.) -- 642776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-ogginfo Version: 0.6.5-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_installdirs -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Entering dh_ruby --install install -d /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby install -D -m644 lib/ogg.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogg.rb install -D -m644 lib/ogginfo.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogginfo.rb install -D -m644 lib/ogg/reader.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogg/reader.rb install -D -m644 lib/ogg/page.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogg/page.rb install -D -m644 lib/ogg/codecs/comments.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogg/codecs/comments.rb install -D -m644 lib/ogg/codecs/vorbis.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogg/codecs/vorbis.rb install -D -m644 lib/ogg/codecs/speex.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogg/codecs/speex.rb install -D -m644 lib/ogg/writer.rb /build/ruby-ogginfo-PsZrMg/ruby-ogginfo-0.6.5/debian/ruby-ogginfo/usr/lib/ruby/vendor_ruby/ogg/writer.rb /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb Loaded suite -e Started sh: 1: oggenc: not found sh: 1: oggenc: not found sh: 1: oggenc: not found sh: 1: oggenc: not found sh: 1: oggenc: not found sh: 1: oggenc: not found Warning: Speex is only optimized for 8, 16 and 32 kHz. It will still work at 44100 Hz but your mileage may vary Encoding 44100 Hz audio using ultra-wideband (sub-band CELP) mode (stereo) 3000+0 records in 3000+0 records out 3072000 bytes (3.1 MB) copied, 0.829607 s, 3.7 MB/s FFF.FFF Finished in 0.934657 seconds. 1) Failure: test_big_tags(OggInfoTest) [./test/test_ruby-ogginfo.rb:197:in `generate_ogg' ./test/test_ruby-ogginfo.rb:219:in `tag_test' ./test/test_ruby-ogginfo.rb:138:in `test_big_tags']: cannot generate ./test/test.ogg, tests cannot be fully performed. 2) Failure: test_charset(OggInfoTest) [./test/test_ruby-ogginfo.rb:197:in `generate_ogg' ./test/test_ruby-ogginfo.rb:143:in `test_charset']: cannot generate ./test/test.ogg, tests cannot be fully performed. 3) Failure: test_checksum(OggInfoTest) [./test/test_ruby-ogginfo.rb:197:in `generate_ogg' ./test/test_ruby-ogginfo.rb:210:in `generate_truncated_ogg' ./test/test_ruby-ogginfo.rb:181:in `test_checksum']: cannot generate ./test/test.ogg, tests cannot be fully performed. 4) Failure: test_length(OggInfoTest) [./test/test_ruby-ogginfo.rb:197:in `generate_ogg' ./test/test_ruby-ogginfo.rb:126:in `test_length']: cannot generate ./test/test.ogg, tests cannot be fully performed. 5) Failure: test_should_not_fail_when_input_is_truncated(OggInfoTest) [./test/test_ruby-ogginfo.rb:197:in `generate_ogg' ./test/test_ruby-ogginfo.rb:161:in `test_should_not_fail_when_input_is_truncated']: cannot generate ./test/test.ogg, tests cannot be fully performed. 6) Failure: test_tag_writing(OggInfoTest) [./test/test_ruby-ogginfo.rb:197:in `generate_ogg' ./test/test_ruby-ogginfo.rb:219:in `tag_test' ./test/test_ruby-ogginfo.rb:134:in `test_tag_writing']: cannot generate ./test/test.ogg, tests cannot be fully performed. 11 tests, 20 assertions, 6 failures, 0 errors ERROR: Test ruby1.8 failed. Exiting. dh_auto_install: dh_ruby --install
Bug#643542: marked as done (maven-bundle-plugin: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 16:34:20 + with message-id e1r8x5q-0007so...@franck.debian.org and subject line Bug#643542: fixed in maven-bundle-plugin 2.3.4-3 has caused the Debian Bug report #643542, regarding maven-bundle-plugin: FTBFS: Error building POM 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.) -- 643542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-bundle-plugin Version: 2.3.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Sep 23 22:39:45 CEST 2011 [INFO] Final Memory: 5M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-bundle-plugin_2.3.4-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-bundle-plugin Source-Version: 2.3.4-3 We believe that the bug you reported is fixed in the latest version of maven-bundle-plugin, which is due to be installed in the Debian FTP archive: libmaven-bundle-plugin-java-doc_2.3.4-3_all.deb to main/m/maven-bundle-plugin/libmaven-bundle-plugin-java-doc_2.3.4-3_all.deb libmaven-bundle-plugin-java_2.3.4-3_all.deb to main/m/maven-bundle-plugin/libmaven-bundle-plugin-java_2.3.4-3_all.deb maven-bundle-plugin_2.3.4-3.debian.tar.gz to main/m/maven-bundle-plugin/maven-bundle-plugin_2.3.4-3.debian.tar.gz maven-bundle-plugin_2.3.4-3.dsc to main/m/maven-bundle-plugin/maven-bundle-plugin_2.3.4-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damien Raude-Morvan draz...@debian.org (supplier of updated maven-bundle-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Sep 2011 18:11:36 +0200 Source: maven-bundle-plugin Binary: libmaven-bundle-plugin-java libmaven-bundle-plugin-java-doc Architecture: source all Version: 2.3.4-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Damien Raude-Morvan draz...@debian.org Description: libmaven-bundle-plugin-java - Maven plugin to handle artifact OSGi metadata libmaven-bundle-plugin-java-doc - Maven plugin to handle artifact OSGi metadata - documentation Closes: 643542 Changes: maven-bundle-plugin (2.3.4-3) unstable; urgency=low . * d/control: Fix FTBFS, add Build-Depends on libmaven-plugin-tools-java. (Closes: #643542.) Checksums-Sha1: cf3e6e9f5e49e6ea5d749e3f52f154e8b105ab8f 2579 maven-bundle-plugin_2.3.4-3.dsc b6892f6b5ecdeebb00edefba0c14b14d5549b6b3 4275 maven-bundle-plugin_2.3.4-3.debian.tar.gz 800dd47a3425520fb41f3b6da96c2964819cb7a9 112692 libmaven-bundle-plugin-java_2.3.4-3_all.deb
Bug#643379: marked as done (fqterm: FTBFS: fqterm_mini_server.cpp:54:3: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Wed, 28 Sep 2011 16:48:06 + with message-id e1r8xik-fc...@franck.debian.org and subject line Bug#643379: fixed in fqterm 0.9.6.9-1 has caused the Debian Bug report #643379, regarding fqterm: FTBFS: fqterm_mini_server.cpp:54:3: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: fqterm Version: 0.9.6.8-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu/CMakeFiles 92 [ 11%] Building CXX object src/unite/CMakeFiles/fqterm_unite.dir/fqterm_mini_server.o cd /build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu/src/unite /usr/bin/g++ -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DAUDIO_OSS -D_OS_LINUX_ -DQT_NO_DEBUG -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Os -DNDEBUG -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/internal -I/build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/../common -I/build/fqterm-TT4DhJ/fqterm-0.9.6.8/obj-x86_64-linux-gnu/src/unite-Wall -D FQTERM_VERSION_STRING=\0.9.6\ -o CMakeFiles/fqterm_unite.dir/fqterm_mini_server.o -c /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp: In member function 'virtual void FQTerm::FQTermMiniServer::incomingConnection(int)': /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:54:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp: In constructor 'FQTerm::FQTermUniteSession::FQTermUniteSession(int)': /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:65:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:67:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:69:3: error: format not a string literal and no format arguments [-Werror=format-security] /build/fqterm-TT4DhJ/fqterm-0.9.6.8/src/unite/fqterm_mini_server.cpp:71:3: error: format not a string literal and no format arguments [-Werror=format-security] cc1plus: some warnings being treated as errors make[3]: *** [src/unite/CMakeFiles/fqterm_unite.dir/fqterm_mini_server.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/fqterm_0.9.6.8-1_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: fqterm Source-Version: 0.9.6.9-1 We believe that the bug you reported is fixed in the latest version of fqterm, which is due to be installed in the Debian FTP archive: fqterm_0.9.6.9-1.debian.tar.gz to main/f/fqterm/fqterm_0.9.6.9-1.debian.tar.gz fqterm_0.9.6.9-1.dsc to main/f/fqterm/fqterm_0.9.6.9-1.dsc fqterm_0.9.6.9-1_amd64.deb to main/f/fqterm/fqterm_0.9.6.9-1_amd64.deb fqterm_0.9.6.9.orig.tar.bz2 to main/f/fqterm/fqterm_0.9.6.9.orig.tar.bz2 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 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution
Bug#615684: qucs: diff for NMU version 0.0.15-1.1
tags 615684 + pending thanks Dear maintainer, I've prepared an NMU for qucs (versioned as 0.0.15-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key ID: 0x8649AA06 : :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of Free Software Foundation Europe `-NP: Rolling Stones diff -u qucs-0.0.15/debian/changelog qucs-0.0.15/debian/changelog --- qucs-0.0.15/debian/changelog +++ qucs-0.0.15/debian/changelog @@ -1,3 +1,15 @@ +qucs (0.0.15-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix ftbfs with gcc-4.5: apply patch from Ubuntu / Daniel T Chen: +- Backport patch from Red Hat Bugzilla #631404 (cf. + https://bugzilla.redhat.com/attachment.cgi?id=511054) to disable + use of tr1 for complex functions. Fixes FTBFS. +Closes: #615684 +LP: #756183 + + -- gregor herrmann gre...@debian.org Wed, 28 Sep 2011 18:30:51 +0200 + qucs (0.0.15-1) unstable; urgency=low * New upstream release. (Closes: #526954) only in patch2: unchanged: --- qucs-0.0.15.orig/qucs-core/configure +++ qucs-0.0.15/qucs-core/configure @@ -6478,7 +6478,6 @@ cat confdefs.h conftest.$ac_ext cat conftest.$ac_ext _ACEOF /* end confdefs.h. */ -#include tr1/complex using namespace std; using namespace std::tr1; int signature.asc Description: Digital signature
Processed: qucs: diff for NMU version 0.0.15-1.1
Processing commands for cont...@bugs.debian.org: tags 615684 + pending Bug #615684 [qucs] qucs: ftbfs with gcc-4.5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 615684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615684 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#642310: marked as done (overwrite error: /usr/share/man/man2/io_getevents.2.gz)
Your message dated Wed, 28 Sep 2011 19:04:48 +0200 with message-id 20110928170448.ga29...@gaara.hadrons.org and subject line Re: Bug#642310: overwrite error: /usr/share/man/man2/io_getevents.2.gz has caused the Debian Bug report #642310, regarding overwrite error: /usr/share/man/man2/io_getevents.2.gz 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.) -- 642310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libaio-dev Version: 0.3.109-1 Severity: serious Trying to upgarde libaio-dev fails with: Unpacking replacement libaio-dev ... dpkg: error processing /var/cache/apt/archives/libaio-dev_0.3.109-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man2/io_getevents.2.gz', which is also in package manpages-dev 3.28-1 MfG Goswin -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages libaio-dev depends on: iu libaio1 0.3.109-2 Linux kernel AIO access library - libaio-dev recommends no packages. libaio-dev suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Wed, 2011-09-28 at 10:30:53 +0200, Goswin von Brederlow wrote: Guillem Jover guil...@debian.org writes: On Wed, 2011-09-21 at 14:28:46 +0200, Goswin von Brederlow wrote: Trying to upgarde libaio-dev fails with: Unpacking replacement libaio-dev ... dpkg: error processing /var/cache/apt/archives/libaio-dev_0.3.109-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man2/io_getevents.2.gz', which is also in package manpages-dev 3.28-1 This is a bug in manpages, which included those when libaio-dev has always provided them, fixed in manpages-dev 3.32-0.2, you should upgrade that one. (Bug #636704) Upgrades have to work in any order or packages have to say otherwise (breaks, conflicts, replaces, ...) so that isn't really a solution. We are talking about a buggy package (manpages-dev) that does not exist anymore on the archive, is not in any stable release, and for which there's a fix released in testing already. So for starters serious here is way way out of proportion. Even if libaio-dev was to drop the pages right now, there would still be a period where upgrades can break, there's no way around this fact. unstable and testing break from time to time, if you cannot cope with that do not use them... Also manpages-dev says: * debian/control: add Replace against libaio-dev, because of aio_init.3.gz and lio_listio.3.gz (Closes: #636704) That is only approriate when the files are moved from libaio-dev to manpages-dev and clearly libaio-dev has not droped those files. They have not moved yet, that does not make manpages-dev wrong, neither libaio-dev. If manpages-dev did not have missed the Replaces on the first place the overwritting issue would not have ever existed. So one or both of the two packages are wrong. I strongly disagree, and as such I'm re-closing this now. regards, guillem ---End Message---
Processed: tagging 643502, tagging 577513, tagging 329526, tagging 269198
Processing commands for cont...@bugs.debian.org: tags 643502 + pending Bug #643502 [src:libdbd-sybase-perl] libdbd-sybase-perl: FTBFS: Can't find Sybase libraries. Added tag(s) pending. tags 577513 + pending Bug #577513 [libdbd-sybase-perl] libdbd-sybase-perl: DBI/DBD internal version mismatch Added tag(s) pending. tags 329526 + pending Bug #329526 [libdbd-sybase-perl] libdbd-sybase-perl: New upstream release Bug #560117 [libdbd-sybase-perl] libdbd-sybase-perl: Ancient version does not support connections to MSSQL Server 2008 Added tag(s) pending. Added tag(s) pending. tags 269198 + pending Bug #269198 [libdbd-sybase-perl] libdbd-sybase-perl 1.00 is badly broken with MS SQL Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 269198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269198 577513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577513 643502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643502 329526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329526 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#564971: marked as done (clamfs: ftbfs with gcc-4.5)
Your message dated Wed, 28 Sep 2011 17:17:32 +
with message-id e1r8xle-0004bh...@franck.debian.org
and subject line Bug#564971: fixed in clamfs 1.0.1-1.1
has caused the Debian Bug report #564971,
regarding clamfs: ftbfs with gcc-4.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.)
--
564971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: clamfs
Version: 1.0.1-1
Severity: normal
Tags: sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.5
The package fails to build in a test rebuild on at least amd64 with
gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4.
For the compiler version used, see:
http://lists.debian.org/debian-devel/2010/01/msg00230.html
The full build log can be found at:
http://people.debian.org/~lucas/logs/2010/01/08b/clamfs_1.0.1-1_lsid64b.buildlog
The last lines of the build log are cwat the end of this report.
The reason of the build failure is likely in the package (compiler or
linker message found in the build log), if this turns out as a gcc bug,
please reassign to the gcc-4.5 package. If the build ends with a
message confused by earlier errors, bailing out, please
ignore it for now; these compiler errors are filed separately.
[...]
config.status: creating config.h
config.status: executing depfiles commands
dh_testdir
/usr/bin/make
make[1]: Entering directory
`/build/user-clamfs_1.0.1-1-amd64-Mjz5ac/clamfs-1.0.1'
/usr/bin/make all-recursive
make[2]: Entering directory
`/build/user-clamfs_1.0.1-1-amd64-Mjz5ac/clamfs-1.0.1'
Making all in src
make[3]: Entering directory
`/build/user-clamfs_1.0.1-1-amd64-Mjz5ac/clamfs-1.0.1/src'
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=25
-DRLOG_COMPONENT=clamfs -D_GNU_SOURCE -I/usr/include -Wall -O2 -DNDEBUG -g -O2
-MT clamfs.o -MD -MP -MF .deps/clamfs.Tpo -c -o clamfs.o clamfs.cxx
mv -f .deps/clamfs.Tpo .deps/clamfs.Po
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=25
-DRLOG_COMPONENT=clamfs -D_GNU_SOURCE -I/usr/include -Wall -O2 -DNDEBUG -g -O2
-MT config.o -MD -MP -MF .deps/config.Tpo -c -o config.o config.cxx
mv -f .deps/config.Tpo .deps/config.Po
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=25
-DRLOG_COMPONENT=clamfs -D_GNU_SOURCE -I/usr/include -Wall -O2 -DNDEBUG -g -O2
-MT rlog.o -MD -MP -MF .deps/rlog.Tpo -c -o rlog.o rlog.cxx
mv -f .deps/rlog.Tpo .deps/rlog.Po
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=25
-DRLOG_COMPONENT=clamfs -D_GNU_SOURCE -I/usr/include -Wall -O2 -DNDEBUG -g -O2
-MT clamav.o -MD -MP -MF .deps/clamav.Tpo -c -o clamav.o clamav.cxx
mv -f .deps/clamav.Tpo .deps/clamav.Po
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=25
-DRLOG_COMPONENT=clamfs -D_GNU_SOURCE -I/usr/include -Wall -O2 -DNDEBUG -g -O2
-MT scancache.o -MD -MP -MF .deps/scancache.Tpo -c -o scancache.o scancache.cxx
scancache.cxx: In constructor 'clamfs::ScanCache::ScanCache(long int, long
int)':
scancache.cxx:40:56: error: expected template-name before '' token
scancache.cxx:40:56: error: expected '{' before '' token
scancache.cxx: At global scope:
scancache.cxx:40:56: error: expected unqualified-id before '' token
make[3]: *** [scancache.o] Error 1
make[2]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/build/user-clamfs_1.0.1-1-amd64-Mjz5ac/clamfs-1.0.1/src'
make[2]: Leaving directory
`/build/user-clamfs_1.0.1-1-amd64-Mjz5ac/clamfs-1.0.1'
make[1]: *** [all] Error 2
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
---End Message---
---BeginMessage---
Source: clamfs
Source-Version: 1.0.1-1.1
We believe that the bug you reported is fixed in the latest version of
clamfs, which is due to be installed in the Debian FTP archive:
clamfs_1.0.1-1.1.diff.gz
to main/c/clamfs/clamfs_1.0.1-1.1.diff.gz
clamfs_1.0.1-1.1.dsc
to main/c/clamfs/clamfs_1.0.1-1.1.dsc
clamfs_1.0.1-1.1_i386.deb
to main/c/clamfs/clamfs_1.0.1-1.1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 564...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian
Bug#639892: Bug not resolved in 1.0-2
In Package 1.0-2 the libpulse-mainlook-glib0 symbols file still contains a wrong package name, this time it points to a nonexisting libpulse-mainloop-mainloop-glib0 package. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639088: Debian bug #639088 - vino-server is not autostarted even though 'Remote Desktop' is enabled
Hi there, Sorry to bother, but the fix that Dominique provided (by modifying the file at path '/usr/share/gnome/autostart/vino-server.desktop') didn't work for me. I tried searching this configuration path (/desktop/gnome/remote_access/enabled) with gconf-editor, but I don't even have any 'remote_access' element in the tree! Should I create it manually? On the other side, where could I find the vino 3.2.0-1 Debian package (for amd64 architecture)? Cheers.
Processed: fixed 642766 in osmosis/0.39+ds1-1, closing 642766
Processing commands for cont...@bugs.debian.org: fixed 642766 osmosis/0.39+ds1-1 Bug #642766 [src:osmosis] osmosis: FTBFS: You must specify a valid JAVA_HOME or JAVACMD Bug Marked as fixed in versions osmosis/0.39+ds1-1. close 642766 Bug#642766: osmosis: FTBFS: You must specify a valid JAVA_HOME or JAVACMD 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Mònica RamÃrez Arceda mon...@probeta.net thanks Stopping processing here. Please contact me if you need assistance. -- 642766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642766 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#642275: marked as done (red5: FTBFS: You must specify a valid JAVA_HOME or JAVACMD!)
Your message dated Wed, 28 Sep 2011 17:50:18 + with message-id e1r8ygw-0002jg...@franck.debian.org and subject line Bug#642275: fixed in red5 1.0~svn4279-1 has caused the Debian Bug report #642275, regarding red5: FTBFS: You must specify a valid JAVA_HOME or JAVACMD! 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.) -- 642275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: java3d Version: 1.5.2+dfsg-6 Severity: serious Justification: fails to build from source User: debian-s...@lists.debian.org Usertags: s390x java3d fails to build as it can't find the path to openjdk: | dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 | dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): | dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 | dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 | dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): | dpkg-buildpackage: source package java3d | dpkg-buildpackage: source version 1.5.2+dfsg-6 | dpkg-source --before-build java3d-1.5.2+dfsg | dpkg-buildpackage: host architecture s390x | fakeroot debian/rules clean | test -x debian/rules | dh_testroot | make: *** [testsanity] Error 1 | You must specify a valid JAVA_HOME or JAVACMD! It sets JAVA_HOME to /usr/lib/jvm/java-6-openjdk, but this path has changed starting with openjdk-6 version 6b23~pre8-2. Full build log is available (s390x, but also fails on other architectures): http://buildd.debian-ports.org/status/fetch.php?pkg=java3darch=s390xver=1.5.2%2Bdfsg-6stamp=1314740476 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-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/bash ---End Message--- ---BeginMessage--- Source: red5 Source-Version: 1.0~svn4279-1 We believe that the bug you reported is fixed in the latest version of red5, which is due to be installed in the Debian FTP archive: libred5-java_1.0~svn4279-1_all.deb to main/r/red5/libred5-java_1.0~svn4279-1_all.deb red5-doc_1.0~svn4279-1_all.deb to main/r/red5/red5-doc_1.0~svn4279-1_all.deb red5-server_1.0~svn4279-1_all.deb to main/r/red5/red5-server_1.0~svn4279-1_all.deb red5_1.0~svn4279-1.debian.tar.gz to main/r/red5/red5_1.0~svn4279-1.debian.tar.gz red5_1.0~svn4279-1.dsc to main/r/red5/red5_1.0~svn4279-1.dsc red5_1.0~svn4279.orig-doc.tar.gz to main/r/red5/red5_1.0~svn4279.orig-doc.tar.gz red5_1.0~svn4279.orig-plugins.tar.gz to main/r/red5/red5_1.0~svn4279.orig-plugins.tar.gz red5_1.0~svn4279.orig.tar.gz to main/r/red5/red5_1.0~svn4279.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 642...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damien Raude-Morvan draz...@debian.org (supplier of updated red5 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Sep 2011 18:25:03 +0200 Source: red5 Binary: libred5-java red5-server red5-doc Architecture: source all Version: 1.0~svn4279-1 Distribution: unstable Urgency: low Maintainer: Damien Raude-Morvan draz...@debian.org Changed-By: Damien Raude-Morvan draz...@debian.org Description: libred5-java - remote API for Red5 flash streaming server red5-doc - flash streaming server - documentation red5-server - flash streaming server Closes: 642275 Changes: red5 (1.0~svn4279-1) unstable; urgency=low . * New upstream snapshot (r4279 in SVN): - d/patches/13_jaudiotagger2.diff: Droped, merged upstream. - d/control: Replace libcommons-httpclient-java by libhttpcore-java and libhttpclient-java. - d/control: Replace libcommons-lang-java by libcommons-lang3-java. - d/control: Depends on libxml-commons-external-java. * d/control: Bump Standards-Version to 3.9.2: no changes needed. * d/control: Depends on librhino-java instead of rhino. * d/README.Debian: Add information about webapp.virtualHosts and remove warning about spring
Bug#643691: Configuring mod_proxy_html causes apache child process to segfault
Package: libapache2-mod-proxy-html Version: 3.0.1-1 Severity: grave Tags: patch -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages libapache2-mod-proxy-html depends on: ii apache22.2.21-1 ii apache2-mpm-prefork [apache2] 2.2.21-1 ii apache2.2-common 2.2.21-1 ii libc6 2.13-18 ii libxml22.7.8.dfsg-4 libapache2-mod-proxy-html recommends no packages. libapache2-mod-proxy-html suggests no packages. -- Configuration Files: /etc/apache2/mods-available/proxy_html.conf changed: ProxyHTMLLinks a href ProxyHTMLLinks areahref ProxyHTMLLinks linkhref ProxyHTMLLinks img src longdesc usemap ProxyHTMLLinks object classid codebase data usemap ProxyHTMLLinks q cite ProxyHTMLLinks blockquote cite ProxyHTMLLinks ins cite ProxyHTMLLinks del cite ProxyHTMLLinks formaction ProxyHTMLLinks input src usemap ProxyHTMLLinks headprofile ProxyHTMLLinks basehref ProxyHTMLLinks iframe src ProxyHTMLEvents onclick ondblclick onmousedown onmouseup \ onmouseover onmousemove onmouseout onkeypress \ onkeydown onkeyup onfocus onblur onload \ onunload onsubmit onreset onselect onchange ProxyHTMLLinks frame src longdesc ProxyHTMLLinks iframe src longdesc ProxyHTMLLinks bodybackground ProxyHTMLLinks applet codebase /etc/apache2/mods-available/proxy_html.load changed: LoadModule proxy_html_module /usr/lib/apache2/modules/mod_proxy_html.so -- no debconf information Using last upstream version fixes the bug -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642961: systemd: debian-fixup.service goes berserk in /run, breaks boot
]] Eckhart Wörner | However, this seems to break on /var/run already being bind-mounted on | /run. The condition holds, and therefore /run (aka /var/run) is wiped | out, breaking the boot process. Can you see if the attached patch fixes this? diff --git a/debian/debian-fixup.service b/debian/debian-fixup.service index 5b391db..6848466 100644 --- a/debian/debian-fixup.service +++ b/debian/debian-fixup.service @@ -6,5 +6,5 @@ DefaultDependencies=no [Service] ExecStart=/lib/systemd/debian-fixup -Type=simple +Type=oneshot RemainAfterExit=true Cheers, -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643432: marked as done (libpmount: FTBFS: src/mtab.c:49:3: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Wed, 28 Sep 2011 18:05:26 + with message-id e1r8yva-000570...@franck.debian.org and subject line Bug#643432: fixed in libpmount 0.0.15 has caused the Debian Bug report #643432, regarding libpmount: FTBFS: src/mtab.c:49:3: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libpmount Version: 0.0.14 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: cc -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -D_REENTRANT -DUSE_LOOP -fPIC -c -o src/mtab.lo src/mtab.c src/mtab.c: In function '__mtab_add': src/mtab.c:49:3: error: format not a string literal and no format arguments [-Werror=format-security] src/mtab.c: In function '__mtab_del': src/mtab.c:102:9: error: format not a string literal and no format arguments [-Werror=format-security] src/mtab.c:90:12: warning: ignoring return value of 'asprintf', declared with attribute warn_unused_result [-Wunused-result] cc1: some warnings being treated as errors make[1]: *** [src/mtab.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/libpmount_0.0.14_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: libpmount Source-Version: 0.0.15 We believe that the bug you reported is fixed in the latest version of libpmount, which is due to be installed in the Debian FTP archive: libpmount-dev_0.0.15_amd64.deb to main/libp/libpmount/libpmount-dev_0.0.15_amd64.deb libpmount0.0_0.0.15_amd64.deb to main/libp/libpmount/libpmount0.0_0.0.15_amd64.deb libpmount_0.0.15.dsc to main/libp/libpmount/libpmount_0.0.15.dsc libpmount_0.0.15.tar.gz to main/libp/libpmount/libpmount_0.0.15.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover guil...@debian.org (supplier of updated libpmount package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 19:39:11 +0200 Source: libpmount Binary: libpmount-dev libpmount0.0 Architecture: source amd64 Version: 0.0.15 Distribution: unstable Urgency: low Maintainer: Guillem Jover guil...@debian.org Changed-By: Guillem Jover guil...@debian.org Description: libpmount-dev - portable mount library - development files libpmount0.0 - portable mount library - shared library Closes: 643432 Changes: libpmount (0.0.15) unstable; urgency=low . * Use a format string on fprintf() instead of directly using a string variable to fix build with -Werror=format-security. Closes: #643432 * Always check asprintf() return code. Checksums-Sha1: 7a723a35b43456afdbb6fc0288f9dc647c33cc70 943 libpmount_0.0.15.dsc 567e940e0e3c1373acc34e26ad198ac183808f46 10445 libpmount_0.0.15.tar.gz 7d883494951f31d7c681f8038cdbe4cce6e6429a 7674 libpmount-dev_0.0.15_amd64.deb 215bc783ba6ee20d633d45a838b773b7a7b5a782 8290 libpmount0.0_0.0.15_amd64.deb Checksums-Sha256: 2a74918a2bf98d9959e2d9e2bc56f4a0d38bdf6d5e9053eb57768fbe0b3914ba 943 libpmount_0.0.15.dsc d5ee972ded9b76e14e94b01771745f917cb99cb124a00c59242fe6a0d7852e4a 10445 libpmount_0.0.15.tar.gz 959463aaf20c9e715f17bb18aaa60d6f1d9bec27da7481371d1124e475ea05ab 7674 libpmount-dev_0.0.15_amd64.deb
Bug#643502: marked as done (libdbd-sybase-perl: FTBFS: Can't find Sybase libraries.)
Your message dated Wed, 28 Sep 2011 18:05:13 +
with message-id e1r8yvn-00052v...@franck.debian.org
and subject line Bug#643502: fixed in libdbd-sybase-perl 1.09-1
has caused the Debian Bug report #643502,
regarding libdbd-sybase-perl: FTBFS: Can't find Sybase libraries.
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.)
--
643502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libdbd-sybase-perl
Version: 1.00-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110923 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
debian/rules build
dh_testdir
# Add here commands to compile the package.
SYBASE=/usr /usr/bin/perl Makefile.PL INSTALLDIRS=vendor /dev/null
Can't find any Sybase libraries in /usr/lib at Makefile.PL line 102, IN
line 44.
make: *** [build-stamp] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/09/23/libdbd-sybase-perl_1.00-3_lsid64.buildlog
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
---End Message---
---BeginMessage---
Source: libdbd-sybase-perl
Source-Version: 1.09-1
We believe that the bug you reported is fixed in the latest version of
libdbd-sybase-perl, which is due to be installed in the Debian FTP archive:
libdbd-sybase-perl_1.09-1.diff.gz
to main/libd/libdbd-sybase-perl/libdbd-sybase-perl_1.09-1.diff.gz
libdbd-sybase-perl_1.09-1.dsc
to main/libd/libdbd-sybase-perl/libdbd-sybase-perl_1.09-1.dsc
libdbd-sybase-perl_1.09-1_amd64.deb
to main/libd/libdbd-sybase-perl/libdbd-sybase-perl_1.09-1_amd64.deb
libdbd-sybase-perl_1.09.orig.tar.gz
to main/libd/libdbd-sybase-perl/libdbd-sybase-perl_1.09.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 643...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve Langasek vor...@debian.org (supplier of updated libdbd-sybase-perl
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 28 Sep 2011 17:42:20 +
Source: libdbd-sybase-perl
Binary: libdbd-sybase-perl
Architecture: source amd64
Version: 1.09-1
Distribution: unstable
Urgency: low
Maintainer: Steve Langasek vor...@debian.org
Changed-By: Steve Langasek vor...@debian.org
Description:
libdbd-sybase-perl - Sybase/MS SQL database driver for the DBI module
Closes: 269198 329526 577513 643502
Changes:
libdbd-sybase-perl (1.09-1) unstable; urgency=low
.
* New upstream release. Closes: #329526.
- includes upstream fix for handling two sequential prepare()s without
an execute(). Closes: #269198.
* dbdimp.c: Add a patch from Raphael Descamps raphael.desca...@1und1.de
to disable BLK_VERSION_* checks if NO_BLK isn't defined.
* Add debian/watch file.
* Makefile.PL: if libct isn't found on the filesystem, assume it's
FreeTDS - fixing a build failure with multiarched freetds.
Closes: #643502.
* Switch to dh(1) and debhelper compat 8.
* Build-depend on libdbi-perl (= 1.612-1) for dh_perl_dbi, so we get a
DBI ABI identifier in our package dependencies. Closes: #577513.
* Add ${misc:Depends} to make debhelper and lintian happy
* Set Vcs-Bzr/Vcs-Browser in debian/control.
* Bump policy-version to 3.9.2.
* Put the manpage in the right '3pm' section, not '3perl' which is
apparently meant only for perl itself.
Checksums-Sha1:
f1e94bc533fb5ce9eac5e767407be7f0948bf87c 1969 libdbd-sybase-perl_1.09-1.dsc
23cad59ab7892732175336087093b1e3c2bda09a 194414
libdbd-sybase-perl_1.09.orig.tar.gz
7d9ad528149a8a340110f915c1cedb3b6060b10f 3081 libdbd-sybase-perl_1.09-1.diff.gz
64f7a8e0828699ac8ffbed1c9c9accc3161bfe68 133758
libdbd-sybase-perl_1.09-1_amd64.deb
Checksums-Sha256:
caed3d183b8f95453dff8ea174626d72641cf85d57ea9ecb86f0e9966d453d28 1969
Bug#643691: CPU eating
When using upstream code it doesn't segfault but eats 100% CPU :( -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643695: haskell-dpkg: FTBFS: pkg-config could not be found
Source: haskell-dpkg Version: 0.0.0-1 Severity: serious Justification: fails to build from source Builds of haskell-dpkg in minimal environments (such as on the autobuilders) have been failing: hlibrary.setup: The program pkg-config version =0.9.0 is required but it could not be found. make: *** [dist-ghc] Error 1 Could you please declare a build dependency on pkg-config and check (with pbuilder or the like) that no others are missing? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643357: marked as done (bickley: FTBFS: kozo-db.c:79:30: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Wed, 28 Sep 2011 18:47:40 + with message-id e1r8zas-0002aj...@franck.debian.org and subject line Bug#643357: fixed in bickley 0.4.4-3 has caused the Debian Bug report #643357, regarding bickley: FTBFS: kozo-db.c:79:30: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bickley Version: 0.4.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[3]: Entering directory `/build/bickley-V2OHYZ/bickley-0.4.4/kozo' CCkozo-db.o kozo-db.c: In function 'handle_lookup_error': kozo-db.c:79:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c:84:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c: In function 'handle_put_error': kozo-db.c:95:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c:99:30: error: format not a string literal and no format arguments [-Werror=format-security] kozo-db.c: In function 'check_version': kozo-db.c:173:21: warning: variable 'err' set but not used [-Wunused-but-set-variable] kozo-db.c: At top level: kozo-db.c:890:1: warning: 'dump_data' defined but not used [-Wunused-function] cc1: some warnings being treated as errors make[3]: *** [libkozo_la-kozo-db.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/bickley_0.4.4-2_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: bickley Source-Version: 0.4.4-3 We believe that the bug you reported is fixed in the latest version of bickley, which is due to be installed in the Debian FTP archive: bickley-daemons-dbg_0.4.4-3_i386.deb to main/b/bickley/bickley-daemons-dbg_0.4.4-3_i386.deb bickley-daemons_0.4.4-3_i386.deb to main/b/bickley/bickley-daemons_0.4.4-3_i386.deb bickley_0.4.4-3.debian.tar.gz to main/b/bickley/bickley_0.4.4-3.debian.tar.gz bickley_0.4.4-3.dsc to main/b/bickley/bickley_0.4.4-3.dsc libbickley-0.4-0_0.4.4-3_i386.deb to main/b/bickley/libbickley-0.4-0_0.4.4-3_i386.deb libbickley-dev_0.4.4-3_i386.deb to main/b/bickley/libbickley-dev_0.4.4-3_i386.deb libkozo-dev_0.4.4-3_i386.deb to main/b/bickley/libkozo-dev_0.4.4-3_i386.deb libkozo0_0.4.4-3_i386.deb to main/b/bickley/libkozo0_0.4.4-3_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) paul...@debian.org (supplier of updated bickley package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Sep 2011 02:09:42 +0800 Source: bickley Binary: bickley-daemons libkozo0 libkozo-dev libbickley-0.4-0 libbickley-dev bickley-daemons-dbg Architecture: source i386 Version: 0.4.4-3 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) paul...@debian.org Changed-By: Ying-Chun Liu (PaulLiu) paul...@debian.org Description: bickley-daemons - bickley daemons for meta data management API and framework bickley-daemons-dbg - bickley daemons for meta data management API and framework (debug libbickley-0.4-0 - bickley is the client API which access the metadata libbickley-dev - bickley is the client API which access the metadata (dev) libkozo-dev - kozo is a database
Bug#643505: marked as done (libspring-security-2.0-java: FTBFS: Cannot open sRGB.pdf)
Your message dated Wed, 28 Sep 2011 20:49:50 +0200 with message-id calj2o_2+iuezw2s_tjbo+uhd+avscw0a8hudunqokyekgkv...@mail.gmail.com and subject line Re: Bug#643505: libspring-security-2.0-java: FTBFS: Cannot open sRGB.pdf has caused the Debian Bug report #643505, regarding libspring-security-2.0-java: FTBFS: Cannot open sRGB.pdf 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.) -- 643505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libspring-security-2.0-java Version: 2.0.5.RELEASE-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: Writing index.html for book(spring-security-reference-guide) Note: namesp. cut : stripped namespace before processing Spring Security WARNING: cannot add @xml:base to node set root element. Relative paths may not work. Note: namesp. cut : processing stripped document Spring Security Note: namesp. cut : stripped namespace before processing Spring Security WARNING: cannot add @xml:base to node set root element. Relative paths may not work. Note: namesp. cut : processing stripped document Spring Security Making portrait pages on A4 paper (210mmx297mm) Exception java.lang.IllegalArgumentException: Cannot open file sRGB.pf make[1]: *** [override_dh_auto_build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/libspring-security-2.0-java_2.0.5.RELEASE-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Hi, On Tue, Sep 27, 2011 at 3:47 PM, Didier Raboud o...@debian.org wrote: java.lang.IllegalArgumentException: Cannot open file sRGB.pf the problem has been fixed with a recent upload of openjdk-6. Torsten ---End Message---
Bug#643506: marked as done (localizer: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 20:52:53 +0200 with message-id CALj2o_1dVjH6BT9EFrx=og8AHHCBb=uw-nbuz_gtit+9f5h...@mail.gmail.com and subject line Re: Bug#643506: localizer: FTBFS: Error building POM has caused the Debian Bug report #643506, regarding localizer: FTBFS: Error building POM 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.) -- 643506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: localizer Version: 1.13-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Fri Sep 23 23:25:59 CEST 2011 [INFO] Final Memory: 18M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/localizer_1.13-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: localizer Version: 1.13-2 On Tue, Sep 27, 2011 at 3:48 PM, Didier Raboud o...@debian.org wrote: [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin fixed by adding Build-Depends-Indep: libmaven-plugin-tools-java. Torsten ---End Message---
Bug#643664: marked as done (lilypond: FTBFS on i386 and kfreebsd-i386)
Your message dated Wed, 28 Sep 2011 18:51:49 + with message-id e1r8zet-0002br...@franck.debian.org and subject line Bug#643664: fixed in lilypond 2.14.2-2 has caused the Debian Bug report #643664, regarding lilypond: FTBFS on i386 and kfreebsd-i386 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.) -- 643664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lilypond Version: 2.14.2-1 Severity: serious Justification: fails to build from source See https://buildd.debian.org/status/fetch.php?pkg=lilypondarch=kfreebsd-i386ver=2.14.2-1stamp=1317146914 and https://buildd.debian.org/status/fetch.php?pkg=lilypondarch=i386ver=2.14.2-1stamp=1317145924 job 0 terminated with signal: 11 error: Children (3 2 1 0) exited with errors. command failed: /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/out/bin/lilypond -I ./ -I ./out-test -I ../../input -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/snippets -I ../../input/regression/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/included/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out/ -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures/./out-test -dbackend=eps --formats=ps -djob-count=4 -dseparate-log-files -dinclude-eps-fonts -dgs-load-lily-fonts --header=texidoc -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/included/ -ddump-profile -dcheck-internal-types -ddump-signatures -danti-alias-factor=1 -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/out/lybook-testdb -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression/out-test -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/snippets -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/input/regression -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/included -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/mf/out -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures -I /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/Documentation/pictures/out-test --formats=eps -deps-box-padding=3.00 -dread-file-list -dno-strip-output-dir /build/buildd-lilypond_2.14.2-1-i386-bX0d2s/lilypond-2.14.2/out/lybook-testdb/snippet-names-1138864437.ly Cheers, Julien ---End Message--- ---BeginMessage--- Source: lilypond Source-Version: 2.14.2-2 We believe that the bug you reported is fixed in the latest version of lilypond, which is due to be installed in the Debian FTP archive: lilypond-data_2.14.2-2_all.deb to main/l/lilypond/lilypond-data_2.14.2-2_all.deb lilypond-doc_2.14.2-2_all.deb to main/l/lilypond/lilypond-doc_2.14.2-2_all.deb lilypond_2.14.2-2.diff.gz to main/l/lilypond/lilypond_2.14.2-2.diff.gz lilypond_2.14.2-2.dsc to main/l/lilypond/lilypond_2.14.2-2.dsc lilypond_2.14.2-2_amd64.deb to main/l/lilypond/lilypond_2.14.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Don Armstrong d...@debian.org (supplier of updated lilypond package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 28 Sep 2011 09:44:40 -0700 Source: lilypond Binary: lilypond lilypond-data lilypond-doc Architecture: source amd64 all Version: 2.14.2-2 Distribution:
Bug#642495: marked as done (Fail to install stardict-gtk)
Your message dated Wed, 28 Sep 2011 19:05:01 +
with message-id e1r8zrf-0005gd...@franck.debian.org
and subject line Bug#642495: fixed in stardict 3.0.1-9
has caused the Debian Bug report #642495,
regarding Fail to install stardict-gtk
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.)
--
642495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: stardict
Version: 3.0.1-8
Severity: grave
Hi,
stardict-gtk and stardict-gnome both ship stardict.desktop now, while
in the earlier versions it is shipped within stardict-common,
$ cat debian/stardict-gtk.install
stardict usr/bin/
debian/tmp/usr/share/applications/* # stardict.desktop
$ cat debian/stardict-gnome.install
debian/tmp/usr/bin/stardict
debian/tmp/usr/lib/bonobo/servers/GNOME_Stardict.server
debian/tmp/usr/share/gnome/*
debian/tmp/usr/share/applications/* # stardict.desktop
debian/tmp/etc/gconf/schemas/*
debian/tmp/usr/share/idl/*
it causes error during installation such as,
Unpacking replacement stardict-gtk ...
dpkg: error processing
/var/cache/apt/archives/stardict-gtk_3.0.1-8_amd64.deb (--unpack):
trying to overwrite '/usr/share/applications/stardict.desktop', which
is also in package stardict-common 3.0.1-7
configured to not write apport reports
Preparing to replace
stardict-common 3.0.1-7 (using .../stardict-common_3.0.1-8_all.deb) ...
Unpacking replacement stardict-common ...
Preparing to replace stardict 3.0.1-7 (using .../stardict_3.0.1-8_all.deb) ...
Unpacking replacement stardict ...
Processing triggers for menu ...
Processing triggers for man-db ...
Processing triggers for bash-completion ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for install-info ...
Processing triggers for doc-base ...
Processing 1 changed doc-base file...
Registering documents with scrollkeeper...
Errors were encountered while processing:
/var/cache/apt/archives/stardict-gtk_3.0.1-8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
dpkg: dependency problems prevent configuration of stardict:
stardict depends on stardict-gtk (= 3.0.1-8) | stardict-gnome (= 3.0.1-8);
however:
Version of stardict-gtk on system is 3.0.1-7+b1.
Package stardict-gnome is not installed.
dpkg: error processing stardict (--configure):
dependency problems - leaving unconfigured
it might work by moving stardict.desktop to stardict-common or
declaring stardict-{gtk,gnome} conflicted with earlier versions of
stardict-common.
Kind regards,
Lifeng Sun
--
signature.asc
Description: GnuPG digital signature
---End Message---
---BeginMessage---
Source: stardict
Source-Version: 3.0.1-9
We believe that the bug you reported is fixed in the latest version of
stardict, which is due to be installed in the Debian FTP archive:
stardict-common_3.0.1-9_all.deb
to main/s/stardict/stardict-common_3.0.1-9_all.deb
stardict-gnome_3.0.1-9_amd64.deb
to main/s/stardict/stardict-gnome_3.0.1-9_amd64.deb
stardict-gtk_3.0.1-9_amd64.deb
to main/s/stardict/stardict-gtk_3.0.1-9_amd64.deb
stardict-plugin-espeak_3.0.1-9_amd64.deb
to main/s/stardict/stardict-plugin-espeak_3.0.1-9_amd64.deb
stardict-plugin-festival_3.0.1-9_amd64.deb
to main/s/stardict/stardict-plugin-festival_3.0.1-9_amd64.deb
stardict-plugin-gucharmap_3.0.1-9_amd64.deb
to main/s/stardict/stardict-plugin-gucharmap_3.0.1-9_amd64.deb
stardict-plugin-spell_3.0.1-9_amd64.deb
to main/s/stardict/stardict-plugin-spell_3.0.1-9_amd64.deb
stardict-plugin_3.0.1-9_amd64.deb
to main/s/stardict/stardict-plugin_3.0.1-9_amd64.deb
stardict_3.0.1-9.debian.tar.gz
to main/s/stardict/stardict_3.0.1-9.debian.tar.gz
stardict_3.0.1-9.dsc
to main/s/stardict/stardict_3.0.1-9.dsc
stardict_3.0.1-9_all.deb
to main/s/stardict/stardict_3.0.1-9_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 642...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrew Lee (李健秋) ajq...@debian.org (supplier of updated stardict package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 28 Sep 2011 15:21:19 +0800
Source:
Bug#643427: marked as done (libidn2-0: FTBFS: idn2.c:161:5: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Wed, 28 Sep 2011 19:03:20 + with message-id e1r8zpc-0004s1...@franck.debian.org and subject line Bug#643427: fixed in libidn2-0 0.8-1 has caused the Debian Bug report #643427, regarding libidn2-0: FTBFS: idn2.c:161:5: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 643427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libidn2-0 Version: 0.7-6 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I./.. -I./.. -I./../gl -I./../gl -I./gl -I./gl -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -c idn2.c idn2.c: In function 'hexdump': idn2.c:110:5: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] /usr/include/string.h:399:15: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c:116:3: warning: pointer targets in passing argument 1 of '__builtin_strlen' differ in signedness [-Wpointer-sign] idn2.c:116:3: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c:116:3: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] idn2.c:116:3: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c:116:3: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] idn2.c:116:3: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c:116:3: warning: pointer targets in passing argument 1 of '__builtin_strlen' differ in signedness [-Wpointer-sign] idn2.c:116:3: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c:116:3: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] idn2.c:116:3: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c:116:3: warning: pointer targets in passing argument 2 of '__builtin_strcmp' differ in signedness [-Wpointer-sign] idn2.c:116:3: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c:117:5: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] /usr/include/string.h:399:15: note: expected 'const char *' but argument is of type 'uint8_t *' idn2.c: In function 'main': idn2.c:136:3: warning: statement with no effect [-Wunused-value] idn2.c:137:3: warning: statement with no effect [-Wunused-value] idn2.c:161:5: error: format not a string literal and no format arguments [-Werror=format-security] idn2.c:179:4: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[5]: *** [idn2.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/libidn2-0_0.7-6_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg1.html A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: libidn2-0 Source-Version: 0.8-1 We believe that the bug you reported is fixed in the latest version of libidn2-0, which is due to be installed in the Debian FTP archive: idn2_0.8-1_amd64.deb to main/libi/libidn2-0/idn2_0.8-1_amd64.deb libidn2-0-dbg_0.8-1_amd64.deb to main/libi/libidn2-0/libidn2-0-dbg_0.8-1_amd64.deb libidn2-0-dev_0.8-1_amd64.deb to main/libi/libidn2-0/libidn2-0-dev_0.8-1_amd64.deb libidn2-0_0.8-1.debian.tar.gz to main/libi/libidn2-0/libidn2-0_0.8-1.debian.tar.gz libidn2-0_0.8-1.dsc to main/libi/libidn2-0/libidn2-0_0.8-1.dsc libidn2-0_0.8-1_amd64.deb to main/libi/libidn2-0/libidn2-0_0.8-1_amd64.deb libidn2-0_0.8.orig.tar.gz to main/libi/libidn2-0/libidn2-0_0.8.orig.tar.gz A summary of the
Bug#643019: monit: FTBFS: configure: error: Architecture not supported: `uname`.
Hi, we we have added support for GNU/kFreeBSD to Monit … it will be part of next release (monit 5.4). It is necessary to install the libkvm-dev package to compile Monit on kFreeBSD. Regards, Martin On Sep 26, 2011, at 6:06 PM, Christoph Egger wrote: Package: src:monit Version: 1:5.3-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: checking for sys/filio.h... yes configure: error: Architecture not supported: `uname`. configure: error: ./configure failed for libmonit Full build log at https://buildd.debian.org/status/fetch.php?pkg=monitarch=kfreebsd-amd64ver=1%3A5.3-1stamp=1316043872 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 642157 in 1.256-1
Processing commands for cont...@bugs.debian.org:
found 642157 1.256-1
Bug #642157 {Done: Dominique Dumont d...@debian.org} [libconfig-model-perl]
libconfig-model-tkui-perl: FTBFS: test failures
There is no source info for the package 'libconfig-model-perl' at version
'1.256-1' with architecture ''
Unable to make a source version for version '1.256-1'
Bug Marked as found in versions 1.256-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
642157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642157
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#643500: marked as done (jcaptcha: FTBFS: Test failures.)
Your message dated Wed, 28 Sep 2011 19:33:37 + with message-id e1r8zsv-99...@franck.debian.org and subject line Bug#643500: fixed in jcaptcha 2.0~alpha1-2 has caused the Debian Bug report #643500, regarding jcaptcha: FTBFS: Test failures. 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.) -- 643500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jcaptcha Version: 2.0~alpha1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /build/jcaptcha-OHD6vh/jcaptcha-2.0~alpha1/jcaptcha/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 48 seconds [INFO] Finished at: Fri Sep 23 22:39:52 CEST 2011 [INFO] Final Memory: 13M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/jcaptcha_2.0~alpha1-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: jcaptcha Source-Version: 2.0~alpha1-2 We believe that the bug you reported is fixed in the latest version of jcaptcha, which is due to be installed in the Debian FTP archive: jcaptcha_2.0~alpha1-2.debian.tar.gz to main/j/jcaptcha/jcaptcha_2.0~alpha1-2.debian.tar.gz jcaptcha_2.0~alpha1-2.dsc to main/j/jcaptcha/jcaptcha_2.0~alpha1-2.dsc libjcaptcha-java-doc_2.0~alpha1-2_all.deb to main/j/jcaptcha/libjcaptcha-java-doc_2.0~alpha1-2_all.deb libjcaptcha-java_2.0~alpha1-2_all.deb to main/j/jcaptcha/libjcaptcha-java_2.0~alpha1-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated jcaptcha package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 21:15:26 +0200 Source: jcaptcha Binary: libjcaptcha-java libjcaptcha-java-doc Architecture: source all Version: 2.0~alpha1-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libjcaptcha-java - Java framework for CAPTCHA definition and integration libjcaptcha-java-doc - Documentation for JCaptcha Closes: 643500 Changes: jcaptcha (2.0~alpha1-2) unstable; urgency=low . * Team upload . [ James Page ] * Fix FTBFS due to changes in dependency chain causing no fonts to be installed: - debian/control: added ttf-dejavu-core to Build-Depends-Indep. * debian/libjcaptcha-java.classpath: removed servlet-api-2.5.jar from classpath as this should always be provided by the servlet container. * debian/control: Updated my email address in Uploaders. . [ Torsten Werner ] * Ignore test failures. (Closes: #643500) Checksums-Sha1: 9345c1498d9347d6749637c782ccf375e8da71aa 1696 jcaptcha_2.0~alpha1-2.dsc c3b63884ae141e14a5bd06f66fcc4dfae8ccb90c 5293 jcaptcha_2.0~alpha1-2.debian.tar.gz 595268fa464e841fbb072310c134a5704de855d4 189102 libjcaptcha-java_2.0~alpha1-2_all.deb 9b273966c12341aeb390700a201c3808e3029eaf 503470 libjcaptcha-java-doc_2.0~alpha1-2_all.deb Checksums-Sha256:
Bug#643703: asterisk: SHA-1 code is doesn't allow modification
Package: asterisk Version: 1:1.6.2.9-2+squeeze3 Severity: serious Tags: upstream Justification: Policy 2.1.3 User: gnewsense-...@nongnu.org Usertags: gnewsense libreplanet File main/sha1.c has this license notice: * This document and translations of it may be copied and furnished to * others, and derivative works that comment on or otherwise explain it * or assist in its implementation may be prepared, copied, published * and distributed, in whole or in part, without restriction of any * kind, provided that the above copyright notice and this paragraph are * included on all such copies and derivative works. However, this * document itself may not be modified in any way, such as by removing * the copyright notice or references to the Internet Society or other * Internet organizations, except as needed for the purpose of * developing Internet standards in which case the procedures for * copyrights defined in the Internet Standards process must be * followed, or as required to translate it into languages other than * English. To my understanding that means you can extend, but not modify the text/ code in this file. This violates DFSG. It looks like this code was copied straight from RFC 3174. I found a discussion [2] on debian-legal from a few years back that says that RFC texts are non-free (except for the first 1000 or so). A summary about copyright on RFC Editor [3] says that derivative works are allowed, but doesn't go into detail. [1] http://www.rfc-editor.org/rfc/rfc3174.txt [2] http://lists.debian.org/debian-legal/2006/04/msg00223.html [3] http://www.rfc-editor.org/copyright.17Feb04.html -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.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
Bug#556340: marked as done (FTBFS with binutils-gold)
Your message dated Wed, 28 Sep 2011 20:54:19 + with message-id e1r9191-0008co...@franck.debian.org and subject line Bug#556340: fixed in sdl-ttf2.0 2.0.9-1.1 has caused the Debian Bug report #556340, regarding FTBFS with binutils-gold 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.) -- 556340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sdl-ttf2.0 Version: 2.0.9-1 Severity: minor User: peter.fritzs...@gmx.de Usertags: no-add-needed Tried to build your package and it fails to build with GNU binutils-gold. The important difference is that --no-add-needed is the default behavior of of GNU binutils-gold. Please provide all needed libraries to the linker when building your executables. It is maybe better in your case that libSDL_ttf.so gets linked against the needed libraries to fix that problem. You can use --no-undefined (or respective -Wl,--no-undefined when linking with g++ or gcc) to check your libraries if they still have symbols which doesn't get resolved by them. dpkg-shlibdeps will also print warnings about unresolved symbols when it gets run in your debian/rules. More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking /bin/bash ./libtool --tag=CC --mode=link gcc -g -O2 -I/usr/include/freetype2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -DHAVE_OPENGL -o showfont showfont.o libSDL_ttf.la -lfreetype -lz -L/usr/lib -lSDL gcc -g -O2 -I/usr/include/freetype2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -DHAVE_OPENGL -o .libs/showfont showfont.o ./.libs/libSDL_ttf.so -L/usr/lib /usr/lib/libfreetype.so -lz /usr/lib/libSDL.so /usr/bin/ld: ./.libs/libSDL_ttf.so: error: undefined reference to 'ceilf' collect2: ld returned 1 exit status make[1]: *** [showfont] Error 1 ---End Message--- ---BeginMessage--- Source: sdl-ttf2.0 Source-Version: 2.0.9-1.1 We believe that the bug you reported is fixed in the latest version of sdl-ttf2.0, which is due to be installed in the Debian FTP archive: libsdl-ttf2.0-0_2.0.9-1.1_amd64.deb to main/s/sdl-ttf2.0/libsdl-ttf2.0-0_2.0.9-1.1_amd64.deb libsdl-ttf2.0-dev_2.0.9-1.1_amd64.deb to main/s/sdl-ttf2.0/libsdl-ttf2.0-dev_2.0.9-1.1_amd64.deb sdl-ttf2.0_2.0.9-1.1.diff.gz to main/s/sdl-ttf2.0/sdl-ttf2.0_2.0.9-1.1.diff.gz sdl-ttf2.0_2.0.9-1.1.dsc to main/s/sdl-ttf2.0/sdl-ttf2.0_2.0.9-1.1.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 556...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Regis Boudin re...@debian.org (supplier of updated sdl-ttf2.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 20:12:07 +0100 Source: sdl-ttf2.0 Binary: libsdl-ttf2.0-0 libsdl-ttf2.0-dev Architecture: source amd64 Version: 2.0.9-1.1 Distribution: unstable Urgency: low Maintainer: Samuel Mimram smim...@debian.org Changed-By: Regis Boudin re...@debian.org Description: libsdl-ttf2.0-0 - ttf library for Simple DirectMedia Layer with FreeType 2 support libsdl-ttf2.0-dev - development files for SDL ttf library (version 2.0) Closes: 556340 631839 633341 Changes: sdl-ttf2.0 (2.0.9-1.1) unstable; urgency=low . * Non-maintainer upload. * Explicitly link against libm, fixing FTBFS with --no-undefined. Closes: #556340. * Stop shipping la file. Closes: #631839, 633341. Checksums-Sha1: bba398c58d5251a0d5e8f6e42445c459ea9fa6f5 1221 sdl-ttf2.0_2.0.9-1.1.dsc 0fa6beb8ceb93d40f69fede16aa0a1de9153b99d 22448 sdl-ttf2.0_2.0.9-1.1.diff.gz e83917bd07ae558432ba85e5576d21c3e09184f9 16596 libsdl-ttf2.0-0_2.0.9-1.1_amd64.deb 27f4905e236909f2c9cc8589cee8221ed046cb40 25802 libsdl-ttf2.0-dev_2.0.9-1.1_amd64.deb Checksums-Sha256: 64517efb626fe8c908a5fb3382e0c7bbb0a61078f7ab9e519392a0809b3b6200 1221 sdl-ttf2.0_2.0.9-1.1.dsc c314e64209533522d5c34489c0347f814045889d7e49715a7e506474645debc7 22448 sdl-ttf2.0_2.0.9-1.1.diff.gz 0226be08488ffed2f18e2fc05b9df1cf1b4175574b827c0c6fe1d0830f25503c 16596 libsdl-ttf2.0-0_2.0.9-1.1_amd64.deb 0008044e107233b9530f5c740d25209cfd29e44f7ebf725b5f0e89556289e90d 25802 libsdl-ttf2.0-dev_2.0.9-1.1_amd64.deb Files:
Bug#643543: marked as done (maven-compiler-plugin: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 20:52:19 + with message-id e1r9175-0007yt...@franck.debian.org and subject line Bug#643543: fixed in maven-compiler-plugin 2.0.2-6 has caused the Debian Bug report #643543, regarding maven-compiler-plugin: FTBFS: Error building POM 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.) -- 643543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-compiler-plugin Version: 2.0.2-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Sep 23 22:59:20 CEST 2011 [INFO] Final Memory: 5M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-compiler-plugin_2.0.2-5_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-compiler-plugin Source-Version: 2.0.2-6 We believe that the bug you reported is fixed in the latest version of maven-compiler-plugin, which is due to be installed in the Debian FTP archive: libmaven-compiler-plugin-java-doc_2.0.2-6_all.deb to main/m/maven-compiler-plugin/libmaven-compiler-plugin-java-doc_2.0.2-6_all.deb libmaven-compiler-plugin-java_2.0.2-6_all.deb to main/m/maven-compiler-plugin/libmaven-compiler-plugin-java_2.0.2-6_all.deb maven-compiler-plugin_2.0.2-6.debian.tar.gz to main/m/maven-compiler-plugin/maven-compiler-plugin_2.0.2-6.debian.tar.gz maven-compiler-plugin_2.0.2-6.dsc to main/m/maven-compiler-plugin/maven-compiler-plugin_2.0.2-6.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-compiler-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 21:40:34 +0200 Source: maven-compiler-plugin Binary: libmaven-compiler-plugin-java libmaven-compiler-plugin-java-doc Architecture: source all Version: 2.0.2-6 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-compiler-plugin-java - Maven Compiler plugin libmaven-compiler-plugin-java-doc - Documentation for Maven Compiler Plugin Closes: 643543 Changes: maven-compiler-plugin (2.0.2-6) unstable; urgency=low . * Add missing Build-Depends-Indep: libmaven-plugin-tools-java. (Closes: #643543) Checksums-Sha1: b6608955ba396a183d90260a9f6ed748f325ea5c 1895 maven-compiler-plugin_2.0.2-6.dsc 5d4a9ebe0bf0251bb80a9de415d8c18a0ec9a202 4544 maven-compiler-plugin_2.0.2-6.debian.tar.gz a546b6161b10efb58bbc59b63f581a80e07f166f 16284 libmaven-compiler-plugin-java_2.0.2-6_all.deb 67de9ae9447bd1a8458d81af1e4a75c339fdce59 28348
Bug#643544: marked as done (maven-dependency-plugin: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 20:52:33 + with message-id e1r917j-00081l...@franck.debian.org and subject line Bug#643544: fixed in maven-dependency-plugin 2.1-4 has caused the Debian Bug report #643544, regarding maven-dependency-plugin: FTBFS: Error building POM 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.) -- 643544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-dependency-plugin Version: 2.1-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Sep 23 23:04:13 CEST 2011 [INFO] Final Memory: 5M/694M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-dependency-plugin_2.1-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-dependency-plugin Source-Version: 2.1-4 We believe that the bug you reported is fixed in the latest version of maven-dependency-plugin, which is due to be installed in the Debian FTP archive: libmaven-dependency-plugin-java-doc_2.1-4_all.deb to main/m/maven-dependency-plugin/libmaven-dependency-plugin-java-doc_2.1-4_all.deb libmaven-dependency-plugin-java_2.1-4_all.deb to main/m/maven-dependency-plugin/libmaven-dependency-plugin-java_2.1-4_all.deb maven-dependency-plugin_2.1-4.debian.tar.gz to main/m/maven-dependency-plugin/maven-dependency-plugin_2.1-4.debian.tar.gz maven-dependency-plugin_2.1-4.dsc to main/m/maven-dependency-plugin/maven-dependency-plugin_2.1-4.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-dependency-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 21:50:17 +0200 Source: maven-dependency-plugin Binary: libmaven-dependency-plugin-java libmaven-dependency-plugin-java-doc Architecture: source all Version: 2.1-4 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-dependency-plugin-java - Maven Dependency Plugin libmaven-dependency-plugin-java-doc - Documentation for Maven Dependency Plugin Closes: 643544 Changes: maven-dependency-plugin (2.1-4) unstable; urgency=low . * Add missing Build-Depends-Indep: libmaven-plugin-tools-java. (Closes: #643544) Checksums-Sha1: 3849bb381a41e2b90b3f5bfa5a10133a29372125 2108 maven-dependency-plugin_2.1-4.dsc c1dc13dfd0a6892142469aac1ed85d9e00f61966 4675 maven-dependency-plugin_2.1-4.debian.tar.gz 081a107be55f472f71992eac0f8a87876b484468 85194 libmaven-dependency-plugin-java_2.1-4_all.deb
Bug#643545: marked as done (maven-doxia-tools: FTBFS: There are test failures.)
Your message dated Wed, 28 Sep 2011 20:52:46 + with message-id e1r917w-00084e...@franck.debian.org and subject line Bug#643545: fixed in maven-doxia-tools 1.2.1-2 has caused the Debian Bug report #643545, regarding maven-doxia-tools: FTBFS: There are test failures. 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.) -- 643545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-doxia-tools Version: 1.2.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /build/maven-doxia-tools-DwP31r/maven-doxia-tools-1.2.1/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 17 seconds [INFO] Finished at: Fri Sep 23 22:45:59 CEST 2011 [INFO] Final Memory: 18M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-doxia-tools_1.2.1-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-doxia-tools Source-Version: 1.2.1-2 We believe that the bug you reported is fixed in the latest version of maven-doxia-tools, which is due to be installed in the Debian FTP archive: libmaven-doxia-tools-java-doc_1.2.1-2_all.deb to main/m/maven-doxia-tools/libmaven-doxia-tools-java-doc_1.2.1-2_all.deb libmaven-doxia-tools-java_1.2.1-2_all.deb to main/m/maven-doxia-tools/libmaven-doxia-tools-java_1.2.1-2_all.deb maven-doxia-tools_1.2.1-2.debian.tar.gz to main/m/maven-doxia-tools/maven-doxia-tools_1.2.1-2.debian.tar.gz maven-doxia-tools_1.2.1-2.dsc to main/m/maven-doxia-tools/maven-doxia-tools_1.2.1-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-doxia-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 22:28:16 +0200 Source: maven-doxia-tools Binary: libmaven-doxia-tools-java libmaven-doxia-tools-java-doc Architecture: source all Version: 1.2.1-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-doxia-tools-java - utilities for integrating Doxia in Maven libmaven-doxia-tools-java-doc - Documentation for Maven Doxia Integration Tools Closes: 643545 Changes: maven-doxia-tools (1.2.1-2) unstable; urgency=low . * Ignore test errors and failures because some tests require network access. (Closes: #643545) Checksums-Sha1: 8c9ed75c79d72d2d72f3290dc308f17a85a45c7c 1960 maven-doxia-tools_1.2.1-2.dsc a755ba2b2cb4dbe21603b54b4edc7ec9d6e8f89e 5638 maven-doxia-tools_1.2.1-2.debian.tar.gz 739e52e34fb3b51d5f9cdb740128d5a5f30593a3 39836 libmaven-doxia-tools-java_1.2.1-2_all.deb 5f76d5d9e9b20560aa0a73c18d027271efc0f9f4 62710 libmaven-doxia-tools-java-doc_1.2.1-2_all.deb Checksums-Sha256: 4d93819626bb2a87164b860d0ae59b26e8260761a57bd8e7d89f6757aad0c071 1960 maven-doxia-tools_1.2.1-2.dsc 2dc9b0cc5f2badeba9c6fe9e2d767f87fcea07f36a0707b369632d8c8b4afc95 5638
Processed: severity of 643205 is serious, tagging 643205
Processing commands for cont...@bugs.debian.org: severity 643205 serious Bug #643205 [src:lintian] lintian: FTBFS: patch-systems-quilt-debian-changes: dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING -b patch-systems-quilt-debian-changes-1.0 gave error exit status 2 Severity set to 'serious' from 'important' tags 643205 + pending Bug #643205 [src:lintian] lintian: FTBFS: patch-systems-quilt-debian-changes: dpkg-buildpackage: error: dpkg-source -iNEVER_MATCH_ANYTHING -INEVER_MATCH_ANYTHING -b patch-systems-quilt-debian-changes-1.0 gave error exit status 2 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 643205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643205 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#643556: marked as done (gdb-mingw-w64: FTBFS: Unpack-time patching fails.)
Your message dated Wed, 28 Sep 2011 21:18:49 + with message-id e1r91wj-0004j5...@franck.debian.org and subject line Bug#643556: fixed in gdb-mingw-w64 1 has caused the Debian Bug report #643556, regarding gdb-mingw-w64: FTBFS: Unpack-time patching fails. 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.) -- 643556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gdb-mingw-w64 Version: 0.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 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 tar xf /usr/src/gdb.tar.* rm -rf /build/gdb-mingw-w64-9c3bYT/gdb-mingw-w64-0.1/upstream mv gdb /build/gdb-mingw-w64-9c3bYT/gdb-mingw-w64-0.1/upstream touch unpack-stamp patch -dupstream -p1 debian/patches/gdb-spelling-fixes.patch patching file gdb/breakpoint.c Hunk #1 succeeded at 12692 (offset 1086 lines). Hunk #2 succeeded at 12701 (offset 1086 lines). patching file gdb/breakpoint.h Hunk #1 succeeded at 1044 (offset 146 lines). Hunk #2 succeeded at 1058 (offset 146 lines). patching file gdb/ChangeLog-2003 patching file gdb/cli/cli-dump.c Hunk #1 succeeded at 679 (offset -3 lines). Hunk #2 succeeded at 719 (offset -3 lines). Hunk #3 succeeded at 731 (offset -3 lines). Hunk #4 succeeded at 743 (offset -3 lines). Hunk #5 succeeded at 755 (offset -3 lines). Hunk #6 succeeded at 767 (offset -3 lines). patching file gdb/dwarf2expr.c Hunk #1 succeeded at 330 (offset 7 lines). Hunk #2 succeeded at 498 (offset 7 lines). patching file gdb/gdbarch.c Hunk #1 FAILED at 3961. 1 out of 1 hunk FAILED -- saving rejects to file gdb/gdbarch.c.rej patching file gdb/gdbarch.sh Hunk #1 FAILED at 1931. 1 out of 1 hunk FAILED -- saving rejects to file gdb/gdbarch.sh.rej patching file gdb/po/gdb.pot Hunk #1 succeeded at 3235 with fuzz 1 (offset 62 lines). Hunk #2 succeeded at 3243 (offset 62 lines). Hunk #3 succeeded at 4645 with fuzz 1 (offset 201 lines). Hunk #4 succeeded at 4659 with fuzz 1 (offset 201 lines). Hunk #5 succeeded at 4673 with fuzz 1 (offset 201 lines). Hunk #6 succeeded at 4687 with fuzz 1 (offset 201 lines). Hunk #7 succeeded at 4701 with fuzz 1 (offset 201 lines). Hunk #8 succeeded at 6728 with fuzz 1 (offset 285 lines). Hunk #9 succeeded at 6739 with fuzz 1 (offset 285 lines). Hunk #10 succeeded at 8635 with fuzz 2 (offset 486 lines). patching file gdb/remote.c Hunk #1 FAILED at 6159. 1 out of 1 hunk FAILED -- saving rejects to file gdb/remote.c.rej patching file gdb/testsuite/gdb.base/help.exp patching file sim/ppc/ChangeLog Hunk #1 succeeded at 2997 (offset 48 lines). patching file sim/ppc/vm.c make: *** [patch-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/gdb-mingw-w64_0.1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: gdb-mingw-w64 Source-Version: 1 We believe that the bug you reported is fixed in the latest version of gdb-mingw-w64, which is due to be installed in the Debian FTP archive: gdb-mingw-w64-target_7.3-1+1_all.deb to main/g/gdb-mingw-w64/gdb-mingw-w64-target_7.3-1+1_all.deb gdb-mingw-w64_1.dsc to main/g/gdb-mingw-w64/gdb-mingw-w64_1.dsc gdb-mingw-w64_1.tar.gz to main/g/gdb-mingw-w64/gdb-mingw-w64_1.tar.gz gdb-mingw-w64_7.3-1+1_amd64.deb to main/g/gdb-mingw-w64/gdb-mingw-w64_7.3-1+1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt st...@sk2.org (supplier of updated gdb-mingw-w64 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 27 Sep 2011 23:36:02 +0200 Source: gdb-mingw-w64 Binary: gdb-mingw-w64 gdb-mingw-w64-target
Bug#643709: libpeas: FTBFS on ia64
Package: libpeas Version: 1.1.1-1 Severity: serious Justification: fails to build from source Looks like the latest libpeas upload FTBFS on ia64: https://buildd.debian.org/status/fetch.php?pkg=libpeasarch=ia64ver=1.1.1-1stamp=1312853584 make[5]: Leaving directory `/build/buildd-libpeas_1.1.1-1-ia64-9buMIp/libpeas-1.1.1/tests/libpeas' TEST: engine... (pid=8094) /engine/new: OK /engine/dispose: OK /engine/get-default: OK /engine/load-plugin: OK /engine/load-plugin-with-dep:OK /engine/load-plugin-with-self-dep: OK /engine/load-plugin-with-nonexistent-dep:OK /engine/unload-plugin: OK /engine/unload-plugin-with-dep: OK /engine/unload-plugin-with-self-dep: OK /engine/unavailable-plugin: OK /engine/not-loadable-plugin: OK /engine/loaded-plugins: OK /engine/nonexistent-loader: OK /engine/disabled-loader: OK /engine/enable-loader-multiple-times:OK /engine/nonexistent-search-path: OK /engine/shutdown:OK PASS: engine TEST: extension-c... (pid=8115) /extension/c/garbage-collect:OK /extension/c/provides-valid: OK /extension/c/provides-invalid: OK /extension/c/create-valid: OK /extension/c/create-invalid: OK /extension/c/reload: OK /bin/bash: line 1: 8093 Terminated G_SLICE=debug-blocks gtester --verbose engine extension-c extension-python extension-set plugin-info make[4]: *** [test] Error 143 /extension/c/call-no-args: FAIL GTester: last random seed: R02Sc1aabbd739f3beab05ea8648a3007c0b make[4]: Leaving directory `/build/buildd-libpeas_1.1.1-1-ia64-9buMIp/libpeas-1.1.1/tests/libpeas' make[3]: *** [test] Error 1 Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643710: fqterm: FTBFS(kfreebsd): linux/soundcard.h: No such file or directory
Package: src:fqterm Version: 0.9.6.9-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: [ 5%] Building CXX object src/common/CMakeFiles/fqterm_common.dir/fqterm_sound.o cd /build/buildd-fqterm_0.9.6.9-1-kfreebsd-amd64-gFhiVG/fqterm-0.9.6.9/obj-x86_64-kfreebsd-gnu/src/common /usr/bin/g++ -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DAUDIO_OSS -D_OS_LINUX_ -DQT_NO_DEBUG -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall -Os -DNDEBUG -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/build/buildd-fqterm_0.9.6.9-1-kfreebsd-amd64-gFhiVG/fqterm-0.9.6.9/obj-x86_64-kfreebsd-gnu/src/common -Wall -D FQTERM_VERSION_STRING=\0.9.6\ -D FQTERM_SVN_REVISION=\0\ -o CMakeFiles/fqterm_common.dir/fqterm_sound.o -c /build/buildd-fqterm_0.9.6.9-1-kfreebsd-amd64-gFhiVG/fqterm-0.9.6.9/src/common/fqterm_sound.cpp /build/buildd-fqterm_0.9.6.9-1-kfreebsd-amd64-gFhiVG/fqterm-0.9.6.9/src/common/fqterm_sound.cpp:39:29: fatal error: linux/soundcard.h: No such file or directory compilation terminated. make[3]: *** [src/common/CMakeFiles/fqterm_common.dir/fqterm_sound.o] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=fqtermarch=kfreebsd-amd64ver=0.9.6.9-1stamp=1317230665 The best solution to this problem might be to just replace linux/soundcard by sys/soundcard which is available not only on linux but also on (k)FreeBSD. Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- 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 630203 is serious
Processing commands for cont...@bugs.debian.org: severity 630203 serious Bug #630203 [src:libpmount] libpmount: FTBFS: error: field 'export' has incomplete type Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 630203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630203 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#633461: marked as done (gobject-introspection: fails to install with Python 2.7: E: pycompile:234: Requested versions are not installed)
Your message dated Wed, 28 Sep 2011 23:14:32 +0200 with message-id 4e838e38.7070...@debian.org and subject line binNMUs scheduled and built has caused the Debian Bug report #633461, regarding gobject-introspection: fails to install with Python 2.7: E: pycompile:234: Requested versions are not installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 633461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gobject-introspection Version: 0.10.8-2 Severity: important User: debian-pyt...@lists.debian.org Usertags: python2.7 If I install python 2.7.2-2 from experimental and gobject-introspection, the installation fails: | # apt-get install -y python-minimal/experimental python/experimental gobject-introspection | Reading package lists... Done | Building dependency tree | Reading state information... Done | Selected version '2.7.2-2' (Debian:experimental [all]) for 'python-minimal' | Selected version '2.7.2-2' (Debian:experimental [all]) for 'python' | The following extra packages will be installed: | libexpat1 libffi5 libgirepository-1.0-1 libglib2.0-0 libpcre3 libsqlite3-0 libssl1.0.0 mime-support python2.7 python2.7-minimal | Suggested packages: | python-doc python-tk python-profiler python2.7-doc binfmt-support | Recommended packages: | libglib2.0-data shared-mime-info file | The following NEW packages will be installed: | gobject-introspection libexpat1 libffi5 libgirepository-1.0-1 libglib2.0-0 libpcre3 libsqlite3-0 libssl1.0.0 mime-support python python-minimal python2.7 | python2.7-minimal | 0 upgraded, 13 newly installed, 0 to remove and 0 not upgraded. [snip - downloading and unpacking] | Setting up libffi5 (3.0.9-7) ... | Setting up libssl1.0.0 (1.0.0d-3) ... | Setting up libpcre3 (8.12-3) ... | Setting up libsqlite3-0 (3.7.7-2) ... | Setting up mime-support (3.51-1) ... | update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. | Setting up python2.7-minimal (2.7.2-2) ... | Linking and byte-compiling packages for runtime python2.7... | Setting up libexpat1 (2.0.1-7) ... | Setting up python2.7 (2.7.2-2) ... | Setting up python-minimal (2.7.2-2) ... | Setting up python (2.7.2-2) ... | Setting up libglib2.0-0 (2.28.6-1) ... | No schema files found: doing nothing. | Setting up libgirepository-1.0-1 (0.10.8-2) ... | Setting up gobject-introspection (0.10.8-2) ... | E: pycompile:234: Requested versions are not installed | dpkg: error processing gobject-introspection (--configure): | subprocess installed post-installation script returned error exit status 3 | Errors were encountered while processing: | gobject-introspection | configured to not write apport reports | E: Sub-process /usr/bin/dpkg returned an error code (1) -- Jakub Wilk ---End Message--- ---BeginMessage--- binNMUs have been scheduled and have been built everywhere. -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- signature.asc Description: OpenPGP digital signature ---End Message---
Bug#643711: qcake: FTBFS(kfreebsd): error: 'ALuint' does not name a type
Package: src:qcake Version: 0.7.2-2 Severity: serious Tags: sid wheezy X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: g++ -c -pipe -I/usr/include/python2.7 -I/usr/include/python2.7 -g -D_REENTRANT -Wall -W -DUSE_SCRIPT_DEBUGGER -DQT_PHONON_LIB -DQT_SCRIPT_LIB -DQT_SCRIPTTOOLS_LIB -DQT_XML_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/glibc-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript -I/usr/include/phonon -I/usr/include/qt4 -I../include -I/usr/include/qt4/phonon_compat -I/usr/X11R6/include -I. -I. -o audioenv.o audioenv.cpp In file included from audioenv.cpp:14:0: audioenv.hpp:67:4: error: 'ALuint' does not name a type audioenv.hpp:68:4: error: 'ALuint' does not name a type audioenv.hpp:69:4: error: 'ALuint' does not name a type audioenv.cpp:45:32: error: ISO C++ forbids declaration of 'ALboolean' with no type [-fpermissive] audioenv.cpp:45:32: error: typedef 'ALboolean' is initialized (use decltype instead) audioenv.cpp:45:20: error: 'vorbisLoader' was not declared in this scope audioenv.cpp:46:1: error: 'vorbisLoader' does not name a type audioenv.cpp: In constructor 'AudioEnv::AudioEnv(QObject*)': audioenv.cpp:52:5: error: 'nextBuffer' was not declared in this scope [...] Full build log at https://buildd.debian.org/status/fetch.php?pkg=qcakearch=kfreebsd-amd64ver=0.7.2-2%2Bb1stamp=1317229127 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643546: marked as done (maven-install-plugin: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 21:30:17 + with message-id e1r91hp-0001x8...@franck.debian.org and subject line Bug#643546: fixed in maven-install-plugin 2.3-4 has caused the Debian Bug report #643546, regarding maven-install-plugin: FTBFS: Error building POM 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.) -- 643546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-install-plugin Version: 2.3-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Sep 23 22:58:00 CEST 2011 [INFO] Final Memory: 5M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-install-plugin_2.3-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-install-plugin Source-Version: 2.3-4 We believe that the bug you reported is fixed in the latest version of maven-install-plugin, which is due to be installed in the Debian FTP archive: libmaven-install-plugin-java-doc_2.3-4_all.deb to main/m/maven-install-plugin/libmaven-install-plugin-java-doc_2.3-4_all.deb libmaven-install-plugin-java_2.3-4_all.deb to main/m/maven-install-plugin/libmaven-install-plugin-java_2.3-4_all.deb maven-install-plugin_2.3-4.debian.tar.gz to main/m/maven-install-plugin/maven-install-plugin_2.3-4.debian.tar.gz maven-install-plugin_2.3-4.dsc to main/m/maven-install-plugin/maven-install-plugin_2.3-4.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-install-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 22:37:12 +0200 Source: maven-install-plugin Binary: libmaven-install-plugin-java libmaven-install-plugin-java-doc Architecture: source all Version: 2.3-4 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-install-plugin-java - Maven install plugin libmaven-install-plugin-java-doc - Documentation for Maven Install Plugin Closes: 643546 Changes: maven-install-plugin (2.3-4) unstable; urgency=low . * Add missing Build-Depends-Indep: libmaven-plugin-tools-java. (Closes: #643546) Checksums-Sha1: 094ab9dc4d28812f5acd5454be62d93bea9592c8 1842 maven-install-plugin_2.3-4.dsc a5d5affbd1da65b408806ac227712f0c2d901b0b 4371 maven-install-plugin_2.3-4.debian.tar.gz 75d50c6d73d57025236c880604fefbfbf6b8881e 15932 libmaven-install-plugin-java_2.3-4_all.deb 045e5bd03e1ba1524890305adfc39496a1334ada 26970 libmaven-install-plugin-java-doc_2.3-4_all.deb Checksums-Sha256:
Bug#643547: marked as done (maven-jar-plugin: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 21:30:33 + with message-id e1r91i5-00024e...@franck.debian.org and subject line Bug#643547: fixed in maven-jar-plugin 2.2-6 has caused the Debian Bug report #643547, regarding maven-jar-plugin: FTBFS: Error building POM 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.) -- 643547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-jar-plugin Version: 2.2-5 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Sep 23 23:21:34 CEST 2011 [INFO] Final Memory: 5M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-jar-plugin_2.2-5_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-jar-plugin Source-Version: 2.2-6 We believe that the bug you reported is fixed in the latest version of maven-jar-plugin, which is due to be installed in the Debian FTP archive: libmaven-jar-plugin-java-doc_2.2-6_all.deb to main/m/maven-jar-plugin/libmaven-jar-plugin-java-doc_2.2-6_all.deb libmaven-jar-plugin-java_2.2-6_all.deb to main/m/maven-jar-plugin/libmaven-jar-plugin-java_2.2-6_all.deb maven-jar-plugin_2.2-6.debian.tar.gz to main/m/maven-jar-plugin/maven-jar-plugin_2.2-6.debian.tar.gz maven-jar-plugin_2.2-6.dsc to main/m/maven-jar-plugin/maven-jar-plugin_2.2-6.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-jar-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 22:45:56 +0200 Source: maven-jar-plugin Binary: libmaven-jar-plugin-java libmaven-jar-plugin-java-doc Architecture: source all Version: 2.2-6 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-jar-plugin-java - Maven Jar Plugin libmaven-jar-plugin-java-doc - Documentation Maven Jar Plugin Closes: 643547 Changes: maven-jar-plugin (2.2-6) unstable; urgency=low . * Add missing Build-Depends-Indep: libmaven-plugin-tools-java. (Closes: #643547) Checksums-Sha1: 477366ce6431d3a266d62542e2b9c66c46041b1f 1899 maven-jar-plugin_2.2-6.dsc 05f3bf9af66b1f2eb8651486ffa144af346b3b53 4733 maven-jar-plugin_2.2-6.debian.tar.gz 7c6a3fd90d6979a2e837a0d2b46c84ad9bbba07a 23606 libmaven-jar-plugin-java_2.2-6_all.deb dea0c27bf44c7776e093d8bd5e3ff82a600f6daf 37642 libmaven-jar-plugin-java-doc_2.2-6_all.deb Checksums-Sha256: 34f6ffb39740c5059140ad0a439c845f5c773336f47e62760b0f51e92bff606a 1899 maven-jar-plugin_2.2-6.dsc
Bug#643549: marked as done (maven-repository-builder: FTBFS: There are test failures.)
Your message dated Wed, 28 Sep 2011 21:30:50 + with message-id e1r91im-0002gh...@franck.debian.org and subject line Bug#643549: fixed in maven-repository-builder 1.0~alpha2-3 has caused the Debian Bug report #643549, regarding maven-repository-builder: FTBFS: There are test failures. 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.) -- 643549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-repository-builder Version: 1.0~alpha2-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /build/maven-repository-builder-sAV18h/maven-repository-builder-1.0~alpha2/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Sat Sep 24 00:24:48 CEST 2011 [INFO] Final Memory: 18M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-repository-builder_1.0~alpha2-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-repository-builder Source-Version: 1.0~alpha2-3 We believe that the bug you reported is fixed in the latest version of maven-repository-builder, which is due to be installed in the Debian FTP archive: libmaven-repository-builder-java-doc_1.0~alpha2-3_all.deb to main/m/maven-repository-builder/libmaven-repository-builder-java-doc_1.0~alpha2-3_all.deb libmaven-repository-builder-java_1.0~alpha2-3_all.deb to main/m/maven-repository-builder/libmaven-repository-builder-java_1.0~alpha2-3_all.deb maven-repository-builder_1.0~alpha2-3.debian.tar.gz to main/m/maven-repository-builder/maven-repository-builder_1.0~alpha2-3.debian.tar.gz maven-repository-builder_1.0~alpha2-3.dsc to main/m/maven-repository-builder/maven-repository-builder_1.0~alpha2-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-repository-builder package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 23:04:04 +0200 Source: maven-repository-builder Binary: libmaven-repository-builder-java libmaven-repository-builder-java-doc Architecture: source all Version: 1.0~alpha2-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-repository-builder-java - Maven Repository Builder libmaven-repository-builder-java-doc - Documentation for Maven Repository Builder Closes: 643549 Changes: maven-repository-builder (1.0~alpha2-3) unstable; urgency=low . * Team upload * Ignore test failures because tests require network access to Maven central. (Closes: #643549) * Reformat extended Description. Checksums-Sha1: a4e339fefc2505117ac64422c439b8ee5882096f 1918 maven-repository-builder_1.0~alpha2-3.dsc d57ffe6456a57d9b58c2cd551eecc4feac33fee3 4040 maven-repository-builder_1.0~alpha2-3.debian.tar.gz ce368e8d6e7dda840e250124335f766182f20082 19350
Bug#643550: marked as done (maven-resources-plugin: FTBFS: Error building POM)
Your message dated Wed, 28 Sep 2011 21:31:06 + with message-id e1r91ic-0002to...@franck.debian.org and subject line Bug#643550: fixed in maven-resources-plugin 2.3-7 has caused the Debian Bug report #643550, regarding maven-resources-plugin: FTBFS: Error building POM 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.) -- 643550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-resources-plugin Version: 2.3-6 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs java-maven Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-plugin-plugin Reason: POM 'org.apache.maven.plugins:maven-plugin-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-plugin-plugin:pom:2.8 for project org.apache.maven.plugins:maven-plugin-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri Sep 23 22:46:26 CEST 2011 [INFO] Final Memory: 5M/724M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-resources-plugin_2.3-6_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-resources-plugin Source-Version: 2.3-7 We believe that the bug you reported is fixed in the latest version of maven-resources-plugin, which is due to be installed in the Debian FTP archive: libmaven-resources-plugin-java-doc_2.3-7_all.deb to main/m/maven-resources-plugin/libmaven-resources-plugin-java-doc_2.3-7_all.deb libmaven-resources-plugin-java_2.3-7_all.deb to main/m/maven-resources-plugin/libmaven-resources-plugin-java_2.3-7_all.deb maven-resources-plugin_2.3-7.debian.tar.gz to main/m/maven-resources-plugin/maven-resources-plugin_2.3-7.debian.tar.gz maven-resources-plugin_2.3-7.dsc to main/m/maven-resources-plugin/maven-resources-plugin_2.3-7.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-resources-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 23:10:33 +0200 Source: maven-resources-plugin Binary: libmaven-resources-plugin-java libmaven-resources-plugin-java-doc Architecture: source all Version: 2.3-7 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-resources-plugin-java - Maven resources plugin libmaven-resources-plugin-java-doc - Documentation for Maven resources plugin Closes: 643550 Changes: maven-resources-plugin (2.3-7) unstable; urgency=low . * Add missing Build-Depends-Indep: libmaven-plugin-tools-java. (Closes: #643550) Checksums-Sha1: 141d4f603da8c4ac25e31155a0df0d5258c0c337 1830 maven-resources-plugin_2.3-7.dsc fb6430541907f8173f24711fa8c2aab9cb7c95c1 4233 maven-resources-plugin_2.3-7.debian.tar.gz 0a82bbf8dfc96a48bb31a381e14aa28aa1506ae9 14152 libmaven-resources-plugin-java_2.3-7_all.deb 95964077a3a879d949be2330648f99125e891bae 30276
Bug#643278: install target in generated Makefile for ipelets missing
retitle 643278 install target in generated Makefile for ipelets missing severity 643278 normal tag 643278 +help thanks The problem is that the Makfile generated for shared/demo/CGAL_ipelets lacks most install related targets. It still works in squeeze (using cmake 2.8.2) and fails in current sid (using cmake 2.8.5), but worked in sid on August ~7th. First I thought the problem was related to the newer cmake version, but that's wrong. Installing cmake 2.8.5 (from backports) in Debian squeeze works fine. Maybe the problem is related to the introduction of multiarch. The new upstream version 3.9-1 has a workaround for the problem (custom cp rule instead of make install), hence, downgrading the severity. Joachim -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: install target in generated Makefile for ipelets missing
Processing commands for cont...@bugs.debian.org: retitle 643278 install target in generated Makefile for ipelets missing Bug #643278 [src:cgal] cgal: FTBFS: No rule to make target `install' Changed Bug title to 'install target in generated Makefile for ipelets missing' from 'cgal: FTBFS: No rule to make target `install'' severity 643278 normal Bug #643278 [src:cgal] install target in generated Makefile for ipelets missing Severity set to 'normal' from 'serious' tag 643278 +help Bug #643278 [src:cgal] install target in generated Makefile for ipelets missing Added tag(s) help. thanks Stopping processing here. Please contact me if you need assistance. -- 643278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643278 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#642756: Fixing RCs #634405 and #642756
Hi OdyX, it seems like neither you nor me can find a proper solution to solve the parallel building problems highlighted by bugs #634405 and #642756. Hence, I propose to simply drop parallel building support, with the attached patch. What do you think ? On one hand we could drop the parallel building support but on the other hand we would limit those who try out massive parallel building. An even simpler solution would be by not passing on DEB_BUILD_OPTIONS=parallel=n from the caller program, e. g. omitting -jn from dpkg-buildpackage. Furthermore I am not even sure if the issues are actually caused by the parallel building. I also experienced failures during the test stage in case of non-parallel building, although these failures only occurred very rarely. As far as I recall a mismatch of the calling convention (stdcall) was identified by me as likely candidate for the failures. I would need to dig out the change from the experimental unicode patch pushed into the git repository. So I tend more to keep the parallel building support. However I am undecided. Best regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643551: marked as done (maven-scm: FTBFS: Failed to resolve artifact.)
Your message dated Wed, 28 Sep 2011 22:03:18 + with message-id e1r92dm-0002ck...@franck.debian.org and subject line Bug#643551: fixed in maven-scm 1.3-4 has caused the Debian Bug report #643551, regarding maven-scm: FTBFS: Failed to resolve artifact. 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.) -- 643551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: maven-scm Version: 1.3-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.maven.scm:maven-scm-provider-vss:jar:debian Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.scm -DartifactId=maven-scm-provider-vss -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.scm -DartifactId=maven-scm-provider-vss -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.maven.scm:maven-scm-client:jar:1.3 2) org.apache.maven.scm:maven-scm-provider-vss:jar:debian -- 1 required artifact is missing. for artifact: org.apache.maven.scm:maven-scm-client:jar:1.3 from the specified remote repositories: central (http://repo1.maven.org/maven2) NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 7 seconds [INFO] Finished at: Fri Sep 23 23:02:33 CEST 2011 [INFO] Final Memory: 156M/1761M [INFO] make: *** [mvn-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/maven-scm_1.3-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: maven-scm Source-Version: 1.3-4 We believe that the bug you reported is fixed in the latest version of maven-scm, which is due to be installed in the Debian FTP archive: libmaven-scm-java-doc_1.3-4_all.deb to main/m/maven-scm/libmaven-scm-java-doc_1.3-4_all.deb libmaven-scm-java_1.3-4_all.deb to main/m/maven-scm/libmaven-scm-java_1.3-4_all.deb maven-scm_1.3-4.debian.tar.gz to main/m/maven-scm/maven-scm_1.3-4.debian.tar.gz maven-scm_1.3-4.dsc to main/m/maven-scm/maven-scm_1.3-4.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Torsten Werner twer...@debian.org (supplier of updated maven-scm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 28 Sep 2011 23:31:16 +0200 Source: maven-scm Binary: libmaven-scm-java libmaven-scm-java-doc Architecture: source all Version: 1.3-4 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Torsten Werner twer...@debian.org Description: libmaven-scm-java - Maven SCM provides a common API for doing SCM operations libmaven-scm-java-doc - Maven SCM provides a common API for doing
