Processed (with 1 errors): reopening 556468, submitter 556468, severity of 556468 is grave
Processing commands for cont...@bugs.debian.org:
reopen 556468 4:4.3.4-3
Failed to reopen 556468: New submitter address 4:4.3.4-3 is not a valid e-mail
address.
submitter 556468 bugs+deb...@kcore.org
Bug #556468 {Done: Xavier Vello xavier.ve...@gmail.com}
[kdebase-workspace-bin] /usr/bin/plasma-desktop: plasma-desktop crashes
(segfault) after login, or also manual start
Changed Bug submitter to 'bugs+deb...@kcore.org' from 'BeLioN
bel...@gmail.com'
# The bug was hijacked. Original bug is fixed though.
severity 556468 grave
Bug #556468 {Done: Xavier Vello xavier.ve...@gmail.com}
[kdebase-workspace-bin] /usr/bin/plasma-desktop: plasma-desktop crashes
(segfault) after login, or also manual start
Severity set to 'grave' from 'critical'
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 556468 is forwarded to https://bugs.kde.org/show_bug.cgi?id=219333
Processing commands for cont...@bugs.debian.org:
forwarded 556468 https://bugs.kde.org/show_bug.cgi?id=219333
Bug #556468 {Done: Xavier Vello xavier.ve...@gmail.com}
[kdebase-workspace-bin] /usr/bin/plasma-desktop: plasma-desktop crashes
(segfault) after login, or also manual start
Changed Bug forwarded-to-address to
'https://bugs.kde.org/show_bug.cgi?id=219333' from
'https://bugs.kde.org/show_bug.cgi?id=220190'
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539542: marked as done (FTBFS with GCC 4.4: dereferencing type-punned pointer will break strict-aliasing rules)
Your message dated Mon, 28 Dec 2009 09:48:06 + with message-id e1npccs-0004gj...@ries.debian.org and subject line Bug#539542: fixed in libnsgif 0.0.1-1.1 has caused the Debian Bug report #539542, regarding FTBFS with GCC 4.4: dereferencing type-punned pointer will break strict-aliasing rules 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.) -- 539542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libnsgif Version: 0.0.1-1 User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.4 Your package fails to build with GCC 4.4. You can reproduce this problem with gcc-4.4/g++-4.4 from unstable. Automatic build of libnsgif_0.0.1-1 on em64t by sbuild/amd64 0.53 ... /usr/bin/make COMPONENT_TYPE=lib-shared PREFIX=/usr make[1]: Entering directory `/build/tbm/libnsgif-0.0.1' COMPILE: src/libnsgif.c cc1: warnings being treated as errors src/libnsgif.c: In function 'gif_initialise': src/libnsgif.c:326: error: dereferencing type-punned pointer will break strict-aliasing rules src/libnsgif.c: In function 'gif_decode_frame': src/libnsgif.c:851: error: dereferencing type-punned pointer will break strict-aliasing rules make[1]: *** [build-Linux-Linux-release-lib-shared/src_libnsgif.o] Error 1 make[1]: Leaving directory `/build/tbm/libnsgif-0.0.1' make: *** [build-stamp] Error 2 -- Martin Michlmayr http://www.cyrius.com/ ---End Message--- ---BeginMessage--- Source: libnsgif Source-Version: 0.0.1-1.1 We believe that the bug you reported is fixed in the latest version of libnsgif, which is due to be installed in the Debian FTP archive: libnsgif0-dbg_0.0.1-1.1_amd64.deb to main/libn/libnsgif/libnsgif0-dbg_0.0.1-1.1_amd64.deb libnsgif0-dev_0.0.1-1.1_amd64.deb to main/libn/libnsgif/libnsgif0-dev_0.0.1-1.1_amd64.deb libnsgif0_0.0.1-1.1_amd64.deb to main/libn/libnsgif/libnsgif0_0.0.1-1.1_amd64.deb libnsgif_0.0.1-1.1.diff.gz to main/libn/libnsgif/libnsgif_0.0.1-1.1.diff.gz libnsgif_0.0.1-1.1.dsc to main/libn/libnsgif/libnsgif_0.0.1-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 539...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Zacchiroli z...@debian.org (supplier of updated libnsgif 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, 26 Dec 2009 10:01:35 +0100 Source: libnsgif Binary: libnsgif0 libnsgif0-dev libnsgif0-dbg Architecture: source amd64 Version: 0.0.1-1.1 Distribution: unstable Urgency: low Maintainer: Debian/Ubuntu NetSurf Package Team d...@netsurf-browser.org Changed-By: Stefano Zacchiroli z...@debian.org Description: libnsgif0 - NetSurf GIF decoder libnsgif0-dbg - NetSurf GIF decoder - Debugging symbols libnsgif0-dev - NetSurf GIF decoder - Development files Closes: 539542 Changes: libnsgif (0.0.1-1.1) unstable; urgency=low . * Non-maintainer upload. * Disable strict aliasing check to fix FTBFS with gcc 4.4, patch by peter green. (Closes: #539542) Checksums-Sha1: faa18017b299b5ee906bba435355f256c1e93736 1098 libnsgif_0.0.1-1.1.dsc 85fe2730addca3c22a12850235172102c86b49b9 2121 libnsgif_0.0.1-1.1.diff.gz f39fac39c6364fe705f034978af2e0ed65060e54 7954 libnsgif0_0.0.1-1.1_amd64.deb 4beba9d2636ac220c181e0e5f48da2b0609881d6 4102 libnsgif0-dev_0.0.1-1.1_amd64.deb bc27f53019c1c421230668645613a1920e7c161d 10692 libnsgif0-dbg_0.0.1-1.1_amd64.deb Checksums-Sha256: 62dd70d108f2a56ced6073562e027f0642ebe493547cccf75951ec2eb570bc7f 1098 libnsgif_0.0.1-1.1.dsc 4fda6cba8657a2d13372c32c1383d1e10837f6feb31ef33da21e80339b7a87d1 2121 libnsgif_0.0.1-1.1.diff.gz e014141b2a8b676e4b8dc917dfe2347579cd2895d4a7e2807fe32c7f5bde2134 7954 libnsgif0_0.0.1-1.1_amd64.deb 94565c7bf10a760c11895f69461eea2e2e217c6b1f0bf7759f477dbab35499f3 4102 libnsgif0-dev_0.0.1-1.1_amd64.deb 4c4637d03e89f7e60ed069ad3584a322e953d3cbb5921a30d0462aaaeb3a06a2 10692 libnsgif0-dbg_0.0.1-1.1_amd64.deb Files: e905ffdfb36d46c38639d91e5ea0b8b9 1098 libs optional libnsgif_0.0.1-1.1.dsc 47c8004a65614e7cc7c0b368ebe1dc2b 2121 libs optional libnsgif_0.0.1-1.1.diff.gz 349c37a84db72cae041a3350e6ef659f 7954 libs optional libnsgif0_0.0.1-1.1_amd64.deb
Processed: severity of 562228 is serious
Processing commands for cont...@bugs.debian.org: severity 562228 serious Bug #562228 [smem] Not installable. Program name ( /usr/bin/smem) already exists in the secure-delete package Severity set to 'serious' from 'critical' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562228: Not installable. Program name ( /usr/bin/smem) already exists in the secure-delete package
thanks for reporting that bug. Setting severity to serious which is usual for cases like this. -Ralf (I am not the package maintainer) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562820: turba2 and horde3: error when trying to install together
Package: horde3,turba2 Version: horde3/3.3.6+debian0-2 Version: turba2/2.3.3+debian0-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2009-12-27 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libcap2 libdb4.8 libmagic1 libpcre3 libsqlite3-0 libxml2 mime-support ucf libapr1 libexpat1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap apache2.2-bin apache2-utils apache2.2-common apache2-mpm-prefork ttf-dejavu-core ttf-dejavu-extra ttf-dejavu fontconfig-config php5-common libapache2-mod-php5 libfreetype6 libfontconfig1 libjpeg62 libpng12-0 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxpm4 libgd2-xpm libt1-5 php5-cli php5-gd libltdl7 libmcrypt4 php5-mcrypt php-pear php-log php-mail php-mail-mimedecode php-mail-mime libjs-prototype libjs-scriptaculous horde3 turba2 W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406859 W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407760 W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406861 Extracting templates from packages: 61% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libcap2. (Reading database ... 10443 files and directories currently installed.) Unpacking libcap2 (from .../libcap2_1%3a2.17-2_amd64.deb) ... Selecting previously deselected package libdb4.8. Unpacking libdb4.8 (from .../libdb4.8_4.8.24-2_amd64.deb) ... Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_5.03-5_amd64.deb) ... Selecting previously deselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_7.8-3_amd64.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.21-2_amd64.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.6.dfsg-1_amd64.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.48-1_all.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0025_all.deb) ... Moving old data out of the way Selecting previously deselected package libapr1. Unpacking libapr1 (from .../libapr1_1.3.8-1_amd64.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-6_amd64.deb) ... Selecting previously deselected package libaprutil1. Unpacking libaprutil1 (from .../libaprutil1_1.3.9+dfsg-3_amd64.deb) ... Selecting previously deselected package libaprutil1-dbd-sqlite3. Unpacking libaprutil1-dbd-sqlite3 (from .../libaprutil1-dbd-sqlite3_1.3.9+dfsg-3_amd64.deb) ... Selecting previously deselected package libaprutil1-ldap. Unpacking libaprutil1-ldap (from .../libaprutil1-ldap_1.3.9+dfsg-3_amd64.deb) ... Selecting previously deselected package apache2.2-bin. Unpacking apache2.2-bin (from .../apache2.2-bin_2.2.14-4_amd64.deb) ... Selecting previously deselected package apache2-utils. Unpacking apache2-utils (from .../apache2-utils_2.2.14-4_amd64.deb) ... Selecting previously deselected package apache2.2-common. Unpacking apache2.2-common (from .../apache2.2-common_2.2.14-4_amd64.deb) ... Selecting previously deselected package apache2-mpm-prefork. Unpacking apache2-mpm-prefork (from .../apache2-mpm-prefork_2.2.14-4_amd64.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.30-2_all.deb) ... Selecting previously deselected package ttf-dejavu-extra. Unpacking ttf-dejavu-extra (from .../ttf-dejavu-extra_2.30-2_all.deb) ... Selecting previously deselected package ttf-dejavu. Unpacking ttf-dejavu (from .../ttf-dejavu_2.30-2_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.6.0-4.2_all.deb) ... Selecting previously deselected package php5-common. Unpacking php5-common (from .../php5-common_5.2.11.dfsg.1-2_amd64.deb) ... Selecting previously deselected package libapache2-mod-php5. Unpacking libapache2-mod-php5 (from .../libapache2-mod-php5_5.2.11.dfsg.1-2_amd64.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.3.11-1_amd64.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.6.0-4.2_amd64.deb) ... Selecting previously deselected package libjpeg62. Unpacking
Bug#562778: marked as done (fglrx-driver: 2.6.32 Debian and fglrx 1:9-12 does not work)
Your message dated Mon, 28 Dec 2009 10:16:15 +0100 with message-id 4b38775f.8010...@debian.org and subject line Re: [Pkg-fglrx-devel] Bug#562778: fglrx-driver: 2.6.32 Debian and fglrx1:9-12 does not work has caused the Debian Bug report #562778, regarding fglrx-driver: 2.6.32 Debian and fglrx 1:9-12 does not work 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.) -- 562778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fglrx-driver Version: 1:9-12-1 Severity: grave Justification: renders package unusable -- Package-specific info: VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Device 95c2 DRM and fglrx Informations from dmesg: [0.00] No AGP bridge found [5.467021] Linux agpgart interface v0.103 [ 35.564134] fglrx: disagrees about version of symbol module_layout Xorg X server configuration file status: -rw-r--r-- 1 root root 1849 May 21 2009 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section ServerLayout Identifier aticonfig Layout Screen 0 aticonfig-Screen[0]-0 0 0 EndSection Section Files EndSection Section Module EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout fr Option XkbVariant latin9 EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Monitor Identifier Configured Monitor EndSection Section Monitor Identifier aticonfig-Monitor[0]-0 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Device Identifier Configured Video Device EndSection Section Device Identifier aticonfig-Device[0]-0 Driver fglrx BusID PCI:1:0:0 EndSection Section Screen Identifier Default Screen MonitorConfigured Monitor EndSection Section Screen Identifier aticonfig-Screen[0]-0 Device aticonfig-Device[0]-0 Monitoraticonfig-Monitor[0]-0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 5538 Aug 29 09:13 /var/log/Xorg.1.log -rw-r--r-- 1 root root 30558 Dec 27 18:13 /var/log/Xorg.2-6-32.log -rw-r--r-- 1 root root 22676 Dec 27 19:52 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30-2-amd64 x86_64 Debian Current Operating System: Linux portable 2.6.32-trunk-amd64 #1 SMP Thu Dec 17 06:29:18 UTC 2009 x86_64 Build Date: 13 October 2009 09:39:10AM xorg-server 2:1.6.5-1 (jcris...@debian.org) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Dec 27 19:52:00 2009 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout aticonfig Layout (**) |--Screen aticonfig-Screen[0]-0 (0) (**) | |--Monitor aticonfig-Monitor[0]-0 (**) | |--Device aticonfig-Device[0]-0 (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled,
Processed: reopening 556468, notfixed 556468 in 4:4.3.4-3
Processing commands for cont...@bugs.debian.org:
reopen 556468
Bug #556468 {Done: Xavier Vello xavier.ve...@gmail.com}
[kdebase-workspace-bin] /usr/bin/plasma-desktop: plasma-desktop crashes
(segfault) after login, or also manual start
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
notfixed 556468 4:4.3.4-3
Bug #556468 [kdebase-workspace-bin] /usr/bin/plasma-desktop: plasma-desktop
crashes (segfault) after login, or also manual start
Ignoring request to alter fixed versions of bug #556468 to the same values
previously set
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531715: marked as done (FTBFS with GCC 4.4: missing #include)
Your message dated Mon, 28 Dec 2009 10:02:15 +
with message-id e1npcqz-0006e8...@ries.debian.org
and subject line Bug#531715: fixed in gcin 1.4.5-1.1
has caused the Debian Bug report #531715,
regarding FTBFS with GCC 4.4: missing #include
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.)
--
531715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gcin
Version: 1.4.5-1
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.4
Tags: patch
Your package fails to build with GCC 4.4, which has cleaned up some more
C++ headers. You always have to #include headers directly and cannot
rely for things to be included indirectly.
You can reproduce this problem with gcc-4.4/g++-4.4 from unstable.
Automatic build of gcin_1.4.5-1 on em64t by sbuild/amd64 0.53
...
g++ -g -O2 -I../im-client -I/usr/include/qt4 -I/usr/include/X11
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -Wall -D_REENTRANT -fPIC
-DQT4 -DQT_SHARED -DQT_IMMODULE -DPIC -c -o gcin-imcontext-qt.o
gcin-imcontext-qt.cpp
gcin-imcontext-qt.cpp: In constructor 'GCINIMContext::GCINIMContext()':
gcin-imcontext-qt.cpp:21: error: 'perror' was not declared in this scope
make[6]: *** [gcin-imcontext-qt.o] Error 1
make[6]: Leaving directory `/build/tbm/gcin-1.4.5/qt4-im'
make[5]: *** [all] Error 2
--- qt4-im/gcin-imcontext-qt.cpp~ 2009-06-03 13:15:29.0 +
+++ qt4-im/gcin-imcontext-qt.cpp2009-06-03 13:16:09.0 +
@@ -3,6 +3,7 @@
#include X11/Xlib.h
#include X11/keysym.h
#include X11/Xutil.h
+#include cstdio
#include gcin-im-client.h
#include QColor
#include QPalette
--
Martin Michlmayr
http://www.cyrius.com/
---End Message---
---BeginMessage---
Source: gcin
Source-Version: 1.4.5-1.1
We believe that the bug you reported is fixed in the latest version of
gcin, which is due to be installed in the Debian FTP archive:
gcin-dev_1.4.5-1.1_all.deb
to main/g/gcin/gcin-dev_1.4.5-1.1_all.deb
gcin-qt3-immodule_1.4.5-1.1_amd64.deb
to main/g/gcin/gcin-qt3-immodule_1.4.5-1.1_amd64.deb
gcin-qt4-immodule_1.4.5-1.1_amd64.deb
to main/g/gcin/gcin-qt4-immodule_1.4.5-1.1_amd64.deb
gcin_1.4.5-1.1.diff.gz
to main/g/gcin/gcin_1.4.5-1.1.diff.gz
gcin_1.4.5-1.1.dsc
to main/g/gcin/gcin_1.4.5-1.1.dsc
gcin_1.4.5-1.1_amd64.deb
to main/g/gcin/gcin_1.4.5-1.1_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 531...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Zacchiroli z...@debian.org (supplier of updated gcin 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, 26 Dec 2009 10:13:19 +0100
Source: gcin
Binary: gcin gcin-dev gcin-qt3-immodule gcin-qt4-immodule
Architecture: source amd64 all
Version: 1.4.5-1.1
Distribution: unstable
Urgency: low
Maintainer: Kanru Chen kos...@debian.org.tw
Changed-By: Stefano Zacchiroli z...@debian.org
Description:
gcin - an GTK+ based input method platform for Chinese users
gcin-dev - an GTK+ based input method platform - development files
gcin-qt3-immodule - an QT3 input method module with gcin as backend
gcin-qt4-immodule - an QT4 input method module with gcin as backend
Closes: 531715
Changes:
gcin (1.4.5-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Add missing #include to fix FTBFS with gcc 4.4, patch by Martin
Michlmayr. (Closes: #531715)
* gcin-qt{3,4}-immodule: add lintian overrides for shlib-defines-rpath,
this is needed to get the package pass through auto-REJECT. Rationale:
rpath is appropriate here, the packages use private shlibs.
Checksums-Sha1:
aa657235e2d381b24a4437eabf1d61c8d46a43aa 1246 gcin_1.4.5-1.1.dsc
a45c0a4f33be0d4fa84985424d2be3aab7a2f2bf 14606 gcin_1.4.5-1.1.diff.gz
9504d2c616623d137450dba661be2449d7bc9dc9 2177710 gcin_1.4.5-1.1_amd64.deb
41e60309d5e3ea1d86f4870de8a93ec8861bfb73 63620 gcin-dev_1.4.5-1.1_all.deb
42b904df75f8acd39e5b5601d3aa726b80bb4488 74586
gcin-qt3-immodule_1.4.5-1.1_amd64.deb
fda4514ab117466a053ed08b66cd61cdc26f1cea 75158
gcin-qt4-immodule_1.4.5-1.1_amd64.deb
Checksums-Sha256:
d3a812e6ce00dc8d2941b3ecbba482cb624393f5c33f1c17e331e80f59beb4a9 1246
Bug#562553: closed by Andreas Tille ti...@debian.org (Bug#562553: fixed in debian-med 1.4)
Hi Andreas, the debian-med 1.4 changelog reads: * Depend from blends-common = 0.6.8 Closes: #562553 I'm not sure fixed the bug, if you look at the attached log (from this bug), you will see that blends-common 0.6.8 was already used cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#562791: libopts25: didn't bump shlibs or soname.
On Sun, Dec 27, 2009 at 07:49:14PM -0800, Bruce Korb wrote: If you generate the option code with new templates and run against old library, you will have a conflict. The library will reject the new code. The new library will accept a program generated against old templates and linked against the old library. Or, I should say it is supposed to. I do not validate this every time. It has worked previously and I've not invalidated any data structures in a long time. In that case the Debian maintainer should have indicated that with the shlibs system. The problem is that I now get a Depends that says libopts25, while I should have gotton libopts25 (= 1:5.10). Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#317358: portmap bind to loopback install option doesn't work
Processing commands for cont...@bugs.debian.org: severity 317358 serious Bug #317358 [portmap] portmap bind to loopback install option doesn't work Severity set to 'serious' from 'normal' tags 317358 - unreproducible - moreinfo Bug #317358 [portmap] portmap bind to loopback install option doesn't work Removed tag(s) unreproducible. Bug #317358 [portmap] portmap bind to loopback install option doesn't work Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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): reassign 547351 to l7-filter-userspace, forcibly merging 562441 547351
Processing commands for cont...@bugs.debian.org:
reassign 547351 l7-filter-userspace
Bug #547351 {Done: Jakub Wilk uba...@users.sf.net} [l7-filter-userspace]
l7-filter-userspace: [FTBFS] 'nfct_sprintf_protocol' was not declared
Ignoring request to reassign bug #547351 to the same package
forcemerge 562441 547351
Bug#562441: l7-filter-userspace: FTBFS: l7-conntrack.cpp:129: error:
'nfct_sprintf_protocol' was not declared in this scope
Bug#547351: l7-filter-userspace: [FTBFS] 'nfct_sprintf_protocol' was not
declared
Mismatch - only Bugs in the same package can be forcibly merged:
Bug 547351 is not in the same package as 562441
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562010: marked as done (cynthiune.app: FTBFS on amd64 and kfreebsd-amd64: ICE)
Your message dated Mon, 28 Dec 2009 13:37:05 +0200 with message-id 1262000225.2638.19.ca...@keel.southway-varna.com and subject line Re: Bug#562010: cynthiune.app: FTBFS on amd64 and kfreebsd-amd64: ICE has caused the Debian Bug report #562010, regarding cynthiune.app: FTBFS on amd64 and kfreebsd-amd64: ICE 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.) -- 562010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cynthiune.app Version: 0.9.5-9 Severity: serious Justification: FTBFS Hi, your package FTBFS on both amd64 and kfreebsd-amd64: | gcc CynthiuneHeaderCell.m -c \ | -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -D_REENTRANT -fPIC -g -Wall -DDEBUG -fno-omit-frame-pointer -DGSWARN -DGSDIAGNOSE -Wno-import -O2 -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -fgnu-runtime -Wall -Wno-import -fconstant-string-class=NSConstantString -IFrameworks -IFrameworks/Cynthiune/Cynthiune.framework/Headers -I. -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ | -o obj/CynthiuneHeaderCell.m.o | CynthiuneHeaderCell.m: In function '-[CynthiuneHeaderCell drawInteriorWithFrame:inView:]': | CynthiuneHeaderCell.m:100: internal compiler error: in simplify_subreg, at simplify-rtx.c:4954 | Please submit a full bug report, | with preprocessed source if appropriate. | See file:///usr/share/doc/gcc-4.4/README.Bugs for instructions. | make[3]: *** [obj/CynthiuneHeaderCell.m.o] Error 1 | make[2]: *** [internal-app-run-compile-submake] Error 2 | make[1]: *** [Cynthiune.all.app.variables] Error 2 | make[1]: Leaving directory `/build/buildd/cynthiune.app-0.9.5' | make: *** [build-stamp] Error 2 I believe amd64 is so widespread that it shouldn't be too hard for you to get preprocessed sources, given it's your package, after all. ;) Build logs at the usual place: https://buildd.debian.org/status/package.php?suite=unstablep=cynthiune.app Mraw, KiBi. ---End Message--- ---BeginMessage--- В 00:35 +0200 на 24.12.2009 (чт), Yavor Doganov написа: Meanwhile, the ICE got fixed in GCC trunk and the 4.4 branch, so it's up to the Debian GCC folks to pick up the patch. Closing the bug; cynthiune.app has been built successfully on amd64 and kfreebsd-amd64 with gcc-4.4/4.4.2-7. ---End Message---
Bug#560446: aplus-fsf: FTBFS: MSFloat.C:123: error: invalid conversion from 'const char*' to 'char*'
I wanted to let you know that I am working on this, but I'm running into a strange issue that's holding me up. I reproduced the bug, fixed the C++, rebuilt on my machine and it works fine. However, I then attempted to build the final packages to be uploaded in a pbuilder chroot and the resulting executable segvs during the test suite. Up to date sid in both cases, compared build logs and nothing apparently differs, etc. I'm trying to figure that out now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: man-db: Shows truncated man pages sometimes
Processing commands for cont...@bugs.debian.org: forcemerge 562503 562535 Bug#562503: upgrade of man-db hangs during postinst, consumes 100% cpu for over 30 minutes Bug#562535: man-db: Shows truncated man pages sometimes Forcibly Merged 562503 562535. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561427: Statically linked ptex also crashes
I tried both 2 options.
- build your own kpathsea4 library and link it statically, but then
apply the attached patch, otherwise it will break
By using the patch, ptex seems to work correctly.
As a workaround I attached another patch to statically link libkpathsea4.
- make sure that the header files in /usr/include/kpathsea/ are used
and not the ones in the package (tetex3), and link dynamically
against libkpathsea5, in this case no patch needed.
Removing dependency on c-vararg.h, adding kpathsea/types.h and using
system libtool (which, as a result, appears to fix FTBFS on kfreebsd:
#511433) it seems to work with libkpathsea5 except that some macros
are needed, P[1-3]{C,H}, which are defined in old c-proto.h. Attached
a patch. Note that this also seems to work with new pTeX 3.1.11.
Regards,
--
YOSHINO Yoshihito yy.y.ja...@gmail.com
diff -urN ptex-bin-3.1.10+0.04b/debian/patches/teTeX/common.mk.patch ptex-bin-3.1.10+0.04b.new/debian/patches/teTeX/common.mk.patch
--- ptex-bin-3.1.10+0.04b/debian/patches/teTeX/common.mk.patch 2009-12-24 22:42:03.0 +0900
+++ ptex-bin-3.1.10+0.04b.new/debian/patches/teTeX/common.mk.patch 2009-12-24 14:03:18.0 +0900
@@ -9,12 +9,3 @@
# You can change [X]CPPFLAGS, [X]CFLAGS, or [X]DEFS, but
# please don't change ALL_CPPFLAGS or ALL_CFLAGS.
-@@ -54,7 +54,7 @@
- kpathsea_dir = $(kpathsea_parent)/kpathsea
- kpathsea_srcdir_parent = $(top_srcdir)/..
- kpathsea_srcdir = $(kpathsea_srcdir_parent)/kpathsea
--kpathsea = $(kpathsea_dir)/libkpathsea.la
-+kpathsea = -lkpathsea
-
- @ma...@ifeq ($(CC), gcc)
- @ma...@xdefs = -Wpointer-arith $(warn_more)
diff -urN ptex-bin-3.1.10+0.04b/debian/rules ptex-bin-3.1.10+0.04b.new/debian/rules
--- ptex-bin-3.1.10+0.04b/debian/rules 2009-12-24 22:42:03.0 +0900
+++ ptex-bin-3.1.10+0.04b.new/debian/rules 2009-12-24 20:59:34.0 +0900
@@ -49,6 +49,8 @@
# Apply patch to texk/make/common.mk (to avoid depending on built-in libkpathsea).
patch -p0 -d $(TETEX_SRC_DIR)/texk/make debian/patches/teTeX/common.mk.patch
+ # Apply patch to texk/kpathsea/fontmap.c (to fix loading of fonts in libkpathsea).
+ patch -p3 -d $(TETEX_SRC_DIR) debian/patches/teTeX/fix-free-error-in-fontmap-lookup.patch
# Apply patches to pTeX source (should be named as *.patch)
# Put patches in debian/patches.
@@ -73,7 +75,7 @@
./configure --prefix=/usr --without-dialog --without-texinfo \
--with-system-ncurses --with-x --with-system-zlib \
--with-system-pnglib --disable-multiplatform \
- --enable-shared)
+ --disable-shared)
# For web2c
(cd $(TETEX_SRC_DIR)/texk/web2c \
CFLAGS=$(CFLAGS) \
@@ -92,6 +94,10 @@
dh_testdir
# Add here commands to compile the package.
+ # Build kpathsea.
+ (cd $(TETEX_SRC_DIR)/texk/kpathsea \
+ make)
+
# Build pTeX.
(cd $(TETEX_SRC_DIR)/texk/web2c/$(PTEX_SRC_DIR) \
make programs)
diff -urN ptex-bin-3.1.10+0.04b/debian/control ptex-bin-3.1.10+0.04b.new/debian/control
--- ptex-bin-3.1.10+0.04b/debian/control 2009-12-24 22:42:03.0 +0900
+++ ptex-bin-3.1.10+0.04b.new/debian/control 2009-12-28 20:02:09.0 +0900
@@ -2,13 +2,13 @@
Section: tex
Priority: optional
Maintainer: Masayuki Hatta (mhatta) mha...@debian.org
-Build-Depends: debhelper ( 4.0.0), texlive-base-bin, texlive-extra-utils, texlive-metapost, flex, bison, libkpathsea-dev | libkpathsea4-dev, ptex-base (= 2.4), ptex-buildsupport (= 3.0)
+Build-Depends: debhelper ( 4.0.0), texlive-binaries, texlive-extra-utils, texlive-metapost, flex, bison, libkpathsea-dev, ptex-base (= 2.4), ptex-buildsupport (= 3.0), libtool
Standards-Version: 3.7.3
Package: ptex-bin
Architecture: any
Replaces: platex
-Depends: ptex-base (= 1:2.0-3), texlive-base-bin, texlive-math-extra, ${shlibs:Depends}
+Depends: ptex-base (= 1:2.0-3), texlive-binaries, texlive-math-extra, ${shlibs:Depends}
Suggests: dvipsk-ja, jbibtex-bin, jmpost, mendexk
Conflicts: platex
Description: The ASCII pTeX binary files
@@ -33,7 +33,7 @@
Package: jmpost
Architecture: any
-Depends: ${shlibs:Depends}, texlive-base-bin
+Depends: ${shlibs:Depends}, texlive-binaries
Recommends: ptex-bin, dvipsk-ja
Description: Japanized MetaPost, a system for drawing pictures
This is jMetaPost, a Japanized MetaPost based on the original
diff -urN ptex-bin-3.1.10+0.04b/debian/patches/teTeX/Makefile.in.patch ptex-bin-3.1.10+0.04b.new/debian/patches/teTeX/Makefile.in.patch
--- ptex-bin-3.1.10+0.04b/debian/patches/teTeX/Makefile.in.patch 1970-01-01 09:00:00.0 +0900
+++ ptex-bin-3.1.10+0.04b.new/debian/patches/teTeX/Makefile.in.patch 2009-12-28 20:02:09.0 +0900
@@ -0,0 +1,11 @@
+--- texk/web2c/web2c/Makefile.in.orig 2004-07-11 07:54:28.0 +
texk/web2c/web2c/Makefile.in 2009-12-28 09:28:33.0 +
+@@ -37,7 +37,7 @@
+ fixwrites: fixwrites.o kps.o
+ $(build_link_command) fixwrites.o kps.o
+ splitup: splitup.o kps.o
+- $(build_link_command) splitup.o kps.o
++ $(build_link_command) -lkpathsea splitup.o
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 562346 + pending Bug #562346 [src:matplotlib] matplotlib: FTBFS: Nonexistent build-dependency: latex-ucs Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 560873 is normal
Processing commands for cont...@bugs.debian.org: severity 560873 normal Bug #560873 [galeon] galeon: remote info disclosure via css Severity set to 'normal' from 'serious' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 556270 is normal
Processing commands for cont...@bugs.debian.org: severity 556270 normal Bug #556270 [galeon] epiphany-browser: CVE-2007-1084 bookmarklets cross-site info disclosure Severity set to 'normal' from 'serious' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 561339 is important
Processing commands for cont...@bugs.debian.org: severity 561339 important Bug #561339 [cacti] CVE-2009-4112: arbitrary command execution Severity set to 'important' from 'grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562846: flim: metamail package no longer exists
Package: flim Version: 1:1.14.9-4 Severity: serious The package metamail has now been removed from unstable, as it appears to be abandoned upstream. This makes flim's recommendation of metamail unfulfillable, as well as the base64-external-* etc. variables in /etc/emacs/site-start.d/50flim.el no longer functional. Julian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547280: Bug #547280: heimdal, rfc 3454, rfc 3492
Dear Jelmer! Samba 4 currently contains the full rfc3454.txt, while the debian heimdal package only contains the tables. Could samba upstream also switch to the tables only rfc3454.txt, in order to resolve this RC bug? RFC 3492 is not a problem as it's considered free according to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489692 WM -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 557000 is serious, user debian-pyt...@lists.debian.org, usertagging 557000
Processing commands for cont...@bugs.debian.org: severity 557000 serious Bug #557000 [distribute] distribute: FTBFS without Python 2.4 Severity set to 'serious' from 'important' user debian-pyt...@lists.debian.org Setting user to debian-pyt...@lists.debian.org (was uba...@users.sf.net). usertags 557000 = python2.4-removal Bug#557000: distribute: FTBFS without Python 2.4 Usertags were: python2.6 ftbfs. Usertags are now: python2.4-removal. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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: reassign 562775 libvtk-java Bug #562775 [gdcm] FTBFS: Could not find vtk.jar file, VTK_JAVA_JAR is wrong, please set proper GDCM_VTK_JAVA_JAR replacement var Bug reassigned from package 'gdcm' to 'libvtk-java'. Bug No longer marked as found in versions 2.0.14-2. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 557293 is serious, user debian-pyt...@lists.debian.org, usertagging 557293
Processing commands for cont...@bugs.debian.org: severity 557293 serious Bug #557293 [polybori] polybori: FTBFS without Python 2.4 Severity set to 'serious' from 'important' user debian-pyt...@lists.debian.org Setting user to debian-pyt...@lists.debian.org (was uba...@users.sf.net). usertags 557293 = python2.4-removal Bug#557293: polybori: FTBFS without Python 2.4 Usertags were: python2.6 ftbfs. Usertags are now: python2.4-removal. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561505: workaround
Hi y'all, This bug happened here too. It causes apt-get upgrade to fail to upgrade all x-server drivers. dpkg --configure hal fails with the same message you described. I also found that even manually invoking hald fails immediately. using top, i found that there are two processes of user haldaemon : hald and hald-addon-acpi. I then did 'killall hald', and after that, dpkg --configure hal worked like a charm. (i also killalled the addon-acpi, but it was already gone). As to your enumerated solutions, 1 is arbitrary, there doesn't seem a real advantage to either choice, 3 and 4 are not sufficient, and 2 kills something, so i like 2 best, but don't see why it should depend on location of pidfile. Happy New Year, Siward -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561427: Statically linked ptex also crashes
Dear Yoshino-san,
thanks a lot for your work. Now it is up to the maintainer of ptex
to implement that. We (debian-tex-maint) are not in the position to
change anything.
I hope that the maintainer will update the package in one way or the
other, otherwise I guess we have to prepare an NMU.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
HAUGHAM (n.)
One who loudly informs other diners in a restaurant what kind of man
he is by calling for the chef by his christian name from the lobby.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: ggz-server: diff for NMU version 0.0.14.1-1.4
Processing commands for cont...@bugs.debian.org: tag 504972 + pending Bug #504972 [ggz-server] FTBFS with GCC 4.4: missing #include Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504972: ggz-server: diff for NMU version 0.0.14.1-1.4
tag 504972 + pending thanks Dear maintainer, I've prepared an NMU for ggz-server (versioned as 0.0.14.1-1.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- /\ ASCII Ribbon : GPG-Key ID: 0xD49AE731 \ /Campaign : CaCert Assurer X against HTML : Debian Maintainer / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ diff -u ggz-server-0.0.14.1/debian/changelog ggz-server-0.0.14.1/debian/changelog --- ggz-server-0.0.14.1/debian/changelog +++ ggz-server-0.0.14.1/debian/changelog @@ -1,3 +1,11 @@ +ggz-server (0.0.14.1-1.4) unstable; urgency=low + + * Non-maintainer upload. + * Fix building with gcc 4.4 (Closes: #504972) using the patch from +Martin Michlmayr + + -- Christoph Egger christ...@debian.org Mon, 28 Dec 2009 16:31:01 +0100 + ggz-server (0.0.14.1-1.3) unstable; urgency=low * Non-maintainer upload. signature.asc Description: Digital signature
Bug#562346: marked as done (matplotlib: FTBFS: Nonexistent build-dependency: latex-ucs)
Your message dated Mon, 28 Dec 2009 15:49:55 + with message-id e1nphr1-0001a1...@ries.debian.org and subject line Bug#562346: fixed in matplotlib 0.99.1.2-2 has caused the Debian Bug report #562346, regarding matplotlib: FTBFS: Nonexistent build-dependency: latex-ucs 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.) -- 562346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: matplotlib Version: 0.99.1.2-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091213 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 7), dvipng, graphviz, ipython, latex-ucs, libfreetype6-dev, libgtk2.0-dev, libpng-dev, python-all-dbg (= 2.4.4-6), python-all-dev (= 2.3.5-7), python-configobj, python-dateutil, python-epydoc, python-gtk2-dev, python-imaging, python-numpy (= 1:1.1.0), python-numpy-dbg (= 1:1.1.0), python-pkg-resources, python-qt4, python-qt4-dev, python-qt-dev, python-setuptools, python-sphinx (= 0.5.1), python-support (= 1.0.0), python-tk (= 2.5.2-1.1), python-traits (= 2.0), python-tz, python-wxgtk2.8, python-wxgtk2.8-dbg, quilt, tcl8.5-dev, texlive-fonts-recommended, texlive-latex-extra, tk8.5-dev, zlib1g-dev ┌──┐ │ Install build dependencies │ └──┘ Checking for already installed source dependencies... W: Unable to locate package latex-ucs debhelper: missing Using default version 7.4.10 dvipng: missing graphviz: missing ipython: missing latex-ucs: missing libfreetype6-dev: missing libgtk2.0-dev: missing libpng-dev: missing python-all-dbg: missing Using default version 2.5.4-4 python-all-dev: missing Using default version 2.5.4-4 python-configobj: missing python-dateutil: missing python-epydoc: missing python-gtk2-dev: missing python-imaging: missing python-numpy: missing Using default version 1:1.3.0-3 python-numpy-dbg: missing Using default version 1:1.3.0-3 python-pkg-resources: missing python-qt4: missing python-qt4-dev: missing python-qt-dev: missing python-setuptools: missing python-sphinx: missing Using default version 0.6.3-1 python-support: missing Using default version 1.0.6 python-tk: missing Using default version 2.5.2-1.1 python-traits: missing Using default version 3.2.0-1 python-tz: missing python-wxgtk2.8: missing python-wxgtk2.8-dbg: missing quilt: missing tcl8.5-dev: missing texlive-fonts-recommended: missing texlive-latex-extra: missing tk8.5-dev: missing zlib1g-dev: missing Checking for source dependency conflicts... E: Couldn't find package latex-ucs The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/13/matplotlib_0.99.1.2-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: matplotlib Source-Version: 0.99.1.2-2 We believe that the bug you reported is fixed in the latest version of matplotlib, which is due to be installed in the Debian FTP archive: matplotlib_0.99.1.2-2.debian.tar.gz to main/m/matplotlib/matplotlib_0.99.1.2-2.debian.tar.gz matplotlib_0.99.1.2-2.dsc to main/m/matplotlib/matplotlib_0.99.1.2-2.dsc python-matplotlib-data_0.99.1.2-2_all.deb to main/m/matplotlib/python-matplotlib-data_0.99.1.2-2_all.deb python-matplotlib-dbg_0.99.1.2-2_amd64.deb to main/m/matplotlib/python-matplotlib-dbg_0.99.1.2-2_amd64.deb python-matplotlib-doc_0.99.1.2-2_all.deb to main/m/matplotlib/python-matplotlib-doc_0.99.1.2-2_all.deb python-matplotlib_0.99.1.2-2_amd64.deb to main/m/matplotlib/python-matplotlib_0.99.1.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 562...@bugs.debian.org,
Bug#562775: Bug#562387: Bug#533193: [Debian-med-packaging] Bug#562387: gdcm: FTBFS: cmake error
On Sun, Dec 27, 2009 at 7:42 PM, Denis Barbier bou...@gmail.com wrote: On 2009/12/27 Mathieu Malaterre wrote: [...] Does this help ? Even if the path is wrong in VTKConfig.cmake, GDCM can cope with that. In the end /usr/share/java/vtk/vtk.jar should be the vtk jar file. [...] I was confused by your message, /usr/share/java/vtk.jar is the expected location of the jar file. and this is what your commit does, If you do the upload, please close this new bug too. thanks http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562775 -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#561417: dglog: Denied requests show up as allowed
Processing commands for cont...@bugs.debian.org: severity 561417 grave Bug #561417 [dglog] dglog: Denied requests show up as allowed Severity set to 'grave' from 'important' tags 561417 pending Bug #561417 [dglog] dglog: Denied requests show up as allowed Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#473400: xlockmore can also be crashed with Alt-SysRq-F
Another way to crash xlockmore is using Alt-SysRq-F. gnome-screensaver is not
vulnerable to this attack. A way to avoid this is to add something like this to
the very beginning of main():
for(;;)
{
pid_t child;
int status;
child = fork();
if(!child)
break;
while(-1 == waitpid(child, status, 0) errno == EINTR)
;
if(!WIFSIGNALED(status))
return EXIT_SUCCESS;
}
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561915: qbittorrent crash
Unfortunately, it looks like the crash is not in this thread. Could you please try to get the backtrace for all threads? In gdb, issue the following command: $ thread apply all bt Thanks in advance. On Sun, Dec 27, 2009 at 2:09 AM, riptide ript...@mundo-r.com wrote: Hello It is reproducible. Every time i run qbittorrent it crashes with the same error. Here is the complete backtrace (I read some doc about gdb) (gdb) bt #0 0x in ?? () #1 0x76bc53dc in ?? () from /usr/lib/libQtGui.so.4 #2 0x76bc613e in ?? () from /usr/lib/libQtGui.so.4 #3 0x76b7f547 in ?? () from /usr/lib/libQtGui.so.4 #4 0x76ba62ca in ?? () from /usr/lib/libQtGui.so.4 #5 0x76bb1541 in ?? () from /usr/lib/libQtGui.so.4 #6 0x76b3ecdd in ?? () from /usr/lib/libQtGui.so.4 #7 0x76b41bf7 in QPainter::drawRects(QRectF const*, int) () from /usr/lib/libQtGui.so.4 #8 0x76b43c63 in QPainter::drawPixmap(QRectF const, QPixmap const, QRectF const) () from /usr/lib/libQtGui.so.4 #9 0x00595c45 in DownloadedPiecesBar::paintEvent(QPaintEvent*) () #10 0x76a70196 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #11 0x76a2001d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #12 0x76a2807a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #13 0x76230c9c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #14 0x76a771be in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #15 0x76a77907 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #16 0x76a76e37 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #17 0x76a77907 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #18 0x76a76e37 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #19 0x76a77907 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #20 0x76a76e37 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QW---Type return to continue, or q return to quit--- idgetBackingStore*) () from /usr/lib/libQtGui.so.4 #21 0x76a77907 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #22 0x76a76e37 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #23 0x76a77907 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #24 0x76a76e37 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #25 0x76a77907 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #26 0x76a77816 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #27 0x76a77816 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #28 0x76a77816 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #29 0x76a77816 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #30 0x76a77816 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject* const, int, QRegion const, QPoint const, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4 #31 0x76a77816 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QListQObject*
Bug#562381: libxml-parser-perl: FTBFS: tests failed
Am Donnerstag, den 24.12.2009, 11:46 +0100 schrieb Lucas Nussbaum: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[2]: Entering directory `/build/user-libxml-parser-perl_2.36-1.1-amd64-mO8frO/libxml-parser-perl-2.36/Expat' make[2]: Leaving directory `/build/user-libxml-parser-perl_2.36-1.1-amd64-mO8frO/libxml-parser-perl-2.36/Expat' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/astress.t ... ok t/cdata.t . ok syntax error at line 14, column 3, byte 214: %ext; ![%bar;[ ==^ !ATTLIST bar xyz (a|b|c) 'b' ]] error in processing external entity reference at line 21, column 3, byte 3161: !ELEMENT bar ANY !ATTLIST bar big CDATA 'This is a large string value to test whether the declaration parser still works when the entity or attribute default value may be broken into multiple calls to the default handler. 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 ' ] ==^ foo/ at /build/user-libxml-parser-perl_2.36-1.1-amd64-mO8frO/libxml-parser-perl-2.36/blib/lib/XML/Parser.pm line 187 t/decl.t .. Dubious, test returned 9 (wstat 2304, 0x900) Failed 29/30 subtests t/defaulted.t . ok t/encoding.t .. ok t/external_ent.t .. ok t/file.t .. ok t/finish.t ok t/namespaces.t ok error in processing external entity reference at line 8, column 0, byte 173: !ENTITY more SYSTEM t/ext2.ent ] ^ fooHappy, happy barjoy;, joy;/bar at /build/user-libxml-parser-perl_2.36-1.1-amd64-mO8frO/libxml-parser-perl-2.36/blib/lib/XML/Parser.pm line 187 t/parament.t .. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 11/12 subtests t/partial.t ... ok t/skip.t .. ok t/stream.t ok Failed 2/14 test programs. 0/90 subtests failed. t/styles.t ok FYI: This is triggered by the recent fix in expat for CVE-2009-3560. See also http://bugs.debian.org/561658 and http://lists.debian.org/debian-devel/2009/12/msg00674.html. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 562381, block 562381 with 561658
Processing commands for cont...@bugs.debian.org: tags 562381 + confirmed help Bug #562381 [src:libxml-parser-perl] libxml-parser-perl: FTBFS: tests failed Added tag(s) confirmed and help. block 562381 with 561658 Bug #562381 [src:libxml-parser-perl] libxml-parser-perl: FTBFS: tests failed Was not blocked by any bugs. Added blocking bug(s) of 562381: 561658 End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525887: Bug can be closed
Dear maintainers, due to a new kernel, this bugreport can safely be closed. Thank you for the work! Cheers Hans -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562729: Revert to previous version
Revert to previous version works : /sbin/rpc.statd --version rpc.statd version 1.1.6 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556809: adasockets: FTBFS: sockets.ads:60:16: (style) in should be omitted
The bug is triggered by the transition from gnat-4.3 to gnat-4.4. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagpending
Processing commands for cont...@bugs.debian.org: tag 560675 + pending Bug #560675 [src:gpe-contacts] gpe-contacts: FTBFS: Nonexistent build-dependency: libmimedir-gnome0-dev Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562884: xscreensaver can be killed with Alt+SysRq+F
Package: xscreensaver Version: 4.24-5 Severity: grave Tags: security Justification: user security hole Hi, I'm a bit new to this bugreporting stuff. I have however discovered that it is possible to kill xscreensaver with Alt+SysRq+F (if this function is not disabled). This may comprimise security when xscreensaver-command is used with the -lock option, because the screen will be unlocked. gnome-screensaver seems not to be vulnerable to this attack. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562757: nfs-common: rpc.statd is unable to register itself with portmap
Waba w...@waba.be wrote: Hi, Upon closer examination (strace), rpc.statd is trying to connect to [::1]:111 while portmap is listening on IPv4 only. Replacing portmap by rpcbind might fix the problem, but I have not tried it. rpcbind, you mean the package that can't be installed because it has a file conflict with libc-bin? RC bug report on Sep 1st 2009, still unfixed. And now that, which seriously leads me wondering about the level of testing that went into this upload. 0 is my guess. Testing on a non-standard installation doesn't count, of course (like a system with rpcbind installed thanks to --force-overwrite). JB. -- Julien BLACHE - Debian GNU/Linux Developer - jbla...@debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562871: tp-smapi-dkms: Fails to install due to missing kernel headers
Package: tp-smapi-dkms Version: 0.40-6 Severity: serious On my system, the tp-smapi-dkms package fails to install with this error message: , | $ sudo dpkg --configure -a | Setting up tp-smapi-dkms (0.40-6) ... | | Error! Your kernel headers for kernel 2.6.31-1-686 cannot be found at | /lib/modules/2.6.31-1-686/build or /lib/modules/2.6.31-1-686/source. | You can use the --kernelsourcedir option to tell DKMS where it's located, or you could install the linux-headers-2.6.31-1-686 package. | dpkg: error processing tp-smapi-dkms (--configure): | subprocess installed post-installation script returned error exit status 1 | Errors were encountered while processing: | tp-smapi-dkms ` I just reproduced by purging and reinstalling the package. dkms is complaining about the correct thing -- the kernel headers aren't installed on the system. But this should not make the postinst script fail. Cheers, -Hilko -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.31-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tp-smapi-dkms depends on: ii dkms 2.1.1.0-2 Dynamic Kernel Module Support Fram tp-smapi-dkms recommends no packages. tp-smapi-dkms 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#554046: debugging the infinite suspend loop
Package: gnome-power-manager
Version: 2.28.1-2
Using g-p-m and lid closing and off we go into infinite cycles.
Sysrq-ing out is the only option.
Attached is a log of
gnome-power-manager --verbose
(btw, why is it so hard to explain in a short answer that the option
--debug is not actually debugging anything?)
Still 100% reproducible.
- suspending with lid-close goes into infinite loop
- suspending with click-power-icon, select suspend *works*
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
MARGATE (n.)
A margate is a particular kind of commissionaire who sees you every
day and is on cheerful Christian-name terms with you, then one day
refuses to let you in because you've forgotten your identify card.
--- Douglas Adams, The Meaning of Liff
TI:05:18:03 TH:0x12e90e0FI:egg-debug.c FN:egg_debug_init,306
- Verbose debugging 1 (on console 0)GPM_VERBOSE
TI:05:18:03 TH:0x12e90e0FI:gpm-main.c FN:main,210
- GNOME Power Manager 2.28.2
TI:05:18:03 TH:0x12e90e0FI:gpm-session.cFN:gpm_session_init,463
- idle: 0, inhibited: 0
TI:05:18:03 TH:0x12e90e0FI:gpm-session.c
FN:gpm_session_register_client,324
- registered startup '(null)' to client id '/org/gnome/SessionManager/Client16'
TI:05:18:03 TH:0x12e90e0FI:egg-console-kit.c
FN:egg_console_kit_init,304
- ConsoleKit session ID: /org/freedesktop/ConsoleKit/Session1
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=124
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=213
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=150
*** WARNING ***
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_xevent_key,203
- could not map keysym 1008ffa8 to keycode
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=233
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=232
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=160
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=244
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=238
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=237
TI:05:18:03 TH:0x12e90e0FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=236
TI:05:18:03 TH:0x12e90e0FI:egg-dbus-proxy.c
FN:egg_dbus_proxy_connect,73
- already connected to org.gnome.ScreenSaver
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness-xrandr.c
FN:gpm_brightness_xrandr_update_cache,628
- screen 1 of 1
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness-xrandr.c
FN:gpm_brightness_xrandr_update_cache,633
- watching ::monitors_changed on 0x12f0130
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness-xrandr.c
FN:gpm_brightness_xrandr_update_cache,654
- adding resource 0x138c8d0
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness.c
FN:gpm_brightness_init,436
- detected XRANDR hardware
TI:05:18:03 TH:0x12e90e0FI:egg-dbus-proxy.c
FN:egg_dbus_proxy_connect,73
- already connected to org.freedesktop.Hal
TI:05:18:03 TH:0x12e90e0FI:egg-dbus-proxy.c
FN:egg_dbus_proxy_connect,73
- already connected to org.freedesktop.Hal
TI:05:18:03 TH:0x12e90e0FI:egg-dbus-proxy.c
FN:egg_dbus_proxy_connect,73
- already connected to org.freedesktop.Hal
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness-hal.c
FN:gpm_brightness_hal_init,476
- Laptop panel levels: 9
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness-hal.c
FN:gpm_brightness_hal_init,492
- laptop_panel.brightness_in_hardware: True
TI:05:18:03 TH:0x12e90e0FI:egg-dbus-proxy.c
FN:egg_dbus_proxy_connect,73
- already connected to org.freedesktop.Hal
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness-hal.c
FN:gpm_brightness_hal_get_hw,119
- GetBrightness returned level: 8
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness-hal.c
FN:gpm_brightness_hal_init,513
- Starting: (8 of 8)
TI:05:18:03 TH:0x12e90e0FI:gpm-brightness.c
FN:gpm_brightness_init,444
- detected HAL hardware
TI:05:18:03 TH:0x12e90e0FI:gpm-prefs-server.c
FN:gpm_prefs_server_set_capability,84
- capability now 4
TI:05:18:03 TH:0x12e90e0
Bug#552902: marked as done (texfam: FTBFS: tangleboot.h:34: error: conflicting types for 'getline')
Your message dated Mon, 28 Dec 2009 20:40:12 + with message-id 1262032812.857689.2243.nullmai...@kmos.homeip.net and subject line Package texfam has been removed from Debian has caused the Debian Bug report #552902, regarding texfam: FTBFS: tangleboot.h:34: error: conflicting types for 'getline' 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.) -- 552902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: texfam Version: 1.2.1-9.1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. In eglibc = 2.9, getline was only defined if _GNU_SOURCE was defined. In eglibc 2.10, getline is always defined (since it became a standard in POSIX2008). The problem is that your package already has a function named getline(), which now conflicts with glibc's. You need to rename your function to something else. Ubuntu already fixed many occurences of your problem, so it is possible that an Ubuntu patch is available for your package. Look at the PTS to find out. Relevant part: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -Wall -O2 -fomit-frame-pointer -c tangleboot.c In file included from tangleboot.c:92: tangleboot.h:34: error: conflicting types for 'getline' /usr/include/stdio.h:651: error: previous declaration of 'getline' was here tangleboot.c: In function 'initialize': tangleboot.c:329: warning: array subscript has type 'char' tangleboot.c:330: warning: array subscript has type 'char' tangleboot.c:339: warning: array subscript has type 'char' tangleboot.c:340: warning: array subscript has type 'char' tangleboot.c: In function 'zinputln': tangleboot.c:406: warning: type defaults to 'int' in declaration of 'c' tangleboot.c: In function 'zprintid': tangleboot.c:429: warning: array subscript has type 'char' tangleboot.c: In function 'zidlookup': tangleboot.c:465: warning: array subscript has type 'char' tangleboot.c:539: warning: array subscript has type 'char' tangleboot.c:556: warning: array subscript has type 'char' tangleboot.c:568: warning: array subscript has type 'char' tangleboot.c:589: warning: array subscript has type 'char' tangleboot.c:593: warning: array subscript has type 'char' tangleboot.c: In function 'zmodlookup': tangleboot.c:667: warning: array subscript has type 'char' tangleboot.c:678: warning: array subscript has type 'char' tangleboot.c:690: warning: array subscript has type 'char' tangleboot.c:716: warning: array subscript has type 'char' tangleboot.c:718: warning: array subscript has type 'char' tangleboot.c: In function 'zprefixlookup': tangleboot.c:761: warning: array subscript has type 'char' tangleboot.c:772: warning: array subscript has type 'char' tangleboot.c:793: warning: suggest explicit braces to avoid ambiguous 'else' tangleboot.c: In function 'zstoretwobytes': tangleboot.c:817: warning: array subscript has type 'char' tangleboot.c:825: warning: array subscript has type 'char' tangleboot.c:825: warning: array subscript has type 'char' tangleboot.c:826: warning: array subscript has type 'char' tangleboot.c:826: warning: array subscript has type 'char' tangleboot.c:827: warning: array subscript has type 'char' tangleboot.c:827: warning: array subscript has type 'char' tangleboot.c: In function 'poplevel': tangleboot.c:871: warning: array subscript has type 'char' tangleboot.c: In function 'getoutput': tangleboot.c:916: warning: array subscript has type 'char' tangleboot.c:918: warning: suggest explicit braces to avoid ambiguous 'else' tangleboot.c:925: warning: array subscript has type 'char' tangleboot.c:952: warning: array subscript has type 'char' tangleboot.c:967: warning: array subscript has type 'char' tangleboot.c:976: warning: array subscript has type 'char' tangleboot.c:984: warning: array subscript has type 'char' tangleboot.c:984: warning: array subscript has type 'char' tangleboot.c:985: warning: array subscript has type 'char' tangleboot.c:985: warning: array subscript has type 'char' tangleboot.c:987: warning: array subscript has type 'char' tangleboot.c:1004: warning: array subscript has type 'char' tangleboot.c:1012: warning: array subscript has type 'char' tangleboot.c:1012: warning: array subscript has type 'char' tangleboot.c:1013: warning: array subscript has type 'char' tangleboot.c:1013: warning: array subscript has type 'char' tangleboot.c:1015: warning: array subscript has type 'char'
Bug#560146: marked as done (kvm: failing to go fullscreen in SDL mode explodes the entire emulator process)
Your message dated Mon, 28 Dec 2009 20:47:08 + with message-id 1262033228.426642.2542.nullmai...@kmos.homeip.net and subject line Package kvm has been removed from Debian has caused the Debian Bug report #560146, regarding kvm: failing to go fullscreen in SDL mode explodes the entire emulator process 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.) -- 560146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kvm Version: 85+dfsg-4.1 Severity: critical Justification: causes serious data loss The situation in which I encountered this involved the OpenSolaris 2009.06 Live CD, after it had entered graphical mode. FWIW, my X configuration is 1280x1024; the graphics window for KVM also appeared to be 1280x1024. The command line was: kvm -name dumbbell -uuid e7c06115-e211-4be5-b7e2-47d1502ed59e \ -m 1024 -hda dumbbell.qcow -vga vmware -net nic,vlan=0 -net user,vlan=0 \ -monitor stdio -no-shutdown -cdrom osol-0906-x86.iso -boot d Pressing C-A-f in the SDL display window to switch to fullscreen mode failed with Could not open SDL display, and the entire emulator process immediately vanished with no chance to checkpoint with a savevm or allow the guest to sync its disks or anything. In this case, I got lucky since it happened early in the OS install stage, but in other circumstances a sudden emulator exit could cause serious data loss, which is why I am filing this as a critical bug, similarly to #537569. (As usual, if this is not the correct severity, please advise as to the correct severity.) --- Drake Wilson -- Package-specific info: selected information from lshal(1): /proc/cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 75 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping: 2 cpu MHz : 2210.047 cache size : 512 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips: 4420.09 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 75 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping: 2 cpu MHz : 2210.047 cache size : 512 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips: 4420.30 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-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/bash Versions of packages kvm depends on: ii adduser3.111 add and remove users and groups ii bridge-utils 1.4-5 Utilities for configuring the Linu ii iproute20090324-1networking and traffic control too ii libasound2 1.0.21a-1 shared library for ALSA applicatio ii libbluetooth3 4.57-1Library to use the BlueZ Linux Blu ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libgnutls262.8.5-2 the GNU TLS library - runtime libr ii libncurses55.7+20090803-2shared libraries for terminal hand ii libpci31:3.1.4-4 Linux PCI Utilities (shared librar ii libpulse0 0.9.21-1 PulseAudio client libraries ii
Bug#553552: marked as done (phpix: dir-or-file-in-var-www /var/www/phpix/albums/Sample Album/A-10.txt and 10 others)
Your message dated Mon, 28 Dec 2009 20:45:38 +
with message-id 1262033138.178611.2395.nullmai...@kmos.homeip.net
and subject line Package phpix has been removed from Debian
has caused the Debian Bug report #553552,
regarding phpix: dir-or-file-in-var-www /var/www/phpix/albums/Sample
Album/A-10.txt and 10 others
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.)
--
553552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: phpix
Version: 2.0.2-7
Severity: serious
User: lintian-ma...@debian.org
Usertags: dir-or-file-in-var-www
Debian packages should not install files under /var/www. This is not
one of the /var directories in the File Hierarchy Standard and is
under the control of the local administrator. Packages should not
assume that it is the document root for a web server; it is very
common for users to change the default document root and packages
should not assume that users will keep any particular setting.
Packages that want to make files available via an installed web server
should instead put instructions for the local administrator in a
README.Debian file and ideally include configuration fragments for
common web servers such as Apache.
As an exception, packages are permitted to create the /var/www
directory due to its past history as the default document root, but
should at most copy over a default file in postinst for a new install.
Refer to Filesystem Hierarchy Standard (The /var Hierarchy) for
details.
One solution that works is to put configuration files into
/etc/package_name, put static content, if any, into
/usr/{share,lib}/package_name, then create /var/lib/package name
as home for the package, and symlink the files from /etc and /usr/
into the /var/lib/package_name. Then create a simple set of
configuration snippets for popular web servers (for example, files one
may link into /etc/apache2/conf.d) and put them into
/etc/package_name. This way user modifiable files stil live in /etc,
and a simple operation can make the package go live.
Filed as serious, since this is a violation of the FHS (which is part
of policy), and also since a package with these files will currently
get this package rejected. See
http://lists.debian.org/debian-devel-announce/2009/10/msg4.html
for details. This means the package has been deemed too buggy to be in
Debian.
manoj
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages phpix depends on:
ii apache2 2.2.14-1Apache HTTP Server metapackage
ii apache2-mpm-prefork [apache2 2.2.14-1Apache HTTP Server - traditional n
ii imagemagick 7:6.5.5.3-1 image manipulation programs
pn php5 none (no description available)
phpix recommends no packages.
phpix suggests no packages.
---End Message---
---BeginMessage---
Version: 2.0.2-7+rm
You filled the bug http://bugs.debian.org/553552 in Debian BTS
against the package phpix. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/558175. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
---End Message---
Bug#534067: marked as done (slide-webdavclient: FTBFS: Nonexistent build-dependency: libxml-im-exporter-java)
Your message dated Mon, 28 Dec 2009 20:40:51 + with message-id 1262032851.006679.2263.nullmai...@kmos.homeip.net and subject line Package slide-webdavclient has been removed from Debian has caused the Debian Bug report #534067, regarding slide-webdavclient: FTBFS: Nonexistent build-dependency: libxml-im-exporter-java 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.) -- 534067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: slide-webdavclient Version: 2.1+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20090620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (= 5.0.0), ant Build-Depends-Indep: java-gcj-compat-dev, libcommons-httpclient-java, libjdom1-java, libxml-im-exporter-java ┌──┐ │ Install build dependencies │ └──┘ Checking for already installed source dependencies... W: Unable to locate package libxml-im-exporter-java debhelper: missing Using default version 7.2.16 ant: missing java-gcj-compat-dev: missing libcommons-httpclient-java: missing libjdom1-java: missing libxml-im-exporter-java: missing Checking for source dependency conflicts... E: Couldn't find package libxml-im-exporter-java The full build log is available from: http://people.debian.org/~lucas/logs/2009/06/20/slide-webdavclient_2.1+dfsg-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--- Version: 2.1+dfsg-2+rm You filled the bug http://bugs.debian.org/534067 in Debian BTS against the package slide-webdavclient. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/531446. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues ---End Message---
Processed: New version of this problem in 3.0.15-3
Processing commands for cont...@bugs.debian.org:
found 534735 3.0.15-3
Bug #534735 {Done: Roland Rosenfeld rol...@debian.org} [privoxy] The
configuration listen-address :8118 is not possible with 3.0.13-1
Bug Marked as found in versions privoxy/3.0.15-3 and reopened.
# privoxy starts and reports no errors, but it doesn't actually *listen*
(nmap reports port as closed)
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527688: marked as done (mod-bt: FTBFS: configure.in:52: error: AC_SUBST: `APXS BUILD_APACHE2' is not a valid shell variable name)
Your message dated Mon, 28 Dec 2009 20:43:40 + with message-id 1262033020.779539.2330.nullmai...@kmos.homeip.net and subject line Package mod-bt has been removed from Debian has caused the Debian Bug report #527688, regarding mod-bt: FTBFS: configure.in:52: error: AC_SUBST: `APXS BUILD_APACHE2' is not a valid shell variable name 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.) -- 527688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mod-bt Version: 0.0.19+p4.2340-1.2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20090508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: dh_testdir autoreconf configure.in:52: error: AC_SUBST: `APXS BUILD_APACHE2' is not a valid shell variable name acinclude.m4:93: MODBT_CHECK_APXS is expanded from... configure.in:52: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 make: *** [configure-stamp5] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/05/08/mod-bt_0.0.19+p4.2340-1.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--- Version: 0.0.19+p4.2340-1.2+rm You filled the bug http://bugs.debian.org/527688 in Debian BTS against the package mod-bt. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/555033. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues ---End Message---
Bug#528519: marked as done (kvm: FTBFS with 2.6.29)
Your message dated Mon, 28 Dec 2009 20:47:07 + with message-id 1262033227.801242.2520.nullmai...@kmos.homeip.net and subject line Package kvm has been removed from Debian has caused the Debian Bug report #528519, regarding kvm: FTBFS with 2.6.29 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.) -- 528519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kvm-source Severity: serious Hi, kvm doesn't build with 2.6.29. ---snip--- [...] /usr/src/modules/kvm/svm.c:1944: error: unknown field 'inject_pending_irq' specified in initializer /usr/src/modules/kvm/svm.c:1944: warning: excess elements in struct initializer /usr/src/modules/kvm/svm.c:1944: warning: (near initialization for 'svm_x86_ops') /usr/src/modules/kvm/svm.c:1945: error: unknown field 'inject_pending_vectors' specified in initializer /usr/src/modules/kvm/svm.c:1945: warning: excess elements in struct initializer /usr/src/modules/kvm/svm.c:1945: warning: (near initialization for 'svm_x86_ops') /usr/src/modules/kvm/svm.c:1947: error: unknown field 'set_tss_addr' specified in initializer /usr/src/modules/kvm/svm.c:1947: warning: excess elements in struct initializer /usr/src/modules/kvm/svm.c:1947: warning: (near initialization for 'svm_x86_ops') /usr/src/modules/kvm/svm.c:1948: error: unknown field 'get_tdp_level' specified in initializer /usr/src/modules/kvm/svm.c:1948: warning: excess elements in struct initializer /usr/src/modules/kvm/svm.c:1948: warning: (near initialization for 'svm_x86_ops') /usr/src/modules/kvm/svm.c:1951: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'svm_init' /usr/src/modules/kvm/svm.c:1957: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'svm_exit' /usr/src/modules/kvm/svm.c:1963: warning: return type defaults to 'int' /usr/src/modules/kvm/svm.c:1963: warning: function declaration isn't a prototype /usr/src/modules/kvm/svm.c: In function 'module_init': /usr/src/modules/kvm/svm.c:1963: error: expected declaration specifiers before 'module_exit' make[6]: *** [/usr/src/modules/kvm/svm.o] Error 1 make[5]: *** [_module_/usr/src/modules/kvm] Error 2 make[4]: *** [sub-make] Error 2 make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-2.6.29-2-686' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/modules/kvm' make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory `/usr/src/modules/kvm' make: *** [kdist_build] Error 2 ---snap--- -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ ---End Message--- ---BeginMessage--- Version: 85+dfsg-4.1+rm You filled the bug http://bugs.debian.org/528519 in Debian BTS against the package kvm. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/562620. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues ---End Message---
Bug#527688: marked as done (mod-bt: FTBFS: configure.in:52: error: AC_SUBST: `APXS BUILD_APACHE2' is not a valid shell variable name)
Your message dated Mon, 28 Dec 2009 20:43:40 + with message-id 1262033020.779539.2330.nullmai...@kmos.homeip.net and subject line Package mod-bt has been removed from Debian has caused the Debian Bug report #527688, regarding mod-bt: FTBFS: configure.in:52: error: AC_SUBST: `APXS BUILD_APACHE2' is not a valid shell variable name 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.) -- 527688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mod-bt Version: 0.0.19+p4.2340-1.2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20090508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: dh_testdir autoreconf configure.in:52: error: AC_SUBST: `APXS BUILD_APACHE2' is not a valid shell variable name acinclude.m4:93: MODBT_CHECK_APXS is expanded from... configure.in:52: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 make: *** [configure-stamp5] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/05/08/mod-bt_0.0.19+p4.2340-1.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--- Version: 0.0.19+p4.2340-1.2+rm You filled the bug http://bugs.debian.org/527688 in Debian BTS against the package mod-bt. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/555033. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues ---End Message---
Bug#553590: marked as done (CVE-2009-3616: Multiple use-after-free vulnerabilities in vnc.c)
Your message dated Mon, 28 Dec 2009 20:47:08 + with message-id 1262033228.068725.2530.nullmai...@kmos.homeip.net and subject line Package kvm has been removed from Debian has caused the Debian Bug report #553590, regarding CVE-2009-3616: Multiple use-after-free vulnerabilities in vnc.c 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.) -- 553590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kvm Severity: grave Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the following CVE (Common Vulnerabilities Exposures) id was published for kvm. CVE-2009-3616[0]: | Multiple use-after-free vulnerabilities in vnc.c in the VNC server in | QEMU 0.10.6 and earlier might allow guest OS users to execute | arbitrary code on the host OS by establishing a connection from a VNC | client and then (1) disconnecting during data transfer, (2) sending a | message using incorrect integer data types, or (3) using the Fuzzy | Screen Mode protocol, related to double free vulnerabilities. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3616 http://security-tracker.debian.org/tracker/CVE-2009-3616 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrtYAYACgkQNxpp46476aqAZQCggUoTDn0woH1Gq2ho3OClxwxR zQMAn26utjy966AXv1YpjIZB9YzErFhw =iWBL -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Version: 85+dfsg-4.1+rm You filled the bug http://bugs.debian.org/553590 in Debian BTS against the package kvm. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/562620. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues ---End Message---
Bug#531445: marked as done (abandoned upstream; please keep out of squeeze)
Your message dated Mon, 28 Dec 2009 20:40:51 + with message-id 1262032851.043766.2265.nullmai...@kmos.homeip.net and subject line Package slide-webdavclient has been removed from Debian has caused the Debian Bug report #531445, regarding abandoned upstream; please keep out of squeeze 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.) -- 531445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libslide-webdavclient-java Version: 2.1+dfsg-2 Severity: serious The Jakarta Slide project was retired on 2007-11-03 and has not been receiving maintenance or security fixes for even longer. This package should therefore be kept out of squeeze. The recommended migration path is Apache Jackrabbit. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29.4-melech (SMP w/2 CPU cores; PREEMPT) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libslide-webdavclient-java depends on: ii default-jre [java2-runtime] 1.5-32 Standard Java or Java compatible R ii jamvm [java1-runtime] 1.5.1-3virtual machine which conforms to ii java-gcj-compat [java2-runtim 1.0.80-3 Java runtime environment using GIJ ii openjdk-6-jre [java2-runtime] 6b16-2 OpenJDK Java runtime, using Hotspo libslide-webdavclient-java recommends no packages. libslide-webdavclient-java suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.1+dfsg-2+rm You filled the bug http://bugs.debian.org/531445 in Debian BTS against the package slide-webdavclient. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/531446. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues ---End Message---
Bug#551620: marked as done (DOS on the LAN when starting kvm with 2 network devices and bridging)
Your message dated Mon, 28 Dec 2009 20:47:06 + with message-id 1262033226.672342.2482.nullmai...@kmos.homeip.net and subject line Package kvm has been removed from Debian has caused the Debian Bug report #551620, regarding DOS on the LAN when starting kvm with 2 network devices and bridging 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.) -- 551620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kvm Version: 85+dfsg-4 Severity: critical Hi, I'm starting kvm with 2 network interfaces like this: sudo kvm -m 256 -drive file=/scratch/ramdisk/build/build/hda.img,if=ide,boot=on -drive file=/scratch/ramdisk/build/build/hdb.img,if=ide,boot=off -net nic,model=e1000,macaddr=54:52:00:00:42:12 -net tap -net nic,model=e1000,macaddr=54:52:00:00:42:13 -net tap -smp 1 -kernel /scratch/ramdisk/build/build/chroot-amd64/boot/vmlinuz-2.6.27.34-1-ql-beowulf -append root=/dev/ram0 rw ramdisk_size=97872 console=ttyS0,115200 quiet --initrd /scratch/ramdisk/build/build/image-beobox-amd64-7.0.0-0.gz -nographic and the /etc/kvm/kvm-ifup script adds both devices to a bridge: -- cat /etc/kvm/kvm-ifup #!/bin/sh # NOTE: For this script to operate properly, it is expected that # you have a br0 BRIDGE=br0 /sbin/ifconfig $1 0.0.0.0 up /usr/sbin/brctl addif $BRIDGE $1 -- The strange thing now is that somehow creates a network loop causing a DOS attack on the local network within seconds. In tcpdump I saw a DHCP Reply to 255.255.255.255 over and over and over again but I guess any broadcast will do. This causes 90% package loss making the local network completly unusable. Michael Tokarev (mjt on #debian-devel) could reproduce the problem. MfG Goswin ---End Message--- ---BeginMessage--- Version: 85+dfsg-4.1+rm You filled the bug http://bugs.debian.org/551620 in Debian BTS against the package kvm. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/562620. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Marco Rodrigues ---End Message---
Bug#553558: marked as done (w3c-linkchecker: dir-or-file-in-var-www /var/www/w3c-linkchecker)
Your message dated Mon, 28 Dec 2009 20:42:21 +
with message-id 1262032941.474098.2288.nullmai...@kmos.homeip.net
and subject line Package w3c-linkchecker has been removed from Debian
has caused the Debian Bug report #553558,
regarding w3c-linkchecker: dir-or-file-in-var-www /var/www/w3c-linkchecker
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.)
--
553558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: w3c-linkchecker
Version: 4.3-1
Severity: serious
User: lintian-ma...@debian.org
Usertags: dir-or-file-in-var-www
Debian packages should not install files under /var/www. This is not
one of the /var directories in the File Hierarchy Standard and is
under the control of the local administrator. Packages should not
assume that it is the document root for a web server; it is very
common for users to change the default document root and packages
should not assume that users will keep any particular setting.
Packages that want to make files available via an installed web server
should instead put instructions for the local administrator in a
README.Debian file and ideally include configuration fragments for
common web servers such as Apache.
As an exception, packages are permitted to create the /var/www
directory due to its past history as the default document root, but
should at most copy over a default file in postinst for a new install.
Refer to Filesystem Hierarchy Standard (The /var Hierarchy) for
details.
One solution that works is to put configuration files into
/etc/package_name, put static content, if any, into
/usr/{share,lib}/package_name, then create /var/lib/package name
as home for the package, and symlink the files from /etc and /usr/
into the /var/lib/package_name. Then create a simple set of
configuration snippets for popular web servers (for example, files one
may link into /etc/apache2/conf.d) and put them into
/etc/package_name. This way user modifiable files stil live in /etc,
and a simple operation can make the package go live.
Filed as serious, since this is a violation of the FHS (which is part
of policy), and also since a package with these files will currently
get this package rejected. See
http://lists.debian.org/debian-devel-announce/2009/10/msg4.html
for details. This means the package has been deemed too buggy to be in
Debian.
manoj
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages w3c-linkchecker depends on:
ii libconfig-general-perl 2.44-1 Generic Configuration Module
ii libhtml-parser-perl 3.62-1 collection of modules that parse H
ii libnet-ip-perl 1.25-2 Perl extension for manipulating IP
ii liburi-perl 1.37+dfsg-1 Manipulates and accesses URI strin
ii libwww-perl 5.833-1 Perl HTTP/WWW client/server librar
ii perl 5.10.1-6Larry Wall's Practical Extraction
w3c-linkchecker recommends no packages.
Versions of packages w3c-linkchecker suggests:
ii libterm-readkey-perl 2.30-4 A perl module for simple terminal
-- no debconf information
---End Message---
---BeginMessage---
Version: 4.3-1+rm
You filled the bug http://bugs.debian.org/553558 in Debian BTS
against the package w3c-linkchecker. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/553903. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
---End Message---
Bug#527371: marked as done (kvm: FTBFS when built twice in a row)
Your message dated Mon, 28 Dec 2009 20:47:08 + with message-id 1262033228.319427.2538.nullmai...@kmos.homeip.net and subject line Package kvm has been removed from Debian has caused the Debian Bug report #527371, regarding kvm: FTBFS when built twice in a row 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.) -- 527371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kvm Version: 84+dfsg-2 Severity: serious Justification: no longer builds from source Hi, kvm currently FTBFS when built twice in a row, because some BIOS images aren't removed properly on clean: dpkg-source: info: using source format `1.0' dpkg-source: info: building kvm using existing kvm_84+dfsg.orig.tar.gz dpkg-source: info: building kvm in kvm_84+dfsg-2.diff.gz dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/linux_boot.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/pxe-rtl8139.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/vgabios.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/pxe-ne2k_pci.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/extboot.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/bios.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/pxe-e1000.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/vgabios-cirrus.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/qemu/pc-bios/pxe-pcnet.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/extboot/extboot.img: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/extboot/extboot.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/extboot/signrom: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/extboot/extboot.o: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/vgabios/VGABIOS-lgpl-latest.debug.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/vgabios/VGABIOS-lgpl-latest.cirrus.debug.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/vgabios/VGABIOS-lgpl-latest.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/vgabios/VGABIOS-lgpl-latest.cirrus.bin: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/vgabios/vbetables-gen: binary file contents changed dpkg-source: error: cannot represent change to kvm-84+dfsg/vgabios/biossums: binary file contents changed dpkg-source: unrepresentable changes to source dpkg-buildpackage: failure: dpkg-source -b kvm-84+dfsg gave error exit status 1 Regards Evgeni Golov -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core) 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 kvm depends on: ii adduser3.110 add and remove users and groups pn bridge-utils none(no description available) ii iproute20090324-1networking and traffic control too ii libasound2 1.0.19-1 shared library for ALSA applicatio ii libc6 2.9-10GNU C Library: Shared libraries ii libgnutls262.6.6-1 the GNU TLS library - runtime libr ii libncurses55.7+20090502-1shared libraries for terminal hand ii libsdl1.2debian1.2.13-4+b1 Simple DirectMedia Layer ii python 2.5.4-2 An interactive high-level object-o ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime Versions of packages kvm recommends: ii linux-imag 2.6.28-x31-1-10.00.Custom Linux kernel binary image for vers ii linux-imag 2.6.29-3 Linux 2.6.29 image on PPro/Celeron ii linux-imag 2.6.29-rc6-x31-1-10.00.Custom Linux
Bug#534735: new version of this problem
I've reopened this bug. When I include the line: listen-address localhost::8118, privoxy starts without error, but doesn't actually listen - the port stays closed. When I turn debugging on, I see this in the log: Info: Listening on port 8118 on IP address localhost Without the line (the default config), the log has: Info: Listening on port 8118 on IP address 127.0.0.1 This works fine. The logs seem to indicate that localhost isn't being properly resolved, and worse still, the program isn't bothering to inform anyone of this. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531829: marked as done (kvm-source: m-a a-i --force kvm fails because it's looking for compiler.h in the wrong place)
Your message dated Mon, 28 Dec 2009 20:47:05 + with message-id 1262033225.385927.2438.nullmai...@kmos.homeip.net and subject line Package kvm has been removed from Debian has caused the Debian Bug report #531829, regarding kvm-source: m-a a-i --force kvm fails because it's looking for compiler.h in the wrong place 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.) -- 531829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kvm-source Version: 72+dfsg-5 Severity: grave Justification: renders package unusable Cannot build kvm-source. ie. make[3]: Entering directory `/usr/src/linux-headers-2.6.29-2-amd64' LD /usr/src/modules/kvm/built-in.o CC [M] /usr/src/modules/kvm/svm.o In file included from command-line:0: /usr/src/modules/kvm/external-module-compat.h:10:28: error: linux/compiler.h: No such file or directory /usr/src/modules/kvm/external-module-compat.h:12:26: error: linux/string.h: No such file or directory In file included from /usr/src/modules/kvm/external-module-compat.h:13, from command-line:0: Package linux-headers-2.6.29-2-common contains compiler.h but at /usr/src/linux-headers-2.6.29-2-common/include/linux/compiler.h . ie not in /usr/src/linux-headers-2.6.29-2-amd64 which is where m-a is looking. -- Package-specific info: selected information from lshal(1): /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz stepping: 6 cpu MHz : 1000.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow bogomips: 4322.60 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz stepping: 6 cpu MHz : 1000.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow bogomips: 4322.53 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-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/bash Versions of packages kvm-source depends on: ii bzip2 1.0.5-1high-quality block-sorting file co ii debhelper 7.2.14 helper programs for debian/rules ii make 3.81-5 The GNU version of the make util ii module-assistant 0.11.1 tool to make module package creati kvm-source recommends no packages. Versions of packages kvm-source suggests: ii kernel-package12.014 A utility for building Linux kerne ii linux-headers-2.6-amd64 [linu 2.6.29+19 Header files for Linux 2.6-amd64 ii linux-headers-2.6.29-2-amd64 2.6.29-5 Header files for Linux 2.6.29-2-am ii linux-source-2.6.29 [linux-so 2.6.29-5 Linux kernel source for version 2. -- no debconf information ---End Message--- ---BeginMessage--- Version: 85+dfsg-4.1+rm You filled the bug http://bugs.debian.org/531829 in Debian BTS against the package kvm. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/562620. That bug might give the reasons why this
Bug#554046: debugging the infinite suspend loop
Le lundi 28 décembre 2009 à 21:32 +0100, Norbert Preining a écrit : - suspending with lid-close goes into infinite loop - suspending with click-power-icon, select suspend *works* Is uswsusp installed? If so, does removing it help? -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Bug#561852: apt: Method http has died unexpectedly (undefined symbol:)
Downgrade to apt-0.7.23.1, apt-get update(not sure if it is needed) and upgrade again solves this problem for me. Before the downgrade the requested command looked like this: (installed apt was: apt_0.7.25_amd64.deb) # ldd /usr/lib/apt/methods/http linux-vdso.so.1 = (0x7fff779ff000) libapt-pkg-libc6.9-6.so.4.8 = /usr/lib/libapt-pkg-libc6.9-6.so.4.8 (0x7f22b2553000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x7f22b2243000) libm.so.6 = /lib/libm.so.6 (0x7f22b1fc) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x7f22b1daa000) libc.so.6 = /lib/libc.so.6 (0x7f22b1a56000) libutil.so.1 = /lib/libutil.so.1 (0x7f22b1852000) libdl.so.2 = /lib/libdl.so.2 (0x7f22b164e000) /lib64/ld-linux-x86-64.so.2 (0x7f22b283e000) # ls -l /usr/lib/libapt-pkg-libc6.9-6.so.4.8 lrwxrwxrwx 1 root root 29 27. Dez 22:04 /usr/lib/libapt-pkg-libc6.9-6.so.4.8 - libapt-pkg-libc6.9-6.so.4.8.1 now this is the output: (installed apt is: apt_0.7.25_amd64.deb) # ldd /usr/lib/apt/methods/http linux-vdso.so.1 = (0x7fff387ff000) libapt-pkg-libc6.9-6.so.4.8 = /usr/lib/libapt-pkg-libc6.9-6.so.4.8 (0x7fea2820) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x7fea27ef) libm.so.6 = /lib/libm.so.6 (0x7fea27c6d000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x7fea27a57000) libc.so.6 = /lib/libc.so.6 (0x7fea27703000) libutil.so.1 = /lib/libutil.so.1 (0x7fea274ff000) libdl.so.2 = /lib/libdl.so.2 (0x7fea272fb000) /lib64/ld-linux-x86-64.so.2 (0x7fea284ee000) # ls -l /usr/lib/libapt-pkg-libc6.9-6.so.4.8 lrwxrwxrwx 1 root root 29 28. Dez 21:58 /usr/lib/libapt-pkg-libc6.9-6.so.4.8 - libapt-pkg-libc6.9-6.so.4.8.0 signature.asc Description: This is a digitally signed message part.
Bug#554046: debugging the infinite suspend loop
On Mo, 28 Dez 2009, Josselin Mouette wrote:
- suspending with lid-close goes into infinite loop
- suspending with click-power-icon, select suspend *works*
Is uswsusp installed? If so, does removing it help?
Removing uswsusp did help indeed.
BTW, I was exploring also some other options and found attached
patch in the suse packages. It seems to deal with very similar
things as clearing duplicate suspend events. Since it is for
2.28.0 I am not sure if it is necessary, but you might take a look
at it. Before removing uswsusp I built a package of g-p-m with
that patch added to the quilt queue and it helped a bit (only one
rogue suspend) but OTOH added something strange, namely that switching
to the console and back initiated a suspend ... Anyway, the bug report is
https://bugzilla.novell.com/show_bug.cgi?id=540517
I have the same warnings
devkit-power-gobject-DEBUG: DBUS timed out, but recovering
So I am not sure how uswsusp is playing into that piece, but at least
once it worked.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
`Time is an illusion. Lunchtime doubly so.'
you should send that in to the
Reader's Digest. They've got a page for people like you.'
--- Ford convincing Arthur to drink three pints in ten
--- minutes at lunchtime.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
Index: gnome-power-manager-2.28.0/src/egg-console-kit.c
===
--- gnome-power-manager-2.28.0.orig/src/egg-console-kit.c
+++ gnome-power-manager-2.28.0/src/egg-console-kit.c
@@ -50,6 +50,9 @@ struct EggConsoleKitPrivate
DBusGProxy *proxy_manager;
DBusGProxy *proxy_session;
gchar *session_id;
+ guint emit_changed_id;
+ gboolean last_emitted_active;
+ gboolean last_changed_active;
};
enum {
@@ -231,13 +234,37 @@ out:
}
/**
+ * egg_console_kit_emit_active_changed_cb:
+ **/
+static gboolean
+egg_console_kit_emit_active_changed_cb (EggConsoleKit *console)
+{
+ egg_debug (emitting active: %i, console-priv-last_changed_active);
+ g_signal_emit (console, signals [EGG_CONSOLE_KIT_ACTIVE_CHANGED], 0, console-priv-last_changed_active);
+ console-priv-last_emitted_active = console-priv-last_changed_active;
+ console-priv-emit_changed_id = 0;
+ return FALSE;
+}
+
+/**
* egg_console_kit_active_changed_cb:
**/
static void
egg_console_kit_active_changed_cb (DBusGProxy *proxy, gboolean active, EggConsoleKit *console)
{
- egg_debug (emitting active: %i, active);
- g_signal_emit (console, signals [EGG_CONSOLE_KIT_ACTIVE_CHANGED], 0, active);
+ if (console-priv-emit_changed_id != 0) {
+ g_source_remove (console-priv-emit_changed_id);
+ console-priv-emit_changed_id = 0;
+ }
+
+ if (console-priv-last_emitted_active == active) {
+ egg_debug (ignoring active (same value as last emitted): %i, active);
+ return;
+ }
+
+ egg_debug (queuing active: %i, active);
+ console-priv-last_changed_active = active;
+ console-priv-emit_changed_id = g_idle_add ((GSourceFunc) egg_console_kit_emit_active_changed_cb, console);
}
/**
@@ -271,6 +298,8 @@ egg_console_kit_init (EggConsoleKit *con
console-priv = EGG_CONSOLE_KIT_GET_PRIVATE (console);
console-priv-proxy_manager = NULL;
console-priv-session_id = NULL;
+ console-priv-emit_changed_id = 0;
+ console-priv-last_changed_active = FALSE;
/* connect to D-Bus */
console-priv-connection = dbus_g_bus_get (DBUS_BUS_SYSTEM, error);
@@ -315,6 +344,8 @@ egg_console_kit_init (EggConsoleKit *con
dbus_g_proxy_connect_signal (console-priv-proxy_session, ActiveChanged,
G_CALLBACK (egg_console_kit_active_changed_cb), console, NULL);
+ console-priv-last_emitted_active = egg_console_kit_is_active (console);
+
out:
return;
}
@@ -338,6 +369,8 @@ egg_console_kit_finalize (GObject *objec
if (console-priv-proxy_session != NULL)
g_object_unref (console-priv-proxy_session);
g_free (console-priv-session_id);
+ if (console-priv-emit_changed_id != 0)
+ g_source_remove (console-priv-emit_changed_id);
G_OBJECT_CLASS (egg_console_kit_parent_class)-finalize (object);
}
Processed: reassign 562363 to libcommons-javaflow-java
Processing commands for cont...@bugs.debian.org: reassign 562363 libcommons-javaflow-java 0.0~svn20060411-3 Bug #562363 [src:jasperreports] jasperreports: FTBFS: java stuff Bug reassigned from package 'src:jasperreports' to 'libcommons-javaflow-java'. Bug No longer marked as found in versions jasperreports/3.7.0+dfsg-1. Bug #562363 [libcommons-javaflow-java] jasperreports: FTBFS: java stuff Bug Marked as found in versions commons-javaflow/0.0~svn20060411-3. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562363: marked as done (jasperreports: FTBFS: java stuff)
Your message dated Mon, 28 Dec 2009 22:04:16 + with message-id e1npnhi-0003gy...@ries.debian.org and subject line Bug#562363: fixed in commons-javaflow 0.0~svn20060411-4 has caused the Debian Bug report #562363, regarding jasperreports: FTBFS: java stuff 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.) -- 562363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jasperreports Version: 3.7.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091213 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-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg' make[1]: Nothing to be done for `update-config'. make[1]: Leaving directory `/build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg' 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/ant-trax.jar:/usr/share/java/bsh.jar:/usr/share/java/asm2.jar:/usr/share/java/groovy.jar:/usr/share/java/jcommon.jar:/usr/share/java/spring-core-2.5.jar:/usr/share/java/spring-beans-2.5.jar:/usr/share/java/commons-digester.jar:/usr/share/java/commons-collections3.jar:/usr/share/java/commons-logging.jar:/usr/share/java/commons-beanutils.jar:/usr/share/java/commons-codec.jar:/usr/share/java/eclipse-ecj.jar:/usr/share/java/xalan2.jar:/usr/share/java/jaxen.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/jxl.jar:/usr/share/java/jakarta-poi.jar:/usr/share/java/itext.jar:/usr/share/java/batik-all.jar:/usr/share/java/jfreechart.jar:/usr/share/java/hibernate3.jar:/usr/share/java/glassfish-javaee.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 jar docs Buildfile: build.xml compile: [mkdir] Created dir: /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/build/classes [javac] Compiling 1183 source files to /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/build/classes [javac] /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/src/net/sf/jasperreports/crosstabs/design/JRDesignCrosstab.java:67: warning: [deprecation] org.apache.commons.collections.SequencedHashMap in org.apache.commons.collections has been deprecated [javac] import org.apache.commons.collections.SequencedHashMap; [javac] ^ [javac] /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/src/net/sf/jasperreports/crosstabs/design/JRDesignCrosstab.java:107: warning: [deprecation] org.apache.commons.collections.SequencedHashMap in org.apache.commons.collections has been deprecated [javac] protected SequencedHashMap variablesList; [javac] ^ [javac] /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/src/net/sf/jasperreports/engine/fill/JRFillObjectFactory.java:136: warning: [deprecation] org.apache.commons.collections.SequencedHashMap in org.apache.commons.collections has been deprecated [javac] import org.apache.commons.collections.SequencedHashMap; [javac] ^ [javac] /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/src/net/sf/jasperreports/engine/fill/JRVirtualizationContext.java:30: warning: [deprecation] org.apache.commons.collections.ReferenceMap in org.apache.commons.collections has been deprecated [javac] import org.apache.commons.collections.ReferenceMap; [javac] ^ [javac] /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/src/net/sf/jasperreports/engine/fill/JRFillCellContents.java:47: warning: [deprecation] org.apache.commons.collections.ReferenceMap in org.apache.commons.collections has been deprecated [javac] import org.apache.commons.collections.ReferenceMap; [javac] ^ [javac] /build/user-jasperreports_3.7.0+dfsg-1-amd64-ogJj9g/jasperreports-3.7.0+dfsg/src/net/sf/jasperreports/engine/util/JRSingletonCache.java:30: warning: [deprecation] org.apache.commons.collections.ReferenceMap in org.apache.commons.collections has been deprecated [javac] import
Bug#540681: marked as done (beast: FTBFS: invalid conversion from 'void* volatile*' to 'volatile void**')
Your message dated Mon, 28 Dec 2009 22:47:11 + with message-id e1npomp-0006ge...@ries.debian.org and subject line Bug#540681: fixed in beast 0.7.1-5.2 has caused the Debian Bug report #540681, regarding beast: FTBFS: invalid conversion from 'void* volatile*' to 'volatile void**' 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.) -- 540681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: beast Version: 0.7.1-5.1 Severity: serious Hi, There was an error while trying to autobuild your package: Start Time: 20090809-1549 [...] Build-Depends: debhelper (= 4.0), quilt, libgtk2.0-dev (= 2.2.2-2), libglib2.0-dev (= 2.2.2-1), libaudiofile-dev, libvorbis-dev, guile-1.6-dev (= 1.6.4-2.1), libart-2.0-dev, libgnomecanvas2-dev, libmad0-dev, libxml-parser-perl, libxml2-utils, imagemagick, gettext, shared-mime-info [...] Toolchain package versions: libc6.1-dev_2.9-23 linux-libc-dev_2.6.30-5 g++-4.3_4.3.4-1+b1 gcc-4.3_4.3.4-1+b1 binutils_2.19.51.20090805-1 libstdc++6_4.4.1-1 libstdc++6-4.3-dev_4.3.4-1+b1 [...] if /bin/bash ../libtool --tag=CXX --mode=compile g++ -DBIRNET_LOG_DOMAIN=\BIRNET\ -I. -I. -I.. -I.. -I.. -I. -I. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_BIRNET_SOURCE_EXTENSIONS -Wall -g -O3 -g -DG_ENABLE_DEBUG -Wdeprecated -Wno-cast-qual -pipe -ftracer -finline-functions -fno-keep-static-consts -MT birnetthreadimpl.lo -MD -MP -MF .deps/birnetthreadimpl.Tpo -c -o birnetthreadimpl.lo birnetthreadimpl.cc; \ then mv -f .deps/birnetthreadimpl.Tpo .deps/birnetthreadimpl.Plo; else rm -f .deps/birnetthreadimpl.Tpo; exit 1; fi mkdir .libs g++ -DBIRNET_LOG_DOMAIN=\BIRNET\ -I. -I. -I.. -I.. -I.. -I. -I. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_BIRNET_SOURCE_EXTENSIONS -Wall -g -O3 -g -DG_ENABLE_DEBUG -Wdeprecated -Wno-cast-qual -pipe -ftracer -finline-functions -fno-keep-static-consts -MT birnetthreadimpl.lo -MD -MP -MF .deps/birnetthreadimpl.Tpo -c birnetthreadimpl.cc -fPIC -DPIC -o .libs/birnetthreadimpl.o birnetthreadimpl.cc: In function 'void* Birnet::g_atomic_pointer_get(volatile void**)': birnetthreadimpl.cc:1496: error: invalid conversion from 'void* volatile*' to 'volatile void**' birnetthreadimpl.cc:1496: error: initializing argument 1 of 'void* Birnet::g_atomic_pointer_get(volatile void**)' make[4]: *** [birnetthreadimpl.lo] Error 1 make[4]: Leaving directory `/build/buildd-beast_0.7.1-5.1-alpha-cEHiFH/beast-0.7.1/birnet' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd-beast_0.7.1-5.1-alpha-cEHiFH/beast-0.7.1/birnet' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd-beast_0.7.1-5.1-alpha-cEHiFH/beast-0.7.1' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-beast_0.7.1-5.1-alpha-cEHiFH/beast-0.7.1' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=alphapkg=beastver=0.7.1-5.1+b1 Kurt ---End Message--- ---BeginMessage--- Source: beast Source-Version: 0.7.1-5.2 We believe that the bug you reported is fixed in the latest version of beast, which is due to be installed in the Debian FTP archive: beast_0.7.1-5.2.diff.gz to main/b/beast/beast_0.7.1-5.2.diff.gz beast_0.7.1-5.2.dsc to main/b/beast/beast_0.7.1-5.2.dsc beast_0.7.1-5.2_amd64.deb to main/b/beast/beast_0.7.1-5.2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 540...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Zacchiroli z...@debian.org (supplier of updated beast 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, 26 Dec 2009 21:33:36 +0100 Source: beast Binary: beast Architecture: source amd64 Version: 0.7.1-5.2 Distribution: unstable Urgency: low Maintainer: Sam Hocevar (Debian packages) sam+...@zoy.org Changed-By: Stefano Zacchiroli z...@debian.org Description: beast - music synthesis and composition framework Closes: 540681 560499 Changes: beast (0.7.1-5.2) unstable;
Bug#560499: marked as done (beast: FTBFS: birnetmsg.cc:386: error: 'stdout' was not declared in this scope)
Your message dated Mon, 28 Dec 2009 22:47:11 + with message-id e1npomp-0006gh...@ries.debian.org and subject line Bug#560499: fixed in beast 0.7.1-5.2 has caused the Debian Bug report #560499, regarding beast: FTBFS: birnetmsg.cc:386: error: 'stdout' 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.) -- 560499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: beast Version: 0.7.1-5.1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -DBIRNET_LOG_DOMAIN=\BIRNET\ -I. -I. -I.. -I.. -I.. -I. -I. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_BIRNET_SOURCE_EXTENSIONS -Wall -g -O3 -g -DG_ENABLE_DEBUG -Wdeprecated -Wno-cast-qual -pipe -ftracer -finline-functions -fno-keep-static-consts -MT birnetmsg.lo -MD -MP -MF .deps/birnetmsg.Tpo -c birnetmsg.cc -fPIC -DPIC -o .libs/birnetmsg.o birnetmsg.cc: In static member function 'static void Birnet::Msg::configure_stdlog(bool, const Birnet::String, uint)': birnetmsg.cc:386: error: 'stdout' was not declared in this scope birnetmsg.cc:386: error: 'stderr' was not declared in this scope birnetmsg.cc:387: error: 'fclose' was not declared in this scope birnetmsg.cc:390: error: 'stdout' was not declared in this scope birnetmsg.cc:392: error: 'fopen' was not declared in this scope birnetmsg.cc: In static member function 'static void Birnet::Msg::display_parts(const char*, Birnet::Msg::Type, const std::vectorBirnet::Msg::Part, std::allocatorBirnet::Msg::Part )': birnetmsg.cc:484: error: 'stderr' was not declared in this scope birnetmsg.cc:484: error: 'fprintf' was not declared in this scope birnetmsg.cc:486: error: 'stderr' was not declared in this scope birnetmsg.cc:486: error: 'fprintf' was not declared in this scope birnetmsg.cc:488: error: 'stderr' was not declared in this scope birnetmsg.cc:488: error: 'fprintf' was not declared in this scope birnetmsg.cc:490: error: 'stderr' was not declared in this scope birnetmsg.cc:490: error: 'fprintf' was not declared in this scope birnetmsg.cc:492: error: 'stderr' was not declared in this scope birnetmsg.cc:492: error: 'fprintf' was not declared in this scope birnetmsg.cc:516: error: 'fprintf' was not declared in this scope birnetmsg.cc:518: error: 'fprintf' was not declared in this scope birnetmsg.cc:520: error: 'fprintf' was not declared in this scope birnetmsg.cc:522: error: 'fprintf' was not declared in this scope make[4]: *** [birnetmsg.lo] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/beast_0.7.1-5.1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: beast Source-Version: 0.7.1-5.2 We believe that the bug you reported is fixed in the latest version of beast, which is due to be installed in the Debian FTP archive: beast_0.7.1-5.2.diff.gz to main/b/beast/beast_0.7.1-5.2.diff.gz beast_0.7.1-5.2.dsc to main/b/beast/beast_0.7.1-5.2.dsc beast_0.7.1-5.2_amd64.deb to main/b/beast/beast_0.7.1-5.2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 560...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Zacchiroli z...@debian.org (supplier of updated beast 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, 26 Dec 2009 21:33:36 +0100 Source: beast Binary: beast Architecture: source amd64 Version: 0.7.1-5.2 Distribution: unstable Urgency: low Maintainer: Sam Hocevar (Debian packages) sam+...@zoy.org Changed-By: Stefano
Bug#557000: marked as done (distribute: FTBFS without Python 2.4)
Your message dated Mon, 28 Dec 2009 23:02:10 + with message-id e1npobk-0008ia...@ries.debian.org and subject line Bug#557000: fixed in distribute 0.6.10-1 has caused the Debian Bug report #557000, regarding distribute: FTBFS without Python 2.4 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.) -- 557000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: distribute Version: 0.6.8-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python2.6 ftbfs Hello, Your package hardcodes Python versions it uses at build time, despite build-depending on python-all-dev (rather than particular python2.X-dev packages). That means that the package will FTBFS once python2.4 is dropped from the set of supported Python versions. Please fix your package to use all the supported Python versions instead. Also, please consider switching from python-central to python-support: http://wiki.debian.org/DebianPython/central2support -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: distribute Source-Version: 0.6.10-1 We believe that the bug you reported is fixed in the latest version of distribute, which is due to be installed in the Debian FTP archive: distribute_0.6.10-1.diff.gz to main/d/distribute/distribute_0.6.10-1.diff.gz distribute_0.6.10-1.dsc to main/d/distribute/distribute_0.6.10-1.dsc distribute_0.6.10.orig.tar.gz to main/d/distribute/distribute_0.6.10.orig.tar.gz python-distribute-doc_0.6.10-1_all.deb to main/d/distribute/python-distribute-doc_0.6.10-1_all.deb python-pkg-resources_0.6.10-1_all.deb to main/d/distribute/python-pkg-resources_0.6.10-1_all.deb python-setuptools_0.6.10-1_all.deb to main/d/distribute/python-setuptools_0.6.10-1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 557...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated distribute 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, 28 Dec 2009 23:52:40 +0100 Source: distribute Binary: python-pkg-resources python-setuptools python-distribute-doc Architecture: source all Version: 0.6.10-1 Distribution: unstable Urgency: low Maintainer: Matthias Klose d...@debian.org Changed-By: Matthias Klose d...@debian.org Description: python-distribute-doc - Python Distutils Enhancements (based on distribute), documentatio python-pkg-resources - Package Discovery and Resource Access using pkg_resources python-setuptools - Python Distutils Enhancements (setuptools compatibility) Closes: 557000 Changes: distribute (0.6.10-1) unstable; urgency=low . * New upstream version. * Stop building for python2.4. Closes: #557000. Checksums-Sha1: 01b4dc7f88647a4e4d0cdfeaf61a20ae8d2f16da 1185 distribute_0.6.10-1.dsc 60b29c6ffbd9ce5f4cbaebba809a8316cf198462 385641 distribute_0.6.10.orig.tar.gz b9da30c67c69f64a2de6fb15aeccc28ad118be96 12784 distribute_0.6.10-1.diff.gz 30734ed242624454a074033627630185b68fadac 64794 python-pkg-resources_0.6.10-1_all.deb 8458da16a2fcad93fafe7ef9a7b972b5fc2ee1d6 217382 python-setuptools_0.6.10-1_all.deb 3b271cb779a0aa4a96ce53163edc1d9f1d3cd620 274534 python-distribute-doc_0.6.10-1_all.deb Checksums-Sha256: 69279654b7de6daf33144dbafd9ccd220077f40b1c814b9231f179d72b7a6845 1185 distribute_0.6.10-1.dsc 3046d9d6d4acedf5a7e2aa73f6370a0f9bf1556faad2904523f16c0945847630 385641 distribute_0.6.10.orig.tar.gz 2011403e3414ab142a38606d0ebe341ef522f796f44925c7c939c546c8470de5 12784 distribute_0.6.10-1.diff.gz 5d092effadb8c97c04b10fe81410a0560cdc3fc624b7938a53aaa071027def68 64794 python-pkg-resources_0.6.10-1_all.deb 147a4c7fad43521920bbf852bbe246ec8232f09a7a1b8ce3e9e584e6c290d58a 217382 python-setuptools_0.6.10-1_all.deb c4518b146863b4459d1e304c8054c84206641bcb9392c2fda970c34f5a8de8a7 274534 python-distribute-doc_0.6.10-1_all.deb Files: 250e5053144abda86c5dedab4ba44805 1185 python optional distribute_0.6.10-1.dsc 99fb4b3e4ef0861bba11aa1905e89fed 385641 python optional distribute_0.6.10.orig.tar.gz 7c5d86dfef2f7e1b19ccd42197f098d6 12784 python optional distribute_0.6.10-1.diff.gz 349cce95c96855d7e14f64b97fc077dc
Bug#560675: marked as done (gpe-contacts: FTBFS: Nonexistent build-dependency: libmimedir-gnome0-dev)
Your message dated Mon, 28 Dec 2009 23:02:41 + with message-id e1npobp-0008r4...@ries.debian.org and subject line Bug#560675: fixed in gpe-contacts 0.49-2 has caused the Debian Bug report #560675, regarding gpe-contacts: FTBFS: Nonexistent build-dependency: libmimedir-gnome0-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.) -- 560675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gpe-contacts Version: 0.49-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ** Using build dependencies supplied by package: Build-Depends: cdbs (= 0.4.5.1), debhelper ( 4.0.0), libgpewidget-dev (= 0.114), libgtk2.0-dev, libxml2-dev, libsqlite0-dev, libdbus-glib-1-dev, libdisplaymigration0-dev (= 0.28), intltool, libgpepimc-dev (= 0.8-4), libgpevtype-dev (= 0.17-5), libmimedir-gnome0-dev, libcontactsdb-dev ┌──┐ │ Install build dependencies │ └──┘ Checking for already installed source dependencies... W: Unable to locate package libmimedir-gnome0-dev cdbs: missing Using default version 0.4.62+nmu1 debhelper: missing Using default version 7.4.10 libgpewidget-dev: missing Using default version 0.117-1 libgtk2.0-dev: missing libxml2-dev: missing libsqlite0-dev: missing libdbus-glib-1-dev: missing libdisplaymigration0-dev: missing Using default version 0.28-7 intltool: missing libgpepimc-dev: missing Using default version 0.9-2 libgpevtype-dev: missing Using default version 0.50-4 libmimedir-gnome0-dev: missing libcontactsdb-dev: missing Checking for source dependency conflicts... E: Couldn't find package libmimedir-gnome0-dev The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/gpe-contacts_0.49-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: gpe-contacts Source-Version: 0.49-2 We believe that the bug you reported is fixed in the latest version of gpe-contacts, which is due to be installed in the Debian FTP archive: gpe-contacts_0.49-2.debian.tar.gz to main/g/gpe-contacts/gpe-contacts_0.49-2.debian.tar.gz gpe-contacts_0.49-2.dsc to main/g/gpe-contacts/gpe-contacts_0.49-2.dsc gpe-contacts_0.49-2_amd64.deb to main/g/gpe-contacts/gpe-contacts_0.49-2_amd64.deb gpe-contacts_0.49.orig.tar.bz2 to main/g/gpe-contacts/gpe-contacts_0.49.orig.tar.bz2 A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 560...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Neil Williams codeh...@debian.org (supplier of updated gpe-contacts 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, 28 Dec 2009 20:46:35 + Source: gpe-contacts Binary: gpe-contacts Architecture: source amd64 Version: 0.49-2 Distribution: unstable Urgency: low Maintainer: Moray Allan mo...@debian.org Changed-By: Neil Williams codeh...@debian.org Description: gpe-contacts - contact manager for GPE Closes: 560675 Changes: gpe-contacts (0.49-2) unstable; urgency=low . * Use pkg-gpe svn * Move the manpage into debian/ * Add licence version to copyright statement. (lintian) * Migrate to dpkg source format 3.0 for upstream .tar.bz2 support. * Fix desktop validity tests using new patches. (lintian) * Move from deprecated debhelper4 compat support. * Remove duplicate well-known-tags file. * Switch to libmimedir-gnome-dev
Bug#562901: couchdb: wrong use of killall in preinst without pre-depends
Package: couchdb Version: 0.10.0-1 Severity: serious Tags: patch Justification: Policy 3.5 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu lucid ubuntu-patch The current version of couchdb calls killall in the preinst, with the following rationale: * Created debian/preinst, now we make sure that couchdb isn't running any beam processes on upgrade. Upgrading from 0.9.0-2 was leaving old code in a running beam process, so you were running 0.9.0 couchdb but had 0.10.0 code installed until you killed the process. Adds a dependency on psmisc. This is broken, because: - You did not add psmisc as a pre-depends of the package as required, you added it as a build-depends. This is a violation of Policy 3.5. - You have not discussed this on debian-devel prior to adding the (logical) pre-dependency. This is also a violation of a Policy 3.5 should requirement. - Your killall command is helplessly incorrect. Processes running as the couchdb user should be managed by the init script, and it should be regarded as a bug in the init script if they aren't being stopped on upgrade. Processes running as users *other* than the couchdb user are not affected by the killall command (and should not be), so whatever problem this preinst was meant to work around is still going to affect those users. I recommend dropping this change entirely, as in the following patch, and if necessary improving the init script to correctly manage these processes. === modified file 'debian/control' --- debian/control 2009-11-21 17:10:39 + +++ debian/control 2009-12-28 22:08:47 + @@ -6,7 +6,7 @@ Standards-Version: 3.8.3 Build-Depends: cdbs (= 0.4.42), debhelper (= 7.2.11), erlang-dev (= 1:13.b.1-dfsg-3), help2man, libcurl4-openssl-dev, - libicu-dev, libmozjs-dev, libreadline-dev, psmisc + libicu-dev, libmozjs-dev, libreadline-dev Homepage: http://couchdb.apache.org/ Vcs-Svn: svn+ssh://svn.debian.org/svn/pkg-erlang/couchdb Vcs-Browser: http://svn.debian.org/viewsvn/pkg-erlang/couchdb === removed file 'debian/preinst' --- debian/preinst 2009-11-21 17:10:39 + +++ debian/preinst 1970-01-01 00:00:00 + @@ -1,29 +0,0 @@ -#!/bin/sh -e -# by Sam Bisbee sbis...@computervip.com Copyright 2009 -# The right to copy, distribute, and modify this file in any medium is released -# to anyone without royalty, provided that this notice and the copyright notice -# is preserved. - -case $1 in - install) -;; - - upgrade) -#Prevent old couchdb code from running in a couchdb process and surviving -#through to our new version. Assumes that it's running as the default -#couchdb user. -killall -q -u couchdb beam /dev/null || true -;; - - abort-upgrade) -;; - - *) -echo preinst called with unknown argument $1 2 -exit 1 -;; -esac - -#DEBHELPER# - -exit 0 Cheers, -- 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525887: marked as done (cpad inhibits to compile)
Your message dated Tue, 29 Dec 2009 00:13:41 +0100 with message-id 4b393ba5.2040...@debian.org and subject line Re: Bug#525887: Bug can be closed has caused the Debian Bug report #525887, regarding cpad inhibits to compile 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.) -- 525887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cpad-kernel-source Severity: serious Justification: no longer builds from source -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: x86_64 Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Hello dear maintainers, I tried to compile cpad-kernel-source, but it fails to compile. It is the same, using m-a a-i cpad-kernel-source or debian/rules binary_modules ( the second does not work at all). Please feel free to ask for more information, but first of all, I have to apologize, when my answer will be late ( I am in the hospital for the next 2 or 3 weeks) since tomorrow. Regards Hans-J. Ullrich ---End Message--- ---BeginMessage--- Hans-J. Ullrich wrote: Dear maintainers, due to a new kernel, this bugreport can safely be closed. Thank you for the work! Ok, closing this bug. Cheers Luk ---End Message---
Processed: severity of 545235 is serious
Processing commands for cont...@bugs.debian.org: #now that gcc4.4 is in unstable it fails to build from source there (confirmed in clean chroot / cowbuilder) severity 545235 serious Bug #545235 [k3d] k3d needs source changes to build with gcc 4.4 Severity set to 'serious' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562575: Bug still present [Re: Bug#562575: installation-reports: Buisnesscard PowerPC installer loops with Segmentation faults]
This bug (562575) is still present in today's netinst CD. The businesscard installer boots and prints the ususal flock of kernel startup messages. then it says: Starting system log daemon Segmentation fault and then it loops saying INFO: kbd-mode: setting console mode to Unicode (UTF-8) Segmentation fault It never gets to the point of asking the usual installation questions for locale, language, etc... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561915: qbittorrent crash
OK, here is the result. :) (gdb) thread apply all bt Thread 5 (Thread 0x7fffe9113910 (LWP 5049)): #0 0x756a7f82 in select () from /lib/libc.so.6 #1 0x7620fd36 in ?? () from /usr/lib/libQtCore.so.4 #2 0x7614b4a5 in ?? () from /usr/lib/libQtCore.so.4 #3 0x776a273a in start_thread () from /lib/libpthread.so.0 #4 0x756ae69d in clone () from /lib/libc.so.6 #5 0x in ?? () Thread 4 (Thread 0x7fffe9fbe910 (LWP 5048)): #0 0x776a6f89 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x779ed723 in boost::asio::detail::task_io_serviceboost::asio::detail::epoll_reactorfalse ::run(boost::system::error_code) () from /usr/lib/libtorrent-rasterbar.so.5 #2 0x77ad7809 in boost::asio::detail::posix_thread::funcboost::asio::detail::resolver_serviceboost::asio::ip::udp::work_io_service_runner::run() () from /usr/lib/libtorrent-rasterbar.so.5 #3 0x779deb0f in asio_detail_posix_thread_function () from /usr/lib/libtorrent-rasterbar.so.5 #4 0x776a273a in start_thread () from /lib/libpthread.so.0 #5 0x756ae69d in clone () from /lib/libc.so.6 #6 0x in ?? () Thread 3 (Thread 0x7fffea7bf910 (LWP 5047)): #0 0x756aecd8 in epoll_wait () from /lib/libc.so.6 #1 0x779ebead in boost::asio::detail::epoll_reactorfalse::run (this=0xb697f0, block=value optimized out) at /usr/include/boost/asio/detail/epoll_reactor.hpp:470 #2 0x779ed6a6 in boost::asio::detail::task_io_serviceboost::asio::detail::epoll_reactorfalse ::run(boost::system::error_code) () from /usr/lib/libtorrent-rasterbar.so.5 #3 0x77a2fac1 in boost::asio::io_service::run (this=0xb676e0) at /usr/include/boost/asio/impl/io_service.ipp:65 ---Type return to continue, or q return to quit--- #4 libtorrent::aux::session_impl::operator() (this=0xb676e0) at session_impl.cpp:1651 #5 0x74fc3d80 in thread_proxy () from /usr/lib/libboost_thread.so.1.40.0 #6 0x776a273a in start_thread () from /lib/libpthread.so.0 #7 0x756ae69d in clone () from /lib/libc.so.6 #8 0x in ?? () Thread 2 (Thread 0x7fffeafc0910 (LWP 5046)): #0 0x776a990b in read () from /lib/libpthread.so.0 #1 0x77ade23d in libtorrent::file::read (this=value optimized out, buf=0x7fffdc3130d0 \211\222, incomplete sequence \357, num_bytes=524288, ec=...) at file.cpp:266 #2 0x77a47d89 in libtorrent::storage::read_impl (this=0xe800d0, buf=value optimized out, slot=value optimized out, offset=value optimized out, size=value optimized out, fill_zero=value optimized out) at storage.cpp:1053 #3 0x77a454ee in libtorrent::piece_manager::check_one_piece (this=0xe77b90, have_piece=value optimized out) at storage.cpp:2241 #4 0x77a470eb in libtorrent::piece_manager::check_files (this=0x1a, current_sl...@0x7fffeafbfda0, have_pie...@0x8, error=...) at storage.cpp:2130 #5 0x77b2f4ea in libtorrent::disk_io_thread::operator() (this=0xb678a8) at disk_io_thread.cpp:1154 #6 0x74fc3d80 in thread_proxy () from /usr/lib/libboost_thread.so.1.40.0 #7 0x776a273a in start_thread () from /lib/libpthread.so.0 #8 0x756ae69d in clone () from /lib/libc.so.6 #9 0x in ?? () Thread 1 (Thread 0x77fcf750 (LWP 5043)): #0 0x in ?? () #1 0x76bc53dc in ?? () from /usr/lib/libQtGui.so.4 #2 0x76bc613e in ?? () from /usr/lib/libQtGui.so.4 #3 0x76b7f547 in ?? () from /usr/lib/libQtGui.so.4 ---Type return to continue, or q return to quit--- #4 0x76ba62ca in ?? () from
Bug#562683: marked as done (FTBFS: make: *** [parser.cpp] Error 1)
Your message dated Tue, 29 Dec 2009 00:02:54 + with message-id e1nppy6-0005ay...@ries.debian.org and subject line Bug#562683: fixed in whitedune 0.28.14-1.1 has caused the Debian Bug report #562683, regarding FTBFS: make: *** [parser.cpp] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 562683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: whitedune Version: 0.28.14-1 Severity: grave --- Please enter the report below this line. --- Hi, whitedune doesn't start on my system. It always fails with segmentation fault. I've tried to provide you an useful back trace, but unfortunately it seems there is not a -gdb package for it. Sorry. Best Regards, Manolo. --- Back Trace. --- ~$ gdb whitedune GNU gdb (GDB) 6.8.50.20090628-cvs-debian Copyright (C) 2009 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/... (no debugging symbols found) (gdb) run Starting program: /usr/bin/whitedune [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0x00538871 in ?? () (gdb) bt #0 0x00538871 in ?? () #1 0x004cfd0b in ?? () #2 0x004d07ac in ?? () #3 0x0040870b in ?? () #4 0x754485c6 in __libc_start_main (main=0x4083d4 glverte...@plt+724, argc=1, ubp_av=0x7fffe5d8, init=0x548110 glverte...@plt+1310736, fini=value optimized out, rtld_fini=value optimized out, stack_end=0x7fffe5c8) at libc-start.c:222 #5 0x00408139 in ?? () #6 0x7fffe5c8 in ?? () #7 0x001c in ?? () #8 0x0001 in ?? () #9 0x7fffe826 in ?? () #10 0x in ?? () (gdb) --- System information. --- Architecture: amd64 Kernel: Linux 2.6.30 Debian Release: squeeze/sid 1001 testing ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed =-+-== lesstif2(= 1:0.94.4) | 1:0.95.0-2.3 libc6(= 2.3) | 2.9-25 libgcc1 (= 1:4.1.1) | 1:4.4.1-4 libgl1-mesa-glx | 7.5.1-1 OR libgl1| libglu1-mesa | 7.5.1-1 OR libglu1 | libjpeg62 | 6b-15 libpng12-0 (= 1.2.13-4) | 1.2.39-1 libstdc++6 (= 4.1.1) | 4.4.1-4 libx11-6 | 2:1.2.2-1 libxext6 | 2:1.0.4-1 libxi6| 2:1.2.1-2 libxmu6 | 2:1.0.4-2 libxp6| 1:1.0.0.xsf1-2 libxt6| 1:1.0.6-1 zlib1g (= 1:1.1.4) | 1:1.2.3.3.dfsg-15 Package's Recommends field is empty. Suggests(Version) | Installed =-+-=== whitedune-docs| ---End Message--- ---BeginMessage--- Source: whitedune Source-Version: 0.28.14-1.1 We believe that the bug you reported is fixed in the latest version of whitedune, which is due to be installed in the Debian FTP archive: whitedune-docs_0.28.14-1.1_all.deb to main/w/whitedune/whitedune-docs_0.28.14-1.1_all.deb whitedune_0.28.14-1.1.diff.gz to main/w/whitedune/whitedune_0.28.14-1.1.diff.gz whitedune_0.28.14-1.1.dsc to main/w/whitedune/whitedune_0.28.14-1.1.dsc whitedune_0.28.14-1.1_i386.deb to main/w/whitedune/whitedune_0.28.14-1.1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 562...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Retout t...@retout.co.uk (supplier of updated whitedune package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 Dec 2009 15:51:59 + Source: whitedune Binary: whitedune whitedune-docs Architecture: source all i386 Version:
Bug#550459: marked as done ([whitedune] Segmentation fault at start up)
Your message dated Tue, 29 Dec 2009 00:02:54 + with message-id e1nppy6-0005as...@ries.debian.org and subject line Bug#550459: fixed in whitedune 0.28.14-1.1 has caused the Debian Bug report #550459, regarding [whitedune] Segmentation fault at start up 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.) -- 550459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: whitedune Version: 0.28.14-1 Severity: grave --- Please enter the report below this line. --- Hi, whitedune doesn't start on my system. It always fails with segmentation fault. I've tried to provide you an useful back trace, but unfortunately it seems there is not a -gdb package for it. Sorry. Best Regards, Manolo. --- Back Trace. --- ~$ gdb whitedune GNU gdb (GDB) 6.8.50.20090628-cvs-debian Copyright (C) 2009 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/... (no debugging symbols found) (gdb) run Starting program: /usr/bin/whitedune [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0x00538871 in ?? () (gdb) bt #0 0x00538871 in ?? () #1 0x004cfd0b in ?? () #2 0x004d07ac in ?? () #3 0x0040870b in ?? () #4 0x754485c6 in __libc_start_main (main=0x4083d4 glverte...@plt+724, argc=1, ubp_av=0x7fffe5d8, init=0x548110 glverte...@plt+1310736, fini=value optimized out, rtld_fini=value optimized out, stack_end=0x7fffe5c8) at libc-start.c:222 #5 0x00408139 in ?? () #6 0x7fffe5c8 in ?? () #7 0x001c in ?? () #8 0x0001 in ?? () #9 0x7fffe826 in ?? () #10 0x in ?? () (gdb) --- System information. --- Architecture: amd64 Kernel: Linux 2.6.30 Debian Release: squeeze/sid 1001 testing ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed =-+-== lesstif2(= 1:0.94.4) | 1:0.95.0-2.3 libc6(= 2.3) | 2.9-25 libgcc1 (= 1:4.1.1) | 1:4.4.1-4 libgl1-mesa-glx | 7.5.1-1 OR libgl1| libglu1-mesa | 7.5.1-1 OR libglu1 | libjpeg62 | 6b-15 libpng12-0 (= 1.2.13-4) | 1.2.39-1 libstdc++6 (= 4.1.1) | 4.4.1-4 libx11-6 | 2:1.2.2-1 libxext6 | 2:1.0.4-1 libxi6| 2:1.2.1-2 libxmu6 | 2:1.0.4-2 libxp6| 1:1.0.0.xsf1-2 libxt6| 1:1.0.6-1 zlib1g (= 1:1.1.4) | 1:1.2.3.3.dfsg-15 Package's Recommends field is empty. Suggests(Version) | Installed =-+-=== whitedune-docs| ---End Message--- ---BeginMessage--- Source: whitedune Source-Version: 0.28.14-1.1 We believe that the bug you reported is fixed in the latest version of whitedune, which is due to be installed in the Debian FTP archive: whitedune-docs_0.28.14-1.1_all.deb to main/w/whitedune/whitedune-docs_0.28.14-1.1_all.deb whitedune_0.28.14-1.1.diff.gz to main/w/whitedune/whitedune_0.28.14-1.1.diff.gz whitedune_0.28.14-1.1.dsc to main/w/whitedune/whitedune_0.28.14-1.1.dsc whitedune_0.28.14-1.1_i386.deb to main/w/whitedune/whitedune_0.28.14-1.1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 550...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Retout t...@retout.co.uk (supplier of updated whitedune package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 Dec 2009 15:51:59 + Source: whitedune Binary: whitedune whitedune-docs Architecture: source all i386 Version:
Processed: bug 560631 is forwarded to http://code.google.com/p/mpmath/issues/detail?id=173
Processing commands for cont...@bugs.debian.org: forwarded 560631 http://code.google.com/p/mpmath/issues/detail?id=173 Bug #560631 [src:mpmath] mpmath: FTBFS: /usr/lib/pymodules/python2.5/py/impl/path/local.py:528: EnvironmentError Set Bug forwarded-to-address to 'http://code.google.com/p/mpmath/issues/detail?id=173'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562904: adonthell ftbfs on armel
package: adonthell version: 0.3.5-4 severity: serious x-debbugs-cc: debian-pyt...@lists.debian.org During the run up to the lenny release python 2.5 was made the default and this made adonthell FTBFS on arm(el) with Fatal Python error: exceptions bootstrapping error. (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486654 ). While doing flyby bugsquashing I took a look at this bug but failed to make any headway. I asked on debian-python but the only response I received was a suggestion to ask upstream. Since I was just doing flyby bugsquashing, had failed to produce a reduced testcase (since I really had no idea what was triggering the bug) and I don't know python I didn't make any contact with upstream (for either python or adonthell). Since a release was looming and noone had made no progress on finding a root cause (afaict none of the maintainers even responsed to the bugreport) I proposed a patch that special cased arm(el) and explicityly chose python2.4 on theese architectures. after some minor revisions this patch was uploaded by Philipp Kern as a NMU. Due to the planned removal of python2.4 Moritz Muehlenhoff reverted this special casing recently and the package now FTBFS again on armel but the soloution used last time is no longer possible. So as Moritz indicated in his changelog entry either the issue with newer python versions needs to be found and fixed (something I'm not capable of doing) or the armel adonthell package needs to be dropped. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539011: marked as done (pop3browser: please no longer Recommend: libmd5-perl)
Your message dated Tue, 29 Dec 2009 00:47:06 + with message-id e1npqes-0007xy...@ries.debian.org and subject line Bug#539011: fixed in pop3browser 0.4.1-1.1 has caused the Debian Bug report #539011, regarding pop3browser: please no longer Recommend: libmd5-perl 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.) -- 539011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pop3browser Version: 0.4.1-1 Severity: wishlist Hi, please no longer Recommend: libmd5-perl. The module is deprecated and has been replaced by Digest::MD5 years ago. Please note that Net::POP3 already supports using Digest::MD5 (libmd5-perl was required for the APOP command before, see #223057). Regards, Ansgar ---End Message--- ---BeginMessage--- Source: pop3browser Source-Version: 0.4.1-1.1 We believe that the bug you reported is fixed in the latest version of pop3browser, which is due to be installed in the Debian FTP archive: pop3browser_0.4.1-1.1.dsc to main/p/pop3browser/pop3browser_0.4.1-1.1.dsc pop3browser_0.4.1-1.1.tar.gz to main/p/pop3browser/pop3browser_0.4.1-1.1.tar.gz pop3browser_0.4.1-1.1_all.deb to main/p/pop3browser/pop3browser_0.4.1-1.1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 539...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tim Retout t...@retout.co.uk (supplier of updated pop3browser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Dec 2009 00:07:43 + Source: pop3browser Binary: pop3browser Architecture: source all Version: 0.4.1-1.1 Distribution: unstable Urgency: low Maintainer: Christoph Baumann c...@debian.org Changed-By: Tim Retout t...@retout.co.uk Description: pop3browser - Allows to check a pop3 mailbox before downloading any mail Closes: 539011 Changes: pop3browser (0.4.1-1.1) unstable; urgency=low . * Non-maintainer upload. * Remove libmd5-perl from Recommends. (Closes: #539011) Checksums-Sha1: 0ef388f76b6a23adb0a9c19a2605a3682e922e26 732 pop3browser_0.4.1-1.1.dsc ad055b6909ae4bc3bf60ef52269569430784305f 6340 pop3browser_0.4.1-1.1.tar.gz 935e324da819c8112f6c88443ef4b1939650d51b 7768 pop3browser_0.4.1-1.1_all.deb Checksums-Sha256: 640e22ec6c0b6fc467c6f9c5f6ac7555c78f2781b0214e9264b8d748351a47ea 732 pop3browser_0.4.1-1.1.dsc 2aebb4fe2a2eb3247af341aa7f09f9b85e890bd5aa33d4b8407153a0f4cf8f57 6340 pop3browser_0.4.1-1.1.tar.gz f94be70f2fb9b149b7c7e1fac7cb2decd8b4c51077a2044144b6853af0d8b94c 7768 pop3browser_0.4.1-1.1_all.deb Files: e50d4556c5ff1a6b7653b5a43aecbbc8 732 mail optional pop3browser_0.4.1-1.1.dsc 269032f7931f3aeb82931bfe0cd84c4b 6340 mail optional pop3browser_0.4.1-1.1.tar.gz 6116ee0ae40a4ea59e4069e7be5966ec 7768 mail optional pop3browser_0.4.1-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAks2qhoACgkQOHNNd4eQFFJxPwCfabrBvZQ7SRvYzRxb+6JsjXY4 wa8AnjLh6sP8LdA3Rx3NHS+lwXKrRmoE =XV6W -END PGP SIGNATURE- ---End Message---
Bug#544859: marked as done (fails to install, trying to overwrite other packages files)
Your message dated Tue, 29 Dec 2009 01:17:18 + with message-id e1npqi6-00022e...@ries.debian.org and subject line Bug#544567: fixed in rpcbind 0.2.0-2 has caused the Debian Bug report #544567, regarding fails to install, trying to overwrite other packages files 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.) -- 544567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: rpcbind Version: 0.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts piuparts.d.o Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Unpacking rpcbind (from .../rpcbind_0.2.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/rpcbind_0.2.0-1_amd64.deb (--unpack): trying to overwrite `/usr/bin/rpcinfo', which is also in package libc6 Errors were encountered while processing: /var/cache/apt/archives/rpcbind_0.2.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) regards, Holger Start: 2009-09-01 11:54:20 UTC Package: rpcbind Priority: extra Section: net Installed-Size: 96 Maintainer: Anibal Monsalve Salazar ani...@debian.org Architecture: amd64 Version: 0.2.0-1 Depends: libc6 (= 2.3), libtirpc1 Filename: pool/main/r/rpcbind/rpcbind_0.2.0-1_amd64.deb Size: 41396 MD5sum: c7bc99d7b21684ea3e6eae7a2ecfbc5b SHA1: b289706d6300ee8e4b748d4c7a98d3e20b4e61e7 SHA256: e7f650e6c00552d6451ecbc2f033729ad15a091a355282f20b03b05f3937c76f Description: converts RPC program numbers into universal addresses The rpcbind utility is a server that converts RPC program numbers into universal addresses. Homepage: http://sourceforge.net/projects/rpcbind/ Executing: sudo /org/piuparts.debian.org/sbin/piuparts --no-symlinks --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/ rpcbind Guessed: debian 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.36~20090820 starting up. 0m0.0s INFO: Command line arguments: /org/piuparts.debian.org/sbin/piuparts --no-symlinks --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/ rpcbind 0m0.0s INFO: Running on: Linux piatti 2.6.30.5-dsa-amd64 #1 SMP Mon Aug 17 02:18:43 CEST 2009 x86_64 0m0.0s DEBUG: Created temporary directory /org/piuparts.debian.org/tmp/tmptCvywb 0m0.0s DEBUG: Unpacking sid.tar.gz into /org/piuparts.debian.org/tmp/tmptCvywb 0m0.0s DEBUG: Starting command: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmptCvywb', '-zxf', 'sid.tar.gz'] 0m2.1s DEBUG: Command ok: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmptCvywb', '-zxf', 'sid.tar.gz'] 0m2.1s DEBUG: Created policy-rc.d and chmodded it. 0m2.1s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmptCvywb', 'apt-get', 'update'] 0m4.3s DUMP: Get:1 http://piatti.debian.org sid Release.gpg [835B] Get:2 http://piatti.debian.org sid Release [100kB] Ign http://piatti.debian.org sid/main Packages/DiffIndex Ign http://piatti.debian.org sid/contrib Packages/DiffIndex Ign http://piatti.debian.org sid/non-free Packages/DiffIndex Get:3 http://piatti.debian.org sid/main Packages [8005kB] Get:4 http://piatti.debian.org sid/contrib Packages [69.3kB] Get:5 http://piatti.debian.org sid/non-free Packages [131kB] Fetched 8306kB in 1s (6668kB/s) Reading package lists... 0m4.3s DEBUG: Command ok: ['chroot', '/org/piuparts.debian.org/tmp/tmptCvywb', 'apt-get', 'update'] 0m4.3s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmptCvywb', 'mount', '-t', 'proc', 'proc', '/proc'] 0m4.3s DEBUG: Command ok: ['chroot', '/org/piuparts.debian.org/tmp/tmptCvywb', 'mount', '-t', 'proc', 'proc', '/proc'] 0m4.3s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmptCvywb', 'apt-get', '-yf', 'upgrade'] 0m10.2s DUMP: Reading package lists... Building dependency tree... Reading state information... The following packages have been
Bug#544567: marked as done (rpcbind: tries to overwrite /usr/bin/rpcinfo from libc{-bin,N})
Your message dated Tue, 29 Dec 2009 01:17:18 +
with message-id e1npqi6-00022e...@ries.debian.org
and subject line Bug#544567: fixed in rpcbind 0.2.0-2
has caused the Debian Bug report #544567,
regarding rpcbind: tries to overwrite /usr/bin/rpcinfo from libc{-bin,N}
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.)
--
544567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: rpcbind
Version: 0.2.0-1
Severity: grave
Justification: renders package unusable (uninstallable)
| Unpacking rpcbind (from .../rpcbind_0.2.0-1_amd64.deb) ...
| dpkg: error processing /var/cache/apt/archives/rpcbind_0.2.0-1_amd64.deb
(--unpack):
| trying to overwrite `/usr/bin/rpcinfo', which is also in package libc-bin
[or in libc{6,6.1,0.1,0.3} prior to version 2.9-24; in either case,
the same goes for its man page]. As such, rpcbind is impossible to
install anywhere without --force-overwrite.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-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 rpcbind depends on:
ii libc6 2.9-26 GNU C Library: Shared libraries
ii libtirpc1 0.2.0-2transport-independent RPC library
rpcbind recommends no packages.
rpcbind suggests no packages.
---End Message---
---BeginMessage---
Source: rpcbind
Source-Version: 0.2.0-2
We believe that the bug you reported is fixed in the latest version of
rpcbind, which is due to be installed in the Debian FTP archive:
rpcbind_0.2.0-2.debian.tar.bz2
to main/r/rpcbind/rpcbind_0.2.0-2.debian.tar.bz2
rpcbind_0.2.0-2.dsc
to main/r/rpcbind/rpcbind_0.2.0-2.dsc
rpcbind_0.2.0-2_amd64.deb
to main/r/rpcbind/rpcbind_0.2.0-2_amd64.deb
rpcbind_0.2.0.orig.tar.bz2
to main/r/rpcbind/rpcbind_0.2.0.orig.tar.bz2
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 544...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anibal Monsalve Salazar ani...@debian.org (supplier of updated rpcbind
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 27 Dec 2009 21:39:02 +1100
Source: rpcbind
Binary: rpcbind
Architecture: source amd64
Version: 0.2.0-2
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar ani...@debian.org
Changed-By: Anibal Monsalve Salazar ani...@debian.org
Description:
rpcbind- converts RPC program numbers into universal addresses
Closes: 544567
Changes:
rpcbind (0.2.0-2) unstable; urgency=low
.
* Don't overwrite files from libc{-bin,N}
Rename rpcinfo to rpcbindinfo and rpcinfo.8 to rpcbindinfo.8
Patch by Ivan Shmakov
Closes: 544567
* Add debian/watch
* Debian source format is 3.0 (quilt)
Checksums-Sha1:
02f077372a76a8f9adfa696004aa437212c28617 271018 rpcbind_0.2.0.orig.tar.bz2
fc9c7af9a8e7220ba8aa4d9dbc31e01277c81590 1063 rpcbind_0.2.0-2.dsc
9baf26f4c040db5ec1d8a5bc97ec5fc923e4a108 3474 rpcbind_0.2.0-2.debian.tar.bz2
da84d0e11a3557d7290063f5cd41c2ac85c1bb86 41738 rpcbind_0.2.0-2_amd64.deb
Checksums-Sha256:
c92f263e0353887f16379d7708ef1fb4c7eedcf20448bc1e4838f59497a00de3 271018
rpcbind_0.2.0.orig.tar.bz2
5c1ea16f869f470696879afc97f5bf8f663dd628028c64e1ff9a71926b022cfe 1063
rpcbind_0.2.0-2.dsc
e54b59ee8beb52ee5767df83e5c07443f4fb929a4e4dea73a657bf294dfac2b0 3474
rpcbind_0.2.0-2.debian.tar.bz2
00342c7bcc76c9f66e95ac373594a8a4be41ebf8e2ea320d5970cb8ca855e765 41738
rpcbind_0.2.0-2_amd64.deb
Files:
1a77ddb1aaea8099ab19c351eeb26316 271018 net extra rpcbind_0.2.0.orig.tar.bz2
060c5330ffd5de1e649bacfb676adaf8 1063 net extra rpcbind_0.2.0-2.dsc
41b1931078f85291aa6bec0e552561ac 3474 net extra rpcbind_0.2.0-2.debian.tar.bz2
f3376f8415cefecb2be4978c37753e00 41738 net extra rpcbind_0.2.0-2_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAks5VhMACgkQgY5NIXPNpFXDiwCfW2hTPm6f46SZbus3uq23BrUR
9dAAnR0/S4A2AO1gamuY3cxh5PfCI/ap
=Fet5
-END PGP SIGNATURE-
---End Message---
Bug#562757: confirmed in my Sid system.
Hi, I can reproduce this nfs-common problem in my Sid system. Tried to install rpcbind, but it conflicts with libc-bin: dpkg: error processing /var/cache/apt/archives/rpcbind_0.2.0-1_i386.deb (--unpack): trying to overwrite '/usr/share/man/man8/rpcinfo.8.gz', which is also in package libc-bin 0:2.10.2-2 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/rpcbind_0.2.0-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Steven. -- Steven Shiau steven _at_ nchc org tw steven _at_ stevenshiau org National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562910: nfs-kernel-server: mountd fails to start
Package: nfs-kernel-server Version: 1:1.2.1-1 Severity: grave Justification: renders package unusable The mountd daemon fails to start: Starting NFS kernel daemon: nfsd mountd failed! Trying it manually: # /usr/sbin/rpc.mountd -F mountd: unable to register (mountd, 1, udp). Replacing the rpc.mountd executable with the 1:1.2.0-4 version fixes it. (This appears to be similar to bug 562757 -- statd in nfs-common.) Bill -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-kernel-server depends on: ii libblkid1 2.16.2-0 block device id library ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libcomerr21.41.9-1 common error description library ii libgssapi-krb5-2 1.7+dfsg-3 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4 mechanism-switch gssapi library ii libk5crypto3 1.7+dfsg-3 MIT Kerberos runtime libraries - C ii libkrb5-3 1.7+dfsg-3 MIT Kerberos runtime libraries ii libnfsidmap2 0.23-2 An nfs idmapping library ii libtirpc1 0.2.0-2transport-independent RPC library ii libwrap0 7.6.q-18 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii nfs-common1:1.2.1-1 NFS support files common to client ii ucf 3.0025 Update Configuration File: preserv nfs-kernel-server recommends no packages. nfs-kernel-server 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#547305: marked as done (FTBFS with gcc4.4)
Your message dated Tue, 29 Dec 2009 03:47:43 + with message-id e1npt3f-0006ce...@ries.debian.org and subject line Bug#547305: fixed in le 1.14.3-1 has caused the Debian Bug report #547305, regarding FTBFS with gcc4.4 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.) -- 547305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: le Version: 1.14.2-1 Hi! After recent archive rebuild in Ubuntu we discovered that le FTBFS because of new gcc4.4. Attached is a quilt patch to fix the issue :) In ubuntu we still use 1.14.0 but my patch also applied to the current version Regards, Stefan Index: le-1.14.2/src/options.cc === --- le-1.14.2.orig/src/options.cc 2009-09-18 14:34:04.781859434 +0200 +++ le-1.14.2/src/options.cc2009-09-18 14:34:32.765831035 +0200 @@ -1239,7 +1239,7 @@ FindColor(new_bw_pal,color_no)); return -1; } - char *l=strchr(button,''); + const char *l=strchr(button,''); if(!l) return -1; char res=toupper(l[1]); ---End Message--- ---BeginMessage--- Source: le Source-Version: 1.14.3-1 We believe that the bug you reported is fixed in the latest version of le, which is due to be installed in the Debian FTP archive: le_1.14.3-1.diff.gz to main/l/le/le_1.14.3-1.diff.gz le_1.14.3-1.dsc to main/l/le/le_1.14.3-1.dsc le_1.14.3-1_i386.deb to main/l/le/le_1.14.3-1_i386.deb le_1.14.3.orig.tar.gz to main/l/le/le_1.14.3.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 547...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphael Geissert geiss...@debian.org (supplier of updated le 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, 28 Dec 2009 18:20:08 -0600 Source: le Binary: le Architecture: source i386 Version: 1.14.3-1 Distribution: unstable Urgency: low Maintainer: Raphael Geissert geiss...@debian.org Changed-By: Raphael Geissert geiss...@debian.org Description: le - Text editor with block and binary operations Closes: 547305 Changes: le (1.14.3-1) unstable; urgency=low . * New upstream release - fixed compilation with gcc 4.4 (Closes: #547305) - added workaround for a ncurses getmouse bug * debian/patches/* removed, merged upstream. * debian/patches/extend-sql-syntax.patch: + More keywords used in MySQL and Oracle added. * debian/patches/fix-html-in-php-syntax-delimiter.patch: + Fix syntax highlighter delimiter in php mode. * debian/patches/debian-changelog-dist-allow-dash.patch: + Allow distribution names with dashes in Debian changelog mode. * debian/control: bumped Standards-Version, no change needed. Checksums-Sha1: f4b3c33094dfdb197cd4f3b61b36ab925914d0dc 1014 le_1.14.3-1.dsc d81408796105bb8473ab80de9867997feb3e5854 565501 le_1.14.3.orig.tar.gz 56a5976fd0c47ca6a4992cab9d655b8b92256572 7073 le_1.14.3-1.diff.gz c8dade659247976e3d4a57e58ac5b99137aa8137 163788 le_1.14.3-1_i386.deb Checksums-Sha256: 27f7a474301a98fd6fde1042830f378fe272eded6aedf2d6ad7e2495d74c2dc5 1014 le_1.14.3-1.dsc 528b96a30fa84959977f27f6f629591332f1b230d26c1d33a163fc39faf9c465 565501 le_1.14.3.orig.tar.gz f8c72180f9fc1ec609f3e2aaa65a61941024b583cd4fe36e28c45dccd05fbefd 7073 le_1.14.3-1.diff.gz 6afae0d450f4639f2d0056e10d96ea76dcde2e557bc6f04aec6bc4935359a8fc 163788 le_1.14.3-1_i386.deb Files: 3366e3d289a4e06d59121f35da42ba90 1014 editors optional le_1.14.3-1.dsc 29ad644b9d300f238f3754b003c33b50 565501 editors optional le_1.14.3.orig.tar.gz 83e6a9626e030e6696530a2e7a1fd1e5 7073 editors optional le_1.14.3-1.diff.gz 5af2b2b71dc82bed28744ba66076ffc6 163788 editors optional le_1.14.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAks5d34ACgkQYy49rUbZzlr0eACfc0z0eHFNxVeDgX6TrR+L9gNK ZgkAoIRYwHTzzHWFVyvNsrVG5sOyul55 =5I5F -END PGP SIGNATURE- ---End Message---
Bug#560641: marked as done (db4.7: FTBFS: Can't locate Debian/Debhelper/Dh_Lib.pm in @INC)
Your message dated Tue, 29 Dec 2009 03:47:24 + with message-id e1npt3m-0006yk...@ries.debian.org and subject line Bug#560641: fixed in db4.7 4.7.25-9 has caused the Debian Bug report #560641, regarding db4.7: FTBFS: Can't locate Debian/Debhelper/Dh_Lib.pm in @INC 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.) -- 560641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: db4.7 Version: 4.7.25-8 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091210 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-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/obj' Installing DB include files: /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/include ... Installing DB library: /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib ... cp -p .libs/libdb-4.7.so /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb-4.7.so cp -p .libs/libdb-4.7.lai /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb-4.7.la cp -p .libs/libdb_cxx-4.7.so /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx-4.7.so cp -p .libs/libdb_cxx-4.7.lai /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx-4.7.la cp -p .libs/libdb_java-4.7.so /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_java-4.7.so cp -p .libs/libdb_java-4.7.lai /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_java-4.7.la cp -p .libs/libdb_tcl-4.7.so /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_tcl-4.7.so cp -p .libs/libdb_tcl-4.7.lai /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_tcl-4.7.la cp -p .libs/libdb-4.7.a /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb-4.7.a chmod 644 /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb-4.7.a ranlib /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb-4.7.a cp -p libdb.a /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb.a chmod 644 /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb.a ranlib /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb.a cp -p .libs/libdb_cxx-4.7.a /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx-4.7.a chmod 644 /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx-4.7.a ranlib /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx-4.7.a cp -p libdb_cxx.a /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx.a chmod 644 /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx.a ranlib /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_cxx.a cp -p .libs/libdb_java-4.7.a /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_java-4.7.a chmod 644 /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_java-4.7.a ranlib /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_java-4.7.a cp -p .libs/libdb_tcl-4.7.a /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_tcl-4.7.a chmod 644 /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_tcl-4.7.a ranlib /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/lib/libdb_tcl-4.7.a libtool: install: warning: remember to run `libtool --finish /usr/lib' Installing DB utilities: /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/bin ... libtool: install: warning: `libdb-4.7.la' has not been installed in `/usr/lib' cp -p .libs/berkeley_db_svc /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/bin/berkeley_db_svc libtool: install: warning: `libdb-4.7.la' has not been installed in `/usr/lib' cp -p .libs/db_archive /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/bin/db_archive libtool: install: warning: `libdb-4.7.la' has not been installed in `/usr/lib' cp -p .libs/db_checkpoint /build/user-db4.7_4.7.25-8-amd64-c84S2D/db4.7-4.7.25/debian/tmp/usr/bin/db_checkpoint libtool: install: warning:
Bug#562884: xscreensaver can be killed with Alt+SysRq+F
Hi, * Lars Olav Dybsjord lar...@ping.uio.no [2009-12-28 21:23]: I'm a bit new to this bugreporting stuff. I have however discovered that it is possible to kill xscreensaver with Alt+SysRq+F (if this function is not disabled). This may comprimise security when xscreensaver-command is used with the -lock option, because the screen will be unlocked. gnome-screensaver seems not to be vulnerable to this attack. This is not really an xscreensaver bug though I realize how much this sucks in practice. The problem is the kernel oomkiller is killing the process with the highest rank which is very likely to be xscreensaver if the screen is locked. Unless I miss something (please note that I am not too much into X11) there is no way to prevent it unless switching of the sysrq feature or reforking died child processes. I am a bit unsure how to handle this, of course from a user perspective this needs to be solved. Cced the rest of the team to get some more input. Cheers Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 For security reasons, all text in this mail is double-rot13 encrypted. pgphQc8NLdiIV.pgp Description: PGP signature
