Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 674451 important Bug #674451 [openstack-dashboard] openstack-dashboard: Compilation failed on: http://localhost:8083/syspanel/ Severity set to 'important' from 'grave' -- Stopping processing here. Please contact me if you need assistance. -- 674451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674451 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#667361: rtorrent: diff for NMU version 0.8.9-2.1
Hi, everybody.
On May 28 2012, gregor herrmann wrote:
(...)
Just ping me when I should look at the git repos again.
That will not be necessary. I was mislead that the libtorrent package needed
another binary package rename and, in that case, I would need to be
sponsored.
But that turned out not to be the case and I have just uploaded both
libtorrent and rtorrent.
Thanks for the offer anyway---I'm sure that I will need sponsoring in the
future.
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: uploaded to delayed/3
Processing commands for cont...@bugs.debian.org: tags 667138 + pending Bug #667138 [codeblocks] codeblocks: ftbfs with GCC-4.7 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 667138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667138 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#667138: uploaded to delayed/3
tags 667138 + pending
thanks
diff -Nru codeblocks-10.05/debian/changelog codeblocks-10.05/debian/changelog
--- codeblocks-10.05/debian/changelog 2011-03-08 10:13:16.0 +0100
+++ codeblocks-10.05/debian/changelog 2012-05-29 08:04:06.0 +0200
@@ -1,3 +1,11 @@
+codeblocks (10.05-2.1) unstable; urgency=low
+
+ * Non maintainer upload.
+ * Drop build dependency on libstdc++6-4.5-dev | libstdc++6-4.4-dev.
+ * Fix build failures with GCC 4.7, build with -fpermissive. Closes: #667138.
+
+ -- Matthias Klose d...@debian.org Tue, 29 May 2012 05:03:19 +
+
codeblocks (10.05-2) unstable; urgency=low
* Added Vcs-* fields to debian/control
diff -Nru codeblocks-10.05/debian/control codeblocks-10.05/debian/control
--- codeblocks-10.05/debian/control 2011-02-28 09:13:34.0 +0100
+++ codeblocks-10.05/debian/control 2012-05-29 07:03:57.0 +0200
@@ -11,7 +11,6 @@
, libbz2-dev
, zlib1g-dev
, libgtk2.0-dev
- , libstdc++6-4.5-dev | libstdc++6-4.4-dev
Standards-Version: 3.9.1
Homepage: http://codeblocks.org
Vcs-Git: git://git.debian.org/collab-maint/codeblocks.git
diff -Nru codeblocks-10.05/debian/patches/ftbfs-gcc-4.7.diff
codeblocks-10.05/debian/patches/ftbfs-gcc-4.7.diff
--- codeblocks-10.05/debian/patches/ftbfs-gcc-4.7.diff 1970-01-01
01:00:00.0 +0100
+++ codeblocks-10.05/debian/patches/ftbfs-gcc-4.7.diff 2012-05-29
08:03:43.0 +0200
@@ -0,0 +1,34 @@
+Index: codeblocks-10.05/src/plugins/contrib/help_plugin/defs.h
+===
+--- codeblocks-10.05.orig/src/plugins/contrib/help_plugin/defs.h
2010-05-22 10:29:35.0 +
codeblocks-10.05/src/plugins/contrib/help_plugin/defs.h2012-05-29
05:18:08.674124530 +
+@@ -289,7 +289,7 @@
+
+ if (i.second == false overwrite)
+ {
+-find(k)-second = t;
++this-find(k)-second = t;
+ }
+
+ return i.first;
+@@ -297,7 +297,7 @@
+
+ int remove(const Key k)
+ {
+-return erase(k);
++return this-erase(k);
+ }
+ };
+
+Index: codeblocks-10.05/src/plugins/contrib/help_plugin/man2html.cpp
+===
+--- codeblocks-10.05.orig/src/plugins/contrib/help_plugin/man2html.cpp
2010-05-22 10:29:35.0 +
codeblocks-10.05/src/plugins/contrib/help_plugin/man2html.cpp
2012-05-29 05:15:59.186120279 +
+@@ -150,6 +150,7 @@
+ # include kdeversion.h
+ # define BYTEARRAY(x) x
+ #endif
++#include unistd.h
+
+ #ifdef __MINGW32__
+ #include io.h
diff -Nru codeblocks-10.05/debian/patches/series
codeblocks-10.05/debian/patches/series
--- codeblocks-10.05/debian/patches/series 2011-02-23 19:05:15.0
+0100
+++ codeblocks-10.05/debian/patches/series 2012-05-29 07:13:27.0
+0200
@@ -2,3 +2,4 @@
02-no_Makefiles_in_debian_dir.patch
03-fix_libX11_linkage.patch
04-add_support_for_sh4.patch
+ftbfs-gcc-4.7.diff
diff -Nru codeblocks-10.05/debian/rules codeblocks-10.05/debian/rules
--- codeblocks-10.05/debian/rules 2011-01-19 23:14:57.0 +0100
+++ codeblocks-10.05/debian/rules 2012-05-29 07:05:23.0 +0200
@@ -15,7 +15,7 @@
--parallel
override_dh_auto_configure:
- dh_auto_configure -- --with-contrib-plugins=all
+ CXXFLAGS=$(dpkg-buildflags --get CXXFLAGS) -fpermissive
dh_auto_configure -- --with-contrib-plugins=all
override_dh_strip:
dh_strip -k
Bug#666383: marked as done (distcc: FTBFS: mkdir: cannot create directory `/etc/distcc': Permission denied)
Your message dated Tue, 29 May 2012 06:47:23 + with message-id e1szgdd-0003zb...@franck.debian.org and subject line Bug#666383: fixed in distcc 3.1-5 has caused the Debian Bug report #666383, regarding distcc: FTBFS: mkdir: cannot create directory `/etc/distcc': Permission denied 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.) -- 666383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: distcc Version: 3.1-4.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»/source' 'make install' will install distcc as follows: man pages/«PKGBUILDDIR»/debian/tmp/usr/share/man/man1 documents/«PKGBUILDDIR»/debian/tmp/usr/share/doc/distcc programs /«PKGBUILDDIR»/debian/tmp/usr/bin system configuration /etc shared data files/«PKGBUILDDIR»/debian/tmp/usr/share/distcc /bin/bash ./mkinstalldirs /«PKGBUILDDIR»/debian/tmp/usr/share/doc/distcc mkdir /«PKGBUILDDIR»/debian/tmp mkdir /«PKGBUILDDIR»/debian/tmp/usr mkdir /«PKGBUILDDIR»/debian/tmp/usr/share mkdir /«PKGBUILDDIR»/debian/tmp/usr/share/doc mkdir /«PKGBUILDDIR»/debian/tmp/usr/share/doc/distcc for p in AUTHORS COPYING NEWS README README.pump INSTALL TODO doc/protocol-1.txt doc/status-1.txt doc/protocol-2.txt doc/reporting-bugs.txt survey.txt; do\ /usr/bin/install -c -m 644 ./$p /«PKGBUILDDIR»/debian/tmp/usr/share/doc/distcc || exit 1; \ done /bin/bash ./mkinstalldirs /«PKGBUILDDIR»/debian/tmp/usr/share/man/man1 mkdir /«PKGBUILDDIR»/debian/tmp/usr/share/man mkdir /«PKGBUILDDIR»/debian/tmp/usr/share/man/man1 for p in man/distcc.1 man/distccd.1 man/distccmon-text.1 man/pump.1 man/include_server.1; do \ /usr/bin/install -c -m 644 ./$p /«PKGBUILDDIR»/debian/tmp/usr/share/man/man1 || exit 1; \ done /bin/bash ./mkinstalldirs /«PKGBUILDDIR»/debian/tmp/usr/bin mkdir /«PKGBUILDDIR»/debian/tmp/usr/bin for p in distcc distccd distccmon-text lsdistcc distccmon-gnome ; do \ /usr/bin/install -c $p /«PKGBUILDDIR»/debian/tmp/usr/bin || exit 1; \ done if test -z /usr/bin/python2.7; then \ echo Not building include-server: No suitable python found; \ else\ mkdir -p ./_include_server \ DISTCC_VERSION=3.1 \ SRCDIR=.\ CFLAGS=-g -O2 -MD -W -Wall -Wimplicit -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wmissing-declarations -Wuninitialized -D_REENTRANT-Wno-missing-prototypes -Wno-missing-declarations -Wno-write-strings -Wp,-U_FORTIFY_SOURCE \ CPPFLAGS=-DHAVE_CONFIG_H -D_GNU_SOURCE -DSYSCONFDIR=\/etc\ -DPKGDATADIR=\/«PKGBUILDDIR»/debian/tmp/usr/share/distcc\ -Isrc -I./src -I./lzo \ /usr/bin/python2.7 ./include_server/setup.py \ build \ --build-base=./_include_server \ --build-temp=./_include_server; \ fi setup.py: PYTHON_CFLAGS must be defined. running build running build_py running build_ext if test -z /usr/bin/python2.7; then \ echo Not building install-include-server: No suitable python found; \ else\ mkdir -p ./_include_server \ DESTDIR=`cd / pwd` \ DISTCC_VERSION=3.1 \ SRCDIR=.\ CFLAGS=-g -O2 -MD -W -Wall -Wimplicit -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wmissing-declarations -Wuninitialized -D_REENTRANT-Wno-missing-prototypes -Wno-missing-declarations -Wno-write-strings -Wp,-U_FORTIFY_SOURCE \ CPPFLAGS=-DHAVE_CONFIG_H -D_GNU_SOURCE -DSYSCONFDIR=\/etc\
Bug#667168: add patch (new upstream version)
tags 667168 + pending thanks Scott, I packaged v4.5, which builds using GCC 4.7 without changes. Ok to upload, or do you prefer to remove the package for the release? package at http://people.debian.org/~doko/tmp/ thanks, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: add patch (new upstream version)
Processing commands for cont...@bugs.debian.org: tags 667168 + pending Bug #667168 [fparser] fparser: ftbfs with GCC-4.7 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 667168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667168 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#544687: libpam-unix2: forks numerous instances of unix2_chkpwd
On Sun, 27 May 2012 21:53:59 +0200 Jakub Wilk jw...@debian.org wrote: It seems that this only happens when a user wants to unlock the screen, not when logging in. Does it happen regardless of whether the entered password was correct or not? This is always happening, regardless of if the password is correct or not. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667169: marked as done (fqterm: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 07:17:41 + with message-id e1szggx-0005a3...@franck.debian.org and subject line Bug#667169: fixed in fqterm 0.9.6.10-1.1 has caused the Debian Bug report #667169, regarding fqterm: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fqterm Version: 0.9.6.10-1 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. fqterm_trace.h:62:9: error: 'pause' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/fqterm_0.9.6.10-1_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] /usr/bin/make -f CMakeFiles/Makefile2 all make[2]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/make -f src/common/CMakeFiles/fqterm_common.dir/build.make src/common/CMakeFiles/fqterm_common.dir/depend make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 9 [ 1%] Generating fqterm_shortcuthelper.moc cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common /usr/bin/moc-qt4 -o /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common/fqterm_shortcuthelper.moc /«PKGBUILDDIR»/src/common/fqterm_shortcuthelper.h /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 8 [ 2%] Generating fqterm_sound.moc cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common /usr/bin/moc-qt4 -o /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common/fqterm_sound.moc /«PKGBUILDDIR»/src/common/fqterm_sound.h cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu /usr/bin/cmake -E cmake_depends Unix Makefiles /«PKGBUILDDIR» /«PKGBUILDDIR»/src/common /«PKGBUILDDIR»/obj-x86_64-linux-gnu /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common/CMakeFiles/fqterm_common.dir/DependInfo.cmake --color= Scanning dependencies of target fqterm_common make[3]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/make -f src/common/CMakeFiles/fqterm_common.dir/build.make src/common/CMakeFiles/fqterm_common.dir/build make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 1 [ 3%] Building CXX object src/common/CMakeFiles/fqterm_common.dir/common.o cd /«PKGBUILDDIR»/obj-x86_64-linux-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 -Wformat -Wformat-security -Werror=format-security -Wall -Os -DNDEBUG -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common-Wall -D FQTERM_VERSION_STRING=\0.9.6\ -D FQTERM_SVN_REVISION=\0\ -o CMakeFiles/fqterm_common.dir/common.o -c /«PKGBUILDDIR»/src/common/common.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 2 [ 4%] Building CXX object src/common/CMakeFiles/fqterm_common.dir/fqterm_trace.o cd /«PKGBUILDDIR»/obj-x86_64-linux-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 -Wformat -Wformat-security -Werror=format-security -Wall -Os -DNDEBUG -I/usr/include/qt4 -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/common-Wall -D FQTERM_VERSION_STRING=\0.9.6\ -D FQTERM_SVN_REVISION=\0\ -o CMakeFiles/fqterm_common.dir/fqterm_trace.o -c /«PKGBUILDDIR»/src/common/fqterm_trace.cpp In file included from /«PKGBUILDDIR»/src/common/fqterm_trace.cpp:29:0: /«PKGBUILDDIR»/src/common/fqterm_trace.h: In function 'void FQTerm::soft_break()': /«PKGBUILDDIR»/src/common/fqterm_trace.h:62:9: error: 'pause' was not declared in this scope make[3]: ***
Bug#667204: marked as done (ibam: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 07:17:56 + with message-id e1szggm-0005al...@franck.debian.org and subject line Bug#667204: fixed in ibam 1:0.5.2-2.1 has caused the Debian Bug report #667204, regarding ibam: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ibam Version: 1:0.5.2-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. /bin/sh: 1: gdk-pixbuf-config: not found The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/ibam_1:0.5.2-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] ---End Message--- ---BeginMessage--- Source: ibam Source-Version: 1:0.5.2-2.1 We believe that the bug you reported is fixed in the latest version of ibam, which is due to be installed in the Debian FTP archive: gkrellm-ibam_0.5.2-2.1_amd64.deb to main/i/ibam/gkrellm-ibam_0.5.2-2.1_amd64.deb ibam_0.5.2-2.1.diff.gz to main/i/ibam/ibam_0.5.2-2.1.diff.gz ibam_0.5.2-2.1.dsc to main/i/ibam/ibam_0.5.2-2.1.dsc ibam_0.5.2-2.1_amd64.deb to main/i/ibam/ibam_0.5.2-2.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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated ibam package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 May 2012 08:23:56 +0200 Source: ibam Binary: ibam gkrellm-ibam Architecture: source amd64 Version: 1:0.5.2-2.1 Distribution: unstable Urgency: low Maintainer: Martin Wuertele m...@debian.org Changed-By: Matthias Klose d...@debian.org Description: gkrellm-ibam - Advanced battery monitor for laptops - gkrellm plugin ibam - Advanced battery monitor for laptops Closes: 667204 Changes: ibam (1:0.5.2-2.1) unstable; urgency=low . * Non maintainer upload. * Fix build failure with GCC 4.7. Closes: #667204. Checksums-Sha1: c14c6d4838d4a1f71e1f9a57d5fc8f39327c80c8 1140 ibam_0.5.2-2.1.dsc b958e3256b61099c13e4ef7f96d6440d1034ff01 6115 ibam_0.5.2-2.1.diff.gz d1a4c7b004d1d5dc21db5bce2475993c7f3e1297 48074 ibam_0.5.2-2.1_amd64.deb 368bcf3a6a7ce1c8fd853810ae03591f6788ed49 35632 gkrellm-ibam_0.5.2-2.1_amd64.deb Checksums-Sha256: d848e873fedec847f45983d5c9fe022cb1ab9b3e67d328c18911bd2bddbcae8c 1140 ibam_0.5.2-2.1.dsc 4946a1e25da963997a7d5bc7be76b07b6706a9507b1a4438b4a214ec3d742b90 6115 ibam_0.5.2-2.1.diff.gz 8ebe1a74d3df8d2300defa9cb22f0634bcce54f34e5b87a9e701b2972d404708 48074 ibam_0.5.2-2.1_amd64.deb b96ecb7cab5c3bbd389f5a498aa375b622bdc3561e4e494675503082e6f5e938 35632 gkrellm-ibam_0.5.2-2.1_amd64.deb Files: 37f2c9af4e047867ee8b0b20788fbf3b 1140 utils optional ibam_0.5.2-2.1.dsc 4a1c3f63581cbcfc3f98f0d66c60cdce 6115 utils optional ibam_0.5.2-2.1.diff.gz 9645915c7cbcd3327a51d2ffa02c911f 48074 utils optional ibam_0.5.2-2.1_amd64.deb 486eb982b125d89b2771dd1be4dce885 35632 x11 optional gkrellm-ibam_0.5.2-2.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/Ec8kACgkQStlRaw+TLJyTmgCeN68XfyFHIwkzwpiUAtUI8qWq V6kAn0FJQlkVtBKMXL6Gd+/JIlIOSjrJ =ija1 -END PGP SIGNATURE- ---End Message---
Processed: Re: FTBFS on sid: checking for mysql_init... no
Processing commands for cont...@bugs.debian.org: tags 672824 - wheezy Bug #672824 [src:mediatomb] mediatomb: FTBFS on sid: checking for mysql_init... no Bug #674328 [src:mediatomb] mediatomb: FTBFS: conftest.c:131: undefined reference to `_doprnt' Removed tag(s) wheezy. Removed tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 672824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672824 674328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674328 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#672824: marked as done (mediatomb: FTBFS on sid: checking for mysql_init... no)
Your message dated Tue, 29 May 2012 03:26:19 -0400 with message-id caecnbvy2jh9i0kumys_c4f45jtyee7aqkbichyavd1seuez...@mail.gmail.com and subject line Re: FTBFS on sid: checking for mysql_init... no has caused the Debian Bug report #672824, regarding mediatomb: FTBFS on sid: checking for mysql_init... no 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.) -- 672824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mediatomb Version: 0.12.1-4 Severity: serious Justification: FTBFS Hello, mediatomb currently FTBFS on sid: checking for mysql_init... no configure: error: unable to configure mysql support I guess this is due to the new mysql version. Samuel -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Thibault samuel.thiba...@fnac.net tohi.cybercable.fr (212.198.0.3) si une personne se reconnait derriere cette adresse que ce soit un pirate ou une victime qu'il se manifeste, cette personne pourrait bien etre un petit malin -+- Fred in NPC : Maman, y a le routeur qui veut me hacker -+- ---End Message--- ---BeginMessage--- tags 672824 - wheezy thanks Fixed in libmysqlclient-dev 5.5.23+dfsg-2 ---End Message---
Bug#674992: actionaz: Please change Build-depends to libcv-dev to libopencv-dev
Source: actionaz
Version: 3.4.1-1
Severity: serious
Tags: patch
Hi,
actionaz FTBFS with latest opencv package.
Because pkg-config file of opencv move from libopencv-core-dev to
libopencv-dev.
We need to change Build-depends. Because actionaz depends on
pkg-config file and cv.h.
From opencv version 2.3.1-10, libopencv-dev came to depend on libcv-dev.
Therefore, you need to set libopencv-dev only.
Would update it?
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: debian-policy is the place to discuss this
Processing commands for cont...@bugs.debian.org: reassign 652011 debian-policy Bug #652011 [general] general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib Bug reassigned from package 'general' to 'debian-policy'. Ignoring request to alter found versions of bug #652011 to the same values previously set Ignoring request to alter fixed versions of bug #652011 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 652011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652011 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#667215: marked as done (jffi: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 07:33:59 + with message-id e1szgwj-0007gr...@franck.debian.org and subject line Bug#667215: fixed in jffi 1.0.2-8.1 has caused the Debian Bug report #667215, regarding jffi: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jffi Version: 1.0.2-8 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. [exec] cc: error: unrecognized command line option '-mimpure-text' The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/jffi_1.0.2-8_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] [javac] Compiling 30 source files to /«PKGBUILDDIR»/build/classes [javac] Init.java:171: warning: [deprecation] toURL() in java.io.File has been deprecated [javac] url = jar.toURL(); [javac] ^ [javac] 1 warning -generate-version-source: [echo] Generating Version.java [mkdir] Created dir: /«PKGBUILDDIR»/build/java/com/kenai/jffi -generate-version: [javac] Compiling 1 source file to /«PKGBUILDDIR»/build/classes -compile-java: -generate-native-headers: -build-native-library: [exec] make[1]: Entering directory `/«PKGBUILDDIR»' [exec] cc -o /«PKGBUILDDIR»/build/jni/libjffi-1.0.so -shared -mimpure-text -static-libgcc -Wl,-soname,libjffi-1.0.so -Wl,-O1 /«PKGBUILDDIR»/build/jni/jffi/Array.o /«PKGBUILDDIR»/build/jni/jffi/CallContext.o /«PKGBUILDDIR»/build/jni/jffi/ClosureMagazine.o /«PKGBUILDDIR»/build/jni/jffi/Exception.o /«PKGBUILDDIR»/build/jni/jffi/FastIntInvoke.o /«PKGBUILDDIR»/build/jni/jffi/FastLongInvoke.o /«PKGBUILDDIR»/build/jni/jffi/FastNumericInvoker.o /«PKGBUILDDIR»/build/jni/jffi/Foreign.o /«PKGBUILDDIR»/build/jni/jffi/Function.o /«PKGBUILDDIR»/build/jni/jffi/Internals.o /«PKGBUILDDIR»/build/jni/jffi/Invoke.o /«PKGBUILDDIR»/build/jni/jffi/LastError.o /«PKGBUILDDIR»/build/jni/jffi/Library.o /«PKGBUILDDIR»/build/jni/jffi/Memory.o /«PKGBUILDDIR»/build/jni/jffi/MemoryIO.o /«PKGBUILDDIR»/build/jni/jffi/MemoryUtil.o /«PKGBUILDDIR»/build/jni/jffi/Struct.o /«PKGBUILDDIR»/build/jni/jffi/Type.o /«PKGBUILDDIR»/build/jni/jffi/deprecated. o -lffi [exec] make[1]: Leaving directory `/«PKGBUILDDIR»' [exec] cc: error: unrecognized command line option '-mimpure-text' [exec] make[1]: *** [/«PKGBUILDDIR»/build/jni/libjffi-1.0.so] Error 1 BUILD FAILED /«PKGBUILDDIR»/custom-build.xml:125: exec returned: 2 Total time: 21 seconds make: *** [debian/stamp-ant-build] Error 1 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: jffi Source-Version: 1.0.2-8.1 We believe that the bug you reported is fixed in the latest version of jffi, which is due to be installed in the Debian FTP archive: jffi_1.0.2-8.1.debian.tar.gz to main/j/jffi/jffi_1.0.2-8.1.debian.tar.gz jffi_1.0.2-8.1.dsc to main/j/jffi/jffi_1.0.2-8.1.dsc libjffi-java_1.0.2-8.1_all.deb to main/j/jffi/libjffi-java_1.0.2-8.1_all.deb libjffi-jni_1.0.2-8.1_amd64.deb to main/j/jffi/libjffi-jni_1.0.2-8.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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated jffi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 May 2012 08:53:38 +0200 Source: jffi Binary: libjffi-java libjffi-jni Architecture: source all amd64 Version: 1.0.2-8.1
Bug#667230: marked as done (kredentials: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 07:34:24 + with message-id e1szgwi-0007ht...@franck.debian.org and subject line Bug#667230: fixed in kredentials 2.0~pre3-1.1 has caused the Debian Bug report #667230, regarding kredentials: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kredentials Version: 2.0~pre3-1 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. krb5_wrap.cpp:408:14: error: 'dup' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/kredentials_2.0~pre3-1_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu /usr/bin/cmake -E cmake_depends Unix Makefiles /«PKGBUILDDIR» /«PKGBUILDDIR»/src /«PKGBUILDDIR»/obj-x86_64-linux-gnu /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/CMakeFiles/kredentials.dir/DependInfo.cmake --color= Scanning dependencies of target kredentials make[3]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/make -f src/CMakeFiles/kredentials.dir/build.make src/CMakeFiles/kredentials.dir/build make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 1 [ 25%] Building CXX object src/CMakeFiles/kredentials.dir/kredentials_automoc.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src /usr/bin/g++ -D_BSD_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=25 -DKDE_DEFAULT_DEBUG_AREA=9876 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScriptTool s -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -o CMakeFiles/kredentials.dir/kredentials_automoc.o -c /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/kredentials_automoc.cpp /usr/bin/cmake -E cmake_progress_report /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 2 [ 50%] Building CXX object src/CMakeFiles/kredentials.dir/main.o cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src /usr/bin/g++ -D_BSD_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=25 -DKDE_DEFAULT_DEBUG_AREA=9876 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src -I/«PKGBUILDDIR»/src -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns
Bug#667239: marked as done (libapache2-mod-encoding: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 07:34:36 + with message-id e1szgwu-0007i8...@franck.debian.org and subject line Bug#667239: fixed in libapache2-mod-encoding 20040616-5.1 has caused the Debian Bug report #667239, regarding libapache2-mod-encoding: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libapache2-mod-encoding Version: 20040616-5 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. gcc: error: unrecognized command line option '-Wc,-Wall' The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/libapache2-mod-encoding_20040616-5_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] # Add here commands to compile the package. #/usr/bin/make #/usr/bin/docbook-to-man debian/libapache2-mod-encoding.sgml libapache2-mod-encoding.1 apxs2 -c -liconv_hook mod_encoding.c /usr/share/apr-1.0/build/libtool --silent --mode=compile --tag=disable-static x86_64-linux-gnu-gcc -prefer-pic -DLINUX=2 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_REENTRANT -I/usr/include -I/usr/include/apr-1.0 -I/usr/include/openssl -I/usr/include/xmltok -pthread -I/usr/include/apache2 -I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -I/usr/include -c -o mod_encoding.lo mod_encoding.c touch mod_encoding.slo mod_encoding.c: In function 'iconv_header': mod_encoding.c:195:3: warning: passing argument 2 of 'ap_getword' from incompatible pointer type [enabled by default] In file included from mod_encoding.c:72:0: /usr/include/apache2/httpd.h:1294:20: note: expected 'const char **' but argument is of type 'char **' mod_encoding.c: In function 'get_client_encoding': mod_encoding.c:245:5: warning: passing argument 1 of 'ap_regexec' from incompatible pointer type [enabled by default] In file included from /usr/include/apache2/httpd.h:59:0, from mod_encoding.c:72: /usr/include/apache2/ap_regex.h:119:17: note: expected 'const struct ap_regex_t *' but argument is of type 'struct regex_t *' mod_encoding.c: At top level: mod_encoding.c:365:4: warning: initialization from incompatible pointer type [enabled by default] mod_encoding.c:365:4: warning: (near initialization for 'mod_enc_commands[0].func.no_args') [enabled by default] mod_encoding.c:369:4: warning: initialization from incompatible pointer type [enabled by default] mod_encoding.c:369:4: warning: (near initialization for 'mod_enc_commands[1].func.no_args') [enabled by default] mod_encoding.c:373:4: warning: initialization from incompatible pointer type [enabled by default] mod_encoding.c:373:4: warning: (near initialization for 'mod_enc_commands[2].func.no_args') [enabled by default] mod_encoding.c:377:4: warning: initialization from incompatible pointer type [enabled by default] mod_encoding.c:377:4: warning: (near initialization for 'mod_enc_commands[3].func.no_args') [enabled by default] mod_encoding.c:381:4: warning: initialization from incompatible pointer type [enabled by default] mod_encoding.c:381:4: warning: (near initialization for 'mod_enc_commands[4].func.no_args') [enabled by default] /usr/share/apr-1.0/build/libtool --silent --mode=link --tag=disable-static x86_64-linux-gnu-gcc -o mod_encoding.la -liconv_hook -rpath /usr/lib/apache2/modules -module -avoid-versionmod_encoding.lo gcc -shared -o mod_encoding.so .libs/mod_encoding.o -Wc,-Wall -liconv_hook gcc: error: unrecognized command line option '-Wc,-Wall' make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: libapache2-mod-encoding Source-Version: 20040616-5.1 We believe that the bug you reported is fixed in the latest version of libapache2-mod-encoding, which is due to be installed in the Debian FTP archive: libapache2-mod-encoding_20040616-5.1.diff.gz to main/liba/libapache2-mod-encoding/libapache2-mod-encoding_20040616-5.1.diff.gz libapache2-mod-encoding_20040616-5.1.dsc
Bug#674242: marked as done (libopencv-dev: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/OpenCV/OpenCVConfig.cmake)
Your message dated Tue, 29 May 2012 07:36:24 + with message-id e1szgye-0007yv...@franck.debian.org and subject line Bug#674242: fixed in opencv 2.3.1-10 has caused the Debian Bug report #674242, regarding libopencv-dev: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/OpenCV/OpenCVConfig.cmake 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.) -- 674242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libopencv-dev Version: 2.3.1-9 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite files that are owned by other packages without declaring a Breaks/Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace libopencv-dev 2.3.1-8 (using .../libopencv-dev_2.3.1-9_amd64.deb) ... Unpacking replacement libopencv-dev ... dpkg: error processing /var/cache/apt/archives/libopencv-dev_2.3.1-9_amd64.deb (--unpack): trying to overwrite '/usr/share/OpenCV/OpenCVConfig.cmake', which is also in package libopencv-core-dev 2.3.1-8 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas libopencv-dev_2.3.1-9.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: opencv Source-Version: 2.3.1-10 We believe that the bug you reported is fixed in the latest version of opencv, which is due to be installed in the Debian FTP archive: libcv-dev_2.3.1-10_amd64.deb to main/o/opencv/libcv-dev_2.3.1-10_amd64.deb libcv2.3_2.3.1-10_amd64.deb to main/o/opencv/libcv2.3_2.3.1-10_amd64.deb libcvaux-dev_2.3.1-10_amd64.deb to main/o/opencv/libcvaux-dev_2.3.1-10_amd64.deb libcvaux2.3_2.3.1-10_amd64.deb to main/o/opencv/libcvaux2.3_2.3.1-10_amd64.deb libhighgui-dev_2.3.1-10_amd64.deb to main/o/opencv/libhighgui-dev_2.3.1-10_amd64.deb libhighgui2.3_2.3.1-10_amd64.deb to main/o/opencv/libhighgui2.3_2.3.1-10_amd64.deb libopencv-calib3d-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-calib3d-dev_2.3.1-10_amd64.deb libopencv-calib3d2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-calib3d2.3_2.3.1-10_amd64.deb libopencv-contrib-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-contrib-dev_2.3.1-10_amd64.deb libopencv-contrib2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-contrib2.3_2.3.1-10_amd64.deb libopencv-core-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-core-dev_2.3.1-10_amd64.deb libopencv-core2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-core2.3_2.3.1-10_amd64.deb libopencv-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-dev_2.3.1-10_amd64.deb libopencv-features2d-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-features2d-dev_2.3.1-10_amd64.deb libopencv-features2d2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-features2d2.3_2.3.1-10_amd64.deb libopencv-flann-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-flann-dev_2.3.1-10_amd64.deb libopencv-flann2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-flann2.3_2.3.1-10_amd64.deb libopencv-gpu-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-gpu-dev_2.3.1-10_amd64.deb libopencv-gpu2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-gpu2.3_2.3.1-10_amd64.deb libopencv-highgui-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-highgui-dev_2.3.1-10_amd64.deb libopencv-highgui2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-highgui2.3_2.3.1-10_amd64.deb libopencv-imgproc-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-imgproc-dev_2.3.1-10_amd64.deb libopencv-imgproc2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-imgproc2.3_2.3.1-10_amd64.deb libopencv-legacy-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-legacy-dev_2.3.1-10_amd64.deb libopencv-legacy2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-legacy2.3_2.3.1-10_amd64.deb libopencv-ml-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-ml-dev_2.3.1-10_amd64.deb libopencv-ml2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-ml2.3_2.3.1-10_amd64.deb libopencv-objdetect-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-objdetect-dev_2.3.1-10_amd64.deb libopencv-objdetect2.3_2.3.1-10_amd64.deb to main/o/opencv/libopencv-objdetect2.3_2.3.1-10_amd64.deb libopencv-video-dev_2.3.1-10_amd64.deb to main/o/opencv/libopencv-video-dev_2.3.1-10_amd64.deb
Bug#666672: please try 1.8.0 from experimental
Hi, The newly uploaded (to experimental) version 1.8.0 uses an internal crypto engine instead of libgcrypt. It reads from /dev/urandom instead of using libgcrypt. I believe libgcrypt initialize its RNG pool from /dev/random. Thus, I would expect that this problem goes away with 1.8.0 assuming your build hosts has a working /dev/urandom. /Simon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667353: marked as done (recoverjpeg: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 07:56:23 + with message-id e1szhhz-q0...@franck.debian.org and subject line Bug#667353: fixed in recoverjpeg 2.0-3.1 has caused the Debian Bug report #667353, regarding recoverjpeg: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: recoverjpeg Version: 2.0-3 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. recovermov.cpp:98:50: error: 'getopt' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/recoverjpeg_2.0-3_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none configure: creating ./config.status config.status: creating Makefile config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build -a make[1]: Entering directory `/«PKGBUILDDIR»' gcc -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\recoverjpeg\ -DVERSION=\2.0\ -I. -g -O2 -c recoverjpeg.c gcc -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\recoverjpeg\ -DVERSION=\2.0\ -I. -g -O2 -c utils.c gcc -g -O2 -o recoverjpeg recoverjpeg.o utils.o g++ -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\recoverjpeg\ -DVERSION=\2.0\ -I. -g -O2 -c -o recovermov.o recovermov.cpp recovermov.cpp: In function 'int main(int, char**)': recovermov.cpp:98:50: error: 'getopt' was not declared in this scope recovermov.cpp:101:31: error: 'optarg' was not declared in this scope recovermov.cpp:114:11: error: 'optind' was not declared in this scope make[1]: *** [recovermov.o] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: recoverjpeg Source-Version: 2.0-3.1 We believe that the bug you reported is fixed in the latest version of recoverjpeg, which is due to be installed in the Debian FTP archive: recoverjpeg_2.0-3.1.debian.tar.gz to main/r/recoverjpeg/recoverjpeg_2.0-3.1.debian.tar.gz recoverjpeg_2.0-3.1.dsc to main/r/recoverjpeg/recoverjpeg_2.0-3.1.dsc recoverjpeg_2.0-3.1_amd64.deb to main/r/recoverjpeg/recoverjpeg_2.0-3.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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated recoverjpeg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 05 Apr 2012 09:19:41 + Source: recoverjpeg Binary: recoverjpeg Architecture: source amd64 Version: 2.0-3.1 Distribution: unstable Urgency: low Maintainer: William Vera bi...@billy.com.mx Changed-By: Matthias Klose d...@debian.org Description: recoverjpeg - tool to recover JPEG images from
Processed: downgrading
Processing commands for cont...@bugs.debian.org: severity 637232 important Bug #637232 [general] general: Multiarch breaks support for non-multiarch toolchain Bug #639214 [general] eglibc: changes to paths concerning crt1.o, crti.o and crtn.o breaks building LLVM Trunk Bug #644986 [general] i386: Compiling gcc-snapshots from upstream with multiarch-toolchain? Bug #648889 [general] /usr/include/features.h(323): catastrophic error: could not open source file bits/predefs.h Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' # this bug is mainly ment to document a decission, so why critical? severity 652011 important Bug #652011 [debian-policy] general: Repeated pattern of FHS violation: Dependencies of /sbin and /bin, belong in /lib Severity set to 'important' from 'serious' # this is mainly disagreeing with the status-quo, so I dont think thats # serious either thanks Stopping processing here. Please contact me if you need assistance. -- 637232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637232 639214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639214 644986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644986 648889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648889 652011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652011 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#674996: linkchecker: wrong 404 reports
Package: linkchecker Version: 7.8-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Normal use of linkchecker via command line. linkchecker reports a lot of 404 errors, but when I open the reported URLs manually, everything is fine and the pages open in a browser without an error - so the output of linkchecker is unreliable at the moment, the reported 404 errors are wrong. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linkchecker depends on: ii libc6 2.13-32 ii python 2.7.2-10 ii python2.7 2.7.3~rc2-2.1 linkchecker recommends no packages. Versions of packages linkchecker suggests: pn clamav-daemon none pn linkchecker-gui none pn linkchecker-web none pn python-cssutils none pn python-gconfnone pn python-geoipnone pn python-optcomplete none pn python-pysqlite2none pn python-twillnone pn python-utidylib none -- Configuration Files: /etc/linkchecker/linkcheckerrc changed: [output] [text] [gml] [dot] [csv] separator=* [sql] [html] [blacklist] [xml] [gxml] [checking] [filtering] [authentication] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674998: Please revert to libtiff-dev before wheezy
Package: vtk Version: 5.8.0-12 Severity: serious -- Forwarded message -- From: Julien Cristau jcris...@debian.org Date: Tue, May 29, 2012 at 10:14 AM Subject: Re: vtk's tiff build-dep To: Mathieu Malaterre ma...@debian.org Cc: Steve Robbins s...@debian.org, v...@packages.debian.org, debian-science debian-scie...@lists.debian.org On Tue, May 29, 2012 at 10:08:41 +0200, Mathieu Malaterre wrote: Salut Julien, On Mon, May 28, 2012 at 11:45 AM, Julien Cristau jcris...@debian.org wrote: it seems you recently switched vtk to build-depend on libtiff5-dev. This is discouraged at this point. What is the reason for that change? I needed to get itk to compile with libtiff5-dev to handle large tiff. I could not get itk to use libtiff5-dev until vtk switches also to libtiff5-dev. Can't that wait until after wheezy? As a side note, I also switch VXL to use libtiff5-dev, is this also an issue ? Seeing how libvxl1.14 has 0 reverse dependencies in squeeze i don't care all that much. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 673245 serious Bug #673245 [tcl-vtk] tcl-vtk: Can't find a usable init.tcl in the following directories Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 673245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673245 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#674990: exim breaks (again?) with TLS packet with unexpected length
On Tue, May 29, 2012 at 02:40:35PM +0900, Norbert PREINING wrote: I have found various suggestions, like adding the Debian-exim user to the group shadow, Where is this dangerous suggestion written? How many CAs do you have enabled to trust? Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- 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#670181: rdate: Uses obsolete libbsd header that will disappear with 0.4.0
Processing commands for cont...@bugs.debian.org: severity 670181 serious Bug #670181 [src:rdate] rdate: Uses obsolete libbsd header that will disappear with 0.4.0 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 670181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670181 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#675002: libpadre-plugin-nopaste-perl: Not installable: padre-plugin-api-2 is no longer available to satisfy Depends
Package: libpadre-plugin-nopaste-perl Version: 0.3.1-3 Severity: grave Justification: renders package unusable Hi, your package can't be built (#674334) because of padre-plugin-api-2, which disappeared. But it also can't be installed any more, for the same reason. FWIW, this blocks the migration to testing for those packages: padre/0.96+dfsg1-1 libpadre-plugin-yaml-perl/0.06-1 libpadre-plugin-spellcheck-perl/1.25-1 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675003: glchess: New game dialog not showing up.
Package: glchess Version: 1:3.4.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, The documentation states: To start a new game, press the New Game buttton on the toolbar. The new game dialog is then shown, which allows you to setup a new game with the settings of your choice. But the New game dialog never shows. When starting it from the command line, nothing particular shows $ glchess ** Message: glchess.vala:396: Detected AI profile GNUchess in /usr/games/gnuchess Version: 3.4.1 Debian Wheezy Thanks for the good work! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages glchess depends on: ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii gnome-games-data 1:3.4.1-2 ii gnuchess 6.0.2-1 ii libc62.13-32 ii libcairo21.10.2-7 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglib2.0-0 2.32.0-4 ii libglu1-mesa [libglu1] 7.11.2-1 ii libgtk-3-0 3.4.2-1 ii librsvg2-2 2.36.1-1 ii libsqlite3-0 3.7.11-2 ii libx11-6 2:1.4.99.901-2 glchess recommends no packages. glchess suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672085: fixed upstream
tag 672085 + fixed-upstream
quit
I've chosen to implement the anonymous union patch from
http://sourceware.org/git/?p=glibc.git;a=patch;h=7dc6bd90c569c49807462b0740b18e32fab4d8b7
by Ulrich Drepper drep...@gmail.com in as far as that patch applies
to the md5 code remaining in QOF.
(svn diff attached)
I've got some more testing to do but this looks good, I expect to be
able to make a new upstream release in a few days.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
Index: qof/md5.c
===
--- qof/md5.c (revision 1327)
+++ qof/md5.c (working copy)
@@ -1,6 +1,6 @@
/* md5.c - Functions to compute MD5 message digest of files or memory blocks
according to the definition of MD5 in RFC 1321 from April 1992.
- Copyright (C) 1995, 1996 Free Software Foundation, Inc.
+ Copyright (C) 1995, 1996, 2011 Free Software Foundation, Inc.
NOTE: The canonical source of this file is maintained with the GNU C
Library. Bugs can be reported to bug-gl...@prep.ai.mit.edu.
@@ -116,9 +116,9 @@
memcpy (ctx-buffer[bytes], fillbuf, pad);
/* Put the 64-bit file length in *bits* at the end of the buffer. */
- *(md5_uint32 *) ctx-buffer[bytes + pad] = SWAP (ctx-total[0] 3);
- *(md5_uint32 *) ctx-buffer[bytes + pad + 4] =
- SWAP ((ctx-total[1] 3) | (ctx-total[0] 29));
+ ctx-buffer32[(bytes + pad) / 4] = SWAP (ctx-total[0] 3);
+ ctx-buffer32[(bytes + pad + 4) / 4] = SWAP ((ctx-total[1] 3) |
+ (ctx-total[0] 29));
/* Process last bytes. */
md5_process_block (ctx-buffer, bytes + pad + 8, ctx);
Index: qof/md5.h
===
--- qof/md5.h (revision 1327)
+++ qof/md5.h (working copy)
@@ -1,6 +1,6 @@
/* md5.h - Declaration of functions and data types used for MD5 sum
computing library functions.
- Copyright (C) 1995, 1996 Free Software Foundation, Inc.
+ Copyright (C) 1995, 1996, 2011 Free Software Foundation, Inc.
NOTE: The canonical source of this file is maintained with the GNU C
Library. Bugs can be reported to bug-gl...@prep.ai.mit.edu.
@@ -86,7 +86,11 @@
md5_uint32 total[2];
md5_uint32 buflen;
- char buffer[128];
+ union
+ {
+ char buffer[128];
+ md5_uint32 buffer32[32];
+ };
};
/*
Index: ChangeLog
===
--- ChangeLog (revision 1330)
+++ ChangeLog (working copy)
@@ -1,3 +1,9 @@
+2012-05-29 Neil Williams li...@codehelp.co.uk
+
+ * Apply patch by Ulrich Drepper drep...@gmail.com
+ to use anonymous union instead of type punning in
+ md5.c|h to avoid compiler error with strict aliasing.
+
2012-03-25 Neil Williams li...@codehelp.co.uk
* Reimplement the deprecated GCache which is due for
pgp1Ts9RmzwHP.pgp
Description: PGP signature
Bug#668793: openshot: Update package to support new version of melt/python-mlt5
severity 668793 pending
thanks
Cyril Brulebois k...@debian.org (28/05/2012):
Fixing this package is needed to get the sox transition done. If
somebody fancies an NMU, that would make most welcome.
Just uploaded, with the attached source debdiff.
Mraw,
KiBi.
diff -Nru openshot-1.4.2/debian/changelog openshot-1.4.2/debian/changelog
--- openshot-1.4.2/debian/changelog 2012-02-01 06:46:39.0 +0100
+++ openshot-1.4.2/debian/changelog 2012-05-29 10:51:59.0 +0200
@@ -1,3 +1,15 @@
+openshot (1.4.2-1.1) unstable; urgency=high
+
+ [ Cyril Brulebois ]
+ * Non-maintainer upload.
+ * Apply Antonio's patch, thanks!
+ * Set urgency to “high”, for the RC bug fix, needed for the sox/mlt transition.
+
+ [ Antonio Ospite ]
+ * Add an optional dependency on python-mlt5. (Closes: #668793)
+
+ -- Cyril Brulebois k...@debian.org Tue, 29 May 2012 10:51:20 +0200
+
openshot (1.4.2-1) unstable; urgency=low
* New upstream release to address bug fixes and regressions from 1.4.1
diff -Nru openshot-1.4.2/debian/control openshot-1.4.2/debian/control
--- openshot-1.4.2/debian/control 2012-02-01 06:45:30.0 +0100
+++ openshot-1.4.2/debian/control 2012-05-29 10:49:21.0 +0200
@@ -19,7 +19,7 @@
python-gtk2,
python-httplib2,
python-imaging,
- python-mlt3 | python-mlt2,
+ python-mlt5 | python-mlt3 | python-mlt2,
python-pygoocanvas,
python-xdg,
${misc:Depends},
signature.asc
Description: Digital signature
Bug#674715: marked as done (CVE-2012-2653: initgroups() adds gid 0 to the group list)
Your message dated Tue, 29 May 2012 09:02:28 + with message-id e1szijw-0002uy...@franck.debian.org and subject line Bug#674715: fixed in arpwatch 2.1a15-1.2 has caused the Debian Bug report #674715, regarding CVE-2012-2653: initgroups() adds gid 0 to the group list 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.) -- 674715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: arpwatch Version: 2.1a15-1.1 Severity: critical Tags: security Justification: root security hole Hi, as reported on oss-sec (http://www.openwall.com/lists/oss-security/2012/05/24/12) the patch added to arpwatch to drop privileges in fact adds the gid 0 (root) group to the group list. This has been allocated CVE-2012-2653. Can you prepare updates fixing this (using pw-pw_gid in the call) or should the security team do it? Regards, -- Yves-Alexis -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-grsec-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: arpwatch Source-Version: 2.1a15-1.2 We believe that the bug you reported is fixed in the latest version of arpwatch, which is due to be installed in the Debian FTP archive: arpwatch_2.1a15-1.2.diff.gz to main/a/arpwatch/arpwatch_2.1a15-1.2.diff.gz arpwatch_2.1a15-1.2.dsc to main/a/arpwatch/arpwatch_2.1a15-1.2.dsc arpwatch_2.1a15-1.2_amd64.deb to main/a/arpwatch/arpwatch_2.1a15-1.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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yves-Alexis Perez cor...@debian.org (supplier of updated arpwatch 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: Sun, 27 May 2012 09:20:52 +0200 Source: arpwatch Binary: arpwatch Architecture: source amd64 Version: 2.1a15-1.2 Distribution: unstable Urgency: high Maintainer: KELEMEN Péter f...@debian.org Changed-By: Yves-Alexis Perez cor...@debian.org Description: arpwatch - Ethernet/FDDI station activity monitor Closes: 674715 Changes: arpwatch (2.1a15-1.2) unstable; urgency=high . * Non-maintainer upload by the Security Team. * Fix initgroups() adding the gid 0 group to the list. Instead of dropping privileges it was in fact adding it. This is CVE-2012-2653. closes: #674715 * debian/rules: - enable hardening flags. * Makefile.in: add LDFLAGS support. Checksums-Sha1: a99f51eb621a0dbcb1d0a7b36cfa650c52b50d0d 1714 arpwatch_2.1a15-1.2.dsc 81b57ead3e4a3d4a8c10678109dfe8e4c03c7a02 147856 arpwatch_2.1a15-1.2.diff.gz 24ba4127de1801e3d24523babb7064e06c11c7dc 193364 arpwatch_2.1a15-1.2_amd64.deb Checksums-Sha256: 9785e1f5ecbde302e8683cbc339aa04d452d3cbf20bd35bd06ed7fff9150ff78 1714 arpwatch_2.1a15-1.2.dsc 43fa24105594e0886aaa571d3ca2cc6a5c07d540b0b134d2b5923c688cc2a8f6 147856 arpwatch_2.1a15-1.2.diff.gz 8965e768c5de971c58335c9508b0cdbb24714a9c72fa4757d569aa4f21571a79 193364 arpwatch_2.1a15-1.2_amd64.deb Files: 628e8c1445bc87dac730fe74c344e246 1714 admin optional arpwatch_2.1a15-1.2.dsc ea6ac9531289f04219349d0faca7cde5 147856 admin optional arpwatch_2.1a15-1.2.diff.gz 5459c8eba786e6ae3edaa3dcad3f977f 193364 admin optional arpwatch_2.1a15-1.2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJPweTIAAoJEDBVD3hx7wuoEAQQAIGGJEehD1DabbFnH7HAPFXm 7dYsIQqAFEHnNdu4zvSaAiqpRJqnrhL/fClmp2+jkj1W1UrTG008ypNHV+9VI+mP JejBSfKtcyVdvXCi1uUs5IzYGkczNN4Bk4/JrdXOLE+DHcJYpDgxA+8VHdvAk2jH vE3/bpfqtctwWOuk0gHeh62YpVe8+pLDDSzr+uMTUvqtbIbiQmo6CzHSFi4Th9WR 3MKJPoPW5OfqT9c0Y0p4rFj9giTO+kbmQFwyU3jE7laSVlJUzftmNcvG/5TDPZv3 iAIGREMrzwoh4acGM7mEt2NAg3KenMyhgA8wRuhbfbI0J9tbV6s777HCUQL5mPk5 hR4IaXroAuGyejfzjRAbt6TDA4XKNxEc97N1Qvy6m6yIMC0h0tROaK7Q44Vm+V18 Vt1gC4HpfKamqlOwXE9t6eJGnOqNc+V2CWJV8DGsPGbboqnmQ/IZ0o5OCqkKuu7C CdtiY8ffKDMLrqWh7UKEwjx6afoNp4ZGXigkn4hHf57i692hFxK4pVCNlv7GBag+ t2omyX9I/+yS2tlLk5jNPHBtG660HHP9lKSgHwEKpzgySRZYbHtmj/iR9o0ryr7i
Bug#672021: uploaded NMU
Marcin, just uploaded the NMU, to get in the archive before the feature freeze, as the libpqxx4 upload didn't happen. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Processed (with 1 errors): Re: Bug#668793: openshot: Update package to support new version of melt/python-mlt5
Processing commands for cont...@bugs.debian.org: tag 668793 pending Bug #668793 [openshot] openshot: Update package to support new version of melt/python-mlt5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 668793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668793 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#673622: marked as done (givaro: causes FTBFS for linbox with GCC 4.7)
Your message dated Tue, 29 May 2012 09:05:52 +
with message-id e1szine-0002k6...@franck.debian.org
and subject line Bug#673622: fixed in givaro 3.2.13-1.3
has caused the Debian Bug report #673622,
regarding givaro: causes FTBFS for linbox with GCC 4.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
673622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libgivaro-dev
Version: 3.2.13-1.2
Severity: serious
Tags: upstream
givaro's includes are causing errors for linbox when building with GCC 4.7
(Bug#667264) -- patch attached:
[...]
../../linbox/field/givaro-gfq.h:137:25: required from here
/usr/include/givaro/givpoly1proot.inl:289:15: error: 'degree' was not declared
in this scope, and no declarations were found by argument-dependent lookup at
the point of instantiation [-fpermissive]
/usr/include/givaro/givpoly1proot.inl:289:15: note: declarations in dependent
base 'Poly1DomGFqDomint, Dense' are not found by unqualified lookup
/usr/include/givaro/givpoly1proot.inl:289:15: note: use 'this-degree' instead
[...]
../../linbox/ring/givaro-polynomial.h:164:68: required from here
/usr/include/givaro/givpoly1factor.inl:168:16: error: 'degree' was not declared
in this scope, and no declarations were found by argument-dependent lookup at
the point of instantiation [-fpermissive]
/usr/include/givaro/givpoly1factor.inl:168:16: note: declarations in dependent
base 'Poly1DomLinBox::Modulardouble, Dense' are not found by unqualified
lookup
/usr/include/givaro/givpoly1factor.inl:168:16: note: use 'this-degree' instead
[...]
../../linbox/field/givaro-gfq.h:100:75: required from here
/usr/include/givaro/givintnumtheo.inl:405:5: error: 'isleq' was not declared in
this scope, and no declarations were found by argument-dependent lookup at the
point of instantiation [-fpermissive]
/usr/include/givaro/givintnumtheo.inl:405:5: note: declarations in dependent
base 'IntegerDom' are not found by unqualified lookup
/usr/include/givaro/givintnumtheo.inl:405:5: note: use 'this-isleq' instead
[...]
Thanks,
Matej
--- givaro-3.2.13~/src/kernel/integer/givintnumtheo.inl
+++ givaro-3.2.13/src/kernel/integer/givintnumtheo.inl
@@ -17,8 +17,8 @@
// === //
templateclass RandIter
typename IntNumTheoDomRandIter::Rep IntNumTheoDomRandIter::phi(Rep res,
const Rep n) const {
-if (isleq(n,1)) return res=n;
-if (isleq(n,3)) return sub(res,n,this-one);
+if (this-isleq(n,1)) return res=n;
+if (this-isleq(n,3)) return this-sub(res,n,this-one);
std::listRep Lf;
Father_t::set(Lf,n);
//return phi (res,Lf,n);
@@ -29,11 +29,11 @@
templateclass RandIter
template templateclass, class class Container, templateclass class Alloc
typename IntNumTheoDomRandIter::Rep IntNumTheoDomRandIter::phi(Rep res,
const ContainerRep, AllocRep Lf, const Rep n) const {
-if (isleq(n,1)) return res=n;
-if (isleq(n,3)) return sub(res,n,this-one);
+if (this-isleq(n,1)) return res=n;
+if (this-isleq(n,3)) return this-sub(res,n,this-one);
res = n; Rep t,m;
for(typename ContainerRep, AllocRep ::const_iterator f=Lf.begin();
f!=Lf.end(); ++f)
-mul(res, divexact(t,res,*f), sub(m, *f, this-one));
+this-mul(res, this-divexact(t,res,*f), this-sub(m, *f, this-one));
return res;
}
@@ -402,8 +402,8 @@
typename IntNumTheoDomRandIter::Rep
IntNumTheoDomRandIter::lowest_prim_root(Rep A, const Rep n) const {
// n must be in {2,4,p^m,2p^m} where p is an odd prime
// else returns zero
-if (isleq(n,4)) return sub(A,n,this-one);
-if (isZero(mod(A,n,4))) return A=this-zero;
+if (this-isleq(n,4)) return this-sub(A,n,this-one);
+if (isZero(this-mod(A,n,4))) return A=this-zero;
Rep phin, tmp;
phi(phin,n);
std::listRep Lf;
@@ -412,15 +412,15 @@
for(f=Lf.begin();f!=Lf.end();++f)
this-div(*f,phin,*f);
int found=0;
-for(A = 2;(isleq(A,n) (! found));addin(A,1)) {
+for(A = 2;(this-isleq(A,n) (! found));this-addin(A,1)) {
if (isOne(gcd(tmp,A,n))) {
found = 1;
for(f=Lf.begin();(f!=Lf.end() found);f++)
found = (! isOne( this-powmod(tmp,A,*f,n)) );
}
}
-if (isleq(A,n))
-return subin(A,1);
+if (this-isleq(A,n))
+return this-subin(A,1);
else
return A=this-zero;
}
--- givaro-3.2.13~/src/library/poly1/givpoly1factor.inl
+++ givaro-3.2.13/src/library/poly1/givpoly1factor.inl
Bug#674990: exim breaks (again?) with TLS packet with unexpected length
Hi Marc, I have found various suggestions, like adding the Debian-exim user to the group shadow, Where is this dangerous suggestion written? Will search for it again. How many CAs do you have enabled to trust? First all as shipped with debian, then I removed all and restarted exim, same effect and same error. I checked with gnutls-cli (or so) that no certificate is loaded. Is there a way to verify what certificates are loaded by exim? Norbert -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674990: exim breaks (again?) with TLS packet with unexpected length
On Tue, May 29, 2012 at 05:59:04PM +0900, Norbert Preining wrote: How many CAs do you have enabled to trust? First all as shipped with debian, then I removed all and restarted exim, same effect and same error. Interesting. Generally, Gnutls will error out with the TLS packet with unexpected length as a quite generic case. I checked with gnutls-cli (or so) that no certificate is loaded. Is there a way to verify what certificates are loaded by exim? Not that I am aware of, but Andreas is very much more fluent in GnuTLS. In exim 4.80, the GnuTLS code was greatly overhauled, so I guess that upstream would be less than willing to invest time into the old GnuTLS code. Can you give a transcript of a gnutls-cli session from your server to the smarthost, if you wish in private mail to andreas and me. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667251: marked as done (libofx: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 09:13:22 + with message-id e1sziuu-0004e9...@franck.debian.org and subject line Bug#667251: fixed in libofx 1:0.9.4-2.1 has caused the Debian Bug report #667251, regarding libofx: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libofx Version: 1:0.9.4-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. ofxpartner.cpp:198:26: error: 'unlink' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/libofx_1:0.9.4-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] ---End Message--- ---BeginMessage--- Source: libofx Source-Version: 1:0.9.4-2.1 We believe that the bug you reported is fixed in the latest version of libofx, which is due to be installed in the Debian FTP archive: libofx-dev_0.9.4-2.1_amd64.deb to main/libo/libofx/libofx-dev_0.9.4-2.1_amd64.deb libofx-doc_0.9.4-2.1_all.deb to main/libo/libofx/libofx-doc_0.9.4-2.1_all.deb libofx4-dbg_0.9.4-2.1_amd64.deb to main/libo/libofx/libofx4-dbg_0.9.4-2.1_amd64.deb libofx4_0.9.4-2.1_amd64.deb to main/libo/libofx/libofx4_0.9.4-2.1_amd64.deb libofx_0.9.4-2.1.debian.tar.gz to main/libo/libofx/libofx_0.9.4-2.1.debian.tar.gz libofx_0.9.4-2.1.dsc to main/libo/libofx/libofx_0.9.4-2.1.dsc ofx_0.9.4-2.1_amd64.deb to main/libo/libofx/ofx_0.9.4-2.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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated libofx 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, 17 Apr 2012 08:08:44 +0200 Source: libofx Binary: libofx4 libofx-dev libofx4-dbg libofx-doc ofx Architecture: source amd64 all Version: 1:0.9.4-2.1 Distribution: unstable Urgency: low Maintainer: Bryan Donlan bdon...@gmail.com Changed-By: Matthias Klose d...@debian.org Description: libofx-dev - development package for libofx4 libofx-doc - documentation for libofx4 libofx4- library to support the Open Financial Exchange format libofx4-dbg - debugging symbols for libofx4 ofx- Open Financial Exchange programs Closes: 667251 Changes: libofx (1:0.9.4-2.1) unstable; urgency=low . * Non maintainer upload. * Fix build failure with GCC 4.7. Closes: #667251. Checksums-Sha1: e62c18f29f0c57c7145f8a237378ac07c91711c8 1450 libofx_0.9.4-2.1.dsc 6421d82618349020b152ac8683f10a52cd464cdb 14038 libofx_0.9.4-2.1.debian.tar.gz f53ead5937a5f33addcddd8024fee369b0cb3bc9 188110 libofx4_0.9.4-2.1_amd64.deb 9652ae5ca814efe0ede3499f8f3dea33f84a039b 157036 libofx-dev_0.9.4-2.1_amd64.deb e8c3e932eeadee53dc79b1959415027dd74994de 664848 libofx4-dbg_0.9.4-2.1_amd64.deb 96322c84a5defc0013246a7b9fb737f1840ab11b 697588 libofx-doc_0.9.4-2.1_all.deb babc78069fb877a296176113819b4bbeb2d8f718 64718 ofx_0.9.4-2.1_amd64.deb Checksums-Sha256: 701ab981dad06083b39d3624d2d91026e36c6449ed5014bc5a95232e72539000 1450 libofx_0.9.4-2.1.dsc ed81dbbca495e08120b17a35d5b056ff967fdda46fa4284680b85e11688703a0 14038 libofx_0.9.4-2.1.debian.tar.gz 2ff7dd106443293ed9adc684a8c3183dba63aaa1bd294755d72f9d005c1b24cb 188110 libofx4_0.9.4-2.1_amd64.deb 845f3bdda176f47c0dfe8331a96d8ea4c5af0452710a134d59a11be397d91ebb 157036 libofx-dev_0.9.4-2.1_amd64.deb 725a67b1cfdeeffc8111f869c075c544d0beb3a907a1711632edbb59aec875fe 664848 libofx4-dbg_0.9.4-2.1_amd64.deb 4cc3f83f9e77bd30b9194caf660bf44310a0c2102f06a4633c8fb74df34502a3 697588 libofx-doc_0.9.4-2.1_all.deb
Bug#667264: marked as done (linbox: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 09:13:37 + with message-id e1sziuj-0004fy...@franck.debian.org and subject line Bug#667264: fixed in linbox 1.1.6~rc0-4.2 has caused the Debian Bug report #667264, regarding linbox: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linbox Version: 1.1.6~rc0-4.1 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. givpoly1proot.inl:289:15: error: 'degree' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/linbox_1.1.6~rc0-4.1_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] linbox-sage.C:617:39: required from here ../../linbox/matrix/matrix-domain.h:821:36: error: 'mulColDense' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] ../../linbox/matrix/matrix-domain.h:821:36: note: declarations in dependent base 'LinBox::MVProductDomainLinBox::GivaroExtensionLinBox::Modularunsigned int ' are not found by unqualified lookup ../../linbox/matrix/matrix-domain.h:821:36: note: use 'this-mulColDense' instead ../../linbox/matrix/matrix-domain.h: In instantiation of 'Vector1 LinBox::MatrixDomainField::mulColSpecialized(Vector1, const Matrix, const Vector2, LinBox::VectorCategories::DenseVectorTag, LinBox::VectorCategories::DenseVectorTag) const [with Vector1 = std::vectorint; Matrix = LinBox::TransposeMatrixLinBox::SparseMatrixLinBox::GivaroGfq, std::vectorstd::pairlong unsigned int, int, std::allocatorstd::pairlong unsigned int, int , LinBox::MatrixCategories::RowMatrixTag; Vector2 = std::vectorint; Field = LinBox::GivaroGfq]': ../../linbox/matrix/matrix-domain.h:861:59: required from 'Vector1 LinBox::MatrixDomainField::mulSpecialized(Vector1, const Matrix, const Vector2, LinBox::MatrixCategories::ColMatrixTag) const [with Vector1 = std::vectorint; Matrix = LinBox::TransposeMatrixLinBox::SparseMatrixLinBox::GivaroGfq, std::vectorstd::pairlong unsigned int, int, std::allocatorstd::pairlong unsigned int, int , LinBox::MatrixCategories::RowMatrixTag; Vector2 = std::vectorint; Field = LinBox::GivaroGfq]' ../../linbox/matrix/matrix-domain.h:404:85: required from 'Vector1 LinBox::MatrixDomainField::vectorMul(Vector1, const Matrix, const Vector2) const [with Vector1 = std::vectorint; Matrix = LinBox::TransposeMatrixLinBox::SparseMatrixLinBox::GivaroGfq, std::vectorstd::pairlong unsigned int, int, std::allocatorstd::pairlong unsigned int, int , LinBox::MatrixCategories::RowMatrixTag; Vector2 = std::vectorint; Field = LinBox::GivaroGfq]' ../../linbox/blackbox/sparse.h:182:34: required from 'OutVector LinBox::SparseMatrix_Field, _Row::applyTranspose(OutVector, const InVector) const [with OutVector = std::vectorint; InVector = std::vectorint; _Field = LinBox::GivaroGfq; _Row = std::vectorstd::pairlong unsigned int, int, std::allocatorstd::pairlong unsigned int, int ]' ../../linbox/blackbox/transpose.h:103:21: required from 'Vector1 LinBox::TransposeBlackbox::apply(Vector1, const Vector2) const [with Vector1 = std::vectorint; Vector2 = std::vectorint; Blackbox = LinBox::SparseMatrixLinBox::GivaroGfq, std::vectorstd::pairlong unsigned int, int, std::allocatorstd::pairlong unsigned int, int ]' ../../linbox/blackbox/compose.h:127:5: required from 'OutVector LinBox::Compose_Blackbox1, _Blackbox2::apply(OutVector, const InVector) const [with OutVector = std::vectorint; InVector = std::vectorint; _Blackbox1 = LinBox::DiagonalLinBox::GivaroGfq, LinBox::VectorCategories::DenseVectorTag; _Blackbox2 = LinBox::TransposeLinBox::SparseMatrixLinBox::GivaroGfq, std::vectorstd::pairlong unsigned int, int, std::allocatorstd::pairlong unsigned int, int]' ../../linbox/blackbox/compose.h:128:5: [ skipping
Bug#667267: marked as done (madlib: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 09:13:50 + with message-id e1sziuw-0004io...@franck.debian.org and subject line Bug#667267: fixed in madlib 1.3.0-2.1 has caused the Debian Bug report #667267, regarding madlib: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: madlib Version: 1.3.0-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. MAdResourceManager.cc:108:31: error: '_SC_PAGE_SIZE' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/madlib_1.3.0-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] command-line:0:0: note: this is the location of the previous definition libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I../Geo -I../Mesh -I../Common -I../Adapt -I../Adapt/constraint -I../Adapt/operator -I../Adapt/output -I../Adapt/quality -I../Adapt/repositioning -I../Adapt/sizeField -I../Adapt/utils -I../Contrib/ANN/include/ANN -I../Contrib/ANN/src -I../Contrib/mathex -I. -I./../Contrib/mathex -D_FORTIFY_SOURCE=2 -D_HAVE_ANN_ -D_HAVE_MATHEX_ -D_HAVE_BLAS_ -DHAVE_BLAS -D_HAVE_LAPACK_ -DHAVE_LAPACK -DHAVE_64BIT_SIZE_T -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -D_FORTIFY_SOURCE=0 -ansi -c MAdStringFieldEvaluator.cc -o MAdStringFieldEvaluator.o /dev/null 21 /bin/bash ../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I../Geo -I../Mesh -I../Common -I../Adapt -I../Adapt/constraint -I../Adapt/operator -I../Adapt/output -I../Adapt/quality -I../Adapt/repositioning -I../Adapt/sizeField -I../Adapt/utils -I../Contrib/ANN/include/ANN -I../Contrib/ANN/src -I../Contrib/mathex -I. -I./../Contrib/mathex -D_FORTIFY_SOURCE=2 -D_HAVE_ANN_ -D_HAVE_MATHEX_ -D_HAVE_BLAS_ -DHAVE_BLAS -D_HAVE_LAPACK_ -DHAVE_LAPACK -DHAVE_64BIT_SIZE_T -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -D_FORTIFY_SOURCE=0 -ansi -c -o MAdMessage.lo MAdMessage.cc libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I../Geo -I../Mesh -I../Common -I../Adapt -I../Adapt/constraint -I../Adapt/operator -I../Adapt/output -I../Adapt/quality -I../Adapt/repositioning -I../Adapt/sizeField -I../Adapt/utils -I../Contrib/ANN/include/ANN -I../Contrib/ANN/src -I../Contrib/mathex -I. -I./../Contrib/mathex -D_FORTIFY_SOURCE=2 -D_HAVE_ANN_ -D_HAVE_MATHEX_ -D_HAVE_BLAS_ -DHAVE_BLAS -D_HAVE_LAPACK_ -DHAVE_LAPACK -DHAVE_64BIT_SIZE_T -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -D_FORTIFY_SOURCE=0 -ansi -c MAdMessage.cc -fPIC -DPIC -o .libs/MAdMessage.o command-line:0:0: warning: _FORTIFY_SOURCE redefined [enabled by default] command-line:0:0: note: this is the location of the previous definition libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I../Geo -I../Mesh -I../Common -I../Adapt -I../Adapt/constraint -I../Adapt/operator -I../Adapt/output -I../Adapt/quality -I../Adapt/repositioning -I../Adapt/sizeField -I../Adapt/utils -I../Contrib/ANN/include/ANN -I../Contrib/ANN/src -I../Contrib/mathex -I. -I./../Contrib/mathex -D_FORTIFY_SOURCE=2 -D_HAVE_ANN_ -D_HAVE_MATHEX_ -D_HAVE_BLAS_ -DHAVE_BLAS -D_HAVE_LAPACK_ -DHAVE_LAPACK -DHAVE_64BIT_SIZE_T -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -D_FORTIFY_SOURCE=0 -ansi -c MAdMessage.cc -o MAdMessage.o /dev/null 21 /bin/bash ../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I../Geo -I../Mesh -I../Common -I../Adapt -I../Adapt/constraint -I../Adapt/operator -I../Adapt/output -I../Adapt/quality -I../Adapt/repositioning -I../Adapt/sizeField -I../Adapt/utils
Bug#667316: marked as done (openvpn-auth-ldap: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 09:15:08 + with message-id e1sziwc-0004d5...@franck.debian.org and subject line Bug#667316: fixed in openvpn-auth-ldap 2.0.3-2.1 has caused the Debian Bug report #667316, regarding openvpn-auth-ldap: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: openvpn-auth-ldap Version: 2.0.3-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. configure: error: Could not locate a working Objective-C runtime. The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/openvpn-auth-ldap_2.0.3-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no configure: WARNING: pf(4) table support will not be included. checking for BSD pf(4) support... no checking for strlcpy... no checking for openldap... yes configure: WARNING: Check library not found. Unit tests will not be built or run. checking for check unit test library... no checking for openvpn-plugin.h... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking how to run the Objective C preprocessor... gcc -E checking objc/objc.h usability... yes checking objc/objc.h presence... yes checking for objc/objc.h... yes checking if linking libobjc requires pthreads... no configure: error: Could not locate a working Objective-C runtime. See `config.log' for more details. checking for GNU Objective C runtime... no make: *** [config.status] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: openvpn-auth-ldap Source-Version: 2.0.3-2.1 We believe that the bug you reported is fixed in the latest version of openvpn-auth-ldap, which is due to be installed in the Debian FTP archive: openvpn-auth-ldap_2.0.3-2.1.debian.tar.gz to main/o/openvpn-auth-ldap/openvpn-auth-ldap_2.0.3-2.1.debian.tar.gz openvpn-auth-ldap_2.0.3-2.1.dsc to main/o/openvpn-auth-ldap/openvpn-auth-ldap_2.0.3-2.1.dsc openvpn-auth-ldap_2.0.3-2.1_amd64.deb to main/o/openvpn-auth-ldap/openvpn-auth-ldap_2.0.3-2.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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated openvpn-auth-ldap 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, 29 May 2012 08:06:47 + Source: openvpn-auth-ldap Binary: openvpn-auth-ldap Architecture: source amd64 Version: 2.0.3-2.1 Distribution: unstable Urgency: low Maintainer: Alberto Gonzalez Iniesta a...@inittab.org Changed-By: Matthias Klose d...@debian.org Description: openvpn-auth-ldap - OpenVPN LDAP authentication module Closes: 667316 Changes: openvpn-auth-ldap (2.0.3-2.1) unstable; urgency=low . * Non maintainer upload. * Fix build failure with GCC 4.7 (Matej Vela). Closes: #667316. Checksums-Sha1: bfa6045f4d6e80cce2ec9df8387d78e95649b5ba 1225 openvpn-auth-ldap_2.0.3-2.1.dsc 6f58de85540f5e2ad9c4660dea0b17682349468d 5047 openvpn-auth-ldap_2.0.3-2.1.debian.tar.gz 80eb0a4d8b42fd05fcbd688a4e4993430edb528a 46678 openvpn-auth-ldap_2.0.3-2.1_amd64.deb
Bug#667383: marked as done (stopmotion: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 09:16:07 + with message-id e1szix9-0004vr...@franck.debian.org and subject line Bug#667383: fixed in stopmotion 0.6.2+git.1.10d2ea43-1.1 has caused the Debian Bug report #667383, regarding stopmotion: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: stopmotion Version: 0.6.2+git.1.10d2ea43-1 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. src/presentation/frontends/qtfrontend/mainwindowgui.cpp:1145:21: error: 'R_OK' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/stopmotion_0.6.2+git.1.10d2ea43-1_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] debian/rules override_dh_auto_build make[1]: Entering directory `/«BUILDDIR»/stopmotion-0.6.2+git.1.10d2ea43' dh_auto_build -- LIBS='-lSDL -lxml2 -lSDL_image -ltar -lvorbisfile -linotifytools -lQtGui -lQtCore -lpthread -lX11 -lm' make[2]: Entering directory `/«BUILDDIR»/stopmotion-0.6.2+git.1.10d2ea43' /usr/bin/uic-qt4 src/presentation/frontends/qtfrontend/helpbrowser.ui -o ui_helpbrowser.h /usr/bin/uic-qt4 src/presentation/frontends/qtfrontend/toolsmenu.ui -o ui_toolsmenu.h g++ -c -m64 -pipe -O2 -w -D_REENTRANT -DNO_DEBUG -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -Isrc -Isrc/presentation/frontends/qtfrontend -Isrc/presentation/frontends/nonguifrontend -Isrc/foundation -Isrc/domain -Isrc/domain/animation -Isrc/presentation -I/usr/include/SDL -I-D_GNU_SOURCE=1 -I-D_REENTRANT -I/usr/include/libxml2 -I. -I. -o config.o src/config.cpp g++ -c -m64 -pipe -O2 -w -D_REENTRANT -DNO_DEBUG -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -Isrc -Isrc/presentation/frontends/qtfrontend -Isrc/presentation/frontends/nonguifrontend -Isrc/foundation -Isrc/domain -Isrc/domain/animation -Isrc/presentation -I/usr/include/SDL -I-D_GNU_SOURCE=1 -I-D_REENTRANT -I/usr/include/libxml2 -I. -I. -o main.o src/main.cpp g++ -c -m64 -pipe -O2 -w -D_REENTRANT -DNO_DEBUG -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -Isrc -Isrc/presentation/frontends/qtfrontend -Isrc/presentation/frontends/nonguifrontend -Isrc/foundation -Isrc/domain -Isrc/domain/animation -Isrc/presentation -I/usr/include/SDL -I-D_GNU_SOURCE=1 -I-D_REENTRANT -I/usr/include/libxml2 -I. -I. -o domainfacade.o src/domain/domainfacade.cpp g++ -c -m64 -pipe -O2 -w -D_REENTRANT -DNO_DEBUG -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -Isrc -Isrc/presentation/frontends/qtfrontend -Isrc/presentation/frontends/nonguifrontend -Isrc/foundation -Isrc/domain -Isrc/domain/animation -Isrc/presentation -I/usr/include/SDL -I-D_GNU_SOURCE=1 -I-D_REENTRANT -I/usr/include/libxml2 -I. -I. -o logger.o src/foundation/logger.cpp g++ -c -m64 -pipe -O2 -w -D_REENTRANT -DNO_DEBUG -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -Isrc -Isrc/presentation/frontends/qtfrontend -Isrc/presentation/frontends/nonguifrontend -Isrc/foundation -Isrc/domain -Isrc/domain/animation -Isrc/presentation -I/usr/include/SDL -I-D_GNU_SOURCE=1 -I-D_REENTRANT -I/usr/include/libxml2 -I. -I. -o animation.o src/domain/animation/animation.cpp g++ -c -m64 -pipe -O2 -w -D_REENTRANT -DNO_DEBUG -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui
Bug#667425: marked as done (xshisen: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 09:16:49 + with message-id e1szixp-00055h...@franck.debian.org and subject line Bug#667425: fixed in xshisen 1:1.51-3.3 has caused the Debian Bug report #667425, regarding xshisen: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xshisen Version: 1:1.51-3.2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. body.C:43:32: error: capture of non-variable 'Body::xsize' The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/xshisen_1:1.51-3.2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] ---End Message--- ---BeginMessage--- Source: xshisen Source-Version: 1:1.51-3.3 We believe that the bug you reported is fixed in the latest version of xshisen, which is due to be installed in the Debian FTP archive: xshisen_1.51-3.3.debian.tar.gz to main/x/xshisen/xshisen_1.51-3.3.debian.tar.gz xshisen_1.51-3.3.dsc to main/x/xshisen/xshisen_1.51-3.3.dsc xshisen_1.51-3.3_amd64.deb to main/x/xshisen/xshisen_1.51-3.3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated xshisen 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, 29 May 2012 16:39:18 +0800 Source: xshisen Binary: xshisen Architecture: source amd64 Version: 1:1.51-3.3 Distribution: unstable Urgency: low Maintainer: Zak B. Elep zak...@spunge.org Changed-By: Matthias Klose d...@debian.org Description: xshisen- Shisen-sho puzzle game for X11 Closes: 667425 Changes: xshisen (1:1.51-3.3) unstable; urgency=low . * Non-maintainer upload. * Fix FTBFS with gcc 4.7 by using “this-foo” where needed (Cyril Brulebois). Closes: #667425. Checksums-Sha1: 6b374046177d7187acfda50ea3a4bfcd4414d3bd 1179 xshisen_1.51-3.3.dsc c036214b23c04d33782f64d4e03dbbcd67387093 63394 xshisen_1.51-3.3.debian.tar.gz 10dc79d62cf348dacf6b1c1510c1ae9d48243afa 66236 xshisen_1.51-3.3_amd64.deb Checksums-Sha256: a4d799a94827a17ebd69daac5ab9bd3b52830a2818e92784e60145f05fc9b45c 1179 xshisen_1.51-3.3.dsc 91c6b1e2a832d3ce32e6fed5b975fcda538243ec3ea8fa21ee1119a0c3ca8e93 63394 xshisen_1.51-3.3.debian.tar.gz 0e11b0051927bf48de9474d7ca425cf02ac541debe8c920332c74fe50db01d99 66236 xshisen_1.51-3.3_amd64.deb Files: b5a6eddd2d2144bc029f902a05e8e58d 1179 games optional xshisen_1.51-3.3.dsc abcd506230671e0be90cb3391ce9611f 63394 games optional xshisen_1.51-3.3.debian.tar.gz 1d2c433d1c3703beeedd59c9bee8e802 66236 games optional xshisen_1.51-3.3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/EjDkACgkQStlRaw+TLJw9OwCeN1QkXizSQHvRV70E1ELUoFiZ GGAAoLcv9UvwaDHg4v0pS0v1Cje3ngvG =g3A/ -END PGP SIGNATURE- ---End Message---
Bug#675005: src:xshisen: maintainer address bounces
Package: xshisen Version: 1:1.51-3.2 Severity: serious The maintainer address for xshisen bounces: Mail Delivery System mailer-dae...@franck.debian.org writes: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: zak...@spunge.org SMTP error from remote mail server after RCPT TO:zak...@spunge.org: host aspmx.l.google.com [173.194.76.27]: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 gx8si14084869qab.44 -- This is a copy of the message, including all the headers. -- Return-path: envel...@ftp-master.debian.org Received: from dak by franck.debian.org with local (Exim 4.72) (envelope-from envel...@ftp-master.debian.org) id 1SZIXp-00055V-PC; Tue, 29 May 2012 09:16:49 + Date: Tue, 29 May 2012 09:16:49 + Message-Id: e1szixp-00055v...@franck.debian.org From: Debian FTP Masters ftpmas...@ftp-master.debian.org To: Matthias Klose d...@debian.org, zak...@spunge.org (Zak B. Elep) X-DAK: dak process-upload X-Debian: DAK X-Debian-Package: xshisen Precedence: bulk MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: xshisen_1.51-3.3_amd64.changes ACCEPTED into unstable Sender: Archive Administrator d...@franck.debian.org Accepted: xshisen_1.51-3.3.debian.tar.gz to main/x/xshisen/xshisen_1.51-3.3.debian.tar.gz xshisen_1.51-3.3.dsc to main/x/xshisen/xshisen_1.51-3.3.dsc xshisen_1.51-3.3_amd64.deb to main/x/xshisen/xshisen_1.51-3.3_amd64.deb Changes: xshisen (1:1.51-3.3) unstable; urgency=low . * Non-maintainer upload. * Fix FTBFS with gcc 4.7 by using “this-foo” where needed (Cyril Brulebois). Closes: #667425. Override entries for your package: xshisen_1.51-3.3.dsc - source games xshisen_1.51-3.3_amd64.deb - optional games Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 667425 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674000: python-pyopencl-headers: fails to upgrade from 'testing' - trying to overwrite /usr/include/pyopencl/pyopencl-ranluxcl.cl
On 2012-05-27 21:06, Tomasz Rybak wrote:
Should I put
Breaks/Replaces: python-pyopencl ( 2011.2.2+git20120508-1)
or
Breaks/Replaces: python-pyopencl ( ${source:Version})?
Policy 7.6 uses hard-coded version, but many packages put
${source:Version} into debian/control. What is advised?
A hardcoded version would be advised because there was a change once in
the past, but any version afterwards is not affected by this.
source:Version is used for other purposes (usually for Relationships
with arch:all packages that don't have a matching binary:Version (at
least after an NMU).
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed upstream
Processing commands for cont...@bugs.debian.org: tag 672085 + fixed-upstream Bug #672085 [src:qof] qof: FTBFS: md5.c:119:2: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] Added tag(s) fixed-upstream. quit Stopping processing here. Please contact me if you need assistance. -- 672085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672085 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#671995: marked as done (compiz: FTBFS: window.cpp:1603:43: error: 'gethostname' was not declared in this scope)
Your message dated Tue, 29 May 2012 09:32:14 + with message-id e1szimk-0001fd...@franck.debian.org and subject line Bug#671995: fixed in compiz 0.8.4-5.2 has caused the Debian Bug report #671995, regarding compiz: FTBFS: window.cpp:1603:43: error: 'gethostname' was not declared in this scope to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 671995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: compiz Version: 0.8.4-5.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../include -DQT_SHARED -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/-g -O2 -Wall -D_FORTIFY_SOURCE=2 -MT window.o -MD -MP -MF .deps/window.Tpo -c -o window.o window.cpp; \ then mv -f .deps/window.Tpo .deps/window.Po; else rm -f .deps/window.Tpo; exit 1; fi window.cpp: In member function 'void KWD::Window::updateWindowGeometry()': window.cpp:1162:17: warning: variable 'w' set but not used [-Wunused-but-set-variable] window.cpp:1162:20: warning: variable 'h' set but not used [-Wunused-but-set-variable] window.cpp: In member function 'void KWD::Window::showKillProcessDialog(Time)': window.cpp:1603:43: error: 'gethostname' was not declared in this scope make[4]: *** [window.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/compiz_0.8.4-5.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: compiz Source-Version: 0.8.4-5.2 We believe that the bug you reported is fixed in the latest version of compiz, which is due to be installed in the Debian FTP archive: compiz-core_0.8.4-5.2_amd64.deb to main/c/compiz/compiz-core_0.8.4-5.2_amd64.deb compiz-dev_0.8.4-5.2_amd64.deb to main/c/compiz/compiz-dev_0.8.4-5.2_amd64.deb compiz-gtk_0.8.4-5.2_amd64.deb to main/c/compiz/compiz-gtk_0.8.4-5.2_amd64.deb compiz-kde_0.8.4-5.2_amd64.deb to main/c/compiz/compiz-kde_0.8.4-5.2_amd64.deb compiz-plugins_0.8.4-5.2_amd64.deb to main/c/compiz/compiz-plugins_0.8.4-5.2_amd64.deb compiz_0.8.4-5.2.diff.gz to main/c/compiz/compiz_0.8.4-5.2.diff.gz compiz_0.8.4-5.2.dsc to main/c/compiz/compiz_0.8.4-5.2.dsc compiz_0.8.4-5.2_all.deb to main/c/compiz/compiz_0.8.4-5.2_all.deb libdecoration0-dev_0.8.4-5.2_amd64.deb to main/c/compiz/libdecoration0-dev_0.8.4-5.2_amd64.deb libdecoration0_0.8.4-5.2_amd64.deb to main/c/compiz/libdecoration0_0.8.4-5.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 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated compiz 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, 29 May 2012 08:51:01 + Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all amd64 Version: 0.8.4-5.2 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Matthias Klose d...@debian.org Description: compiz - OpenGL window and compositing manager compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window
Bug#672032: marked as done (debtags: FTBFS: debtags.cc:319:23: error: 'unlink' was not declared in this scope)
Your message dated Tue, 29 May 2012 09:32:30 + with message-id e1szin0-0001iu...@franck.debian.org and subject line Bug#672032: fixed in debtags 1.9.1 has caused the Debian Bug report #672032, regarding debtags: FTBFS: debtags.cc:319:23: error: 'unlink' was not declared in this scope to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 672032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: debtags Version: 1.9 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/tagcoll-2.0.13 -I/usr/include/tagcoll-2.0.13 -DSCRIPTDIR=\/usr/share/debtags\ -DBINDIR=\/usr/bin\-g -O2 -c -o debtags.o debtags.cc debtags.cc: In destructor 'AtomicStdioWriter::~AtomicStdioWriter()': debtags.cc:319:23: error: 'unlink' was not declared in this scope debtags.cc:319:23: note: suggested alternative: In file included from debtags.cc:49:0: /usr/include/wibble/sys/fs.h:64:6: note: 'wibble::sys::fs::unlink' debtags.cc: In member function 'void AtomicStdioWriter::flush()': debtags.cc:340:15: error: 'fdatasync' was not declared in this scope debtags.cc: In function 'int main(int, const char**)': debtags.cc:702:30: error: 'X_OK' was not declared in this scope make[4]: *** [debtags.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/debtags_1.9_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: debtags Source-Version: 1.9.1 We believe that the bug you reported is fixed in the latest version of debtags, which is due to be installed in the Debian FTP archive: debtags_1.9.1.dsc to main/d/debtags/debtags_1.9.1.dsc debtags_1.9.1.tar.gz to main/d/debtags/debtags_1.9.1.tar.gz debtags_1.9.1_amd64.deb to main/d/debtags/debtags_1.9.1_amd64.deb python-debtagshw_1.9.1_all.deb to main/d/debtags/python-debtagshw_1.9.1_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 672...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated debtags 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, 09 May 2012 22:22:40 + Source: debtags Binary: debtags python-debtagshw Architecture: source amd64 all Version: 1.9.1 Distribution: unstable Urgency: high Maintainer: Enrico Zini enr...@debian.org Changed-By: Matthias Klose d...@debian.org Description: debtags- Enables support for package tags python-debtagshw - Match debtags hardware:: tags against the actual hardware Closes: 672032 Changes: debtags (1.9.1) unstable; urgency=high . * Non maintainer upload. * Fix build failure with GCC 4.7. Closes: #672032. Checksums-Sha1: bdd2d170145afe967350eae9ceafabeb1d922031 1215 debtags_1.9.1.dsc a3fbe799376a78e62e14460744738adb737dad11 916643 debtags_1.9.1.tar.gz d01ffa60319571c8785d7a6749ce795664606e37 644352 debtags_1.9.1_amd64.deb b5ebed0e6d785f78b3641c8a8b4cba7cd8591b56 17934 python-debtagshw_1.9.1_all.deb Checksums-Sha256: 7375179a3642662369d9c2d07cdf4bd929d0cca6bf03e31936bc8eebd3c99957 1215 debtags_1.9.1.dsc c60d28fe1de6ce83258e3fc6553a5bd2cfce7c6e7384d2deea4e932448fe931a 916643 debtags_1.9.1.tar.gz a284ee852acd461a3d07826274075f8c3b095aa9874b6697ba82aa0caa3e3a4e 644352 debtags_1.9.1_amd64.deb 7347b4bc424b8bfe05cb73a1c13c920c355849181c8ce74808776f458a7b6dd2 17934 python-debtagshw_1.9.1_all.deb Files: 5d3ae71cf7ec785d2cd88ee15962f1c1 1215 admin optional debtags_1.9.1.dsc 9c424a82ceadd0126c23ab18bcf88369 916643 admin optional debtags_1.9.1.tar.gz 148ba2ecfc8a56a639cd9a7a264d8868 644352 admin optional debtags_1.9.1_amd64.deb
Bug#672021: marked as done (libpqxx3: FTBFS: ../include/pqxx/util.hxx:412:5: error: 'to_string' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point
Your message dated Tue, 29 May 2012 09:36:30 + with message-id e1sziqs-0002bx...@franck.debian.org and subject line Bug#672021: fixed in libpqxx3 3.1-1.1 has caused the Debian Bug report #672021, regarding libpqxx3: FTBFS: ../include/pqxx/util.hxx:412:5: error: 'to_string' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-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.) -- 672021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libpqxx3 Version: 3.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../include -I../include -I/usr/include/postgresql -c -o connection_base.lo connection_base.cxx libtool: compile: x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I../include -I../include -I/usr/include/postgresql -c connection_base.cxx -fPIC -DPIC -o .libs/connection_base.o In file included from ../include/pqxx/util:18:0, from ../include/pqxx/except.hxx:27, from ../include/pqxx/except:19, from ../include/pqxx/result.hxx:31, from ../include/pqxx/result:19, from ../include/pqxx/binarystring.hxx:26, from ../include/pqxx/binarystring:18, from connection_base.cxx:46: ../include/pqxx/util.hxx: In instantiation of 'std::string pqxx::separated_list(const string, ITER, ITER, ACCESS) [with ITER = __gnu_cxx::__normal_iteratorpqxx::prepare::internal::prepared_def::param*, std::vectorpqxx::prepare::internal::prepared_def::param ; ACCESS = pqxx::prepare::internal::get_sqltype; std::string = std::basic_stringchar]': connection_base.cxx:1018:35: required from here ../include/pqxx/util.hxx:412:5: error: 'to_string' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] In file included from ../include/pqxx/strconv:18:0, from ../include/pqxx/result.hxx:32, from ../include/pqxx/result:19, from ../include/pqxx/binarystring.hxx:26, from ../include/pqxx/binarystring:18, from connection_base.cxx:46: ../include/pqxx/strconv.hxx:239:22: note: 'std::string pqxx::to_string(const char*)' declared here, later in the translation unit In file included from ../include/pqxx/util:18:0, from ../include/pqxx/except.hxx:27, from ../include/pqxx/except:19, from ../include/pqxx/result.hxx:31, from ../include/pqxx/result:19, from ../include/pqxx/binarystring.hxx:26, from ../include/pqxx/binarystring:18, from connection_base.cxx:46: ../include/pqxx/util.hxx:416:7: error: 'to_string' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] In file included from ../include/pqxx/strconv:18:0, from ../include/pqxx/result.hxx:32, from ../include/pqxx/result:19, from ../include/pqxx/binarystring.hxx:26, from ../include/pqxx/binarystring:18, from connection_base.cxx:46: ../include/pqxx/strconv.hxx:239:22: note: 'std::string pqxx::to_string(const char*)' declared here, later in the translation unit make[2]: *** [connection_base.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/libpqxx3_3.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: libpqxx3 Source-Version: 3.1-1.1 We believe that the bug you reported is fixed in the latest version of libpqxx3, which is due to be installed in the Debian FTP archive: libpqxx-3.1-dbg_3.1-1.1_amd64.deb to main/libp/libpqxx3/libpqxx-3.1-dbg_3.1-1.1_amd64.deb
Bug#668793: marked as done (openshot: Update package to support new version of melt/python-mlt5)
Your message dated Tue, 29 May 2012 09:38:52 + with message-id e1szita-00038v...@franck.debian.org and subject line Bug#668793: fixed in openshot 1.4.2-1.1 has caused the Debian Bug report #668793, regarding openshot: Update package to support new version of melt/python-mlt5 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.) -- 668793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: openshot Version: 1.4.2-1 Severity: normal Hi Jonathan, The melt packages were updated, which removes python-mlt3 and subsequently openshot: $ sudo apt-get dist-upgrade -Vs Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: libmlt4 (0.7.8-2) openshot (1.4.2-1) python-mlt3 (0.7.8-2) The following NEW packages will be installed: libmlt5 (0.7.8+git20120409-1) The following packages will be upgraded: libmlt++3 (0.7.8-2 = 0.7.8+git20120409-1) melt (0.7.8-2 = 0.7.8+git20120409-1) 2 upgraded, 1 newly installed, 3 to remove and 0 not upgraded. Remv openshot [1.4.2-1] Remv python-mlt3 [0.7.8-2] Inst melt [0.7.8-2] (0.7.8+git20120409-1 Debian:unstable [i386]) [] Inst libmlt++3 [0.7.8-2] (0.7.8+git20120409-1 Debian:unstable [i386]) [] Remv libmlt4 [0.7.8-2] [] Inst libmlt5 (0.7.8+git20120409-1 Debian:unstable [i386]) Conf libmlt5 (0.7.8+git20120409-1 Debian:unstable [i386]) Conf melt (0.7.8+git20120409-1 Debian:unstable [i386]) Conf libmlt++3 (0.7.8+git20120409-1 Debian:unstable [i386]) Thanks! -- Kind regards, Michael -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'testing'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openshot depends on: ii fontconfig 2.8.0-3.1 ii gtk2-engines-pixbuf 2.24.10-1 ii librsvg2-common 2.36.0-5 ii melt none ii python 2.7.2-10 ii python-gtk2 2.24.0-3 ii python-httplib2 0.7.4-1 ii python-imaging 1.1.7-4 ii python-mlt3 0.7.8-2 ii python-pygoocanvas 0.14.1-1+b3 ii python-support 1.0.14 ii python-xdg 0.19-4 Versions of packages openshot recommends: ii frei0r-plugins 1.1.22git20091109-1.2 ii openshot-doc1.4.2-1 Versions of packages openshot suggests: ii blender none ii inkscape 0.48.3.1-1+b1 -- no debconf information ---End Message--- ---BeginMessage--- Source: openshot Source-Version: 1.4.2-1.1 We believe that the bug you reported is fixed in the latest version of openshot, which is due to be installed in the Debian FTP archive: openshot-doc_1.4.2-1.1_all.deb to main/o/openshot/openshot-doc_1.4.2-1.1_all.deb openshot_1.4.2-1.1.debian.tar.gz to main/o/openshot/openshot_1.4.2-1.1.debian.tar.gz openshot_1.4.2-1.1.dsc to main/o/openshot/openshot_1.4.2-1.1.dsc openshot_1.4.2-1.1_all.deb to main/o/openshot/openshot_1.4.2-1.1_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 668...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois k...@debian.org (supplier of updated openshot 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, 29 May 2012 10:51:20 +0200 Source: openshot Binary: openshot openshot-doc Architecture: source all Version: 1.4.2-1.1 Distribution: unstable Urgency: high Maintainer: Jonathan Thomas jonathan.oo...@gmail.com Changed-By: Cyril Brulebois k...@debian.org Description: openshot - Create and edit videos and movies openshot-doc - Help manual for OpenShot Video Editor Closes: 668793 Changes: openshot (1.4.2-1.1) unstable; urgency=high . [ Cyril Brulebois ] * Non-maintainer upload. * Apply Antonio's patch, thanks! * Set urgency to “high”, for the RC bug fix, needed for the sox/mlt transition. . [ Antonio Ospite ] * Add an optional dependency on python-mlt5. (Closes: #668793) Checksums-Sha1: 383f34521d7c45523e39f3e4365ed1409c40a5ab 1287
Bug#674970: marked as done (sugar-toolkit-gtk3: FTBFS: missing pygtk-codegen-2.0 from python-gtk2-dev)
Your message dated Tue, 29 May 2012 09:39:45 + with message-id e1sziu1-0003nl...@franck.debian.org and subject line Bug#674970: fixed in sugar-toolkit-gtk3 0.96.1-2 has caused the Debian Bug report #674970, regarding sugar-toolkit-gtk3: FTBFS: missing pygtk-codegen-2.0 from python-gtk2-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 674970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sugar-toolkit-gtk3 Version: 0.96.1-1 Severity: serious Justification: fails to build from source Builds of sugar-toolkit-gtk3 in minimal environments (such as on the autobuilders) have been failing due to missing pygtk-codegen-2.0, which comes from the python-gtk2-dev package. Could you please declare a build dependency on it and check with pbuilder or the like that no others are missing? Thanks! ---End Message--- ---BeginMessage--- Source: sugar-toolkit-gtk3 Source-Version: 0.96.1-2 We believe that the bug you reported is fixed in the latest version of sugar-toolkit-gtk3, which is due to be installed in the Debian FTP archive: gir1.2-sugarext-1.0_0.96.1-2_amd64.deb to main/s/sugar-toolkit-gtk3/gir1.2-sugarext-1.0_0.96.1-2_amd64.deb libsugarext-data_0.96.1-2_all.deb to main/s/sugar-toolkit-gtk3/libsugarext-data_0.96.1-2_all.deb libsugarext-dbg_0.96.1-2_amd64.deb to main/s/sugar-toolkit-gtk3/libsugarext-dbg_0.96.1-2_amd64.deb libsugarext-dev_0.96.1-2_amd64.deb to main/s/sugar-toolkit-gtk3/libsugarext-dev_0.96.1-2_amd64.deb libsugarext0_0.96.1-2_amd64.deb to main/s/sugar-toolkit-gtk3/libsugarext0_0.96.1-2_amd64.deb python-sugar3_0.96.1-2_amd64.deb to main/s/sugar-toolkit-gtk3/python-sugar3_0.96.1-2_amd64.deb sugar-toolkit-gtk3_0.96.1-2.debian.tar.gz to main/s/sugar-toolkit-gtk3/sugar-toolkit-gtk3_0.96.1-2.debian.tar.gz sugar-toolkit-gtk3_0.96.1-2.dsc to main/s/sugar-toolkit-gtk3/sugar-toolkit-gtk3_0.96.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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard d...@jones.dk (supplier of updated sugar-toolkit-gtk3 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, 29 May 2012 10:47:01 +0200 Source: sugar-toolkit-gtk3 Binary: libsugarext0 libsugarext-data libsugarext-dev libsugarext-dbg python-sugar3 gir1.2-sugarext-1.0 Architecture: source all amd64 Version: 0.96.1-2 Distribution: unstable Urgency: low Maintainer: Debian OLPC debian-olpc-de...@lists.alioth.debian.org Changed-By: Jonas Smedegaard d...@jones.dk Description: gir1.2-sugarext-1.0 - GTK3-based Sugar toolkit - GObject introspection libsugarext-data - GTK3-based Sugar toolkit - common files libsugarext-dbg - GTK3-based Sugar toolkit - debugging symbols libsugarext-dev - GTK3-based Sugar toolkit - develelopment files libsugarext0 - GTK3-based Sugar toolkit - runtime library python-sugar3 - GTK3-based Sugar toolkit - Python bindings Closes: 674970 Changes: sugar-toolkit-gtk3 (0.96.1-2) unstable; urgency=low . * Update package relations: + Fix build-depend on python-gtk2-dev. Closes: bug#674970. Thanks to Aaron M. Ucko. + Fix have python-sugar3 depend on imported GIR bindings. + Build-depend on dh-buildinfo: Works with multiarch now. + Relax libsugarext0 to recommend (not depend on) libsugarext-data. * Improve libsugarext-data long description to clarify it contains translations. Checksums-Sha1: 4565ed54cd42860c01e729751c3618da79fc5e40 2598 sugar-toolkit-gtk3_0.96.1-2.dsc 6e26e913ca4ccd5a15e84b10edb7d354a5212935 12040 sugar-toolkit-gtk3_0.96.1-2.debian.tar.gz f358de96e513d1c7f74b376dfb6466017c966931 41466 libsugarext-data_0.96.1-2_all.deb 52746fb4645b0d7f3bf913eaf7af6e44d911ab60 51134 libsugarext0_0.96.1-2_amd64.deb aca76ca40b0e8a0191d4852705e93755d25483b2 15834 libsugarext-dev_0.96.1-2_amd64.deb 8e40a87a6e3aed2079324b3ec602340e00451f6f 235412 libsugarext-dbg_0.96.1-2_amd64.deb d998d48de3eb37920c8541122944fb9c3099a1d8 153306 python-sugar3_0.96.1-2_amd64.deb adcae9ce02e749f9e742ad7bc28c75c1a52ce1b0 13972 gir1.2-sugarext-1.0_0.96.1-2_amd64.deb Checksums-Sha256:
Bug#674990: exim breaks (again?) with TLS packet with unexpected length
On Di, 29 Mai 2012, Marc Haber wrote: I have found various suggestions, like adding the Debian-exim user to the group shadow, Where is this dangerous suggestion written? http://vk6hgr.echidna.id.au/blog/?p=184 Can you give a transcript of a gnutls-cli session from your server to the smarthost, if you wish in private mail to andreas and me. Actually, no, I realized that it didn't work out. Ok here is what I have: * swaks: $ swaks --tls --server smtp.jaist.ac.jp -p 587 --to prein...@logic.at === Trying smtp.jaist.ac.jp:587... === Connected to smtp.jaist.ac.jp. - 220 jaist.ac.jp ESMTP mail service ready - EHLO mithrandir - 250-mailrelayi.jaist.ac.jp - 250-8BITMIME - 250-SIZE 104857600 - 250-AUTH PLAIN LOGIN - 250-STARTTLS - 250 AUTH=PLAIN LOGIN - STARTTLS - 220 Go ahead Segmentation fault $ dmesg | tail -1 [ 4963.125646] swaks[21719]: segfault at 0 ip 7f0bfd596e10 sp 7fff363daa38 error 4 in libcrypto.so.1.0.0[7f0bfd46e000+1b7000] * openssl $ openssl s_client -connect smtp.jaist.ac.jp:587CONNECTED(0003) 140240510559912:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:766: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 320 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE --- $ * gnutls-cli $ gnutls-cli -s -p 587 smtp.jaist.ac.jp Processed 0 CA certificate(s). Resolving 'smtp.jaist.ac.jp'... Connecting to '150.65.19.12:587'... - Simple Client Mode: 220 jaist.ac.jp ESMTP mail service ready EHLO mithrandir (nothing ... pressing Ctrl-D) *** Starting TLS handshake (nothing ... until I Ctrl-C out) Does this help you? Anything else? (Sorry, no I don't speak SMTP protocol fluently) Norbert -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639400:
Hi, While an updated network-manager-strongswan 1.3 [1] for NM 0.9 is available for some time now, it has not been uploaded yet. Seems that my sponsor (the strongswan package maintainer) is rather busy. Maybe an other DD is willing to review and upload this package. Regards Martin [1]http://download.strongswan.org/NetworkManager/NetworkManager-strongswan-1.3.0.tar.gz network-manager-strongswan_1.3.0-1.dsc Description: PGP signature network-manager-strongswan_1.3.0-1.diff.gz Description: GNU Zip compressed data
Bug#674990: exim breaks (again?) with TLS packet with unexpected length
On Tue, May 29, 2012 at 06:45:52PM +0900, Norbert Preining wrote: On Di, 29 Mai 2012, Marc Haber wrote: I have found various suggestions, like adding the Debian-exim user to the group shadow, Where is this dangerous suggestion written? http://vk6hgr.echidna.id.au/blog/?p=184 The author of this blog entry has not read the documentation. Adding Debian-exim to the shadow group is the most insecure way to get authentication (as a server) to work. It has nothing to do with TLS at all. You might want to revert that change on your system as you are exposing all your password hashes to an attacker. * openssl $ openssl s_client -connect smtp.jaist.ac.jp:587CONNECTED(0003) That will not work. You need to use STARTTLS, -starttls smtp $ gnutls-cli -s -p 587 smtp.jaist.ac.jp Processed 0 CA certificate(s). Resolving 'smtp.jaist.ac.jp'... Connecting to '150.65.19.12:587'... - Simple Client Mode: 220 jaist.ac.jp ESMTP mail service ready EHLO mithrandir (nothing ... pressing Ctrl-D) The server stalls at this point before even switching to TLS. This is a problem of the remote side that I can see from here as well. You should report this to the operators of the server, it is broken. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 629952
Processing commands for cont...@bugs.debian.org: tags 629952 + squeeze Bug #629952 [subversion] subversion fails to build for stable(-security) on kfreebsd Ignoring request to alter tags of bug #629952 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 629952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629952 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#674349: marked as done (fwbuilder: FTBFS: ../fwbuilder/ThreadTools.h:168:5: error: 'ssize_t' does not name a type)
Your message dated Tue, 29 May 2012 10:03:24 + with message-id e1szjgu-0001ro...@franck.debian.org and subject line Bug#674349: fixed in fwbuilder 5.1.0-1.1 has caused the Debian Bug report #674349, regarding fwbuilder: FTBFS: ../fwbuilder/ThreadTools.h:168:5: error: 'ssize_t' does not name a type 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.) -- 674349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: fwbuilder Version: 5.1.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -c -m64 -pipe -g -D__STDC_FORMAT_MACROS -Wno-unused-parameter -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -fPIC -Wall -W -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I.. -I../.. -I/usr/include -I/usr/include/libxml2 -I../../../.. -o .obj/ThreadTools.o ThreadTools.cpp In file included from ThreadTools.cpp:31:0: ../fwbuilder/ThreadTools.h:168:5: error: 'ssize_t' does not name a type ThreadTools.cpp:182:82: error: no 'ssize_t libfwbuilder::TimeoutCounter::read(int, void*, size_t) const' member function declared in class 'libfwbuilder::TimeoutCounter' make[5]: *** [.obj/ThreadTools.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/fwbuilder_5.1.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on 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: fwbuilder Source-Version: 5.1.0-1.1 We believe that the bug you reported is fixed in the latest version of fwbuilder, which is due to be installed in the Debian FTP archive: fwbuilder-common_5.1.0-1.1_all.deb to main/f/fwbuilder/fwbuilder-common_5.1.0-1.1_all.deb fwbuilder-dbg_5.1.0-1.1_amd64.deb to main/f/fwbuilder/fwbuilder-dbg_5.1.0-1.1_amd64.deb fwbuilder-doc_5.1.0-1.1_all.deb to main/f/fwbuilder/fwbuilder-doc_5.1.0-1.1_all.deb fwbuilder_5.1.0-1.1.debian.tar.gz to main/f/fwbuilder/fwbuilder_5.1.0-1.1.debian.tar.gz fwbuilder_5.1.0-1.1.dsc to main/f/fwbuilder/fwbuilder_5.1.0-1.1.dsc fwbuilder_5.1.0-1.1_amd64.deb to main/f/fwbuilder/fwbuilder_5.1.0-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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated fwbuilder 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, 29 May 2012 09:23:33 + Source: fwbuilder Binary: fwbuilder fwbuilder-common fwbuilder-doc fwbuilder-dbg Architecture: source all amd64 Version: 5.1.0-1.1 Distribution: unstable Urgency: low Maintainer: Sylvestre Ledru sylves...@debian.org Changed-By: Matthias Klose d...@debian.org Description: fwbuilder - Firewall administration tool GUI fwbuilder-common - Firewall administration tool GUI (common files) fwbuilder-dbg - Firewall administration tool GUI (debugging symbols) fwbuilder-doc - Firewall administration tool GUI documentation Closes: 674349 Changes: fwbuilder (5.1.0-1.1) unstable; urgency=low . * Non maintainer upload * Fix build failure with GCC 4.7 (Ilya Barygin). Closes: #674349. Checksums-Sha1: 53a6a4e3e52efaec084f45679a21662c3c171465 1494 fwbuilder_5.1.0-1.1.dsc 9e13c4031b22c79da1b6189d7f4934f1cb084c7c 10235 fwbuilder_5.1.0-1.1.debian.tar.gz 89b7b693e901032a30e96b1307af7731599c6cf2 354374 fwbuilder-common_5.1.0-1.1_all.deb 1d3d32810ad9873a5f4f3f4e1059403899ec80a4 1076180 fwbuilder-doc_5.1.0-1.1_all.deb 186b49bc50263fe67672846c44c95e02a73dbcb9 12105988 fwbuilder_5.1.0-1.1_amd64.deb 1ad6d1042bd6de8485b302ab7d5499b125ea9a37 71153710 fwbuilder-dbg_5.1.0-1.1_amd64.deb Checksums-Sha256: ede7dc5f4886c674c9ed8a6b837aebd6a37d311b07e533a97a3eded913097e52 1494 fwbuilder_5.1.0-1.1.dsc
Bug#667265: marked as done (lmms: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 10:05:57 + with message-id e1szjjn-0001y0...@franck.debian.org and subject line Bug#667265: fixed in lmms 0.4.10-2.2 has caused the Debian Bug report #667265, regarding lmms: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lmms Version: 0.4.10-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. LocalZynAddSubFx.cpp:132:12: error: 'unlink' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/lmms_0.4.10-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] make[3]: Leaving directory `/«PKGBUILDDIR»' make[3]: Entering directory `/«PKGBUILDDIR»' [ 96%] Building CXX object plugins/zynaddsubfx/src/DSP/CMakeFiles/zynaddsubfx_dsp.dir/AnalogFilter.o [ 96%] Building CXX object plugins/zynaddsubfx/src/DSP/CMakeFiles/zynaddsubfx_dsp.dir/FFTwrapper.o [ 96%] Building CXX object plugins/zynaddsubfx/src/DSP/CMakeFiles/zynaddsubfx_dsp.dir/Filter.o [ 96%] Building CXX object plugins/zynaddsubfx/src/DSP/CMakeFiles/zynaddsubfx_dsp.dir/FormantFilter.o [ 96%] Building CXX object plugins/zynaddsubfx/src/DSP/CMakeFiles/zynaddsubfx_dsp.dir/SVFilter.o [ 96%] Building CXX object plugins/zynaddsubfx/src/DSP/CMakeFiles/zynaddsubfx_dsp.dir/Unison.o /«PKGBUILDDIR»/plugins/zynaddsubfx/src/DSP/Unison.cpp:74:2: warning: #warning : todo: if bandwidth is too small the audio will be self canceled (because of the sign change of the outputs) [-Wcpp] /«PKGBUILDDIR»/plugins/zynaddsubfx/src/DSP/Unison.cpp:102:2: warning: #warning todo: test if unison_amplitude_samples is to big and reallocate bigger memory [-Wcpp] /«PKGBUILDDIR»/plugins/zynaddsubfx/src/DSP/Unison.cpp:170:2: warning: #warning I will use relative amplitude, so the delay might be bigger than the whole buffer [-Wcpp] /«PKGBUILDDIR»/plugins/zynaddsubfx/src/DSP/Unison.cpp:172:2: warning: #warning I have to enlarge (reallocate) the buffer to make place for the whole delay [-Wcpp] Linking CXX static library libzynaddsubfx_dsp.a make[3]: Leaving directory `/«PKGBUILDDIR»' [ 96%] Built target zynaddsubfx_dsp make[3]: Entering directory `/«PKGBUILDDIR»' Scanning dependencies of target ZynAddSubFxCore make[3]: Leaving directory `/«PKGBUILDDIR»' make[3]: Entering directory `/«PKGBUILDDIR»' [ 96%] Building CXX object plugins/zynaddsubfx/CMakeFiles/ZynAddSubFxCore.dir/LocalZynAddSubFx.o /«PKGBUILDDIR»/plugins/zynaddsubfx/LocalZynAddSubFx.cpp: In member function 'void LocalZynAddSubFx::loadXML(const string)': /«PKGBUILDDIR»/plugins/zynaddsubfx/LocalZynAddSubFx.cpp:132:12: error: 'unlink' was not declared in this scope make[3]: *** [plugins/zynaddsubfx/CMakeFiles/ZynAddSubFxCore.dir/LocalZynAddSubFx.o] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: *** [plugins/zynaddsubfx/CMakeFiles/ZynAddSubFxCore.dir/all] Error 2 make[1]: *** [all] Error 2 make: *** [install] Error 2 make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: lmms Source-Version: 0.4.10-2.2 We believe that the bug you reported is fixed in the latest version of lmms, which is due to be installed in the Debian FTP archive: lmms-common_0.4.10-2.2_all.deb to main/l/lmms/lmms-common_0.4.10-2.2_all.deb lmms_0.4.10-2.2.debian.tar.gz to main/l/lmms/lmms_0.4.10-2.2.debian.tar.gz lmms_0.4.10-2.2.dsc to main/l/lmms/lmms_0.4.10-2.2.dsc lmms_0.4.10-2.2_amd64.deb to main/l/lmms/lmms_0.4.10-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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp.
Bug#673841: marked as done (sofa-framework: FTBFS with GCC-4.7)
Your message dated Tue, 29 May 2012 10:07:29 + with message-id e1szjkr-0002g1...@franck.debian.org and subject line Bug#673841: fixed in sofa-framework 1.0~beta4-6.1 has caused the Debian Bug report #673841, regarding sofa-framework: FTBFS with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 673841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sofa-framework Version: 1.0~beta4-6 Severity: serious Justification: FTBFS Hello, sofa-framework currently FTBFS in sid: componentmodel/behavior/MechanicalMapping.inl:91:3: error: 'apply' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] See attached full log. Samuel -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.4 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Thibault samuel.thiba...@fnac.net * y se leve dans 2h10 sofa-framework.log.gz Description: application/gunzip ---End Message--- ---BeginMessage--- Source: sofa-framework Source-Version: 1.0~beta4-6.1 We believe that the bug you reported is fixed in the latest version of sofa-framework, which is due to be installed in the Debian FTP archive: libsofa1-dev_1.0~beta4-6.1_amd64.deb to main/s/sofa-framework/libsofa1-dev_1.0~beta4-6.1_amd64.deb libsofa1_1.0~beta4-6.1_amd64.deb to main/s/sofa-framework/libsofa1_1.0~beta4-6.1_amd64.deb sofa-apps_1.0~beta4-6.1_amd64.deb to main/s/sofa-framework/sofa-apps_1.0~beta4-6.1_amd64.deb sofa-data_1.0~beta4-6.1_all.deb to main/s/sofa-framework/sofa-data_1.0~beta4-6.1_all.deb sofa-doc_1.0~beta4-6.1_all.deb to main/s/sofa-framework/sofa-doc_1.0~beta4-6.1_all.deb sofa-framework_1.0~beta4-6.1.debian.tar.gz to main/s/sofa-framework/sofa-framework_1.0~beta4-6.1.debian.tar.gz sofa-framework_1.0~beta4-6.1.dsc to main/s/sofa-framework/sofa-framework_1.0~beta4-6.1.dsc sofa-tutorials_1.0~beta4-6.1_all.deb to main/s/sofa-framework/sofa-tutorials_1.0~beta4-6.1_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 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated sofa-framework 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, 29 May 2012 09:18:41 + Source: sofa-framework Binary: sofa-apps libsofa1-dev libsofa1 sofa-tutorials sofa-data sofa-doc Architecture: source all amd64 Version: 1.0~beta4-6.1 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Matthias Klose d...@debian.org Description: libsofa1 - Simulation Open Framework Architecture - runtime libsofa1-dev - Simulation Open Framework Architecture - development sofa-apps - GUI for the Simulation Open Framework Architecture (SOFA) sofa-data - Simulation Open Framework Architecture - data sofa-doc - SOFA class reference documentation sofa-tutorials - Simulation Open Framework Architecture - tutorials Closes: 673841 Changes: sofa-framework (1.0~beta4-6.1) unstable; urgency=low . * Non maintainer upload. * Fix build failure with GCC 4.7 (Matej Vela). Closes: #673841. Checksums-Sha1: 272cc2734d7610f6ec84f0e9b24651158bc1612b 1990 sofa-framework_1.0~beta4-6.1.dsc b49efc4cff7f3b92efdda190058277cd5d483c42 18904 sofa-framework_1.0~beta4-6.1.debian.tar.gz 03af656ca31ff639134cd29eb1ef09a784fb0ec7 78368 sofa-tutorials_1.0~beta4-6.1_all.deb 7cf6b5910dec0e96eda580dd4943cffc54aae289 32420228 sofa-data_1.0~beta4-6.1_all.deb c7cfe21c108f83f5e5048cb664727c77bab07368 4964 sofa-doc_1.0~beta4-6.1_all.deb 9f1431aceae6f70d799f8ccae95a6d26f205b7bd 23270 sofa-apps_1.0~beta4-6.1_amd64.deb 0e9d2979e105c66017ae9fb0b04c756449b71e14 997528 libsofa1-dev_1.0~beta4-6.1_amd64.deb f68139df0a6e43825d198d6cfa5f7884ade486a6 9713998 libsofa1_1.0~beta4-6.1_amd64.deb Checksums-Sha256:
Processed: not upstream
Processing commands for cont...@bugs.debian.org: tags 674713 - upstream Bug #674713 [php5-suhosin] php5-suhosin no longer provides suhosin.so Removed tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 674713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674713 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#673198: marked as done (lintian: The 2.5.7 source package is missing files (causing FTBFS))
Your message dated Tue, 29 May 2012 10:22:31 +
with message-id e1szjzp-0005ab...@franck.debian.org
and subject line Bug#673198: fixed in lintian 2.5.8
has caused the Debian Bug report #673198,
regarding lintian: The 2.5.7 source package is missing files (causing FTBFS)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
673198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lintian
Version: 2.5.7
Severity: serious
Thanks to Luca Falavigna for spotting this.
The issue is that at least 3 files are missing[1] from the Lintian
source package, which cases a FTBFS (due to test failures). Most
likely this is caused by dpkg-source's @tar_ignore_default_pattern
which excludes .so files.
~Niels
[1] t/tests/apache2-modules-general/debian/{mod_baz.so,mod_foo2.so,mod_foo.so}
The files are empty files.
---End Message---
---BeginMessage---
Source: lintian
Source-Version: 2.5.8
We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive:
lintian_2.5.8.dsc
to main/l/lintian/lintian_2.5.8.dsc
lintian_2.5.8.tar.gz
to main/l/lintian/lintian_2.5.8.tar.gz
lintian_2.5.8_all.deb
to main/l/lintian/lintian_2.5.8_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 673...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Niels Thykier ni...@thykier.net (supplier of updated lintian 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, 29 May 2012 11:49:47 +0200
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.8
Distribution: unstable
Urgency: low
Maintainer: Debian Lintian Maintainers lintian-ma...@debian.org
Changed-By: Niels Thykier ni...@thykier.net
Description:
lintian- Debian package checker
Closes: 662134 667895 669911 671387 673106 673109 673112 673198 673352 673449
673451 673611 673613 673862
Changes:
lintian (2.5.8) unstable; urgency=low
.
Its like 2.5.7, only with less false positives and no FTBFS.
.
* checks/binaries{,.desc}:
+ [NT] Fix a too strict regex causing false-positives for
biarch packages. This was a regression introduced in
version 2.5.7. Thanks to Sven Joachim for reporting it.
(Closes: #673106)
+ [NT] Demote certainty of hardening-no-stackprotector to
wild-guess and move it to debian/extra-hardening profile.
+ [NT] Skip hardening-no-fortify-functions for binaries only
using the unprotected memcpy. This greatly reduces the
number of false positives for binaries compiled with
gcc-4.7 -O2 (or higher optimization). (Closes: #673112)
* checks/files:
+ [NT] Properly handle symlinks in icon directories. Thanks
to Nicholas Breen for the report and Felix Geyer for the
patches. (Closes: #673352)
+ [NT] Ignore wrong sizes on images in animations as it may
be a method to implement the animation. Thanks to Matthias
Klumpp for the report and Felix Geyer for the patch.
(Closes: #673862)
+ [NT] Ignore wrong icon sizes if the size difference is at
most 2px. Thanks to Felix Geyer for the patch.
* checks/scripts:
+ [NT] Refactor the %versioned_interpreters into a new
data file.
* checks/shared-libs:
+ [NT] Fix false positive dev-pkg-without-shlib-symlink
for shared libraries using libtool -release X.Y.
Thanks to Sven Joachim for the report. (Closes: #673109)
+ [NT] Fix false positive dev-pkg-without-shlib-symlink
for shared libraries installed in /lib. Lintian now
correctly expects the dev-symlink beneath /usr/lib.
Thanks to Guillem Jover for the report.
* checks/source-copyright:
+ [NT] Use the in-memory contents of the copyright file
instead of re-reading the file when parsing it as a
DEP-5 copyright file.
.
* collection/objdump-info{,.desc}:
+ [NT] Drop -D flag for readelf when looking for symbols.
This makes some checks more reliable in Ubuntu. Thanks
to Marc Deslauriers for the report and the patch.
(Closes: #673451)
.
*
Bug#675016: ifupdown: don't use PPP updetach option by default
Package: ifupdown Version: 0.7~rc3 Severity: critical Justification: breaks the whole system I have specified this bug as critical/breaks the whole system, because its effect is that if an external PPP link does not come up for some reason, the system boot fails. It actually gets wedged so hard that you cannot even boot into recovery mode to fix it; the problem can only be resolved with a rescue disk. This is completely unacceptable. According to the ifupdown package changelog, as of version 0.7~alpha4, ifup -a will use the updetach option for PPP interfaces. This may be an attempt to address the problem described in #127786, #287173, and #347594, wherein it is implied that other boot scripts which depend on the PPP link should be able to rely on it being up by the time they are run. This fails for two reasons. First, the termination of pppd updetach does not by any means guarantee that the PPP link is up, only that the attempt was made. It might have timed out and then failed, so other boot processes must be prepared to deal with that contingency anyway. Second, PPP links can go up and down depending on conditions on external WAN links and telephone lines, which are not in any way controllable by the local system or its human administrators. For maximum resiliency, it therefore makes sense to specify the PPP options persist maxfail 0 in /etc/network/interfaces, so that if the link does not come up on boot, or goes down later, the PPP daemon will keep retrying indefinitely until it does come up. Unfortunately, the combination of these options, a broken WAN link, and the updetach option now baked into the ifup binary result in an unbootable system, which cannot even be gotten into recovery mode. This is unacceptable. It is quite inappropriate for updetach to be hard-wired into a binary executable, where it can only be removed with a hex editor. However, the patch for #196877, where this change is made, provides another solution to the network dependency problem: Allow passing PPP options (presumably in /etc/network/interfaces). If anybody wishes to have the updetach behavior, let them specify it there, without forcing it on other installations where it is quite possibly fatal. Suggestion for further work on network dependencies at boot: perhaps this is better handled in a general way for any type of network interface, through hotplug or udev, or something like that? What happens if /etc/network/interfaces specifies auto eth0/iface eth0 inet dhcp, and the DHCP server is not responding for some reason? Does this also result in a boot failure? Is this not exactly analogous to the PPP situation described above? There seems to be some discussion of these issues in #245642. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.3 ii initscripts 2.88dsf-22.1 ii iproute 20120105-1 ii libc62.13-32 ii lsb-base 3.2-28 ifupdown recommends no packages. Versions of packages ifupdown suggests: pn isc-dhcp-client [dhcp-client] 4.2.2.dfsg.1-5 pn net-tools 1.60-23 pn ppp2.4.5-5.1 pn rdnssd none -- no debconf information -- debsums errors found: debsums: changed file /sbin/ifdown (from ifupdown package) debsums: changed file /sbin/ifquery (from ifupdown package) debsums: changed file /sbin/ifup (from ifupdown package) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675005: src:xshisen: maintainer address bounces
Hi! Ansgar Burchardt wrote: Package: xshisen Version: 1:1.51-3.2 Severity: serious The maintainer address for xshisen bounces: I made a new package updating my email address as well as acknowledging NMUs some months ago: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668148 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674389: marked as done (jenkins-memory-monitor: FTBFS: tests failed)
Your message dated Tue, 29 May 2012 10:50:34 +
with message-id e1szk0y-000364...@franck.debian.org
and subject line Bug#674389: fixed in jenkins-memory-monitor 1.7-2
has caused the Debian Bug report #674389,
regarding jenkins-memory-monitor: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
674389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: jenkins-memory-monitor
Version: 1.7-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120524 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
debian/rules build
test -x debian/rules
mkdir -p .
/usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian
mh_patchpoms -pjenkins-memory-monitor --debian-build --keep-pom-version
--maven-repo=/«PKGBUILDDIR»/debian/maven-repo
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to
check if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo package
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO]
[INFO] Building memory-monitor
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /«PKGBUILDDIR»/src/main/resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 7 source files to /«PKGBUILDDIR»/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /«PKGBUILDDIR»/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 1 source file to /«PKGBUILDDIR»/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /«PKGBUILDDIR»/target/surefire-reports
---
T E S T S
---
Running org.jvnet.hudson.MemoryMonitorTest
Memory:1603/3836MB Swap:407824/409565MB
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.272 sec
FAILURE!
Results :
Tests in error:
test2(org.jvnet.hudson.MemoryMonitorTest): 'top' unavailable
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
Please refer to /«PKGBUILDDIR»/target/surefire-reports for the individual
test results.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 5 seconds
[INFO] Finished at: Wed May 23 20:56:15 UTC 2012
[INFO] Final Memory: 14M/58M
[INFO]
make: *** [mvn-build] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/05/24/jenkins-memory-monitor_1.7-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
Bug#666586: marked as done (xmds-doc: FTBFS: ! Package hyperref Error: Wrong DVI mode driver option `hypertex',)
Your message dated Tue, 29 May 2012 11:11:43 + with message-id e1szkl1-0004w0...@franck.debian.org and subject line Bug#666586: fixed in xmds-doc 0~svn.1884-3.1 has caused the Debian Bug report #666586, regarding xmds-doc: FTBFS: ! Package hyperref Error: Wrong DVI mode driver option `hypertex', 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.) -- 666586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xmds-doc Version: 0~svn.1884-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120331 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/«PKGBUILDDIR»/latex/figures' epstopdf advectionMatlabPlot.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf advectionScilabPlot.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf classes.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf defferential.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf diffusionMatlabPlot.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf diffusionScilabPlot.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf fibre1.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf fibre2.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf funct.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf kubo1.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf kubo2.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf kuboTutorialMatlabPlot.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf kuboTutorialScilabPlot.eps Name main::opt_restricted used only once: possible typo at /usr/bin/epstopdf line 254. Name main::opt_version used only once: possible typo at /usr/bin/epstopdf line 288. Name main::opt_help used only once: possible typo at /usr/bin/epstopdf line 283. epstopdf
Bug#675022: Frequent lockups when using icedove (thunderbird)
Package: xserver-xorg-video-intel Version: 2:2.19.0-1 Severity: grave Since upgrading xserver-xorg-video-intel from 2:2.18.0-2 to 2:2.19.0-1 I get frequent lookups of X. So far this always happened when opening a large email folder in icedove(thunderbird). At this point the desktop is completely frozen and the system no longer reacts on keyboard input. I can still move the mouse, but X no longer reacts on clicks. This both happened in a composited DE (gnome-shell) and a non-composited DE (gnome-fallback/metacity). Downgrading to 2:2.18.0-2 reliably fixes the problem for me. My system is a X220 sandy bridge laptop, i.e a HD 3000 integrated graphics card. When the lockup happens I get a Xorg backtrace in Xorg.0.log (attached) As this particular error happened several times a day and I had to hard-reset my laptop, I'm filing with RC severity. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Nov 11 2011 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2044664 May 20 10:59 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 Kernel version (/proc/version): --- Linux version 3.2.0-2-amd64 (Debian 3.2.18-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon May 21 17:45:41 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 42647 May 20 23:56 /var/log/Xorg.1.log -rw-r--r-- 1 root root 56472 May 29 12:04 /var/log/Xorg.0.log udev information: - P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME=Power Button E: PHYS=LNXPWRBN/button/input0 E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: UDEV_LOG=3 E: USEC_INITIALIZED=12086995 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4 N: input/event4 E: BACKSPACE=guess E: DEVNAME=/dev/input/event4 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4 E: DMI_VENDOR=LENOVO E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: MAJOR=13 E: MINOR=68 E: SUBSYSTEM=input E: UDEV_LOG=3 E: USEC_INITIALIZED=12292596 E: XKBLAYOUT=de E: XKBMODEL=pc105 E: XKBVARIANT=nodeadkeys P: /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXVIDEO_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: KEY=3e000b 0 0 0 E: MODALIAS=input:b0019vp0006e-e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw E: NAME=Video Bus E: PHYS=LNXVIDEO/video/input0 E: PRODUCT=19/0/6/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: UDEV_LOG=3 E: USEC_INITIALIZED=14014544 P: /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11/event11 N: input/event11 E: BACKSPACE=guess E: DEVNAME=/dev/input/event11 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11/event11 E: DMI_VENDOR=LENOVO E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: MAJOR=13 E: MINOR=75 E: SUBSYSTEM=input E: UDEV_LOG=3 E: USEC_INITIALIZED=14017133 E: XKBLAYOUT=de E: XKBMODEL=pc105 E: XKBVARIANT=nodeadkeys P: /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2 E: EV=21 E: ID_FOR_SEAT=input-acpi-PNP0C0D_00 E: ID_INPUT=1 E: ID_PATH=acpi-PNP0C0D:00 E: ID_PATH_TAG=acpi-PNP0C0D_00 E: MODALIAS=input:b0019vp0005e-e0,5,kramlsfw0, E: NAME=Lid Switch E: PHYS=PNP0C0D/button/input0 E: PRODUCT=19/0/5/0 E: PROP=0 E: SUBSYSTEM=input E: SW=1 E: TAGS=:seat: E: UDEV_LOG=3 E: USEC_INITIALIZED=12084770 P: /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2/event2 N: input/event2 E: DEVNAME=/dev/input/event2 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2/event2 E: ID_INPUT=1 E: ID_PATH=acpi-PNP0C0D:00 E: ID_PATH_TAG=acpi-PNP0C0D_00 E: MAJOR=13 E: MINOR=66 E: SUBSYSTEM=input E: UDEV_LOG=3 E: USEC_INITIALIZED=12087029 P: /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 E: EV=3 E: ID_FOR_SEAT=input-acpi-PNP0C0E_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-PNP0C0E:00 E: ID_PATH_TAG=acpi-PNP0C0E_00 E: KEY=4000 0 0 E:
Processed: Re: Bug#675022: Acknowledgement (Frequent lockups when using icedove (thunderbird))
Processing commands for cont...@bugs.debian.org: forwarded 675022 https://bugs.freedesktop.org/show_bug.cgi?id=50455 Bug #675022 [xserver-xorg-video-intel] Frequent lockups when using icedove (thunderbird) Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=50455'. thanks Stopping processing here. Please contact me if you need assistance. -- 675022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675022 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#667111: marked as done (bcov: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 12:17:11 + with message-id e1szlmn-0001nu...@franck.debian.org and subject line Bug#667111: fixed in bcov 0.2-1.1 has caused the Debian Bug report #667111, regarding bcov: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bcov Version: 0.2-1 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. coverage.cpp:121:40: error: 'close' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/bcov_0.2-1_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking libdwarf.h usability... yes checking libdwarf.h presence... yes checking for libdwarf.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build -a make[1]: Entering directory `/«PKGBUILDDIR»' Making all in src make[2]: Entering directory `/«PKGBUILDDIR»/src' g++ -DPACKAGE_NAME=\bcov\ -DPACKAGE_TARNAME=\bcov\ -DPACKAGE_VERSION=\0.2\ -DPACKAGE_STRING=\bcov\ 0.2\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\bcov\ -DVERSION=\0.2\ -DHAVE_LIBELF=1 -DHAVE_LIBDWARF=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIBDWARF_H=1 -I. -g -O2 -c -o coverage.o coverage.cpp coverage.cpp: In function 'bool readDwarfLineNumbers(const string, std::mapstd::basic_stringchar, std::vectorstd::pairunsigned int, void* )': coverage.cpp:121:40: error: 'close' was not declared in this scope coverage.cpp:122:43: error: 'close' was not declared in this scope coverage.cpp:170:12: error: 'close' was not declared in this scope make[2]: *** [coverage.o] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/src' make[1]: *** [all-recursive] Error 1 dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: bcov Source-Version: 0.2-1.1 We believe that the bug you reported is fixed in the latest version of bcov, which is due to be installed in the Debian FTP archive: bcov_0.2-1.1.debian.tar.gz to main/b/bcov/bcov_0.2-1.1.debian.tar.gz bcov_0.2-1.1.dsc to main/b/bcov/bcov_0.2-1.1.dsc bcov_0.2-1.1_amd64.deb to main/b/bcov/bcov_0.2-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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated bcov 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: Sun, 27 May 2012 13:55:17 +0200 Source: bcov Binary: bcov Architecture: source amd64 Version: 0.2-1.1 Distribution: unstable Urgency: low Maintainer: Sebastian Dröge sl...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: bcov - Code coverage analysis tool Closes: 667111 Changes: bcov (0.2-1.1) unstable; urgency=low . * Non-maintainer upload. . [ Cyril Brulebois ] * Fix FTBFS with gcc 4.7 by fixing missing unistd.h includes (Closes: #667111). Checksums-Sha1: df621cf1ca304dd825e7f872adcded65de9b77d4 1684
Bug#667419: marked as done (xdiskusage: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 12:18:36 +
with message-id e1szlnk-0001rc...@franck.debian.org
and subject line Bug#667419: fixed in xdiskusage 1.48-10.1
has caused the Debian Bug report #667419,
regarding xdiskusage: ftbfs with GCC-4.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
667419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: xdiskusage
Version: 1.48-10
Severity: important
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.7
The package fails to build in a test rebuild on at least amd64 with
gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The
severity of this report may be raised before the wheezy release.
xdiskusage.C:408:6: error: redeclaration of 'int i'
The full build log can be found at:
http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/xdiskusage_1.48-10_unstable-gcc47.log
The last lines of the build log are at the end of this report.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
[...]
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for c++... c++
checking whether the C++ compiler (c++ ) works... yes
checking whether the C++ compiler (c++ ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether c++ accepts -g... yes
checking for a BSD compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for X... no
Ignoring libraries requested by configure.
updating cache ./config.cache
creating ./config.status
creating makeinclude
make[1]: Leaving directory `/«PKGBUILDDIR»'
make[1]: Entering directory `/«PKGBUILDDIR»'
c++ -Wall -O2 -c panels.C
c++ -Wall -O2 -c xdiskusage.C
xdiskusage.C: In static member function 'static OutputWindow*
OutputWindow::make(const char*, Disk*)':
xdiskusage.C:408:6: error: redeclaration of 'int i'
xdiskusage.C:406:16: error: 'int i' previously declared here
xdiskusage.C:508:71: warning: format '%d' expects argument of type 'int', but
argument 4 has type 'size_t {aka long unsigned int}' [-Wformat]
xdiskusage.C:526:75: warning: format '%d' expects argument of type 'int', but
argument 3 has type 'size_t {aka long unsigned int}' [-Wformat]
xdiskusage.C: In member function 'void OutputWindow::draw_tree(Node*, int, ull,
double, double)':
xdiskusage.C:715:32: warning: suggest parentheses around '' within '||'
[-Wparentheses]
make[1]: *** [xdiskusage.o] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
---End Message---
---BeginMessage---
Source: xdiskusage
Source-Version: 1.48-10.1
We believe that the bug you reported is fixed in the latest version of
xdiskusage, which is due to be installed in the Debian FTP archive:
xdiskusage_1.48-10.1.debian.tar.gz
to main/x/xdiskusage/xdiskusage_1.48-10.1.debian.tar.gz
xdiskusage_1.48-10.1.dsc
to main/x/xdiskusage/xdiskusage_1.48-10.1.dsc
xdiskusage_1.48-10.1_amd64.deb
to main/x/xdiskusage/xdiskusage_1.48-10.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 667...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated xdiskusage 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: Sun, 27 May 2012 14:01:23 +0200
Source: xdiskusage
Binary: xdiskusage
Architecture: source amd64
Version: 1.48-10.1
Distribution: unstable
Urgency: low
Maintainer: Thierry Randrianiriana randrianiri...@gmail.com
Changed-By: gregor herrmann gre...@debian.org
Description:
xdiskusage - Displays a graphic of your disk usage with du
Closes: 667419
Changes:
xdiskusage (1.48-10.1) unstable; urgency=low
.
* Non-maintainer upload.
.
[ Cyril Brulebois ]
* Fix FTBFS with gcc 4.7 by avoiding redeclared variable names in
nested scopes
Bug#667364: marked as done (rutilt: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 12:35:12 +
with message-id e1szldo-0002my...@franck.debian.org
and subject line Bug#667364: fixed in rutilt 0.16-2.2
has caused the Debian Bug report #667364,
regarding rutilt: ftbfs with GCC-4.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
667364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: rutilt
Version: 0.16-2.1
Severity: important
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.7
The package fails to build in a test rebuild on at least amd64 with
gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The
severity of this report may be raised before the wheezy release.
lib/src//UserData.cxx:72:53: error: '::getuid' has not been declared
The full build log can be found at:
http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/rutilt_0.16-2.1_unstable-gcc47.log
The last lines of the build log are at the end of this report.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
[...]
Kernel sources path set to : /usr
Using : -pipe -Wall -g -DNDEBUG -O3 as compilation options.
Labelling RutilT : 0.16-2.1
Generating Makefile constants... done
Generating program constants... done
Generating desktop launcher... done
Generating helper_launcher.sh... done
touch configure-stamp
dh_testdir
/usr/bin/make
make[1]: Entering directory `/«PKGBUILDDIR»'
Compiling lib/WE17Driver.o
Compiling lib/RTDrivers.o
lib/src//RTDrivers.cxx: In member function 'void
{anonymous}::CScanResult::ParseIE(const {anonymous}::CScanResult::SIE,
nsWireless::CEncryptionD) const':
lib/src//RTDrivers.cxx:203:79: warning: suggest parentheses around '' within
'||' [-Wparentheses]
lib/src//RTDrivers.cxx:260:75: warning: suggest parentheses around '' within
'||' [-Wparentheses]
Compiling lib/RutilT.o
Compiling lib/Parameters.o
lib/src//Parameters.cxx: In member function 'bool
nsWireless::CEncryptionD::operator==(const nsWireless::CEncryptionD) const':
lib/src//Parameters.cxx:361:76: warning: suggest parentheses around '' within
'||' [-Wparentheses]
lib/src//Parameters.cxx:363:79: warning: suggest parentheses around '' within
'||' [-Wparentheses]
Compiling lib/CWE17Module.o
Compiling lib/RTModules.o
Compiling lib/UserData.o
lib/src//UserData.cxx: In function 'std::string {anonymous}::GetHomeDir()':
lib/src//UserData.cxx:72:53: error: '::getuid' has not been declared
make[1]: *** [lib/UserData.o] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
---End Message---
---BeginMessage---
Source: rutilt
Source-Version: 0.16-2.2
We believe that the bug you reported is fixed in the latest version of
rutilt, which is due to be installed in the Debian FTP archive:
rutilt_0.16-2.2.diff.gz
to main/r/rutilt/rutilt_0.16-2.2.diff.gz
rutilt_0.16-2.2.dsc
to main/r/rutilt/rutilt_0.16-2.2.dsc
rutilt_0.16-2.2_amd64.deb
to main/r/rutilt/rutilt_0.16-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 667...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated rutilt 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: Sun, 27 May 2012 14:16:37 +0200
Source: rutilt
Binary: rutilt
Architecture: source amd64
Version: 0.16-2.2
Distribution: unstable
Urgency: low
Maintainer: Debian Ralink packages maintainers
pkg-ralink-maintain...@lists.alioth.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
rutilt - Configuration tool for rt2x00 wireless network cards
Closes: 667364
Changes:
rutilt (0.16-2.2) unstable; urgency=low
.
* Non-maintainer upload.
.
[ Cyril Brulebois ]
* Fix FTBFS with gcc 4.7 by fixing missing unistd.h include
(Closes: #667364).
Checksums-Sha1:
f7b02146b046955a4bc93b1cadbc2dcb63e95aa5 2067 rutilt_0.16-2.2.dsc
Bug#675016: ifupdown: don't use PPP updetach option by default
Hello, On Tue, 29 May 2012 03:28:46 -0700 Ian Bruce ian_br...@fastmail.net wrote: I have specified this bug as critical/breaks the whole system, because its effect is that if an external PPP link does not come up for some reason, the system boot fails. It actually gets wedged so hard that you cannot even boot into recovery mode to fix it; the problem can only be resolved with a rescue disk. This is completely unacceptable. I agree with many points of yours, but please explain how does it break the boot sequence. Networking initscript allows ifup to fail as far as I can see. How exactly does it break for you? -- WBR, Andrew signature.asc Description: PGP signature
Bug#667362: marked as done (rubberband: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 12:50:28 + with message-id e1szlsa-00039a...@franck.debian.org and subject line Bug#667362: fixed in rubberband 1.3-1.3 has caused the Debian Bug report #667362, regarding rubberband: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: rubberband Version: 1.3-1.2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. src/main.cpp:496:25: error: 'usleep' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/rubberband_1.3-1.2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] /usr/bin/make make[1]: Entering directory `/«PKGBUILDDIR»' x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/AudioCurve.o src/AudioCurve.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/ConstantAudioCurve.o src/ConstantAudioCurve.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/FFT.o src/FFT.cpp src/FFT.cpp: In destructor 'virtual RubberBand::FFTs::D_FFTW::~D_FFTW()': src/FFT.cpp:156:18: warning: variable 'save' set but not used [-Wunused-but-set-variable] x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/HighFrequencyAudioCurve.o src/HighFrequencyAudioCurve.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/PercussiveAudioCurve.o src/PercussiveAudioCurve.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/Profiler.o src/Profiler.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/Resampler.o src/Resampler.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/rubberband-c.o src/rubberband-c.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/RubberBandStretcher.o src/RubberBandStretcher.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/SilentAudioCurve.o src/SilentAudioCurve.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/SpectralDifferenceAudioCurve.o src/SpectralDifferenceAudioCurve.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/StretchCalculator.o src/StretchCalculator.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/StretcherImpl.o src/StretcherImpl.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/StretcherProcess.o src/StretcherProcess.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband -Isrc-c -o src/StretcherChannelData.o src/StretcherChannelData.cpp x86_64-linux-gnu-g++ -DHAVE_FFTW3 -DFFTW_DOUBLE_ONLY -DNO_THREAD_CHECKS -g -O2 -fPIC -Wall -Woverloaded-virtual -Irubberband
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 654643 important Bug #654643 [masqmail] masqmail: Silently discards mails when mbox exceeds 2 GiB Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 654643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654643 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#667329: marked as done (powertop: ftbfs with GCC-4.7)
Your message dated Tue, 29 May 2012 13:05:07 + with message-id e1szm6l-00049g...@franck.debian.org and subject line Bug#667329: fixed in powertop 1.97-2.1 has caused the Debian Bug report #667329, regarding powertop: ftbfs with GCC-4.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: powertop Version: 1.97-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. main.cpp:60:16: error: 'sleep' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/powertop_1.97-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] fakeroot debian/rules clean test -x debian/rules dh_testroot rm -f debian/stamp-makefile-build debian/stamp-makefile-install /usr/bin/make -C . -k clean make[1]: Entering directory `/«PKGBUILDDIR»' rm -f *.o *~ powertop DEADJOE core.* */*.o */*~ csstoh css.h make[1]: Leaving directory `/«PKGBUILDDIR»' dh_clean debian/rules build-arch test -x debian/rules mkdir -p . /usr/bin/make -C . make[1]: Entering directory `/«PKGBUILDDIR»' gcc -o csstoh csstoh.c ./csstoh powertop.css css.h CC lib.cpp CC main.cpp main.cpp: In function 'void do_sleep(int)': main.cpp:60:16: error: 'sleep' was not declared in this scope main.cpp:68:14: error: 'usleep' was not declared in this scope main.cpp: In function 'int main(int, char**)': main.cpp:169:15: error: 'getuid' was not declared in this scope main.cpp:176:57: warning: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result [-Wunused-result] main.cpp:177:47: warning: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result [-Wunused-result] main.cpp:178:76: warning: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result [-Wunused-result] make[1]: *** [main.o] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ---End Message--- ---BeginMessage--- Source: powertop Source-Version: 1.97-2.1 We believe that the bug you reported is fixed in the latest version of powertop, which is due to be installed in the Debian FTP archive: powertop_1.97-2.1.debian.tar.gz to main/p/powertop/powertop_1.97-2.1.debian.tar.gz powertop_1.97-2.1.dsc to main/p/powertop/powertop_1.97-2.1.dsc powertop_1.97-2.1_amd64.deb to main/p/powertop/powertop_1.97-2.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 667...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated powertop 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: Sun, 27 May 2012 14:34:09 +0200 Source: powertop Binary: powertop Architecture: source amd64 Version: 1.97-2.1 Distribution: unstable Urgency: low Maintainer: Patrick Winnertz win...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: powertop - Linux tool to find out what is using power on a laptop Closes: 667329 Changes: powertop (1.97-2.1) unstable; urgency=low . * Non-maintainer upload. . [ Cyril Brulebois ] * Fix FTBFS with gcc 4.7 by fixing missing unistd.h includes (Closes: #667329). Checksums-Sha1: eafafa563d1f995b378aa13a0e0d426efeedaf23 1830 powertop_1.97-2.1.dsc 4795f6fcaf34db2d208d530f1aa3fcf402e16e75 5967 powertop_1.97-2.1.debian.tar.gz e75cf220527996a74eb321936de277d95967d63c 128898 powertop_1.97-2.1_amd64.deb Checksums-Sha256:
Bug#635982: fix
although this bug is filed as fixed, to really work, cmake needs a file called wt-config.cmake in /usr/lib/wt/cmake; it's as easy as renaming /usr/lib/wt/cmake/FindWt.cmake to /usr/lib/wt/cmake/wt-config.cmake (adding a softlink worked for me) Regards, Rutger -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621460: Patch for NMU 1.6.17dfsg-3.1
subversion (1.6.17dfsg-3.1) unstable; urgency=low * Non-maintainer upload * Disable test-suite which was broken by apr 1.4.6 update (Closes: #669494) * Also rescue on Errno::EINVAL (Closes: #624810, #629952) * Split libsvn-java to libsvn-java and libsvn-jni (Closes: #670034) * Depend on generic libdb-dev and db-util (Closes: #621460) * Install java files prior to dh_install -i call -- Ondřej Surý ond...@debian.org Tue, 29 May 2012 13:59:11 +0200 The fix for #624810, #629952 should also apply to stable updates. The update will unfortunatelly be stalled in NEW queue due -java, -jni split. O. -- Ondřej Surý ond...@sury.org subversion_1.6.17dfsg-3.1.diff Description: Binary data
Bug#669560: marked as done (xfonts-kaname: FTBFS: gzip: knmzn12xbi.pcf: No such file or directory)
Your message dated Tue, 29 May 2012 13:36:38 + with message-id e1szmbg-0007ic...@franck.debian.org and subject line Bug#669560: fixed in xfonts-kaname 1.1-9.1 has caused the Debian Bug report #669560, regarding xfonts-kaname: FTBFS: gzip: knmzn12xbi.pcf: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 669560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xfonts-kaname Version: 1.1-9 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120419 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 configure the package. chmod +x debian/mkbold chmod +x debian/mkitalic touch configure-stamp dh_testdir # mkbold debian/mkbold -V kaname-latin1.bdf kaname-latin1b.bdf progress|0%| progress|8%\ progress|= 16%- progress|= 23%/ progress|== 31%| progress|=== 39%\ progress|=== 47%- progress|55%/ progress|62%| progress|= 70%\ progress|== 78%- progress|== 86%/ progress|=== 94%| # italic debian/mkitalic -V kaname-latin1.bdf kaname-latin1i.bdf debian/mkitalic -V kaname-latin1b.bdf kaname-latin1bi.bdf debian/mkitalic -V knm12p.bdf knm12pi.bdf debian/mkitalic -V knm12pb.bdf knm12pbi.bdf debian/mkitalic -V knmzn12x.bdf knmzn12xi.bdf debian/mkitalic -V knmzn12xb.bdf knmzn12xbi.bdf # make pcf files for FONT in kaname-latin1b.bdf kaname-latin1i.bdf kaname-latin1bi.bdf knm12pi.bdf knm12pbi.bdf knmzn12xi.bdf knmzn12xbi.bdf; do \ fontfile=`echo $FONT | sed -e 's/.bdf//'`; \ bdftopcf -o $fontfile.pcf $fontfile.bdf; \ gzip -9 $fontfile.pcf; \ done BDF Error on line 1: bad 'STARTFONT' bdftopcf: bdf input, kaname-latin1i.bdf, corrupt gzip: kaname-latin1i.pcf: No such file or directory BDF Error on line 1: bad 'STARTFONT' bdftopcf: bdf input, kaname-latin1bi.bdf, corrupt gzip: kaname-latin1bi.pcf: No such file or directory BDF Error on line 1: bad 'STARTFONT' bdftopcf: bdf input, knm12pi.bdf, corrupt gzip: knm12pi.pcf: No such file or directory BDF Error on line 1: bad 'STARTFONT' bdftopcf: bdf input, knm12pbi.bdf, corrupt gzip: knm12pbi.pcf: No such file or directory BDF Error on line 1: bad 'STARTFONT' bdftopcf: bdf input, knmzn12xi.bdf, corrupt gzip: knmzn12xi.pcf: No such file or directory BDF Error on line 1: bad 'STARTFONT' bdftopcf: bdf input, knmzn12xbi.bdf, corrupt gzip: knmzn12xbi.pcf: No such file or directory make: *** [build-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/04/19/xfonts-kaname_1.1-9_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: xfonts-kaname Source-Version: 1.1-9.1 We believe that the bug you reported is fixed in the latest version of xfonts-kaname, which is due to be installed in the Debian FTP archive: xfonts-kaname_1.1-9.1.diff.gz to main/x/xfonts-kaname/xfonts-kaname_1.1-9.1.diff.gz xfonts-kaname_1.1-9.1.dsc to main/x/xfonts-kaname/xfonts-kaname_1.1-9.1.dsc xfonts-kaname_1.1-9.1_all.deb to main/x/xfonts-kaname/xfonts-kaname_1.1-9.1_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
Bug#675016: ifupdown: don't use PPP updetach option by default
Hello, On Tue, 29 May 2012 06:34:59 -0700 ian_br...@fastmail.net wrote: pppd persist maxfail 0 updetach does not return until the PPP link comes up. If this does not happen for some reason, it never returns at all, and the boot sequence stops before any console is available, even in recovery mode. It's easy to reproduce the problem: enable the persist and maxfail 0 options, unplug the ethernet cable to the modem, and reboot. Simple solution: take the updetach out of the ifup binary, as it was until recently, and if necessary, put it in /etc/network/interfaces, since this is now allowed to specify arbitrary options. Okay, makes sense. Better solution: find some dependency mechanism with hotplug or udev that also works for DHCP or any other network configuration system. Not in the next month as freeze is soon. -- WBR, Andrew signature.asc Description: PGP signature
Bug#675016: ifupdown: don't use PPP updetach option by default
On Tue, 29 May 2012 14:47:58 +0200 Andrew Shadura bugzi...@tut.by wrote: I agree with many points of yours, but please explain how does it break the boot sequence. Networking initscript allows ifup to fail as far as I can see. How exactly does it break for you? pppd persist maxfail 0 updetach does not return until the PPP link comes up. If this does not happen for some reason, it never returns at all, and the boot sequence stops before any console is available, even in recovery mode. It's easy to reproduce the problem: enable the persist and maxfail 0 options, unplug the ethernet cable to the modem, and reboot. Simple solution: take the updetach out of the ifup binary, as it was until recently, and if necessary, put it in /etc/network/interfaces, since this is now allowed to specify arbitrary options. Better solution: find some dependency mechanism with hotplug or udev that also works for DHCP or any other network configuration system. There's no valid reason why the entire boot sequence should have to wait until some WAN interface comes up; anything that actually depends on that happening should find some other way of noticing it. -- Ian Bruce -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 675016
Processing commands for cont...@bugs.debian.org: tags 675016 + pending Bug #675016 [ifupdown] ifupdown: don't use PPP updetach option by default Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 675016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675016 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#671866: gmp: causes gcc ICEs on amd64 and kfreebsd-amd64
On Sun, May 27, 2012 at 09:57:14 +0200, bodr...@mail.dm.unipi.it wrote: Anyway, the following workaround may solve the problem: http://gmplib.org:8000/gmp-5.0/rev/ffdad0cda019 Thanks, much appreciated. 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#629952: Patch for NMU 1.6.17dfsg-3.1
And one last bit of the patch (apply on top of the attachment):
diff --git a/debian/changelog b/debian/changelog
index 15e4e33..7af3da1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,8 +6,9 @@ subversion (1.6.17dfsg-3.1) unstable; urgency=low
* Split libsvn-java to libsvn-java and libsvn-jni (Closes: #670034)
* Depend on generic libdb-dev and db-util (Closes: #621460)
* Install java files prior to dh_install -i call
+ * Declare proper relationships between -jni and -java packages
- -- Ondřej Surý ond...@debian.org Tue, 29 May 2012 13:59:11 +0200
+ -- Ondřej Surý ond...@debian.org Tue, 29 May 2012 15:49:32 +0200
subversion (1.6.17dfsg-3) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index f94fe1f..73a8fe2 100644
--- a/debian/control
+++ b/debian/control
@@ -128,6 +128,8 @@ Section: java
Architecture: any
Multi-Arch: same
Pre-Depends: multiarch-support
+Breaks: libsvn-java ( 1.6.17dfsg-3.1)
+Replaces: libsvn-java ( 1.6.17dfsg-3.1)
Depends: libsvn1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
Description: Java native interface bindings for Subversion
This is a set of Java classes which provide the functionality of
On Tue, May 29, 2012 at 3:26 PM, Ondřej Surý ond...@sury.org wrote:
subversion (1.6.17dfsg-3.1) unstable; urgency=low
* Non-maintainer upload
* Disable test-suite which was broken by apr 1.4.6 update (Closes: #669494)
* Also rescue on Errno::EINVAL (Closes: #624810, #629952)
* Split libsvn-java to libsvn-java and libsvn-jni (Closes: #670034)
* Depend on generic libdb-dev and db-util (Closes: #621460)
* Install java files prior to dh_install -i call
-- Ondřej Surý ond...@debian.org Tue, 29 May 2012 13:59:11 +0200
The fix for #624810, #629952 should also apply to stable updates.
The update will unfortunatelly be stalled in NEW queue due -java, -jni split.
O.
--
Ondřej Surý ond...@sury.org
--
Ondřej Surý ond...@sury.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675003: glchess: New game dialog not showing up.
On 29.05.2012 10:48, Pierre ANCELOT wrote: Package: glchess Version: 1:3.4.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, The documentation states: To start a new game, press the New Game buttton on the toolbar. The new game dialog is then shown, which allows you to setup a new game with the settings of your choice. Could you check if you have running gnuchess processes using 100% CPU -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#675003: glchess: New game dialog not showing up.
I had, and they remained after I closed the game. I ended up killing them. On Tue, May 29, 2012 at 3:18 PM, Michael Biebl bi...@debian.org wrote: On 29.05.2012 10:48, Pierre ANCELOT wrote: Package: glchess Version: 1:3.4.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, The documentation states: To start a new game, press the New Game buttton on the toolbar. The new game dialog is then shown, which allows you to setup a new game with the settings of your choice. Could you check if you have running gnuchess processes using 100% CPU -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- http://www.neko-consulting.com Educate and inform the whole mass of the people... They are the only sure reliance for the preservation of our liberty. —Thomas Jefferson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 675003 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=677037
Processing commands for cont...@bugs.debian.org: forwarded 675003 https://bugzilla.gnome.org/show_bug.cgi?id=677037 Bug #675003 [glchess] glchess: New game dialog not showing up. Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=677037'. thanks Stopping processing here. Please contact me if you need assistance. -- 675003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675003 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#666377: marked as done (cameleon: FTBFS: debian/xml-man/en/tdl.byte.1: No such file or directory at /usr/bin/dh_installman line 127.)
Your message dated Tue, 29 May 2012 15:03:38 +
with message-id e1sznxs-0001qd...@franck.debian.org
and subject line Bug#666377: fixed in cameleon 1.9.21-2
has caused the Debian Bug report #666377,
regarding cameleon: FTBFS: debian/xml-man/en/tdl.byte.1: No such file or
directory at /usr/bin/dh_installman line 127.
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.)
--
666377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: cameleon
Version: 1.9.21-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a recent dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
make[3]: Entering directory `/«PKGBUILDDIR»/doc'
Installing documentation...
/«PKGBUILDDIR»/debian/cameleon/usr/lib/ocaml/cameleon/stdlib.odoc installed
/«PKGBUILDDIR»/debian/cameleon/usr/lib/ocaml/cameleon/cameleon.odoc installed
make[3]: Leaving directory `/«PKGBUILDDIR»/doc'
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: Leaving directory `/«PKGBUILDDIR»'
touch debian/stamp-makefile-install
Adding cdbs dependencies to debian/cameleon.substvars
dh_installdirs -pcameleon
VERSION=1.9.21-1; \
VERSION=${VERSION%%-*}; \
sed -i s/@VERSION@/$VERSION/g '/«PKGBUILDDIR»/debian/META.cameleon'
# Remove unused binaries
rm -f /«PKGBUILDDIR»/debian/cameleon/usr/bin/*.x
# Move documentation (cameleon-doc)
mv /«PKGBUILDDIR»/debian/cameleon//usr/lib/ocaml/cameleon/*.odoc \
'/«PKGBUILDDIR»/debian/cameleon-doc//usr/lib/ocaml/cameleon'
# Install library (libcameleon-ocaml-dev)
mv '/«PKGBUILDDIR»/debian/cameleon//usr/lib/ocaml/cameleon' \
'/«PKGBUILDDIR»/debian/libcameleon-ocaml-dev//usr/lib/ocaml'
mv '/«PKGBUILDDIR»/debian/cameleon/usr/bin/make_my_chamo'
'/«PKGBUILDDIR»/debian/cameleon/usr/bin/make_my_chamo.tmp'
(echo '#!/bin/sh'; cat
'/«PKGBUILDDIR»/debian/cameleon/usr/bin/make_my_chamo.tmp')
'/«PKGBUILDDIR»/debian/cameleon/usr/bin/make_my_chamo'
rm -f '/«PKGBUILDDIR»/debian/cameleon/usr/bin/make_my_chamo.tmp'
Adding cdbs dependencies to debian/libcameleon-ocaml-dev.substvars
dh_installdirs -plibcameleon-ocaml-dev
dh_installdocs -pcameleon ./README ./TODO
dh_installexamples -pcameleon
dh_installman -pcameleon
debian/xml-man/en/tdl.byte.1: No such file or directory at
/usr/bin/dh_installman line 127.
make: *** [binary-install/cameleon] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/30/cameleon_1.9.21-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
---End Message---
---BeginMessage---
Source: cameleon
Source-Version: 1.9.21-2
We believe that the bug you reported is fixed in the latest version of
cameleon, which is due to be installed in the Debian FTP archive:
cameleon-doc_1.9.21-2_all.deb
to main/c/cameleon/cameleon-doc_1.9.21-2_all.deb
cameleon_1.9.21-2.debian.tar.gz
to main/c/cameleon/cameleon_1.9.21-2.debian.tar.gz
cameleon_1.9.21-2.dsc
to main/c/cameleon/cameleon_1.9.21-2.dsc
cameleon_1.9.21-2_amd64.deb
to main/c/cameleon/cameleon_1.9.21-2_amd64.deb
libcameleon-ocaml-dev_1.9.21-2_amd64.deb
to main/c/cameleon/libcameleon-ocaml-dev_1.9.21-2_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 666...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mehdi Dogguy me...@debian.org (supplier of updated cameleon 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, 29 May 2012 15:13:13 +0200
Source: cameleon
Binary: cameleon cameleon-doc
Bug#667361: rtorrent: diff for NMU version 0.8.9-2.1
On Tue, 29 May 2012 03:27:00 -0300, Rogério Brito wrote: On May 28 2012, gregor herrmann wrote: (...) Just ping me when I should look at the git repos again. That will not be necessary. I was mislead that the libtorrent package needed another binary package rename and, in that case, I would need to be sponsored. But that turned out not to be the case and I have just uploaded both libtorrent and rtorrent. Even better :) Thanks for the offer anyway---I'm sure that I will need sponsoring in the future. Or you finally become a DD :) (But yes, feel free to ping me if you need help with uploading.) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Art Garfunkel: Sometimes When I'm Dreaming signature.asc Description: Digital signature
Processed: found 667111 in 0.2-1.1
Processing commands for cont...@bugs.debian.org:
# on i386
found 667111 0.2-1.1
Bug #667111 {Done: gregor herrmann gre...@debian.org} [bcov] bcov: ftbfs with
GCC-4.7
Marked as found in versions bcov/0.2-1.1; no longer marked as fixed in versions
bcov/0.2-1.1 and reopened.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
667111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667111
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#667111: bcov: diff for NMU version 0.2-1.2
tags 667111 + pending thanks Dear maintainer, I've prepared an NMU for bcov (versioned as 0.2-1.2) that should fix the issue of -1.1 on i386, and I've uploaded it to DELAYED/1. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: hons: shielded with ease diff -Nru bcov-0.2/debian/changelog bcov-0.2/debian/changelog --- bcov-0.2/debian/changelog 2012-05-27 13:55:27.0 +0200 +++ bcov-0.2/debian/changelog 2012-05-29 17:29:32.0 +0200 @@ -1,3 +1,12 @@ +bcov (0.2-1.2) unstable; urgency=low + + * Non-maintainer upload. + * Extend patch to add the missing include to yet another file, the original +patch was not enough for i386. +Hopefully really closes: #667111 + + -- gregor herrmann gre...@debian.org Tue, 29 May 2012 17:28:19 +0200 + bcov (0.2-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru bcov-0.2/debian/patches/fix-ftbfs-with-gcc-4.7 bcov-0.2/debian/patches/fix-ftbfs-with-gcc-4.7 --- bcov-0.2/debian/patches/fix-ftbfs-with-gcc-4.7 2012-05-27 13:55:13.0 +0200 +++ bcov-0.2/debian/patches/fix-ftbfs-with-gcc-4.7 2012-05-29 17:31:30.0 +0200 @@ -22,3 +22,13 @@ //--- using namespace std; //--- +--- bcov-0.2.orig/src/Debugger.cpp bcov-0.2/src/Debugger.cpp +@@ -21,6 +21,7 @@ + #include sys/ptrace.h + #include sys/user.h + #include sys/wait.h ++#include unistd.h + //--- + using namespace std; + //--- signature.asc Description: Digital signature
Processed: bcov: diff for NMU version 0.2-1.2
Processing commands for cont...@bugs.debian.org: tags 667111 + pending Bug #667111 [bcov] bcov: ftbfs with GCC-4.7 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 667111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667111 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#670756: marked as done (libswt-gtk-3-java: please update for current version of swt-cairo-gtk)
Your message dated Tue, 29 May 2012 15:37:29 + with message-id e1szoud-0005pr...@franck.debian.org and subject line Bug#670756: fixed in swt-gtk 3.8.0~rc2-1 has caused the Debian Bug report #670756, regarding libswt-gtk-3-java: please update for current version of swt-cairo-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.) -- 670756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libswt-gtk-3-java Version: 3.7.2-2 Severity: serious Tags: lfs Justification: Policy 8.6 So when I try to start tuxguitar... Exception in thread main org.eclipse.swt.SWTException: Unable to load graphics library [Cairo is required] (java.lang.UnsatisfiedLinkError: no swt- cairo-gtk-3555 or swt-cairo-gtk in swt.library.path, java.library.path or the jar file) at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.graphics.Device.checkCairo(Device.java:176) at org.eclipse.swt.graphics.Path.init(Path.java:78) at org.herac.tuxguitar.gui.editors.TGPainter.initPath(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.TGResources.getImage(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.TGResources.getScoreNoteImage(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.TGResources.initImages(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.TGResources.load(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.layout.ViewLayout.reloadStyles(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.Tablature.reloadStyles(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.Tablature.setViewLayout(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.Tablature.loadViewLayout(Unknown Source) at org.herac.tuxguitar.gui.editors.tab.Tablature.reloadViewLayout(Unknown Source) at org.herac.tuxguitar.gui.editors.TablatureEditor.showTablature(Unknown Source) at org.herac.tuxguitar.gui.TuxGuitar.createComposites(Unknown Source) at org.herac.tuxguitar.gui.TuxGuitar.displayGUI(Unknown Source) at org.herac.tuxguitar.gui.TGMain.main(Unknown Source) Caused by: java.lang.UnsatisfiedLinkError: no swt-cairo-gtk-3555 or swt-cairo- gtk in swt.library.path, java.library.path or the jar file at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:159) at org.eclipse.swt.internal.cairo.Cairo.clinit(Cairo.java:27) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at org.eclipse.swt.graphics.Device.checkCairo(Device.java:173) The workaround I came up with was to link libswt-cairo-gtk.so to the new jni name like so ln -s /usr/lib/jni/libswt-cairo-gtk-3740.so /usr/lib/jni/libswt-cairo-gtk.so but this shouldn't be nessicary. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0-rc2-rt2-00249-ga9d3702 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libswt-gtk-3-java depends on: ii libswt-gtk-3-jni 3.7.2-2 libswt-gtk-3-java recommends no packages. Versions of packages libswt-gtk-3-java suggests: pn libswt-gtk-3-java-gcj none -- no debconf information ---End Message--- ---BeginMessage--- Source: swt-gtk Source-Version: 3.8.0~rc2-1 We believe that the bug you reported is fixed in the latest version of swt-gtk, which is due to be installed in the Debian FTP archive: libswt-cairo-gtk-3-jni_3.8.0~rc2-1_amd64.deb to main/s/swt-gtk/libswt-cairo-gtk-3-jni_3.8.0~rc2-1_amd64.deb libswt-glx-gtk-3-jni_3.8.0~rc2-1_amd64.deb to main/s/swt-gtk/libswt-glx-gtk-3-jni_3.8.0~rc2-1_amd64.deb libswt-gnome-gtk-3-jni_3.8.0~rc2-1_amd64.deb to main/s/swt-gtk/libswt-gnome-gtk-3-jni_3.8.0~rc2-1_amd64.deb libswt-gtk-3-java-gcj_3.8.0~rc2-1_amd64.deb to main/s/swt-gtk/libswt-gtk-3-java-gcj_3.8.0~rc2-1_amd64.deb libswt-gtk-3-java_3.8.0~rc2-1_amd64.deb to main/s/swt-gtk/libswt-gtk-3-java_3.8.0~rc2-1_amd64.deb libswt-gtk-3-jni_3.8.0~rc2-1_amd64.deb to main/s/swt-gtk/libswt-gtk-3-jni_3.8.0~rc2-1_amd64.deb libswt-webkit-gtk-3-jni_3.8.0~rc2-1_amd64.deb to main/s/swt-gtk/libswt-webkit-gtk-3-jni_3.8.0~rc2-1_amd64.deb swt-gtk_3.8.0~rc2-1.diff.gz to main/s/swt-gtk/swt-gtk_3.8.0~rc2-1.diff.gz swt-gtk_3.8.0~rc2-1.dsc to main/s/swt-gtk/swt-gtk_3.8.0~rc2-1.dsc
Bug#667417: wrapitk-python build failure?
Hi, just NMUed sofa-framework, and it looks like wrapitk-python is the last failing package when built with GCC 4.7. Did somebody forward the issue upstream, or did investigate it? Thanks, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674365: marked as done (libconfig-model-tkui-perl: FTBFS: tests failed)
Your message dated Tue, 29 May 2012 16:02:50 + with message-id e1szosk-0007re...@franck.debian.org and subject line Bug#674365: fixed in libconfig-model-tkui-perl 1.336-1 has caused the Debian Bug report #674365, regarding libconfig-model-tkui-perl: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 674365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libconfig-model-tkui-perl Version: 1.335-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build dh build dh_testdir dh_auto_configure Checking prerequisites... build_requires: ! Test::MemoryCycle is not installed ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation Run 'Build installdeps' to install missing prerequisites. Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'Config-Model-TkUI' version 'installdirs=vendor' dh_auto_build Building Config-Model-TkUI dh_auto_test Name Pod::POM::Node::Pod::ATTRIBS used only once: possible typo at /usr/share/perl5/Pod/POM/Node.pm line 80. t/config-model-ui.t .. ok Name Pod::POM::Node::Pod::ATTRIBS used only once: possible typo at /usr/share/perl5/Pod/POM/Node.pm line 80. # Looks like you planned 6 tests but ran 5. t/config-model-wizard.t .. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 1/6 subtests (less 1 skipped subtest: 4 okay) t/pod.t .. ok t/release-pod-syntax.t ... skipped: these tests are for release candidate testing Test Summary Report --- t/config-model-wizard.t (Wstat: 65280 Tests: 5 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 6 tests but ran 5. Files=4, Tests=71, 2 wallclock secs ( 0.05 usr 0.02 sys + 1.43 cusr 0.25 csys = 1.75 CPU) Result: FAIL Failed 1/4 test programs. 0/71 subtests failed. dh_auto_test: perl Build test returned exit code 255 make: *** [build] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/libconfig-model-tkui-perl_1.335-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: libconfig-model-tkui-perl Source-Version: 1.336-1 We believe that the bug you reported is fixed in the latest version of libconfig-model-tkui-perl, which is due to be installed in the Debian FTP archive: libconfig-model-tkui-perl_1.336-1.debian.tar.gz to main/libc/libconfig-model-tkui-perl/libconfig-model-tkui-perl_1.336-1.debian.tar.gz libconfig-model-tkui-perl_1.336-1.dsc to main/libc/libconfig-model-tkui-perl/libconfig-model-tkui-perl_1.336-1.dsc libconfig-model-tkui-perl_1.336-1_all.deb to main/libc/libconfig-model-tkui-perl/libconfig-model-tkui-perl_1.336-1_all.deb libconfig-model-tkui-perl_1.336.orig.tar.gz to main/libc/libconfig-model-tkui-perl/libconfig-model-tkui-perl_1.336.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 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont d...@debian.org (supplier of updated libconfig-model-tkui-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 May 2012 17:34:54 +0200 Source: libconfig-model-tkui-perl Binary: libconfig-model-tkui-perl Architecture: source all Version: 1.336-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Dominique Dumont d...@debian.org Description: libconfig-model-tkui-perl - Tk GUI to edit config data through Config::Model Closes: 674365
Processed: Re: aptitude: FTBFS
Processing commands for cont...@bugs.debian.org: severity 667793 serious Bug #667793 [aptitude] aptitude: FTBFS Severity set to 'serious' from 'minor' thanks Stopping processing here. Please contact me if you need assistance. -- 667793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667793 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#670733: ocaml-cry: FTBFS: Incorrectly thinks it's building as root
On 13/05/12 23:37, Hendrik Tews wrote: ... the incorrect root test comes from file m4/base_checks.m4 deleting the line 'RUNNING_USER=$USER' there and running ./bootstrap then yields checking that calling user is not root... ok and the package builds fine (done with autoconf 2.69; maybe its better to downgrade to 2.68 to keep the patch small). Thanks for the investigation! Could you prepare patches for the affected packages so that we fix them in Unstable? (You can set Team upload in the debian/changelog). Cheers, -- 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#674226: ball: FTBFS in sid: use of deleted function 'BALL::String::String(const BALL::String)'
Thank you, Samuel. Upstream is aware of this problem and also knows about next month's freeze. They will do what they can do. Steffen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 660567
Processing commands for cont...@bugs.debian.org: tags 660567 + help Bug #660567 [screen] screen: Immediately exits on kfreebsd when trying to start a new session Added tag(s) help. thanks Stopping processing here. Please contact me if you need assistance. -- 660567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660567 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: .
Processing commands for cont...@bugs.debian.org: tag 671064 +pending Bug #671064 [src:nmap] nmap: FTBFS[kfreebsd]: error: 'CLOCK_MONOTONIC' undeclared Added tag(s) pending. thank you Stopping processing here. Please contact me if you need assistance. -- 671064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671064 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#675022: Acknowledgement (Frequent lockups when using icedove (thunderbird))
I can confirm that the proposed fix to disable FBC worked for me. Since i915.i915_enable_fbc=0, the GPU hangs didn't occur again. I'm wondering if xserver-xorg-video-intel should ship a modprobe file accordingly or if it is feasible to backport the fixes in 3.4 that were briefly mentioned in the upstream bug report. [1] https://bugs.freedesktop.org/show_bug.cgi?id=50455#c9 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: tagging 674341
Processing commands for cont...@bugs.debian.org: tags 674341 + pending Bug #674341 [src:mpfi] mpfi: FTBFS: tests failed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 674341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674341 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#674844: [FIGlet] Figlet Font Licensing
On Mon, May 28, 2012 at 1:44 PM, John Cowan co...@mercury.ccil.org wrote: Jonathan McCrohan scripsit: During a review of my updated figlet 2.2.4-1 package[1], it was discovered that the fonts directory still contains non-distributable files. An example of these files are the fonts/8859-*.flc files. These files contain the following paragraph: Unicode, Inc. specifically excludes the right to re-distribute this file directly to third parties or other organizations whether for profit or not. Those should simply be replaced by the verbatim contents of the corresponding files at http://www.unicode.org/Public/MAPPINGS/ISO8859 . In addition, the jis0201.flc file should be replaced likewise by the verbatim contents of http://www.unicode.org/Public/MAPPINGS/OBSOLETE/EASTASIA/JIS/JIS0201.TXT . Changes made as directed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674844: [FIGlet] Figlet Font Licensing
Claudio Matsuoka scripsit: Changes made as directed. Great. You should test it, at least as far as making sure figlet doesn't choke on the new files. -- A rose by any other nameJohn Cowan may smell as sweet, http://www.ccil.org/~cowan but if you called it an onion co...@ccil.org you'd get cooks very confused. --RMS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
