Bug#640969: Exits with: ImportError: No module named bpython.cli
tags 640969 confirmed
thanks
On Fri, 09 Sep 2011 12:31:12 +0900, Mitsubishi Evo II wrote:
I just upgraded to bpython, and when running it from the command line
it immediatly exits as follows:
% bpython
Traceback (most recent call last):
File /usr/bin/bpython, line 9, in module
load_entry_point('bpython==0.10.1', 'console_scripts', 'bpython')()
File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 305, in
load_entry_point return get_distribution(dist).load_entry_point(group, name)
File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 2245, in
load_entry_point return ep.load()
File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 1955, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
ImportError: No module named bpython.cli
Uhm, ok, confirmed, seems like an upgrade problem caused by the switch from
pysupport to dh_python2.
Reinstalling it fixes the problem -- I'll try to fix the upgrade path as well.
Kindly,
David
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://deb.li/dapal
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
Bug#630517: icu: FTBFS on the kfreebsd-amd64
tags 630517 + patch
user debian-...@lists.debian.org
usertag 630517 + kfreebsd
--
Hi.
Please apply patch bellow to configure.in
and propagate it into configure.
Petr
--- source/configure.in
+++ source/configure.in
@@ -604,7 +604,7 @@
# Check to see if genccode can generate simple assembly.
GENCCODE_ASSEMBLY=
case ${host} in
-*-linux*|i*86-*-*bsd*|i*86-pc-gnu)
+*-linux*|*-kfreebsd*-gnu*|i*86-*-*bsd*|i*86-pc-gnu)
if test $GCC = yes; then
# We're using gcc, and the simple -a gcc command line works for
genccode
GENCCODE_ASSEMBLY=-a gcc
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: icu: FTBFS on the kfreebsd-amd64
Processing commands for cont...@bugs.debian.org: tags 630517 + patch Bug #630517 [src:icu] FTBFS: icu: ../lib/libicudata.a: could not read symbols: Archive has no index; run ranlib to add one Added tag(s) patch. user debian-...@lists.debian.org Setting user to debian-...@lists.debian.org (was petr.salin...@seznam.cz). usertag 630517 + kfreebsd Bug#630517: FTBFS: icu: ../lib/libicudata.a: could not read symbols: Archive has no index; run ranlib to add one There were no usertags set. Usertags are now: kfreebsd. -- Stopping processing here. Please contact me if you need assistance. -- 630517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630517 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#640969: Exits with: ImportError: No module named bpython.cli
Hi David, * David Paleino da...@debian.org [110909 15:02]: Uhm, ok, confirmed, seems like an upgrade problem caused by the switch from pysupport to dh_python2. Ahh. Reinstalling it fixes the problem -- I'll try to fix the upgrade path as well. Ok, thanks for the speedy confirmation and workaround. Cheers, Evo. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640960: CVE-?????: broken CTCP parsing can be used to crash the core
Hi, thanks for the notice. I'll prepare a new package upload tonight. Thanks, Thomas Am Freitag, den 09.09.2011 um 0:58 schrieb Timo Juhani Lindfors: Package: quassel Version: 0.6.3-2 Severity: important Tags: security When people send me 0010 75 74 61 73 21 7a 7a 40 31 37 38 2d 33 37 2d 31 |utas!zz@178-37-1| 0020 30 34 2d 34 32 2e 61 64 73 6c 2e 69 6e 65 74 69 |04-42.adsl.ineti| 0030 61 2e 70 6c 20 4a 4f 49 4e 20 23 71 75 61 73 73 |a.pl JOIN #quass| 0040 65 6c 0d 0a 37 36 36 37 30 3a 55 c3 8c a6 5b 7e |el..76670:U...[~| 0050 8a 26 3a 6b 75 74 61 73 21 7a 7a 40 31 37 38 2d |.:kutas!zz@178-| 0060 33 37 2d 31 30 34 2d 34 32 2e 61 64 73 6c 2e 69 |37-104-42.adsl.i| 0070 6e 65 74 69 61 2e 70 6c 20 50 52 49 56 4d 53 47 |netia.pl PRIVMSG| 0080 20 23 71 75 61 73 73 65 6c 20 3a 01 41 43 54 49 | #quassel :.ACTI| 0090 4f 4e 20 01 01 56 45 52 53 49 4f 4e 01 01 56 45 |ON ..VERSION..VE| 00a0 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 |RSION..VERSION..| 00b0 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e |VERSION..VERSION| 00c0 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 |..VERSION..VERSI| 00d0 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 |ON..VERSION..VER| 00e0 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 |SION..VERSION..V| 00f0 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 |ERSION..VERSION.| 0100 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f |.VERSION..VERSIO| 0110 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 |N..VERSION..VERS| 0120 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 |ION..VERSION..VE| 0130 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 |RSION..VERSION..| 0140 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e |VERSION..VERSION| 0150 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 |..VERSION..VERSI| 0160 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 |ON..VERSION..VER| 0170 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 |SION..VERSION..V| 0180 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 |ERSION..VERSION.| 0190 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f |.VERSION..VERSIO| 01a0 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 |N..VERSION..VERS| 01b0 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 |ION..VERSION..VE| 01c0 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 |RSION..VERSION..| 01d0 56 45 52 53 49 4f 4e 01 01 0d 0a |VERSION| quasselcore crashes. The upstream bug report is http://bugs.quassel-irc.org/issues/1095 Gentoo bug report is https://bugs.gentoo.org/382313 (there is some mention about requesting a CVE) Workaround: 1) Settings-Configure Quassel-IRC-Ignore List-New 2) Strictness: Dynamic 3) Rule Type: CTCP 4) Ignore Rule: * VERSION 5) Scope: Global Where is the Vcs for quassel? I could prepare a fix. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages quassel depends on: ii dbus-x111.2.24-4+squeeze1simple interprocess messaging syst ii gawk1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8GCC support library ii libphonon4 4:4.6.0really4.4.2-1 the core library of the Phonon mul ii libqt4-dbus 4:4.6.3-4+squeeze1 Qt 4 D-Bus module ii libqt4-network 4:4.6.3-4+squeeze1 Qt 4 network module ii libqt4-script 4:4.6.3-4+squeeze1 Qt 4 script module ii libqt4-sql 4:4.6.3-4+squeeze1 Qt 4 SQL module ii libqt4-sql-sqlite 4:4.6.3-4+squeeze1 Qt 4 SQLite 3 database driver ii libqt4-webkit 4:4.6.3-4+squeeze1 Qt 4 WebKit module ii libqt4-xmlpatterns 4:4.6.3-4+squeeze1 Qt 4 XML patterns module ii libqtcore4 4:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii phonon 4:4.6.0really4.4.2-1 metapackage for the Phonon multime ii quassel-data0.6.3-2 distributed IRC client - shared da quassel recommends no packages. quassel 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#639178: tar: FTBFS(kfreebsd): 56: incremental dump when the parent directory is unreadable FAILED (listed03.at:25)
Hi, just to make it clear. The tar works as expected, it just emits extra warning. Current tar version expects more than POSIX guarantees. Even inside the tar source src/misc.c is written: FIXME: There should be no need to get the absolute file name. getcwd is slow, it might fail, and it does not necessarily return a canonical name even when it succeeds. Perhaps we can use dev+ino pairs instead of names? */ Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640874: leave: debian/rules is not a Makefile
On Thu, Sep 08, 2011 at 04:53:01PM +0200, Raphael Hertzog wrote: And still, this is a Makefile so you can quickly reuse Makefile snippets that others have been writing to add support for supplementary targets (like get-orig-source) or even to influence the environment (like the Makefile snippets that dpkg 1.16.1 is going to provide). Same can work for pretty much any other similar language. Except that by standardizing on make we avoid to have to duplicate those things for multiple languages! OTOH, if you actually want to that stuff from e.g. a Python debian/rules file, you should be able to simply run make -f /usr/share/common/stuff.mk get-orig-source ? :) -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640874: leave: debian/rules is not a Makefile
On Thu, Sep 08, 2011 at 04:18:34PM -0700, Russ Allbery wrote: (I don't recall if anyone tried to loop you into that discussion; if that didn't happen, that was a flaw in that discussion process to be sure.) Nope, sorry, I missed that. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640874: leave: debian/rules is not a Makefile
Since my reasoning here didn't seem to leave a particular positive dent with those tech-ctte members who have responded so far, I would just like to solicit Ian Jackson's input, given his role in defining and implementing the debian/rules calling convention originally. In other worse, if I can't convince the original author of a non-make-dependent API that the API isn't make-dependent, there is no recourse but to yield :) Or if my memory serves me wrong and it was instead some other person, particularly one that isn't intricately involved with Debian or can't be reached any more, I'm also done. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 640195 serious Bug #640195 [paraview] paraview-dev transition Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 640195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640195 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: your mail
Processing commands for cont...@bugs.debian.org: tag 629942 pending Bug #629942 [python-ecryptfs] python-ecryptfs: missing dependency on python Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 629942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629942 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#565092: marked as done (qgo: ftbfs with gcc-4.5)
Your message dated Fri, 09 Sep 2011 08:49:12 + with message-id e1r1wls-0006xk...@franck.debian.org and subject line Bug#565092: fixed in qgo 1.5.4-r3-2.1 has caused the Debian Bug report #565092, regarding qgo: ftbfs with gcc-4.5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 565092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qgo Version: 1.5.4-r3-1 Severity: normal Tags: sid User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.5 The package fails to build in a test rebuild on at least amd64 with gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4. For the compiler version used, see: http://lists.debian.org/debian-devel/2010/01/msg00230.html The full build log can be found at: http://people.debian.org/~lucas/logs/2010/01/08b/qgo_1.5.4-r3-1_lsid64b.buildlog The last lines of the build log are cwat the end of this report. The reason of the build failure is likely in the package (compiler or linker message found in the build log), if this turns out as a gcc bug, please reassign to the gcc-4.5 package. If the build ends with a message confused by earlier errors, bailing out, please ignore it for now; these compiler errors are filed separately. [...] gamedialog.cpp:562:70: error: initializing argument 2 of 'QColor::QColor(QRgb, uint)' gamedialog.cpp:563:70: error: cannot call constructor 'QColor::QColor' directly gamedialog.cpp:563:70: note: for a function-style cast, remove the redundant '::QColor' gamedialog.cpp:563:70: error: invalid conversion from 'const char*' to 'QRgb' gamedialog.cpp:563:70: error: initializing argument 1 of 'QColor::QColor(QRgb, uint)' gamedialog.cpp:563:70: error: invalid conversion from 'const char*' to 'uint' gamedialog.cpp:563:70: error: initializing argument 2 of 'QColor::QColor(QRgb, uint)' gamedialog.cpp:569:71: error: cannot call constructor 'QColor::QColor' directly gamedialog.cpp:569:71: note: for a function-style cast, remove the redundant '::QColor' gamedialog.cpp:570:70: error: cannot call constructor 'QColor::QColor' directly gamedialog.cpp:570:70: note: for a function-style cast, remove the redundant '::QColor' gamedialog.cpp:570:70: error: invalid conversion from 'const char*' to 'QRgb' gamedialog.cpp:570:70: error: initializing argument 1 of 'QColor::QColor(QRgb, uint)' gamedialog.cpp:570:70: error: invalid conversion from 'const char*' to 'uint' gamedialog.cpp:570:70: error: initializing argument 2 of 'QColor::QColor(QRgb, uint)' gamedialog.cpp:571:70: error: cannot call constructor 'QColor::QColor' directly gamedialog.cpp:571:70: note: for a function-style cast, remove the redundant '::QColor' gamedialog.cpp:571:70: error: invalid conversion from 'const char*' to 'QRgb' gamedialog.cpp:571:70: error: initializing argument 1 of 'QColor::QColor(QRgb, uint)' gamedialog.cpp:571:70: error: invalid conversion from 'const char*' to 'uint' gamedialog.cpp:571:70: error: initializing argument 2 of 'QColor::QColor(QRgb, uint)' make[4]: *** [gamedialog.o] Error 1 make[4]: Leaving directory `/build/user-qgo_1.5.4-r3-1-amd64-u0uflc/qgo-1.5.4-r3/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/user-qgo_1.5.4-r3-1-amd64-u0uflc/qgo-1.5.4-r3/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/user-qgo_1.5.4-r3-1-amd64-u0uflc/qgo-1.5.4-r3' make[1]: *** [all] Error 2 make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: qgo Source-Version: 1.5.4-r3-2.1 We believe that the bug you reported is fixed in the latest version of qgo, which is due to be installed in the Debian FTP archive: qgo_1.5.4-r3-2.1.diff.gz to main/q/qgo/qgo_1.5.4-r3-2.1.diff.gz qgo_1.5.4-r3-2.1.dsc to main/q/qgo/qgo_1.5.4-r3-2.1.dsc qgo_1.5.4-r3-2.1_amd64.deb to main/q/qgo/qgo_1.5.4-r3-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 565...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Fousse lfou...@debian.org (supplier of updated qgo 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:
Bug#628353: octave-symbolic: FTBFS: Inconsistency detected by ld.so: dl-close.c: 737: _dl_close: Assertion `map-l_init_called' failed!
On Thu, Sep 08, 2011 at 01:34:14PM +0100, Colin Watson wrote:
Thanks to a note from John W. Eaton that the development version doesn't
suffer from this problem, I tracked down the fix and have prepared a
suitable patch against the Debian package. Please consider this to fix
the octave-symbolic build failure.
Urgh, I missed the existence of debian/in/series. Updated patch
follows.
* New patch: clear_symbol_table: Clean up top-level variables when exiting
Octave (closes: #628353, LP: #831157).
diff -u octave3.2-3.2.4/debian/patches/series
octave3.2-3.2.4/debian/patches/series
--- octave3.2-3.2.4/debian/patches/series
+++ octave3.2-3.2.4/debian/patches/series
@@ -14,2 +14,3 @@
avoid-implicit-conversion
+clear_symbol_table
diff -u octave3.2-3.2.4/debian/in/series octave3.2-3.2.4/debian/in/series
--- octave3.2-3.2.4/debian/in/series
+++ octave3.2-3.2.4/debian/in/series
@@ -24,2 +24,3 @@
avoid-implicit-conversion
+clear_symbol_table
:]
only in patch2:
unchanged:
--- octave3.2-3.2.4.orig/debian/patches/clear_symbol_table
+++ octave3.2-3.2.4/debian/patches/clear_symbol_table
@@ -0,0 +1,90 @@
+Description: Clean up top-level variables when exiting Octave
+ This fixes this assertion failure:
+ .
+ Inconsistency detected by ld.so: dl-close.c: 736: _dl_close: Assertion
+ `map-l_init_called' failed!
+ .
+ This patch is slightly modified from the upstream commits to add
+ __attribute__ ((visibility (hidden))) to the symbol_table::cleanup
+ method, in order that this patch does not change the externally-visible
+ ABI. That modification can and should be dropped when moving to a new
+ upstream version containing this fix.
+Origin: upstream, http://hg.savannah.gnu.org/hgweb/octave/rev/692ab4eaf965
+Origin: upstream, http://hg.savannah.gnu.org/hgweb/octave/rev/a5a05b2ebb9d
+Author: Jaroslav Hajek high...@gmail.com
+Bug: http://savannah.gnu.org/bugs/?34195
+Bug-Debian: http://bugs.debian.org/633719
+Bug-Debian: http://bugs.debian.org/628353
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/831157
+
+Index: b/src/symtab.cc
+===
+--- a/src/symtab.cc
b/src/symtab.cc
+@@ -1193,6 +1193,39 @@
+ }
+ }
+
++void symbol_table::cleanup (void)
++{
++ // Clear variables in top scope.
++ all_instances[xtop_scope]-clear_variables ();
++
++ // Clear function table. This is a hard clear, ignoring mlocked functions.
++ fcn_table.clear ();
++
++ // Clear variables in global scope.
++ // FIXME: are there any?
++ all_instances[xglobal_scope]-clear_variables ();
++
++ // Clear global variables.
++ global_table.clear ();
++
++ // Delete all possibly remaining scopes.
++ for (all_instances_iterator iter = all_instances.begin ();
++ iter != all_instances.end (); iter++)
++{
++ scope_id scope = iter-first;
++ if (scope != xglobal_scope scope != xtop_scope)
++scope_id_cache::free (scope);
++
++ // First zero the table entry to avoid possible duplicate delete.
++ symbol_table *inst = iter-second;
++ iter-second = 0;
++
++ // Now delete the scope. Note that there may be side effects, such as
++ // deleting other scopes.
++ delete inst;
++}
++}
++
+ DEFUN (ignore_function_time_stamp, args, nargout,
+ -*- texinfo -*-\n\
+ @deftypefn {Built-in Function} {@var{val} =} ignore_function_time_stamp ()\n\
+Index: b/src/symtab.h
+===
+--- a/src/symtab.h
b/src/symtab.h
+@@ -1838,6 +1838,8 @@
+ static void stash_dir_name_for_subfunctions (scope_id scope,
+ const std::string dir_name);
+
++ static void cleanup (void) __attribute__ ((visibility (hidden)));
++
+ private:
+
+ typedef std::mapstd::string, symbol_record::const_iterator
table_const_iterator;
+Index: b/src/toplev.cc
+===
+--- a/src/toplev.cc
b/src/toplev.cc
+@@ -673,6 +673,9 @@
+ {
+ do_octave_atexit ();
+
++ // Clean up symbol table.
++ SAFE_CALL (symbol_table::cleanup, ());
++
+ SAFE_CALL (sysdep_cleanup, ())
+
+ if (octave_exit)
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629942: marked as done (python-ecryptfs: missing dependency on python)
Your message dated Fri, 09 Sep 2011 11:52:54 +0200 with message-id 4e69e1f6.9070...@progress-technologies.net and subject line Re: python-ecryptfs: missing dependency on python has caused the Debian Bug report #629942, regarding python-ecryptfs: missing dependency on python 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.) -- 629942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-ecryptfs Version: 87-1 Severity: serious python-ecryptfs contains a python module, but has no dependency on python (except on i386). Cheers, Julien ---End Message--- ---BeginMessage--- Version: 0.92-2 -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ ---End Message---
Bug#640874: leave: debian/rules is not a Makefile
On Thu, Sep 08, 2011 at 04:18:50PM +0200, Josip Rodin wrote: Ahem, so I must quote it: #!/bin/sh -e tmp=`pwd`/debian/leave if echo $DEB_BUILD_OPTIONS | grep -vq noopt; then optflag=-O2 fi if echo $DEB_BUILD_OPTIONS | grep -vq nostrip; then stripflag=-s fi Does not do a word-wise search for the option names, preventing future compatibility with other options having these options as substrings. Whereas the naive implementation using make would DTRT. So that's strike one. ;) The whole idea that we're changing something in the build-arch handling is a nice supporting argument for my idea that we don't have a reason to hardcode make - the fact that we control the API means that we are able to make this decision, rather than having to adjust to whatever some semi-random program does. If you ignore all transitions constraints, sure. At the same time, Debian decided debian/rules must be a Makefile and you're not adjusting to cope. No, Debian did not decide to explicitly ban non-shell rules files at any point in time, it was a leftover from a text conversion that never got fixed. I disagree with this interpretation of the history of the requirement (agreeing instead with Bdale), but if it would put this issue to rest, I would be happy to vote on it explicitly with the TC to require a makefile. The handful of exceptions have definitely caused us far more trouble as a project than any benefit you get as a maintainer from using a shell script in place of a makefile. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#629942: python-ecryptfs: missing dependency on python
On Fri, Sep 9, 2011 at 11:52:54 +0200, Daniel Baumann wrote: Version: 0.92-2 There's no such version, fwiw. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 629416 serious Bug #629416 [plymouth] plymouth: breaks wheeze upgrade with initramfs failure Severity set to 'serious' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 629416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629416 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#556526: hurd - FHS violation: /libexec
On Wed, Sep 7, 2011 at 11:07 AM, Philipp Kern pk...@debian.org wrote: On Mon, Nov 16, 2009 at 03:40:05PM +0100, Bastian Blank wrote: Hurd violates the FHS by using /libexec. This name seems to be only used by init and /etc/ttys. I'm upgrading this to serious on the grounds that this package is only useful on the non-release architecture hurd-i386 and it's clearly a policy violation that makes the package unsuitable for a release. There's a patch here: http://lists.archhurd.org/devel/msg00102.html. The patch moves /libexec/* to /etc. I guess /sbin (or maybe, /lib/hurd) would be more appropriate. What do you think? -- Jérémie Koenig j...@jk.fr.eu.org http://jk.fr.eu.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556526: hurd - FHS violation: /libexec
Jérémie Koenig j...@jk.fr.eu.org writes: On Wed, Sep 7, 2011 at 11:07 AM, Philipp Kern pk...@debian.org wrote: On Mon, Nov 16, 2009 at 03:40:05PM +0100, Bastian Blank wrote: Hurd violates the FHS by using /libexec. This name seems to be only used by init and /etc/ttys. I'm upgrading this to serious on the grounds that this package is only useful on the non-release architecture hurd-i386 and it's clearly a policy violation that makes the package unsuitable for a release. There's a patch here: http://lists.archhurd.org/devel/msg00102.html. The patch moves /libexec/* to /etc. I guess /sbin (or maybe, /lib/hurd) would be more appropriate. What do you think? With my occassional Hurd user hat on, /lib/hurd sounds like the most appropriate place to put these stuff into, or failing that, /sbin. But definitely not /etc. Neither init, nor console-run strike me as things the user would wish to edit. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640969: marked as done (Exits with: ImportError: No module named bpython.cli)
Your message dated Fri, 09 Sep 2011 11:32:21 +
with message-id e1r1zjl-0002bo...@franck.debian.org
and subject line Bug#640969: fixed in bpython 0.10.1-2
has caused the Debian Bug report #640969,
regarding Exits with: ImportError: No module named bpython.cli
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.)
--
640969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: bpython
Version: 0.10.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I just upgraded to bpython, and when running it from the command line
it immediatly exits as follows:
% bpython
Traceback (most recent call last):
File /usr/bin/bpython, line 9, in module
load_entry_point('bpython==0.10.1', 'console_scripts', 'bpython')()
File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 305, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 2245, in
load_entry_point
return ep.load()
File /usr/lib/python2.6/dist-packages/pkg_resources.py, line 1955, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
ImportError: No module named bpython.cli
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
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 bpython depends on:
ii python2.6.7-3
ii python-pkg-resources 0.6.16-1
ii python-pygments 1.4+dfsg-2
ii python2.6 2.6.7-4
ii python2.7 2.7.2-5
bpython recommends no packages.
bpython suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: bpython
Source-Version: 0.10.1-2
We believe that the bug you reported is fixed in the latest version of
bpython, which is due to be installed in the Debian FTP archive:
bpython-gtk_0.10.1-2_all.deb
to main/b/bpython/bpython-gtk_0.10.1-2_all.deb
bpython-urwid_0.10.1-2_all.deb
to main/b/bpython/bpython-urwid_0.10.1-2_all.deb
bpython3_0.10.1-2_all.deb
to main/b/bpython/bpython3_0.10.1-2_all.deb
bpython_0.10.1-2.debian.tar.gz
to main/b/bpython/bpython_0.10.1-2.debian.tar.gz
bpython_0.10.1-2.dsc
to main/b/bpython/bpython_0.10.1-2.dsc
bpython_0.10.1-2_all.deb
to main/b/bpython/bpython_0.10.1-2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 640...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Paleino da...@debian.org (supplier of updated bpython package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 09 Sep 2011 13:13:51 +0200
Source: bpython
Binary: bpython bpython3 bpython-gtk bpython-urwid
Architecture: source all
Version: 0.10.1-2
Distribution: unstable
Urgency: low
Maintainer: David Paleino da...@debian.org
Changed-By: David Paleino da...@debian.org
Description:
bpython- fancy interface to the Python interpreter - Curses frontend
bpython-gtk - fancy interface to the Python interpreter - GTK+ frontend
bpython-urwid - fancy interface to the Python interpreter - urwid frontend
bpython3 - fancy interface to the Python interpreter - Curses frontend
Closes: 640969
Changes:
bpython (0.10.1-2) unstable; urgency=low
.
* Huge BUG in the conversion from dh_pysupport to dh_python2:
in 0.9.7.1-1's (pysupport) postrm, I inconditionally removed
/usr/lib/python*/*-packages/bpython (which was wrong), and
this removed also files shipped by 0.10.1-1, thus causing an
ImportError fixable only by re-installation.
Added preinst nuking old postrms, so that upgrades are clean
(Closes: #640969)
Checksums-Sha1:
14ecd9cf21d12676ada4bdc81bcef34efbf71980 1245 bpython_0.10.1-2.dsc
c3fbbeee3d93e159705289f5c2f7e2d11ea282e5 7239 bpython_0.10.1-2.debian.tar.gz
6f92fa02904d52cc89181d1414272d9b99d98c6d 58612 bpython_0.10.1-2_all.deb
7a9b87d911fa5aeebd7c9fd8710eff0c694cc3ef 71496
Processed: notfound 640638 in 1.8.13-4, notfound 633775 in 1.8.13-4
Processing commands for cont...@bugs.debian.org:
notfound 640638 1.8.13-4
Bug #640638 {Done: OndÅej Surý ond...@debian.org} [libbotan-1.8.2]
libbotan-1.8.2: Outdated binary packages in unstable
Bug #633775 {Done: OndÅej Surý ond...@debian.org} [libbotan-1.8.2]
libbotan-1.8.2 breaks packages that depend on version 1.8.2
There is no source info for the package 'libbotan-1.8.2' at version '1.8.13-4'
with architecture ''
Unable to make a source version for version '1.8.13-4'
Bug No longer marked as found in versions 1.8.13-4.
Bug No longer marked as found in versions 1.8.13-4.
notfound 633775 1.8.13-4
Bug #633775 {Done: OndÅej Surý ond...@debian.org} [libbotan-1.8.2]
libbotan-1.8.2 breaks packages that depend on version 1.8.2
Bug #640638 {Done: OndÅej Surý ond...@debian.org} [libbotan-1.8.2]
libbotan-1.8.2: Outdated binary packages in unstable
There is no source info for the package 'libbotan-1.8.2' at version '1.8.13-4'
with architecture ''
Unable to make a source version for version '1.8.13-4'
Ignoring request to alter found versions of bug #633775 to the same values
previously set
Ignoring request to alter found versions of bug #640638 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
633775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633775
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#629567: Intending to NMU emacs23
Hi Rob, I intend to upload the attached NMU to DELAYED/2-days later today. I hope that's ok with you? It makes emacs23 buildable again in sid and adjusts the build-dependency on libjpeg to use the right dev package. Kind regards Philipp Kern diff -Nru emacs23-23.3+1/debian/changelog emacs23-23.3+1/debian/changelog --- emacs23-23.3+1/debian/changelog 2011-04-10 19:40:31.0 +0200 +++ emacs23-23.3+1/debian/changelog 2011-09-09 12:55:51.0 +0200 @@ -1,3 +1,13 @@ +emacs23 (23.3+1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Build-depend on libjpeg-dev instead of libjpeg62-dev. +(Closes: #633744) + * Add multiarch compatibility by passing the right crt-dir +to configure. (Closes: #629567) + + -- Philipp Kern pk...@debian.org Fri, 09 Sep 2011 12:55:18 +0200 + emacs23 (23.3+1-1) unstable; urgency=low * Incorporate new upstream version 23.3. diff -Nru emacs23-23.3+1/debian/control emacs23-23.3+1/debian/control --- emacs23-23.3+1/debian/control 2011-04-10 19:41:48.0 +0200 +++ emacs23-23.3+1/debian/control 2011-09-09 13:19:49.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Rob Browning r...@defaultvalue.org Build-Depends: bsd-mailx | mailx, libncurses5-dev, texinfo, liblockfile-dev, librsvg2-dev, libgif-dev | libungif4-dev, libtiff4-dev | libtiff-dev, xaw3dg-dev, - libpng12-dev, libjpeg62-dev, libm17n-dev, libotf-dev, + libpng12-dev, libjpeg-dev, libm17n-dev, libotf-dev, libgpm-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], libdbus-1-dev, autoconf, automake, autotools-dev, dpkg-dev ( 1.10.0), quilt (= 0.42), debhelper (= 7.0.50~), libxaw7-dev, sharutils, imagemagick, libgtk2.0-dev, diff -Nru emacs23-23.3+1/debian/control.in emacs23-23.3+1/debian/control.in --- emacs23-23.3+1/debian/control.in2011-04-10 19:33:31.0 +0200 +++ emacs23-23.3+1/debian/control.in2011-09-09 13:18:37.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Rob Browning r...@defaultvalue.org Build-Depends: bsd-mailx | mailx, libncurses5-dev, texinfo, liblockfile-dev, librsvg2-dev, libgif-dev | libungif4-dev, libtiff4-dev | libtiff-dev, xaw3dg-dev, - libpng12-dev, libjpeg62-dev, libm17n-dev, libotf-dev, + libpng12-dev, libjpeg-dev, libm17n-dev, libotf-dev, libgpm-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], libdbus-1-dev, autoconf, automake, autotools-dev, dpkg-dev ( 1.10.0), quilt (= 0.42), debhelper (= 7.0.50~), libxaw7-dev, sharutils, imagemagick, libgtk2.0-dev, diff -Nru emacs23-23.3+1/debian/rules emacs23-23.3+1/debian/rules --- emacs23-23.3+1/debian/rules 2011-04-10 19:33:31.0 +0200 +++ emacs23-23.3+1/debian/rules 2011-09-09 12:55:14.0 +0200 @@ -446,6 +446,9 @@ confflags += --with-pop=yes confflags += --enable-locallisppath=$(local_lpath) +# multiarch compatibility +confflags += --with-crt-dir=/usr/lib/$(shell dpkg-architecture -qDEB_HOST_MULTIARCH) + # x configure flags confflags_x := $(confflags) confflags_x += --with-x=yes signature.asc Description: Digital signature
Bug#554644: marked as done (FTBFS with binutils-gold)
Your message dated Fri, 09 Sep 2011 12:02:33 + with message-id e1r1zmz-0007gz...@franck.debian.org and subject line Bug#554644: fixed in gnet 2.0.8-2.1 has caused the Debian Bug report #554644, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 554644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gnet Version: 2.0.8-1 Severity: minor User: peter.fritzs...@gmx.de Usertags: no-add-needed Tried to build your package and it fails to build with GNU binutils-gold. The important difference is that --no-add-needed is the default behavior of of GNU binutils-gold. Please provide all needed libraries to the linker when building your executables. More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking /bin/bash ../../libtool --tag=CC --mode=link cc -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -g -Wall -O2 -D_REENTRANT -DGNET_EXPERIMENTAL -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wl,-z,defs -Wl,-O1 -Wl,--as-needed -o test-xmlrpc-client test-xmlrpc-client.o libgnetxmlrpc.a ../../src/libgnet-2.0.la -lresolv -lnsl mkdir .libs cc -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -g -Wall -O2 -D_REENTRANT -DGNET_EXPERIMENTAL -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wl,-z -Wl,defs -Wl,-O1 -o .libs/test-xmlrpc-client test-xmlrpc-client.o -Wl,--as-needed libgnetxmlrpc.a ../../src/.libs/libgnet-2.0.so -lresolv -lnsl /usr/bin/ld: test-xmlrpc-client.o: in function main:test-xmlrpc-client.c:53: error: undefined reference to 'g_free' /usr/bin/ld: test-xmlrpc-client.o: in function main:test-xmlrpc-client.c:65: error: undefined reference to 'g_free' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_delete:xmlrpc-client.c:78: error: undefined reference to 'g_string_free' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_new:xmlrpc-client.c:43: error: undefined reference to 'g_malloc0' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_new:xmlrpc-client.c:65: error: undefined reference to 'g_string_new' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_new:xmlrpc-client.c:63: error: undefined reference to 'g_assertion_message_expr' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:219: error: undefined reference to 'g_string_new' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:220: error: undefined reference to 'g_string_new' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:224: error: undefined reference to 'g_string_append_printf' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:240: error: undefined reference to 'g_string_append' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:239: error: undefined reference to 'g_string_append' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:241: error: undefined reference to 'g_string_append' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:247: error: undefined reference to 'g_string_append' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:252: error: undefined reference to 'g_string_append_printf' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:259: error: undefined reference to 'g_string_append_len' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:262: error: undefined reference to 'g_string_free' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:265: error: undefined reference to 'g_string_free' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:93: error: undefined reference to 'g_string_new' /usr/bin/ld: libgnetxmlrpc.a(xmlrpc-client.o): in function gnet_xmlrpc_client_call:xmlrpc-client.c:134: error: undefined reference to
Bug#625756: marked as done (electric-fence: FTBFS due to OOM with gcc-4.5)
Your message dated Fri, 09 Sep 2011 12:47:45 + with message-id e1r20uj-0002yu...@franck.debian.org and subject line Bug#625756: fixed in electric-fence 2.1.17 has caused the Debian Bug report #625756, regarding electric-fence: FTBFS due to OOM with gcc-4.5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 625756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: electric-fence Version: 2.1.16 Severity: serious When I build electric-fence from source on amd64/sid with gcc-4.5 or gcc-4.6, the ./tstheap 3072 call gets to iteration 100 and then starts allocating massive amounts of memory. Within less than a minute it goes through 3.5GB of physical memory and 5GB of swap. It is then killed by the OOM killer. As a consequence, the package fails to build from source. I've looked at the code and haven't been able to track down the problem yet. The code does work correctly without optimization, but still goes out of control at -O1. I suspect this is a consequence of optimizer improvements. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-rc5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages electric-fence depends on: ii libc6 2.13-2 Embedded GNU C Library: Shared lib electric-fence recommends no packages. electric-fence suggests no packages. -- no debconf information -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: electric-fence Source-Version: 2.1.17 We believe that the bug you reported is fixed in the latest version of electric-fence, which is due to be installed in the Debian FTP archive: electric-fence_2.1.17.dsc to main/e/electric-fence/electric-fence_2.1.17.dsc electric-fence_2.1.17.tar.gz to main/e/electric-fence/electric-fence_2.1.17.tar.gz electric-fence_2.1.17_i386.deb to main/e/electric-fence/electric-fence_2.1.17_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 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthew Vernon matt...@debian.org (supplier of updated electric-fence 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: Fri, 09 Sep 2011 13:32:50 +0100 Source: electric-fence Binary: electric-fence Architecture: source i386 Version: 2.1.17 Distribution: unstable Urgency: low Maintainer: Matthew Vernon matt...@debian.org Changed-By: Matthew Vernon matt...@debian.org Description: electric-fence - A malloc(3) debugger Closes: 625756 Changes: electric-fence (2.1.17) unstable; urgency=low . * patch from Colin Watson to build with -fno-tree-dse as otherwise gcc =4.5 mis-optimises AllocateMoreSlots() (Closes: #625756). Checksums-Sha1: 2f51f6025eed2112b28e0601b565ae441825775f 1361 electric-fence_2.1.17.dsc bb109848f276e2216e4a2f6e769b7213cc971f78 30754 electric-fence_2.1.17.tar.gz e627e811082d72df231e3253c1f22a5f75af042d 22086 electric-fence_2.1.17_i386.deb Checksums-Sha256: f0466c7957a958643f93dea75ccce802650b189c6b2917c2aa5b626f0c27e819 1361 electric-fence_2.1.17.dsc 010a9644d8796e7d344ec4b5a39c27eaa1bf9039c427b500d48262f89f959f3f 30754 electric-fence_2.1.17.tar.gz a42006ccd31c8450973e72cf84d6e02eae20c6d367d3ad4e5c1133d9ca418ab2 22086 electric-fence_2.1.17_i386.deb Files: 769d71f8c695414acf39663b343d924c 1361 devel extra electric-fence_2.1.17.dsc 59c9ef2011a56e0e070eb62c5a0fc360 30754 devel extra electric-fence_2.1.17.tar.gz 6b5091d716bc1246a2cec1fa677685bd 22086 devel extra electric-fence_2.1.17_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIVAwUBTmoH3hL00hyPamPIAQhK7Q/+OBPXQIDUpCii2mhH/WoK+9mKRjLS179C L2QZEIDDkLQahcDLvilJKNQUcOc4KGF0EPEj0Qk7McSESjEZxWacGLn+3J5E6dBJ
Bug#641015: upower: depends on libimobiledevice2 from experimental [amd64]
Package: upower Version: 0.9.13-1 Severity: serious Justification: package cannot be installed or upgraded Dear Maintainer, According to the buildd logs, the upower [amd64] package was uploaded by maintainer directly and it seems that was not build on a clean 'unstable' chroot because it depends on libimobiledevice2 which cannot be found on sid but only on experimental. Thanks -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-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 upower depends on: ii dbus 1.4.14-1 ii libc6 2.13-20 ii libdbus-1-31.4.14-1 ii libdbus-glib-1-2 0.94-4 ii libglib2.0-0 2.28.6-1 ii libgudev-1.0-0 172-1 ii libimobiledevice1 1.0.6-3 ii libplist1 1.6-2 ii libpolkit-gobject-1-0 0.102-1 ii libupower-glib10.9.13-1 ii libusb-1.0-0 2:1.0.8-5 ii pm-utils 1.4.1-8 ii udev 172-1 Versions of packages upower recommends: ii policykit-1 0.102-1 upower 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#625379: libpri: ftbfs with gcc-4.6 -Werror
On Tue, May 03, 2011 at 10:33:37AM +, Matthias Klose wrote:
Package: libpri
Version: 1.4.11.3-1
Severity: important
Tags: wheezy sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.6 ftbfs-werror
This package builds with -Werror, and GCC 4.6 triggers new warnings
which will make the package fail to build. Currently a Debian patch
just passes
-Wno-error=unused-but-set-variable and
-Wno-error=unused-but-set-parameter
to avoid build failures, but this patch will be reverted with the
GCC 4.6.1 release, and the severity of the report will be raised.
The full build log can be found at:
http://people.debian.org/~doko/tmp/werror/libpri_1.4.11.3-1_lsid64.buildlog
The last lines of the build log are at the end of this report.
I have just done an NMU to fix this longstanding issue. Please find the
corresponding patch below:
diff -Nru libpri-1.4.11.3/debian/changelog libpri-1.4.11.3/debian/changelog
--- libpri-1.4.11.3/debian/changelog2010-07-06 09:48:50.0 +0200
+++ libpri-1.4.11.3/debian/changelog2011-09-09 14:57:53.0 +0200
@@ -1,3 +1,10 @@
+libpri (1.4.11.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add gcc-4.6-werror to fix FTBFS with gcc-4.6. Closes: #625379.
+
+ -- Aurelien Jarno aure...@debian.org Fri, 09 Sep 2011 14:54:45 +0200
+
libpri (1.4.11.3-1) unstable; urgency=low
* New upstream bugfix release.
diff -Nru libpri-1.4.11.3/debian/patches/gcc-4.6-werror
libpri-1.4.11.3/debian/patches/gcc-4.6-werror
--- libpri-1.4.11.3/debian/patches/gcc-4.6-werror 1970-01-01
01:00:00.0 +0100
+++ libpri-1.4.11.3/debian/patches/gcc-4.6-werror 2011-09-09
14:57:24.0 +0200
@@ -0,0 +1,15 @@
+Remove unused variable
+
+--- libpri-1.4.11.3.orig/q921.c
libpri-1.4.11.3/q921.c
+@@ -808,10 +808,8 @@ void q921_dump(struct pri *pri, q921_h *
+
+ if ((h-u.ft == 3) (h-u.m3 == 0) (h-u.m2 == 0) (h-u.data[0]
== 0x0f)) {
+ int ri;
+- int tei;
+
+ ri = (h-u.data[1] 8) | h-u.data[2];
+- tei = (h-u.data[4] 1);
+ /* TEI assignment related */
+ switch (h-u.data[3]) {
+ case Q921_TEI_IDENTITY_REQUEST:
diff -Nru libpri-1.4.11.3/debian/patches/series
libpri-1.4.11.3/debian/patches/series
--- libpri-1.4.11.3/debian/patches/series 2010-07-06 09:43:55.0
+0200
+++ libpri-1.4.11.3/debian/patches/series 2011-09-09 14:57:04.0
+0200
@@ -1 +1,2 @@
enable-gcc-optimizations
+gcc-4.6-werror
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625379: marked as done (libpri: ftbfs with gcc-4.6 -Werror)
Your message dated Fri, 09 Sep 2011 13:18:23 + with message-id e1r20yn-0006eu...@franck.debian.org and subject line Bug#625379: fixed in libpri 1.4.11.3-1.1 has caused the Debian Bug report #625379, regarding libpri: ftbfs with gcc-4.6 -Werror 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.) -- 625379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libpri Version: 1.4.11.3-1 Severity: important Tags: wheezy sid User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.6 ftbfs-werror This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures, but this patch will be reverted with the GCC 4.6.1 release, and the severity of the report will be raised. The full build log can be found at: http://people.debian.org/~doko/tmp/werror/libpri_1.4.11.3-1_lsid64.buildlog The last lines of the build log are at the end of this report. ---End Message--- ---BeginMessage--- Source: libpri Source-Version: 1.4.11.3-1.1 We believe that the bug you reported is fixed in the latest version of libpri, which is due to be installed in the Debian FTP archive: libpri-dev_1.4.11.3-1.1_amd64.deb to main/libp/libpri/libpri-dev_1.4.11.3-1.1_amd64.deb libpri1.4_1.4.11.3-1.1_amd64.deb to main/libp/libpri/libpri1.4_1.4.11.3-1.1_amd64.deb libpri_1.4.11.3-1.1.debian.tar.gz to main/libp/libpri/libpri_1.4.11.3-1.1.debian.tar.gz libpri_1.4.11.3-1.1.dsc to main/libp/libpri/libpri_1.4.11.3-1.1.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno aure...@debian.org (supplier of updated libpri package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 Sep 2011 14:54:45 +0200 Source: libpri Binary: libpri-dev libpri1.4 Architecture: source amd64 Version: 1.4.11.3-1.1 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: libpri-dev - Primary Rate ISDN specification development files libpri1.4 - Primary Rate ISDN specification library Closes: 625379 Changes: libpri (1.4.11.3-1.1) unstable; urgency=low . * Non-maintainer upload. * Add gcc-4.6-werror to fix FTBFS with gcc-4.6. Closes: #625379. Checksums-Sha1: c955481378b7b08a0109b2bf089c8a8953c9cde9 1295 libpri_1.4.11.3-1.1.dsc d9aa38856449fb9875c5f1645d1467dbb703ac13 9093 libpri_1.4.11.3-1.1.debian.tar.gz 5ec423b612c53e43620c03fe30eb60acd3ba1d37 197926 libpri-dev_1.4.11.3-1.1_amd64.deb 1020364d462c1c20a4221e3dba81c6cee3676b31 156764 libpri1.4_1.4.11.3-1.1_amd64.deb Checksums-Sha256: 1cefe35d3b70d9e1b17a5c6e0896e31ce83c41fd7a5d0f22e927d9a86e0919eb 1295 libpri_1.4.11.3-1.1.dsc 2bb0b770205761c4f2afc73875e46ce229aecc70abfb8f44d98a2b3af8b5500f 9093 libpri_1.4.11.3-1.1.debian.tar.gz 7e493ee64ac6dcb649ace4e1af6d2a014d9bb81bb642ed559c4c5c31f8b5f2d4 197926 libpri-dev_1.4.11.3-1.1_amd64.deb a8a0e71f45368e8bc3be178f3025f4841580be74a2e81741fe13fc50511a 156764 libpri1.4_1.4.11.3-1.1_amd64.deb Files: 5c5183a5e9b98e888fe2aa586bc5b68c 1295 libs optional libpri_1.4.11.3-1.1.dsc 45240d00c69059f46127ed7b37dfebcb 9093 libs optional libpri_1.4.11.3-1.1.debian.tar.gz 0941e88d3d15d531807f34bf5030a019 197926 libdevel optional libpri-dev_1.4.11.3-1.1_amd64.deb a979ca6d00811408512543d0c873e1ce 156764 libs optional libpri1.4_1.4.11.3-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iD4DBQFOag7gw3ao2vG823MRAjBXAKCJgmD7yWLEo3fWuJa2t8NrTXGiPgCVGEs4 HWnncok1UksZrPQsXWC6uQ== =sxjW -END PGP SIGNATURE- ---End Message---
Bug#633744: Intending to NMU emacs23
Philipp Kern pk...@debian.org writes: Hi Rob, I intend to upload the attached NMU to DELAYED/2-days later today. I hope that's ok with you? It makes emacs23 buildable again in sid and adjusts the build-dependency on libjpeg to use the right dev package. That's probably fine. It's going to be at least some time next week before I'm back up to speed. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639064: ygraph: diff for NMU version 0.16~cvs20090218-1.1
tags 639064 + patch tags 639064 + pending thanks Dear maintainer, I've prepared an NMU for ygraph (versioned as 0.16~cvs20090218-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage: http://info.comodo.priv.at/ - PGP/GPG key ID: 0x8649AA06 : :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of Free Software Foundation Europe `-NP: Sonstiges: Should auld aquaintaince be forgot diff -u ygraph-0.16~cvs20090218/debian/changelog ygraph-0.16~cvs20090218/debian/changelog --- ygraph-0.16~cvs20090218/debian/changelog +++ ygraph-0.16~cvs20090218/debian/changelog @@ -1,3 +1,11 @@ +ygraph (0.16~cvs20090218-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix FTBFS: please build-depend on libjpeg-dev, not libjpeg62-dev | +libjpeg-dev: do as the bug title says (closes: #639064). + + -- gregor herrmann gre...@debian.org Fri, 09 Sep 2011 15:42:55 +0200 + ygraph (0.16~cvs20090218-1) unstable; urgency=medium * New upstream version 0.16, currently only available in CVS. diff -u ygraph-0.16~cvs20090218/debian/control ygraph-0.16~cvs20090218/debian/control --- ygraph-0.16~cvs20090218/debian/control +++ ygraph-0.16~cvs20090218/debian/control @@ -2,7 +2,7 @@ Section: science Priority: optional Maintainer: Daniel Kobras kob...@debian.org -Build-Depends: debhelper (= 7.0.0), autotools-dev, libglib2.0-dev, libgtk2.0-dev, libpopt-dev, libjpeg62-dev | libjpeg-dev, libpng12-0-dev | libpng-dev, libtiff4-dev | libtiff-dev, zlib1g-dev | libz-dev, libbz2-dev, docbook-utils +Build-Depends: debhelper (= 7.0.0), autotools-dev, libglib2.0-dev, libgtk2.0-dev, libpopt-dev, libjpeg-dev, libpng12-0-dev | libpng-dev, libtiff4-dev | libtiff-dev, zlib1g-dev | libz-dev, libbz2-dev, docbook-utils Standards-Version: 3.8.0 Package: ygraph signature.asc Description: Digital signature
Processed: ygraph: diff for NMU version 0.16~cvs20090218-1.1
Processing commands for cont...@bugs.debian.org: tags 639064 + patch Bug #639064 [src:ygraph] ygraph: FTBFS: please build-depend on libjpeg-dev, not libjpeg62-dev | libjpeg-dev Added tag(s) patch. tags 639064 + pending Bug #639064 [src:ygraph] ygraph: FTBFS: please build-depend on libjpeg-dev, not libjpeg62-dev | libjpeg-dev Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 639064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639064 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#556318: marked as done (FTBFS with binutils-gold)
Your message dated Fri, 09 Sep 2011 13:48:13 + with message-id e1r21rf-0002ru...@franck.debian.org and subject line Bug#556318: fixed in regina-normal 4.90-1 has caused the Debian Bug report #556318, regarding FTBFS with binutils-gold to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 556318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: regina-normal Version: 4.6-1 Severity: minor User: peter.fritzs...@gmx.de Usertags: no-add-needed Tried to build your package and it fails to build with GNU binutils-gold. The important difference is that --no-add-needed is the default behavior of of GNU binutils-gold. Please provide all needed libraries to the linker when building your executables. More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking /bin/bash ../../../libtool --silent --tag=CXX --mode=link g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -g -O2 -Wformat-security -Wmissing-format-attribute -fno-check-new -fno-common-o regina-kde examplesaction.o main.o reginamain.o reginapref.o reginaiface_skel.o ../common/libregina-kdecommon.la ../../../engine/libregina-engine.la -lkparts -lkabc -lkdeui -lkio -lkdecore -lqt-mt -lz -lpng -lz -lm -lXext -lX11 -lSM -lICE -lpthread -lktexteditor -L/usr/lib -L/usr/share/qt3/lib -lgmp -lm -lz /usr/bin/ld: main.o: in function main:main.cpp:58: error: undefined reference to 'DCOPClient::registerAs(QCString const, bool)' /usr/bin/ld: reginamain.o: in function ReginaMain::ReginaMain():reginamain.cpp:71: error: undefined reference to 'DCOPObject::DCOPObject()' /usr/bin/ld: reginamain.o: in function ReginaMain::ReginaMain():reginamain.cpp:78: error: undefined reference to 'DCOPObject::setObjId(QCString const)' /usr/bin/ld: reginamain.o: in function ReginaMain::ReginaMain():reginamain.cpp:99: error: undefined reference to 'DCOPObject::~DCOPObject()' /usr/bin/ld: reginamain.o: in function ReginaMain::ReginaMain():reginamain.cpp:78: error: undefined reference to 'DCOPObject::setObjId(QCString const)' /usr/bin/ld: reginamain.o: in function ReginaMainInterface::~ReginaMainInterface():reginamain.cpp(.text._ZN19ReginaMainInterfaceD0Ev+0x28): error: undefined reference to 'DCOPObject::~DCOPObject()' /usr/bin/ld: reginamain.o: in function ReginaMainInterface::~ReginaMainInterface():reginamain.cpp(.text._ZN19ReginaMainInterfaceD1Ev+0x24): error: undefined reference to 'DCOPObject::~DCOPObject()' /usr/bin/ld: reginamain.o: in function ReginaMain::~ReginaMain():reginamain.h:266: error: undefined reference to 'DCOPObject::~DCOPObject()' /usr/bin/ld: reginamain.o: in function vtable for ReginaMain:reginamain.cpp(.rodata._ZTV10ReginaMain+0x850): error: undefined reference to 'DCOPObject::processDynamic(QCString const, QMemArraychar const, QCString, QMemArraychar)' /usr/bin/ld: reginamain.o: in function vtable for ReginaMain:reginamain.cpp(.rodata._ZTV10ReginaMain+0x858): error: undefined reference to 'DCOPObject::functionsDynamic()' /usr/bin/ld: reginamain.o: in function vtable for ReginaMain:reginamain.cpp(.rodata._ZTV10ReginaMain+0x860): error: undefined reference to 'DCOPObject::interfacesDynamic()' /usr/bin/ld: reginamain.o: in function vtable for ReginaMain:reginamain.cpp(.rodata._ZTV10ReginaMain+0x878): error: undefined reference to 'DCOPObject::virtual_hook(int, void*)' /usr/bin/ld: reginamain.o: in function construction vtable for ReginaMainInterface-in-ReginaMain:reginamain.cpp(.rodata._ZTC10ReginaMain664_19ReginaMainInterface+0xd8): error: undefined reference to 'DCOPObject::processDynamic(QCString const, QMemArraychar const, QCString, QMemArraychar)' /usr/bin/ld: reginamain.o: in function construction vtable for ReginaMainInterface-in-ReginaMain:reginamain.cpp(.rodata._ZTC10ReginaMain664_19ReginaMainInterface+0xe0): error: undefined reference to 'DCOPObject::functionsDynamic()' /usr/bin/ld: reginamain.o: in function construction vtable for ReginaMainInterface-in-ReginaMain:reginamain.cpp(.rodata._ZTC10ReginaMain664_19ReginaMainInterface+0xe8): error: undefined reference to 'DCOPObject::interfacesDynamic()' /usr/bin/ld: reginamain.o: in function construction vtable for ReginaMainInterface-in-ReginaMain:reginamain.cpp(.rodata._ZTC10ReginaMain664_19ReginaMainInterface+0x100): error: undefined reference to
Bug#624882: marked as done (regina-normal: FTBFS: i18nutils.cpp:115:9: error: 'ptrdiff_t' was not declared in this scope)
Your message dated Fri, 09 Sep 2011 13:48:13 + with message-id e1r21rf-0002rx...@franck.debian.org and subject line Bug#624882: fixed in regina-normal 4.90-1 has caused the Debian Bug report #624882, regarding regina-normal: FTBFS: i18nutils.cpp:115:9: error: 'ptrdiff_t' 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.) -- 624882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: regina-normal Version: 4.6-3 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110502 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../../libtool --silent --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../engine -I../../engine -I/usr/include/libxml2 -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -g -O2 -Wformat-security -Wmissing-format-attribute -fno-check-new -fno-common -MT i18nutils.lo -MD -MP -MF .deps/i18nutils.Tpo -c -o i18nutils.lo i18nutils.cpp i18nutils.cpp: In member function 'virtual std::basic_streambufchar::int_type regina::i18n::IConvStreamBuffer::overflow(std::basic_streambufchar::int_type)': i18nutils.cpp:107:19: warning: conversion to 'std::basic_streambufchar::char_type' from 'std::basic_streambufchar::int_type' may alter its value [-Wconversion] i18nutils.cpp:115:9: error: 'ptrdiff_t' was not declared in this scope i18nutils.cpp:115:9: note: suggested alternatives: /usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note: 'std::ptrdiff_t' /usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note: 'std::ptrdiff_t' i18nutils.cpp:115:19: error: expected ';' before 'n' i18nutils.cpp:116:32: error: 'n' was not declared in this scope i18nutils.cpp:148:40: warning: conversion to 'int' from 'long int' may alter its value [-Wconversion] i18nutils.cpp:158:40: warning: conversion to 'int' from 'long int' may alter its value [-Wconversion] i18nutils.cpp:166:40: warning: conversion to 'int' from 'long int' may alter its value [-Wconversion] i18nutils.cpp:173:44: warning: conversion to 'int' from 'long int' may alter its value [-Wconversion] make[4]: *** [i18nutils.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/05/02/regina-normal_4.6-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: regina-normal Source-Version: 4.90-1 We believe that the bug you reported is fixed in the latest version of regina-normal, which is due to be installed in the Debian FTP archive: regina-normal-dev_4.90-1_amd64.deb to main/r/regina-normal/regina-normal-dev_4.90-1_amd64.deb regina-normal-doc_4.90-1_all.deb to main/r/regina-normal/regina-normal-doc_4.90-1_all.deb regina-normal-mpi_4.90-1_amd64.deb to main/r/regina-normal/regina-normal-mpi_4.90-1_amd64.deb regina-normal_4.90-1.diff.gz to main/r/regina-normal/regina-normal_4.90-1.diff.gz regina-normal_4.90-1.dsc to main/r/regina-normal/regina-normal_4.90-1.dsc regina-normal_4.90-1_amd64.deb to main/r/regina-normal/regina-normal_4.90-1_amd64.deb regina-normal_4.90.orig.tar.gz to main/r/regina-normal/regina-normal_4.90.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 624...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Burton b...@debian.org (supplier of updated regina-normal 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: Sat,
Processed (with 1 errors): merging 640966 641018, severity of 640966 is serious
Processing commands for cont...@bugs.debian.org: merge 640966 641018 Bug#640966: linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug#641018: linux-image-2.6.32-5-686: Kernel-OOPS (sometimes) when using lsof Mismatch - only Bugs in same state can be merged: Values for `severity' don't match: #640966 has `important'; #641018 has `normal' severity 640966 serious Bug #640966 [linux-2.6] linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug #640973 [linux-2.6] Non-privileged fuser oopses kernel Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 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: affects 640966
Processing commands for cont...@bugs.debian.org: affects 640966 release.debian.org Bug #640966 [linux-2.6] linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug #640973 [linux-2.6] Non-privileged fuser oopses kernel Added indication that 640966 affects release.debian.org Added indication that 640973 affects release.debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 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#640859: freeplane: FTBFS due to invalid JAVA_HOME value
Hello Miguel, few questions before I start to look into it: - your pbuilder chroot is on sid pure? - do you have JAVA_HOME and/or JAVACMD defined in your environment/chroot? I'm a bit at loss because it should work without any environment variable defined, and surely /bin/java shouldn't be a valid option, but it's been a rather long time since I last built so perhaps something changed in sid!? Thanks for the report, we'll fix it ;-) Eric On 08/09/11 01:36, Miguel Landaeta wrote: Package: freeplane Version: 0.9.0+dfsg-1 Severity: serious The relevant error message: [ ... ] /bin/sh: 1: /bin/java: not found make: [buildxml-clean] Error 127 (ignored) test -x debian/rules dh_testroot rmdir freemind rmdir: failed to remove `freemind': Directory not empty make: [cleanbuilddir] Error 1 (ignored) You must specify a valid JAVA_HOME or JAVACMD! make: *** [testsanity] Error 1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 640966 641018
Processing commands for cont...@bugs.debian.org: forcemerge 640966 641018 Bug#640966: linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug#641018: linux-image-2.6.32-5-686: Kernel-OOPS (sometimes) when using lsof Bug#640973: Non-privileged fuser oopses kernel Forcibly Merged 640966 640973 641018. thanks Stopping processing here. Please contact me if you need assistance. -- 641018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641018 640973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640973 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 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#641018: Kernel-OOPS (sometimes) when using lsof
Package: linux-2.6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Same issue here, it appears (to me) only when you call 'lsof' with unprivileged user. Obviously this behavior was introduced by the last security upgrade (2.6.32-35squeeze1). Dmesg (with the stack trace) is attached. - -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (800, 'stable-updates'), (800, 'stable'), (96, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk5qQEkACgkQbO4uEp7kOBPK9gCfVeoCh+/rj+Mb4TwBmFtrqjmX NbkAnA1hwxxWsgESfbPSFoOgb7oKopqF =9UhI -END PGP SIGNATURE- [ 4704.125330] BUG: unable to handle kernel paging request at fff3 [ 4704.125335] IP: [8112f98d] m_stop+0x15/0x4c [ 4704.125342] PGD 1003067 PUD 1004067 PMD 0 [ 4704.125346] Oops: [#11] SMP [ 4704.125348] last sysfs file: /sys/devices/virtual/sound/timer/uevent [ 4704.125352] CPU 0 [ 4704.125353] Modules linked in: fuse firewire_sbp2 loop snd_ca0106 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_ac97_codec ac97_bus snd_pcm snd_seq snd_timer snd_seq_device radeon arc4 ttm snd ecb soundcore rt2500pci drm_kms_helper snd_page_alloc rt2x00pci rt2x00lib led_class pcspkr edac_core edac_mce_amd k8temp mac80211 psmouse serio_raw evdev cfg80211 rfkill drm i2c_nforce2 i2c_algo_bit eeprom_93cx6 i2c_core button processor ext4 mbcache jbd2 crc16 sg sr_mod usbhid hid sd_mod crc_t10dif cdrom ohci_hcd ata_generic sata_sil pata_amd sata_nv fan firewire_ohci thermal firewire_core crc_itu_t thermal_sys sky2 libata ehci_hcd forcedeth scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] [ 4704.125398] Pid: 3166, comm: lsof Tainted: G D2.6.32-5-amd64 #1 MS-7125 [ 4704.125400] RIP: 0010:[8112f98d] [8112f98d] m_stop+0x15/0x4c [ 4704.125405] RSP: 0018:880094767e88 EFLAGS: 00010286 [ 4704.125407] RAX: 8131fad0 RBX: 880094767ed8 RCX: 00d07c574067 [ 4704.125410] RDX: ff00 RSI: fff3 RDI: 8800bc205a80 [ 4704.125412] RBP: 88003761b200 R08: 880094767e78 R09: [ 4704.125414] R10: 1000 R11: 811516f3 R12: fff3 [ 4704.125417] R13: fff3 R14: R15: 1000 [ 4704.125420] FS: 7fbcd63a1700() GS:88000180() knlGS: [ 4704.125422] CS: 0010 DS: ES: CR0: 80050033 [ 4704.125424] CR2: fff3 CR3: 947a6000 CR4: 06f0 [ 4704.125427] DR0: DR1: DR2: [ 4704.125429] DR3: DR6: 0ff0 DR7: 0400 [ 4704.125432] Process lsof (pid: 3166, threadinfo 880094766000, task 8800374c46a0) [ 4704.125434] Stack: [ 4704.125435] 1000 880094767ed8 8800bc205a80 81105aa9 [ 4704.125439] 0 01b4fc98 880094767f50 01b4ec90 8800945e1000 [ 4704.125443] 0 8800bc205ab8 8001 1000 [ 4704.125447] Call Trace: [ 4704.125451] [81105aa9] ? seq_read+0x269/0x388 [ 4704.125456] [810ef510] ? vfs_read+0xa6/0xff [ 4704.125459] [810ef625] ? sys_read+0x45/0x6e [ 4704.125463] [81010b42] ? system_call_fastpath+0x16/0x1b [ 4704.125465] Code: 48 89 df e8 e3 c2 f1 ff 31 c0 40 84 ed 49 0f 45 c4 5b 5d 41 5c c3 55 53 48 83 ec 08 48 85 f6 48 8b 6f 60 74 1a 48 3b 75 10 74 14 48 8b 1e 48 8d 7b 60 e8 dd 86 f3 ff 48 89 df e8 ac c2 f1 ff 48 [ 4704.125489] RIP [8112f98d] m_stop+0x15/0x4c [ 4704.125493] RSP 880094767e88 [ 4704.125495] CR2: fff3 [ 4704.125497] ---[ end trace c010ebc4cf0d5b6d ]---
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 641018 important Bug #641018 [linux-2.6] linux-image-2.6.32-5-686: Kernel-OOPS (sometimes) when using lsof Bug #640966 [linux-2.6] linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug #640973 [linux-2.6] Non-privileged fuser oopses kernel Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' End of message, stopping processing here. Please contact me if you need assistance. -- 641018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641018 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#640859: freeplane: FTBFS due to invalid JAVA_HOME value
On Fri, Sep 09, 2011 at 04:12:20PM +0200, Eric Lavarde wrote: few questions before I start to look into it: - your pbuilder chroot is on sid pure? - do you have JAVA_HOME and/or JAVACMD defined in your environment/chroot? I'm a bit at loss because it should work without any environment variable defined, and surely /bin/java shouldn't be a valid option, but it's been a rather long time since I last built so perhaps something changed in sid!? Hello Eric, Sorry if I reacted too quickly on this bug. My pbuilder is clean and up to date. I didn't define JAVA_HOME explicitly anywhere in my pbuilder. openjdk-6 (6b23~pre8-2) introduced changes related to multi-arch, so now /usr/lib/jvm/java-6-openjdk is not a valid JAVA_HOME anymore. In my workstation (amd64) /usr/lib/jvm/java-6-openjdk-amd64 is a valid path. I went ahead and committed a change in freemind (and freeplane since it seems to have the same bug) to switch to default-java that provides a stable JAVA_HOME path and it points to openjdk-6 in almost all architectures anyway. Feel free to revert my changes if you find something wrong. Cheers, -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#628303: marked as done (libjboss-remoting-java: FTBFS: CoyoteInvoker.java:82: org.jboss.remoting.transport.coyote.CoyoteInvoker is not abstract and does not override abstract method log(org.apache
Your message dated Fri, 09 Sep 2011 14:47:45 + with message-id e1r22mr-0006t6...@franck.debian.org and subject line Bug#628303: fixed in libjboss-remoting-java 2.5.3.SP1-1 has caused the Debian Bug report #628303, regarding libjboss-remoting-java: FTBFS: CoyoteInvoker.java:82: org.jboss.remoting.transport.coyote.CoyoteInvoker is not abstract and does not override abstract method log(org.apache.coyote.Request,org.apache.coyote.Response,long) in org.apache.coyote.Adapter 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.) -- 628303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libjboss-remoting-java Version: 2.5.2.SP1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1' make[1]: Nothing to be done for `update-config'. make[1]: Leaving directory `/build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1' cd . /usr/lib/jvm/default-java/bin/java -classpath /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/jboss-common.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/tomcat-coyote.jar:/usr/share/java/commons-httpclient.jar:/usr/share/java/servlet-api-2.5.jar:/usr/share/java/jboss-serialization.jar:/usr/share/java/jboss-jmx.jar:/usr/share/java/jnpserver.jar:/usr/share/java/concurrent.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true -Dcompile.optimize=true -buildfile debian/build.xml -propertyfile /build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1/debian/ant.properties jar Buildfile: /build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1/debian/build.xml compile: [mkdir] Created dir: /build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1/class [javac] /build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1/debian/build.xml:13: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 269 source files to /build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1/class [javac] /build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1/src/org/jboss/remoting/transport/coyote/CoyoteInvoker.java:82: org.jboss.remoting.transport.coyote.CoyoteInvoker is not abstract and does not override abstract method log(org.apache.coyote.Request,org.apache.coyote.Response,long) in org.apache.coyote.Adapter [javac] public class CoyoteInvoker extends WebServerInvoker implements Adapter [javac]^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 1 error BUILD FAILED /build/user-libjboss-remoting-java_2.5.2.SP1-2-amd64-0f2SK8/libjboss-remoting-java-2.5.2.SP1/debian/build.xml:13: Compile failed; see the compiler error output for details. Total time: 3 seconds make: *** [debian/stamp-ant-build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/05/28/libjboss-remoting-java_2.5.2.SP1-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: libjboss-remoting-java Source-Version: 2.5.3.SP1-1 We believe that the bug you reported is fixed in the latest version of libjboss-remoting-java, which is due to be installed in the Debian FTP archive: libjboss-remoting-java_2.5.3.SP1-1.debian.tar.gz to
Processed: your mail
Processing commands for cont...@bugs.debian.org: block 632861 by 640488 Bug #632861 [libvtkedge-dev] libvtkedge-dev: package needs template (*.txx) files Was not blocked by any bugs. Added blocking bug(s) of 632861: 640488 block 634739 by 640488 Bug #634739 [libvtkedge] libvtkedge: Wrong license in description Was not blocked by any bugs. Added blocking bug(s) of 634739: 640488 thanks Stopping processing here. Please contact me if you need assistance. -- 634739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634739 632861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632861 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#629567: Intending to NMU emacs23
On 2011-09-09 13:54 +0200, Philipp Kern wrote: I intend to upload the attached NMU to DELAYED/2-days later today. I hope that's ok with you? It makes emacs23 buildable again in sid and adjusts the build-dependency on libjpeg to use the right dev package. I haven't tested it, but the attached diff is definitely not sufficient. To fix #629567 you need to patch src/s/gnu-linux.h as I mentioned in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629567#10. Also, emacs23 will still FTBFS on any-i386 unless you include the patch from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620795#38. If you fix those problems it would be good to test whether the segfault I experienced in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8623 still occurs. IIRC I could not reproduce it anymore when building emacs23 with later gcc-4.6 versions, but my memory might be faulty. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629567: Intending to NMU emacs23
Hi, On Fri, Sep 09, 2011 at 08:48:59AM -0500, Rob Browning wrote: Philipp Kern pk...@debian.org writes: I intend to upload the attached NMU to DELAYED/2-days later today. I hope that's ok with you? It makes emacs23 buildable again in sid and adjusts the build-dependency on libjpeg to use the right dev package. That's probably fine. It's going to be at least some time next week before I'm back up to speed. pushed to DELAYED/1-day then. Thanks Philipp Kern signature.asc Description: Digital signature
Bug#564968: marked as done (bobot++: ftbfs with gcc-4.5)
Your message dated Fri, 09 Sep 2011 15:32:10 + with message-id e1r233q-0004x8...@franck.debian.org and subject line Bug#564968: fixed in bobot++ 1:1.97-10.4 has caused the Debian Bug report #564968, regarding bobot++: ftbfs with gcc-4.5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 564968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bobot++ Version: 1:1.97-10.3 Severity: normal Tags: sid User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.5 The package fails to build in a test rebuild on at least amd64 with gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4. For the compiler version used, see: http://lists.debian.org/debian-devel/2010/01/msg00230.html The full build log can be found at: http://people.debian.org/~lucas/logs/2010/01/08b/bobot++_1:1.97-10.3_lsid64b.buildlog The last lines of the build log are cwat the end of this report. The reason of the build failure is likely in the package (compiler or linker message found in the build log), if this turns out as a gcc bug, please reassign to the gcc-4.5 package. If the build ends with a message confused by earlier errors, bailing out, please ignore it for now; these compiler errors are filed separately. [...] g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c Server.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c ServerConnection.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c ServerList.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c ServerQueue.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c ServerQueueItem.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c Socket.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c String.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c StringTokenizer.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c ShitEntry.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c ShitList.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c TodoList.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c User.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c UserCommands.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c UserList.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c Utils.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c BotInterp.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c Interp.C g++ -Wall -O2 -DHAVE_STL_CLEAR -DUSESCRIPTS -DMULTITHREAD -c ScriptCommands.C ScriptCommands.C: In static member function 'static scm_unused_struct* ScriptCommands::getServerList()': ScriptCommands.C:386:23: error: 'Server::Server' cannot appear in a constant-expression ScriptCommands.C:386:31: error: template argument 1 is invalid ScriptCommands.C:386:31: error: template argument 2 is invalid ScriptCommands.C:386:43: error: expected initializer before 'it' ScriptCommands.C:388:11: error: 'it' was not declared in this scope make[2]: *** [ScriptCommands.o] Error 1 make[2]: Leaving directory `/build/user-bobot++_1.97-10.3-amd64-rrT7Vh/bobot++-1.97/source' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/user-bobot++_1.97-10.3-amd64-rrT7Vh/bobot++-1.97' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: bobot++ Source-Version: 1:1.97-10.4 We believe that the bug you reported is fixed in the latest version of bobot++, which is due to be installed in the Debian FTP archive: bobot++_1.97-10.4.diff.gz to main/b/bobot++/bobot++_1.97-10.4.diff.gz bobot++_1.97-10.4.dsc to main/b/bobot++/bobot++_1.97-10.4.dsc bobot++_1.97-10.4_i386.deb to main/b/bobot++/bobot++_1.97-10.4_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 564...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated bobot++ package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 Sep 2011 17:09:43 +0200 Source: bobot++ Binary:
Bug#641038: icedtea-plugin: uninstallable on amd64/sid due to openjdk update
Package: icedtea-plugin Version: 1.1-1 Severity: grave Due to the update to openjdk that Breaks icedtea-web, icedtea-plugin is uninstallable on amd64/sid. Because I need a working Java plugin for various purposes, this prevents me from updating openjdk 6 and 7. Please fix this as soon as possible. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-rc4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedtea-plugin depends on: ii icedtea-netx1.1-1 ii libatk1.0-0 2.0.1-2 ii libc6 2.13-20 ii libcairo2 1.10.2-6.1 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.6-2 ii libgcc1 1:4.6.1-9 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.28.6-3 ii libgtk2.0-0 2.24.6-1 ii libnspr4-0d 4.8.9-1 ii libpango1.0-0 1.28.4-3 ii libstdc++6 4.6.1-9 ii openjdk-6-jre 6b23~pre8-1 ii xulrunner-1.9.1 1.9.1.19-3 icedtea-plugin recommends no packages. icedtea-plugin suggests no packages. -- no debconf information -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Processed: Re: Bug#633704: horrible Segmentation fault
Processing commands for cont...@bugs.debian.org: tags 633704 patch Bug #633704 [uni2ascii] horrible Segmentation fault Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 633704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633704 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: linux-image-2.6.32-5-686: kernel oops after upgrade to 2.6.32-35squeeze1
Processing commands for cont...@bugs.debian.org: forcemerge 640966 641040 Bug#640966: linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug#641040: linux-image-2.6.32-5-686: kernel oops after upgrade to 2.6.32-35squeeze1 Bug#640973: Non-privileged fuser oopses kernel Bug#641018: linux-image-2.6.32-5-686: Kernel-OOPS (sometimes) when using lsof Bug#641034: linux-image-2.6.32-5-amd64: Kernel Oops with gnome-system-monitor Forcibly Merged 640966 640973 641018 641034 641040. # make it more visible again severity 640966 serious Bug #640966 [linux-2.6] linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug #640973 [linux-2.6] Non-privileged fuser oopses kernel Bug #641018 [linux-2.6] linux-image-2.6.32-5-686: Kernel-OOPS (sometimes) when using lsof Bug #641034 [linux-2.6] linux-image-2.6.32-5-amd64: Kernel Oops with gnome-system-monitor Bug #641040 [linux-2.6] linux-image-2.6.32-5-686: kernel oops after upgrade to 2.6.32-35squeeze1 Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 641034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641034 641018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641018 641040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641040 640973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org: retitle 640973 linux-image-2.6.32-5-amd64: Non-privileged fuser oopses Bug #640973 [linux-2.6] Non-privileged fuser oopses kernel Bug #640966 [linux-2.6] linux-image-2.6.32-5-686: Kernel Oops with Google Chrome Bug #641018 [linux-2.6] linux-image-2.6.32-5-686: Kernel-OOPS (sometimes) when using lsof Bug #641034 [linux-2.6] linux-image-2.6.32-5-amd64: Kernel Oops with gnome-system-monitor Bug #641040 [linux-2.6] linux-image-2.6.32-5-686: kernel oops after upgrade to 2.6.32-35squeeze1 Changed Bug title to 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' from 'Non-privileged fuser oopses kernel' Changed Bug title to 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' from 'linux-image-2.6.32-5-686: Kernel Oops with Google Chrome' Changed Bug title to 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' from 'linux-image-2.6.32-5-686: Kernel-OOPS (sometimes) when using lsof' Changed Bug title to 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' from 'linux-image-2.6.32-5-amd64: Kernel Oops with gnome-system-monitor' Changed Bug title to 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' from 'linux-image-2.6.32-5-686: kernel oops after upgrade to 2.6.32-35squeeze1' kernel Unknown command or malformed arguments to command. thanks Stopping processing here. Please contact me if you need assistance. -- 640973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640973 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#640195: Processed: your mail
Bug #640195 [paraview] paraview-dev transition Severity set to 'serious' from 'important' I am not agree with that. Why is that bug serious? It does not break anything. I would keep it normal. Anton On Fri, Sep 9, 2011 at 9:28 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Processing commands for cont...@bugs.debian.org: severity 640195 serious Bug #640195 [paraview] paraview-dev transition Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 640195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-maintainers mailing list debian-science-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640973: linux-image-2.6.32-5-amd64: Non-privileged fuser oopses kernel
Oh dear... I hit send on the second rename email hours ago, before the merges, while in a wifi-free area... would not mind if someone undoes this action or picks a more suitable title.
Processed (with 1 errors): Re:
Processing commands for cont...@bugs.debian.org: retitle 640973 linux-image-2.6.32-5-(amd64|686): kernel oops after Bug #640973 [linux-2.6] linux-image-2.6.32-5-amd64: Non-privileged fuser oopses Bug #640966 [linux-2.6] linux-image-2.6.32-5-amd64: Non-privileged fuser oopses Bug #641018 [linux-2.6] linux-image-2.6.32-5-amd64: Non-privileged fuser oopses Bug #641034 [linux-2.6] linux-image-2.6.32-5-amd64: Non-privileged fuser oopses Bug #641040 [linux-2.6] linux-image-2.6.32-5-amd64: Non-privileged fuser oopses Changed Bug title to 'linux-image-2.6.32-5-(amd64|686): kernel oops after' from 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' Changed Bug title to 'linux-image-2.6.32-5-(amd64|686): kernel oops after' from 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' Changed Bug title to 'linux-image-2.6.32-5-(amd64|686): kernel oops after' from 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' Changed Bug title to 'linux-image-2.6.32-5-(amd64|686): kernel oops after' from 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' Changed Bug title to 'linux-image-2.6.32-5-(amd64|686): kernel oops after' from 'linux-image-2.6.32-5-amd64: Non-privileged fuser oopses' upgrade to 2.6.32-35squeeze1 Unknown command or malformed arguments to command. thanks Stopping processing here. Please contact me if you need assistance. -- 640973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640973 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: retitle 640966 to Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020
Processing commands for cont...@bugs.debian.org: retitle 640966 Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug #640966 [linux-2.6] linux-image-2.6.32-5-(amd64|686): kernel oops after Bug #640973 [linux-2.6] linux-image-2.6.32-5-(amd64|686): kernel oops after Bug #641018 [linux-2.6] linux-image-2.6.32-5-(amd64|686): kernel oops after Bug #641034 [linux-2.6] linux-image-2.6.32-5-(amd64|686): kernel oops after Bug #641040 [linux-2.6] linux-image-2.6.32-5-(amd64|686): kernel oops after Changed Bug title to 'Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020' from 'linux-image-2.6.32-5-(amd64|686): kernel oops after' Changed Bug title to 'Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020' from 'linux-image-2.6.32-5-(amd64|686): kernel oops after' Changed Bug title to 'Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020' from 'linux-image-2.6.32-5-(amd64|686): kernel oops after' Changed Bug title to 'Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020' from 'linux-image-2.6.32-5-(amd64|686): kernel oops after' Changed Bug title to 'Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020' from 'linux-image-2.6.32-5-(amd64|686): kernel oops after' thanks Stopping processing here. Please contact me if you need assistance. -- 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 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: notfound 637031 in 0.9.13-1, notfixed 637031 in 0.9.13-1
Processing commands for cont...@bugs.debian.org:
notfound 637031 0.9.13-1
Bug #637031 {Done: Alessio Treglia ales...@debian.org} [libass4] libass4:
Crash with freetype 2.4.6
Bug No longer marked as found in versions libass/0.9.13-1.
notfixed 637031 0.9.13-1
Bug #637031 {Done: Alessio Treglia ales...@debian.org} [libass4] libass4:
Crash with freetype 2.4.6
Bug No longer marked as fixed in versions 0.9.13-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
637031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637031
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#629567: Intending to NMU emacs23
On Fri, Sep 09, 2011 at 05:09:19PM +0200, Sven Joachim wrote: On 2011-09-09 13:54 +0200, Philipp Kern wrote: I intend to upload the attached NMU to DELAYED/2-days later today. I hope that's ok with you? It makes emacs23 buildable again in sid and adjusts the build-dependency on libjpeg to use the right dev package. I haven't tested it, but the attached diff is definitely not sufficient. To fix #629567 you need to patch src/s/gnu-linux.h as I mentioned in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629567#10. Also, emacs23 will still FTBFS on any-i386 unless you include the patch from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620795#38. True. It did build and work just fine on amd64 with the patches I proposed. So the attached debdiff builds on both i386 and amd64. If you fix those problems it would be good to test whether the segfault I experienced in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8623 still occurs. IIRC I could not reproduce it anymore when building emacs23 with later gcc-4.6 versions, but my memory might be faulty. Doesn't crash for me on amd64. I put the result into DELAYED/2-days and cut my original build. Kind regards Philipp Kern diff -Nru emacs23-23.3+1/debian/changelog emacs23-23.3+1/debian/changelog --- emacs23-23.3+1/debian/changelog 2011-04-10 19:40:31.0 +0200 +++ emacs23-23.3+1/debian/changelog 2011-09-09 20:25:37.0 +0200 @@ -1,3 +1,17 @@ +emacs23 (23.3+1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Build-depend on libjpeg-dev instead of libjpeg62-dev. +(Closes: #633744) + * Add multiarch compatibility by passing the right crt-dir +to configure. (Closes: #629567) + * Also use the correct crt1.o location in gnu-linux.h; thanks +to Sven Joachim. (Closes: #629567) + * Fix up manged include paths on i386 due to multiarch. +(Closes: #620795) + + -- Philipp Kern pk...@debian.org Fri, 09 Sep 2011 20:24:47 +0200 + emacs23 (23.3+1-1) unstable; urgency=low * Incorporate new upstream version 23.3. diff -Nru emacs23-23.3+1/debian/control emacs23-23.3+1/debian/control --- emacs23-23.3+1/debian/control 2011-04-10 19:41:48.0 +0200 +++ emacs23-23.3+1/debian/control 2011-09-09 20:40:36.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Rob Browning r...@defaultvalue.org Build-Depends: bsd-mailx | mailx, libncurses5-dev, texinfo, liblockfile-dev, librsvg2-dev, libgif-dev | libungif4-dev, libtiff4-dev | libtiff-dev, xaw3dg-dev, - libpng12-dev, libjpeg62-dev, libm17n-dev, libotf-dev, + libpng12-dev, libjpeg-dev, libm17n-dev, libotf-dev, libgpm-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], libdbus-1-dev, autoconf, automake, autotools-dev, dpkg-dev ( 1.10.0), quilt (= 0.42), debhelper (= 7.0.50~), libxaw7-dev, sharutils, imagemagick, libgtk2.0-dev, diff -Nru emacs23-23.3+1/debian/control.in emacs23-23.3+1/debian/control.in --- emacs23-23.3+1/debian/control.in2011-04-10 19:33:31.0 +0200 +++ emacs23-23.3+1/debian/control.in2011-09-09 13:18:37.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Rob Browning r...@defaultvalue.org Build-Depends: bsd-mailx | mailx, libncurses5-dev, texinfo, liblockfile-dev, librsvg2-dev, libgif-dev | libungif4-dev, libtiff4-dev | libtiff-dev, xaw3dg-dev, - libpng12-dev, libjpeg62-dev, libm17n-dev, libotf-dev, + libpng12-dev, libjpeg-dev, libm17n-dev, libotf-dev, libgpm-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64], libdbus-1-dev, autoconf, automake, autotools-dev, dpkg-dev ( 1.10.0), quilt (= 0.42), debhelper (= 7.0.50~), libxaw7-dev, sharutils, imagemagick, libgtk2.0-dev, diff -Nru emacs23-23.3+1/debian/patches/0014-Cope-with-multiarch-location-of-crt1.o.patch emacs23-23.3+1/debian/patches/0014-Cope-with-multiarch-location-of-crt1.o.patch --- emacs23-23.3+1/debian/patches/0014-Cope-with-multiarch-location-of-crt1.o.patch 1970-01-01 01:00:00.0 +0100 +++ emacs23-23.3+1/debian/patches/0014-Cope-with-multiarch-location-of-crt1.o.patch 2011-09-09 18:59:13.0 +0200 @@ -0,0 +1,27 @@ +Author: Sven Joachim svenj...@gmx.de +Date: Sat, 25 Jun 2011 08:25:48 +0200 +Bug-Debian: http://bugs.debian.org/629567 +Subject: Cope with multiarch location of crt1.o +Applied-Upstream: http://lists.gnu.org/archive/html/emacs-diffs/2010-04/msg00325.html +--- + +--- emacs23-23.3+1.orig/src/s/gnu-linux.h emacs23-23.3+1/src/s/gnu-linux.h +@@ -168,7 +168,7 @@ along with GNU Emacs. If not, see http + /* Ask GCC where to find libgcc.a. */ + #define LIB_GCC `$(CC) $(C_SWITCH_X_SITE) -print-libgcc-file-name` + +-#define START_FILES pre-crt0.o /usr/lib/crt1.o /usr/lib/crti.o ++#define START_FILES pre-crt0.o $(CRT_DIR)/crt1.o $(CRT_DIR)/crti.o + + /* Here is how to find X Windows. LD_SWITCH_X_SITE_AUX gives an -R option +says where to find X windows at run time. */ +@@ -198,7 +198,7 @@ along with GNU Emacs. If not, see http + #define LIBS_DEBUG + #undef LIB_GCC + #define LIB_GCC +-#define LIB_STANDARD -lgcc
Bug#631950: remmina-plugin-nx unable to connect with libssh-4_0.5.0-2
Hi Laurent. It seems this has been fixed in their repo,... can you cherry pick that patch? https://red.libssh.org/issues/60 Chris. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 465598 in 1.2.6-2
Processing commands for cont...@bugs.debian.org:
fixed 465598 1.2.6-2
Bug #465598 {Done: Thijs Kinkhorst th...@debian.org} [libsdl-image1.2]
libsdl-image1.2: Security update 1.2.5-2etch1 is not installed
Bug Marked as fixed in versions sdl-image1.2/1.2.6-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
465598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465598
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#640960: marked as done (CVE-?????: broken CTCP parsing can be used to crash the core)
Your message dated Fri, 09 Sep 2011 20:47:45 + with message-id e1r27zf-0002hb...@franck.debian.org and subject line Bug#640960: fixed in quassel 0.7.3-1 has caused the Debian Bug report #640960, regarding CVE-?: broken CTCP parsing can be used to crash the core 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.) -- 640960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: quassel Version: 0.6.3-2 Severity: important Tags: security When people send me 0010 75 74 61 73 21 7a 7a 40 31 37 38 2d 33 37 2d 31 |utas!zz@178-37-1| 0020 30 34 2d 34 32 2e 61 64 73 6c 2e 69 6e 65 74 69 |04-42.adsl.ineti| 0030 61 2e 70 6c 20 4a 4f 49 4e 20 23 71 75 61 73 73 |a.pl JOIN #quass| 0040 65 6c 0d 0a 37 36 36 37 30 3a 55 c3 8c a6 5b 7e |el..76670:U...[~| 0050 8a 26 3a 6b 75 74 61 73 21 7a 7a 40 31 37 38 2d |.:kutas!zz@178-| 0060 33 37 2d 31 30 34 2d 34 32 2e 61 64 73 6c 2e 69 |37-104-42.adsl.i| 0070 6e 65 74 69 61 2e 70 6c 20 50 52 49 56 4d 53 47 |netia.pl PRIVMSG| 0080 20 23 71 75 61 73 73 65 6c 20 3a 01 41 43 54 49 | #quassel :.ACTI| 0090 4f 4e 20 01 01 56 45 52 53 49 4f 4e 01 01 56 45 |ON ..VERSION..VE| 00a0 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 |RSION..VERSION..| 00b0 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e |VERSION..VERSION| 00c0 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 |..VERSION..VERSI| 00d0 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 |ON..VERSION..VER| 00e0 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 |SION..VERSION..V| 00f0 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 |ERSION..VERSION.| 0100 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f |.VERSION..VERSIO| 0110 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 |N..VERSION..VERS| 0120 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 |ION..VERSION..VE| 0130 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 |RSION..VERSION..| 0140 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e |VERSION..VERSION| 0150 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 |..VERSION..VERSI| 0160 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 |ON..VERSION..VER| 0170 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 |SION..VERSION..V| 0180 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 |ERSION..VERSION.| 0190 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 49 4f |.VERSION..VERSIO| 01a0 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 52 53 |N..VERSION..VERS| 01b0 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 56 45 |ION..VERSION..VE| 01c0 52 53 49 4f 4e 01 01 56 45 52 53 49 4f 4e 01 01 |RSION..VERSION..| 01d0 56 45 52 53 49 4f 4e 01 01 0d 0a |VERSION| quasselcore crashes. The upstream bug report is http://bugs.quassel-irc.org/issues/1095 Gentoo bug report is https://bugs.gentoo.org/382313 (there is some mention about requesting a CVE) Workaround: 1) Settings-Configure Quassel-IRC-Ignore List-New 2) Strictness: Dynamic 3) Rule Type: CTCP 4) Ignore Rule: * VERSION 5) Scope: Global Where is the Vcs for quassel? I could prepare a fix. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages quassel depends on: ii dbus-x111.2.24-4+squeeze1simple interprocess messaging syst ii gawk1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8GCC support library ii libphonon4 4:4.6.0really4.4.2-1 the core library of the Phonon mul ii libqt4-dbus 4:4.6.3-4+squeeze1 Qt 4 D-Bus module ii libqt4-network 4:4.6.3-4+squeeze1 Qt 4 network module ii libqt4-script 4:4.6.3-4+squeeze1 Qt 4 script module ii libqt4-sql 4:4.6.3-4+squeeze1 Qt 4 SQL module ii libqt4-sql-sqlite 4:4.6.3-4+squeeze1 Qt 4 SQLite 3 database driver ii libqt4-webkit 4:4.6.3-4+squeeze1 Qt 4 WebKit module ii libqt4-xmlpatterns 4:4.6.3-4+squeeze1 Qt 4 XML patterns module ii libqtcore4 4:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module ii libstdc++6 4.4.5-8 The GNU Standard
Bug#625222: desktop-base: 625222: spacefun plymouth theme needs plymouth-drm
On ven., 2011-09-09 at 22:24 +0200, Paul Wise wrote: It looks like the spacefun plymouth theme needs plymouth-drm for the script module[1]. I'm not sure how exactly this could be fixed, but two thoughts come to mind. desktop-base could recommend plymouth-drm to pull the module in but allow folks who don't use plymouth to keep it off their systems. That means plymouth is installed by default on Debian install. Do we want that on the base installs? Is it possible for Wheezy? What happens to non-KMS people which have plymouth installed? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Processed: severity of 636559 is serious
Processing commands for cont...@bugs.debian.org: severity 636559 serious Bug #636559 [nepenthes] FTBFS with libcurl4-gnutls-dev 7.21.7-1 on alpha Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 636559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636559 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#640813: marked as done (java-wrappers: find_java_runtime function is broken for openjdk)
Your message dated Fri, 09 Sep 2011 21:17:07 + with message-id e1r28rf-0005b9...@franck.debian.org and subject line Bug#640813: fixed in java-wrappers 0.1.23 has caused the Debian Bug report #640813, regarding java-wrappers: find_java_runtime function is broken for openjdk 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.) -- 640813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: java-wrappers Version: 0.1.22 Severity: important miguel@alice:~$ dpkg-query -l openjdk-6-jdk 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 VersionDescription +++-==-==- ii openjdk-6-jre 6b23~pre9-1OpenJDK Java runtime, using Hotspot JIT miguel@alice:~$ java -version java version 1.6.0_23 OpenJDK Runtime Environment (IcedTea6 1.11pre) (6b23~pre9-1) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) miguel@alice:~$ . /usr/lib/java-wrappers/java-wrappers.sh miguel@alice:~$ find_java_runtime openjdk [warning] -bash: No java runtime was found miguel@alice:~$ -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages java-wrappers depends on: ii unzip 6.0-5 java-wrappers recommends no packages. java-wrappers suggests no packages. -- no debconf information -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche ---End Message--- ---BeginMessage--- Source: java-wrappers Source-Version: 0.1.23 We believe that the bug you reported is fixed in the latest version of java-wrappers, which is due to be installed in the Debian FTP archive: java-wrappers_0.1.23.dsc to main/j/java-wrappers/java-wrappers_0.1.23.dsc java-wrappers_0.1.23.tar.gz to main/j/java-wrappers/java-wrappers_0.1.23.tar.gz java-wrappers_0.1.23_all.deb to main/j/java-wrappers/java-wrappers_0.1.23_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 640...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Fourmond fourm...@debian.org (supplier of updated java-wrappers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 Sep 2011 22:56:25 +0200 Source: java-wrappers Binary: java-wrappers Architecture: source all Version: 0.1.23 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Vincent Fourmond fourm...@debian.org Description: java-wrappers - wrappers for java executables Closes: 640813 Changes: java-wrappers (0.1.23) unstable; urgency=medium . * Correctly find the now architecture-dependent openjdk6 flavor (closes: #640813) * Urgency medium to avoid breaking applications in testing when openjdk6 migrates Checksums-Sha1: 95ccc5bf79aae328b065251f5196806c8bf899a9 955 java-wrappers_0.1.23.dsc 5dd2988aba0f503582f6b3f7d5ce4c7300ae0ed0 8899 java-wrappers_0.1.23.tar.gz 909b0fa738907521b398a5a2d8791ad58f447f58 10608 java-wrappers_0.1.23_all.deb Checksums-Sha256: e79d2333fb197b918399c9a61c9a5be50b54f2c152f96dd65dd45e152ba125ac 955 java-wrappers_0.1.23.dsc 9dfb0657b5fa66301bc1174314dc11957e3e581e31dc3ff35c41aaeeff938bb3 8899 java-wrappers_0.1.23.tar.gz 43442a6c79b7bdb1f96fa7227a727638a2904942116935838f5af282e2196ab5 10608 java-wrappers_0.1.23_all.deb Files: eb2e0c91c71ed297f1fcaaeaa6aa145a 955 java optional java-wrappers_0.1.23.dsc 5f6692b3c5e52da82278fcf00b4938af 8899 java optional java-wrappers_0.1.23.tar.gz 54c879ba8f616c8bdf5c77d94dc607a8 10608 java optional java-wrappers_0.1.23_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk5qflcACgkQx/UhwSKygsrvoACfbpFO49P34VW5M9aDLXRDmaTw
Bug#636397: New deja-dup upload in unstable?
On Thu, Sep 8, 2011 at 10:03 AM, Jérémy Bobbio lu...@debian.org wrote: Hi Jose! deja-dup still has a RC bug in unstable due to the libnotify 0.7 transition. Uploading either the package currently in experimental or a newer upstream release in unstable would fix this issue. Could you make a new deja-dup upload to unstable? Hi, I am expecting to upload 19.91 (yes, I know it is the unstable branch, but should work ok), but I need itstool package first to be uploaded to Debian (#639788). Once it is done, I will upload it. Regards, -- José Carlos García Sogo js...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634140: marked as done (libgeotiff-dfsg: Please Build-Depends on libjpeg-dev, not libjpeg62-dev)
Your message dated Fri, 09 Sep 2011 21:32:44 + with message-id e1r28gm-0008te...@franck.debian.org and subject line Bug#634140: fixed in libgeotiff-dfsg 1.3.0-1 has caused the Debian Bug report #634140, regarding libgeotiff-dfsg: Please Build-Depends on libjpeg-dev, not libjpeg62-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 634140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libgeotiff-dfsg Version: 1.2.5-1 Severity: important Hello Debian GIS Project, We are transitionning from libjpeg62 to libjpeg8. As mentionned on debian-devel-announce[1], please update libgeotiff-dfsg to Build-Depends on libjpeg-dev instead of libjpeg62-dev. The following Build-Depends was found: libgeotiff-dfsg :Build-Depends: libjpeg62-dev [1] http://lists.debian.org/debian-devel-announce/2010/02/msg6.html Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. ---End Message--- ---BeginMessage--- Source: libgeotiff-dfsg Source-Version: 1.3.0-1 We believe that the bug you reported is fixed in the latest version of libgeotiff-dfsg, which is due to be installed in the Debian FTP archive: geotiff-bin_1.3.0-1_i386.deb to main/libg/libgeotiff-dfsg/geotiff-bin_1.3.0-1_i386.deb libgeotiff-dev_1.3.0-1_i386.deb to main/libg/libgeotiff-dfsg/libgeotiff-dev_1.3.0-1_i386.deb libgeotiff-dfsg_1.3.0-1.diff.gz to main/libg/libgeotiff-dfsg/libgeotiff-dfsg_1.3.0-1.diff.gz libgeotiff-dfsg_1.3.0-1.dsc to main/libg/libgeotiff-dfsg/libgeotiff-dfsg_1.3.0-1.dsc libgeotiff-dfsg_1.3.0.orig.tar.gz to main/libg/libgeotiff-dfsg/libgeotiff-dfsg_1.3.0.orig.tar.gz libgeotiff2_1.3.0-1_i386.deb to main/libg/libgeotiff-dfsg/libgeotiff2_1.3.0-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 634...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francesco Paolo Lovergine fran...@debian.org (supplier of updated libgeotiff-dfsg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 Sep 2011 13:59:19 +0200 Source: libgeotiff-dfsg Binary: libgeotiff-dev libgeotiff2 geotiff-bin Architecture: source i386 Version: 1.3.0-1 Distribution: unstable Urgency: low Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Francesco Paolo Lovergine fran...@debian.org Description: geotiff-bin - the GeoTIFF library -- tools libgeotiff-dev - the GeoTIFF library -- development files libgeotiff2 - the GeoTIFF library -- run-time files Closes: 634140 Changes: libgeotiff-dfsg (1.3.0-1) unstable; urgency=low . [ Alan Boudreault ] * New upstream release. * Updated some debian/* file for the new libgeotiff 1.3. * Updated the project homepage in debian/control. * Modified the package names with the proper major version in debian/control. * Added Alan as Uploader in debian/control. . [ Francesco Paolo Lovergine ] * Now following the new SONAME for libgeotiff as adopted upstream: package name changed as consequence * Updated to use libjpeg-dev as build-dep. (closes: #634140) * Now original autoconf helpers file are restored at cleaning time, to be nice against SCMs. * Added Vcs-* fields in debian/control. Checksums-Sha1: 7cdb3ee9d4d70afee2909aec4f3e5c30138c88ae 1449 libgeotiff-dfsg_1.3.0-1.dsc 4086dca88279d8d0f2641ac50b4111e8463a2ee5 448665 libgeotiff-dfsg_1.3.0.orig.tar.gz 1053a09268dc6c6c65e0020ad813e32fdd4ccc9d 31911 libgeotiff-dfsg_1.3.0-1.diff.gz 09f87b3c2c3b7a714447cd634b770896d34c3a7b 112946 libgeotiff-dev_1.3.0-1_i386.deb ba7c5f31095d5ee230b1d57599b4704316c865e5 71560 libgeotiff2_1.3.0-1_i386.deb 5462c3a1727a8d539f89fd2a79ae6cfb50c172d2 44648 geotiff-bin_1.3.0-1_i386.deb Checksums-Sha256: baf44d89f98bd18d9aece2004a593c8eb9ef7cb22d0668e77e58b9d2ec521361 1449 libgeotiff-dfsg_1.3.0-1.dsc 2dab0b1e194df3324e9e8963103c957f45563854c8611b42131f74c5bcb03c8d 448665 libgeotiff-dfsg_1.3.0.orig.tar.gz e7eb1a731989853be878abe54de20e436fb569068ffc16aed36ac5b90a89e21c 31911 libgeotiff-dfsg_1.3.0-1.diff.gz 144e7b79d4df979f733b1947c15a289dce569f1ecf816c7ba6a6df2d57a50275 112946 libgeotiff-dev_1.3.0-1_i386.deb
Processed: reassign 640560 to libvtk5-dev, forcibly merging 506992 640560
Processing commands for cont...@bugs.debian.org: reassign 640560 libvtk5-dev Bug #640560 [src:itksnap] itksnap: FTBFS: make[3]: *** No rule to make target `/usr/lib64/libpq.so', needed by `InsightSNAP'. Stop. Bug reassigned from package 'src:itksnap' to 'libvtk5-dev'. Bug No longer marked as found in versions itksnap/2.2.0-1. forcemerge 506992 640560 Bug#506992: libvtk5-dev: transitive linking and LINK_INTERFACE_LIBRARIES Bug#640560: itksnap: FTBFS: make[3]: *** No rule to make target `/usr/lib64/libpq.so', needed by `InsightSNAP'. Stop. Bug#555185: libvtk5-dev: Invalid dependency in VTKConfig.cmake/VTKLibraryDepends.cmake Bug#629815: gofigure2: FTBFS: make[3]: *** No rule to make target `/usr/lib/libdl.so', needed by `lib/libvtkRenderingAddOn2.so.0.8'. Stop. Bug#630559: libvtk5-dev: linking against VTK using cmake broken because of multiarch Bug#634548: vtkedge: FTBFS: make[3]: *** No rule to make target `/usr/lib/libGLU.so', needed by `bin/libVTKEdge.so'. Stop. Bug#636869: vmtk: FTBFS on all plateforms: No rule to make target `/usr/lib/libpng.so' Bug#638692: gdcm: FTBFS: make[3]: *** No rule to make target `/usr/lib/libpng.so', needed by `bin/libvtkgdcm.so.2.0.17'. Stop. Bug#640383: gofigure2: FTBFS: No rule to make target `/usr/lib/libpng.so', needed by `lib/libitkQt.so.0.8'. Stop. Bug#640555: gdcm: FTBFS: make[3]: *** No rule to make target `/usr/lib64/libpq.so', needed by `bin/libvtkgdcm.so.2.0.17'. Stop. Bug#640556: ginkgocadx: FTBFS: make[3]: *** No rule to make target `/usr/lib64/libpq.so', needed by `src/cadxcore/libCADxCore.so.2.5.0.0'. Stop. Bug#640561: kwwidgets: FTBFS: make[3]: *** No rule to make target `/usr/lib/libpng.so', needed by `bin/libKWWidgets.so.1.0.1009.0'. Stop. Bug#640566: slicer: FTBFS: make[3]: *** No rule to make target `/usr/lib64/libpq.so', needed by `bin/libmimxAdapter.so.3.6.3'. Stop. Forcibly Merged 506992 555185 629815 630559 634548 636869 638692 640383 640555 640556 640560 640561 640566. thanks Stopping processing here. Please contact me if you need assistance. -- 634548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634548 630559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630559 506992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506992 640560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640560 555185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555185 636869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636869 640556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640556 640561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640561 638692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638692 640566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640566 640383: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640383 640555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640555 629815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629815 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#641052: evolution uses insecure connection when storing the sent message to the sent folder
Package: evolution Version: 3.0.3-1 Severity: serious Reporting the security issue myself, see http://article.gmane.org/gmane.comp.security.oss.general/5833 for more info. -- Yves-Alexis -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages evolution depends on: ii dbus 1.4.14-1 ii debconf [debconf-2.0] 1.5.41 ii evolution-common 3.0.3-2 ii evolution-data-server 3.0.3-1 ii gconf22.32.4-1 ii gnome-icon-theme 3.0.0-4 ii libatk1.0-0 2.0.1-2 ii libc6 2.13-20 ii libcairo-gobject2 1.10.2-6.1 ii libcairo2 1.10.2-6.1 ii libcamel-1.2-23 3.0.3-1 ii libcanberra-gtk3-00.28-1 ii libcanberra0 0.28-1 ii libebackend-1.2-1 3.0.3-1 ii libebook1.2-103.0.3-1 ii libecal1.2-8 3.0.3-1 ii libedataserver1.2-14 3.0.3-1 ii libedataserverui-3.0-03.0.3-1 ii libegroupwise1.2-13 3.0.3-1 ii libenchant1c2a1.6.0-3 ii libevolution 3.0.3-2 ii libfontconfig12.8.0-3 ii libfreetype6 2.4.6-2 ii libgail-3-0 3.0.12-2 ii libgconf2-4 2.32.4-1 ii libgdata110.8.1-2 ii libgdk-pixbuf2.0-02.24.0-1 ii libglib2.0-0 2.28.6-1 ii libgnome-desktop-3-0 3.0.2-2 ii libgtk-3-03.0.12-2 ii libgtkhtml-4.0-0 4.0.2-1 ii libgtkhtml-editor-4.0-0 4.0.2-1 ii libgweather-3-0 3.0.2-1 ii libical0 0.44-3 ii libice6 2:1.0.7-2 ii libnotify40.7.4-1 ii libnspr4-0d 4.8.9-1 ii libnss3-1d3.12.11-3 ii libpango1.0-0 1.28.4-3 ii libsm62:1.2.0-2 ii libsoup-gnome2.4-12.34.3-1 ii libsoup2.4-1 2.34.3-1 ii libsqlite3-0 3.7.7-2 ii libstartup-notification0 0.12-1 ii libunique-3.0-0 3.0.0-1 ii libxml2 2.7.8.dfsg-4 ii psmisc22.14-1 Versions of packages evolution recommends: pn bogofilter | spamassassin none pn evolution-plugins 3.0.3-2 pn evolution-webcal none pn yelp none Versions of packages evolution suggests: pn bug-buddy none pn evolution-dbg none pn evolution-exchange none pn evolution-plugins-experimental none pn gnupg 1.4.11-3 pn network-manager none -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636397: New deja-dup upload in unstable?
On Fri, Sep 09, 2011 at 11:30:58PM +0200, Jose Carlos Garcia Sogo wrote: I am expecting to upload 19.91 (yes, I know it is the unstable branch, but should work ok), but I need itstool package first to be uploaded to Debian (#639788). Once it is done, I will upload it. I'd rather not miss the deadline to have a fixed version of 14.2-1 in squeeze (wrt. #624598). Is there a chance that this upload will be made before two weeks? Otherwise, I think it would be better to simple re-upload the version currently in experimental to unstable for now. Cheers, -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#641052: [Evolution] Bug#641052: evolution uses insecure connection when storing the sent message to the sent folder
reassign 641052 src:evolution-data-server3 forwarded 641052 https://bugzilla.gnome.org/show_bug.cgi?id=648277 clone 641052 -1 reassign -1 evolution-data-server thanks On ven., 2011-09-09 at 23:41 +0200, Yves-Alexis Perez wrote: Reporting the security issue myself, see http://article.gmane.org/gmane.comp.security.oss.general/5833 for more info. In fact this is more evolution-data-server than evolution itself, and it seems it's present in eds 2.x too. Note that it won't always happen, it might depend on how exactly the accounts are configured and how folders are selected. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Processed: Re: [Evolution] Bug#641052: evolution uses insecure connection when storing the sent message to the sent folder
Processing commands for cont...@bugs.debian.org: reassign 641052 src:evolution-data-server3 Bug #641052 [evolution] evolution uses insecure connection when storing the sent message to the sent folder Bug reassigned from package 'evolution' to 'src:evolution-data-server3'. Bug No longer marked as found in versions evolution/3.0.3-1. forwarded 641052 https://bugzilla.gnome.org/show_bug.cgi?id=648277 Bug #641052 [src:evolution-data-server3] evolution uses insecure connection when storing the sent message to the sent folder Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=648277'. clone 641052 -1 Bug#641052: evolution uses insecure connection when storing the sent message to the sent folder Bug 641052 cloned as bug 641054. reassign -1 evolution-data-server Bug #641054 [src:evolution-data-server3] evolution uses insecure connection when storing the sent message to the sent folder Bug reassigned from package 'src:evolution-data-server3' to 'evolution-data-server'. thanks Stopping processing here. Please contact me if you need assistance. -- 641054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641054 641052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641052 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 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#616282: marked as done (tulip: replace doxygen and texlive-* build dependencies with doxygen-latex)
Your message dated Fri, 09 Sep 2011 22:19:35 + with message-id e1r29q7-0008k4...@franck.debian.org and subject line Bug#616282: fixed in tulip 3.6.0dfsg-2 has caused the Debian Bug report #616282, regarding tulip: replace doxygen and texlive-* build dependencies with doxygen-latex 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.) -- 616282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:tulip Version: 3.1.2-2.3 Severity: minor User: d...@debian.org Usertag: doxygen-latex The package build-depends on doxygen and one or more of the texlive-* packages, likely it is building some latex/pdf docs using a doxygen.sty generated by doxygen. The doxygen.sty generated by doxygen-1.7.3 now depends on even more macros, so instead of adding more texlive-* dependencies to doxygen, or adding the texlive-* packages to the build dependencies of each source package, a new doxygen-latex package was introduced, depending on all required packages used by doxygen.sty. . If the package builds such documentation, please build-depend on doxygen-latex. If not, please close the report as invalid. ---End Message--- ---BeginMessage--- Source: tulip Source-Version: 3.6.0dfsg-2 We believe that the bug you reported is fixed in the latest version of tulip, which is due to be installed in the Debian FTP archive: libgzstreamtlp-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libgzstreamtlp-3.6_3.6.0dfsg-2_amd64.deb libogdftlp-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libogdftlp-3.6_3.6.0dfsg-2_amd64.deb libtulip-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-3.6_3.6.0dfsg-2_amd64.deb libtulip-dev_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-dev_3.6.0dfsg-2_amd64.deb libtulip-ogdf-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-ogdf-3.6_3.6.0dfsg-2_amd64.deb libtulip-ogl-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-ogl-3.6_3.6.0dfsg-2_amd64.deb libtulip-qt4-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-qt4-3.6_3.6.0dfsg-2_amd64.deb tulip-doc_3.6.0dfsg-2_all.deb to main/t/tulip/tulip-doc_3.6.0dfsg-2_all.deb tulip_3.6.0dfsg-2.debian.tar.gz to main/t/tulip/tulip_3.6.0dfsg-2.debian.tar.gz tulip_3.6.0dfsg-2.dsc to main/t/tulip/tulip_3.6.0dfsg-2.dsc tulip_3.6.0dfsg-2_amd64.deb to main/t/tulip/tulip_3.6.0dfsg-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 616...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yann Dirson dir...@debian.org (supplier of updated tulip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 Sep 2011 22:58:34 +0200 Source: tulip Binary: tulip tulip-doc libtulip-3.6 libtulip-dev libtulip-ogl-3.6 libtulip-qt4-3.6 libtulip-ogdf-3.6 libogdftlp-3.6 libgzstreamtlp-3.6 Architecture: source amd64 all Version: 3.6.0dfsg-2 Distribution: unstable Urgency: low Maintainer: Yann Dirson dir...@debian.org Changed-By: Yann Dirson dir...@debian.org Description: libgzstreamtlp-3.6 - gzstream shared library, built for Tulip libogdftlp-3.6 - Open Graph Drawing Framework shared library, built for Tulip libtulip-3.6 - Tulip graph library - core runtime libtulip-dev - Tulip graph library - core development files libtulip-ogdf-3.6 - Tulip graph library - OGDF runtime libtulip-ogl-3.6 - Tulip graph library - OpenGL runtime libtulip-qt4-3.6 - Tulip graph library - Qt/OpenGL GUI runtime tulip - System dedicated to the visualization of huge graphs tulip-doc - Documentation for the Tulip graph-visualization system Closes: 616282 639313 Changes: tulip (3.6.0dfsg-2) unstable; urgency=low . * Don't build docs for tulip-doc from build-arch, move java packages, docbook-xsl and doxygen to Build-Depend-Indep (where default-jre-headless was, already). Closes: #639313. Uses debhelper compat level 9 for this, but for unknown reason so we do not get multiarch paths. * Drop apparently-useless build-dep on texlive-extra-utils (Closes: #616282). * Cleanup: merge the 2 gzstream-related patches in debian/patches, since the second one was obsoleting the first one. * Drop long-useless build-dep on sharutils. * Remove docs/doxygen/xml on
Bug#639313: marked as done (tulip: FTBFS: /bin/sh: java: not found)
Your message dated Fri, 09 Sep 2011 22:19:36 + with message-id e1r29q8-0008ka...@franck.debian.org and subject line Bug#639313: fixed in tulip 3.6.0dfsg-2 has caused the Debian Bug report #639313, regarding tulip: FTBFS: /bin/sh: java: 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.) -- 639313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:tulip Version: 3.6.0dfsg-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: make[5]: Entering directory `/build/buildd-tulip_3.6.0dfsg-1-s390-eWhi9U/tulip-3.6.0dfsg/obj-s390-linux-gnu' cd /build/buildd-tulip_3.6.0dfsg-1-s390-eWhi9U/tulip-3.6.0dfsg/obj-s390-linux-gnu/docs/developerHandbook java -cp /usr/share/java/saxon.jar:/usr/share/java/saxon.jar:/build/buildd-tulip_3.6.0dfsg-1-s390-eWhi9U/tulip-3.6.0dfsg/docs/common:/usr/share/java/xml-resolver.jar com.icl.saxon.StyleSheet -x org.apache.xml.resolver.tools.ResolvingXMLReader -y org.apache.xml.resolver.tools.ResolvingXMLReader -r org.apache.xml.resolver.tools.CatalogResolver -u /build/buildd-tulip_3.6.0dfsg-1-s390-eWhi9U/tulip-3.6.0dfsg/docs/developerHandbook/index.docbook /build/buildd-tulip_3.6.0dfsg-1-s390-eWhi9U/tulip-3.6.0dfsg/docs/common/tulip-html.xsl /bin/sh: java: not found make[5]: *** [docs/developerHandbook/CMakeFiles/dev_html] Error 127 make[5]: Leaving directory `/build/buildd-tulip_3.6.0dfsg-1-s390-eWhi9U/tulip-3.6.0dfsg/obj-s390-linux-gnu' make[4]: *** [docs/developerHandbook/CMakeFiles/dev_html.dir/all] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=tuliparch=s390ver=3.6.0dfsg-1stamp=1314301362 Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ---End Message--- ---BeginMessage--- Source: tulip Source-Version: 3.6.0dfsg-2 We believe that the bug you reported is fixed in the latest version of tulip, which is due to be installed in the Debian FTP archive: libgzstreamtlp-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libgzstreamtlp-3.6_3.6.0dfsg-2_amd64.deb libogdftlp-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libogdftlp-3.6_3.6.0dfsg-2_amd64.deb libtulip-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-3.6_3.6.0dfsg-2_amd64.deb libtulip-dev_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-dev_3.6.0dfsg-2_amd64.deb libtulip-ogdf-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-ogdf-3.6_3.6.0dfsg-2_amd64.deb libtulip-ogl-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-ogl-3.6_3.6.0dfsg-2_amd64.deb libtulip-qt4-3.6_3.6.0dfsg-2_amd64.deb to main/t/tulip/libtulip-qt4-3.6_3.6.0dfsg-2_amd64.deb tulip-doc_3.6.0dfsg-2_all.deb to main/t/tulip/tulip-doc_3.6.0dfsg-2_all.deb tulip_3.6.0dfsg-2.debian.tar.gz to main/t/tulip/tulip_3.6.0dfsg-2.debian.tar.gz tulip_3.6.0dfsg-2.dsc to main/t/tulip/tulip_3.6.0dfsg-2.dsc tulip_3.6.0dfsg-2_amd64.deb to main/t/tulip/tulip_3.6.0dfsg-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 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yann Dirson dir...@debian.org (supplier of updated tulip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 Sep 2011 22:58:34 +0200 Source: tulip Binary: tulip tulip-doc libtulip-3.6 libtulip-dev libtulip-ogl-3.6 libtulip-qt4-3.6 libtulip-ogdf-3.6 libogdftlp-3.6 libgzstreamtlp-3.6 Architecture: source amd64 all Version: 3.6.0dfsg-2 Distribution: unstable Urgency: low Maintainer: Yann Dirson dir...@debian.org Changed-By: Yann Dirson dir...@debian.org Description: libgzstreamtlp-3.6 - gzstream shared library, built for Tulip libogdftlp-3.6 - Open Graph Drawing Framework shared library, built for Tulip libtulip-3.6 - Tulip graph library - core runtime libtulip-dev - Tulip graph library - core development files libtulip-ogdf-3.6 - Tulip graph library - OGDF runtime libtulip-ogl-3.6 - Tulip graph library - OpenGL runtime libtulip-qt4-3.6 - Tulip graph library - Qt/OpenGL GUI runtime tulip - System dedicated to the visualization of huge graphs
Bug#636397: New deja-dup upload in unstable?
On Fri, Sep 9, 2011 at 11:42 PM, Jérémy Bobbio lu...@debian.org wrote:
On Fri, Sep 09, 2011 at 11:30:58PM +0200, Jose Carlos Garcia Sogo wrote:
I am expecting to upload 19.91 (yes, I know it is the unstable branch,
but should work ok), but I need itstool package first to be uploaded
to Debian (#639788). Once it is done, I will upload it.
I'd rather not miss the deadline to have a fixed version of 14.2-1 in
squeeze (wrt. #624598). Is there a chance that this upload will be made
before two weeks?
I am trying right now, but it seems that generated code from vala has
to be updated in the patch. But running vala -C DuplicityInstance.vala
gives me the following error - I don't know how to solve it:
DuplicityInstance.vala:243.3-243.17: error: The type name
`DataInputStream' could not be found
DataInputStream reader;
^^^
DuplicityInstance.vala:244.3-244.6: error: The type name `File' could
not be found
File logfile;
DuplicityInstance.vala:245.3-245.6: error: The type name `File' could
not be found
File scriptfile;
DuplicityInstance.vala:77.14-77.20: error: The symbol `IOError' could
not be found
catch (IOError.EXISTS e) {
^^^
DuplicityInstance.vala:272.17-272.21: error: The symbol `Posix' could
not be found
Posix.kill((Posix.pid_t)child_pid, Posix.SIGKILL);
^
DuplicityInstance.vala:276.17-276.21: error: The symbol `Posix' could
not be found
Posix.kill((Posix.pid_t)child_pid, Posix.SIGSTOP);
^
DuplicityInstance.vala:280.17-280.21: error: The symbol `Posix' could
not be found
Posix.kill((Posix.pid_t)child_pid, Posix.SIGCONT);
^
DuplicityInstance.vala:334.7-334.17: error: The type name
`InputStream' could not be found
InputStream stream;
^^^
Compilation failed: 8 error(s), 0 warning(s)
Otherwise, I think it would be better to simple re-upload the version
currently in experimental to unstable for now.
I am considering that.
Thanks
--
José Carlos García Sogo
js...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618096: solved in 1.4.7
Hi, Both bugs #618096 and #625397, are solved in the latest upstream release: 1.4.7. Ana -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629671: libpuzzle: FTBFS: vector_ops.c:74: undefined reference to `sqrt'
On Wed, Jun 08, 2011 at 04:13:44PM +0200, Didier Raboud wrote: Source: libpuzzle Version: 0.9-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110607 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/puzzle.o .libs/tunables.o .libs/dvec.o .libs/cvec.o .libs/compress.o .libs/vector_ops.o /usr/lib/libgd.so -L/usr/lib -Wl,-z -Wl,defs -Wl,--as-needed -Wl,-soname -Wl,libpuzzle.so.1 -o .libs/libpuzzle.so.1.0.0 .libs/dvec.o: In function `puzzle_autocrop_axis': /«BUILDDIR»/libpuzzle-0.9/src/dvec.c:167: undefined reference to `round' .libs/dvec.o: In function `puzzle_fill_avglgls': /«BUILDDIR»/libpuzzle-0.9/src/dvec.c:380: undefined reference to `round' /«BUILDDIR»/libpuzzle-0.9/src/dvec.c:513: undefined reference to `round' /«BUILDDIR»/libpuzzle-0.9/src/dvec.c:395: undefined reference to `round' /«BUILDDIR»/libpuzzle-0.9/src/dvec.c:398: undefined reference to `round' .libs/dvec.o:/«BUILDDIR»/libpuzzle-0.9/src/dvec.c:403: more undefined references to `round' follow .libs/vector_ops.o: In function `puzzle_vector_euclidean_length': /«BUILDDIR»/libpuzzle-0.9/src/vector_ops.c:74: undefined reference to `sqrt' collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2011/06/07/libpuzzle_0.9-4_lsid64.buildlog Dear PhotoTools Maintainers, Do you have time for looking at this bug or would like help with a NMU? Ana -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615787: tokyotyrant: ftbfs with gold or ld --no-add-needed
On Mon, Feb 28, 2011 at 12:53:48AM +, Matthias Klose wrote: Package: tokyotyrant Version: 1.1.40-4 Severity: important Tags: sid User: peter.fritzs...@gmx.de Usertags: no-add-needed The package fails to build in a test rebuild on at least amd64 with ld --no-add-needed. For details, please see: http://lists.debian.org/debian-devel-announce/2011/02/msg00011.html http://wiki.debian.org/ToolChain/DSOLinking Dear maintainers, This bug has a patch available in the BTS, do you have time to look at this or do you need help with a NMU? Ana -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629671: libpuzzle: FTBFS: vector_ops.c:74: undefined reference to `sqrt'
Ana Guerrero a...@debian.org (10/09/2011): Dear PhotoTools Maintainers, Do you have time for looking at this bug or would like help with a NMU? KiBi said ENOTIME for pkg-phototools-related stuff, and I'm sure people there would appreciate the love you're proposing for that package, so I'll be bold and suggest you NMU it right away. Thanks! Mraw, KiBi. signature.asc Description: Digital signature
Processed: tagging 622063
Processing commands for cont...@bugs.debian.org: # seems patch does fix it! thanks ;) tags 622063 + pending Bug #622063 [src:mailfilter] mailfilter: FTBFS: socket.cc:123:37: error: invalid conversion from 'const SSL_METHOD*' to 'SSL_METHOD*' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 622063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622063 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#640960: CVE-?????: broken CTCP parsing can be used to crash the core
Hi, it seems ubuntu people backported the fix against 0.6.1: https://launchpadlibrarian.net/79454811/quassel_0.6.1-0ubuntu1_0.6.1-0ubuntu1.2.diff.gz maybe this could help with the squeeze backport? -Timo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 640966
Processing commands for cont...@bugs.debian.org: tags 640966 + pending Bug #640966 [linux-2.6] Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug #640973 [linux-2.6] Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug #641018 [linux-2.6] Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug #641034 [linux-2.6] Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Bug #641040 [linux-2.6] Oops when unprivileged user reads /proc/pid/maps, regression in fix for CVE-2011-1020 Ignoring request to alter tags of bug #640966 to the same tags previously set Ignoring request to alter tags of bug #640973 to the same tags previously set Ignoring request to alter tags of bug #641018 to the same tags previously set Ignoring request to alter tags of bug #641034 to the same tags previously set Ignoring request to alter tags of bug #641040 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 640966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966 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#624588: marked as done (regina-normal: FTBFS on armel i386 mips powerpc s390 sparc (tests fail))
Your message dated Sat, 10 Sep 2011 12:03:48 +1000 with message-id bcb42157-a920-456a-a57a-5d6ad7a87...@debian.org and subject line regina-normal tests passing has caused the Debian Bug report #624588, regarding regina-normal: FTBFS on armel i386 mips powerpc s390 sparc (tests fail) 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.) -- 624588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: regina-normal Version: 4.6-3 Severity: serious Justification: fails to build from source See build logs from https://buildd.debian.org/status/package.php?p=regina-normal Cheers, Julien ---End Message--- ---BeginMessage--- Version: 4.90-2 As hoped, it looks as though regina-normal's test suite is passing on all architectures with the new upstream release and new build infrastructure. Closing this bug accordingly. - Ben. ---End Message---
Bug#641072: gnome control center hangs when clicking on bluetooth icon
Package: gnome-bluetooth Severity: grave Version: 3.0.0-1 I cannot use bluetooth with gnome 3. It is working fine on a squeeze live system. Initial error message is (gnome-control-center:6819): GLib-GObject-WARNING **: specified class size for type `BluetoothChooser' is smaller than the parent type's `GtkVBox' class size (gnome-control-center:6819): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-control-center:6819): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (gnome-control-center:6819): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_WIDGET (child)' failed (gnome-control-center:6819): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed and back trace without debugging symbols installed (not sure how useful it is, hope it will give an initial guide). May be others can see if it can be reproduced. pravi@savannah:~$ gdb --pid=6819 GNU gdb (GDB) 7.2-debian Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Attaching to process 6819 Reading symbols from /usr/bin/gnome-control-center...(no debugging symbols found)...done. Reading symbols from /usr/lib/libgnome-control-center.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgnome-control-center.so.1 Reading symbols from /usr/lib/libgtk-3.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgtk-3.so.0 Reading symbols from /usr/lib/libgdk-3.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgdk-3.so.0 Reading symbols from /usr/lib/libpangocairo-1.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libpangocairo-1.0.so.0 Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0 Reading symbols from /usr/lib/libcairo.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcairo.so.2 Reading symbols from /usr/lib/libpango-1.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libpango-1.0.so.0 Reading symbols from /usr/lib/libgnome-menu.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgnome-menu.so.2 Reading symbols from /usr/lib/libgio-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgio-2.0.so.0 Reading symbols from /usr/lib/libgobject-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgobject-2.0.so.0 Reading symbols from /usr/lib/libgthread-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgthread-2.0.so.0 Reading symbols from /lib/libglib-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libglib-2.0.so.0 Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] [New Thread 0x7ffa42195700 (LWP 6822)] [New Thread 0x7ffa42c43700 (LWP 6821)] Loaded symbols for /lib/x86_64-linux-gnu/libpthread.so.0 Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 Reading symbols from /usr/lib/libatk-1.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libatk-1.0.so.0 Reading symbols from /usr/lib/libcairo-gobject.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcairo-gobject.so.2 Reading symbols from /usr/lib/libpangoft2-1.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libpangoft2-1.0.so.0 Reading symbols from /usr/lib/libfreetype.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libfontconfig.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfontconfig.so.1 Reading symbols from /usr/lib/libgmodule-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgmodule-2.0.so.0 Reading symbols from /lib/x86_64-linux-gnu/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/librt.so.1 Reading symbols from /usr/lib/libgconf-2.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgconf-2.so.4 Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libm.so.6 Reading symbols from /usr/lib/libX11.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libX11.so.6 Reading symbols from /usr/lib/libXcomposite.so.1...(no debugging symbols
