Bug#701832: doxygen consistently segfaults on kfreebsd-i386 when building opendnssec documentation
On Wed, Feb 27, 2013 at 07:24:59PM +0100, Ond??ej Surý wrote: the doxygen segfaults on kfreebsd-i386 when building opendnssec package and it blocks it's transition from unstable to testing. How do you know that it segfaults? I looked at your build logs, but those looked more like hanging. They were all hanging while creating dot graphs (using multiple threads), so maybe this is a race condition leading to a dead lock? On the other hand they all hanged on graph 37 out of 144, so it appears deterministic. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701832: doxygen consistently segfaults on kfreebsd-i386 when building opendnssec documentation
Right, I have jumped to conclusions prematurely. Anyway it still blocks only on kfreebsd-i386. If you have an idea how to do a workaround, I am open to anything. Ondrej On Thu, Feb 28, 2013 at 9:13 AM, Helmut Grohne hel...@subdivi.de wrote: On Wed, Feb 27, 2013 at 07:24:59PM +0100, Ond??ej Surı wrote: the doxygen segfaults on kfreebsd-i386 when building opendnssec package and it blocks it's transition from unstable to testing. How do you know that it segfaults? I looked at your build logs, but those looked more like hanging. They were all hanging while creating dot graphs (using multiple threads), so maybe this is a race condition leading to a dead lock? On the other hand they all hanged on graph 37 out of 144, so it appears deterministic. Helmut -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625956: marked as done (src:doxygen: missing source for src/jquery.js)
Your message dated Thu, 28 Feb 2013 09:32:36 + with message-id e1uazqu-0001zk...@franck.debian.org and subject line Bug#625956: fixed in doxygen 1.8.1.2-2 has caused the Debian Bug report #625956, regarding src:doxygen: missing source for src/jquery.js 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.) -- 625956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:doxygen Version: 1.7.4-1 Severity: serious Tags: upstream Justification: missing source The doxygen source package contains only the compressed (minified) version of jquery.js. Of course it probably shouldn't embed jquery.js at all, but if it does, it should embed an editable, uncompressed version. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (900, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: doxygen Source-Version: 1.8.1.2-2 We believe that the bug you reported is fixed in the latest version of doxygen, 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 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Helmut Grohne hel...@subdivi.de (supplier of updated doxygen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 28 Feb 2013 10:09:45 +0100 Source: doxygen Binary: doxygen doxygen-latex doxygen-doc doxygen-gui Architecture: source amd64 all Version: 1.8.1.2-2 Distribution: unstable Urgency: low Maintainer: Matthias Klose d...@debian.org Changed-By: Helmut Grohne hel...@subdivi.de Description: doxygen- Documentation system for C, C++, Java, Python and other languages doxygen-doc - Documentation for doxygen doxygen-gui - GUI configuration tool for doxygen doxygen-latex - Documentation system for C, C++, Java, Python and other languages Closes: 625956 Changes: doxygen (1.8.1.2-2) unstable; urgency=low . [ Mònica Ramírez Arceda ] * Non-maintainer upload. * Include jquery-1.7.1.js source in debian/jquery and update its license. This file has the source code for src/jquery_p[123].js. Closes: #625956. * Include jquery.scrollTo-1.4.2.js in debian/jquery and add its license. This file has the source code for src/jquery_fx.js. * Include jquery-ui*.js and jquery.ba-hashchange.js in debian/jquery and add their licenses. These files have the source code for src/jquery_ui.js. . [ Helmut Grohne ] * Added myself as uploader. Checksums-Sha1: a091e0e630b633b9d2abd9da178338be18d824ea 1466 doxygen_1.8.1.2-2.dsc 9678b1b76deec1342924c0a833956251b0069299 197070 doxygen_1.8.1.2-2.debian.tar.gz ddc3c1bd1b8de93d8daa8247d957fd64dedf2517 2578406 doxygen_1.8.1.2-2_amd64.deb 2d22fd5585f0618b3254d413d8bb1e16c7fa06e2 263290 doxygen-gui_1.8.1.2-2_amd64.deb f240f6e7d634471c5e25882b5bb2c0dde3f4908c 11284 doxygen-latex_1.8.1.2-2_all.deb b97632ff6a1e787db1d6758d5ca8ae905678c436 2150946 doxygen-doc_1.8.1.2-2_all.deb Checksums-Sha256: 520c95c9379c83c228b12fe3e40f9618f759a98db8981411454e8b4a60b0bb98 1466 doxygen_1.8.1.2-2.dsc 09a8043d418fc80b849309696ccd017676f55d5e4c92e32d3280ce0579b0030d 197070 doxygen_1.8.1.2-2.debian.tar.gz 82054cd9574bcbaa090c2ea48ab9d01c4d355389acf7d0ebec73bf5d6e5d1a9b 2578406 doxygen_1.8.1.2-2_amd64.deb dad1b7171cd2577ae83315514bc06ee7d96df2f1c2f859ffa9616ed473426c33 263290 doxygen-gui_1.8.1.2-2_amd64.deb 2ae6a864a96a157f04a593938d6d8a552ec3c7d6ea9800a41b3c0a68737d87db 11284 doxygen-latex_1.8.1.2-2_all.deb a68e7d90414c5ff0200b08d7a596da2f8319fc39e4485fe1bf388e0c31cee3a5 2150946 doxygen-doc_1.8.1.2-2_all.deb Files: e590b11e7e25bef496e43dc1429eb47e 1466 devel optional doxygen_1.8.1.2-2.dsc e83ea3b52c371b6bd4bda9bdfde60c0a 197070 devel optional doxygen_1.8.1.2-2.debian.tar.gz 0feeb89cf7f00c1174fecba3975e0b33 2578406 devel optional doxygen_1.8.1.2-2_amd64.deb 7ccb613435767286973d54724c85d5db 263290 devel optional doxygen-gui_1.8.1.2-2_amd64.deb 2dab7035812b37b4b9b5bdcd81d59143 11284 devel optional
Bug#701868: cannot connect to IRC server
Package: libssl1.0.0 Version: 1.0.1e-1 Severity: grave This version of OpenSSL makes it impossible to connect to my company's IRC server. I have tried four IRC clients (irssi, kvirc, konversation and quassel) and all of them disconnect shortly after connecting. ircssi gives this error: SSL read error: decryption failed or bad record mac kvirc says: [09:39:59] [irc.example.net]: *** You are connected using SSL cipher DHE-RSA-AES-256-CBC-SHA1 [09:40:00] [SSL ERROR]: decryption failed or bad record mac [09:40:00] [SOCKET ERROR]: Secure Socket Layer error [09:40:00] Connection terminated [irc.example.net (1.2.3.4:1234)] I have verified that everything works when I downgrade to 1.0.1c-4. Probably same as this bug: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/113 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-better (SMP w/4 CPU cores; PREEMPT) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssl depends on: ii libc62.13-38 ii libssl1.0.0 1.0.1e-1 ii zlib1g 1:1.2.7.dfsg-13 openssl recommends no packages. Versions of packages openssl suggests: ii ca-certificates 20130119 -- 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#701864: 'Frontier Artistic License' text missing in debian/copyright
tag 701864 +accepted thanks On Thu, Feb 28, 2013 at 09:41:42AM +0200, Damyan Ivanov wrote: Package: cfengine3 Version: 3.0.5+dfsg-1 Severity: serious The copyright file of cfengine3 version 3.0.5+dfsg-1 misses the full text of the Frontier Artistic License, violating Debian Policy 12.5. A pointer to a web page with the license is not a verbatim copy of its copyright information and distribution license. Thanks for opening the bug, I will fix it this weekend. Cheers Antonio -- 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#701864: 'Frontier Artistic License' text missing in debian/copyright
Processing commands for cont...@bugs.debian.org: tag 701864 +accepted Unknown tag/s: accepted. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore. Bug #701864 [cfengine3] 'Frontier Artistic License' text missing in debian/copyright Requested to add no tags; doing nothing. thanks Stopping processing here. Please contact me if you need assistance. -- 701864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701864 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#701744: [Pkg-xen-devel] Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
On Thu, 2013-02-28 at 07:47 +0100, Ingo Jürgensmann wrote: Am 26.02.2013 um 19:19 schrieb Ian Campbell i...@hellion.org.uk: So, was the hypervisor upgrade also accompanied by a kernel update, in either the dom0 or guest domains? If so what versions were involved and where? Additionally to the last mail: After running two days stable with the downgraded packages, I've now upgraded the hypervisor package to xen-hypervisor-4.0-amd64_4.0.1-5.6_amd64.deb again and rebooted. If the machine runs stable with that, I'd say the kernel package is broken. And if the issues popping up again now, it's the hypervisor. I am 99% positive it will turn out to be the kernel, but please do let us know. All domUs are still running the updated kernel packages (pre DSA-2632-1), the dom0 the downgraded kernel package. When you reach a conclusion (assuming it is the one I expect!) please can you confirm the fixed+broken kernel package versions so I can reassign as appropriate. Unfortunately I'm about to go travelling for a week but I have asked one of my colleagues to try and take a look at this. Ian. -- Ian Campbell A beginning is the time for taking the most delicate care that balances are correct. -- Princess Irulan, Manual of Maud'Dib -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701686: marked as done (bowtie2: FTBFS[!linux]: help2man: can't get `--help' info)
Your message dated Thu, 28 Feb 2013 12:32:30 + with message-id e1ub2f0-0001yp...@franck.debian.org and subject line Bug#701686: fixed in bowtie2 2.1.0-1 has caused the Debian Bug report #701686, regarding bowtie2: FTBFS[!linux]: help2man: can't get `--help' info 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.) -- 701686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:bowtie2 Version: 2.0.6-1 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: debian/rules override_dh_auto_install make[1]: Entering directory `/build/buildd-bowtie2_2.0.6-1-kfreebsd-amd64-TCHdXD/bowtie2-2.0.6' mkdir -p /build/buildd-bowtie2_2.0.6-1-kfreebsd-amd64-TCHdXD/bowtie2-2.0.6/debian/bowtie2/usr/share/man/man1/ help2man --name=wrapper for bowtie2-align --no-info \ /build/buildd-bowtie2_2.0.6-1-kfreebsd-amd64-TCHdXD/bowtie2-2.0.6/bowtie2 /build/buildd-bowtie2_2.0.6-1-kfreebsd-amd64-TCHdXD/bowtie2-2.0.6/debian/bowtie2/usr/share/man/man1/bowtie2.1 help2man: can't get `--help' info from /build/buildd-bowtie2_2.0.6-1-kfreebsd-amd64-TCHdXD/bowtie2-2.0.6/bowtie2 Try `--no-discard-stderr' if option outputs to stderr make[1]: *** [override_dh_auto_install] Error 2 make[1]: Leaving directory `/build/buildd-bowtie2_2.0.6-1-kfreebsd-amd64-TCHdXD/bowtie2-2.0.6' make: *** [binary-arch] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=bowtie2arch=kfreebsd-amd64ver=2.0.6-1stamp=1361653538 Regards Christoph If you have further questions please mail debian-...@lists.debian.org ---End Message--- ---BeginMessage--- Source: bowtie2 Source-Version: 2.1.0-1 We believe that the bug you reported is fixed in the latest version of bowtie2, 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. Alexandre Mestiashvili a...@biotec.tu-dresden.de (supplier of updated bowtie2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 27 Feb 2013 15:58:40 +0100 Source: bowtie2 Binary: bowtie2 bowtie2-examples Architecture: source amd64 all Version: 2.1.0-1 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Alexandre Mestiashvili a...@biotec.tu-dresden.de Description: bowtie2- ultrafast memory-efficient short read aligner bowtie2-examples - Examples for bowtie2, Closes: 701686 Changes: bowtie2 (2.1.0-1) unstable; urgency=low . * - d/help2man-wrapper: as kindly suggested by Andreas Tille Closes: #701686 - d/rules: use help2man-wrapper instead of help2man to generate man pages * Imported Upstream version 2.1.0 * refreshed patches Checksums-Sha1: b1a1d39e3d9aa05ae2f4a174d8b47a2daa487bcc 2159 bowtie2_2.1.0-1.dsc 8e3d60d9e834c55a8381dd6b5a2fc8b34d95e35f 5534486 bowtie2_2.1.0.orig.tar.gz cf79aaee824fce732957d6b187a383a772b8e128 6289 bowtie2_2.1.0-1.debian.tar.gz 4dcb3e1af03c64da6ff6e077ec2dd44aa2085939 1060158 bowtie2_2.1.0-1_amd64.deb 0c1afaffa2ca1d84757d587acbfe3a48dab8bdae 4882646 bowtie2-examples_2.1.0-1_all.deb Checksums-Sha256: 069d3d14f8df7689b4475fccbb2b4d93e82bfb49777fe6a584a0e5297d431ed9 2159 bowtie2_2.1.0-1.dsc 6d24be8af7fc2b6c43e329bcfa98a9108e7f8338c6bacf651642b871b76a 5534486 bowtie2_2.1.0.orig.tar.gz 9b93ff50412a8e1e0d69e09b03f916ffd88fa24b1490bf424d87be077f1965f4 6289 bowtie2_2.1.0-1.debian.tar.gz d080d4ddd2dc0e93ca0733017da8ca2c79392e3f724019cce7dfce6d4e26bded 1060158 bowtie2_2.1.0-1_amd64.deb 33eeea0349932084af9036cb44275d5039d52c2ff82d370f5772969031bad069 4882646 bowtie2-examples_2.1.0-1_all.deb Files: 39165d80cfd03b94f479876f9b23c00b 2159 science extra bowtie2_2.1.0-1.dsc 874af34a581619af6ff04b637d3bed53 5534486 science extra bowtie2_2.1.0.orig.tar.gz 85d94a31749c78b78f14db088f641079 6289 science extra bowtie2_2.1.0-1.debian.tar.gz
Bug#700710: marked as done (fcitx-libs-gclient: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libfcitx-gclient.so.0.1)
Your message dated Thu, 28 Feb 2013 12:48:23 + with message-id e1ub2un-0006a2...@franck.debian.org and subject line Bug#700710: fixed in fcitx 1:4.2.7-2 has caused the Debian Bug report #700710, regarding fcitx-libs-gclient: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libfcitx-gclient.so.0.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 700710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fcitx-libs-gclient Version: 1:4.2.7-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + fcitx-libs-dev Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 unselected package fcitx-libs-gclient:amd64. Unpacking fcitx-libs-gclient:amd64 (from .../fcitx-libs-gclient_1%3a4.2.7-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/fcitx-libs-gclient_1%3a4.2.7-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libfcitx-gclient.so.0.1', which is also in package fcitx-libs:amd64 1:4.2.4.1-7 cheers, Andreas fcitx-libs-dev_1:4.2.7-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: fcitx Source-Version: 1:4.2.7-2 We believe that the bug you reported is fixed in the latest version of fcitx, 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 700...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su wzss...@gmail.com (supplier of updated fcitx 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: Thu, 28 Feb 2013 17:00:35 +0800 Source: fcitx Binary: fcitx fcitx-bin fcitx-data fcitx-libs fcitx-libs-gclient fcitx-libs-qt fcitx-libs-dev gir1.2-fcitx-1.0 fcitx-dbg fcitx-ui-classic fcitx-frontend-all fcitx-frontend-gtk2 fcitx-frontend-gtk3 fcitx-frontend-qt4 fcitx-pinyin fcitx-qw fcitx-table fcitx-table-all fcitx-table-bingchan fcitx-table-cangjie fcitx-table-dianbaoma fcitx-table-erbi fcitx-table-wanfeng fcitx-table-wbpy fcitx-table-wubi fcitx-table-ziranma fcitx-modules fcitx-module-dbus fcitx-module-x11 fcitx-module-lua fcitx-module-kimpanel fcitx-module-quickphrase-editor fcitx-tools Architecture: source all amd64 Version: 1:4.2.7-2 Distribution: unstable Urgency: low Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org Changed-By: YunQiang Su wzss...@gmail.com Description: fcitx - Flexible Input Method Framework fcitx-bin - Flexible Input Method Framework - essential binaries fcitx-data - Flexible Input Method Framework - essential data files fcitx-dbg - Flexible Input Method Framework - debugging symbols fcitx-frontend-all - Flexible Input Method Framework - frontends metapackage fcitx-frontend-gtk2 - Flexible Input Method Framework - GTK+ 2 IM Module frontend fcitx-frontend-gtk3 - Flexible Input Method Framework - GTK+ 3 IM Module frontend fcitx-frontend-qt4 - Flexible Input Method Framework - Qt4 IM Module frontend fcitx-libs - Flexible Input Method Framework - library files fcitx-libs-dev - Flexible Input Method Framework - library development files fcitx-libs-gclient - Flexible Input Method Framework - D-Bus client library for Glib fcitx-libs-qt - Flexible Input Method Framework - D-Bus client library for Qt fcitx-module-dbus - Flexible Input Method Framework - D-Bus module and IPC frontend fcitx-module-kimpanel - Flexible Input Method Framework - KIMPanel protocol module fcitx-module-lua - Flexible Input Method Framework - Lua module fcitx-module-quickphrase-editor - Flexible Input Method Framework - Quick Phrase editor module fcitx-module-x11 - Flexible Input Method Framework - X11 module and XIM frontend fcitx-modules - Flexible Input Method Framework - core modules fcitx-pinyin
Bug#700815: marked as done (fcitx: doesn't start due to library problem)
Your message dated Thu, 28 Feb 2013 12:48:23 + with message-id e1ub2un-0006a2...@franck.debian.org and subject line Bug#700710: fixed in fcitx 1:4.2.7-2 has caused the Debian Bug report #700710, regarding fcitx: doesn't start due to library problem 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.) -- 700710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fcitx Version: 1:4.2.7-1 Severity: grave Dear Maintainer, currently, fcitx does not start at all: $ fcitx -d fcitx: symbol lookup error: fcitx: undefined symbol: FcitxXDGMakeDirUser $ Kind regards, --Toni++ -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fcitx depends on: ii fcitx-bin 1:4.2.7-1 ii fcitx-data 1:4.2.7-1 ii fcitx-modules 1:4.2.7-1 Versions of packages fcitx recommends: ii fcitx-config-gtk 0.4.5.1-1 ii fcitx-frontend-all 1:4.2.7-1 ii fcitx-frontend-fbterm 0.2.0-1 ii fcitx-ui-classic 1:4.2.7-1 ii fcitx-ui-light 0.1.3-2 ii im-config [im-switch] 0.20 ii kde-config-fcitx 0.3.4-1 Versions of packages fcitx suggests: ii fcitx-m17n 0.2.0-1 ii fcitx-tools 1:4.2.7-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: fcitx Source-Version: 1:4.2.7-2 We believe that the bug you reported is fixed in the latest version of fcitx, 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 700...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su wzss...@gmail.com (supplier of updated fcitx 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: Thu, 28 Feb 2013 17:00:35 +0800 Source: fcitx Binary: fcitx fcitx-bin fcitx-data fcitx-libs fcitx-libs-gclient fcitx-libs-qt fcitx-libs-dev gir1.2-fcitx-1.0 fcitx-dbg fcitx-ui-classic fcitx-frontend-all fcitx-frontend-gtk2 fcitx-frontend-gtk3 fcitx-frontend-qt4 fcitx-pinyin fcitx-qw fcitx-table fcitx-table-all fcitx-table-bingchan fcitx-table-cangjie fcitx-table-dianbaoma fcitx-table-erbi fcitx-table-wanfeng fcitx-table-wbpy fcitx-table-wubi fcitx-table-ziranma fcitx-modules fcitx-module-dbus fcitx-module-x11 fcitx-module-lua fcitx-module-kimpanel fcitx-module-quickphrase-editor fcitx-tools Architecture: source all amd64 Version: 1:4.2.7-2 Distribution: unstable Urgency: low Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org Changed-By: YunQiang Su wzss...@gmail.com Description: fcitx - Flexible Input Method Framework fcitx-bin - Flexible Input Method Framework - essential binaries fcitx-data - Flexible Input Method Framework - essential data files fcitx-dbg - Flexible Input Method Framework - debugging symbols fcitx-frontend-all - Flexible Input Method Framework - frontends metapackage fcitx-frontend-gtk2 - Flexible Input Method Framework - GTK+ 2 IM Module frontend fcitx-frontend-gtk3 - Flexible Input Method Framework - GTK+ 3 IM Module frontend fcitx-frontend-qt4 - Flexible Input Method Framework - Qt4 IM Module frontend fcitx-libs - Flexible Input Method Framework - library files fcitx-libs-dev - Flexible Input Method Framework - library development files fcitx-libs-gclient - Flexible Input Method Framework - D-Bus client library for Glib fcitx-libs-qt - Flexible Input Method Framework - D-Bus client library for Qt fcitx-module-dbus - Flexible Input Method Framework - D-Bus module and IPC frontend fcitx-module-kimpanel - Flexible Input Method Framework - KIMPanel protocol module fcitx-module-lua - Flexible Input Method Framework - Lua module fcitx-module-quickphrase-editor - Flexible Input Method Framework - Quick Phrase editor module fcitx-module-x11 - Flexible Input Method Framework - X11 module and XIM frontend fcitx-modules - Flexible Input Method Framework - core modules fcitx-pinyin - Flexible Input Method Framework - classic
Bug#701558: marked as done (fcitx-bin: bashism in /bin/sh script)
Your message dated Thu, 28 Feb 2013 12:48:23 + with message-id e1ub2un-0006af...@franck.debian.org and subject line Bug#701558: fixed in fcitx 1:4.2.7-2 has caused the Debian Bug report #701558, regarding fcitx-bin: bashism in /bin/sh script 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.) -- 701558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fcitx-bin Version: 4.2.7-1 Severity: serious User: debian-rele...@lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: possible bashism in ./usr/bin/fcitx-configtool line 72 (should be word 21): if (kcmshell4 --list 2/dev/null | grep ^kcm_fcitx /dev/null); then possible bashism in ./usr/bin/fcitx-configtool line 82 (should be word 21): if which fcitx-config-gtk /dev/null; then possible bashism in ./usr/bin/fcitx-configtool line 88 (should be word 21): if which fcitx-config-gtk3 /dev/null; then Not using bash (or a Debian Policy conformant shell interpreter which doesn't provide such an extra feature) as /bin/sh is likely to lead to errors or unexpected behaviours. You can find hints about how to fix bashisms at: https://wiki.ubuntu.com/DashAsBinSh Thank you, Raphael Geissert ---End Message--- ---BeginMessage--- Source: fcitx Source-Version: 1:4.2.7-2 We believe that the bug you reported is fixed in the latest version of fcitx, 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. YunQiang Su wzss...@gmail.com (supplier of updated fcitx 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: Thu, 28 Feb 2013 17:00:35 +0800 Source: fcitx Binary: fcitx fcitx-bin fcitx-data fcitx-libs fcitx-libs-gclient fcitx-libs-qt fcitx-libs-dev gir1.2-fcitx-1.0 fcitx-dbg fcitx-ui-classic fcitx-frontend-all fcitx-frontend-gtk2 fcitx-frontend-gtk3 fcitx-frontend-qt4 fcitx-pinyin fcitx-qw fcitx-table fcitx-table-all fcitx-table-bingchan fcitx-table-cangjie fcitx-table-dianbaoma fcitx-table-erbi fcitx-table-wanfeng fcitx-table-wbpy fcitx-table-wubi fcitx-table-ziranma fcitx-modules fcitx-module-dbus fcitx-module-x11 fcitx-module-lua fcitx-module-kimpanel fcitx-module-quickphrase-editor fcitx-tools Architecture: source all amd64 Version: 1:4.2.7-2 Distribution: unstable Urgency: low Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org Changed-By: YunQiang Su wzss...@gmail.com Description: fcitx - Flexible Input Method Framework fcitx-bin - Flexible Input Method Framework - essential binaries fcitx-data - Flexible Input Method Framework - essential data files fcitx-dbg - Flexible Input Method Framework - debugging symbols fcitx-frontend-all - Flexible Input Method Framework - frontends metapackage fcitx-frontend-gtk2 - Flexible Input Method Framework - GTK+ 2 IM Module frontend fcitx-frontend-gtk3 - Flexible Input Method Framework - GTK+ 3 IM Module frontend fcitx-frontend-qt4 - Flexible Input Method Framework - Qt4 IM Module frontend fcitx-libs - Flexible Input Method Framework - library files fcitx-libs-dev - Flexible Input Method Framework - library development files fcitx-libs-gclient - Flexible Input Method Framework - D-Bus client library for Glib fcitx-libs-qt - Flexible Input Method Framework - D-Bus client library for Qt fcitx-module-dbus - Flexible Input Method Framework - D-Bus module and IPC frontend fcitx-module-kimpanel - Flexible Input Method Framework - KIMPanel protocol module fcitx-module-lua - Flexible Input Method Framework - Lua module fcitx-module-quickphrase-editor - Flexible Input Method Framework - Quick Phrase editor module fcitx-module-x11 - Flexible Input Method Framework - X11 module and XIM frontend fcitx-modules - Flexible Input Method Framework - core modules fcitx-pinyin - Flexible Input Method Framework - classic Pinyin engine fcitx-qw - Flexible Input Method Framework - QuWei
Bug#701776: fsck.btrfs do not accept -a so the system will not boot anymore
I confirm Axel Beckert's statement in message #60. My system cannot boot with the latest patch 0.19+20130131-2 Tim Cuthbertson
Bug#695500: debian-installer-7.0-netboot-kfreebsd-amd64: does not boot from pxe - still reproduceable
Hi,
On 21/02/13 06:39, Martin Zobel-Helas wrote:
for tftpd-hpa it is even worse:
| CLIENT MAC ADDR: 00 00 24 CE 6E B8
| CLIENT IP: 10.24.0.10 MASK: 255.255.255.0 DHCP IP: 10.24.0.1
| TFTP.
| PXE-M0F: Exiting Intel Boot Agent.
|
| No Boot device available, enter monitor.
That looks more like a problem with the configuration of tftpd-hpa, or
the DHCP response? Since there is no mention of grub2pxe at all.
I've tried kfreebsd-i386 d-i rc1 on a few thin client systems, which
have Intel UNDI PXE-2.0, with Realtek RTL 8139 or Via Rhine II onboard
NICs, and all were able to netboot the GRUB menu.
My test setup is detailed below.
/etc/dhcp3/dhcpd.conf :
allow booting;
allow bootp;
host kfreebsd-i386 {
# Client MAC / IP
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 192.0.2.2;
# TFTP server / boot filename
next-server 192.0.2.1;
filename grub2pxe;
}
/etc/default/tftpd-hpa :
TFTP_OPTIONS=--secure --refuse utimeout
TFTP_USERNAME=tftp
TFTP_DIRECTORY=/var/lib/tftpboot
TFTP_ADDRESS=0.0.0.0:69
# ps ax | grep tftpd
23480 ?Ss 0:00 /usr/sbin/in.tftpd --listen --user tftp
--address 0.0.0.0:69 --secure --refuse utimeout /var/lib/tftpboot
/var/lib/tftpboot/ :
lrwxrwxrwx 1 root root 39 Feb 27 20:11 grub2pxe -
debian-installer/kfreebsd-i386/grub2pxe
/var/lib/tftpboot/debian-installer/kfreebsd-i386/ :
-rw-r--r-- 1 root root4987 Feb 11 23:59 font.pf2~
-rw-r--r-- 1 root root 130587 Feb 11 23:59 grub2pxe
-rw-r--r-- 1 root root1153 Feb 27 20:46 grub.cfg
-rw-r--r-- 1 root root 4875366 Feb 11 23:59 initrd.gz
-rw-r--r-- 1 root root 5123957 Feb 11 23:59 kfreebsd-9.gz
-rw-r--r-- 1 root root 75511 Feb 11 23:59 splash.png
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695500: debian-installer-7.0-netboot-kfreebsd-amd64: does not boot from pxe - still reproduceable
On 21/02/13 06:39, Martin Zobel-Helas wrote: | CLIENT MAC ADDR: 00 00 24 CE 6E B8 | CLIENT IP: 10.24.0.10 MASK: 255.255.255.0 DHCP IP: 10.24.0.1 | TFTP. | PXE-M0F: Exiting Intel Boot Agent. | | No Boot device available, enter monitor. Apparently that can simply mean 'file not found': http://comments.gmane.org/gmane.comp.hardware.soekris.technical/17688 You may want to get a tcpdump capture of this from the TFTP server, and/or dry-run your setting of 'filename' (as in dhcpd.conf), with the command-line client, i.e.: $ tftp 192.0.2.1 tftp get grub2pxe Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700716: marked as done (python-imaging: FTBFS: dh_movefiles: .../_imagingtk.so not found (supposed to put it in python-imaging-tk))
Your message dated Thu, 28 Feb 2013 14:33:34 +
with message-id e1ub4ya-0006c1...@franck.debian.org
and subject line Bug#700716: fixed in python-defaults 2.7.3-11
has caused the Debian Bug report #700716,
regarding python-imaging: FTBFS: dh_movefiles: .../_imagingtk.so not found
(supposed to put it in python-imaging-tk)
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.)
--
700716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-imaging
Version: 1.1.7+1.7.8-2
Severity: serious
Justification: fails to build from source
python-imaging FTBFS on buildds:
| dh_movefiles -ppython-imaging-tk \
| --sourcedir=debian/python-imaging \
| usr/lib/python2.6/$(basename $(_py_=2.6; python${_py_#python*}
-c 'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/_imagingtk.so \
| usr/lib/python2.6/$(basename $(_py_=2.6; python${_py_#python*}
-c 'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/PIL/ImageTk.py
| dh_movefiles:
debian/python-imaging/usr/lib/python2.6/dist-packages/_imagingtk.so not found
(supposed to put it in python-imaging-tk)
| make: *** [install-python2.6] Error 1
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=python-imagingarch=i386ver=1.1.7%2B1.7.8-2stamp=1360996465
--
Jakub Wilk
---End Message---
---BeginMessage---
Source: python-defaults
Source-Version: 2.7.3-11
We believe that the bug you reported is fixed in the latest version of
python-defaults, 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 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated python-defaults package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 28 Feb 2013 14:43:06 +0100
Source: python-defaults
Binary: python python-minimal python-examples python-dev libpython-dev idle
python-doc python-dbg libpython-dbg python-all python-all-dev python-all-dbg
Architecture: source all amd64
Version: 2.7.3-11
Distribution: experimental
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
idle - IDE for Python using Tkinter (default version)
libpython-dbg - debug build of the Python Interpreter (version 2.7)
libpython-dev - header files and a static library for Python (default)
python - interactive high-level object-oriented language (default version)
python-all - package depending on all supported Python runtime versions
python-all-dbg - package depending on all supported Python debugging packages
python-all-dev - package depending on all supported Python development packages
python-dbg - debug build of the Python Interpreter (version 2.7)
python-dev - header files and a static library for Python (default)
python-doc - documentation for the high-level object-oriented language Python
python-examples - examples for the Python language (default version)
python-minimal - minimal subset of the Python language (default version)
Closes: 700716
Changes:
python-defaults (2.7.3-11) experimental; urgency=low
.
* Add Multi-Arch: same packages libpython-all-{dev,dbg} (not yet built,
python2.6 doesn't have support for multiarch).
* python-dbg: Stop providing python-gdbm-dbg, python-tk-dbg. Closes: #700716.
* Add a libpython-stdlib package (not yet built).
Checksums-Sha1:
f5a8c2a6644b14176e0a876dbc25484bd5b236d6 1664 python-defaults_2.7.3-11.dsc
00eb3c7523a39e9e6b2e94caebf38a14c88abf90 880161 python-defaults_2.7.3-11.tar.gz
220cd7c2c786b8123b481bd7141da2fb868c0a58 852 python-examples_2.7.3-11_all.deb
5818e5daf1f755f7013ca9d8c32c8bde2f9822b7 3056 idle_2.7.3-11_all.deb
491900e2bd069a93a1fabeac03b58e575950217f 22894 python-doc_2.7.3-11_all.deb
a9328c4d0ab150c537e40c69c5865486c13a4123 184250 python_2.7.3-11_amd64.deb
afd46c4049b3def3185bfcfaccaff13085a74dfe 42002
python-minimal_2.7.3-11_amd64.deb
dc22fe6cdfb0f4123905568b2f5e1a978386e111 1088 python-dev_2.7.3-11_amd64.deb
f91eee39e785652c8ec6cb967eb03ea25aae991c 19406
Processed: severity of 642096 is serious
Processing commands for cont...@bugs.debian.org: severity 642096 serious Bug #642096 [reportbug] Unable to create configuration file (UnicodeEncodeError) Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 642096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642096 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: severity of 642096 is serious
Processing commands for cont...@bugs.debian.org: severity 642096 normal Bug #642096 [reportbug] Unable to create configuration file (UnicodeEncodeError) Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 642096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642096 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#701897: CVE-2012-5667: buffer overflow with overly long input lines
Package: grep Severity: grave Version: 2.6.3-3 Tags: security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org Hi, the following vulnerability was published for grep. CVE-2012-5667[0]: | Multiple integer overflows in GNU Grep before 2.11 might allow | context-dependent attackers to execute arbitrary code via vectors | involving a long input line that triggers a heap-based buffer | overflow. 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-5667 http://security-tracker.debian.org/tracker/CVE-2012-5667 Please adjust the affected versions in the BTS as needed. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Not yet fixed in stable...
Processing commands for cont...@bugs.debian.org:
unarchive 694810
Bug #694810 {Done: Michael Stapelberg stapelb...@debian.org} [plib] plib:
CVE-2012-4552
Unarchived Bug 694810
found 694810 1.8.5-5
Bug #694810 {Done: Michael Stapelberg stapelb...@debian.org} [plib] plib:
CVE-2012-4552
There is no source info for the package 'plib' at version '1.8.5-5' with
architecture ''
Unable to make a source version for version '1.8.5-5'
Marked as found in versions 1.8.5-5.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
694810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694810
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: [bts-link] source package src:busybox
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:busybox # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #686502 (http://bugs.debian.org/686502) # Bug title: busybox unxz silently fails to decompress multiple compressed streams on input # * https://bugs.busybox.net/show_bug.cgi?id=5804 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 686502 + fixed-upstream Bug #686502 [src:busybox] busybox unxz silently fails to decompress multiple compressed streams on input Added tag(s) fixed-upstream. usertags 686502 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 686502 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 686502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686502 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#701868: [Pkg-openssl-devel] Bug#701868: cannot connect to IRC server
On Thu, Feb 28, 2013 at 10:36:11AM +0100, Marcus Better wrote: Package: libssl1.0.0 Version: 1.0.1e-1 Severity: grave This version of OpenSSL makes it impossible to connect to my company's IRC server. I have tried four IRC clients (irssi, kvirc, konversation and quassel) and all of them disconnect shortly after connecting. Do you know what IRC software is being used, and with which library it links? It should display the version on connect, or you can do /version ircssi gives this error: SSL read error: decryption failed or bad record mac kvirc says: [09:39:59] [irc.example.net]: *** You are connected using SSL cipher DHE-RSA-AES-256-CBC-SHA1 [09:40:00] [SSL ERROR]: decryption failed or bad record mac [09:40:00] [SOCKET ERROR]: Secure Socket Layer error [09:40:00] Connection terminated [irc.example.net (1.2.3.4:1234)] I have verified that everything works when I downgrade to 1.0.1c-4. Probably same as this bug: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/113 So can you try with export OPENSSL_ia32cap=~0x202? Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656877: Also seen on Thecus (iop32x)
Control: fixed -1 3.0~rc.2 On Tue, 22 May 2012 14:25:07 -0600, Martin Michlmayr wrote: * Colin Tuckley col...@debian.org [2012-05-22 18:08]: I've noticed that when the kernel gets upgraded by apt-get upgrade that it does *not* run flash-kernel on my Squeeze system. This is a well known issue which has been resolved in testing/unstable: flash-kernel (3.0~rc.2) experimental; urgency=low Marking the bug as fixed in this version. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Paul McCartney: Coquette signature.asc Description: Digital signature
Processed: Re: Bug#656877: Also seen on Thecus (iop32x)
Processing control commands: fixed -1 3.0~rc.2 Bug #656877 [flash-kernel] flash-kernel is not being run for kernel upgrades with unchanged ABI version Bug #673418 [flash-kernel] flash-kernel is not being run for kernel upgrades with unchanged ABI version Bug #701781 [flash-kernel] linux-image-2.6.32-5-kirkwood: Cannot load usbcore kernel module Marked as fixed in versions flash-kernel/3.0~rc.2. Marked as fixed in versions flash-kernel/3.0~rc.2. Marked as fixed in versions flash-kernel/3.0~rc.2. -- 656877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656877 673418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673418 701781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701781 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#701916: Kill local user processes on logout
Package: ltsp-client-core Version: 5.4.2-5 Severity: grave Tags: patch upstream LTSP fat clients and also thin clients that use localapps, mount /home/username with SSHFS and unmount it on logout. Unfortunately at the point where the unmount happens, local processes are still running, and when Xorg killed them later on, they end up writing their data to the local tmpfs filesystem because the SSHFS mount is no longer there. That's one reason for data loss (hence the grave severity), but there's another, worse one: On the next login of the same user, /home/username/data of the processes I mentioned above exist locally on the tmpfs, so the LTSP code thinks that the sysadmin has taken care to mount the user home dirs via other means (e.g. NFS), so the SSHFS mount is no longer needed. Thus, all user sessions after the first one, use a local tmpfs /home/username. Users don't see their existing documents or settings, and any new document they write, will be saved in the local tmpfs and lost on client reboot. Here's the upstream bug report: https://bugs.launchpad.net/ltsp/+bug/1093144 And the patch: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2462 Only one file needs to be patched, client/localapps/ldm-rc.d/X99-zlocalapps-cleanup. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 701815 is important
Processing commands for cont...@bugs.debian.org: severity 701815 important Bug #701815 [aisleriot] aisleriot: Spider - While playing Spider, an exception occurs whenever you stack (complete) a column Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 701815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701815 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: severity of 699145 is important
Processing commands for cont...@bugs.debian.org: severity 699145 important Bug #699145 [bind9] bind9: CVE-2012-5689 Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 699145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 701897 in 2.11-1
Processing commands for cont...@bugs.debian.org: fixed 701897 2.11-1 Bug #701897 [grep] CVE-2012-5667: buffer overflow with overly long input lines Marked as fixed in versions grep/2.11-1. thanks Stopping processing here. Please contact me if you need assistance. -- 701897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701897 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: severity of 687611 is important
Processing commands for cont...@bugs.debian.org: severity 687611 important Bug #687611 [apt] debian-archive-keyring: /usr/share/keyrings/debian-archive-removed-keys.gpg gets modified during squeeze-wheezy upgrade Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 687611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687611 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#701115: owncloud: multiple vulnerabilities (oC-SA-2013-003, oC-SA-2013-004, oC-SA-2013-006)
On Wed, 27 Feb 2013 12:14:19 +0700, Prach Pongpanich wrote:
I have prepared a patch which solves the this bug.
Thanks alot, this patch looks perfect; I just checked with the
commits (stable4) mentioned in the oC-SAs, and it's indeed identical
:)
The patch also applies more or less to the version in testing (module
debian/changelog, obviously); what fails is the part about
settings/js/users.js. - I now tried to adjust this part, but since I
don't speak JS this was more guesswork.
I'm attaching the debdiff for an upload to t-p-u.
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Rebekka Bakken: Didn't I
diff -Nru owncloud-4.0.4debian2/debian/changelog owncloud-4.0.4debian2/debian/changelog
--- owncloud-4.0.4debian2/debian/changelog 2013-02-02 23:55:58.0 +0100
+++ owncloud-4.0.4debian2/debian/changelog 2013-02-28 19:17:48.0 +0100
@@ -1,3 +1,16 @@
+owncloud (4.0.4debian2-3.4) testing-proposed-updates; urgency=low
+
+ * Non-maintainer upload.
+ * Multiple security fixes (Closes: #701115):
++ debian/patches/13_oc-sa-2013-003.patch:
+ - CVE-2013-0297 and CVE-2013-0307: XSS vulnerability
++ debian/patches/14_oc-sa-2013-004.patch:
+ - CVE-2013-0299 and CVE-2013-0301: Multiple CSRF vulnerabilities
++ debian/patches/15_oc-sa-2013-006.patch:
+ - CVE-2013-0303: Multiple code executions
+
+ -- Prach Pongpanich prach...@gmail.com Wed, 27 Feb 2013 11:38:52 +0700
+
owncloud (4.0.4debian2-3.3) testing-proposed-updates; urgency=high
* Non-maintainer upload.
diff -Nru owncloud-4.0.4debian2/debian/patches/13_oc-sa-2013-003.patch owncloud-4.0.4debian2/debian/patches/13_oc-sa-2013-003.patch
--- owncloud-4.0.4debian2/debian/patches/13_oc-sa-2013-003.patch 1970-01-01 01:00:00.0 +0100
+++ owncloud-4.0.4debian2/debian/patches/13_oc-sa-2013-003.patch 2013-02-28 19:33:15.0 +0100
@@ -0,0 +1,32 @@
+Description: Fix multiple cross-site scripting (XSS) vulnerabilities (CVE-2013-0297, CVE-2013-0307)
+Origin: upstream
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701115
+
+Index: owncloud-4.0.4debian2/settings/js/users.js
+===
+--- owncloud-4.0.4debian2.orig/settings/js/users.js 2013-02-28 19:32:53.666411633 +0100
owncloud-4.0.4debian2/settings/js/users.js 2013-02-28 19:33:12.982410942 +0100
+@@ -198,7 +198,7 @@
+ }
+ }
+ $.each(allGroups,function(i,group){
+- select.append($('option value='+group+''+group+'/option'));
++ select.append($('option value=' + escapeHTML(group) + '' + escapeHTML(group) + '/option'));
+ });
+ tr.find('td.groups').append(select);
+ if(tr.find('td.remove img').length==0){
+Index: owncloud-4.0.4debian2/apps/external/templates/settings.php
+===
+--- owncloud-4.0.4debian2.orig/apps/external/templates/settings.php 2013-02-28 19:32:53.666411633 +0100
owncloud-4.0.4debian2/apps/external/templates/settings.php 2013-02-28 19:32:53.662411633 +0100
+@@ -6,8 +6,8 @@
+ ?php
+ $sites = OC_External::getSites();
+ for($i = 0; $i sizeof($sites); $i++) {
+- echo 'liinput type=text name=site_name[] class=site_name value='.$sites[$i][0].' placeholder='.$l-t('Name').' /
+- input type=text class=site_url name=site_url[] value='.$sites[$i][1].' placeholder='.$l-t('URL').' /
++ echo 'liinput type=text name=site_name[] class=site_name value='.OC_Util::sanitizeHTML($sites[$i][0]).' placeholder='.$l-t('Name').' /
++ input type=text class=site_url name=site_url[] value='.OC_Util::sanitizeHTML($sites[$i][1]).' placeholder='.$l-t('URL').' /
+ img class=svg action delete_button src='.OCP\image_path(, actions/delete.svg) .' title='.$l-t(Remove site).' /
+ /li';
+ }
diff -Nru owncloud-4.0.4debian2/debian/patches/14_oc-sa-2013-004.patch owncloud-4.0.4debian2/debian/patches/14_oc-sa-2013-004.patch
--- owncloud-4.0.4debian2/debian/patches/14_oc-sa-2013-004.patch 1970-01-01 01:00:00.0 +0100
+++ owncloud-4.0.4debian2/debian/patches/14_oc-sa-2013-004.patch 2013-02-28 19:24:46.0 +0100
@@ -0,0 +1,126 @@
+Description: Fix multiple cross-site request forgery (CSRF) vulnerabilities (CVE-2013-0299,CVE-2013-0301)
+Origin: upstream
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701115
+
+--- a/apps/calendar/ajax/settings/guesstimezone.php
b/apps/calendar/ajax/settings/guesstimezone.php
+@@ -9,6 +9,7 @@
+
+ OCP\JSON::checkLoggedIn();
+ OCP\JSON::checkAppEnabled('calendar');
++OCP\JSON::callCheck();
+
+ $l = OC_L10N::get('calendar');
+
+--- a/apps/admin_migrate/settings.php
b/apps/admin_migrate/settings.php
+@@ -27,6 +27,8 @@ OCP\App::checkAppEnabled('admin_migrate');
+
+ // Export?
+ if
Bug#701642: btrfs-tools: diff for NMU version 0.19+20120328-7.1
tags 701642 + patch tags 701642 + pending thanks Hi, I've prepared an NMU for btrfs-tools (versioned as 0.19+20120328-7.1) and will upload asap. Patch attached. Cheers, Julien diff -Nru btrfs-tools-0.19+20120328/debian/changelog btrfs-tools-0.19+20120328/debian/changelog --- btrfs-tools-0.19+20120328/debian/changelog 2012-06-29 17:57:00.0 +0200 +++ btrfs-tools-0.19+20120328/debian/changelog 2013-02-28 19:54:50.0 +0100 @@ -1,3 +1,11 @@ +btrfs-tools (0.19+20120328-7.1) wheezy; urgency=low + + * Non-maintainer upload. + * Move udev rules file from 60-btrfs.rules to 70-btrfs.rules so it runs +after blkid (closes: #701642). Thanks, Bastian Blank! + + -- Julien Cristau jcris...@debian.org Thu, 28 Feb 2013 19:54:48 +0100 + btrfs-tools (0.19+20120328-7) unstable; urgency=low * Using official package-type for udeb packages in control now. diff -Nru btrfs-tools-0.19+20120328/debian/rules btrfs-tools-0.19+20120328/debian/rules --- btrfs-tools-0.19+20120328/debian/rules 2012-06-29 03:40:53.0 +0200 +++ btrfs-tools-0.19+20120328/debian/rules 2013-02-28 19:52:46.0 +0100 @@ -27,7 +27,7 @@ done # Adding udev integration - install -D -m 0644 debian/local/btrfs.udev debian/btrfs-tools/lib/udev/rules.d/60-btrfs.rules + install -D -m 0644 debian/local/btrfs.udev debian/btrfs-tools/lib/udev/rules.d/70-btrfs.rules # Adding initramfs-tools integration install -D -m 0755 debian/local/btrfs.hook debian/btrfs-tools/usr/share/initramfs-tools/hooks/btrfs signature.asc Description: Digital signature
Processed: btrfs-tools: diff for NMU version 0.19+20120328-7.1
Processing commands for cont...@bugs.debian.org:
tags 701642 + patch
Bug #701642 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[btrfs-tools] btrfs-tools - Udev hook runs before blkid
Added tag(s) patch.
tags 701642 + pending
Bug #701642 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[btrfs-tools] btrfs-tools - Udev hook runs before blkid
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
701642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701642
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 699885
Processing commands for cont...@bugs.debian.org: tags 699885 + wheezy-ignore Bug #699885 [bouncycastle] TLS timing attack in bouncycastle (Lucky 13) Added tag(s) wheezy-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 699885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699885 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#701925: survival: FTBFS: Can't open /usr/lib/R/etc/Renviron
Package: src:survival Version: 2.37-4-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: dh_clean: dh_clean -k is deprecated; use dh_prep instead dh_installdirs -A mkdir -p . dh_installdirs usr/lib/R/library echo R:Depends=r-base-core (= 2.15.3~20130326-1) debian/r-cran-survival.substvars if test -f /usr/bin/xvfb-run; then \ xvfb-run -a\ R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library --clean \ . ;\ else\ R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library \ --clean . ;\ fi /usr/lib/R/bin/Rcmd: 37: .: Can't open /usr/lib/R/etc/Renviron make: *** [R_any_arch] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=survivalarch=amd64ver=2.37-4-1stamp=1361935064 Regards Christoph -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 682952
Processing commands for cont...@bugs.debian.org: close 682952 Bug #682952 [cdrom] Installation fails on locking for security updates Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 682952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682952 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#701744: [Pkg-xen-devel] Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
Am 28.02.2013 um 11:28 schrieb Ian Campbell i...@hellion.org.uk: I am 99% positive it will turn out to be the kernel, but please do let us know. Shortly before 18:00 today I reinstalled linux-image-2.6.32-5-xen-amd64_2.6.32-48_amd64.deb as kernel and it took only 2.5 hours to trigger the issue. The hypervisor is xen-hypervisor-4.0-amd64 4.0.1-5.4 at this time. All domUs are still running the updated kernel packages (pre DSA-2632-1), the dom0 the downgraded kernel package. When you reach a conclusion (assuming it is the one I expect!) please can you confirm the fixed+broken kernel package versions so I can reassign as appropriate. Unfortunately I'm about to go travelling for a week but I have asked one of my colleagues to try and take a look at this. I will now upgrade to DSA-2632-1 kernels and see whether that works or has the same issues. Will keep you updated. -- Ciao...// Fon: 0381-2744150 Ingo \X/ http://blog.windfluechter.net gpg pubkey: http://www.juergensmann.de/ij_public_key.asc -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 700670
Processing commands for cont...@bugs.debian.org: tags 700670 + wheezy-ignore Bug #700670 [cltl] cltl: /usr/share/doc/cltl/* disappearing after lenny - squeeze - wheezy upgrade Added tag(s) wheezy-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 700670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 693208 in clang/1:3.0-6.1
Processing commands for cont...@bugs.debian.org:
fixed 693208 clang/1:3.0-6.1
Bug #693208 {Done: Sylvestre Ledru sylves...@debian.org} [clang] clang unable
to link trivial test program on armhf
Marked as fixed in versions clang/1:3.0-6.1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
693208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693208
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: severity of 648965 is normal
Processing commands for cont...@bugs.debian.org: severity 648965 normal Bug #648965 [comixcursors-righthanded] comixcursors-righthanded: update-alternatives not used Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 648965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648965 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#701926: asertion failure when assigning certain USB devices to guest
Package: qemu-kvm, qemu-system Version: 1.1.2+dfsg-5 Severity: serious Tags: confirmed patch upstream pending In addition to another USB issue/regression in qemu[-kvm] 1.1, which is described in #683983, there's one more of the same theme. Certain host USB devices, for example, a Logitech ClearChat Pro headset (ID 046d:0a0b), causes an assertion failure when used with a windows guest: usb_packet_complete: Assertion `((ep-queue)-tqh_first) == p' failed. The mentioned headset for example, causes this assertion failure to happen when unplugging the device or when using buttons, while it generally works fine. This bug has been fixed upstream in early days of past-1.1 series development (ie, shortly after 1.1 has been released), but never found its way into any stable series. The severity of this bug is serious because generally, these devices work just fine, untill some event happens, and when it happen, the guest is effectively powered down, with any unsaved data being lost. After wheezy will be out, much more people will use various USB devices with their guests, so the issue will be more apparent. /mjt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()
On Thu, Jan 31, 2013 at 19:25:50 +0100, tom schorpp wrote: Package: crystalhd-dkms Version: 1:0.0~git20110715.fdd2f19-7 Severity: critical Tags: patch Justification: breaks the whole system Reproducible NULL pointer BUG at crystalhd-0.0~git20110715.fdd2f19/driver/linux/crystalhd_misc.c:515, triggered by adobe flash plugin from dmo repo, ffmpeg, mplayer, bino or other, mostly on heavy ioq usage or after FETCH_TIMEOUT and/or unclosed driver HANDLEs. Does the maintainer or somebody on pkg-multimedia plan on fixing this RC bug? If not I'll consider a NMU removing the dkms package from crystalhd source. Cheers, Julien signature.asc Description: Digital signature
Processed: tagging 701832
Processing commands for cont...@bugs.debian.org: tags 701832 + wheezy-ignore Bug #701832 [doxygen] doxygen consistently segfaults on kfreebsd-i386 when building opendnssec documentation Added tag(s) wheezy-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 701832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701832 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#701832: doxygen consistently segfaults on kfreebsd-i386 when building opendnssec documentation
On Wed, Feb 27, 2013 at 19:24:59 +0100, Ondřej Surý wrote: Package: doxygen Version: 1.8.1.2-1 Severity: grave Hi, the doxygen segfaults on kfreebsd-i386 when building opendnssec package and it blocks it's transition from unstable to testing. Could you please look at that? The build logs are here: https://buildd.debian.org/status/logs.php?arch=kfreebsd-i386pkg=opendnssecver=1%3A1.3.9-4 I have also opened this on debian-bsd list: http://lists.debian.org/debian-bsd/2013/02/msg00117.html Is there any way you could work around this in opendnssec? E.g. by not building the doc on that arch for now? kfreebsd porters, a look at this issue would be appreciated. Thanks, Julien signature.asc Description: Digital signature
Bug#701925: survival: FTBFS: Can't open /usr/lib/R/etc/Renviron
On 28 February 2013 at 11:28, Christoph Egger wrote: | Package: src:survival | Version: 2.37-4-1 | Severity: serious | Tags: sid wheezy | Justification: fails to build from source (but built successfully in the past) | | Hi! | | Your package failed to build on the buildds: | | dh_clean: dh_clean -k is deprecated; use dh_prep instead | dh_installdirs -A | mkdir -p . | dh_installdirsusr/lib/R/library | echo R:Depends=r-base-core (= 2.15.3~20130326-1) debian/r-cran-survival.substvars | if test -f /usr/bin/xvfb-run; then\ |xvfb-run -a\ | R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library --clean \ |. ;\ | else\ |R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library \ | --clean . ;\ | fi | /usr/lib/R/bin/Rcmd: 37: .: Can't open /usr/lib/R/etc/Renviron | make: *** [R_any_arch] Error 2 | | Full build log at | https://buildd.debian.org/status/fetch.php?pkg=survivalarch=amd64ver=2.37-4-1stamp=1361935064 What version of r-base-core did you use? There was a bug, it has been fixed: r-base (2.15.3~20130327-1) unstable; urgency=low * Second rc build (rev62077) of R 2.15.3 expected March 1 * debian/r-base-core.postinst: Fix typo in /etc/R/Renviron mode correction creation (thanks again, Don Armstrong!) (Closes: #701774) -- Dirk Eddelbuettel e...@debian.org Wed, 27 Feb 2013 15:09:55 -0600 Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 695500, user release.debian....@packages.debian.org, usertagging 695500
Processing commands for cont...@bugs.debian.org: tags 695500 + moreinfo wheezy-ignore Bug #695500 [debian-installer-7.0-netboot-kfreebsd-amd64] debian-installer-7.0-netboot-kfreebsd-amd64: does not boot from pxe Added tag(s) moreinfo and wheezy-ignore. user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was jcris...@debian.org). usertags 695500 wheezy-can-defer There were no usertags set. Usertags are now: wheezy-can-defer. thanks Stopping processing here. Please contact me if you need assistance. -- 695500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695500 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#701832: doxygen consistently segfaults on kfreebsd-i386 when building opendnssec documentation
On Thu, Feb 28, 2013 at 8:49 PM, Julien Cristau jcris...@debian.org wrote: Is there any way you could work around this in opendnssec? E.g. by not building the doc on that arch for now? I could, and it was the plan if nobody comes up with some clever idea till the end of the week. O. -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701925: survival: FTBFS: Can't open /usr/lib/R/etc/Renviron
Dirk Eddelbuettel e...@debian.org writes: On 28 February 2013 at 11:28, Christoph Egger wrote: | Package: src:survival | Version: 2.37-4-1 | Severity: serious | Tags: sid wheezy | Justification: fails to build from source (but built successfully in the past) | | Hi! | | Your package failed to build on the buildds: | | dh_clean: dh_clean -k is deprecated; use dh_prep instead | dh_installdirs -A | mkdir -p . | dh_installdirs usr/lib/R/library | echo R:Depends=r-base-core (= 2.15.3~20130326-1) debian/r-cran-survival.substvars | if test -f /usr/bin/xvfb-run; then \ | xvfb-run -a\ | R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library --clean \ | . ;\ | else\ | R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library \ | --clean . ;\ | fi | /usr/lib/R/bin/Rcmd: 37: .: Can't open /usr/lib/R/etc/Renviron | make: *** [R_any_arch] Error 2 | | Full build log at | https://buildd.debian.org/status/fetch.php?pkg=survivalarch=amd64ver=2.37-4-1stamp=1361935064 What version of r-base-core did you use? There was a bug, it has been fixed: The one I checked used 2.15.3~20130326-1. I'll give it back on the buildds and see if it gets fixed. Christoph -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 657281, user release.debian....@packages.debian.org, usertagging 657281
Processing commands for cont...@bugs.debian.org: tags 657281 + wheezy-ignore Bug #657281 [fop] src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free Added tag(s) wheezy-ignore. user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was jcris...@debian.org). usertags 657281 wheezy-can-defer There were no usertags set. Usertags are now: wheezy-can-defer. thanks Stopping processing here. Please contact me if you need assistance. -- 657281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657281 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#674156: marked as done (glib2.0: GStaticMutex ABI change on armel, armhf, mipsel, powerpc, s390, sparc and probably mips)
Your message dated Thu, 28 Feb 2013 21:16:36 +0100 with message-id 20130228201636.gq5...@radis.cristau.org and subject line Re: Bug#674156: glib2.0: GStaticMutex ABI change on armel, armhf, mipsel, powerpc, s390, sparc and probably mips has caused the Debian Bug report #674156, regarding glib2.0: GStaticMutex ABI change on armel, armhf, mipsel, powerpc, s390, sparc and probably mips 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.) -- 674156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gstreamer0.10-plugins-good Version: 0.10.31-2 Severity: important Hi, Currently ther are detection problems of gstreamer0.10-plugins-good's rtpmp2tpay (which is provided by libgstrtp.so according to gst-inspect-0.10) on most architectures. This breaks the build of gnome-dvb-daemon: https://buildd.debian.org/status/package.php?p=gnome-dvb-daemon -- Sebastian ---End Message--- ---BeginMessage--- On Mon, Jan 28, 2013 at 09:38:47 +, Simon McVittie wrote: On Fri, 11 Jan 2013 at 18:39:24 +, Simon McVittie wrote: By making a sourceful upload of gstreamer0.10, together with the sourceful upload of swami that has already happened and a pile of 14 binNMUs (see 694525#59), we can get full upgrades into a consistent state. Julien has NMU'd gstreamer0.10 and scheduled some binNMUs, and swami has migrated, so all we're waiting for to achieve this is for gstreamer0.10 to migrate. (This can be tracked by waiting for #697025, which is also RC, to migrate.) So, assuming no serious problems with the NMU, it's only a matter of time before full upgrades are OK. Regarding the original bug, gnome-dvb-daemon was recently built on the affected architectures; it is now built on all Linux architectures. So, from that point of view, job done. As for partial upgrades: Julien's NMU of gstreamer0.10 bumped the shlibs, so if dependent packages are rebuilt (up to 22 source NMUs of Multi-arch: same packages, and up to 38 binNMUs of other packages, see http://bugs.debian.org/694525#59), certain broken combinations (namely: new dependent package, old gstreamer0.10) will be prevented. There hasn't been any systematic upload of these; it's an open question whether it's worthwhile to do all of these, or just the binNMUs, or neither. The other broken combination (new gstreamer0.10, old dependent package) can only be addressed via Breaks relations. I think Julien's conclusion was that this has an unacceptable risk of introducing weird upgrade bugs where apt fails to find a solution, similar to http://bugs.debian.org/676485? Right. I think we can close the bug against glib now, as the ABI change is not going to be reverted and we've (hopefully) done what we could to minimize the damage it causes. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#701744: [Pkg-xen-devel] Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures
Am 28.02.2013 um 11:28 schrieb Ian Campbell i...@hellion.org.uk: All domUs are still running the updated kernel packages (pre DSA-2632-1), the dom0 the downgraded kernel package. linux-image-2.6.32-5-xen-amd64 2.6.32-48squeeze1 triggered the problem within 30 mins. ;-) When you reach a conclusion (assuming it is the one I expect!) please can you confirm the fixed+broken kernel package versions so I can reassign as appropriate. Conclusion: it's the kernel... ;-) Working: - kernel: linux-image-2.6.32-5-xen-amd64_2.6.32-46_amd64.deb - hypervisor: xen-hypervisor-4.0-amd64_4.0.1-5.4_amd64.deb, xen-hypervisor-4.0-amd64_4.0.1-5.6_amd64.deb Not Working kernels: - linux-image-2.6.32-5-xen-amd64_2.6.32-48_amd64.deb - linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze1_amd64.deb So, I'm going back to linux-image-2.6.32-5-xen-amd64_2.6.32-46_amd64.deb... -- Ciao...// Fon: 0381-2744150 Ingo \X/ http://blog.windfluechter.net gpg pubkey: http://www.juergensmann.de/ij_public_key.asc -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696547: mounts wrong device when multiple devices connected
Control: tag -1 moreinfo Control: severity -1 important On Sat, Dec 22, 2012 at 18:36:19 +0100, Daniel Pocock wrote: Package: gphoto2-2 Version: 2.4.6-3 Severity: serious I've marked this bug serious because it could lead to someone accessing or deleting files on the wrong device when multiple devices are connected. I have a Samsung Galaxy SIII connected to a USB port. It is not mounted. While the phone is connected, I then connect a second device, Nikon D800 DSLR camera, to another USB port. A popup appears telling me that a device has been detected (You have just inserted a medium with digital photos) and asking me what I want to do with it A popup from what app? Your desktop environment? Which is that? I select the option to browse the contents in a window The window appears with the title 'NIKON DSC D800' - but the contents of the window are the files on the Samsung Galaxy SIII. If I unplug the phone, and then connect the camera again, I don't see any popup. Note this problem is intermittent: sometimes I connect the DSLR and no popup appears. However, whenever the popup does appear, I get the files from the phone in a window titled 'NIKON DSC D800' Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#696547: mounts wrong device when multiple devices connected
Processing control commands: tag -1 moreinfo Bug #696547 [gphoto2] mounts wrong device when multiple devices connected Added tag(s) moreinfo. severity -1 important Bug #696547 [gphoto2] mounts wrong device when multiple devices connected Severity set to 'important' from 'serious' -- 696547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696547 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#698068: mysql-server-5.5: Serious regression in replication caused by fix for CVE-2012-4414
On Sun, 2013-02-03 at 22:53 +0100, Moritz Mühlenhoff wrote: On Sat, Jan 26, 2013 at 11:26:27AM +, Adam D. Barratt wrote: On Sun, 2013-01-13 at 11:53 -0800, Clint Byrum wrote: According to this blog post by Stewart Smith: http://www.mysqlperformanceblog.com/2013/01/13/cve-2012-4414-in-mysql-5-5-29-and-percona-server-5-5-29/ It looks like 5.5.29 has a serious problem with replication. Is there any news on a fix for that? It unfortunately means the other RC fixes from 5.5.29 are stuck in unstable. :-( Personally I don't think a bug in some replication scenarios is more severe than migrating the security fixes... But I leave that to the MySQL maintainers. MySQL maintainers - ping? 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#701925: survival: FTBFS: Can't open /usr/lib/R/etc/Renviron
On 28 February 2013 at 12:09, Christoph Egger wrote: | Dirk Eddelbuettel e...@debian.org writes: | On 28 February 2013 at 11:28, Christoph Egger wrote: | | Package: src:survival | | Version: 2.37-4-1 | | Severity: serious | | Tags: sid wheezy | | Justification: fails to build from source (but built successfully in the past) | | | | Hi! | | | | Your package failed to build on the buildds: | | | | dh_clean: dh_clean -k is deprecated; use dh_prep instead | | dh_installdirs -A | | mkdir -p . | | dh_installdirsusr/lib/R/library | | echo R:Depends=r-base-core (= 2.15.3~20130326-1) debian/r-cran-survival.substvars | | if test -f /usr/bin/xvfb-run; then\ | |xvfb-run -a\ | | R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library --clean \ | |. ;\ | | else\ | |R CMD INSTALL -l /build/buildd-survival_2.37-4-1-armel-A5Zprq/survival-2.37-4/debian/r-cran-survival/usr/lib/R/library \ | | --clean . ;\ | | fi | | /usr/lib/R/bin/Rcmd: 37: .: Can't open /usr/lib/R/etc/Renviron | | make: *** [R_any_arch] Error 2 | | | | Full build log at | | https://buildd.debian.org/status/fetch.php?pkg=survivalarch=amd64ver=2.37-4-1stamp=1361935064 | | What version of r-base-core did you use? There was a bug, it has been | fixed: | | The one I checked used 2.15.3~20130326-1. I'll give it back on the | buildds and see if it gets fixed. Fingers crossed. I need two extra iterations, one to add the needed chmod command (after mktemp) and one to fix a typo so that chmod uses the correct modes :-/ And it never fails in my pbuilder ... as I have R pinned in there as I build so manu r-cran-* packages. And when the file does not need to be created, the bug remains in hiding. Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701642: marked as done (btrfs-tools - Udev hook runs before blkid)
Your message dated Thu, 28 Feb 2013 20:47:29 + with message-id e1ubao1-0005pl...@franck.debian.org and subject line Bug#701642: fixed in btrfs-tools 0.19+20120328-7.1 has caused the Debian Bug report #701642, regarding btrfs-tools - Udev hook runs before blkid 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.) -- 701642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: btrfs-tools Version: 0.19+20120328-7 Severity: grave btrfs-tools includes a udev hook to scan btrfs filesystems. This hook checks ID_FS_TYPE. However the hook is evaluated _before_ blkid is used to determine this variable. The hook is called 60-btrfs.rules. blkid is used in 60-persistent*.rules, which orders after. Bastian -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-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 btrfs-tools depends on: ii e2fslibs1.42.5-1 ii libc6 2.13-38 ii libcomerr2 1.42.5-1 ii libuuid12.20.1-5.3 ii zlib1g 1:1.2.7.dfsg-13 btrfs-tools recommends no packages. btrfs-tools suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: btrfs-tools Source-Version: 0.19+20120328-7.1 We believe that the bug you reported is fixed in the latest version of btrfs-tools, 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. Julien Cristau jcris...@debian.org (supplier of updated btrfs-tools 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: Thu, 28 Feb 2013 19:54:48 +0100 Source: btrfs-tools Binary: btrfs-tools btrfs-tools-udeb btrfs-tools-dbg Architecture: source amd64 Version: 0.19+20120328-7.1 Distribution: wheezy Urgency: low Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net Changed-By: Julien Cristau jcris...@debian.org Description: btrfs-tools - Checksumming Copy on Write Filesystem utilities btrfs-tools-dbg - Checksumming Copy on Write Filesystem utilities (debug) btrfs-tools-udeb - Checksumming Copy on Write Filesystem utilities (udeb) (udeb) Closes: 701642 Changes: btrfs-tools (0.19+20120328-7.1) wheezy; urgency=low . * Non-maintainer upload. * Move udev rules file from 60-btrfs.rules to 70-btrfs.rules so it runs after blkid (closes: #701642). Thanks, Bastian Blank! Checksums-Sha1: 12870fefe6094161ef6ed56d1253e00b7e78353f 1987 btrfs-tools_0.19+20120328-7.1.dsc 1b5568574ea1eae88ca996b04b1730b5de18ab0b 9436 btrfs-tools_0.19+20120328-7.1.debian.tar.xz e45efe7e065fe510d6433293a44d5aaa2f8d9acf 239758 btrfs-tools_0.19+20120328-7.1_amd64.deb dd2e22e3775aedc21580669a65c55dd41580f71e 101552 btrfs-tools-udeb_0.19+20120328-7.1_amd64.udeb 19f6cf05a4182ee2ba57b14ce8360d67f0890e2d 4037168 btrfs-tools-dbg_0.19+20120328-7.1_amd64.deb Checksums-Sha256: 4a107258f237e28e598a126ad5fa83f83c025e24f8cc7d6a53700dcc3c121d36 1987 btrfs-tools_0.19+20120328-7.1.dsc d6e38cb2115f1d3774609a560d7b3d7f4cb7cbeb008a1dce5d9f5b621bbb35d9 9436 btrfs-tools_0.19+20120328-7.1.debian.tar.xz 43576c548e514d0bd88138b2a91f861262e61da9040dee8ee063ef150c9549f1 239758 btrfs-tools_0.19+20120328-7.1_amd64.deb c9aa59fb02e3e26bccf9714874292b9c4ca31e5605f583e634cb5861008445d5 101552 btrfs-tools-udeb_0.19+20120328-7.1_amd64.udeb 5f3d81ef0f07157b2c8529bb5c2ec377406c7ed8dfaae130b2fcc92c896fe7af 4037168 btrfs-tools-dbg_0.19+20120328-7.1_amd64.deb Files: 09e7129235f999d8c8c05fc2c62192ec 1987 admin optional btrfs-tools_0.19+20120328-7.1.dsc 3907bb766de885e5064dee794017cee2 9436 admin optional btrfs-tools_0.19+20120328-7.1.debian.tar.xz ef5b91ed7be2b668da664e9ce5a0731a 239758 admin optional btrfs-tools_0.19+20120328-7.1_amd64.deb 61cf7eaf4a1837d05652675c3a300e46 101552 debian-installer optional btrfs-tools-udeb_0.19+20120328-7.1_amd64.udeb 67ea0eae133a281d1cb440f45fb1eaf2 4037168
Bug#698294: diff for NMU 2.7.18-2.1
tags 698294 + pending thanks Dear maintainer, I've prepared an NMU for puppet (versioned as 2.7.18-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Cheers, Anton diff -Nru puppet-2.7.18/debian/changelog puppet-2.7.18/debian/changelog --- puppet-2.7.18/debian/changelog 2012-09-19 11:45:14.0 +0200 +++ puppet-2.7.18/debian/changelog 2013-02-28 21:15:05.0 +0100 @@ -1,3 +1,10 @@ +puppet (2.7.18-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix checksum mismatch when copying followed symlinks. (Closes: #698294) + + -- Anton Gladky gl...@debian.org Thu, 28 Feb 2013 21:14:32 +0100 + puppet (2.7.18-2) unstable; urgency=low [ Faidon Liambotis ] diff -Nru puppet-2.7.18/debian/patches/fix_checksum_missmatch_symlinks puppet-2.7.18/debian/patches/fix_checksum_missmatch_symlinks --- puppet-2.7.18/debian/patches/fix_checksum_missmatch_symlinks 1970-01-01 01:00:00.0 +0100 +++ puppet-2.7.18/debian/patches/fix_checksum_missmatch_symlinks 2013-02-28 21:13:39.0 +0100 @@ -0,0 +1,18 @@ +Description: Fixes checksum mismatch when copying followed symlinks +Origin: http://projects.puppetlabs.com/issues/7680#note-6 +Acked-by: Anton Gladky gl...@debian.org +Applied-Upstream: https://github.com/sodabrew/puppet/commit/9acce27806afb75570c156ff883d7b5edb8d7cb3 +Bug-Debian: http://bugs.debian.org/698294 +Last-Update: 2013-02-28 + +--- a/lib/puppet/type/file/source.rb b/lib/puppet/type/file/source.rb +@@ -117,7 +117,7 @@ + param_name = (metadata_method == :checksum) ? :content : metadata_method + next if metadata_method == :owner and !Puppet.features.root? + next if metadata_method == :checksum and metadata.ftype == directory +-next if metadata_method == :checksum and metadata.ftype == link and metadata.links == :manage ++next if metadata_method == :checksum and metadata.ftype == link and resource[:links] == :manage + + if Puppet.features.microsoft_windows? + next if [:owner, :group].include?(metadata_method) and !local? diff -Nru puppet-2.7.18/debian/patches/series puppet-2.7.18/debian/patches/series --- puppet-2.7.18/debian/patches/series 2012-09-19 11:45:14.0 +0200 +++ puppet-2.7.18/debian/patches/series 2013-02-28 21:01:24.0 +0100 @@ -1,2 +1,3 @@ apache2-passenger-template fix_logcheck +fix_checksum_missmatch_symlinks signature.asc Description: OpenPGP digital signature
Processed: diff for NMU 2.7.18-2.1
Processing commands for cont...@bugs.debian.org: tags 698294 + pending Bug #698294 [puppet] puppet: Checksum mismatch when copying followed symlinks (upstream #7680) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 698294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 650293 in 0.3.1-2.5
Processing commands for cont...@bugs.debian.org:
fixed 650293 0.3.1-2.5
Bug #650293 {Done: Ãrjan Persson ora...@fobie.net} [src:python-greenlet]
segfault while running it with eventlet
Marked as fixed in versions python-greenlet/0.3.1-2.5.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
650293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650293
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#701897: CVE-2012-5667: buffer overflow with overly long input lines
tags 701897 squeeze unreproducible -- I have tried the PoC proposed by the original reported, but have different outcomes: - On a running squeeze distribution, nothing happens. No segfaults, in particular. - On a wheezy machine, I downloaded version 2.6.3's .dsc from the QA page's link, configured, and built it; When I run the PoC, I get: grep: memory exhausted which is the same result that I get when I use the version installed on the machine. The notes on the Debian Security Tracker, however, suggest that the segfault is reproducible. It would be interesting to know other voices on this. I tag the issue with `squeeze' because it is the only possibly vulnerable version (2.11). -- Gianluca Ciccarelli GPG key ID: 0x39BBDB6C signature.asc Description: Digital signature
Processed: CVE-2012-5667: buffer overflow with overly long input lines
Processing commands for cont...@bugs.debian.org: tags 701897 squeeze unreproducible Bug #701897 [grep] CVE-2012-5667: buffer overflow with overly long input lines Added tag(s) unreproducible and squeeze. -- Stopping processing here. Please contact me if you need assistance. -- 701897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701897 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#700790: marked as done (gtkmm-documentation: directory vs. symlink conflict: /usr/share/doc/gtkmm-3.0)
Your message dated Thu, 28 Feb 2013 21:17:35 + with message-id e1ubar9-0002kf...@franck.debian.org and subject line Bug#700790: fixed in gtkmm-documentation 3.4.0-2 has caused the Debian Bug report #700790, regarding gtkmm-documentation: directory vs. symlink conflict: /usr/share/doc/gtkmm-3.0 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.) -- 700790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gtkmm-documentation Version: 3.4.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: squeeze - wheezy For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi From the attached log (usually somewhere in the middle...): 0m55.2s INFO: dirname part contains a symlink: /usr/share/doc/gtkmm-3.0/tutorial (gtkmm-documentation) != /usr/share/doc/libgtkmm-3.0-doc/tutorial (?) Hmm, looks like gtkmm-documentation installs something in the documentation directory of another package, but that has changed to a symlink inbetween ... cheers, Andreas gtkmm-documentation_3.4.0-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: gtkmm-documentation Source-Version: 3.4.0-2 We believe that the bug you reported is fixed in the latest version of gtkmm-documentation, 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 700...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau jcris...@debian.org (supplier of updated gtkmm-documentation 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: Thu, 28 Feb 2013 21:43:52 +0100 Source: gtkmm-documentation Binary: gtkmm-documentation Architecture: source all Version: 3.4.0-2 Distribution: unstable Urgency: medium Maintainer: Deng Xiyue manphiz-gu...@users.alioth.debian.org Changed-By: Julien Cristau jcris...@debian.org Description: gtkmm-documentation - Documentation of C++ wrappers for GLib/GTK+ Closes: 700790 Changes: gtkmm-documentation (3.4.0-2) unstable; urgency=medium . * Team upload * Remove /usr/share/doc/gtkmm-3.0/tutorial symlink (closes: #700790). /usr/share/doc/gtkmm-3.0 is itself a symlink, which messes things up. Checksums-Sha1: 72377b21d9791d444f8201dfc9e542694f438751 2343 gtkmm-documentation_3.4.0-2.dsc 79681163a9d5a8f2df17127a428e7613cfd4d5ce 4831 gtkmm-documentation_3.4.0-2.debian.tar.gz 88e8ee8f3f758d852c026c55ff1b92820d34b21e 2994618 gtkmm-documentation_3.4.0-2_all.deb Checksums-Sha256: f4bb04fcab3b91416ffac6c46987dbde66abc11ff864cbe9f31ced205302 2343 gtkmm-documentation_3.4.0-2.dsc 04ef529503fd72f4908b36a5489867ebf7796da86ac6715d545e5f7bcadd1b41 4831 gtkmm-documentation_3.4.0-2.debian.tar.gz cdcbcad50f86d33a5de7ba1ea33e51f4d28823de0251e879e3ecb33f1d156787 2994618 gtkmm-documentation_3.4.0-2_all.deb Files:
Bug#698527: marked as done (elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries)
Your message dated Thu, 28 Feb 2013 21:32:44 + with message-id e1ubb5o-0005wp...@franck.debian.org and subject line Bug#698527: fixed in elmerfem 6.1.0.svn.5396.dfsg2-2 has caused the Debian Bug report #698527, regarding elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries 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.) -- 698527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: elmer Version: 6.1.0.svn.5396.dfsg2-1 Severity: serious Justification: Policy 2.3 Hello, this may sound like a revival of bug #618696 [1], but in fact it's distinct (although the evergreen OpenCASCADE GPL-incompatibility is still involved...). [1] http://bugs.debian.org/618696 Let's start from the beginning, anyway. I've recently found out that all libav binary packages in Debian are effectively licensed under the GNU GPL, rather than under the GNU LGPL. This would have been easier to spot, if more clearly documented [2]. [2] http://bugs.debian.org/698019 After this discover, I searched for packages potentially affected by this strong copyleft. I noticed that the binary package named elmer depends on some libav packages and I remembered the well-known OpenCASCADE GPL-incompatibility. Hence, I examined all the binaries shipped by the elmer binary package with ldd and I found out that /usr/bin/ElmerGUI.real is linked with the following libraries, among others: libTKSTL.so.2 [...] libTKXSBase.so.2 = OCE (OpenCASCADE Community Edition) License: OCTPL GPL-incompatible libmysqlclient.so.18 = MySQL client library License: GPL-2+ with FOSS exception (which does not allow linking with OCTPL-licensed works...) libavformat.so.53 = libavformat Effective license: GPL-3+ libavcodec.so.53 = libavcodec Effective license: GPL-2+ or libavcodec-extra Effective license: GPL-3+ libavutil.so.51 = libavutil Effective license: GPL-2+ libswscale.so.2 = libswscale Effective license: GPL-2+ (for further details, see the already mentioned bug #698019 [2], especially its message #27 [3]) [3] http://bugs.debian.org/698019#27 libcrypto.so.1.0.0 libssl.so.1.0.0 = OpenSSL License: OpenSSL license (which is GPL-incompatible!) libjbig.so.0 = JBIG-KIT library License: GPL-2+ libxvidcore.so.4 = Xvid library License: GPL-2+ libx264.so.123 = x264 library License: GPL-2+ (unless used solely through avisynth_c.h interfaces) libmp3lame.so.0 = LAME library License: GPL-2+ (since it apparently includes GPL-licensed files) So, in summary, it seems to me that this binary is linked with a number of GPL-licensed libraries, and with two GPL-incompatible libraries (OpenCASCADE Community Edition and OpenSSL). Once again, the possible solutions I can think of, in descending order of desirability, are: (A) Open CASCADE S.A.S. should be contacted and persuaded to re-license Open CASCADE Technology under GPLv2-and-v3-compatible terms; OpenSSL should be replaced by GnuTLS or disabled. (B) OpenCASCADE Community Edition should be substituted with a GPLv2-and-v3-compatible replacement, if any is available; OpenSSL should be replaced by GnuTLS or disabled. (C) All the GPL-licensed libraries should be substituted with non-strong-copyleft replacements or disabled. As usual, if anyone is willing to contribute to the persuasion effort I am carrying on to convince Open CASCADE S.A.S. to switch to the GNU LGPL v2.1, his/her help will be more than appreciated by me! As explained in bug #617613 [4], I have been trying hard to achieve this result since April 2009... [4] http://bugs.debian.org/617613 Thanks for any help you can provide. P.S.: the binary package named libelmersolver-6.1 probably needs a similar audit ---End Message--- ---BeginMessage--- Source: elmerfem Source-Version: 6.1.0.svn.5396.dfsg2-2 We believe that the bug you reported is fixed in the latest version of elmerfem, 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 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boris Pek tehnic...@mail.ru (supplier of updated elmerfem package) (This message was generated automatically at their request; if you believe that there is a problem with it please
Bug#701056: marked as done (FTBFS: notangle: not found)
Your message dated Thu, 28 Feb 2013 21:32:50 + with message-id e1ubb5u-0005bx...@franck.debian.org and subject line Bug#701056: fixed in noweb 2.11b-7.1 has caused the Debian Bug report #701056, regarding FTBFS: notangle: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: noweb Version: 2.11b-7 Severity: serious Justification: FTBFS Usertags: goto-cc In an attempt to build the package in a clean pbuilder environment, the package FTBFS: dpatch apply-all [...] dpatch cat-all patch-stampT mv -f patch-stampT patch-stamp cd /home/mictau/build/noweb/noweb-2.11b/src ./awkname awk touch patch-awk-stamp dh_testdir cd /home/mictau/build/noweb/noweb-2.11b/src \ /usr/bin/make LIBSRC=icon ICONC=icont \ BIN=/usr/bin LIB=/usr/lib/noweb MAN=/usr/share/man \ LIBNAME=/usr/lib/noweb ELISP=/usr/share/emacs/site-lisp \ TEXINPUTS=/usr/share/texmf/tex/plain/misc \ TEXNAME=/usr/share/texmf/tex/plain/misc make[1]: Entering directory `/home/mictau/build/noweb/noweb-2.11b/src' chmod +w Makefile notangle -R'script' Makefile.nw | sh Makefile /bin/sh: 1: notangle: not found chmod -w Makefile chmod: Makefile: new permissions are r--rw-r--, not r--r--r-- make[1]: *** [Makefile] Error 1 It seems the package expects to find the notangle command, which is provided by the package itself, in the PATH. This isn't the case unless the noweb package is installed. The full build log is attached. Best, Michael failed-noweb.gz Description: application/gunzip pgprVVeWlLXB9.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: noweb Source-Version: 2.11b-7.1 We believe that the bug you reported is fixed in the latest version of noweb, 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. Maximiliano Curia m...@debian.org (supplier of updated noweb 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: Thu, 21 Feb 2013 21:43:25 +0100 Source: noweb Binary: noweb nowebm Architecture: source all amd64 Version: 2.11b-7.1 Distribution: unstable Urgency: low Maintainer: Hubert Chathi uho...@debian.org Changed-By: Maximiliano Curia m...@debian.org Description: noweb - A WEB-like literate-programming tool nowebm - A WEB-like literate-programming tool - transitional package Closes: 701056 Changes: noweb (2.11b-7.1) unstable; urgency=low . * Non-maintainer upload. * debian/patches/99_touch.dpatch: Add src/Makefile to the list of touched files. (Closes: #701056) Checksums-Sha1: cef190346e549bd548ed5fce073da1924bac31a0 1775 noweb_2.11b-7.1.dsc d62e67af3b5e3c7ed82bf04536ca2296a15b96e7 14939 noweb_2.11b-7.1.diff.gz 4620b85db345a1994e5364e36fb1401c5d53defe 5744 nowebm_2.11b-7.1_all.deb b465c75ba9dac1847829ed9ee6cdfd3e3902b379 757826 noweb_2.11b-7.1_amd64.deb Checksums-Sha256: 0b48cc3053f7747b67b73d6d961022d4b1cebdcbc724e5220a290d0b5ebfa406 1775 noweb_2.11b-7.1.dsc 300230e1bbea037bfd4dc9e665f87122d8d56d9a75fa8e9bc79db57a5e0134c3 14939 noweb_2.11b-7.1.diff.gz 1bb4add34f87d97afeacecbe51236ec12e94dc226994e498c59ba1ffe0b21738 5744 nowebm_2.11b-7.1_all.deb 98eb997a36ece0e73beac9f98f5bb22819d00dc1402323cc5a6a1bf90853a3a9 757826 noweb_2.11b-7.1_amd64.deb Files: dc46665e37e36e0cf11b854107c23cd0 1775 devel extra noweb_2.11b-7.1.dsc 5f0ee04d362e73da1e978a01d66c3450 14939 devel extra noweb_2.11b-7.1.diff.gz 7f96493f425fb9277e1234ebb81a1384 5744 devel extra nowebm_2.11b-7.1_all.deb 9e116454bf40959aeaf486138ff5e8d7 757826 devel extra noweb_2.11b-7.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRJooKAAoJEMcZdpmymyMq+K8P/0ifa3gCVSbUwCRE7kMXtPZI WjJRVQvLcuadzKSf+TxWGK75LeO3IjW9CiJQ3bx35TdsE04wS1j4e1W9nmSOjljy U+avww0lavT5G5i1n9snNOmnqgMEhYdybMYzOG1vh4HLoiEKCr5xfl60Vugi+Dvt A2BBWa3UUnhjSq53fke6R5X4B2MmMziOGjPGFq/F/LtDtbqJ1RXFXVAbyBJscdQw bYhKCwKiwDJ6pJoXoRf8BWbZCKGaoXRBudTFImPWbHd7aTpHWjXKbl9QGLZbJMYP
Bug#698068: mysql-server-5.5: Serious regression in replication caused by fix for CVE-2012-4414
I will try and upload 5.5.30 packages soon. No point in shipping old stuff in the release when more changes are bound to drop in security updates anyway. So we should downgrade this bug after that upload. On Feb 28, 2013, at 12:29, Adam D. Barratt a...@adam-barratt.org.uk wrote: On Sun, 2013-02-03 at 22:53 +0100, Moritz Mühlenhoff wrote: On Sat, Jan 26, 2013 at 11:26:27AM +, Adam D. Barratt wrote: On Sun, 2013-01-13 at 11:53 -0800, Clint Byrum wrote: According to this blog post by Stewart Smith: http://www.mysqlperformanceblog.com/2013/01/13/cve-2012-4414-in-mysql-5-5-29-and-percona-server-5-5-29/ It looks like 5.5.29 has a serious problem with replication. Is there any news on a fix for that? It unfortunately means the other RC fixes from 5.5.29 are stuck in unstable. :-( Personally I don't think a bug in some replication scenarios is more severe than migrating the security fixes... But I leave that to the MySQL maintainers. MySQL maintainers - ping? 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#699470: crystalhd-dkms: Kernel null pointer BUG in crystalhd_dioq_fetch_wait()
On 28.02.2013 20:41, Julien Cristau wrote: On Thu, Jan 31, 2013 at 19:25:50 +0100, tom schorpp wrote: Package: crystalhd-dkms Version: 1:0.0~git20110715.fdd2f19-7 Severity: critical Tags: patch Justification: breaks the whole system Reproducible NULL pointer BUG at crystalhd-0.0~git20110715.fdd2f19/driver/linux/crystalhd_misc.c:515, triggered by adobe flash plugin from dmo repo, ffmpeg, mplayer, bino or other, mostly on heavy ioq usage or after FETCH_TIMEOUT and/or unclosed driver HANDLEs. Does the maintainer or somebody on pkg-multimedia plan on fixing this RC bug? If not I'll consider a NMU removing the dkms package from crystalhd source. Cheers, Julien Known linux-media Maintainers STAGING - CRYSTAL HD VIDEO DECODER M:Naren Sankar nsan...@broadcom.com M:Jarod Wilson ja...@wilsonet.com M:Scott Davilla davi...@4pi.com M:Manu Abraham abraham.m...@gmail.com seem to have left the Broadcom's legacy driver code, focusing on the new linux-media staging driver, but limited time, one stated lately on the linux-media/LKML, nothing read from the others. I could adapt it to new kernel releases the next 2-3 years, but nothing more, not a experienced kernel driver coder, no debian package/policy maintaining motivation because I do not use dkms or debian kernels packages. If my last patch applies to Your codebase in the debian git repository (mine is from git.linuxtv.org, according to the git changelog more advanced in the gstreamer plugin, merge?) You may consider it hotfixed and release with known multithreading (gstreamer based transcoders/matroska demuxers) and PM ACPI S3 issues? Has not crashed here any more, nor notable side effects with usual playback use cases, including Totem (gstreamer). y tom -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701897: CVE-2012-5667: buffer overflow with overly long input lines
On Thu, Feb 28, 2013 at 21:56:12 +0100, Gianluca Ciccarelli wrote: I tag the issue with `squeeze' because it is the only possibly vulnerable version (2.11). Please don't do that. That's not what the suite tags are for, version tracking does that job (I removed the tag). Cheers, Julien signature.asc Description: Digital signature
Processed: tagging 701897
Processing commands for cont...@bugs.debian.org: tags 701897 - squeeze Bug #701897 [grep] CVE-2012-5667: buffer overflow with overly long input lines Removed tag(s) squeeze. thanks Stopping processing here. Please contact me if you need assistance. -- 701897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701897 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#698136: marked as done (dspam: recipient corrpution when releasing a message from quarantine)
Your message dated Thu, 28 Feb 2013 22:02:32 + with message-id e1ubbye-0001qr...@franck.debian.org and subject line Bug#698136: fixed in dspam 3.10.1+dfsg-9 has caused the Debian Bug report #698136, regarding dspam: recipient corrpution when releasing a message from quarantine 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.) -- 698136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dspam Version: 3.10.1+dfsg-6 Severity: important Dear Maintainer, When releasing mail from quarantine, dspam corrupts the FROM part in the SMTP/LMTP handshake (normal spam filter workflow works fine, this only affects the release process). The released email gets bounced and this leads to data loss, rendering the quarantine useless as false positives can't be recovered. please implement the following upstream patch that fixes the problem: http://dspam.git.sourceforge.net/git/gitweb.cgi?p=dspam/dspam;a=commit;h=cbed19764df8ecc1469f739ca33eb92aa3f67584 After applying the patch dspam works as intended. -- 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=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- dspam-3.10.1+dfsg.orig/src/dspam.c +++ dspam-3.10.1+dfsg/src/dspam.c @@ -499,7 +499,7 @@ process_message ( } /* Change also the mail recipient */ -ATX-recipient = CTX-username; +strcpy(ATX-recipient, CTX-username); } } ---End Message--- ---BeginMessage--- Source: dspam Source-Version: 3.10.1+dfsg-9 We believe that the bug you reported is fixed in the latest version of dspam, 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 698...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Preud'homme robo...@debian.org (supplier of updated dspam 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: Thu, 28 Feb 2013 21:33:50 +0100 Source: dspam Binary: dspam dspam-webfrontend libdspam7 libdspam7-dev libdspam7-drv-hash libdspam7-drv-pgsql libdspam7-drv-mysql libdspam7-drv-sqlite3 dspam-doc dspam-dbg libdspam7-dbg Architecture: source amd64 all Version: 3.10.1+dfsg-9 Distribution: testing-proposed-updates Urgency: low Maintainer: Debian DSPAM Maintainers pkg-dspam-m...@lists.alioth.debian.org Changed-By: Thomas Preud'homme robo...@debian.org Description: dspam - Scalable, fast and statistical anti-spam filter dspam-dbg - debugging symbols for dspam dspam-doc - Documentation for DSPAM anti-spam filter dspam-webfrontend - Webfrontend for DSPAM anti-spam filter libdspam7 - Core message processing and classification functionality for DSPA libdspam7-dbg - debugging symbols for DSPAM related libraries libdspam7-dev - Development headers for libdspam libdspam7-drv-hash - Hash backend for DSPAM anti-spam filter libdspam7-drv-mysql - MySQL backend for DSPAM anti-spam filter libdspam7-drv-pgsql - PostgreSQL backend for DSPAM anti-spam filter libdspam7-drv-sqlite3 - sqlite3 backend for DSPAM anti-spam filter Closes: 698136 Changes: dspam (3.10.1+dfsg-9) testing-proposed-updates; urgency=low . * Add a new version of the patch fixing recipient corruption when releasing a message from quarantine (Closes: #698136). Checksums-Sha1: 1c219f5498e2d30940b458411bbd833eb5598bed 2540 dspam_3.10.1+dfsg-9.dsc f3e32f2500653daed3ecb8ef933a145b9c67d811 64286 dspam_3.10.1+dfsg-9.debian.tar.gz 04b2e80397edb86821e848d85b8ffe6ba80827bd 425062 dspam_3.10.1+dfsg-9_amd64.deb 2e18eb54e7306851c748b6250c3c7e3248baa914 200596 dspam-webfrontend_3.10.1+dfsg-9_all.deb db24ec1f7f1009317bea020002185658e2d88096 149292 libdspam7_3.10.1+dfsg-9_amd64.deb 754f9b2e9867d45dbb67b1dce6f978a8bd4d378f 308320 libdspam7-dev_3.10.1+dfsg-9_amd64.deb b3252571c175eaa36305940887bb182137e29144 109740 libdspam7-drv-hash_3.10.1+dfsg-9_amd64.deb c86ad9ccc9bbf4cae19c8b29e70b44dd5ca60066 125338 libdspam7-drv-pgsql_3.10.1+dfsg-9_amd64.deb
Bug#634930: Bug#699560: gpa/0.9.0-4: Setting wheezy-ignore for #634930
On Fri, Feb 1, 2013 at 21:16:43 +0100, Daniel Leidert wrote: Package: release.debian.org Severity: normal Weitergeleitete Nachricht Von: Daniel Leidert daniel.leidert.s...@gmx.net An: debian-rele...@lists.debian.org Betreff: gpa/0.9.0-3: Setting wheezy-ignore for #634930 Datum: Sun, 27 Jan 2013 16:19:42 +0100 Hi, The upload of gpa/0.9.0-2 contained a workaround for #634930 [1] which avoids this crash. The crash itself is not reproducible for me although several people reported it. So the (programmed) cause is still unknown. But the bug appears on a special X.509 certificate [2]. So backporting the --disable-x509 switch is just a workaround. However it looks like the to be the best solution for wheezy atm. I'm therefor asking for setting the wheezy-ignore tag for this RC-bug. (The other RC bug is currently being fixed.) wheezy-ignore tag added. Cheers, Julien signature.asc Description: Digital signature
Processed: user release.debian....@packages.debian.org, usertagging 634930, tagging 634930
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was jcris...@debian.org). usertags 634930 wheezy-can-defer There were no usertags set. Usertags are now: wheezy-can-defer. # per 699560 tags 634930 + wheezy-ignore Bug #634930 [gpa] gpa: GPA unusable due to General Assuan error Added tag(s) wheezy-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 634930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634930 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#701936: btrfs-tools: renders systems with btrfs root file systems unbootable: check_mounted(): Could not open /run/rootdev + Could not check mount status: No such device or address
Package: btrfs-tools Version: 0.19+20130131-2 Severity: critical Justification: renders systems with btrfs as root file-system unbootable Hi, Axel Beckert wrote on Wed, 27 Feb 2013 20:01:30 +0100: btrfs-tools (0.19+20130131-2) unstable; urgency=low . * Replacing fsck.btrfs with wrapper arround 'btrfs check' to avoid different behaviour based on the filename btrfs is copied to (Closes: #701776). Thanks for the quick fix, but unfortunately the problem persists, just with a different error message and a different exit-code, but with the same symptom: The system fails to start. check_mounted(): Could not open /run/rootdev Could not check mount status: No such device or address fsck died with exit status 250 There's one more confirmation that there's still an issue which breaks systems, even with the newest version, at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701776#65 Additionally, several people contacted me on Jabber/IRC about how to fix this issue, too, so I'm posting a recipe at the end of this mail and also Cc this mail to #701776. Do you have any preference if #701776 should be reopend or if a new bug should be filed for that? Since I didn't get a reply from Daniel on this question within a day, I'm herewith filing a new bug report as the issue may have a different cause despite very similar symptoms and the affected systems still being broken if you don't downgrade btrfs-tools to 0.19+20121004-1 or earlier. As I already wrote in #701776, I consider such breakage of severity critical since http://www.debian.org/Bugs/Developer.en.html#severities defines critical as makes unrelated software on the system (or the whole system) break. I see this condition as given. For all those who are also suffering from this issue, too, here's the recipe how I downgraded btrfs-tools to the version from testing again on my system: At the maintenance mode password prompt, enter the root password. You may need to add /sbin and /usr/sbin to the path depending on your login shell setup. Thanks Christian Stalp! # export PATH=/sbin:/usr/sbin:$PATH With the default setup, sourcing /etc/profile should suffice. # . /etc/profile Mount the root file system read-write: # mount -o remount,rw / Mount the /boot partition, if existing: # mount /boot Either get network, ... # dhclient eth0 (Since Julien Cristau NMUed btrfs-tools in Wheezy yesterday[1], you may want to update your package lists, too.) # apt-get update ..., fetch the version from testing (assuming you have a deb-line with testing in your sources.list, too) and downgrade to it, ... # apt-get install -t testing btrfs-tools ... or, if you haven't done apt-get clean for a while, you may be able to just do # dpkg -i /var/cache/apt/archives/btrfs-tools_0.19+20121004-1_*.deb Then call sync to make sure the new version is on disk: # sync and reboot, e.g. by pressing Ctrl-D. That way, both, Christian and me got working systems back again. [1] http://packages.qa.debian.org/b/btrfs-tools/news/20130228T204729Z.html 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#680436: Not building on architectures which a package has not previously built on is not RC
Control: -1 severity important While this is certainly a bug, it's not a release critical bug. See http://release.debian.org/wheezy/rc_policy.txt §4. Don Armstrong -- To punish me for my contempt of authority, Fate has made me an authority myself -- Albert Einstein http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700716: marked as done (python-imaging: FTBFS: dh_movefiles: .../_imagingtk.so not found (supposed to put it in python-imaging-tk))
Your message dated Thu, 28 Feb 2013 23:17:44 +
with message-id e1ubcjq-0002qh...@franck.debian.org
and subject line Bug#700716: fixed in python-imaging 1.1.7+1.7.8-4
has caused the Debian Bug report #700716,
regarding python-imaging: FTBFS: dh_movefiles: .../_imagingtk.so not found
(supposed to put it in python-imaging-tk)
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.)
--
700716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-imaging
Version: 1.1.7+1.7.8-2
Severity: serious
Justification: fails to build from source
python-imaging FTBFS on buildds:
| dh_movefiles -ppython-imaging-tk \
| --sourcedir=debian/python-imaging \
| usr/lib/python2.6/$(basename $(_py_=2.6; python${_py_#python*}
-c 'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/_imagingtk.so \
| usr/lib/python2.6/$(basename $(_py_=2.6; python${_py_#python*}
-c 'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/PIL/ImageTk.py
| dh_movefiles:
debian/python-imaging/usr/lib/python2.6/dist-packages/_imagingtk.so not found
(supposed to put it in python-imaging-tk)
| make: *** [install-python2.6] Error 1
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=python-imagingarch=i386ver=1.1.7%2B1.7.8-2stamp=1360996465
--
Jakub Wilk
---End Message---
---BeginMessage---
Source: python-imaging
Source-Version: 1.1.7+1.7.8-4
We believe that the bug you reported is fixed in the latest version of
python-imaging, 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 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated python-imaging package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 28 Feb 2013 14:59:19 +0100
Source: python-imaging
Binary: python-imaging python-imaging-dbg python-imaging-tk
python-imaging-tk-dbg python-imaging-sane python-imaging-sane-dbg
python3-imaging python3-imaging-dbg python3-imaging-tk python3-imaging-tk-dbg
python3-imaging-sane python3-imaging-sane-dbg python-imaging-doc
python-imaging-compat
Architecture: source all amd64
Version: 1.1.7+1.7.8-4
Distribution: experimental
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
python-imaging - Python Imaging Library (Pillow fork)
python-imaging-compat - Python Imaging Library compatibility layer
python-imaging-dbg - Python Imaging Library (debug extension)
python-imaging-doc - Examples for the Python Imaging Library
python-imaging-sane - Python Imaging Library - SANE interface (Pillow fork)
python-imaging-sane-dbg - Python Imaging Library - SANE interface (debug
extension)
python-imaging-tk - Python Imaging Library - ImageTk Module (Pillow fork)
python-imaging-tk-dbg - Python Imaging Library - ImageTk Module (debug
extension)
python3-imaging - Python Imaging Library (Python3)
python3-imaging-dbg - Python Imaging Library (Python3 debug extension)
python3-imaging-sane - Python Imaging Library - SANE interface (Python3)
python3-imaging-sane-dbg - Python Imaging Library - SANE interface (Python
3debug extension)
python3-imaging-tk - Python Imaging Library - ImageTk Module (Python3)
python3-imaging-tk-dbg - Python Imaging Library - ImageTk Module (Python3
debug extension)
Closes: 700716
Changes:
python-imaging (1.1.7+1.7.8-4) experimental; urgency=low
.
* Require python-defaults (= 2.7.3-11) for the build. Closes: #700716.
Checksums-Sha1:
91773568f3cc20bc7fb4bda17aa99384f0e8f1d1 2244 python-imaging_1.1.7+1.7.8-4.dsc
bc6d2ed4ba79d4f99e8427e29f24de4b89046d3d 275151
python-imaging_1.1.7+1.7.8-4.debian.tar.gz
7b73cb57a12524afb57b7cc54181eb64dad4b344 19592
python-imaging-doc_1.1.7+1.7.8-4_all.deb
965b26434f7419f243e7d6d84364f51c802ae630 9430
python-imaging-compat_1.1.7+1.7.8-4_all.deb
5dcda7251def690b322658a16ccb1798fdbb34c9 446152
python-imaging_1.1.7+1.7.8-4_amd64.deb
41a81465845067290de8af32200845eabb521c72 1135132
python-imaging-dbg_1.1.7+1.7.8-4_amd64.deb
Bug#701779: marked as done (Fails to install due to missing library (in dependency?))
Your message dated Thu, 28 Feb 2013 23:48:59 + with message-id e1ubddf-0007c6...@franck.debian.org and subject line Bug#701779: fixed in ltt-control 2.1.1-1 has caused the Debian Bug report #701779, regarding Fails to install due to missing library (in dependency?) 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.) -- 701779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lttng-tools Version: 2.1.0~rc9-1 Severity: grave Justification: renders package unusable The package or one of its dependencies appears to be missing a symlink for a required library. Setting up lttng-tools (2.1.0~rc9-1) ... /usr/sbin/addgroup [] Starting lttng-sessiond : lttng-sessiond/usr/bin/lttng-sessiond: error while loading shared libraries: liblttng-ust-ctl.so.0: cannot open shared object file: No such file or directory failed! invoke-rc.d: initscript lttng-sessiond, action start failed. As shown in bold, liblttng-ust-ctl isnt found. $ ldd /usr/bin/lttng-sessiond linux-vdso.so.1 = (0x7fff551a5000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7fa93cce8000) liblttng-ctl.so.0 = /usr/lib/x86_64-linux-gnu/liblttng-ctl.so.0 (0x7fa93cac6000) liburcu-common.so.1 = /usr/lib/liburcu-common.so.1 (0x7fa93c8c2000) liburcu.so.1 = /usr/lib/liburcu.so.1 (0x7fa93c6bc000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa93c4b8000) *liblttng-ust-ctl.so.0 = not found* libpopt.so.0 = /lib/x86_64-linux-gnu/libpopt.so.0 (0x7fa93c2aa000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fa93c08e000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7fa93bd03000) /lib64/ld-linux-x86-64.so.2 (0x7fa93d15c000) Looking for it in the filesystem i find an unresolved symlink, liblttng-ust-ctl.so.1.0.0 $ ls -al /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl* -rw-r--r-- 1 root root 217596 Jan 21 09:01 /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.a lrwxrwxrwx 1 root root 25 Jan 21 09:01 /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.so - liblttng-ust-ctl.so.1.0.0 $ dpkg -S /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.so liblttng-ust-dev:amd64: /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.so $ dpkg -S liblttng-ust-ctl.so.1.0.0 dpkg-query: no path found matching pattern *liblttng-ust-ctl.so.1.0.0* Im not sure which package should be installing liblttng-ust-ctl.so.0 and liblttng-ust-ctl.so.1.0.0, but it didnt happen on my install. I guess i can just do the symlink myself. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lttng-tools depends on: ii libc6 2.13-38 ii liblttng-ctl0 2.1.0~rc9-1 ii liblttng-ust0 2.1.1-1 ii libpopt01.16-7 ii liburcu10.7.6-1 ii lttng-modules-dkms 2.1.0-1 Versions of packages lttng-tools recommends: ii babeltrace 1.0.3-1 lttng-tools suggests no packages. -- debconf-show failed ---End Message--- ---BeginMessage--- Source: ltt-control Source-Version: 2.1.1-1 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: Thu, 28 Feb 2013 18:34:16 -0500 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-1 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
Bug#699258: Pending fixes for bugs in the libio-async-loop-glib-perl package
tag 699258 + pending thanks Some bugs in the libio-async-loop-glib-perl package are closed in revision 507c63278450cb7f97b01cc60c5686e6cac8569e in branch 'master' by gregor herrmann The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libio-async-loop-glib-perl.git;a=commitdiff;h=507c632 Commit message: Disable t/06loop-control.t. These tests are unreliable and have been removed by upstream for the next release; cf. CPAN RT#83033. Closes: #699258 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libio-async-loop-glib-perl package
Processing commands for cont...@bugs.debian.org: tag 699258 + pending Bug #699258 [src:libio-async-loop-glib-perl] libio-async-loop-glib-perl: FTBFS: test failed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 699258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699258 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#699258: marked as done (libio-async-loop-glib-perl: FTBFS: test failed)
Your message dated Fri, 01 Mar 2013 00:32:58 + with message-id e1ubdue-0005t9...@franck.debian.org and subject line Bug#699258: fixed in libio-async-loop-glib-perl 0.20-3 has caused the Debian Bug report #699258, regarding libio-async-loop-glib-perl: FTBFS: test failed 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.) -- 699258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libio-async-loop-glib-perl Version: 0.20-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130129 qa-ftbfs Justification: FTBFS in wheezy on amd64 Hi, During a rebuild of all packages in *wheezy*, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00use.t ... ok t/01loop-io.t ... ok t/02loop-timer.t ok t/03loop-signal.t ... ok t/04loop-idle.t . ok t/05loop-child.t ok # Failed test 'loop_once(2) when idle took at least 1.5 seconds' # at /usr/share/perl5/IO/Async/LoopTests.pm line 140. # '3.814697265625e-05' # = # '1.5' # Looks like you failed 1 test of 12. t/06loop-control.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/12 subtests t/11share-io.t .. ok t/12share-timer.t ... ok t/15share-child.t ... ok t/99pod.t ... ok Test Summary Report --- t/06loop-control.t (Wstat: 256 Tests: 12 Failed: 1) Failed test: 6 Non-zero exit status: 1 Files=11, Tests=111, 18 wallclock secs ( 0.04 usr 0.07 sys + 0.70 cusr 0.18 csys = 0.99 CPU) Result: FAIL Failed 1/11 test programs. 1/111 subtests failed. make[1]: *** [test_dynamic] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2013/01/29/libio-async-loop-glib-perl_0.20-2_wheezy.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: libio-async-loop-glib-perl Source-Version: 0.20-3 We believe that the bug you reported is fixed in the latest version of libio-async-loop-glib-perl, 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 699...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated libio-async-loop-glib-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 01 Mar 2013 01:16:04 +0100 Source: libio-async-loop-glib-perl Binary: libio-async-loop-glib-perl Architecture: source all Version: 0.20-3 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libio-async-loop-glib-perl - Perl extension for an event loop using GLib Closes: 699258 Changes: libio-async-loop-glib-perl (0.20-3) unstable; urgency=low . * Disable t/06loop-control.t. These tests are unreliable and have been removed by upstream for the next release; cf. CPAN RT#83033. (Closes: #699258) Checksums-Sha1: fedf68890aad99396400b7577c6057d08b910026 2308 libio-async-loop-glib-perl_0.20-3.dsc 9c49a31a9ebe884bcb1a9326b45211ceda3fddb2 2920 libio-async-loop-glib-perl_0.20-3.debian.tar.gz d780a78207eaf02a71aaceb22a15246e0dd4e74b 9896 libio-async-loop-glib-perl_0.20-3_all.deb Checksums-Sha256: 4f671cc8e5df93d8fd5f3e6650da41d39662164996f53874b653f690e7c40001 2308 libio-async-loop-glib-perl_0.20-3.dsc 533e811ba5f64bf98f9ae0a9d19700052e0afde71fbe674628e9c1d8f7d6ec31 2920 libio-async-loop-glib-perl_0.20-3.debian.tar.gz 74104345b8dbdb4d021c3b2c9dda3e3b4b969828cf095ef540d3bb97c1d79c23 9896 libio-async-loop-glib-perl_0.20-3_all.deb Files: db270ffbd98fca16658d051a3b1816a4 2308 perl
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 692899 + pending Bug #692899 [zope2.12] zope2.12: [CVE-2012-5485 to 5508] Multiple vectors corrected within 20121106 fix Added tag(s) pending. tags 699743 + patch Bug #699743 [emms] emms: fails to upgrade lenny - squeeze - wheezy: emms-setup.el:96:8:Error: Symbol's value as variable is void: emms-directory Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 692899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692899 699743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699743 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#701916: Kill local user processes on logout
Processing control commands: tags 701916 pending Bug #701916 [ltsp-client-core] Kill local user processes on logout Added tag(s) pending. tags 700881 pending Bug #700881 [ltsp-client-core] ltsp-client-core: thin client can't boot if it has set PRINTER_0_DEVICE in lts.conf Added tag(s) pending. -- 700881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700881 701916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701916 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#701916: Kill local user processes on logout
Processing control commands: tags 701916 pending Bug #701916 [ltsp-client-core] Kill local user processes on logout Ignoring request to alter tags of bug #701916 to the same tags previously set tags 700881 pending Bug #700881 [ltsp-client-core] ltsp-client-core: thin client can't boot if it has set PRINTER_0_DEVICE in lts.conf Ignoring request to alter tags of bug #700881 to the same tags previously set -- 700881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700881 701916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701916 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#701916: Kill local user processes on logout
Control: tags 701916 pending
Control: tags 700881 pending
Committed the following to the ltsp-debian-packaging bzr branch:
diff -Nru ltsp-5.4.2/debian/changelog ltsp-5.4.2/debian/changelog
--- ltsp-5.4.2/debian/changelog 2013-01-08 22:01:18.0 -0800
+++ ltsp-5.4.2/debian/changelog 2013-02-28 17:46:18.0 -0800
@@ -1,3 +1,15 @@
+ltsp (5.4.2-6) UNRELEASED; urgency=low
+
+ * Add patch to run jetpipe from ltsp-client-core init script rather than
+init-ltsp.d hook (Closes: #700881). Running from init-ltsp.d is far too
+early in the boot process and causes daemonization to fail, which stops
+boot from continuing. Thanks to James McQuillan for the report.
+ * Avoid data loss with fatclients or localapps by killing local user
+processes at end of session (LP: #1093144, Closes: #701916).
+Thanks to Alkis Georgopoulos for the patch!
+
+ -- Vagrant Cascadian vagr...@debian.org Mon, 18 Feb 2013 13:50:35 -0800
+
ltsp (5.4.2-5) unstable; urgency=low
* ltsp-client-core: Depend on initramfs-tools 0.99, to ensure /run is
diff -Nru ltsp-5.4.2/debian/patches/jetpipe-from-ltsp-client-core-init-script
ltsp-5.4.2/debian/patches/jetpipe-from-ltsp-client-core-init-script
--- ltsp-5.4.2/debian/patches/jetpipe-from-ltsp-client-core-init-script
1969-12-31 16:00:00.0 -0800
+++ ltsp-5.4.2/debian/patches/jetpipe-from-ltsp-client-core-init-script
2013-02-18 14:14:37.0 -0800
@@ -0,0 +1,82 @@
+Author: Vagrant Cascadian vagr...@debian.org
+Bug-Debian: http://bugs.debian.org/700881
+Upstream-Bug: https://bugs.launchpad.net/ltsp/+bug/996533
+
+Start jetpipe from ltsp-client-core init script, as it fails to daemonize when
+executed from init-ltsp.d, which is run before /sbin/init is started.
+
+Index: ltsp-5.4.2/client/initscripts/ltsp-core
+===
+--- ltsp-5.4.2.orig/client/initscripts/ltsp-core 2013-02-18
14:07:20.509826079 -0800
ltsp-5.4.2/client/initscripts/ltsp-core2013-02-18 14:07:25.593851287
-0800
+@@ -35,6 +35,33 @@
+ . /lib/lsb/init-functions
+ . /usr/share/ltsp/ltsp-init-common
+
++start_printers() {
++for I in 0 1 2; do
++eval PRINTER_DEVICE=\$\{PRINTER_${I}_DEVICE\}
++if [ -n ${PRINTER_DEVICE} ]; then
++eval PORT=\$\{PRINTER_${I}_PORT:=910${I}\}
++eval BAUD=\$\{PRINTER_${I}_SPEED:-9600\}
++eval SIZE=\$\{PRINTER_${I}_DATABITS:-8\}
++eval PARITY=\$\{PRINTER_${I}_PARITY:-none\}
++eval FLOW=\$\{PRINTER_${I}_FLOWCTRL:-soft\}
++
++JETPIPE_ARGS=
++[ -n $BAUD ] JETPIPE_ARGS=${JETPIPE_ARGS} -b ${BAUD}
++[ -n $SIZE ] JETPIPE_ARGS=${JETPIPE_ARGS} -y ${SIZE}
++[ -n $PARITY ] JETPIPE_ARGS=${JETPIPE_ARGS} -p ${PARITY}
++if [ -n $FLOW ]; then
++if [ $FLOW = soft ]; then
++JETPIPE_ARGS=${JETPIPE_ARGS} -x
++else
++JETPIPE_ARGS=${JETPIPE_ARGS} -r
++fi
++fi
++
++/usr/sbin/jetpipe ${JETPIPE_ARGS} ${PRINTER_DEVICE} ${PORT}
++fi
++done
++}
++
+ case $1 in
+ start)
+ log_action_begin_msg Starting LTSP client...
+@@ -48,6 +75,7 @@
+ /bin/plymouth quit --retain-splash
+ fi
+
++start_printers || true
+ start_screen_sessions || true
+ start_sound || true
+
+Index: ltsp-5.4.2/client/share/ltsp/init-ltsp.d/50-jetpipe
+===
+--- ltsp-5.4.2.orig/client/share/ltsp/init-ltsp.d/50-jetpipe 2013-02-18
14:07:20.509826079 -0800
/dev/null 1970-01-01 00:00:00.0 +
+@@ -1,24 +0,0 @@
+-for I in 0 1 2; do
+-eval PRINTER_DEVICE=\$\{PRINTER_${I}_DEVICE\}
+-if [ -n ${PRINTER_DEVICE} ]; then
+-eval PORT=\$\{PRINTER_${I}_PORT:=910${I}\}
+-eval BAUD=\$\{PRINTER_${I}_SPEED:-9600\}
+-eval SIZE=\$\{PRINTER_${I}_DATABITS:-8\}
+-eval PARITY=\$\{PRINTER_${I}_PARITY:-none\}
+-eval FLOW=\$\{PRINTER_${I}_FLOWCTRL:-soft\}
+-
+-JETPIPE_ARGS=
+-[ -n $BAUD ] JETPIPE_ARGS=${JETPIPE_ARGS} -b ${BAUD}
+-[ -n $SIZE ] JETPIPE_ARGS=${JETPIPE_ARGS} -y ${SIZE}
+-[ -n $PARITY ] JETPIPE_ARGS=${JETPIPE_ARGS} -p ${PARITY}
+-if [ -n $FLOW ]; then
+-if [ $FLOW = soft ]; then
+-JETPIPE_ARGS=${JETPIPE_ARGS} -x
+-else
+-JETPIPE_ARGS=${JETPIPE_ARGS} -r
+-fi
+-fi
+-
+-/usr/sbin/jetpipe ${JETPIPE_ARGS} ${PRINTER_DEVICE} ${PORT}
+-fi
+-done
diff -Nru ltsp-5.4.2/debian/patches/kill-local-processes
ltsp-5.4.2/debian/patches/kill-local-processes
--- ltsp-5.4.2/debian/patches/kill-local-processes 1969-12-31
16:00:00.0 -0800
+++ ltsp-5.4.2/debian/patches/kill-local-processes 2013-02-28
17:19:10.0 -0800
@@ -0,0 +1,53 @@
+ 2462 Alkis Georgopoulos 2013-02-27
+ revision-id:alk...@gmail.com-20130227091132-h2ql7stdqy42yhx8
+ Kill local user
Bug#701936: btrfs-tools: renders systems with btrfs root file systems unbootable: check_mounted(): Could not open /run/rootdev + Could not check mount status: No such device or address
Hi,
some more information about the issue:
Happens on Sid i386 for me. /boot is a separate partition and / is a
btrfs upon a dm_crypt partition.
Axel Beckert wrote:
check_mounted(): Could not open /run/rootdev
Could not check mount status: No such device or address
fsck died with exit status 250
I provoked this situation again and also tried Dmitrijs's patch from
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=45;filename=fix-up-fsck.patch;att=1;bug=701776
in combination with Daniel's new wrapper, but that doesn't change
anything.
/run/rootdev exists in that situation and looks like this:
brw--- 1 root root 0, 16 Mar 1 00:56 /run/rootdev
It's not mounted at that point. (The root partition is mounted ro at
/dev/mapper/sda2_crypt in my case.)
From utils.c:
812 fd = open(file, O_RDONLY);
813 if (fd 0) {
814 fprintf (stderr, check_mounted(): Could not open
%s\n, file);
815 return -errno;
816 }
From open(3):
ENXIO The named file is a character special or block special file,
and the device associated with this special file does not exist.
So btrfs check tries to read /run/rootdev but can't find the
according device to that block special file.
Potential explanations for this behaviour:
* /run/rootdev has the wrong major and minor numbers. (But it
worked before, e.g. with btrfs-tools from testing. Nevertheless
other tools like less -f provoke the same error.)
* btrfs check accesses the blockdevice in a different way than
btrfsck did. (But I couldn't find any relevant difference in the
source code compared to the code of the working version on a first a
glance.)
So both explanations seem unrealistic for some reasons... Which
suggests that the culprit is probably somewhere else. :-/
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: Re: [pkg-dhcp-devel] Bug#648401: isc-dhcp-relay: dhcrelay(8) doesn't mention need for -i on server facing interface
Processing control commands: severity -1 important Bug #648401 [isc-dhcp-relay] DHCP relay agent does not listen properly for return packets Severity set to 'important' from 'grave' -- 648401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648401 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#648401: [pkg-dhcp-devel] Bug#648401: isc-dhcp-relay: dhcrelay(8) doesn't mention need for -i on server facing interface
control: severity -1 important On Tue, Feb 19, 2013 at 5:59 PM, Steinar H. Gunderson wrote: I'd say this means dhcrelay itself is pretty much completely broken, and I'm upgrading severity accordingly. It shouldn't subject the BOOTREPLY packets to interface checking, or it should have a separate list of interfaces from which it can come; I think this actually works for DHCPv6, where you have separate “lower” and “upper” interface options, but I haven't tested it. Although this behavior is not quite right, its also not entirely broken, so I'm downgrading the severity. For wheezy, those few users that really require correct behavior here can apply the patch themselves. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701945: ccrypt fails to install with emac23 due to /etc/emacs23/site-start.d does not exist
Package: ccrypt Version: 1.9-4 Severity: serious Justification: Fails to install due to wrong path /etc/emacs/site-start.d exists /etc/emacs23/stie-start.d does not. This breaks ccrypt's install script and ccrypt fails to install. emacs23 is successfully installed (after removed; it could not install with ccrypt installed due to this same error). -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ccrypt depends on: ii libc6 2.13-38 ccrypt recommends no packages. ccrypt 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: Re: Bug#651636 GtkLauncher segfaults on mipsel, JavaScript-related
Processing control commands: severity -1 important Bug #651636 [src:webkit] GtkLauncher segfaults on mipsel, JavaScript-related Bug #673469 [src:webkit] libwebkitgtk-1.0-0: segfaults all the time on armel, javascript related Bug #688640 [src:webkit] JavaScriptCore segmentation fault on PowerPC Severity set to 'important' from 'grave' Severity set to 'important' from 'grave' Severity set to 'important' from 'grave' -- 651636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651636 673469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673469 688640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 701350 experimental Bug #701350 [src:s3ql] Data corruption with eglibc 2.17 Added tag(s) experimental. thanks Stopping processing here. Please contact me if you need assistance. -- 701350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701350 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#701350: Processed: your mail
Hi Michael, What does the experimental tag mean? I just removed the sid tag on behest of the release team, so I'm not sure that this one is appropriate either. Note that even though the unit tests only fail with libc 2.17, both the woody and sid S3QL versions contain the buggy code. Best, -Nikolaus On 02/28/2013 07:24 PM, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: tag 701350 experimental Bug #701350 [src:s3ql] Data corruption with eglibc 2.17 Added tag(s) experimental. thanks Stopping processing here. Please contact me if you need assistance. -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701949: elserv: fails to install with emacs33; cat -: No such file or directory during byte-compilation
Package: elserv Version: 0.4.0+0.20011203cvs-17.1 Severity: serious Justification: Fails to install elserv's install script is broken: Install elserv for emacs Install elserv for emacs23 install/elserv: Handling emacs23, logged in /tmp/elc_xMv5B7.log -- which file is empty cat: -: No such files or directory ERROR: install script from elserv package failed dpkg: error processing elserver (--configure): subprocess installed post-installation script returned error exit status 1 The error can be worked around by not using cat EOF notation (maybe an extraneous leading space?) -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages elserv depends on: ii emacs23 [emacsen] 23.4+1-4 ii flim 1:1.14.9+0.20110516-1 ii ruby 4.9 ii ruby1.8 [ruby] 1.8.7.358-6 elserv recommends no packages. Versions of packages elserv suggests: pn emacs-wiki none pn mhc none -- 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#701949: elserv: heredocs are lazy evaluated which means parantheses are a problem
Package: elserv Version: 0.4.0+0.20011203cvs-17.1 Followup-For: Bug #701949 Upon googling (well really duckduckgo) I discovered that heredocs (e.g the cat EOF path.el) are lazy evaluated in bash, which I think means the parentheses get evaluated before the cat, which screws up the heredoc (empty). In any event replacing there heredoc with echo ( setq ... ) path.el works around the issue. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages elserv depends on: ii emacs23 [emacsen] 23.4+1-4 ii flim 1:1.14.9+0.20110516-1 ii ruby 4.9 ii ruby1.8 [ruby] 1.8.7.358-6 elserv recommends no packages. Versions of packages elserv suggests: pn emacs-wiki none pn mhc none -- 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#701838: marked as done (sudo: CVE-2013-1775 authentication bypass when clock is reset)
Your message dated Fri, 01 Mar 2013 05:32:53 + with message-id e1ubiat-0007fq...@franck.debian.org and subject line Bug#701838: fixed in sudo 1.8.5p2-1+nmu1 has caused the Debian Bug report #701838, regarding sudo: CVE-2013-1775 authentication bypass when clock is reset 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.) -- 701838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sudo Severity: grave Tags: security Hi, the following vulnerability was published for sudo. CVE-2013-1775[0]: (from the upstream report) Sudo 1.8.6p7 and 1.7.10p7 are now available which include a fix for the following bug: Sudo authentication bypass when clock is reset Summary: When a user successfully authenticates with sudo, a time stamp file is updated to allow that user to continue running sudo without requiring a password for a preset time period (five minutes by default). The user's time stamp file can be reset using sudo -k or removed altogether via sudo -K. A user who has sudo access and is able to control the local clock (common in desktop environments) can run a command via sudo without authenticating as long as they have previously authenticated themselves at least once by running sudo -k and then setting the clock to the epoch (1970-01-01 01:00:00). The vulnerability does not permit a user to run commands other than those allowed by the sudoers policy. Sudo versions affected: Sudo 1.6.0 through 1.7.10p7 and sudo 1.8.0 through 1.8.6p7. Details: By default, sudo displays a lecture when the user's time stamp file is not present. In sudo 1.6, the -k option was changed to reset the time stamp file to the epoch rather than remove it to prevent the lecture from being displayed the next time sudo was run. No special case was added for handling a time stamp file set to the epoch since the clock should never legitimately be set to that value. However, there are two common ways for the clock to be reset to the epoch. The first way is when the clock is reset due to a fully drained battery on some systems. The other way is by a user logged in to a desktop environment that allows changes to the date and time. As long as the user has successfully run sudo before, they are able to run sudo -k to reset the time stamp file. This action does not require a password and is not logged. If the user is also able to reset the date and time to the epoch (1970-01-01 01:00:00), they will be able to run sudo without having to authenticate. Impact: The flaw may allow someone with physical access to a machine that is not password-protected to run sudo commands without knowing the logged in user's password. On systems where sudo is the principal way of running commands as root, such as on Ubuntu and Mac OS X, there is a greater chance that the logged in user has run sudo before and thus that an attack would succeed. Fix: The bug is fixed in sudo 1.8.6p7 and 1.7.10p7. These versions will ignore a time stamp file that is set to the epoch. Workaround: Using sudo -K instead of sudo -k will completely remove the time stamp file instead of just resetting it. Credit: I'd like to thank Marco Schoepl for finding and reporting this long-standing bug. 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-2013-1775 http://security-tracker.debian.org/tracker/CVE-2013-1775 Please adjust the affected versions in the BTS as needed. Cheers Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 pgpMVtipusY2f.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: sudo Source-Version: 1.8.5p2-1+nmu1 We believe that the bug you reported is fixed in the latest version of sudo, 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. Michael Gilbert mgilb...@debian.org (supplier of updated sudo package) (This message was generated automatically at their
Bug#701952: debian-el: fails to install due to heredoc failing; lazy evaluation and parentheses the culprit?
Package: debian-el Version: 35.2+nmu1 Severity: serious Justification: fails to install Like elserv debian-el fails to install, complaining that cat: -: No such file. Also like elserv, replacing the heredoc (cat EOF path.el (setq ... ) EOF) with echo (setq ... ) path.el works. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debian-el depends on: ii bzip2 1.0.6-4 ii dpkg 1.16.9 ii emacs23 [emacsen] 23.4+1-4 ii file 5.11-2 ii install-info 4.13a.dfsg.1-10 ii reportbug 6.4.3 Versions of packages debian-el recommends: ii dlocate 1.02 ii groff-base 1.21-9 ii wget1.13.4-3 Versions of packages debian-el suggests: pn gnus none -- 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#701952: dpkg-dev-el: Also dpkg-dev-el fails for same reason (bad heredoc)
Package: dpkg-dev-el Version: 35.2+nmu1 Followup-For: Bug #701952 dpkg-dev-el exhibits the same problem (heredoc fails), with same solution (replace heredoc with echo and quoting any quotes). -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg-dev-el depends on: ii debian-el 35.2+nmu1 ii emacs23 [emacsen] 23.4+1-4 Versions of packages dpkg-dev-el recommends: ii wget 1.13.4-3 Versions of packages dpkg-dev-el suggests: ii dpkg-dev 1.16.9 -- 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#701952: devscripts-el: Also devscript-el (bad heredoc)
Package: devscripts-el Version: 35.2+nmu1 Followup-For: Bug #701952 Heredoc problem is also present in devscripts-el and using echo makes it work. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devscripts-el depends on: ii apel 10.8-2 ii bash 4.2+dfsg-0.1 ii devscripts 2.12.6 ii dpkg-dev-el35.2+nmu1 ii emacs23 [emacsen] 23.4+1-4 Versions of packages devscripts-el recommends: ii elserv 0.4.0+0.20011203cvs-17.1 devscripts-el 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: tags 701185 + patch
Processing commands for cont...@bugs.debian.org: tags 701185 + patch Bug #701185 [hplip] CVE-2013-0200: Insecure temporary files Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 701185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701185 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#701838: nmu for security issues
Hi, I uploaded an nmu fixing the recent security issues. Please see attached patch. Best wishes, Mike sudo.patch Description: Binary data
Bug#701953: initramfs-tools: Missing modules prevent passphrase entry with usb keyboard
Package: initramfs-tools Version: 0.109 Severity: critical Justification: breaks the whole system Dear Maintainer, I have a usb keyboard attached to a system with an unencrypted /boot and a LUKS-encrypted partition (LVM physical volume) containing the other filesystems. Today I installed linux-image-3.8-trunk-amd64 (3.8-1~experimental.1). initramfs-tools created a corresponding initrd, as expected. Booting this kernel/initrd in grub2 resulted in a plymouth passphrase entry screen, but a usb keyboard that did not work in any port. All keyboard lights were off. The system was thus unbootable without a non-usb keyboard (hence critical severity). Without a non-usb keyboard or backup grub entry (3.7 kernel with working initrd), I would have been unable to access my system without rescue media. This is a regression from the behaviour of initramfs-tools with linux-image-3.7 -trunk-amd64 (3.7.8-1~experimental.1). The failure appears identical to this: http://linux-kernel.2935.n7.nabble.com/PROBLEM-3-8-0-rc4-keyboard-failure-at- boot-tp585937p587518.html Workaround is to add the following modules to /etc/initramfs-tools/modules, as described in the link above: ehci_pci usbcore usb_common xhci_hcd uhci_hcd ehci_hcd ohci_hcd usbhid hid_generic Once these lines were added, I ran update-initramfs -u, was able to boot linux-image-3.8-trunk-amd64 with the new initrd, successfully enter my passphrase at the plymouth prompt with a usb keyboard, and the system booted normally. See also #639876. This report differs in that I have MODULES=most. And this is critical not wishlist. -- Package-specific info: -- initramfs sizes -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.8-trunk-amd64 root=/dev/mapper/vg-root ro quiet splash -- /proc/filesystems ext4 fuseblk -- lsmod Module Size Used by cpufreq_conservative13225 0 cpufreq_stats 12866 0 cpufreq_powersave 12454 0 cpufreq_userspace 12576 0 ppdev 12763 0 lp 17160 0 ip6t_REJECT12512 2 nf_conntrack_ipv6 13649 1 nf_defrag_ipv6 12885 1 nf_conntrack_ipv6 ip6table_filter12540 1 ip6_tables 22011 1 ip6table_filter ipt_REJECT 12502 2 xt_tcpudp 12570 1 nf_conntrack_ipv4 18549 2 nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 uinput 17478 1 xt_conntrack 12681 3 nf_conntrack 58420 3 xt_conntrack,nf_conntrack_ipv4,nf_conntrack_ipv6 iptable_filter 12536 1 ip_tables 21997 1 iptable_filter x_tables 19041 8 ip6table_filter,ip_tables,xt_tcpudp,xt_conntrack,iptable_filter,ipt_REJECT,ip6_tables,ip6t_REJECT loop 22908 0 fuse 62705 3 acpi_cpufreq 13354 0 mperf 12453 1 acpi_cpufreq arc4 12543 2 iwldvm111692 0 mac80211 371723 1 iwldvm snd_hda_codec_hdmi 31479 1 snd_hda_codec_idt 53750 1 iTCO_wdt 12831 0 iTCO_vendor_support12704 1 iTCO_wdt snd_usb_audio 105940 1 snd_usbmidi_lib23337 1 snd_usb_audio snd_hda_intel 31301 3 snd_seq_midi 12848 0 snd_seq_midi_event 13316 1 snd_seq_midi snd_hda_codec 88441 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel snd_rawmidi23034 2 snd_usbmidi_lib,snd_seq_midi snd_hwdep 13189 2 snd_usb_audio,snd_hda_codec snd_pcm68523 4 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel snd_page_alloc 13018 2 snd_pcm,snd_hda_intel uvcvideo 70803 0 snd_seq45225 2 snd_seq_midi_event,snd_seq_midi iwlwifi64362 1 iwldvm videobuf2_vmalloc 12860 1 uvcvideo coretemp 12854 0 snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi videobuf2_memops 12519 1 videobuf2_vmalloc snd_timer 22812 2 snd_pcm,snd_seq videobuf2_core 31098 1 uvcvideo kvm_intel 118327 0 videodev 92117 2 uvcvideo,videobuf2_core dell_wmi 12477 0 sparse_keymap 12760 1 dell_wmi dell_laptop16779 0 snd53077 20 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device media 18184 2 uvcvideo,videodev kvm 319005 1 kvm_intel dcdbas 13307 1 dell_laptop soundcore 13026 1 snd psmouse69190 0 joydev 17317 0 serio_raw 12940 0 cfg80211 352039 3 iwlwifi,mac80211,iwldvm i2c_i801 17045 0 parport_pc 22409 0 parport31901 3 lp,ppdev,parport_pc lpc_ich16757 0 rfkill 19166 1 cfg80211 mei
Processed: Re: Bug#701936: btrfs-tools: renders systems with btrfs root file systems unbootable: check_mounted(): Could not open /run/rootdev + Could not check mount status: No such device or addre
Processing commands for cont...@bugs.debian.org: retitle 701936 btrfs can't fsck /run/rootdev on boot Bug #701936 [btrfs-tools] btrfs-tools: renders systems with btrfs root file systems unbootable: check_mounted(): Could not open /run/rootdev + Could not check mount status: No such device or address Changed Bug title to 'btrfs can't fsck /run/rootdev on boot' from 'btrfs-tools: renders systems with btrfs root file systems unbootable: check_mounted(): Could not open /run/rootdev + Could not check mount status: No such device or address' severity 701936 serious Bug #701936 [btrfs-tools] btrfs can't fsck /run/rootdev on boot Severity set to 'serious' from 'critical' tag 701936 sid Bug #701936 [btrfs-tools] btrfs can't fsck /run/rootdev on boot Added tag(s) sid. thanks Stopping processing here. Please contact me if you need assistance. -- 701936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701936 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#701649: libvirt-bin - libvirtd changes permissions of devices to libvirt-qemu:kvm (CVE-2013-1766)
Figured I'd add that it's not limited to devices- it can change the permissions of arbitrary files, such as /boot/vmlinuz-*, if that matters. live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701936: btrfs can't fsck /run/rootdev on boot
retitle 701936 btrfs can't fsck /run/rootdev on boot with sysvinit severity 701936 important clone 701936 -1 reassign -1 sysvinit thanks works with systemd, it's sysvinit specific. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: btrfs can't fsck /run/rootdev on boot
Processing commands for cont...@bugs.debian.org: retitle 701936 btrfs can't fsck /run/rootdev on boot with sysvinit Bug #701936 [btrfs-tools] btrfs can't fsck /run/rootdev on boot Changed Bug title to 'btrfs can't fsck /run/rootdev on boot with sysvinit' from 'btrfs can't fsck /run/rootdev on boot' severity 701936 important Bug #701936 [btrfs-tools] btrfs can't fsck /run/rootdev on boot with sysvinit Severity set to 'important' from 'serious' clone 701936 -1 Bug #701936 [btrfs-tools] btrfs can't fsck /run/rootdev on boot with sysvinit Bug 701936 cloned as bug 701956 reassign -1 sysvinit Bug #701956 [btrfs-tools] btrfs can't fsck /run/rootdev on boot with sysvinit Bug reassigned from package 'btrfs-tools' to 'sysvinit'. No longer marked as found in versions btrfs-tools/0.19+20130131-2. Ignoring request to alter fixed versions of bug #701956 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 701936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701936 701956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701956 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
