Bug#743855: marked as done (projectl ftbfs after the gdc update in 4.8.2-19)
Your message dated Mon, 21 Apr 2014 05:48:23 + with message-id and subject line Bug#743855: fixed in projectl 1.001.dfsg1-7 has caused the Debian Bug report #743855, regarding projectl ftbfs after the gdc update in 4.8.2-19 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.) -- 743855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: projectl Version: 1.001.dfsg1-6 Severity: serious Tags sid jessie [...] cc1d: warning: command line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for D src/util/parts.d:635: error: multiple field maxParts initialization make[2]: *** [projectl] Error 1 --- End Message --- --- Begin Message --- Source: projectl Source-Version: 1.001.dfsg1-7 We believe that the bug you reported is fixed in the latest version of projectl, 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 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Miriam Ruiz (supplier of updated projectl 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: Mon, 21 Apr 2014 07:05:22 +0200 Source: projectl Binary: projectl Architecture: source amd64 Version: 1.001.dfsg1-7 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Miriam Ruiz Description: projectl - sword action shooting Closes: 743855 Changes: projectl (1.001.dfsg1-7) unstable; urgency=medium . * Fixed ftbfs after the gdc update in 4.8.2-19. Closes: #743855 * Upgraded Standards-Version from 3.9.4 to 3.9.6 * Changed my email address to mir...@debian.org Checksums-Sha1: fa7dd583299faf5e3550d2dcf8aabb005a2f1679 1528 projectl_1.001.dfsg1-7.dsc a48cf9d8a4565a94e1c872a91e168b5687ca3fe6 32564 projectl_1.001.dfsg1-7.debian.tar.xz 45142f9032c5a45df71cc57847ce72f093014462 512380 projectl_1.001.dfsg1-7_amd64.deb Checksums-Sha256: 4d4f0c7ca488ab1d3f8e68c5a50a22ba83bc68e07acd2ecedd3971cdccddb068 1528 projectl_1.001.dfsg1-7.dsc 0d72e7fd80bace8ee0dbe55d9e7d975858b77899c58af973587499498fea790b 32564 projectl_1.001.dfsg1-7.debian.tar.xz fbd46c7017fc3f6ba4eb5811dcca99c2eeaecbdc8a4452e8e32dfd303286 512380 projectl_1.001.dfsg1-7_amd64.deb Files: ec1bd5497cd2e3b0ba81c9199084bb87 1528 games optional projectl_1.001.dfsg1-7.dsc eb7bb7cf99f50bec3b66773e1f8a6943 32564 games optional projectl_1.001.dfsg1-7.debian.tar.xz b04d418b4dc2c5fafec34ab9582310d1 512380 games optional projectl_1.001.dfsg1-7_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNUrkcACgkQfbltLjbuCGE4LQCdGl9gzZje1126++JZAMMz3m7g AmAAoJP601YNXhXFTXGYX+EjIRxlo7al =recU -END PGP SIGNATURE End Message ---
Bug#744943: ruby-sass: Cannot load sass/script/node
On Sun, 20 Apr 2014 12:56:30 Jonas Smedegaard wrote: > Bug arguably is at both packages (but I maintain both, so no need for > further BTS ping-pong): Sorry, I didn't check who maintain those packages. My intention was merely to assign bug to the right package. My impression is that the problem is in "ruby-sass" package because updating it broke "ruby-compass" which (unlike "ruby-sass") was not updated recently. > I suspect this problem to be caused not by changes to ruby-sass code (it > was upgraded), but instead to change of default Ruby version. > > I guess this could be solved by a simple binNMU of ruby-compass. I re-built "ruby-compass" in "unstable" but it did not fix the problem. > Also there is a new major release of Compass that I want to > upgrade to - i.e. my plan is to do a source-full release instead and > expect that to magically solve this issue. I also hope that new upstream release of "ruby-compass" will fix the problem. Until then we're stuck with broken `compass` unfortunately... -- Regards, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 745243 + pending Bug #745243 [python-dugong] s3ql: FTBFS on kfreebsd Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 745243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745243 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#745243: (no subject)
reassign 745243 python-dugong thanks The build actually works fine. The unit tests fail, but this is because the python3-dugong package is not kFreeBSD compatible. -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 745243 python-dugong Bug #745243 [s3ql] s3ql: FTBFS on kfreebsd Bug reassigned from package 's3ql' to 'python-dugong'. No longer marked as found in versions s3ql/2.8.1+dfsg-1. Ignoring request to alter fixed versions of bug #745243 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 745243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745243 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: As usual, I forgot to CC control before.
Processing commands for cont...@bugs.debian.org: > reassign 745233 libgmp10 Bug #745233 [libhogweed2] libhogweed2: should have versioned depend on newer libgmp10 Bug reassigned from package 'libhogweed2' to 'libgmp10'. No longer marked as found in versions nettle/2.7.1-2. Ignoring request to alter fixed versions of bug #745233 to the same values previously set > retitle 745233 libgmp10: Wrong shlibs information after 6.0.0 adds new symbols Bug #745233 [libgmp10] libhogweed2: should have versioned depend on newer libgmp10 Changed Bug title to 'libgmp10: Wrong shlibs information after 6.0.0 adds new symbols' from 'libhogweed2: should have versioned depend on newer libgmp10' > affects 745233 libhogweed2 Bug #745233 [libgmp10] libgmp10: Wrong shlibs information after 6.0.0 adds new symbols Added indication that 745233 affects libhogweed2 > -- Stopping processing here. Please contact me if you need assistance. -- 745233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745233 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: limit source to haxe, tagging 736596
Processing commands for cont...@bugs.debian.org: > #haxe (1:3.1.3+repack-1) unstable; urgency=medium > # > # * Regenerate js file from source (Closes: #736596). > # > limit source haxe Limiting to bugs with field 'source' containing at least one of 'haxe' Limit currently set to 'source':'haxe' > tags 736596 + pending Bug #736596 [src:haxe] [src:haxe] Sourceless file Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 736596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736596 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#740744: marked as done (dns323-firmware-tools: Please migrate to Ruby 2.0/2.1)
Your message dated Sun, 20 Apr 2014 21:34:36 + with message-id and subject line Bug#740744: fixed in dns323-firmware-tools 0.6-2 has caused the Debian Bug report #740744, regarding dns323-firmware-tools: Please migrate to Ruby 2.0/2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 740744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dns323-firmware-tools Version: 0.5-1 Severity: normal Dear Maintainer, your package "dns323-firmware-tools" explicitly depends on ruby1.9.1. As per the Debian Ruby team bits, all versions of Ruby < 2.1 will be removed from jessie. Please test your package with Ruby 2.0 and 2.1, and then switch the Depends: line to read "ruby" instead of "ruby1.9.1". Important changes from 1.9 to 2.0: - location of ruby/config.h has changed; it's location is now available from: ruby -r rbconfig -e "print RbConfig::CONFIG['rubyarchhdrdir']" - path for binary extensions has changed; it's location is now available from: ruby -r rbconfig -e "print RbConfig::CONFIG['vendorarchdir']" Thank you, Christian -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- --- End Message --- --- Begin Message --- Source: dns323-firmware-tools Source-Version: 0.6-2 We believe that the bug you reported is fixed in the latest version of dns323-firmware-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 740...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matt Palmer (supplier of updated dns323-firmware-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 13 Apr 2014 10:00:52 +1000 Source: dns323-firmware-tools Binary: dns323-firmware-tools Architecture: source all Version: 0.6-2 Distribution: unstable Urgency: low Maintainer: Matt Palmer Changed-By: Matt Palmer Description: dns323-firmware-tools - build and manipulate firmware images for the DNS-323 Closes: 740744 Changes: dns323-firmware-tools (0.6-2) unstable; urgency=low . * Correct ruby dependency. Closes: #740744. Checksums-Sha1: 0ca32518a70ef2983d64b2c49e98737d27641853 1146 dns323-firmware-tools_0.6-2.dsc 5a5dd2790220bf3debdd7947ffb770427fa0a64b 2045 dns323-firmware-tools_0.6-2.diff.gz 446c80fb772e01360bf97f35b6ab6b92ed838305 9110 dns323-firmware-tools_0.6-2_all.deb Checksums-Sha256: d89db1300446abe75af6eb171536436fec3fcd442134e40c52a1ec8fb6ecc36e 1146 dns323-firmware-tools_0.6-2.dsc f27016bb53f4ccaf2e9f790058a0671743373cad2399e7efe75b483f7750d0bd 2045 dns323-firmware-tools_0.6-2.diff.gz 686ca00b5b5e87184df3ce2e683704d4dead5a98e764430b0842309f6a2bae86 9110 dns323-firmware-tools_0.6-2_all.deb Files: 2b3bc1235049a893fac58e45914fcda0 1146 otherosfs optional dns323-firmware-tools_0.6-2.dsc c765179db8698e7531c325b8c6d98d9e 2045 otherosfs optional dns323-firmware-tools_0.6-2.diff.gz bddb987fd93bce993a36b1ad3829fc63 9110 otherosfs optional dns323-firmware-tools_0.6-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iD8DBQFTVDaGBEnrTWk1E4cRAjnOAJ0bHNRw2xKiLgpi7yHw8bWLEGHn9ACcDzWk Gtyn1r87ymYWH0BwCcE74f8= =wW8O -END PGP SIGNATURE End Message ---
Processed: fixed 745223 in 0.9.0.12-1, closing 745223
Processing commands for cont...@bugs.debian.org: > fixed 745223 0.9.0.12-1 Bug #745223 [src:haskell-swish] Please update build-depends Marked as fixed in versions haskell-swish/0.9.0.12-1. > close 745223 Bug #745223 [src:haskell-swish] Please update build-depends Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 745223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745223 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#726661: Does not permit login as root from version 1:6.2p2-6
Confirming that this bug is still open: I freshly installed Debian testing "Jessie" with only SSH Server from tasksel and I was not able to login using root, although it is possible to do so in Wheezy. > Workaround: comment out this line in /etc/pam.d/ssh: > > session required pam_loginuid.so Didn't work. (In fact I reverted all changes to /etc/pam.d/ssh after seeing that next step was successful) > Downgrading openssh-server to the version on stable (1:6.0p1-4) fixed the problem. This was the helping hint, thank you very much! Additionally, root login must be enabled. After all, all that should be needed to downgrade and enable: echo "deb http://ftp.de.debian.org/debian/ wheezy main" >> /etc/apt/sources.list apt-get update apt-get remove openssh-server apt-get install openssh-server=1:6.0p1-4 openssh-client=1:6.0p1-4 sed -i "s/^PermitRootLogin without-password/PermitRootLogin yes/" /etc/ssh/sshd_config /etc/init.d/ssh restart Hope these steps help saving time the next one googling for "debian jessie enable root ssh" to workaround this bug ;) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: dns323-firmware-tools: diff for NMU version 0.6-1.1
Processing commands for cont...@bugs.debian.org: > tags 740744 + patch Bug #740744 [dns323-firmware-tools] dns323-firmware-tools: Please migrate to Ruby 2.0/2.1 Added tag(s) patch. > tags 740744 + pending Bug #740744 [dns323-firmware-tools] dns323-firmware-tools: Please migrate to Ruby 2.0/2.1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 740744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740744 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#740744: dns323-firmware-tools: diff for NMU version 0.6-1.1
tags 740744 + patch tags 740744 + pending thanks Dear maintainer, I've prepared an NMU for dns323-firmware-tools (versioned as 0.6-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u dns323-firmware-tools-0.6/debian/changelog dns323-firmware-tools-0.6/debian/changelog --- dns323-firmware-tools-0.6/debian/changelog +++ dns323-firmware-tools-0.6/debian/changelog @@ -1,3 +1,10 @@ +dns323-firmware-tools (0.6-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Depend on ruby instead of ruby1.9.1. (Closes: #740744) + + -- Cédric Boutillier Sun, 20 Apr 2014 22:19:32 +0200 + dns323-firmware-tools (0.6-1) unstable; urgency=low * New upstream release. diff -u dns323-firmware-tools-0.6/debian/control dns323-firmware-tools-0.6/debian/control --- dns323-firmware-tools-0.6/debian/control +++ dns323-firmware-tools-0.6/debian/control @@ -8,7 +8,7 @@ Package: dns323-firmware-tools Architecture: all -Depends: ruby1.9.1 +Depends: ruby Description: build and manipulate firmware images for the DNS-323 This package contains programs for manipulating the firmware images used by the D-Link DNS-323 and similar devices (firmwares sometimes referred to as signature.asc Description: Digital signature
Processed: tagging 745354
Processing commands for cont...@bugs.debian.org: > tags 745354 - security Bug #745354 [apt] apt-get fails on cdrom added with apt-cdrom while updating Removed tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 745354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: bug 744807 is forwarded to https://github.com/cucumber/gherkin/issues/305
Processing commands for cont...@bugs.debian.org: > forwarded 744807 https://github.com/cucumber/gherkin/issues/305 Bug #744807 [src:ruby-gherkin] FTBFS: ERROR: Test "ruby2.1" failed. Set Bug forwarded-to-address to 'https://github.com/cucumber/gherkin/issues/305'. > thanks Stopping processing here. Please contact me if you need assistance. -- 744807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744807 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: tags
Processing commands for cont...@bugs.debian.org: > tags 745307 + confirmed upstream Bug #745307 [src:dose3] FTBFS with ocamlgraph 1.8.4 Added tag(s) upstream and confirmed. > End of message, stopping processing here. Please contact me if you need assistance. -- 745307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745307 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#741752: marked as done (odt2txt: FTBFS: zip.h:53:21: fatal error: zipconf.h: No such file or directory)
Your message dated Sun, 20 Apr 2014 19:48:22 + with message-id and subject line Bug#741752: fixed in odt2txt 0.4+git20100620-1.1 has caused the Debian Bug report #741752, regarding odt2txt: FTBFS: zip.h:53:21: fatal error: zipconf.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 741752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: odt2txt Version: 0.4+git20100620-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140315 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): > cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat > -Werror=format-security -Wall -DHAVE_LIBZIP -D_FORTIFY_SOURCE=2 -c -o > odt2txt.o odt2txt.c > In file included from odt2txt.c:40:0: > /usr/include/zip.h:53:21: fatal error: zipconf.h: No such file or directory > #include > ^ > compilation terminated. > make[1]: *** [odt2txt.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/03/15/odt2txt_0.4+git20100620-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: odt2txt Source-Version: 0.4+git20100620-1.1 We believe that the bug you reported is fixed in the latest version of odt2txt, 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 741...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated odt2txt 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, 15 Apr 2014 21:11:48 +0200 Source: odt2txt Binary: odt2txt Architecture: source amd64 Version: 0.4+git20100620-1.1 Distribution: unstable Urgency: medium Maintainer: Nelson A. de Oliveira Changed-By: Petter Reinholdtsen Description: odt2txt- simple converter from OpenDocument Text to plain text Closes: 741752 Changes: odt2txt (0.4+git20100620-1.1) unstable; urgency=medium . * Non-maintainer upload using patch from Hideki Yamane to fix RC bug. * debian/control - Add "Build-Depends: pkg-config" * debian/rules - Add pkg-config to fix FTBFS "zip.h:53:21: fatal error: zipconf.h: No such file or directory" with libzip-dev changes (Closes: #741752) Checksums-Sha1: 2114cfb1e83cdf05ad1d9fc1a9be59db2ff2197a 1172 odt2txt_0.4+git20100620-1.1.dsc c59fc3ba4f0116f9e522371bca5172351c2f90da 3346 odt2txt_0.4+git20100620-1.1.debian.tar.bz2 fcf134f068cea81dcf988cf150019064e434c510 12632 odt2txt_0.4+git20100620-1.1_amd64.deb Checksums-Sha256: 618bd7f79d1174372812900d3be5ed4f9c7c943b46f74ea26663423cad62ed6a 1172 odt2txt_0.4+git20100620-1.1.dsc 2d583940aa5866d9fedc4be3679dd4a7b9f862c7fb025a7694bb818bcdebe046 3346 odt2txt_0.4+git20100620-1.1.debian.tar.bz2 c631b009c42db2ebed9d5a0f6e87398114afc4682998966cba5b1c863f178829 12632 odt2txt_0.4+git20100620-1.1_amd64.deb Files: 765c3745a2ae9e65f8500b30203a6b6d 1172 text optional odt2txt_0.4+git20100620-1.1.dsc b371d030a368b8495cfe6e8b2293abef 3346 text optional odt2txt_0.4+git20100620-1.1.debian.tar.bz2 d65d14e8b2868422c5791751f0f0c56d 12632 text optional odt2txt_0.4+git20100620-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iD8DBQFTTYV620zMSyow1ykRAu6GAJ0ei1R+GGYObVR1hs1qp7Fkg+aLrQCfYWlg uOgw8WNl3JvQkeYiOufDIhg= =I8tB -END PGP SIGNATURE End Message ---
Bug#745354: apt-get fails on cdrom added with apt-cdrom while updating
Package: apt Version: 0.9.7.9+deb7u1 Severity: grave Tags: d-i security Justification: user security hole -- Some information added by myself: I have added the architecture i386 to install skype, but my computer has architekture amd64. It could be that the output of apt-get tries to say that there is an error with architekture i386 - but I don't know real about it. -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image.*"; APT::NeverAutoRemove:: "^kfreebsd-image.*"; APT::NeverAutoRemove:: "^linux-restricted-modules.*"; APT::NeverAutoRemove:: "^linux-ubuntu-modules-.*"; APT::NeverAutoRemove:: "^gnumach$"; APT::NeverAutoRemove:: "^gnumach-image.*"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Never-MarkAuto-Sections:: "oldlibs"; APT::Never-MarkAuto-Sections:: "restricted/oldlibs"; APT::Never-MarkAuto-Sections:: "universe/oldlibs"; APT::Never-MarkAuto-Sections:: "multiverse/oldlibs"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "[ ! -f /var/run/dbus/system_bus_socket ] || /usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt org.debian.apt.CacheChanged || true"; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 1 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Architectures:: "i386"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "1"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "2"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-9n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "3"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-9"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "4"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "5"; APT::Compressor::lzma::CompressArg ""; APT::Compressor::lzma::CompressArg:: "--format=lzma"; APT::Compressor::lzma::CompressArg:: "-9"; APT::Compressor::lzma::UncompressArg ""; APT::Compressor::lzma::UncompressArg:: "--format=lzma"; APT::Compressor::lzma::UncompressArg:: "-d"; APT::CompressorName ""; APT::CompressorExtension "."; APT::CompressorBinary ""; APT::CompressorCost "100"; APT::CompressorCompressArg ""; APT::CompressorCompressArg:: "-9"; APT::CompressorUncompressArg ""; APT::CompressorUncompressArg:: "-d"; Dir "/"; Dir::State "var/lib/apt/"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::mirrors "mirrors/"; Dir::State::extended_states "extended_states"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt/"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt/"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::sourceparts "sources.list.d"; Dir::Etc::vendorlist "vendors.list"; Dir::Etc::vendorparts "vendors.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::netrc "auth.conf"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Etc::preferencesparts "preferences.d"; Dir::Etc::trusted "trusted.gpg"; Dir::Etc::trustedparts "trusted.gpg.d"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::solvers ""; Dir::Bin::solvers::
Bug#743276: marked as done (python-cigi builds for python3.3, not python2.7)
Your message dated Sun, 20 Apr 2014 19:33:30 + with message-id and subject line Bug#743276: fixed in cigi-ccl 3.3.3a+svn818-6 has caused the Debian Bug report #743276, regarding python-cigi builds for python3.3, not python2.7 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.) -- 743276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-cigi Version: 3.3.3a+svn818-5 Severity: grave Tags: sid jessie python-cigi depends on libpython3.3, and the extension is built for 3.3, not 2.7, making it unusable. And please don't link the extension against the python library. --- End Message --- --- Begin Message --- Source: cigi-ccl Source-Version: 3.3.3a+svn818-6 We believe that the bug you reported is fixed in the latest version of cigi-ccl, 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 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Klee Dienes (supplier of updated cigi-ccl 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: Sat, 19 Apr 2014 22:38:08 -0400 Source: cigi-ccl Binary: libcigicl-dev libcigicl1-dbg libcigicl1 cigi-ccl-examples python-cigi python3-cigi Architecture: source amd64 Version: 3.3.3a+svn818-6 Distribution: unstable Urgency: medium Maintainer: Klee Dienes Changed-By: Klee Dienes Description: cigi-ccl-examples - compiled examples for the CIGI class library (CCL) libcigicl-dev - development files for the CIGI class library (CCL) libcigicl1 - runtime library for the CIGI class library (CCL) libcigicl1-dbg - debug symbols for the CIGI class library (CCL) python-cigi - Python bindings for the CIGI class library python3-cigi - Python bindings for the CIGI class library Closes: 743275 743276 Changes: cigi-ccl (3.3.3a+svn818-6) unstable; urgency=medium . * Update python support to use distutils. (Closes: #743275, #743276) Checksums-Sha1: f76bc7998695c8bb6c4cb40ed36c15ab3b2db081 2095 cigi-ccl_3.3.3a+svn818-6.dsc e1588d33065ee44ec1a95994deecd07ff3f59429 15984 cigi-ccl_3.3.3a+svn818-6.debian.tar.xz b65636f5aa4820d2050b5928aacc05984c7ae80e 242080 libcigicl-dev_3.3.3a+svn818-6_amd64.deb fd89e22f284400802bb55216e99b238a00a583dc 6691256 libcigicl1-dbg_3.3.3a+svn818-6_amd64.deb b29a91748bb65c6ae1b5a652b463691ded05aea2 134984 libcigicl1_3.3.3a+svn818-6_amd64.deb fff93a903b037bad414be1250c88aab960ae056a 27022 cigi-ccl-examples_3.3.3a+svn818-6_amd64.deb 6a7f39fce730cde43f59b3cfcb038034b8e0709b 326088 python-cigi_3.3.3a+svn818-6_amd64.deb 4b2b3827e2f2642aa8f4ab9fa84490fc535ab3cd 326974 python3-cigi_3.3.3a+svn818-6_amd64.deb Checksums-Sha256: edd01a8b997ccb243a8a2ccf1b676c2b480459fca4b28817d0346b09746613a9 2095 cigi-ccl_3.3.3a+svn818-6.dsc 3f03cc39898f886d864346ca567e3a5842aa983e968e94f0a516a6ee3b62c363 15984 cigi-ccl_3.3.3a+svn818-6.debian.tar.xz cb3ea9fd33fb4e3b0fb4e5323e682962229519cce6709a7c4588a72329a96e17 242080 libcigicl-dev_3.3.3a+svn818-6_amd64.deb d663ad632589f0d6fa159944314424999b3f5624fdb9d70c7508b432737da0f7 6691256 libcigicl1-dbg_3.3.3a+svn818-6_amd64.deb 6125a24662ba57abc855f99ce394162bc7e93e77180581e9edd0432b0c87b21e 134984 libcigicl1_3.3.3a+svn818-6_amd64.deb 231e47710755171348d7b4d01802efdec84c893693d379d3f58e9e7e5c56795a 27022 cigi-ccl-examples_3.3.3a+svn818-6_amd64.deb 57ab666cfbe1c04422b910ced790025a8e85772e42af7113c011ee57820819d2 326088 python-cigi_3.3.3a+svn818-6_amd64.deb 4a89298717ae3d323fba528f60220c4ece02b9f3810354905f4764f54568b96a 326974 python3-cigi_3.3.3a+svn818-6_amd64.deb Files: 38cad5a55c4500c53b5c8d15bad4ad62 2095 libs optional cigi-ccl_3.3.3a+svn818-6.dsc 4ed1ff8d112caad25f9b26f4666dc643 15984 libs optional cigi-ccl_3.3.3a+svn818-6.debian.tar.xz f6f59d6f4791b67ebfac28fb59b7385b 242080 libdevel optional libcigicl-dev_3.3.3a+svn818-6_amd64.deb ce497c5f859f78bfb11a5564857e8472 6691256 debug extra libcigicl1-dbg_3.3.3a+svn818-6_amd64.deb e960ea73c6aa07e9f15a7b258f8ebae3 134984 libs optional libcigicl1_3.3.3a+svn818-6_amd64.deb e0379a1767630df47a05a25c1a4e2c40 27022 devel optional cigi-ccl-examples_3.3.3a+svn818-6_amd64.deb d4f988c0d
Bug#743275: marked as done (python3-cigi installs an untagged python3 extension)
Your message dated Sun, 20 Apr 2014 19:33:30 + with message-id and subject line Bug#743275: fixed in cigi-ccl 3.3.3a+svn818-6 has caused the Debian Bug report #743275, regarding python3-cigi installs an untagged python3 extension 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.) -- 743275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-cigi Version: 3.3.3a+svn818-5 Severity: grave Tags: sid jessie User: debian-pyt...@lists.debian.org Usertags: python3.4 python3-cigi installs an untagged python3 extension _cigi.so, which is tried to load from python3.4 and fails. There are several issues: - the extension should be tagged (renamed) with the python ABI tag. The easiest way to do this is to use dh_python3 on the package. - The package build-depends on python3-all-dev, but only builds for the default python3 version. Either build the extension for all python versions, or just use python3-dev as the b-d. --- End Message --- --- Begin Message --- Source: cigi-ccl Source-Version: 3.3.3a+svn818-6 We believe that the bug you reported is fixed in the latest version of cigi-ccl, 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 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Klee Dienes (supplier of updated cigi-ccl 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: Sat, 19 Apr 2014 22:38:08 -0400 Source: cigi-ccl Binary: libcigicl-dev libcigicl1-dbg libcigicl1 cigi-ccl-examples python-cigi python3-cigi Architecture: source amd64 Version: 3.3.3a+svn818-6 Distribution: unstable Urgency: medium Maintainer: Klee Dienes Changed-By: Klee Dienes Description: cigi-ccl-examples - compiled examples for the CIGI class library (CCL) libcigicl-dev - development files for the CIGI class library (CCL) libcigicl1 - runtime library for the CIGI class library (CCL) libcigicl1-dbg - debug symbols for the CIGI class library (CCL) python-cigi - Python bindings for the CIGI class library python3-cigi - Python bindings for the CIGI class library Closes: 743275 743276 Changes: cigi-ccl (3.3.3a+svn818-6) unstable; urgency=medium . * Update python support to use distutils. (Closes: #743275, #743276) Checksums-Sha1: f76bc7998695c8bb6c4cb40ed36c15ab3b2db081 2095 cigi-ccl_3.3.3a+svn818-6.dsc e1588d33065ee44ec1a95994deecd07ff3f59429 15984 cigi-ccl_3.3.3a+svn818-6.debian.tar.xz b65636f5aa4820d2050b5928aacc05984c7ae80e 242080 libcigicl-dev_3.3.3a+svn818-6_amd64.deb fd89e22f284400802bb55216e99b238a00a583dc 6691256 libcigicl1-dbg_3.3.3a+svn818-6_amd64.deb b29a91748bb65c6ae1b5a652b463691ded05aea2 134984 libcigicl1_3.3.3a+svn818-6_amd64.deb fff93a903b037bad414be1250c88aab960ae056a 27022 cigi-ccl-examples_3.3.3a+svn818-6_amd64.deb 6a7f39fce730cde43f59b3cfcb038034b8e0709b 326088 python-cigi_3.3.3a+svn818-6_amd64.deb 4b2b3827e2f2642aa8f4ab9fa84490fc535ab3cd 326974 python3-cigi_3.3.3a+svn818-6_amd64.deb Checksums-Sha256: edd01a8b997ccb243a8a2ccf1b676c2b480459fca4b28817d0346b09746613a9 2095 cigi-ccl_3.3.3a+svn818-6.dsc 3f03cc39898f886d864346ca567e3a5842aa983e968e94f0a516a6ee3b62c363 15984 cigi-ccl_3.3.3a+svn818-6.debian.tar.xz cb3ea9fd33fb4e3b0fb4e5323e682962229519cce6709a7c4588a72329a96e17 242080 libcigicl-dev_3.3.3a+svn818-6_amd64.deb d663ad632589f0d6fa159944314424999b3f5624fdb9d70c7508b432737da0f7 6691256 libcigicl1-dbg_3.3.3a+svn818-6_amd64.deb 6125a24662ba57abc855f99ce394162bc7e93e77180581e9edd0432b0c87b21e 134984 libcigicl1_3.3.3a+svn818-6_amd64.deb 231e47710755171348d7b4d01802efdec84c893693d379d3f58e9e7e5c56795a 27022 cigi-ccl-examples_3.3.3a+svn818-6_amd64.deb 57ab666cfbe1c04422b910ced790025a8e85772e42af7113c011ee57820819d2 326088 python-cigi_3.3.3a+svn818-6_amd64.deb 4a89298717ae3d323fba528f60220c4ece02b9f3810354905f4764f54568b96a 326974 python3-cigi_3.3.3a+svn818-6_amd64.deb Files: 38cad5a55c4500c53b5c8d15bad4ad62 2095 libs optional cigi-ccl_3.3.3a+svn818-6.dsc 4ed1ff8d112caad25f9b26f4666dc643 15984 libs optional cigi-ccl_3.3.3a+svn818-6.debian.tar.xz f6f59d6f4791b67ebfac28fb59b7385b 24
Processed: clone
Processing commands for cont...@bugs.debian.org: > clone 743275 -1 Bug #743275 [python3-cigi] python3-cigi installs an untagged python3 extension Bug 743275 cloned as bug 745351 > retitle -1 python3-cigi should build using all available python versions Bug #745351 [python3-cigi] python3-cigi installs an untagged python3 extension Changed Bug title to 'python3-cigi should build using all available python versions' from 'python3-cigi installs an untagged python3 extension' > severity -1 normal Bug #745351 [python3-cigi] python3-cigi should build using all available python versions Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 743275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743275 745351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745351 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#744751: perl -i ignores errors (!)
severity 744751 wishlist thanks On Tue, Apr 15, 2014 at 10:02:56PM +0300, Niko Tyni wrote: > On Mon, Apr 14, 2014 at 12:02:51PM +0100, Ian Jackson wrote: > > Package: perl > > Version: 5.14.2-21+deb7u1 > > Severity: grave > > > mariner:~/junk> perl -i.bak -pe '' nonexistent > > Can't open nonexistent: No such file or directory. > > mariner:~/junk> echo $? > > 0 > I can see that it would be useful if an exit code would be propagated > on errors, somewhat like for instance find(1) does. I suppose it > should replace the implicit exit(0) at the end of the program so that > explicit exit() or die() calls and the like in the program would take > precedence. > > This seems like it might be a feasible change for the future, but it > needs to be discussed and implemented upstream. Backward compatibility > is a high priority for perl, so it might well get rejected too. > > Anyway, I think this is an enhancement request of the 'wishlist' category, > not a grave bug. It all seems to be working as designed. Lowering the severity as per above. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#744751: perl -i ignores errors (!)
Processing commands for cont...@bugs.debian.org: > severity 744751 wishlist Bug #744751 [perl] perl -i ignores errors (!) Severity set to 'wishlist' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 744751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744751 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#745233: libhogweed2: should have versioned depend on newer libgmp10
söndagen den 20 april 2014 12.53.02 skrev Steve M. Robbins: > So to be sure: adding "-V" is the right thing to do here? You should add "-V libgmp10 (>= 6.0.0)" and keep it that way until further symbols are added. But preferably you should create a symbols file so that packages that don't use the new symbols don't get unnecessarily strict dependencies: Go back to the previous version or, to be sure, the first version with SOVERSION 10 (5.0.x). Add a file debian/libgmp10.symbols with the following content: libgmp.so.10 libgmp10 #MINVER# Build the package. You should get complaints about new symbols and a diff. Apply that diff, but change the version number on each line to only consist of the upstream version (or the upstream version + "~", to allow for backports). For symbols that have existed from the beginning of libgmp10, you can change the version number to 0, meaning no versioned dependency will be generated. Repeat for each nee upstream version that might have added new symbols (which I guess means 5.1.x and 6.0.0). -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#745233: libhogweed2: should have versioned depend on newer libgmp10
On April 20, 2014 06:59:31 PM Magnus Holmgren wrote: > reassign 745233 libgmp10 > retitle 745233 libgmp10: Wrong shlibs information after 6.0.0 adds new > symbols affects 745233 libhogweed2 > thanks > > söndagen den 20 april 2014 12.55.09 Ivo De Decker: > > On Sun, Apr 20, 2014 at 01:14:18AM +0200, Magnus Holmgren wrote: > > > That kind of thing should never happen; that's what we have shlibs and > > > symbols files for. Do you know if there's any reason that libgmp10 > > > doesn't include a symbols file and/or declare new a minimum version in > > > it's shlibs file? > > > > I agree that this shouldn't happen, but I don't know why libgmp10 doesn't > > include symbols or shlibs files that enforce this dependency. I'm adding a > > Cc to to gmp maintainers. Well, the reason would be ignorance and sloth on my part. :-( > I think I can even dare reassign the bug. Please update the dh_makeshlibs > command for gmp 6.0.0 So to be sure: adding "-V" is the right thing to do here? Thanks, -Steve signature.asc Description: This is a digitally signed message part.
Bug#743717: marked as done (subunit: FTBFS on all arch)
Your message dated Sun, 20 Apr 2014 18:03:47 + with message-id and subject line Bug#743717: fixed in subunit 0.0.18-4 has caused the Debian Bug report #743717, regarding subunit: FTBFS on all arch 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.) -- 743717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: subunit version: 0.0.18-2 severity: serious Hi, The latest upload of subunit FTBFS on all arches. The upload was probably built in an unclean or outdated environment. https://buildd.debian.org/status/package.php?p=subunit&suite=sid Cheers, Ivo --- End Message --- --- Begin Message --- Source: subunit Source-Version: 0.0.18-4 We believe that the bug you reported is fixed in the latest version of subunit, 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 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gonéri Le Bouder (supplier of updated subunit 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: Sun, 20 Apr 2014 15:22:43 +0200 Source: subunit Binary: subunit libsubunit-perl python-subunit python3-subunit libsubunit0 libsubunit-dev libcppunit-subunit0 libcppunit-subunit-dev Architecture: source all amd64 Version: 0.0.18-4 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack Changed-By: Gonéri Le Bouder Description: libcppunit-subunit-dev - SubunitTestProgressListener for CPPUnit - Development headers libcppunit-subunit0 - SubunitTestProgressListener for CPPUnit - C++ shared library libsubunit-dev - Unit testing protocol - Development headers and static library fo libsubunit-perl - perl parser and diff for Subunit streams libsubunit0 - Unit testing protocol - C/C++ shared library python-subunit - unit testing protocol - Python bindings to generate and consume s python3-subunit - unit testing protocol - Python3 bindings to generate and consume subunit- command line tools for processing Subunit streams Closes: 743717 Changes: subunit (0.0.18-4) unstable; urgency=medium . * control: Fix a minor typo in my name * Fix the clean target to be sure we can can do two build in a raw * Adjust arch all in build-indep target (Closes: #743717) - thanks Ivo De Decker Checksums-Sha1: 45658c8787ae390dcedaf3025ea05fede5d26e8e 2678 subunit_0.0.18-4.dsc 61b267ff8b4e506a80c21a53a292a4ce030c7928 172656 subunit_0.0.18-4.debian.tar.xz 91fcd1af4803fd885c5bef4d73a42e510c9538ed 21252 subunit_0.0.18-4_all.deb 2763c0b6ff7f6d7416c0089e7006e7397eb9a75a 8008 libsubunit-perl_0.0.18-4_all.deb 8f7f2ee3ecd357f98edfc82e49f0894aad50bcc1 62480 python-subunit_0.0.18-4_all.deb 0e86c2d6045c1663b74b9b2f0f2cf0068b698e7d 61544 python3-subunit_0.0.18-4_all.deb c288ad789589b72cf6c4dc90157663063579fff4 8502 libsubunit0_0.0.18-4_amd64.deb c334b9cdc447a5af85ec4b404e8a306e018e03c4 9168 libsubunit-dev_0.0.18-4_amd64.deb 971ab1a292310a65edc518f1463c1436b51d8b43 11154 libcppunit-subunit0_0.0.18-4_amd64.deb 260c0e23fdf820fd2e0374d75a53929214d2dbc3 11612 libcppunit-subunit-dev_0.0.18-4_amd64.deb Checksums-Sha256: d21e420a608168d0916a6c02a343db3cddfc763ebf62adfe37271dd13bbc44a9 2678 subunit_0.0.18-4.dsc 2b86409c98f74b615df95690b5fba27b52231e2698fb0b2ab1cf7c404bbef595 172656 subunit_0.0.18-4.debian.tar.xz ddd2d24e68187ec35b3bdb5aca6799a567e9ccef0413e91f4faf6bdbc3b10f91 21252 subunit_0.0.18-4_all.deb 54c31f72d1e275741d8b3b96a0da6c12895cf8d09d0d25bedd6ffb48fd04ceca 8008 libsubunit-perl_0.0.18-4_all.deb 72bdce9180a96a9bc5c8bf18bcc6f84544af5ef4f4e6e2a83600999057c906c9 62480 python-subunit_0.0.18-4_all.deb df01795bdc0894e34523402745e90eed51b9e40c656fdd14d2639ce1f8200103 61544 python3-subunit_0.0.18-4_all.deb d06fb95a095bd5a144efe2c1edc113f61acd03e78f21499308f6325293682bcb 8502 libsubunit0_0.0.18-4_amd64.deb efc399dbaf66b8f8e6af52388a850a3f431410985b5576305f00c6ad71cb4f11 9168 libsubunit-dev_0.0.18-4_amd64.deb bc2912ea03d0fa9b354e739163205a1cade0fef051afc481e6bf963436163759 11154 libcppunit-subunit0_0.0.18-4_amd64.deb 431eb58a7734aab962ca558edd8930e96f81e31cc498463fd42e422ea89c5e56 11612 libcppunit-subunit
Bug#745233: libhogweed2: should have versioned depend on newer libgmp10
reassign 745233 libgmp10 retitle 745233 libgmp10: Wrong shlibs information after 6.0.0 adds new symbols affects 745233 libhogweed2 thanks söndagen den 20 april 2014 12.55.09 Ivo De Decker: > On Sun, Apr 20, 2014 at 01:14:18AM +0200, Magnus Holmgren wrote: > > That kind of thing should never happen; that's what we have shlibs and > > symbols files for. Do you know if there's any reason that libgmp10 > > doesn't include a symbols file and/or declare new a minimum version in > > it's shlibs file? > I agree that this shouldn't happen, but I don't know why libgmp10 doesn't > include symbols or shlibs files that enforce this dependency. I'm adding a > Cc to to gmp maintainers. I think I can even dare reassign the bug. Please update the dh_makeshlibs command for gmp 6.0.0 or, preferably, add a symbols file. Then nettle and all other packages that reference the new symbols should be binNMUed. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#739743: marked as done (FTBFS: circular dependency)
Your message dated Sun, 20 Apr 2014 09:55:23 -0700 with message-id <868ur0djpg@hiro.keithp.com> and subject line Already fixed has caused the Debian Bug report #739743, regarding FTBFS: circular 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.) -- 739743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfontconfig1 Severity: serious fontconfig recently added a build-dependency on docbook-utils, and hence an indirect build-dependency on itself. As the arch:any libfontconfig1 has an exact version dependency on the arch:all fontconfig-config, this causes the build to fail on all architectures other than the first: https://buildd.debian.org/status/package.php?p=fontconfig --- End Message --- --- Begin Message --- Version: 2.11.0-5 The changelog format was incorrect, causing this bug to not get closed. -- keith.pack...@intel.com pgpbZ1aXXNKAc.pgp Description: PGP signature --- End Message ---
Bug#745339: xwelltris: Doesn't start (Loading resources..ERROR: Can't find file)
Package: xwelltris Version: 1.0.1-15 Severity: grave Dear Maintainer, When attempting to start xwelltris I get the following error message: $ xwelltris Loading resources..ERROR: Can't find file board2.gif in: ./ ./data /home/debian/.xwelltris /usr/share/xwelltris ..ERROR: Can't find file font2.gif in: ./ ./data /home/debian/.xwelltris /usr/share/xwelltris ..ERROR: Can't find file wellintro.gif in: ./ ./data /home/debian/.xwelltris /usr/share/xwelltris ..ERROR: Can't find file topnine.gif in: ./ ./data /home/debian/.xwelltris /usr/share/xwelltris ..ERROR: Can't find file wellcuts.gif in: ./ ./data /home/debian/.xwelltris /usr/share/xwelltris ..done ERROR: Can't find file polyomino.dat in: ./ ./data /home/debian/.xwelltris /usr/share/xwelltris Can not open input file, polyomino.dat My guess is that it should also look in /usr/share/games/xwelltris/ where the graphic files are installed. Just to test, I added a symlink in /usr/share, which made the game run. It did complain about welltris.scores though, which probably needs a similar fix. Originally discovered in Ubuntu, see https://bugs.launchpad.net/ubuntu/+source/xwelltris/+bug/1309718 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xwelltris depends on: ii libc62.18-4 ii libgcc1 1:4.9-20140411-2 ii libsdl-image1.2 1.2.12-5+b2 ii libsdl1.2debian 1.2.15-9 ii libstdc++6 4.9-20140411-2 xwelltris recommends no packages. xwelltris suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim http://desserud.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#739743: FTBFS: circular dependency
Keith Packard writes: > Ivo De Decker writes: > >> Hi Keith, >> >> On Sun, Feb 23, 2014 at 08:09:41PM -0800, Keith Packard wrote: >>> I've uploaded 2.11.0-5 which just provides the pre-built documentation >>> as a debian patch for now. >>> >>> I think I'll probably eliminate the fontconfig-config package and just >>> merge the contents of that into the libfontconfig1 package; the benefit >>> of the separate fontconfig-config in disk space savings isn't great >>> enough to justify needing a separate package, I think. >> >> This bug is still blocking migration to testing. If this is unintentional, >> you >> should probably downgrade is (because the main issue is solved), or just >> close >> it. > > Sorry, got side-tracked with other things. I'll rework the packaging > today and upload. Yeah, I just typo'd the changelog entry which was supposed to close the bug. Missing colon. -- keith.pack...@intel.com pgpnq9p7sw1KG.pgp Description: PGP signature
Bug#739743: FTBFS: circular dependency
Ivo De Decker writes: > Hi Keith, > > On Sun, Feb 23, 2014 at 08:09:41PM -0800, Keith Packard wrote: >> I've uploaded 2.11.0-5 which just provides the pre-built documentation >> as a debian patch for now. >> >> I think I'll probably eliminate the fontconfig-config package and just >> merge the contents of that into the libfontconfig1 package; the benefit >> of the separate fontconfig-config in disk space savings isn't great >> enough to justify needing a separate package, I think. > > This bug is still blocking migration to testing. If this is unintentional, you > should probably downgrade is (because the main issue is solved), or just close > it. Sorry, got side-tracked with other things. I'll rework the packaging today and upload. -- keith.pack...@intel.com pgpLiMg7ptNoe.pgp Description: PGP signature
Bug#743717: [PKG-Openstack-devel] Bug#743717: closed by Thomas Goirand (Bug#743717: fixed in subunit 0.0.18-3)
On 04/20/2014 08:34 PM, Gonéri Le Bouder wrote: > On Sun, Apr 20, 2014 at 01:06:05PM +0200, Ivo De Decker wrote: >> Hi, > >> I just tried the rebuild myself (with pbuilder), and it seems the problem >> happens when building only the architecture-specific package (which is what >> happens on the buildds). When building both architecture specific and >> architecture independent packages, the build works fine. > Ah! Thanks Ivo you deserve a beer for that :) > > Cheers, Hum... So the build would build only the arch-specific packages, I get it now, and it makes sense. But how to fix the debian/rules file then? Should I, in the override_dh_python3 target, check if there's a $(CURDIR)/debian/subunit/usr/bin folder, and do nothing if it's not there? Or is there a way to have override_dh_python3 happen only when build-arch-indep is called? 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#744910: [debian-mysql] Bug#744910: mysql-5.5: Oracle SPU April 2014
MariaDB 5.5.37 has been in upload ready since Friday, but my sponsor isn't available right now and I don't have upload permissions. All builds and test suites pass as seen in logs at http://buildbot.askmonty.org/buildbot/builders/debpkg-sid http://buildbot.askmonty.org/buildbot/builders/debpkg-trusty https://launchpad.net/~mysql-ubuntu/+archive/mariadb/+builds?build_text=&build_state=all For my part security team is free to pull from git.debian.org/pkg-mysql/mariadb-5.5.git and upload. -- Check out our blog at http://seravo.fi/blog and follow @ottokekalainen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Bug#744910: mysql-5.5: Oracle SPU April 2014
Processing control commands: > clone 744910 -1 Bug #744910 [mysql-5.5] mysql-5.5: Oracle SPU April 2014 Bug 744910 cloned as bug 745330 > reassign -1 src:mariadb-5.5 Bug #745330 [mysql-5.5] mysql-5.5: Oracle SPU April 2014 Bug reassigned from package 'mysql-5.5' to 'src:mariadb-5.5'. Ignoring request to alter found versions of bug #745330 to the same values previously set Ignoring request to alter fixed versions of bug #745330 to the same values previously set > retitle -1 Corresponding MariaDB CVEs for Oracle SPU April 2014 Bug #745330 [src:mariadb-5.5] mysql-5.5: Oracle SPU April 2014 Changed Bug title to 'Corresponding MariaDB CVEs for Oracle SPU April 2014' from 'mysql-5.5: Oracle SPU April 2014' -- 744910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744910 745330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745330 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#744910: mysql-5.5: Oracle SPU April 2014
Control: clone 744910 -1 Control: reassign -1 src:mariadb-5.5 Control: retitle -1 Corresponding MariaDB CVEs for Oracle SPU April 2014 On Wed, Apr 16, 2014 at 08:58:48AM +0200, Moritz Muehlenhoff wrote: > Package: mysql-5.5 > Severity: grave > Tags: security > Justification: user security hole > > Hi, > please see > http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html Cloning also for mariadb-5.5 source package. See also [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1088234 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: jbigkit: diff for NMU version 2.0-2.1
Processing commands for cont...@bugs.debian.org: > tags 743960 + pending Bug #743960 [src:jbigkit] jbigkit: CVE-2013-6369: stack-based buffer overflow flaw Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 743960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743960 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#743960: jbigkit: diff for NMU version 2.0-2.1
tags 743960 + pending
thanks
Dear maintainer,
I've prepared an NMU for jbigkit (versioned as 2.0-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards
Salvatore
diff -Nru jbigkit-2.0/debian/changelog jbigkit-2.0/debian/changelog
--- jbigkit-2.0/debian/changelog 2012-04-09 11:30:09.0 +0200
+++ jbigkit-2.0/debian/changelog 2014-04-20 16:38:15.0 +0200
@@ -1,3 +1,11 @@
+jbigkit (2.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add CVE-2013-6369.patch patch.
+CVE-2013-6369: Fix stack-based buffer overflow flaw. (Closes: #743960)
+
+ -- Salvatore Bonaccorso Sun, 20 Apr 2014 16:37:42 +0200
+
jbigkit (2.0-2) unstable; urgency=low
* Correct typo in new Makefile, so that libjbig.so now points to a file
diff -Nru jbigkit-2.0/debian/patches/CVE-2013-6369.patch jbigkit-2.0/debian/patches/CVE-2013-6369.patch
--- jbigkit-2.0/debian/patches/CVE-2013-6369.patch 1970-01-01 01:00:00.0 +0100
+++ jbigkit-2.0/debian/patches/CVE-2013-6369.patch 2014-04-20 16:38:15.0 +0200
@@ -0,0 +1,113 @@
+From f4d30a432e6ba8062f53262785922ba3429bc84e Mon Sep 17 00:00:00 2001
+From: Markus Kuhn
+Date: Wed, 20 Nov 2013 17:06:47 +
+Subject: [PATCH] Fix two DPPRIV buffer overflows and a bug
+
+* jbig.c:jbg_dec_in(): when a BIE with option DPPRIV=1 was received,
+ the included private DP table (1728 bytes) was loaded into
+ 20-byte array s->buffer, creating a buffer overflow vulnerability.
+ It is now loaded instead into a malloc'ed temporary buffer.
+
+* jbig.c:jbg_dec_in(): buffer allocated for internal representation
+ of private DP table was 1728 bytes long, but must be 6912 bytes long,
+ creating another buffer overflow vulnerability.
+
+* jbig.c: a loop in the routines for converting between the internal and
+ external representations of a DP table terminated earlier than intended.
+ As a result, a private DP table provided to the decoder was not
+ interpreted correctly. Likewise, if a user asked the encoder to output
+ its standard DP table (which is only useful for testing), the result
+ would have been incorrect.
+
+* tstcodec.c: test case for DPPRIV=1 added.
+
+The buffer overflow vulnerability was reported by Florian Weimer (Red Hat)
+and has been assigned CVE-2013-6369.
+
+None of these fixes should affect ABI compatibility; jbig.h remains unchanged.
+
+All past releases of jbig.c are believed to be affected.
+The jbig85.c lightwight implementation was not affected.
+---
+ libjbig/jbig.c | 16 ++--
+ libjbig/tstcodec.c | 11 ---
+ 2 files changed, 18 insertions(+), 9 deletions(-)
+
+diff --git a/libjbig/jbig.c b/libjbig/jbig.c
+index f3c35cc..48fc128 100644
+--- a/libjbig/jbig.c
b/libjbig/jbig.c
+@@ -1738,7 +1738,7 @@ void jbg_int2dppriv(unsigned char *dptable, const char *internal)
+ #define FILL_TABLE1(offset, len, trans) \
+ for (i = 0; i < len; i++) { \
+ k = 0; \
+-for (j = 0; j < 8; j++) \
++for (j = 0; i >> j; j++) \
+ k |= ((i >> j) & 1) << trans[j]; \
+ dptable[(i + offset) >> 2] |= \
+ (internal[k + offset] & 3) << ((3 - (i&3)) << 1); \
+@@ -1769,7 +1769,7 @@ void jbg_dppriv2int(char *internal, const unsigned char *dptable)
+ #define FILL_TABLE2(offset, len, trans) \
+ for (i = 0; i < len; i++) { \
+ k = 0; \
+-for (j = 0; j < 8; j++) \
++for (j = 0; i >> j; j++) \
+ k |= ((i >> j) & 1) << trans[j]; \
+ internal[k + offset] = \
+ (dptable[(i + offset) >> 2] >> ((3 - (i & 3)) << 1)) & 3; \
+@@ -2574,6 +2574,7 @@ int jbg_dec_in(struct jbg_dec_state *s, unsigned char *data, size_t len,
+ unsigned long x, y;
+ unsigned long is[3], ie[3];
+ size_t dummy_cnt;
++ unsigned char *dppriv;
+
+ if (!cnt) cnt = &dummy_cnt;
+ *cnt = 0;
+@@ -2711,13 +2712,16 @@ int jbg_dec_in(struct jbg_dec_state *s, unsigned char *data, size_t len,
+ (s->options & (JBG_DPON | JBG_DPPRIV | JBG_DPLAST)) ==
+ (JBG_DPON | JBG_DPPRIV)) {
+ assert(s->bie_len >= 20);
++if (!s->dppriv || s->dppriv == jbg_dptable)
++ s->dppriv = (char *) checked_malloc(1728, sizeof(char));
+ while (s->bie_len < 20 + 1728 && *cnt < len)
+- s->buffer[s->bie_len++ - 20] = data[(*cnt)++];
++ s->dppriv[s->bie_len++ - 20] = data[(*cnt)++];
+ if (s->bie_len < 20 + 1728)
+ return JBG_EAGAIN;
+-if (!s->dppriv || s->dppriv == jbg_dptable)
+- s->dppriv = (char *) checked_malloc(1728, sizeof(char));
+-jbg_dppriv2int(s->dppriv, s->buffer);
++dppriv = s->dppriv;
++s->dppriv = (char *) checked_malloc(6912, sizeof(char));
++jbg_dppriv2int(s->dppriv, dppriv);
++checked_free(dppriv);
+ }
+
+ /*
+diff --git a/libjbig/tstcodec.c b/libjbig/tstcodec.c
+index 44bae57..6289748 100644
+--- a/libjbig/tstcodec.c
b/libjbig/tstcodec.c
+@@ -483,11 +483,16 @@ int main(int argc, char **argv)
+ problems += test_cycle(&pp, 1960, 1951,
+ JBG_DELAY_AT | JBG_TPBON | JBG_TPDON | JBG_DPON,
+ 0, 6,
Bug#745327: python-slip: Missing dependency on python-six
Package: python-slip
Version: 0.6.0-1
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I have installed firewalld in FreedomBox and ran the command firewall-cmd
and it resulted in a error the six could not be imported. I believe this could
reproduced on a debootstraped install.
* What exactly did you do (or not do) that was effective (or
ineffective)?
firewall-cmd --state
* What was the outcome of this action?
Traceback (most recent call last):
File "/usr/bin/firewall-cmd", line 32, in
from firewall.client import FirewallClient
File "/usr/lib/python2.7/dist-packages/firewall/client.py", line 29, in
import slip.dbus
File "/usr/lib/python2.7/dist-packages/slip/dbus/__init__.py", line 8, in
from . import service
File "/usr/lib/python2.7/dist-packages/slip/dbus/service.py", line 30, in
from six import with_metaclass
ImportError: No module named six
* What outcome did you expect instead?
I expected the 'firewall-cmd --state' to show the current state of the
firewall daemon.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-slip depends on:
ii python 2.7.5-5
python-slip recommends no packages.
python-slip suggests no packages.
-- no debconf information
diff -upr python-slip-0.6.0.old/debian/control python-slip-0.6.0/debian/control
--- python-slip-0.6.0.old/debian/control 2014-03-01 01:44:51.0 +0530
+++ python-slip-0.6.0/debian/control 2014-04-20 19:45:32.411648296 +0530
@@ -15,7 +15,8 @@ Architecture: all
Pre-Depends: ${misc:Pre-Depends}
Depends:
${misc:Depends},
- ${python:Depends}
+ ${python:Depends},
+ python-six
Description: miscellaneous convenience, extension and workaround code for Python
The Simple Library for Python packages contain miscellaneous code for
convenience, extension and workaround purposes.
@@ -28,7 +29,8 @@ Depends:
${python:Depends},
python-slip (= ${source:Version}),
python-dbus,
- python-decorator
+ python-decorator,
+ python-six
Description: convenience functions for dbus services
The Simple Library for Python packages contain miscellaneous code for
convenience, extension and workaround purposes.
Processed: redland-bindings: diff for NMU version 1.0.16.1-2.1
Processing commands for cont...@bugs.debian.org: > tags 743993 + patch Bug #743993 [redland-bindings] FTBFS: ruby-2.0.0/ruby/ruby.h:24:25: fatal error: ruby/config.h: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 743993: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743993 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#743993: redland-bindings: diff for NMU version 1.0.16.1-2.1
tags 743993 + patch
thanks
Dear maintainer,
I've prepared an NMU for redland-bindings (versioned as 1.0.16.1-2.1). The diff
is attached to this message.
Regards.
diff -Nru redland-bindings-1.0.16.1/debian/changelog
redland-bindings-1.0.16.1/debian/changelog
--- redland-bindings-1.0.16.1/debian/changelog 2014-03-08 06:34:38.0
+0100
+++ redland-bindings-1.0.16.1/debian/changelog 2014-04-20 15:54:59.0
+0200
@@ -1,3 +1,10 @@
+redland-bindings (1.0.16.1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix build for Ruby 2.0. (Closes: #743993)
+
+ -- Christian Hofstaedtler Sun, 20 Apr 2014 15:54:31 +0200
+
redland-bindings (1.0.16.1-2) unstable; urgency=medium
* Acknowlege NMU - thanks Christian.
diff -Nru redland-bindings-1.0.16.1/debian/patches/ruby-header-dir.patch
redland-bindings-1.0.16.1/debian/patches/ruby-header-dir.patch
--- redland-bindings-1.0.16.1/debian/patches/ruby-header-dir.patch
1970-01-01 01:00:00.0 +0100
+++ redland-bindings-1.0.16.1/debian/patches/ruby-header-dir.patch
2014-04-20 15:53:58.0 +0200
@@ -0,0 +1,56 @@
+diff --git a/configure b/configure
+index 5593952..1c8cc27 100755
+--- a/configure
b/configure
+@@ -12311,7 +12311,7 @@ if test "X$RUBY" != X; then
+ RUBY_ARCHDIR=`$RUBY -rrbconfig -e "print RbConfig::CONFIG['archdir']"`
+ ruby_install_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['$ruby_install_dir_variable']"`
+ ruby_header_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['rubyhdrdir']"`
+- ruby_arch_config=`$RUBY -rrbconfig -e "puts RbConfig::CONFIG['arch']"`
++ ruby_arch_header_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['rubyarchhdrdir']"`
+ ruby_arch_install_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['$ruby_arch_install_dir_variable']"`
+ librubyarg_shared=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['LIBRUBYARG_SHARED']"`
+
+@@ -12342,13 +12342,7 @@ $as_echo "$RUBY_ARCH_INSTALLDIR from RbConfig::CONFIG
$ruby_arch_install_dir_var
+ { $as_echo "$as_me:${as_lineno-$LINENO}: checking Ruby headers dir" >&5
+ $as_echo_n "checking Ruby headers dir... " >&6; }
+ if test "X$ruby_header_dir_config" != "Xnil" -a "X$ruby_header_dir_config"
!= "X"; then
+-RUBY_INCLUDES="$RUBY_INCLUDES -I$ruby_header_dir_config"
+-if test "X$ruby_arch_config" != "Xnil" -a "X$ruby_arch_config" != "X";
then
+- ruby_arch_hdrdir="$ruby_header_dir_config/$ruby_arch_config"
+- if test -d "$ruby_arch_hdrdir"; then
+-RUBY_INCLUDES="$RUBY_INCLUDES -I$ruby_arch_hdrdir"
+- fi
+-fi
++RUBY_INCLUDES="$RUBY_INCLUDES -I$ruby_header_dir_config
-I$ruby_arch_header_dir_config"
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $RUBY_INCLUDES from
RbConfig::CONFIG rubyhdrdir" >&5
+ $as_echo "$RUBY_INCLUDES from RbConfig::CONFIG rubyhdrdir" >&6; }
+ else
+diff --git a/configure.ac b/configure.ac
+index b285c3b..d9712e1 100644
+--- a/configure.ac
b/configure.ac
+@@ -364,7 +364,7 @@ if test "X$RUBY" != X; then
+ RUBY_ARCHDIR=`$RUBY -rrbconfig -e "print RbConfig::CONFIG['archdir']"`
+ ruby_install_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['$ruby_install_dir_variable']"`
+ ruby_header_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['rubyhdrdir']"`
+- ruby_arch_config=`$RUBY -rrbconfig -e "puts RbConfig::CONFIG['arch']"`
++ ruby_arch_header_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['rubyarchhdrdir']"`
+ ruby_arch_install_dir_config=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['$ruby_arch_install_dir_variable']"`
+ librubyarg_shared=`$RUBY -rrbconfig -e "puts
RbConfig::CONFIG['LIBRUBYARG_SHARED']"`
+ changequote([, ])dnl
+@@ -389,13 +389,7 @@ if test "X$RUBY" != X; then
+
+ AC_MSG_CHECKING(Ruby headers dir)
+ if test "X$ruby_header_dir_config" != "Xnil" -a "X$ruby_header_dir_config"
!= "X"; then
+-RUBY_INCLUDES="$RUBY_INCLUDES -I$ruby_header_dir_config"
+-if test "X$ruby_arch_config" != "Xnil" -a "X$ruby_arch_config" != "X";
then
+- ruby_arch_hdrdir="$ruby_header_dir_config/$ruby_arch_config"
+- if test -d "$ruby_arch_hdrdir"; then
+-RUBY_INCLUDES="$RUBY_INCLUDES -I$ruby_arch_hdrdir"
+- fi
+-fi
++RUBY_INCLUDES="$RUBY_INCLUDES -I$ruby_header_dir_config
-I$ruby_arch_header_dir_config"
+ AC_MSG_RESULT($RUBY_INCLUDES from RbConfig::CONFIG rubyhdrdir)
+ else
+ if test -r "$RUBY_ARCHDIR/ruby.h"; then
diff -Nru redland-bindings-1.0.16.1/debian/patches/series
redland-bindings-1.0.16.1/debian/patches/series
--- redland-bindings-1.0.16.1/debian/patches/series 1970-01-01
01:00:00.0 +0100
+++ redland-bindings-1.0.16.1/debian/patches/series 2014-04-20
15:54:13.0 +0200
@@ -0,0 +1 @@
+ruby-header-dir.patch
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731415: unrar-free is dead upstream and completely useless
Why not make it a transit package to unar, then ? -- Jérôme -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#739743: FTBFS: circular dependency
Hi Keith, On Sun, Feb 23, 2014 at 08:09:41PM -0800, Keith Packard wrote: > I've uploaded 2.11.0-5 which just provides the pre-built documentation > as a debian patch for now. > > I think I'll probably eliminate the fontconfig-config package and just > merge the contents of that into the libfontconfig1 package; the benefit > of the separate fontconfig-config in disk space savings isn't great > enough to justify needing a separate package, I think. This bug is still blocking migration to testing. If this is unintentional, you should probably downgrade is (because the main issue is solved), or just close it. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733570: marked as done (sash: Wrong Built-Using)
Your message dated Sun, 20 Apr 2014 13:19:30 + with message-id and subject line Bug#733570: fixed in sash 3.8-1 has caused the Debian Bug report #733570, regarding sash: Wrong Built-Using 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.) -- 733570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sash Version: 3.7-13 Severity: serious Hi, Your upload got rejected on a few arches with the following error: sash_3.7-13_ia64.deb: APT could not parse Built-Using field It's saying: Built-Using: libc6-dev (= ), zlib (= 1:1.2.8.dfsg-1) libc6-dev does not exist on all arches, it's called libc6.1-dev on ia64, libc0.3-dev on hurd and libc0.1-dev on kfreebsd. I also understand that it should be using a source package name instead of the binary package name, as you do for zlib. But maybe that's an effect of not finding the binary package? Kurt --- End Message --- --- Begin Message --- Source: sash Source-Version: 3.8-1 We believe that the bug you reported is fixed in the latest version of sash, 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 733...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tollef Fog Heen (supplier of updated sash 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: Sun, 20 Apr 2014 08:23:04 +0200 Source: sash Binary: sash Architecture: source amd64 Version: 3.8-1 Distribution: unstable Urgency: medium Maintainer: Tollef Fog Heen Changed-By: Tollef Fog Heen Description: sash - Stand-alone shell Closes: 733570 Changes: sash (3.8-1) unstable; urgency=medium . * New upstream version. * Use grep-status to pull out package name of what provides libc-dev and use that when filling out built-using. Closes: #733570 Checksums-Sha1: ed12beda75f0d02b73aae0f545e81bc227303454 1737 sash_3.8-1.dsc 6e40cffb912444a8de5e144f38d2a51c847cf07f 53049 sash_3.8.orig.tar.gz 3024366f740abdda7cd975648dcd8569072329c2 14900 sash_3.8-1.debian.tar.xz dd7ca91ea190fff09527af4e5a29f9264a8ddd0c 349614 sash_3.8-1_amd64.deb Checksums-Sha256: 6cb5c0ad284bb6d084325bbe898c351128f312e920327caa75fb42a4cbbc5c9b 1737 sash_3.8-1.dsc 13c4f9a911526949096bf543c21a41149e6b037061193b15ba6b707eea7b6579 53049 sash_3.8.orig.tar.gz 94803af63dde5af69dd7a45eb1039303b69551c6c760a8bb428600652c4c4d91 14900 sash_3.8-1.debian.tar.xz 33881eea4bff987b496ae476114233d1e37bdc12b2ef0651a089d19426e54ccc 349614 sash_3.8-1_amd64.deb Files: c6c3a768cc493959f7f5c393dec2020a 1737 shells optional sash_3.8-1.dsc 105faad43be231dd9f439e96c70d76aa 53049 shells optional sash_3.8.orig.tar.gz d3b13fbea578d9eac772239e4729ff85 14900 shells optional sash_3.8-1.debian.tar.xz 5060b6557adf109f57bf32a91615eb5a 349614 shells optional sash_3.8-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTU8aTAAoJELZaSHHKGdcXiJUP/RJ2Ely4ikTPcev0zN9VXj9F l2v5i0Du6ftZdMDkOY1KbiE4aiQWMLphUTNNHiSpSS/tk7dMRJEQkXbqz8SQbBkS AcpPXR04Ylqsa1qAWSzcvaIESrMyDkYXunKOmghW0bgM/PER1/J0G+Ey2H+ksh3n ig8tcVxutqCPu7umt5W9aa6wJWmKqMe3rH0M/kj30rDKPNsGqDfKESKhfy8GtTFG NRvlikcUPUOWHJYsEo7tmFZp8o0nwGSSyrDSHtPmxp/fxdTui/kAIPS2LgqJs0gT Jp1Q8/628STzuRp1p0RXDd5vv2YDnIWZyxHR7ePs5kkFR0lStR2UN3A8itGyhRvH czmtBJXgMO6uEmfCzi3uEcOHox3yJI9uT81oM+BPgfjgT9usg3xJqW3ggWew7RmG 0LnXJLecdf8eastnq7yGRlxEqTMMkP3SLMWr5G7oHOGSF+1t/xwnQtjnTXdsEv4g TLPrlnbd3W7bYBWXWAvUR4hQN1RMCpQHD1yU4W3Fz3M6dxdejJSUvM1uUmJFE5ZV Gt1BEy18IulPQQDDdPPCoDqu4tWxRDCRR18Vgm3AHO+ED5n1TRCuHnK+kcPrwfnA Gql/gwJpwAwp6HrVVxv88E4yH5Li4jcCob97AwKpPgqWFft1J8a9CWcUipbi13mO b1b6AQTVYGX9kuzVWo3m =SSi4 -END PGP SIGNATURE End Message ---
Bug#743717: [PKG-Openstack-devel] Bug#743717: closed by Thomas Goirand (Bug#743717: fixed in subunit 0.0.18-3)
On Sun, Apr 20, 2014 at 01:06:05PM +0200, Ivo De Decker wrote: > Hi, > I just tried the rebuild myself (with pbuilder), and it seems the problem > happens when building only the architecture-specific package (which is what > happens on the buildds). When building both architecture specific and > architecture independent packages, the build works fine. Ah! Thanks Ivo you deserve a beer for that :) Cheers, -- Gonéri pgp03LdfTfGCm.pgp Description: PGP signature
Bug#745307: FTBFS with ocamlgraph 1.8.4
Source: dose3 Version: 3.1.3-7 Severity: serious Dear Maintainer, dose3 fails to build with the latest version of ocamlgraph. Last lines of build log: > + ocamlfind ocamlc -c -w -24 -ccopt -O9 -package extlib -package pcre > -package cudf -package ocamlgraph -pp 'camlp4o.opt -I_build > Camlp4MacroParser.cmxs -DHASZIP -DHASBZ2 -DHASRPM -DHASOCAMLGRAPH' -I algo > -I doselibs -o algo/defaultgraphs.cmo algo/defaultgraphs.ml > File "algo/defaultgraphs.ml", line 134, characters 41-48: > Error: Signature mismatch: >... >Values do not match: > val edge_attributes : >G.E.t -> >[> `Color of int > | `Label of string > | `Style of [> `Dashed | `Solid ] ] >list >is not included in > val edge_attributes : E.t -> Graph.Graphviz.DotAttributes.edge list >File "algo/defaultgraphs.ml", line 126, characters 10-25: > Actual declaration > Command exited with code 2. > make[2]: *** [algo/algo.cma] Error 10 > dh_auto_build: make -j1 returned exit code 2 > make[2]: Leaving directory `/«PKGBUILDDIR»' > make[1]: *** [override_dh_auto_build] Error 2 > make[1]: Leaving directory `/«PKGBUILDDIR»' > make: *** [build-arch] Error 2 > dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Full logs are available at: https://buildd.debian.org/status/package.php?p=dose3&suite=sid Cheers, -- Stéphane -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743717: [PKG-Openstack-devel] Bug#743717: closed by Thomas Goirand (Bug#743717: fixed in subunit 0.0.18-3)
Hi, On Sun, Apr 20, 2014 at 09:48:47AM +0800, Thomas Goirand wrote: > Yes, I did rebuild it also in a fresh amd64 cowbuilder env as well. In > fact, that's what does Jenkins each time I push (it even rebuilds for > Wheezy, Precise and Trusty), but out of options, I did try to setup a > completely new Sid environment using Cowbuilder. And it did work as > well, which is weird. > > So now, I really don't get what is happening with the buildds, and why > they don't have binaries in $(CURDIR)/debian/subunit/usr/bin/* just > right after dh_python3 happens (eg: see the log, this is what this bug > is about, and IMO it has very little to do with my system being > up-to-date or not). > > Yes, I could try to get myself setup with sbuild, but I'm not sure it > would help to understand what's going on. :( > > Does anyone have a clue? I just tried the rebuild myself (with pbuilder), and it seems the problem happens when building only the architecture-specific package (which is what happens on the buildds). When building both architecture specific and architecture independent packages, the build works fine. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745306: AptPackages.py: /etc/init.d/apt-p2p start fails
Package: apt-p2p Version: 0.1.6+nmu1 Severity: grave File: AptPackages.py Tags: patch Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installation of the package. * What exactly did you do (or not do) that was effective (or ineffective)? Issue the command '/etc/init.d/apt-p2p start' at root prompt. * What was the outcome of this action? The following error message was displayed : Starting apt-p2pUnhandled Error Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 642, in run runApp(config) File "/usr/lib/python2.7/dist-packages/twisted/scripts/twistd.py", line 23, in runApp _SomeApplicationRunner(config).run() File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 376, in run self.application = self.createOrGetApplication() File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 441, in createOrGetApplication application = getApplication(self.config, passphrase) --- --- File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 452, in getApplication application = service.loadApplication(filename, style, passphrase) File "/usr/lib/python2.7/dist-packages/twisted/application/service.py", line 405, in loadApplication application = sob.loadValueFromFile(filename, 'application', passphrase) File "/usr/lib/python2.7/dist-packages/twisted/persisted/sob.py", line 210, in loadValueFromFile exec fileObj in d, d File "/usr/sbin/apt-p2p", line 73, in from apt_p2p.apt_p2p import AptP2P File "/usr/lib/pymodules/python2.7/apt_p2p/apt_p2p.py", line 19, in from MirrorManager import MirrorManager File "/usr/lib/pymodules/python2.7/apt_p2p/MirrorManager.py", line 16, in from AptPackages import AptPackages File "/usr/lib/pymodules/python2.7/apt_p2p/AptPackages.py", line 40, in from apt.progress.old import OpProgress exceptions.ImportError: No module named old * What outcome did you expect instead? The usual 'Starting apt-p2p' message. * Problem fixed The problem was fixed by editing the file '/usr/lib/pymodules/python2.7/apt_p2p/AptPackages.py' and replace the code line : from apt.progress.old import OpProgress by the the code line : from apt.progress.base import OpProgress It save my day, but may be this fix has sides effects I cannot even imagine. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages apt-p2p depends on: ii adduser 3.113+nmu3 ii python 2.7.5-5 ii python-apt 0.9.3.5 ii python-debian0.1.21+nmu2 ii python-pysqlite2 2.6.3-3 ii python-support 1.0.15 ii python-twisted-web2 8.1.0-3 apt-p2p recommends no packages. apt-p2p suggests no packages. -- Configuration Files: /etc/apt-p2p/apt-p2p.conf changed: [DEFAULT] PORT = 9970 UPLOAD_LIMIT = 0 MIN_DOWNLOAD_PEERS = 0 CACHE_DIR = /var/cache/apt-p2p LOCAL_OK = yes REMOTE_STATS = yes UNLOAD_PACKAGES_CACHE = 5m KEY_REFRESH = 2.5h USERNAME = apt-p2p DHT = apt_p2p_Khashmir DHT-ONLY = no [apt_p2p_Khashmir] BOOTSTRAP = earpop.petiteanse.net:9970 vortex.petiteanse.net:9970 starlight.petiteanse.net:9970 chalet.petiteanse.net:9970 ratrace.petiteanse.net:9970 hermit.petiteanse.net:9970 turmoil.petiteanse.net:9970 plantation.petiteanse.net:9970 steer.petiteanse.net:9970 BOOTSTRAP_NODE = yes CHECKPOINT_INTERVAL = 5m CONCURRENT_REQS = 8 STORE_REDUNDANCY = 6 RETRIEVE_VALUES = -1 MAX_FAILURES = 3 MIN_PING_INTERVAL = 15m BUCKET_STALENESS = 1h KEY_EXPIRE = 3h KRPC_TIMEOUT = 9s KRPC_INITIAL_DELAY = 2s SPEW = no -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744943: ruby-sass: Cannot load sass/script/node
Quoting Dmitry Smirnov (2014-04-20 12:23:43) > This problem was introduced in package "ruby-sass/3.3.4-1" which rendered > `compass` unusable... I re-assigned this bug accordingly. Thanks. Bug arguably is at both packages (but I maintain both, so no need for further BTS ping-pong): I suspect this problem to be caused not by changes to ruby-sass code (it was upgraded), but instead to change of default Ruby version. I guess this could be solved by a simple binNMU of ruby-compass. I am not skilled in requesting binNMUs so have not dived into that. Also there is a new major release of Compass that I want to upgrade to - i.e. my plan is to do a source-full release instead and expect that to magically solve this issue. I am bogged down with CDBS and Ghostscript packaging right now - so if someone reading this knows how to request a binNMU for ruby-compass, please go ahead with that. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#745233: libhogweed2: should have versioned depend on newer libgmp10
Hi Magnus, On Sun, Apr 20, 2014 at 01:14:18AM +0200, Magnus Holmgren wrote: > lördagen den 19 april 2014 15.21.21 skrev Ivo De Decker: > > The new nettle upload contains a version of libhogweed2 which uses symbols > > from the new version (6.0.0) of libgmp10, but it doesn't have a versioned > > dependency. This means it's possible to install libhogweed2 with an older > > version of libgmp10, but this doesn't work. > > That kind of thing should never happen; that's what we have shlibs and > symbols > files for. Do you know if there's any reason that libgmp10 doesn't include a > symbols file and/or declare new a minimum version in it's shlibs file? I agree that this shouldn't happen, but I don't know why libgmp10 doesn't include symbols or shlibs files that enforce this dependency. I'm adding a Cc to to gmp maintainers. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744943: ruby-sass: Cannot load sass/script/node
This problem was introduced in package "ruby-sass/3.3.4-1" which rendered `compass` unusable... I re-assigned this bug accordingly. -- All the best, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Processed: reassign 744943 to ruby-sass
Processing commands for cont...@bugs.debian.org: > reassign 744943 ruby-sass 3.3.4-1 Bug #744943 [ruby-compass] ruby-compass: Cannot load sass/script/node Bug reassigned from package 'ruby-compass' to 'ruby-sass'. No longer marked as found in versions ruby-compass/0.12.2~dfsg-4. Ignoring request to alter fixed versions of bug #744943 to the same values previously set Bug #744943 [ruby-sass] ruby-compass: Cannot load sass/script/node Marked as found in versions ruby-sass/3.3.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 744943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744943 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#745301: libmms: CVE-2014-2892: heap-based buffer overflow
Source: libmms Version: 0.6-1 Severity: grave Tags: security upstream fixed-upstream Hi, the following vulnerability was published for libmms. CVE-2014-2892[0]: heap-based buffer overflow If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-2892 https://security-tracker.debian.org/tracker/CVE-2014-2892 [1] http://sourceforge.net/p/libmms/code/ci/03bcfccc22919c72742b7338d02859962861e0e8 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org: > tags 744398 + sid jessie Bug #744398 [debsums] debsums claim migrated conffile /etc/init/startpar-bridge.conf was modified Added tag(s) sid and jessie. > tags 745224 + sid jessie Bug #745224 [src:stretchplayer] stretchplayer: FTBFS due to version of cmake Added tag(s) sid and jessie. > tags 743990 + sid jessie Bug #743990 [subtle] subtle: Depends on obsolete version of ruby Added tag(s) sid and jessie. > thanks Stopping processing here. Please contact me if you need assistance. -- 743990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743990 744398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744398 745224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 745189
Processing commands for cont...@bugs.debian.org: > tags 745189 + squeeze Bug #745189 [wordpress] [wordpress] Dependency unavailable on squeeze Added tag(s) squeeze. > thanks Stopping processing here. Please contact me if you need assistance. -- 745189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 745189 is serious
Processing commands for cont...@bugs.debian.org: > severity 745189 serious Bug #745189 [wordpress] [wordpress] Dependency unavailable on squeeze Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 745189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745189 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#743073: marked as done (openturns: FTBFS: Tests failures)
Your message dated Sun, 20 Apr 2014 08:16:42 + with message-id and subject line Bug#743073: fixed in openturns 1.3-2 has caused the Debian Bug report #743073, regarding openturns: FTBFS: Tests failures 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.) -- 743073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openturns Version: 1.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140329 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): > 348/362 Test #355: cppcheck_RandomizedLHS_std > ... Passed0.62 sec > Start 356: cppcheck_RandomizedQuasiMonteCarlo_std > Start 357: cppcheck_Wilks_std > Start 358: cppcheck_VisualTest_std > 349/362 Test #357: cppcheck_Wilks_std > ... Passed0.73 sec > 350/362 Test #356: cppcheck_RandomizedQuasiMonteCarlo_std > ... Passed0.75 sec > Start 359: cppcheck_FittingTest_std > Start 360: cppcheck_HypothesisTest_std > 351/362 Test #341: cppcheck_FunctionalChaos_ishigami_sparse > . Passed9.00 sec > Start 361: cppcheck_LinearModelTest_std > 352/362 Test #338: cppcheck_FunctionalChaos_gsobol > .. Passed 11.70 sec > Start 362: cppcheck_NormalityTest_std > 353/362 Test #362: cppcheck_NormalityTest_std > ... Passed0.92 sec > 354/362 Test #359: cppcheck_FittingTest_std > . Passed5.35 sec > 355/362 Test #342: cppcheck_FunctionalChaos_ishigami_database > ... Passed 14.22 sec > 356/362 Test #360: cppcheck_HypothesisTest_std > ..***Failed6.02 sec > --- /«PKGBUILDDIR»/lib/test/t_HypothesisTest_std.expout 2014-03-06 > 09:09:07.0 + > +++ /«PKGBUILDDIR»/obj-x86_64-linux-gnu/lib/test/t_HypothesisTest_std.out > 2014-03-30 11:48:05.540711963 + > @@ -1,5 +1,5 @@ > ChiSquared=class=TestResult name=Unnamed type=TwoSampleChiSquared > binaryQualityMeasure=true p-value threshold=0.1 p-value=0.985079 > description=[] > ChiSquared2=class=TestResult name=Unnamed type=TwoSampleChiSquared > binaryQualityMeasure=false p-value threshold=0.1 p-value=1.15627e-20 > description=[] > -Pearson=class=TestResult name=Unnamed type=TwoSamplePearson > binaryQualityMeasure=false p-value threshold=0.1 p-value=6.40572e-08 > description=[] > -Smirnov=class=TestResult name=Unnamed type=TwoSampleSmirnov > binaryQualityMeasure=false p-value threshold=0.1 p-value=7.47514e-11 > description=[] > -Spearman=class=TestResult name=Unnamed type=TwoSampleSpearman > binaryQualityMeasure=false p-value threshold=0.1 p-value=0 description=[] > +Pearson=class=TestResult name=Unnamed type=TwoSamplePearson > binaryQualityMeasure=false p-value threshold=0.1 p-value=1.24732e-05 > description=[] > +Smirnov=class=TestResult name=Unnamed type=TwoSampleSmirnov > binaryQualityMeasure=true p-value threshold=0.1 p-value=1 description=[] > +Spearman=class=TestResult name=Unnamed type=TwoSampleSpearman > binaryQualityMeasure=false p-value threshold=0.1 p-value=1.5068e-05 > description=[] > > 357/362 Test #361: cppcheck_LinearModelTest_std > .***Failed7.71 sec > --- /«PKGBUILDDIR»/lib/test/t_LinearModelTest_std.expout 2014-03-06 > 09:09:07.0 + > +++ /«PKGBUILDDIR»/obj-x86_64-linux-gnu/lib/test/t_LinearModelTest_std.out > 2014-03-30 11:48:08.032712355 + > @@ -1,4 +1,4 @@ > -LinearModelAdjustedRSquared=class=TestResult name=Unnamed > type=AdjustedRSquared binaryQualityMeasure=false p-value threshold=0.95 > p-value=0.251488 description=[] > -LinearModelFisher=class=TestResult name=Unnamed type=Fisher > binaryQualityMeasure=false p-value threshold=0.05 p-value=1 description=[] > +LinearModelAdjustedRSquared=class=TestResult name=Unnamed > type=AdjustedRSquared binaryQualityMeasure=false p-value threshold=0.95 > p-value=0.169409 description=[] > +LinearModelFisher=class=TestResult name=Unnamed type=Fisher > binaryQualityMeasure=false p-value threshold=0.05 p-value=0.85 > description=[] > LinearModelResidualMean=class=TestResult name=Unnamed type=ResidualMean > binaryQualityMeasure=true p-value threshold=0.05 p-value=1
Bug#745279: installation fails: entries directory not created
Package: gummiboot Version: 44-1 Severity: serious On a machine that never had gummiboot installed installation fails: Unpacking gummiboot (from .../gummiboot_44-1_amd64.deb) ... Processing triggers for man-db ... Setting up gummiboot (44-1) ... Install 3.12-0.bpo.1-amd64 to ESP /usr/sbin/update-gummiboot: 42: /usr/sbin/update-gummiboot: cannot create /boot/efi/loader/entries/a8eed5e4232ff9061cf1191a4b75b971-3.12-0.bpo.1-amd64.conf: Directory nonexistent dpkg: error processing gummiboot (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: gummiboot E: Sub-process /usr/bin/dpkg returned an error code (1) pkern@simplex ~ % find /boot/efi /boot/efi /boot/efi/a8eed5e4232ff9061cf1191a4b75b971 /boot/efi/a8eed5e4232ff9061cf1191a4b75b971/3.12-0.bpo.1-amd64 /boot/efi/a8eed5e4232ff9061cf1191a4b75b971/3.12-0.bpo.1-amd64/linux /boot/efi/a8eed5e4232ff9061cf1191a4b75b971/3.12-0.bpo.1-amd64/initrd The kernel and initrd are installed using »install -D«, which creates the directories in question. The entries snippet, however, is created using output redirection and no initial »mkdir -p« or »install« to create the target directory. Kind regards and thanks Philipp Kern -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (900, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-0.bpo.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 gummiboot depends on: ii libblkid1 2.20.1-5.3 ii libc6 2.18-4 Versions of packages gummiboot recommends: ii systemd 204-8~bpo70+1 gummiboot suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#745274: Acknowledgement (privoxy: systemd runs privoxy as root and logs messages via syslogd)
Patch updated: clean up stale pid file when service stopped diff --git a/debian/changelog b/debian/changelog index b00da4c..8702738 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +privoxy (3.0.21-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * When starting via systemd, do not run daemon as root, and honour +log file configuration. + + -- Carlos Maddela Sun, 20 Apr 2014 10:35:11 +1000 + privoxy (3.0.21-2) unstable; urgency=low * Use autotools-dev for arm64 compatibility (Closes: #727948). diff --git a/debian/privoxy.service b/debian/privoxy.service index 58f285d..7a48ffc 100644 --- a/debian/privoxy.service +++ b/debian/privoxy.service @@ -1,10 +1,14 @@ [Unit] Description=Privacy enhancing HTTP Proxy - + [Service] -ExecStart=/usr/sbin/privoxy --no-daemon /etc/privoxy/config -StandardOutput=syslog -StandardError=syslog +Environment=PIDFILE=/var/run/privoxy.pid +Environment=OWNER=privoxy +Environment=CONFIGFILE=/etc/privoxy/config +Type=forking +PIDFile=$PIDFILE +ExecStart=/usr/sbin/privoxy --pidfile $PIDFILE --user $OWNER $CONFIGFILE +ExecStopPost=/bin/rm -f $PIDFILE [Install] WantedBy=multi-user.target
