Bug#768263: libglobus-rsl-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libglobus-rsl-doc Version: 10.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m5.5s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libglobus-rsl-doc/changelog.Debian.gz (libglobus-rsl-doc) != /usr/share/doc/libglobus-rsl-dev/changelog.Debian.gz (libglobus-rsl-dev:amd64) /usr/share/doc/libglobus-rsl-doc/copyright (libglobus-rsl-doc) != /usr/share/doc/libglobus-rsl-dev/copyright (libglobus-rsl-dev:amd64) cheers, Andreas libglobus-rsl-doc_10.8-1.log.gz Description: application/gzip
Bug#768264: libglobus-scheduler-event-generator-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libglobus-scheduler-event-generator-doc Version: 5.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m11.2s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libglobus-scheduler-event-generator-doc/changelog.Debian.gz (libglobus-scheduler-event-generator-doc) != /usr/share/doc/libglobus-scheduler-event-generator-dev/changelog.Debian.gz (libglobus-scheduler-event-generator-dev:amd64) /usr/share/doc/libglobus-scheduler-event-generator-doc/copyright (libglobus-scheduler-event-generator-doc) != /usr/share/doc/libglobus-scheduler-event-generator-dev/copyright (libglobus-scheduler-event-generator-dev:amd64) cheers, Andreas libglobus-scheduler-event-generator-doc_5.6-1.log.gz Description: application/gzip
Bug#768266: libmyproxy-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libmyproxy-doc Version: 6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m28.2s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libmyproxy-doc/changelog.Debian.gz (libmyproxy-doc) != /usr/share/doc/libmyproxy-dev/changelog.Debian.gz (libmyproxy-dev:amd64) /usr/share/doc/libmyproxy-doc/copyright (libmyproxy-doc) != /usr/share/doc/libmyproxy-dev/copyright (libmyproxy-dev:amd64) cheers, Andreas libmyproxy-doc_6.0-1.log.gz Description: application/gzip
Bug#768267: libonig2-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libonig2-dbg Version: 5.9.5-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m2.5s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libonig2-dbg/changelog.Debian.gz (libonig2-dbg:amd64) != /usr/share/doc/libonig2/changelog.Debian.gz (libonig2:amd64) /usr/share/doc/libonig2-dbg/changelog.gz (libonig2-dbg:amd64) != /usr/share/doc/libonig2/changelog.gz (libonig2:amd64) /usr/share/doc/libonig2-dbg/copyright (libonig2-dbg:amd64) != /usr/share/doc/libonig2/copyright (libonig2:amd64) cheers, Andreas libonig2-dbg_5.9.5-2.log.gz Description: application/gzip
Bug#718062: [PATCH] libnfo: FTBFS: Makefile:2: *** config.mak is not present,, run configure !. Stop.
Source: libnfo Version: 1.0.1-1 Followup-For: Bug #718062 Tags: patch X-Debbugs-Cc: bren...@br.ibm.com User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, The issue reported here can be easily resolved using a 'dh_clean' rule in the debian/rules file. The patch attached here helps the package to build smoothly. Thanks for considering the patch! Thanks and regards, Brahadambal Srinivasan -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16-trunk-powerpc64le (SMP w/32 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash dpkg-source: warning: extracting unsigned source package (/home/latha/libnfo/libnfo_1.0.1-1.dsc) diff -Nru libnfo-1.0.1/debian/rules libnfo-1.0.1/debian/rules --- libnfo-1.0.1/debian/rules 2014-11-06 07:20:20.0 + +++ libnfo-1.0.1/debian/rules 2010-01-27 09:42:32.0 + @@ -21,7 +21,4 @@ override_dh_strip: dh_strip --dbg-package=libnfo1-dbg -clean: - dh_clean - .PHONY: override_dh_auto_configure override_dh_strip
Bug#706877: insserv: breaks dist-upgrade by installing before packages fix their init scripts
On 20/10/13 at 09:33 +0200, Petter Reinholdtsen wrote: [Jamin W. Collins] It may be bogus or incomplete boot script ordering information, but it previously worked, keep that in mind. One does not expect a Debian dist-upgrade from one stable release to another to result in a non-functional system. Sure. But the fact that the ordering was not broken when the dependencies was ignored do not really matter much. 'ignoring ordering loops' is another way to say 'generate incorrect boot sequence', which might result in a non-bootable system. So there is no safe way to continue when the boot ordering can not be trusted, and update-rc.d refuse to upgrade more packages when this happen as a safe-guard against silently breaking the boot (which would only be discovered the next time the machine is booted, instead of when the upgrade happen). The former effectively left me locked out of my systems. I had to reboot every one of them to a single user root session to fix them as my user existed only in LDAP and then unrelated init scripts caused the upgrade to abort in such a way that my user could no longer be validated for sudo. Had the upgrade proceeded, the system would have been in complete working order (AFAICT). Did you run 'sudo apt-get dist-upgrade', and was unable to run a new sudo command when the upgrade failed? Perhaps a safer approach is to use 'sudo -i' and then run 'apt-get dist-upgrade' with a root shell to make sure you can recover when something go wrong? Anyway, I am positive to try to figure out way to avoid breaking systems where upgrading packages in a different order would work, but do not know which packages have incorrect dependencies in earlier versions leading to dependency loops and thus do not know how to do it. :) Hi, Is this bug still a problem for wheezy-jessie upgrades? One could argue that all packages with problematic dependencies could likely have been fixed during the jessie cycle. Looking at bugs mentioned in this bug log: #651037: a duplicate of #650995; fixed in wheezy #680223: caused by munin-node, fixed in wheezy #695751: discussion on dependencies on packages themselves depending on $all, either implicitely or explicitely (because they would have no LSB headers). There are only a few packages remaining with missing LSB headers[1], and none of them seem likely to be depended. There are more that depend explicitely on $all[2] (lintian has a check for that), and maybe they should be fixed, but again, none of them seem likely to be depended on, except maybe cloud-init. So I believe that in practice, this problem is not so severe. #589238: several (old) reports of dependency loops. (last activity in 2011) Given that this bug was present (unfixed) in wheezy, and the situation can only have improved since then, I think that this bug should be jessie-ignore'd. [1] https://lintian.debian.org/tags/init.d-script-missing-lsb-section.html [2] https://lintian.debian.org/tags/init.d-script-depends-on-all-virtual-facility.html - Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768269: appdata-tools and appstream-util: error when trying to install together
Package: appstream-util,appdata-tools Version: appstream-util/0.3.2-1 Version: appdata-tools/0.1.7-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-11-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 30% Extracting templates from packages: 61% Extracting templates from packages: 91% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libgmp10:amd64. (Reading database ... 10892 files and directories currently installed.) Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-3_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-3) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-3_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2) ... Preparing to unpack .../libp11-kit0_0.20.7-1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.7-1) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.2-2_amd64.deb ... Unpacking libtasn1-6:amd64 (4.2-2) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.8-3_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.8-3) ... Selecting previously unselected package libkeyutils1:amd64. Preparing to unpack .../libkeyutils1_1.5.9-5_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-5) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12.1+dfsg-11_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12.1+dfsg-11_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12.1+dfsg-11_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12.1+dfsg-11_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.2+dfsg1-1_amd64.deb ... Unpacking libxml2:amd64 (2.9.2+dfsg1-1) ... Selecting previously unselected package libglib2.0-0:amd64. Preparing to unpack .../libglib2.0-0_2.42.0-2_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.42.0-2) ... Selecting previously unselected package libatk1.0-data. Preparing to unpack .../libatk1.0-data_2.14.0-1_all.deb ... Unpacking libatk1.0-data (2.14.0-1) ... Selecting previously unselected package libatk1.0-0:amd64. Preparing to unpack .../libatk1.0-0_2.14.0-1_amd64.deb ... Unpacking libatk1.0-0:amd64 (2.14.0-1) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6) ... Selecting previously unselected package libpng12-0:amd64. Preparing to unpack .../libpng12-0_1.2.50-2_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.50-2) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../libfreetype6_2.5.2-2_amd64.deb ... Unpacking libfreetype6:amd64 (2.5.2-2) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0030_all.deb ... Moving old data out of the way Unpacking ucf (3.0030) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../fonts-dejavu-core_2.34-1_all.deb ... Unpacking fonts-dejavu-core (2.34-1) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../fontconfig-config_2.11.0-6.1_all.deb ... Unpacking fontconfig-config (2.11.0-6.1) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../libfontconfig1_2.11.0-6.1_amd64.deb ... Unpacking libfontconfig1:amd64 (2.11.0-6.1) ... Selecting previously unselected package libpixman-1-0:amd64. Preparing to unpack .../libpixman-1-0_0.32.6-3_amd64.deb ... Unpacking libpixman-1-0:amd64 (0.32.6-3) ... Selecting previously unselected package libxau6:amd64. Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ... Unpacking libxau6:amd64 (1:1.0.8-1) ... Selecting previously unselected package libxdmcp6:amd64. Preparing to unpack .../libxdmcp6_1%3a1.1.1-1_amd64.deb ... Unpacking libxdmcp6:amd64 (1:1.1.1-1) ... Selecting previously unselected package libxcb1:amd64. Preparing to unpack .../libxcb1_1.10-3_amd64.deb ... Unpacking
Bug#768270: librubberband-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: librubberband-dev Version: 1.8.1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m5.2s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/librubberband-dev/changelog.Debian.gz (librubberband-dev:amd64) != /usr/share/doc/librubberband2/changelog.Debian.gz (librubberband2:amd64) /usr/share/doc/librubberband-dev/changelog.gz (librubberband-dev:amd64) != /usr/share/doc/librubberband2/changelog.gz (librubberband2:amd64) /usr/share/doc/librubberband-dev/copyright (librubberband-dev:amd64) != /usr/share/doc/librubberband2/copyright (librubberband2:amd64) cheers, Andreas librubberband-dev_1.8.1-5.log.gz Description: application/gzip
Bug#768272: lilypond-doc: unhandled symlink to directory conversion: /usr/share/info/lilypond
Package: lilypond-doc Version: 2.18.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m23.9s INFO: dirname part contains a symlink: /usr/share/info/lilypond/00 (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/00 (?) /usr/share/info/lilypond/00/lily-1d0bbe5b.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/00/lily-1d0bbe5b.png (?) /usr/share/info/lilypond/00/lily-21876455.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/00/lily-21876455.png (?) /usr/share/info/lilypond/00/lily-3b688333.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/00/lily-3b688333.png (?) /usr/share/info/lilypond/00/lily-43d93de7.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/00/lily-43d93de7.png (?) /usr/share/info/lilypond/ff/lily-f31b0618.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ff/lily-f31b0618.png (?) /usr/share/info/lilypond/ff/lily-f6ebaf30.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ff/lily-f6ebaf30.png (?) /usr/share/info/lilypond/ff/lily-f8c03253.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ff/lily-f8c03253.png (?) /usr/share/info/lilypond/ly-examples (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ly-examples (?) /usr/share/info/lilypond/ly-examples/ancient-headword.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ly-examples/ancient-headword.png (?) /usr/share/info/lilypond/ly-examples/aucun-snippet.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ly-examples/aucun-snippet.png (?) /usr/share/info/lilypond/ly-examples/bach-bwv610.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ly-examples/bach-bwv610.png (?) /usr/share/info/lilypond/ly-examples/bach-schenker.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ly-examples/bach-schenker.png (?) /usr/share/info/lilypond/ly-examples/cary.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/ly-examples/cary.png (?) /usr/share/info/lilypond/pictures/text-input-parts-single-output.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/pictures/text-input-parts-single-output.png (?) /usr/share/info/lilypond/pictures/text-input-pop-annotate.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/pictures/text-input-pop-annotate.png (?) /usr/share/info/lilypond/pictures/text-input-pop-output.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/pictures/text-input-pop-output.png (?) /usr/share/info/lilypond/pictures/text-input-score-annotate.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/pictures/text-input-score-annotate.png (?) /usr/share/info/lilypond/pictures/text-input-score-output.png (lilypond-doc) != /usr/share/doc/lilypond/html/Documentation/pictures/text-input-score-output.png (?) cheers, Andreas lilypond-doc_2.18.2-3.log.gz Description: application/gzip
Bug#768275: python-whoosh-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-whoosh-doc Version: 2.5.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m0.9s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-whoosh-doc/NEWS.Debian.gz (python-whoosh-doc) != /usr/share/doc/python-whoosh/NEWS.Debian.gz (python-whoosh) /usr/share/doc/python-whoosh-doc/changelog.Debian.gz (python-whoosh-doc) != /usr/share/doc/python-whoosh/changelog.Debian.gz (python-whoosh) /usr/share/doc/python-whoosh-doc/copyright (python-whoosh-doc) != /usr/share/doc/python-whoosh/copyright (python-whoosh) /usr/share/doc/python-whoosh-doc/html (python-whoosh-doc) != /usr/share/doc/python-whoosh/html (?) /usr/share/doc/python-whoosh-doc/html/_sources (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/_sources (?) /usr/share/doc/python-whoosh-doc/html/_sources/analysis.txt (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/_sources/analysis.txt (?) /usr/share/doc/python-whoosh-doc/html/_sources/api (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/_sources/api (?) /usr/share/doc/python-whoosh-doc/html/_sources/api/analysis.txt (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/_sources/api/analysis.txt (?) /usr/share/doc/python-whoosh-doc/html/tech (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/tech (?) /usr/share/doc/python-whoosh-doc/html/tech/backend.html (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/tech/backend.html (?) /usr/share/doc/python-whoosh-doc/html/tech/filedb.html (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/tech/filedb.html (?) /usr/share/doc/python-whoosh-doc/html/tech/index.html (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/tech/index.html (?) /usr/share/doc/python-whoosh-doc/html/threads.html (python-whoosh-doc) != /usr/share/doc/python-whoosh/html/threads.html (?) cheers, Andreas python-whoosh-doc_2.5.7-2.log.gz Description: application/gzip
Bug#768276: voms-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: voms-doc Version: 2.0.11-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 0m56.6s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/voms-doc/changelog.Debian.gz (voms-doc) != /usr/share/doc/voms-dev/changelog.Debian.gz (voms-dev) /usr/share/doc/voms-doc/changelog.gz (voms-doc) != /usr/share/doc/voms-dev/changelog.gz (voms-dev) /usr/share/doc/voms-doc/copyright (voms-doc) != /usr/share/doc/voms-dev/copyright (voms-dev) cheers, Andreas voms-doc_2.0.11-3.log.gz Description: application/gzip
Processed: reassign 768223 to src:direwolf
Processing commands for cont...@bugs.debian.org: reassign 768223 src:direwolf 1.0-1 Bug #768223 [direwolf,direwolf-doc] direwolf, direwolf-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/ll2utm, /usr/share/man/man1/ll2utm.1.gz Warning: Unknown package 'direwolf-doc' Bug reassigned from package 'direwolf,direwolf-doc' to 'src:direwolf'. No longer marked as found in versions 1.0-1. Ignoring request to alter fixed versions of bug #768223 to the same values previously set Bug #768223 [src:direwolf] direwolf, direwolf-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/ll2utm, /usr/share/man/man1/ll2utm.1.gz Marked as found in versions direwolf/1.0-1. thanks Stopping processing here. Please contact me if you need assistance. -- 768223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768223 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#768270: librubberband-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Followup-For: Bug #768270 Similer problems in rubberband-vamp and rubberband-ladspa: 1m8.7s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/rubberband-vamp/changelog.Debian.gz (rubberband-vamp) != /usr/share/doc/librubberband2/changelog.Debian.gz (librubberband2:amd64) /usr/share/doc/rubberband-vamp/changelog.gz (rubberband-vamp) != /usr/share/doc/librubberband2/changelog.gz (librubberband2:amd64) /usr/share/doc/rubberband-vamp/copyright (rubberband-vamp) != /usr/share/doc/librubberband2/copyright (librubberband2:amd64) 1m3.7s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/rubberband-ladspa/changelog.Debian.gz (rubberband-ladspa) != /usr/share/doc/librubberband2/changelog.Debian.gz (librubberband2:amd64) /usr/share/doc/rubberband-ladspa/changelog.gz (rubberband-ladspa) != /usr/share/doc/librubberband2/changelog.gz (librubberband2:amd64) /usr/share/doc/rubberband-ladspa/copyright (rubberband-ladspa) != /usr/share/doc/librubberband2/copyright (librubberband2:amd64) cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765156: flashproxy is marked for autoremoval from testing
Hi, Holger Levsen wrote (05 Nov 2014 14:40:06 GMT) : 1. bumping the standards version now is often perceived as unwanted noise by those reviewing the changes to decide whether to let it enter jessie. leave it now, but next time please only include non-cosmetic changes _if_ you add non ron-RC fixes at all. Definitely. See the freeze [policy] and the various messages pointing to it, sent by the release team to d-d-a. [policy] https://release.debian.org/jessie/freeze_policy.html Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768279: r-cran-epi: unhandled symlink to directory conversion: /usr/lib/R/site-library/Epi/doc
Package: r-cran-epi Version: 1.1.67-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m15.9s INFO: dirname part contains a symlink: /usr/lib/R/site-library/Epi/doc/Follow-up.R (r-cran-epi) != /usr/share/doc/r-cran-epi/Follow-up.R (?) /usr/lib/R/site-library/Epi/doc/Follow-up.pdf (r-cran-epi) != /usr/share/doc/r-cran-epi/Follow-up.pdf (?) /usr/lib/R/site-library/Epi/doc/Follow-up.rnw (r-cran-epi) != /usr/share/doc/r-cran-epi/Follow-up.rnw (?) /usr/lib/R/site-library/Epi/doc/index.html (r-cran-epi) != /usr/share/doc/r-cran-epi/index.html (?) /usr/lib/R/site-library/Epi/doc/sim-Lexis.R (r-cran-epi) != /usr/share/doc/r-cran-epi/sim-Lexis.R (?) /usr/lib/R/site-library/Epi/doc/sim-Lexis.pdf (r-cran-epi) != /usr/share/doc/r-cran-epi/sim-Lexis.pdf (?) /usr/lib/R/site-library/Epi/doc/sim-Lexis.rnw (r-cran-epi) != /usr/share/doc/r-cran-epi/sim-Lexis.rnw (?) cheers, Andreas r-cran-epi_1.1.67-2.log.gz Description: application/gzip
Bug#768285: python-pyvorbis-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-pyvorbis-dbg Version: 1.5-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m14.2s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-ogg-dbg/changelog.Debian.gz (python-ogg-dbg) != /usr/share/doc/python-ogg/changelog.Debian.gz (python-ogg) /usr/share/doc/python-ogg-dbg/changelog.gz (python-ogg-dbg) != /usr/share/doc/python-ogg/changelog.gz (python-ogg) /usr/share/doc/python-ogg-dbg/copyright (python-ogg-dbg) != /usr/share/doc/python-ogg/copyright (python-ogg) /usr/share/doc/python-pyvorbis-dbg/changelog.Debian.gz (python-pyvorbis-dbg) != /usr/share/doc/python-pyvorbis/changelog.Debian.gz (python-pyvorbis) /usr/share/doc/python-pyvorbis-dbg/changelog.gz (python-pyvorbis-dbg) != /usr/share/doc/python-pyvorbis/changelog.gz (python-pyvorbis) /usr/share/doc/python-pyvorbis-dbg/copyright (python-pyvorbis-dbg) != /usr/share/doc/python-pyvorbis/copyright (python-pyvorbis) cheers, Andreas python-pyvorbis-dbg_1.5-3.log.gz Description: application/gzip
Bug#768283: librrd-ruby: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: librrd-ruby Version: 1.4.8-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m9.5s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/librrd-ruby/CONTRIBUTORS.gz (librrd-ruby) != /usr/share/doc/librrd-ruby1.8/CONTRIBUTORS.gz (librrd-ruby1.8) /usr/share/doc/librrd-ruby/NEWS.Debian.gz (librrd-ruby) != /usr/share/doc/librrd-ruby1.8/NEWS.Debian.gz (librrd-ruby1.8) /usr/share/doc/librrd-ruby/NEWS.gz (librrd-ruby) != /usr/share/doc/librrd-ruby1.8/NEWS.gz (librrd-ruby1.8) /usr/share/doc/librrd-ruby/changelog.Debian.gz (librrd-ruby) != /usr/share/doc/librrd-ruby1.8/changelog.Debian.gz (librrd-ruby1.8) /usr/share/doc/librrd-ruby/changelog.gz (librrd-ruby) != /usr/share/doc/librrd-ruby1.8/changelog.gz (librrd-ruby1.8) /usr/share/doc/librrd-ruby/copyright (librrd-ruby) != /usr/share/doc/librrd-ruby1.8/copyright (librrd-ruby1.8) cheers. Andreas librrd-ruby_1.4.8-1.1.log.gz Description: application/gzip
Bug#767845: marked as done (flightgear: Frequently crashes when using TerraSync)
Your message dated Thu, 06 Nov 2014 08:59:48 + with message-id 545b3884.9010...@zoho.com and subject line simgear now rebuilt has caused the Debian Bug report #767845, regarding flightgear: Frequently crashes when using TerraSync 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.) -- 767845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flightgear Version: 3.0.0-3 Severity: grave Justification: makes TerraSync almost unusable This crash is due to #765855 which has just been fixed in libopenscenegraph100. However, even after upgrading libopenscenegraph100 to 3.2.1-5 the crashes still happen quite frequently, ruining many perfectly good flights (4 times in the past 24 hours for me alone and several people reported similar crashes). The frequency of the crashes appears to increase as new TerraSync data becomes available. According to comment #59, it is necessary to recompile flightgear and possibly simgear in order to benefit from the bug fix. Therefore please upload 3.0.0-4 :) -- Ludovic Brenta. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (1, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flightgear depends on: ii flightgear-data-all 3.0.0-1 ii freeglut3 2.8.1-2 ii libc6 2.19-12 ii libdbus-1-3 1.8.8-2 ii libgcc1 1:4.9.1-16 ii libgl1-mesa-glx [libgl1] 10.3.1-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgsm1 1.0.13-4 ii libice6 2:1.0.9-1 ii libjpeg62-turbo 1:1.3.1-8 ii libopenal11:1.15.1-5 ii libopenscenegraph100 3.2.1-5 ii libopenthreads20 3.2.1-5 ii libplib1 1.8.5-7 ii libpng12-01.2.50-2 ii libsimgearcore3.0.0 3.0.0-6 ii libsimgearscene3.0.0 3.0.0-6 ii libsm62:1.2.2-1 ii libspeex1 1.2~rc1.2-1 ii libspeexdsp1 1.2~rc1.2-1 ii libsqlite3-0 3.8.7-1 ii libstdc++64.9.1-16 ii libudev1 215-5+b1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxi62:1.7.4-1 ii libxmu6 2:1.1.2-1 ii zlib1g1:1.2.8.dfsg-2 flightgear recommends no packages. flightgear suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- simgear has now been recompiled against a fixed openscenegraph, so installing libsimgearscene3.0.0 3.0.0-6+b1 should fix this problem. (This version may not have reached all mirrors yet. It does not appear to be necessary to also recompile flightgear, or to actually install the fixed libopenscenegraph100.) If installing this doesn't help, please reopen the bug.---End Message---
Bug#768286: python{, 3}-zope.interface-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python3-zope.interface-dbg,python-zope.interface-dbg Version: 4.1.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m47.2s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python3-zope.interface-dbg/changelog.Debian.gz (python3-zope.interface-dbg) != /usr/share/doc/python3-zope.interface/changelog.Debian.gz (python3-zope.interface) /usr/share/doc/python3-zope.interface-dbg/copyright (python3-zope.interface-dbg) != /usr/share/doc/python3-zope.interface/copyright (python3-zope.interface) 1m8.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/python-zope.interface-dbg/changelog.Debian.gz (python-zope.interface-dbg) != /usr/share/doc/python-zope.interface/changelog.Debian.gz (python-zope.interface) /usr/share/doc/python-zope.interface-dbg/copyright (python-zope.interface-dbg) != /usr/share/doc/python-zope.interface/copyright (python-zope.interface) cheers, Andreas python3-zope.interface-dbg_4.1.1-2.log.gz Description: application/gzip
Bug#768287: libnetfilter-log{-dev, 1-dbg}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libnetfilter-log-dev,libnetfilter-log1-dbg Version: 1.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m36.6s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libnetfilter-log-dev/changelog.Debian.gz (libnetfilter-log-dev:amd64) != /usr/share/doc/libnetfilter-log1/changelog.Debian.gz (libnetfilter-log1:amd64) /usr/share/doc/libnetfilter-log-dev/copyright (libnetfilter-log-dev:amd64) != /usr/share/doc/libnetfilter-log1/copyright (libnetfilter-log1:amd64) 1m27.0s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libnetfilter-log1-dbg/changelog.Debian.gz (libnetfilter-log1-dbg:amd64) != /usr/share/doc/libnetfilter-log1/changelog.Debian.gz (libnetfilter-log1:amd64) /usr/share/doc/libnetfilter-log1-dbg/copyright (libnetfilter-log1-dbg:amd64) != /usr/share/doc/libnetfilter-log1/copyright (libnetfilter-log1:amd64) cheers, Andreas libnetfilter-log-dev_1.0.1-1.log.gz Description: application/gzip
Bug#768275: python-whoosh-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On Thu, Nov 06, 2014 at 09:32:21AM +0100, Andreas Beckmann wrote: It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. ---end quoted text--- I thought that I have fixed this already by adding: debian/python-whoosh.maintscript with the following line: symlink_to_dir /usr/share/doc/python-whoosh /usr/share/doc/python-whoosh-doc 2.4.1-1~ python-whoosh So why isn't that working ? -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Bug#767297: marked as done (spamassassin: Argument 0.80_2 isn't numeric in numeric lt ())
Your message dated Thu, 06 Nov 2014 09:19:32 + with message-id e1xmje4-0001o9...@franck.debian.org and subject line Bug#766718: fixed in libnet-dns-perl 0.81-1 has caused the Debian Bug report #766718, regarding spamassassin: Argument 0.80_2 isn't numeric in numeric lt () 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.) -- 766718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: spamassassin Version: 3.4.0-3 Severity: normal Having just updated my packages (spamassassin and others), I'm now seeing the following in my logs: spamd[6169]: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm line 214. spamd[6169]: Argument 0.80_2 isn't numeric in numeric lt () at /usr/share/perl5/Mail/SpamAssassin/Dns.pm line 521. spamd[6988]: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/DKIM/PublicKey.pm line 113. spamd[6988]: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/DKIM/Policy.pm line 81. Francois -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.21 pn libarchive-tar-perl none ii libhtml-parser-perl 3.71-1+b2 ii libnet-dns-perl 0.80.2-2 ii libnetaddr-ip-perl 4.075+dfsg-1+b1 ii libsocket6-perl 0.25-1+b1 ii libsys-hostname-long-perl 1.4-3 ii libwww-perl 6.08-1 ii perl5.20.1-2 ii perl-modules [libio-zlib-perl] 5.20.1-2 Versions of packages spamassassin recommends: ii gnupg 1.4.18-4 ii libio-socket-inet6-perl2.72-1 ii libmail-spf-perl 2.9.0-3 ii perl [libsys-syslog-perl] 5.20.1-2 ii sa-compile 3.4.0-3 ii spamc 3.4.0-3 Versions of packages spamassassin suggests: ii libdbi-perl 1.631-3+b1 ii libio-socket-ssl-perl 2.002-1 ii libmail-dkim-perl 0.40-1 ii perl [libcompress-zlib-perl] 5.20.1-2 ii pyzor 1:0.5.0-2 ii razor 1:2.85-4.1+b1 -- Configuration Files: /etc/spamassassin/init.pre changed: loadplugin Mail::SpamAssassin::Plugin::RelayCountry loadplugin Mail::SpamAssassin::Plugin::URIDNSBL loadplugin Mail::SpamAssassin::Plugin::Hashcash loadplugin Mail::SpamAssassin::Plugin::SPF /etc/spamassassin/v310.pre changed: loadplugin Mail::SpamAssassin::Plugin::Pyzor loadplugin Mail::SpamAssassin::Plugin::Razor2 loadplugin Mail::SpamAssassin::Plugin::SpamCop loadplugin Mail::SpamAssassin::Plugin::AntiVirus loadplugin Mail::SpamAssassin::Plugin::AutoLearnThreshold loadplugin Mail::SpamAssassin::Plugin::TextCat loadplugin Mail::SpamAssassin::Plugin::WhiteListSubject loadplugin Mail::SpamAssassin::Plugin::MIMEHeader loadplugin Mail::SpamAssassin::Plugin::ReplaceTags /etc/spamassassin/v320.pre changed: loadplugin Mail::SpamAssassin::Plugin::Check loadplugin Mail::SpamAssassin::Plugin::HTTPSMismatch loadplugin Mail::SpamAssassin::Plugin::URIDetail loadplugin Mail::SpamAssassin::Plugin::Bayes loadplugin Mail::SpamAssassin::Plugin::BodyEval loadplugin Mail::SpamAssassin::Plugin::DNSEval loadplugin Mail::SpamAssassin::Plugin::HTMLEval loadplugin Mail::SpamAssassin::Plugin::HeaderEval loadplugin Mail::SpamAssassin::Plugin::MIMEEval loadplugin Mail::SpamAssassin::Plugin::RelayEval loadplugin Mail::SpamAssassin::Plugin::URIEval loadplugin Mail::SpamAssassin::Plugin::WLBLEval loadplugin Mail::SpamAssassin::Plugin::VBounce loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody loadplugin Mail::SpamAssassin::Plugin::ASN loadplugin Mail::SpamAssassin::Plugin::ImageInfo -- no debconf information ---End Message--- ---BeginMessage--- Source: libnet-dns-perl Source-Version: 0.81-1 We believe that the bug you reported is fixed in the latest version of libnet-dns-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 766...@bugs.debian.org, and the maintainer will reopen the bug
Bug#766718: marked as done (Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm)
Your message dated Thu, 06 Nov 2014 09:19:32 + with message-id e1xmje4-0001o9...@franck.debian.org and subject line Bug#766718: fixed in libnet-dns-perl 0.81-1 has caused the Debian Bug report #766718, regarding Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm 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.) -- 766718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: spamassassin Version: 3.4.0-3 Severity: minor I get this warning every time I run spamassassin: $ spamassassin /dev/null /dev/null Oct 25 10:48:42.555 [5732] warn: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm line 214. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.17-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.21 pn libarchive-tar-perl none ii libhtml-parser-perl 3.71-1+b2 ii libnet-dns-perl 0.80.2-2 ii libnetaddr-ip-perl 4.075+dfsg-1+b1 ii libsocket6-perl 0.25-1+b1 ii libsys-hostname-long-perl 1.4-3 ii libwww-perl 6.08-1 ii perl5.20.1-2 ii perl-modules [libio-zlib-perl] 5.20.1-2 Versions of packages spamassassin recommends: ii gnupg 1.4.18-4 ii libio-socket-inet6-perl2.72-1 pn libmail-spf-perl none ii perl [libsys-syslog-perl] 5.20.1-2 pn sa-compile none pn spamc none Versions of packages spamassassin suggests: pn libdbi-perl none ii libio-socket-ssl-perl 2.002-1 pn libmail-dkim-perl none ii perl [libcompress-zlib-perl] 5.20.1-2 pn pyzor none pn razor none -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: libnet-dns-perl Source-Version: 0.81-1 We believe that the bug you reported is fixed in the latest version of libnet-dns-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated libnet-dns-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Oct 2014 15:04:31 +0100 Source: libnet-dns-perl Binary: libnet-dns-perl Architecture: source Version: 0.81-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libnet-dns-perl - Perform DNS queries from a Perl script Closes: 766718 Changes: libnet-dns-perl (0.81-1) unstable; urgency=medium . * New upstream version 0.81 (Closes: #766718) Checksums-Sha1: 4a5dd06296c338c3fa280594f7e5d0c0f936bc44 2240 libnet-dns-perl_0.81-1.dsc b0f08e87ccd8a063196db1a57ef1acd818bf 197700 libnet-dns-perl_0.81.orig.tar.gz a5c7bcd37dd399d98ea4a8714fda4a04ff7062f9 7272 libnet-dns-perl_0.81-1.debian.tar.xz Checksums-Sha256: cc5e60d42c749bc486f3e972e23a786ef252b82fc12ce2bbd7d5e9f90de37acf 2240 libnet-dns-perl_0.81-1.dsc b36c8ead6edf68da5d9de2b0a22a47d7216e2d7eb52c8cde96724988f68a6d46 197700 libnet-dns-perl_0.81.orig.tar.gz 0ad664d1d762e31a1cba5dabd4354d20d90480c02282b282b593850900aeddac 7272 libnet-dns-perl_0.81-1.debian.tar.xz Files: f3795d5a27b02b5f07e77eb1f670e9ba 2240 perl optional libnet-dns-perl_0.81-1.dsc 26375d4310beb108b0e2b3bf30403ee5 197700 perl optional libnet-dns-perl_0.81.orig.tar.gz b4de90b38195bc151be51081b7bee318 7272 perl optional libnet-dns-perl_0.81-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUWyTTXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
Bug#768288: linux: FTBFS on i386: incomplete migration from 486 to 586 flavour
Source: linux Version: 3.16.7-1 Severity: serious Justification: fails to build from source (but built successfully in the past) linux/3.16.7-1 has this change: * [i386] Rename 486 flavour to 586, as it has not worked on 486 processors since we enabled CC_STACKPROTECTOR (Closes: #766105) - Select M586TSC instead of M486 but the i386 build log indicates that it is still trying (and now failing) to run kernel-wedge for the 486 flavour. Regards, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768289: linux-image-3.16-3-amd64: Suspend/sleep causes laptop to never wake up, lose data
Package: src:linux Version: 3.16.5-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? When I close the lid on my laptop, it goes to sleep (suspend). * What was the outcome of this action? When I open it up, the system never wakes up, which equals to system crash and data loss. * What outcome did you expect instead? The system should come out of suspend/sleep and resume operation, which works fine on Windows 7 Pro on this very same PC. (Dual boot) More info: Hardware: Toshiba Portege Z30 Ultrabook, Intel Core i7 4600U DMI decode: http://pastebin.com/30Jhfr77 lspci -v: http://pastebin.com/sBWXCGjM The problem could be upower, or kernel itself. This bug makes Debian a non-functional on this laptop. Sadly I can't use Debian 7.0 Wheezy on it, due to lack of Ethernet drivers. I am using Debian GNU/Linux 8.0 Jessie BETA -- Package-specific info: ** Version: Linux version 3.16-3-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-12) ) #1 SMP Debian 3.16.5-1 (2014-10-10) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-3-amd64 root=UUID=7db0fed9-1e96-400d-aa67-6f207494c318 ro nomodeset quiet ** Not tainted ** Kernel log: [2.889609] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.889612] sound hdaudioC1D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.889613] sound hdaudioC1D0:mono: mono_out=0x0 [2.889615] sound hdaudioC1D0:inputs: [2.889617] sound hdaudioC1D0: Mic=0x19 [2.889619] sound hdaudioC1D0: Internal Mic=0x12 [2.894254] tpm_tis 00:01: 1.2 TPM (device-id 0xB, rev-id 16) [2.896801] mei_me :00:16.0: NFC MEI VERSION: IVN 0x1 Vendor ID 0x1 Type 0x1 [2.896884] media: Linux media interface: v0.10 [2.899023] Linux video capture interface: v2.00 [2.900243] input: PC Speaker as /devices/platform/pcspkr/input/input9 [2.900779] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input7 [2.900818] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input8 [2.902105] usbcore: registered new interface driver cdc_ncm [2.903951] usbcore: registered new interface driver cdc_wdm [2.905371] uvcvideo: Found UVC 1.00 device TOSHIBA Web Camera - FHD (04f2:b3b2) [2.907487] input: TOSHIBA Web Camera - FHD as /devices/pci:00/:00:14.0/usb2/2-7/2-7:1.0/input/input11 [2.909160] usbcore: registered new interface driver uvcvideo [2.909163] USB Video Class driver (1.1.1) [2.909735] cdc_mbim 2-4:2.12: cdc-wdm0: USB WDM device [2.909898] cdc_mbim 2-4:2.12 wwan0: register 'cdc_mbim' at usb-:00:14.0-4, CDC MBIM, 9e:53:13:62:95:ce [2.909920] usbcore: registered new interface driver cdc_mbim [2.910139] snd_hda_intel :00:03.0: Cannot turn on display power on i915 [2.911142] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [2.912241] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [2.912730] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [2.912776] AVX2 version of gcm_enc/dec engaged. [2.917712] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [2.924290] alg: No test for crc32 (crc32-pclmul) [2.945188] usb 2-6.3.2: new full-speed USB device number 7 using xhci_hcd [2.965220] iTCO_vendor_support: vendor-support=0 [2.965667] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [2.965701] iTCO_wdt: Found a Lynx Point_LP TCO device (Version=2, TCOBASE=0x1860) [2.965838] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [2.975733] Adding 2103292k swap on /dev/sda6. Priority:-1 extents:1 across:2103292k SSFS [2.999458] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null) [3.010100] systemd-journald[166]: Received request to flush runtime journal from PID 1 [3.031414] usb 2-6.3.2: New USB device found, idVendor=0b97, idProduct=7772 [3.031418] usb 2-6.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.031420] usb 2-6.3.2: Product: O2Micro CCID SC Reader [3.031422] usb 2-6.3.2: Manufacturer: O2 [3.031519] usb 2-6.3.2: ep 0x81 - rounding interval to 1024 microframes, ep desc says 2040 microframes [3.048094] toshiba_acpi: Accelerometer not supported [3.187490] e1000e :00:19.0: irq 58 for MSI/MSI-X [3.270648] usb 2-8: new full-speed USB device number 8 using xhci_hcd [3.282077] random: nonblocking pool is initialized [3.290638] e1000e :00:19.0: irq 58 for MSI/MSI-X [3.290744] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [3.296232] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [3.399420] usb 2-8: New USB device found, idVendor=8087, idProduct=07dc [3.399421] usb 2-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [3.412408] Bluetooth: Core ver 2.19 [
Bug#764798: RE: Bug#764798: grub2: Grub rescue shell with RAID 6 mdadm over 8 disks
On Thu, 23 Oct 2014 18:20:00 -0500 Mike ctrl...@yahoo.com wrote:
Greetings, anything else needed from me?
Thanks.
This is complete guessing, but could the file, util/deviceiter.c, i.e. the
iteration over devices, have something to do with it? In version
grub2-2.02~beta2, there is this block beginning in line 713 (inside of an
#ifdef __linux__):
/* ATARAID disks. */
for (i = 0; i 8; i++)
{
[...]
}
Interestingly, there is a similar block starting in line 645
/* IDE disks. */
for (i = 0; i 96; i++)
{
[...]
}
which might explain why this problem has not been detected/fixed beforehand.
There weren't probably a lot of users with more than 96 IDE disks …
This can be completely wrong, but if you already have a test setup, you might
get the package (apt-get build-dep grub2; apt-get source grub2) change the
value, rebuild the package (fakeroot dpkg-buildpackage -b -uc -us should
work), install (dpkg -i ...) and test it.
Kind regards
Patrick
signature.asc
Description: This is a digitally signed message part.
Bug#766718: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Control: reassign -1 spamassassin/3.4.0-3
Control: tag -1 upstream patch
-=| Francois Marier, 06.11.2014 12:15:02 +1300 |=-
While I hesitate to bump the severity of this bug to the highest one, it
does break unrelated software (spamassassin).
Spamassassin depends on libnet-dns-perl. That's not unrelated
software. mutt would be an example of unrelated software.
As it stands, several features of SpamAssassin are broken in sid and
jessie due to the unusual version number.
The SpamAssassin upstream have said that this is not a bug in SA but that it
comes from the fact that a pre-release version of Net::DNS was uploaded to
Debian.
I think that SA should not use numeric comparison operators for things
that aren't numbers.
The query for Net::DNS' version could be fixed as:
use version 0.77;
$txtdata_can_provide_a_list = version-parse(Net::DNS-VERSION) =
version-parse('0.69');
I assume this can be fixed by uploading the next upstream release of
Net::DNS?
... or by patching lib/Mail/SpamAssassin/Plugin/AskDNS.pm in SA. Note
that version 0.77 is provided by perl from version 5.10.1 on.
Reassigning back since (1) IMO the bug lies in SA and (2) even if
Net-DNS 0.81 reaches testing, SA needs an upload anyway with bumped
dependency version. Not sure what severity to choose, so leaving that
to SA maintainer.
I could prepare a full-blown debdiff with the above patch if that
would help.
-- dam
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#766718: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Processing control commands:
reassign -1 spamassassin/3.4.0-3
Unknown command or malformed arguments to command.
tag -1 upstream patch
Bug #766718 {Done: Ondřej Surý ond...@debian.org} [libnet-dns-perl] Argument
0.80_2 isn't numeric in numeric ge (=) at
/usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Bug #767297 {Done: Ondřej Surý ond...@debian.org} [libnet-dns-perl]
spamassassin: Argument 0.80_2 isn't numeric in numeric lt ()
Added tag(s) upstream and patch.
Added tag(s) upstream and patch.
--
766718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766718
767297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 766718 to spamassassin
Processing commands for cont...@bugs.debian.org:
reassign 766718 spamassassin 3.4.0-3
Bug #766718 {Done: Ondřej Surý ond...@debian.org} [libnet-dns-perl] Argument
0.80_2 isn't numeric in numeric ge (=) at
/usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Bug #767297 {Done: Ondřej Surý ond...@debian.org} [libnet-dns-perl]
spamassassin: Argument 0.80_2 isn't numeric in numeric lt ()
Bug reassigned from package 'libnet-dns-perl' to 'spamassassin'.
Bug reassigned from package 'libnet-dns-perl' to 'spamassassin'.
No longer marked as found in versions libnet-dns-perl/0.80.2-2.
No longer marked as found in versions libnet-dns-perl/0.80.2-2.
No longer marked as fixed in versions libnet-dns-perl/0.81-1.
No longer marked as fixed in versions libnet-dns-perl/0.81-1.
Bug #766718 {Done: Ondřej Surý ond...@debian.org} [spamassassin] Argument
0.80_2 isn't numeric in numeric ge (=) at
/usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Bug #767297 {Done: Ondřej Surý ond...@debian.org} [spamassassin]
spamassassin: Argument 0.80_2 isn't numeric in numeric lt ()
Marked as found in versions spamassassin/3.4.0-3.
Marked as found in versions spamassassin/3.4.0-3.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
766718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766718
767297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767297
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#768275: python-whoosh-doc: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 2014-11-06 10:11, أحمد المحمودي wrote: I thought that I have fixed this already by adding: debian/python-whoosh.maintscript with the following line: symlink_to_dir /usr/share/doc/python-whoosh /usr/share/doc/python-whoosh-doc 2.4.1-1~ python-whoosh So why isn't that working ? Please follow the discussion at https://bugs.debian.org/768245, seems to be the same problem there. In the worst case there are quite a few packages implementing this in the wrong way: https://piuparts.debian.org/wheezy2jessie/installs_over_symlink_issue.html Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768203: sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli
Andreas Beckmann a...@debian.org writes: during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. Hi, Something is strange here, as sblim-wbemcli was never part of wheezy, thus it is not supposed to be upgraded from there. It installed fine in 'wheezy', then the upgrade to 'jessie' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. The sblim-wbemcli package indeed had a file conflict with python-pywbem 0.7.0-4 (see #679607). However, the conflicting file was renamed in the jessie version of python-pywbem. From the attached log (scroll to the bottom...): Selecting previously unselected package sblim-wbemcli. This sounds more like a new install of sblim-wbemcli, not an upgrade. Unpacking sblim-wbemcli (from .../sblim-wbemcli_1.6.2-8_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/sblim-wbemcli_1.6.2-8_amd64.deb (--unpack): trying to overwrite '/usr/bin/wbemcli', which is also in package python-pywbem 0.7.0-4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/sblim-wbemcli_1.6.2-8_amd64.deb Which is expected to fail with python-pywbem 0.7.0-4 present. However, I wonder how you managed to get into this situation. A wheezy - jessie upgrade should have upgraded python-pywbem to 0.8.0~dev650-1, and you shouldn't experience problems trying to install sblim-wbemcli next to that version. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces Of course the above problem could be declared in the metadata of sblim-wbemcli, though 7.6 does not seem to apply here. 7.4 (Conflicts) seems more appropriate to me, if something really is needed. I initially thought it was not, but you surely know better, please advise me. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768294: freeipa: CVE-2014-7828: password not required when OTP in use
Source: freeipa Version: 4.0.4-2 Severity: grave Tags: security upstream patch Hi, the following vulnerability was published for freeipa. CVE-2014-7828[0]: password not required when OTP in use See [1] for details and upstream ticket[2]. 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] https://security-tracker.debian.org/tracker/CVE-2014-7828 [1] https://www.redhat.com/archives/freeipa-devel/2014-November/msg00068.html [2] https://fedorahosted.org/freeipa/ticket/4690 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766718: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Control: reopen -1 Reopening since the bug is not fixed in spamassassin. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- 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#766718: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Processing control commands:
reopen -1
Bug #766718 {Done: Ondřej Surý ond...@debian.org} [spamassassin] Argument
0.80_2 isn't numeric in numeric ge (=) at
/usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Bug #767297 {Done: Ondřej Surý ond...@debian.org} [spamassassin]
spamassassin: Argument 0.80_2 isn't numeric in numeric lt ()
Bug reopened
Ignoring request to alter fixed versions of bug #766718 to the same values
previously set
Ignoring request to alter fixed versions of bug #767297 to the same values
previously set
--
766718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766718
767297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767297
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#768112: marked as done (slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sinfo)
Your message dated Thu, 06 Nov 2014 10:21:27 + with message-id e1xmkbz-0003ek...@franck.debian.org and subject line Bug#768112: fixed in slurm-llnl 14.03.9-4 has caused the Debian Bug report #768112, regarding slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sinfo 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.) -- 768112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: slurm-client Version: 14.03.9-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package slurm-client. Unpacking slurm-client (from .../slurm-client_14.03.9-3_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/slurm-client_14.03.9-3_amd64.deb (--unpack): trying to overwrite '/usr/bin/sinfo', which is also in package sinfo 0.0.46-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/slurm-client_14.03.9-3_amd64.deb For more information also see https://bugs.debian.org/764441 clurm-client needs to mirror the conflict with sinfo cheers, Andreas sinfo=0.0.46-2_slurm-client=14.03.9-3.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: slurm-llnl Source-Version: 14.03.9-4 We believe that the bug you reported is fixed in the latest version of slurm-llnl, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gennaro Oliva oliv...@na.icar.cnr.it (supplier of updated slurm-llnl 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: Thu, 06 Nov 2014 10:28:03 +0100 Source: slurm-llnl Binary: slurm-wlm slurm-client slurmd slurmctld libslurmdb27 libslurm27 libpmi0 libslurm-dev libslurmdb-dev libpmi0-dev slurm-wlm-doc slurm-wlm-basic-plugins slurm-wlm-basic-plugins-dev sview slurmdbd libslurm-perl libslurmdb-perl slurm-wlm-torque libpam-slurm slurm-llnl slurm-llnl-slurmdbd Architecture: source amd64 all Version: 14.03.9-4 Distribution: unstable Urgency: medium Maintainer: Gennaro Oliva oliv...@na.icar.cnr.it Changed-By: Gennaro Oliva oliv...@na.icar.cnr.it Description: libpam-slurm - PAM module to authenticate using the SLURM resource manager libpmi0- SLURM PMI library implementation libpmi0-dev - SLURM PMI library implementation development files libslurm-dev - SLURM development files libslurm-perl - Perl API for SLURM libslurm27 - Runtime library files for SLURM libslurmdb-dev - SLURM DataBase Daemon development files libslurmdb-perl - Perl API for the SLURM database libslurmdb27 - Runtime library files for the SLURM DataBase Daemon slurm-client - SLURM client side commands slurm-llnl - transitional dummy package for slurm-wlm slurm-llnl-slurmdbd - transitional dummy package for slurmdbd slurm-wlm - Simple Linux Utility for Resource Management slurm-wlm-basic-plugins - SLURM basic plugins slurm-wlm-basic-plugins-dev - SLURM basic plugins development files slurm-wlm-doc - SLURM docmentation slurm-wlm-torque - Torque compatibility wrappers for SLURM slurmctld - SLURM central management daemon slurmd - SLURM compute node daemon slurmdbd - Secure enterprise-wide interface to a database for SLURM sview - GUI to view and modify SLURM state Closes: 768112 Changes: slurm-llnl (14.03.9-4) unstable; urgency=medium . * Declaring slurm-client conflict with sinfo (Closes: #768112) Checksums-Sha1: 585ef2e06464fd05b12e96c68955b9696f5c71bd 3277 slurm-llnl_14.03.9-4.dsc 77cbd769b70b5ac9ab196f837ae68dc434b45d19 45684 slurm-llnl_14.03.9-4.debian.tar.xz 0a954bbe6f3634eed40a88d7ae66559e3cd70131
Bug#747908: libtuxcap: diff for NMU version 1.4.0.dfsg2-2.2
Control: tag -1 pending
Dear maintainer,
I've prepared an NMU for libtuxcap (versioned as 1.4.0.dfsg2-2.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I should delay
it longer.
Regards,
--
Colin Watson [cjwat...@debian.org]
diff -u libtuxcap-1.4.0.dfsg2/debian/changelog libtuxcap-1.4.0.dfsg2/debian/changelog
--- libtuxcap-1.4.0.dfsg2/debian/changelog
+++ libtuxcap-1.4.0.dfsg2/debian/changelog
@@ -1,3 +1,10 @@
+libtuxcap (1.4.0.dfsg2-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use pkg-config to get ImageMagick build flags (closes: #747908).
+
+ -- Colin Watson cjwat...@debian.org Thu, 06 Nov 2014 10:16:34 +
+
libtuxcap (1.4.0.dfsg2-2.1) unstable; urgency=low
* Non-maintainer upload.
diff -u libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch
--- libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch
+++ libtuxcap-1.4.0.dfsg2/debian/patches/cmake_imagemagick.patch
@@ -1,19 +1,56 @@
-Description: cmake's ImageMagick module seems to have changed and now looks
- for the executables, while we only need the libs here
+Description: Use pkg-config to get ImageMagick build flags
Origin: vendor
-Bug-Debian: http://bugs.debian.org/674369
+Bug-Debian: https://bugs.debian.org/747908
Forwarded: no
-Author: gregor herrmann gre...@debian.org
-Last-Update: 2012-06-07
+Author: Colin Watson cjwat...@ubuntu.com
+Last-Update: 2014-10-31
+Index: b/tuxcap/CMakeLists.txt
+===
--- a/tuxcap/CMakeLists.txt
+++ b/tuxcap/CMakeLists.txt
-@@ -16,7 +16,7 @@
+@@ -16,10 +16,10 @@
Find_Package ( SDL REQUIRED )
Find_Package ( SDL_mixer REQUIRED )
-Find_Package ( ImageMagick REQUIRED )
-+Find_Package ( ImageMagick COMPONENTS Magick++ MagickWand MagickCore REQUIRED )
Find_Package ( OpenGL REQUIRED )
- FIND_PACKAGE(ImageMagickLib)
+-FIND_PACKAGE(ImageMagickLib)
++FIND_PACKAGE(PkgConfig REQUIRED)
++PKG_CHECK_MODULES(IMAGEMAGICK REQUIRED Magick++ MagickWand MagickCore)
+
+ FIND_PACKAGE(AudiereLib)
+ IF(AUDIERELIB_FOUND)
+@@ -31,8 +31,7 @@
+${SDL_LIBRARY}
+${SDLMIXER_LIBRARY}
+${OPENGL_LIBRARIES}
+- ${IMAGEMAGICKLIB_LIBRARIES}
+- ${IMAGEMAGICKLIB_CXX_LIBRARIES}
++ ${IMAGEMAGICK_LIBRARIES}
+ )
+
+ IF (PYTHON_LIBRARIES)
+@@ -76,11 +75,7 @@
+ MESSAGE(FATAL_ERROR libSDL requested but not found.)
+ ENDIF(SDL_FOUND)
+
+-IF(IMAGEMAGICKLIB_FOUND)
+-MESSAGE(lib ImageMagick found. ${IMAGEMAGICKLIB_INCLUDE_DIR} ${IMAGEMAGICKLIB_LIBRARIES} ${IMAGEMAGICKLIB_CXX_LIBRARIES})
+-ELSE(IMAGEMAGICKLIB_FOUND)
+-MESSAGE(FATAL_ERROR lib ImageMagick requested but not found.)
+-ENDIF(IMAGEMAGICKLIB_FOUND)
++MESSAGE(lib ImageMagick found. ${IMAGEMAGICK_INCLUDE_DIRS} ${IMAGEMAGICK_LIBRARIES})
+
+ IF(SDLMIXER_FOUND)
+ MESSAGE(libSDL_mixer found. ${SDLMIXER_INCLUDE_DIR} ${SDLMIXER_LIBRARY})
+@@ -96,7 +91,7 @@
+
+ SET ( MY_INCLUDE_DIRS
+ #/usr/include/swfdec-0.5 /usr/include/glib-2.0 /usr/lib/glib-2.0/include
+-{SDL_INCLUDE_DIR} ${IMAGEMAGICKLIB_INCLUDE_DIR} ${SDLMIXER_INCLUDE_DIR} ${OPENGL_INCLUDE_DIR} ${PYTHON_INCLUDE_PATH} )
++{SDL_INCLUDE_DIR} ${IMAGEMAGICK_INCLUDE_DIRS} ${SDLMIXER_INCLUDE_DIR} ${OPENGL_INCLUDE_DIR} ${PYTHON_INCLUDE_PATH} )
+ IF(AUDIERELIB_FOUND)
+ SET ( MY_INCLUDE_DIRS ${MY_INCLUDE_DIRS} ${AUDIERELIB_INCLUDE_DIR} )
+ ENDIF(AUDIERELIB_FOUND)
Bug#768240: marked as done (cyrus-doc-2.4, cyrus-clients-2.4: copyright file missing after upgrade (policy 12.5))
Your message dated Thu, 06 Nov 2014 10:49:14 + with message-id e1xmkcs-0005iz...@franck.debian.org and subject line Bug#768240: fixed in cyrus-imapd-2.4 2.4.17+caldav~beta10-7 has caused the Debian Bug report #768240, regarding cyrus-doc-2.4, cyrus-clients-2.4: copyright file missing after upgrade (policy 12.5) 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.) -- 768240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cyrus-doc-2.4,cyrus-clients-2.4 Version: 2.4.17+caldav~beta10-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: wheezy - jessie From the attached log (scroll to the bottom...): 1m22.2s ERROR: WARN: Inadequate results from running adequate! cyrus-doc-2.4: missing-copyright-file /usr/share/doc/cyrus-doc-2.4/copyright MISSING COPYRIGHT FILE: /usr/share/doc/cyrus-doc-2.4/copyright # ls -lad /usr/share/doc/cyrus-doc-2.4 drwxr-xr-x 2 root root 40 Nov 3 06:58 /usr/share/doc/cyrus-doc-2.4 # ls -la /usr/share/doc/cyrus-doc-2.4/ total 0 drwxr-xr-x 2 root root 40 Nov 3 06:58 . drwxr-xr-x 140 root root 3000 Nov 3 06:58 .. 1m32.9s ERROR: WARN: Inadequate results from running adequate! cyrus-clients-2.4: missing-copyright-file /usr/share/doc/cyrus-clients-2.4/copyright MISSING COPYRIGHT FILE: /usr/share/doc/cyrus-clients-2.4/copyright # ls -lad /usr/share/doc/cyrus-clients-2.4 drwxr-xr-x 2 root root 40 Nov 3 06:02 /usr/share/doc/cyrus-clients-2.4 # ls -la /usr/share/doc/cyrus-clients-2.4/ total 0 drwxr-xr-x 2 root root 40 Nov 3 06:02 . drwxr-xr-x 140 root root 3000 Nov 3 06:02 .. Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. cheers, Andreas cyrus-doc-2.4_2.4.17+caldav~beta10-6.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: cyrus-imapd-2.4 Source-Version: 2.4.17+caldav~beta10-7 We believe that the bug you reported is fixed in the latest version of cyrus-imapd-2.4, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated cyrus-imapd-2.4 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: SHA512 Format: 1.8 Date: Thu, 06 Nov 2014 10:48:34 +0100 Source: cyrus-imapd-2.4 Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder cyrus-replication cyrus-nntpd cyrus-caldav cyrus-clients cyrus-dev libcyrus-imap-perl cyrus-common-2.4 cyrus-doc-2.4 cyrus-imapd-2.4 cyrus-pop3d-2.4 cyrus-admin-2.4 cyrus-murder-2.4 cyrus-replication-2.4 cyrus-nntpd-2.4 cyrus-caldav-2.4 cyrus-clients-2.4 cyrus-dev-2.4 libcyrus-imap-perl24 Architecture: source all Version: 2.4.17+caldav~beta10-7 Distribution: unstable Urgency: medium Maintainer: Debian Cyrus Team pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: cyrus-admin - Cyrus mail system - administration tools cyrus-admin-2.4 - Cyrus mail system - administration tools [dummy package] cyrus-caldav - Cyrus mail system - CalDAV and CardDAV support cyrus-caldav-2.4 - Cyrus mail system - CalDAV and CardDAV support [dummy package] cyrus-clients - Cyrus mail system - test
Processed: libtuxcap: diff for NMU version 1.4.0.dfsg2-2.2
Processing control commands: tag -1 pending Bug #747908 [libtuxcap] [libtuxcap] [transition blocker] Please allow to compile with imagemagick/experimental Added tag(s) pending. -- 747908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747908 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#768275: Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On Thu, Nov 06, 2014 at 10:40:01AM +0100, Andreas Beckmann wrote:
It may be the missing Pre-Depends you added in -3 (but I don't see any
errors from d-m-h in the logs). But it would be better to use
${misc:Pre-Depends} instead and have debhelper fill in the correct
versions instead of hardcoding them (since you are using .maintscript
files).
---end quoted text---
Well, in the case of python-whoosh (#768275), python-whoosh does have
the Pre-Depends yet it also failed.
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyID: 0xEDDDA1B7
GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
signature.asc
Description: Digital signature
Bug#767171: marked as done (tnftp: CVE-2014-8517: ftp(1) can be made execute arbitrary commands by malicious webserver)
Your message dated Thu, 06 Nov 2014 11:22:17 + with message-id e1xml8r-xs...@franck.debian.org and subject line Bug#767171: fixed in tnftp 20130505-2 has caused the Debian Bug report #767171, regarding tnftp: CVE-2014-8517: ftp(1) can be made execute arbitrary commands by malicious webserver 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.) -- 767171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tnftp Severity: grave Tags: security Please see http://www.openwall.com/lists/oss-security/2014/10/28/4 No CVE ID has been assigned yet. This doesn't warrant a DSA, but you could fix it up in a point release. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: tnftp Source-Version: 20130505-2 We believe that the bug you reported is fixed in the latest version of tnftp, 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anibal Monsalve Salazar ani...@debian.org (supplier of updated tnftp 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: SHA512 Format: 1.8 Date: Thu, 06 Nov 2014 10:42:01 + Source: tnftp Binary: tnftp Architecture: source amd64 Version: 20130505-2 Distribution: unstable Urgency: medium Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: tnftp - enhanced ftp client Closes: 759467 767171 Changes: tnftp (20130505-2) unstable; urgency=medium . * Only trust filenames with special meaning if they came from the command line. CVE-2014-8517. Add upstream patch CVE-2014-8517.patch. Closes: #767171. * Run dh-autoreconf to update for new architectures. Patch by Brahadambal Srinivasan la...@linux.vnet.ibm.com. Closes: 759467. * Standards Version is 3.9.6. * Fix uses-deprecated-compression-for-data-tarball. * Fix build-depends-on-obsolete-package. build-depends: hardening-wrapper = use dpkg-buildflags instead. Checksums-Sha1: 0ae33994045d362047f232441784913dbbddf073 1742 tnftp_20130505-2.dsc c24c22862522f257954997b696aaad130e9e02ad 6684 tnftp_20130505-2.debian.tar.xz 0c9b3c0a3e1052357f80718ffc983632f934679f 170162 tnftp_20130505-2_amd64.deb Checksums-Sha256: af466271cd5ed2c76c060eea5551b97c350eaf6f2bfd8e1a7091b3f5c342a773 1742 tnftp_20130505-2.dsc 2acea23ca1b36099a6517f1215edefb196c8d2b06fde30cecacfed5d34a11d19 6684 tnftp_20130505-2.debian.tar.xz c442209bc774a09813632eccd2c3d34b01fd86739f3220c65903cd3366a9bd53 170162 tnftp_20130505-2_amd64.deb Files: 614d5d30801431bbe6bc52c3ba5a1c4a 1742 net optional tnftp_20130505-2.dsc 7f6c8e47de72ba5e38e0e78cfd93b10d 6684 net optional tnftp_20130505-2.debian.tar.xz c477e2b89f398523bc68277c8bc9b346 170162 net optional tnftp_20130505-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUW1HxAAoJEHxWrP6UeJfYxKwP/1fqHgB6M9xfBMMs2suMUPLV aO4T1mH20AIz1Q6cjuixXoTX1qufIBM3c5CDtrqsy7wnQiLif8nKKGHqJu7+yZhL VzCu960agXR5aVWk6LES5CPBGi3J2VWNytLv++nj1ANCCkax46TAd372uqJCAuFT KbkJMjWv3d+BUxCR4xhYGh0rztQGRCYExh11Nf8DG6TxQbdrKc+vOoAFtpSRoUcP DdYoNXzwf7u71CU+lIfXPHDgKEhwW5ULUH8vEpY3jbYckUJI5B3RjVqW9LcezhC0 3ut70IdV1nMjKtoqgv6TMso8By8hFwD2C2dG6usqY3l3TQuZihyVhkgLgEl4gO15 AE/UU+4hzvnsDTq6tRoByvL/inmV+8TFaaXtv1rBYYDPehRYYMCF/ncx38xZ+KYV CwXoqM0Z5lMvFrdVmMJDKrk3IFtWWWnzyH6iZmB1F7BMI49o5DJLFdaZcyrxoJRR zJrgpbbzbFePljQst4A8D4Uwl0xnEaqJ5JKDzmRdu5bq3cT6o1udu2DN5dKDtW1j JsguntTCHkB35uQIlxWBr9EXH6lgFO/u65BcmMYPA4YW7TN7sKxmcOl09L2ci+Y7 VtrCZPBy/LzoPpAxqdvgKP+FJ7Dfsx7EKm0s5xR4oOOTQLT0H+MgEr+liJzTlHRq ZSvZbuPt2mOF50hXDclm =FAB5 -END PGP SIGNATUREEnd Message---
Bug#767999: problem with debootstrap in wheezy
Note: dpkg 1.17.21 has migrated to testing, and, as a result, the current debootstrap in wheezy is now unable to create chroots for both jessie and sid (previously it was only sid and jessie still worked). As of today, in jessie we still have base-files 7.6. So, as I suspected, the recent changes in dpkg are the most likely reason why this problem didn't bite us before, not the changes I did in base-files 7.7. I hope this might definitely clarify some past misunderstandings about this problem. Thanks a lot. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: macchanger: Randomization fails
Processing commands for cont...@bugs.debian.org:
unarchive 738460
Bug #738460 {Done: ty...@mit.edu (Theodore Y. Ts'o)} [macchanger] macchanger:
Randomization fails for final three octets
Bug #740947 {Done: ty...@mit.edu (Theodore Y. Ts'o)} [macchanger] macchanger:
Random mac feature fails in all of the random mac assigning options
Unarchived Bug 738460
Unarchived Bug 740947
found 738460 macchanger/1.7.0-2
Bug #738460 {Done: ty...@mit.edu (Theodore Y. Ts'o)} [macchanger] macchanger:
Randomization fails for final three octets
Bug #740947 {Done: ty...@mit.edu (Theodore Y. Ts'o)} [macchanger] macchanger:
Random mac feature fails in all of the random mac assigning options
Marked as found in versions macchanger/1.7.0-2 and reopened.
Marked as found in versions macchanger/1.7.0-2 and reopened.
thank you
Stopping processing here.
Please contact me if you need assistance.
--
738460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738460
740947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740947
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#738460: macchanger: Randomization fails
unarchive 738460 found 738460 macchanger/1.7.0-2 thank you Hello The patch 08-fix_random_MAC_choice.patch has been changed from version 1.7.0-1.1, with no mention in the debian changelog. That version of the patch totally breaks macchanger. To understand this, look at mac.c in function mc_mac_random. First you need to realize that the variable newmac should be called oldmac: It is assigned the original mac address. Then, mac is randomized until it is different from the original one called newmac. And finally newmac - the original mac address - is copied back into mac !! oO Please revert the change in version 1.7.0-2 and use the patch from version 1.7.0-1.1, or similar. signature.asc Description: OpenPGP digital signature
Bug#768203: sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli
Since no upgrade ordering is not guaranteed by the package manager, I'm looking for all possibly problematic (partial) upgrade paths from wheezy to jessie, that includes files being moved from one package to another (that may not have existed in wheezy.) And I try to really excercise all paths not forbidden by Breaks/Conflicts :-) On 2014-11-06 11:00, Ferenc Wagner wrote: Of course the above problem could be declared in the metadata of sblim-wbemcli, though 7.6 does not seem to apply here. 7.4 (Conflicts) seems more appropriate to me, if something really is needed. I initially thought it was not, but you surely know better, please advise me. If a package was in wheezy and is completely gone in jessie, unversioned Replaces+Conflicts in the successor are OK. If the package still exists (even as an empty transitional package), use versioned Breaks+Replaces ( the-first-version-no-longer-shipping-the-files~) The trailing ~ is recommended for backports-compatibility. Breaks are much easier to handle for the package manager than Conflicts. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Debian bugs: #768183
Processing commands for cont...@bugs.debian.org: fixed 768183 psocksxx/0.0.6-2 Bug #768183 [src:psocksxx] psocksxx: FTBFS: '.../libpsocksxx-doc/docs/' is not a directory The source psocksxx and version 0.0.6-2 do not appear to match any binary packages Marked as fixed in versions psocksxx/0.0.6-2. -- Stopping processing here. Please contact me if you need assistance. -- 768183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768183 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#740034: marked as done (lshw can crash arm64 systems)
Your message dated Thu, 06 Nov 2014 12:49:21 + with message-id e1xmmv7-000727...@franck.debian.org and subject line Bug#740034: fixed in lshw 02.17-1.1 has caused the Debian Bug report #740034, regarding lshw can crash arm64 systems 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.) -- 740034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lshw Version: 02.16-2 Severity: wishlist Tags: patch lshw, when executed as root, will troll through /dev/mem looking for an smbios table. This causes an oops on some arm64 hardware. ---End Message--- ---BeginMessage--- Source: lshw Source-Version: 02.17-1.1 We believe that the bug you reported is fixed in the latest version of lshw, 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. Neil Williams codeh...@debian.org (supplier of updated lshw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Nov 2014 12:16:13 + Source: lshw Binary: lshw lshw-gtk Architecture: source amd64 Version: 02.17-1.1 Distribution: unstable Urgency: medium Maintainer: Ghe Rivero g...@debian.org Changed-By: Neil Williams codeh...@debian.org Description: lshw - information about hardware configuration lshw-gtk - graphical information about hardware configuration Closes: 740034 757689 Changes: lshw (02.17-1.1) unstable; urgency=medium . * Non-maintainer upload. * Disable the memory scanning for all architectures other than i386 and x86_64. Patch from Leif Lindholm unixsm...@gmail.com (Closes: #740034) * Prevent segfault if system has FAT partition(s) Patch from Alban Browaeys pra...@yahoo.com (Closes: #757689) Checksums-Sha1: 008463539bd97cca147236e4683d156d3329a7b7 1684 lshw_02.17-1.1.dsc d3d2fbaaf8b17628d7fbf286c851afda599a4b54 17381 lshw_02.17-1.1.diff.gz 6bc6eeaaf42964f96e6b1e2cdc8f21ddeb2e06ad 233958 lshw_02.17-1.1_amd64.deb cd1b30709a5916e3133c88c1dfda06bd17930579 308892 lshw-gtk_02.17-1.1_amd64.deb Checksums-Sha256: a8c01d3afb7ea5ecf9139eb0efce9e9928c702a6b428f41b4cc3eb33f22eb39c 1684 lshw_02.17-1.1.dsc 5616ae28df2daa1404f1c875528807e4c8e72889ddd5cd4cc7975fcc33f8f1c0 17381 lshw_02.17-1.1.diff.gz 67a4c365fc95b99296277e6e3eb84bfafeeb7081fb4d88e9b16b41705c2a2b61 233958 lshw_02.17-1.1_amd64.deb be901a7801465fe4b43f91a14e7beba99ee9a363f8517187178cc802b2bf4a54 308892 lshw-gtk_02.17-1.1_amd64.deb Files: 1254e244500db7a439a099138b526ca2 1684 utils optional lshw_02.17-1.1.dsc 29b9771af5682f986ae6864a37e332d0 17381 utils optional lshw_02.17-1.1.diff.gz f9e5e82522e430e27e7cd11f0018a859 233958 utils optional lshw_02.17-1.1_amd64.deb 96fafebc52bff0e6db35c5498901b6d4 308892 utils optional lshw-gtk_02.17-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUW2ioAAoJEPFn5DyBQ7aCyO0P/jIA+PxCOUvpZCIgGzpAg11K jxi6q+fsXZ4ytYhKToOASNd7C/wutxwZ9ccbC+QFRQRzO5Y7KrTD+LmGhqF0GQAR /yzF5vuu2IeJ+VJBNSJIFY9psvxxwG4UEDwwL965endwMrRM4DUSQfxSb7oxStA1 yZlRg/3l3Qt4uZNAJdR+dmdzQfxu8YwvDKfDgg6WPFV47W1VswvrzhNo7rePm9M1 IsqxbEPfn3XSuwC9CqOe1++S0jieYjWnOJImgU3coMmaxqvSbrG9JpwVW64wrRaB EPE6hj/47g+8l/WlboYAl96tfQL9xbT2kAkzTpjoWkzm8uVmQe/89JS/l2mFMick dNJGZfBvQXUB/Dbt1VMdbiKc7qkiIctKDoRLtTINWZ33PA0Oy1L2pWwGwvTjoZmj mrXoRjBJXPiXWT09ILWlrnQUOWm8d+UB7AXYPKGS1NvC5qCeNJGiuFRyp+bSX53M aLECUOzGIM1oUO3hntNYSc9lSD7yTczMznKSB8MoYe2Z0pE9QRyW/szj3mlWT9bG FbqRn9cG0SJNk1qGRgxvqHkIwn94kCABggOQDQ5CKfWDNocw6oe+9NEVdH9TDT5C lLSPyvaHNi7BSPOYQJ99jhJhUzDw3dW+3GyfVXOOnmFh63Ma7tfxrkjHozFzly6L oW817D1nlLBAwXIHjCq+ =lCxk -END PGP SIGNATUREEnd Message---
Bug#757689: marked as done (Segfault if system has FAT partition(s))
Your message dated Thu, 06 Nov 2014 12:49:21 +
with message-id e1xmmv7-00072c...@franck.debian.org
and subject line Bug#757689: fixed in lshw 02.17-1.1
has caused the Debian Bug report #757689,
regarding Segfault if system has FAT partition(s)
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.)
--
757689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lshw
Version: 4.8-1.1
Machine: System: TOSHIBA product: Satellite C75D-B v: PSCLEU-003002
Mobo: TOSHIBA model: Portable PC v: MP Bios: Insyde v: 1.10
date: 04/30/2014
CPU: Quad core AMD A6-6310 APU with AMD Radeon R4 Graphics (-MCP-)
cache: 8192 KB
Clock Speeds: 1: 1000 MHz 2: 1000 MHz 3: 1800 MHz 4: 1000 MHz
Kernel~3.14-2-amd64 x86_64
Debian branch: testing
Mem~1522.2/6955.7MB
Problem:
lshw works as user, but it throws warning that it should be used as su.
As root it does not show any output and crashes with segmentation fault.
root@notosh:/home/ckosloff# lshw
Segmentation fault
Here is output of strace lshw, as root.
read(3, 0 interface\nb100 OpenVox Commun..., 1024) = 1024
read(3, Luna K3 Hardware Security Module..., 1024) = 1024
read(3, card 3.3V (PCI-Express) (5th ge..., 1024) = 1024
read(3, ionRGB-E2S\n\t1151 VisionSD4+1S\n\t..., 1024) = 1024
read(3, Winbond\n\te000 W89C940\ne159 Ti..., 1024) = 1024
read(3, 2 Pro\n\t9898 Digi32/8\neabb Aash..., 1024) = 1024
read(3, Gig Ethernet/OC-3/OC-12/OC-48\n\t6..., 1024) = 1024
read(3, ks, Inc.\n# Subsystem ID for PATA..., 1024) = 1024
read(3, MA single stepping\n\t\t30 ADMA co..., 1024) = 1024
read(3, CMCIA bridge\n\t06 NuBus bridge\n\t..., 1024) = 1024
read(3, oller\n\t06 IOMMU\n\t80 System per..., 1024) = 1024
read(3, er\n\t02 Satellite audio communic..., 1024) = 478
read(3, , 1024) = 0
close(3)= 0
mmap(NULL, 2625536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7f87f9e77000
munmap(0x7f87fa0f8000, 1314816) = 0
brk(0x1337000) = 0x1337000
brk(0x1358000) = 0x1358000
brk(0x1379000) = 0x1379000
brk(0x139a000) = 0x139a000
brk(0x13bb000) = 0x13bb000
brk(0x13dc000) = 0x13dc000
brk(0x13fd000) = 0x13fd000
open(/etc/pci.ids, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/share/pci.ids, O_RDONLY)= -1 ENOENT (No such file or
directory)
open(/usr/local/share/pci.ids, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/share/lshw-common/pci.ids, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/share/pci.ids, O_RDONLY)= -1 ENOENT (No such file or
directory)
getcwd(/home/ckosloff, 4097) = 15
chdir(/sys/bus/pci/devices) = 0
openat(AT_FDCWD, ., O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
getdents(3, /* 26 entries */, 32768)= 816
lstat(:00:00.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:01.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:01.1, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:02.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:02.2, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:02.3, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:02.4, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:08.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:10.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:11.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:12.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:13.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:14.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:14.2, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:14.3, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:18.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:18.1, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:18.2, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:18.3, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:18.4, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:00:18.5, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:01:00.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:05:00.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
lstat(:06:00.0, {st_mode=S_IFLNK|0777, st_size=0, ...}) = 0
getdents(3, /* 0 entries */,
Processed: tagging 726370, severity of 726370 is important
Processing commands for cont...@bugs.debian.org: # Patch maybe working, maybe not tags 726370 + moreinfo Bug #726370 [src:libgphoto2] gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150. Added tag(s) moreinfo. severity 726370 important Bug #726370 [src:libgphoto2] gphoto2: Nikon D300, Darktable hangs and Dolphin shows error code 150. Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 726370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768183: marked as done (psocksxx: FTBFS: '.../libpsocksxx-doc/docs/' is not a directory)
Your message dated Thu, 06 Nov 2014 13:34:20 + with message-id e1xmnce-0005ij...@franck.debian.org and subject line Bug#768183: fixed in psocksxx 0.0.6-2 has caused the Debian Bug report #768183, regarding psocksxx: FTBFS: '.../libpsocksxx-doc/docs/' is not a 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.) -- 768183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: psocksxx Version: 0.0.6-1 Severity: serious Justification: fails to build from source Builds of psocksxx covering only its architecture-dependent binary packages (as on the autobuilders, or with dpkg-buildpackage -B) have been failing: cp -r /«PKGBUILDDIR»/doc/doxygen/html/* /«PKGBUILDDIR»/debian/libpsocksxx-doc/usr/share/doc/libpsocksxx-doc/docs/ cp: target '/«PKGBUILDDIR»/debian/libpsocksxx-doc/usr/share/doc/libpsocksxx-doc/docs/' is not a directory make[1]: *** [override_dh_installdocs] Error 1 debian/rules:26: recipe for target 'override_dh_installdocs' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 debian/rules:19: recipe for target 'binary-arch' failed Could you please take a look, and arrange to run this command only when actually building the -doc package? For that matter, it would be good to move doxygen to Build-Depends-Indep and likewise run it only when building the -doc package. Thanks! ---End Message--- ---BeginMessage--- Source: psocksxx Source-Version: 0.0.6-2 We believe that the bug you reported is fixed in the latest version of psocksxx, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jörg Frings-Fürst deb...@jff-webhosting.net (supplier of updated psocksxx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Nov 2014 13:10:19 +0100 Source: psocksxx Binary: libpsocksxx0 libpsocksxx-dev libpsocksxx-doc Architecture: source amd64 all Version: 0.0.6-2 Distribution: unstable Urgency: medium Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net Changed-By: Jörg Frings-Fürst deb...@jff-webhosting.net Description: libpsocksxx-dev - psocksxx is a C++ wrapper for POSIX sockets (development files) libpsocksxx-doc - psocksxx is a C++ wrapper for POSIX sockets (documentation) libpsocksxx0 - psocksxx is a C++ wrapper for POSIX sockets Closes: 768183 Changes: psocksxx (0.0.6-2) unstable; urgency=medium . * debian/rules: - Add *-indep rules to fix FTBFS when building architecture-specific targets (Closes: #768183). * debian/control: - Move doxygen from Build-Depends to Build-Depends-Indep. * debian/patches/10_test_network.patch: - Disable test_connect_addr test to fix FTBFS. Checksums-Sha1: 5f4bce92254f148dbe354a5b96b96fcf568d5462 2102 psocksxx_0.0.6-2.dsc 0f2ac4f0ec62defdd7b9667baab3aa9fec254ceb 25795 psocksxx_0.0.6.orig.tar.gz 9704284726b88edf62a1fbcb8032f38af0a8907f 4088 psocksxx_0.0.6-2.debian.tar.xz c5c834cfef962e458cba204a9fca3be2355f51f2 19610 libpsocksxx0_0.0.6-2_amd64.deb 49fdf3fed4dbe2cae52ce3db5f58a635c1473950 10826 libpsocksxx-dev_0.0.6-2_amd64.deb 4be36337bdec914cea01e0a18af400ca4253908f 125164 libpsocksxx-doc_0.0.6-2_all.deb Checksums-Sha256: 6f8074b509bd507a2dfb2cf16bd66a44b137530651f18a2de36ea3515c4bff47 2102 psocksxx_0.0.6-2.dsc 045d20c44d719259fa6b84cd1fac6cbd9b291360ed033d561e36618b998a1806 25795 psocksxx_0.0.6.orig.tar.gz c12134b730c7fc55c44770dcc370a6d99ef8a41387522437ada5726af6d46854 4088 psocksxx_0.0.6-2.debian.tar.xz 022d384b2c511b8cf0a9b89dbf7ca45dc4370a2d658a63a23a085b870d1612c4 19610 libpsocksxx0_0.0.6-2_amd64.deb 2011a56487aa10392f2678015c98d8ccbb184901ee65e3f86e83c22dac2be9f1 10826 libpsocksxx-dev_0.0.6-2_amd64.deb 4cbd7f1fc975eb2bb093f7e0e024eab3cb1571572697c542b97247743ab96f7b 125164 libpsocksxx-doc_0.0.6-2_all.deb Files: 6b83b57bcf666c87ee14961c703dcfae 2102 libs optional psocksxx_0.0.6-2.dsc 712359c9c102aa254f45121bde0a5748 25795 libs optional psocksxx_0.0.6.orig.tar.gz b8651170197f7a8e0ea6af8eed8fc75c 4088 libs optional
Bug#704915: marked as done (auctex: Fails to install)
Your message dated Thu, 06 Nov 2014 14:32:47 +0100 with message-id 87egtgpi80.fsf@tabbi.olympus.invalid and subject line Fixed in squeeze-backports has caused the Debian Bug report #704915, regarding auctex: Fails to install 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.) -- 704915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: auctex Version: 11.85-1 Severity: grave Justification: renders package unusable Debian Squeeze AMD64. The package in subject fails to install (fresh install). This is the output from terminal: # LC_ALL=C aptitude install auctex The following NEW packages will be installed: auctex 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/1305 kB of archives. After unpacking 4678 kB will be used. Preconfiguring packages ... Selecting previously deselected package auctex. (Reading database ... 254909 files and directories currently installed.) Unpacking auctex (from .../auctex_11.85-1_all.deb) ... Processing triggers for install-info ... Processing triggers for man-db ... Processing triggers for doc-base ... Processing 2 added doc-base file(s)... Registering documents with scrollkeeper... Setting up auctex (11.85-1) ... install/auctex: Setting up for emacs23 (log file: /usr/share/emacs23/site- lisp/auctex//CompilationLog)... emacs-package-install: /usr/lib/emacsen- common/packages/install/auctex emacs23 emacs23 failed at /usr/lib/emacsen- common/emacs-package-install line 30, TSORT line 1. dpkg: error processing auctex (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: auctex E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up auctex (11.85-1) ... install/auctex: Setting up for emacs23 (log file: /usr/share/emacs23/site- lisp/auctex//CompilationLog)... emacs-package-install: /usr/lib/emacsen- common/packages/install/auctex emacs23 emacs23 failed at /usr/lib/emacsen- common/emacs-package-install line 30, TSORT line 1. dpkg: error processing auctex (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: auctex Thank you very much in advance, Domenico -- Package-specific info: Content of '/usr/share/emacs/site-lisp/auctex/' 4445a5aa5b0c6dd4eeb5d6a7b214b9a7 /usr/share/emacs/site-lisp/auctex/ChangeLog 7a5ac7b2ea13114a7237cad95ce9e127 /usr/share/emacs/site-lisp/auctex/Makefile 94b8353848c014c5aad9e29b149ff931 /usr/share/emacs/site-lisp/auctex/Makefile.in f86b3412ef7d2947d5ab37ab13f2200d /usr/share/emacs/site-lisp/auctex/aclocal.m4 c515b501a8d5009537edfb0348d3f14e /usr/share/emacs/site-lisp/auctex/auctex.el e23e60e9de6051db5156aecaaaea11e7 /usr/share/emacs/site-lisp/auctex/auctex.el.in 3366a99dd44e27fa57e0bcc130c4fa1c /usr/share/emacs/site-lisp/auctex/bib-cite.el 542b9f88e6d102b497e17c104de7568a /usr/share/emacs/site-lisp/auctex/confdefs.h 683dbf2998518f1d182da52f12bd1d63 /usr/share/emacs/site-lisp/auctex/config.log dbb7f49fb883815b70b880b1c047d6b7 /usr/share/emacs/site-lisp/auctex/config.status 8f868ec2c03618542b54b36547f83afd /usr/share/emacs/site-lisp/auctex/configure 9ad8e6370c812d9a54f4b76b7b6ccfcd /usr/share/emacs/site-lisp/auctex/configure.ac bc74f7b5fa3e81249059523bda2af187 /usr/share/emacs/site-lisp/auctex/context-en.el 7e5fea718848deb6b66d2f2050c4c4d9 /usr/share/emacs/site-lisp/auctex/context-nl.el 66cdeaf725eadcbd25f55cefa4fdce88 /usr/share/emacs/site-lisp/auctex/context.el 2b11f4f8c3a4189bf7cc8fec5a51e8c0 /usr/share/emacs/site-lisp/auctex/doc/Makefile 2b11f4f8c3a4189bf7cc8fec5a51e8c0 /usr/share/emacs/site-lisp/auctex/doc/Makefile.in 6f9d9372928534a7b6549aca174f026e /usr/share/emacs/site-lisp/auctex/font-latex.el f176261b5a5511cbe1401ee72ffb8947 /usr/share/emacs/site-lisp/auctex/images/amstex.xpm d33121019448617a3ad3bcafdeb8db40 /usr/share/emacs/site-lisp/auctex/images/bibtex.xpm 1a43d6438010bceb374ab0a5f2bd05a8 /usr/share/emacs/site-lisp/auctex/images/dropdown.xpm 41f1ae0341ae2e307d92a7b8b815f868 /usr/share/emacs/site-lisp/auctex/images/dvipdf.xpm 2e4b8669b0168f32247411be3f999437 /usr/share/emacs/site-lisp/auctex/images/dvips.xpm 55f7600cadc3a209e94bacf6bbc42a7c
Bug#765118: marked as done (scilab: FTBFS: [javac] /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/jogl/JoGLCanvas.java:23: error: cannot find symbol)
Your message dated Thu, 06 Nov 2014 13:50:44 +
with message-id e1xmnsw-0007ic...@franck.debian.org
and subject line Bug#765118: fixed in scilab 5.5.1-3
has caused the Debian Bug report #765118,
regarding scilab: FTBFS: [javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/jogl/JoGLCanvas.java:23:
error: cannot find symbol
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.)
--
765118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: scilab
Version: 5.5.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 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):
make[3]: Entering directory '/«PKGBUILDDIR»/modules/prebuildjava'
Buildfile: /«PKGBUILDDIR»/modules/prebuildjava/build.xml
scirenderer:
[echo] Using:
[echo] ${thirdparty.dir}
[echo] /usr/share/java/jogl2.jar
[echo] /usr/share/java/gluegen2-rt.jar
[echo] /usr/share/java/jlatexmath.jar
init:
[mkdir] Created dir: /«PKGBUILDDIR»/modules/scirenderer/build/classes
[mkdir] Created dir: /«PKGBUILDDIR»/modules/scirenderer/build/test
[mkdir] Created dir: /«PKGBUILDDIR»/modules/scirenderer/jar
compile:
[javac] Compiling 117 source files to
/«PKGBUILDDIR»/modules/scirenderer/build/classes
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/Canvas.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/Drawer.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/DrawingTools.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/PackageInfo.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/SciRendererException.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/BuffersManager.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/DataBuffer.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/ElementsBuffer.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/buffers/IndicesBuffer.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/clipping/ClippingManager.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/clipping/ClippingPlane.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/data/AbstractDataProvider.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/data/DataProvider.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/data/DataUser.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/G2DCanvas.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/G2DCanvasFactory.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/G2DDrawingTools.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/buffers/G2DBuffersManager.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/buffers/G2DElementsBuffer.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/buffers/G2DIndicesBuffer.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/clipping/G2DClippingManager.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/clipping/G2DClippingPlane.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/lighting/G2DLight.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/lighting/G2DLightManager.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/AbstractDrawable3DObject.java
[javac]
/«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/g2d/motor/BoundingBox.java
[javac]
Bug#739989: marked as done (debian-installer-utils: log-output change breaks speech synthesis)
Your message dated Thu, 6 Nov 2014 15:04:31 +0100 with message-id 20141106140431.gd17...@mraw.org and subject line Re: Bug#739989: debian-installer-utils: log-output change breaks speech synthesis has caused the Debian Bug report #739989, regarding debian-installer-utils: log-output change breaks speech synthesis 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.) -- 739989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: debian-installer-utils Version: 1.103 Severity: serious Tags: d-i Justification: breaks speech synthesis Hi Colin, the change below breaks speech synthesis, as reported here: https://lists.debian.org/debian-accessibility/2014/02/msg00093.html and suspected here: https://lists.debian.org/debian-accessibility/2014/02/msg00102.html I've checked that building d-i against testing udebs lets me reproduced this issue, and that adding d-i-utils' binaries to localudebs after having reverted this change fixes speech synthesis. commit 9c6685364a56697ea9c590e1bc93a73ade88b679 Author: Colin Watson cjwat...@debian.org Date: Fri Feb 7 17:07:46 2014 + log-output: Always install a no-op SIGCHLD handler This copes with the case where the subsidiary process starts a daemon which does not fully disconnect its standard file descriptors (LP: #1021293). See also the changelog for 1.46. (http://anonscm.debian.org/gitweb/?p=d-i/debian-installer-utils.git;a=commit;h=9c6685364a56697ea9c590e1bc93a73ade88b679) Can you please have a look? Worst case I could revert and upload with urgency=high (the package is in testing now), but having a proper fix would be nice if it's only a matter of days. Mraw, KiBi. ---End Message--- ---BeginMessage--- Cyril Brulebois k...@debian.org (2014-02-24): Source: debian-installer-utils Version: 1.103 Severity: serious Tags: d-i Justification: breaks speech synthesis Hi Colin, the change below breaks speech synthesis, as reported here: https://lists.debian.org/debian-accessibility/2014/02/msg00093.html and suspected here: https://lists.debian.org/debian-accessibility/2014/02/msg00102.html I've checked that building d-i against testing udebs lets me reproduced this issue, and that adding d-i-utils' binaries to localudebs after having reverted this change fixes speech synthesis. commit 9c6685364a56697ea9c590e1bc93a73ade88b679 Author: Colin Watson cjwat...@debian.org Date: Fri Feb 7 17:07:46 2014 + log-output: Always install a no-op SIGCHLD handler This copes with the case where the subsidiary process starts a daemon which does not fully disconnect its standard file descriptors (LP: #1021293). See also the changelog for 1.46. (http://anonscm.debian.org/gitweb/?p=d-i/debian-installer-utils.git;a=commit;h=9c6685364a56697ea9c590e1bc93a73ade88b679) Can you please have a look? Worst case I could revert and upload with urgency=high (the package is in testing now), but having a proper fix would be nice if it's only a matter of days. Since this change was reverted, let's close this bug report for now. Mraw, KiBi. signature.asc Description: Digital signature ---End Message---
Bug#767999: debootstrap/base-passwd: #767999 and #766459 should really be fixed in base-passwd
[ BCC'ing Santiago, Holger, Adam, Cyril ]
Hi all,
I'm refraining from quoting the preceding mails as most of you will have those
in their inbox, and I'd rather summarise the situation right here:
At least Santiago's and my opinion diverge on whether base-passwd is presently
in line with policy on 3.8 Essential packages. Therefore the route from here
appears to hinge on interpreting policy in one of two ways: my point is that
base-passwd, at present, is not providing its functionality after just being
unpacked - it does require postinst having been run. Santiago claims, if I
interpret this correctly, that every package has to be configured at least once
before being useful at all (irrespective of whether it is essential or not).
The steps from here are such:
1. Determine whether base-passwd is in line with policy on providing its
functionality as an essential package.
A) If it is, then debootstrap is buggy.
B) If base-passwd violates policy, then base-passwd is buggy.
2. If debootstrap is buggy, then the most effective way of updating as many
debootstrap installations as possible must be found.
3. If base-passwd violates policy, policy could be amended to acknowledge
base-passwd's special case. Then again we are in situation 2.
4. If base-passwd violates policy and policy would not be amended, then
base-passwd will need to be changed. Again, as you aren't base-passwd's
maintainer, you are not to be tasked with this.
My point of view is that base-passwd should be changed, and thanks to
suggestions from Tollef last night the attached patch should actually achieve
this. The idea simply is to sort out creating /etc/passwd and /etc/group in
preinst already, so that these files will be present once the package reaches
the state unpacked.
Using a version of base-passwd modified in this way makes wheezy's debootstrap
work for me.
I am thus CC'ing Colin as base-passwd's maintainer to gather his input - I'm not
really up for any bug-reassigning game, so I'd rather not do this myself without
consent by any of the involved package maintainers (I'm just a debootstrap
user...).
Best,
Michael
diff -Nru base-passwd-3.5.36/debian/other base-passwd-3.5.36/debian/other
--- base-passwd-3.5.36/debian/other 1970-01-01 01:00:00.0 +0100
+++ base-passwd-3.5.36/debian/other 2014-11-06 11:18:54.0 +
@@ -0,0 +1,10 @@
+
+override_dh_clean:
+ dh_auto_clean
+ $(RM) debian/preinst
+
+override_dh_auto_configure:
+ cp debian/preinst.in debian/preinst
+ sed -e '/@PASSWD@/ {' -e 'r passwd.master' -e 'd' -e '}' -i
debian/preinst
+ sed -e '/@GROUP@/ {' -e 'r group.master' -e 'd' -e '}' -i debian/preinst
+
diff -Nru base-passwd-3.5.36/debian/preinst.in
base-passwd-3.5.36/debian/preinst.in
--- base-passwd-3.5.36/debian/preinst.in1970-01-01 01:00:00.0
+0100
+++ base-passwd-3.5.36/debian/preinst.in2014-11-06 10:47:29.0
+
@@ -0,0 +1,23 @@
+#! /bin/sh
+
+set -e
+
+if [ ! $1 = install ] ; then
+exit 0
+fi
+
+if [ ! -e /etc/passwd ] ; then
+ cat /etc/passwd EOF
+@PASSWD@
+EOF
+fi
+
+if [ ! -e /etc/group ] ; then
+ cat /etc/group EOF
+@GROUP@
+EOF
+fi
+
+#DEBHELPER#
+
+exit 0
diff -Nru base-passwd-3.5.36/debian/rules base-passwd-3.5.36/debian/rules
--- base-passwd-3.5.36/debian/rules 2014-08-31 18:04:51.0 +0100
+++ base-passwd-3.5.36/debian/rules 2014-11-06 11:25:54.0 +
@@ -5,6 +5,16 @@
export DEB_BUILD_MAINT_OPTIONS := hardening=+all
export DEB_CFLAGS_MAINT_APPEND := -Wall
+override_dh_auto_clean:
+ dh_auto_clean
+ $(RM) debian/preinst
+
+override_dh_auto_install:
+ cp debian/preinst.in debian/preinst
+ sed -e '/@PASSWD@/ {' -e 'r passwd.master' -e 'd' -e '}' -i
debian/preinst
+ sed -e '/@GROUP@/ {' -e 'r group.master' -e 'd' -e '}' -i debian/preinst
+ dh_auto_install
+
override_dh_installdebconf:
touch debian/base-passwd.substvars
mv debian/base-passwd.substvars debian/base-passwd.substvars.real
pgptOtUFR9L9o.pgp
Description: PGP signature
Bug#768203: sblim-wbemcli: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/wbemcli
Andreas Beckmann a...@debian.org writes: Since no upgrade ordering is not guaranteed by the package manager, I'm looking for all possibly problematic (partial) upgrade paths from wheezy to jessie, I'm afraid I don't understand. You're talking about upgrades, but you couldn't possibly have python-pywbem and sblim-wbemcli installed together, unless python-pywbem was at 0.8.0~dev650-1, its latest version. And then there's no problem with any version of sblim-wbemcli. No version of sblim-wbemcli is included in wheezy, though. that includes files being moved from one package to another (that may not have existed in wheezy.) And I try to really excercise all paths not forbidden by Breaks/Conflicts :-) Maybe you install python-pywbem in wheezy, then switch sources to jessie and install sblim-wbemcli without dist-upgrading first? That's the only scenario I can think of which exhibits this problem. On 2014-11-06 11:00, Ferenc Wagner wrote: Of course the above problem could be declared in the metadata of sblim-wbemcli, though 7.6 does not seem to apply here. 7.4 (Conflicts) seems more appropriate to me, if something really is needed. I initially thought it was not, but you surely know better, please advise me. If a package was in wheezy and is completely gone in jessie, unversioned Replaces+Conflicts in the successor are OK. No, this is not the case, both packages are in jessie, but python-pywbem has its former /usr/bin/wbemcli binary renamed to avoid conflict with sblim-wbemcli. Replaces does not play either, the packages have different (tough in part similar) purposes, as well as the clashing binaries. If the package still exists (even as an empty transitional package), use versioned Breaks+Replaces ( the-first-version-no-longer-shipping-the-files~) The trailing ~ is recommended for backports-compatibility. Breaks are much easier to handle for the package manager than Conflicts. But Breaks does not forbid unpacking both packages together, which is really impossible, as both contain the same file. All this suggests Conflicts: python-pywbem ( 0.8.0~dev650-1~) should be added to sblim-wbemcli to avoid this error on any setup. Do you agree? -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Automatic run doesn't change the serial number, only vendor id
Processing control commands: block -1 by 738460 Bug #768325 [macchanger] Automatic run doesn't change the serial number, only vendor id 768325 was not blocked by any bugs. 768325 was not blocking any bugs. Added blocking bug(s) of 768325: 738460 and 740947 -- 768325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768325 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#742140: libpam-oath: PAM module does not check whether strdup allocations succeeded
Hi,
we have the following debian bug report about an security isuse in
libpam-oath (source oath-toolkit, upstream web page
http://www.nongnu.org/oath-toolkit/ ).
What is the appropriate process to get an CVE number on it? This issue
is already public, as it is documented in the debian bug tracking
system.
Andi
* Eero Häkkinen (eer...@bigfoot.com) [141106 14:31]:
Package: libpam-oath
Version: 2.0.2-2
Severity: grave
Tags: security upstream patch
The OATH Toolkit PAM module does not check whether strdup allocations
succeeded. This may result in null pointer dereference and application
crash.
Depending on the use of the PAM module, this may be remotely exploitable.
diff --git a/pam_oath/pam_oath.c b/pam_oath/pam_oath.c
index 8379358..e2d3363 100644
--- a/pam_oath/pam_oath.c
+++ b/pam_oath/pam_oath.c
@@ -146,6 +146,12 @@ pam_sm_authenticate (pam_handle_t * pamh,
char *query_prompt = NULL;
char *onlypasswd = strdup ();/* empty passwords never match */
+ if (!onlypasswd)
+{
+ retval = PAM_BUF_ERR;
+ goto done;
+}
+
parse_cfg (flags, argc, argv, cfg);
retval = pam_get_user (pamh, user, NULL);
@@ -265,6 +271,11 @@ pam_sm_authenticate (pam_handle_t * pamh,
{
free (onlypasswd);
onlypasswd = strdup (password);
+ if (!onlypasswd)
+{
+ retval = PAM_BUF_ERR;
+ goto done;
+}
/* user entered their system password followed by generated OTP? */
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): forcibly merging 761047 722912
Processing commands for cont...@bugs.debian.org: forcemerge 761047 722912 Bug #761047 [libcogl20] libcogl20: breaks upgrade from wheezy to jessie Unable to merge bugs because: package of #722912 is 'libclutter-1.0-0' not 'libcogl20' Failed to forcibly merge 761047: Did not alter merged bugs thanks Stopping processing here. Please contact me if you need assistance. -- 722912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722912 761047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 722912 to libcogl20, forcibly merging 761047 722912
Processing commands for cont...@bugs.debian.org: reassign 722912 libcogl20 Bug #722912 [libclutter-1.0-0] libclutter-1.0-0: apt does not find an upgrade path from wheezy to jessie: libcogl12 : Breaks: libclutter-1.0-0 ( 1.14) but 1.10.8-2 is to be installed Bug reassigned from package 'libclutter-1.0-0' to 'libcogl20'. No longer marked as found in versions clutter-1.0/1.14.4-3 and clutter-1.0/1.18.2-1. Ignoring request to alter fixed versions of bug #722912 to the same values previously set forcemerge 761047 722912 Bug #761047 [libcogl20] libcogl20: breaks upgrade from wheezy to jessie Bug #722912 [libcogl20] libclutter-1.0-0: apt does not find an upgrade path from wheezy to jessie: libcogl12 : Breaks: libclutter-1.0-0 ( 1.14) but 1.10.8-2 is to be installed Marked as found in versions cogl/1.18.2-2. Merged 722912 761047 thanks Stopping processing here. Please contact me if you need assistance. -- 722912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722912 761047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761047 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#745844: marked as done (libimobiledevice-utils: Segfault with iphone 3GS on many utilities)
Your message dated Thu, 06 Nov 2014 14:59:33 + with message-id 2c035198dda5434c76ad5a4eff4b9...@mail.adsl.funky-badger.org and subject line Re: [Pkg-gtkpod-devel] Bug#745844: libimobiledevice: Re: libimobiledevice-utils: Segfault with iphone 3GS on many utilities has caused the Debian Bug report #745844, regarding libimobiledevice-utils: Segfault with iphone 3GS on many utilities 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.) -- 745844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libimobiledevice-utils Version: 1.1.6+dfsg-1 Severity: important Dear Maintainer, I work under the gnome-shell environment, with systemd, network-manager, and every recommended package for this (batteries included). When plugging my iphone 3GS (under iOS 5, if I am not mistaken; definitely not iOS 7), I get the following log trace: avril 25 13:32:15 fiona kernel: iphone-set-info[2893]: segfault at 0 ip 7ff2caa94ada sp 7fff700cd438 error 4 in libc-2.18.so[7ff2caa13000+1a] avril 25 13:33:23 fiona kernel: iphone-set-info[3014]: segfault at 0 ip 7f2c27cbdada sp 7fff089dc978 error 4 in libc-2.18.so[7f2c27c3c000+1a] avril 25 13:44:44 fiona kernel: iphone-set-info[3522]: segfault at 0 ip 7f77b0b6bada sp 7fff11c9ece8 error 4 in libc-2.18.so[7f77b0aea000+1a] (various plug/unplug). When launching in the console, ideviceinfo (and most other utilities) segfault; root@fiona:/home/jcdubacq# gdb ideviceinfo GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/ideviceinfo...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/ideviceinfo warning: no loadable sections found in added symbol-file system-supplied DSO at 0x77ffa000 warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. strlen () at ../sysdeps/x86_64/strlen.S:106 106 ../sysdeps/x86_64/strlen.S: Aucun fichier ou dossier de ce type. (gdb) bt #0 strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x7747081e in __GI___strdup (s=0x0) at strdup.c:41 #2 0x77bd81da in plist_new_string () from /usr/lib/x86_64-linux-gnu/libplist.so.2 #3 0x779be93c in ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 #4 0x779bf403 in lockdownd_client_new_with_handshake () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 #5 0x00401567 in ?? () #6 0x77410b45 in __libc_start_main (main=0x401080, argc=1, argv=0x7fffe648, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe638) at libc-start.c:287 #7 0x00401612 in ?? () Can I help in any other way? I use iphone tethering rarely, but when I do, I depend on it (and I will depend on it soon for some lecture). -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (800, 'testing'), (200, 'unstable'), (80, '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 Versions of packages libimobiledevice-utils depends on: ii libc6 2.18-4 ii libgcrypt111.5.3-4 ii libgnutls262.12.23-13 ii libimobiledevice4 1.1.6+dfsg-1 ii libplist2 1.11-3 ii libtasn1-6 3.4-3 ii libusbmuxd21.0.9-1 libimobiledevice-utils recommends no packages. libimobiledevice-utils suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.0.8+git20140527.e72f2f7-1 On 2014-09-24 7:52, Chow Loong Jin wrote: On Tue, Sep 16, 2014 at 10:51:35AM +0200, Shérab wrote: Hi, I just uploaded a usbmuxd snapshot, seeing that upstream hasn't done anything to usbmuxd for a couple of months. I understand a release is coming soon. That upload fixes the bug for me, thanks!!!
Bug#766484: FTBFS in a cowbuilder: Error: listen EADDRNOTAVAIL
Hi,
just trying on an i386 buildd, it fails by:
ln -fs out/Release/node node
/usr/bin/python tools/test.py --arch=ia32 simple
=== release test-crypto-stream ===
Path: simple/test-crypto-stream
assert.js:92
throw new assert.AssertionError({
^
AssertionError: false == true
at Decipheriv.end (/«PKGBUILDDIR»/test/simple/test-crypto-stream.js:74:5)
at Decipheriv.anonymous (/«PKGBUILDDIR»/test/common.js:198:15)
at Decipheriv.emit (events.js:117:20)
at done (_stream_transform.js:190:19)
at _stream_transform.js:131:9
at Decipheriv.Cipher._flush (crypto.js:269:5)
at Decipheriv.anonymous (_stream_transform.js:130:12)
at Decipheriv.g (events.js:180:16)
at Decipheriv.emit (events.js:117:20)
at finishMaybe (_stream_writable.js:360:12)
Command: out/Release/node /«PKGBUILDDIR»/test/simple/test-crypto-stream.js
[03:34|% 100|+ 607|- 1]: Done
make[1]: *** [test-simple] Error 1
Makefile:114: recipe for target 'test-simple' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [debian/stamp-makefile-check] Error 2
/usr/share/cdbs/1/class/makefile.mk:67: recipe for target
'debian/stamp-makefile-check' failed
Andi
--
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 762272 is important
Processing commands for cont...@bugs.debian.org:
# Worked around
severity 762272 important
Bug #762272 {Done: Helmut Grohne hel...@subdivi.de} [src:doxygen] doxygen:
segfaults when building efl (on ix86 amd amd64)
Severity set to 'important' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
762272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: user release.debian....@packages.debian.org, tagging 701814, tagging 709198, tagging 694986 ...
Processing commands for cont...@bugs.debian.org: # RT sprint decision (-ignore, is-blocker) # moreinfo/unreproduciable changes are BTS cleaning user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was ni...@thykier.net). tags 701814 + jessie-ignore Bug #701814 [os-prober] os-prober: damages XFS exported via iSCSI but not mounted locally; potential data loss Added tag(s) jessie-ignore. tags 709198 + jessie-ignore Bug #709198 [debconf] debconf: should not use python in maintainer scripts Added tag(s) jessie-ignore. tags 694986 + jessie-ignore Bug #694986 [initscripts] flash-kernel: postinst modifies /etc/default/rcS Added tag(s) jessie-ignore. tags 745835 + jessie-ignore Bug #745835 [lynx-cur] lynx-cur: certificate revocation is not checked Added tag(s) jessie-ignore. tags 752610 + jessie-ignore Bug #752610 [lynx-cur] lynx: Can connect to CVE-2014-0092 test site Added tag(s) jessie-ignore. severity 715204 important Bug #715204 [automake] automake: Doesn't use TESTS_ENVIRONMENT with parallel test Severity set to 'important' from 'serious' severity 747054 important Bug #747054 [eclipse] FTBFS: package javax.servlet.http does not exist Severity set to 'important' from 'serious' tags 747054 - unreproducible Bug #747054 [eclipse] FTBFS: package javax.servlet.http does not exist Removed tag(s) unreproducible. severity 649038 important Bug #649038 [elfutils] elfutils FTBFS on kfreebsd Severity set to 'important' from 'serious' usertags 714045 jessie-is-blocker There were no usertags set. Usertags are now: jessie-is-blocker. tags 747141 + jessie-ignore Bug #747141 [debhelper] debhelper: dh_installdocs --link-doc forces source-version dependencies Added tag(s) jessie-ignore. severity 765017 normal Bug #765017 [spice-client-glib-usb-acl-helper] SECURITY - normal users are allowed full access to USB devices per default Severity set to 'normal' from 'critical' tags 765380 + jessie-ignore Bug #765380 [src:gcc-4.8] don't ship gcc-4.8 with jessie Added tag(s) jessie-ignore. retitle 765380 gcc-4.8: do not ship with Jessie+1 Bug #765380 [src:gcc-4.8] don't ship gcc-4.8 with jessie Changed Bug title to 'gcc-4.8: do not ship with Jessie+1' from 'don't ship gcc-4.8 with jessie' tags 756179 + moreinfo Bug #756179 [efibootmgr] grub-efi-amd64: Boot failure after upgrade to 2.02~beta2-11 Added tag(s) moreinfo. severity 756179 important Bug #756179 [efibootmgr] grub-efi-amd64: Boot failure after upgrade to 2.02~beta2-11 Severity set to 'important' from 'critical' severity 764692 important Bug #764692 [libc0.1-dev] glibc: removed __FAVOR_BSD from features.h Severity set to 'important' from 'serious' tags 741464 - moreinfo unreproducible Bug #741464 [grub-pc-bin] grub-pc-bin: freezes after terminal_input at_keyboard Removed tag(s) unreproducible and moreinfo. severity 741464 grave Bug #741464 [grub-pc-bin] grub-pc-bin: freezes after terminal_input at_keyboard Severity set to 'grave' from 'critical' tags 765567 + jessie-ignore Bug #765567 [docbook-xsl] Please use non-recursive version Added tag(s) jessie-ignore. severity 764590 important Bug #764590 [procps] procps: fails to build from source in sid on amd64 Severity set to 'important' from 'critical' severity 740509 important Bug #740509 [glibc] ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address Bug #765882 [glibc] freebsd-net-tools: ifconfig ioctl siocaifaddr Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' severity 766370 important Bug #766370 [libc6] login[5797]: segfault at ip sp error 14 in librt-2.19.so Severity set to 'important' from 'critical' tags 766370 + unreproducible Bug #766370 [libc6] login[5797]: segfault at ip sp error 14 in librt-2.19.so Added tag(s) unreproducible. tags 766397 + jessie-ignore Bug #766397 [emacs24] emacs/gnus: Uses s_client to for SSL. Added tag(s) jessie-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 649038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649038 694986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694986 701814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701814 709198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709198 714045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714045 715204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715204 740509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740509 741464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741464 745835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745835 747054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747054 747141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747141 752610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752610 756179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756179 764590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764590 764692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764692 765017:
Bug#682420: marked as done (libpaper: Multi-Arch: same but postrm removes arch-independent configuration)
Your message dated Thu, 06 Nov 2014 15:35:41 + with message-id e1xmp65-0003al...@franck.debian.org and subject line Bug#682420: fixed in libpaper 1.1.24+nmu4 has caused the Debian Bug report #682420, regarding libpaper: Multi-Arch: same but postrm removes arch-independent configuration 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.) -- 682420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libpaper Version: 1.1.24+nmu2 Severity: important X-Debbugs-Cc: Colin Watson cjwat...@ubuntu.com, Wookey woo...@wookware.org libpaper1.postrm contains the following code: case $1 in purge) [ -x /usr/bin/ucf ] ucf --purge /etc/papersize rm -f /etc/papersize ;; esac Therefore if I run the following operations, /etc/papersize will be removed even though libpaper1 is still installed. dpkg -i libpaper1_1.1.24+nmu2_i386.deb libpaper1_1.1.24+nmu2_amd64.deb echo a4 /etc/papersize dpkg --purge libpaper1_1.1.24+nmu2_amd64.deb Possible fixes: a) Remove Multi-Arch: same for libpaper1 in wheezy b) Manage /etc/papersize in a separate libpaper-common package. The configuration file's name doesn't vary with the soname so the current state seems like a policy §10.7.4 violation waiting to happen anyway. c) Guard the code that purges /etc/papersize with a test that libpaper1 is already purged for all other architectures. Sorry to notice this so late. Thoughts? Regards, Jonathan ---End Message--- ---BeginMessage--- Source: libpaper Source-Version: 1.1.24+nmu4 We believe that the bug you reported is fixed in the latest version of libpaper, 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 682...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated libpaper 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: SHA512 Format: 1.8 Date: Sat, 01 Nov 2014 14:35:13 +0100 Source: libpaper Binary: libpaper1 libpaper-utils libpaper-dev Architecture: source amd64 Version: 1.1.24+nmu4 Distribution: unstable Urgency: medium Maintainer: Giuseppe Sacco eppes...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: libpaper-dev - library for handling paper characteristics (development files) libpaper-utils - library for handling paper characteristics (utilities) libpaper1 - library for handling paper characteristics Closes: 658159 682420 688293 Changes: libpaper (1.1.24+nmu4) unstable; urgency=medium . * Non-maintainer upload. * Fix Multi-Arch: same but postrm removes arch-independent configuration: Guard removal of /etc/papersize in libpaper1.postrm with check for DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT; depend on dpkg (= 1.17.2). Thanks to Ivo De Decker for the proposal. (Closes: #682420) * Debconf template translations: - new: Polish, thanks Michał Kułach, closes: #658159 - updated: Turkish, thanks Atila KOÇ, closes: #688293 Checksums-Sha1: 1ed90df822dd40b679caa45bc733296e2c98edbd 1748 libpaper_1.1.24+nmu4.dsc 830c7e5c0f77d4f8a314ba3ea93dfd954bdd3a4e 370195 libpaper_1.1.24+nmu4.tar.gz 34ea87b52c033e2450ee8291a7ee29f6036ca6b0 22036 libpaper1_1.1.24+nmu4_amd64.deb 78644c7ef87a42aa1519f2a02182a11bd5dab1a2 17472 libpaper-utils_1.1.24+nmu4_amd64.deb f694659f2fe0679d40909e89cb114553dc257555 17028 libpaper-dev_1.1.24+nmu4_amd64.deb Checksums-Sha256: 8d152b3bad6bdfc1bbd62c608bd3fee9c021ec920f721a531f5dc3505da79ec2 1748 libpaper_1.1.24+nmu4.dsc 2491fce3f590d922d2d3070555df4425921b89c76a18e1c62e36336d6657526a 370195 libpaper_1.1.24+nmu4.tar.gz 1e388a177c04f0f87e9920cec3b6f417ed359578e147f4856e0735fb2f8cd255 22036 libpaper1_1.1.24+nmu4_amd64.deb 58abd2460e94ebfe33eecfdb3c19dc2e0ead9652267cb47e0cad07b82616915d 17472 libpaper-utils_1.1.24+nmu4_amd64.deb e666ff064b4592b2a44df7b37663235d361ea09ce03382ad576f73c598576dc4 17028 libpaper-dev_1.1.24+nmu4_amd64.deb Files: baa103e42274cadc58fc5a57c311b222 1748 libs optional libpaper_1.1.24+nmu4.dsc 155d2e589e2f4ef163de8fbbc5d3dd1e 370195
Bug#759959: marked as done (midori: FTBFS: dpkg-query: error: --listfiles needs at least one package name argument)
Your message dated Thu, 06 Nov 2014 15:38:13 + with message-id e1xmp8x-0003av...@franck.debian.org and subject line Bug#759959: fixed in midori 0.4.3+dfsg-0.2 has caused the Debian Bug report #759959, regarding midori: FTBFS: dpkg-query: error: --listfiles needs at least one package name argument 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.) -- 759959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: midori Version: 0.4.3+dfsg-0.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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): make[1]: Entering directory '/«BUILDDIR»/midori-0.4.3+dfsg' dpkg-query: package 'libwebkitgtk-dev' is not available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libwebkitgtk-dev' is not available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: error: --listfiles needs at least one package name argument Use --help for help about querying packages. dpkg-query: package 'libwebkitgtk-dev' is not available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libwebkitgtk-dev' is not available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: error: --listfiles needs at least one package name argument Use --help for help about querying packages. dpkg-query: package 'libwebkitgtk-dev' is not available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: error: --listfiles needs at least one package name argument Use --help for help about querying packages. dpkg-query: package 'libwebkitgtk-dev' is not available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libwebkitgtk-dev' is not available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: error: --listfiles needs at least one package name argument Use --help for help about querying packages. presubj parameters: Replacing %LIBWEBKIT_PKG% with Replacing %GTKLAUNCHER% with test -f /var/lib/dpkg/info/.list debian/rules:44: recipe for target 'debian/presubj' failed make[1]: *** [debian/presubj] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/midori_0.4.3+dfsg-0.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. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- Source: midori Source-Version: 0.4.3+dfsg-0.2 We believe that the bug you reported is fixed in the latest version of midori, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Neil Williams codeh...@debian.org (supplier of updated midori package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Nov 2014 14:04:07 + Source: midori Binary: midori midori-dbg Architecture: source amd64 Version: 0.4.3+dfsg-0.2 Distribution: unstable Urgency: medium Maintainer: Ryan Niebur
Bug#695271: marked as done (libpaper1: harmful purge action in M-A:same package)
Your message dated Thu, 06 Nov 2014 15:35:41 + with message-id e1xmp65-0003al...@franck.debian.org and subject line Bug#682420: fixed in libpaper 1.1.24+nmu4 has caused the Debian Bug report #682420, regarding libpaper1: harmful purge action in M-A:same package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 682420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libpaper1 Version: 1.1.24+nmu2 Severity: important The postrm purge removes /etc/papersize. In a setting where you can purge libpaper1:i386 while still using libpaper1:amd64 this causes trouble. The bug is currently unreproducible due to ucf lacking M-A:foreign. As soon as ucf gains that flag, this bug is RC. Helmut ---End Message--- ---BeginMessage--- Source: libpaper Source-Version: 1.1.24+nmu4 We believe that the bug you reported is fixed in the latest version of libpaper, 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 682...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated libpaper 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: SHA512 Format: 1.8 Date: Sat, 01 Nov 2014 14:35:13 +0100 Source: libpaper Binary: libpaper1 libpaper-utils libpaper-dev Architecture: source amd64 Version: 1.1.24+nmu4 Distribution: unstable Urgency: medium Maintainer: Giuseppe Sacco eppes...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: libpaper-dev - library for handling paper characteristics (development files) libpaper-utils - library for handling paper characteristics (utilities) libpaper1 - library for handling paper characteristics Closes: 658159 682420 688293 Changes: libpaper (1.1.24+nmu4) unstable; urgency=medium . * Non-maintainer upload. * Fix Multi-Arch: same but postrm removes arch-independent configuration: Guard removal of /etc/papersize in libpaper1.postrm with check for DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT; depend on dpkg (= 1.17.2). Thanks to Ivo De Decker for the proposal. (Closes: #682420) * Debconf template translations: - new: Polish, thanks Michał Kułach, closes: #658159 - updated: Turkish, thanks Atila KOÇ, closes: #688293 Checksums-Sha1: 1ed90df822dd40b679caa45bc733296e2c98edbd 1748 libpaper_1.1.24+nmu4.dsc 830c7e5c0f77d4f8a314ba3ea93dfd954bdd3a4e 370195 libpaper_1.1.24+nmu4.tar.gz 34ea87b52c033e2450ee8291a7ee29f6036ca6b0 22036 libpaper1_1.1.24+nmu4_amd64.deb 78644c7ef87a42aa1519f2a02182a11bd5dab1a2 17472 libpaper-utils_1.1.24+nmu4_amd64.deb f694659f2fe0679d40909e89cb114553dc257555 17028 libpaper-dev_1.1.24+nmu4_amd64.deb Checksums-Sha256: 8d152b3bad6bdfc1bbd62c608bd3fee9c021ec920f721a531f5dc3505da79ec2 1748 libpaper_1.1.24+nmu4.dsc 2491fce3f590d922d2d3070555df4425921b89c76a18e1c62e36336d6657526a 370195 libpaper_1.1.24+nmu4.tar.gz 1e388a177c04f0f87e9920cec3b6f417ed359578e147f4856e0735fb2f8cd255 22036 libpaper1_1.1.24+nmu4_amd64.deb 58abd2460e94ebfe33eecfdb3c19dc2e0ead9652267cb47e0cad07b82616915d 17472 libpaper-utils_1.1.24+nmu4_amd64.deb e666ff064b4592b2a44df7b37663235d361ea09ce03382ad576f73c598576dc4 17028 libpaper-dev_1.1.24+nmu4_amd64.deb Files: baa103e42274cadc58fc5a57c311b222 1748 libs optional libpaper_1.1.24+nmu4.dsc 155d2e589e2f4ef163de8fbbc5d3dd1e 370195 libs optional libpaper_1.1.24+nmu4.tar.gz e91c4facf9611b26e0f3d0cf808067e1 22036 libs optional libpaper1_1.1.24+nmu4_amd64.deb 935a408a202623a47477d1b59037b5cb 17472 utils optional libpaper-utils_1.1.24+nmu4_amd64.deb 3f0ad9777c4c78a32608c7b56e483208 17028 libdevel optional libpaper-dev_1.1.24+nmu4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUVOHCXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGBA8P/iVbz3EvVbeQcRQ+4DTO1lU7 8hPK0pg3Uxy3e9/i12G6eFCwR3Y80x25Bui3bXxwzy4D6jmod08SLpPxqXdyf4T5 bxB7Zr/+akovacQk55T843IWDSg7kA6GCJZMjyqWuvYh3Ika8K7oFoHb4t87LOaE scmZEUJHe8ey5kRRey/tJxEQoMZXPsdZ0vRhJLq05GysOub/KGyL+47pytSC9tjJ
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
Cyril Brulebois k...@debian.org (2014-09-06): Philipp Kern pk...@debian.org (2014-09-05): On Fri, Sep 05, 2014 at 09:55:24AM +0200, Cyril Brulebois wrote: Steven Chamberlain ste...@pyro.eu.org (2014-08-31): On 31/08/14 07:00, Philipp Kern wrote: Is perhaps the same true for stop_rdnssd() on the next line? So Steven committed a patch in to git, getting rid of the dhcp part; Philipp, should I upload that and we'll figure out the rdnssd part another time? ACK. I wanted to look at it today, but meh. rdnssd isn't as critical as it won't take your interface down if you kill it. You just won't get updated DNS information. Alright, thanks. Quickly checked on Linux that going back to the network step still kills the dhcp client and get it started again. Tagged and uploaded. Mraw, KiBi. Should that get fixed in wheezy as well? I've spotted this is still marked as affecting this release but if that's no practical issue (we would have been aware of this for quite some time already I guess), it might be OK to wheezy-ignore it or notfound it in wheezy's version. Thoughts? Mraw, KiBi. signature.asc Description: Digital signature
Bug#753442: debootstrap: host's /run/shm gets unmounted after debootstrap run
Daniel Reichelt deb...@nachtgeist.net (2014-07-02): Package: debootstrap Version: 1.0.48+deb7u1 Severity: critical Justification: breaks unrelated software Hi, after running debootstrap the host's /run/shm tmpfs mount gets unmounted. Since the mount point /run/shm itself is set to root:root/750, this breaks any other package which relies on being able to write to /run/shm as non-root. (In my case, python's multiprocessing fails miserably due to the lack of write privileges to /run/shm, which is how I noticed this issue in the first place.) I tried debootstrap on clean and current wheezy and jessie installations, only wheezy was affected. Let me know if you need any further information. I seem to be unable to reproduce it with 1.0.60~bpo70+1 but I can with 1.0.48+deb7u1; I didn't spot anything obvious from a very quick look, but I'll try to track this down a bit later (probably after the release sprint). Mraw, KiBi. signature.asc Description: Digital signature
Bug#764437: console-setup hangs during install in jessie/wheezy on eeepc 1005ha
Control: severity -1 important marv mar...@ctech.ca (2014-10-08): Package: console-setup Version: 1.113 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, Installing Debian Wheezy or Jessie with a net install iso on my EEEPC 1005HA just won't work. It will hang or reboot on the installing base system around 99% when console-setup runs. I have tried running the setup with boot params acpi=off, nomodeset, blacklisting the i915 module, ... nothing gets the job done. Only way i've found to get around it is to rename or delete /target/usr/bin/ckbcomp during the install (and you have to be quick to catch it). After doing so and booting the now successful install, renaming /usr/bin/ckbcomp back, the system will not boot any more. I've tried installing with different keymaps/locales nothing seems to help... Hi, thanks for the bug report. Since this seems to be very (hardware) specific, I'm adjusting the severity for the time being. Hopefully somebody will be able to give some hints on how to debug this further. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#764437: console-setup hangs during install in jessie/wheezy on eeepc 1005ha
Processing control commands: severity -1 important Bug #764437 [console-setup] console-setup hangs during install in jessie/wheezy on eeepc 1005ha Severity set to 'important' from 'critical' -- 764437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package libxslt
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package libxslt # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #750593 (http://bugs.debian.org/750593) # Bug title: xsltproc: bus error on some architectures # * http://bugzilla.gnome.org/show_bug.cgi?id=736077 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - NOTABUG # * closed upstream tags 750593 + fixed-upstream Bug #750593 [xsltproc] xsltproc: bus error on some architectures Added tag(s) fixed-upstream. usertags 750593 + status-RESOLVED resolution-NOTABUG There were no usertags set. Usertags are now: resolution-NOTABUG status-RESOLVED. thanks Stopping processing here. Please contact me if you need assistance. -- 750593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593 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#757689: Still segfault
Just updated my jessie testing system, which is same as above, except that it now has kernel 3.16.3 installed. Ran full update dist-upgrade. Retested lshw. Got this: ckosloff@notosh:~$ su Password: root@notosh:/home/ckosloff# lshw Segmentation fault root@notosh:/home/ckosloff# -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745441: totem-plugins-dvb-daemon: Failed activating DVB DBUS service
On 21/04/14 20:20, Frederik Himpe wrote: Package: totem-plugins-dvb-daemon Version: 1:0.2.10-1 Severity: grave Tags: upstream patch Justification: renders package unusable When activating the DVB Daemon plug-in in Totem, this error pops up: Failed activating DVB DBus service 'NoneType' object has no attribute 'set_image' Traceback (most recent call last): File /usr/lib/totem/plugins/dvb-daemon/dvb-daemon.py, line 680, in _on_group_loaded self._configure_mode() File /usr/lib/totem/plugins/dvb-daemon/dvb-daemon.py, line 481, in _configure_mode self.single_group = self.channels[group_iter][self.channels.COL_GROUP] File /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py, line 788, in __getitem__ aiter = self._getiter(key) File /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py, line 776, in _getiter aiter = self.get_iter(key) File /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py, line 810, in get_iter path = self._coerce_path(path) File /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py, line 785, in _coerce_path return TreePath(path) File /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py, line 1135, in __new__ path = :.join(str(val) for val in path) TypeError: 'NoneType' object is not iterable DVB functionality is not working in Totem after that. This is upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=709483 , which has a patch. I've backported the patch and tested it, but there's an additional problem now. Totem switch to python3 plugins, but the dvb plugin is python2, so it won't load. See https://bugzilla.gnome.org/show_bug.cgi?id=739742 If nobody fixes this soon with a minimal patch, we'll probably have to remove the totem dvb plugin. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704953: marked as done (Crash recovery crashes everytime, cannot start anymore)
Your message dated Thu, 06 Nov 2014 16:59:41 + with message-id 545ba8fd.3030...@debian.org and subject line Re: Bug#704953: Crash recovery crashes everytime, cannot start anymore has caused the Debian Bug report #704953, regarding Crash recovery crashes everytime, cannot start anymore 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.) -- 704953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: epiphany-browser-webkit2 Version: 3.7.91-1 Severity: serious After crashing with pages open, now trying to start crashes again everytime. Below is a backtrace after starting under gdb with debug symbols installed. Thread 10 (Thread 0x7fff933ec700 (LWP 2083)): #0 0x745f3165 in sqlite3BtreeSetCachedRowid (iRowid=0, pCur=optimized out) at sqlite3.c:53784 #1 sqlite3VdbeExec (p=p@entry=0x7fff7c013998) at sqlite3.c:4378 #2 0x745d8911 in sqlite3Step (p=0x7fff7c013998) at sqlite3.c:64047 #3 sqlite3_step (pStmt=0x7fff7c013998) at sqlite3.c:64120 #4 sqlite3_step (pStmt=0x7fff7c013998) at sqlite3.c:64108 #5 0x00491365 in ephy_sqlite_statement_step (self=self@entry=0x17de150, error=error@entry=0x7fff933ebb88) at /home/kov/debian/epiphany/build-area/epiphany-browser-3.7.91/./lib/ephy-sqlite-statement.c:177 #6 0x00485218 in ephy_history_service_find_url_rows (self=optimized out, query=optimized out) at /home/kov/debian/epiphany/build-area/epiphany-browser-3.7.91/./lib/history/ephy-history-service-urls-table.c:352 #7 0x00481409 in ephy_history_service_execute_query_urls (self=optimized out, query=optimized out, result=0x19d84c0) at /home/kov/debian/epiphany/build-area/epiphany-browser-3.7.91/./lib/history/ephy-history-service.c:740 #8 0x00481d1a in ephy_history_service_process_message (message=0x19d84a0, self=0x17ccc00) at /home/kov/debian/epiphany/build-area/epiphany-browser-3.7.91/./lib/history/ephy-history-service.c:1230 #9 run_history_service_thread (self=0x17ccc00) at /home/kov/debian/epiphany/build-area/epiphany-browser-3.7.91/./lib/history/ephy-history-service.c:469 #10 0x7256fa05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x71cc1e0e in start_thread (arg=0x7fff933ec700) at pthread_create.c:311 #12 0x719f594d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 9 (Thread 0x7fff8b7fe700 (LWP 2082)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x75d7dc0b in WebCore::IconDatabase::syncThreadMainLoop() () at ../Source/WebCore/loader/icon/IconDatabase.cpp:1463 #2 0x75d7de28 in WebCore::IconDatabase::iconDatabaseSyncThread() () at ../Source/WebCore/loader/icon/IconDatabase.cpp:1058 #3 0x7078f191 in WTF::wtfThreadEntryPoint(void*) () at ../Source/WTF/wtf/ThreadingPthreads.cpp:196 #4 0x71cc1e0e in start_thread (arg=0x7fff8b7fe700) at pthread_create.c:311 #5 0x719f594d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 8 (Thread 0x7fff8bfff700 (LWP 2081)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7258b605 in g_cond_wait_until () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x725216f1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7257014a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7256fa05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x71cc1e0e in start_thread (arg=0x7fff8bfff700) at pthread_create.c:311 #6 0x719f594d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 7 (Thread 0x7fff93bed700 (LWP 2079)): #0 0x719ea1ad in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7254bdac in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7254c28a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7078f191 in WTF::wtfThreadEntryPoint(void*) () at ../Source/WTF/wtf/ThreadingPthreads.cpp:196 #4 0x71cc1e0e in start_thread (arg=0x7fff93bed700) at pthread_create.c:311 #5 0x719f594d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 6 (Thread 0x7fffe1371700 (LWP 2078)): #0 0x719ea1ad in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7254bdac in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7254c28a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3
Bug#766195: marked as done (linux: Network-related panic in Linux 3.2.63 (CVE-2014-7207))
Your message dated Thu, 06 Nov 2014 17:02:15 +
with message-id e1xmqrr-0006zj...@franck.debian.org
and subject line Bug#766195: fixed in linux 3.2.63-2+deb7u1
has caused the Debian Bug report #766195,
regarding linux: Network-related panic in Linux 3.2.63 (CVE-2014-7207)
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.)
--
766195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: linux
Version: 3.2.63-2
Severity: important
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
X-Debbugs-Cc: debian-ad...@lists.debian.org, m...@debian.org
Hi,
after the latest point release some debian.org hosts became unreliable.
That was tracked down to a panic in the networking code. Ben provided a
test patch:
From: Ben Hutchings b...@decadent.org.uk
Date: Tue, 21 Oct 2014 00:49:22 +0100
Subject: ipv6: ipv6_select_ident: handle null rt
Forwarded: not-needed
In Linux 3.2, ipv6_select_ident() can apparently still be called with
rt == NULL and must avoid dereferencing it in this case.
We should probably fix the callers, so WARN_ON_ONCE to get a clue
about how this happens.
---
--- a/net/ipv6/ip6_output.c
+++ b/net/ipv6/ip6_output.c
@@ -604,13 +604,18 @@ void ipv6_select_ident(struct frag_hdr *
static bool hashrnd_initialized = false;
u32 hash, id;
+ if (WARN_ON_ONCE(!rt)) {
+ hash = 0;
+ goto reserve;
+ }
+
if (unlikely(!hashrnd_initialized)) {
hashrnd_initialized = true;
get_random_bytes(ip6_idents_hashrnd,
sizeof(ip6_idents_hashrnd));
}
hash = __ipv6_addr_jhash(rt-rt6i_dst.addr, ip6_idents_hashrnd);
hash = __ipv6_addr_jhash(rt-rt6i_src.addr, hash);
-
+reserve:
id = ip_idents_reserve(hash, 1);
fhdr-identification = htonl(id);
}
which resulted in the following trace:
[ 436.375412] [ cut here ]
[ 436.375439] WARNING: at /usr/src/linux-3.2.63/net/ipv6/ip6_output.c:607
ipv6_select_ident+0x28/0x8b()
[ 436.375446] Hardware name: ProLiant DL585 G2
[ 436.375451] Modules linked in: ipmi_devintf ip6t_REJECT ip6t_LOG
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT ipt_ULOG
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ses
xt_hashlimit enclosure xt_multiport iptable_filter ip_tables x_tables crc32c
ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp
libiscsi scsi_transport_iscsi bridge sd_mod dm_round_robin crc_t10dif bonding
xfs ext4 crc16 jbd2 hmac drbd lru_cache 8021q garp stp dm_snapshot loop
dm_multipath scsi_dh vhost_net tun macvtap macvlan kvm_amd kvm radeon ttm
ipmi_si drm_kms_helper ipmi_msghandler k8temp powernow_k8 mperf hpilo drm
power_supply i2c_algo_bit shpchp amd64_edac_mod edac_mce_amd edac_core psmouse
hpwdt i2c_core snd_pcm snd_page_alloc snd_timer snd soundcore processor cdc_acm
pcspkr evdev serio_raw container button thermal_sys ext3 mbcache jbd dm_mod
usbhid hid sg sr_mod cdrom hpsa ata_generic lpfc pata_amd uhci_hcd libata
scsi_transport_fc scsi_tgt ohci_hcd bnx2 ehci_hcd cciss scsi_mod usbcore
usb_common [last unloaded: scsi_wait_scan]
[ 436.375642] Pid: 12085, comm: unbound Not tainted 3.2.0-4-amd64 #1 Debian
3.2.63-2a~test
[ 436.375647] Call Trace:
[ 436.375666] [81046d61] ? warn_slowpath_common+0x78/0x8c
[ 436.375676] [812ff40f] ? ipv6_select_ident+0x28/0x8b
[ 436.375685] [81311411] ? udp6_ufo_fragment+0x124/0x1a2
[ 436.375696] [812fd569] ? ipv6_gso_segment+0xb8/0x14e
[ 436.375705] [81036273] ? __wake_up_common+0x40/0x77
[ 436.375715] [812905b4] ? skb_gso_segment+0x208/0x28b
[ 436.375725] [81037f7b] ? __wake_up+0x35/0x46
[ 436.375734] [81071295] ? arch_local_irq_save+0x11/0x17
[ 436.375746] [813508f9] ? _raw_spin_lock_irqsave+0x9/0x25
[ 436.375756] [8105266a] ? lock_timer_base.isra.29+0x23/0x47
[ 436.375764] [81350937] ? _raw_spin_unlock_irqrestore+0xe/0xf
[ 436.375771] [81052926] ? __mod_timer+0x139/0x14b
[ 436.375781] [8104c2c9] ? _local_bh_enable_ip.isra.11+0x1e/0x88
[ 436.375794] [a06b159a] ? ip6t_do_table+0x5b2/0x5e4 [ip6_tables]
[ 436.375805] [81292337] ? dev_hard_start_xmit+0x32d/0x518
[ 436.375814] [812b28bd] ? nf_iterate+0x41/0x77
[ 436.375823] [812a8a63] ? sch_direct_xmit+0x61/0x135
[ 436.375833] [812927e4] ? dev_queue_xmit+0x2c2/0x46b
[ 436.375856] [a05db84b] ?
Bug#708946: GFDL documentation with front and back cover
On Sun, May 19, 2013 at 05:14:22PM +0200, bastien ROUCARIES wrote: Grub documentation doc/grub.texi is not free. Please free grub. I started working on a grub-legacy-doc package today (#724474) and discovered something amusing. The licence change to the FDL was actually introduced *after* 0.97, and pulled into the Debian package by way of a CVS sync! This was even fixed previously in 0.97-12, but I think this was then reverted in 0.97-60 when the packaging switched to Bazaar branching. Rather than introducing a new source package for this, I'm therefore just going to revert these patches again. Whee. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765352: marked as done (wpa: arbitrary command execution via action scripts)
Your message dated Thu, 06 Nov 2014 17:06:08 + with message-id e1xmqvc-0007ox...@franck.debian.org and subject line Bug#765352: fixed in wpa 1.0-3+deb7u1 has caused the Debian Bug report #765352, regarding wpa: arbitrary command execution via action scripts 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.) -- 765352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: wpa Severity: serious Tags: security Hi, the following vulnerability was published for wpa. It affects both wpa-supplicant and hostapd: CVE-2014-3686[0]: action script execution vulnerability From https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-3686: Jouni Malinen discovered that a string supplied from a remote device could be supplied to a system() call in wpa_cli or hostapd_cli when running an action script (with the -a option), resulting in arbitrary command execution. This issue could also be triggered by an attacker within radio range. Patches are available from the following: http://w1.fi/security/2014-1/ 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-3686 https://security-tracker.debian.org/tracker/CVE-2014-3686 Please adjust the affected versions in the BTS as needed. -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ ---End Message--- ---BeginMessage--- Source: wpa Source-Version: 1.0-3+deb7u1 We believe that the bug you reported is fixed in the latest version of wpa, 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 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefan Lippers-Hollmann s@gmx.de (supplier of updated wpa 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: SHA512 Format: 1.8 Date: Wed, 15 Oct 2014 23:32:54 +0200 Source: wpa Binary: hostapd wpagui wpasupplicant wpasupplicant-udeb Architecture: source amd64 Version: 1.0-3+deb7u1 Distribution: wheezy-security Urgency: high Maintainer: Debian/Ubuntu wpasupplicant Maintainers pkg-wpa-de...@lists.alioth.debian.org Changed-By: Stefan Lippers-Hollmann s@gmx.de Description: hostapd- user space IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authentica wpagui - graphical user interface for wpa_supplicant wpasupplicant - client support for WPA and WPA2 (IEEE 802.11i) wpasupplicant-udeb - Client support for WPA and WPA2 (IEEE 802.11i) (udeb) Closes: 765352 Changes: wpa (1.0-3+deb7u1) wheezy-security; urgency=high . * Apply upstream patches for CVE-2014-3686 (Closes: #765352): - add os_exec() helper to run external programs - wpa_cli: Use os_exec() for action script execution - hostapd_cli: Use os_exec() for action script execution Checksums-Sha1: 280c90ff1ede69932f3d78efb01c1ce185a5f573 3157 wpa_1.0-3+deb7u1.dsc f89b69e4795eec697e4542309430b3003473704c 1973926 wpa_1.0.orig.tar.gz e273fe1731694119a74f08ffb4a60ab241815551 88566 wpa_1.0-3+deb7u1.debian.tar.gz d5e724d8042f681205052e7d749d63362410a9c2 476162 hostapd_1.0-3+deb7u1_amd64.deb 65be775a80baee10623991807a9c3b9788b9f0ff 368680 wpagui_1.0-3+deb7u1_amd64.deb cbe50b4186ff2d254c342e287060dad20edf4d46 608696 wpasupplicant_1.0-3+deb7u1_amd64.deb 3b5118d80b211b8a0b9e1c854c890047114d274d 154882 wpasupplicant-udeb_1.0-3+deb7u1_amd64.udeb Checksums-Sha256: 35cb768a6613d1528798f0e7b54aac5f553b3430fe3751fb614cef9772c29ac8 3157 wpa_1.0-3+deb7u1.dsc f2e91686ed250850b4929d8b48a8eae0b7b13c333ebbf4230d173379964240ef 1973926 wpa_1.0.orig.tar.gz ddab9c5bc1f69ae64f4e916f4e2af90bef9f946ea4f9ac69e11c7e460d096069 88566 wpa_1.0-3+deb7u1.debian.tar.gz c46d6012820a589a16063d42590e93fcc0fb7694186808772c61f3e6d4eada38 476162 hostapd_1.0-3+deb7u1_amd64.deb 318df62d73e7752da8f648d17f11b089b63a2ee81cf3dccc13a3fb23b5227282 368680 wpagui_1.0-3+deb7u1_amd64.deb 9e734bed8ac6b92742df5fcdf6d9359b7c9b6a15d784c8c774796dbd2ab07e62 608696
Bug#765440: deap-doc: please add Conflicts: python-deap-doc
All right, that's heavy problem. A fix is on the way. Greetings, Daniel Stender -- http://qa.debian.org/developer.php?login=debian%40danielstender.com GPG key: 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757689: strace of segfault
readlink(:00:01.0/driver/module, ../../../../module/drm, 4096) = 22
access(../../../../module/drm, F_OK) = -1 ENOENT (No such file or
directory)
access(:00:01.0/rom, F_OK)= 0
access(:00:01.0/irq, F_OK)= 0
open(:00:01.0/irq, O_RDONLY) = 3
read(3, 84\n, 1024) = 3
read(3, , 1024) = 0
close(3)= 0
access(:00:01.0/resource, F_OK) = 0
open(:00:01.0/resource, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f488eeb8000
read(3, 0xe000 0xeff..., 4096) = 741
read(3, , 4096) = 0
close(3)= 0
munmap(0x7f488eeb8000, 4096)= 0
open(:00:01.1/config, O_RDONLY) = 3
read(3,
\2\20@\230\7\4\20\0\0\0\3\4\20\0\200\0\4\0\306\362\0\0\0\0\0\0\0\0\0\0\0\0...,
64) = 64
read(3,
\0\0\0\0\0\0\0\0\tP\10\0y\0216\371\1X\3\6\0\0\0\0\20\240\222\0\241\201\0\0...,
192) = 192
close(3)= 0
access(:00:01.1/driver, F_OK) = 0
readlink(:00:01.1/driver, ../../../bus/pci/drivers/snd_hda...,
4096) = 38
readlink(:00:01.1/driver/module,
../../../../module/snd_hda_intel, 4096) = 32
access(../../../../module/snd_hda_intel, F_OK) = -1 ENOENT (No such
file or directory)
access(:00:01.1/rom, F_OK)= -1 ENOENT (No such file or
directory)
access(:00:01.1/irq, F_OK)= 0
open(:00:01.1/irq, O_RDONLY) = 3
read(3, 82\n, 1024) = 3
read(3, , 1024) = 0
close(3)= 0
access(:00:01.1/resource, F_OK) = 0
open(:00:01.1/resource, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f488eeb8000
read(3, 0xf2c6 0xf2c..., 4096) = 741
read(3, , 4096) = 0
close(3)= 0
munmap(0x7f488eeb8000, 4096)= 0
open(:00:02.0/config, O_RDONLY) = 3
read(3,
\\20k\25\0\0\0\0\0\0\0\6\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0..., 64)
= 64
read(3,
\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
192) = 192
close(3)= 0
access(:00:02.0/driver, F_OK) = -1 ENOENT (No such file or
directory)
access(:00:02.0/resource, F_OK) = 0
open(:00:02.0/resource, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f488eeb8000
read(3, 0x 0x000..., 4096) = 741
read(3, , 4096) = 0
close(3)= 0
munmap(0x7f488eeb8000, 4096)= 0
open(:00:02.2/config, O_RDONLY) = 3
read(3,
\\0209\24\7\0\20\0\0\0\4\6\20\0\201\0\0\0\0\0\0\0\0\0\0\1\4\0!!\0
..., 64) = 64
read(3,
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1X\3\310\0\0\0\0\20\240B\1\\200\0\0...,
192) = 192
close(3)= 0
access(:00:02.2/driver, F_OK) = 0
readlink(:00:02.2/driver, ../../../bus/pci/drivers/pciepor...,
4096) = 33
readlink(:00:02.2/driver/module, 0x7fff0eca6980, 4096) = -1 ENOENT
(No such file or directory)
access(:00:02.2/driver/module, F_OK) = -1 ENOENT (No such file or
directory)
access(:00:02.2/rom, F_OK)= -1 ENOENT (No such file or
directory)
access(:00:02.2/irq, F_OK)= 0
open(:00:02.2/irq, O_RDONLY) = 3
read(3, 49\n, 1024) = 3
read(3, , 1024) = 0
close(3)= 0
access(:00:02.2/resource, F_OK) = 0
open(:00:02.2/resource, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f488eeb8000
read(3, 0x 0x000..., 4096) = 969
read(3, , 4096) = 0
close(3)= 0
munmap(0x7f488eeb8000, 4096)= 0
open(:00:02.3/config, O_RDONLY) = 3
read(3,
\\0209\24\7\0\20\0\0\0\4\6\20\0\201\0\0\0\0\0\0\0\0\0\0\5\5\0\361\1\0\0...,
64) = 64
read(3,
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1X\3\310\0\0\0\0\20\240B\1\\200\0\0...,
192) = 192
close(3)= 0
access(:00:02.3/driver, F_OK) = 0
readlink(:00:02.3/driver, ../../../bus/pci/drivers/pciepor...,
4096) = 33
readlink(:00:02.3/driver/module, 0x7fff0eca6980, 4096) = -1 ENOENT
(No such file or directory)
access(:00:02.3/driver/module, F_OK) = -1 ENOENT (No such file or
directory)
access(:00:02.3/rom, F_OK)= -1 ENOENT (No such file or
directory)
access(:00:02.3/irq, F_OK)= 0
open(:00:02.3/irq, O_RDONLY) = 3
read(3, 50\n, 1024) = 3
read(3, , 1024) = 0
Bug#766114: [pkg-fso-maint] Bug#766114: Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf
Am Dienstag, 4. November 2014, 20:15:15 schrieb hikaru.deb...@web.de: That doesn't help: # apt-get install fso-deviced-n900 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libgcrypt11 libgee2 libgnutls26 libjpeg62 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: fso-deviced Recommended packages: fso-deviced-platform The following NEW packages will be installed: fso-deviced fso-deviced-n900 0 upgraded, 2 newly installed, 0 to remove and 114 not upgraded. Need to get 0 B/146 kB of archives. After this operation, 617 kB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package fso-deviced. (Reading database ... 42289 files and directories currently installed.) Preparing to unpack .../fso-deviced_0.12.0-2_armhf.deb ... Unpacking fso-deviced (0.12.0-2) ... Selecting previously unselected package fso-deviced-n900. Preparing to unpack .../fso-deviced-n900_0.12.0-2_armhf.deb ... Unpacking fso-deviced-n900 (0.12.0-2) ... Processing triggers for man-db (2.7.0.2-2) ... Processing triggers for dbus (1.8.8-2) ... Setting up fso-deviced (0.12.0-2) ... [FAIL] Starting freesmartphone.org device daemon : fso-deviced failed! invoke-rc.d: initscript fso-deviced, action start failed. dpkg: error processing package fso-deviced (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of fso-deviced-n900: fso-deviced-n900 depends on fso-deviced (= 0.12.0-2); however: Package fso-deviced is not configured yet. dpkg: error processing package fso-deviced-n900 (--configure): dependency problems - leaving unconfigured Processing triggers for dbus (1.8.8-2) ... Errors were encountered while processing: fso-deviced fso-deviced-n900 E: Sub-process /usr/bin/dpkg returned an error code (1) Hmm, it's a strange thing. If I recompile fso-deviced eveything works as expected. It seems, the generated .c files from vala-sources are broken. signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#766718: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Processing control commands: tags -1 + wontfix Bug #766718 [spamassassin] Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm Bug #767297 [spamassassin] spamassassin: Argument 0.80_2 isn't numeric in numeric lt () Added tag(s) wontfix. Added tag(s) wontfix. severity -1 important Bug #766718 [spamassassin] Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm Bug #767297 [spamassassin] spamassassin: Argument 0.80_2 isn't numeric in numeric lt () Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' -- 766718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766718 767297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767297 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#766718: Argument 0.80_2 isn't numeric in numeric ge (=) at /usr/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm
Control: tags -1 + wontfix Control: severity -1 important On Thu, Nov 06, 2014 at 11:42:28AM +0200, Damyan Ivanov wrote: Reassigning back since (1) IMO the bug lies in SA and (2) even if Net-DNS 0.81 reaches testing, SA needs an upload anyway with bumped dependency version. Not sure what severity to choose, so leaving that to SA maintainer. I am not interested in playing bug ping-pong with the libnet-dns-perl maintainers, though this bug lies with that package. It has already been fixed upstream and in unstable. Re-setting severity to important since functionality is not impaired. (The warnings, while extremely annoying, are ultimately inconsequential. Spamassassin continues to run as intended.) If we want to release jessie without this bug in it, then we need to get libnet-dns-perl 0.81 into the release. signature.asc Description: Digital signature
Bug#768226: marked as done (ghc-mod-el: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/emacs/site-lisp/ghc-mod/ghc.el)
Your message dated Thu, 06 Nov 2014 18:18:46 + with message-id e1xmrdv-0007km...@franck.debian.org and subject line Bug#768226: fixed in ghc-mod 5.2.1.1-2 has caused the Debian Bug report #768226, regarding ghc-mod-el: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/emacs/site-lisp/ghc-mod/ghc.el 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.) -- 768226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ghc-mod-el Version: 5.2.1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package ghc-mod-el. Unpacking ghc-mod-el (from .../ghc-mod-el_5.2.1.1-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/ghc-mod-el_5.2.1.1-1_all.deb (--unpack): trying to overwrite '/usr/share/emacs/site-lisp/ghc-mod/ghc.el', which is also in package ghc-mod 1.10.18-1 Errors were encountered while processing: /var/cache/apt/archives/ghc-mod-el_5.2.1.1-1_all.deb cheers, Andreas ghc-mod=1.10.18-1_ghc-mod-el=5.2.1.1-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: ghc-mod Source-Version: 5.2.1.1-2 We believe that the bug you reported is fixed in the latest version of ghc-mod, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Gröber d...@darkboxed.org (supplier of updated ghc-mod package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Nov 2014 17:42:36 +0100 Source: ghc-mod Binary: ghc-mod ghc-mod-el Architecture: source all amd64 Version: 5.2.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group pkg-haskell-maintain...@lists.alioth.debian.org Changed-By: Daniel Gröber d...@darkboxed.org Description: ghc-mod- Happy Haskell programming ghc-mod-el - Happy Haskell programming with Emacs Closes: 768226 Changes: ghc-mod (5.2.1.1-2) unstable; urgency=medium . * Fix upgrading ghc-mod from wheezy by declaring a Replaces+Breaks relation for ghc-mod-el. (Closes: #768226) Checksums-Sha1: 3e74e8ad85a2bf1a676120f03cc11efe48c1b782 2498 ghc-mod_5.2.1.1-2.dsc e81be007bc62b5f4bb0da668ef00374406aecb08 4248 ghc-mod_5.2.1.1-2.debian.tar.xz abc3f32634faaedc182ec03521d21ec39907faf6 25580 ghc-mod-el_5.2.1.1-2_all.deb 072f7458852fdabc57ded1bff0670a161863d7a5 11263490 ghc-mod_5.2.1.1-2_amd64.deb Checksums-Sha256: 933f2f7532472c62e2aea2d3c99a7477a44fc4370b0f6a90af8f11f9bc14bdda 2498 ghc-mod_5.2.1.1-2.dsc b583e7b4f13a2b51ff39769d0116b0c1ba00f03b463e7af8e2c8ef85ecae2b1f 4248 ghc-mod_5.2.1.1-2.debian.tar.xz bf8837806a58237ef40195508ace5303215789f39cac8f075b5e838ae73dfabe 25580 ghc-mod-el_5.2.1.1-2_all.deb 3b92c895e9866d484077bb1643a65e58b21d9819241bdfca90676573cb987e56 11263490 ghc-mod_5.2.1.1-2_amd64.deb Files: add2f4db655d67b147be70b81aa6890b 2498 haskell extra ghc-mod_5.2.1.1-2.dsc bef589d3c21a5036944e19ec0e450c17 4248 haskell extra ghc-mod_5.2.1.1-2.debian.tar.xz 56b03c170e597a1549c7758d52bf27cc 25580 haskell extra ghc-mod-el_5.2.1.1-2_all.deb fd8b85b60924ed513c32031cab6067a1 11263490 haskell extra ghc-mod_5.2.1.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUW7nTAAoJED2QirPw+/UfjooP/ioQivvNXRZSHNmia+CwJqM9 WmTW3lxkSK4NmJ4onicYTb3TYLYibS4KhcfViKpFUeqJxjd7pXh3aroSlqRn1mok v1Z8nv4PMrAUlWkX2nYWau5abKpoppgBUaCjQHZyv1EpGBsQ7v7iwPWzooTyTfiO K22GgmrsOTCQSC+A0m69NqZH+P+yw5f2VoH6I9qW0aN59kZEnjc5hbAPsTXkQb8E 6m/F60kU0XXZ0WfvzpIqyNZPApSOcXb2amT59+hgPINzXTEAAL2X4H7Ub/LiUQdi FPqECjSnSH+SXqmscRXfOJK0YifpmjY/Lx70OlIe3BXraQno7iDRL+VOrdu1L9+I biHPSW9QGODm3Dj82N9icJzIdf8PCnoIagJIYn9N+u0fPRREH9mhK2BvBtS31XQB
Bug#768351: must declare dependencies the Drupal way
Package: drupal7-mod-jscommunicator Version: 1.0.1-2 Severity: serious The .info file needs to include all dependencies for Drupal to ensure they are enabled correctly at runtime. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768351: marked as done (must declare dependencies the Drupal way)
Your message dated Thu, 06 Nov 2014 18:34:34 + with message-id e1xmrtc-y9...@franck.debian.org and subject line Bug#768351: fixed in drupal7-mod-jscommunicator 1.1-1 has caused the Debian Bug report #768351, regarding must declare dependencies the Drupal way 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.) -- 768351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: drupal7-mod-jscommunicator Version: 1.0.1-2 Severity: serious The .info file needs to include all dependencies for Drupal to ensure they are enabled correctly at runtime. ---End Message--- ---BeginMessage--- Source: drupal7-mod-jscommunicator Source-Version: 1.1-1 We believe that the bug you reported is fixed in the latest version of drupal7-mod-jscommunicator, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Pocock dan...@pocock.pro (supplier of updated drupal7-mod-jscommunicator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Nov 2014 19:22:31 +0100 Source: drupal7-mod-jscommunicator Binary: drupal7-mod-jscommunicator Architecture: source all Version: 1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Daniel Pocock dan...@pocock.pro Description: drupal7-mod-jscommunicator - Browser-based messaging, phone and video chat application Closes: 768351 Changes: drupal7-mod-jscommunicator (1.1-1) unstable; urgency=medium . * New upstream release. * Declare runtime dependencies for Drupal. (Closes: #768351) Checksums-Sha1: 814b2952e63576af15eeb4df35e36db617a7e285 2129 drupal7-mod-jscommunicator_1.1-1.dsc 85bf818ed1afb11ca6cfd2995069a24ddb07dec9 1593 drupal7-mod-jscommunicator_1.1.orig.tar.gz ac5bf7ae982cb1684f200c022739bc4be5c52dca 1796 drupal7-mod-jscommunicator_1.1-1.debian.tar.xz 55d874a47b81f970d87afd4d0f782f4bf74d4cd7 3176 drupal7-mod-jscommunicator_1.1-1_all.deb Checksums-Sha256: 2a37b2e641bfa4952ea81226ff5fbfbf84adbcd3330c7e61e1630aa998c082c3 2129 drupal7-mod-jscommunicator_1.1-1.dsc 93156c73e0ac74e3e3d6197b98955b9482fd0b0a9dc147a1ed6a1006bbffd2d1 1593 drupal7-mod-jscommunicator_1.1.orig.tar.gz b22ce1ba6736bd136bb94814d2eebfa85bf66e1b395067a3d852c1e577b5faf6 1796 drupal7-mod-jscommunicator_1.1-1.debian.tar.xz cc2f96ea78edbe5101bf410032d1f4012f7c4cef5bf0ec95088b1028e5b040d8 3176 drupal7-mod-jscommunicator_1.1-1_all.deb Files: 2081b7f7d4adac80df6b9cbc9d06d7cd 2129 web optional drupal7-mod-jscommunicator_1.1-1.dsc 3cd3e77d3d0d2bcede9e0a382601b307 1593 web optional drupal7-mod-jscommunicator_1.1.orig.tar.gz 6b8c8cc0f5adf235e86e9884f4e3fc42 1796 web optional drupal7-mod-jscommunicator_1.1-1.debian.tar.xz 9bcf9dcfa33cf26a024c417875fe1e00 3176 web optional drupal7-mod-jscommunicator_1.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJUW70iAAoJEGxlgOd711bEMgQP+gJzmYkXibkC0PMJEpwIBUoJ BrBNAnM2ZwQyOACr+ViTKzI5pq/pV0k6uHXbjmlrqZPI9HUSQz39yVLU3ujXFO75 lev2yJDUdWml7vXK1iv+okbeR94q1mynNYLV4rZQOMUv+4hcYhuf0rruKNc9m+Eb KJNw01IbNol+70rGZuLFoKscVFtpeBpgR5pxfGdVrEiIBZiHqmk9HLmDvIrLC/o/ PqTyyPrFDAaN1jI8NoeULiEcX73FSUE8l/QbPMozt0j511wTfSArUGAKqbbJxIPX R+nxci/nuRXoZt1pGAUYpxxU2ZAg75Gi4FaEOcTnbaFv38r7Y1g3qyyKsrHaheVs cseROWrYl7sLbz9emn8lw+IQ9GgFjdVQoK0dWW+xGZzSzY5R+ZN5DdrLN/607D5t fvZUrPzRdefvuSInArhTt0cboQzLi0VF4z0Q0ve/cm0oDtNeb67w14iQ/d1zCoaw lXtcc2FkBsl0R8gEOcE5XFEKjootMHTkUV2E5RFGrHMoDlrQJyLv1jPPojpBwGZm 6E2MGTtoCff70UKNH1uiOHgrtjZ86nZyFsQSb/6CjyRayPERHQDQPKRlPqy/bdYL lHrBNOIEdhCRURZyVe8mIhzFpqbLez0OAZdMVmQhB1jPLh5YjSEd8tSm0XEcgQ8p 0GDaSneTwLzgzODbWzso =R0zM -END PGP SIGNATUREEnd Message---
Bug#768354: must sync with JSCommunicator itself
Package: drupal7-mod-drucall Version: 2.0.1-1 Severity: serious A newer JSCommunicator version was uploaded but the DruCall module could not be uploaded earlier while waiting for the FTP masters to approve new Drupal dependency wrapper packages drupal7-mod-jqueryi18nproperties and drupal7-mod-fontawesome They were approved just before the freeze and now everything needs to be uploaded and unblocked in sync to work together. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742140: libpam-oath: PAM module does not check whether strdup allocations succeeded
* Andreas Barth: we have the following debian bug report about an security isuse in libpam-oath (source oath-toolkit, upstream web page http://www.nongnu.org/oath-toolkit/ ). What is the appropriate process to get an CVE number on it? This issue is already public, as it is documented in the debian bug tracking system. Does this actually have any application impact? Not checking for error on malloc failure is extremely common, and many applications use wrappers such as xmalloc which explicitly terminate the process on malloc failure. -- 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#768216: libgeographic-dev: fails to upgrade from 'wheezy' - trying to overwrite /usr/include/GeographicLib/TransverseMercatorExact.hpp
Processing control commands: tags -1 pending Bug #768216 [libgeographic-dev] libgeographic-dev: fails to upgrade from 'wheezy' - trying to overwrite /usr/include/GeographicLib/TransverseMercatorExact.hpp Added tag(s) pending. -- 768216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768216 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#768216: libgeographic-dev: fails to upgrade from 'wheezy' - trying to overwrite /usr/include/GeographicLib/TransverseMercatorExact.hpp
Control: tags -1 pending On 11/06/2014 02:15 AM, Andreas Beckmann wrote: during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libgeographic13. Unpacking libgeographic13 (from .../libgeographic13_1.37-2_amd64.deb) ... Selecting previously unselected package libgeographic-dev. Unpacking libgeographic-dev (from .../libgeographic-dev_1.37-2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libgeographic-dev_1.37-2_amd64.deb (--unpack): trying to overwrite '/usr/include/GeographicLib/TransverseMercatorExact.hpp', which is also in package libgeographiclib-dev 1.21-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libgeographic-dev_1.37-2_amd64.deb Hi Andreas, Thanks for reporting this. I have uploaded a fixed package to d.mentors.net, and I am awaiting sponsorship. Regards, Ross -- 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#768216: libgeographic-dev: fails to upgrade from 'wheezy' - trying to overwrite /usr/include/GeographicLib/TransverseMercatorExact.hpp
Processing control commands: tags -1 pending Bug #768216 [libgeographic-dev] libgeographic-dev: fails to upgrade from 'wheezy' - trying to overwrite /usr/include/GeographicLib/TransverseMercatorExact.hpp Ignoring request to alter tags of bug #768216 to the same tags previously set -- 768216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768216 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 767225
Processing commands for cont...@bugs.debian.org: tags 767225 + pending Bug #767225 [libc6] regex: don't deref NULL upon heap allocation failure Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 767225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767225 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#768354: marked as done (must sync with JSCommunicator itself)
Your message dated Thu, 06 Nov 2014 19:19:01 + with message-id e1xmsad-0006ji...@franck.debian.org and subject line Bug#768354: fixed in drupal7-mod-drucall 2.1-1 has caused the Debian Bug report #768354, regarding must sync with JSCommunicator itself 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.) -- 768354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: drupal7-mod-drucall Version: 2.0.1-1 Severity: serious A newer JSCommunicator version was uploaded but the DruCall module could not be uploaded earlier while waiting for the FTP masters to approve new Drupal dependency wrapper packages drupal7-mod-jqueryi18nproperties and drupal7-mod-fontawesome They were approved just before the freeze and now everything needs to be uploaded and unblocked in sync to work together. ---End Message--- ---BeginMessage--- Source: drupal7-mod-drucall Source-Version: 2.1-1 We believe that the bug you reported is fixed in the latest version of drupal7-mod-drucall, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Pocock dan...@pocock.pro (supplier of updated drupal7-mod-drucall package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Nov 2014 19:33:06 +0100 Source: drupal7-mod-drucall Binary: drupal7-mod-drucall Architecture: source all Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Daniel Pocock dan...@pocock.pro Description: drupal7-mod-drucall - WebRTC SIP module for the Drupal CMS Closes: 768354 Changes: drupal7-mod-drucall (2.1-1) unstable; urgency=medium . * New upstream release. * Sync content with JSCommunicator. (Closes: #768354) Checksums-Sha1: c3ba868396941005b7a725549f2fefa6895acef8 2029 drupal7-mod-drucall_2.1-1.dsc e4286bfd3af0ae105c7eb3809368dd09e0a0a605 1035677 drupal7-mod-drucall_2.1.orig.tar.gz 15c1dfa809e4cbe6917adf269e26d85315e29347 1864 drupal7-mod-drucall_2.1-1.debian.tar.xz ccb7cce01e3281108ad62626e37442850d627081 896234 drupal7-mod-drucall_2.1-1_all.deb Checksums-Sha256: 22b6819f250c0165bb378d649b6287bfa4fd6c5b1f32d405d7a84c664aad68d2 2029 drupal7-mod-drucall_2.1-1.dsc 6710d5e6dec6c2a75546175e088bd84adebce07078dbac0b64fe4e701f562ea8 1035677 drupal7-mod-drucall_2.1.orig.tar.gz 03552ed54b94ff0c192f2c21460d2e1296c3c7e56aa34c6845bc4fe684171bf1 1864 drupal7-mod-drucall_2.1-1.debian.tar.xz 3b140580add90ca6ebd85ad9f7aa3429347e1104103a9340549de756cd132074 896234 drupal7-mod-drucall_2.1-1_all.deb Files: d4806ceded68e9a794eb03c9ac8c3e66 2029 web optional drupal7-mod-drucall_2.1-1.dsc 2096514cdaa6ae3ef38e0df49b25e110 1035677 web optional drupal7-mod-drucall_2.1.orig.tar.gz f4d6bd0158cb4264dacc8dab02ee839a 1864 web optional drupal7-mod-drucall_2.1-1.debian.tar.xz a7d855ca0b98a252f1b7790beb39 896234 web optional drupal7-mod-drucall_2.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJUW8cRAAoJEGxlgOd711bEM8kP+wVsFlHGF+Dfd1sDpVvG6bTV amAAorkdNPX7gXDHuZ5SI55LzUnvHHM9xRch0W/ee3bfwCa+IpyrJLbuKNi9Gbwm C5jlVIGMSTeRgyUSfZoljkANIKCaBolkk2BYSI8NTbjUGhARoI1bSxckSy78q1Oz pdhn5PGoR+z+1mHyvUXLvDaa+XYDr0P3BCrflvgUJ4VWftD/XHfi6tcqqanL4nZQ ddmz6JAWdlL/OCzApTy82xSLeXPY1t3afT794NhfSmUlzvv+4rNXcFUs+OZLOAci iq8HD0zPVrUJWcxojCBjlNGCh063dsJS6zSwpZ6QZPOguuWxmt+KOpGrmft4aoRC mNIT3Ols0ce9sfBwPI+KHsTtmr0c3ql5Rk+u1K0maqeBNUknbNlwtw7oxkcDG0Ll XPFQXBdocorvjG/yZz4VqbMGsu7IKuWkHssCEqRBKvMp7GaNH0T0vEb4zI4UgqqC 4aSGDUt0G2vSd72bpTfxB8YTglGYhX7xJFBMV57HR02Likn5+CN9h1zb09Dz5enT oyh4gYmlt3RxUnlyylCXpZW0XTRxmaY0RMNstfa1a5NYYVGGTpGT7ql5mxga8NKK 6X/Cf8vz9FJIvUSsQc3l8ifJpKaUSZ1VoyFZfcrG72aBe3L4PuFHWYBgslWjbsy7 DuTYujjP/fsjS8WB33qc =M6JP -END PGP SIGNATUREEnd Message---
Bug#768363: adjust font-awesome dependency version
Package: libjs-jscommunicator Version: 2.0.0-1 Severity: serious The font-awesome package has a ~ symbol in the dfsg version. Therefore, depending on the constraint (= 4.2.0) doesn't match the version 4.2.0~dfsg-1 Relax the dependency to depend on (= 4.1.0~dfsg) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768363: adjust font-awesome dependency version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/11/14 21:22, Jonas Smedegaard wrote: Quoting Daniel Pocock (2014-11-06 20:43:48) The font-awesome package has a ~ symbol in the dfsg version. Therefore, depending on the constraint (= 4.2.0) doesn't match the version 4.2.0~dfsg-1 Relax the dependency to depend on (= 4.1.0~dfsg) Dependency should be 4.2.0~dfsg (i.e. 2 instead of 1). Perhaps simply a typo... Not quite, 4.1.0~dfsg appears to be sufficient for this and it is in backports. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJUW9kMAAoJEGxlgOd711bErF4QAIVYmGxLX9LH5mHnzgG5nnM+ 7hmdPrqi0sXh9O8oD/L6sLBl/1j+wk/isqnqjw2RDFXPLEPvoW5td3+UaxKoal9r AkVLImwhRdUvmGKrmIBdCnS7QMt189N5iiQcrBpDRlTQ12MYCDPidQ9oZwwuYxbF jc16qBooJewMMfbRIw1/nbcJKLNmB8AK3hAjV7czMhhHd4uEQawXEthz7ImHMuHz IXUn88/SSDjX0lHjhTkCLVCkjXHZMMYVzx444QOY9KUsjvrQsUYyROCPEZXQ8/xv Cjbijl18p9F3oqCKw14MuaBdt5TxCbOQUC1MHwYx5LORinEtCYGmhrogZERzFwMW 2+AvVDJWnHGo7DJ+HPX4dtM5e5bPXmzQMAOQI+WyyjtZpEMVdEvRZgt0fTUEv//N FU11oDRqST+yNqHhUDaATdmDinIVY/HLIQw8KbSNUCiN2NZYcVAd0UpRIqUnpzKW 2VgMfPh0EhOV09oq6ZH/ozdyUnmbolPn/hFJ2I2Yny8ydAtw35QrrGXxyp5kzCFl Opt4dd9zKCDmySJnsXiCjSvqbEko5wYKtlbMkV/7KD1yqIqF5x2r3IF+GhEcQAhz tFkm/TcaTM2g4gVQwipMPuKh2WtbCiScsJRD/z1AVjC16zjSpA9XoGyKndKfwv3X yeFmmZiyFifRLGpE1DDw =TuT8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768363: adjust font-awesome dependency version
Quoting Daniel Pocock (2014-11-06 20:43:48) The font-awesome package has a ~ symbol in the dfsg version. Therefore, depending on the constraint (= 4.2.0) doesn't match the version 4.2.0~dfsg-1 Relax the dependency to depend on (= 4.1.0~dfsg) Dependency should be 4.2.0~dfsg (i.e. 2 instead of 1). Perhaps simply a typo... Regards, - 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#766462: with plymouth installed, I don't get any gettys on my VCs
On Tue, 28 Oct 2014, Laurent Bigonville wrote: Could you please add a bit more information here? Which architectures are you talking about? is your system completely up-to-date? Which init system are you using? amd64, completely up to date jessie, /sbin/init is provided by systemd-sysv. Could you also please try to add plymouth.debug to the kernel cmdline, it should create a plymouth-debug.log in /var/log. Please attach the file here. Did that, didn't get a logfile. Let me know how I can help. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.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: gstreamer0.10: diff for NMU version 0.10.36-1.5
Processing control commands: tags 761916 + patch Bug #761916 [src:gstreamer0.10] gstreamer0.10: gir packages missing Depends against libraries Added tag(s) patch. -- 761916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761916 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#761916: gstreamer0.10: diff for NMU version 0.10.36-1.5
Control: tags 761916 + patch Dear maintainer, I've prepared an NMU for gstreamer0.10 (versioned as 0.10.36-1.5). The diff is attached to this message. Regards. diff -Nru gstreamer0.10-0.10.36/debian/changelog gstreamer0.10-0.10.36/debian/changelog --- gstreamer0.10-0.10.36/debian/changelog 2014-08-24 00:41:19.0 +0200 +++ gstreamer0.10-0.10.36/debian/changelog 2014-11-06 20:46:58.0 +0100 @@ -1,3 +1,11 @@ +gstreamer0.10 (0.10.36-1.5) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: Remove outdated mangling of debian/shlibs.local, this is +breaking dependencies generation for gir packages. (Closes: #761916) + + -- Laurent Bigonville bi...@debian.org Thu, 06 Nov 2014 20:46:56 +0100 + gstreamer0.10 (0.10.36-1.4) unstable; urgency=low * Non-maintainer upload with maintainers permission. diff -Nru gstreamer0.10-0.10.36/debian/rules gstreamer0.10-0.10.36/debian/rules --- gstreamer0.10-0.10.36/debian/rules 2013-01-26 12:17:15.0 +0100 +++ gstreamer0.10-0.10.36/debian/rules 2014-11-06 20:45:23.0 +0100 @@ -214,25 +214,6 @@ DEB_INSTALL_DOCS_ALL += debian/README.Debian NEWS DEB_SHLIBDEPS_INCLUDE += debian/$(gst_lib)/usr/lib/$(DEB_HOST_MULTIARCH) -# override shlibs for libraries from this source before computing dependencies -# of packages generated from this source; we already have inter-dependencies -# expressed manually in the control file, we do not need the shlibs to add -# duplicates -# (this rule runs just before the dh_shlibdeps) -common-binary-fixup-arch:: - mkdir -p $(CURDIR)/fake-home - HOME=$(CURDIR)/fake-home \ - dh_girepository -pgir1.2-gstreamer-$(gst_abi) - rm -rf $(CURDIR)/fake-home - -rm -f debian/shlibs.local - cat debian/*/DEBIAN/shlibs | \ - sed -n -r -e 's/(([^ ]+: )?([^ ]+) ([^ ]+)) .*/\1/p' \ -debian/shlibs.local - -# (this rules runs just after the dh_shlibdeps) -common-binary-predeb-arch:: - -rm -f debian/shlibs.local - install/$(gst_lib_dev):: gcc -o debian/tmp/usr/bin/gst-codec-info-0.10 debian/gst-codec-info.c $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) `pkg-config --libs --cflags glib-2.0 gthread-2.0 gmodule-no-export-2.0 gobject-2.0 libxml-2.0` debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libgstreamer-0.10.so -Idebian/tmp/usr/include/gstreamer-0.10 perldoc -o man debian/dh_gstscancodecs debian/tmp/usr/share/man/man1/dh_gstscancodecs.1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766462: with plymouth installed, I don't get any gettys on my VCs
On Thu, 06 Nov 2014, Peter Palfrader wrote: Did that, didn't get a logfile. } weasel@defiant:/var/log$ cat /proc/cmdline } BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/vg0-root ro splash quiet plymouth.debug } weasel@defiant:/var/log$ ls -l pl* } zsh: no matches found: pl* However, removing splash from the kernel command line (it was set in /etc/default/grub from my wheezy), makes gettys work on the VCs again. Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768363: adjust font-awesome dependency version
Quoting Daniel Pocock (2014-11-06 21:24:45) On 06/11/14 21:22, Jonas Smedegaard wrote: Quoting Daniel Pocock (2014-11-06 20:43:48) The font-awesome package has a ~ symbol in the dfsg version. Therefore, depending on the constraint (= 4.2.0) doesn't match the version 4.2.0~dfsg-1 Relax the dependency to depend on (= 4.1.0~dfsg) Dependency should be 4.2.0~dfsg (i.e. 2 instead of 1). Perhaps simply a typo... Not quite, 4.1.0~dfsg appears to be sufficient for this and it is in backports. Fair enough - I just reacted based on your own words above doesn't match the version 4.2.0~dfsg-1, which does not explain why it is ok to relax even further. In case you want release team to process this for Jessie, it might make sense to elaborate a bit why relaxing even further is ok - as there is nothing particular mentioned in changelog of fonts-font-awesome¹. - Jonas ¹ not font-awesome - again I guess it's just a typo here in the bugreport but mentioning to be on the safe side. -- * 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
Processed: [libjpeg62-turbo] [DOS] Stack smashing
Processing control commands: affects -1 imagemagick Bug #768369 [libjpeg62-turbo] [libjpeg62-turbo] [DOS] Stack smashing Added indication that 768369 affects imagemagick -- 768369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768369 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
