Processed: severity 735503 normal
Processing commands for cont...@bugs.debian.org: > severity 735503 normal Bug #735503 [src:horizon] Sourceless file Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 735503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735503 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#735503: Fixed upstream
Hi, FYI, this has been fixed upstream [1], and is scheduled to be released on the 17th of April with the rest of OpenStack Icehouse. Therefore, it is my view that, while this bug still exist, its severity can be downgraded. It would be currently complicated and not productive to maintain a specific DFSG branch, and I don't think it's worse the effort, as it will be solved soon anyway. Thomas [1] https://review.openstack.org/#/c/67096/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: icedtea-web: FTBFS[kfreebsd-any]: sun.security.util.SecurityConstants not found
Processing control commands: > tags -1 + pending Bug #739032 {Done: Matthias Klose } [src:openjdk-7] icedtea-web: FTBFS[kfreebsd-any]: sun.security.util.SecurityConstants not found Added tag(s) pending. -- 739032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739032 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#739032: icedtea-web: FTBFS[kfreebsd-any]: sun.security.util.SecurityConstants not found
Control: tags -1 + pending fixed in bzr. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740802: stunnel4: CVE-2014-0016
Package: stunnel4 Severity: grave Tags: security Justification: user security hole Hi, please see http://article.gmane.org/gmane.comp.security.oss.general/12283 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740696: marked as done (bash: Uninstallable, file /usr/share/doc/bash/bash.html in both bash and bash-doc)
Your message dated Wed, 05 Mar 2014 06:58:20 +0100 with message-id <5316bcfc.9050...@debian.org> and subject line Re: Bug#740696: bash: Uninstallable, file /usr/share/doc/bash/bash.html in both bash and bash-doc has caused the Debian Bug report #740696, regarding bash: Uninstallable, file /usr/share/doc/bash/bash.html in both bash and bash-doc 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.) -- 740696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bash bash-doc Version: 4.3-1 Severity: grave Justification: renders package unusable bash_4.3-1_amd64.deb can't install with bash-doc (either 4.2+dfsg-1 or 4.3). Also the file is a slightly different size between bash 4.3-1 and bash-doc 4.3-1. Preparing to unpack .../archives/bash_4.3-1_amd64.deb ... Unpacking bash (4.3-1) over (4.2+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/bash_4.3-1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/bash/bash.html', which is also in package bash-doc 4.2+dfsg-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) $ dpkg-deb -c /var/cache/apt/archives/bash_4.3-1_amd64.deb | grep bash.html -rw-r--r-- root/root329685 2014-03-03 22:27 ./usr/share/doc/bash/bash.html $ dpkg-deb -c /var/cache/apt/archives/bash-doc_4.3-1_all.deb | grep bash.html -rw-r--r-- root/root330770 2014-03-03 22:27 ./usr/share/doc/bash/bash.html lrwxrwxrwx root/root 0 2014-03-03 22:27 ./usr/share/doc/bash-doc/bash.html -> ../bash/bash.html -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0-rc5-local-00041-g8cb38e9-dirty (SMP w/6 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 7.2 ii dash 0.5.7-4 ii debianutils 4.4 ii libc62.18-4 ii libtinfo55.9+20140118-1 Versions of packages bash recommends: pn bash-completion Versions of packages bash suggests: ii bash-doc 4.2+dfsg-1 -- no debconf information --- End Message --- --- Begin Message --- Version: 4.3-2 Am 04.03.2014 07:33, schrieb Steve Cotton: > Package: bash bash-doc > Version: 4.3-1 > Severity: grave > Justification: renders package unusable > > bash_4.3-1_amd64.deb can't install with bash-doc (either 4.2+dfsg-1 or 4.3). > > Also the file is a slightly different size between bash 4.3-1 and bash-doc > 4.3-1. > > Preparing to unpack .../archives/bash_4.3-1_amd64.deb ... > Unpacking bash (4.3-1) over (4.2+dfsg-1) ... > dpkg: error processing archive /var/cache/apt/archives/bash_4.3-1_amd64.deb > (--unpack): > trying to overwrite '/usr/share/doc/bash/bash.html', which is also in > package bash-doc 4.2+dfsg-1 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)--- End Message ---
Bug#739032: marked as done (icedtea-web: FTBFS[kfreebsd-any]: sun.security.util.SecurityConstants not found)
Your message dated Wed, 05 Mar 2014 06:54:40 +0100 with message-id <5316bc20.5090...@debian.org> and subject line kfreebsd-* binaries for icedtea-web are removed has caused the Debian Bug report #739032, regarding icedtea-web: FTBFS[kfreebsd-any]: sun.security.util.SecurityConstants 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.) -- 739032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: icedtea-web Version: 1.4.2-1 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd icedtea-web builds with openjdk-7/7u25-2.3.12-4 but not 7u51-2.4.5-2; this seems to be a new portability issue in the JRE: configure:7339: checking if sun.security.util.SecurityConstants is available sun/applet/Test.java:4: warning: SecurityConstants is internal proprietary API and may be removed in a future release import sun.security.util.SecurityConstants; ^ 1 warning Exception in thread "main" java.lang.InternalError: sun.net.PortConfig: unknown OS at sun.net.PortConfig$1.run(PortConfig.java:59) at sun.net.PortConfig$1.run(PortConfig.java:45) at java.security.AccessController.doPrivileged(Native Method) at sun.net.PortConfig.(PortConfig.java:44) at java.net.SocketPermission$1.run(SocketPermission.java:1217) at java.net.SocketPermission$1.run(SocketPermission.java:1209) at java.security.AccessController.doPrivileged(Native Method) at java.net.SocketPermission.initEphemeralPorts(SocketPermission.java:1208) at java.net.SocketPermission.(SocketPermission.java:235) at sun.security.util.SecurityConstants.(SecurityConstants.java:259) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:190) at sun.applet.Test.main(Test.java:11) configure:7376: result: no configure:7383: error: sun.security.util.SecurityConstants not found. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- kfreebsd-* binaries for icedtea-web are removed--- End Message ---
Bug#737706: marked as done (Missing examples in python3 package)
Your message dated Wed, 05 Mar 2014 04:00:07 + with message-id and subject line Bug#737687: fixed in openslide-python 0.5.1-3 has caused the Debian Bug report #737687, regarding Missing examples in python3 package 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.) -- 737687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-openslide Severity: grave Version: 0.5.1-2 The package is missing the examples files. See python-openslide for completeness --- End Message --- --- Begin Message --- Source: openslide-python Source-Version: 0.5.1-3 We believe that the bug you reported is fixed in the latest version of openslide-python, 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 737...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated openslide-python 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Mar 2014 21:10:53 + Source: openslide-python Binary: python-openslide python3-openslide python-openslide-examples Architecture: source all Version: 0.5.1-3 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team Changed-By: Mathieu Malaterre Description: python-openslide - Python 2 wrapper for reading whole slide image files python-openslide-examples - Python examples for python-openslide and python3-openslide python3-openslide - Python 3 wrapper for reading whole slide image files Closes: 737687 737707 Changes: openslide-python (0.5.1-3) unstable; urgency=low . * As per upstream, need python 3.3. Closes: #737707 * Add a package to handle the duplicate examples situation. Closes: #737687 Checksums-Sha1: b48ffcacc49afeb1d4083251f80e2bcf05a71a46 2211 openslide-python_0.5.1-3.dsc 6e852e79d9889eadb1480ce42212e14f297008e6 3740 openslide-python_0.5.1-3.debian.tar.gz 9a6f23660b63ecfbca52bc51ef85cec1de720f52 12146 python-openslide_0.5.1-3_all.deb 80756ead54ea225fb005ce87c0e0476aa6046d18 11940 python3-openslide_0.5.1-3_all.deb b635089db01bfa5ca0592937a8d01cd6fd929c7a 139226 python-openslide-examples_0.5.1-3_all.deb Checksums-Sha256: 3846be9e389e8f54915bb7e9802f737f6d1a57d9538e070366cfd6d3bb369883 2211 openslide-python_0.5.1-3.dsc c2113970919ee543a1dd904a59133fd0e1c3584e17017d38d17e6e07e6feefc8 3740 openslide-python_0.5.1-3.debian.tar.gz eefa24db54c2d73604035b7fe4813f334a32c28a45e394655647373c528480f2 12146 python-openslide_0.5.1-3_all.deb a57dd1329c9fe34f86fcb994f3a6bb10c3216639225e7d2ca8993c1327f62715 11940 python3-openslide_0.5.1-3_all.deb af39fe4fe269a7987d7b9319653f8a3d176cd9df1ed83267f01c685fb0472faa 139226 python-openslide-examples_0.5.1-3_all.deb Files: c555d24c37a67fa52a9ee267f17e916a 2211 python optional openslide-python_0.5.1-3.dsc 293a456e305b485d4190c9bb6fa80404 3740 python optional openslide-python_0.5.1-3.debian.tar.gz d3f310debfd11e4658264fa60cd4af44 12146 python optional python-openslide_0.5.1-3_all.deb c42afed361920e0f96fbb3ac81636591 11940 python optional python3-openslide_0.5.1-3_all.deb 10a5d2b37f552544454bf7f7380f63c7 139226 python optional python-openslide-examples_0.5.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBAgAGBQJTFkafAAoJEAFx4YKK4JNF8PEP/A8jbt3zM7GQS/1jvwMG8FCX gSxOoMyZ3LnWtUxbApLNO+AEIQINcFmtHR8sEC0MRHUJrwqggAGwril9ocAY2hY2 cHAPXRwbIPLYwPhNkFW0/Enl9qUo87GLRYCK2ffWOn6OkmeHXXCyVcpJ6ONMLPEq DDZ3O8NXp26jxgGAI/wK1XtSWD7Dq7KLBFR4KMXuGlLkfEE2Kz4KqFo6NFHID07p F81rFqEsQAfBs8JT8/MDNwLnEjrn8ZFWpzT5ekVx3MklhXrbjKNq4G9Nn3jtMFWV l5oJedBl/bs53VQRCOhhIpTzyR0x0BxrTullunQeqjEzKXq7AJ1sqPKvuiGI20rJ oZQuM6OIT9WCz4X2PntwPt37/+/KPNpK+6pGwyHSyPpsrii7+TFFgDdjWWKW05dX uRXrTmxIYOMK4mizIhO6XohbHh4bZTBa/+6GlmapGRL9c9MV0jGWmLRmwUOym5O9 hIf0LKFI2mNseZC79HBaVQ6OKbSvZSPfJFGJKsnA3TjXq1SRQtMihDYEmEVfBml/ J9kOHzYn1nb98RtNJd1MCPbYFKw8vEYHDMfVxj6xn7i7Dg5syjPKNOsxCO4w9xh0 /v2deA/sWKaJooNoY2l6i3uyT/dM7V6uVyY6ezhJdJXZtmRUnIZ31r2zlh7od7N9 MQXXUSPXaWv9+E17YOPB =f+MA -END PGP SIGNATURE End Message ---
Bug#737687: marked as done (Examples missing from package)
Your message dated Wed, 05 Mar 2014 04:00:07 + with message-id and subject line Bug#737687: fixed in openslide-python 0.5.1-3 has caused the Debian Bug report #737687, regarding Examples missing from package 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.) -- 737687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-openslide Version: 0.5.1-2 python3-openslide Recommends packages needed by the examples (python3-flask and libjs-jquery) but doesn't actually ship the examples. --- End Message --- --- Begin Message --- Source: openslide-python Source-Version: 0.5.1-3 We believe that the bug you reported is fixed in the latest version of openslide-python, 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 737...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre (supplier of updated openslide-python 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Mar 2014 21:10:53 + Source: openslide-python Binary: python-openslide python3-openslide python-openslide-examples Architecture: source all Version: 0.5.1-3 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team Changed-By: Mathieu Malaterre Description: python-openslide - Python 2 wrapper for reading whole slide image files python-openslide-examples - Python examples for python-openslide and python3-openslide python3-openslide - Python 3 wrapper for reading whole slide image files Closes: 737687 737707 Changes: openslide-python (0.5.1-3) unstable; urgency=low . * As per upstream, need python 3.3. Closes: #737707 * Add a package to handle the duplicate examples situation. Closes: #737687 Checksums-Sha1: b48ffcacc49afeb1d4083251f80e2bcf05a71a46 2211 openslide-python_0.5.1-3.dsc 6e852e79d9889eadb1480ce42212e14f297008e6 3740 openslide-python_0.5.1-3.debian.tar.gz 9a6f23660b63ecfbca52bc51ef85cec1de720f52 12146 python-openslide_0.5.1-3_all.deb 80756ead54ea225fb005ce87c0e0476aa6046d18 11940 python3-openslide_0.5.1-3_all.deb b635089db01bfa5ca0592937a8d01cd6fd929c7a 139226 python-openslide-examples_0.5.1-3_all.deb Checksums-Sha256: 3846be9e389e8f54915bb7e9802f737f6d1a57d9538e070366cfd6d3bb369883 2211 openslide-python_0.5.1-3.dsc c2113970919ee543a1dd904a59133fd0e1c3584e17017d38d17e6e07e6feefc8 3740 openslide-python_0.5.1-3.debian.tar.gz eefa24db54c2d73604035b7fe4813f334a32c28a45e394655647373c528480f2 12146 python-openslide_0.5.1-3_all.deb a57dd1329c9fe34f86fcb994f3a6bb10c3216639225e7d2ca8993c1327f62715 11940 python3-openslide_0.5.1-3_all.deb af39fe4fe269a7987d7b9319653f8a3d176cd9df1ed83267f01c685fb0472faa 139226 python-openslide-examples_0.5.1-3_all.deb Files: c555d24c37a67fa52a9ee267f17e916a 2211 python optional openslide-python_0.5.1-3.dsc 293a456e305b485d4190c9bb6fa80404 3740 python optional openslide-python_0.5.1-3.debian.tar.gz d3f310debfd11e4658264fa60cd4af44 12146 python optional python-openslide_0.5.1-3_all.deb c42afed361920e0f96fbb3ac81636591 11940 python optional python3-openslide_0.5.1-3_all.deb 10a5d2b37f552544454bf7f7380f63c7 139226 python optional python-openslide-examples_0.5.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAEBAgAGBQJTFkafAAoJEAFx4YKK4JNF8PEP/A8jbt3zM7GQS/1jvwMG8FCX gSxOoMyZ3LnWtUxbApLNO+AEIQINcFmtHR8sEC0MRHUJrwqggAGwril9ocAY2hY2 cHAPXRwbIPLYwPhNkFW0/Enl9qUo87GLRYCK2ffWOn6OkmeHXXCyVcpJ6ONMLPEq DDZ3O8NXp26jxgGAI/wK1XtSWD7Dq7KLBFR4KMXuGlLkfEE2Kz4KqFo6NFHID07p F81rFqEsQAfBs8JT8/MDNwLnEjrn8ZFWpzT5ekVx3MklhXrbjKNq4G9Nn3jtMFWV l5oJedBl/bs53VQRCOhhIpTzyR0x0BxrTullunQeqjEzKXq7AJ1sqPKvuiGI20rJ oZQuM6OIT9WCz4X2PntwPt37/+/KPNpK+6pGwyHSyPpsrii7+TFFgDdjWWKW05dX uRXrTmxIYOMK4mizIhO6XohbHh4bZTBa/+6GlmapGRL9c9MV0jGWmLRmwUOym5O9 hIf0LKFI2mNseZC79HBaVQ6OKbSvZSPfJFGJKsnA3TjXq1SRQtMihDYEmEVfBml/ J9kOHzYn1nb98RtNJd1MCPbYFKw8vEYHDMfVxj6xn7i7Dg5syjPKNOsxCO4w9xh0 /v2deA/sWKaJooNoY2l6i3uyT/dM7V6uVyY6ezhJdJXZtmRUnIZ31r2zlh7od7N9 MQXXUSPXaWv9+E17YOPB =f+MA -END PGP SIGNATURE End Message ---
Processed: tagging 726370, found 726370 in 2.5.3.1-1, affects 726370
Processing commands for cont...@bugs.debian.org: > tags 726370 - moreinfo Bug #726370 [gphoto2] gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150. Removed tag(s) moreinfo. > found 726370 2.5.3.1-1 Bug #726370 [gphoto2] gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150. There is no source info for the package 'gphoto2' at version '2.5.3.1-1' with architecture '' Unable to make a source version for version '2.5.3.1-1' Marked as found in versions 2.5.3.1-1. > affects 726370 libgphoto2-6 Bug #726370 [gphoto2] gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150. Added indication that 726370 affects libgphoto2-6 > thanks Stopping processing here. Please contact me if you need assistance. -- 726370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726370 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#735898: pavucontrol segmentation fault
On 2014-03-04 16:08:15, Léo Cavaillé wrote: > The patch is on pavucontrol debian git, and I finished the packaging of > 2.0 version today, tomorrow I will upload pavucontrol 2.0-1 to the archive. That's great, thanks! Do you want me to remove the upload from DELAYED/2? It should be overriden by the 2.0 upload anyways... It's my first "real" NMU... :) A. -- La guerre, c'est le massacre d'hommes qui ne se connaissent pas, au profit d'hommes qui se connaissent mais ne se massacreront pas. - Paul Valéry pgp8izzGJFHbq.pgp Description: PGP signature
Bug#726370: gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150.
Package: gphoto2 Version: 2.4.14-1 Followup-For: Bug #726370 Control: tags -1 - moreinfo Control: found -1 2.5.3.1-1 Control: affects -1 libgphoto2-6 The problem is not actually with the gphoto2 binary package, but with the library, which is what darktable really uses. Case in point: i purged gphoto2 and darktable still starts (but I can reproduce the hang). So yes, the problem is still there in 2.5. I see this in my syslog: mars 04 20:07:13 marcos kernel: usb 5-2: new high-speed USB device number 29 using ehci-pci mars 04 20:07:13 marcos kernel: usb 5-2: New USB device found, idVendor=04a9, idProduct=320f mars 04 20:07:13 marcos kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 mars 04 20:07:13 marcos kernel: usb 5-2: Product: Canon Digital Camera mars 04 20:07:13 marcos kernel: usb 5-2: Manufacturer: Canon Inc. mars 04 20:07:13 marcos kernel: usb 5-2: SerialNumber: 0DA11DBB8DBD46FE9C4AF75C3A1A1BE7 mars 04 20:07:13 marcos mtp-probe[3975]: checking bus 5, device 29: "/sys/devices/pci:00/:00:1d.7/usb5/5-2" mars 04 20:07:13 marcos mtp-probe[3975]: bus: 5, device: 29 was not an MTP device mars 04 20:07:13 marcos colord[1548]: Device added: sysfs-Canon_Inc.-Canon_Digital_Camera mars 04 20:07:14 marcos org.gtk.Private.UDisks2VolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.UDisks2VolumeMonitor[16216]: ### debug: Name owner ':1.79' vanished mars 04 20:07:14 marcos org.gtk.Private.UDisks2VolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.GoaVolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.GoaVolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.GPhoto2VolumeMonitor[16216]: ### debug: emit_signal: 0x1be4370 mars 04 20:07:14 marcos org.gtk.Private.MTPVolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.MTPVolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.GPhoto2VolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.GPhoto2VolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.AfcVolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.AfcVolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.AfcVolumeMonitor[16216]: ### debug: Name owner ':1.80' vanished mars 04 20:07:14 marcos org.gtk.Private.GPhoto2VolumeMonitor[16216]: ### debug: Name owner ':1.80' vanished mars 04 20:07:14 marcos org.gtk.Private.GoaVolumeMonitor[16216]: ### debug: Name owner ':1.80' vanished mars 04 20:07:14 marcos org.gtk.Private.MTPVolumeMonitor[16216]: ### debug: Name owner ':1.80' vanished mars 04 20:07:14 marcos org.gtk.Private.UDisks2VolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.UDisks2VolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.GoaVolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.GoaVolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.MTPVolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.MTPVolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.GPhoto2VolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.GPhoto2VolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.AfcVolumeMonitor[16216]: ### debug: in handle_supported mars 04 20:07:14 marcos org.gtk.Private.AfcVolumeMonitor[16216]: ### debug: in handle_list mars 04 20:07:14 marcos org.gtk.Private.GPhoto2VolumeMonitor[16216]: ### debug: Name owner ':1.84' vanished mars 04 20:07:14 marcos org.gtk.Private.AfcVolumeMonitor[16216]: ### debug: Name owner ':1.84' vanished mars 04 20:07:14 marcos org.gtk.Private.MTPVolumeMonitor[16216]: ### debug: Name owner ':1.84' vanished mars 04 20:07:14 marcos org.gtk.Private.GoaVolumeMonitor[16216]: ### debug: Name owner ':1.84' vanished mars 04 20:07:14 marcos org.gtk.Private.UDisks2VolumeMonitor[16216]: ### debug: Name owner ':1.84' vanished Notice how this is not a Nikon D300 but a Canon G12, so I suspect the problem is not only related with a single machine. Furthermore, this was working fine in Debian Wheezy, so I am not sure at all the problem is in gphoto 2.4, if anything it's in 2.5 or darktable... Let me know if I test this in any other way. A. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740505: marked as done (burp: Burp is casting pointer to 64-bit value into a pointer to a 32-bit value)
Your message dated Tue, 04 Mar 2014 22:33:32 + with message-id and subject line Bug#740505: fixed in burp 1.3.48-2 has caused the Debian Bug report #740505, regarding burp: Burp is casting pointer to 64-bit value into a pointer to a 32-bit value 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.) -- 740505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: burp Version: 1.3.48-1 Severity: important Dear Maintainer, Burp is casting pointer to 64-bit value into a pointer to a 32-bit value the causing that burp the build of burp is failing on 64-bit big endian platform like s390x see: http://paste.debian.net/84821/ Burp is casting pointer to 64-bit value into a pointer to a 32-bit value For example in in handy.c, line 570 if(!EVP_CipherFinal_ex(enc_ctx, eoutbuf, (int *)&eoutlen)) eoutlen is size_t Thanks to Aurelien to help indentify the problem. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages burp depends on: ii libacl1 2.2.52-1 ii libc62.17-97 ii libgcc1 1:4.8.2-14 ii libncurses5 5.9+20140118-1 ii librsync10.9.7-10 ii libssl1.0.0 1.0.1f-1 ii libstdc++6 4.8.2-14 ii libtinfo55.9+20140118-1 ii zlib1g 1:1.2.8.dfsg-1 burp recommends no packages. burp suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: burp Source-Version: 1.3.48-2 We believe that the bug you reported is fixed in the latest version of burp, 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 740...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastiaan Franciscus van den Dikkenberg (supplier of updated burp 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Mar 2014 15:54:28 +0100 Source: burp Binary: burp burp-dbg Architecture: source amd64 Version: 1.3.48-2 Distribution: unstable Urgency: low Maintainer: Bastiaan Franciscus van den Dikkenberg Changed-By: Bastiaan Franciscus van den Dikkenberg Description: burp - Simple cross-platform network BackUp and Restore Program burp-dbg - debugging symbols for Burp Closes: 740505 740547 Changes: burp (1.3.48-2) unstable; urgency=low . * Add patch to fix pointer casting in src/msg.c:transfer_gzfile_in to fix FTBFS on 64-bit big-endian architectures (Closes: #740505): - debian/patches/endian.patch * Replace debian/patches/disable_tests.patch with debian/patches/fixskiptest, so that only test 6 and 7 are skipped when there is no PRNG available. * Add patch for the test function wait_for_backup_to_finish to check for the existance of /var/spool/burp/testclient/lockfile instead of the symlinks /var/spool/burp/testclient/{working,finishing} (Closes: #740547): - debian/patches/wait_for_backup_to_finish.patch * Now using autoreconf for better portability: - Change dh $@ to dh $@ --with autoreconf in debian/rules file. - Add dependency on dh-autoreconf in debian/control. * Change dh_verbose to 1 to solve compiler-flags-hidden warnings in debian/rules file. * Remove obsolete overrides in rules file: - override_dh_auto_install - override_dh_install - override_dh_installdocs * Using dh_auto_configure instead of just running ./configure with the following options in debian/rules: - prefix /usr - sysconfdir /etc/burp - sbindir $${prefix}/sbin - mandir $${prefix}/share/man - C/CPP/LD flags uses exported build flags * Add debian/burp.install and debian/burp.dirs. Checksums-Sha1: 419262081c873dde93762d935f36a4da8b6e62db 1983 burp_1.3.48-2.dsc ca3cd489f6ee843771858f9aae26877209851473 683509 burp_1.3.48.orig.tar.bz2 b6df07c5b8aad949899df2a6b4b
Bug#736740: marked as done ([src:letodms] Sourceless file)
Your message dated Tue, 04 Mar 2014 21:21:40 + with message-id and subject line Bug#736740: fixed in letodms 3.3.11+dfsg.1-1 has caused the Debian Bug report #736740, regarding [src:letodms] Sourceless file 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.) -- 736740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: letodms Version:3.3.11+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: letodms 3.3.11+dfsg-2 (source) js/jquery.min.js Bastien --- End Message --- --- Begin Message --- Source: letodms Source-Version: 3.3.11+dfsg.1-1 We believe that the bug you reported is fixed in the latest version of letodms, 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 736...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francisco Manuel Garcia Claramonte (supplier of updated letodms 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Mar 2014 11:16:42 +0100 Source: letodms Binary: letodms Architecture: source all Version: 3.3.11+dfsg.1-1 Distribution: unstable Urgency: low Maintainer: Francisco Manuel Garcia Claramonte Changed-By: Francisco Manuel Garcia Claramonte Description: letodms- document management system based on PHP and MySQL Closes: 669826 718759 720992 720993 732867 736740 Changes: letodms (3.3.11+dfsg.1-1) unstable; urgency=low . * Added MariaDB as alternative to dependences list. (Closes: #732867) * Removed js/jquery.min.js from Debian source package. It is a sourceless file. Created new +dfsg.1 source Debian package, (Closes: #736740) * Added patch to upate Russian translation. Thanks to Sergey Alyoshin for the patch. (Closes: #720993) * Added patchs to fix some messages in English translation and php script. Thanks to Sergey Alyoshin for the patch (Closes: #720992) * Updated README.Debian file. * Updated to debian policy 3.9.5. * Updated copyright file, repackaged upstream source description. * Updated for transition to apache 2.4. (Closes: #669826) + Updated depends and recommends to apache2 in debian/control (Closes: #718759) + Renamed apache2 config file to letodms.conf + Renamed old apache.conf (for localhost url) to apache.local.conf + Removed debian/letodms.links file. + Changed debian/letodms-postinst. Use apache2-maintscript-helper to enable letodms site. Checksums-Sha1: e96e776e1d5dbea3670b807827685dacedd35d67 1089 letodms_3.3.11+dfsg.1-1.dsc 104484658eedfe2c7b4e57a9c2aa6952542ac4fe 410290 letodms_3.3.11+dfsg.1.orig.tar.gz d05c4f4cbd415bd4c54e97a8096416dd04746b10 50814 letodms_3.3.11+dfsg.1-1.debian.tar.gz 670b3e3ebf1ae37052b5d00448a386098b639b09 419238 letodms_3.3.11+dfsg.1-1_all.deb Checksums-Sha256: 4491fa3f7785a60668766a7ce950b1cd09443f777b88637764cb5b03ee284e4e 1089 letodms_3.3.11+dfsg.1-1.dsc 831db3257606e01d7cf8b40ecd0df74bafabca4ae225a0c4227f5bc80f0ce094 410290 letodms_3.3.11+dfsg.1.orig.tar.gz 7ef559042b4cc0b807847652323f1498302eec744fbb1751826b53c595a6013f 50814 letodms_3.3.11+dfsg.1-1.debian.tar.gz 83689d6d540e9d9b57db714ec6a84bd16b108c1444d52b52e38fd9f3fecc84a0 419238 letodms_3.3.11+dfsg.1-1_all.deb Files: b28c0ae3ee436b44149808de609f5437 1089 web optional letodms_3.3.11+dfsg.1-1.dsc 2d5507f6c90d90452b61a2ac579f490c 410290 web optional letodms_3.3.11+dfsg.1.orig.tar.gz dccf56b997a5f81de3e4ee3e4965ee88 50814 web optional letodms_3.3.11+dfsg.1-1.debian.tar.gz 87d57a852844d8386ad810743be3b6d2 419238 web optional letodms_3.3.11+dfsg.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlMWKCMACgkQmpU8glVqulGvewCfVYLeBFW+Xygkj44XBQBNEAMK uZQAnj28Nq+FsFgkSHGL8T9LQPqAa0Fz =mXVG -END PGP SIGNATURE End Message ---
Bug#735898: pavucontrol segmentation fault
On 03/04/2014 06:32 AM, Antoine Beaupré wrote: Package: pavucontrol Followup-For: Bug #735898 Control: tags -1 pending I'll upload this patch shortly (NMU, 2 days delay), since it seems to fix the problem and pavucontrol is threatened by autoremoval. Hi Antoine, The patch is on pavucontrol debian git, and I finished the packaging of 2.0 version today, tomorrow I will upload pavucontrol 2.0-1 to the archive. Thanks for your help, Cheers, -- Léo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: src:petsc: FTBFS on s390x: libscalapack-mpich2 unusable
Processing control commands: > block -1 by 740620 Bug #740765 [src:petsc] src:petsc: FTBFS on s390x: libscalapack-mpich2 unusable 740765 was not blocked by any bugs. 740765 was not blocking any bugs. Added blocking bug(s) of 740765: 740620 -- 740765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740765 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#740765: src:petsc: FTBFS on s390x: libscalapack-mpich2 unusable
Package: src:petsc Version: 3.4.2.dfsg1-7 Severity: serious Control: block -1 by 740620 petsc FTBFS on s390x. This is essentially due to the MPICH2->MPICH3 transition, which broke scalapack on s390x. See #740620 for more details. Once scalapack is fixed, a sourceful upload of petsc will be needed which includes commit a904239. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: Digital signature
Processed: Re: Bug#740620: nmu: scalapack_1.8.0-9
Processing control commands: > reassign -1 src:scalapack 1.8.0-9 Bug #740620 [release.debian.org] nmu: scalapack_1.8.0-9 Bug reassigned from package 'release.debian.org' to 'src:scalapack'. Ignoring request to alter found versions of bug #740620 to the same values previously set Ignoring request to alter fixed versions of bug #740620 to the same values previously set Bug #740620 [src:scalapack] nmu: scalapack_1.8.0-9 Marked as found in versions scalapack/1.8.0-9. > severity -1 serious Bug #740620 [src:scalapack] nmu: scalapack_1.8.0-9 Severity set to 'serious' from 'normal' > retitle -1 scalapack: should not silently change the library SONAME when MPI > implementation changes Bug #740620 [src:scalapack] nmu: scalapack_1.8.0-9 Changed Bug title to 'scalapack: should not silently change the library SONAME when MPI implementation changes' from 'nmu: scalapack_1.8.0-9' > clone -1 -2 Bug #740620 [src:scalapack] scalapack: should not silently change the library SONAME when MPI implementation changes Bug 740620 cloned as bug 740764 > reassign -2 src:blacs-mpi 1.1-31.1 Bug #740764 [src:scalapack] scalapack: should not silently change the library SONAME when MPI implementation changes Bug reassigned from package 'src:scalapack' to 'src:blacs-mpi'. No longer marked as found in versions scalapack/1.8.0-9. Ignoring request to alter fixed versions of bug #740764 to the same values previously set Bug #740764 [src:blacs-mpi] scalapack: should not silently change the library SONAME when MPI implementation changes Marked as found in versions blacs-mpi/1.1-31.1. > retitle -2 blacs-mpi: should not silently change the library SONAME when MPI > implementation changes Bug #740764 [src:blacs-mpi] scalapack: should not silently change the library SONAME when MPI implementation changes Changed Bug title to 'blacs-mpi: should not silently change the library SONAME when MPI implementation changes' from 'scalapack: should not silently change the library SONAME when MPI implementation changes' -- 740620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740620 740764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740764 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#740491: nfs-common: fails to upgrade (action "restart" failed)
Package: nfs-common Followup-For: Bug #740491 I've had this happen on two machines I've upgrade so far. It turns out that you get an error (sorry, didn't copy down the exact message) when you try to run: rpcinfo -d status 1 to un-register the service. On a third machine, I ran that *beofore* upgrading and also stopped nfs-common, and that avoided the problem. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: block 708350 with 739032 739927
Processing commands for cont...@bugs.debian.org: > block 708350 with 739032 739927 Bug #708350 [release.debian.org] transition: java7 708350 was not blocked by any bugs. 708350 was not blocking any bugs. Added blocking bug(s) of 708350: 739927 and 739032 > thanks Stopping processing here. Please contact me if you need assistance. -- 708350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: unarchiving rm bugs
Processing commands for cont...@bugs.debian.org: > unarchive 669831 Bug #669831 {Done: Debian FTP Masters } [mantis] mantis: transition towards Apache 2.4 Unarchived Bug 669831 > unarchive 679213 Bug #679213 {Done: Debian FTP Masters } [mantis] Installation fails without apache2 Bug #722245 {Done: Debian FTP Masters } [mantis] mantis: unable to install mantis if apache isn't installed Unarchived Bug 679213 Unarchived Bug 722245 > unarchive 689638 Bug #689638 {Done: Debian FTP Masters } [mantis] mantis: target version not available as a filter Unarchived Bug 689638 > unarchive 689639 Bug #689639 {Done: Debian FTP Masters } [mantis] mantis: dynamic filters broken Unarchived Bug 689639 > unarchive 689640 Bug #689640 {Done: Debian FTP Masters } [mantis] mantis: custom fields do not show in search results Unarchived Bug 689640 > unarchive 693339 Bug #693339 {Done: Debian FTP Masters } [mantis] mantis: [INTL:ja] New Japanese translation Unarchived Bug 693339 > unarchive 695730 Bug #695730 {Done: Debian FTP Masters } [mantis] mantis: Requests missing sound.js, causes 404 error Unarchived Bug 695730 > unarchive 698481 Bug #698481 {Done: Debian FTP Masters } [mantis] mantis: multiple XSS vulnerabilities CVE-2013-0197, CVE-2013-1810, CVE-2013-1811 Unarchived Bug 698481 > unarchive 717482 Bug #717482 {Done: Debian FTP Masters } [mantis] mantis: CVE-2013-1934: XSS issue in adm_config_report.php when displaying complex value Unarchived Bug 717482 > unarchive 723200 Bug #723200 {Done: Debian FTP Masters } [mantis] mantis install.php creates database user with wrong permissions Unarchived Bug 723200 > unarchive 727180 Bug #727180 {Done: Debian FTP Masters } [mantis] mantis: CVE-2013-4460: XSS in account_sponsor_page.php project names Unarchived Bug 727180 > unarchive 727783 Bug #727783 {Done: Debian FTP Masters } [mantis] [mantis] E: Internal Error, No file name for mantis:i386 Unarchived Bug 727783 > unarchive 727787 Bug #727787 {Done: Debian FTP Masters } [mantis] [mantis] Install fail Unarchived Bug 727787 > unarchive 729474 Bug #729474 {Done: Debian FTP Masters } [mantis] mantis: default conf allows directory listing Unarchived Bug 729474 > thanks Stopping processing here. Please contact me if you need assistance. -- 669831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669831 679213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679213 689638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689638 689639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689639 689640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689640 693339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693339 695730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695730 698481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698481 717482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717482 722245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722245 723200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723200 727180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727180 727783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727783 727787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727787 729474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729474 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#732651: marked as done (Please remove t1lib dependency)
Your message dated Tue, 04 Mar 2014 17:04:51 + with message-id and subject line Bug#732651: fixed in swftools 0.9.2+git20130725-2 has caused the Debian Bug report #732651, regarding Please remove t1lib 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.) -- 732651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: swftools Severity: serious Hi, t1lib is slated to be removed (in favor of freetype) before wheezy ships [0],[1]. This package is currently one of its reverse dependencies. Please convert the package to use freetype. [0] http://bugs.debian.org/637488 [1] http://bugs.debian.org/637040 Cheers, Moritz --- End Message --- --- Begin Message --- Source: swftools Source-Version: 0.9.2+git20130725-2 We believe that the bug you reported is fixed in the latest version of swftools, 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 732...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Welzel (supplier of updated swftools 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Mar 2014 09:00:00 +0100 Source: swftools Binary: swftools swftools-dbg Architecture: source amd64 Version: 0.9.2+git20130725-2 Distribution: unstable Urgency: low Maintainer: Christian Welzel Changed-By: Christian Welzel Description: swftools - Collection of utilities for SWF file manipulation/creation swftools-dbg - Collection of utilities for SWF file manipulation/creation (debug Closes: 732651 Changes: swftools (0.9.2+git20130725-2) unstable; urgency=low . * Removed build dependency on libt1-dev. (Closes: 732651) * Bump Standards Version to 3.9.5. * Added debian/gbp.conf. Checksums-Sha1: 3297b1b981c20078641077886c868c0745f03b92 2054 swftools_0.9.2+git20130725-2.dsc a8a6bbcb29c26a08e44fbe2f21fb49e0d415dc6f 13148 swftools_0.9.2+git20130725-2.debian.tar.xz 9515ebcd8cfebae5c0e8bac1844061a5eabb8637 845556 swftools_0.9.2+git20130725-2_amd64.deb 3b79eef15bce4b58a13ad36b2b70e274f6643458 1776684 swftools-dbg_0.9.2+git20130725-2_amd64.deb Checksums-Sha256: ecd2a1229f0569d2d3f28ec9abe6cecbef5f132a0c301bbea11dee38fedd4f8f 2054 swftools_0.9.2+git20130725-2.dsc 985af0f0c8073a712625c46e1c77c78a6d557cfbc06e873c14e3c2a84712f0c4 13148 swftools_0.9.2+git20130725-2.debian.tar.xz f7835462b6c6baf00764ef520b8e7462432c883e369c1d1c6ccd3de44b180262 845556 swftools_0.9.2+git20130725-2_amd64.deb 1dd25318c955def036a81b27dff84e1b2217525be6fb7d99f01ad0ea6b8e5e71 1776684 swftools-dbg_0.9.2+git20130725-2_amd64.deb Files: 6be78c76a0481123839493f435b6afb9 2054 utils extra swftools_0.9.2+git20130725-2.dsc e67affb82e138301ce3f7ee5a19dc804 13148 utils extra swftools_0.9.2+git20130725-2.debian.tar.xz 0250e0122bdaa3e074f47fcc2e9a07a0 845556 utils extra swftools_0.9.2+git20130725-2_amd64.deb 5f3392657bd2a076197c5cb583167ce2 1776684 debug extra swftools-dbg_0.9.2+git20130725-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTFgYaAAoJEBDCk7bDfE426KAQALOowRQbM2Cxd6rUMlT2SGax SVSGoKLVruH20TCyp6JonXhPRwbLrSsIhZzbW8r/qQsaZB2vKEGcZc5uilWVXdhN ijK0aMZrlScwtKCVyxPultUgwlKa4/9VFKuOaKSihYG57obhoDF10dcpVD4HHo1Q O7V1RBb8bSc2Mi+23WeBcFpwq2OcqkPrb4shfjpnv45CbOJph/9h04QNh6Jiy5aw FOtHK5KgMKNDFHHzKUM4NziXe6oZt9u8ozO52VZnkIQuJDbdaRHrOcc8l9Esk8T9 QKn3h6hCRq0qzrRMQr5vEFEpypjIj/Spy/FGFnA1HWm4eTl611Pc9fvMTr+3MupK sDJcZdUr6PX34OJW0EvmqYFa/f4OEaa44ds5pPn12rwgnpqVrZHL1b+kAWr8za5u cM/ML+fsfIYFiVQ8y/eoZ5EsfVwCxjjy1xntIAc/tonstUyu1P9lJjyECPXnnaiW EfCsWa4ad4tKBOnQ91mNpJN3bAQ3D30aJLUsccqj7jZcbR+ejpsOUjZc46fpqGOy uGBpf3IOSKsvRQcefny96EQ8I8gnZM+c6DtfwwS6xmptFZ7B41b38KQHaWxbrBhv YyJkGY4p2P47gzNhXdMlt5FTgmiM3TQfPo4OXlOzdrQ9/aY1Kp41wGARx0kRxKjz 9AkMky1FH8Pja29ydXji =OAr1 -END PGP SIGNATURE End Message ---
Bug#738435: marked as done (taskcoach: FTBFS: Tests failed)
Your message dated Tue, 04 Mar 2014 16:20:45 + with message-id and subject line Bug#738435: fixed in taskcoach 1.3.36-1 has caused the Debian Bug report #738435, regarding taskcoach: FTBFS: Tests 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.) -- 738435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: taskcoach Version: 1.3.35-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140208 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > == > ERROR: testSaveSelection_Child (integrationtests.SaveTest.SaveTest) > -- > Traceback (most recent call last): > File "/«PKGBUILDDIR»/tests_tmp/integrationtests/SaveTest.py", line 27, in > setUp > self.mockApp = mock.App() > File "/«PKGBUILDDIR»/taskcoachlib/patterns/singleton.py", line 29, in > __call__ > class_.instance = super(Singleton, class_).__call__(*args, **kwargs) > File "/«PKGBUILDDIR»/tests_tmp/integrationtests/mock.py", line 48, in > __init__ > self.init() > File "/«PKGBUILDDIR»/tests_tmp/integrationtests/mock.py", line 52, in init > super(App, self).init(loadSettings=False, loadTaskFile=False) > File "/«PKGBUILDDIR»/taskcoachlib/application/application.py", line 190, in > init > self.settings, splash=splash) > File "/«PKGBUILDDIR»/taskcoachlib/gui/mainwindow.py", line 69, in __init__ > self._create_window_components() # Not private for test purposes > File "/«PKGBUILDDIR»/taskcoachlib/gui/mainwindow.py", line 128, in > _create_window_components > self.__create_menu_bar() > File "/«PKGBUILDDIR»/taskcoachlib/gui/mainwindow.py", line 142, in > __create_menu_bar > self.viewer, self.taskFile)) > File "/«PKGBUILDDIR»/taskcoachlib/gui/menu.py", line 216, in __init__ > viewerContainer), _('&New')), > File "/«PKGBUILDDIR»/taskcoachlib/gui/menu.py", line 554, in __init__ > TaskTemplateMenu(mainwindow, taskList=tasks, settings=settings), > File "/«PKGBUILDDIR»/taskcoachlib/gui/menu.py", line 328, in __init__ > super(TaskTemplateMenu, self).__init__(mainwindow) > File "/«PKGBUILDDIR»/taskcoachlib/gui/menu.py", line 99, in __init__ > self.updateMenu() > File "/«PKGBUILDDIR»/taskcoachlib/gui/menu.py", line 133, in updateMenu > self.updateMenuItems() > File "/«PKGBUILDDIR»/taskcoachlib/gui/menu.py", line 338, in updateMenuItems > self.fillMenu(self.getUICommands()) > File "/«PKGBUILDDIR»/taskcoachlib/gui/menu.py", line 347, in getUICommands > settings=self.settings) for name in > persistence.TemplateList(path).names()] > File "/«PKGBUILDDIR»/taskcoachlib/persistence/templatelist.py", line 27, in > __init__ > self._templates = self._readTemplates(TemplateReader, openFile) > File "/«PKGBUILDDIR»/taskcoachlib/persistence/templatelist.py", line 32, in > _readTemplates > for filename in self._templateFilenames(): > File "/«PKGBUILDDIR»/taskcoachlib/persistence/templatelist.py", line 51, in > _templateFilenames > filenames = [name for name in os.listdir(self._path) if \ > OSError: [Errno 2] No such file or directory: > '/sbuild-nonexistent/.TaskCoach/taskcoach-templates' > > == > ERROR: testSaveSelection_Parent (integrationtests.SaveTest.SaveTest) > -- > Traceback (most recent call last): > File "/«PKGBUILDDIR»/tests_tmp/integrationtests/SaveTest.py", line 27, in > setUp > self.mockApp = mock.App() > File "/«PKGBUILDDIR»/taskcoachlib/patterns/singleton.py", line 29, in > __call__ > class_.instance = super(Singleton, class_).__call__(*args, **kwargs) > File "/«PKGBUILDDIR»/tests_tmp/integrationtests/mock.py", line 48, in > __init__ > self.init() > File "/«PKGBUILDDIR»/tests_tmp/integrationtests/mock.py", line 52, in init > super(App, self).init(loadSettings=False, loadTaskFile=False) > File "/«PKGBUILDDIR»/taskcoachlib/application/application.py", line 190, in > init > self.settings, splash=splash) > File "/«PKGBUILDDIR»/taskcoachlib/gui/mainwindow.py", line 69, in __init__ > self._create_window_components() # Not private for test purposes > File "/«PKGBUILDDIR»/taskcoachlib/gui/mainwindow.py", line 128, in > _create_
Bug#705109: Workaround for failing slapd upgrade (Lenny -> Squeeze)
Hi all, a few weeks ago I was bitten by this bug as well. I found a way to work around the described slapd upgrade failure. In Squeeze 6.0.1 the upgrade scripts worked as expected. Therefor I used an old repository from http://snapshot.debian.org/ to upgrade from Lenny to Squeeze 6.0.1: $ echo "deb http://snapshot.debian.org/archive/debian/20110616T030927Z/ squeeze main" > /etc/apt/sources.list $ apt-get update $ apt-get install apt aptitude dpkg $ apt-get dist-upgrade This dist-upgrade worked like a charm. Afterwards I changed my sources.list to something like "http.debian.net" and upgraded to current Squeeze release. I thought this could be of interest for someone else. Best regards Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736765: my experience with i915kms, newcons and k-11
Em 2014-02-27 20:26, Robert Millan escreveu: On 27/02/2014 23:25, Robert Millan wrote: On 27/02/2014 18:25, Christoph Egger wrote: On Sun, Feb 23, 2014 at 11:44:35AM -0300, brunomaxi...@openmailbox.org wrote: but, any input (mouse, touchpad, keyboard) doesn't work, so I can't log in. This is happening with you guys or just me? Any idea? Thanks, Happens for me since xserver 1.15 or something (very recent update in jessie). I don't have any input working in any way (kfreebsd 9.2 or 9.3) with slim. I'll try to allocate some time to fix that but can't promise anything currently. Probably HAL-related. xserver 1.15 works fine with the devd patch, I tested that version just a few days ago. Here's the most recent version. Also needs the Debian bits from: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736765#47 When that patch will be applied in the package? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735438: marked as done (quickfix: FTBFS on mips, but previously built there)
Your message dated Tue, 04 Mar 2014 15:40:23 + with message-id and subject line Bug#735438: fixed in quickfix 1.13.3+dfsg-7 has caused the Debian Bug report #735438, regarding quickfix: FTBFS on mips, but previously built there 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.) -- 735438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: quickfix Version: 1.13.3+dfsg-6 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Your package "quickfix" previously got built on mips, but the latest upload to build there. Excerpt from the buildd log: > make[4]: Entering directory `/«BUILDDIR»/quickfix-1.13.3+dfsg/src/python' /bin/sh ../../libtool --tag=CXX --mode=compile /usr/bin/g++ -DHAVE_CONFIG_H -I. -I../.. -I. -I.. -I../.. -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Werror=format-security -O3 -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include/libxml2 -I/usr/include/python2.7 -I/usr/include/mips-linux-gnu/python2.7 -fPIC -DPIC -MT QuickfixPython.lo -MD -MP -MF .deps/QuickfixPython.Tpo -c -o QuickfixPython.lo QuickfixPython.cpp libtool: compile: /usr/bin/g++ -DHAVE_CONFIG_H -I. -I../.. -I. -I.. -I../.. -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Werror=format-security -O3 -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include/libxml2 -I/usr/include/python2.7 -I/usr/include/mips-linux-gnu/python2.7 -fPIC -DPIC -MT QuickfixPython.lo -MD -MP -MF .deps/QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o .libs/QuickfixPython.o g++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See for instructions. make[4]: *** [QuickfixPython.lo] Error 1 make[4]: Leaving directory `/«BUILDDIR»/quickfix-1.13.3+dfsg/src/python' < In a previous build run: > make[4]: Entering directory `/«BUILDDIR»/quickfix-1.13.3+dfsg/src/python' /bin/sh ../../libtool --tag=CXX --mode=compile /usr/bin/g++ -DHAVE_CONFIG_H -I. -I../.. -I. -I.. -I../.. -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Werror=format-security -O3 -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include/libxml2 -I/usr/include/python2.7 -I/usr/include/mips-linux-gnu/python2.7 -fPIC -DPIC -MT QuickfixPython.lo -MD -MP -MF .deps/QuickfixPython.Tpo -c -o QuickfixPython.lo QuickfixPython.cpp libtool: compile: /usr/bin/g++ -DHAVE_CONFIG_H -I. -I../.. -I. -I.. -I../.. -D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Werror=format-security -O3 -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include/libxml2 -I/usr/include/python2.7 -I/usr/include/mips-linux-gnu/python2.7 -fPIC -DPIC -MT QuickfixPython.lo -MD -MP -MF .deps/QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o .libs/QuickfixPython.o as: out of memory allocating 4072 bytes after a total of 1995243520 bytes /tmp/ccKZKuWC.s: Assembler messages: /tmp/ccKZKuWC.s: Fatal error: can't close .libs/QuickfixPython.o: Memory exhausted make[4]: *** [QuickfixPython.lo] Error 1 make[4]: Leaving directory `/«BUILDDIR»/quickfix-1.13.3+dfsg/src/python' < Maybe it would be a good idea to split QuickfixPython.cpp into multiple files. Thank you, Christian --- End Message --- --- Begin Message --- Source: quickfix Source-Version: 1.13.3+dfsg-7 We believe that the bug you reported is fixed in the latest version of quickfix, 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 735...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roberto C. Sanchez (supplier of updated quickfix 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Mar 2014 08:44:50 -0500 Source: quickfix Binary: libquickfix-dev libquickfix14 libquickfix14-dbg libquickfix-doc Architecture: source all amd64 Version: 1.13.3+dfsg-7 Distribution: unstable Urgency: low Maintainer: Athena Capital Research Changed-By: Roberto C. Sanchez Description: libquickfix-dev - FIX protocol library - development files libquickfix-doc - FIX protocol library - documentation libquickfix14 - FIX protocol library - runtime files
Bug#733456: marked as done (contextfree: FTBFS on mips/mipsel/sparc and m68k/sh4: undefined reference to `__sync_bool_compare_and_swap_8')
Your message dated Tue, 04 Mar 2014 15:34:04 + with message-id and subject line Bug#733456: fixed in contextfree 3.0.5+dfsg1-2.1 has caused the Debian Bug report #733456, regarding contextfree: FTBFS on mips/mipsel/sparc and m68k/sh4: undefined reference to `__sync_bool_compare_and_swap_8' 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.) -- 733456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: contextfree Version: 3.0.5+dfsg1-2 Severity: serious Tags: upstream patch Justification: fails to build from source (but built successfully in the past) contextfree fails to build on mips/mipsel/sparc and m68k/sh4 with the following error message: | cc -Wl,-z,relro objs/cfdg.o objs/Rand64.o objs/makeCFfilename.o objs/cfdgimpl.o objs/renderimpl.o objs/builder.o objs/shape.o objs/variation.o objs/countable.o objs/tempfile.o objs/aggCanvas.o objs/HSBColor.o objs/SVGCanvas.o objs/primShape.o objs/bounds.o objs/shapeSTL.o objs/tiledCanvas.o objs/astexpression.o objs/astreplacement.o objs/pathIterator.o objs/stacktype.o objs/CmdInfo.o objs/abstractPngCanvas.o objs/ast.o objs/ffCanvasDummy.o objs/pngCanvas.o objs/posixSystem.o objs/main.o objs/posixTimer.o objs/posixVersion.o objs/lex.yy.o objs/cfdg.tab.o objs/agg_trans_affine.o objs/agg_curves.o objs/agg_vcgen_contour.o objs/agg_vcgen_stroke.o objs/agg_bezier_arc.o objs/agg_color_rgba.o -Lsrc-ffmpeg/lib -L/usr/local/lib -lstdc++ -lpng -lm -fexceptions -o cfdg | objs/posixSystem.o: In function `PosixSystem::tempFileForWrite(std::string&)': | /«BUILDDIR»/contextfree-3.0.5+dfsg1/src-unix/posixSystem.cpp:126: warning: the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp' | objs/astreplacement.o: In function `AST::ASTcompiledPath::NextPathUID()': | /«BUILDDIR»/contextfree-3.0.5+dfsg1/src-common/astreplacement.cpp:952: undefined reference to `__sync_fetch_and_add_8' | /«BUILDDIR»/contextfree-3.0.5+dfsg1/src-common/astreplacement.cpp:952: undefined reference to `__sync_fetch_and_add_8' | /«BUILDDIR»/contextfree-3.0.5+dfsg1/src-common/astreplacement.cpp:952: undefined reference to `__sync_fetch_and_add_8' | objs/CmdInfo.o: In function `AST::CommandInfo::tryInit(unsigned int, AST::ASTcompiledPath*, double, AST::ASTpathCommand const*)': | /«BUILDDIR»/contextfree-3.0.5+dfsg1/src-common/CmdInfo.cpp:61: undefined reference to `__sync_bool_compare_and_swap_8' | collect2: error: ld returned 1 exit status The problem is that the new version of contextfree try to uses 64-bit GCC legacy atomic builtins [1], which are not all available on all architectures. The solution to this problem is to use the new GCC atomics, similar to the C11 ones [2]. For that you need GCC 4.8, which is unfortunately not the default on all architectures, and to link with libatomic. The later library provides a fallback implementation if a given atomic bultin is not available natively, which is usually the case for 64-bit atomics on 32-bit platforms. The patch below implements that and should fix the problem, though I have only tested it on mips so far. --- contextfree-3.0.5+dfsg1/debian/control +++ contextfree-3.0.5+dfsg1/debian/control @@ -3,7 +3,7 @@ Priority: extra Maintainer: Bram Senders Uploaders: Paul van Tilburg -Build-Depends: debhelper (>= 9), flex, bison, libpng-dev +Build-Depends: debhelper (>= 9), flex, bison, libpng-dev, g++-4.8 Standards-Version: 3.9.5 Homepage: http://contextfreeart.org/ --- contextfree-3.0.5+dfsg1/debian/patches/04-gcc-4.8-atomic.patch +++ contextfree-3.0.5+dfsg1/debian/patches/04-gcc-4.8-atomic.patch @@ -0,0 +1,36 @@ +--- a/Makefile b/Makefile +@@ -45,7 +45,7 @@ + AGG_SRCS = agg_trans_affine.cpp agg_curves.cpp agg_vcgen_contour.cpp \ + agg_vcgen_stroke.cpp agg_bezier_arc.cpp agg_color_rgba.cpp + +-LIBS = stdc++ png m ++LIBS = stdc++ png m atomic + + # + # FFmpeg support +--- a/src-common/CmdInfo.cpp b/src-common/CmdInfo.cpp +@@ -58,7 +58,10 @@ + (__int64)(std::numeric_limits::max()), + (__int64)0) == (__int64)(std::numeric_limits::max())) + #else +-if (__sync_bool_compare_and_swap(&mPathUID, std::numeric_limits::max(), (UIDtype)0)) ++const UIDtype expected = std::numeric_limits::max(); ++const UIDtype desired = 0; ++if (__atomic_compare_exchange(&mPathUID, &expected, &desired, ++ false, __ATOMIC_SEQ_CST, __ATOMIC_SEQ_CST)) + #endif + init(i, path, w, c); + } +-
Bug#740614: marked as done (glance: does not handle requests after installation)
Your message dated Tue, 04 Mar 2014 23:25:42 +0800 with message-id <5315f076.7000...@goirand.fr> and subject line Closing, as per discussion has caused the Debian Bug report #740614, regarding glance: does not handle requests after installation 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.) -- 740614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glance Version: 2013.2.2-2 Severity: serious Justification: renders package unusable Hi, After installing glance, I get the following errors in the log: 2014-03-03 16:11:23.179 17528 WARNING glance.store.base [-] Failed to configure store correctly: Store sheepdog could not be configured correctly. Reason: Error in store configuration: Unexpected error while running command. Command: collie Exit code: 127 Stdout: '' Stderr: '/bin/sh: 1: collie: not found\n' Disabling add method. 2014-03-03 16:11:23.202 17528 WARNING glance.store.base [-] Failed to configure store correctly: Store cinder could not be configured correctly. Reason: Cinder storage requires a context. Disabling add method. 2014-03-03 16:11:23.448 17528 WARNING keystoneclient.middleware.auth_token [-] Configuring auth_uri to point to the public identity endpoint is required; clients may not be able to authenticate against an admin endpoint Installing sheepdog fixes the first warning. installing python-cinderclient apparently fixes the second warning. Configuring auth_uri in glance-api.conf fixes the third one: [keystone_authtoken] auth_host = 127.0.0.1 auth_port = 35357 auth_protocol = http auth_uri = http://127.0.0.1:35357 Lucas -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages glance depends on: ii dpkg 1.17.6 ii glance-api 2013.2.2-2 ii glance-registry 2013.2.2-2 glance recommends no packages. Versions of packages glance suggests: pn python-ceph -- no debconf information --- End Message --- --- Begin Message --- Closing, as per discussion--- End Message ---
Bug#740614: [PKG-Openstack-devel] Bug#740614: Bug#740614: glance: does not handle requests after installation
On 03/04/2014 07:55 PM, Lucas Nussbaum wrote: > On 04/03/14 at 19:22 +0800, Thomas Goirand wrote: >> On 03/04/2014 12:28 AM, Lucas Nussbaum wrote: >>> Package: glance >>> Version: 2013.2.2-2 >>> Severity: serious >>> Justification: renders package unusable >>> >>> Hi, >>> >>> After installing glance, I get the following errors in the log: >>> 2014-03-03 16:11:23.179 17528 WARNING glance.store.base [-] Failed to >>> configure store correctly: Store sheepdog could not be configured >>> correctly. Reason: Error in store configuration: Unexpected error while >>> running command. >>> Command: collie >>> Exit code: 127 >>> Stdout: '' >>> Stderr: '/bin/sh: 1: collie: not found\n' Disabling add method. >>> 2014-03-03 16:11:23.202 17528 WARNING glance.store.base [-] Failed to >>> configure store correctly: Store cinder could not be configured correctly. >>> Reason: Cinder storage requires a context. Disabling add method. >>> 2014-03-03 16:11:23.448 17528 WARNING keystoneclient.middleware.auth_token >>> [-] Configuring auth_uri to point to the public identity endpoint is >>> required; clients may not be able to authenticate against an admin endpoint >>> >>> Installing sheepdog fixes the first warning. >>> >>> installing python-cinderclient apparently fixes the second warning. >>> >>> Configuring auth_uri in glance-api.conf fixes the third one: >>> [keystone_authtoken] >>> auth_host = 127.0.0.1 >>> auth_port = 35357 >>> auth_protocol = http >>> auth_uri = http://127.0.0.1:35357 >>> >> If I understand well, you've been able to fix everything. How come then >> it's a "serious" issue that makes "package unusable"? > > because without additional tweaking, the package doesn't work at all? It does work for me. Also, I find it very weird that you are suggesting auth_uri isn't good by default, because by default (I've just checked), there's no such directive at all shipped by the package. The default in the package is (located in /usr/share/glance-common): [keystone_authtoken] auth_host = 127.0.0.1 auth_port = 35357 auth_protocol = http admin_tenant_name = %SERVICE_TENANT_NAME% admin_user = %SERVICE_USER% admin_password = %SERVICE_PASSWORD% This is the exact copy of the upstream configuration file btw. As you can see, there's no such thing as "auth_uri" (which would otherwise override auth_host, auth_port and auth_protocol). Also, in what you have pasted, it seems to be missing the admin tenant information. Probably you should just purge glance-common and reinstall it to make sure it's configured correctly (there's debconf prompts to do that...). I'm therefore closing the bug. Feel free to discuss the issue more though, if you still think there's a problem in the packaging. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740730: fcitx-mozc: input method doesn't load with GTK2 frontend
Package: fcitx-mozc Version: 1.13.1651.102-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgraded fcitx-mozc along with mozc-server and dependencies from 1.12.1599.102 to 1.13.1651.102-2. However, the problem was already present in 1.13.1651.102-1. * What was the outcome of this action? The input method was expected to become active. * What outcome did you expect instead? The input didn't activate at all. Furthermore, the problem appears only with the GTK2 front-end. The GTK3, Qt4, Qt5 front-ends work flawlessly. Also, in GTK2 the input method is not registered at all as it doesn't appear in the context menu on GTK2 text entries (right click -> Input Methods lists only "Simple" and "None" with "Simple" selected as the default). I think that the severity setting is justified because core productivity applications like Iceweasel still rely on GTK2. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-5.dmz.2-liquorix-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fcitx-mozc depends on: ii fcitx-bin 1:4.2.8.3-2+b1 ii fcitx-data 1:4.2.8.3-2 ii fcitx-modules 1:4.2.8.3-2+b1 ii libc6 2.18-4 ii libprotobuf82.5.0-9 ii libstdc++6 4.8.2-16 ii mozc-data 1.12.1599.102-1 ii mozc-server 1.13.1651.102-2 ii tegaki-zinnia-japanese 0.3-1 Versions of packages fcitx-mozc recommends: ii fcitx 1:4.2.8.3-2 ii mozc-utils-gui 1.13.1651.102-2 fcitx-mozc 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: Adjust severity for installation-reports bugs
Processing commands for cont...@bugs.debian.org: > severity 706649 important Bug #706649 [installation-reports] installation-report: the partitioner ignores preexisting windows7 partitions Severity set to 'important' from 'critical' > severity 731720 important Bug #731720 [installation-reports] installation-reports: Debian Wheezy installer damages partition table Severity set to 'important' from 'critical' > severity 732656 important Bug #732656 [installation-reports] installation-reports: modprobe -l command in hw-config script fails Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 706649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706649 731720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731720 732656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732656 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#733556: Ok I think someone has this issue backwards.
* Peter Dolding , 2014-03-04, 13:11: wine should not be run as root. There is no wrapper on binfmt_misc to make it fail in case of a .exe on root. Why should such a protection be implemented in the wrapped rather than in wine itself? Reason why wine should not run as root. Wine can run Windows viruses very effectively. Huh. /bin/sh can run Linux malware very effectively. Does it mean that we shouldn't let users run #!/bin/sh scripts as root?! Number 2 WINEPREFIX settings. Direct running by binfmt_misc cannot tell that X application in fact owns to alternative WINEPREFIX. Wine does not use extended Xattr to declare WINEPREFIX ownership on .exe files. No idea what you're talking about here. Really I would like to hear the real-world examples that require this feature. Like Mathieu, I've been using this feature to ease cross-compiling. Basically the broken state is a good time to patch up a security issue. Please explain why do you think that this is a security issue: ./foo.exe but this is not: wine foo.exe Anyway, if Debian wine maintainers decide that this feature is no longer desirable, then: 1) It should be documented in NEWS.Debian; 2) The /usr/bin/wine-auto interpreter should be properly removed from the binfmt-support database. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722035: switch from ffgtk to roger
> Roger Router has been finalized and I'm not waiting for sponsorship so s/not/now/ On 04.03.2014 18:08, Andreas Henriksson wrote: > fwiw, I'm personally not interested in sponsoring anything that > doesn't give users a (best effort?) upgrade path. I wasn't aware you're actually in a position to sponsor. And I hope that my usual sponsors will help me with roger. FWIW, I'm not even sure what you mean with "best effort upgrade path" or what's missing to get there. In any case, there isn't really an upgrade happening as such since the two packages can actually happily coexist on the same system. It's simply that ffgtk is dead upstream and the development efforts there are now solely focused on roger. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734241: init/upstart script problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Apologies Looks like bug mail is just not getting through to the maintainer ML. I'll look to fix this for the next upload I do for the firefly release. Cheers James - -- James Page Ubuntu and Debian Developer james.p...@ubuntu.com jamesp...@debian.org -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFcS/AAoJEL/srsug59jDfxYP/0iaiVo4wCjLIOHU0+fNF5zb NGjundn/ePad/b84ftul/Dw833wc5aBNvHG6pBzQ+g9eF4YLIhHzbFlNRnf+SmXp de9LjsCNg10i/QpTywIocx2Iy8czRbHx8fRTjpOQFYARViazoeYNDiuyTOHo/oQh BGZdE8sCA2gWHuGBd8TcKdi+aZhbLxWqn/9eB4TtmTkzvwoggVEKHyhUr+isQfZm rt8DeaenhWLtmcI/sD/baVJbSIDGuKy4o/8V21p13rchQOVYpaBNM77zzOhFMQV2 fYvv0ZWt9QPjjpp/xgwmDUwBRhn8RfZOU3UzGi0MJPjodthhmb4gxA/qWNRpPFdr /hVyOp+l29jghJp7nwVo0qMOVXMnGGmeYPekQVi0BWo8OTHom1lU53I8T97GnXBb Ly6ITjRU9P3tZ5IO5DkIS+FyRWgccSi/CNJSm3JTpB+LWuH4D2zkaTGNsN8YcFXt XceuFuX7/+EZGjbD8wbkHGagb8oeL5pV52ANPf5lHXEz6+ybUe4AwzqTWFmv6pU/ 99AvDzklJy1iBRMWzu//Gau/MfgE/wEbQlZGZRxrTxAkZ5FoAdxbVXfIaw2eSkks IKbwzCRH9Neq062pa5TcBYASO26v7eUxvxIvvBb6KU427IZgzkpYdVPRW4OdqpIr obZKWeT6+yf/lksXyrYS =rJ4o -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740614: [PKG-Openstack-devel] Bug#740614: glance: does not handle requests after installation
On 04/03/14 at 19:22 +0800, Thomas Goirand wrote: > On 03/04/2014 12:28 AM, Lucas Nussbaum wrote: > > Package: glance > > Version: 2013.2.2-2 > > Severity: serious > > Justification: renders package unusable > > > > Hi, > > > > After installing glance, I get the following errors in the log: > > 2014-03-03 16:11:23.179 17528 WARNING glance.store.base [-] Failed to > > configure store correctly: Store sheepdog could not be configured > > correctly. Reason: Error in store configuration: Unexpected error while > > running command. > > Command: collie > > Exit code: 127 > > Stdout: '' > > Stderr: '/bin/sh: 1: collie: not found\n' Disabling add method. > > 2014-03-03 16:11:23.202 17528 WARNING glance.store.base [-] Failed to > > configure store correctly: Store cinder could not be configured correctly. > > Reason: Cinder storage requires a context. Disabling add method. > > 2014-03-03 16:11:23.448 17528 WARNING keystoneclient.middleware.auth_token > > [-] Configuring auth_uri to point to the public identity endpoint is > > required; clients may not be able to authenticate against an admin endpoint > > > > Installing sheepdog fixes the first warning. > > > > installing python-cinderclient apparently fixes the second warning. > > > > Configuring auth_uri in glance-api.conf fixes the third one: > > [keystone_authtoken] > > auth_host = 127.0.0.1 > > auth_port = 35357 > > auth_protocol = http > > auth_uri = http://127.0.0.1:35357 > > > > > > Lucas > > Hi Lucas, > > If I understand well, you've been able to fix everything. How come then > it's a "serious" issue that makes "package unusable"? because without additional tweaking, the package doesn't work at all? > Also, this seems related to using sheepdog, which I never used. I'm > convince that the default setup of Glance (using keystone and the local > file-based store) works out of the box, and we've been using RDB (using > Ceph) without issue. > > It looks like to me that the only thing we should fix is add > python-cinderclient as dependency, and completely removing the auth_uri > parameter of the default config file (so that other directives are in > use by default). > > Your thoughts? > > I'll be waiting for more input from you, I don't have enough openstack knowledge to provide valuable input: I'm just reporting that by default it doesn't work. Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740614: [PKG-Openstack-devel] Bug#740614: glance: does not handle requests after installation
On 03/04/2014 12:28 AM, Lucas Nussbaum wrote: > Package: glance > Version: 2013.2.2-2 > Severity: serious > Justification: renders package unusable > > Hi, > > After installing glance, I get the following errors in the log: > 2014-03-03 16:11:23.179 17528 WARNING glance.store.base [-] Failed to > configure store correctly: Store sheepdog could not be configured correctly. > Reason: Error in store configuration: Unexpected error while running command. > Command: collie > Exit code: 127 > Stdout: '' > Stderr: '/bin/sh: 1: collie: not found\n' Disabling add method. > 2014-03-03 16:11:23.202 17528 WARNING glance.store.base [-] Failed to > configure store correctly: Store cinder could not be configured correctly. > Reason: Cinder storage requires a context. Disabling add method. > 2014-03-03 16:11:23.448 17528 WARNING keystoneclient.middleware.auth_token > [-] Configuring auth_uri to point to the public identity endpoint is > required; clients may not be able to authenticate against an admin endpoint > > Installing sheepdog fixes the first warning. > > installing python-cinderclient apparently fixes the second warning. > > Configuring auth_uri in glance-api.conf fixes the third one: > [keystone_authtoken] > auth_host = 127.0.0.1 > auth_port = 35357 > auth_protocol = http > auth_uri = http://127.0.0.1:35357 > > > Lucas Hi Lucas, If I understand well, you've been able to fix everything. How come then it's a "serious" issue that makes "package unusable"? Also, this seems related to using sheepdog, which I never used. I'm convince that the default setup of Glance (using keystone and the local file-based store) works out of the box, and we've been using RDB (using Ceph) without issue. It looks like to me that the only thing we should fix is add python-cinderclient as dependency, and completely removing the auth_uri parameter of the default config file (so that other directives are in use by default). Your thoughts? I'll be waiting for more input from you, Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733352: Bowtie and tophat fail to build with seqan >= 1.4
Hi David, On Tue, Mar 04, 2014 at 11:17:21AM +0100, Weese, David wrote: > > > Ognyan Kulev promised a patch for bowie > > Ok, can you please paste my last mail (with the instructions) at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733398 to help him. I'm pretty sure that Ognyan is aware of the information since he was responding to the bug report. (I also add the address of the tophat bug to keep others informed.) > >> - seems to be const problem > >> - the constructor of a seqan::Gaps<..., Alloc> was called with a const > >> String and requires a non-const String > >> - from just the error report I can't say how to fix it > > > > Would a full build log which is more verbose than > > > > https://bugs.debian.org/733352 > > > > help to create a patch? > > > > Not really. What I need is to reproduce your exact build environment to > reproduce the exact error and provide a patch. The exact build environment can be createt quite easily on a Debian (or also Ubuntu machine). You create a pbuilder environment via pbuilder --create sid fetch the package source apt-get source tophat cd to the unpacked dir and say pdebuild Which builds the package inside the pbuilder chroot. If you need more detailed information I'd be happy to providvide it. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722035: switch from ffgtk to roger
Hello Rolf! Thanks for working on ffgtk/roger! On Tue, Mar 04, 2014 at 05:33:00PM +0800, Rolf Leggewie wrote: > On 04.03.2014 17:17, Rolf Leggewie wrote: > > the successor to ffgtk is called Roger Router. > > Well, I forgot to mention the most important bit; the packaging for > Roger Router has been finalized and I'm not waiting for sponsorship so > that the new package can land in NEW. Thanks, I was a bit lost reading your initial mail. :) > > https://mentors.debian.net/package/roger-router > http://mentors.debian.net/debian/pool/main/r/roger-router/roger-router_1.8.4-1.dsc > http://bugs.debian.org/739845 (ITP) > > I expect ffgtk will be removed from Debian unstable. I'd prefer to have > that happen after the replacement has landed. fwiw, I'm personally not interested in sponsoring anything that doesn't give users a (best effort?) upgrade path. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724148: marked as done (libpthread-workqueue: FTBFS: make[1]: *** No rule to make target `config.mk'. Stop.)
Your message dated Tue, 04 Mar 2014 09:44:36 + with message-id and subject line Bug#724148: fixed in libpthread-workqueue 0.9-1 has caused the Debian Bug report #724148, regarding libpthread-workqueue: FTBFS: make[1]: *** No rule to make target `config.mk'. Stop. 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.) -- 724148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpthread-workqueue Version: 0.8.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > CFLAGS="" LDADD="-lpthread" dh clean >dh_testdir >dh_auto_clean > make[1]: Entering directory `/«PKGBUILDDIR»' > Makefile:22: config.mk: No such file or directory > make[1]: *** No rule to make target `config.mk'. Stop. > make[1]: Leaving directory `/«PKGBUILDDIR»' > dh_auto_clean: make -j1 distclean returned exit code 2 > make: *** [clean] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/libpthread-workqueue_0.8.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: libpthread-workqueue Source-Version: 0.9-1 We believe that the bug you reported is fixed in the latest version of libpthread-workqueue, 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 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Heily (supplier of updated libpthread-workqueue 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Mar 2014 13:05:09 -0500 Source: libpthread-workqueue Binary: libpthread-workqueue-dev libpthread-workqueue0 Architecture: source amd64 Version: 0.9-1 Distribution: unstable Urgency: low Maintainer: Mark Heily Changed-By: Mark Heily Description: libpthread-workqueue-dev - thread pool library (development files) libpthread-workqueue0 - thread pool library Closes: 724148 Changes: libpthread-workqueue (0.9-1) unstable; urgency=low . * New upstream version * Switch to using GNU autotools. (Closes: #724148) Checksums-Sha1: 63c933544e10b4d9712a14b1730f4afa26d6a5c7 1980 libpthread-workqueue_0.9-1.dsc ba2da9164f35c45dc7170972f7cf129cb0b84ca5 87 libpthread-workqueue_0.9.orig.tar.gz ac8faa0bb8dabcee3088cccbe4d45b61b3646f63 2744 libpthread-workqueue_0.9-1.debian.tar.xz 7463282f53a7d3ac0007cf3c48dfd1618a11ee12 9078 libpthread-workqueue-dev_0.9-1_amd64.deb fca5b1a8b218111af82986afd299ace970966fc0 14966 libpthread-workqueue0_0.9-1_amd64.deb Checksums-Sha256: b856c37455f79ee2ce24b34258a6399d4c0bc8593be1514dd6e8bea03ae4796e 1980 libpthread-workqueue_0.9-1.dsc 847b8b963cdd3a66dadb460697113d34c855fe973fa00f54574ee10505752b28 87 libpthread-workqueue_0.9.orig.tar.gz 0932db0f05b063cc40d7b0c50be6fde3d5b42a1967bb86505ee8d5136b72147d 2744 libpthread-workqueue_0.9-1.debian.tar.xz cfe306968eb88c85a1101b5ab9757e524ee6069a0bc0c666d16c865816ce2fce 9078 libpthread-workqueue-dev_0.9-1_amd64.deb 07aa0b63f9108cc74cda5371c8fe5a1e15264b8ca7b27cb31be2e70a81dcdb43 14966 libpthread-workqueue0_0.9-1_amd64.deb Files: e101f792f4c1ed60998507f0e19c9c46 1980 libs extra libpthread-workqueue_0.9-1.dsc 02aa7ec80c6aab139d19b79762e6f693 87 libs extra libpthread-workqueue_0.9.orig.tar.gz d196f65d6975adeba1b4d303cb3ffbb4 2744 libs extra libpthread-workqueue_0.9-1.debian.tar.xz 955e8653f86e5e2620e6c51d66d4655f 9078 libdevel extra libpthread-workqueue-dev_0.9-1_amd64.deb 9fd24e6b84a0cb678e81de9bcfcbc738 14966 libs extra libpthread-workqueue0_0.9-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Lin
Bug#722035: switch from ffgtk to roger
On 04.03.2014 17:17, Rolf Leggewie wrote: > the successor to ffgtk is called Roger Router. Well, I forgot to mention the most important bit; the packaging for Roger Router has been finalized and I'm not waiting for sponsorship so that the new package can land in NEW. https://mentors.debian.net/package/roger-router http://mentors.debian.net/debian/pool/main/r/roger-router/roger-router_1.8.4-1.dsc http://bugs.debian.org/739845 (ITP) I expect ffgtk will be removed from Debian unstable. I'd prefer to have that happen after the replacement has landed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722035: switch from ffgtk to roger
Hello Andreas, the successor to ffgtk is called Roger Router. Upstream is the same but treats the two projects as completely separate so there is no "upgrade path" as such. Configuration is fairly simple, though, so I don't see much of a problem here. And apparently configuration stored on the router itself will get imported, so it's not lost. http://en.tabos.org/forum/viewtopic.php?f=7&t=878 (in German) Feel free to contact me with any concerns or suggestions you may have. Regards Rolf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732651: Please remove t1lib dependency
Hi Moritz, > nothing needs to be done except dropping the build-dep on libt1-dev. I uploaded a new version to m.d.n: http://mentors.debian.net/debian/pool/main/s/swftools/swftools_0.9.2+git20130725-2.dsc I cannot upload as i am no DD or DM for this package, so please upload it for me. -- MfG, Christian Welzel GPG-Key: pub 4096R/5117E119 2011-09-19 Fingerprint: 3688 337C 0D3E 3725 94EC E401 8D52 CDE9 5117 E119 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737511: no new version bug
Hi Bastian, On Tue, Mar 4, 2014 at 9:21 AM, Bastian Blank wrote: > On Mon, Mar 03, 2014 at 06:10:16PM +0100, Janos Guljas wrote: >> Could you confirm that the buffer corruption is *NOT* fixed in the new >> upstream release 2.0.2 as it handles the offset parameter? > > Wrong question. The bug did not _ask_ for a new upstream version. This > is the only occurance you may close a bug this way. Everything else > looks like you closed them by error. No bugs were closed by error, that is a false statement and malicious assumption. > > There were maintainers that closed bugs en-bulk this way because they did > not want to read them. New upstream release did fix this issue, which is marked in the changelog as such. There were no "en-bulk" bugs closed, especially not unread ones. > > The bug-fix was shipped as part of the new release, so add a new line > stating _what_ was fixed. > > Bastian Thank you for you contribution, Janos -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740696: bash: Uninstallable, file /usr/share/doc/bash/bash.html in both bash and bash-doc
Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/doc/bash/bash.html /usr/share/doc/bash/bashref.html -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733556: Ok I think someone has this issue backwards.
On Tue, Mar 4, 2014 at 4:11 AM, Peter Dolding wrote: > Basically as far as the main wine project knows no end user has an use > for binfmt_misc loading .exe files. So to them its one of those > bright spark ideas by package makers without any consideration to > security. I do. >From my cmake build system setup, a test is simply a command line application returning EXIT_SUCCESS / EXIT_FAILED. $ cmake --help-command add_test [...] add_test(NAME testname COMMAND Exename arg1 arg2 ... ) [...] Therefore I'd like to be able to use binfmt_misc just like any other qemu-* (+binfmt_misc) simulated environment. Steps (within the *same* machine, thanks to recent multiarch wine32/64 setup): $ cat bla.c int main() { return 0; } $ i586-mingw32msvc-gcc -o bla.exe bla.c $ export WINEPREFIX=~/wine32 $ ./bla.exe && echo "ok" ok $ x86_64-w64-mingw32-gcc -o bla2.exe bla.c $ export WINEPREFIX=~/wine64 $./bla2.exe && echo "ok" ok This works very well for me and I like it this way, I can run cross compilation + test executions targeting wine 32bits *and* 64bits . This machine is a compilation machine, I have no issues with security concerns. 2cts -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737511: no new version bug
On Mon, Mar 03, 2014 at 06:10:16PM +0100, Janos Guljas wrote: > Could you confirm that the buffer corruption is *NOT* fixed in the new > upstream release 2.0.2 as it handles the offset parameter? Wrong question. The bug did not _ask_ for a new upstream version. This is the only occurance you may close a bug this way. Everything else looks like you closed them by error. There were maintainers that closed bugs en-bulk this way because they did not want to read them. The bug-fix was shipped as part of the new release, so add a new line stating _what_ was fixed. Bastian -- Bastian Blank Berater Durchwahl: +49 2161 / 4643-194 credativ GmbH, HRB Mönchengladbach 12080 Zentrale: +49 2161 / 4643-0 Hohenzollernstr. 133 Fax: +49 2161 / 4643-100 D-41061 Mönchengladbach www: http://www.credativ.de Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731009: marked as done (xmlstarlet: FTBFS on mips: java.lang.IllegalArgumentException: Invalid profile data)
Your message dated Tue, 4 Mar 2014 19:02:03 +1100 with message-id <20140304080203.ga28...@master.debian.org> and subject line Re: xmlstarlet: FTBFS on mips: java.lang.IllegalArgumentException: Invalid profile data has caused the Debian Bug report #731009, regarding xmlstarlet: FTBFS on mips: java.lang.IllegalArgumentException: Invalid profile data 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.) -- 731009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xmlstarlet Version: 1.5.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, xmlstarlet FTBFS on mips: https://buildd.debian.org/status/fetch.php?pkg=xmlstarlet&arch=mips&ver=1.5.0-1&stamp=1382959110 gawk -f ./usage2c.awk src/validate-usage.txt > src/validate-usage.c gcc -DHAVE_CONFIG_H -I. -I/usr/include -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 -Wall -pedantic -ansi -g -O2 -Wformat -Werror=format-security -c -o src/validate-usage.o src/validate-usage.c gcc -Wall -pedantic -ansi -g -O2 -Wformat -Werror=format-security -L/usr/lib -L/usr/lib -Wl,-z,relro -Wl,-z,now -o xml src/trans.o src/xml.o src/xml_C14N.o src/xml_depyx.o src/xml_edit.o src/xml_elem.o src/xml_escape.o src/xml_format.o src/xml_ls.o src/xml_pyx.o src/xml_select.o src/xml_trans.o src/xml_validate.o src/usage.o src/c14n-usage.o src/depyx-usage.o src/edit-usage.o src/elem-usage.o src/escape-usage.o src/format-usage.o src/ls-usage.o src/pyx-usage.o src/select-usage.o src/trans-usage.o src/unescape-usage.o src/validate-usage.o -lexslt -lxslt -lxml2 /usr/bin/xsltproc --stringparam VERSION '1.5.0' --stringparam PROG "`echo xml | /bin/sed 's/xml$/xmlstarlet/'`" ./doc/replace-PROG-VERSION.xsl doc/xmlstarlet-man.xml | /usr/bin/xsltproc -o doc/xmlstarlet.1 \ /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl \ - Note: Writing xmlstarlet.1 /usr/bin/xsltproc --stringparam VERSION '1.5.0' --stringparam PROG "`echo xml | /bin/sed 's/xml$/xmlstarlet/'`" ./doc/replace-PROG-VERSION.xsl doc/xmlstarlet-ug.xml | /usr/bin/xsltproc --param section.autolabel 1 --stringparam generate.toc 'book toc,title' ./doc/xmlstar-fodoc-style.xsl - > doc/xmlstarlet-ug.fo Making portrait pages on USletter paper (8.5inx11in) /usr/bin/fop -q doc/xmlstarlet-ug.fo doc/xmlstarlet-ug.pdf Exception java.lang.IllegalArgumentException: Invalid profile data make[2]: *** [doc/xmlstarlet-ug.pdf] Error 1 rm doc/xmlstarlet-ug.fo make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: *** [all] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 Andreas --- End Message --- --- Begin Message --- On Mon, Dec 30, 2013 at 07:15:25PM +, Jurica Stanojkovic wrote: > Hello, > > This issue is resolved with new version of openjdk-6_6b29-1.13.0-1 > > This was issue with lcms (1) used with previous version of openjdk-6 > (6b27-1.12.7-2) New version of openjdk-6 is using lcms2. > > I am sending, as attachment, log of successful build for this package > with openjdk-6_6b29-1.13.0-1 > > If needed, I will provide additional info. > > Could you please trigger rebuild (give back) this package. > > Thanks! > Jurica Thank you Jurica! signature.asc Description: Digital signature --- End Message ---