Bug#679968: in ipython shell -- inserts history substitution before the prompt line -- renders python-mode interactive use with ipython unusable
Am 05.07.2012 19:25, schrieb Yaroslav Halchenko: On Tue, 03 Jul 2012, Barry Warsaw wrote: We can easily link bugs in Launchpad to the related bug in Debian, but that's about it. N.B. Ideally, I am as a user report bugs in Debian using reportbug, and then the mighty Maintainer either fixes them himself or forwards upstream (i.e. LP). Who am I to steal the pleasure of maintainership duties away from him ? ;) and as you kindly pointed out -- it might not be a bug of python-mode.el?... +1 so, is it or is it not, Dear Maintainer? ;) If you think a bug results from python-mode.el, best is IMO reporting it at https://bugs.launchpad.net/python-mode also From there it's easy indeed linking it to the orignal ticket. Sure, may report it for you as done with lp:1020412 However, as it lists me as the reporter than, some info was lost. Usually the name of the reporter signales the kind of (open) bug for me already. It's faster than reading the larger title. ATM I simply can't use python-mode productively. Any interactive ipython shell becomes a pain Sorry about that. Being aware, something remains TBD with IPython-shell behavior. Patches welcome. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680470: Two security issues: AST-2012-010 / AST-2012-011
Package: asterisk Severity: grave Tags: security http://downloads.asterisk.org/pub/security/AST-2012-010.html (no CVE yet) http://downloads.asterisk.org/pub/security/AST-2012-011.html (CVE-2012-3812) 1.6 is not mentioned in the Affected versions, but I haven't validated whether because it's no longer supported/tracked upstream or because the issues are not present. Can you double-check? For sid/wheezy, please remember that we're in freeze and only isolated fixes are to be made instead of updating to a new full upstream release. Once you've uploaded, please send an unblock request by filing a bug against the release.debian.org pseudo package. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555168: Unclear license situation for (e)glibc locales provided by you
Hi, As it was suggested in the bugreport, most of those locales were copied from one common example and nobody could imagine that it would ever be necessary to license this data properly in the future... Anyway, I'm fine with re-licensing ru_UA under LGPLv2.1+ -- Denys On Wed, Jun 27, 2012 at 10:01:16AM +0200, Helge Kreutzmann wrote: Hello, you are listed as contact person/author of the following locale: ru_UA This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 this locale could strictly speaking not be part of Debian which would be a great loss. (Currently it is allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense this locale to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to zsnes, tagging 679826, tagging 680078, tagging 607311, tagging 679526
Processing commands for cont...@bugs.debian.org: #zsnes (1.510+bz2-4) unstable; urgency=low # # * Disable build on amd64 (Closes: #679526) #- Add Multi-Arch: Foreign # * debian/rules : #- use find -delete instead of command expansion #- use dpkg-buildflags #- add -Wl,--as-needed to LDFLAGS (Closes: #607311) # * Add patch to initialize the ao_sample_format structure #(thanks also to Goswin von Brederlow - Closes: #679826) # * Install high-res PNG icons provided with the sources (Closes: #680078) # limit source zsnes Limiting to bugs with field 'source' containing at least one of 'zsnes' Limit currently set to 'source':'zsnes' tags 679826 + pending Bug #679826 [zsnes] zsnes: segfaults on start in testing i386 Added tag(s) pending. tags 680078 + pending Bug #680078 [zsnes] zsnes: Please install high-res PNG icons provided with the sources Added tag(s) pending. tags 607311 + pending Bug #607311 [src:zsnes] zsnes: FTBFS on Ubuntu Added tag(s) pending. tags 679526 + pending Bug #679526 [zsnes] Build-Depends on obsolete package ia32-libs-dev Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 607311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607311 679526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679526 679826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679826 680078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672048: qwbfsmanager: diff for NMU version 1.2.1-1.1
tags 672048 + patch
tags 672048 + pending
tags 677930 + patch
tags 677930 + pending
thanks
Dear maintainer,
I've prepared an NMU for qwbfsmanager (versioned as 1.2.1-1.1) and
will upload it to DELAYED/2 as soon I am in reach of my key (which
will be tonight CEST). Please feel free to tell me if I should
delay it longer.
Regards.
Evgeni Golov
diff -Nru qwbfsmanager-1.2.1/debian/changelog
qwbfsmanager-1.2.1/debian/changelog
--- qwbfsmanager-1.2.1/debian/changelog 2011-12-31 17:15:47.0 +0100
+++ qwbfsmanager-1.2.1/debian/changelog 2012-07-06 08:38:07.0 +0200
@@ -1,3 +1,15 @@
+qwbfsmanager (1.2.1-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS with recent qmake
+Patch by: Filipe AZEVEDO pas...@gmail.com
+Closes: #672048
+ * Fix FTBFS with gcc-4.7
+Patch by: Ilya Barygin randomact...@ubuntu.com
+Closes: #677930
+
+ -- Evgeni Golov evg...@debian.org Fri, 06 Jul 2012 08:38:04 +0200
+
qwbfsmanager (1.2.1-1) unstable; urgency=low
* New upstream release. (Closes: #626681)
diff -Nru qwbfsmanager-1.2.1/debian/patches/fix_qmake_replace.patch
qwbfsmanager-1.2.1/debian/patches/fix_qmake_replace.patch
--- qwbfsmanager-1.2.1/debian/patches/fix_qmake_replace.patch 1970-01-01
01:00:00.0 +0100
+++ qwbfsmanager-1.2.1/debian/patches/fix_qmake_replace.patch 2012-07-06
08:19:00.0 +0200
@@ -0,0 +1,52 @@
+From: Filipe AZEVEDO (Nox P@sNox) pas...@gmail.com
+Date: Sun, 11 Mar 2012 20:13:14 +0100
+Subject: [PATCH] Fix slash / backslash replace in qmake project
+Origin: upstream
+ Based on upstream commit
+
https://github.com/pasnox/fresh/commit/ae40018bcd80ead2dcdefc0af63a92e50f69b3f6
+
+Index: qwbfsmanager-1.2.1/fresh/functions.pri
+===
+--- qwbfsmanager-1.2.1.orig/fresh/functions.pri2011-04-03
22:45:01.0 +0200
qwbfsmanager-1.2.1/fresh/functions.pri 2012-07-06 08:16:50.904152534
+0200
+@@ -4,6 +4,9 @@
+
+ win32:!isEqual( Q_OS, windows ):CONFIG *= win32_crossbuild
+
++SLASH = /
++BACKSLASH = $$escape_expand( \\ )
++
+ # lupdate/lrelease too buggy ( not full qmake interpreter ), so avoid
functions def in this case
+ isEmpty( translations_pass ) {
+ # return the list of directories recursively from a given path ($$1)
+@@ -21,7 +24,7 @@
+ _q_folders = $$system( $$command )
+ _q_folders *= $$1
+
+- _q_folders = $$replace( _q_folders, , / )
++ _q_folders = $$replace( _q_folders, $$BACKSLASH, $SLASH
)
+
+ # loop paths
+ for( q_folder, _q_folders ) {
+Index: qwbfsmanager-1.2.1/fresh/installs.pri
+===
+--- qwbfsmanager-1.2.1.orig/fresh/installs.pri 2011-04-03 22:45:01.0
+0200
qwbfsmanager-1.2.1/fresh/installs.pri 2012-07-06 08:17:42.704151145
+0200
+@@ -42,7 +42,7 @@
+ win32:!win32_crossbuild:fresh_core_headers.files*= $$system(
for /R src/core %i in (*.h) do @echo %i )
+ else:fresh_core_headers.files *= $$system( find src/core -name '*.h' )
+
+- fresh_core_headers.files = $$replace( fresh_core_headers.files, ,
/ )
++ fresh_core_headers.files = $$replace( fresh_core_headers.files,
$$BACKSLASH, $SLASH )
+
+ # gui headers
+ fresh_gui_headers.path = $$FRESH_INSTALL_HEADERS/FreshGui
+@@ -50,7 +50,7 @@
+ win32:!win32_crossbuild:fresh_gui_headers.files *= $$system( for /R
src/gui %i in (*.h) do @echo %i )
+ else:fresh_gui_headers.files*= $$system( find src/gui -name '*.h' )
+
+- fresh_gui_headers.files = $$replace( fresh_gui_headers.files, ,
/ )
++ fresh_gui_headers.files = $$replace( fresh_gui_headers.files,
$$BACKSLASH, $SLASH )
+
+ # generate fresh.prf
+ # remove old one if needed
diff -Nru qwbfsmanager-1.2.1/debian/patches/gcc-4.7.patch
qwbfsmanager-1.2.1/debian/patches/gcc-4.7.patch
--- qwbfsmanager-1.2.1/debian/patches/gcc-4.7.patch 1970-01-01
01:00:00.0 +0100
+++ qwbfsmanager-1.2.1/debian/patches/gcc-4.7.patch 2012-07-06
07:39:21.0 +0200
@@ -0,0 +1,23 @@
+Description: fix compilation with gcc 4.7
+Author: Ilya Barygin randomact...@ubuntu.com
+
+---
qwbfsmanager-1.2.1.orig/fresh/src/gui/environmentvariablemanager/pEnvironmentVariablesModel.cpp
qwbfsmanager-1.2.1/fresh/src/gui/environmentvariablemanager/pEnvironmentVariablesModel.cpp
+@@ -225,12 +225,12 @@ pEnvironmentVariablesModel::Variables pE
+ const QString name = variable.section( '=', 0, 0 );
+ const QString value = variable.section( '=', 1 );
+
+- pEnvironmentVariablesModel::Variable variable;
+- variable.name = name;
+- variable.value = value;
+- variable.enabled = true;
++
Processed: qwbfsmanager: diff for NMU version 1.2.1-1.1
Processing commands for cont...@bugs.debian.org: tags 672048 + patch Bug #672048 [src:qwbfsmanager] qwbfsmanager: FTBFS: src/gui/pColorButton.h:35:25: fatal error: FreshExport.h: No such file or directory Ignoring request to alter tags of bug #672048 to the same tags previously set tags 672048 + pending Bug #672048 [src:qwbfsmanager] qwbfsmanager: FTBFS: src/gui/pColorButton.h:35:25: fatal error: FreshExport.h: No such file or directory Added tag(s) pending. tags 677930 + patch Bug #677930 [qwbfsmanager] qwbfsmanager: FTBFS with gcc 4.7 Ignoring request to alter tags of bug #677930 to the same tags previously set tags 677930 + pending Bug #677930 [qwbfsmanager] qwbfsmanager: FTBFS with gcc 4.7 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 672048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672048 677930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 680405
Processing commands for cont...@bugs.debian.org: affects 680405 node-xmpp Bug #680405 [node-node-expat] changed name from node-expat to node_expat, breaking all consumers Added indication that 680405 affects node-xmpp thanks Stopping processing here. Please contact me if you need assistance. -- 680405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679789: trying to overwrite '/usr/share/doc/kde/HTML/en/konqueror/format-font-size-less.png', which is also in package kdebase-data 4:4.6.5-1
Hello, On Thursday 05 July 2012 22:28:36 K L wrote: What's the status of the bug? My system cannot do upgrade anymore. Is there a way to revert back or allow me upgrade again? We have to wait a bit. Anyway: dpkg --force-overwrite -i /var/cache/apt/archives/konqueror_4%3a4.8.4-1_i386.deb signature.asc Description: This is a digitally signed message part.
Bug#673268: libqtwebkit4: utterly incorrect debian/copyright
I will have time to work on it in the coming week. -- Elena ``of Valhalla'' Grandi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 680405
Processing commands for cont...@bugs.debian.org: affects 680405 node-ltx Bug #680405 [node-node-expat] changed name from node-expat to node_expat, breaking all consumers Added indication that 680405 affects node-ltx thanks Stopping processing here. Please contact me if you need assistance. -- 680405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: merge my stupidity
Processing commands for cont...@bugs.debian.org: reassign 678762 node-node-expat Bug #678762 [src:node-xmpp] node-xmpp: FTBFS: Error: Cannot find module 'node-expat' Bug reassigned from package 'src:node-xmpp' to 'node-node-expat'. No longer marked as found in versions node-xmpp/0.3.2-1. Ignoring request to alter fixed versions of bug #678762 to the same values previously set forcemerge 680405 678762 Bug #680405 [node-node-expat] changed name from node-expat to node_expat, breaking all consumers Bug #680405 [node-node-expat] changed name from node-expat to node_expat, breaking all consumers Added tag(s) sid and wheezy. Bug #678762 [node-node-expat] node-xmpp: FTBFS: Error: Cannot find module 'node-expat' Severity set to 'grave' from 'serious' Added indication that 678762 affects node-ltx,node-xmpp Marked as found in versions node-expat/1.6.0-1. Added tag(s) upstream. Merged 678762 680405 thanks Stopping processing here. Please contact me if you need assistance. -- 678762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678762 680405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): unblock 677762 with 76914 676918
Processing commands for cont...@bugs.debian.org: unblock 677762 with 76914 676918 Bug #677762 [ia32-libs-gtk] Multiarch issues 677762 was blocked by: 677787 650777 661714 676914 650787 676918 641614 677786 641615 68 69 677762 was not blocking any bugs. Removed blocking bug(s) of 677762: 676918, 76914, and 676914 Failed to set blocking bugs of 677762: can't find location for 76914. thanks Stopping processing here. Please contact me if you need assistance. -- 677762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unblock 677762 with 677779
Processing commands for cont...@bugs.debian.org: unblock 677762 with 69 Bug #677762 [ia32-libs-gtk] Multiarch issues 677762 was blocked by: 677787 650777 661714 650787 641614 641615 677786 68 69 677762 was not blocking any bugs. Removed blocking bug(s) of 677762: 69 thanks Stopping processing here. Please contact me if you need assistance. -- 677762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679761: olsrd: diff for NMU version 0.6.3-3.1
tags 679761 + patch tags 679761 + pending thanks Dear maintainer, I've prepared an NMU for olsrd (versioned as 0.6.3-3.1) and will upload it to DELAYED/2 as soon I am in reach of my key (which will be tonight CEST). Please feel free to tell me if I should delay it longer. Regards. Evgeni Golov diff -Nru olsrd-0.6.3/debian/changelog olsrd-0.6.3/debian/changelog --- olsrd-0.6.3/debian/changelog2012-06-30 16:00:52.0 +0200 +++ olsrd-0.6.3/debian/changelog2012-07-06 10:20:17.0 +0200 @@ -1,3 +1,11 @@ +olsrd (0.6.3-3.1) unstable; urgency=low + + * Non-maintainer upload. + * Drop OS=linux from the make call, fixing FTBFS on !linux +Closes: #679761 + + -- Evgeni Golov evg...@debian.org Fri, 06 Jul 2012 10:19:48 +0200 + olsrd (0.6.3-3) unstable; urgency=low * update broken jsoninfo plugin with patches from upstream git diff -Nru olsrd-0.6.3/debian/rules olsrd-0.6.3/debian/rules --- olsrd-0.6.3/debian/rules2012-06-28 00:26:51.0 +0200 +++ olsrd-0.6.3/debian/rules2012-07-06 10:19:47.0 +0200 @@ -7,7 +7,7 @@ dh $@ override_dh_auto_build: - $(MAKE) OS=linux DEBUG=0 build_all + $(MAKE) DEBUG=0 build_all $(MAKE) -C gui/linux-gtk $(MAKE) -C src/olsr_switch -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: olsrd: diff for NMU version 0.6.3-3.1
Processing commands for cont...@bugs.debian.org: tags 679761 + patch Bug #679761 [src:olsrd] olsrd: FTBFS[kfreebsd]: fatal error: linux/types.h: No such file or directory Added tag(s) patch. tags 679761 + pending Bug #679761 [src:olsrd] olsrd: FTBFS[kfreebsd]: fatal error: linux/types.h: No such file or directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 679761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 677762 with 650787
Processing commands for cont...@bugs.debian.org: block 677762 with 650787 Bug #677762 [ia32-libs-gtk] Multiarch issues 677762 was blocked by: 677787 650777 661714 650787 641614 641615 677786 68 677762 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #677762 to the same blocks previously set thanks Stopping processing here. Please contact me if you need assistance. -- 677762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680480: strongswan: Missing Replaces: against libstrongswan
Package: strongswan Version: 4.6.4-4 Severity: serious Justification: unupgradable Hi, looks like some Replaces is missing: | Preparing to replace strongswan 4.5.2-1.5 (using .../strongswan_4.6.4-4_all.deb) ... | Unpacking replacement strongswan ... | dpkg: error processing /var/cache/apt/archives/strongswan_4.6.4-4_all.deb (--unpack): | trying to overwrite '/etc/logcheck/ignore.d.server/strongswan', which is also in package libstrongswan 4.6.4-4 Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680481: vmm and vmware-manager: error when trying to install together
Package: vmm,vmware-manager Version: vmware-manager/0.2.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-30 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: Selecting previously unselected package vmware-manager. Unpacking vmware-manager (from .../vmware-manager_0.2.0-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/vmware-manager_0.2.0-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/vmm.1.gz', which is also in package vmm 0.6.0-1 Processing triggers for install-info ... Errors were encountered while processing: /var/cache/apt/archives/vmware-manager_0.2.0-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/man/man1/vmm.1.gz This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. - Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. vmm=0.6.0-1_vmware-manager=0.2.0-1.log.gz Description: GNU Zip compressed data
Bug#680483: beast and beast-mcmc: error when trying to install together
Package: beast,beast-mcmc Version: beast-mcmc/1.6.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-30 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: Selecting previously unselected package beast-mcmc. Unpacking beast-mcmc (from .../beast-mcmc_1.6.2-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/beast-mcmc_1.6.2-2_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/beast.xpm', which is also in package beast 0.7.4-4 Errors were encountered while processing: /var/cache/apt/archives/beast-mcmc_1.6.2-2_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/pixmaps/beast.xpm This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. - Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. beast=0.7.4-4_beast-mcmc=1.6.2-2.log.gz Description: GNU Zip compressed data
Bug#680484: gmap and scotch: error when trying to install together
Package: gmap,scotch Version: scotch/5.1.12b.dfsg-1.1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-16 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: Selecting previously unselected package scotch. Unpacking scotch (from .../scotch_5.1.12b.dfsg-1.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/scotch_5.1.12b.dfsg-1.1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/gmap.1.gz', which is also in package gmap 2012-06-12-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/scotch_5.1.12b.dfsg-1.1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/gmap usr/share/man/man1/gmap.1.gz This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. - Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. gmap=2012-06-12-1_scotch=5.1.12b.dfsg-1.1.log.gz Description: GNU Zip compressed data
Processed: tagging 680410
Processing commands for cont...@bugs.debian.org: tags 680410 + pending Bug #680410 [salt-minion] salt-minion should depend or recommend dmidecode Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 680410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 680317
Processing commands for cont...@bugs.debian.org:
tags 680317 + pending
Bug #680317 {Done: Thijs Kinkhorst th...@debian.org} [ia32-libs-gtk]
Uninstallable due dependency to unexisting package: i32-libs-gtk-i386
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
680317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 659061 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=679460
Processing commands for cont...@bugs.debian.org: forwarded 659061 https://bugzilla.gnome.org/show_bug.cgi?id=679460 Bug #659061 [brasero] brasero: segfaults when creating a subfolder Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=679460'. thanks Stopping processing here. Please contact me if you need assistance. -- 659061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680317: [Pkg-ia32-libs-maintainers] Bug#680317: Uninstallable due dependency to unexisting package: i32-libs-gtk-i386
On Thu, Jul 05, 2012 at 12:45:55AM +0200, Marco Nenciarini wrote: Package: ia32-libs-gtk Version: 20120616 Severity: serious The package ia32-libs-gtk is uninstallable due to dependency on i32-libs- gtk-i386 (missing 'a' in ia32) However, even with the correct spelling, I can't find the ia32-libs-gtk-i386 package anywhere. Fixed in 20120706: http://mentors.debian.net/package/ia32-libs-gtk http://mentors.debian.net/debian/pool/main/i/ia32-libs-gtk/ia32-libs-gtk_20120706.dsc Feel free to sponsor the upload. Note: I've put some packages into Recommends because they are still Multi-Arch buggy. This allows ia32-libs-gtk-i386 to be installed and tested without them but might break some applications. They should move back to depends as the bugs get fixed. MfG Goswin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679671: [Pkg-ia32-libs-maintainers] Bug#679671: ia32-libs-i386: depends on removed package libdb4.8
On Thu, Jul 05, 2012 at 08:55:37PM -0400, Larry wrote: The dependency problem was with package ia32-libs-i386. You submitted new ia32-libs but not the package in question ia32-libs-i386 It still depends on the removed package libdb4.8, thus ia32-libs is still broken because it depends on ia32-libs-386 which still needs to be updated. Both ia32-libs and ia32-libs-i386 are build from the same source ia32-libs. ia32-libs-i386 just needs to be build by the i386 autobuilder, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680378. MfG Goswin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 676140 in 1.8.4-1, found 677407 in 1:3.4+1, found 680481 in vmware-manager/0.2.0-1 ...
Processing commands for cont...@bugs.debian.org: found 676140 1.8.4-1 Bug #676140 [sssd] needs to do proper cleanup of /etc/apparmor.d/disable/ Marked as found in versions sssd/1.8.4-1. found 677407 1:3.4+1 Bug #677407 [gnome-core] gnome-dbg: fails to upgrade from squeeze - apt does not find an upgrade path Marked as found in versions meta-gnome3/1:3.4+1. found 680481 vmware-manager/0.2.0-1 Bug #680481 [vmm,vmware-manager] vmm and vmware-manager: error when trying to install together Marked as found in versions vmware-manager/0.2.0-1. found 680481 vmm/0.6.0-1 Bug #680481 [vmm,vmware-manager] vmm and vmware-manager: error when trying to install together Marked as found in versions vmm/0.6.0-1. found 680483 beast/0.7.4-4 Bug #680483 [beast,beast-mcmc] beast and beast-mcmc: error when trying to install together Marked as found in versions beast/0.7.4-4. found 680483 beast-mcmc/1.6.2-2 Bug #680483 [beast,beast-mcmc] beast and beast-mcmc: error when trying to install together Marked as found in versions beast-mcmc/1.6.2-2. found 680484 gmap/2012-06-12-1 Bug #680484 [gmap,scotch] gmap and scotch: error when trying to install together Marked as found in versions gmap/2012-06-12-1. found 680484 scotch/5.1.12b.dfsg-1.1 Bug #680484 [gmap,scotch] gmap and scotch: error when trying to install together Marked as found in versions scotch/5.1.12b.dfsg-1.1. thanks Stopping processing here. Please contact me if you need assistance. -- 676140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676140 677407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677407 680481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680481 680483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680483 680484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680483: marked as done (beast and beast-mcmc: error when trying to install together)
Your message dated Fri, 06 Jul 2012 10:02:15 + with message-id e1sn5md-0006jd...@franck.debian.org and subject line Bug#680483: fixed in beast-mcmc 1.6.2-3 has caused the Debian Bug report #680483, regarding beast and beast-mcmc: error when trying to install together 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.) -- 680483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: beast,beast-mcmc Version: beast-mcmc/1.6.2-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-30 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: Selecting previously unselected package beast-mcmc. Unpacking beast-mcmc (from .../beast-mcmc_1.6.2-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/beast-mcmc_1.6.2-2_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/beast.xpm', which is also in package beast 0.7.4-4 Errors were encountered while processing: /var/cache/apt/archives/beast-mcmc_1.6.2-2_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/pixmaps/beast.xpm This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. - Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. beast=0.7.4-4_beast-mcmc=1.6.2-2.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: beast-mcmc Source-Version: 1.6.2-3 We believe that the bug you reported is fixed in the latest version of beast-mcmc, which is due to be installed in the Debian FTP archive: beast-mcmc-doc_1.6.2-3_all.deb to contrib/b/beast-mcmc/beast-mcmc-doc_1.6.2-3_all.deb beast-mcmc-examples_1.6.2-3_all.deb to contrib/b/beast-mcmc/beast-mcmc-examples_1.6.2-3_all.deb beast-mcmc-lib_1.6.2-3_amd64.deb to contrib/b/beast-mcmc/beast-mcmc-lib_1.6.2-3_amd64.deb beast-mcmc_1.6.2-3.debian.tar.gz to contrib/b/beast-mcmc/beast-mcmc_1.6.2-3.debian.tar.gz beast-mcmc_1.6.2-3.dsc to contrib/b/beast-mcmc/beast-mcmc_1.6.2-3.dsc beast-mcmc_1.6.2-3_all.deb to contrib/b/beast-mcmc/beast-mcmc_1.6.2-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 680...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated beast-mcmc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 06 Jul 2012 11:30:19 +0200 Source: beast-mcmc Binary: beast-mcmc beast-mcmc-lib beast-mcmc-examples beast-mcmc-doc Architecture: source all amd64 Version: 1.6.2-3 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: beast-mcmc - Bayesian MCMC phylogenetic inference beast-mcmc-doc - Bayesian MCMC phylogenetic inference - documentation beast-mcmc-examples - Bayesian MCMC phylogenetic inference - example data beast-mcmc-lib - Bayesian MCMC phylogenetic inference Closes: 680483 Changes: beast-mcmc (1.6.2-3) unstable; urgency=low . *
Bug#680492: CVE-2011-4408
Package: ubuntu-sso-client Severity: grave Tags: security http://www.ubuntu.com/usn/USN-1464-1/ Should this package really be included in Wheezy? There were just two uploads 15 months ago and it's totally behind upstream (Ubuntu has 3.99.1) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645998: closed by Josip Rodin joy-packa...@debian.org (Bug#645998: fixed in freeradius 2.1.12+dfsg-1)
On Wed, Jul 04, 2012 at 01:08:59PM +0200, José Antonio Antelo wrote: Is it possible to backport freeradius to stable version? Yes, I'll get to it eventually. You can also request that someone else does it in the backports support channels. And try to add the new FR to debian 7 before being frozen? It's already en route there. (Please don't Cc: owner@bugs.d.o on specific bug report matters.) -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667629: libapache-mod-auth-radius: diff for NMU version 1.5.8-1.1
On Mon, Jul 02, 2012 at 06:08:53AM +0200, Fabio M. Di NItto wrote: On 07/01/2012 02:50 PM, Arno Töll wrote: tags 667629 + patch tags 667629 + pending thanks Dear maintainer, I've prepared an NMU for libapache-mod-auth-radius (versioned as 1.5.8-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Go ahead and let it in :) Thanks for taking care of it. Ditto... after the initial confusion, I simply forgot about the whole Apache kerfuffle :) -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679761: olsrd: diff for NMU version 0.6.3-3.1
Hi! On 07/06/2012 10:37 AM, evg...@debian.org wrote: I've prepared an NMU for olsrd (versioned as 0.6.3-3.1) and will upload it to DELAYED/2 as soon I am in reach of my key (which will be tonight CEST). Please feel free to tell me if I should delay it longer. Thanks for your patch! I'd prefer to upload it myself, since we need to include the patch to the Debian SVN anyway. If HC doesn't do, I'll upload later today. Thanks, Roland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, i had a look at brasero build logs and have to drop the appealing theory of sizeof(off_t) == 4. The compiler gets a sufficient macro to avoid this: -D_FILE_OFFSET_BITS=64 I now managed to build Brasero brasero-2.30.3-2 from the Debian sources. It shows no differences to the previously installed one. The installed libisofs and libburn are very old now. Is there a way to test again with the current versions in Debian sid ? -- Summary for now: I am unable to reproduce the described problems about partially or completely written CD or DVD which are unreadable afterwards. If burning starts here, then it completes up to the moment when Brasero should recognize that it successfully ejected the medium. The resulting media are mountable and bear the correct content for all files which are recorded. Missing are only files of which the name begins by a dot .. Note well: George's patch is not yet applied. -- Realtime recorded details of my brasero adventures: So i continue trying to build brasero from source on my libburnia-upstream infested system. It says libburn is installed. But brasero refuses to link to it when built by dpkg-buildpackage. So i do # rm /usr/local/lib/libburn.a # rm /usr/local/lib/libisofs.a # apt-get purge libburn4 (brasero and others get de-installed, too) # apt-get purge libisofs6 # apt-get install libburn4 # apt-get install libisofs6 # apt-get install libburn-dev # apt-get install libisofs-dev This has installed antique libburn-0.8.0 and libisofs-0.6.32. Released in spring 2009 ! Now i get warnings about the failure to sign $ dpkg-buildpackage ... dpkg-buildpackage: binary and diff upload (original source NOT included) dpkg-buildpackage: warning: Failed to sign .dsc and .changes file $ echo $? 1 I continue with George's instructions: Remove any previous brasero package you might have: # apt-get --purge remove brasero (seems to have been removed already when i removed libburn4) install yours: # ls -l brasero_2.30.3-2_amd64.deb -rw-r--r-- 1 thomas thomas 677008 Jul 6 11:49 ../brasero_2.30.3-2_amd64.deb # dpkg -i brasero_2.30.3-2_amd64.deb ... dpkg: dependency problems prevent configuration of brasero: brasero depends on libbrasero-media0 (= 2.30.3-2); however: Package libbrasero-media0 is not installed. dpkg: error processing brasero (--install): dependency problems - leaving unconfigured ... # apt-get install libbrasero-media0 ... # dpkg -i brasero_2.30.3-2_amd64.deb $ brasero It starts. It remembers my data disc project and annoys me by popping up with the usual protest about deep directories. Loaded is a DVD+RW. (This type is reported to get spoiled and then needing some kind of re-vitalization. I suspect that growisofs warns about an existing ISO-9660 superblock. This could be silenced e.g. by overwriting the first 64 kB of the medium with zeros.) Maximum speed, Burn the image directly ... ... Burn. It asks whether i want to blank the current disc. (That would probably be such an overwrite with zeros.) libisofs DEBUG messages appear ... 55 % ... 100 %. I abort the integrity check in favor of my own means. The media ejection is then as broken as was with the originally installed brasero. Let's see what we got. Today the burner is /dev/sr0 : # mount /dev/sr0 /mnt $ diff -r libburn_dir /mnt/libburn_dir yields complaints about missing .files. (Is that a bug or a feature ?) No messages about differing file content. The same positive result with $ xorriso -indev /dev/sr0 -compare_r libburn_dir /libburn_dir 21 \ | fgrep -v ' : st_' | fgrep -v 'annot find' Well. For completeness the same with a CD-RW: I get asked whether i want to blank the disc. I confirm. libisofs reports about colliding dumb-ISO names (which is normal) ... Oops ? The Burning data DVD window says Ejecting Medium while libisofs says that it is still writing parts of the directory tree: brasero (libisofs)DEBUG : Writing ISO Path tables After a timeout i get asked to eject manually. I confirm and get a window Error while burning. MEDIA: closed or not recordable,. I take the opportunity to save the log. ... BraseroLibisofs called brasero_job_get_action BraseroLibisofs Finished track successfully BraseroLibisofs stopping BraseroLibburn called brasero_job_get_action BraseroLibburn creating input ... BraseroLibburn Precheck failed MEDIA: closed or not recordable, BraseroLibisofs stopping BraseroLibburn stopping BraseroLibburn closing connection for BraseroLibburn Session error : MEDIA: closed or not recordable, (brasero_burn_record brasero-burn.c:2839) This is reproducible again on a second try. It did work yesterday. Regrettably not the problem i am hunting for. $ xorriso -outdev /dev/sr0 -blank fast ... 30 seconds of pacifier messages ... Media
Bug#679761: olsrd: diff for NMU version 0.6.3-3.1
Hi, On Fri, Jul 06, 2012 at 01:34:55PM +0200, Roland Stigge wrote: On 07/06/2012 10:37 AM, evg...@debian.org wrote: I've prepared an NMU for olsrd (versioned as 0.6.3-3.1) and will upload it to DELAYED/2 as soon I am in reach of my key (which will be tonight CEST). Please feel free to tell me if I should delay it longer. Thanks for your patch! yw I'd prefer to upload it myself, since we need to include the patch to the Debian SVN anyway. If HC doesn't do, I'll upload later today. Sure, go on, less trouble for me :) Thanks Evgeni -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680397: [Debichem-devel] Bug#680397: aces3: FTBFS: Times out
Hi, On Thu, Jul 05, 2012 at 06:50:40PM +0200, Kurt Roeckx wrote: Source: aces3 Version: 3.0.6-4 Severity: serious Your package fails to build on a few arches, timing out in the test suite: (cd tests; OMPI_MCA_plm_rsh_agent=/bin/false csh ./runscript) Running 1.1.1.1 mpirun: killing job... E: Caught signal 'Terminated': terminating immediately -- mpirun noticed that process rank 0 with PID 9855 on node murphy exited on signal 0 (Unknown signal 0). -- mpirun: clean termination accomplished make: *** [build-arch] Terminated make[1]: *** [override_dh_auto_test] Terminated Build killed with signal TERM after 150 minutes of inactivity On i386, this might indeed be a problem we have to investigate. On arm* I would guess the autobuilders are just too slow to finish the test suite on time for now. Unfortunately, the ACESIII developers really used rather heavy stuff for their test suite. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676081: marked as done (rrdtool: FTBFS: main.c:102:5: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Fri, 06 Jul 2012 12:17:14 + with message-id e1sn7tg-00071z...@franck.debian.org and subject line Bug#676081: fixed in rrdtool 1.4.7-1.1 has caused the Debian Bug report #676081, regarding rrdtool: FTBFS: main.c:102:5: error: format not a string literal and no format arguments [-Werror=format-security] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 676081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rrdtool Version: 1.4.7-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs User: debian-r...@lists.debian.org Usertags: default19 Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»/bindings/ruby' compiling main.c main.c: In function 'string_arr_new': main.c:60:22: warning: format '%s' expects argument of type 'char *', but argument 3 has type 'long int' [-Wformat] main.c:60:22: warning: format '%ld' expects argument of type 'long int', but argument 4 has type 'int' [-Wformat] main.c: In function 'rrd_call': main.c:102:5: error: format not a string literal and no format arguments [-Werror=format-security] main.c: In function 'rb_rrd_infocall': main.c:170:5: error: format not a string literal and no format arguments [-Werror=format-security] main.c: In function 'rb_rrd_fetch': main.c:246:5: error: format not a string literal and no format arguments [-Werror=format-security] main.c: In function 'rb_rrd_graph': main.c:291:5: error: format not a string literal and no format arguments [-Werror=format-security] main.c: In function 'rb_rrd_last': main.c:319:5: error: format not a string literal and no format arguments [-Werror=format-security] main.c: In function 'rb_rrd_xport': main.c:340:5: error: format not a string literal and no format arguments [-Werror=format-security] cc1: some warnings being treated as errors make[1]: *** [main.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/rrdtool_1.4.7-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: rrdtool Source-Version: 1.4.7-1.1 We believe that the bug you reported is fixed in the latest version of rrdtool, which is due to be installed in the Debian FTP archive: liblua5.1-rrd-dev_1.4.7-1.1_amd64.deb to main/r/rrdtool/liblua5.1-rrd-dev_1.4.7-1.1_amd64.deb liblua5.1-rrd0_1.4.7-1.1_amd64.deb to main/r/rrdtool/liblua5.1-rrd0_1.4.7-1.1_amd64.deb librrd-dev_1.4.7-1.1_amd64.deb to main/r/rrdtool/librrd-dev_1.4.7-1.1_amd64.deb librrd-ruby1.8_1.4.7-1.1_amd64.deb to main/r/rrdtool/librrd-ruby1.8_1.4.7-1.1_amd64.deb librrd-ruby1.9.1_1.4.7-1.1_amd64.deb to main/r/rrdtool/librrd-ruby1.9.1_1.4.7-1.1_amd64.deb librrd-ruby_1.4.7-1.1_all.deb to main/r/rrdtool/librrd-ruby_1.4.7-1.1_all.deb librrd4_1.4.7-1.1_amd64.deb to main/r/rrdtool/librrd4_1.4.7-1.1_amd64.deb librrdp-perl_1.4.7-1.1_all.deb to main/r/rrdtool/librrdp-perl_1.4.7-1.1_all.deb librrds-perl_1.4.7-1.1_amd64.deb to main/r/rrdtool/librrds-perl_1.4.7-1.1_amd64.deb python-rrdtool_1.4.7-1.1_amd64.deb to main/r/rrdtool/python-rrdtool_1.4.7-1.1_amd64.deb rrdcached_1.4.7-1.1_amd64.deb to main/r/rrdtool/rrdcached_1.4.7-1.1_amd64.deb rrdtool-dbg_1.4.7-1.1_amd64.deb to main/r/rrdtool/rrdtool-dbg_1.4.7-1.1_amd64.deb rrdtool-tcl_1.4.7-1.1_amd64.deb to main/r/rrdtool/rrdtool-tcl_1.4.7-1.1_amd64.deb rrdtool_1.4.7-1.1.diff.gz to main/r/rrdtool/rrdtool_1.4.7-1.1.diff.gz rrdtool_1.4.7-1.1.dsc to main/r/rrdtool/rrdtool_1.4.7-1.1.dsc rrdtool_1.4.7-1.1_amd64.deb to main/r/rrdtool/rrdtool_1.4.7-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 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Wiltshire j...@debian.org (supplier of updated rrdtool package) (This message was generated automatically at their request; if you believe
Bug#670405: ekiga: Ekiga crashes on startup
On 09/05/12 12:24, Eugen Dedu wrote: On 25/04/12 12:42, Alberto Garcia wrote: Package: ekiga Version: 3.2.7-4.2 Severity: grave Justification: renders package unusable Since a few weeks ago, Ekiga crashes on startup (shortly after showing the main window) and I cannot use it at all. It doesn't seem to happen 100% of the times, though, but the problem is very easy to reproduce. Could you please send us the -d 4 output when it crashes? Try like this: gdb -- args ekiga -d 4 21|tee log.txt and press of course: thread apply all bt when it crashes More info on http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze Be also sure that you have ptlib, opal and ekiga's dbg packages installed. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679447: libcoro-perl often segfaults
On 11:12 Fri 29 Jun , Alessandro Ghedini wrote: On Fri, Jun 29, 2012 at 06:31:52AM +0400, Dmitry E. Oboukhov wrote: found 679447 6.070-1+b1 thanks I can't reproduce crashes in 6.070-1+b1 :) sorry for mistake. 6.070-1+b1 crashes, too Still, I can't reproduce it. The example code you provided doesn't segfault (with $n = 100, bigger than that my pc freezes), and Corona works fine too. On amd64 it seems to work fine. Could you please provide a more specific procedure to reproduce the issue? That is, how are you getting failures so reliably? Hi! I've extracted a code that causes segfaults. It can be found here: https://gist.github.com/3059829 start server (it will create socket with default name or ARGV[0]) and then start client (it will connect to socket with default name or ARGV[0]). see also comments under gist.github -- . ''`. Dmitry E. Oboukhov : :’ : email: un...@debian.org jabber://un...@uvw.ru `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537 signature.asc Description: Digital signature
Processed: I've extracted a full test
Processing commands for cont...@bugs.debian.org: tags 679447 -moreinfo Bug #679447 [libcoro-perl] libcoro-perl often segfaults Removed tag(s) moreinfo. tags 679447 -unreproducible Bug #679447 [libcoro-perl] libcoro-perl often segfaults Removed tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 679447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680503: isdnutils: 3.25 upstream tarball is in fact still dfsg-nonfree
Package: isdnutils Version: 1:3.25-1 Severity: serious Justification: Policy 2.2.1 I am filing this as maintainer against my own package since it's RC-severity and I will need a freeze exception to fix it. In the past few months I had been working with upstream to drop dfsg-nonfree bits from their tarball and make my life easier. git diff $dfsgbranch $upstreambranch|lsdiff recently led me to believe that the difference between upstream and what we were shipping as the dfsg-tarball had essentially dwindled down to insignificant bits such as dotfiles, etc, leaving upstream dfsg-free. This assumption turns out to be mistaken and we need to ship 3.25 as dfsg, too, just like previous versions. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680503: isdnutils: 3.25 upstream tarball is in fact still dfsg-nonfree
On 06/07/12 14:38, Rolf Leggewie wrote: Package: isdnutils Version: 1:3.25-1 Severity: serious Justification: Policy 2.2.1 I am filing this as maintainer against my own package since it's RC-severity and I will need a freeze exception to fix it. In the past few months I had been working with upstream to drop dfsg-nonfree bits from their tarball and make my life easier. git diff $dfsgbranch $upstreambranch|lsdiff recently led me to believe that the difference between upstream and what we were shipping as the dfsg-tarball had essentially dwindled down to insignificant bits such as dotfiles, etc, leaving upstream dfsg-free. This assumption turns out to be mistaken and we need to ship 3.25 as dfsg, too, just like previous versions. Apologies if I misunderstood your bugreport, but are filing this bugreport because you want to change the version schema by appeding a +dfsg bit to it? Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680508: /usr/bin/kvm: segfault at 10 ip 00007fed4d3bf78e sp 00007fed3e364990 error 4 in kvm[7fed4d260000+381000]
Package: qemu-kvm Version: 1.1~z0+dfsg-1 Severity: grave File: /usr/bin/kvm Justification: renders package unusable Hi, KVM is crashing with the following backtrace: --- stack trace --- #0 0x7fed4d3bf78e in virtio_pci_mask_vq (vector=1, vector@entry=error reading variable: Cannot access memory at address 0x7fed3e3649c8, vq=0x7fed4ecf43f0, vq@entry=error reading variable: Cannot access memory at address 0x7fed3e3649c8, masked=0, masked@entry=error reading variable: Cannot access memory at address 0x7fed3e3649c8, dev=error reading variable: Unhandled dwarf expression opcode 0xfa) at /build/buildd-qemu-kvm_1.1~z0+dfsg-1-amd64-0ZEDoL/qemu-kvm-1.1~z0+dfsg/hw/virtio-pci.c:546 notifier = 0x7fed4ecf4438 r = optimized out Cannot access memory at address 0x7fed3e3649c8 The VM's are launched using libvirt /usr/bin/kvm -S -M pc-0.15 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name Fedora17 -uuid b2e66a22-4296-199e-a927-7e565035a27c -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Fedora17.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/Fedora17.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b3:d7:9c,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spic evmc,id= charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 Cheers Laurent Bigonville -- Package-specific info: /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz stepping: 5 microcode : 0x3 cpu MHz : 1199.000 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm ida arat dts tpr_shadow vnmi flexpriority ept vpid bogomips: 5320.31 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 : 37 model name : Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz stepping: 5 microcode : 0x3 cpu MHz : 1199.000 cache size : 3072 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 2 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 11 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm ida arat dts tpr_shadow vnmi flexpriority ept vpid bogomips: 5320.31 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 37 model name : Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz stepping: 5 microcode : 0x3 cpu MHz : 1199.000 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 11 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
Bug#680509: openexr: FTBFS on non-linux (or when disabling large stacks)
Source: openexr
Version: 1.6.1-5
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
Hi,
most probably due to GCC 4.7, openexr does not compile when large
stacks are disabled, which is done by default on any non-Linux
architecture (see also configure.ac).
The problem can also be seen in a recent rebuild on hurd-i386[1],
or just when trying to compile it on e.g. kfreebsd; for example on
kfreebsd-amd64:
| g++ -DHAVE_CONFIG_H -I. -I. -I../config -I/usr/include/OpenEXR -I..
-I../config -D_FORTIFY_SOURCE=2 -pipe -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -c ImfHuf.cpp -fPIC
-DPIC -o .libs/ImfHuf.o
| In file included from ImfHuf.cpp:50:0:
| ./ImfAutoArray.h: In instantiation of 'Imf::AutoArrayT, size::AutoArray()
[with T = int; int size = 65537]':
| ImfHuf.cpp:298:34: required from here
| ./ImfAutoArray.h:60:39: error: 'memset' was not declared in this scope, and
no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
| In file included from /usr/include/string.h:642:0,
| from ImfHuf.cpp:52:
| /usr/include/x86_64-kfreebsd-gnu/bits/string3.h:77:1: note: 'void*
memset(void*, int, size_t)' declared here, later in the translation unit
| In file included from ImfHuf.cpp:50:0:
| ./ImfAutoArray.h: In instantiation of 'Imf::AutoArrayT, size::AutoArray()
[with T = long unsigned int*; int size = 65537]':
| ImfHuf.cpp:299:38: required from here
| ./ImfAutoArray.h:60:39: error: 'memset' was not declared in this scope, and
no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
| In file included from /usr/include/string.h:642:0,
| from ImfHuf.cpp:52:
| /usr/include/x86_64-kfreebsd-gnu/bits/string3.h:77:1: note: 'void*
memset(void*, int, size_t)' declared here, later in the translation unit
| In file included from ImfHuf.cpp:50:0:
| ./ImfAutoArray.h: In instantiation of 'Imf::AutoArrayT, size::AutoArray()
[with T = long unsigned int; int size = 65537]':
| ImfHuf.cpp:361:36: required from here
| ./ImfAutoArray.h:60:39: error: 'memset' was not declared in this scope, and
no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
| In file included from /usr/include/string.h:642:0,
| from ImfHuf.cpp:52:
| /usr/include/x86_64-kfreebsd-gnu/bits/string3.h:77:1: note: 'void*
memset(void*, int, size_t)' declared here, later in the translation unit
| In file included from ImfHuf.cpp:50:0:
| ./ImfAutoArray.h: In instantiation of 'Imf::AutoArrayT, size::AutoArray()
[with T = Imf::{anonymous}::HufDec; int size = 16384]':
| ImfHuf.cpp:1050:37: required from here
| ./ImfAutoArray.h:60:39: error: 'memset' was not declared in this scope, and
no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
| In file included from /usr/include/string.h:642:0,
| from ImfHuf.cpp:52:
| /usr/include/x86_64-kfreebsd-gnu/bits/string3.h:77:1: note: 'void*
memset(void*, int, size_t)' declared here, later in the translation unit
| make[3]: *** [ImfHuf.lo] Error 1
Attached there is a patch that fixes the issue, by including cstring
in ImfAutoArray.h only with no large stacks enabled, and making sure
to call memset from the std namespace.
(Note: it seems openexr 1.7.0 will no more memset() the data array
in the no large stacks implementation.)
[1]
https://buildd.debian.org/status/fetch.php?pkg=openexrarch=hurd-i386ver=1.6.1-5%2Bb1stamp=1337862561
Thanks,
--
Pino
--- a/IlmImf/ImfAutoArray.h
+++ b/IlmImf/ImfAutoArray.h
@@ -46,6 +46,10 @@
#include OpenEXRConfig.h
+#if !defined (HAVE_LARGE_STACK)
+#include cstring
+#endif
+
namespace Imf {
@@ -57,7 +61,7 @@
{
public:
- AutoArray (): _data (new T [size]) {memset(_data, 0, size * sizeof(T));}
+ AutoArray (): _data (new T [size]) {::std::memset(_data, 0, size * sizeof(T));}
~AutoArray () {delete [] _data;}
operator T * () {return _data;}
Bug#679665: [Pkg-javascript-devel] Bug#679665: jquery: build-deps not satisfiable in wheezy
On 12-07-05 at 11:05pm, Mehdi Dogguy wrote: On 05/07/12 22:57, Jonas Smedegaard wrote: If we skip installing minified files, then yes it breaks. If we skip minifying but still install - i.e. install files that are 0% minified - then only download times should be affected. I think that this is the best option we have at this stage. In any case, it's your call as a maintainer to choose which solution you want to implement. Switching to slimit might be a sexy option but also falls in the changing the compressor category, imho. How about this: Now: 1) Skip generating and installing any minified files at build time. 2) Try minify and fallback to copy in postinst script: for if in $files-to-be-minified; do of=$(basename $if .js).min.js javascript-minifier -o $of $if | cp -a $if $of done 3) Remove minified/copied files in remove state of postrm script: for if in $files-to-be-minified; do of=$(basename $if .js).min.js rm -f $of done (javascript-minifier should use same basic syntax as both yui-compressor and uglifyjs share today.) Official result now: * Javascript files will not be minified. Unofficial possibility now: * Add /usr/local/bin/javascript-minifier symlink to yui-compressor * Add /usr/local/bin/javascript-minifier custom compressor script Official possibility later (perhaps even at a stable point release): * Add javascript-minifier package with debconf handling of /etc/alternatives symlinking of /usr/bin/javascript-minifier and perhaps also /usr/sbin/update-javascript-minifications. How does that sound? Too complex at this stage? @Marcelo: What do you think? What do others in the team think? Regards, - Jonas P.S. Yes - I still think generally across all Javascript packages... -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#679765: [Pkg-puppet-devel] Bug#679765: puppetmaster - CA prone to MD5 collision attacks
The patch at https://github.com/puppetlabs/puppet/pull/616/files changes the default hash settings from MD5 and SHA1 to SHA256. This should have no effect on operation (or security) on existing environments. With an existinc CA, I've tested adding nodes with a patched master and client, a patched master against unpatched clients, and unpatched clients against a patched master. Securing existing puppet environments requires some work. * The creation of a new CA certificate. * Does the CA need a new key as well? * Would existing nodes automatically trust the new CA certificate, if it comes from the same key? In the worst case, an automated upgrade path would be needed for large environments. For smaller environments, it is possible, but rather tedious, to remove /var/lib/puppet/ssl/ on master and all nodes, start the master, start the nodes, and use puppet cert sign nodename (alternatively puppet cert sign --all, or use /etc/puppet/autosign.conf if you have a closed environment) -- Stig Sandbeck Mathisen pgpbsF3MjSHmJ.pgp Description: PGP signature
Bug#668383: smokeping: fails to install, remove, distupgrade, and install again
On Wed, Apr 11, 2012 at 04:20:34PM +0200, Andreas Beckmann wrote: Package: smokeping Version: 2.6.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts during a test with piuparts I noticed your package failed to install (in 'squeeze'), remove (but not purge), distupgrade to 'wheezy', and install again. Setting up smokeping (2.6.8-1) ... Configuration file `/etc/smokeping/basepage.html' == File on system created by you or by a script. == File also in package provided by package maintainer. Antoine, are you aware of this open release critical bug? I see I'm still listed in Uploaders. Please remove me, I no longer consider myself responsible for this package. Thanks for your work, -- Niko Tyni nt...@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#665894: NMUing for RC bug
No maintainer response for 3 months, so I'll upload this NMU shortly.Binary files /tmp/QwHFJsfGn1/python-dateutil-1.5/dateutil/zoneinfo/zoneinfo-2010g.tar.gz and /tmp/zvV9EAtm8d/python-dateutil-1.5+dfsg/dateutil/zoneinfo/zoneinfo-2010g.tar.gz differ
diff -Nru python-dateutil-1.5/debian/changelog python-dateutil-1.5+dfsg/debian/changelog
--- python-dateutil-1.5/debian/changelog 2011-08-30 16:20:51.0 -0400
+++ python-dateutil-1.5+dfsg/debian/changelog 2012-07-06 10:00:10.0 -0400
@@ -1,3 +1,15 @@
+python-dateutil (1.5+dfsg-0.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Repack upstream tarball to remove non-free time zone information
+(sourceless binary data) (Closes: #665894)
+ * Remove reference to dateutil/zoneinfo/zoneinfo-2010g.tar.gz from both
+upstream build system and debian/rules
+- The file was not shipped in the binary, so there's no impact on the
+ functionality of the package
+
+ -- Scott Kitterman sc...@kitterman.com Fri, 06 Jul 2012 09:00:45 -0400
+
python-dateutil (1.5-1) unstable; urgency=low
[ Guido Günther ]
diff -Nru python-dateutil-1.5/debian/patches/Remove_Zoneinfo_Tarball_665894 python-dateutil-1.5+dfsg/debian/patches/Remove_Zoneinfo_Tarball_665894
--- python-dateutil-1.5/debian/patches/Remove_Zoneinfo_Tarball_665894 1969-12-31 19:00:00.0 -0500
+++ python-dateutil-1.5+dfsg/debian/patches/Remove_Zoneinfo_Tarball_665894 2012-07-06 10:00:10.0 -0400
@@ -0,0 +1,78 @@
+Description: Remove dateutil/zoneinfo/zoneinfo-2010g.tar.gz from build system
+ python-dateutil (1.5+dfsg-0.1) unstable; urgency=low
+ .
+ * Non-maintainer upload.
+ * Repack upstream tarball to remove non-free time zone information
+ (sourceless binary data) (Closes: #665894)
+ * Remove reference to dateutil/zoneinfo/zoneinfo-2010g.tar.gz from both
+ upstream build system and debian/rules
+ - The file was not shipped in the binary, so there's no impact on the
+ functionality of the package
+Author: Scott Kitterman sc...@kitterman.com
+Bug-Debian: http://bugs.debian.org/665894
+Origin: vendor
+Forwarded: no
+Last-Update: 2012-07-06
+
+Index: python-dateutil-1.5+dfsg/MANIFEST.in
+===
+--- python-dateutil-1.5+dfsg.orig/MANIFEST.in 2012-07-06 09:37:24.398650586 -0400
python-dateutil-1.5+dfsg/MANIFEST.in 2012-07-06 09:37:50.042649829 -0400
+@@ -1,4 +1,4 @@
+-recursive-include dateutil *.py *.tar.*
++recursive-include dateutil *.py
+ recursive-include sandbox *.py
+ include setup.py setup.cfg MANIFEST.in README LICENSE NEWS Makefile
+ include test.py example.py
+Index: python-dateutil-1.5+dfsg/setup.py
+===
+--- python-dateutil-1.5+dfsg.orig/setup.py 2012-07-06 09:37:24.414650583 -0400
python-dateutil-1.5+dfsg/setup.py 2012-07-06 09:37:50.042649829 -0400
+@@ -29,7 +29,5 @@
+ datetime module, available in Python 2.3+.
+ ,
+ packages = [dateutil, dateutil.zoneinfo],
+- package_data={: [*.tar.gz]},
+- include_package_data=True,
+ zip_safe=False,
+ )
+Index: python-dateutil-1.5+dfsg/python_dateutil.egg-info/SOURCES.txt
+===
+--- python-dateutil-1.5+dfsg.orig/python_dateutil.egg-info/SOURCES.txt 2012-07-06 09:37:24.426650583 -0400
python-dateutil-1.5+dfsg/python_dateutil.egg-info/SOURCES.txt 2012-07-06 09:37:50.042649829 -0400
+@@ -16,11 +16,10 @@
+ dateutil/tz.py
+ dateutil/tzwin.py
+ dateutil/zoneinfo/__init__.py
+-dateutil/zoneinfo/zoneinfo-2010g.tar.gz
+ python_dateutil.egg-info/PKG-INFO
+ python_dateutil.egg-info/SOURCES.txt
+ python_dateutil.egg-info/dependency_links.txt
+ python_dateutil.egg-info/not-zip-safe
+ python_dateutil.egg-info/top_level.txt
+ sandbox/rrulewrapper.py
+-sandbox/scheduler.py
+\ No newline at end of file
++sandbox/scheduler.py
+Index: python-dateutil-1.5+dfsg/test.py
+===
+--- python-dateutil-1.5+dfsg.orig/test.py 2012-07-06 09:37:46.118649944 -0400
python-dateutil-1.5+dfsg/test.py 2012-07-06 09:38:12.294649170 -0400
+@@ -3883,7 +3883,7 @@
+ self.assertEqual(datetime(2003,10,26,0,59,tzinfo=tz).tzname(), EDT)
+ self.assertEqual(datetime(2003,10,26,1,00,tzinfo=tz).tzname(), EST)
+
+-def testZoneInfoFileStart1(self):
++def testZoneInfoFileStart1(self):
+ tz = zoneinfo.gettz(EST5EDT)
+ self.assertEqual(datetime(2003,4,6,1,59,tzinfo=tz).tzname(), EST)
+ self.assertEqual(datetime(2003,4,6,2,00,tzinfo=tz).tzname(), EDT)
+@@ -3900,7 +3900,7 @@
+ t1 = t0.astimezone(utc)
+ t2 = t1.astimezone(nyc)
+ self.assertEquals(t0, t2)
+-self.assertEquals(nyc.dst(t0), timedelta(hours=1))
++self.assertEquals(nyc.dst(t0), timedelta(hours=1))
+
+ def testICalStart1(self):
+ tz = tzical(StringIO(self.TZICAL_EST5EDT)).get()
diff -Nru
Processed (with 1 errors): Re: kvm-1.0 segfaults with -M pc-1.0 (and older) and vhost-net
Processing commands for cont...@bugs.debian.org:
severity 679788 serious
Bug #679788 [qemu-kvm] kvm-1.0 segfaults with -M pc-1.0 (and older) and
vhost-net
Bug #680460 [qemu-kvm] KVM crashes with segfault error for kernel linux-3.4.4
AMD64
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
severity 680508 serious
Bug #680508 [qemu-kvm] /usr/bin/kvm: segfault at 10 ip 7fed4d3bf78e sp
7fed3e364990 error 4 in kvm[7fed4d26+381000]
Severity set to 'serious' from 'grave'
merge 680508 679788
Bug #680508 [qemu-kvm] /usr/bin/kvm: segfault at 10 ip 7fed4d3bf78e sp
7fed3e364990 error 4 in kvm[7fed4d26+381000]
Unable to merge bugs because:
forwarded of #679788 is 'http://www.spinics.net/lists/kvm/msg75053.html' not ''
forwarded of #680460 is 'http://www.spinics.net/lists/kvm/msg75053.html' not ''
Failed to merge 680508: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x242df80)',
'requester', 'Laurent Bigonville bi...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'20120706160127.65da6...@eldamar.bigon.be', 'request_subject', ...) called at
/usr/lib/debbugs/service line 872
eval {...} called at /usr/lib/debbugs/service line 871
thanks
Stopping processing here.
Please contact me if you need assistance.
--
679788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679788
680460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680460
680508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#679968: in ipython shell -- inserts history substitution before the prompt line -- renders python-mode interactive use with ipython unusable
Processing commands for cont...@bugs.debian.org: forwarded 679968 https://bugs.launchpad.net/python-mode/+bug/1020412 Bug #679968 [python-mode] in ipython shell -- inserts history substitution before the prompt line -- renders python-mode interactive use with ipython unusable Set Bug forwarded-to-address to 'https://bugs.launchpad.net/python-mode/+bug/1020412'. thanks Stopping processing here. Please contact me if you need assistance. -- 679968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679665: [Pkg-javascript-devel] Bug#679665: jquery: build-deps not satisfiable in wheezy
On Fri, Jul 6, 2012 at 15:13:41 +0200, Jonas Smedegaard wrote: How does that sound? Too complex at this stage? Very much so, I'm afraid. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 679788 680508
Processing commands for cont...@bugs.debian.org: forcemerge 679788 680508 Bug #679788 [qemu-kvm] kvm-1.0 segfaults with -M pc-1.0 (and older) and vhost-net Bug #680460 [qemu-kvm] KVM crashes with segfault error for kernel linux-3.4.4 AMD64 Bug #680508 [qemu-kvm] /usr/bin/kvm: segfault at 10 ip 7fed4d3bf78e sp 7fed3e364990 error 4 in kvm[7fed4d26+381000] Set Bug forwarded-to-address to 'http://www.spinics.net/lists/kvm/msg75053.html'. Added tag(s) upstream and pending. Bug #680460 [qemu-kvm] KVM crashes with segfault error for kernel linux-3.4.4 AMD64 Merged 679788 680460 680508 thanks Stopping processing here. Please contact me if you need assistance. -- 679788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679788 680460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680460 680508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680518: kdeutils' ark binary got superseded by the ark source package
Package: kdeutils Version: 4:4.7.4-2 Severity: serious wanna-build cc9856fa36ea51dfcc1c451fb9b9b396494a0fe1 for sid on amd64 merge-v3 2012 Jul 06 14:12:42 kdeutils_4:4.7.4-2 (amd64, sid): skipped because binaries (assumed to be) overwritten (ark, 4:4.7.4-2 vs. 4:4.8.4-2) = kdeutils should drop the ark binary -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679827: [chromium]
Package: chromium Version: 20.0.1132.43~r143823-1 I'd also like to confirm this bug on open-source radeon drivers (r600 branch). Reverting to version 18 fixes everything. --- System information. --- Architecture: amd64 Kernel: Linux 3.5.0-rc3 Debian Release: wheezy/sid 950 testing www.deb-multimedia.org 950 testing security.debian.org 950 testing ftp.cz.debian.org 900 unstableftp.cz.debian.org 850 experimentalftp.cz.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== gconf-service | 3.2.5-1 libasound2(= 1.0.16) | libatk1.0-0 (= 1.12.4) | libbz2-1.0| libc6 (= 2.11) | libcairo2 (= 1.6.0) | libcups2 (= 1.4.0) | libdbus-1-3 (= 1.2.14) | libevent-2.0-5 (= 2.0.10-stable) | libexpat1 (= 2.0.1) | libflac8 (= 1.2.1) | libfontconfig1 (= 2.9.0) | libfreetype6 (= 2.3.9) | libgcc1 (= 1:4.1.1) | libgconf-2-4 (= 2.31.1) | libgcrypt11(= 1.4.5) | libgdk-pixbuf2.0-0(= 2.22.0) | libglib2.0-0 (= 2.18.0) | libgnome-keyring0 (= 2.22.2) | libgtk2.0-0 (= 2.24.0) | libjpeg8 (= 8c) | libnspr4(= 2:4.9-2~) | libnss3 (= 2:3.13.4-2~) | OR libnss3-1d(= 3.12.3) | libpango1.0-0 (= 1.20.0) | libpng12-0 (= 1.2.13-4) | libpulse0 (= 0.99.1) | libspeex1(= 1.2~beta3-1) | libstdc++6 (= 4.6) | libudev0 (= 146) | libwebp2 | libx11-6 | libxcomposite1 (= 1:0.3-1) | libxext6 | libxfixes3| libxml2(= 2.7.4) | libxrender1 | libxslt1.1(= 1.1.25) | libxss1 | zlib1g (= 1:1.2.0) | xdg-utils | chromium-inspector| Package's Recommends field is empty. Suggests (Version) | Installed -+-=== chromium-l10n| 20.0.1132.43~r143823-1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680518: kdeutils' ark binary got superseded by the ark source package
Alle venerdì 6 luglio 2012, Philipp Kern ha scritto: wanna-build cc9856fa36ea51dfcc1c451fb9b9b396494a0fe1 for sid on amd64 merge-v3 2012 Jul 06 14:12:42 kdeutils_4:4.7.4-2 (amd64, sid): skipped because binaries (assumed to be) overwritten (ark, 4:4.7.4-2 vs. 4:4.8.4-2) = kdeutils should drop the ark binary Actually, kdeutils will be dropped soon: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664681#115 -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#680460: KVM crashes with segfault error for kernel linux-3.4.4 AMD64
Very sorry for the mistakes as I have never used reportbug before. I have fired up reportbug and submitted the information you requested. Thanks. -- Regards, Hor Jiun Shyong ä½ä¿é On 07/06/2012 06:13 PM, Michael Tokarev wrote: On 06.07.2012 13:25, Hor Jiun Shyong wrote: Where's the kvm command line?? #virsh start diaoyudao Hint: I asked for KVM command line, not for VIRSH command line. Where's the output from qemu-kvm bug script? I have installed qemu-kvm-dgb package and set the logging option as below. export LIBVIRT_DEBUGS=1 export LIBVIRT_LOG_OUTPUTS=1:file:virsh.log log_filters=1:libvirt 1:util 1:qemu log_outputs=1:file:/var/log/libvirt/libvirtd.log Under kernel 3.4.4-amd64, (where kvm guest crashes with segfault error), there is no log output for both virsh.log and libvirtd.log when I ran the virsh start command to boot-up the guest.Under kernel 3.2.0-3-amd64, (where kvm guest runs fine) there are output for libvirtd.log . Hint: When you submit a bug against a package using a tool like reportbug, the tool collects the info which is actually useful, both generally (versions of dependent components, version of the kernel etc) and package-specific. As I mentioned already, I tempted to close this bugreport rigth away due to lack of basic information, but instead asked you to provide the required info. You provided no info I asked you about. However, Haruo Kinoshita provided the missing bits for you. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680460: KVM crashes with segfault error for kernel linux-3.4.4 AMD64
Package: qemu-kvm Version: 1.1~z0+dfsg-1 Followup-For: Bug #680460 -- Package-specific info: /proc/cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 6 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 pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 1 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 6 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 pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 2 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 6 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 pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 3 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 6 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 pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.4 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-kvm depends on: ii adduser 3.113+nmu3 ii ipxe1.0.0+git-20120202.f6840ba-3 ii ipxe-qemu 1.0.0+git-20120202.f6840ba-3 ii libaio1 0.3.109-3 ii libasound2 1.0.25-3
Bug#680520: superseded by libtext-bibtex-perl
Package: libbtparse Version: 0.34-3 Severity: serious libbtparse-dev got taken over by src:libtext-bibtex-perl and builds a newer SONAME of libbtparse. I guess that src:libbtparse should hence be removed. signature.asc Description: Digital signature
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, in order to apply George's patch anyway, i have tried to disable libburn so that growisofs would be used with DVD. No success. Both, growisofs and libburn are enabled but also greyed, so that i cannot change their checkboxes. Whatever, just in case it brings any new insight: $ cd brasero-2.30.3 $ mv ~/check-child-status debian/patches/check-child-status $ echo check-child-status debian/patches/series $ dpkg-buildpackage ... time enough for a tea break ... # apt-get --purge remove brasero # apt-get install libbrasero-media0 # dpkg -i brasero_2.30.3-2_amd64.deb $ brasero Well, it still burns readable DVD. How to get a log file ? Just try burning another DVD, fail, and get offered to save a log. Life is so easy ... :)) It still uses libburn, not growisofs. But no further insight: + BRASERO_JOB_LOG (data, process exited with status %d, WEXITSTATUS (status)); + BRASERO_JOB_LOG (data, process killed by signal %d, WTERMSIG(status)); + BRASERO_JOB_LOG (data, process stopped by signal %d, WSTOPSIG(status)); The word process does not appear in the log of the failed run. It did not get that far, i assume. + printf(process exited, status=%d\n, WEXITSTATUS(status)); + printf(process killed by signal %d\n, WTERMSIG(status)); + printf(process stopped by signal %d\n, WSTOPSIG(status)); Nothing to see of those in xterm where i started brasero. Not with the successful runs either. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663989: marked as done (snappea: needs tight dependency on python)
Your message dated Fri, 06 Jul 2012 14:47:41 + with message-id e1sn9or-0007bw...@franck.debian.org and subject line Bug#663989: fixed in snappea 3.0d3-22 has caused the Debian Bug report #663989, regarding snappea: needs tight dependency on python to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 663989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: snappea Version: 3.0d3-20 Severity: serious Justification: Debian Policy 3.5, Python Policy 3.1.1 snappea includes a private Python extension module (/usr/lib/snappea/SnapPeaC.so). Such extensions are normally not binary compatible across different Python versions, so the package must declare tight dependency on the version for which the extensions was built. -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: snappea Source-Version: 3.0d3-22 We believe that the bug you reported is fixed in the latest version of snappea, which is due to be installed in the Debian FTP archive: snappea-dev_3.0d3-22_i386.deb to main/s/snappea/snappea-dev_3.0d3-22_i386.deb snappea_3.0d3-22.diff.gz to main/s/snappea/snappea_3.0d3-22.diff.gz snappea_3.0d3-22.dsc to main/s/snappea/snappea_3.0d3-22.dsc snappea_3.0d3-22_i386.deb to main/s/snappea/snappea_3.0d3-22_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 663...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman sc...@kitterman.com (supplier of updated snappea package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 06 Jul 2012 10:20:00 -0400 Source: snappea Binary: snappea snappea-dev Architecture: source i386 Version: 3.0d3-22 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Scott Kitterman sc...@kitterman.com Description: snappea- program for creating and studying hyperbolic 3-manifolds snappea-dev - development files for SnapPea hyperbolic 3-manifold tool Closes: 663989 Changes: snappea (3.0d3-22) unstable; urgency=low . * QA upload. * Switch from a very odd combination of the utterly obsolete dh_python and the merely deprecated dh_pycentral to dh_python2 so dependencies are generated correctly (Closes: #663989) - Adjust python related build-depends, drop python-central from build- depends, and change the obsolete XS-Python-Version: current field to X-Python-Version to the correct Python is used - Update debian/rules to use dh_python2 Checksums-Sha1: 3b473f3a1450e4e22467da74a13bbf3777cb9f8e 1078 snappea_3.0d3-22.dsc 21bae38faaf9f302e8b572ab189d6873b33793e6 635523 snappea_3.0d3-22.diff.gz 680bdec451786016d4c44dc9ba77c0c3ac3f6319 638418 snappea_3.0d3-22_i386.deb 4c847829c582a7ef9fbc75321e3b42c666f14491 290224 snappea-dev_3.0d3-22_i386.deb Checksums-Sha256: 4ba7103d0da9f52c4fae749cc67c65e70a9bc51eacee424c5df22a1586dd63e7 1078 snappea_3.0d3-22.dsc 099d05477940390b40893ae132aa30124cb1a8803205cb7c0e804012a10fc86a 635523 snappea_3.0d3-22.diff.gz b949859379e8d8b72f7501ba2f0b40c11aab4ab8214f467ae516ae5eaf064734 638418 snappea_3.0d3-22_i386.deb 298c40c5a2dde718153567206a6e4259f0f6164f955af809e30131e704ab9e29 290224 snappea-dev_3.0d3-22_i386.deb Files: 7c548b375869cc5663800a2b9b430b95 1078 math extra snappea_3.0d3-22.dsc ce16e6bef38119607c27231dcfab04ff 635523 math extra snappea_3.0d3-22.diff.gz 44a7854c64974fb62de22a0d8af2cbb3 638418 math extra snappea_3.0d3-22_i386.deb 31753bdbc5b222174d5021609be80c09 290224 libdevel extra snappea-dev_3.0d3-22_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/291EACgkQHajaM93NaGo+HgCcCQr//pYRLVd+ritu1ItS151o j+IAoJTkXkMtu+b0AFV4ultcb4hnRRka =ugW7 -END PGP SIGNATURE- ---End Message---
Bug#665894: marked as done (python-dateutil: missing source for zone info database)
Your message dated Fri, 06 Jul 2012 14:47:35 + with message-id e1sn9ol-0007am...@franck.debian.org and subject line Bug#665894: fixed in python-dateutil 1.5+dfsg-0.1 has caused the Debian Bug report #665894, regarding python-dateutil: missing source for zone info database 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.) -- 665894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-dateutil Version: 1.5-1 Severity: serious Justification: Policy 2.1 dateutil/zoneinfo/zoneinfo-2010g.tar.gz contains pre-compiled zone info database, but no source for it is included in the .orig.tar. -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: python-dateutil Source-Version: 1.5+dfsg-0.1 We believe that the bug you reported is fixed in the latest version of python-dateutil, which is due to be installed in the Debian FTP archive: python-dateutil_1.5+dfsg-0.1.debian.tar.gz to main/p/python-dateutil/python-dateutil_1.5+dfsg-0.1.debian.tar.gz python-dateutil_1.5+dfsg-0.1.dsc to main/p/python-dateutil/python-dateutil_1.5+dfsg-0.1.dsc python-dateutil_1.5+dfsg-0.1_all.deb to main/p/python-dateutil/python-dateutil_1.5+dfsg-0.1_all.deb python-dateutil_1.5+dfsg.orig.tar.gz to main/p/python-dateutil/python-dateutil_1.5+dfsg.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 665...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman sc...@kitterman.com (supplier of updated python-dateutil package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 06 Jul 2012 09:00:45 -0400 Source: python-dateutil Binary: python-dateutil Architecture: source all Version: 1.5+dfsg-0.1 Distribution: unstable Urgency: low Maintainer: Guido Günther a...@sigxcpu.org Changed-By: Scott Kitterman sc...@kitterman.com Description: python-dateutil - powerful extensions to the standard datetime module Closes: 665894 Changes: python-dateutil (1.5+dfsg-0.1) unstable; urgency=low . * Non-maintainer upload. * Repack upstream tarball to remove non-free time zone information (sourceless binary data) (Closes: #665894) * Remove reference to dateutil/zoneinfo/zoneinfo-2010g.tar.gz from both upstream build system and debian/rules - The file was not shipped in the binary, so there's no impact on the functionality of the package Checksums-Sha1: 66f059061466940ee7ce0ce19ec9045181927728 1296 python-dateutil_1.5+dfsg-0.1.dsc c39a3f28c47e1e5a9f3ff2fb430c9d529246ef75 65637 python-dateutil_1.5+dfsg.orig.tar.gz 18ef09952e85e5c31313d1321e16a3e73d9f8166 8079 python-dateutil_1.5+dfsg-0.1.debian.tar.gz f6b24c4980fa4a8506be7e90ad4babd5fdd09734 55300 python-dateutil_1.5+dfsg-0.1_all.deb Checksums-Sha256: 0833a4b5151c393a8ef7751cf27fc8b8bb490dba2fec83ffc68c50a028a355db 1296 python-dateutil_1.5+dfsg-0.1.dsc 511a0d786a66d7e27e3b44a6ab7ba54c00c7ada10fff053afc9631dabbd47e6f 65637 python-dateutil_1.5+dfsg.orig.tar.gz d20baf2b1a57b8cb8ccda73894c351f8b7cf61eb3a4b87e37183fdb598efda98 8079 python-dateutil_1.5+dfsg-0.1.debian.tar.gz fd6318e4689230a6a0c26ba411cd5ac75228ab2d8b80331ab76e445f7cd3b597 55300 python-dateutil_1.5+dfsg-0.1_all.deb Files: eddbca6bc3a32ffea751c86bf1a92918 1296 python optional python-dateutil_1.5+dfsg-0.1.dsc a91da6f9111deee137e807ba4c88b2ae 65637 python optional python-dateutil_1.5+dfsg.orig.tar.gz 9389f4e769a91442e1658c1c0107aa15 8079 python optional python-dateutil_1.5+dfsg-0.1.debian.tar.gz e6ef38c3bb98539202ef03b3f7ff0302 55300 python optional python-dateutil_1.5+dfsg-0.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/28bwACgkQHajaM93NaGpVIwCgmGHzoRHnVY/P9paJ1B1wSrb6 t00An317xW/u6cwsp+FqSutx/sefU/Ov =9tYy -END PGP SIGNATURE- ---End Message---
Bug#672167: [Pkg-fonts-devel] Bug#672167: fonts-bpg-georgian: fails to upgrade from 'testing' - trying to overwrite /usr/share/fonts/truetype/fonts-bpg-georgian/BPG_Rioni.ttf
On Wed, May 09, 2012 at 10:40:47AM +0200, Christian PERRIER wrote: Quoting Andreas Beckmann (deb...@abeckmann.de): Package: fonts-bpg-georgian Version: 0.5a-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'unstable' fails because it tries to overwrite files that are owned by other packages without declaring a Breaks/Replaces relation. Thanks for catching it. This is entirely my fault by doing a badly prepared update when I was renaming all ttf-* packages to fonts-* A fixed package is on its way. *poke* :-) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680520: superseded by libtext-bibtex-perl
Hi Philipp On Fri, Jul 06, 2012 at 08:34:01AM -0600, Philipp Kern wrote: Package: libbtparse Version: 0.34-3 Severity: serious libbtparse-dev got taken over by src:libtext-bibtex-perl and builds a newer SONAME of libbtparse. I guess that src:libbtparse should hence be removed. Thanks for the pointer! This should be correct, there was a discussion about this some time ago on the debian-perl list[1]. [1]: https://lists.debian.org/debian-perl/2012/03/msg1.html Regards, Salvatore signature.asc Description: Digital signature
Bug#666280: marked as done (jlint: FTBFS: jlint.cc:299:50: error: invalid conversion from 'const char*' to 'char*' [-fpermissive])
Your message dated Fri, 06 Jul 2012 15:02:16 + with message-id e1sna2y-xi...@franck.debian.org and subject line Bug#666280: fixed in jlint 3.0-4.5 has caused the Debian Bug report #666280, regarding jlint: FTBFS: jlint.cc:299:50: error: invalid conversion from 'const char*' to 'char*' [-fpermissive] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 666280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jlint Version: 3.0-4.4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a newer dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: g++ -c -Wall -O2 -g jlint.cc jlint.cc: In function 'void format_message(int, const utf_string, int, __va_list_tag*)': jlint.cc:185:29: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] jlint.cc:197:31: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] jlint.cc:240:68: warning: field precision specifier '.*' expects argument of type 'int', but argument 3 has type 'long int' [-Wformat] jlint.cc: In function 'void set_class_source_path(class_desc*)': jlint.cc:299:50: error: invalid conversion from 'const char*' to 'char*' [-fpermissive] jlint.cc: In function 'bool parse_class_file(byte*)': jlint.cc:431:9: warning: unused variable 'desc_index' [-Wunused-variable] jlint.cc:496:13: warning: unused variable 'max_stack' [-Wunused-variable] jlint.cc:325:7: warning: unused variable 'minor_version' [-Wunused-variable] jlint.cc:327:7: warning: unused variable 'major_version' [-Wunused-variable] jlint.cc: In function 'int main(int, char**)': jlint.cc:1086:50: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] make[1]: *** [jlint.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/jlint_3.0-4.4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: jlint Source-Version: 3.0-4.5 We believe that the bug you reported is fixed in the latest version of jlint, which is due to be installed in the Debian FTP archive: jlint-doc_3.0-4.5_all.deb to main/j/jlint/jlint-doc_3.0-4.5_all.deb jlint_3.0-4.5.diff.gz to main/j/jlint/jlint_3.0-4.5.diff.gz jlint_3.0-4.5.dsc to main/j/jlint/jlint_3.0-4.5.dsc jlint_3.0-4.5_i386.deb to main/j/jlint/jlint_3.0-4.5_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 666...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luk Claes l...@debian.org (supplier of updated jlint package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 06 Jul 2012 02:53:01 + Source: jlint Binary: jlint jlint-doc Architecture: source all i386 Version: 3.0-4.5 Distribution: unstable Urgency: low Maintainer: Ganesan Rajagopal rgane...@debian.org Changed-By: Luk Claes l...@debian.org Description: jlint - A Java Program Checker jlint-doc - Manual for jlint - a Java Program Checker Closes: 666280 Changes: jlint (3.0-4.5) unstable; urgency=low . * Non-maintainer upload. * Fix makefile target dependencies (Closes: #666280). Checksums-Sha1: b34db6de71a53499dfcbfd112b196cb46deab53a 1058 jlint_3.0-4.5.dsc 2029d6a04a6bdeed6a75c153e0455262011b4d89 5596 jlint_3.0-4.5.diff.gz b3093b2d87f1887ee87ffb02633de63638ec103b 188152 jlint-doc_3.0-4.5_all.deb 86fb7a715edfcda04f2fddde1fbf57a024ab3d41 59898 jlint_3.0-4.5_i386.deb Checksums-Sha256:
Bug#666362: marked as done (jless: FTBFS: autoheader: Use AC_DEFINE([CS_REGEX], [], [Description]))
Your message dated Fri, 06 Jul 2012 15:02:10 + with message-id e1sna2s-w7...@franck.debian.org and subject line Bug#666362: fixed in jless 382-iso262-2.1 has caused the Debian Bug report #666362, regarding jless: FTBFS: autoheader: Use AC_DEFINE([CS_REGEX], [], [Description]) 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.) -- 666362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jless Version: 382-iso262-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' cd . autoheader autoheader: warning: missing template: CS_REGEX autoheader: Use AC_DEFINE([CS_REGEX], [], [Description]) autoheader: warning: missing template: HAVE_POSIX_REGCOMP_CS autoheader: warning: missing template: HAVE_V8_REGCOMP_CS autoheader: warning: missing template: MSB_ENABLE make[1]: *** [configure] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/jless_382-iso262-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: jless Source-Version: 382-iso262-2.1 We believe that the bug you reported is fixed in the latest version of jless, which is due to be installed in the Debian FTP archive: jless_382-iso262-2.1.diff.gz to main/j/jless/jless_382-iso262-2.1.diff.gz jless_382-iso262-2.1.dsc to main/j/jless/jless_382-iso262-2.1.dsc jless_382-iso262-2.1_i386.deb to main/j/jless/jless_382-iso262-2.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 666...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luk Claes l...@debian.org (supplier of updated jless package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 06 Jul 2012 02:40:57 + Source: jless Binary: jless Architecture: source i386 Version: 382-iso262-2.1 Distribution: unstable Urgency: low Maintainer: Tatsuki Sugiura s...@nemui.org Changed-By: Luk Claes l...@debian.org Description: jless - A file pager program, similar to more(1) supporting ISO2022 Closes: 666362 Changes: jless (382-iso262-2.1) unstable; urgency=low . * Non-maintainer upload. * Fix AC_DEFINEs (Closes: #666362). Checksums-Sha1: 3cc51210952844056501eff61f8f5678558962c0 1073 jless_382-iso262-2.1.dsc 52df4d82151c7d0b7aeb1f6713ef13b0957dec06 125416 jless_382-iso262-2.1.diff.gz 7277bcaacb5c1634ca75d672c285dd7f682e330f 134704 jless_382-iso262-2.1_i386.deb Checksums-Sha256: 142dbf7741d0d7b4b3825ec402eb494d8dc4cea78172d353098fdd444ff98c81 1073 jless_382-iso262-2.1.dsc 972f3852a065ca5b9fd32c5c16bdb47d73884c95b4b9211618e41193526ae790 125416 jless_382-iso262-2.1.diff.gz 24aa4f080045043669dfd2d1391fa51ff8fc2b38e9ff92bc786da730533e7682 134704 jless_382-iso262-2.1_i386.deb Files: 98695229ef0532139be8dc95752f9b22 1073 text extra jless_382-iso262-2.1.dsc c33d828a8a509fdf47787d9c7847bbdd 125416 text extra jless_382-iso262-2.1.diff.gz 06d69ae89d1514247ef47f1373d0a67f 134704 text extra jless_382-iso262-2.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk/2+pwACgkQ+C5cwEsrK5615wCeO9jHbJ59rByPWbsegQQcW0Kl 3bYAoMNCwJbPD9cXZ/lBPYyQ18gOL1Ze =APgS -END PGP SIGNATURE- ---End Message---
Bug#608981: Crash with long GGI_DISPLAY environment variable
On Mon, Jan 17, 2011 at 12:27:15AM +0100, Julien Cristau wrote: user release.debian@packages.debian.org usertag 608981 squeeze-can-defer tag 608981 squeeze-ignore kthxbye On Fri, Jan 14, 2011 at 23:35:48 +0100, Moritz Mühlenhoff wrote: reassign 608981 libggi2 thanks On Wed, Jan 05, 2011 at 04:16:36PM +1100, Silvio Cesare wrote: Package: zhcon Version: 1:0.2.6-5.2 Severity: important Tags: security zhcon crashes when a long GGI_DISPLAY environment variable is used with ggi. Probably indicative of a buffer overflow. zhcon is SUID root, so this crash might potentially lead to privilege escalation. I haven't investigated further, so it is possible that this is a non exploitable crash. That's a but in libggi, not zhcon. Reassining. Can be fixed through security post release, so tagging as not a blocker. If anyone wants this fixed before the release, they need to upload *now*. A note to Wheezy bug hunters; I'm proceeding with the removal of libggi for Wheezy. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680515: Merging
severity 680514 grave merge 680514 680515 thanks A MTA issue caused me to think the first one hadn't gone through. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Merging
Processing commands for cont...@bugs.debian.org: severity 680514 grave Bug #680514 [xserver-xorg-video-intel] xserver-xorg-video-intel: X locks up with EQ overflow Severity set to 'grave' from 'critical' merge 680514 680515 Bug #680514 [xserver-xorg-video-intel] xserver-xorg-video-intel: X locks up with EQ overflow Bug #680515 [xserver-xorg-video-intel] xserver-xorg-video-intel: Frequent hangs with EQ overflowing Merged 680514 680515 thanks Stopping processing here. Please contact me if you need assistance. -- 680514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680514 680515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Road map (was: Brasero corrupts all blank CD-R when burning)
Dear Thomas, thank you for your effort. Unfortunately no one affected by this problem has replied yet. (Although we should give them some more time to reply. Other things might be more important currently.) Until then I suggest to not bother anymore with that problem. If we do not get anymore replies during the next two weeks, I suggest to split up the Debian bug report. The first one of rpnpif, downgrade the severity to important and mark it as unreproducible as it worked for you. Simon’s answer is probably the other bug about stopping at half time/size which also is dealt with at the Launchpad report. This seems to be an issue with newer versions and that help and more information are needed to fix it. Thanks, Paul signature.asc Description: This is a digitally signed message part
Bug#679788: kvm-1.0 segfaults with -M pc-1.0 (and older) and vhost-net
On 06.07.2012 18:01, Laurent Bigonville wrote: severity 679788 serious severity 680508 serious merge 680508 679788 thanks Hi, I'm setting the severity of these bugs to serious (not critical as it's not completely broken). I really have the feeling that this cannot migrate to testing before the problem is fixed as libvirt is quite wildly used in conjunction with kvm. Hmm. I thought exactly the opposite - to let this version to enter testing before uploading the next batch of fixes, so that more testing in various obscure situations (which I didn't find myself) will be possible, and at the same time to have even more bugfixes... since the issue has a rather trivial workaround. But now when I see how many bugreports like this is flowing in, maybe you're right and it is really necessary to fix it while it is in sid. It is more work for the release team, but heck, less work and frustration for users... Oh well. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 666196 in 3.9.5-4
Processing commands for cont...@bugs.debian.org: notfound 666196 3.9.5-4 Bug #666196 [zorp] zorp: Missing dependency on python-radix No longer marked as found in versions zorp/3.9.5-4. thanks Stopping processing here. Please contact me if you need assistance. -- 666196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 666196 in 3.9.5-4
Processing commands for cont...@bugs.debian.org: fixed 666196 3.9.5-4 Bug #666196 [zorp] zorp: Missing dependency on python-radix Marked as fixed in versions zorp/3.9.5-4. thanks Stopping processing here. Please contact me if you need assistance. -- 666196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666196: marked as done (zorp: Missing dependency on python-radix)
Your message dated Fri, 06 Jul 2012 11:18:46 -0400 with message-id 2100991.9dmWqTVL08@scott-latitude-e6320 and subject line Not sure why this got reopened has caused the Debian Bug report #666196, regarding zorp: Missing dependency on python-radix 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.) -- 666196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: zorp Version: 3.9.5-3 Severity: serious Justification: Policy 7.2 Zorp's /usr/share/zorp/pylib/Zorp/Zone.py imports 'radix', which is provided by the python-radix package. Without that installed, attempting to start zorp will result in an import error and a backtrace. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zorp depends on: ii adduser 3.113+nmu1 ii libc6 2.13-26 ii libglib2.0-02.30.2-6 ii libssl1.0.0 1.0.0g-1 ii libzorp3.9 3.9.5-3 ii libzorpll3.9-1 3.9.1.3-1 ii python 2.7.2-10 ii python-dns 2.3.6-1 ii python-kzorp3.9.5-3 ii python-openssl 0.13-1 ii python-support 1.0.14 zorp recommends no packages. Versions of packages zorp suggests: pn zorp-doc none pn zorp-modules none -- Configuration Files: /etc/zorp/instances.conf.sample [Errno 13] Permission denied: u'/etc/zorp/instances.conf.sample' /etc/zorp/policy.py.sample [Errno 13] Permission denied: u'/etc/zorp/policy.py.sample' /etc/zorp/zorpctl.conf [Errno 13] Permission denied: u'/etc/zorp/zorpctl.conf' -- no debconf information ---End Message--- ---BeginMessage--- I checked and zorp depends on python-radix in both Sid and Wheezy. signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#659061: brasero: segfaults when creating a subfolder
I tried it in version 3.4.1 and I can no longer reproduce it. Great! Thanks Simon Am 28.06.2012 00:20, schrieb Michael Biebl: Hi, I can't reproduce this problem with 3.4.1 (the current version in sid). Could you please try again and check if the problem is fixed for you, too? Michael -- 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#674908: [sparc] iceweasel: JavaScript crash on some sites
Processing commands for cont...@bugs.debian.org: retitle 674908 [sparc] iceweasel: JavaScript crash on some sites Bug #674908 [iceweasel] iceweasel crashes on several websites Changed Bug title to '[sparc] iceweasel: JavaScript crash on some sites' from 'iceweasel crashes on several websites' thanks Stopping processing here. Please contact me if you need assistance. -- 674908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Road map (was: Brasero corrupts all blank CD-R, when burning)
I'll give this patch a try this afternoon. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Road map (was: Brasero corrupts all blank CD-R, when burning)
I'll give the patch a try this afternoon. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680484: gmap and scotch: error when trying to install together
On Fri, 2012-07-06 at 11:14 +0200, Andreas Beckmann wrote: Package: gmap,scotch Version: scotch/5.1.12b.dfsg-1.1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2012-06-16 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: Selecting previously unselected package scotch. Unpacking scotch (from .../scotch_5.1.12b.dfsg-1.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/scotch_5.1.12b.dfsg-1.1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/gmap.1.gz', which is also in package gmap 2012-06-12-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/scotch_5.1.12b.dfsg-1.1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/gmap usr/share/man/man1/gmap.1.gz This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. - Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. Hi, I just upload a fix on Debian science git. Hope it helps Best C -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679665: [Pkg-javascript-devel] Bug#679665: jquery: build-deps not satisfiable in wheezy
On 12-07-06 at 04:10pm, Julien Cristau wrote: On Fri, Jul 6, 2012 at 15:13:41 +0200, Jonas Smedegaard wrote: How does that sound? Too complex at this stage? Very much so, I'm afraid. Could you elaborate a bit? Please note that only first part is relevant now (and later parts are optional). - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#680536: openvswitch - Fails to start without /etc/protocols
Package: openvswitch Version: 1.4.2+git20120612-2 Severity: serious The openvswitch-switch init script fails to start stuff if /etc/protocols is missing. This file is provided by the non-essential netbase, so it needs a dependency. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680537: openvswitch - Plays with iptables without consent
Package: openvswitch Version: 1.4.2+git20120612-2 Severity: serious The openvswitch-switch init script modifies filter rules using iptables without consent by the admin. Bastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, Paul Menzel wrote: Until then I suggest to not bother anymore with that problem. It gives libisofs a bad name. Probably the squeeze Brasero is two notches too old. This comment could explain why: https://bugzilla.gnome.org/show_bug.cgi?id=655601#c5 ... Nico Zanferrari 2012-01-16 10:15:30 UTC: ... - the bug started on Brasero version 2.32.1 and it's still ...present in 3.2.x. It was not present in version 2.32.0. ... - it happens on all hw, and all current distros ... - it happens only with on-the-fly burning, which is the ...default option by the way. Mine is 2.30.3 I need instructions how to get into this range of versions. I suggest to split up the Debian bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617409 could well be just a classical 100%-run-but-unreadable problem. Usually caused by bad compatibility of drive and media. The 30%-to-50%-early-burn-end problem in Launchpad is probably the one for which one needs the newer Brasero. It would thus still lurk in Debian sid, rather than in squeeze. So actually one should just deprecate to follow the Launchpad link. I apologize for having fueled that branch. But Debian will possibly get affected by its next release, anyway. https://bugzilla.gnome.org/show_bug.cgi?id=655601 https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117 Be careful with believing in me too confirmations. E.g. https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/788300 is very understandable to me after two days with Brasero. Its flaws together with bad compatibility of drive and media can cause any kind of urban legends. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Road map (was: Brasero corrupts all blank CD-R when burning)
Hello, Sorry for the time to reply. I was busy. Le 6 juillet 2012, Paul Menzel a écrit : thank you for your effort. Unfortunately no one affected by this problem has replied yet. (Although we should give them some more time to reply. Other things might be more important currently.) I have also this issue. Until then I suggest to not bother anymore with that problem. If we do not get anymore replies during the next two weeks, I suggest to split up the Debian bug report. The first one of rpnpif, downgrade the severity to important and mark it as unreproducible as it worked for you. Simon’s answer is probably the other bug about stopping at half time/size which also is dealt with at the Launchpad report. This seems to be an issue with newer versions and that help and more information are needed to fix it. You are perhaps right with the speed that it should not be the problem. xorriso works fine for me with CD-RW and CD-R. I have tried the George's patch. This works fine for CR-RW only but not with CD-R (I have crashed 2 CD-R to confirm). With CD-R, some files are full of 00H. But I have a message at the end of compilation that give the list of the patches and that said for each, that they are removed. Normal ? Regards. -- Alain Rpnpif -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: [Pkg-libburnia-devel] Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
On Friday 06 July 2012 16:43:07 Thomas Schmitt wrote: Hi, Thomas, thank you performing these tests. I think you've done enough already :) in order to apply George's patch anyway, i have tried to disable libburn so that growisofs would be used with DVD. No success. Both, growisofs and libburn are enabled but also greyed, so that i cannot change their checkboxes. Hm, did you try to mess up with gconf-editor (package of the same name)? You can start it, and search for brasero string, that is Ctrl+F... then find brasero/config/priorities and adjust the weights of growisofs and libisofs plugins, so these being higher than the rest. It is not like I'm an expert in this particlar area:P Whatever, just in case it brings any new insight: $ cd brasero-2.30.3 $ mv ~/check-child-status debian/patches/check-child-status $ echo check-child-status debian/patches/series $ dpkg-buildpackage ... time enough for a tea break ... # apt-get --purge remove brasero # apt-get install libbrasero-media0 # dpkg -i brasero_2.30.3-2_amd64.deb $ brasero Well, it still burns readable DVD. How to get a log file ? Just try burning another DVD, fail, and get offered to save a log. Hm, uses libburn and libisofs and you observed a fail? Life is so easy ... :)) It still uses libburn, not growisofs. But no further insight: + BRASERO_JOB_LOG (data, process exited with status %d, WEXITSTATUS (status)); + BRASERO_JOB_LOG (data, process killed by signal %d, WTERMSIG(status)); + BRASERO_JOB_LOG (data, process stopped by signal %d, WSTOPSIG(status)); The word process does not appear in the log of the failed run. It did not get that far, i assume. + printf(process exited, status=%d\n, WEXITSTATUS(status)); + printf(process killed by signal %d\n, WTERMSIG(status)); + printf(process stopped by signal %d\n, WSTOPSIG(status)); Nothing to see of those in xterm where i started brasero. Not with the successful runs either. As I get it from the code brasero_process_watch_child() routine, containing those prints, would only be called when external applications like growisofs are being started in the child process (there are also routines to read their stdout and stderr). Hence, there is no chance to see them in your libburn+libisofs test above. OTOH, in the log file [1] where growisofs was engaged you can see: BraseroGrowisofs process finished with status 0 which is spitted by the original routine brasero_process_watch_child() ... if (waitpid (priv-pid, status, WNOHANG) = 0) return TRUE; priv-return_status = WEXITSTATUS (status); priv-watch = 0; priv-pid = 0; BRASERO_JOB_LOG (data, process finished with status %i, WEXITSTATUS (status)); ... and where is it not actually wait()'ed properly, since the waitpid() could have returned positive value (child's pid) due to the child's change of state, e.g. child being signalled for any (obscure) reason (SIGPIPE, SIGKILL, etc), and also child's exit status is being blindly examined by flat WEXITSTATUS(status), instead of first checking WIFEXITED(status) for returning true, i.e. that the child has actually exited. Thus, the above log message of process finished with status 0 is pretty much bogus in this particular case shown in the log with the burn failure halfway around ~49-50%. (see the tail of waitpid(2) for a good example of a diligent parent waiting for their possibly naughty child) [1] https://launchpadlibrarian.net/71440716/brasero_log.txt -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679586: dia: Fails to run
Hi, just stumbled over this report and have to add a me too to the unreproducable bit, on GNOME only and am64 though. I'd say this should be downgraded to important as the package works for most users and does not actually produce any data loss (or did it erase files while crashing? or crashed *after* you did some work in it?) Regards Evgeni -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning
Hi Sorry I'm overstrained by the Debian infrastructure. ;-) I hit all the reportbug crasher bugs too... But anyway, I updated to brasero 3.4.1 and I can still reproduce the bug. I used a CD-RW and created a data project with one folder with two files in it (about 300MB). I enabled on-the-fly burning (see screen shot). It burned, reported success and failed to eject the CD. The CD contains no valid file system and it can not be mounted. Brasero is also unable to clear the CD. I have to use K3B to format it (strange!). Notes: - Disabling the option Burn the image directly without saving to disc (see screen shot) creates a working CDs (that can be ejected automatically too). - Burning ISO images with brasero works fine. Just today I burned a Debian and an Ubuntu image without problems. - Kernel: Linux 3.2.0-2-amd64 I hope this helps. I will have a look at xorriso... the manpage looks horrible. Any specific parameters I should test? Cheers Simon simon@beutelteufel:~$ brasero brasero (libisofs)DEBUG : Creating low level ECMA-119 tree... brasero (libisofs)DEBUG : Matching hardlinks... brasero (libisofs)DEBUG : Sorting the low level tree... brasero (libisofs)DEBUG : Mangling names... brasero (libisofs)DEBUG : Creating low level Joliet tree... brasero (libisofs)DEBUG : Sorting the Joliet tree... brasero (libisofs)DEBUG : Mangling Joliet names... brasero (libisofs)DEBUG : Computing position of dir structure brasero (libisofs)DEBUG : Computing length of pathlist brasero (libisofs)DEBUG : Computing position of Joliet dir structure brasero (libisofs)DEBUG : Computing length of Joliet pathlist brasero (libisofs)DEBUG : Starting image writing... brasero (libisofs)DEBUG : Write volume descriptors brasero (libisofs)DEBUG : Write Primary Volume Descriptor brasero (libisofs)DEBUG : Write SVD for Joliet brasero (libisofs)DEBUG : Writing ISO Path tables brasero (libisofs)DEBUG : Writing Joliet Path tables brasero (libisofs)DEBUG : Writing Files... brasero (libisofs)DEBUG : Processed 5180 of 103584 KB (5 %) brasero (libisofs)DEBUG : Processed 10360 of 103584 KB (10 %) brasero (libisofs)DEBUG : Processed 15538 of 103584 KB (15 %) brasero (libisofs)DEBUG : Processed 20718 of 103584 KB (20 %) brasero (libisofs)DEBUG : Processed 25896 of 103584 KB (25 %) brasero (libisofs)DEBUG : Processed 31076 of 103584 KB (30 %) brasero (libisofs)DEBUG : Processed 36256 of 103584 KB (35 %) brasero (libisofs)DEBUG : Processed 41434 of 103584 KB (40 %) brasero (libisofs)DEBUG : Processed 46614 of 103584 KB (45 %) brasero (libisofs)DEBUG : Processed 51792 of 103584 KB (50 %) brasero (libisofs)DEBUG : Processed 56972 of 103584 KB (55 %) brasero (libisofs)DEBUG : Processed 62152 of 103584 KB (60 %) brasero (libisofs)DEBUG : Processed 67330 of 103584 KB (65 %) brasero (libisofs)DEBUG : Processed 72510 of 103584 KB (70 %) brasero (libisofs)DEBUG : Processed 77688 of 103584 KB (75 %) brasero (libisofs)DEBUG : Processed 82868 of 103584 KB (80 %) brasero (libisofs)DEBUG : Processed 88048 of 103584 KB (85 %) brasero (libisofs)DEBUG : Processed 93226 of 103584 KB (90 %) brasero (libisofs)DEBUG : Processed 98406 of 103584 KB (95 %) brasero (libisofs)DEBUG : Processed 103584 of 103584 KB (100 %) simon@beutelteufel:~$ sudo mount -t iso9660 -r /dev/cdrom /media/cdrom0 mount: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so [22295.543931] ISO 9660 Extensions: Microsoft Joliet Level 3 [22295.597809] ISO 9660 Extensions: RRIP_1991A [22796.601042] sr 0:0:0:0: [sr0] Device not ready [22796.601048] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [22796.601054] sr 0:0:0:0: [sr0] Sense Key : Not Ready [current] [22796.601060] sr 0:0:0:0: [sr0] Add. Sense: Medium not present [22796.601067] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00 [22796.601079] end_request: I/O error, dev sr0, sector 8 [22796.601086] Buffer I/O error on device sr0, logical block 1 [22796.605512] sr 0:0:0:0: [sr0] Device not ready [22796.605515] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [22796.605520] sr 0:0:0:0: [sr0] Sense Key : Not Ready [current] [22796.605525] sr 0:0:0:0: [sr0] Add. Sense: Medium not present [22796.605532] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00 [22796.605544] end_request: I/O error, dev sr0, sector 8 [22796.605553] Buffer I/O error on device sr0, logical block 1 [22796.606436] sr 0:0:0:0: [sr0] Device not ready [22796.606439] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [22796.606449] sr 0:0:0:0: [sr0] Sense Key : Not Ready [current] [22796.606454] sr 0:0:0:0: [sr0] Add. Sense: Medium not present [22796.606462] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00 [22796.606474] end_request: I/O error, dev sr0, sector 8 [22796.606482] Buffer I/O error on device sr0, logical block 1 [22796.607453] sr
Processed: found 680428 in 3.4.1-3, tagging 680428
Processing commands for cont...@bugs.debian.org: found 680428 3.4.1-3 Bug #680428 [liblapacke-dev] liblapacke-dev: Can not link against liblapacke Marked as found in versions lapack/3.4.1-3. tags 680428 + pending Bug #680428 [liblapacke-dev] liblapacke-dev: Can not link against liblapacke Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 680428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 680414 serious Bug #680414 [src:aircrack-ng] aircrack-ng: FTBFS on most architectures Severity set to 'serious' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 680414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: [Pkg-libburnia-devel] Bug#617409: brasero: Road map (was: Brasero corrupts all blank CD-R when burning)
On Friday 06 July 2012 18:11:19 Alain Rpnpif wrote: Hello, Sorry for the time to reply. I was busy. Hi Alain, and thanks for the feedback! Le 6 juillet 2012, Paul Menzel a écrit : thank you for your effort. Unfortunately no one affected by this problem has replied yet. (Although we should give them some more time to reply. Other things might be more important currently.) I have also this issue. Until then I suggest to not bother anymore with that problem. If we do not get anymore replies during the next two weeks, I suggest to split up the Debian bug report. The first one of rpnpif, downgrade the severity to important and mark it as unreproducible as it worked for you. Simon’s answer is probably the other bug about stopping at half time/size which also is dealt with at the Launchpad report. This seems to be an issue with newer versions and that help and more information are needed to fix it. You are perhaps right with the speed that it should not be the problem. Nod. xorriso works fine for me with CD-RW and CD-R. This is quite useful piece of information! This would keep us sane... well at least we are not on crack with the underlying libburnia libraries :) I have tried the George's patch. This works fine for CR-RW only but not with CD-R (I have crashed 2 CD-R to confirm). With CD-R, some files are full of 00H. Interesting. Now there is something I don't really get: You were using libisofs plugin to talk to the growisofs plugin engaging growisofs as burner application. But to my best knowledge growisofs is only able to burn on DVDs? Could this explain a possible growisofs failure when faced with the task to burn non-DVDs? I'd expected growisofs to be tested with DVDs and to succeed indeed. Btw, any log messages like this one: https://launchpadlibrarian.net/71440716/brasero_log.txt or any printf's on the terminal you have started brasero on? But I have a message at the end of compilation that give the list of the patches and that said for each, that they are removed. Normal ? It is expected. You can also see 'dpkg-source: info:' messages at the begining, saying that unapplied patches listed in 'series' are being applied. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, Alain Rpnpif wrote: This works fine for CR-RW only but not with CD-R (I have crashed 2 CD-R to confirm). With CD-R, some files are full of 00H. This supports the theory of poor compatibility of drive and media. Blank CD-RW and CD-R are handled identically by burn software. They make no difference to the ISO-9660 software either. xorriso works fine for me with CD-RW and CD-R. This weakens said theory. There might be a difference in CD write mode between xorriso and Brasero. SAO versus TAO. Sometimes the one still works whereas the other is already failing. What xorriso commands did you use exactly ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666196: closed by Scott Kitterman deb...@kitterman.com (Not sure why this got reopened)
I checked and zorp depends on python-radix in both Sid and Wheezy. Zorp does, but python-kzorp, which uses python-radix (and does not depend on zorp) does not. The dependency was added, but not to the right package. Granted, python-kzorp is kind-of useless without zorp, but accidentally satisfying dependencies is, well, accidental, and as such, not quite appropriate. On the other hand, this most likely won't affect anyone anyway, so *shrug* -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679447: Coro segfaults
Hi, Marc! I tried to up a project using Coro and stumbled on segfaults in perl Coro. Then I realized my project with AnyEvent (old way), but today I had some time to create test, so I've extracted part of code from my project and placed it here: https://gist.github.com/3059829 I think it segfaults if a module uses weaken refs (trees, iterators, objects that uses AE-watchers, etc), but I can be mistaken. The code segfaults randomly but pretty often. The code segfaults under Perl-5.14.2 and Perl-5.8.8 (I've tested in using perlbrew). Could You analyse the problem? -- . ''`. Dmitry E. Oboukhov : :’ : email: un...@debian.org jabber://un...@uvw.ru `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537 signature.asc Description: Digital signature
Processed: Now occurs on even more archs :-((
Processing commands for cont...@bugs.debian.org:
reopen 679554
Bug #679554 {Done: Helge Kreutzmann deb...@helgefjell.de} [goobox] goobox:
FTBS on mipsel, builds on (almost) all archs fine
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions goobox/3.0.1-3.
found 679554 3.0.1-3
Bug #679554 [goobox] goobox: FTBS on mipsel, builds on (almost) all archs fine
Marked as found in versions goobox/3.0.1-3.
retitle 679554 goobox: FTBS on some architectures (currently mipsel, ia64 and
amd64)
Bug #679554 [goobox] goobox: FTBS on mipsel, builds on (almost) all archs fine
Changed Bug title to 'goobox: FTBS on some architectures (currently mipsel,
ia64 and amd64)' from 'goobox: FTBS on mipsel, builds on (almost) all archs
fine'
# Now this problem happens on even more architectures
retitle 679552 Problems on mipsel, ia64 and amd64: nsgmls:OSFD0:18:0:E:
reference to entity REFENTRY for which no system identifier could be
generated
Bug #679552 [sp] sp: Problems on mipsel: nsgmls:OSFD0:18:0:E: reference to
entity REFENTRY for which no system identifier could be generated
Changed Bug title to 'Problems on mipsel, ia64 and amd64:
nsgmls:OSFD0:18:0:E: reference to entity REFENTRY for which no system
identifier could be generated' from 'sp: Problems on mipsel:
nsgmls:OSFD0:18:0:E: reference to entity REFENTRY for which no system
identifier could be generated'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
679552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679552
679554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666196: closed by Scott Kitterman deb...@kitterman.com (Not sure why this got reopened)
On Friday, July 06, 2012 06:50:37 PM Gergely Nagy wrote: Granted, python-kzorp is kind-of useless without zorp, but accidentally satisfying dependencies is, well, accidental, and as such, not quite appropriate. Fair point. I think it's a bug, but not RC. I'll reopen and lower the severity. Zorp/Zone.py, which is in zorp uses radix, so adding it to zorp was necessary, it use my not have been sufficient. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679761: marked as done (olsrd: FTBFS[kfreebsd]: fatal error: linux/types.h: No such file or directory)
Your message dated Fri, 06 Jul 2012 17:32:17 + with message-id e1snco9-0003na...@franck.debian.org and subject line Bug#679761: fixed in olsrd 0.6.3-4 has caused the Debian Bug report #679761, regarding olsrd: FTBFS[kfreebsd]: fatal error: linux/types.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 679761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:olsrd Version: 0.6.3-3 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: [CC] src/lq_plugin_default_float.c [CC] src/lq_plugin_default_fpm.c [CC] src/main.c src/main.c:65:25: fatal error: linux/types.h: No such file or directory compilation terminated. make[2]: *** [src/main.o] Error 1 make[2]: Leaving directory `/build/buildd-olsrd_0.6.3-3-kfreebsd-amd64-4pNbb2/olsrd-0.6.3' make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory `/build/buildd-olsrd_0.6.3-3-kfreebsd-amd64-4pNbb2/olsrd-0.6.3' make: *** [build-arch] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=olsrdarch=kfreebsd-amd64ver=0.6.3-3stamp=1341076534 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ---End Message--- ---BeginMessage--- Source: olsrd Source-Version: 0.6.3-4 We believe that the bug you reported is fixed in the latest version of olsrd, which is due to be installed in the Debian FTP archive: olsrd-gui_0.6.3-4_i386.deb to main/o/olsrd/olsrd-gui_0.6.3-4_i386.deb olsrd-plugins_0.6.3-4_i386.deb to main/o/olsrd/olsrd-plugins_0.6.3-4_i386.deb olsrd_0.6.3-4.debian.tar.gz to main/o/olsrd/olsrd_0.6.3-4.debian.tar.gz olsrd_0.6.3-4.dsc to main/o/olsrd/olsrd_0.6.3-4.dsc olsrd_0.6.3-4_i386.deb to main/o/olsrd/olsrd_0.6.3-4_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 679...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Stigge sti...@antcom.de (supplier of updated olsrd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 06 Jul 2012 18:58:27 +0200 Source: olsrd Binary: olsrd olsrd-plugins olsrd-gui Architecture: source i386 Version: 0.6.3-4 Distribution: unstable Urgency: low Maintainer: Roland Stigge sti...@antcom.de Changed-By: Roland Stigge sti...@antcom.de Description: olsrd - optimized link-state routing daemon (unik-olsrd) olsrd-gui - GTK GUI to control and get info about olsrd olsrd-plugins - various plugins to enhance olsrd Closes: 679761 Changes: olsrd (0.6.3-4) unstable; urgency=low . * debian/rules: Drop OS=linux from the make call, fixing FTBFS on !linux, thanks to Evgeni Golov (Closes: #679761) Checksums-Sha1: f7c4b88ba88cf3860830f7785a98c09ee7c2580b 1335 olsrd_0.6.3-4.dsc df839fbaf159601efa71dca14475535e96bd71c4 25947 olsrd_0.6.3-4.debian.tar.gz 1ff8eeba93cdb336110da4b7599d8d6a95fb19dd 249044 olsrd_0.6.3-4_i386.deb ebbfe65da8b2db27bcb26ac5c19d24b3e9ca6f58 277904 olsrd-plugins_0.6.3-4_i386.deb fdfefba128a11767e7d53cb61ecfd090e2be60cd 81516 olsrd-gui_0.6.3-4_i386.deb Checksums-Sha256: ea7239e0c6a7372e44f7ea8ca5b08101c9b3da57bb39174711ddd196c6433bf4 1335 olsrd_0.6.3-4.dsc 1b02f918db70844c51f4cfbc4a6b7b678be5eaf5cd283157f743db083fe16c36 25947 olsrd_0.6.3-4.debian.tar.gz a9dba5b93b99dd6b01b6a14f40980a080d7cd241083d6095e951f5f4bcb310b7 249044 olsrd_0.6.3-4_i386.deb cbf39e7b50bcb054a4e17141846c75831fed838be8aa5a94704720bd40450f66 277904 olsrd-plugins_0.6.3-4_i386.deb 4afafe0d2002463972f4ea0d9251536084c732d7041d6a6926d21831b3222f79 81516 olsrd-gui_0.6.3-4_i386.deb Files: ee08bbfa464ede1610b18d47b8ea498f 1335 net extra olsrd_0.6.3-4.dsc 30def6711e33fc9724d29932e887c516 25947 net extra olsrd_0.6.3-4.debian.tar.gz 38e63d0fbea9341ca9bc8dc7fb1a9e1b 249044 net extra olsrd_0.6.3-4_i386.deb 591dec34dcf948e7b7d89e6c8e0e8a1e 277904 net extra
Bug#659061: marked as done (brasero: segfaults when creating a subfolder)
Your message dated Fri, 06 Jul 2012 19:27:00 +0200 with message-id 4ff71fe4.8000...@debian.org and subject line Re: brasero: segfaults when creating a subfolder has caused the Debian Bug report #659061, regarding brasero: segfaults when creating a subfolder 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.) -- 659061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: brasero Version: 3.2.0-3 Severity: serious 1. Create a data project 2. Add a folder with some files in it 3. Select a file inside this folder 4. Press on the new folder button 5. Enter a name and hit enter 6. Segfault Backtrace attached. --- System information. --- Architecture: amd64 Kernel: Linux 3.1.0-1-amd64 Debian Release: wheezy/sid 990 testing security.debian.org 990 testing mirror.switch.ch 500 unstable mirror.switch.ch 500 oneiric ppa.launchpad.net 150 experimental mirror.switch.ch --- Package information. --- Depends (Version) | Installed -+-= libatk1.0-0 (= 1.12.4) | 2.2.0-2 libbrasero-media3-1 (= 3.2.0-3) | 3.2.0-3 libc6 (= 2.4) | 2.13-24 libcairo-gobject2 (= 1.10.0) | 1.10.2-6.2 libcairo2 (= 1.2.4) | 1.10.2-6.2 libfontconfig1 (= 2.8.0) | 2.8.0-3.1 libfreetype6 (= 2.2.1) | 2.4.8-1 libgdk-pixbuf2.0-0 (= 2.22.0) | 2.24.0-2 libglib2.0-0 (= 2.30.0) | 2.30.2-6 libgstreamer-plugins-base0.10-0 (= 0.10.12) | 0.10.35-1 libgstreamer0.10-0 (= 0.10.15) | 0.10.35-1 libgtk-3-0 (= 3.0.0) | 3.2.3-1 libice6 (= 1:1.0.0) | 2:1.0.7-2 libnautilus-extension1a (= 2.91) | 3.2.1-2+b1 libpango1.0-0 (= 1.14.0) | 1.29.4-2 libsm6 | 2:1.2.0-2 libtotem-plparser17 (= 2.32) | 2.32.6-2 libtracker-sparql-0.12-0 (= 0.10.0) | 0.12.9-1+b1 libxml2 (= 2.7.4) | 2.7.8.dfsg-7 gstreamer0.10-plugins-base (= 0.10.0) | 0.10.35-1 gnome-icon-theme | 3.2.1.2-1 gvfs | 1.10.1-2 brasero-common (= 3.2.0-3) | 3.2.0-3 Package's Recommends field is empty. Suggests (Version) | Installed =-+-=== vcdimager | 0.7.23-5 libdvdcss2 | GNU gdb (GDB) 7.3-debian Copyright (C) 2011 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/... Reading symbols from /usr/bin/brasero...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/brasero [Thread debugging using libthread_db enabled] [New Thread 0x7fffe7991700 (LWP 11074)] [New Thread 0x7fffe6f7c700 (LWP 11075)] [Thread 0x7fffe6f7c700 (LWP 11075) exited] [New Thread 0x7fffe6f7c700 (LWP 11076)] [New Thread 0x7fffd7b4b700 (LWP 11083)] [New Thread 0x7fffd7145700 (LWP 11086)] [Thread 0x7fffd7b4b700 (LWP 11083) exited] [New Thread 0x7fffd7b4b700 (LWP 11087)] [Thread 0x7fffd7b4b700 (LWP 11087) exited] Program received signal SIGSEGV, Segmentation fault. g_str_hash (v=0x0) at /tmp/buildd/glib2.0-2.30.2/./glib/gstring.c:142 142 /tmp/buildd/glib2.0-2.30.2/./glib/gstring.c: Datei oder Verzeichnis nicht gefunden. in /tmp/buildd/glib2.0-2.30.2/./glib/gstring.c (gdb) bt #0 g_str_hash (v=0x0) at /tmp/buildd/glib2.0-2.30.2/./glib/gstring.c:142 #1 0x73c766e3 in g_hash_table_lookup_node (hash_return=synthetic pointer, key=0x0, hash_table=0xde34c0) at /tmp/buildd/glib2.0-2.30.2/./glib/ghash.c:360 #2 g_hash_table_lookup (hash_table=0xde34c0, key=0x0) at /tmp/buildd/glib2.0-2.30.2/./glib/ghash.c:1029 #3 0x77987143 in brasero_data_project_rename_node () from /usr/lib/libbrasero-burn3.so.1 #4 0x0043f67f in ?? () #5 0x74558804 in g_closure_invoke (closure=0xdd1870, return_value=0x0, n_param_values=3, param_values=0x12ac0f0, invocation_hint=optimized out) at /tmp/buildd/glib2.0-2.30.2/./gobject/gclosure.c:774 #6 0x7456a78a in signal_emit_unlocked_R (node=optimized out, detail=0, instance=0xdcf5a0, emission_return=0x0, instance_and_params=0x12ac0f0) at /tmp/buildd/glib2.0-2.30.2/./gobject/gsignal.c:3272 #7 0x74573e11 in g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=optimized out) at /tmp/buildd/glib2.0-2.30.2/./gobject/gsignal.c:3003 #8 0x74573fb2 in g_signal_emit (instance=optimized out, signal_id=optimized out, detail=optimized out) at
Processed: notfixed 666196 in 3.9.5-4
Processing commands for cont...@bugs.debian.org:
notfixed 666196 3.9.5-4
Bug #666196 {Done: Scott Kitterman deb...@kitterman.com} [zorp] zorp: Missing
dependency on python-radix
No longer marked as fixed in versions zorp/3.9.5-4.
severity 666196 normal
Bug #666196 {Done: Scott Kitterman deb...@kitterman.com} [zorp] zorp: Missing
dependency on python-radix
Severity set to 'normal' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
666196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680520: superseded by libtext-bibtex-perl
reassign 680520 ftp.debian.org retitle 680520 RM: libbtparse -- RoQA; package superseded severity 680520 normal thanks On Fri, 06 Jul 2012 08:34:01 -0600, Philipp Kern wrote: Package: libbtparse Version: 0.34-3 Severity: serious libbtparse-dev got taken over by src:libtext-bibtex-perl and builds a newer SONAME of libbtparse. I guess that src:libbtparse should hence be removed. Right, thanks for noticing! This should have happened back in March, when we thought this happen automatically. Wrong guess :) The previous maintainer has agreed to the removal already: https://lists.debian.org/debian-perl/2012/01/msg00085.html https://lists.debian.org/debian-perl/2012/03/msg1.html This also involves removing libtext-bibtex-perl | 0.38-1+b2 | unstable | hurd-i386 Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- signature.asc Description: Digital signature
Processed: Re: Bug#680520: superseded by libtext-bibtex-perl
Processing commands for cont...@bugs.debian.org: reassign 680520 ftp.debian.org Bug #680520 [libbtparse] superseded by libtext-bibtex-perl Bug reassigned from package 'libbtparse' to 'ftp.debian.org'. No longer marked as found in versions 0.34-3. Ignoring request to alter fixed versions of bug #680520 to the same values previously set retitle 680520 RM: libbtparse -- RoQA; package superseded Bug #680520 [ftp.debian.org] superseded by libtext-bibtex-perl Changed Bug title to 'RM: libbtparse -- RoQA; package superseded' from 'superseded by libtext-bibtex-perl' severity 680520 normal Bug #680520 [ftp.debian.org] RM: libbtparse -- RoQA; package superseded Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 680520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 679447 is forwarded to schm...@schmorp.de
Processing commands for cont...@bugs.debian.org: forwarded 679447 schm...@schmorp.de Bug #679447 [libcoro-perl] libcoro-perl often segfaults Set Bug forwarded-to-address to 'schm...@schmorp.de'. thanks Stopping processing here. Please contact me if you need assistance. -- 679447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 660259 in 1.4.1-3
Processing commands for cont...@bugs.debian.org: found 660259 1.4.1-3 Bug #660259 [libmpich2-dev] mpich2: FTBFS: [sparc] missing files Bug #666140 [libmpich2-dev] mpich2: FTBFS: dh_install: libmpich2-3 missing files (usr/lib/libmpich.so.3*), aborting Marked as found in versions mpich2/1.4.1-3. Marked as found in versions mpich2/1.4.1-3. thanks Stopping processing here. Please contact me if you need assistance. -- 660259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660259 666140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)
Hi, Hm, did you try to mess up with gconf-editor Not yet. But i try now:. I do not see an alternative to apps|brasero|config|priority|libisofs-image Well i now set apps|brasero|config|priority|growisofs-burn 1 This did not change anything. Now growisofs process to see while the DVD burn is going on. I try: apps|brasero|config|priority|libburn-burn 2 (At the second try the setting becomes persistent.) No growisofs process to spot. Sigh. apps|brasero|filter|hidden could be to blame for the missing dot-files. Yes. It is. So my results now pass diff -r without much complaints. But it is not flawless yet. An empty directory is still missing on the DVD: libburn_dir/hurd-git/gnumach/.git/refs/tags Hm, uses libburn and libisofs and you observed a fail? A failure to properly recognize the state of the loaded medium after a first run succeeded and ended in the well-known Brasero failure to eject. After this, the program is quite unusable and has to be ended. I purposely did try another burn, just to get offered the log. Regrettably i cannot provoke a log with a successful run. I roughly understand your theory about WEXITSTATUS. It would explain why Brasero stops to transfer more data. But without being able to engage growisofs, it will be hard to examine. So how do i upgrade libisofs, libburn and Brasero to sid ? How do i enable use of growisofs ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
