Bug#703332: If they are API compatible you MUST generate and install a GAC policy file!
On Tue, Apr 2, 2013 at 1:04 AM, Jonathan Wiltshire j...@debian.org wrote: As mummy/1.0.3-2 is unsuitable for Wheezy please could you prepare a backport of your patch for an upload to testing-proposed-updates, and submit a debdiff to the release team for approval. 1.0.2-5 will transition to Wheezy... 1.0.3-2 should be blocked by freeze, correct ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 704486 in libobject-authority-perl/0.4-1
Processing commands for cont...@bugs.debian.org: found 704486 libobject-authority-perl/0.4-1 Bug #704486 [libobject-authority-perl,librole-commons-perl] librole-commons-perl: trying to overwrite '/usr/share/perl5/Object/AUTHORITY.pm', which is also in package libobject-authority-perl 0.004-1 The source libobject-authority-perl and version 0.4-1 do not appear to match any binary packages Marked as found in versions libobject-authority-perl/0.4-1. thanks Stopping processing here. Please contact me if you need assistance. -- 704486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704486 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 704486 in librole-commons-perl/0.101-1
Processing commands for cont...@bugs.debian.org: found 704486 librole-commons-perl/0.101-1 Bug #704486 [libobject-authority-perl,librole-commons-perl] librole-commons-perl: trying to overwrite '/usr/share/perl5/Object/AUTHORITY.pm', which is also in package libobject-authority-perl 0.004-1 Marked as found in versions librole-commons-perl/0.101-1. thanks Stopping processing here. Please contact me if you need assistance. -- 704486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704486 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: reassign 704486 to libobject-authority-perl,librole-commons-perl
Processing commands for cont...@bugs.debian.org: reassign 704486 libobject-authority-perl,librole-commons-perl Bug #704486 [librole-commons-perl] librole-commons-perl: trying to overwrite '/usr/share/perl5/Object/AUTHORITY.pm', which is also in package libobject-authority-perl 0.004-1 Bug reassigned from package 'librole-commons-perl' to 'libobject-authority-perl,librole-commons-perl'. No longer marked as found in versions librole-commons-perl/0.101-1. Ignoring request to alter fixed versions of bug #704486 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 704486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704486 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#704486: librole-commons-perl: trying to overwrite '/usr/share/perl5/Object/AUTHORITY.pm', which is also in package libobject-authority-perl 0.004-1
Same on amd64/sid. -Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703332: If they are API compatible you MUST generate and install a GAC policy file!
On 02.04.2013 07:53, Mathieu Malaterre wrote: On Tue, Apr 2, 2013 at 1:04 AM, Jonathan Wiltshire j...@debian.org wrote: As mummy/1.0.3-2 is unsuitable for Wheezy please could you prepare a backport of your patch for an upload to testing-proposed-updates, and submit a debdiff to the release team for approval. 1.0.2-5 will transition to Wheezy... It *did*, nearly a year ago. 1.0.3-2 should be blocked by freeze, correct ? Yes. 1.0.3-1 also contains changes which are not suitable for unblocking, hence Jonathan's request for a backport of the RC fix via t-p-u. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702965: feedback: works
Hi, after upgrading libprocps0 the problem went away. Just so you know. Thanks, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 691883
Processing commands for cont...@bugs.debian.org: close 691883 1.2.6-2+squeeze6 Bug #691883 [mahara] Multiple security issues Marked as fixed in versions mahara/1.2.6-2+squeeze6. Bug #691883 [mahara] Multiple security issues Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 691883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691883 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#703852: [Pkg-mediawiki-devel] Bug#703852: Bug#703852: [mediawiki] mw{en, dis}ext ineffective for new installs
On Thu, 28 Mar 2013, Filipus Klutiero wrote: There's a very simple solution to that which would solve even more problems. Unfortunately, it requires a larger change. Well, let’s just not do that right now. The upgrade to 1.19 was on very short notice already, and, IIRC, Jonathan wanted to make something that installs more nicely after the release anyway. And, for what’s worth, I’m obviously against any non-backwards-compatible changes in that manner… The list of extensions in /etc/mediawiki-extensions/extensions-available/ has nothing for Interwiki (except a symlink to its predessors, SpecialInterwiki). The SpecialInterwiki.php one is the correct one to use. https://evolvis.org/plugins/mediawiki/wiki/evolvis/index.php/Special:Interwiki (for example) works just fine (provided you’re Forge Admin ☺), and that’s what this extension is supposed to provide. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 704457 to php5-gd, severity of 704457 is grave, tagging 704457 ...
Processing commands for cont...@bugs.debian.org: reassign 704457 php5-gd Bug #704457 [php5-cli] undefined symbol: gdImagePaletteToTrueColor in Unknown on line 0 Bug reassigned from package 'php5-cli' to 'php5-gd'. No longer marked as found in versions php5/5.5.0~beta2-1. Ignoring request to alter fixed versions of bug #704457 to the same values previously set severity 704457 grave Bug #704457 [php5-gd] undefined symbol: gdImagePaletteToTrueColor in Unknown on line 0 Severity set to 'grave' from 'important' tags 704457 + experimental Bug #704457 [php5-gd] undefined symbol: gdImagePaletteToTrueColor in Unknown on line 0 Added tag(s) experimental. retitle 704457 gd extension broken due new embedded libgd functions not added to gd_compat layer Bug #704457 [php5-gd] undefined symbol: gdImagePaletteToTrueColor in Unknown on line 0 Changed Bug title to 'gd extension broken due new embedded libgd functions not added to gd_compat layer' from 'undefined symbol: gdImagePaletteToTrueColor in Unknown on line 0' thanks Stopping processing here. Please contact me if you need assistance. -- 704457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704457 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 704457
Processing commands for cont...@bugs.debian.org: tags 704457 + experimental confirmed Bug #704457 [php5-gd] gd extension broken due new embedded libgd functions not added to gd_compat layer Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 704457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704457 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#702251: marked as done (otrs2: upgrade fails from 3.1.11 to 3.2.2)
Your message dated Tue, 02 Apr 2013 09:03:10 + with message-id e1umx7w-00049c...@franck.debian.org and subject line Bug#702251: fixed in otrs2 3.1.7+dfsg1-8 has caused the Debian Bug report #702251, regarding otrs2: upgrade fails from 3.1.11 to 3.2.2 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.) -- 702251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: otrs2 Version: 3.2.2+dfsg1-1 Severity: important -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages otrs2 depends on: ii adduser 3.113+nmu3 ii apache2-mpm-worker [httpd-cgi] 2.2.22-12 ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii dpkg1.16.9 ii libapache2-reload-perl 0.12-1 ii libauthen-sasl-perl 2.1500-1 ii libcrypt-passwdmd5-perl 1.3-10 ii libcss-minifier-perl0.01-1 ii libdate-pcalc-perl 6.1-1+b2 ii libdbd-pg-perl 2.19.2-2 ii libdbi-perl 1.622-1 ii libemail-valid-perl 0.190-1 ii libgd-graph-perl1.44-6 ii libgd-text-perl 0.86-8 ii libio-stringy-perl 2.110-5 ii libjavascript-minifier-perl 1.05-1 ii libjs-jquery1.7.2+dfsg-1 ii libjs-jquery-ui 1.8.ooops.21+dfsg-2 ii libjs-prototype 1.7.0-2 ii libjs-yui 2.9.0.dfsg.0.1-0.1 ii libjson-perl2.53-1 ii libmail-imapclient-perl 3.31-2 ii libmail-pop3client-perl 2.17-1 ii libmailtools-perl 2.09-1 ii libmime-tools-perl 5.503-1 ii libnet-imap-simple-perl 1.2030-1 ii libnet-imap-simple-ssl-perl 1.3-3 ii libnet-smtp-ssl-perl1.01-3 ii libpdf-api2-perl2.019-1 ii libsoap-lite-perl 0.714-1 ii libtext-csv-perl1.21-1 ii libtext-diff-perl 1.41-1 ii libxml-feedpp-perl 0.43-1 ii libxml-parser-perl 2.41-1+b1 ii libyaml-libyaml-perl0.38-3 ii libyaml-perl0.81-1 ii perl [libdigest-sha-perl] 5.14.2-18 ii ttf-dejavu-core 2.33-3 ii ttf-dejavu-extra2.33-3 ii ucf 3.0025+nmu3 Versions of packages otrs2 recommends: ii ispell 3.3.02-6 ii libapache-dbi-perl 1.11-1 ii postgresql 9.1+134wheezy3 ii procmail3.22-20 Versions of packages otrs2 suggests: ii libencode-hanextra-perl 0.23-2+b2 ii libjson-xs-perl 2.320-1+b1 ii libnet-ldap-perl1:0.4400-1 ii libnet-smtp-tls-butmaintained-perl 0.17-1 ii libtext-csv-xs-perl 0.90-1 pn otrs2-doc-en | otrs2-doc-de none -- debconf information excluded ---End Message--- ---BeginMessage--- Source: otrs2 Source-Version: 3.1.7+dfsg1-8 We believe that the bug you reported is fixed in the latest version of otrs2, which is due to be installed in the Debian FTP archive. 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 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi pmatth...@debian.org (supplier of updated otrs2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Apr 2013 10:39:24 +0200 Source: otrs2 Binary: otrs2 otrs Architecture: source all Version: 3.1.7+dfsg1-8 Distribution: unstable Urgency: high Maintainer: Patrick Matthäi pmatth...@debian.org Changed-By: Patrick Matthäi pmatth...@debian.org Description: otrs - Open Ticket Request System (OTRS 3) otrs2 - Open Ticket Request System Closes: 702251 Changes: otrs2 (3.1.7+dfsg1-8) unstable; urgency=high . * Add missing post database schemas for new installations with dbconfig. Without it, new
Bug#704257: missing libgl1-mesa-dri in upgrades
On Mon, Apr 1, 2013 at 11:16 PM, Daniel Pocock dan...@pocock.com.au wrote: On 01/04/13 22:04, John Paul Adrian Glaubitz wrote: On 04/01/2013 09:59 PM, Daniel Pocock wrote: Agreed, but that doesn't complete the picture, as libgl1-mesa-glx doesn't depend on libgl1-mesa-dri: $ apt-cache depends libgl1-mesa-glx ... Recommends: libgl1-mesa-dri Well, Recommends are installed by default, aren't they? However, I'm Not during upgrade or dist-upgrade operations. This is specifically an upgrading issue. From man apt-get: upgrade: ... under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed. Correct for apt/squeeze, partly-wrong for apt/wheezy (since 0.8.15.3). A package requiring a new recommends which is in a non-broken policy state previously will be held back just like other packages requiring a new depends in apt/wheezy. In apt/squeeze the policy will break, which you could fix with apt-get install --fix-policy, but that is going to fix ALL recommends. We are going to be fine in this regard as many packages have a new dependency in a new release (upgrade is mostly for between releases). In this case it is at least multiarch-support. dist-upgrade: ... intelligently handles changing dependencies with new versions of packages dist-upgrade on the other hand installs new recommends since the introduction of recommends. Keyword is new: If you had recommends disabled previously and/or removed a recommends apt will not install this recommendation again. (It compares the recommends list of the old version with the new version and only uninstalled recommends present in the new, but not in the old version are marked for installation). Of course, if the recommends isn't installable you will still get a solution which doesn't include this recommends which will be displayed as usual. You have to install it later by hand then as it now an old recommends … (In stable, uninstallability shouldn't happen though) I guess the confusion comes from the word dependencies: In APT namespace dependency means any relation which is allowed; not just a Depends. So the sentence should be read as … handles changing Pre-Depends, Depends, Conflicts, Breaks, Replaces, Provides, Recommends (if enabled, default yes) and Suggests (if enabled, default no) with new versions … (for the sake of completion: Enhances are not handled) It's just that a user shouldn't really be required to know what those are. (if you digg deaper [usually in non-user facing texts] you will come across hard, important, soft, negative and positive dependencies to complete the confusion. I will leave it as an exercise for now which subsets are meant with those adjectives) Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 704257
Processing commands for cont...@bugs.debian.org: # not a bug close 704257 Bug #704257 [empathy] missing dependency Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 704257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704257 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#704517: Fails to build with experimental gobject-introspection
Package: liblangtag Version: 0.4.0-5 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) Building with experimental gobject-introspection results in the following build errors: cc: error: unrecognized command line option '--symbol-prefix=lt' cc: error: unrecognized command line option '--identifier-prefix=Lt' Passing the flags meant for the g-ir-scanner using SCANNERFLAGS instead of CFLAG fixes this. Debdiff attached which solves the issue (note the root Makefile.am change was done to make autoreconf work..) -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru liblangtag-0.4.0/debian/changelog liblangtag-0.4.0/debian/changelog --- liblangtag-0.4.0/debian/changelog 2013-01-09 19:40:58.0 +0100 +++ liblangtag-0.4.0/debian/changelog 2013-04-02 10:47:27.0 +0200 @@ -1,3 +1,9 @@ +liblangtag (0.4.0-6) UNRELEASED; urgency=low + + * Fix build with new gobject-introspection + + -- Sjoerd Simons sjoerd.sim...@collabora.co.uk Tue, 02 Apr 2013 10:47:07 +0200 + liblangtag (0.4.0-5) experimental; urgency=low * make doc build into override_dh_auto_build-indep target diff -Nru liblangtag-0.4.0/debian/control liblangtag-0.4.0/debian/control --- liblangtag-0.4.0/debian/control 2013-01-09 19:37:08.0 +0100 +++ liblangtag-0.4.0/debian/control 2013-04-02 10:47:38.0 +0200 @@ -1,7 +1,7 @@ Source: liblangtag Priority: optional Maintainer: Rene Engelhard r...@debian.org -Build-Depends: debhelper (= 8.0.0), autotools-dev, pkg-config, libxml2-dev, libglib2.0-dev, check, libgirepository1.0-dev, gobject-introspection, libtool, locales +Build-Depends: debhelper (= 8.0.0), autotools-dev, pkg-config, libxml2-dev, libglib2.0-dev, check, libgirepository1.0-dev, gobject-introspection, libtool, locales, dh-autoreconf Build-Depends-Indep: gtk-doc-tools Build-Conflicts: locales-all Standards-Version: 3.9.2 diff -Nru liblangtag-0.4.0/debian/patches/fix-build-with-g-i-1.36.patch liblangtag-0.4.0/debian/patches/fix-build-with-g-i-1.36.patch --- liblangtag-0.4.0/debian/patches/fix-build-with-g-i-1.36.patch 1970-01-01 01:00:00.0 +0100 +++ liblangtag-0.4.0/debian/patches/fix-build-with-g-i-1.36.patch 2013-04-02 10:48:57.0 +0200 @@ -0,0 +1,24 @@ +--- a/Makefile.am b/Makefile.am +@@ -8,9 +8,7 @@ + #SUBDIRS += docs tests + SUBDIRS += tests + +-ACLOCAL_AMFLAGS = \ +- -I m4macros \ +- $(NULL) ++ACLOCAL_AMFLAGS = -I m4macros + + CONFIGURE_DEPENDENCIES = \ + requires \ +--- a/liblangtag-gobject/Makefile.am b/liblangtag-gobject/Makefile.am +@@ -171,6 +171,8 @@ + $(NULL) + LangTag_0_4_gir_CFLAGS = \ + $(INCLUDES) \ ++ $(NULL) ++LangTag_0_4_gir_SCANNERFLAGS = \ + --symbol-prefix=lt \ + --identifier-prefix=Lt \ + -v\ diff -Nru liblangtag-0.4.0/debian/patches/series liblangtag-0.4.0/debian/patches/series --- liblangtag-0.4.0/debian/patches/series 2012-11-21 22:56:00.0 +0100 +++ liblangtag-0.4.0/debian/patches/series 2013-04-02 10:47:57.0 +0200 @@ -1,2 +1,3 @@ no_encoding.diff liblangtag-ppc.diff +fix-build-with-g-i-1.36.patch diff -Nru liblangtag-0.4.0/debian/rules liblangtag-0.4.0/debian/rules --- liblangtag-0.4.0/debian/rules 2013-01-09 19:38:14.0 +0100 +++ liblangtag-0.4.0/debian/rules 2013-04-02 10:49:42.0 +0200 @@ -24,7 +24,7 @@ dh_auto_clean %: - dh $@ --with autotools-dev --with gir + dh $@ --with autotools-dev --with gir --with autoreconf override_dh_auto_configure: dh_auto_configure -- $(CONFIGURE_FLAGS)
Processed: severity of 704479 is critical
Processing commands for cont...@bugs.debian.org: severity 704479 critical Bug #704479 [postgresql-9.1] postgresql: high-exposure security vulnerability Severity set to 'critical' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 704479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704479 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#704521: virtuoso-opensource-6.1: Virtuoso server stop script fails to stop server cleanly, potentially causing database corruption
Package: virtuoso-opensource-6.1 Severity: critical Justification: causes serious data loss Dear Maintainer. When calling '/etc/init.d/virtuoso-opensource-6.1 stop', virtuoso may still be running after the script completes. This might lead to database corruption, e.g. on system reboot. Seemingly, the script fails to wait for a clean exit of the server in this section: quote stop) log_daemon_msg Stopping $DESC $NAME if running ; then # Only stop the server if we see it running errcode=0 stop_server || errcode=$? log_end_msg $errcode else # If it's not running don't do anything log_progress_msg apparently not running log_end_msg 0 exit 0 fi ;; /quote I have modified the script to temporarily circumvent the situation on my system by enclosing part of this snippet in a while-loop, as below: quote stop) log_daemon_msg Stopping $DESC $NAME # keep stopping the server if it fails to stop while running; do if running ; then # Only stop the server if we see it running errcode=0 stop_server || errcode=$? log_end_msg $errcode else # If it's not running don't do anything log_progress_msg apparently not running log_end_msg 0 exit 0 fi sleep 2 # wait two seconds before looping done ;; /quote As my knowledge of rc.d scripts is limited, this was a quick hack to prevent my database to suffer corruption. My solution does not cater for the need to force-stop virtuoso. If the server does not exit cleanly at some point, I have effectively created an infinite loop. Please fix this situation in a more proper fashion. Regards ;)Frode Frode Severin Hatlevik -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694717: nut-server cannot start automatically on system boot
Hello comrades. Is there any progress in your work? I have some observations on the work of nut-server. If the service could not be started automatically, it also can not be started using the command sudo /etc/init.d/nut-server start , but command sudo upsdrvctl start works always. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702251: marked as done (otrs2: upgrade fails from 3.1.11 to 3.2.2)
Your message dated Tue, 02 Apr 2013 12:18:25 + with message-id e1un0at-0005bo...@franck.debian.org and subject line Bug#702251: fixed in otrs2 3.2.4-1 has caused the Debian Bug report #702251, regarding otrs2: upgrade fails from 3.1.11 to 3.2.2 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.) -- 702251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: otrs2 Version: 3.2.2+dfsg1-1 Severity: important -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages otrs2 depends on: ii adduser 3.113+nmu3 ii apache2-mpm-worker [httpd-cgi] 2.2.22-12 ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii dpkg1.16.9 ii libapache2-reload-perl 0.12-1 ii libauthen-sasl-perl 2.1500-1 ii libcrypt-passwdmd5-perl 1.3-10 ii libcss-minifier-perl0.01-1 ii libdate-pcalc-perl 6.1-1+b2 ii libdbd-pg-perl 2.19.2-2 ii libdbi-perl 1.622-1 ii libemail-valid-perl 0.190-1 ii libgd-graph-perl1.44-6 ii libgd-text-perl 0.86-8 ii libio-stringy-perl 2.110-5 ii libjavascript-minifier-perl 1.05-1 ii libjs-jquery1.7.2+dfsg-1 ii libjs-jquery-ui 1.8.ooops.21+dfsg-2 ii libjs-prototype 1.7.0-2 ii libjs-yui 2.9.0.dfsg.0.1-0.1 ii libjson-perl2.53-1 ii libmail-imapclient-perl 3.31-2 ii libmail-pop3client-perl 2.17-1 ii libmailtools-perl 2.09-1 ii libmime-tools-perl 5.503-1 ii libnet-imap-simple-perl 1.2030-1 ii libnet-imap-simple-ssl-perl 1.3-3 ii libnet-smtp-ssl-perl1.01-3 ii libpdf-api2-perl2.019-1 ii libsoap-lite-perl 0.714-1 ii libtext-csv-perl1.21-1 ii libtext-diff-perl 1.41-1 ii libxml-feedpp-perl 0.43-1 ii libxml-parser-perl 2.41-1+b1 ii libyaml-libyaml-perl0.38-3 ii libyaml-perl0.81-1 ii perl [libdigest-sha-perl] 5.14.2-18 ii ttf-dejavu-core 2.33-3 ii ttf-dejavu-extra2.33-3 ii ucf 3.0025+nmu3 Versions of packages otrs2 recommends: ii ispell 3.3.02-6 ii libapache-dbi-perl 1.11-1 ii postgresql 9.1+134wheezy3 ii procmail3.22-20 Versions of packages otrs2 suggests: ii libencode-hanextra-perl 0.23-2+b2 ii libjson-xs-perl 2.320-1+b1 ii libnet-ldap-perl1:0.4400-1 ii libnet-smtp-tls-butmaintained-perl 0.17-1 ii libtext-csv-xs-perl 0.90-1 pn otrs2-doc-en | otrs2-doc-de none -- debconf information excluded ---End Message--- ---BeginMessage--- Source: otrs2 Source-Version: 3.2.4-1 We believe that the bug you reported is fixed in the latest version of otrs2, which is due to be installed in the Debian FTP archive. 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 702...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi pmatth...@debian.org (supplier of updated otrs2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Apr 2013 14:02:40 +0200 Source: otrs2 Binary: otrs2 otrs Architecture: source all Version: 3.2.4-1 Distribution: experimental Urgency: high Maintainer: Patrick Matthäi pmatth...@debian.org Changed-By: Patrick Matthäi pmatth...@debian.org Description: otrs - Open Ticket Request System (OTRS 3) otrs2 - Open Ticket Request System Closes: 702251 Changes: otrs2 (3.2.4-1) experimental; urgency=high . * New upstream release. - Improved permission checks in LinkObject, this fixes CVE-2013-2625. - Refresh
Bug#703146: Bug#704263: installation-reports: busybox fails to verify on current wheezy/sid installer
Hi, Adam Baxter wrote: Subject: […] busybox fails to verify on current wheezy/sid installer Same here. But not only busybox, but also dmsetup, libdevmapper1.02.1, etc. As this was prefixed with in-target I checked how the issue is presented from inside the chroot: apt-get install busybox really complains about an unauthenticated package. apt-get update doesn't solve the issue but reveals the source for the issue: W: GPG errror: http://debian.ethz.ch wheezy Release: The following signatures were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze) ftpmas...@debian.org According to https://lists.debian.org/debian-mirrors/2013/03/msg5.html this looks a lot like http://bugs.debian.org/703146 (Cc'ed), too, which is worked on. Interestingly the issue could be solved by running the following commands inside the chroot while D-I asks me which kernel to install: # cd /var/lib/apt/lists # rm ftp.*.debian.org* # apt-get update # apt-get install busybox (No BADSIG here, installs fine.) (If I do this before that question, debootstrap seems to overwrite the previous installation and hence the manually installed busybox.) So the funny thing is that all packages were accepted despite the BADSIG issue, except busybox. Sounds as if there's more broken than just #703146. It also seems to have forgotten some settings after aborting at the busybox install failure. E.g. preseeding stuff (otherwise I would have expected that it doesn't ask me for the kernel to choose at some point) as well the fact that it should have had installed lvm2 into the target (as I manually partitioned a VG in the installer), i.e. it didn't find any root file system at the first reboot and I had to boot via PXE for rescue mode to install lvm2, too. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704111: [cfe-dev] Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.
Sylvestre Ledru wrote: FYI, as soon as Wheezy is released, I will upload version 3.2 or 3.3 of clang and the llvm toolchain. Now that the issue of finding a minimal fix for testing/unstable is out of the way. I just took a look at the package in experimental. I noticed the following. You switched to bintutils-gold unconditionally. Since binutils-gold is not available on all architectures this has made the package unbuildable on a number of architectures where it was previously built successfully. The armhf situation still needs attention. Specifically clang still defaults to using a rediculously low CPU and once the correct CPU is selected it still defaults to using all the vfp registers and neon. The inappropriate use of altivec on powerpc that adam conrad pointed out while I was working on the unstable package was still there. Debdiff with fixes for the above issues is attached. Note that while I have included a changelog entry I have no intention of NMUing this. diff -Nru clang-3.2/debian/changelog clang-3.2/debian/changelog --- clang-3.2/debian/changelog 2013-03-15 15:13:26.0 + +++ clang-3.2/debian/changelog 2013-04-01 02:35:41.0 + @@ -1,3 +1,13 @@ +clang (1:3.2-1~exp9) UNRELEASED; urgency=low + + * Use binutils-gold only on architectures where it is actually available + * 33-armhf-defaults.diff Fix defaults to use correct CPU and FPU for +debian armhf (Closes: #704111) + * 34-powerpc-no-altivec.diff disable altivec by default on powerpc because +debian powerpc does not require altivec (patch cherry picked from ubuntu) + + -- Peter Michael Green plugw...@raspbian.org Mon, 01 Apr 2013 01:37:38 + + clang (1:3.2-1~exp8) experimental; urgency=low * Limit the dependency of clang-3.2 on compiler-rt to amd64 i386 diff -Nru clang-3.2/debian/compiler-rt/usr/bin/asan_symbolize clang-3.2/debian/compiler-rt/usr/bin/asan_symbolize --- clang-3.2/debian/compiler-rt/usr/bin/asan_symbolize 1970-01-01 00:00:00.0 + +++ clang-3.2/debian/compiler-rt/usr/bin/asan_symbolize 2013-04-01 07:14:17.0 + @@ -0,0 +1,356 @@ +#!/usr/bin/env python +#===- lib/asan/scripts/asan_symbolize.py ---===# +# +# The LLVM Compiler Infrastructure +# +# This file is distributed under the University of Illinois Open Source +# License. See LICENSE.TXT for details. +# +#======# +import bisect +import os +import re +import subprocess +import sys + +llvm_symbolizer = None +symbolizers = {} +filetypes = {} +vmaddrs = {} +DEBUG = False + + +# FIXME: merge the code that calls fix_filename(). +def fix_filename(file_name): + for path_to_cut in sys.argv[1:]: +file_name = re.sub('.*' + path_to_cut, '', file_name) + file_name = re.sub('.*asan_[a-z_]*.cc:[0-9]*', '_asan_rtl_', file_name) + file_name = re.sub('.*crtstuff.c:0', '???:0', file_name) + return file_name + + +class Symbolizer(object): + def __init__(self): +pass + + def symbolize(self, addr, binary, offset): +Symbolize the given address (pair of binary and offset). + +Overriden in subclasses. +Args: +addr: virtual address of an instruction. +binary: path to executable/shared object containing this instruction. +offset: instruction offset in the @binary. +Returns: +list of strings (one string for each inlined frame) describing +the code locations for this instruction (that is, function name, file +name, line and column numbers). + +return None + + +class LLVMSymbolizer(Symbolizer): + def __init__(self, symbolizer_path): +super(LLVMSymbolizer, self).__init__() +self.symbolizer_path = symbolizer_path +self.pipe = self.open_llvm_symbolizer() + + def open_llvm_symbolizer(self): +if not os.path.exists(self.symbolizer_path): + return None +cmd = [self.symbolizer_path, + '--use-symbol-table=true', + '--demangle=false', + '--functions=true', + '--inlining=true'] +if DEBUG: + print ' '.join(cmd) +return subprocess.Popen(cmd, stdin=subprocess.PIPE, +stdout=subprocess.PIPE) + + def symbolize(self, addr, binary, offset): +Overrides Symbolizer.symbolize. +if not self.pipe: + return None +result = [] +try: + symbolizer_input = '%s %s' % (binary, offset) + if DEBUG: +print symbolizer_input + print self.pipe.stdin, symbolizer_input + while True: +function_name = self.pipe.stdout.readline().rstrip() +if not function_name: + break +file_name = self.pipe.stdout.readline().rstrip() +file_name = fix_filename(file_name) +if (not function_name.startswith('??') and +not file_name.startswith('??')): + # Append only valid frames. + result.append('%s in %s %s' % (addr, function_name, +
Bug#659390: bug#670232
Hi, I looked into it and after populating the database by hand and also fixing manually the initial issue [1]. It doesn't work anyway, the following errors appear: [Mon Apr 01 02:15:47 2013] [error] [client x.x.x.x] PHP Warning: include(bookmarks.tpl.php): failed to open stream: No such file or directory in /usr/share/php/SemanticScuttle/Model/Template.php on line 89 [Mon Apr 01 02:15:47 2013] [error] [client x.x.x.x] PHP Warning: include(): Failed opening 'bookmarks.tpl.php' for inclusion (include_path='/etc/semanticscuttle/templates/default:/etc/semanticscuttle/templates/default:.:/usr/share/php:/usr/share/pear:/usr/share/php/SemanticScuttle/../') in /usr/share/php/SemanticScuttle/Model/Template.php on line 89 I wonder if this package have ever worked (looking at popcorn doesn't look like). At this stage, I prefer looking for a nicer replacement of scuttle/semanticscuttle. I doubt a NMU would have small changes, I would go with removing semanticscuttle from Wheezy. I got it to work (that is, not throw obvious immediate errors) from a clean install by fixing three separate problems: 1) Initial issue reported in bug: No default configuration file config.default.php found. This is really, really strange. Fixed by creating a symlink from /usr/share/semanticscuttle/data/config.default.php to /usr/share/php/data/SemanticScuttle/ 2) Database not populated. This is because the dbconfig-common file is named /usr/share/dbconfig-common/data/semanticscuttle/install/tables.sql, while it should be named /usr/share/dbconfig-common/data/semanticscuttle/install/mysql. 3) Spews strict standards errors to the browser. Fixed by setting $debugMode to false in /etc/semanticscuttle/config.php. After fixing these three errors I didn't see any immediate (!) errors anymore. So while I think each one of those could be fixed by a one or few lines change in the packaging, it's more that the package was apparently in wheezy for over a year in this state, with these three rather orthogonal but immediately obvious errors. This, combined with the fact that semanticscuttle was never in a stable release and the maintainer has agreed already with removal from wheezy as an option, leads me to the conclusion that removal from wheezy is the best option at this point. Hence, I'm filing a removal request with the release team. Cheers, Thijs signature.asc Description: This is a digitally signed message part.
Bug#704531: liblangtag: FTBFS on arm*: test case fails
Package: liblangtag Version: 0.4.0-5 Severity: serious Tags: upstream Hello, Your package fails to build on arm* architectures due to test case failure: Running suite(s): lt_tag_t 50%: Checks: 4, Failures: 0, Errors: 2 check-tag.c:46:E:Basic functionality:test_lt_tag_parse:0: (after this point) Test timeout expired check-tag.c:210:E:Basic functionality:test_lt_tag_match:0: (after this point) Test timeout expired FAIL: check-tag [...] make[5]: *** [check-TESTS] Error 1 == 1 of 9 tests failed Please report to http://github.com/tagoh/liblangtag/issues == Also see: https://buildd.debian.org/status/package.php?p=liblangtagsuite=experimental -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.8-trunk-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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#704537: librole-commons-perl and libauthority-shared-perl: error when trying to install together
Package: libauthority-shared-perl,librole-commons-perl Version: libauthority-shared-perl/0.06-1 Version: librole-commons-perl/0.101-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-04-02 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libalgorithm-c3-perl libsub-name-perl libobject-role-perl libobject-authority-perl libauthority-shared-perl libvariable-magic-perl libparams-util-perl libsub-install-perl libdata-optlist-perl libsub-exporter-perl libb-hooks-endofscope-perl libclass-c3-perl libparams-classify-perl libmodule-runtime-perl libtry-tiny-perl libmodule-implementation-perl liblist-moreutils-perl libpackage-deprecationmanager-perl libpackage-stash-perl libclass-load-perl libmro-compat-perl libclass-method-modifiers-perl libsub-exporter-progressive-perl libdevel-globaldestruction-perl libhash-fieldhash-perl libpadwalker-perl liblexical-underscore-perl librole-tiny-perl libstrictures-perl libmoo-perl libsub-identify-perl libnamespace-clean-perl libobject-id-perl liburi-perl libscalar-list-utils-perl libscalar-does-perl librole-commons-perl Extracting templates from packages: 81% Extracting templates from packages: 100% Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libalgorithm-c3-perl. (Reading database ... 10775 files and directories currently installed.) Unpacking libalgorithm-c3-perl (from .../libalgorithm-c3-perl_0.08-1_all.deb) ... Selecting previously unselected package libsub-name-perl. Unpacking libsub-name-perl (from .../libsub-name-perl_0.05-1+b2_amd64.deb) ... Selecting previously unselected package libobject-role-perl. Unpacking libobject-role-perl (from .../libobject-role-perl_0.001-1_all.deb) ... Selecting previously unselected package libobject-authority-perl. Unpacking libobject-authority-perl (from .../libobject-authority-perl_0.004-1_all.deb) ... Selecting previously unselected package libauthority-shared-perl. Unpacking libauthority-shared-perl (from .../libauthority-shared-perl_0.006-1_all.deb) ... Selecting previously unselected package libvariable-magic-perl. Unpacking libvariable-magic-perl (from .../libvariable-magic-perl_0.52-1_amd64.deb) ... Selecting previously unselected package libparams-util-perl. Unpacking libparams-util-perl (from .../libparams-util-perl_1.07-1_amd64.deb) ... Selecting previously unselected package libsub-install-perl. Unpacking libsub-install-perl (from .../libsub-install-perl_0.926-1_all.deb) ... Selecting previously unselected package libdata-optlist-perl. Unpacking libdata-optlist-perl (from .../libdata-optlist-perl_0.107-1_all.deb) ... Selecting previously unselected package libsub-exporter-perl. Unpacking libsub-exporter-perl (from .../libsub-exporter-perl_0.984-1_all.deb) ... Selecting previously unselected package libb-hooks-endofscope-perl. Unpacking libb-hooks-endofscope-perl (from .../libb-hooks-endofscope-perl_0.11-1_all.deb) ... Selecting previously unselected package libclass-c3-perl. Unpacking libclass-c3-perl (from .../libclass-c3-perl_0.24-1_all.deb) ... Selecting previously unselected package libparams-classify-perl. Unpacking libparams-classify-perl (from .../libparams-classify-perl_0.013-4_amd64.deb) ... Selecting previously unselected package libmodule-runtime-perl. Unpacking libmodule-runtime-perl (from .../libmodule-runtime-perl_0.013-1_all.deb) ... Selecting previously unselected package libtry-tiny-perl. Unpacking libtry-tiny-perl (from .../libtry-tiny-perl_0.12-1_all.deb) ... Selecting previously unselected package libmodule-implementation-perl. Unpacking libmodule-implementation-perl (from .../libmodule-implementation-perl_0.06-1_all.deb) ... Selecting previously unselected package liblist-moreutils-perl. Unpacking liblist-moreutils-perl (from .../liblist-moreutils-perl_0.33-1+b1_amd64.deb) ... Selecting previously unselected package libpackage-deprecationmanager-perl. Unpacking libpackage-deprecationmanager-perl (from .../libpackage-deprecationmanager-perl_0.13-1_all.deb) ... Selecting previously unselected package libpackage-stash-perl. Unpacking libpackage-stash-perl (from .../libpackage-stash-perl_0.34-1_all.deb) ... Selecting previously unselected package libclass-load-perl. Unpacking libclass-load-perl (from .../libclass-load-perl_0.20-1_all.deb) ... Selecting previously unselected package libmro-compat-perl. Unpacking libmro-compat-perl (from .../libmro-compat-perl_0.12-1_all.deb) ... Selecting previously unselected package libclass-method-modifiers-perl. Unpacking libclass-method-modifiers-perl (from .../libclass-method-modifiers-perl_2.03-1_all.deb) ... Selecting previously unselected package libsub-exporter-progressive-perl.
Bug#704190: ltsp-build-client fails because of apt GPG error
Package: debootstrap Followup-For: Bug #704190 Confirming the workaround. After installing debootstrap .47 from Unstable, it works well. I hope You'll be able to get the fix to Wheezy too. Thank You for Your help. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=sk_SK.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to sk_SK.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debootstrap depends on: ii gnupg 1.4.12-7 ii wget 1.13.4-3 Versions of packages debootstrap recommends: ii debian-archive-keyring 2012.4 debootstrap suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): merge 704486 and 704537
Processing commands for cont...@bugs.debian.org: merge 704486 704537 Bug #704486 [libobject-authority-perl,librole-commons-perl] librole-commons-perl: trying to overwrite '/usr/share/perl5/Object/AUTHORITY.pm', which is also in package libobject-authority-perl 0.004-1 Unable to merge bugs because: package of #704537 is 'libauthority-shared-perl,librole-commons-perl' not 'libobject-authority-perl,librole-commons-perl' Failed to merge 704486: Did not alter merged bugs Debbugs::Control::set_merged('transcript', 'GLOB(0x1d256b8)', 'requester', 'Axel Beckert a...@debian.org', 'request_addr', 'cont...@bugs.debian.org', 'request_msgid', '20130402181711.gg28...@sym.noone.org', 'request_subject', ...) called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538 eval {...} called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537 Debbugs::Control::Service::control_line('line', undef, 'clonebugs', 'HASH(0x1c62400)', 'limit', 'HASH(0x1c61de8)', 'common_control_options', 'ARRAY(0x1c61e30)', 'errors', ...) called at /usr/lib/debbugs/service line 474 kthxbye Stopping processing here. Please contact me if you need assistance. -- 704486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704486 704537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704537 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: user debian-secur...@lists.debian.org, usertagging 702574, usertagging 633088 ...
Processing commands for cont...@bugs.debian.org: user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). usertags 702574 + tracked Usertags were: CVE-2013-1843 CVE-2013-1842 tracked. Usertags are now: CVE-2013-1843 CVE-2013-1842 tracked. usertags 633088 + tracked Usertags were: CVE-2012-2743 tracked CVE-2012-2742. Usertags are now: CVE-2012-2743 tracked CVE-2012-2742. retitle 674447 CVE-2012-2942 Bug #674447 {Done: Luk Claes l...@debian.org} [haproxy] CVE-2012-2391 Changed Bug title to 'CVE-2012-2942' from 'CVE-2012-2391' thanks Stopping processing here. Please contact me if you need assistance. -- 633088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633088 674447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674447 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: #704537/#704486 only affect Sid because librole-commons-perl is not in Wheezy
Processing commands for cont...@bugs.debian.org: tag 704537 + sid Bug #704537 [libauthority-shared-perl,librole-commons-perl] librole-commons-perl and libauthority-shared-perl: error when trying to install together Added tag(s) sid. tag 704486 + sid Bug #704486 [libobject-authority-perl,librole-commons-perl] librole-commons-perl: trying to overwrite '/usr/share/perl5/Object/AUTHORITY.pm', which is also in package libobject-authority-perl 0.004-1 Added tag(s) sid. kthxbye Stopping processing here. Please contact me if you need assistance. -- 704486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704486 704537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704537 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#695224: Locale::Maketext versioning in perl package
On Sun, Mar 31, 2013 at 05:46:12PM +0100, Dominic Hargreaves wrote: There is a problem with the perl package, as discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695224#55 onwards, whereby the application of the security fix in that ticket now causes double-escaping problems where people workaround the problem by escaping themselves, when they detect an earlier Locale::Maketext by version number. I am slightly wary about importing the new (1.23) version of Locale::Maketext as I mentioned in that bug already, but my fears may be unfounded. Could you comment about whether you would accept such a change in wheezy at this time? (I can't really decide whether it's RC or not). FWIW, it looks clear to me that the only functional changes in the patch are the $VERSION increments in the .pm files. The rest is documentation and test cases, and the only important $VERSION is most probably the main one in Locale/Maketext.pm. While that change itself is trivial, it has action-at-distance effects - otherwise this wouldn't be an issue at all. I think the risk potential is mostly in breaking something that's trusting Module::CoreList (dh-make-perl and lintian come to mind, CPAN.pm and CPANPLUS.pm might be affected somehow too?), and that it's not a very big risk but still a real one. Thinking about the necessity of this: Paul is IMO right that security fixes and other backported stuff usually don't change functionality API-wise, and I'm generally sympathetic to the idea of incrementing $VERSION when they do. Unfortunately that's hard to do in the general case (as the versioning scheme doesn't really support downstream branching.) In this specific case, upgrading Locale::Maketext fully to 1.23 in wheezy would probably have been the right thing to do if we had anticipated these issues. But we didn't, and it seems very late in the release process to do it now. Also, I can't really see us applying anything but the targeted fix for squeeze. I see Fedora/RedHat also upgraded their Locale::Maketext modules without incrementing $VERSION (I checked the patches in RHEL 6 / Perl 5.10.1 and Fedora Core 16 17 / Perl 5.14.3). So it looks like even if we do try to fix this for wheezy, applications still have to check for features rather than versions to stay on the safe side. -- 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
Processed: Re: Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t
Processing control commands: fixed -1 0.35-1 Bug #704267 [src:libdr-tarantool-perl] libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t Marked as fixed in versions libdr-tarantool-perl/0.35-1. -- 704267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704267 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#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t
Control: fixed -1 0.35-1 Hi, Andrey Rahmatullin wrote: On Sun, Mar 31, 2013 at 12:54:32PM +0100, Dominic Hargreaves wrote: FWIW it didn't fail here in a sid am64 chroot. True; in sid, the failure (with 0.15-1) seems to come at # Failed test 'errstr' # at t/020-low_level_client.t line 125. # 'Duplicate key exists in unique index 0' # doesn't match '(?^:already exists)' (i386 and amd64). Oh, I also missed the fact that the bug has a different version that I tested. So, to be clear, I tested 0.35-1 which is the sid version. 0.15-1 from testing on a sid amd64 chroot fails with the same error as in your quote above. I can reproduce the issue on a Sid machine (no chroot) with 0.15-1 on i386 Sid + Experimental: ok 25 - type not ok 26 - errstr ok 27 - * select reply code However, 0.35-1 from sid FTBFS for me, too, on i386 Sid + Experimental: Test Summary Report --- t/020-low_level_client.t (Wstat: 256 Tests: 9 Failed: 1) Failed test: 9 Non-zero exit status: 1 Parse errors: Bad plan. You planned 101 tests but ran 9. t/050-async-client.t (Wstat: 256 Tests: 10 Failed: 1) Failed test: 10 Non-zero exit status: 1 Parse errors: Bad plan. You planned 80 tests but ran 10. t/060-sync-client.t (Wstat: 28416 Tests: 9 Failed: 0) Non-zero exit status: 111 Parse errors: Bad plan. You planned 57 tests but ran 9. t/080-tarantool.t (Wstat: 28416 Tests: 9 Failed: 0) Non-zero exit status: 111 Parse errors: Bad plan. You planned 33 tests but ran 9. t/090-parallel-requests.t (Wstat: 256 Tests: 12 Failed: 1) Failed test: 12 Non-zero exit status: 1 Parse errors: Bad plan. You planned 49 tests but ran 12. t/100-transform.t (Wstat: 28416 Tests: 11 Failed: 0) Non-zero exit status: 111 Parse errors: Bad plan. You planned 18 tests but ran 11. t/110-netsplit-readahead.t (Wstat: 256 Tests: 12 Failed: 1) Failed test: 12 Non-zero exit status: 1 Parse errors: Bad plan. You planned 24 tests but ran 12. Files=16, Tests=581, 8 wallclock secs ( 0.53 usr 0.07 sys + 6.64 cusr 0.90 csys = 8.14 CPU) Result: FAIL Failed 7/16 test programs. 4/581 subtests failed. Yeah, no clean chroot, lots of perl modules installed, but anyway. I actually just tried to quickly reproduce the 0.15-1 FTBFS but 0.35-1 works statement to mark 0.35-1 as fixed, but actually there seems to be at least some FTBFS issues, too. So next step is pbuilder (on amd64 though). And it actually builds fine, hence marking 0.35-1 as fixed. I'll try to figure out which other package caused the above mentioned FTBFS and file it as a separate (non-RC) bug. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704544: nova-common: fails to install: sed: can't read /etc/default/nova: No such file or directory
Package: nova-common Version: 2012.1.1-16 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package nova-common. (Reading database ... 17249 files and directories currently installed.) Unpacking nova-common (from .../nova-common_2012.1.1-16_all.deb) ... Setting up nova-common (2012.1.1-16) ... sed: can't read /etc/default/nova: No such file or directory dpkg: error processing nova-common (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: nova-common cheers, Andreas nova-common_2012.1.1-16.log.gz Description: GNU Zip compressed data
Processed: Re: CVE-2012-2942
Processing control commands: reopen -1 Bug #674447 {Done: Luk Claes l...@debian.org} [haproxy] CVE-2012-2942 '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 haproxy/1.4.15-1. -- 674447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674447 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#674447: CVE-2012-2942
Control: reopen -1 Hi Luk On Sat, Jun 23, 2012 at 10:03:21AM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the haproxy package: #674447: CVE-2012-2391 It has been closed by Luk Claes l...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Luk Claes l...@debian.org by replying to this email. I was currently looking at the list of bugs with security tag but not tracked in the security tracker[1] and noticed #674447. [1]: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=security;users=debian-secur...@lists.debian.org;exclude=tracked Noticed that you closed this bug with version 1.4.15-1. Is this correct? Looking at the code and the information the pach from [2] still applies and corrects the trash and trashlen. However /usr/share/doc/haproxy/configuration.txt.gz clearly says: tune.bufsize number Sets the buffer size to this size (in bytes). Lower values allow more sessions to coexist in the same amount of RAM, and higher values allow some applications with very large cookies to work. The default value is 16384 and can be changed at build time. It is strongly recommended not to change this from the default value, as very low values will break some services such as statistics, and values larger than default size will increase memory usage, possibly causing the system to run out of memory. At least the global maxconn parameter should be decreased by the same factor as this one is increased. So changing this from non-default value can result in the problem (downgrading severity for the bugreport?) [2]: http://haproxy.1wt.eu/git?p=haproxy-1.4.git;a=commitdiff;h=30297cb17147a8d339eb160226bcc08c91d9530b The mentioned patch was only applied 1.4.21 upstream. Would be great if you could doublecheck my comment above. Or why is it fixed in 1.4.15? Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: CVE-2012-2942
Processing control commands: reopen -1 Bug #674447 [haproxy] CVE-2012-2942 Bug 674447 is not marked as done; doing nothing. -- 674447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674447 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#704547: CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode.
Package: nvidia-glx Version: 195.36.24-1 Severity: critical Tags: security Justification: root security hole Quoting from http://nvidia.custhelp.com/app/answers/detail/a_id/3290 When the NVIDIA driver for the X Window System is operated in NoScanout mode, and an X client installs an ARGB cursor that is larger than the expected size (64x64 or 256x256, depending on the driver version), the driver will overflow a buffer. This can cause a denial of service (e.g., an X server segmentation fault), or could be exploited to achieve arbitrary code execution. Because the X server runs as setuid root in many configurations, an attacker could potentially use this vulnerability in those configurations to gain root privileges. To install an ARGB cursor, an application would require a connection to a running X server. Normally, X servers are configured to only accept authenticated connections from the local host, but some X servers may be configured to more permissively allow connections, and/or to allow connections over a network. NoScanout mode is enabled implicitly on NVIDIA products which lack display output connectors, and can be enabled explicitly on some other configurations with the X configuration option: Option UseDisplayDevice none NVIDIA GPU drivers for OSes other than Linux, FreeBSD, VMware ESX, and Solaris are not affected. This vulnerability has been present since NVIDIA driver version 195.22. The overflow is fixed in 304.88, 310.44, 313.30, and all drivers newer than those versions. NVIDIA recommends that users upgrade to a fixed driver version, or disable NoScanout mode, where possible. This vulnerability was identified by NVIDIA. There are no known reports of exploits of this vulnerability in the wild. Vulnerable versions in Debian: nvidia-graphics-drivers | 195.36.31-6squeeze2 | squeeze/non-free | source nvidia-graphics-drivers | 295.59-1~bpo60+2| squeeze-backports/non-free | source nvidia-graphics-drivers | 304.64-4| wheezy/non-free| source nvidia-graphics-drivers | 304.84-1| sid/non-free | source nvidia-graphics-drivers | 313.26-1| experimental/non-free | source sid and experimental will be fixed by a new upstream versions to be uploaded later today or tomorrow. No fix will be possible for squeeze and squeeze-backports (as this is a closed source driver and these ancient versions are no longer supported). Andreas -- 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#704531: liblangtag: FTBFS on arm*: test case fails
Processing commands for cont...@bugs.debian.org: severity 704531 important Bug #704531 [liblangtag] liblangtag: FTBFS on arm*: test case fails Severity set to 'important' from 'serious' tag 704531 + help Bug #704531 [liblangtag] liblangtag: FTBFS on arm*: test case fails Added tag(s) help. thanks Stopping processing here. Please contact me if you need assistance. -- 704531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704531 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#704531: liblangtag: FTBFS on arm*: test case fails
severity 704531 important tag 704531 + help thanks On Tue, Apr 02, 2013 at 05:26:05PM +0200, Hector Oron wrote: Severity: serious Wrong. It never built on arm* so this is not aerious. Your package fails to build on arm* architectures due to test case failure: Running suite(s): lt_tag_t 50%: Checks: 4, Failures: 0, Errors: 2 check-tag.c:46:E:Basic functionality:test_lt_tag_parse:0: (after this point) Test timeout expired check-tag.c:210:E:Basic functionality:test_lt_tag_match:0: (after this point) Test timeout expired FAIL: check-tag [...] make[5]: *** [check-TESTS] Error 1 == 1 of 9 tests failed Please report to http://github.com/tagoh/liblangtag/issues == Yes, I know. We even debugged this with upstream once and except the memory and cpu consumption going up quite fast nothing was found out. Also see: https://buildd.debian.org/status/package.php?p=liblangtagsuite=experimental I know, I *do* follow build logs of my packages. What if you would actually be helpful and not telling the obvious with a overinflated severity? :) Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701976: marked as done (ltt-control: FTBFS: /usr/bin/ld: tp.o: undefined reference to symbol 'rcu_dereference_sym')
Your message dated Tue, 02 Apr 2013 21:03:31 + with message-id e1un8md-0006vc...@franck.debian.org and subject line Bug#701976: fixed in ltt-control 2.1.1-2 has caused the Debian Bug report #701976, regarding ltt-control: FTBFS: /usr/bin/ld: tp.o: undefined reference to symbol 'rcu_dereference_sym' 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.) -- 701976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ltt-control Version: 2.1.1-1 Severity: serious Tags: patch sid User: debian-powerpc...@breakpoint.cc Usertags: powerpcspe Hi, ltt-control FTBFS on several arches like this: [...] make[4]: Entering directory `/«PKGBUILDDIR»/tests/tools/streaming' CC unit_tests.o CCLD unit_tests CC gen-ust-events.o CC tp.o CCLD gen-ust-events /usr/bin/ld: tp.o: undefined reference to symbol 'rcu_dereference_sym' /usr/bin/ld: note: 'rcu_dereference_sym' is defined in DSO /usr/lib/liburcu-bp.so.1 so try adding it to the linker command line /usr/lib/liburcu-bp.so.1: could not read symbols: Invalid operation collect2: ld returned 1 exit status make[4]: *** [gen-ust-events] Error 1 make[4]: Leaving directory `/«PKGBUILDDIR»/tests/tools/streaming' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/tests/tools' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»/tests' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2cd dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 [...] The attached patch fixes this by autoreconf'ing. Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.8.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash diff -ruN ltt-control-2.1.1.orig/debian/control ltt-control-2.1.1/debian/control --- ltt-control-2.1.1.orig/debian/control 2013-03-01 00:34:37.0 +0100 +++ ltt-control-2.1.1/debian/control 2013-03-01 10:48:43.238021748 +0100 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Jon Bernard jbern...@debian.org Build-Depends: debhelper (= 9), libpopt-dev, liburcu-dev (= 0.7.4), - liblttng-ust-dev (= 2.1.1-2) + liblttng-ust-dev (= 2.1.1-2), dh-autoreconf Standards-Version: 3.9.3 Vcs-Git: git://git.debian.org/git/collab-maint/ltt-control.git Vcs-Browser: http://git.debian.org/?p=collab-maint/ltt-control.git;a=summary diff -ruN ltt-control-2.1.1.orig/debian/rules ltt-control-2.1.1/debian/rules --- ltt-control-2.1.1.orig/debian/rules 2013-03-01 00:34:37.0 +0100 +++ ltt-control-2.1.1/debian/rules 2013-03-01 10:48:26.430017571 +0100 @@ -3,7 +3,7 @@ export DEB_BUILD_MAINT_OPTIONS := hardening=+all %: - dh $@ + dh $@ --with autoreconf override_dh_auto_install: # rename the bash completion file before installation ---End Message--- ---BeginMessage--- Source: ltt-control Source-Version: 2.1.1-2 We believe that the bug you reported is fixed in the latest version of ltt-control, which is due to be installed in the Debian FTP archive. 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 701...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jon Bernard jbern...@debian.org (supplier of updated ltt-control package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 02 Apr 2013 16:03:39 -0400 Source: ltt-control Binary: lttng-tools liblttng-ctl0 liblttng-ctl-dev ltt-bin liblttd0 liblttd-dev liblttctl0 liblttctl-dev Architecture: source amd64 Version: 2.1.1-2 Distribution: unstable Urgency: low Maintainer: Jon Bernard jbern...@debian.org Changed-By: Jon Bernard jbern...@debian.org Description: liblttctl-dev - Transitional package for liblttng-ctl-dev liblttctl0 - Transitional package for liblttng-ctl0 liblttd-dev - Transitional package for liblttng-ctl-dev liblttd0 - Transitional package for liblttng-ctl0 liblttng-ctl-dev - LTTng control and
Bug#704111: marked as done (clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.)
Your message dated Tue, 02 Apr 2013 21:03:12 + with message-id e1un8mk-0006gq...@franck.debian.org and subject line Bug#704111: fixed in clang 1:3.2-1~exp9 has caused the Debian Bug report #704111, regarding clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting. 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.) -- 704111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: clang Version: 1:3.0-6.1 Severity: grave x-debbugs-cc: debian-...@lists.debian.org; cfe-...@cs.uiuc.edu (note for non-debian people reading this, the version of clang in debian wheezy is a 3.0 based version which already has patches to make it invoke the linker with appropriate arguments. The llvm version also appears to be 3.0 again somewhat patched by debian) I recently discovered that the version of clang in debian wheezy and raspbian wheezy does not work correctly on either debian armhf or raspbian. It seems the problem is that clang can't work out what CPU type it should be using and defaults to something very low (specifically arm7tdmi). With this CPU selected clang silently fails to properly use the hard float ABI and as such any armhf code it generates is broken and won't call floating point routines correctly. It also causes an assertion failure in the bfd linker (but links successfully with the gold linker). Setting the CPU type to something sensible makes it implement the hard float ABI correctly and also stops the assertion failure in the bfd linker. I have managed to figure out how to patch clang to change the default CPU for armhf (patch attatched). However i'm not sure what it is best to set it to for debian armhf*. In particular this block of code from just below where my patch is applied seems to map all armv7 variants to a CPU type of coretex-a8. return llvm::StringSwitchconst char *(MArch) .Cases(armv2, armv2a,arm2) .Case(armv3, arm6) .Case(armv3m, arm7m) .Cases(armv4, armv4t, arm7tdmi) .Cases(armv5, armv5t, arm10tdmi) .Cases(armv5e, armv5te, arm1026ejs) .Case(armv5tej, arm926ej-s) .Cases(armv6, armv6k, arm1136jf-s) .Case(armv6j, arm1136j-s) .Cases(armv6z, armv6zk, arm1176jzf-s) .Case(armv6t2, arm1156t2-s) .Cases(armv7, armv7a, armv7-a, cortex-a8) .Cases(armv7r, armv7-r, cortex-r4) .Cases(armv7m, armv7-m, cortex-m3) .Case(ep9312, ep9312) .Case(iwmmxt, iwmmxt) .Case(xscale, xscale) .Cases(armv6m, armv6-m, cortex-m0) // If all else failed, return the most base CPU LLVM supports.
Bug#704551: libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite
Package: libdr-tarantool-perl Severity: serious Version: 0.35-1 Hi, while investigating #704267 I noticed the following: On a not that slow, but virtual machine with a load 1 and running amd64 Sid, the test t/110-netsplit-readahead.t, subtest delay maximum occassionally fails (and hence the package FTBFS) because it seems to expect that some test takes at maximum 200ms more than then minimum amount of time it expects to be needed. In the following example the test ran just 0.0024 seconds too long and hence failed: # Failed test 'delay maximum' # at t/110-netsplit-readahead.t line 141. # '0.26538348197937' # # '0.263' # Looks like you failed 1 test of 24. t/110-netsplit-readahead.t .. Sometimes the difference was over 0.1 seconds, too. Running t/110-netsplit-readahead.t many times in a row, the test failed for 25% of the runs for me. How to reproduce: p=0; f=0; for i in `seq 1 100`; do prove t/110-netsplit-readahead.t (( p++ )) || (( f++ )); done; echo p=$p f=$f (Since t/110-netsplit-readahead.t does not exist in the version of libdr-tarantool-perl in Wheezy, only the version in Sid is affected and 704267 is a different issue.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704266: libdr-tarantool-perl: FTBFS: test failure: t/110-netsplit-readahead.t
Control: retitle -1 libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite (t/110-netsplit-readahead.t) Control: merge -1 704551 Hi, Dominic Hargreaves wrote: This package FTBFS in a clean sid chroot: Sometimes: Andrey Rahmatullin wrote: I cannot reproduce this with an amd64 sid sbuild, the package builds corectly there. It's non-deterministically as I reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704551 This is actually the same issue. Merging. (Was hunting RC bugs in Wheezy and stumbled over #704266 when debugging #704267, but due to the focus on Wheezy I oversaw that this was more or less already reported.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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): Re: Bug#704266: libdr-tarantool-perl: FTBFS: test failure: t/110-netsplit-readahead.t
Processing control commands: retitle -1 libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite (t/110-netsplit-readahead.t) Bug #704266 [src:libdr-tarantool-perl] libdr-tarantool-perl: FTBFS: test failure: t/110-netsplit-readahead.t Changed Bug title to 'libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite (t/110-netsplit-readahead.t)' from 'libdr-tarantool-perl: FTBFS: test failure: t/110-netsplit-readahead.t' merge -1 704551 Bug #704266 [src:libdr-tarantool-perl] libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite (t/110-netsplit-readahead.t) Unable to merge bugs because: package of #704551 is 'libdr-tarantool-perl' not 'src:libdr-tarantool-perl' Failed to merge 704266: Did not alter merged bugs Debbugs::Control::set_merged('transcript', 'GLOB(0x2b27a30)', 'requester', 'Axel Beckert a...@debian.org', 'request_addr', '704266-sub...@bugs.debian.org', 'request_msgid', '20130402211908.ga11...@sym.noone.org', 'request_subject', ...) called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538 eval {...} called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537 Debbugs::Control::Service::control_line('line', 'merge -1 704551', 'clonebugs', 'HASH(0x2b3e680)', 'limit', 'HASH(0x2b458d0)', 'common_control_options', 'ARRAY(0x2b459a8)', 'errors', ...) called at /usr/lib/debbugs/process line 1039 -- 704266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704266 704551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704551 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: Processed (with 1 errors): Re: Bug#704266: libdr-tarantool-perl: FTBFS: test failure: t/110-netsplit-readahead.t
Processing commands for cont...@bugs.debian.org: # merge -1 704551 # Bug #704266 [src:libdr-tarantool-perl] libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite (t/110-netsplit-readahead.t) # Unable to merge bugs because: # package of #704551 is 'libdr-tarantool-perl' not 'src:libdr-tarantool-perl' # Failed to merge 704266: Did not alter merged bugs reassign 704551 src:libdr-tarantool-perl Bug #704551 [libdr-tarantool-perl] libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite Bug reassigned from package 'libdr-tarantool-perl' to 'src:libdr-tarantool-perl'. No longer marked as found in versions libdr-tarantool-perl/0.35-1. Ignoring request to alter fixed versions of bug #704551 to the same values previously set merge 704266 704551 Bug #704266 [src:libdr-tarantool-perl] libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite (t/110-netsplit-readahead.t) Bug #704551 [src:libdr-tarantool-perl] libdr-tarantool-perl: Non-deterministically FTBFS due to time measuring tests in test suite Marked as found in versions libdr-tarantool-perl/0.35-1. Merged 704266 704551 kthxbye Stopping processing here. Please contact me if you need assistance. -- 704266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704266 704551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704551 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#704547: marked as done (CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode.)
Your message dated Tue, 02 Apr 2013 21:48:56 + with message-id e1un94a-kh...@franck.debian.org and subject line Bug#704547: fixed in nvidia-graphics-drivers 304.88-1 has caused the Debian Bug report #704547, regarding CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode. 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.) -- 704547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nvidia-glx Version: 195.36.24-1 Severity: critical Tags: security Justification: root security hole Quoting from http://nvidia.custhelp.com/app/answers/detail/a_id/3290 When the NVIDIA driver for the X Window System is operated in NoScanout mode, and an X client installs an ARGB cursor that is larger than the expected size (64x64 or 256x256, depending on the driver version), the driver will overflow a buffer. This can cause a denial of service (e.g., an X server segmentation fault), or could be exploited to achieve arbitrary code execution. Because the X server runs as setuid root in many configurations, an attacker could potentially use this vulnerability in those configurations to gain root privileges. To install an ARGB cursor, an application would require a connection to a running X server. Normally, X servers are configured to only accept authenticated connections from the local host, but some X servers may be configured to more permissively allow connections, and/or to allow connections over a network. NoScanout mode is enabled implicitly on NVIDIA products which lack display output connectors, and can be enabled explicitly on some other configurations with the X configuration option: Option UseDisplayDevice none NVIDIA GPU drivers for OSes other than Linux, FreeBSD, VMware ESX, and Solaris are not affected. This vulnerability has been present since NVIDIA driver version 195.22. The overflow is fixed in 304.88, 310.44, 313.30, and all drivers newer than those versions. NVIDIA recommends that users upgrade to a fixed driver version, or disable NoScanout mode, where possible. This vulnerability was identified by NVIDIA. There are no known reports of exploits of this vulnerability in the wild. Vulnerable versions in Debian: nvidia-graphics-drivers | 195.36.31-6squeeze2 | squeeze/non-free | source nvidia-graphics-drivers | 295.59-1~bpo60+2| squeeze-backports/non-free | source nvidia-graphics-drivers | 304.64-4| wheezy/non-free| source nvidia-graphics-drivers | 304.84-1| sid/non-free | source nvidia-graphics-drivers | 313.26-1| experimental/non-free | source sid and experimental will be fixed by a new upstream versions to be uploaded later today or tomorrow. No fix will be possible for squeeze and squeeze-backports (as this is a closed source driver and these ancient versions are no longer supported). Andreas ---End Message--- ---BeginMessage--- Source: nvidia-graphics-drivers Source-Version: 304.88-1 We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers, which is due to be installed in the Debian FTP archive. 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 704...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated nvidia-graphics-drivers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Apr 2013 22:43:31 +0200 Source: nvidia-graphics-drivers Binary: nvidia-glx xserver-xorg-video-nvidia nvidia-glx-ia32 libgl1-nvidia-glx libxvmcnvidia1 libgl1-nvidia-glx-ia32 nvidia-alternative nvidia-kernel-dkms nvidia-kernel-source nvidia-vdpau-driver nvidia-vdpau-driver-ia32 nvidia-smi libcuda1 libcuda1-ia32 libnvidia-compiler libnvidia-compiler-ia32 libnvcuvid1 libnvidia-ml1 nvidia-opencl-common nvidia-opencl-icd nvidia-opencl-icd-ia32 nvidia-libopencl1 nvidia-libopencl1-ia32 libgl1-nvidia-alternatives libgl1-nvidia-alternatives-ia32 libglx-nvidia-alternatives nvidia-detect Architecture: source amd64 Version: 304.88-1 Distribution: unstable Urgency: low Maintainer: Debian NVIDIA
Processed: reassign 703313 to xserver-xorg-video-nvidia, tagging 703313, severity of 703313 is important ...
Processing commands for cont...@bugs.debian.org: reassign 703313 xserver-xorg-video-nvidia Bug #703313 [nvidia-kernel-dkms] nvidia-kernel-dkms: Upgrade breaks VT text consoles Bug reassigned from package 'nvidia-kernel-dkms' to 'xserver-xorg-video-nvidia'. No longer marked as found in versions nvidia-graphics-drivers/304.84-1. Ignoring request to alter fixed versions of bug #703313 to the same values previously set tags 703313 + upstream Bug #703313 [xserver-xorg-video-nvidia] nvidia-kernel-dkms: Upgrade breaks VT text consoles Added tag(s) upstream. severity 703313 important Bug #703313 [xserver-xorg-video-nvidia] nvidia-kernel-dkms: Upgrade breaks VT text consoles Severity set to 'important' from 'grave' retitle 703313 nvidia-glx: 304.64 - 304.84 breaks VT text consoles Bug #703313 [xserver-xorg-video-nvidia] nvidia-kernel-dkms: Upgrade breaks VT text consoles Changed Bug title to 'nvidia-glx: 304.64 - 304.84 breaks VT text consoles' from 'nvidia-kernel-dkms: Upgrade breaks VT text consoles' forcemerge 703313 703543 Bug #703313 [xserver-xorg-video-nvidia] nvidia-glx: 304.64 - 304.84 breaks VT text consoles Bug #703313 [xserver-xorg-video-nvidia] nvidia-glx: 304.64 - 304.84 breaks VT text consoles Marked as found in versions nvidia-graphics-drivers/304.84-1. Bug #703543 [xserver-xorg-video-nvidia] xserver-xorg-video-nvidia: After exiting xorg is the display dead, the prompt does not show Merged 703313 703543 thanks Stopping processing here. Please contact me if you need assistance. -- 703313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703313 703543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org: forcemerge 704486 704537 Bug #704486 [libobject-authority-perl,librole-commons-perl] librole-commons-perl: trying to overwrite '/usr/share/perl5/Object/AUTHORITY.pm', which is also in package libobject-authority-perl 0.004-1 Unable to merge bugs because: package of #704537 is 'libauthority-shared-perl,librole-commons-perl' not 'libobject-authority-perl,librole-commons-perl' Failed to forcibly merge 704486: Did not alter merged bugs Debbugs::Control::set_merged('transcript', 'GLOB(0x20b46c8)', 'requester', 'Michael Gilbert mgilb...@debian.org', 'request_addr', 'cont...@bugs.debian.org', 'request_msgid', 'CANTw=MPqaE_anUW2cjhipJZQ=MJbubc-4U32w2NiAvVkt9=f...@mail.gma...', 'request_subject', ...) called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552 eval {...} called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551 Debbugs::Control::Service::control_line('line', undef, 'clonebugs', 'HASH(0x1fec400)', 'limit', 'HASH(0x1febde8)', 'common_control_options', 'ARRAY(0x1febe30)', 'errors', ...) called at /usr/lib/debbugs/service line 474 thanks Stopping processing here. Please contact me if you need assistance. -- 704486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704486 704537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704537 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#704558: monobristol: does not start at all
Package: monobristol Version: 0.60.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, after installation monobristol does not start but gives the error Cannot open assembly '@expanded_libdir@/monobristol/monoBristol.exe':File not found Reproducible: always. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 Versions of packages monobristol depends on: ii bristol0.60.10-3 ii libglib2.0-cil 2.12.10-5 ii libgtk2.0-cil 2.12.10-5 ii libmono-corlib4.0-cil 2.10.8.1-8 ii libmono-posix4.0-cil 2.10.8.1-8 ii libmono-system-xml4.0-cil 2.10.8.1-8 ii libmono-system4.0-cil 2.10.8.1-8 ii mono-runtime 2.10.8.1-8 Versions of packages monobristol recommends: ii jackd 5 monobristol suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t
Hi again, Dominic Hargreaves wrote: On Sun, Mar 31, 2013 at 04:00:24PM +0600, Andrey Rahmatullin wrote: On Sat, Mar 30, 2013 at 05:37:27PM +, Dominic Hargreaves wrote: In a clean wheezy chroot: ok 51 - code not ok 52 - errstr # Failed test 'errstr' # at t/050-async-client.t line 268. # 'Lua error: stack overflow (call: out of stack)' # doesn't match '(?^:Partial key in)' FWIW it didn't fail here in a sid am64 chroot. FWIW I could _not_ reproduce that FTBFS when building the (0.15-1) package with pbuilder in a Wheezy chroot on Squeeze (all amd64), but I could reproduce this issue on a Wheezy i386 box (without chroot). Dominic, did you experience the build failure on i386? If so, this looks very similar to https://bugs.launchpad.net/tarantool/+bug/1021177 Citing from there: | After gcc-4.7 patches tarantool began returning different errors on | different architectures: | | if you call 'box.select()' (without arguments): | on amd64 You receive an error: Partial key in an exact match (key | field count: ... | but on i386 You receive an error: Lua error: stack overflow (call: | out of stack) | | both architectures returned the same errors until gcc4.7 patches The above LP bug report has been marked invalid with the following explanation: | I guess that you use different types of indexes on your hosts (HASH on | amd64 and TREE on i386) | | TREE index supports both box.select(0) and | box.space[x]:index[y]:iterator(box.index.ALL) without a key. | box.select() in this case returns all tuples from a space. The number | of returned tuples is limited only by Lua stack size. | If a result set is too large then Lua raises Lua error: stack | overflow (call: out of stack) error. | See https://bugs.launchpad.net/tarantool/+bug/1018775 This is again a (confirmed) bug report against tarantool and there is explained: | Currently select_range() can only return 8000 tuples, because it | puts these tuples into a Lua table, and then calls unpack() on the | table. So for me this currently looks like an issue in tarantool and not in libdr-tarantool-perl. I'm though not sure what's the best way to solve that. For wheezy patching the testsuite to accept both types of error messages is possibly an option to solve this issue. True; in sid, the failure (with 0.15-1) seems to come at # Failed test 'errstr' # at t/020-low_level_client.t line 125. # 'Duplicate key exists in unique index 0' # doesn't match '(?^:already exists)' Indeed. That test seems to check for an error message which likely comes from some of the packages built from the tarantool source package and not from libdr-tarantool-perl itself. And since tarantool in Wheezy has 1.4.6+20120629+2158-1 while Sid has 1.4.8+20130306.1415-1 I suspect that this error message has changed in tarantool between those two versions. That test probably should be more fault tolerant to multiple upstream versions. For the latter issue, patching the testsuite to match the current error message is sufficient. But since libdr-tarantool-perl has already 0.35-1 in Sid, it's no more necessary. (Oh, and my 0.35-1 FTBFS from my previous mail ended up in http://bugs.debian.org/704551) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 704537 in librole-commons-perl/0.101-1, found 704537 in libauthority-shared-perl/0.006-1
Processing commands for cont...@bugs.debian.org: found 704537 librole-commons-perl/0.101-1 Bug #704537 [libauthority-shared-perl,librole-commons-perl] librole-commons-perl and libauthority-shared-perl: error when trying to install together Marked as found in versions librole-commons-perl/0.101-1. found 704537 libauthority-shared-perl/0.006-1 Bug #704537 [libauthority-shared-perl,librole-commons-perl] librole-commons-perl and libauthority-shared-perl: error when trying to install together Marked as found in versions libauthority-shared-perl/0.006-1. thanks Stopping processing here. Please contact me if you need assistance. -- 704537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 704267 to reflect arch-specific FTBFS
Processing commands for cont...@bugs.debian.org: retitle 704267 libdr-tarantool-perl: FTBFS on i386 Wheezy (but not amd64): test failure: t/050-async-client.t Bug #704267 [src:libdr-tarantool-perl] libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t Changed Bug title to 'libdr-tarantool-perl: FTBFS on i386 Wheezy (but not amd64): test failure: t/050-async-client.t' from 'libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t' kthxbye Stopping processing here. Please contact me if you need assistance. -- 704267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704267 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: unarchiving 680484, reassign 680484 to scotch, fixed 680484 in 5.1.12b.dfsg-2, closing 680484
Processing commands for cont...@bugs.debian.org: unarchive 680484 Bug #680484 {Done: Andreas Tille ti...@debian.org} [gmap,scotch] gmap and scotch: error when trying to install together Unarchived Bug 680484 reassign 680484 scotch 5.1.12b.dfsg-1.1 Bug #680484 {Done: Andreas Tille ti...@debian.org} [gmap,scotch] gmap and scotch: error when trying to install together Bug reassigned from package 'gmap,scotch' to 'scotch'. No longer marked as found in versions scotch/5.1.12b.dfsg-1.1 and gmap/2012-06-12-1. No longer marked as fixed in versions scotch/5.1.12b.dfsg-2. Bug #680484 {Done: Andreas Tille ti...@debian.org} [scotch] gmap and scotch: error when trying to install together Marked as found in versions scotch/5.1.12b.dfsg-1.1. fixed 680484 5.1.12b.dfsg-2 Bug #680484 {Done: Andreas Tille ti...@debian.org} [scotch] gmap and scotch: error when trying to install together Marked as fixed in versions scotch/5.1.12b.dfsg-2. close 680484 Bug #680484 {Done: Andreas Tille ti...@debian.org} [scotch] gmap and scotch: error when trying to install together Bug 680484 is already marked as done; not doing anything. thanks Stopping processing here. Please contact me if you need assistance. -- 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#704546: Segfault when starting asterisk 1:1.6.2.9-2+squeeze10
On Tue, Apr 02, 2013 at 08:53:19PM +0200, Michael Abmayer wrote: Package: asterisk Version: 1:1.6.2.9-2+squeeze10 Severity: Grave Hi, a few seconds after starting asterisk it crashes with a segfault - in a similar manner like with the squeeze9-packages. squeeze8 works well without any problems. What info do you need else for fixing, how can I help? Sincerly, Michael uname -a Linux logorrhoe 2.6.32-5-amd64 #1 SMP Mon Feb 25 00:26:11 UTC 2013 x86_64 GNU/Linux cat /etc/debian_version 6.0.7 core follows: Core was generated by `asterisk -U asterisk -g -c'. Program terminated with signal 11, Segmentation fault. #0 0x7fafcddebf2a in strchrnul () from /lib/libc.so.6 (gdb) bt #0 0x7fafcddebf2a in strchrnul () from /lib/libc.so.6 #1 0x7fafcddacd2f in vfprintf () from /lib/libc.so.6 #2 0x7fafcddd2732 in vsnprintf () from /lib/libc.so.6 #3 0x00461ec8 in ast_devstate_changed (state=AST_DEVICE_UNKNOWN, cachable=3250240028, fmt=0x7fff5199f990 \030) at devicestate.c:524 #4 0x7fafc1b92166 in pbx_capi_register_device_state_providers () at chan_capi_devstate.c:62 #5 0x7fafc1b7f545 in load_module () at chan_capi.c:8897 #6 0x0048afd7 in start_resource (mod=0x7fafc403c350) at loader.c:747 #7 0x0048b58f in load_resource_list (load_order=value optimized out, global_symbols=0, mod_count=value optimized out) at loader.c:925 #8 0x0048b909 in load_modules (preload_only=0) at loader.c:1072 #9 0x004341e4 in main (argc=value optimized out, argv=value optimized out) at asterisk.c:3694 (gdb) bt full #0 0x7fafcddebf2a in strchrnul () from /lib/libc.so.6 No symbol table info available. #1 0x7fafcddacd2f in vfprintf () from /lib/libc.so.6 No symbol table info available. #2 0x7fafcddd2732 in vsnprintf () from /lib/libc.so.6 No symbol table info available. #3 0x00461ec8 in ast_devstate_changed (state=AST_DEVICE_UNKNOWN, cachable=3250240028, fmt=0x7fff5199f990 \030) at devicestate.c:524 buf = '\000' repeats 40 times, @\000\000\000\000\000\000\000\230\216\f?\177\000\000\250\216\f?\177\000\000\000\000\000\000\000\000\000\000@\000\000\000\000\000\000 ap = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fff5199fa80, reg_save_area = 0x7fff5199f9b0}} #4 0x7fafc1b92166 in pbx_capi_register_device_state_providers () at chan_capi_devstate.c:62 capiController = 0x7fff5199f9b0 i = 1 capi_num_controllers = value optimized out #5 0x7fafc1b7f545 in load_module () at chan_capi.c:8897 The segfault is at loading chan_capi.so . Can you please try disabling its load and see if Asterisk then loads successfully? To disable it, add the line 'noload = chan_capi.so' to the section '[modules]' in /etc/asterisk/modules.conf . cfg = 0x7fafc1db4b70 res = 0 __PRETTY_FUNCTION__ = load_module __FUNCTION__ = load_module -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704561: libwsutil-dev: fails to upgrade from squeeze - trying to overwrite /usr/include/wireshark/wsutil/file_util.h
Package: libwsutil-dev Version: 1.8.2-5wheezy1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'wheezy' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously deselected package libwsutil-dev. Unpacking libwsutil-dev (from .../libwsutil-dev_1.8.2-5wheezy1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libwsutil-dev_1.8.2-5wheezy1_amd64.deb (--unpack): trying to overwrite '/usr/include/wireshark/wsutil/file_util.h', which is also in package wireshark-dev 1.2.11-6+squeeze9 cheers, Andreas wireshark-dev=1.2.11-6+squeeze9_libwsutil-dev=1.8.2-5wheezy1.log.gz Description: GNU Zip compressed data
Processed: package unusable with Wheezy default Ruby version
Processing control commands: severity -1 serious Bug #704249 [ruby-fusefs] ruby-fusefs: undefined symbol STR2CSTR with Ruby 1.9 Severity set to 'serious' from 'normal' tags -1 -patch Bug #704249 [ruby-fusefs] ruby-fusefs: undefined symbol STR2CSTR with Ruby 1.9 Removed tag(s) patch. -- 704249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704249 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#704562: live-config-doc: fails to upgrade from squeeze - trying to overwrite /usr/share/man/de/man7/live-config.7.gz
Package: live-config-doc Version: 3.0.21-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'wheezy' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously deselected package live-config-doc. (Reading database ... 6403 files and directories currently installed.) Unpacking live-config-doc (from .../live-config-doc_3.0.21-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/live-config-doc_3.0.21-1_all.deb (--unpack): trying to overwrite '/usr/share/man/de/man7/live-config.7.gz', which is also in package live-config 2.0.15-1 configured to not write apport reports Errors were encountered while processing: /var/cache/apt/archives/live-config-doc_3.0.21-1_all.deb cheers, Andreas live-config=2.0.15-1_live-config-doc=3.0.21-1.log.gz Description: GNU Zip compressed data
Bug#704426: marked as done (isc-dhcp: cve-2013-2494)
Your message dated Wed, 03 Apr 2013 01:02:36 + with message-id e1unc60-00072i...@franck.debian.org and subject line Bug#704426: fixed in isc-dhcp 4.2.2.dfsg.1-5+deb70u4 has caused the Debian Bug report #704426, regarding isc-dhcp: cve-2013-2494 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.) -- 704426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: isc-dhcp severity: serious version: 4.2.2.dfsg.1-5 The embedded bind library is affected by the subject issue. I am currently working on fixed packages. ---End Message--- ---BeginMessage--- Source: isc-dhcp Source-Version: 4.2.2.dfsg.1-5+deb70u4 We believe that the bug you reported is fixed in the latest version of isc-dhcp, which is due to be installed in the Debian FTP archive. 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 704...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert mgilb...@debian.org (supplier of updated isc-dhcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 01 Apr 2013 00:41:48 + Source: isc-dhcp Binary: isc-dhcp-server isc-dhcp-server-dbg isc-dhcp-server-ldap isc-dhcp-common isc-dhcp-dev isc-dhcp-client isc-dhcp-client-dbg isc-dhcp-client-udeb isc-dhcp-relay isc-dhcp-relay-dbg Architecture: source amd64 Version: 4.2.2.dfsg.1-5+deb70u4 Distribution: testing-proposed-updates Urgency: high Maintainer: Debian ISC DHCP maintainers pkg-dhcp-de...@lists.alioth.debian.org Changed-By: Michael Gilbert mgilb...@debian.org Description: isc-dhcp-client - ISC DHCP client isc-dhcp-client-dbg - ISC DHCP client (debugging symbols) isc-dhcp-client-udeb - ISC DHCP Client for debian-installer (udeb) isc-dhcp-common - common files used by all the isc-dhcp* packages isc-dhcp-dev - API for accessing and modifying the DHCP server and client state isc-dhcp-relay - ISC DHCP relay daemon isc-dhcp-relay-dbg - DHCP relay daemon (debugging symbols) isc-dhcp-server - ISC DHCP server for automatic IP address assignment isc-dhcp-server-dbg - ISC DHCP server for automatic IP address assignment (debug) isc-dhcp-server-ldap - DHCP server able to use LDAP as backend Closes: 704426 Changes: isc-dhcp (4.2.2.dfsg.1-5+deb70u4) testing-proposed-updates; urgency=high . * Fix cve-2013-2494: issues with regular expression handling in the embedded bind library (closes: #704426). Checksums-Sha1: 176b4d4d910ed2836278e453742cf916e5b78cdb 3329 isc-dhcp_4.2.2.dfsg.1-5+deb70u4.dsc cb33c75de9249f1b799ca019e68f30a7ce1ac0b6 97659 isc-dhcp_4.2.2.dfsg.1-5+deb70u4.debian.tar.gz 4f74dc33c9ba3c11fc21dec94c9bdb9ff9e9ad70 935184 isc-dhcp-server_4.2.2.dfsg.1-5+deb70u4_amd64.deb ea2f7f2ed29806e7068d9c7351c32dc936bbe6e4 2533136 isc-dhcp-server-dbg_4.2.2.dfsg.1-5+deb70u4_amd64.deb 56919cbdf7c0fc2a9a7f76de7247f223cb32a1bc 891604 isc-dhcp-server-ldap_4.2.2.dfsg.1-5+deb70u4_amd64.deb eb353c4d566c82ceb7ce0206e81880ee9ee04f3c 851576 isc-dhcp-common_4.2.2.dfsg.1-5+deb70u4_amd64.deb 1d552eee2eb966e039d7492611cc03ce4b01f80b 773502 isc-dhcp-dev_4.2.2.dfsg.1-5+deb70u4_amd64.deb 8bd1f0ee6567e800ea1da815fde11ff81eefa357 791970 isc-dhcp-client_4.2.2.dfsg.1-5+deb70u4_amd64.deb 965aaf848b102d79d84b786e9165526db0e8f0f0 2208626 isc-dhcp-client-dbg_4.2.2.dfsg.1-5+deb70u4_amd64.deb cf2a03910e50761c57d7b291222b15bf9643ac68 600898 isc-dhcp-client-udeb_4.2.2.dfsg.1-5+deb70u4_amd64.udeb ab169d0649ff221d659f60f34d44c065e2d7f96d 732738 isc-dhcp-relay_4.2.2.dfsg.1-5+deb70u4_amd64.deb 3880b8dc383878d90b664b7d8179d52bb073bdb3 2113056 isc-dhcp-relay-dbg_4.2.2.dfsg.1-5+deb70u4_amd64.deb Checksums-Sha256: ba4a4de2e171c9eecf1008c5f456616934356165472dddcb685aef3801b5b713 3329 isc-dhcp_4.2.2.dfsg.1-5+deb70u4.dsc fe3b587b5ae9858bedea3efa24467661e3ed6dd7882e16a4d0efe65c5b9ef707 97659 isc-dhcp_4.2.2.dfsg.1-5+deb70u4.debian.tar.gz e7b36fa1ac9e7ab843c750585abee2d27abaf2dacd8268f19d7037f7161a5452 935184 isc-dhcp-server_4.2.2.dfsg.1-5+deb70u4_amd64.deb e6e941b159a4a59245b4aa88a4ea5b0f9c83ec3f328ede7c30ec562dd3a07d6f 2533136 isc-dhcp-server-dbg_4.2.2.dfsg.1-5+deb70u4_amd64.deb 25ccc14577a698d5c33f6bef83503a6aea003eebdedb766ce480456c84e2c7c2 891604
Processed: your mail
Processing commands for cont...@bugs.debian.org: notfound 702071 0.18.4-5 Bug #702071 {Done: Pino Toscano p...@debian.org} [poppler] CVE-2013-1788, CVE-2013-1789 and CVE-2013-1790 There is no source info for the package 'poppler' at version '0.18.4-5' with architecture '' Unable to make a source version for version '0.18.4-5' No longer marked as found in versions poppler/0.18.4-5. found 702071 0.12.4-1 Bug #702071 {Done: Pino Toscano p...@debian.org} [poppler] CVE-2013-1788, CVE-2013-1789 and CVE-2013-1790 There is no source info for the package 'poppler' at version '0.12.4-1' with architecture '' Unable to make a source version for version '0.12.4-1' Marked as found in versions 0.12.4-1. thanks Stopping processing here. Please contact me if you need assistance. -- 702071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702071 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): Re: Bug#704567: CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode.
Processing commands for cont...@bugs.debian.org: # duplicate bug report forcemerge 704547 704567 Bug #704547 {Done: Andreas Beckmann a...@debian.org} [nvidia-glx] CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode. Unable to merge bugs because: package of #704567 is 'nvidia-graphics-drivers' not 'nvidia-glx' Failed to forcibly merge 704547: Did not alter merged bugs Debbugs::Control::set_merged('transcript', 'GLOB(0xaae750)', 'requester', 'Vincent Cheng vincentc1...@gmail.com', 'request_addr', 'cont...@bugs.debian.org', 'request_msgid', 'CACZd_tAc_VMOK5v42fuA=EM-FA=xejrcb9uw_1ak2xh2g0e...@mail.gma...', 'request_subject', ...) called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552 eval {...} called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551 Debbugs::Control::Service::control_line('line', undef, 'clonebugs', 'HASH(0x1aa0400)', 'limit', 'HASH(0x1a9fde8)', 'common_control_options', 'ARRAY(0x1a9fe30)', 'errors', ...) called at /usr/lib/debbugs/service line 474 thanks Stopping processing here. Please contact me if you need assistance. -- 704547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704547 704567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704567 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: merging 704547 and 704567
Processing commands for cont...@bugs.debian.org: reassign 704567 nvidia-glx Bug #704567 [nvidia-graphics-drivers] CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode. Bug reassigned from package 'nvidia-graphics-drivers' to 'nvidia-glx'. No longer marked as found in versions 195.36.31-6squeeze2. Ignoring request to alter fixed versions of bug #704567 to the same values previously set forcemerge 704547 704567 Bug #704547 {Done: Andreas Beckmann a...@debian.org} [nvidia-glx] CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode. Bug #704567 [nvidia-glx] CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB Cursor Buffer Overflow in NoScanout Mode. Severity set to 'critical' from 'important' Marked Bug as done Marked as fixed in versions nvidia-graphics-drivers/304.88-1. Marked as found in versions nvidia-graphics-drivers/195.36.24-1. Added tag(s) security. Merged 704547 704567 thanks Stopping processing here. Please contact me if you need assistance. -- 704547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704547 704567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704567 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#704572: freetds: Add -lgcrypt to LDFLAGS to fix underlinking
Package: freetds Version: 0.91-2 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring ubuntu-patch Dear Maintainer, During a test rebuild of all packages in Ubuntu, it was found that freetds failed to build from source because it did not explicitly link against libgcrypt. In Ubuntu, the attached patch was applied to achieve the following: * debian/rules: Add -lgcrypt to LDFLAGS to fix underlinking FTBFS. Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers raring-updates APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring'), (100, 'raring-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-15-generic (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash === modified file 'debian/rules' --- debian/rules 2011-11-14 21:20:25 + +++ debian/rules 2013-04-03 02:12:54 + @@ -1,6 +1,7 @@ #!/usr/bin/make -f export DEB_CFLAGS_MAINT_APPEND = -Wall -DDBLIB_UNIMPLEMENTED=1 +export DEB_LDFLAGS_MAINT_APPEND = -lgcrypt DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
Bug#704573: libwebp: cve-2012-5127
Package: libwebp Severity: serious Version: 0.1.3-3 Tags: security Hi, the following vulnerability was published for libwebp. CVE-2012-5127[0]: | Integer overflow in Google Chrome before 23.0.1271.64 allows remote | attackers to cause a denial of service (out-of-bounds read) or | possibly have unspecified other impact via a crafted WebP image. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5127 http://security-tracker.debian.org/tracker/CVE-2012-5127 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704573: Acknowledgement (libwebp: cve-2012-5127)
I've uploaded an nmu fixing this issue to delayed/5. Please see attached patch. Best wishes, Mike libwebp.patch Description: Binary data
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 704573 patch Bug #704573 [libwebp] libwebp: cve-2012-5127 Added tag(s) patch. tag 704573 pending Bug #704573 [libwebp] libwebp: cve-2012-5127 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 704573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704573 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#704572: freetds: Add -lgcrypt to LDFLAGS to fix underlinking
Control: severity -1 important Control: tags -1 - patch Hi Logan, On Tue, Apr 02, 2013 at 10:15:54PM -0400, Logan Rosen wrote: Package: freetds Version: 0.91-2 Severity: serious Tags: patch Dear Maintainer, During a test rebuild of all packages in Ubuntu, it was found that freetds failed to build from source because it did not explicitly link against libgcrypt. In Ubuntu, the attached patch was applied to achieve the following: * debian/rules: Add -lgcrypt to LDFLAGS to fix underlinking FTBFS. Thanks for considering the patch. Thanks for the patch. FWIW I'm going to upload a different solution that addresses this in the upstream build rules where it should be rather than working around it in debian/rules. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Processed: Re: Bug#704572: freetds: Add -lgcrypt to LDFLAGS to fix underlinking
Processing control commands: severity -1 important Bug #704572 [freetds] freetds: Add -lgcrypt to LDFLAGS to fix underlinking Severity set to 'important' from 'serious' tags -1 - patch Bug #704572 [freetds] freetds: Add -lgcrypt to LDFLAGS to fix underlinking Removed tag(s) patch. -- 704572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704572 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#704562: live-config-doc: fails to upgrade from squeeze - trying to overwrite /usr/share/man/de/man7/live-config.7.gz
Processing commands for cont...@bugs.debian.org: tag 704562 pending Bug #704562 [live-config-doc] live-config-doc: fails to upgrade from squeeze - trying to overwrite /usr/share/man/de/man7/live-config.7.gz Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 704562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704562 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