Processed: r4743 - packages/fonts-bpg-georgian/trunk/debian
Processing commands for cont...@bugs.debian.org: > tags 672167 pending Bug #672167 [fonts-bpg-georgian] fonts-bpg-georgian: fails to upgrade from 'testing' - trying to overwrite /usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Rioni.ttf Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 672167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672167 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#671970: marked as done (tdiary-contrib: FTBFS: make: rsync: Command not found)
Your message dated Wed, 09 May 2012 06:48:07 + with message-id and subject line Bug#671970: fixed in tdiary-contrib 3.1.20120506-2 has caused the Debian Bug report #671970, regarding tdiary-contrib: FTBFS: make: rsync: Command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 671970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tdiary-contrib Version: 3.1.20120506-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: > fakeroot debian/rules binary > test -x debian/rules > dh_testroot > dh_prep > dh_installdirs -A > mkdir -p "." > Adding cdbs dependencies to debian/tdiary-contrib.substvars > dh_installdirs -ptdiary-contrib > rsync -rlpqHSC js /«PKGBUILDDIR»/debian/tdiary-contrib/usr/share/tdiary/ > make: rsync: Command not found > make: *** [install/tdiary-contrib] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/tdiary-contrib_3.1.20120506-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 --- --- Begin Message --- Source: tdiary-contrib Source-Version: 3.1.20120506-2 We believe that the bug you reported is fixed in the latest version of tdiary-contrib, which is due to be installed in the Debian FTP archive: tdiary-contrib_3.1.20120506-2.debian.tar.gz to main/t/tdiary-contrib/tdiary-contrib_3.1.20120506-2.debian.tar.gz tdiary-contrib_3.1.20120506-2.dsc to main/t/tdiary-contrib/tdiary-contrib_3.1.20120506-2.dsc tdiary-contrib_3.1.20120506-2_all.deb to main/t/tdiary-contrib/tdiary-contrib_3.1.20120506-2_all.deb tdiary-mode_3.1.20120506-2_all.deb to main/t/tdiary-contrib/tdiary-mode_3.1.20120506-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Taku YASUI (supplier of updated tdiary-contrib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 09 May 2012 15:26:10 +0900 Source: tdiary-contrib Binary: tdiary-contrib tdiary-mode Architecture: source all Version: 3.1.20120506-2 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers Changed-By: Taku YASUI Description: tdiary-contrib - Plugins of tDiary to add functionalities tdiary-mode - tDiary editing mode for Emacsen Closes: 671970 Changes: tdiary-contrib (3.1.20120506-2) unstable; urgency=low . * debian/control: Add rsync to Build-Deps (closes: #671970). Checksums-Sha1: c8064adf995a87f14040a04282e6cdac045bfd07 2128 tdiary-contrib_3.1.20120506-2.dsc 69baa49323547f416149bd2c6dce0214d2eeb374 10493 tdiary-contrib_3.1.20120506-2.debian.tar.gz 3848c28d60fd1170494104f91090655abb16fd5c 382910 tdiary-contrib_3.1.20120506-2_all.deb 61dd785d3246ac09db7e315057f99d7eafc4cbe9 15050 tdiary-mode_3.1.20120506-2_all.deb Checksums-Sha256: af95d9d3ec68f6c37d493c66330ac821b087ad48119d3ddfe3c38302569c1bba 2128 tdiary-contrib_3.1.20120506-2.dsc ed1f5da904d7ef3e8eb348adb6547b240ff271df15a8aebdd724304ad847eb62 10493 tdiary-contrib_3.1.20120506-2.debian.tar.gz 5f9c5f5ebefd01e83a0166a4c5cde61886a63fc01b1ffb516a9b766fab68fe7e 382910 tdiary-contrib_3.1.20120506-2_all.deb b343a92be31171bb74af7e7251f485fb2b5bbf7cbd216b01d418a12a77ff7cc9 15050 tdiary-mode_3.1.20120506-2_all.deb Files: bb518ad59f34bddef7c9337b74d65f9a 2128 web extra tdiary-contrib_3.1.20120506-2.dsc 5671443b24c5d2a227ad67fcb9b61de8 10493 web extra tdiary-contrib_3.1.20120506-2.debian.tar.gz b81570a4c8678f56083fc569f5af66de 382910 web extra tdiary-contrib_3.1.20120506-2_all.deb 0349485448ce0082930a959bace24bd4 15050 web extra tdiary-mode_3.1.20120506-2_all.deb -BEGIN
Bug#672210: songwrite doesn't start
Package: songwrite
Version: 0.14-8
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Songwrite fails to start like so:
Traceback (most recent call last):
File "/usr/bin/songwrite", line 134, in
import main
File "/usr/bin/../share/songwrite/main.py", line 21, in
import globdef, song, player, ui
File "/usr/bin/../share/songwrite/song.py", line 1352, in
END_TRACK = struct.pack(">bbb", 0xFF, 0x2F, 0x00)
struct.error: byte format requires -128 <= number <= 127
If I change the shebang line at the top of /usr/bin/songwrite from
#!/usr/bin/python -O
to
#!/usr/bin/python2.6 -O
it works, so I guess the different bytes implementation from python 2.6 to 2.7
means the code won't work on 2.7, which is current Testing. There are several
calls to struct.pack elsewhere in the code which have the same problem, but
I'm not sure of the best way to fix it. Changing the format argument (say,
"bbb" to "HHH") fixes it too, but as I've never used struct, I'm just shooting
in the dark.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.4-2012-04-16-02.48 (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 songwrite depends on:
ii evince-gtk [postscript-viewer] 3.2.1-1+b1
ii ghostscript [postscript-viewer] 9.05~dfsg-5
ii lilypond 2.14.2-2+b1
ii python 2.7.2-10
ii python-editobj 0.5.7-9
ii python-support 1.0.14
ii python-tk2.7.3-1
ii timidity 2.13.2-40
songwrite recommends no packages.
songwrite 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#672208: python-dolfin: Extension module cpp not found/built
Package: python-dolfin Version: 1.0.0-4+b2 Severity: grave Justification: renders package unusable Dear Maintainer, Here's an example traceback when running the poisson equation demo. $ python demo_poisson.py Traceback (most recent call last): File "demo_poisson.py", line 40, in from dolfin import * File "/usr/lib/python2.7/dist-packages/dolfin/__init__.py", line 23, in from dolfin.cppimports import * File "/usr/lib/python2.7/dist-packages/dolfin/cppimports.py", line 4, in import dolfin.cpp as cpp ImportError: No module named cpp It seems that in the current (1.0.0-4+b2) version of python-dolfin, the extension module cpp is somehow not built. You can, for example, compare the size of the package files as seen in snapshot.debian.org python-dolfin_1.0.0-4+b1_amd64.deb Seen in debian on 2012-04-12 04:27:45 in /pool/main/d/dolfin. Size: 2068978 python-dolfin_1.0.0-4+b2_amd64.deb Seen in debian on 2012-04-27 22:09:51 in /pool/main/d/dolfin. Size: 111986 Regards, ST -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'gutsy') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-dolfin depends on: ii libdolfin1.0 1.0.0-4+b2 ii libdolfin1.0-dev 1.0.0-4+b2 ii python2.7.2-10 ii python-ffc1.0.0-1 ii python-instant1.0.0-1 ii python-numpy [python-numpy-abi9] 1:1.6.1-8 ii python-ufc2.0.5-1+b1 ii python-ufl1.0.0-1 ii python-viper 1.0.0-1 ii python2.7 2.7.3~rc2-2.1 ii swig2.0 2.0.5-1 python-dolfin recommends no packages. Versions of packages python-dolfin suggests: pn dolfin-doc -- 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#664569: NMU diff
Hi Scott,
thanks for your effort. NMU is fine however, it would be really great
if you would commit your changes to SVN. The easiest way to do so
would probably be
debcheckout --user= pythonqt
Commit permissions are granted to every DD.
Kind regards and thanks again for helping us out
Andreas.
On Wed, May 09, 2012 at 12:25:14AM -0400, Scott Kitterman wrote:
> I'll upload the attached diff shortly to delay/2 in order to minimize impact
> on
> the Qt 4.8 transition. If you'd prefer I delay it further because you are
> preparing an upload, please let me know.
>
> Scott K
>
> diff -Nru pythonqt-2.0.1/debian/changelog pythonqt-2.0.1/debian/changelog
> --- pythonqt-2.0.1/debian/changelog 2011-03-10 10:19:44.0 -0500
> +++ pythonqt-2.0.1/debian/changelog 2012-05-09 00:14:30.0 -0400
> @@ -1,3 +1,14 @@
> +pythonqt (2.0.1-1.1) unstable; urgency=low
> +
> + * Non-maintainer upload.
> + * Fix FTBFS with Qt 4.8 (Closes: #664569)
> +- Add debian/patches/stddecorators_no_keywords.patch
> +- Extend debian/patches/cmakebuildsystem.patch to compile with
> + -DQT_NO_KEYWORDS
> +- Thanks to Felix Geyer for the patch
> +
> + -- Scott Kitterman Wed, 09 May 2012 00:14:21 -0400
> +
> pythonqt (2.0.1-1) unstable; urgency=low
>
>* Initial release (Closes: #616698)
> diff -Nru pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch
> pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch
> --- pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch 2011-03-10
> 10:19:44.0 -0500
> +++ pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch 2012-05-09
> 00:14:12.0 -0400
> @@ -2,7 +2,7 @@
> ===
> --- /dev/null1970-01-01 00:00:00.0 +
> +++ PythonQt2.0.1/CMakeLists.txt 2011-03-06 19:23:17.0 +0100
> -@@ -0,0 +1,259 @@
> +@@ -0,0 +1,266 @@
> +cmake_minimum_required(VERSION 2.8)
> +
>
> +#-
> @@ -240,6 +240,13 @@
> +set_target_properties(PythonQt PROPERTIES DEFINE_SYMBOL PYTHONQT_EXPORTS)
> +set_target_properties(PythonQt PROPERTIES ${PythonQt_LIBRARY_PROPERTIES})
> +
> ++foreach(source ${gen_moc_sources})
> ++ string(REGEX MATCH "PythonQtStdDecorators" match ${source})
> ++ if(match)
> ++set_property(SOURCE ${source} PROPERTY COMPILE_FLAGS -DQT_NO_KEYWORDS)
> ++ endif(match)
> ++endforeach(source {gen_moc_sources})
> ++
> +#
> +# That should solve linkage error on Mac when the project is used in a
> superbuild setup
> +# See http://blog.onesadcookie.com/2008/01/installname-magic.html
> diff -Nru pythonqt-2.0.1/debian/patches/series
> pythonqt-2.0.1/debian/patches/series
> --- pythonqt-2.0.1/debian/patches/series 2011-03-10 10:19:44.0
> -0500
> +++ pythonqt-2.0.1/debian/patches/series 2012-05-09 00:14:12.0
> -0400
> @@ -1 +1,2 @@
> cmakebuildsystem.patch
> +stddecorators_no_keywords.patch
> diff -Nru pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch
> pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch
> --- pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch
> 1969-12-31 19:00:00.0 -0500
> +++ pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch
> 2012-05-09 00:14:12.0 -0400
> @@ -0,0 +1,24 @@
> +--- pythonqt-2.0.1.orig/src/PythonQtStdDecorators.h
> pythonqt-2.0.1/src/PythonQtStdDecorators.h
> +@@ -56,16 +56,20 @@ class PYTHONQT_EXPORT PythonQtStdDecorat
> + {
> + Q_OBJECT
> +
> +-public slots:
> ++public Q_SLOTS:
> + bool connect(QObject* sender, const QByteArray& signal, PyObject*
> callable);
> + bool connect(QObject* sender, const QByteArray& signal, QObject*
> receiver, const QByteArray& slot);
> + bool disconnect(QObject* sender, const QByteArray& signal, PyObject*
> callable);
> + bool disconnect(QObject* sender, const QByteArray& signal, QObject*
> receiver, const QByteArray& slot);
> +
> ++#ifndef QT_NO_KEYWORDS
> + #undef emit
> ++#endif
> + void emit(QObject* sender, const QByteArray& signal, PyObject* arg1 =
> NULL,PyObject* arg2 = NULL,
> + PyObject* arg3 = NULL,PyObject* arg4 = NULL,PyObject* arg5 =
> NULL,PyObject* arg6 = NULL,PyObject* arg7 = NULL);
> ++#ifndef QT_NO_KEYWORDS
> + #define emit
> ++#endif
> +
> + QObject* parent(QObject* o);
> + void setParent(QObject* o, QObject* parent);
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669505: marked as done (tuxfootball: FTBFS: gcc: error: unrecognized option '-V')
Your message dated Wed, 09 May 2012 06:18:23 + with message-id and subject line Bug#669505: fixed in tuxfootball 0.3.1-1 has caused the Debian Bug report #669505, regarding tuxfootball: FTBFS: gcc: error: unrecognized option '-V' 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.) -- 669505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tuxfootball Version: 0.3.0-3 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: > gcc version 4.6.3 (Debian 4.6.3-4) > configure:4165: $? = 0 > configure:4154: gcc -V >&5 > gcc: error: unrecognized option '-V' > gcc: fatal error: no input files > compilation terminated. > configure:4165: $? = 4 > configure:4154: gcc -qversion >&5 > gcc: error: unrecognized option '-qversion' > gcc: fatal error: no input files > compilation terminated. > configure:4165: $? = 4 > configure:4169: checking whether we are using the GNU C compiler > configure:4188: gcc -c conftest.c >&5 > configure:4188: $? = 0 > configure:4197: result: yes > configure:4206: checking whether gcc accepts -g > configure:4226: gcc -c -g conftest.c >&5 > configure:4226: $? = 0 > configure:4267: result: yes > configure:4284: checking for gcc option to accept ISO C89 > configure:4348: gcc -c -g -O2 conftest.c >&5 > configure:4348: $? = 0 > configure:4361: result: none needed > configure:4383: checking dependency style of gcc > configure:4493: result: none > configure:4513: checking how to run the C preprocessor > configure:4544: gcc -E conftest.c > configure:4544: $? = 0 > configure:4558: gcc -E conftest.c > conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory > compilation terminated. > configure:4558: $? = 1 > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "tuxfootball" > | #define PACKAGE_TARNAME "tuxfootball" > | #define PACKAGE_VERSION "0.3.0" > | #define PACKAGE_STRING "tuxfootball 0.3.0" > | #define PACKAGE_BUGREPORT "http://tuxfootball.sourceforge.net/"; > | #define PACKAGE_URL "" > | /* end confdefs.h. */ > | #include > configure:4583: result: gcc -E > configure:4603: gcc -E conftest.c > configure:4603: $? = 0 > configure:4617: gcc -E conftest.c > conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory > compilation terminated. > configure:4617: $? = 1 > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "tuxfootball" > | #define PACKAGE_TARNAME "tuxfootball" > | #define PACKAGE_VERSION "0.3.0" > | #define PACKAGE_STRING "tuxfootball 0.3.0" > | #define PACKAGE_BUGREPORT "http://tuxfootball.sourceforge.net/"; > | #define PACKAGE_URL "" > | /* end confdefs.h. */ > | #include > configure:4646: checking whether ln -s works > configure:4650: result: yes > configure:4657: checking whether make sets $(MAKE) > configure:4679: result: yes > configure:4731: checking for ranlib > configure:4747: found /usr/bin/ranlib > configure:4758: result: ranlib > configure:4781: checking whether NLS is requested > configure:4790: result: yes > configure:4806: checking for intltool >= 0.35.0 > configure:4813: result: 0.50.2 found > configure:4821: checking for intltool-update > configure:4839: found /usr/bin/intltool-update > configure:4851: result: /usr/bin/intltool-update > configure:4861: checking for intltool-merge > configure:4879: found /usr/bin/intltool-merge > configure:4891: result: /usr/bin/intltool-merge > configure:4901: checking for intltool-extract > configure:4919: found /usr/bin/intltool-extract > configure:4931: result: /usr/bin/intltool-extract > configure:5062: checking for xgettext > configure:5080: found /usr/bin/xgettext > configure:5092: result: /usr/bin/xgettext > configure:5102: checking for msgmerge > configure:5120: found /usr/bin/msgmerge > configure:5132: result: /usr/bin/msgmerge > configure:5142: checking for msgfmt > configure:5160: found /usr/bin/msgfmt > configure:5172: result: /usr/bin/msgfmt > configure:5182: checking for gmsgfmt > configure:5213: result: /usr/bin/msgfmt > configure:5233: checking for perl > configure:5251: found /usr/bin/perl > configure:5263: result: /usr/bin/perl > configure:5274: checking for perl >= 5.8.1 > configure:5281: result: 5.14.2 > configure:5285: checking for XML::Parser > configure:5288: result: ok > configure:5313: gcc -o conftest -g -O2 conftest.c >&5 > configure:5313: $? = 0 > configure:5
Bug#671800: xserver-xorg-video-savage: segfaults under X.Org X Server 1.12.1
Stefan Lippers-Hollmann (09/05/2012): > Thanks a lot, xserver-xorg-video-savage 1:2.3.4-1 is working perfectly. Thanks for the confirmation, too. Mraw, KiBi. signature.asc Description: Digital signature
Bug#672204: csladspa causes several audio programs to segfault
Package: csladspa Version: 1:5.17.6~dfsg-2 Severity: critical Justification: breaks unrelated software Dear Maintainer, After a recent upgrade which included csladspa, several music/audio programs, which were not themselves updated, failed to start with a segmentation fault. So far this applies to Audacity, Ardour, Rosegarden and Hydrogen. Uninstalling csladspa returned these programs to normal function. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.4-2012-04-16-02.48 (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 csladspa depends on: ii libc62.13-32 ii libcsound64-5.2 1:5.17.6~dfsg-2 ii libgcc1 1:4.7.0-7 ii libstdc++6 4.7.0-7 csladspa recommends no packages. csladspa 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#664569: NMU diff
I'll upload the attached diff shortly to delay/2 in order to minimize impact on
the Qt 4.8 transition. If you'd prefer I delay it further because you are
preparing an upload, please let me know.
Scott K
diff -Nru pythonqt-2.0.1/debian/changelog pythonqt-2.0.1/debian/changelog
--- pythonqt-2.0.1/debian/changelog 2011-03-10 10:19:44.0 -0500
+++ pythonqt-2.0.1/debian/changelog 2012-05-09 00:14:30.0 -0400
@@ -1,3 +1,14 @@
+pythonqt (2.0.1-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS with Qt 4.8 (Closes: #664569)
+- Add debian/patches/stddecorators_no_keywords.patch
+- Extend debian/patches/cmakebuildsystem.patch to compile with
+ -DQT_NO_KEYWORDS
+- Thanks to Felix Geyer for the patch
+
+ -- Scott Kitterman Wed, 09 May 2012 00:14:21 -0400
+
pythonqt (2.0.1-1) unstable; urgency=low
* Initial release (Closes: #616698)
diff -Nru pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch
--- pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch 2011-03-10 10:19:44.0 -0500
+++ pythonqt-2.0.1/debian/patches/cmakebuildsystem.patch 2012-05-09 00:14:12.0 -0400
@@ -2,7 +2,7 @@
===
--- /dev/null 1970-01-01 00:00:00.0 +
+++ PythonQt2.0.1/CMakeLists.txt 2011-03-06 19:23:17.0 +0100
-@@ -0,0 +1,259 @@
+@@ -0,0 +1,266 @@
+cmake_minimum_required(VERSION 2.8)
+
+#-
@@ -240,6 +240,13 @@
+set_target_properties(PythonQt PROPERTIES DEFINE_SYMBOL PYTHONQT_EXPORTS)
+set_target_properties(PythonQt PROPERTIES ${PythonQt_LIBRARY_PROPERTIES})
+
++foreach(source ${gen_moc_sources})
++ string(REGEX MATCH "PythonQtStdDecorators" match ${source})
++ if(match)
++set_property(SOURCE ${source} PROPERTY COMPILE_FLAGS -DQT_NO_KEYWORDS)
++ endif(match)
++endforeach(source {gen_moc_sources})
++
+#
+# That should solve linkage error on Mac when the project is used in a superbuild setup
+# See http://blog.onesadcookie.com/2008/01/installname-magic.html
diff -Nru pythonqt-2.0.1/debian/patches/series pythonqt-2.0.1/debian/patches/series
--- pythonqt-2.0.1/debian/patches/series 2011-03-10 10:19:44.0 -0500
+++ pythonqt-2.0.1/debian/patches/series 2012-05-09 00:14:12.0 -0400
@@ -1 +1,2 @@
cmakebuildsystem.patch
+stddecorators_no_keywords.patch
diff -Nru pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch
--- pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch 1969-12-31 19:00:00.0 -0500
+++ pythonqt-2.0.1/debian/patches/stddecorators_no_keywords.patch 2012-05-09 00:14:12.0 -0400
@@ -0,0 +1,24 @@
+--- pythonqt-2.0.1.orig/src/PythonQtStdDecorators.h
pythonqt-2.0.1/src/PythonQtStdDecorators.h
+@@ -56,16 +56,20 @@ class PYTHONQT_EXPORT PythonQtStdDecorat
+ {
+ Q_OBJECT
+
+-public slots:
++public Q_SLOTS:
+ bool connect(QObject* sender, const QByteArray& signal, PyObject* callable);
+ bool connect(QObject* sender, const QByteArray& signal, QObject* receiver, const QByteArray& slot);
+ bool disconnect(QObject* sender, const QByteArray& signal, PyObject* callable);
+ bool disconnect(QObject* sender, const QByteArray& signal, QObject* receiver, const QByteArray& slot);
+
++#ifndef QT_NO_KEYWORDS
+ #undef emit
++#endif
+ void emit(QObject* sender, const QByteArray& signal, PyObject* arg1 = NULL,PyObject* arg2 = NULL,
+ PyObject* arg3 = NULL,PyObject* arg4 = NULL,PyObject* arg5 = NULL,PyObject* arg6 = NULL,PyObject* arg7 = NULL);
++#ifndef QT_NO_KEYWORDS
+ #define emit
++#endif
+
+ QObject* parent(QObject* o);
+ void setParent(QObject* o, QObject* parent);
signature.asc
Description: This is a digitally signed message part.
Bug#671866: gmp: causes gcc ICEs on amd64 and kfreebsd-amd64
On Tue, May 08, 2012 at 09:26:40PM +0200, Julien Cristau wrote: > > > As I'd like this fixed ASAP to get the buildds back in working > > > condition, I'll be preparing a NMU with --disable-fat. Please yell if > > > you think I shouldn't upload it. Thanks for this. -Steve signature.asc Description: Digital signature
Bug#662712: marked as done (fracplanet: FTBFS against Qt 4.8)
Your message dated Wed, 09 May 2012 03:17:20 + with message-id and subject line Bug#662712: fixed in fracplanet 0.4.0-2 has caused the Debian Bug report #662712, regarding fracplanet: FTBFS against Qt 4.8 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.) -- 662712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fracplanet Version: 0.4.0-1.1 User: debian-qt-...@lists.debian.org Usertags: qt48-transition Hi, Your package fails to build against Qt 4.8 which is currently in experimental. The transition to unstable/testing is tracked in bug #653903. I'm attaching a patch by Andreas Moog that contains the necessary changes. It can be applied even before Qt 4.8 enters unstable. Build log: > g++ -c -include obj/fracplanet -m64 -pipe -O2 -DFRACPLANET_VERSION="0.4.0" > -DFRACPLANET_BUILD="0.4.0 (release build)" -DNDEBUG -DQT_NO_ASCII_CAST > -D_REENTRANT -Wall -W > -DQT_DLL -DQT_NO_DEBUG -DQT_OPENGL_LIB -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/QtOpenGL -I/usr/include/qt4 -I/usr/X11R6/include -Imoc -o > obj/triangle_mesh_viewer_display.o triangle_mesh_viewer_display.cpp > triangle_mesh_viewer_display.cpp: In member function 'virtual void > TriangleMeshViewerDisplay::paintGL()': > triangle_mesh_viewer_display.cpp:149:6: error: 'gluLookAt' was not declared > in this scope > triangle_mesh_viewer_display.cpp: In member function 'virtual void > TriangleMeshViewerDisplay::resizeGL(int, int)': > triangle_mesh_viewer_display.cpp:456:6: error: 'gluPerspective' was not > declared in this scope > make[1]: *** [obj/triangle_mesh_viewer_display.o] Error 1 Regards, Felix Description: Import glu.h to build against qt4.8 Author: Andreas Moog Bug-Ubuntu: https://launchpad.net/bugs/935091 Index: fracplanet/triangle_mesh_viewer_display.cpp === --- fracplanet.orig/triangle_mesh_viewer_display.cpp 2012-02-25 19:07:23.0 +0100 +++ fracplanet/triangle_mesh_viewer_display.cpp 2012-02-25 19:07:23.0 +0100 @@ -24,6 +24,8 @@ #include "matrix33.h" #include "triangle_mesh_viewer.h" +#include + TriangleMeshViewerDisplay::TriangleMeshViewerDisplay(TriangleMeshViewer* parent,const QGLFormat& format,const ParametersRender* param,const std::vector& m,bool verbose) :QGLWidget(format,parent) ,_notify(*parent) Index: fracplanet/fracplanet.pro === --- fracplanet.orig/fracplanet.pro 2012-02-25 19:11:13.857517000 +0100 +++ fracplanet/fracplanet.pro 2012-02-25 19:11:32.498508269 +0100 @@ -8,7 +8,7 @@ HEADERS += $$system(ls *.h) SOURCES += $$system(ls *.cpp) -LIBS += -lboost_program_options +LIBS += -lboost_program_options -lGLU DEFINES += QT_DLL --- End Message --- --- Begin Message --- Source: fracplanet Source-Version: 0.4.0-2 We believe that the bug you reported is fixed in the latest version of fracplanet, which is due to be installed in the Debian FTP archive: fracplanet_0.4.0-2.debian.tar.gz to main/f/fracplanet/fracplanet_0.4.0-2.debian.tar.gz fracplanet_0.4.0-2.dsc to main/f/fracplanet/fracplanet_0.4.0-2.dsc fracplanet_0.4.0-2_i386.deb to main/f/fracplanet/fracplanet_0.4.0-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 662...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated fracplanet 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, 08 May 2012 22:38:42 -0400 Source: fracplanet Binary: fracplanet Architecture: source i386 Version: 0.4.0-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Scott Kitterman Description: fracplanet - Fractal planet generator Closes: 662712 Changes: fracplanet (0.4.0-2) unstable; urgency=low . * QA upload. * Orphaned package, see #661455, set maintainer to Debian QA Group * Add missing include to fix FTBFS with Qt 4.8 (Closes: #662712) - Thanks to Andreas Moog from Ubuntu for the patch and to Felix Geyer for for
Bug#671800: xserver-xorg-video-savage: segfaults under X.Org X Server 1.12.1
Hi On Wednesday 09 May 2012, Julien Cristau wrote: > On Mon, May 7, 2012 at 09:08:54 +0200, Tormod Volden wrote: […] > > Wow, a savage user! I am hoping to get a newer savage version done > > soon, unless someone beats me to it. Anyway, this issue might be > > outside the driver. Do you have libpciaccess 13.1? This is in my > > experience necessary in order to run xserver 1.12. > > > We need c3eaacd25358c225e355a1ea7d64dece8188b69a, which is in savage > 2.3.4. Thanks a lot, xserver-xorg-video-savage 1:2.3.4-1 is working perfectly. Regards Stefan Lippers-Hollmann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: limit source to krb5, tagging 660869, tagging 670457, tagging 670918, tagging 672075
Processing commands for cont...@bugs.debian.org: > #krb5 (1.10.1+dfsg-1) unstable; urgency=low > # > # * Fix use counts on preauthentication, Closes: #670457 > # * Fix kadmin access controls, Closes: #670918 > # * Fix history from old databases, Closes: #660869 > # * Fix gcc 4.6.2 may be used uninitialized warnings/errors, Closes: #672075 > # > limit source krb5 Limiting to bugs with field 'source' containing at least one of 'krb5' Limit currently set to 'source':'krb5' > tags 660869 + pending Bug #660869 [krb5-kdc] krb5-kdc: Cannot change passwords if password history is used Added tag(s) pending. > tags 670457 + pending Bug #670457 [libkrb5-3] libkrb5-3: after failed auth, subsequent auths in the same context fail Added tag(s) pending. > tags 670918 + pending Bug #670918 [krb5] CVE-2012-1012 Added tag(s) pending. > tags 672075 + pending Bug #672075 [src:krb5] krb5: FTBFS: deltat.c:1694:12: error: 'yylval' may be used uninitialized in this function [-Werror=maybe-uninitialized] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 660869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660869 670457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670457 670918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670918 672075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672075 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: add patch
Processing commands for cont...@bugs.debian.org: > tags 672055 + patch Bug #672055 [src:libstxxl] libstxxl: FTBFS: mlock.cpp:32:32: error: 'sleep' was not declared in this scope Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 672055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672055 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#672055: add patch
tags 672055 + patch
thanks
diff -Nru libstxxl-1.3.1/debian/changelog libstxxl-1.3.1/debian/changelog
--- libstxxl-1.3.1/debian/changelog 2012-02-18 14:40:48.0 +
+++ libstxxl-1.3.1/debian/changelog 2012-05-09 00:51:21.0 +
@@ -1,3 +1,10 @@
+libstxxl (1.3.1-2.1) unstable; urgency=low
+
+ * Non maintainer upload
+ * Fix build failure with GCC 4.7. Closes: #672055.
+
+ -- Matthias Klose Wed, 09 May 2012 00:50:24 +
+
libstxxl (1.3.1-2) unstable; urgency=low
* Team upload
diff -Nru libstxxl-1.3.1/debian/patches/gcc-4.7.diff
libstxxl-1.3.1/debian/patches/gcc-4.7.diff
--- libstxxl-1.3.1/debian/patches/gcc-4.7.diff 1970-01-01 00:00:00.0
+
+++ libstxxl-1.3.1/debian/patches/gcc-4.7.diff 2012-05-09 00:52:08.0
+
@@ -0,0 +1,12 @@
+Index: libstxxl-1.3.1/utils/mlock.cpp
+===
+--- libstxxl-1.3.1.orig/utils/mlock.cpp2010-08-31 12:22:17.0
+
libstxxl-1.3.1/utils/mlock.cpp 2012-05-09 00:52:06.136011616 +
+@@ -17,6 +17,7 @@
+ #include
+ #include
+ #include
++#include
+
+ int main(int argc, char ** argv)
+ {
diff -Nru libstxxl-1.3.1/debian/patches/series
libstxxl-1.3.1/debian/patches/series
--- libstxxl-1.3.1/debian/patches/series2012-02-18 14:24:18.0
+
+++ libstxxl-1.3.1/debian/patches/series2012-05-09 00:51:26.0
+
@@ -1 +1,2 @@
enable-shared.patch
+gcc-4.7.diff
Processed: affects 672167, affects 672170, affects 670422, reopening 670495, severity of 660598 is serious ...
Processing commands for cont...@bugs.debian.org:
> affects 672167 + ttf-bpg-georgian-fonts
Bug #672167 [fonts-bpg-georgian] fonts-bpg-georgian: fails to upgrade from
'testing' - trying to overwrite
/usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Rioni.ttf
Added indication that 672167 affects ttf-bpg-georgian-fonts
> affects 672170 + quantum-plugin-cisco quantum-plugin-linuxbridge
> quantum-plugin-openvswitch quantum-plugin-ryu
Bug #672170 [python-quantum] python-quantum: fails to upgrade from 'testing' -
trying to overwrite /usr/share/pyshared/quantum/plugins/cisco/run_tests.py
Added indication that 672170 affects quantum-plugin-cisco,
quantum-plugin-linuxbridge, quantum-plugin-openvswitch, and quantum-plugin-ryu
> affects 670422 + libstarpu-contrib-dev
Bug #670422 [libstarpu-dev] libstarpu-dev: uninstallable in sid: too strict gcc
dependency
Added indication that 670422 affects libstarpu-contrib-dev
> reopen 670495
Bug #670495 {Done: Olivier Sallou } [biomaj-watcher]
biomaj-watcher: fails to upgrade from testing: ln: failed to create symbolic
link `/usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/gnumail.jar': File
exists
Bug reopened
Ignoring request to alter fixed versions of bug #670495 to the same values
previously set
> severity 660598 serious
Bug #660598 [sdic] sdic: fails to install - emacs-package-install fails
Severity set to 'serious' from 'normal'
> tags 660598 - moreinfo unreproducible
Bug #660598 [sdic] sdic: fails to install - emacs-package-install fails
Removed tag(s) unreproducible and moreinfo.
> affects 670494 + ptex-jtex
Bug #670494 [ptex-bin] ptex-bin: leaves diversions after upgrade from squeeze
Ignoring request to set affects of bug 670494 to the same value previously set
> found 670494 ptex-jtex/1.7+1-13
Bug #670494 [ptex-bin] ptex-bin: leaves diversions after upgrade from squeeze
Marked as found in versions ptex-jtex/1.7+1-13.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was deb...@abeckmann.de).
> usertags 669271 piuparts
Bug#669271: libreoffice creates big directory structure in /root
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
660598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660598
669271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669271
670422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670422
670494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670494
670495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670495
672167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672167
672170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#670918: CVE-2012-1012
Processing commands for cont...@bugs.debian.org: > severity 670918 normal Bug #670918 [krb5] CVE-2012-1012 Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 670918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670918 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#670918: CVE-2012-1012
severity 670918 normal thanks > "Moritz" == Moritz Muehlenhoff writes: Moritz> Package: krb5 Severity: grave Tags: security Moritz> Please see Moritz> https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-1012 Moritz> for details I agree that Debian has the bug, but as Redhat points out there's not a security impact unless you're using string attributes, which the core code (and that in Debian ) doesn't use. So, I think this is not RC. -- 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
Processing commands for cont...@bugs.debian.org: > tags 672100 + patch Bug #672100 [src:presage] presage: FTBFS: profileManagerTest.cpp:86:47: error: 'unlink' was not declared in this scope Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 672100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672100 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: add patch
Processing commands for cont...@bugs.debian.org: > tags 672076 + patch Bug #672076 [src:libshevek] libshevek: FTBFS: src/file.cc:47:7: error: '::close' has not been declared Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 672076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672076 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#672076: add patch
tags 672076 + patch
thanks
diff -u libshevek-1.2/debian/changelog libshevek-1.2/debian/changelog
--- libshevek-1.2/debian/changelog
+++ libshevek-1.2/debian/changelog
@@ -1,3 +1,10 @@
+libshevek (1.2-1.1) unstable; urgency=low
+
+ * Non maintainer upload.
+ * Fix build failure with GCC 4.7. Closes: #672076.
+
+ -- Matthias Klose Tue, 08 May 2012 23:16:26 +
+
libshevek (1.2-1) unstable; urgency=low
* Remove build dependencies; let them be added to doxygen-latex instead.
only in patch2:
unchanged:
--- libshevek-1.2.orig/src/telnet.cc
+++ libshevek-1.2/src/telnet.cc
@@ -16,6 +16,7 @@
*/
#include "telnet.hh"
+#include
namespace shevek
{
@@ -79,7 +80,7 @@
return &options[i];
}
// the type will be used in responses, so set it to the correct value
-nop_option.type = opt;
+nop_option.type = (enum option) opt;
return &nop_option;
}
only in patch2:
unchanged:
--- libshevek-1.2.orig/src/telnet.hh
+++ libshevek-1.2/src/telnet.hh
@@ -63,7 +63,7 @@
typedef void (telnet::*action)(option_t *opt);
struct option_t
{
- char type;
+ enum option type;
action will, wont, doo, dont;
bool here, there, not_both;
};
only in patch2:
unchanged:
--- libshevek-1.2.orig/src/socket.cc
+++ libshevek-1.2/src/socket.cc
@@ -17,6 +17,7 @@
#include "socket.hh"
#include "error.hh"
+#include
namespace shevek
{
only in patch2:
unchanged:
--- libshevek-1.2.orig/src/process.cc
+++ libshevek-1.2/src/process.cc
@@ -20,6 +20,7 @@
#include "debug.hh"
#include
#include
+#include
extern "C"
{
only in patch2:
unchanged:
--- libshevek-1.2.orig/src/file.cc
+++ libshevek-1.2/src/file.cc
@@ -20,6 +20,7 @@
#include
#include
#include
+#include
namespace shevek
{
Bug#672100: add patch
tags 672100 + patch thanks diff -Nru presage-0.8.7/debian/changelog presage-0.8.7/debian/changelog --- presage-0.8.7/debian/changelog 2011-10-23 16:23:26.0 + +++ presage-0.8.7/debian/changelog 2012-05-08 22:45:24.0 + @@ -1,3 +1,10 @@ +presage (0.8.7-1.1) unstable; urgency=low + + * Non maintainer upload + * Fix build failure with GCC 4.7. Closes: #672100. + + -- Matthias Klose Tue, 08 May 2012 22:41:56 + + presage (0.8.7-1) unstable; urgency=low * New upstream release. diff -Nru presage-0.8.7/debian/patches/ftbfs-gcc-4.7.diff presage-0.8.7/debian/patches/ftbfs-gcc-4.7.diff --- presage-0.8.7/debian/patches/ftbfs-gcc-4.7.diff 1970-01-01 00:00:00.0 + +++ presage-0.8.7/debian/patches/ftbfs-gcc-4.7.diff 2012-05-08 22:52:15.0 + @@ -0,0 +1,27 @@ +Index: presage-0.8.7/test/lib/core/profileManagerTest.cpp +=== +--- presage-0.8.7.orig/test/lib/core/profileManagerTest.cpp2010-04-13 17:52:47.0 + presage-0.8.7/test/lib/core/profileManagerTest.cpp 2012-05-08 22:44:46.823256668 + +@@ -30,6 +30,7 @@ + #include "core/predictorActivator.h" + #include "core/selector.h" + ++#include + #include + + CPPUNIT_TEST_SUITE_REGISTRATION( ProfileManagerTest ); +Index: presage-0.8.7/test/lib/predictors/smoothedNgramPredictorTest.cpp +=== +--- presage-0.8.7.orig/test/lib/predictors/smoothedNgramPredictorTest.cpp 2010-04-14 17:20:38.0 + presage-0.8.7/test/lib/predictors/smoothedNgramPredictorTest.cpp 2012-05-08 22:52:12.870836609 + +@@ -23,9 +23,7 @@ + + + // for unlink(), getcwd() +-#ifdef HAVE_UNISTD_H +-# include +-#endif ++#include + + #include "smoothedNgramPredictorTest.h" + diff -Nru presage-0.8.7/debian/patches/series presage-0.8.7/debian/patches/series --- presage-0.8.7/debian/patches/series 1970-01-01 00:00:00.0 + +++ presage-0.8.7/debian/patches/series 2012-05-08 22:42:53.0 + @@ -0,0 +1 @@ +ftbfs-gcc-4.7.diff
Processed: add patch
Processing commands for cont...@bugs.debian.org: > tags 672086 + patch Bug #672086 [src:libsfml] libsfml: FTBFS: Linux/Joystick.cpp:103:62: error: 'read' was not declared in this scope Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 672086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672086 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: add patch
Processing commands for cont...@bugs.debian.org: > tags 672021 + patch Bug #672021 [src:libpqxx3] 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] Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 672021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672021 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#672086: add patch
tags 672086 + patch thanks diff -u libsfml-1.6+dfsg1/debian/changelog libsfml-1.6+dfsg1/debian/changelog --- libsfml-1.6+dfsg1/debian/changelog +++ libsfml-1.6+dfsg1/debian/changelog @@ -1,3 +1,10 @@ +libsfml (1.6+dfsg1-2.2) unstable; urgency=low + + * Non-maintainer upload. + * Fix build failure with GCC 4.7. Closes: #672086. + + -- Matthias Klose Tue, 08 May 2012 22:54:35 + + libsfml (1.6+dfsg1-2.1) unstable; urgency=low * Non-maintainer upload. diff -u libsfml-1.6+dfsg1/debian/patches/series libsfml-1.6+dfsg1/debian/patches/series --- libsfml-1.6+dfsg1/debian/patches/series +++ libsfml-1.6+dfsg1/debian/patches/series @@ -6,0 +7 @@ +debian/gcc-4.7.diff only in patch2: unchanged: --- libsfml-1.6+dfsg1.orig/debian/patches/debian/gcc-4.7.diff +++ libsfml-1.6+dfsg1/debian/patches/debian/gcc-4.7.diff @@ -0,0 +1,12 @@ +Index: libsfml-1.6+dfsg1/src/SFML/Window/Linux/Joystick.cpp +=== +--- libsfml-1.6+dfsg1.orig/src/SFML/Window/Linux/Joystick.cpp 2010-01-27 14:00:27.0 + libsfml-1.6+dfsg1/src/SFML/Window/Linux/Joystick.cpp 2012-05-08 22:59:40.098386041 + +@@ -27,6 +27,7 @@ + + #include + #include ++#include + + + namespace sf
Bug#672021: add patch
tags 672021 + patch thanks diff -Nru libpqxx3-3.1/debian/changelog libpqxx3-3.1/debian/changelog --- libpqxx3-3.1/debian/changelog 2011-11-28 21:33:40.0 + +++ libpqxx3-3.1/debian/changelog 2012-05-08 23:47:30.0 + @@ -1,3 +1,10 @@ +libpqxx3 (3.1-1.1) unstable; urgency=low + + * Non maintainer upload + * Work around build failure with GCC 4.7. Closes: #672021. + + -- Matthias Klose Tue, 08 May 2012 23:44:51 + + libpqxx3 (3.1-1) unstable; urgency=low [ Marcin Kulisz ] diff -Nru libpqxx3-3.1/debian/rules libpqxx3-3.1/debian/rules --- libpqxx3-3.1/debian/rules 2011-11-28 21:36:48.0 + +++ libpqxx3-3.1/debian/rules 2012-05-08 23:50:38.0 + @@ -3,6 +3,8 @@ #export DH_VERBOSE=1 export LIBRARY_VERSION=3.1 +CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) -fpermissive + %: dh $@
Processed: add patch
Processing commands for cont...@bugs.debian.org: > tags 672074 + patch Bug #672074 [src:libgwenhywfar] libgwenhywfar: FTBFS: libtest.cpp:117:14: error: 'sleep' was not declared in this scope Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 672074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672074 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#672074: add patch
tags 672074 + patch
thanks
diff -u libgwenhywfar-4.3.1/debian/changelog
libgwenhywfar-4.3.1/debian/changelog
--- libgwenhywfar-4.3.1/debian/changelog
+++ libgwenhywfar-4.3.1/debian/changelog
@@ -1,3 +1,10 @@
+libgwenhywfar (4.3.1-1.1) unstable; urgency=low
+
+ * Non maintainer upload
+ * Fix build failure with GCC 4.7. Closes: #672074.
+
+ -- Matthias Klose Tue, 08 May 2012 23:33:25 +
+
libgwenhywfar (4.3.1-1) unstable; urgency=low
* New upstream release
only in patch2:
unchanged:
--- libgwenhywfar-4.3.1.orig/gui/qt4/libtest.cpp
+++ libgwenhywfar-4.3.1/gui/qt4/libtest.cpp
@@ -10,6 +10,7 @@
#include
#include
+#include
int test1(int argc, char **argv) {
only in patch2:
unchanged:
--- libgwenhywfar-4.3.1.orig/gui/fox16/libtest.cpp
+++ libgwenhywfar-4.3.1/gui/fox16/libtest.cpp
@@ -8,6 +8,7 @@
# define sleep(x) Sleep(x)
#endif
+#include
#undef BUILDING_FOX16_GUI
Bug#672189: python3-dbus: does not depend on python3
Package: python3-dbus Version: 1.0.0-1 Severity: serious Justification: Policy 3.5 python3-dbus doesn't depend on python3 and doesn't byte-compile its Python modules. Perhaps you should use dh_python3? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672181: itrans: uninstallable in sid
Package: itrans Version: 5.3-10 Severity: grave Tags: sid Justification: renders package unusable User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: * tex-common breaks itrans (<= 5.3-10) It was already removed from testing: http://packages.qa.debian.org/i/itrans/news/20120505T163910Z.html Cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672179: kmail: Kmail can not launch slaves
Package: kmail Version: 4:4.4.11.1+l10n-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropiate *** * What led up to the situation? Upgrading kernel and unrelated software * What exactly did you do (or not do) that was effective (or ineffective)? Upgrading KDE software was uneffective * What was the outcome of this action? none * What outcome did you expect instead? Kmail working normally *** End of the template - remove these lines *** When I launch kmail it can not open pop accounts nor imap accounts, nor send e-mails out. Launching it from a konsole shows the errors: impossible to create slaves. See below: user@host:~$ kmail Unable to load library icui18n "Cannot load library icui18n: (libicui18n.so.48: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio)" QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work kmail(29438)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kmail(29438)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: user@host:~$ kmail(29438)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory! kmail(29438)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory! kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «file». " kmail(29438): couldn't create slave: "Imposible crear esclavo de E/S: Klauncher devolvió: Protocolo desconocido «imap». " kmail(29438)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdeui (Wallet): The kwalletd service has been disabled kmail(29438)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: user@host:~$ -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kmail depends on: ii kdebase-runtime 4:4.7.4-2 ii kdepim-runtime 4:4.4.11.1-2 ii kdepimlibs-kio-plugins 4:4.7.4-2+b1 ii libakonadi-contact4 4:4.7.4-2+b1 ii libakonadi-kde4 4:4.7.4-2+b1 ii libc6 2.13-20 ii libgcc1 1:4.6.1-10 ii libgpgme++2 4:4.7.4-2+b1 ii libkabc44:4.7.4-2+b1 ii libkcal4
Bug#672177: libsdl-ruby: uninstallable in sid
Package: libsdl-ruby Version: 2.1.1.1-1 Severity: grave Tags: sid Justification: renders package unusable User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: * ruby-sdl breaks libsdl-ruby (<< 2.1.1.1-2~) * libsdl-ruby depends on ruby-sdl via libsdl-ruby1.8 As libsdl-ruby was renamed to ruby-sdl, but there is no transitional package for libsdl-ruby, maybe libsdl-ruby should be removed from sid? Cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672002: marked as done (yoshimi: FTBFS: JackEngine.cpp:53:24: error: 'usleep' was not declared in this scope)
Your message dated Tue, 08 May 2012 23:20:24 + with message-id and subject line Bug#672002: fixed in yoshimi 0.060.12-2 has caused the Debian Bug report #672002, regarding yoshimi: FTBFS: JackEngine.cpp:53:24: error: 'usleep' 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.) -- 672002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yoshimi Version: 0.060.12-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: > /usr/bin/c++ -DYOSHI_FIFO_DIR=\"/dev/shm\" -DMAX_BANK_ROOT_DIRS=128 > -DMAX_AD_HARMONICS=128 -DMAX_SUB_HARMONICS=64 -DPAD_MAX_SAMPLES=64 > -DNUM_MIDI_PARTS=16 -DNUM_MIDI_CHANNELS=16 -DMAX_ENVELOPE_POINTS=40 > -DPI=3.1415926536f -DLOG_2=0.693147181f -DNUM_VOICES=8 -DPOLIPHONY=60 > -DNUM_SYS_EFX=4 -DNUM_INS_EFX=8 -DNUM_PART_EFX=3 -DNUM_KIT_ITEMS=16 > -DVELOCITY_MAX_SCALE=8.0f -DMAX_EQ_BANDS=8 -DMAX_FILTER_STAGES=5 > -DFF_MAX_VOWELS=6 -DFF_MAX_FORMANTS=12 -DFF_MAX_SEQUENCE=8 > -DMAX_PHASER_STAGES=12 -DMAX_ALIENWAH_DELAY=100 -DDEFAULT_AUDIO=jack_audio > -DDEFAULT_MIDI=jack_midi -DJACK_SESSION -DJACK_LATENCY -O3 -ffast-math > -fomit-frame-pointer -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu > -I/«PKGBUILDDIR»/src -I/usr/include/alsa -I/usr/lib/fltk > -D'YOSHIMI_VERSION="0.060.12"' -D'BASE_INSTALL_DIR="/usr"' -lasound -ljack > -lpthread -lrt -o CMakeFiles/yoshimi.dir/MusicIO/AlsaClient.cpp.o -c > /«PKGBUILDDIR»/src/MusicIO/AlsaClient.cpp > /usr/bin/cmake -E cmake_progress_report > /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 80 > /«PKGBUILDDIR»/src/MusicIO/JackEngine.cpp: In member function 'bool > JackEngine::connectServer(std::string)': > /«PKGBUILDDIR»/src/MusicIO/JackEngine.cpp:53:24: error: 'usleep' was not > declared in this scope > /«PKGBUILDDIR»/src/MusicIO/JackEngine.cpp: In member function 'void* > JackEngine::midiThread()': > /«PKGBUILDDIR»/src/MusicIO/JackEngine.cpp:407:16: warning: converting 'false' > to pointer type 'void*' [-Wconversion-null] > [ 79%] Building CXX object CMakeFiles/yoshimi.dir/MusicIO/JackAlsaClient.cpp.o > /usr/bin/c++ -DYOSHI_FIFO_DIR=\"/dev/shm\" -DMAX_BANK_ROOT_DIRS=128 > -DMAX_AD_HARMONICS=128 -DMAX_SUB_HARMONICS=64 -DPAD_MAX_SAMPLES=64 > -DNUM_MIDI_PARTS=16 -DNUM_MIDI_CHANNELS=16 -DMAX_ENVELOPE_POINTS=40 > -DPI=3.1415926536f -DLOG_2=0.693147181f -DNUM_VOICES=8 -DPOLIPHONY=60 > -DNUM_SYS_EFX=4 -DNUM_INS_EFX=8 -DNUM_PART_EFX=3 -DNUM_KIT_ITEMS=16 > -DVELOCITY_MAX_SCALE=8.0f -DMAX_EQ_BANDS=8 -DMAX_FILTER_STAGES=5 > -DFF_MAX_VOWELS=6 -DFF_MAX_FORMANTS=12 -DFF_MAX_SEQUENCE=8 > -DMAX_PHASER_STAGES=12 -DMAX_ALIENWAH_DELAY=100 -DDEFAULT_AUDIO=jack_audio > -DDEFAULT_MIDI=jack_midi -DJACK_SESSION -DJACK_LATENCY -O3 -ffast-math > -fomit-frame-pointer -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu > -I/«PKGBUILDDIR»/src -I/usr/include/alsa -I/usr/lib/fltk > -D'YOSHIMI_VERSION="0.060.12"' -D'BASE_INSTALL_DIR="/usr"' -lasound -ljack > -lpthread -lrt -o CMakeFiles/yoshimi.dir/MusicIO/JackAlsaClient.cpp.o -c > /«PKGBUILDDIR»/src/MusicIO/JackAlsaClient.cpp > /usr/bin/cmake -E cmake_progress_report > /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles > make[3]: *** [CMakeFiles/yoshimi.dir/MusicIO/JackEngine.cpp.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/yoshimi_0.060.12-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 --- --- Begin Message --- Source: yoshimi Source-Version: 0.060.12-2 We believe that the bug you reported is fixed in the latest version of yoshimi, which is due to be installed in the Debian FTP archive: yoshimi-data_0.060.12-2_all.deb to main/y/yoshimi/yoshimi-data_0.060.12-2_all.deb yoshimi-dbg_0.060.12-2_amd64.deb to main/y/yoshimi/yoshimi-dbg_0.060.12-2_amd64.deb yoshimi_0.060.12-2.debi
Bug#670495: biomaj-watcher: fails to upgrade from testing: ln: failed to create symbolic link `/usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/gnumail.jar': File exists
Package: biomaj-watcher Version: 1.2.0-6 Followup-For: Bug #670495 Hi, the problem is still present in 1.2.0-6: Setting up biomaj-watcher (1.2.0-6) ... Updating Context.xml... Configuration complete ln: failed to create symbolic link `/usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/gnumail.jar': File exists dpkg: error processing biomaj-watcher (--configure): subprocess installed post-installation script returned error exit status 1 Andreas biomaj-watcher_1.2.0-6.log.gz Description: GNU Zip compressed data
Bug#672170: python-quantum: fails to upgrade from 'testing' - trying to overwrite /usr/share/pyshared/quantum/plugins/cisco/run_tests.py
Package: python-quantum
Version: 2012.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'unstable' 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
This problem is exposed during the upgrade of the 'quantum-plugin-cisco'
package, not by upgrading only the buggy package itself.
In order to have piuparts automatically track this problem, I'll mark
this bug as Affects/Found in the exposing package(s), too.
>From the attached log (scroll to the bottom...):
Selecting previously unselected package python-quantum.
Unpacking python-quantum (from .../python-quantum_2012.1-2_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/python-quantum_2012.1-2_all.deb (--unpack):
trying to overwrite
'/usr/share/pyshared/quantum/plugins/cisco/run_tests.py', which is also in
package quantum-plugin-cisco 2012.1-1
configured to not write apport reports
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to replace quantum-plugin-cisco 2012.1-1 (using
.../quantum-plugin-cisco_2012.1-2_all.deb) ...
Unpacking replacement quantum-plugin-cisco ...
Errors were encountered while processing:
/var/cache/apt/archives/python-quantum_2012.1-2_all.deb
A similar problem seems to affect
quantum-plugin-{linuxbridge,nicira,openvswitch,ryu,sample}
cheers,
Andreas
quantum-plugin-cisco_2012.1-2.log.gz
Description: GNU Zip compressed data
Bug#672167: fonts-bpg-georgian: fails to upgrade from 'testing' - trying to overwrite /usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Rioni.ttf
Package: fonts-bpg-georgian Version: 0.5a-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'unstable' 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 This problem is exposed during the upgrade of the 'ttf-bpg-georgian-fonts' package, not by upgrading only the buggy package itself. In order to have piuparts automatically track this problem, I'll mark this bug as Affects/Found in the exposing package(s), too. >From the attached log (scroll to the bottom...): Preparing to replace fonts-bpg-georgian 0.5a-2 (using .../fonts-bpg-georgian_0.5a-4_all.deb) ... Unpacking replacement fonts-bpg-georgian ... dpkg: error processing /var/cache/apt/archives/fonts-bpg-georgian_0.5a-4_all.deb (--unpack): trying to overwrite '/usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Rioni.ttf', which is also in package ttf-bpg-georgian-fonts 0.5a-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) configured to not write apport reports Preparing to replace ttf-bpg-georgian-fonts 0.5a-2 (using .../ttf-bpg-georgian-fonts_0.5a-4_all.deb) ... Unpacking replacement ttf-bpg-georgian-fonts ... Errors were encountered while processing: /var/cache/apt/archives/fonts-bpg-georgian_0.5a-4_all.deb cheers, Andreas ttf-bpg-georgian-fonts_0.5a-4.log.gz Description: GNU Zip compressed data
Bug#672085: qof: ftbfs with GCC-4.7
On 08.05.2012 22:21, Neil Williams wrote: > tag 672085 + help quit > > On Tue, 08 May 2012 18:57:52 + Matthias Klose wrote: > >> user debian-...@lists.debian.org usertags 672085 + ftbfs-gcc-4.7 thanks >> >> The build failure is exposed by building with gcc-4.7/g++-4.7, which is >> now the default gcc/g++ on x86 architectures. >> >> Some hints on fixing these issues can be found at >> http://gcc.gnu.org/gcc-4.7/porting_to.html > > This particular issue isn't covered in those hints, it's an internal MD5 > process which is the same as the internal MD5 code in eglibc. > > I could hide the problem by dropping -Werror or adding -fno-strict-aliasing > but it's not clear to me why the same code compiles in eglibc and not in > qof, especially when eglibc is passing -fstrict-aliasing. eglibc doesn't use the default compiler, but the warning is still seen when building a recent libiberty (e.g. in gcc-4.7, or gcc-snapshot). forwarded to http://gcc.gnu.org/PR53285 for now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: affects 671716
Processing commands for cont...@bugs.debian.org: > affects 671716 + texlive-full Bug #671716 [texlive-latex-base] texlive-latex-base: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man1/mptopdf.1.gz Added indication that 671716 affects texlive-full > thanks Stopping processing here. Please contact me if you need assistance. -- 671716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671716 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#671124: initscripts: Fails to update due to mountoverflowtmp
Roger Leigh (08/05/2012): > On Wed, May 02, 2012 at 01:15:42AM +0200, Cyril Brulebois wrote: > > Preparing to replace initscripts 2.88dsf-22 (using > > .../initscripts_2.88dsf-22.1_amd64.deb) ... > > Unpacking replacement initscripts ... > > Processing triggers for man-db ... > > Setting up initscripts (2.88dsf-22.1) ... > > update-rc.d: error: unable to read /etc/init.d/mountoverflowtmp > > dpkg: error processing initscripts (--configure): > > subprocess installed post-installation script returned error exit status 1 > > This is quite odd, because there were no changes to mountoverflowtmp > between 2.88dsf-22 and 2.88dsf-22.1. It was an NMU of debconf > template translations only, and there were no changes to > mountoverflowtmp for a long time (years) prior to this. > > In experimental in 2.88dsf-23, we did remove the mountoverflowtmp > script. Is it a possibility that you installed -23 and downgraded > to -22? It's a vague possibility that dpkg failed to reinstall > the conffile, and this resulted in update-rc.d failing due to the > script not being present. It doesn't seem like I ever had 2.88dsf-23. I might have killed that script manually because it caused me to lose time due to ENOSPC (no thanks for the crazy setup), but then this is /etc. Below, the output of: (zgrep initscripts dpkg.log*; grep initscripts dpkg.log*)|perl -pe 's/.*?://'|sort In the meanwhile, I worked around it with just a touch on it; then got a warning due to lack of +x bit (but that's only a very vague recollection, that might have been something else); and from that point I have been able to get back to work. Mraw, KiBi. -- 2011-05-16 11:57:53 status half-configured initscripts 2.88dsf-13.2 2011-05-16 11:57:53 status half-installed initscripts 2.88dsf-13.2 2011-05-16 11:57:53 status half-installed initscripts 2.88dsf-13.2 2011-05-16 11:57:53 status half-installed initscripts 2.88dsf-13.2 2011-05-16 11:57:53 status unpacked initscripts 2.88dsf-13.2 2011-05-16 11:57:53 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:53 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:53 upgrade initscripts 2.88dsf-13.2 2.88dsf-13.6 2011-05-16 11:57:55 configure initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:55 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:56 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status half-configured initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:57 status unpacked initscripts 2.88dsf-13.6 2011-05-16 11:57:59 status installed initscripts 2.88dsf-13.6 2011-05-23 13:12:13 status half-configured initscripts 2.88dsf-13.6 2011-05-23 13:12:13 status half-installed initscripts 2.88dsf-13.6 2011-05-23 13:12:13 status half-installed initscripts 2.88dsf-13.6 2011-05-23 13:12:13 status unpacked initscripts 2.88dsf-13.6 2011-05-23 13:12:13 upgrade initscripts 2.88dsf-13.6 2.88dsf-13.7 2011-05-23 13:12:14 status half-installed initscripts 2.88dsf-13.6 2011-05-23 13:12:14 status unpacked initscripts 2.88dsf-13.7 2011-05-23 13:12:14 status unpacked initscripts 2.88dsf-13.7 2011-05-23 13:12:15 configure initscripts 2.88dsf-13.7 2011-05-23 13:12:15 status unpacked initscripts 2.88dsf-13.7 20
Bug#672124: CVE-2011-3620
Hi, looks like this one: https://issues.apache.org/jira/browse/QPID-3652 which - according to the bug itself affects 0.12. Comparing the diff from https://reviews.apache.org/r/2988/diff/#index_header makes me wonder, because the changes are not present in 0.14, but in the upcoming 0.16 release. RedHat itself used the CVE to update from 0.12 to 0.14 - with a ~2MiB patch which includes the changes mentioned above. So my short midnight conclusion is that the fix is not included in the upstream 0.14 release and is therefor not included in the Debian packages currently in testing and unstable. I'm not sure how this is handled, because qpid is not in stable. There are a couple of compiling issues open that were caused by the GCC 4.7 migration, that will make it hard to re-compile the 0.14 without adding several patches. Because we're not in "stable", I personally tend to wait for the final 0.16 release that is sadly a couple of days late. It fixes this issue - and also the compilation problems. How to deal with this? Am 08.05.2012 19:40, schrieb Moritz Muehlenhoff: Package: qpid-cpp Severity: grave Tags: security The following was reported for qpid-cpp: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3620 I'm not sure if this affects the Debian package, please investigate. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672073: marked as done (q4wine: FTBFS: qtlocalpeer.cpp:103:54: error: '::getuid' has not been declared)
Your message dated Tue, 08 May 2012 22:04:08 + with message-id and subject line Bug#672073: fixed in q4wine 0.121-4 has caused the Debian Bug report #672073, regarding q4wine: FTBFS: qtlocalpeer.cpp:103:54: error: '::getuid' has not been declared 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.) -- 672073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: q4wine Version: 0.121-3 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: > make[4]: Entering directory `/«PKGBUILDDIR»/builddir' > [ 2%] [ 2%] [ 3%] [ 4%] Building CXX object > src/qtsingleapplication/CMakeFiles/qtsingleapp.dir/qtsingleapplication.cpp.o > Updating '../../../src/i18n/ru_ru.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Building CXX object > src/qtsingleapplication/CMakeFiles/qtsingleapp.dir/moc_qtsingleapplication.cxx.o > Building CXX object > src/qtsingleapplication/CMakeFiles/qtsingleapp.dir/qtlocalpeer.cpp.o > Building CXX object > src/qtsingleapplication/CMakeFiles/qtsingleapp.dir/moc_qtlocalpeer.cxx.o > Updating '../../../src/i18n/uk_ua.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '../../../src/i18n/pt_br.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '../../../src/i18n/es_es.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '../../../src/i18n/it_it.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '../../../src/i18n/cs_cz.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '../../../src/i18n/he_il.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '../../../src/i18n/pl_pl.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '../../../src/i18n/de_de.ts'... > Found 817 source text(s) (0 new and 817 already existing) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/en_us.qm'... > Generated 206 translation(s) (161 finished and 45 unfinished) > Ignored 611 untranslated source text(s) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/ru_ru.qm'... > Generated 817 translation(s) (817 finished and 0 unfinished) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/uk_ua.qm'... > Generated 814 translation(s) (814 finished and 0 unfinished) > Ignored 3 untranslated source text(s) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/pt_br.qm'... > Generated 816 translation(s) (814 finished and 2 unfinished) > Ignored 1 untranslated source text(s) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/es_es.qm'... > Generated 814 translation(s) (813 finished and 1 unfinished) > Ignored 3 untranslated source text(s) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/it_it.qm'... > Generated 816 translation(s) (814 finished and 2 unfinished) > Ignored 1 untranslated source text(s) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/cs_cz.qm'... > Generated 816 translation(s) (814 finished and 2 unfinished) > Ignored 1 untranslated source text(s) > Updating '/«PKGBUILDDIR»/builddir/src/i18n/he_il.qm'... > Generated 816 translation(s) (814 finished and 2 unfinished) > Ignored 1 untranslated source text(s) > /«PKGBUILDDIR»/src/qtsingleapplication/qtlocalpeer.cpp: In constructor > 'QtLocalPeer::QtLocalPeer(QObject*, const QString&)': > /«PKGBUILDDIR»/src/qtsingleapplication/qtlocalpeer.cpp:103:54: error: > '::getuid' has not been declared > /«PKGBUILDDIR»/src/qtsingleapplication/qtlocalpeer.cpp:103:54: note: > suggested alternative: > In file included from > /«PKGBUILDDIR»/src/qtsingleapplication/qtlockedfile_unix.cpp:49:0, > from > /«PKGBUILDDIR»/src/qtsingleapplication/qtlocalpeer.cpp:67: > /usr/include/unistd.h:694:16: note: 'QtLP_Private::getuid' > Updating '/«PKGBUILDDIR»/builddir/src/i18n/pl_pl.qm'... > Generated 816 translation(s) (814 finished and 2 unfinis
Bug#672012: marked as done (sdl-sound1.2: FTBFS: shn.c:1277: undefined reference to `log')
Your message dated Tue, 08 May 2012 22:04:23 + with message-id and subject line Bug#672012: fixed in sdl-sound1.2 1.0.3-6 has caused the Debian Bug report #672012, regarding sdl-sound1.2: FTBFS: shn.c:1277: undefined reference to `log' 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.) -- 672012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sdl-sound1.2 Version: 1.0.3-5 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: > gcc -shared .libs/SDL_sound.o .libs/alt_audio_convert.o > .libs/audio_convert.o .libs/extra_rwops.o -Wl,--whole-archive > decoders/.libs/libdecoders.a decoders/timidity/.libs/libtimidity.a > decoders/mpglib/.libs/libmpglib.a -Wl,--no-whole-archive > -L/usr/lib/x86_64-linux-gnu -lSDL -lmikmod > /usr/lib/x86_64-linux-gnu/libvorbis.so > /usr/lib/x86_64-linux-gnu/libvorbisfile.so -lFLAC -logg -lspeex -Wl,-z > -Wl,relro -Wl,--no-undefined -Wl,--as-needed -Wl,-soname > -Wl,libSDL_sound-1.0.so.1 -o .libs/libSDL_sound-1.0.so.1.0.2 > decoders/.libs/libdecoders.a(shn.o): In function `SHN_read': > /«PKGBUILDDIR»/decoders/shn.c:1277: undefined reference to `log' > decoders/timidity/.libs/libtimidity.a(instrum_dls.o): In function `to_msec': > /«PKGBUILDDIR»/decoders/timidity/instrum_dls.c:1097: undefined reference to > `pow' > decoders/timidity/.libs/libtimidity.a(mix.o): In function `update_tremolo': > /«PKGBUILDDIR»/decoders/timidity/mix.c:170: undefined reference to `sin' > decoders/timidity/.libs/libtimidity.a(resample.o): In function > `update_vibrato': > /«PKGBUILDDIR»/decoders/timidity/resample.c:269: undefined reference to `sin' > decoders/mpglib/.libs/libmpglib.a(libmpglib_la-tabinit.o): In function > `make_decode_tables': > /«PKGBUILDDIR»/decoders/mpglib/tabinit.c:43: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/tabinit.c:43: undefined reference to `cos' > decoders/mpglib/.libs/libmpglib.a(libmpglib_la-layer2.o): In function > `init_layer2': > /«PKGBUILDDIR»/decoders/mpglib/layer2.c:54: undefined reference to `pow' > decoders/mpglib/.libs/libmpglib.a(libmpglib_la-layer3.o): In function > `init_layer3': > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:111: undefined reference to `pow' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:114: undefined reference to `pow' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `sin' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `sin' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `sin' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `sin' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `sin' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `cos' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:177: undefined reference to `pow' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:106: undefined reference to `tan' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:173: undefined reference to `pow' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:179: undefined reference to `pow' > /«PKGBUILDDIR»/decoders/mpglib/layer3.c:119: undefined reference to `sqrt' > collect2: error: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/
Bug#670156: marked as done (xserver-xorg-core: input devices no longer detected)
Your message dated Tue, 08 May 2012 22:04:42 + with message-id and subject line Bug#669949: fixed in sysvinit 2.88dsf-24 has caused the Debian Bug report #669949, regarding xserver-xorg-core: input devices no longer detected 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.) -- 669949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-core Version: 2:1.11.4-1 Severity: normal Dear Maintainer, I can no longer use my keyboard/mouse after startx since X seems to no longer detect input devices. I'm not sure exactly what package is responsible since this started happening yesterday. Initially I was using a combination of unstable/experimental X packages, but since I've downgraded to just unstable the problem still persists. As noted in bug #585642 my devices are also missing ID_INPUT attributes for some reason. Let me know if I can provide anything more. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Apr 9 19:13 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2056560 Mar 4 17:44 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] Xorg X server configuration file status: -rw-r--r-- 1 root root 1356 Apr 22 10:16 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "ServerLayout" Identifier "Layout0" Screen "Screen0" EndSection #Section "Files" ## ModulePath "/usr/local/lib/xorg/modules" # ModulePath "/usr/lib/xorg/modules/" #EndSection Section "ServerFlags" Option "DefaultServerLayout" "Layout0" Option "DontZap" "off" Option "DRI2" "on" EndSection Section "Device" Identifier "ATI Radeon HD 4850" Driver "radeon" Option "Monitor-DVI-0" "dvi-0" Option "Monitor-DVI-1" "dvi-1" EndSection Section "Screen" Identifier "Screen0" Monitor "dvi-0" Device "ATI Radeon HD 4850" SubSection "Display" Virtual 4096 4096 EndSubSection EndSection Section "Monitor" Identifier "dvi-0" EndSection Section "Monitor" Identifier "dvi-1" Option "RightOf" "dvi-0" EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: #options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.3.0-trunk-amd64 (Debian 3.3.2-1~experimental.1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Apr 16 01:06:59 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 6428 Feb 25 2011 /var/log/Xorg.3.log -rw-r--r-- 1 root root 44211 Oct 20 2011 /var/log/Xorg.12.log -rw-r--r-- 1 root root 42164 Dec 15 09:15 /var/log/Xorg.1exit.log -rw-r--r-- 1 root root 46268 Apr 21 08:47 /var/log/Xorg.2.log -rw-r--r-- 1 root root 38047 Apr 22 09:00 /var/log/Xorg.1.log -rw-r--r-- 1 root root 38253 Apr 23 08:56 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 6581.588] X.Org X Server 1.11.4 Release Date: 2012-01-27 [ 6581.591] X Protocol Version 11, Revision 0 [ 6581.592] Build Operating System: Linux 3.2.0-1-amd64 x86_64 Debian [ 6581.593] Current Operating System: Linux robocomp 3.3.0-trunk-amd64 #1 SMP Mon Apr 16 01:06:59 UTC 2012 x86_64 [ 6581.594] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.3.0-trunk-amd64 root=UUID=4f6d38d8-
Bug#670644: marked as done (shotwell: Segfault once a photo is selected)
Your message dated Wed, 09 May 2012 00:02:48 +0200 with message-id <4fa99808.7000...@debian.org> and subject line Re: shotwell: Segfault once a photo is selected has caused the Debian Bug report #670644, regarding shotwell: Segfault once a photo is selected 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.) -- 670644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: shotwell Version: 0.12.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, As titled. Here's a stack trace. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux- gnu/i686/cmov/libthread_db.so.1". Core was generated by `shotwell'. Program terminated with signal 11, Segmentation fault. #0 0xb4cc9fcc in std::basic_string, std::allocator >::basic_string(std::string const&) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 (gdb) bt #0 0xb4cc9fcc in std::basic_string, std::allocator >::basic_string(std::string const&) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #1 0xb7565d21 in Exiv2::ExifKey::ExifKey(std::string const&) () from /usr/lib/libexiv2.so.9 #2 0xb7677c3b in gexiv2_metadata_get_exif_tag_rational () from /usr/lib/libgexiv2.so.1 #3 0x0811ccbd in photo_metadata_get_rational () #4 0x0811eeec in photo_metadata_get_exposure_string () #5 0x082a474c in ?? () #6 0x082a1d59 in properties_get_single_properties () #7 0x082a1f00 in ?? () #8 0x082a3e9a in ?? () #9 0x082a1b89 in properties_get_properties () #10 0x082a1c20 in ?? () #11 0x082a31c2 in ?? () #12 0x082a1959 in properties_internal_update_properties () #13 0x082a1acc in properties_update_properties () #14 0x081416ae in ?? () #15 0x080b8e13 in ?? () #16 0xb4dd42f0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #17 0xb4dd68aa in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #18 0xb4dd6cb5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #19 0xb4dd70fb in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #20 0xb57ebcb5 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 #21 0x08312976 in application_start () #22 0x081e9da7 in library_exec () #23 0x081eb3fe in _vala_main () #24 0x080b3848 in main () -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (50, 'experimental'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_HK.utf8, LC_CTYPE=en_HK.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages shotwell depends on: ii dbus-x11 1.5.12-1 ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii libatk1.0-0 2.4.0-2 ii libc62.13-30 ii libcairo-gobject21.10.2-7 ii libcairo21.10.2-7 ii libexif120.6.20-2 ii libexiv2-9 0.20-2.1 ii libfontconfig1 2.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-1 ii libgexiv2-1 0.4.1-1 ii libglib2.0-0 2.32.0-4 ii libgomp1 4.7.0-3 ii libgphoto2-2 2.4.13-2 ii libgphoto2-port0 2.4.13-2 ii libgstreamer-plugins-base0.10-0 0.10.36-1 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.2.3-1 ii libgudev-1.0-0 175-3.1 ii libjavascriptcoregtk-3.0-0 1.6.3-1 ii libpango1.0-01.29.4-3+b1 ii libraw2 0.13.8-1 ii librest-0.7-00.7.12-1 ii librsvg2-common 2.36.0-5 ii libsoup2.4-1 2.34.3-1 ii libsqlite3-0 3.7.11-2 ii libstdc++6 4.7.0-3 ii libunique-3.0-0 3.0.2-1 ii libwebkitgtk-3.0-0 1.6.3-1 ii libx11-6 2:1.4.4-4 ii libxml2 2.7.8.dfsg-9 shotwell recommends no packages. shotwell suggests
Bug#670085: marked as done (insserv: update-rc.d is a dangling symlink)
Your message dated Tue, 08 May 2012 22:04:42 + with message-id and subject line Bug#670085: fixed in sysvinit 2.88dsf-24 has caused the Debian Bug report #670085, regarding insserv: update-rc.d is a dangling symlink 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.) -- 670085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: insserv: update-rc.d is a dangling symlink Package: insserv Version: 1.14.0-3 Severity: grave Justification: renders package unusable Hello, While trying to debug another issue on my system I had to install xorg-dev which brought libvirt-bin 0.9.11-2 which failed to configure because update-rc.d was missing (in fact, a dangling symlink to /usr/sbin/update-rc.d-insserv which is missing). sysv-rc on my system is version 2.88dsf-22.1 which is >>2.87dsf-2, as the changelog mentions. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (999, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0-rc3-heidi (SMP w/2 CPU cores) Locale: LANG=ro_RO.utf8, LC_CTYPE=ro_RO.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages insserv depends on: ii libc6 2.13-27 insserv recommends no packages. Versions of packages insserv suggests: pn bootchart2 -- debconf information: * insserv/enable: true --- End Message --- --- Begin Message --- Source: sysvinit Source-Version: 2.88dsf-24 We believe that the bug you reported is fixed in the latest version of sysvinit, which is due to be installed in the Debian FTP archive: bootlogd_2.88dsf-24_amd64.deb to main/s/sysvinit/bootlogd_2.88dsf-24_amd64.deb initscripts_2.88dsf-24_amd64.deb to main/s/sysvinit/initscripts_2.88dsf-24_amd64.deb sysv-rc_2.88dsf-24_all.deb to main/s/sysvinit/sysv-rc_2.88dsf-24_all.deb sysvinit-utils_2.88dsf-24_amd64.deb to main/s/sysvinit/sysvinit-utils_2.88dsf-24_amd64.deb sysvinit_2.88dsf-24.debian.tar.gz to main/s/sysvinit/sysvinit_2.88dsf-24.debian.tar.gz sysvinit_2.88dsf-24.dsc to main/s/sysvinit/sysvinit_2.88dsf-24.dsc sysvinit_2.88dsf-24_amd64.deb to main/s/sysvinit/sysvinit_2.88dsf-24_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 670...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Leigh (supplier of updated sysvinit 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, 29 Apr 2012 23:52:14 +0100 Source: sysvinit Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd Architecture: source amd64 all Version: 2.88dsf-24 Distribution: experimental Urgency: low Maintainer: Debian sysvinit maintainers Changed-By: Roger Leigh Description: bootlogd - daemon to log boot messages initscripts - scripts for initializing and shutting down the system sysv-rc- System-V-like runlevel change mechanism sysvinit - System-V-like init utilities sysvinit-utils - System-V-like utilities Closes: 353229 437176 624391 660824 668307 669949 670085 Changes: sysvinit (2.88dsf-24) experimental; urgency=low . [ Roger Leigh ] * initscripts: - Don't generate or touch /etc/motd. Instead, the dynamic part of /etc/motd is created as /run/motd.dynamic, leaving /etc/motd entirely under the control of the system administrator. If /etc/motd is a symlink to /run/motd, /etc/motd.tail is moved back to /etc/motd. Closes: #353229, #624391, #668307. /etc/motd is not removed if initscripts is purged, since it's not owned by initscripts. - By default, /run/motd is just the output of uname, preserving the existing behaviour. However, should the administrator wish to include dynamic information in the motd, they may write scripts to update /run/motd.dynamic as they please. Closes: #437176. - motd generation is split from bootlogs into a separate motd init script. - bootlogs init script has been removed; current logging daemons handle this themselves, making this script redundant. - tmpfs mounts are never cleaned by bootclean.sh. Cleaning /run can lea
Bug#669949: marked as done (sysvinit: Break X11: no more mouse and keyboard)
Your message dated Tue, 08 May 2012 22:04:42 + with message-id and subject line Bug#669949: fixed in sysvinit 2.88dsf-24 has caused the Debian Bug report #669949, regarding sysvinit: Break X11: no more mouse and keyboard 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.) -- 669949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sysvinit Version: 2.88dsf-23 Severity: important After upgrade, X11 does not report any keybord or mouse on my laptop. If I plug a USB mouse its detected. If the USB mouse is plugged before X starts its not detected either. Probably related to hal/udev but... NB: I modified the /etc/defalt/tmpfs to get /tmp as a normal fs. # mount /tmp as a tmpfs. Defaults to yes; set to no to disable (/tmp # will then be part of the root filesystem). /tmp may also be # configured to be a separate mount in /etc/fstab. RAMTMP=no My xorg.conf is pretty slim: Section "InputClass" Identifier "touchpad catchall" Driver "evdev" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option"Emulate3Buttons""true" EndSection -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.2 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysvinit depends on: ii debianutils 4.3 ii initscripts 2.88dsf-23 ii libc6 2.13-30 ii libselinux1 2.1.9-4 ii libsepol1 2.1.4-3 ii sysv-rc 2.88dsf-23 ii sysvinit-utils 2.88dsf-22.1 sysvinit recommends no packages. sysvinit suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: sysvinit Source-Version: 2.88dsf-24 We believe that the bug you reported is fixed in the latest version of sysvinit, which is due to be installed in the Debian FTP archive: bootlogd_2.88dsf-24_amd64.deb to main/s/sysvinit/bootlogd_2.88dsf-24_amd64.deb initscripts_2.88dsf-24_amd64.deb to main/s/sysvinit/initscripts_2.88dsf-24_amd64.deb sysv-rc_2.88dsf-24_all.deb to main/s/sysvinit/sysv-rc_2.88dsf-24_all.deb sysvinit-utils_2.88dsf-24_amd64.deb to main/s/sysvinit/sysvinit-utils_2.88dsf-24_amd64.deb sysvinit_2.88dsf-24.debian.tar.gz to main/s/sysvinit/sysvinit_2.88dsf-24.debian.tar.gz sysvinit_2.88dsf-24.dsc to main/s/sysvinit/sysvinit_2.88dsf-24.dsc sysvinit_2.88dsf-24_amd64.deb to main/s/sysvinit/sysvinit_2.88dsf-24_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 669...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Leigh (supplier of updated sysvinit 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, 29 Apr 2012 23:52:14 +0100 Source: sysvinit Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd Architecture: source amd64 all Version: 2.88dsf-24 Distribution: experimental Urgency: low Maintainer: Debian sysvinit maintainers Changed-By: Roger Leigh Description: bootlogd - daemon to log boot messages initscripts - scripts for initializing and shutting down the system sysv-rc- System-V-like runlevel change mechanism sysvinit - System-V-like init utilities sysvinit-utils - System-V-like utilities Closes: 353229 437176 624391 660824 668307 669949 670085 Changes: sysvinit (2.88dsf-24) experimental; urgency=low . [ Roger Leigh ] * initscripts: - Don't generate or touch /etc/motd. Instead, the dynamic part of /etc/motd is created as /run/motd.dynamic, leaving /etc/motd entirely under the control of the system administrator. If /etc/motd is a symlink to /run/motd, /etc/motd.tail is moved back to /etc/motd. Closes: #353229, #624391, #668307. /etc/motd is not removed if initscripts is purged, since it's not owned by initscripts. - By default, /run/motd is just the output of uname, preserving the existing behaviour. However, should the administrator wish to include dynamic information in the motd,
Bug#668307: marked as done (initscripts: recreates /etc/motd)
Your message dated Tue, 08 May 2012 22:04:42 + with message-id and subject line Bug#668307: fixed in sysvinit 2.88dsf-24 has caused the Debian Bug report #668307, regarding initscripts: recreates /etc/motd 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.) -- 668307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initscripts Version: 2.88dsf-22.1 Severity: serious Justification: policy 10.7.3, does not preserve local changes : tfheen@qurzaw ~ > sudo rm -f /etc/motd : tfheen@qurzaw ~ > sudo dpkg-reconfigure initscripts : tfheen@qurzaw ~ > ls -l /etc/motd* lrwxrwxrwx 1 root root 13 april 10 22:41 /etc/motd -> /var/run/motd It shouldn't recreate that file if the admin has removed it. (It should also point at /run rather than /var/run, but that's a more minor matter.) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initscripts depends on: ii coreutils 8.13-3.1 ii debianutils 4.3 ii libc6 2.13-27 ii lsb-base4.1+Debian0 ii mount 2.20.1-4 ii sysv-rc 2.88dsf-22.1 ii sysvinit-utils 2.88dsf-22.1 ii ucf 3.0025+nmu2 Versions of packages initscripts recommends: ii e2fsprogs 1.42.2-1 ii psmisc 22.16-1 initscripts suggests no packages. -- no debconf information -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are --- End Message --- --- Begin Message --- Source: sysvinit Source-Version: 2.88dsf-24 We believe that the bug you reported is fixed in the latest version of sysvinit, which is due to be installed in the Debian FTP archive: bootlogd_2.88dsf-24_amd64.deb to main/s/sysvinit/bootlogd_2.88dsf-24_amd64.deb initscripts_2.88dsf-24_amd64.deb to main/s/sysvinit/initscripts_2.88dsf-24_amd64.deb sysv-rc_2.88dsf-24_all.deb to main/s/sysvinit/sysv-rc_2.88dsf-24_all.deb sysvinit-utils_2.88dsf-24_amd64.deb to main/s/sysvinit/sysvinit-utils_2.88dsf-24_amd64.deb sysvinit_2.88dsf-24.debian.tar.gz to main/s/sysvinit/sysvinit_2.88dsf-24.debian.tar.gz sysvinit_2.88dsf-24.dsc to main/s/sysvinit/sysvinit_2.88dsf-24.dsc sysvinit_2.88dsf-24_amd64.deb to main/s/sysvinit/sysvinit_2.88dsf-24_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 668...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Leigh (supplier of updated sysvinit 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, 29 Apr 2012 23:52:14 +0100 Source: sysvinit Binary: sysvinit sysvinit-utils sysv-rc initscripts bootlogd Architecture: source amd64 all Version: 2.88dsf-24 Distribution: experimental Urgency: low Maintainer: Debian sysvinit maintainers Changed-By: Roger Leigh Description: bootlogd - daemon to log boot messages initscripts - scripts for initializing and shutting down the system sysv-rc- System-V-like runlevel change mechanism sysvinit - System-V-like init utilities sysvinit-utils - System-V-like utilities Closes: 353229 437176 624391 660824 668307 669949 670085 Changes: sysvinit (2.88dsf-24) experimental; urgency=low . [ Roger Leigh ] * initscripts: - Don't generate or touch /etc/motd. Instead, the dynamic part of /etc/motd is created as /run/motd.dynamic, leaving /etc/motd entirely under the control of the system administrator. If /etc/motd is a symlink to /run/motd, /etc/motd.tail is moved back to /etc/motd. Closes: #353229, #624391, #668307. /etc/motd is not removed if initscripts is purged, since it's not owned by initscripts. - By default, /run/motd is just the output of uname, preserving the existing behaviour. However, should the administrator wish to include dynamic information in the motd, they may write scripts to update /run/motd.dynamic as they please. Closes: #437176. - motd generation is split fro
Bug#672079: Bug#672118: qsstv: diff for NMU version 7.1.7-1.1
mart...@brumit.nl said: >Added patch makes it build again. Thanks for creating this patch. It has been incorporated into qsstv-7.1.7-2 (which was uploaded a few minutes ago). -- Steve Kostecke // K0STK -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672079: marked as done (qsstv: FTBFS: wavio.cpp:285:33: error: 'lseek' was not declared in this scope)
Your message dated Tue, 08 May 2012 21:52:24 + with message-id and subject line Bug#672079: fixed in qsstv 7.1.7-2 has caused the Debian Bug report #672079, regarding qsstv: FTBFS: wavio.cpp:285:33: error: 'lseek' 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.) -- 672079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qsstv Version: 7.1.7-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: > g++ -c -m64 -pipe -O2 -D_REENTRANT -Wall -W -DQT_NO_DEBUG -DQT_GUI_LIB > -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED > -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore > -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 > -I../tmp -I. -o ../tmp/wavio.o wavio.cpp > wavio.cpp: In member function 'bool wavIO::writeHeader()': > wavio.cpp:285:33: error: 'lseek' was not declared in this scope > make[2]: *** [../tmp/wavio.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/qsstv_7.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 accessible from the build systems. --- End Message --- --- Begin Message --- Source: qsstv Source-Version: 7.1.7-2 We believe that the bug you reported is fixed in the latest version of qsstv, which is due to be installed in the Debian FTP archive: qsstv_7.1.7-2.debian.tar.gz to main/q/qsstv/qsstv_7.1.7-2.debian.tar.gz qsstv_7.1.7-2.dsc to main/q/qsstv/qsstv_7.1.7-2.dsc qsstv_7.1.7-2_amd64.deb to main/q/qsstv/qsstv_7.1.7-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 672...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Kostecke (supplier of updated qsstv 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, 08 May 2012 15:22:00 -0500 Source: qsstv Binary: qsstv Architecture: source amd64 Version: 7.1.7-2 Distribution: unstable Urgency: low Maintainer: Debian Hamradio Maintainers Changed-By: Steve Kostecke Description: qsstv - Qt-based slow-scan TV and fax Closes: 672079 672118 Changes: qsstv (7.1.7-2) unstable; urgency=low . * Fix FTBFS with GCC 4.7. Thanks Martijn van Brummelen. Closes: #672079, #672118. Checksums-Sha1: 29f693d731f5b23f15c7a6f53dae2581cf25909a 1260 qsstv_7.1.7-2.dsc 6c97e119a62f0a66c6ea3df0b36b6c4dde479483 9410 qsstv_7.1.7-2.debian.tar.gz 9e206a95d66a7ba3dc618eef59d4ac115cc124a2 1905850 qsstv_7.1.7-2_amd64.deb Checksums-Sha256: 1998e1b8a76ee0a871977defd7addf97775791b86442c6b02169d7b2e6ca 1260 qsstv_7.1.7-2.dsc 51f7e2294f24a9d1af78c44883271f5a897ad7f5b36b84bdd62c15c23633c937 9410 qsstv_7.1.7-2.debian.tar.gz 7496221a8071860a20f0920e34eb7ba3783ccbd244b787ccf95d93e2c43763bc 1905850 qsstv_7.1.7-2_amd64.deb Files: c24fba7f24b74a3972ac13cec4c66e8a 1260 hamradio optional qsstv_7.1.7-2.dsc 76223d1d30357f653b4139964ec48a5a 9410 hamradio optional qsstv_7.1.7-2.debian.tar.gz 510d40126db87df0e23eba3aff4007f5 1905850 hamradio optional qsstv_7.1.7-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk+pjLEACgkQElhTTDfsemmOJACdEAhKcLyjRbOcahKIs20gcfmV BUEAni5pLJ322pX/3Wr6At/Ax3CWYrA8 =s3oU -END PGP SIGNATURE- --- End Message ---
Bug#671124: initscripts: Fails to update due to mountoverflowtmp
On Wed, May 02, 2012 at 01:15:42AM +0200, Cyril Brulebois wrote: > Preparing to replace initscripts 2.88dsf-22 (using > .../initscripts_2.88dsf-22.1_amd64.deb) ... > Unpacking replacement initscripts ... > Processing triggers for man-db ... > Setting up initscripts (2.88dsf-22.1) ... > update-rc.d: error: unable to read /etc/init.d/mountoverflowtmp > dpkg: error processing initscripts (--configure): > subprocess installed post-installation script returned error exit status 1 This is quite odd, because there were no changes to mountoverflowtmp between 2.88dsf-22 and 2.88dsf-22.1. It was an NMU of debconf template translations only, and there were no changes to mountoverflowtmp for a long time (years) prior to this. In experimental in 2.88dsf-23, we did remove the mountoverflowtmp script. Is it a possibility that you installed -23 and downgraded to -22? It's a vague possibility that dpkg failed to reinstall the conffile, and this resulted in update-rc.d failing due to the script not being present. I've not received any other reports of this problem to date, and I can't yet reproduce the problem on my own systems--I never had any problem with the 22.1 upgrade, and the -23 and -24 upgrades from experimental have never caused any upgrade problems on my test systems either. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658893: [php-maint] php5 testing transition
On Tue, 2012-05-08 at 22:38 +0100, Adam D. Barratt wrote:
> On Mon, 2012-05-07 at 10:02 +0200, Thijs Kinkhorst wrote:
> > PHP upstream has now announced new releases for tomorrow, which also fix
> > another security issue:
> > http://www.php.net/archive/2012.php#id2012-05-06-1
> >
> > It would be great if we could get that into unstable swiftly and then
> > start the migration process.
>
> Unfortunately, there's a slight problem with this.
>
> php5 produces a php5-mysql binary package, and a mysql-5.5 package
> taking over libmysqlclient-dev hit unstable this morning. That means
> that php5-mysql will end up with a dependency on libmysqlclient18, which
> isn't in testing. php5-mysql appears to have a bunch of r-deps, so
> breaking it temporarily probably isn't the greatest plan either.
Julien pointed out on IRC that I possibly panicked a little too much
here. mysql-5.{1,5} are separate source packages, so we'd "just" need
to wait for mysql-5.5 to be migratable.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671984: [Pkg-haskell-maintainers] Bug#671984: bluetile: FTBFS: build-dependency not installable: libghc-glade-dev
Hi Lucas, I very much appreciate these FTBFS bug reports. I’m not so sure about FTBFS for unsatisfiable build-dependencies, as these are more often than not a bug in a different package, or just a temporary problem due to rebuilds. A suggestion: Is there a chance that your tool can also close these bugs once the problem has disappeared? Then these temporary problems do not require additional work on the maintainer side? Thanks, Joachim Am Dienstag, den 08.05.2012, 13:57 +0200 schrieb Lucas Nussbaum: > Source: bluetile > Version: 0.6-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: > > ┌──┐ > > │ Install bluetile build dependencies (apt-based resolver) > >│ > > └──┘ > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Reading state information... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > sbuild-build-depends-bluetile-dummy : Depends: libghc-glade-dev but it is > > not going to be installed > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. > > The full build log is available from: >http://people.debian.org/~lucas/logs/2012/05/08/bluetile_0.6-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. > > > > ___ > Pkg-haskell-maintainers mailing list > pkg-haskell-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#658893: [php-maint] php5 testing transition
On Mon, 2012-05-07 at 10:02 +0200, Thijs Kinkhorst wrote: > PHP upstream has now announced new releases for tomorrow, which also fix > another security issue: > http://www.php.net/archive/2012.php#id2012-05-06-1 > > It would be great if we could get that into unstable swiftly and then > start the migration process. Unfortunately, there's a slight problem with this. php5 produces a php5-mysql binary package, and a mysql-5.5 package taking over libmysqlclient-dev hit unstable this morning. That means that php5-mysql will end up with a dependency on libmysqlclient18, which isn't in testing. php5-mysql appears to have a bunch of r-deps, so breaking it temporarily probably isn't the greatest plan either. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667429: marked as done (zsnes: ftbfs with GCC-4.7)
Your message dated Tue, 08 May 2012 21:37:32 + with message-id and subject line Bug#667429: fixed in zsnes 1.510+bz2-3 has caused the Debian Bug report #667429, regarding zsnes: 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.) -- 667429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zsnes Version: 1.510+bz2-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. tools/depbuild.cpp:168:37: error: 'F_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/zsnes_1.510+bz2-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. [...] SDL support Version 1.2.15 NASM support NASM version 2.09.10 compiled on Aug 29 2011 zlib support Version 1.2.6 PNG support Yes, version 1.2.47 OpenGL supportYes JMA support Yes ZSNES debuggerEnabled The binary will be installed in /usr/bin Configure complete, now type 'make' and pray. make[1]: Leaving directory `/«BUILDDIR»/zsnes-1.510+bz2' dh_auto_build -a -O--sourcedirectory=src make[1]: Entering directory `/«BUILDDIR»/zsnes-1.510+bz2/src' g++ -m32 -pipe -I. -I/usr/local/include -I/usr/include -D__UNIXSDL__ -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -D__OPENGL__ -march=i486 -O3 -fomit-frame-pointer -fprefetch-loop-arrays -fforce-addr -s -D__RELEASE__ -fno-rtti -o tools/fileutil.o -c tools/fileutil.cpp tools/fileutil.cpp:1:0: warning: -fprefetch-loop-arrays not supported for this target (try -march switches) [enabled by default] g++ -m32 -pipe -I. -I/usr/local/include -I/usr/include -D__UNIXSDL__ -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -D__OPENGL__ -march=i486 -O3 -fomit-frame-pointer -fprefetch-loop-arrays -fforce-addr -s -D__RELEASE__ -fno-rtti -o tools/strutil.o -c tools/strutil.cpp tools/strutil.cpp:1:0: warning: -fprefetch-loop-arrays not supported for this target (try -march switches) [enabled by default] g++ -m32 -pipe -I. -I/usr/local/include -I/usr/include -D__UNIXSDL__ -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -D__OPENGL__ -march=i486 -O3 -fomit-frame-pointer -fprefetch-loop-arrays -fforce-addr -s -D__RELEASE__ -fno-rtti -o tools/depbuild tools/depbuild.cpp tools/fileutil.o tools/strutil.o tools/depbuild.cpp:1:0: warning: -fprefetch-loop-arrays not supported for this target (try -march switches) [enabled by default] tools/depbuild.cpp: In function 'void dependency_calculate(const char*, stat&)': tools/depbuild.cpp:168:37: error: 'F_OK' was not declared in this scope tools/depbuild.cpp:168:41: error: 'access' was not declared in this scope make[1]: *** [tools/depbuild] Error 1 make[1]: Leaving directory `/«BUILDDIR»/zsnes-1.510+bz2/src' 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 --- --- Begin Message --- Source: zsnes Source-Version: 1.510+bz2-3 We believe that the bug you reported is fixed in the latest version of zsnes, which is due to be installed in the Debian FTP archive: zsnes_1.510+bz2-3.debian.tar.gz to main/z/zsnes/zsnes_1.510+bz2-3.debian.tar.gz zsnes_1.510+bz2-3.dsc to main/z/zsnes/zsnes_1.510+bz2-3.dsc zsnes_1.510+bz2-3_amd64.deb to main/z/zsnes/zsnes_1.510+bz2-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. Etienne Millon (supplier of updated zsnes 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
Bug#672156: Should be dropped in favour of squid3
Package: squid Severity: serious I remember some discussion before the Squeeze release about both squid and squid3 being included in a stable release and thus needing double security updates. >From what I remember squid3 still lacked some features at that time and having both in Squeeze was meant to allow people to transition from Squid 2 to Squid 3 in a stable release. As such, we should now exclude squid from Wheezy. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671941: marked as done (gnome-commander: FTBFS with gcc 4.7)
Your message dated Tue, 08 May 2012 21:27:28 + with message-id and subject line Bug#672027: fixed in gnome-commander 1.2.8.15-2.1 has caused the Debian Bug report #672027, regarding gnome-commander: 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.) -- 672027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-commander Version: 1.2.8.15-2 Severity: serious Justification: FTBFS Hi, so apparently the archive-wide rebuild for gcc 4.7 didn't lead to any bug against your package, but the thing is it got binNMUd for the exiv2 transition and it fails to build due to the recent switch to gcc 4.7 as default compiler for a bunch of architectures. I'm not quoting the lengthy error messages, but you now need to use std::make_pair() rather than just make_pair(). Full build log: https://buildd.debian.org/status/fetch.php?pkg=gnome-commander&arch=amd64&ver=1.2.8.15-2%2Bb1&stamp=1336432082 I'll push a branch to the collab-maint repository as soon as I have the bug number so that I can use it in Bug-Debian in the patch, and in the changelog. Mraw, KiBi. --- End Message --- --- Begin Message --- Source: gnome-commander Source-Version: 1.2.8.15-2.1 We believe that the bug you reported is fixed in the latest version of gnome-commander, which is due to be installed in the Debian FTP archive: gnome-commander-data_1.2.8.15-2.1_all.deb to main/g/gnome-commander/gnome-commander-data_1.2.8.15-2.1_all.deb gnome-commander-dbg_1.2.8.15-2.1_amd64.deb to main/g/gnome-commander/gnome-commander-dbg_1.2.8.15-2.1_amd64.deb gnome-commander_1.2.8.15-2.1.debian.tar.gz to main/g/gnome-commander/gnome-commander_1.2.8.15-2.1.debian.tar.gz gnome-commander_1.2.8.15-2.1.dsc to main/g/gnome-commander/gnome-commander_1.2.8.15-2.1.dsc gnome-commander_1.2.8.15-2.1_amd64.deb to main/g/gnome-commander/gnome-commander_1.2.8.15-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 672...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gnome-commander 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, 08 May 2012 21:31:18 +0200 Source: gnome-commander Binary: gnome-commander gnome-commander-data gnome-commander-dbg Architecture: source amd64 all Version: 1.2.8.15-2.1 Distribution: unstable Urgency: high Maintainer: Michael Vogt Changed-By: Matthias Klose Description: gnome-commander - nice and fast file manager for the GNOME desktop gnome-commander-data - Data files for GNOME Commander gnome-commander-dbg - Debugging symbols for gnome-commander Closes: 672027 Changes: gnome-commander (1.2.8.15-2.1) unstable; urgency=high . * Non maintainer upload. * Work around build failure with GCC 4.7 (build with -fpermissive). Closes: #672027. * Fix build errors with -Werror=format-security. Checksums-Sha1: 54e2951e4975fad547a486a0cc3f358ea0774c25 1804 gnome-commander_1.2.8.15-2.1.dsc a61f7bd6eb69e9118a5818b242baa5419c450240 9493 gnome-commander_1.2.8.15-2.1.debian.tar.gz 242570e21a967da50e9353437321d69d94c09f5f 542610 gnome-commander_1.2.8.15-2.1_amd64.deb 087563a3a635c55957113932d03588b9ac5db2d1 3559408 gnome-commander-data_1.2.8.15-2.1_all.deb 120efce8889068c8d4cec1fa2581c1f8e5d49fc3 3686788 gnome-commander-dbg_1.2.8.15-2.1_amd64.deb Checksums-Sha256: cc851cc45001282acd85a2cdb633f4b13e4ef84898035d1586279813d0caa707 1804 gnome-commander_1.2.8.15-2.1.dsc a2099f5b4fd84083566159c26c4f199ddef02bb9f1e9b4e406519b3dab6b2fc6 9493 gnome-commander_1.2.8.15-2.1.debian.tar.gz 052c9df60c8732095493bab016c91217c2b8432e5705f0d9f945475ec9a6e7c5 542610 gnome-commander_1.2.8.15-2.1_amd64.deb b53ae339027c73db8ed7687745c3e7f7285e0304199bcdb3590bfb325b194924 3559408 gnome-commander-data_1.2.8.15-2.1_all.deb 52b67879e751fe4f54b4d95bb346c07225f30b9209e5b5baec485ca372160e9e 3686788 gnome-commander-dbg_1.2.8.15-2.1_amd64.deb Files: 526cea45fbe6d8ef6937127cfa1a1b9a 1804 gnome optional gnome-commander_1.2.8.15-2.1.dsc ac6b72d64c11b21f201f730c48a4a2ab 9493 gnome optional gnome-commander_1.2.8.15-2.1.debian.tar.gz bc9f4973c708318799a1c354aaed48b7 54
Bug#672027: marked as done (gnome-commander: FTBFS: ./../dict.h:58:102: error: 'make_pair' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of i
Your message dated Tue, 08 May 2012 21:27:28 + with message-id and subject line Bug#672027: fixed in gnome-commander 1.2.8.15-2.1 has caused the Debian Bug report #672027, regarding gnome-commander: FTBFS: ./../dict.h:58:102: error: 'make_pair' 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.) -- 672027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-commander Version: 1.2.8.15-2 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../.. -Wall -I../.. -I./.. -pthread -D_REENTRANT > -DORBIT2=1 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 > -I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 > -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 > -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include > -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 > -I/usr/include/libpng12 -I/usr/include/libgnomeui-2.0 > -I/usr/include/libart-2.0 -I/usr/include/libgnome-2.0 > -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 > -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include > -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 > -I/usr/include/bonobo-activation-2.0 -pthread -I/usr/include/gconf/2 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include > -I/usr/include/taglib -I/usr/include/poppler > -DPLUGIN_DIR=\""/usr/lib/gnome-commander/plugins"\" -g -O2 -c -o > gnome-cmd-tags-taglib.o gnome-cmd-tags-taglib.cc > In file included from ./../utils.h:33:0, > from gnome-cmd-tags.h:30, > from gnome-cmd-tags-doc.h:25, > from gnome-cmd-tags-doc.cc:37: > ./../gnome-cmd-pixmap.h: In function 'void > gnome_cmd_pixmap_free(GnomeCmdPixmap*)': > ./../gnome-cmd-pixmap.h:47:5: warning: 'void gdk_pixbuf_unref(GdkPixbuf*)' is > deprecated (declared at > /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use > 'g_object_unref' instead [-Wdeprecated-declarations] > ./../gnome-cmd-pixmap.h:47:37: warning: 'void gdk_pixbuf_unref(GdkPixbuf*)' > is deprecated (declared at > /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use > 'g_object_unref' instead [-Wdeprecated-declarations] > In file included from ./../utils.h:33:0, > from gnome-cmd-tags.h:30, > from gnome-cmd-tags-exiv2.h:25, > from gnome-cmd-tags-exiv2.cc:26: > ./../gnome-cmd-pixmap.h: In function 'void > gnome_cmd_pixmap_free(GnomeCmdPixmap*)': > ./../gnome-cmd-pixmap.h:47:5: warning: 'void gdk_pixbuf_unref(GdkPixbuf*)' is > deprecated (declared at > /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use > 'g_object_unref' instead [-Wdeprecated-declarations] > ./../gnome-cmd-pixmap.h:47:37: warning: 'void gdk_pixbuf_unref(GdkPixbuf*)' > is deprecated (declared at > /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use > 'g_object_unref' instead [-Wdeprecated-declarations] > In file included from ./../utils.h:33:0, > from gnome-cmd-tags.h:30, > from gnome-cmd-tags.cc:29: > ./../gnome-cmd-pixmap.h: In function 'void > gnome_cmd_pixmap_free(GnomeCmdPixmap*)': > ./../gnome-cmd-pixmap.h:47:5: warning: 'void gdk_pixbuf_unref(GdkPixbuf*)' is > deprecated (declared at > /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use > 'g_object_unref' instead [-Wdeprecated-declarations]In file included from > ./../utils.h:33:0, > from gnome-cmd-tags.h:30, >
Bug#671981: marked as done (ganeti: FTBFS: configure: error: ip command not found)
Your message dated Tue, 08 May 2012 21:25:07 + with message-id and subject line Bug#671981: fixed in ganeti 2.5.0-2 has caused the Debian Bug report #671981, regarding ganeti: FTBFS: configure: error: ip command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 671981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ganeti Version: 2.5.0-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: > debian/rules build > dh_testdir > # Add here commands to compile the package. > ./configure \ > --prefix=/usr \ > --localstatedir=/var \ > --sysconfdir=/etc \ > --with-export-dir=/var/lib/ganeti/export \ > > --with-iallocator-search-path=/usr/local/lib/ganeti/iallocators,/usr/lib/ganeti/iallocators > \ > > --with-os-search-path=/srv/ganeti/os,/usr/local/lib/ganeti/os,/usr/lib/ganeti/os,/usr/share/ganeti/os > \ > --docdir=/usr/share/doc/ganeti2 \ > --enable-htools --enable-htools-rapi > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking how to create a ustar tar archive... gnutar > configure: error: ip command not found > configure: Running ganeti-masterd as root:root > configure: Running ganeti-rapi as root:root > configure: Running ganeti-confd as root:root > configure: Group for daemons is root > configure: Group for clients is root > checking whether ln -s works... yes > checking for ip... no > make: *** [build-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/ganeti_2.5.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: ganeti Source-Version: 2.5.0-2 We believe that the bug you reported is fixed in the latest version of ganeti, which is due to be installed in the Debian FTP archive: ganeti-htools_2.5.0-2_amd64.deb to main/g/ganeti/ganeti-htools_2.5.0-2_amd64.deb ganeti2_2.5.0-2_all.deb to main/g/ganeti/ganeti2_2.5.0-2_all.deb ganeti_2.5.0-2.debian.tar.gz to main/g/ganeti/ganeti_2.5.0-2.debian.tar.gz ganeti_2.5.0-2.dsc to main/g/ganeti/ganeti_2.5.0-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 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iustin Pop (supplier of updated ganeti 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, 08 May 2012 22:34:10 +0200 Source: ganeti Binary: ganeti2 ganeti-htools Architecture: source all amd64 Version: 2.5.0-2 Distribution: unstable Urgency: low Maintainer: Debian Ganeti Team Changed-By: Iustin Pop Description: ganeti-htools - Cluster allocation tools for Ganeti ganeti2- Cluster-based virtualization management software Closes: 671981 Changes: ganeti (2.5.0-2) unstable; urgency=low . * Fix Build-Depends (no more separate -Indep depends, add iproute) (Closes: #671981) Checksums-Sha1: b811f905b22b3a9b34545fc990403b431ab4cb4e 2215 ganeti_2.5.0-2.dsc f9b49cffc140c12c74f68c52a419df813ea47803 10888 ganeti_2.5.0-2.debian.tar.gz ab11a8f06627f0b7610b9ac9e292f197358fa1e9 1386062 ganeti2_2.5.0-2_all.deb 883b59c786e6ae4c18e0e1077425311ee1ebbb0d 851804 ganeti-htools_2.5.0-2_amd64.deb Checksums-Sha256: fa8f2e9b77ae2bf610a396504d0690c86077fc89847c58b6b926b4e4f19805e0 2215 ganeti_2.5.0-2
Bug#672029: marked as done (dynare: FTBFS: ModelTree.cc:805:43: error: redeclaration of 'std::vector::const_iterator it')
Your message dated Tue, 08 May 2012 21:22:30 + with message-id and subject line Bug#672029: fixed in dynare 4.2.5-2 has caused the Debian Bug report #672029, regarding dynare: FTBFS: ModelTree.cc:805:43: error: redeclaration of 'std::vector::const_iterator it' 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.) -- 672029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dynare Version: 4.2.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: > g++ -DPACKAGE_NAME=\"dynare\" -DPACKAGE_TARNAME=\"dynare\" > -DPACKAGE_VERSION=\"4.2.5\" -DPACKAGE_STRING=\"dynare\ 4.2.5\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"dynare\" > -DVERSION=\"4.2.5\" -DHAVE_BOOST=/\*\*/ -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_BOOST_GRAPH_ADJACENCY_LIST_HPP=1 > -DHAVE_BOOST_ALGORITHM_STRING_TRIM_HPP=1 > -DHAVE_BOOST_ALGORITHM_STRING_SPLIT_HPP=1 -DHAVE_BOOST_LEXICAL_CAST_HPP=1 > -DBOOST_NO_HASH=/\*\*/ -DHAVE_BLAS=1 -DHAVE_LAPACK=1 -DHAVE_PTHREAD=1 -I. > -I/usr/include -I. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall > -Wno-parentheses -c -o dynare_m-Shocks.o `test -f 'Shocks.cc' || echo > './'`Shocks.cc > > (/usr/share/texmf/tex/latex/beamer/base/themes/color/beamercolorthemedefault.st > y) > (/usr/share/texmf/tex/latex/beamer/base/themes/inner/beamerinnerthemedefault.st > y) > (/usr/share/texmf/tex/latex/beamer/base/themes/outer/beamerouterthemedefault.st > y))) > (/usr/share/texmf/tex/latex/beamer/base/themes/theme/beamerthemeMadrid.sty > (/usr/share/texmf/tex/latex/beamer/base/themes/color/beamercolorthemewhale.sty) > > (/usr/share/texmf/tex/latex/beamer/base/themes/color/beamercolorthemeorchid.sty > ) > (/usr/share/texmf/tex/latex/beamer/base/themes/inner/beamerinnerthemerounded.st > y) > (/usr/share/texmf/tex/latex/beamer/base/themes/outer/beamerouterthemeinfolines. > sty)) (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty > (/usr/share/texlive/texmf-dist/tex/generic/babel/english.ldf > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def))) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def > StaticModel.cc: In member function 'void > StaticModel::writeModelEquationsOrdered_M(const string&) const': > StaticModel.cc:218:7: warning: variable 'nze' set but not used > [-Wunused-but-set-variable] > (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu) > (/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu) > (/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu))) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/times.sty) > (./preprocessor.aux) > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ot1phv.fd) > *geometry* driver: auto-detecting > *geometry* detected driver: pdftex > (/usr/share/texlive/texmf-dist/tex/context/base/supp-pdf.mkii > [Loading MPS to PDF converter (version 2006.09.02).] > ) (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty > (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/grfext.sty) > (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg)) > ABD: EveryShipout initializing macros > (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty > (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty)) > (./preprocessor.out) (./preprocessor.out) > (/usr/share/texmf/tex/latex/beamer/base/translator/dicts/translator-basic-dicti > onary/translator-basic-dictionary-English.dict) > (/usr/share/texmf/tex/latex/beamer/base/translator/dicts/translator-bibliograph > y-dictionary/translator-bibliography-dictionary-English.dict) > (/usr/share/texmf/tex/latex/beamer/base/translator/dicts/translator-environment > -dictionary/translator-environment-dictionary-English.dict) > (/usr/share/texmf/tex/latex/beamer/base/translator/dicts/translator-m
Bug#671988: marked as done (blackbox: FTBFS: dh_makeshlibs: dpkg-gensymbols -plibbt0 -Idebian/libbt0.symbols -Pdebian/libbt0 returned exit code 1)
Your message dated Tue, 08 May 2012 21:17:22 + with message-id and subject line Bug#671988: fixed in blackbox 0.70.1-9 has caused the Debian Bug report #671988, regarding blackbox: FTBFS: dh_makeshlibs: dpkg-gensymbols -plibbt0 -Idebian/libbt0.symbols -Pdebian/libbt0 returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 671988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: blackbox Version: 0.70.1-8 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: > make[1]: Entering directory `/«PKGBUILDDIR»' > rm -rf /«PKGBUILDDIR»/debian/libbt/usr/share/doc/libbt > dh_link -plibbt usr/share/doc/libbt0 usr/share/doc/libbt > dh_link > make[1]: Leaving directory `/«PKGBUILDDIR»' >dh_compress >dh_fixperms >dh_strip >dh_makeshlibs > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbt0/DEBIAN/symbols doesn't match > completely debian/libbt0.symbols > --- debian/libbt0.symbols (libbt0_0.70.1-8_amd64) > +++ dpkg-gensymbolsUS6qrN 2012-05-08 08:58:52.559804810 + > @@ -70,6 +70,8 @@ > _ZN2bt12EventHandlerD0Ev@Base 0.70.1 > _ZN2bt12EventHandlerD1Ev@Base 0.70.1 > _ZN2bt12EventHandlerD2Ev@Base 0.70.1 > + > _ZN2bt12_timer_queueIPNS_5TimerESt6vectorIS2_SaIS2_EENS_13TimerLessThanEED1Ev@Base > 0.70.1-8 > + > _ZN2bt12_timer_queueIPNS_5TimerESt6vectorIS2_SaIS2_EENS_13TimerLessThanEED2Ev@Base > 0.70.1-8 > _ZN2bt13alignResourceERKNS_8ResourceEPKcS4_NS_9AlignmentE@Base 0.70.1 > _ZN2bt14createPenCacheERKNS_7DisplayE@Base 0.70.1 > _ZN2bt14createShmImageERKNS_7DisplayERKNS_10ScreenInfoEjj@Base 0.70.1 > @@ -79,8 +81,8 @@ > _ZN2bt15RealPixmapCache4findEjRKNS_7TextureEjjm@Base 0.70.1 > _ZN2bt15RealPixmapCache5clearEb@Base 0.70.1 > _ZN2bt15RealPixmapCache7releaseEm@Base 0.70.1 > - _ZN2bt15RealPixmapCache9CacheItemD1Ev@Base 0.70.1 > - _ZN2bt15RealPixmapCache9CacheItemD2Ev@Base 0.70.1 > +#MISSING: 0.70.1-8# _ZN2bt15RealPixmapCache9CacheItemD1Ev@Base 0.70.1 > +#MISSING: 0.70.1-8# _ZN2bt15RealPixmapCache9CacheItemD2Ev@Base 0.70.1 > _ZN2bt15RealPixmapCacheC1ERKNS_7DisplayE@Base 0.70.1 > _ZN2bt15RealPixmapCacheC2ERKNS_7DisplayE@Base 0.70.1 > _ZN2bt15RealPixmapCacheD1Ev@Base 0.70.1 > @@ -279,6 +281,8 @@ > _ZN2bt9FontCache11findXftFontERKSsj@Base 0.70.1 > _ZN2bt9FontCache5clearEb@Base 0.70.1 > _ZN2bt9FontCache7releaseERKSsj@Base 0.70.1 > + _ZN2bt9FontCache8FontNameD1Ev@Base 0.70.1-8 > + _ZN2bt9FontCache8FontNameD2Ev@Base 0.70.1-8 > _ZN2bt9FontCacheC1ERKNS_7DisplayE@Base 0.70.1 > _ZN2bt9FontCacheC2ERKNS_7DisplayE@Base 0.70.1 > _ZN2bt9FontCacheD1Ev@Base 0.70.1 > @@ -286,6 +290,8 @@ > _ZN2bt9MenuDelay7timeoutEPNS_5TimerE@Base 0.70.1 > _ZN2bt9MenuStyle3getERNS_11ApplicationEj@Base 0.70.1 > _ZN2bt9MenuStyle4loadERKNS_8ResourceE@Base 0.70.1 > + _ZN2bt9MenuStyle6_titleD1Ev@Base 0.70.1-8 > + _ZN2bt9MenuStyle6_titleD2Ev@Base 0.70.1-8 > _ZN2bt9MenuStyle6stylesE@Base 0.70.1 > _ZN2bt9MenuStyleC1ERNS_11ApplicationEj@Base 0.70.1 > _ZN2bt9MenuStyleC2ERNS_11ApplicationEj@Base 0.70.1 > @@ -293,6 +299,7 @@ > _ZN2bt9itostringEm@Base 0.70.1 > _ZN2bt9mkdirhierERKSsi@Base 0.70.1 > _ZN2bt9toUnicodeERKSs@Base 0.70.1 > + _ZN9__gnu_cxx11char_traitsIjE4copyEPjPKjm@Base 0.70.1-8 > _ZNK2bt11Application10grabButtonEjjmbjiimmb@Base 0.70.1 > _ZNK2bt11Application12ungrabButtonEjjm@Base 0.70.1 > _ZNK2bt11Application8XDisplayEv@Base 0.70.1 > @@ -375,11 +382,15 @@ > _ZNK2bt9MenuStyle8itemRectERKNS_8MenuItemE@Base 0.70.1 > _ZNK2bt9MenuStyle9drawTitleEmRKNS_4RectERKSbIjSt11char_traitsIjESaIjEE@Base > 0.70.1 > _ZNK2bt9MenuStyle9titleRectERKSbIjSt11char_traitsIjESaIjEE@Base 0.70.1 > + _ZNSbIjSt11char_traitsIjESaIjEE12_M_leak_hardEv@Base 0.70.1-8 > + _ZNSbIjSt11char_traitsIjESaIjEE15_M_replace_safeEmmPKjm@Base 0.70.1-8 > _ZNSbIjSt11char_traitsIjESaIjEE4_Rep20_S_empty_rep_storageE@Base 0.70.1 > (arch=!amd64 !ia64 !kfreebsd-amd64 !s390 !s390x !alpha !ppc64 > !sparc64)_Z
Bug#671954: marked as done (clxclient: FTBFS: symbols errors)
Your message dated Tue, 08 May 2012 21:18:07 + with message-id and subject line Bug#671954: fixed in clxclient 3.6.1-5 has caused the Debian Bug report #671954, regarding clxclient: FTBFS: symbols errors 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.) -- 671954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clxclient Version: 3.6.1-4 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: > make[1]: Entering directory `/«PKGBUILDDIR»' > /usr/bin/install -d /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu > /usr/bin/install -d /«PKGBUILDDIR»/debian/tmp/usr/include > /usr/bin/install -m 644 clxclient.h /«PKGBUILDDIR»/debian/tmp/usr/include > /usr/bin/install -m 755 libclxclient.so.3.6.1 > /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu > /sbin/ldconfig -n /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu > ln -sf libclxclient.so.3.6.1 > /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/libclxclient.so > make[1]: Leaving directory `/«PKGBUILDDIR»' >dh_install -O-Smakefile >dh_installdocs -O-Smakefile >dh_installchangelogs -O-Smakefile >dh_installexamples -O-Smakefile >dh_installman -O-Smakefile >dh_installcatalogs -O-Smakefile >dh_installcron -O-Smakefile >dh_installdebconf -O-Smakefile >dh_installemacsen -O-Smakefile >dh_installifupdown -O-Smakefile >dh_installinfo -O-Smakefile >dh_installinit -O-Smakefile >dh_installmenu -O-Smakefile >dh_installmime -O-Smakefile >dh_installmodules -O-Smakefile >dh_installlogcheck -O-Smakefile >dh_installlogrotate -O-Smakefile >dh_installpam -O-Smakefile >dh_installppp -O-Smakefile >dh_installudev -O-Smakefile >dh_installwm -O-Smakefile >dh_installxfonts -O-Smakefile >dh_installgsettings -O-Smakefile >dh_bugfiles -O-Smakefile >dh_ucf -O-Smakefile >dh_lintian -O-Smakefile >dh_gconf -O-Smakefile >dh_icons -O-Smakefile >dh_perl -O-Smakefile >dh_usrlocal -O-Smakefile >dh_link -O-Smakefile >dh_compress -O-Smakefile >dh_fixperms -O-Smakefile >dh_strip -O-Smakefile >dh_makeshlibs -O-Smakefile > dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libclxclient3/DEBIAN/symbols doesn't match > completely debian/libclxclient3.symbols.amd64 > --- debian/libclxclient3.symbols.amd64 (libclxclient3_3.6.1-4_amd64) > +++ dpkg-gensymbolsJ1bbl7 2012-05-08 08:43:35.694806824 + > @@ -9,8 +9,8 @@ > _ZN5EdestD0Ev@Base 3.6.1 > _ZN5EdestD1Ev@Base 3.6.1 > _ZN5EdestD2Ev@Base 3.6.1 > - _ZN5EsyncD1Ev@Base 3.6.1 > - _ZN5EsyncD2Ev@Base 3.6.1 > +#MISSING: 3.6.1-4# _ZN5EsyncD1Ev@Base 3.6.1 > +#MISSING: 3.6.1-4# _ZN5EsyncD2Ev@Base 3.6.1 > _ZN6X_draw10drawpointsEiP6XPoint@Base 3.6.1 > _ZN6X_draw10drawstringEPKci@Base 3.6.1 > _ZN6X_draw12drawsegmentsEiP8XSegment@Base 3.6.1 > dh_makeshlibs: dpkg-gensymbols -plibclxclient3 > -Idebian/libclxclient3.symbols.amd64 -Pdebian/libclxclient3 > -edebian/libclxclient3/usr/lib/x86_64-linux-gnu/libclxclient.so.3.6.1 > returned exit code 1 > make: *** [binary] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/clxclient_3.6.1-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: clxclient Source-Version: 3.6.1-5 We believe that the bug you reported is fixed in the latest version of clxclient, which is due to be installed in the Debian FTP archive: clxclient_3.6.1-5.debian.tar.gz to main/c/clxclient/clxclient_3.6.1-5.debian.tar.gz clxclient_3.6.1-5.dsc to main/c/clxclient/clxclient_3.6.1-5.dsc libclxclient-dev_3.6.1-5_amd64.deb to main/c/clxclient/libclxclient-dev_3.6.1-5_amd64.deb libclxclient3_3.6.1-5_amd64.deb to main/c/clxclient/libcl
Processed: forcibly merging 671941 672027
Processing commands for cont...@bugs.debian.org: > forcemerge 671941 672027 Bug #671941 [src:gnome-commander] gnome-commander: FTBFS with gcc 4.7 Bug #672027 [src:gnome-commander] gnome-commander: FTBFS: ./../dict.h:58:102: error: 'make_pair' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] Added tag(s) pending and patch. Bug #671941 [src:gnome-commander] gnome-commander: FTBFS with gcc 4.7 Added tag(s) sid and wheezy. Merged 671941 672027 > thanks Stopping processing here. Please contact me if you need assistance. -- 671941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671941 672027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672027 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#672140: [Pkg-utopia-maintainers] Bug#672140: prompts for root passwords on a sudo-only system
Hi, Am 08.05.2012 21:55, schrieb Joey Hess: > Package: policykit-1 > Version: 0.104-2 > Severity: serious Could you elaborate on the severity? > Tags: d-i > > In d-i, it is very easy to set up a system without entering a root > password. d-i sets up sudo, and configures gksu to use it > (by changing an alternative). > > On such a system, I was prompted by policykit for the (nonexistant) root > password when network-manager wanted to authenticate me in order to > associate to a wireless network. I assume policykit prompts for the root > password for other things too. Was that in gnome-shell or gnome-fallback? Is your user in group sudo / any other user in group sudo? > > If there is some setting we can make in d-i to new installs to make > policykit use sudo, please let me know, and I will make it. It wouldn't > solve the problem when upgrading existing installs that use sudo, but > it'd be better than nothing. Adding a user to group sudo should be sufficient to mark it as account with admin privileges, i.e. a d-i setup which adds the user to group sudo (which is the case for a password-less root-account) should work ootb. Michael signature.asc Description: OpenPGP digital signature
Processed: qsstv: diff for NMU version 7.1.7-1.1
Processing commands for cont...@bugs.debian.org: > tags 672079 + patch Bug #672079 [src:qsstv] qsstv: FTBFS: wavio.cpp:285:33: error: 'lseek' was not declared in this scope Added tag(s) patch. > tags 672079 + pending Bug #672079 [src:qsstv] qsstv: FTBFS: wavio.cpp:285:33: error: 'lseek' was not declared in this scope Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 672079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672079 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#672079: qsstv: diff for NMU version 7.1.7-1.1
tags 672079 + patch
tags 672079 + pending
thanks
Forgot to mention the bug in the changelog
Regards.
martijn van brummelen
diff -Nru qsstv-7.1.7/debian/changelog qsstv-7.1.7/debian/changelog
--- qsstv-7.1.7/debian/changelog 2012-04-21 05:43:08.0 +0200
+++ qsstv-7.1.7/debian/changelog 2012-05-08 22:18:24.0 +0200
@@ -1,3 +1,10 @@
+qsstv (7.1.7-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBS ('lseek' was not declared in this scope) (Closes: #672079).
+
+ -- Martijn van Brummelen Tue, 08 May 2012 22:18:24 +0200
+
qsstv (7.1.7-1) unstable; urgency=low
* New upstream release (Jan 4, 2012)
diff -Nru qsstv-7.1.7/debian/patches/ftbs_672079.patch qsstv-7.1.7/debian/patches/ftbs_672079.patch
--- qsstv-7.1.7/debian/patches/ftbs_672079.patch 1970-01-01 01:00:00.0 +0100
+++ qsstv-7.1.7/debian/patches/ftbs_672079.patch 2012-05-08 17:31:29.0 +0200
@@ -0,0 +1,36 @@
+Description:
+ TODO: Put a short summary on the line above and replace this paragraph
+ with a longer explanation of this change. Complete the meta-information
+ with other relevant fields (see below for details). To make it easier, the
+ information below has been extracted from the changelog. Adjust it or drop
+ it.
+ .
+ qsstv (7.1.7-1.1) unstable; urgency=low
+ .
+ * Non-maintainer upload.
+ * Fix FTBS ('lseek' was not declared in this scope).
+Author: Martijn van Brummelen
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: ,
+Bug:
+Bug-Debian: http://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded:
+Reviewed-By:
+Last-Update:
+
+--- qsstv-7.1.7.orig/src/wavio.cpp
qsstv-7.1.7/src/wavio.cpp
+@@ -34,6 +34,7 @@
+ #include
+ #include "configparams.h"
+ #include "supportfunctions.h"
++#include
+
+ //#include "qfilterdesignglobal.h"
+
diff -Nru qsstv-7.1.7/debian/patches/series qsstv-7.1.7/debian/patches/series
--- qsstv-7.1.7/debian/patches/series 2012-04-21 06:44:09.0 +0200
+++ qsstv-7.1.7/debian/patches/series 2012-05-08 17:33:30.0 +0200
@@ -1,3 +1,4 @@
set-install-prefix.patch
fix-html-doc-path.patch
fix-target-path.patch
+ftbs_672079.patch
Processed: Re: Bug#672085: qof: ftbfs with GCC-4.7
Processing commands for cont...@bugs.debian.org: > tag 672085 + help 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) help. > 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#672085: qof: ftbfs with GCC-4.7
tag 672085 + help quit On Tue, 08 May 2012 18:57:52 + Matthias Klose wrote: > user debian-...@lists.debian.org > usertags 672085 + ftbfs-gcc-4.7 > thanks > > The build failure is exposed by building with gcc-4.7/g++-4.7, > which is now the default gcc/g++ on x86 architectures. > > Some hints on fixing these issues can be found at > http://gcc.gnu.org/gcc-4.7/porting_to.html This particular issue isn't covered in those hints, it's an internal MD5 process which is the same as the internal MD5 code in eglibc. I could hide the problem by dropping -Werror or adding -fno-strict-aliasing but it's not clear to me why the same code compiles in eglibc and not in qof, especially when eglibc is passing -fstrict-aliasing. I'm fairly sure that this needs no source code changes in md5.c, this is something related to the build system options but I have to admit I can't quite see where it lies currently. (Due to the history of the code in QOF, exactly the same code still exists in all versions of GnuCash.) -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpaI5ILOSar5.pgp Description: PGP signature
Bug#672052: qastools: ftbfs with GCC-4.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 At a first glance it seems that an include is missing. This issue is mentioned in http://gcc.gnu.org/gcc-4.7/porting_to.html (thanks for the link) My sid vm installation is very dusty and needs an updated first but I'll try to fix this soon. - -- Sebastian Holtermann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJPqX2TAAoJECkBQ2tME2NmIrYIALrnuQZJb0bCjs1+PQygemy7 bNJmhcof4t3qtqZtjd8Flt6BY9T5bdBuTsgo9F7nVT/laXR5yLpTu8XErAzqaCrf lyjz51Sfzx+z85x3jy3XkhOPBxAygt3ugCE4Qsbd79RdjLzcLFNHtBQwUPYKbHby zA9V6HLni2dOrz8vXquRPuY1zBnov60ywUZpHJMZzsPrgl+1ncc6AT/jWUvDQLgu K6BF/JcUkwTYWfdPu7ghAiCZw1qQhfBpqmyCt/TZvo+HYqCNTDTFij4IgO41V8cd couRdRrcfwL6EMYTPXNWMo+9Iq149Y0mPltyXe7u9nm4ht4bYzQ9OrUQrsBJogo= =8oH0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable
Processing commands for cont...@bugs.debian.org: > severity 671944 minor Bug #671944 [libnepomuk4] libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable Severity set to 'minor' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 671944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671944 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#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable
severity 671944 minor thanks Hi, Alle martedì 8 maggio 2012, Ralf Jung ha scritto: > Package: libnepomuk4 > Version: 4:4.7.4-4 > Severity: grave > Justification: renders package unusable > > Virtuoso is missing from testing, and without it, Nepomuk does not > work (also see [1]). As I had to find out the hard way [2], The fact that virtuoso is missing from testing is not something related to us. > reporting this against Virtuoso is wrong (sorry for the multiple bug > reports caused by this). As a result of virtuoso missing, new > installations will not be able to get a working Nepomuk, making the > package unusable. Err no, sorry, we're not talking about a daemon or a service, but about a library, which is linked directly and indirectly by lot of KDE applications: | Package: libkio5 | Depends: [...], libnepomuk4 (...), [...] this is because the KIO dialog for overwriting a file can optionally show semantic metadata to compare the two files; note the feature just works when the semantic desktop is enabled (i.e. not just when you have virtuoso installed, but also when you have the semantic desktop *enabled* in system settings). So applications which would use KIO for handling non-local files but no semantic desktop would get virtuoso installed? No thanks. Even those who explicitly link to libnepomuk usually can just work fine without semantic desktop enabled, just with those features disabled. Either way, the dependency you proposed is really way out. If you care about having virtuoso in testing again, then cooperate with its maintainers. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#672140: prompts for root passwords on a sudo-only system
Package: policykit-1 Version: 0.104-2 Severity: serious Tags: d-i In d-i, it is very easy to set up a system without entering a root password. d-i sets up sudo, and configures gksu to use it (by changing an alternative). On such a system, I was prompted by policykit for the (nonexistant) root password when network-manager wanted to authenticate me in order to associate to a wireless network. I assume policykit prompts for the root password for other things too. If there is some setting we can make in d-i to new installs to make policykit use sudo, please let me know, and I will make it. It wouldn't solve the problem when upgrading existing installs that use sudo, but it'd be better than nothing. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages policykit-1 depends on: ii consolekit 0.4.5-3 ii dbus 1.5.12-1 ii libc6 2.13-32 ii libexpat1 2.1.0-1 ii libglib2.0-0 2.32.2-1 ii libpam0g 1.1.3-7 ii libpolkit-agent-1-00.104-2 ii libpolkit-backend-1-0 0.104-2 ii libpolkit-gobject-1-0 0.104-2 policykit-1 recommends no packages. policykit-1 suggests no packages. -- no debconf information -- see shy jo signature.asc Description: Digital signature
Bug#672088: marked as done (xye: FTBFS: src/gen.cpp:153:34: error: 'access' was not declared in this scope)
Your message dated Tue, 08 May 2012 19:51:49 + with message-id and subject line Bug#672088: fixed in xye 0.12.1+dfsg-4 has caused the Debian Bug report #672088, regarding xye: FTBFS: src/gen.cpp:153:34: error: 'access' 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.) -- 672088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xye Version: 0.12.1+dfsg-3 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++ -DDATA_PATH=\"/usr/share/xye/\" -I. -I. -g -O2 -I/usr/include/SDL > -D_GNU_SOURCE=1 -D_REENTRANT -c -o gen.o `test -f 'src/gen.cpp' || echo > './'`src/gen.cpp > src/gen.cpp: In function 'bool DoesFileExist(const char*)': > src/gen.cpp:153:34: error: 'access' was not declared in this scope > make[1]: *** [gen.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/xye_0.12.1+dfsg-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Source: xye Source-Version: 0.12.1+dfsg-4 We believe that the bug you reported is fixed in the latest version of xye, which is due to be installed in the Debian FTP archive: xye-data_0.12.1+dfsg-4_all.deb to main/x/xye/xye-data_0.12.1+dfsg-4_all.deb xye_0.12.1+dfsg-4.debian.tar.gz to main/x/xye/xye_0.12.1+dfsg-4.debian.tar.gz xye_0.12.1+dfsg-4.dsc to main/x/xye/xye_0.12.1+dfsg-4.dsc xye_0.12.1+dfsg-4_amd64.deb to main/x/xye/xye_0.12.1+dfsg-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 672...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bart Martens (supplier of updated xye 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, 08 May 2012 19:04:04 + Source: xye Binary: xye xye-data Architecture: source amd64 all Version: 0.12.1+dfsg-4 Distribution: unstable Urgency: low Maintainer: Bart Martens Changed-By: Bart Martens Description: xye- puzzle game - get all the gems in the room xye-data - puzzle game - get all the gems in the room Closes: 672088 Changes: xye (0.12.1+dfsg-4) unstable; urgency=low . * debian/patches/g++-4.7.diff: Fixes FTBFS. Closes: #672088. Checksums-Sha1: 3e7c14ac3e2e649f1aac16fb9bd5c73b9645be73 1813 xye_0.12.1+dfsg-4.dsc 61becca23c2c5ae1b1c6587dc5ac02b70fb9546d 4436 xye_0.12.1+dfsg-4.debian.tar.gz fe05525128a11ed05bb8b583d28a7241445bf652 261598 xye_0.12.1+dfsg-4_amd64.deb 662979a84a83ddc7675f8ce0b34d777c25bb4bfd 1896238 xye-data_0.12.1+dfsg-4_all.deb Checksums-Sha256: 142d5a20a05bb8166c8ea71f9bb1b383ede27035ce6f897bc60a7a83826646c1 1813 xye_0.12.1+dfsg-4.dsc 657995b5b978d24917aa4a44a382135cf5b1a95cbe7d0863d80a320f49bed00e 4436 xye_0.12.1+dfsg-4.debian.tar.gz 50c4c82df28debe85ea74b02f5b32d41fd47a9f9a1ec14942f44c428a3396506 261598 xye_0.12.1+dfsg-4_amd64.deb c6a94acc23600520230fb4c1d9c779e4a58e980c535ff84c5720198cf2848897 1896238 xye-data_0.12.1+dfsg-4_all.deb Files: 05ebf4ee56386b27450ee6d36513c54e 1813 games optional xye_0.12.1+dfsg-4.dsc 0d78555f414d975c194ac6223053d6e7 4436 games optional xye_0.12.1+dfsg-4.debian.tar.gz 1b28b58fca533a33031b95d575f6e1f8 261598 games optional xye_0.12.1+dfsg-4_amd64.deb f591c561139a1d38de2deb64d8979790 1896238 games optional xye-data_0.12.1+dfsg-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJPqXVkAAoJEDNV9NY7WCHMbagP/jbptAdmB7IYRhhEeU7sg9DM Uq+VIsl+K+15eT+PZVpYVLsCsgWhv0qtyItuBm49YfO9sB22306R6XbJHnhMAuG6 LskctO2jcl5Sgv6qldEKLR6zwV+eSmt/9fXboMuxaJwEzhuWBWP2bLters4sIdxu srgrN2Rkr12PJeDM53F4S1+oKZsbkkKNcSFDOmo5v
Bug#671866: marked as done (gmp: causes gcc ICEs on amd64 and kfreebsd-amd64)
Your message dated Tue, 08 May 2012 19:50:12 + with message-id and subject line Bug#671866: fixed in gmp 2:5.0.5+dfsg-1.1 has caused the Debian Bug report #671866, regarding gmp: causes gcc ICEs on amd64 and kfreebsd-amd64 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.) -- 671866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmp Version: 2:5.0.5+dfsg-1 Severity: grave Justification: renders package unusable Hi, it looks like the update from gmp 2:5.0.4+dfsg-1 to 2:5.0.5+dfsg-1 causes gcc to ICE on the buildds. See e.g. https://buildd.debian.org/status/fetch.php?pkg=ufraw&arch=amd64&ver=0.18-1.1%2Bb2&stamp=1336402119 Cheers, Julien --- End Message --- --- Begin Message --- Source: gmp Source-Version: 2:5.0.5+dfsg-1.1 We believe that the bug you reported is fixed in the latest version of gmp, which is due to be installed in the Debian FTP archive: gmp_5.0.5+dfsg-1.1.diff.gz to main/g/gmp/gmp_5.0.5+dfsg-1.1.diff.gz gmp_5.0.5+dfsg-1.1.dsc to main/g/gmp/gmp_5.0.5+dfsg-1.1.dsc lib32gmp-dev_5.0.5+dfsg-1.1_amd64.deb to main/g/gmp/lib32gmp-dev_5.0.5+dfsg-1.1_amd64.deb lib32gmp10_5.0.5+dfsg-1.1_amd64.deb to main/g/gmp/lib32gmp10_5.0.5+dfsg-1.1_amd64.deb lib32gmpxx4_5.0.5+dfsg-1.1_amd64.deb to main/g/gmp/lib32gmpxx4_5.0.5+dfsg-1.1_amd64.deb libgmp-dev_5.0.5+dfsg-1.1_amd64.deb to main/g/gmp/libgmp-dev_5.0.5+dfsg-1.1_amd64.deb libgmp10-doc_5.0.5+dfsg-1.1_all.deb to main/g/gmp/libgmp10-doc_5.0.5+dfsg-1.1_all.deb libgmp10_5.0.5+dfsg-1.1_amd64.deb to main/g/gmp/libgmp10_5.0.5+dfsg-1.1_amd64.deb libgmp3-dev_5.0.5+dfsg-1.1_amd64.deb to main/g/gmp/libgmp3-dev_5.0.5+dfsg-1.1_amd64.deb libgmpxx4ldbl_5.0.5+dfsg-1.1_amd64.deb to main/g/gmp/libgmpxx4ldbl_5.0.5+dfsg-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 671...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated gmp 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, 08 May 2012 19:24:03 +0200 Source: gmp Binary: libgmp10 libgmpxx4ldbl libgmp-dev lib32gmp10 lib32gmpxx4 lib32gmp-dev lib64gmp10 lib64gmpxx4 lib64gmp-dev libgmp10-doc libgmp3-dev Architecture: source all amd64 Version: 2:5.0.5+dfsg-1.1 Distribution: unstable Urgency: low Maintainer: Debian Science Team Changed-By: Julien Cristau Description: lib32gmp-dev - Multiprecision arithmetic library developers tools (32bit) lib32gmp10 - Multiprecision arithmetic library (32bit) lib32gmpxx4 - Multiprecision arithmetic library (C++ bindings, 32bit) lib64gmp-dev - Multiprecision arithmetic library developers tools (64bit) lib64gmp10 - Multiprecision arithmetic library (64bit library) lib64gmpxx4 - Multiprecision arithmetic library (C++ bindings, 64bit) libgmp-dev - Multiprecision arithmetic library developers tools libgmp10 - Multiprecision arithmetic library libgmp10-doc - Multiprecision arithmetic library example code libgmp3-dev - Multiprecision arithmetic library developers tools libgmpxx4ldbl - Multiprecision arithmetic library (C++ bindings) Closes: 671866 Changes: gmp (2:5.0.5+dfsg-1.1) unstable; urgency=low . * Non-maintainer upload. * Revert to --disable-fat, as it seems to cause gcc to abort on some machines (closes: #671866) Checksums-Sha1: c3eba4677a7ce69bf4e8c2b311a621f09df2c124 2489 gmp_5.0.5+dfsg-1.1.dsc 278acb0bf899dd73d48024d4031d92f4415181fc 18219 gmp_5.0.5+dfsg-1.1.diff.gz 30bb070a7e6b7443d3ce3a646752e7eae1b78219 160090 libgmp10-doc_5.0.5+dfsg-1.1_all.deb 352894a346e0891b12854ba890f4881dafd46677 250342 libgmp10_5.0.5+dfsg-1.1_amd64.deb ece357ef8dc214027e8ffd606c0fb41afebc4a22 21402 libgmpxx4ldbl_5.0.5+dfsg-1.1_amd64.deb 4c25bc708064805e21561470feb1c4cab633807a 608022 libgmp-dev_5.0.5+dfsg-1.1_amd64.deb 1601aaafea2f51210adea364fa5b35e45e0103ac 234012 lib32gmp10_5.0.5+dfsg-1.1_amd64.deb c03bfed781c415083d0f0646816b0343e153b5a7 21000 lib32gmpxx4_5.0.5+dfsg-1.1_amd64.deb b6effe3bf807e031963ae9cb1bc6c39fc0c1a071 302710 lib32gmp-dev_5.0.5+dfsg-1.1_amd64.deb 4226d1d0717bbc89ca3067ec6e4fe3461b4c2b1c 13550 libgmp3-dev_5.0.5+dfsg-1.1_amd64.deb Checksums-Sha256: 258a55715
Bug#671866: gmp: causes gcc ICEs on amd64 and kfreebsd-amd64
On Tue, May 8, 2012 at 19:43:41 +0200, Laurent Fousse wrote: > Hi, > > * Julien Cristau [Tue, May 08, 2012 at 07:19:15PM +0200]: > > On Mon, May 7, 2012 at 22:09:55 -0500, Steve M. Robbins wrote: > > > > > Interesting. It could well be the configure option. For the past 6 > > > years, Debian built using --disable-fat on amd64. I changed it > > > because there are both bug workarounds and code speedups that are > > > processor-based. So it makes more sense for the code to detect the > > > processor at runtime. > > > > > As I'd like this fixed ASAP to get the buildds back in working > > condition, I'll be preparing a NMU with --disable-fat. Please yell if > > you think I shouldn't upload it. > > Could you confirm that it fixes the issue? Anyway, I see no problem > with that. > Just re-tested, on a kvm guest, trying to build the hello package: - fresh sid build chroot, gcc aborts - with a local no-change rebuild of libgmp10, gcc aborts - with a --disable-fat libgmp10, build works fine NMU diff below. Cheers, Julien diff -u gmp-5.0.5+dfsg/debian/changelog gmp-5.0.5+dfsg/debian/changelog --- gmp-5.0.5+dfsg/debian/changelog +++ gmp-5.0.5+dfsg/debian/changelog @@ -1,3 +1,11 @@ +gmp (2:5.0.5+dfsg-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Revert to --disable-fat, as it seems to cause gcc to abort on some +machines (closes: #671866) + + -- Julien Cristau Tue, 08 May 2012 19:24:03 +0200 + gmp (2:5.0.5+dfsg-1) unstable; urgency=low * New upstream. diff -u gmp-5.0.5+dfsg/debian/rules gmp-5.0.5+dfsg/debian/rules --- gmp-5.0.5+dfsg/debian/rules +++ gmp-5.0.5+dfsg/debian/rules @@ -44,7 +44,7 @@ lib64dir = usr/lib64 -confflags = --prefix=/usr --enable-cxx --enable-fat +confflags = --prefix=/usr --enable-cxx --disable-fat ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE)) AR = ar signature.asc Description: Digital signature
Bug#667385: marked as done (sunpinyin: ftbfs with GCC-4.7)
Your message dated Tue, 08 May 2012 19:21:13 + with message-id and subject line Bug#667385: fixed in sunpinyin 2.0.3+git20120404-1 has caused the Debian Bug report #667385, regarding sunpinyin: 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.) -- 667385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sunpinyin Version: 2.0.3-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. src/lexicon/genPYT.cpp:117: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/sunpinyin_2.0.3-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. [...] g++ -o src/ime-core/imi_view_classic.os -c -O2 -g -pipe -DHAVE_CONFIG_H -DSUNPINYIN_DATA_DIR='"/usr/lib/sunpinyin/data"' -fPIC -I. -Isrc -Isrc/pinyin -Isrc/ime-core -Isrc/lexicon -Isrc/slm -Isrc/slm/tslmendian -Isrc/slm/slmprune -Isrc/slm/slmbuild -Isrc/slm/thread -Isrc/slm/slmseg -Isrc/slm/getWordFreq -Isrc/slm/slminfo -Isrc/slm/tslmpack -Isrc/slm/tslminfo -Isrc/slm/tools -Isrc/slm/mmseg -Isrc/slm/ids2ngram src/ime-core/imi_view_classic.cpp g++ -o src/ime-core/imi_winHandler.os -c -O2 -g -pipe -DHAVE_CONFIG_H -DSUNPINYIN_DATA_DIR='"/usr/lib/sunpinyin/data"' -fPIC -I. -Isrc -Isrc/pinyin -Isrc/ime-core -Isrc/lexicon -Isrc/slm -Isrc/slm/tslmendian -Isrc/slm/slmprune -Isrc/slm/slmbuild -Isrc/slm/thread -Isrc/slm/slmseg -Isrc/slm/getWordFreq -Isrc/slm/slminfo -Isrc/slm/tslmpack -Isrc/slm/tslminfo -Isrc/slm/tools -Isrc/slm/mmseg -Isrc/slm/ids2ngram src/ime-core/imi_winHandler.cpp g++ -o src/ime-core/ic_history.os -c -O2 -g -pipe -DHAVE_CONFIG_H -DSUNPINYIN_DATA_DIR='"/usr/lib/sunpinyin/data"' -fPIC -I. -Isrc -Isrc/pinyin -Isrc/ime-core -Isrc/lexicon -Isrc/slm -Isrc/slm/tslmendian -Isrc/slm/slmprune -Isrc/slm/slmbuild -Isrc/slm/thread -Isrc/slm/slmseg -Isrc/slm/getWordFreq -Isrc/slm/slminfo -Isrc/slm/tslmpack -Isrc/slm/tslminfo -Isrc/slm/tools -Isrc/slm/mmseg -Isrc/slm/ids2ngram src/ime-core/ic_history.cpp src/ime-core/ic_history.cpp: In member function 'bool CBigramHistory::loadFromFile(const char*)': src/ime-core/ic_history.cpp:186:36: error: 'read' was not declared in this scope src/ime-core/ic_history.cpp:190:14: error: 'close' was not declared in this scope scons: *** [src/ime-core/ic_history.os] Error 1 scons: building terminated because of errors. make: [install-stamp] Error 2 (ignored) for p in genpyt idngram_merge slminfo slmseg tslminfo getWordFreq ids2ngram mmseg slmbuild slmprune slmthread tslmendian tslmpack; do install -D -m 0755 build/$p /«PKGBUILDDIR»/debian/tmp/usr/bin/$p; done install: cannot stat `build/genpyt': No such file or directory install: cannot stat `build/idngram_merge': No such file or directory install: cannot stat `build/slminfo': No such file or directory install: cannot stat `build/slmseg': No such file or directory install: cannot stat `build/tslminfo': No such file or directory install: cannot stat `build/getWordFreq': No such file or directory install: cannot stat `build/ids2ngram': No such file or directory install: cannot stat `build/mmseg': No such file or directory install: cannot stat `build/slmbuild': No such file or directory install: cannot stat `build/slmprune': No such file or directory install: cannot stat `build/slmthread': No such file or directory install: cannot stat `build/tslmendian': No such file or directory install: cannot stat `build/tslmpack': No such file or directory make: [install-stamp] Error 1 (ignored) mkdir -p /«PKGBUILDDIR»/debian/tmp/usr/share/sunpinyin/ cp -r python /«PKGBUILDDIR»/debian/tmp/usr/share/sunpinyin/ dh_install --sourcedir=debian/tmp --fail-missing dh_install: libsunpinyin-dev missing files (usr/include/*), aborting make: *** [install-stamp] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 --- End Message --- --- Begin Message --- Source: sunpinyin Source-Version: 2.0.3+git20120404-1 We believe that the bug you reported is fixe
Bug#665033: marked as done (smarty-gettext: Fails to install, nmet dependencies)
Your message dated Tue, 08 May 2012 19:04:36 + with message-id and subject line Bug#665040: fixed in smarty-gettext 1.0b1-5 has caused the Debian Bug report #665040, regarding smarty-gettext: Fails to install, nmet dependencies 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.) -- 665040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lwat Version: 0.17-4.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > ┌──┐ > │ Install lwat build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-lwat-dummy : Depends: smarty-gettext but it is not > going to be installed > E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/21/lwat_0.17-4.2.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 --- --- Begin Message --- Source: smarty-gettext Source-Version: 1.0b1-5 We believe that the bug you reported is fixed in the latest version of smarty-gettext, which is due to be installed in the Debian FTP archive: smarty-gettext_1.0b1-5.debian.tar.gz to main/s/smarty-gettext/smarty-gettext_1.0b1-5.debian.tar.gz smarty-gettext_1.0b1-5.dsc to main/s/smarty-gettext/smarty-gettext_1.0b1-5.dsc smarty-gettext_1.0b1-5_all.deb to main/s/smarty-gettext/smarty-gettext_1.0b1-5_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated smarty-gettext 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, 08 May 2012 20:41:04 +0200 Source: smarty-gettext Binary: smarty-gettext Architecture: source all Version: 1.0b1-5 Distribution: unstable Urgency: low Maintainer: Raphaël Hertzog Changed-By: Raphaël Hertzog Description: smarty-gettext - Gettext plugin enabling internationalization in Smarty Closes: 665033 665040 672103 Changes: smarty-gettext (1.0b1-5) unstable; urgency=low . * Move files to the new location used by smarty 3. * Ajust depends to ensure we have smarty using the new location too. * Update Standards-Version to 3.9.3 (no change needed). * Increase debhelper compat level to 9. * Depend on "smarty3" instead of "smarty" since no proper transition has been done with the latter being removed and the former one being orphaned. :-( Closes: #665033, #665040, #672103 Checksums-Sha1: f7c8759f9d1c79628be9682cab96afb6acd5e895 1942 smarty-gettext_1.0b1-5.dsc c58be2e2c258ed3df90937f93304e6fff4e93edd 2044 smarty-gettext_1.0b1-5.debian.tar.gz e61e47d76991a37cb0853dd34ab2ef2ef0855269 8700 smarty-gettext_1.0b1-5_all.deb Checksums-Sha256: ddb674e70641a933f94be4cbd075a043b311b1ebe626c669f1ec34ed1fc3d5e6 1942 smarty-gettext_1.0b1-5.dsc 54aa403898f6b17c8a7b5a6c0e6be2a038a48e63438cbe39e415612d29241855 2044 smarty-gettext_1.0b1-5.debian.tar.gz 10c84ab1a6848426872a70cb6ac70fad7c333d65695ef54ea869ca407e6da144 8700 smarty-gettext_1.0b1-5_all.deb Files: 9d8f3cd17538a9617afb4453a32552e2 1942 web optional smarty-gettex
Bug#665040: marked as done (slbackup-php: FTBFS: build-dependency not installable: smarty-gettext)
Your message dated Tue, 08 May 2012 19:04:36 + with message-id and subject line Bug#665040: fixed in smarty-gettext 1.0b1-5 has caused the Debian Bug report #665040, regarding slbackup-php: FTBFS: build-dependency not installable: smarty-gettext 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.) -- 665040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slbackup-php Version: 0.3-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > ┌──┐ > │ Install slbackup-php build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-slbackup-php-dummy : Depends: smarty-gettext but it is > not going to be installed > E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/21/slbackup-php_0.3-3.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 --- --- Begin Message --- Source: smarty-gettext Source-Version: 1.0b1-5 We believe that the bug you reported is fixed in the latest version of smarty-gettext, which is due to be installed in the Debian FTP archive: smarty-gettext_1.0b1-5.debian.tar.gz to main/s/smarty-gettext/smarty-gettext_1.0b1-5.debian.tar.gz smarty-gettext_1.0b1-5.dsc to main/s/smarty-gettext/smarty-gettext_1.0b1-5.dsc smarty-gettext_1.0b1-5_all.deb to main/s/smarty-gettext/smarty-gettext_1.0b1-5_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated smarty-gettext 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, 08 May 2012 20:41:04 +0200 Source: smarty-gettext Binary: smarty-gettext Architecture: source all Version: 1.0b1-5 Distribution: unstable Urgency: low Maintainer: Raphaël Hertzog Changed-By: Raphaël Hertzog Description: smarty-gettext - Gettext plugin enabling internationalization in Smarty Closes: 665033 665040 672103 Changes: smarty-gettext (1.0b1-5) unstable; urgency=low . * Move files to the new location used by smarty 3. * Ajust depends to ensure we have smarty using the new location too. * Update Standards-Version to 3.9.3 (no change needed). * Increase debhelper compat level to 9. * Depend on "smarty3" instead of "smarty" since no proper transition has been done with the latter being removed and the former one being orphaned. :-( Closes: #665033, #665040, #672103 Checksums-Sha1: f7c8759f9d1c79628be9682cab96afb6acd5e895 1942 smarty-gettext_1.0b1-5.dsc c58be2e2c258ed3df90937f93304e6fff4e93edd 2044 smarty-gettext_1.0b1-5.debian.tar.gz e61e47d76991a37cb0853dd34ab2ef2ef0855269 8700 smarty-gettext_1.0b1-5_all.deb Checksums-Sha256: ddb674e70641a933f94be4cbd075a043b311b1ebe626c669f1ec34ed1fc3d5e6 1942 smarty-gettext_1.0b1-5.dsc 54aa403898f6b17c8a7b5a6c0e6be2a038a48e63438cbe39e415612d29241855 2044 smarty-gettext_1.0b1-5.debian.tar.gz 10c84ab1a6848426872a70cb6ac70fad7c333d65695ef54ea869ca407e6da144 8700 smarty-gettext_1.0b1-5_all.deb Files: 9d8f3cd17538a9617afb4453a325
Bug#665033: marked as done (smarty-gettext: Fails to install, nmet dependencies)
Your message dated Tue, 08 May 2012 19:04:36 + with message-id and subject line Bug#665033: fixed in smarty-gettext 1.0b1-5 has caused the Debian Bug report #665033, regarding smarty-gettext: Fails to install, nmet dependencies 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.) -- 665033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lwat Version: 0.17-4.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > ┌──┐ > │ Install lwat build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-lwat-dummy : Depends: smarty-gettext but it is not > going to be installed > E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/21/lwat_0.17-4.2.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 --- --- Begin Message --- Source: smarty-gettext Source-Version: 1.0b1-5 We believe that the bug you reported is fixed in the latest version of smarty-gettext, which is due to be installed in the Debian FTP archive: smarty-gettext_1.0b1-5.debian.tar.gz to main/s/smarty-gettext/smarty-gettext_1.0b1-5.debian.tar.gz smarty-gettext_1.0b1-5.dsc to main/s/smarty-gettext/smarty-gettext_1.0b1-5.dsc smarty-gettext_1.0b1-5_all.deb to main/s/smarty-gettext/smarty-gettext_1.0b1-5_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated smarty-gettext 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, 08 May 2012 20:41:04 +0200 Source: smarty-gettext Binary: smarty-gettext Architecture: source all Version: 1.0b1-5 Distribution: unstable Urgency: low Maintainer: Raphaël Hertzog Changed-By: Raphaël Hertzog Description: smarty-gettext - Gettext plugin enabling internationalization in Smarty Closes: 665033 665040 672103 Changes: smarty-gettext (1.0b1-5) unstable; urgency=low . * Move files to the new location used by smarty 3. * Ajust depends to ensure we have smarty using the new location too. * Update Standards-Version to 3.9.3 (no change needed). * Increase debhelper compat level to 9. * Depend on "smarty3" instead of "smarty" since no proper transition has been done with the latter being removed and the former one being orphaned. :-( Closes: #665033, #665040, #672103 Checksums-Sha1: f7c8759f9d1c79628be9682cab96afb6acd5e895 1942 smarty-gettext_1.0b1-5.dsc c58be2e2c258ed3df90937f93304e6fff4e93edd 2044 smarty-gettext_1.0b1-5.debian.tar.gz e61e47d76991a37cb0853dd34ab2ef2ef0855269 8700 smarty-gettext_1.0b1-5_all.deb Checksums-Sha256: ddb674e70641a933f94be4cbd075a043b311b1ebe626c669f1ec34ed1fc3d5e6 1942 smarty-gettext_1.0b1-5.dsc 54aa403898f6b17c8a7b5a6c0e6be2a038a48e63438cbe39e415612d29241855 2044 smarty-gettext_1.0b1-5.debian.tar.gz 10c84ab1a6848426872a70cb6ac70fad7c333d65695ef54ea869ca407e6da144 8700 smarty-gettext_1.0b1-5_all.deb Files: 9d8f3cd17538a9617afb4453a32552e2 1942 web optional smarty-gettex
Bug#665040: marked as done (slbackup-php: FTBFS: build-dependency not installable: smarty-gettext)
Your message dated Tue, 08 May 2012 19:04:36 + with message-id and subject line Bug#665033: fixed in smarty-gettext 1.0b1-5 has caused the Debian Bug report #665033, regarding slbackup-php: FTBFS: build-dependency not installable: smarty-gettext 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.) -- 665033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slbackup-php Version: 0.3-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > ┌──┐ > │ Install slbackup-php build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-slbackup-php-dummy : Depends: smarty-gettext but it is > not going to be installed > E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/21/slbackup-php_0.3-3.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 --- --- Begin Message --- Source: smarty-gettext Source-Version: 1.0b1-5 We believe that the bug you reported is fixed in the latest version of smarty-gettext, which is due to be installed in the Debian FTP archive: smarty-gettext_1.0b1-5.debian.tar.gz to main/s/smarty-gettext/smarty-gettext_1.0b1-5.debian.tar.gz smarty-gettext_1.0b1-5.dsc to main/s/smarty-gettext/smarty-gettext_1.0b1-5.dsc smarty-gettext_1.0b1-5_all.deb to main/s/smarty-gettext/smarty-gettext_1.0b1-5_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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated smarty-gettext 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, 08 May 2012 20:41:04 +0200 Source: smarty-gettext Binary: smarty-gettext Architecture: source all Version: 1.0b1-5 Distribution: unstable Urgency: low Maintainer: Raphaël Hertzog Changed-By: Raphaël Hertzog Description: smarty-gettext - Gettext plugin enabling internationalization in Smarty Closes: 665033 665040 672103 Changes: smarty-gettext (1.0b1-5) unstable; urgency=low . * Move files to the new location used by smarty 3. * Ajust depends to ensure we have smarty using the new location too. * Update Standards-Version to 3.9.3 (no change needed). * Increase debhelper compat level to 9. * Depend on "smarty3" instead of "smarty" since no proper transition has been done with the latter being removed and the former one being orphaned. :-( Closes: #665033, #665040, #672103 Checksums-Sha1: f7c8759f9d1c79628be9682cab96afb6acd5e895 1942 smarty-gettext_1.0b1-5.dsc c58be2e2c258ed3df90937f93304e6fff4e93edd 2044 smarty-gettext_1.0b1-5.debian.tar.gz e61e47d76991a37cb0853dd34ab2ef2ef0855269 8700 smarty-gettext_1.0b1-5_all.deb Checksums-Sha256: ddb674e70641a933f94be4cbd075a043b311b1ebe626c669f1ec34ed1fc3d5e6 1942 smarty-gettext_1.0b1-5.dsc 54aa403898f6b17c8a7b5a6c0e6be2a038a48e63438cbe39e415612d29241855 2044 smarty-gettext_1.0b1-5.debian.tar.gz 10c84ab1a6848426872a70cb6ac70fad7c333d65695ef54ea869ca407e6da144 8700 smarty-gettext_1.0b1-5_all.deb Files: 9d8f3cd17538a9617afb4453a325
Processed: Re: Bug#656115: closed by Mathieu Malaterre (Bug#656115: fixed in vtk 5.8.0-10)
Processing commands for cont...@bugs.debian.org:
> notfixed 656115 5.8.0-11
Bug #656115 {Done: Mathieu Malaterre }
[libvtk5-dev] libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK without
libvtk5-qt4-dev being installed
Bug #584300 {Done: Mathieu Malaterre }
[libvtk5-dev] libvtk5-dev: Remove information about wrapped languages from
VTKConfig.cmake
No longer marked as fixed in versions vtk/5.8.0-11.
No longer marked as fixed in versions vtk/5.8.0-11.
> found 656115 5.8.0-11
Bug #656115 {Done: Mathieu Malaterre }
[libvtk5-dev] libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK without
libvtk5-qt4-dev being installed
Bug #584300 {Done: Mathieu Malaterre }
[libvtk5-dev] libvtk5-dev: Remove information about wrapped languages from
VTKConfig.cmake
Did not alter found versions and reopened.
Did not alter found versions and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
584300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584300
656115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656115
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#672038:
Fixed in sludge 2.2-1 [1,2]. I'm waiting for a sponsor to upload it. [3] Best regards, Tobias [1] http://mentors.debian.net/package/sludge [2] http://mentors.debian.net/debian/pool/main/s/sludge/sludge_2.2-1.dsc [3] http://wiki.debian.org/Games/Sponsors/Queue -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656115: closed by Mathieu Malaterre (Bug#656115: fixed in vtk 5.8.0-10)
notfixed 656115 5.8.0-11
found 656115 5.8.0-11
thanks
My bad. I did not realize VTKConfigQt.cmake is still shipped within
libvtk5-dev and not libvtk5-qt4-dev
very sorry about that.
On Tue, May 8, 2012 at 7:57 PM, Jochen Sprickerhof
wrote:
> found 656115 5.8.0-11
> thanks
>
> Hi,
>
> I'm sorry, but this bug is _still_ not fixed with the last upload:
> $ dpkg -l libvtk5-qt4-dev libvtk5-dev
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Description
> +++-==-==-
> ii libvtk5-dev 5.8.0-11 VTK header files for building C++ code
> No packages found matching libvtk5-qt4-dev.
>
> $ cat CMakeLists.txt
> cmake_minimum_required(VERSION 2.8)
> find_package(VTK)
> message(STATUS "QVTK found: ${VTK_USE_QVTK}")
>
> $ cmake .
> [..]
>
> -- QVTK found: ON
>
> And it would still be great if the VTKTargets-release.cmake would not clutter
> the output with debug messages like these (or at least have a quiet flat):
> -- The imported target "vtkPythonCore" references the file
> "/usr/lib/libvtkPythonCore.so.5.8.0"
> but this file does not exist. Possible reasons include:
> * The file was deleted, renamed, or moved to another location.
> * An install or uninstall procedure did not complete successfully.
> * The installation package was faulty and contained
> "/usr/lib/vtk-5.8/VTKTargets-release.cmake"
> but not all the files it references.
>
> Thanks,
>
> Jochen
>
>
>
--
Mathieu
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667158: marked as done (esys-particle: ftbfs with GCC-4.7)
Your message dated Tue, 08 May 2012 19:02:21 + with message-id and subject line Bug#667158: fixed in esys-particle 2.1-4 has caused the Debian Bug report #667158, regarding esys-particle: 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.) -- 667158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: esys-particle Version: 2.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. ../Geometry/CircularNeighbourTable.hpp:227:81: error: 'getVecIndex' 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/esys-particle_2.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. [...] In file included from ../Geometry/CircularNeighbourTable.h:116:0, from ../Geometry/ParticleGenerator.h:18, from ../Geometry/BlockGenerator.h:17, from BlockGenerator.cpp:14: ../Geometry/CircularNeighbourTable.hpp: In instantiation of 'void esys::lsm::CircularNeighbourTable::insert(esys::lsm::CircularNeighbourTable::Particle*) [with TmplParticle = SimpleParticle; esys::lsm::CircularNeighbourTable::Particle = SimpleParticle]': BlockGenerator.cpp:129:35: required from here ../Geometry/CircularNeighbourTable.hpp:227:81: error: 'getVecIndex' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] ../Geometry/CircularNeighbourTable.hpp:227:81: note: declarations in dependent base 'esys::lsm::NeighbourTable' are not found by unqualified lookup ../Geometry/CircularNeighbourTable.hpp:227:81: note: use 'this->getVecIndex' instead ../Geometry/CircularNeighbourTable.hpp:228:81: error: 'getVecIndex' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] ../Geometry/CircularNeighbourTable.hpp:228:81: note: declarations in dependent base 'esys::lsm::NeighbourTable' are not found by unqualified lookup ../Geometry/CircularNeighbourTable.hpp:228:81: note: use 'this->getVecIndex' instead make[4]: *** [BlockGenerator.lo] Error 1 make[4]: *** Waiting for unfinished jobs libtool: compile: mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include -I../Foundation -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -c GeometryInfo.cpp -o GeometryInfo.o >/dev/null 2>&1 libtool: compile: mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include -I../Foundation -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -c VtkXmlWriter.cpp -o VtkXmlWriter.o >/dev/null 2>&1 libtool: compile: mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include -I../Foundation -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -c ParticleFitter.cpp -o ParticleFitter.o >/dev/null 2>&1 libtool: compile: mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include -I../Foundation -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -c GranularGougeBlock3D.cpp -o GranularGougeBlock3D.o >/dev/null 2>&1 libtool: compile: mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include -I../Foundation -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -c GougeBlock3D.cpp -o GougeBlock3D.o >/dev/null 2>&1 libtool: compile: mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include -I../Foundation -D_FORTIFY_SOURCE=2 -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -c RandomBlockGenerator.cpp -o RandomBlockGenerator.o >/dev/null 2>&1 libtool: compile: mpicxx -DHAVE_CON
Bug#584300: marked as done (libvtk5-dev: Remove information about wrapped languages from VTKConfig.cmake)
Your message dated Tue, 8 May 2012 21:00:54 +0200
with message-id
and subject line Re: Bug#656115: closed by Mathieu Malaterre
(Bug#656115: fixed in vtk 5.8.0-10)
has caused the Debian Bug report #656115,
regarding libvtk5-dev: Remove information about wrapped languages from
VTKConfig.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.)
--
656115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvtk5-dev
Version: 5.4.2-7
Severity: wishlist
Tags: patch
Hello,
The file /usr/lib/vtk-5.4/VTKConfig.cmake contains
configuration used when building package, in particular
information about wrapped languages are hardcoded.
For instance VTK_WRAP_PYTHON is always set to true
even if python-vtk is not installed.
This patch puts snippets about wrapped languages into
separate files, which are shipped by python-vtk, vtk-tcl
and libvtk-java.
Please tell me whether I could create a branch on git.d.o
with this patch, maybe it will be easier to discuss this
feature.
Denis
split-vtkconfig.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
fixed 656115 5.8.0-11
thanks
Jochen,
Please do not reopen the bug if you have old vtk packages still
around. Thanks.
$ grep VTK_USE_QT /usr/lib/vtk-5.8/*.cmake
/usr/lib/vtk-5.8/VTKConfigQt.cmake:SET(VTK_USE_QT "ON")
$ dpkg -S /usr/lib/vtk-5.8/VTKConfigQt.cmake
libvtk5-dev: /usr/lib/vtk-5.8/VTKConfigQt.cmake
On Tue, May 8, 2012 at 7:57 PM, Jochen Sprickerhof
wrote:
> found 656115 5.8.0-11
> thanks
>
> Hi,
>
> I'm sorry, but this bug is _still_ not fixed with the last upload:
> $ dpkg -l libvtk5-qt4-dev libvtk5-dev
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Description
> +++-==-==-
> ii libvtk5-dev 5.8.0-11 VTK header files for building C++ code
> No packages found matching libvtk5-qt4-dev.
>
> $ cat CMakeLists.txt
> cmake_minimum_required(VERSION 2.8)
> find_package(VTK)
> message(STATUS "QVTK found: ${VTK_USE_QVTK}")
>
> $ cmake .
> [..]
>
> -- QVTK found: ON
>
> And it would still be great if the VTKTargets-release.cmake would not clutter
> the output with debug messages like these (or at least have a quiet flat):
> -- The imported target "vtkPythonCore" references the file
> "/usr/lib/libvtkPythonCore.so.5.8.0"
> but this file does not exist. Possible reasons include:
> * The file was deleted, renamed, or moved to another location.
> * An install or uninstall procedure did not complete successfully.
> * The installation package was faulty and contained
> "/usr/lib/vtk-5.8/VTKTargets-release.cmake"
> but not all the files it references.
>
> Thanks,
>
> Jochen
>
>
>
--
Mathieu
--- End Message ---
Bug#656115: marked as done (libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK without libvtk5-qt4-dev being installed)
Your message dated Tue, 8 May 2012 21:00:54 +0200
with message-id
and subject line Re: Bug#656115: closed by Mathieu Malaterre
(Bug#656115: fixed in vtk 5.8.0-10)
has caused the Debian Bug report #656115,
regarding libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK without
libvtk5-qt4-dev being installed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
656115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvtk5-dev
Version: 5.8.0-5
Severity: normal
Dear Maintainer,
could you add a test to VTKConfig.cmake, such that it only set's
VTK_USE_QVTK when libvtk5-qt4-dev is installed? For example testing the
presence of /usr/lib/libQVTK.so should work. Otherwise every project
using QVTK would have to test it as well.
Thanks,
Jochen
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (480, 'precise'), (480, 'natty'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/8 CPU cores)
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 libvtk5-dev depends on:
ii libavcodec-dev 4:0.8~beta2-1
ii libavformat-dev4:0.8~beta2-1
ii libavutil-dev 4:0.8~beta2-1
ii libc6-dev 2.13-24
ii libexpat1-dev [libexpat-dev] 2.0.1-7.2
ii libfreetype6-dev 2.4.8-1
ii libgl1-mesa-dev [libgl-dev]7.11.2-1
ii libgl2ps-dev 1.3.6-1
ii libglu1-mesa-dev [libglu-dev] 7.11.2-1
ii libjpeg8-dev [libjpeg-dev] 8c-2
ii libmysqlclient-dev 5.1.58-1
ii libnetcdf-dev 1:4.1.1-6
ii libpng12-dev [libpng-dev] 1.2.46-4
ii libpq-dev 9.1.2-4
ii libqt4-dev 4:4.7.4-2
ii libswscale-dev 4:0.8~beta2-1
ii libtiff-dev4.0.0~beta7-2
ii libvtk5.8 5.8.0-5
ii libx11-dev 2:1.4.4-4
ii libxft-dev 2.2.0-3
ii libxml2-dev2.7.8.dfsg-6
ii libxss-dev 1:1.2.1-2
ii libxt-dev 1:1.1.1-2
ii mpi-default-dev1.0.1
ii tcl8.5-dev 8.5.11-1
ii tk8.5-dev 8.5.11-1
ii x11proto-core-dev 7.0.22-1
ii zlib1g-dev 1:1.2.3.4.dfsg-3
libvtk5-dev recommends no packages.
Versions of packages libvtk5-dev suggests:
pn vtk-doc
pn vtk-examples
-- no debconf information
--- End Message ---
--- Begin Message ---
fixed 656115 5.8.0-11
thanks
Jochen,
Please do not reopen the bug if you have old vtk packages still
around. Thanks.
$ grep VTK_USE_QT /usr/lib/vtk-5.8/*.cmake
/usr/lib/vtk-5.8/VTKConfigQt.cmake:SET(VTK_USE_QT "ON")
$ dpkg -S /usr/lib/vtk-5.8/VTKConfigQt.cmake
libvtk5-dev: /usr/lib/vtk-5.8/VTKConfigQt.cmake
On Tue, May 8, 2012 at 7:57 PM, Jochen Sprickerhof
wrote:
> found 656115 5.8.0-11
> thanks
>
> Hi,
>
> I'm sorry, but this bug is _still_ not fixed with the last upload:
> $ dpkg -l libvtk5-qt4-dev libvtk5-dev
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Description
> +++-==-==-
> ii libvtk5-dev 5.8.0-11 VTK header files for building C++ code
> No packages found matching libvtk5-qt4-dev.
>
> $ cat CMakeLists.txt
> cmake_minimum_required(VERSION 2.8)
> find_package(VTK)
> message(STATUS "QVTK found: ${VTK_USE_QVTK}")
>
> $ cmake .
> [..]
>
> -- QVTK found: ON
>
> And it would still be great if the VTKTargets-release.cmake would not clutter
> the output with debug messages like these (or at least have a quiet flat):
> -- The imported target "vtkPythonCore" references the file
> "/usr/lib/libvtkPythonCore.so.5.8.0"
> but this file does not exist. Possible reasons include:
> * The file was deleted, renamed, or moved to another location.
> * An install or uninstall procedure did not complete successfully.
> * The installation package was faulty and contained
> "/usr/lib/vtk-5.8/VTKTargets-release.cmake"
> but not all the files it references.
>
> Thanks,
>
> Jochen
>
>
>
--
Mathieu
--- End Message ---
Processed: Re: Bug#656115: closed by Mathieu Malaterre (Bug#656115: fixed in vtk 5.8.0-10)
Processing commands for cont...@bugs.debian.org: > fixed 656115 5.8.0-11 Bug #656115 [libvtk5-dev] libvtk5-dev: VTKConfig.cmake sets VTK_USE_QVTK without libvtk5-qt4-dev being installed Bug #584300 [libvtk5-dev] libvtk5-dev: Remove information about wrapped languages from VTKConfig.cmake Marked as fixed in versions vtk/5.8.0-11. Marked as fixed in versions vtk/5.8.0-11. > thanks Stopping processing here. Please contact me if you need assistance. -- 584300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584300 656115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656115 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#672097: lxappearance-obconf: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672097 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672100: presage: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672100 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672098: ekiga: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672098 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672099: gvfs: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672099 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672095: serna-free: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672095 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672094: protobuf: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672094 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672093: jxgrabkey: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672093 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672091: qpid-cpp: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672091 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672090: bowtie2: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672090 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672089: icewm: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672089 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672088: xye: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672088 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672087: lilypond: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672087 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672086: libsfml: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672086 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672085: qof: ftbfs with GCC-4.7
user debian-...@lists.debian.org usertags 672085 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
