Bug#840417: marked as done (pdf2htmlex: FTBFS with new release of fontforge)
Your message dated Sat, 15 Oct 2016 07:50:25 + with message-id and subject line Bug#840417: fixed in fontforge 1:20161005~dfsg-2 has caused the Debian Bug report #840417, regarding pdf2htmlex: FTBFS with new release of fontforge 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.) -- 840417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdf2htmlex Severity: serious User: pkg-fonts-de...@lists.alioth.debian.org Usertags: fontforge-transition Dear Maintainer, pdf2htmlex FTBFS with new version of fontforge (currently in experimental). Below is the snippet of log showing the error. /encoding.cc [ 47%] Building C object CMakeFiles/pdf2htmlEX.dir/src/util/ffw.c.o /usr/bin/cc -I/<>/pdf2htmlex-0.14.6+ds/src -I/usr/include/poppler -I/usr/include/fontforge -g -O2 -fdebug-prefix-map=/<>/pdf2htmlex-0.14.6+ds=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -o CMakeFiles/pdf2htmlEX.dir/src/util/ffw.c.o -c /<>/pdf2htmlex-0.14.6+ds/src/util/ffw.c In file included from /usr/include/fontforge/baseviews.h:30:0, from /<>/pdf2htmlex-0.14.6+ds/src/util/ffw.c:17: /usr/include/fontforge/ffglib.h:27:18: fatal error: glib.h: No such file or directory #include ^ compilation terminated. CMakeFiles/pdf2htmlEX.dir/build.make:425: recipe for target 'CMakeFiles/pdf2htmlEX.dir/src/util/ffw.c.o' failed make[4]: *** [CMakeFiles/pdf2htmlEX.dir/src/util/ffw.c.o] Error 1 make[4]: Leaving directory '/<>/pdf2htmlex-0.14.6+ds/obj-x86_64-linux-gnu' CMakeFiles/Makefile2:102: recipe for target 'CMakeFiles/pdf2htmlEX.dir/all' failed make[3]: *** [CMakeFiles/pdf2htmlEX.dir/all] Error 2 make[3]: Leaving directory '/<>/pdf2htmlex-0.14.6+ds/obj-x86_64-linux-gnu' Makefile:141: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/<>/pdf2htmlex-0.14.6+ds/obj-x86_64-linux-gnu' dh_auto_build: make -j1 returned exit code 2 debian/rules:21: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>/pdf2htmlex-0.14.6+ds' debian/rules:13: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 It looks like missing dependency on glib development headers. The full log is available at ¹. We intend to upload the fontforge to unstable in about a week's time. If you need any more information please feel free to contact us (Fonts team). ¹ https://angband.pl/tmp/ff11/failed/pdf2htmlex_amd64-2016-10-10T23:47:05Z.build -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: fontforge Source-Version: 1:20161005~dfsg-2 We believe that the bug you reported is fixed in the latest version of fontforge, 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 840...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vasudev Kamath (supplier of updated fontforge 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: Sat, 15 Oct 2016 12:05:27 +0530 Source: fontforge Binary: fontforge fontforge-nox fontforge-common libfontforge-dev libfontforge2 libgdraw5 python-fontforge fontforge-dbg Architecture: source all i386 Version: 1:20161005~dfsg-2 Distribution: experimental Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Vasudev Kamath Description: fontforge - font editor fontforge-common - font editor (common files) fontforge-dbg - debugging symbols for fontforge fontforge-nox - font editor - non-X version libfontforge-dev - font editor - runtime library (development files) libfontforge2 - font editor - runtime library libgdraw5
Bug#838833: asterisk: AST-2016-006
The issue is tracked by the security team as https://security-tracker.debian.org/tracker/CVE-2016-7550 >. I guess the easiest fix is to upgrade the unstable version from upstream, as the older versions of Debian are not affected and a quick search did not point me to a patch. -- Happy hacking Petter Reinholdtsen
Bug#840815: acl2: FTBFS on some architectures: HARD ACL2 ERROR in ASSERT$: Assertion failed:
Source: acl2 Version: 7.2dfsg-2 Severity: serious Hi, Your package failed to build on mips64el, as well as in some other (non-release) architectures. From the mips64el log: start address -T 0xc0c0f0 ;; Finished loading #p"boot-strap-pass-2.o" ;; Loading "defpkgs.lisp" [GC for 95 SYMBOL pages..(T=9).GC finished] [GC for 334 CONS pages..(T=10).GC finished] [GC for 344 CONS pages..(T=10).GC finished] [GC for 344 CONS pages..(T=10).GC finished] [GC for 344 CONS pages..(T=10).GC finished] ;; Finished loading "defpkgs.lisp" [GC for 74 SFUN pages..(T=10).GC finished] HARD ACL2 ERROR in ASSERT$: Assertion failed: (ASSERT$ (AND (TRUE-LISTP DIR) (EQ (CAR DIR) :ROOT)) (LET* ((MSWINDOWS-DRIVE (MSWINDOWS-DRIVE # STATE)) (TMP (IF MSWINDOWS-DRIVE # "/"))) (DOLIST (X DIR) (WHEN (STRINGP X) (SETQ TMP #))) (WHEN (STRINGP NAME) (SETQ TMP (CONCATENATE # TMP NAME))) (WHEN (STRINGP TYPE) (SETQ TMP (CONCATENATE # TMP "." TYPE))) (LET ((NAMESTRING-TMP #) (NAMESTRING-TRUENAME #)) (COND (# TMP) (# TMP) (T # #) (See :DOC set-iprint to be able to see elided values in this message.) ACL2 Error in ACL2-INTERFACE: Evaluation aborted. To debug see :DOC print-gv, see :DOC trace, and see :DOC wet. Error: Fast links are on: do (si::use-fast-links nil) for debugging Signalled by INITIALIZE-ACL2. Raw Lisp Break. SIMPLE-ERROR: ACL2 Halted Broken at APPLY. Type :H for Help. 1 Return to top level. ACL2>>make[2]: Entering directory '/«PKGBUILDDIR»' ACL2_WD is /«PKGBUILDDIR» Initialization FAILED: acl2-status.txt should contain :INITIALIZED. GNUmakefile:340: recipe for target 'check_init_ok' failed make[2]: *** [check_init_ok] Error 1 Full logs at https://buildd.debian.org/status/package.php?p=acl2 Emilio
Processed: Pending fixes for bugs in the libcompress-raw-lzma-perl package
Processing commands for cont...@bugs.debian.org: > tag 839987 + pending Bug #839987 [libcompress-raw-lzma-perl] libcompress-raw-lzma-perl: Version Mismatch due to new src:xz-utils Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 839987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#839987: Pending fixes for bugs in the libcompress-raw-lzma-perl package
tag 839987 + pending thanks Some bugs in the libcompress-raw-lzma-perl package are closed in revision 898ccbda13fe5e910ae1a95f979e9afc92ad9784 in branch 'master' by gregor herrmann The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libcompress-raw-lzma-perl.git/commit/?id=898ccbd Commit message: Add patch to turn off check for liblzma version at runtime. Closes: #839987
Bug#840818: nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver
Package: nvidia-driver Severity: serious Tags: upstream Justification: Policy 1.1 After installing nvidia-driver on a fresh installed debian (or on it's distributions too), the driver could not be loaded causes to boot in low-graphics mode. The main problem is here, that the package overwrites the xserver-xorg-nouveau driver and it's hard to be restored, even purging nvidia-driver and reinstalling/reconfiguring xserver-xorg-nouveau. For me, a complete new Debian installation was the solution. The package was working earlyer on Linux Mint Sarah, but now breaks both system. # Hardware configuration: Dell Precision M4600 with dual-video card: * 1x Nvidia Quadro 2000M * 1x Intel HD 1000 <-- Not identified by even lspci -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Processed: Re: bamfdaemon: unowned directory after purge: /usr/share/applications/
Processing control commands: > severity -1 serious Bug #683757 {Done: Mike Gabriel } [bamfdaemon] bamfdaemon: unowned directory after purge: /usr/share/applications/ Severity set to 'serious' from 'important' > found -1 0.5.3-1~exp1 Bug #683757 {Done: Mike Gabriel } [bamfdaemon] bamfdaemon: unowned directory after purge: /usr/share/applications/ Marked as found in versions bamf/0.5.3-1~exp1; no longer marked as fixed in versions bamf/0.5.3-1~exp1 and reopened. > found -1 0.5.3-1~exp2 Bug #683757 [bamfdaemon] bamfdaemon: unowned directory after purge: /usr/share/applications/ Marked as found in versions bamf/0.5.3-1~exp2. -- 683757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840134: marked as done (asciinema: d/copyright has wrong license)
Your message dated Sat, 15 Oct 2016 10:24:22 + with message-id and subject line Bug#840134: fixed in asciinema 1.3.0-2 has caused the Debian Bug report #840134, regarding asciinema: d/copyright has wrong license 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.) -- 840134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ascinema Severity: serious Justification: Policy 4.5 Hallo Gustavo, while reviewing your package I figured out that d/copyright claims the wrong license. It claims: Files: * Copyright: (c) 2013-2016, Marcin Kulik License: MIT while the upstream's README.md says GPL-3 or later. -- tobi -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: asciinema Source-Version: 1.3.0-2 We believe that the bug you reported is fixed in the latest version of asciinema, 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 840...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gustavo panizzo (supplier of updated asciinema package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 11 Oct 2016 09:28:07 +0800 Source: asciinema Binary: asciinema Architecture: source Version: 1.3.0-2 Distribution: unstable Urgency: medium Maintainer: gustavo panizzo Changed-By: gustavo panizzo Description: asciinema - Record and share your terminal sessions, the right way Closes: 840134 Changes: asciinema (1.3.0-2) unstable; urgency=medium . * Correct the license from MIT to GPL-3+ (Closes: #840134). * Relicense the debian directory to GPL-3+ * Use upstream manpage * Run the test suite, as it does not get run by default * Store the generated tarball using pristine-tar Checksums-Sha1: 7c3190516f1837005f416049902951d56eac4d4d 1866 asciinema_1.3.0-2.dsc a307918214befcc80e772b56efecae04565c3064 3100 asciinema_1.3.0-2.debian.tar.xz Checksums-Sha256: 08998438bfd45bee4fb64e20d2f33e27d213eb7ea7a467c44331aaf0c0b9c629 1866 asciinema_1.3.0-2.dsc b443bf1654b19bf7545a9fc9b7c96c48fdb5c10b27703caf80d66276e4b89987 3100 asciinema_1.3.0-2.debian.tar.xz Files: 949e6b2a678f0dd6fa865d9e104ce28d 1866 utils optional asciinema_1.3.0-2.dsc 1bf2a24cf3754cc204495ca8359a0631 3100 utils optional asciinema_1.3.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYAgBiAAoJEJFk+h0XvV02DV0QALdKGtAr0bnOMuYfwC+B0xJj hcpSmefJJuqVi+2lLqq8Fw+DGGMeGJ0++50VrcOiotkChR3GX8ORgANCHXAXH1nx pmbJNL+b00ZV5PFI4ycM+Txhniv2x+8G4DTp6G6KSM9VRhmRj84qK/iC/cOI3DOl ltsEK7mWfQIS6d9b3ruZEVJRiPFB1aslrOQQq8rc9aodJZ0YVy2jv6Hqd+6hOmvb TMxWpEEzvQ89TW4NDKGcfw8DD/ZZkysZJ6zVgfds5bC5xjuVZ+LPpZivVwtlG8gk Xbc7D45bYaPc79qKkmhi75/S305xJSn5e7GGBlmm3NDNPdihe8o8tCT6hyHDQSzF jJGYlAFNBEFdxjhqlV2ioe/b+Fz5h4eZtbYpEeCldIDQtE293SeFakBosys+WZWb lVj8ynq/nFTxrdIKGlfCZrr9eBRYua/mp4LdynJS6fWgQRwGft/j+GSs72UJibEk Lbr8csqK/Cj17CPpGF0vmLsEdxeXy+sgqTdzxCXEQrGozPc4TgGX9kFFkw7a2wKh i1G20OhDKXFrGC+P98qFuwFn/4B6iq+chhZZk9RxGxm1lqcILI7x5Hp6gXVb4u7e Q8XbJk4kkJif6CLh9WvhWL7h0UQF2/NViRL89M/oSzKwfGApwsz6U4XvKBSC3uD3 T1ffPHqjOyafwAGvwrA8 =NK74 -END PGP SIGNATURE End Message ---
Bug#839987: marked as done (libcompress-raw-lzma-perl: Version Mismatch due to new src:xz-utils)
Your message dated Sat, 15 Oct 2016 10:39:41 + with message-id and subject line Bug#839987: fixed in libcompress-raw-lzma-perl 2.069-2 has caused the Debian Bug report #839987, regarding libcompress-raw-lzma-perl: Version Mismatch due to new src:xz-utils 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.) -- 839987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcompress-raw-lzma-perl Version: 2.069-1 Severity: grave User: debian-p...@lists.debian.org Usertags: autopkgtest As noticed by the autopkgtest checks at ci.debian.net, this library can't be used on current sid/amd64 anymore. # perl -e 'use Compress::Raw::Lzma' Subroutine Compress::Raw::Lzma::constant redefined at /usr/lib/x86_64-linux-gnu/perl5/5.24/Compress/Raw/Lzma.pm line 165. Subroutine Compress::Raw::Lzma::lzma_version_number redefined at /usr/lib/x86_64-linux-gnu/perl5/5.24/Compress/Raw/Lzma.pm line 165. [...] Subroutine Compress::Raw::Lzma::Options::DESTROY redefined at /usr/lib/x86_64-linux-gnu/perl5/5.24/Compress/Raw/Lzma.pm line 165. Version Mismatch - Built with version 5001, library used is version 50020022 Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. This is clearly caused by the new liblzma5 (src:xz-utils) in sid. We seem to need either tighter (preferably binNMU-safe) versioned dependencies or disabling the version check. Not sure what triggered all the warnings but it's presumably related. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: libcompress-raw-lzma-perl Source-Version: 2.069-2 We believe that the bug you reported is fixed in the latest version of libcompress-raw-lzma-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 839...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libcompress-raw-lzma-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: Sat, 15 Oct 2016 12:00:49 +0200 Source: libcompress-raw-lzma-perl Binary: libcompress-raw-lzma-perl Architecture: source Version: 2.069-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 839987 Description: libcompress-raw-lzma-perl - low-level interface to lzma compression library Changes: libcompress-raw-lzma-perl (2.069-2) unstable; urgency=medium . [ Salvatore Bonaccorso ] * debian/control: Use HTTPS transport protocol for Vcs-Git URI . [ gregor herrmann ] * debian/copyright: change Copyright-Format 1.0 URL to HTTPS. * Add patch to turn off check for liblzma version at runtime. (Closes: #839987) * Update years of packaging copyright. * Set bindnow linker flag in debian/rules. * Declare compliance with Debian Policy 3.9.8. Checksums-Sha1: 717f6503f7b16f34d4a7385d6f1faf4e683cb828 2306 libcompress-raw-lzma-perl_2.069-2.dsc f43962accadd5aaa5aece9eb77fe5069e3c7ab3f 2700 libcompress-raw-lzma-perl_2.069-2.debian.tar.xz Checksums-Sha256: a52e5752bce5e8de3b5dd5b4a59a2678ae8d5c5f816333481e6c2a0e8e495b9d 2306 libcompress-raw-lzma-perl_2.069-2.dsc df2a87d4d66854ccab7909841bbe587ba6f89671aae22eaa5b2b1a32b4c2f7a3 2700 libcompress-raw-lzma-perl_2.069-2.debian.tar.xz Files: 34b69d287a6cc38581be018b3172feca 2306 perl optional libcompress-raw-lzma-perl_2.069-2.dsc 8d1e5987d86e7e424a3a64dfe5e75a6f 2700 perl optional libcompress-raw-lzma-perl_2.069-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJ8BAEBCgBmBQJYAf6uXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGFWgP/RjyL8wPX0tZKRyJDYvEseth CVzESOeiQBXBEn9utCvt0syFmh3Eu/WpN7VBPIJ/H5jLT+dCB4ADlc/BsZAmZ5qG 9V/y+x7Vkfurv6ESMugR3bbyr4IuE75WR6LYweUtB4s4khgbZ9s3KCAHqH5LinXs pR1yF5+Z5eumSC8sO+L2wXbyUbIYSe8/zPkbFsuEtidsM/oq6JXs+DedrEdsRaV4 TXasXwwgol9CdeQS/oOp8DkDhz7u+jyrvKqUnyx5LCq1SaB7UnRUuqdcCcj5hqds gRdgx9ItCE5nJn58qrIM7DaTlGu+sG5jTWJEVAuDcLJJnALD4FHGdkrCblnbsOId lbKDYIvMydxyL8mpfo3z8dZO2jwNlIEyKNFeL5mwT+dFLqFrpqUUDOs4PtqHO
Processed: Re: Bug#840342: [nvidia-legacy-304xx-driver] Confirmation
Processing control commands: > retitle -1 nvidia-legacy-304xx-driver: OpenGL broken in 304.132 Bug #840342 [nvidia-legacy-304xx-driver] [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver Changed Bug title to 'nvidia-legacy-304xx-driver: OpenGL broken in 304.132' from '[ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver'. > tag -1 upstream Bug #840342 [nvidia-legacy-304xx-driver] nvidia-legacy-304xx-driver: OpenGL broken in 304.132 Added tag(s) upstream. > severity -1 serious Bug #840342 [nvidia-legacy-304xx-driver] nvidia-legacy-304xx-driver: OpenGL broken in 304.132 Severity set to 'serious' from 'normal' -- 840342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [pkg-gnupg-maint] Bug#840680: dirmngr: Dirmngr not always responding
Processing control commands: > severity -1 grave Bug #840680 [dirmngr] dirmngr: Dirmngr not always responding Severity set to 'grave' from 'important' -- 840680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840823: execnet: FTBFS (failing tests)
Package: src:execnet Version: 1.4.1-2 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=pybuild --with python2,python3,sphinxdoc dh_testdir -i -O--buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:184: python2.7 setup.py config running config I: pybuild base:184: python3.5 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:184: /usr/bin/python setup.py build running build running build_py [... snipped ...] testing/test_gateway.py::TestBasicGateway::test_gateway_status_no_real_channel[thread-ssh] SKIPPED testing/test_gateway.py::TestBasicGateway::test_gateway_status_no_real_channel[thread-proxy] PASSED testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen] FAILED === short test summary info SKIP [3] /<>/testing/conftest.py:148: no python3.2 found SKIP [3] /<>/testing/conftest.py:148: no jython found SKIP [3] /<>/testing/conftest.py:148: no python2.6 found SKIP [3] /<>/testing/conftest.py:148: no pypy found SKIP [3] /<>/testing/conftest.py:148: no python3.3 found SKIP [36] /usr/lib/python2.7/dist-packages/_pytest/config.py:1142: no 'gspecs' option found === FAILURES === ___ TestBasicGateway.test_gateway_status_busy[thread-popen] self = gw = def test_gateway_status_busy(self, gw): numchannels = gw.remote_status().numchannels ch1 = gw.remote_exec("channel.send(1); channel.receive()") ch2 = gw.remote_exec("channel.receive()") ch1.receive() status = gw.remote_status() assert status.numexecuting == 2 # number of active execution threads assert status.numchannels == numchannels + 2 ch1.send(None) ch2.send(None) ch1.waitclose() ch2.waitclose() for i in range(10): status = gw.remote_status() if status.numexecuting == 0: break else: > pytest.fail("did not get correct remote status") E Failed: did not get correct remote status testing/test_gateway.py:88: Failed pytest-warning summary WI1 /<>/testing/conftest.py:21 'pytest_runtest_setup' hook uses deprecated __multicall__ argument WC1 None pytest_funcarg__specsocket: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. Interrupted: stopping after 1 failures = 1 failed, 135 passed, 51 skipped, 3 pytest-warnings in 8.69 seconds == E: pybuild pybuild:276: test: plugin custom failed with: exit code=2: python2.7 -m pytest -v -x -rs testing/ dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned exit code 13 debian/rules:8: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 25 make[1]: Leaving directory '/<>' debian/rules:5: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 The relevant part of the build log is included above. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. Thanks.
Bug#840824: ruby-text-table: FTBFS (failing tests)
Package: src:ruby-text-table Version: 1.2.4-1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=ruby --with ruby dh_testdir -i -O--buildsystem=ruby dh_update_autotools_config -i -O--buildsystem=ruby dh_auto_configure -i -O--buildsystem=ruby dh_ruby --configure dh_auto_build -i -O--buildsystem=ruby dh_ruby --build dh_ruby --build dh_auto_test -i -O--buildsystem=ruby dh_ruby --test fakeroot debian/rules binary-indep dh binary-indep --buildsystem=ruby --with ruby [... snipped ...] 1) Text::Table table-wide alignment of rows # Not yet implemented # ./spec/integration/alignment_spec.rb:174 2) Text::Table table-wide alignment of headers # Not yet implemented # ./spec/integration/alignment_spec.rb:178 3) Text::Table table-wide alignment of footers # Not yet implemented # ./spec/integration/alignment_spec.rb:182 4) Text::Table rows with unequal number of cells # Not yet implemented # ./spec/integration/parts_spec.rb:27 Failures: 1) Text::Table::Cell should return correct column index Failure/Error: @table.text_table_rows.first.cells[2].column_index.should == 3 expected: 3 got: 2 (using ==) # ./spec/cell_spec.rb:20:in `block (2 levels) in ' Deprecation Warnings: Requiring `rspec/autorun` when running RSpec via the `rspec` command is deprecated. Called from /<>/spec/spec_helper.rb:5:in `'. Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /<>/spec/cell_spec.rb:10:in `block (2 levels) in '. If you need more of the backtrace for any of these deprecations to identify where to make the necessary changes, you can configure `config.raise_errors_for_deprecations!`, and it will turn the deprecation warnings into errors, giving you the full backtrace. 2 deprecation warnings total Finished in 0.05929 seconds (files took 0.12143 seconds to load) 47 examples, 1 failure, 4 pending Failed examples: rspec ./spec/cell_spec.rb:17 # Text::Table::Cell should return correct column index /usr/bin/ruby2.3 /usr/bin/rspec ./spec/cell_spec.rb ./spec/enumerable_spec.rb ./spec/integration/alignment_spec.rb ./spec/integration/boundaries_spec.rb ./spec/integration/column_spans_spec.rb ./spec/integration/parts_spec.rb failed ERROR: Test "ruby2.3" failed. Exiting. dh_auto_install: dh_ruby --install /<>/debian/ruby-text-table returned exit code 1 debian/rules:15: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 The relevant part of the build log is included above. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. Thanks.
Bug#840825: libtag1-dev: missing header files
Package: libtag1-dev Version: 1.11+dfsg.1-0.1 Severity: serious Control: affects -1 kid3 X-Debbugs-CC: m...@lm7.fr Hi, taglib 1.11+dfsg.1-0.1 and 1.11+dfsg.1-0.2 are missing various include files which should be shipped in /usr/include. These are reported by dh_install: dh_install --list-missing dh_install: usr/include/taglib/podcastframe.h exists in debian/tmp but is not installed to anywhere dh_install: usr/include/taglib/tableofcontentsframe.h exists in debian/tmp but is not installed to anywhere dh_install: usr/include/taglib/eventtimingcodesframe.h exists in debian/tmp but is not installed to anywhere dh_install: usr/include/taglib/chapterframe.h exists in debian/tmp but is not installed to anywhere dh_install: usr/include/taglib/synchronizedlyricsframe.h exists in debian/tmp but is not installed to anywhere This at least breaks kid3 which uses these headers if taglib is new enough. Can I also suggest enabling "dh_install --fail-missing" so this doesn't happen again :) Thanks, James signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#840818: nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver
Processing control commands: > severity -1 normal Bug #840818 [nvidia-driver] nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver Severity set to 'normal' from 'serious' -- 840818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840818: nvidia-driver: Breaks system on a fresh installed debian; Buggy, but overwrites nouveau driver
Control: severity -1 normal On Sat, 2016-10-15 at 12:15 +0200, Domonkos Lezsák wrote: > Package: nvidia-driver > Severity: serious > Tags: upstream > Justification: Policy 1.1 No, it's not. If this is an issue, it is _very_ specific to one type of machine. It is not a general issue with the packages. > After installing nvidia-driver on a fresh installed debian (or on it's > distributions too), the driver could not be loaded causes to boot in > low-graphics mode. Without kernel and xorg logs it's impossible to tell what the problem is. > The main problem is here, that the package overwrites the > xserver-xorg-nouveau driver and it's hard to be restored, even purging > nvidia-driver and reinstalling/reconfiguring xserver-xorg-nouveau. For me, a > complete new Debian installation was the solution. It does not overwrite nouveau, it blacklists it, and that's working as intended as the proprietary modules and the nouveau modules are mutually exclusive. > The package was working earlyer on Linux Mint Sarah, but now breaks both > system. > > # Hardware configuration: > Dell Precision M4600 > with dual-video card: > * 1x Nvidia Quadro 2000M > * 1x Intel HD 1000 <-- Not identified by even lspci I can only find conflicting information online, some say that laptop is an optimus system, some say it isn't. You should check your BIOS, make sure it is up to date, and check if there are optimus or switchable graphics options. If it is an optimus system, you must install bumblebee-nvidia, and then the Intel card will be used as the main gpu and you can use the discrete one via optirun. https://wiki.debian.org/Bumblebee If it is not an optimus system, then it most likely has a switch in the bios to decide which card to use. Or it could be hardcoded to always use the nvidia one. In this case it is very much dependent on the specific hardware. Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Processed: libtag1-dev: missing header files
Processing control commands: > affects -1 kid3 Bug #840825 [libtag1-dev] libtag1-dev: missing header files Added indication that 840825 affects kid3 -- 840825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840826: princeprocessor: /usr/bin/pp64 is already used by polylib-utils
Package: princeprocessor Version: 0.21-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Selecting previously unselected package princeprocessor. Preparing to unpack .../princeprocessor_0.21-2_amd64.deb ... Unpacking princeprocessor (0.21-2) ... dpkg: error processing archive /var/cache/apt/archives/princeprocessor_0.21-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/pp64', which is also in package polylib-utils 5.22.5-3+dfsg Errors were encountered while processing: /var/cache/apt/archives/princeprocessor_0.21-2_amd64.deb Probably the newly introduced packages should rename that binary. cheers, Andreas
Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)
Package: src:lucene-solr Version: 3.6.2+dfsg-8 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --with maven_repo_helper dh_testdir -i dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>/lucene-solr-3.6.2+dfsg' # Link in jars from /usr/share/java rather # than patching the build process for pkg in `cat debian/build-jars`; \ do \ ln -sf `echo $pkg | cut -d : -f 1` `echo $pkg | cut -d : -f 2`; \ done ln: failed to create symbolic link './lucene/lib/ant.jar': No such file or directory [... snipped ...] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:535) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1182) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1033) [junit] Caused by: java.net.NoRouteToHostException: No route to host [junit] at java.net.PlainSocketImpl.socketConnect(Native Method) [junit] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [junit] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [junit] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [junit] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [junit] at java.net.Socket.connect(Socket.java:589) [junit] at java.net.Socket.connect(Socket.java:538) [junit] at java.net.Socket.(Socket.java:434) [junit] at java.net.Socket.(Socket.java:211) [junit] at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) [junit] at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148) [junit] at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) [junit] ... 44 more [junit] [junit] [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.301 sec [junit] [junit] - Standard Error - [junit] NOTE: reproduce with: ant test -Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter -Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b -Dargs="-Dfile.encoding=ANSI_X3.4-1968" [junit] NOTE: reproduce with: ant test -Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter -Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b -Dargs="-Dfile.encoding=ANSI_X3.4-1968" [junit] NOTE: test params are: locale=it, timezone=Pacific/Enderbury [junit] NOTE: all tests run in this JVM: [junit] [TestRemoteCachingWrapperFilter] [junit] NOTE: Linux 4.7.0-1-amd64 amd64/Oracle Corporation 1.8.0_102 (64-bit)/cpus=1,threads=1,free=86734984,total=95354880 [junit] - --- [junit] Test org.apache.lucene.search.TestRemoteCachingWrapperFilter FAILED BUILD FAILED /<>/lucene-solr-3.6.2+dfsg/lucene/build.xml:584: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:1051: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/contrib/contrib-build.xml:61: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:692: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed! The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed! The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed! The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed! Total time: 10 minutes 58 seconds debian/rules:31: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>/lucene-solr-3.6.2+dfsg' debian/rules:8: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 The build was made in a KVM/QEMU virtual machine with 1 CPU using sbuild. I attach a full build log, but the build system leaks the IP of the machine (it probably shouldn't). I've redacted that. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible
Processed: user debian...@lists.debian.org, usertagging 840788, affects 840788, severity of 840788 is serious
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 840788 piuparts There were no usertags set. Usertags are now: piuparts. > affects 840788 + libvtk6-dev Bug #840788 [src:vtk6] vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev Added indication that 840788 affects libvtk6-dev > severity 840788 serious Bug #840788 [src:vtk6] vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 840788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840826: princeprocessor: /usr/bin/pp64 is already used by polylib-utils
Hi Andreas, thanks for noticing this and letting me know. I will make sure to rename the single binary in this package to avoid the name clash. Cheers Sascha > On 15 Oct 2016, at 13:22, Andreas Beckmann wrote: > > Package: princeprocessor > Version: 0.21-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install > because it tries to overwrite other packages files. > > Selecting previously unselected package princeprocessor. > Preparing to unpack .../princeprocessor_0.21-2_amd64.deb ... > Unpacking princeprocessor (0.21-2) ... > dpkg: error processing archive > /var/cache/apt/archives/princeprocessor_0.21-2_amd64.deb (--unpack): > trying to overwrite '/usr/bin/pp64', which is also in package polylib-utils > 5.22.5-3+dfsg > Errors were encountered while processing: > /var/cache/apt/archives/princeprocessor_0.21-2_amd64.deb > > Probably the newly introduced packages should rename that binary. > > > cheers, > > Andreas > >
Processed: retitle 840806 to libgd2: CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr()
Processing commands for cont...@bugs.debian.org: > retitle 840806 libgd2: CVE-2016-6911: invalid read in > gdImageCreateFromTiffPtr() Bug #840806 [src:libgd2] libgd2: invalid read in gdImageCreateFromTiffPtr() Changed Bug title to 'libgd2: CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr()' from 'libgd2: invalid read in gdImageCreateFromTiffPtr()'. > thanks Stopping processing here. Please contact me if you need assistance. -- 840806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)
I forgot to tell that I can reproduce this only on some machines but not in others. The machines on which it fails (there are more than one) seem to be the ones having some corporate firewall rules I can't disable. This is probably not just a coincidence. However, since packages are not supposed to use the network during the build, a bad network configuration should never make the package to FTBFS anyway. Thanks.
Bug#840831: libvirtuoso5.5-cil: fails to install: E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed
Package: libvirtuoso5.5-cil Version: 6.1.6+dfsg2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package libvirtuoso5.5-cil. (Reading database ... (Reading database ... 7366 files and directories currently installed.) Preparing to unpack .../libvirtuoso5.5-cil_6.1.6+dfsg2-3+b1_amd64.deb ... Unpacking libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ... Setting up libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ... * Installing 1 assembly from libvirtuoso5.5-cil into Mono E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed E: Installation of libvirtuoso5.5-cil with /usr/share/cli-common/runtimes.d/mono failed dpkg: error processing package libvirtuoso5.5-cil (--configure): subprocess installed post-installation script returned error exit status 29 Errors were encountered while processing: libvirtuoso5.5-cil cheers, andreas libvirtuoso5.5-cil_6.1.6+dfsg2-3+b1.log.gz Description: application/gzip
Processed: Bug#840826 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 840826 pending Bug #840826 [princeprocessor] princeprocessor: /usr/bin/pp64 is already used by polylib-utils Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 840826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840826: marked as pending
tag 840826 pending thanks Hello, Bug #840826 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-security/princeprocessor.git;a=commitdiff;h=75e5860 --- commit 75e58607c5d13c027f55015c19a495e26d9f7712 Author: Sascha Steinbiss Date: Sat Oct 15 11:52:55 2016 + rename binary to avoid name clash diff --git a/debian/changelog b/debian/changelog index 9c5a6a5..021ff75 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +princeprocessor (0.21-3) UNRELEASED; urgency=medium + + * Rename executable to avoid name clash with /usr/bin/pp64 from +polylib-utils. Thanks to Andreas Beckmann for the hint. +Closes: #840826 + + -- Sascha Steinbiss Sat, 15 Oct 2016 11:39:50 + + princeprocessor (0.21-2) unstable; urgency=medium * Restrict architectures to 64-bit ones.
Bug#839190:
hello dearest
Bug#840725: marked as done (libhmsbeagle: FTBFS and bd-uninstallable almost everywhere)
Your message dated Sat, 15 Oct 2016 12:25:47 + with message-id and subject line Bug#840725: fixed in libhmsbeagle 2.1.2+20160831-1 has caused the Debian Bug report #840725, regarding libhmsbeagle: FTBFS and bd-uninstallable almost everywhere 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.) -- 840725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libhmsbeagle Version: 2.1.2+20160525-1 Severity: serious Hi, Your package failed to build on i386 with: /«BUILDDIR»/libhmsbeagle-2.1.2+20160525/libhmsbeagle/GPU/GPUInterface.h: In member function 'void opencl_device::GPUInterface::PrintfDeviceVector(GPUPtr, int, double, int*, Real)': /«BUILDDIR»/libhmsbeagle-2.1.2+20160525/libhmsbeagle/GPU/GPUInterface.h:188:55: error: there are no arguments to 'malloc' that depend on a template parameter, so a declaration of 'malloc' must be available [-fpermissive] Real* hPtr = (Real*) malloc(sizeof(Real) * length); ^ Also, the package is bd-uninstallable everywhere else because libpoclu-dev is not available. See https://buildd.debian.org/status/package.php?p=libhmsbeagle Emilio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: libhmsbeagle Source-Version: 2.1.2+20160831-1 We believe that the bug you reported is fixed in the latest version of libhmsbeagle, 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 840...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libhmsbeagle 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: Sat, 15 Oct 2016 13:15:32 +0200 Source: libhmsbeagle Binary: libhmsbeagle-dev libhmsbeagle1v5 libhmsbeagle-java Architecture: source amd64 Version: 2.1.2+20160831-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libhmsbeagle-dev - High-performance lib for Bayesian and Maximum Likelihood phylogen libhmsbeagle-java - High-performance lib for Bayesian and Maximum Likelihood phylogen libhmsbeagle1v5 - High-performance lib for Bayesian and Maximum Likelihood phylogen Closes: 827120 840725 Changes: libhmsbeagle (2.1.2+20160831-1) unstable; urgency=medium . * New upstream commit * d/watch pointing to Github * ocl-icd-opencl-dev now provided by khronos-opencl-clhpp Closes: #840725 * Fixed symlink Closes: #827120 Checksums-Sha1: 267c764044a6cb5c232f4f04e76f7746541ca97c 2424 libhmsbeagle_2.1.2+20160831-1.dsc f5a6b9cb8b44d2a57a2d5a1cc21649f80736fe8d 248912 libhmsbeagle_2.1.2+20160831.orig.tar.xz 0fea75ed5138aab69a7fb91d8b4c6d0ed6d2b927 35948 libhmsbeagle_2.1.2+20160831-1.debian.tar.xz 94796f8feb1e87385de239ace019fda317cb3b6f 166138 libhmsbeagle-dev_2.1.2+20160831-1_amd64.deb 4f73b1a7e94f3fbd5043d467ca69f873d15fab9e 23982 libhmsbeagle-java_2.1.2+20160831-1_amd64.deb f93c2a4b425e90d4a4bb7dbc74c2ce4a3bfe0f33 690386 libhmsbeagle1v5-dbgsym_2.1.2+20160831-1_amd64.deb d7fb20303bcf390122f080e1394b6c19309750e5 116178 libhmsbeagle1v5_2.1.2+20160831-1_amd64.deb Checksums-Sha256: 9bc2c33ba4a63653ab20377bc3d80a31f7aebca555c2386b23f4b1ee64cfcf08 2424 libhmsbeagle_2.1.2+20160831-1.dsc 476fd0a17f2b6ea9560cd0f0c9105936f5da77b9c85717cfaa6042a861a9782f 248912 libhmsbeagle_2.1.2+20160831.orig.tar.xz 9c70812375add4e5a3860d17d0dcad9bfdc62181532264e28eebeee67e529600 35948 libhmsbeagle_2.1.2+20160831-1.debian.tar.xz d994f2606b3db5c2286c03fb05047e517fa884565cb25a4a1696acb435767362 166138 libhmsbeagle-dev_2.1.2+20160831-1_amd64.deb 3511c33ad082611947a6ecd1afb9303b243382ed3af3bab2cb73755b48809aad 23982 libhmsbeagle-java_2.1.2+2016
Bug#838671: marked as done (openchangeproxy: uninstallable in jessie, broken by samba)
Your message dated Sat, 15 Oct 2016 15:40:10 +0300 with message-id <20161015124010.cquf4kwha5fkz...@bunk.spdns.de> and subject line openchangeproxy has been removed from unstable has caused the Debian Bug report #838671, regarding openchangeproxy: uninstallable in jessie, broken by samba 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.) -- 838671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openchangeproxy Version: 1:2.2-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in stable: Package: openchangeproxy Source: openchange (1:2.2-5) Version: 1:2.2-5+b1 Depends: ..., samba-libs (>= 2:4.1.13+dfsg) Package: samba-libs Source: samba Version: 2:4.2.10+dfsg-0+deb8u3 Replaces: ... Depends: ... Pre-Depends: ... Conflicts: ... Breaks: ..., openchangeproxy (<< 1:2.2-6), ... Cheers, Andreas --- End Message --- --- Begin Message --- openchangeproxy has already been removed from unstable (#804335). cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: Version tracking fixes
Processing commands for cont...@bugs.debian.org: > found 833828 1.2.1-2 Bug #833828 [python3-django-markupfield] Migrations of stable's python3-django-markupfield (1.2.1) do not work with stable's django version (1.7.x). Marked as found in versions django-markupfield/1.2.1-2. > fixed 833828 1.4.0-1 Bug #833828 [python3-django-markupfield] Migrations of stable's python3-django-markupfield (1.2.1) do not work with stable's django version (1.7.x). Marked as fixed in versions django-markupfield/1.4.0-1. > found 834153 3.6.1-2 Bug #834153 [gitolite3] gitolite3 should depend on openssh-client Marked as found in versions gitolite3/3.6.1-2. > fixed 834153 3.6.4-2 Bug #834153 [gitolite3] gitolite3 should depend on openssh-client There is no source info for the package 'gitolite3' at version '3.6.4-2' with architecture '' Unable to make a source version for version '3.6.4-2' Marked as fixed in versions 3.6.4-2. > found 839130 10.0.27-1 Bug #839130 [mariadb-server-10.0] mariadb-server-10.0: mariadb-server stops after each apt install related command Marked as found in versions mariadb-10.0/10.0.27-1. > tags 840698 -experimental Bug #840698 [xnetcardconfig] xnetcardconfig: does not work with ruby-gnome2 3.0.9-1 Removed tag(s) experimental. > tags 840699 -experimental Bug #840699 [ninix-aya] ninix-aya: does not work with ruby-gnome2 3.0.9-1 Removed tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 833828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833828 834153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834153 839130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839130 840698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840698 840699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere
Processing control commands: > reopen -1 Bug #840725 {Done: Andreas Tille } [src:libhmsbeagle] libhmsbeagle: FTBFS and bd-uninstallable almost everywhere 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions libhmsbeagle/2.1.2+20160831-1. > found -1 2.1.2+20160831-1 Bug #840725 [src:libhmsbeagle] libhmsbeagle: FTBFS and bd-uninstallable almost everywhere Marked as found in versions libhmsbeagle/2.1.2+20160831-1. -- 840725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere
Control: reopen -1 Control: found -1 2.1.2+20160831-1 Hi, On 14/10/16 10:21, Andreas Tille wrote: > Hi Emilio, > > this is a known issue which would be fixed if khronos-opencl-clhpp would > be accepted by ftpmaster in new queue. I've given a hint to frpmaster > about this hoping that this can be solved quickly but unfortunately with > no success so far. :-( Not sure how that was supposed to help, but the new version still fails to build on i386, and is still bd-uninst because of the missing libpoclu-dev everywhere else, see https://buildd.debian.org/status/package.php?p=libhmsbeagle Cheers, Emilio
Processed: user debian...@lists.debian.org, usertagging 837281, affects 837281, reopening 837281
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 837281 piuparts Usertags were: qa-ftbfs qa-ftbfs-20160910. Usertags are now: qa-ftbfs piuparts qa-ftbfs-20160910. > affects 837281 + python-manila-ui Bug #837281 {Done: Thomas Goirand } [src:manila-ui] manila-ui: FTBFS: compressor.exceptions.OfflineGenerationError: No template loaders defined. You must set TEMPLATE_LOADERS in your settings or set 'loaders' in your TEMPLATES dictionary. Added indication that 837281 affects python-manila-ui > reopen 837281 Bug #837281 {Done: Thomas Goirand } [src:manila-ui] manila-ui: FTBFS: compressor.exceptions.OfflineGenerationError: No template loaders defined. You must set TEMPLATE_LOADERS in your settings or set 'loaders' in your TEMPLATES dictionary. 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions manila-ui/2.5.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 837281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#837281: manila-ui: FTBFS: compressor.exceptions.OfflineGenerationError: No template loaders defined. You must set TEMPLATE_LOADERS in your settings or set 'loaders' in your TEMPLATES dictionary.
Followup-For: Bug #837281 Hi, attached is a piuparts log from python-manila-ui_2.5.1-0 in stretch showing the same problem. This pulled in python-django all 1:1.10.1-1 python-django-horizon all 3:9.0.1-2 openstack-dashboard all 3:9.0.1-2 python-django-horizon and openstack-dashboard have 3:10.0.0-1 in unstable, so maybe the dependencies are not yet strict enough to pull in all the required new package versions? Andreas python-manila-ui_2.5.1-0.log.gz Description: application/gzip
Bug#839931: freeradius-config: fails to upgrade from 'sid' - trying to overwrite /etc/freeradius/clients.conf
Followup-For: Bug #839931 Control: found -1 3.0.12+dfsg-1 Hi, there are still file overwrite problems in the latest version: Preparing to unpack .../07-freeradius_3.0.12+dfsg-1_amd64.deb ... Unpacking freeradius (3.0.12+dfsg-1) over (2.2.8+dfsg-0.1+b3) ... dpkg: warning: unable to delete old directory '/etc/freeradius/sites-enabled': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius/sites-available': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius/modules': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius/certs': Directory not empty dpkg: warning: unable to delete old directory '/etc/freeradius': Directory not empty Selecting previously unselected package freeradius-config. Preparing to unpack .../08-freeradius-config_3.0.12+dfsg-1_amd64.deb ... Unpacking freeradius-config (3.0.12+dfsg-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-5B7fDA/08-freeradius-config_3.0.12+dfsg-1_amd64.deb (--unpack): trying to overwrite '/etc/freeradius/hints', which is also in package freeradius 3.0.12+dfsg-1 Andreas
Processed: Re: freeradius-config: fails to upgrade from 'sid' - trying to overwrite /etc/freeradius/clients.conf
Processing control commands: > found -1 3.0.12+dfsg-1 Bug #839931 {Done: Michael Stapelberg } [freeradius-config] freeradius-config: fails to upgrade from 'sid' - trying to overwrite /etc/freeradius/clients.conf Marked as found in versions freeradius/3.0.12+dfsg-1; no longer marked as fixed in versions freeradius/3.0.12+dfsg-1 and reopened. -- 839931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840840: pocl: Does not build on several architectures
Source: pocl Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, the pocl source does not build on several architectures where it has built before. The problem seem to be failed tests. Please see: https://buildd.debian.org/status/package.php?p=pocl Kind regards and thanks for maintaining pocl Andreas. -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#840841: digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded
Package: digikam Version: 4:5.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'stretch' fails. >From the attached log (scroll to the bottom...): [...] # distupgrade from jessie to stretch 3m14.4s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA', 'apt-get', '-yf', 'dist-upgrade'] 5m43.2s DUMP: Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: [...] Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: digikam digikam-private-libs libclucene-core1 libebml4 libgpgme++2 libmarblewidget19 libmatroska6 libopencv-calib3d2.4 libopencv-contrib2.4 libopencv-core2.4 libopencv-features2d2.4 libopencv-flann2.4 libopencv-highgui2.4 libopencv-imgproc2.4 libopencv-ml2.4 libopencv-objdetect2.4 libopencv-video2.4 libproxy1 libstreamanalyzer0 libtag1-vanilla libtag1c2a perl-modules vlc-plugin-pulse The following NEW packages will be installed: [...] # ok, lets try to install it in stretch 5m45.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA', 'apt-get', '-y', 'install', 'digikam'] 5m45.6s DUMP: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: digikam : Depends: digikam-private-libs (= 4:5.2.0-1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. 5m45.6s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmp_SRqAA', 'apt-get', '-y', 'install', 'digikam'] cheers, Andreas digikam_4:5.2.0-1.log.gz Description: application/gzip
Bug#840845: python-pygraphviz: FTBFS with /bin/sh as bash
Source: python-pygraphviz Version: 1.3.1-1 Severity: serious Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, Due to the commented-out "set -e; \" line (note the trailing backslash!), python-pygraphviz FTBFS when /bin/sh is bash. Minimal patch attached. However, you should probably uncomment the set -e bit and drop the leading - so that test failures actually cause a FTBFS otherwise that's another bug IMHO. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/debian/rules b/debian/rules index fcb04c5..f0e6a22 100755 --- a/debian/rules +++ b/debian/rules @@ -42,7 +42,7 @@ override_dh_installdocs: override_dh_auto_test: ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),) - #set -e; \ + #set -e; -for python in $(PYTHON2) $(PYTHON3); do \ echo "-- running tests for "$$python" plain --" ; \ LIB=$$($$python -c "from distutils.command.build import build ; from distutils.core import Distribution ; b = build(Distribution()) ; b.finalize_options() ; print (b.build_platlib)") ; \
Bug#839791: qtcreator: builds with clang support on armel
On miércoles, 5 de octubre de 2016 12:52:08 A. M. ART Emilio Pozuelo Monfort wrote: > Source: qtcreator > Version: 4.1.0-1 > Severity: serious > > Hi! > > qtcreator builds with LLVM 3.8 on armel, however LLVM 3.8 is not > available there. (Well, there is an old version still in the archive, > built from a snapshot from llvm-toolchain-snapshot, which hasn't been > removed yet, that will happen soon in #839033. > > Note this is blocking testing migration: Hi! I'm missing some commits in the repo, as soon as they are pushed I'll happily fix this. Soory for the delay! -- I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. Linus Benedict Torvalds. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: Fw: Bug#837798: RFS: libcgicc/3.2.16-0.1 NMU -- C++ class library for writing CGI applications
Processing control commands: > tags -1 patch pending Bug #811988 [libcgicc] libcgicc: FTBFS with GCC 6: call overloaded is ambiguous Added tag(s) pending and patch. -- 811988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840840: marked as done (pocl: Does not build on several architectures)
Your message dated Sat, 15 Oct 2016 15:59:16 +0200 with message-id and subject line Re: Bug#840840: pocl: Does not build on several architectures has caused the Debian Bug report #840840, regarding pocl: Does not build on several architectures 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.) -- 840840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pocl Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, the pocl source does not build on several architectures where it has built before. The problem seem to be failed tests. Please see: https://buildd.debian.org/status/package.php?p=pocl Kind regards and thanks for maintaining pocl Andreas. -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- On 2016-10-15 15:28, Andreas Tille wrote: > the pocl source does not build on several architectures where it has built > before. The problem seem to be failed tests. Please see: Huh? The only architecture with outdated binaries is powerpcspe (which only "successfully" built them in the past thanks to a nocheck buildd). Feel free to get them decrufted as well. Andreas--- End Message ---
Bug#840825: libtag1-dev: missing header files
Hi James, Le samedi 15 octobre 2016, 12:02:06 EDT James Cowgill a écrit : > taglib 1.11+dfsg.1-0.1 and 1.11+dfsg.1-0.2 are missing various include > files which should be shipped in /usr/include. These are reported by > dh_install: Thanks for reporting the problem and sorry for the trouble. I'll be working on a new NMU in the next few days. > This at least breaks kid3 which uses these headers if taglib is new > enough. Can I also suggest enabling "dh_install --fail-missing" so this > doesn't happen again :) Will do, thanks for the suggestion! Cheers, Matteo signature.asc Description: This is a digitally signed message part.
Bug#840840: pocl: Does not build on several architectures
Hi Andreas, On Sat, Oct 15, 2016 at 03:59:16PM +0200, Andreas Beckmann wrote: > Huh? The only architecture with outdated binaries is powerpcspe (which > only "successfully" built them in the past thanks to a nocheck buildd). > Feel free to get them decrufted as well. What about arm64: https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=arm64&ver=0.13-8&stamp=1476101601 armhf: https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=armhf&ver=0.13-8&stamp=1476101525 mips: https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=mips&ver=0.13-8&stamp=1476107564 and all those others listed here https://buildd.debian.org/status/package.php?p=pocl Kind regards Andreas. -- http://fam-tille.de
Bug#840847: freezegun: FTBFS under some timezones (eg. GMT-14)
Source: freezegun Version: 0.3.6-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs timezones X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, freezegun fails to build from source in logs/unstable undersome timezones (eg. TZ="/usr/share/zoneinfo/Etc/GMT-14"): [..] == FAIL: tests.test_class_import.test_import_localtime -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/build-2nd/freezegun-0.3.6/freezegun/api.py", line 449, in wrapper result = func(*args, **kwargs) File "/build-2nd/freezegun-0.3.6/tests/test_class_import.py", line 83, in test_import_localtime assert struct.tm_mday == 14 AssertionError: time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1) = fake_localtime_function() assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_year == 2012 assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_mon == 1 >> assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_mday == 14 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/debian/logs/unstable/amd64/freezegun_0.3.6-1.build2.log.gz (Note the use of fake_localtime, which is going to vary under such extreme timezones.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- freezegun.0.3.6-1.logs.unstable.log.txt.gz Description: Binary data
Bug#840840: pocl: Does not build on several architectures
On 2016-10-15 16:09, Andreas Tille wrote: > Hi Andreas, > > On Sat, Oct 15, 2016 at 03:59:16PM +0200, Andreas Beckmann wrote: >> Huh? The only architecture with outdated binaries is powerpcspe (which >> only "successfully" built them in the past thanks to a nocheck buildd). >> Feel free to get them decrufted as well. > > What about > >arm64: > https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=arm64&ver=0.13-8&stamp=1476101601 >armhf: > https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=armhf&ver=0.13-8&stamp=1476101525 >mips: > https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=mips&ver=0.13-8&stamp=1476107564 > > and all those others listed here > >https://buildd.debian.org/status/package.php?p=pocl Right, pocl FTBFS everywhere except linux-i386/amd64, and always has (with maybe some spurious successes when tests were not being run). Everything outdated on the release architectures has been decrufted. Or did you want to file a *wishlist* bug to support more architectures? FTBFS on an architecture where it has not been built before (i.e. no outdated binary packages in the archive that would prevent testing migration) is not RC. Andreas
Bug#840488: bareos: Bareos crashes on "status dir"
Package: bareos Version: 15.2.4-1+b1 Followup-For: Bug #840488 Dear Maintainer, This bug also appears with: bconsole -> status all or if you enter just status and then select 5 ("All") It appears with postgresql 9.5 and 9.6 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bareos depends on: ii bareos-client15.2.4-1+b1 ii bareos-director 15.2.4-1+b1 ii bareos-storage 15.2.4-1+b1 bareos recommends no packages. bareos suggests no packages. -- no debconf information
Bug#811863: Fix/Workaround for the tagcoll2 FTBFS
Control: tags 811863 +patch What broke the build is that gcc 6 changed the default C++ standard from C++98 to C++14. Not all valid C++98 code is also valid C++11 and C++14 code. Note that this just changed the default, when told to process C++98 code gcc 6 does not differ in any significant way from gcc 5. Making the code compatible with C++14 would be the best possible solution, but as a workaround it is possible to fix the build with this change to tell gcc that this is C++98 code. --- debian/rules.old2016-10-15 15:35:54.0 + +++ debian/rules2016-10-15 15:36:40.0 + @@ -1,5 +1,7 @@ #!/usr/bin/make -f +export DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++98 + %: dh $@ cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Fix/Workaround for the tagcoll2 FTBFS
Processing control commands: > tags 811863 +patch Bug #811863 [tagcoll2] tagcoll2: FTBFS with GCC 6: no matching function for call to Added tag(s) patch. -- 811863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#821701: [Pkg-php-pecl] Bug#821701: src:php-json: PHP 7.0 Transition
On Tue, Apr 19, 2016 at 10:17:50AM +0200, Ondřej Surý wrote: > Control: notfound -1 php-json/1:7.0+35 > Control: found -1 php-json/1.3.7-1 > Control: severity -1 serious Hi Ondřej, is there any reason for keeping the php-json source package in unstable, or should it be removed? Thanks Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: tagging 840841
Processing commands for cont...@bugs.debian.org: > tags 840841 + help Bug #840841 [digikam] digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 840841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#821701: [Pkg-php-pecl] Bug#821701: src:php-json: PHP 7.0 Transition
Adrian, it needs to go together with src:php5 that we still keep for s-p-u. But I was just going to ask security team if that's still needed since we are doing all updates via jessie-security anyway. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu On Sat, Oct 15, 2016, at 17:54, Adrian Bunk wrote: > On Tue, Apr 19, 2016 at 10:17:50AM +0200, Ondřej Surý wrote: > > Control: notfound -1 php-json/1:7.0+35 > > Control: found -1 php-json/1.3.7-1 > > Control: severity -1 serious > > Hi Ondřej, > > is there any reason for keeping the php-json source package in unstable, > or should it be removed? > > Thanks > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed >
Bug#822981: marked as done (tomcat-maven-plugin: FTBFS: [..] org.codehaus.plexus:plexus-component-metadata:jar:1.0-beta-3.0.7 has not been downloaded)
Your message dated Sat, 15 Oct 2016 18:58:07 +0300 with message-id <20161015155807.7qlcbzlhj5njp...@bunk.spdns.de> and subject line tomcat-maven-plugin was removed from Debian has caused the Debian Bug report #822981, regarding tomcat-maven-plugin: FTBFS: [..] org.codehaus.plexus:plexus-component-metadata:jar:1.0-beta-3.0.7 has not been downloaded 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.) -- 822981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tomcat-maven-plugin Version: 1.1-2.4 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, tomcat-maven-plugin fails to build from source in unstable/amd64: [..] Adding debian:Actalis_Authentication_Root_CA.pem Adding debian:AddTrust_External_Root.pem Adding debian:AddTrust_Low-Value_Services_Root.pem Adding debian:AddTrust_Public_Services_Root.pem Adding debian:AddTrust_Qualified_Certificates_Root.pem Adding debian:AffirmTrust_Commercial.pem Adding debian:AffirmTrust_Networking.pem Adding debian:AffirmTrust_Premium.pem Adding debian:AffirmTrust_Premium_ECC.pem Adding debian:ApplicationCA_-_Japanese_Government.pem Adding debian:Atos_TrustedRoot_2011.pem Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem Adding debian:Baltimore_CyberTrust_Root.pem Adding debian:Buypass_Class_2_CA_1.pem Adding debian:Buypass_Class_2_Root_CA.pem Adding debian:Buypass_Class_3_Root_CA.pem Adding debian:CA_Disig.pem Adding debian:CA_Disig_Root_R1.pem Adding debian:CA_Disig_Root_R2.pem Adding debian:CA_WoSign_ECC_Root.pem Adding debian:CFCA_EV_ROOT.pem Adding debian:CNNIC_ROOT.pem Adding debian:COMODO_Certification_Authority.pem Adding debian:COMODO_ECC_Certification_Authority.pem Adding debian:COMODO_RSA_Certification_Authority.pem Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem Adding debian:Camerfirma_Global_Chambersign_Root.pem Adding debian:Certification_Authority_of_WoSign_G2.pem Adding debian:Certigna.pem Adding debian:Certinomis_-_Autorité_Racine.pem Adding debian:Certinomis_-_Root_CA.pem Adding debian:Certplus_Class_2_Primary_CA.pem Adding debian:Certum_Root_CA.pem Adding debian:Certum_Trusted_Network_CA.pem Adding debian:Chambers_of_Commerce_Root_-_2008.pem Adding debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem Adding debian:ComSign_CA.pem Adding debian:Comodo_AAA_Services_root.pem Adding debian:Comodo_Secure_Services_root.pem Adding debian:Comodo_Trusted_Services_root.pem Adding debian:Cybertrust_Global_Root.pem Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem Adding debian:DST_ACES_CA_X6.pem Adding debian:DST_Root_CA_X3.pem Adding debian:Deutsche_Telekom_Root_CA_2.pem Adding debian:DigiCert_Assured_ID_Root_CA.pem Adding debian:DigiCert_Assured_ID_Root_G2.pem Adding debian:DigiCert_Assured_ID_Root_G3.pem Adding debian:DigiCert_Global_Root_CA.pem Adding debian:DigiCert_Global_Root_G2.pem Adding debian:DigiCert_Global_Root_G3.pem Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem Adding debian:DigiCert_Trusted_Root_G4.pem Adding debian:E-Tugra_Certification_Authority.pem Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem Adding debian:EC-ACC.pem Adding debian:EE_Certification_Centre_Root_CA.pem Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem Adding debian:Entrust_Root_Certification_Authority.pem Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem Adding debian:Entrust_Root_Certification_Authority_-_G2.pem Adding debian:Equifax_Secure_CA.pem Adding debian:Equifax_Secure_Global_eBusiness_CA.pem Adding debian:Equifax_Secure_eBusiness_CA_1.pem Adding debian:GeoTrust_Global_CA.pem Adding debian:GeoTrust_Global_CA_2.pem Adding debian:GeoTrust_Primary_Certification_Authority.pem Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem Adding debian:GeoTrust_Universal_CA.pem Adding debian:GeoTrust_Universal_CA_2.pem Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem Adding debian:GlobalSign_Root_CA.pem Adding debian:GlobalSign_Root_CA_-_R2.pem Adding debian:GlobalSign_Root_CA_-_R3.pem Adding debian:Global_Chambersign_Root_-_2008.pem Adding d
Bug#824825: marked as done (liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm)
Your message dated Sat, 15 Oct 2016 19:01:56 +0300 with message-id <20161015160156.bdpcuotc2cinl...@bunk.spdns.de> and subject line This bug was already fixed has caused the Debian Bug report #824825, regarding liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite /usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm 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.) -- 824825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: liblxqt-l10n Version: 0.10.9-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package liblxqt-l10n. Preparing to unpack .../liblxqt-l10n_0.10.9-1_all.deb ... Unpacking liblxqt-l10n (0.10.9-1) ... dpkg: error processing archive /var/cache/apt/archives/liblxqt-l10n_0.10.9-1_all.deb (--unpack): trying to overwrite '/usr/share/lxqt/translations/liblxqt/liblxqt_ar.qm', which is also in package liblxqt0:amd64 0.10.0-5 Processing triggers for fontconfig (2.11.0-6.4) ... Errors were encountered while processing: /var/cache/apt/archives/liblxqt-l10n_0.10.9-1_all.deb cheers, Andreas liblxqt0=0.10.0-5_liblxqt-l10n=0.10.9-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 0.11.0-19-g717bd7e-2 lxqt-l10n (0.11.0-19-g717bd7e-2) experimental; urgency=medium * Fixed package names and versions in Breaks and Replaces (Closes: #840679) -- Alf Gaida Thu, 13 Oct 2016 21:49:35 +0200 cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#825261: marked as done (dvswitch: FTBFS in experimental)
Your message dated Sat, 15 Oct 2016 19:06:42 +0300 with message-id <20161015160642.pquvjtn7cuyzc...@bunk.spdns.de> and subject line dvswitch was removed from experimental has caused the Debian Bug report #825261, regarding dvswitch: FTBFS in experimental 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.) -- 825261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dvswitch Version: 0.9.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) dvswitch FTBFS in experimental. Since it was removed from sid already (#795838: RM: dvswitch -- ROM; FTBFS, unlikely to be fixed), perhaps it should be removed from experimental, too? Andreas --- End Message --- --- Begin Message --- dvswitch was removed from experimental (#829359). cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#840841: digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded
Hello, Thanks for the bug report. On Saturday, October 15, 2016 3:35:24 PM CDT you wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'jessie'. The output you quoted doesn't indicate WHY it was to be removed. Do you know? > # ok, lets try to install it in stretch > 5m45.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA', > 'apt-get', '-y', 'install', 'digikam'] 5m45.6s DUMP: > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: >digikam : Depends: digikam-private-libs (= 4:5.2.0-1) but it is not going > to be installed E: Unable to correct problems, you have held broken > packages. I can assure you it is installable in sid. What broken packages were being held? -Steve signature.asc Description: This is a digitally signed message part.
Bug#837236: marked as done (elixir-lang: FTBFS: Uncaught error in rebar_core: {'EXIT',)
Your message dated Sat, 15 Oct 2016 16:23:14 + with message-id and subject line Bug#837236: fixed in elixir-lang 1.3.3-2 has caused the Debian Bug report #837236, regarding elixir-lang: FTBFS: Uncaught error in rebar_core: {'EXIT', 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.) -- 837236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: elixir-lang Version: 1.2.6-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160910 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[2]: Entering directory '/<>' > cd lib/elixir && /usr/bin/rebar clean > Uncaught error in rebar_core: {'EXIT', >{undef, > [{crypto,start,[],[]}, > {rebar,run_aux,2, > [{file,"src/rebar.erl"},{line,212}]}, > {rebar,main,1, > [{file,"src/rebar.erl"},{line,58}]}, > {escript,run,2, > [{file,"escript.erl"},{line,757}]}, > {escript,start,1, > [{file,"escript.erl"},{line,277}]}, > {init,start_em,1,[]}, > {init,do_boot,3,[]}]}} > Makefile:114: recipe for target 'clean' failed > make[2]: *** [clean] Error 1 The full build log is available from: http://aws-logs.debian.net/2016/09/10/elixir-lang_1.2.6-1_unstable.log (That DNS record was just updated. Use http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it doesn't work) A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: elixir-lang Source-Version: 1.3.3-2 We believe that the bug you reported is fixed in the latest version of elixir-lang, 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 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeny Golyshev (supplier of updated elixir-lang 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: Wed, 05 Oct 2016 22:43:17 +0300 Source: elixir-lang Binary: elixir Architecture: source Version: 1.3.3-2 Distribution: unstable Urgency: medium Maintainer: Evgeny Golyshev Changed-By: Evgeny Golyshev Description: elixir - functional meta-programming aware language Closes: 837236 Changes: elixir-lang (1.3.3-2) unstable; urgency=medium . * Add erlang-crypto to Build-Depends (Closes: #837236) Checksums-Sha1: cb1c9f535e42ee1e72e424e35873207a0c20c3c7 2037 elixir-lang_1.3.3-2.dsc 475b0594d7dd0342f4de1ba8525c90ba5633724e 8224 elixir-lang_1.3.3-2.debian.tar.xz Checksums-Sha256: 9b0bfbd718218c96d5e631e616632cf06a321bc27063785a331c06cdef539af3 2037 elixir-lang_1.3.3-2.dsc dcee24b7547a551e8f54ce64c8ecc43ed4225ac36031998f753fc8b05d22100a 8224 elixir-lang_1.3.3-2.debian.tar.xz Files: 364bb55a0fa6055c8a1f59c77db1c070 2037 interpreters optional elixir-lang_1.3.3-2.dsc 2ed8447422e6d11450d55840c0309647 8224 interpreters optional elixir-lang_1.3.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYAkKHAAoJEPwNsbvNRgvelU8QAPbjFxXsYeiYrVBNpMpzR2PT k/S3CQxZ9yyYmGVVN0nm9ee9K48kANQD5Xvx+OV8kjMMz0Yexhqpo+o0lMGD6aaJ op4P5WwfM7Q1Zae7VxK4IyM/YRpIQRSe1+u+w+65YWUtTDlMAeS8LXHFhfArovj1 L3E01ikgVzL8+3fX+BUFzfui1RMiT4pS+wsrVt+7HwROeqE8q1lshzDwelo0abeA tcGvj43TduDc0VZU8hJsVX9PspAnZbtu/M8tP7vfHABRZwATJftPcZO6C37eCW5u tp7rvdpT1AwPW3SDissu7jVE448YHgCUR9oQZ11wLolTuZ0SUm8LHnSwp7AnJNr6 9IXBUW5/Qn0VLx3gC6mFv6W1BLKVr3ucoSQ48sVix2ZkvCry93a8d2F/l4omvyJ3 ab+EMSbHqcimEwhTcslAGezIFk3bKwOg1XIEv/KVXFFNxz
Bug#606048: marked as done (perdition: package upgrade removes and does not regenerate .db files)
Your message dated Sat, 15 Oct 2016 19:37:53 +0300 with message-id <20161015163753.ijnz52qvnpdce...@bunk.spdns.de> and subject line Re: Bug#606048: Perdition package upgrade removes and does not regenerate .db files has caused the Debian Bug report #606048, regarding perdition: package upgrade removes and does not regenerate .db files 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.) -- 606048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: perdition Version: 1.17.1-2+lenny2 Severity: serious I just upgraded to the latest lenny perdition package. The upgrade resulted in the /etc/perdition/popmap.*.db files being removed and not regenerated. It seems that I was upgrading from 1.17.1-2. I suspect this could be the result of the fix for bug #595432. I'm not sure if it is a bug in the old package or a bug in the new package version but the new packages should gracefully upgrade from the old, irrespective of which one is 'wrong'. This resulted in loss of service while the problem was debugged and corrected so I consider it a serious problem. Cheers, Tim -- Tim Nicholas - t...@wetafx.co.nz Systems Administrator, Weta Digital, NZ --- End Message --- --- Begin Message --- On Fri, Dec 10, 2010 at 06:29:18AM +0900, Simon Horman wrote: >... > Moving forwards this shouldn't be necessary, as > the db files aren't removed by postrm any more. > But there is no telling what version a user > might be upgrading from. Only upgrades from the previous stable (and from packages in between) are supported. I am closing this bug since it does not even seem to be relevant to squeeze -> wheezy upgrades. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: Move to the correct package
Processing commands for cont...@bugs.debian.org: > reassign 671469 src:elmerfem 6.1.0.svn.5396.dfsg-5.1 Bug #671469 [src:elmer] "FTBFS on arm*" Warning: Unknown package 'src:elmer' Bug reassigned from package 'src:elmer' to 'src:elmerfem'. No longer marked as found in versions elmer/6.1.0.svn.5396.dfsg-5.1. Ignoring request to alter fixed versions of bug #671469 to the same values previously set Bug #671469 [src:elmerfem] "FTBFS on arm*" Marked as found in versions elmerfem/6.1.0.svn.5396.dfsg-5.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 671469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#698527: marked as done (elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries)
Your message dated Sat, 15 Oct 2016 19:54:28 +0300 with message-id <20161015165428.wyomoqygfuuvl...@bunk.spdns.de> and subject line Already fixed in oldstable has caused the Debian Bug report #698527, regarding elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 698527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elmer Version: 6.1.0.svn.5396.dfsg2-1 Severity: serious Justification: Policy 2.3 Hello, this may sound like a revival of bug #618696 [1], but in fact it's distinct (although the evergreen OpenCASCADE GPL-incompatibility is still involved...). [1] http://bugs.debian.org/618696 Let's start from the beginning, anyway. I've recently found out that all libav binary packages in Debian are effectively licensed under the GNU GPL, rather than under the GNU LGPL. This would have been easier to spot, if more clearly documented [2]. [2] http://bugs.debian.org/698019 After this discover, I searched for packages potentially affected by this strong copyleft. I noticed that the binary package named "elmer" depends on some libav packages and I remembered the well-known OpenCASCADE GPL-incompatibility. Hence, I examined all the binaries shipped by the elmer binary package with ldd and I found out that /usr/bin/ElmerGUI.real is linked with the following libraries, among others: libTKSTL.so.2 [...] libTKXSBase.so.2 => OCE (OpenCASCADE Community Edition) License: OCTPL GPL-incompatible libmysqlclient.so.18 => MySQL client library License: GPL-2+ with FOSS exception (which does not allow linking with OCTPL-licensed works...) libavformat.so.53 => libavformat Effective license: GPL-3+ libavcodec.so.53 => libavcodec Effective license: GPL-2+ or libavcodec-extra Effective license: GPL-3+ libavutil.so.51 => libavutil Effective license: GPL-2+ libswscale.so.2 => libswscale Effective license: GPL-2+ (for further details, see the already mentioned bug #698019 [2], especially its message #27 [3]) [3] http://bugs.debian.org/698019#27 libcrypto.so.1.0.0 libssl.so.1.0.0 => OpenSSL License: OpenSSL license (which is GPL-incompatible!) libjbig.so.0 => JBIG-KIT library License: GPL-2+ libxvidcore.so.4 => Xvid library License: GPL-2+ libx264.so.123 => x264 library License: GPL-2+ (unless used solely through avisynth_c.h interfaces) libmp3lame.so.0 => LAME library License: GPL-2+ (since it apparently includes GPL-licensed files) So, in summary, it seems to me that this binary is linked with a number of GPL-licensed libraries, and with two GPL-incompatible libraries (OpenCASCADE Community Edition and OpenSSL). Once again, the possible solutions I can think of, in descending order of desirability, are: (A) Open CASCADE S.A.S. should be contacted and persuaded to re-license Open CASCADE Technology under GPLv2-and-v3-compatible terms; OpenSSL should be replaced by GnuTLS or disabled. (B) OpenCASCADE Community Edition should be substituted with a GPLv2-and-v3-compatible replacement, if any is available; OpenSSL should be replaced by GnuTLS or disabled. (C) All the GPL-licensed libraries should be substituted with non-strong-copyleft replacements or disabled. As usual, if anyone is willing to contribute to the persuasion effort I am carrying on to convince Open CASCADE S.A.S. to switch to the GNU LGPL v2.1, his/her help will be more than appreciated by me! As explained in bug #617613 [4], I have been trying hard to achieve this result since April 2009... [4] http://bugs.debian.org/617613 Thanks for any help you can provide. P.S.: the binary package named "libelmersolver-6.1" probably needs a similar audit --- End Message --- --- Begin Message --- I am closing this bug since it is already fixed in oldstable. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#671469: marked as done ("FTBFS on arm*")
Your message dated Sat, 15 Oct 2016 20:01:48 +0300 with message-id <20161015170148.mayjgwbnrogjv...@bunk.spdns.de> and subject line This seems to be already fixed has caused the Debian Bug report #671469, regarding "FTBFS on arm*" 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.) -- 671469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org X-DebBugs-CC: Anton Gladky , debian-science-maintain...@lists.debian.org Greetings, Please remove all of the OCE shared libraries with library version 1, such as liboce-foundation1 (i.e. upstream version 0.8.0). It seems they are blocking the transition to 0.9.1, which is built on all platforms. There is no transition page on http://release.debian.org/transitions/html/ , 0.9.1 is now 44 days old, and all reverse-depends have built successfully, so I believe this removal is the only thing standing in the way of a transition. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 6.1.0.svn.5396.dfsg-5.2 Version 6.1.0.svn.5396.dfsg-5.2 did build successfully on armel, I assume this issue was somehow resolved back then. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: Re: openscenegraph-3.4: FTBFS (internal compiler error: Segmentation fault)
Processing commands for cont...@bugs.debian.org: > notfound 840834 openscenegraph-3.4/3.4.0+dfsg1-4 Bug #840834 [src:openscenegraph-3.4] openscenegraph-3.4: FTBFS (internal compiler error: Segmentation fault) No longer marked as found in versions openscenegraph-3.4/3.4.0+dfsg1-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 840834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840788: vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev
On Sat, 15 Oct 2016 13:36:31 +0200 Andreas Beckmann wrote: > On Fri, 14 Oct 2016 23:44:15 +0200 Bas Couwenberg > wrote: > > Please change the libmysqlclient-dev build dependency to > > default-libmysqlclient-dev. The vtk6 build dependencies are > > no longer installable now that libgdal-dev depends on > > default-libmysqlclient-dev which is not co-installable with > > libmysqlclient-dev. > > There is also a dependency libvtk6-dev -> libmysqlclient-dev which > renders the package uninstallable in sid. Yes, and my patch [0] changes both to default-libmysqlclient-dev. Kind Regards, Bas [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=840788;filename=vtk6_6.3.0%2Bdfsg1-1_default-libmysqlclient-dev.patch;msg=5
Bug#840756: marked as done (node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked)
Your message dated Sat, 15 Oct 2016 17:28:01 + with message-id and subject line Bug#840756: fixed in node-lex-parser 0.1.4-2 has caused the Debian Bug report #840756, regarding node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked 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.) -- 840756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-lex-parser Version: 0.1.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automatic builds of node-lex-parser all failed with either npm ERR! Error: Attempt to unlock jison@0.4.x, which hasn't been locked npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11) npm ERR! at cb (/usr/share/npm/lib/cache/add-named.js:32:5) npm ERR! at /usr/share/npm/lib/cache/add-named.js:41:20 npm ERR! at /usr/share/npm/lib/utils/locker.js:22:20 npm ERR! at /usr/share/npm/node_modules/inflight/inflight.js:22:7 npm ERR! at Array.forEach (native) npm ERR! at res (/usr/share/npm/node_modules/inflight/inflight.js:21:9) npm ERR! at /usr/lib/nodejs/once.js:17:15 npm ERR! at afterMkdir (/usr/share/npm/lib/cache/get-stat.js:53:14) npm ERR! at /usr/lib/nodejs/mkdirp/index.js:34:29 or npm ERR! Error: Attempt to unlock test@*, which hasn't been locked npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11) [...] depending on the architecture. For whatever reason, the problem was with jison@0.4.x on arm64, armhf, mips, powerpc, ppc64el, s390x, and the non-release architecture kfreebsd-amd64, and test@* on i386, mips64el, mipsel, and the non-release architecture kfreebsd-i386. Could you please take a look? Thanks! FTR, I'm classifying this bug as a regression even though node-lex-parser is new because I strongly suspect it would also affect binNMUs on amd64. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: node-lex-parser Source-Version: 0.1.4-2 We believe that the bug you reported is fixed in the latest version of node-lex-parser, 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 840...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-lex-parser 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: Sat, 15 Oct 2016 22:27:07 +0530 Source: node-lex-parser Binary: node-lex-parser Architecture: source amd64 Version: 0.1.4-2 Distribution: unstable Urgency: medium Maintainer: Pirate Praveen Changed-By: Pirate Praveen Description: node-lex-parser - parser for lexical grammars used by jison and jison-lex Closes: 840756 Changes: node-lex-parser (0.1.4-2) unstable; urgency=medium . * Use system jison (Closes: #840756) Checksums-Sha1: e9e8519fbe3a1c80f1e395f8fb1aef5bb6213acf 1925 node-lex-parser_0.1.4-2.dsc f777d6c065ed60b3024f2fca4be541c03944f92d 2260 node-lex-parser_0.1.4-2.debian.tar.xz 4393f85ac2428f76c641774bf641f3bfd13b9183 11646 node-lex-parser_0.1.4-2_amd64.deb Checksums-Sha256: bb468e7e13b63361cefbfb0fd959c95fc97287cad3dd7e608dc6b2e38ee50156 1925 node-lex-parser_0.1.4-2.dsc 1b9f175f54f707c2422f3d817b1527eecd02a999f4ab71222853264dfb50b86c 2260 node-lex-parser_0.1.4-2.debian.tar.xz 1e0446d6e89837b2014df035abf554d7525069d132edf535171544bb9753b485 11646 node-lex-parser_0.1.4-2_amd64.deb Files: 2ea80f34642390e1e72e5c721ba387ec 1925 web optional node-lex-parser_0.1.4-2.dsc 406b33c96b5cbe2b6cfd59cfcf8a46a3 2260 web optional node-lex-parser_0.1.4-2.debian.tar.xz 622b8406436a77095ce068ea79e67174 11646 web optional node-lex-parser_0.1.4-2_amd64.deb -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYAmB5AAoJEM4fnGdFEsIqs1UP/0kzVI2Qjd2x0muM/HzQleWa trD7d//Ga5fcBxMO3vN0jJedwdiupbHQ6CSBuZa03fi1RkiwatAPmrj7yIz+0n7L BJ3us6Oo/b+KA8fdhVrccOEK+mssI12iZjdsmOxixK9BFd+cxmbkq6PPc/rPOL3o uAy//tALIWMMCbtTUGi/D2vt/XSKlgTj9l6mnfJj0sKrKcgM5dusXTzuL/RfjFEO Vxo47OeyKdHPoXzfDe9bTdsONE3cNwUYfWmh0
Bug#840760: marked as done (node-livescript: FTBFS (npm: Command not found))
Your message dated Sat, 15 Oct 2016 17:28:08 + with message-id and subject line Bug#840760: fixed in node-livescript 1.5.0+dfsg-2 has caused the Debian Bug report #840760, regarding node-livescript: FTBFS (npm: Command not found) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 840760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-livescript Version: 1.5.0+dfsg-1 Severity: serious Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep dh_testdir -i dh_update_autotools_config -i dh_auto_configure -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>/node-livescript-1.5.0+dfsg' npm install jison make[1]: npm: Command not found debian/rules:11: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 127 make[1]: Leaving directory '/<>/node-livescript-1.5.0+dfsg' debian/rules:8: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 The relevant part of the build log is included above. It is strongly recommended that packages are built in a clean sid chroot to ensure that they are buildable (i.e. no missing build-dependencies). Thanks. --- End Message --- --- Begin Message --- Source: node-livescript Source-Version: 1.5.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of node-livescript, 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 840...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-livescript 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: Sat, 15 Oct 2016 22:32:20 +0530 Source: node-livescript Binary: livescript Architecture: source all Version: 1.5.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Description: livescript - language which compiles to JavaScript Closes: 840760 Changes: node-livescript (1.5.0+dfsg-2) unstable; urgency=medium . * Use jison package, drop npm (Closes: #840760) Checksums-Sha1: cb8010c85d26528189a5edbc3c9314aa41ee2cf6 2045 node-livescript_1.5.0+dfsg-2.dsc c35016c144bf4a9d218b182491d6467f24c2573e 3028 node-livescript_1.5.0+dfsg-2.debian.tar.xz e1707bd3350d2f35ef0ca64fdda8ee94f96d8615 69630 livescript_1.5.0+dfsg-2_all.deb Checksums-Sha256: 01250f469ff824de27a9f11fbaada154d9a2c0554a922585c91c213630cacc83 2045 node-livescript_1.5.0+dfsg-2.dsc c1c860766e6e396d1a176a02c5ce819938e2daa335857960aea2b001c0f06798 3028 node-livescript_1.5.0+dfsg-2.debian.tar.xz ac7b1019e1b0edd9edc2f951babae8ca156a9c5c058a01e5b4b37307d67c4258 69630 livescript_1.5.0+dfsg-2_all.deb Files: 336c6109f4952d7990deb579bcf22fea 2045 web optional node-livescript_1.5.0+dfsg-2.dsc 8f5713ee6f9106fbd8bce9c285ff817b 3028 web optional node-livescript_1.5.0+dfsg-2.debian.tar.xz 3d12c426c1019760832aa5a9de0edafd 69630 web optional livescript_1.5.0+dfsg-2_all.deb -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYAmKcAAoJEM4fnGdFEsIqoFUP/iRD2wW4UBIdZp+6njBCnbPZ tlCj9S4Zfvsyf53JpYIVY46W7wzKK2BZxVNPLvDJk+ZRKG166CosR0EekKo/AU4J zZQCi9g2u6YKX9Nt6pZWYenYpUwwlNyyYITGeZrgfCcssg5Ly561iyc++kyHBeYJ 29Wc8Ln4dg0AproU1ij7NTbWT4QsyQCarJiEuN45cQlpmkMK90J04jLqiD+/AA/h A0/wDGSj5fwn5wjZ5IY1yheORz1oPSsnUc5c6iHYbjQChcXPfud/yY53P3OvyL7e dM7MiykI8HDoA6FujPCqx+//uxS6wRVlxs7/awav3I3SwZGLThx4SDRwX1gd+S8/ EdODCEpA4czf/Vmuq6jLzctpkzUji6UlBxQlwpTl0LpbQYb5xGTIaHxc/XPCUZ3q CK1j6lG8GAWJt2nexigHns68UxQR/4Ls+KGTHnYDsagyLU3NK+RUrvICSd3CQ3OQ /7RIKYDbljCdCipMyH6zFRovkkQyAABK/os6vq/wZchVPhJ4cN4JLcJ0J9Bf7Gqo +bdS83sKAGR3YViFUF0tKSfxUDxMeHsnLSbVvD5Mv0+66w4aHECRHass0IMHEy8p pWOWJb5DIoTGwPD+AQw8mpgvXhu+/rdw0H02Vzt7WczpGYNFkXwGH1cLUHxIypMd r4LNOXT++Q
Bug#840725: Bug#840840: pocl: Does not build on several architectures
On Sat, Oct 15, 2016 at 04:27:45PM +0200, Andreas Beckmann wrote: > On 2016-10-15 16:09, Andreas Tille wrote: > > > >https://buildd.debian.org/status/package.php?p=pocl > > Right, pocl FTBFS everywhere except linux-i386/amd64, and always has > (with maybe some spurious successes when tests were not being run). > Everything outdated on the release architectures has been decrufted. > > Or did you want to file a *wishlist* bug to support more architectures? > FTBFS on an architecture where it has not been built before (i.e. no > outdated binary packages in the archive that would prevent testing > migration) is not RC. Well, the thing is that bug #840725 of libhmsbeagle was reopened[1] because libpoclu-dev is not available on most architectures. Since libhmsbeagle has build on all those architectures either the set of Build-Depends has changed (may be together with khronos-opencl-clhpp?) or there was a point in time when pocl has build on more architectures than currently. So if the fact remains that pocl does not build anywhere else than on intel I need to restrict the set of architectures for libhmsbeagle as well. Kind regards Andreas. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840725;msg=22 -- http://fam-tille.de
Processed: retitle 840805 to libgd2: CVE-2016-8670: Stack Buffer Overflow in GD dynamicGetbuf
Processing commands for cont...@bugs.debian.org: > retitle 840805 libgd2: CVE-2016-8670: Stack Buffer Overflow in GD > dynamicGetbuf Bug #840805 [src:libgd2] libgd2: Stack Buffer Overflow in GD dynamicGetbuf Changed Bug title to 'libgd2: CVE-2016-8670: Stack Buffer Overflow in GD dynamicGetbuf' from 'libgd2: Stack Buffer Overflow in GD dynamicGetbuf'. > thanks Stopping processing here. Please contact me if you need assistance. -- 840805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840840: pocl: Does not build on several architectures
On 2016-10-15 19:57, Andreas Tille wrote: > because libpoclu-dev is not available on most architectures. Since > libhmsbeagle has build on all those architectures either the set of > Build-Depends has changed (may be together with khronos-opencl-clhpp?) > or there was a point in time when pocl has build on more architectures > than currently. The outdated libhmsbeagle binary packages are from 2.1.2+20150609-1.1, predating the use of libpoclu-dev (since 2.1.2+20151220-1). So libhmsbeagle never built successfully with libpoclu-dev on more architectures than currently (i.e. only on amd64). While theoretically pocl could be available on all architectures (that support CPUs), that doesn't work right now and I don't know if anyone is working on fixing this. > So if the fact remains that pocl does not build anywhere else than on > intel I need to restrict the set of architectures for libhmsbeagle as > well. Or just restrict the use of OpenCL to the architectures that have pocl? Andreas
Bug#835336: Pending fixes for bugs in the influxdb package
tag 835336 + pending thanks Some bugs in the influxdb package are closed in revision f1edbb720ccf16d7ce2e028657b1382689a1fedd in branch 'master' by aviau The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/influxdb.git/commit/?id=f1edbb7 Commit message: Remove existing static files (Closes: #835336)
Processed: Pending fixes for bugs in the influxdb package
Processing commands for cont...@bugs.debian.org: > tag 835336 + pending Bug #835336 [src:influxdb] influxdb: FTBFS in testing (go generate returned exit code 1) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 835336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#835336: marked as done (influxdb: FTBFS in testing (go generate returned exit code 1))
Your message dated Sat, 15 Oct 2016 18:54:12 + with message-id and subject line Bug#835336: fixed in influxdb 0.13.0+dfsg1-5 has caused the Debian Bug report #835336, regarding influxdb: FTBFS in testing (go generate returned exit code 1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 835336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:influxdb Version: 0.13.0+dfsg1-4 Severity: serious Dear maintainer: I tried to build this package on stretch with dpkg-buildpackage -A and sbuild and it failed with an error like this: -- go generate -v -ldflags=-X main.version=0.13.0 github.com/[...] [ very long list, see attach for details] returned exit code 1 -- I attach five different build logs on two different virtual machines. The builds were made on a virtual machine having either 6GB or 3GB of RAM, and 4GB of swap. I was able to build version 0.10.2+dfsg1-2 without problems. Thanks. influxdb_0.13.0+dfsg1-4_amd64-20160803T1310Z.gz Description: application/gzip influxdb_0.13.0+dfsg1-4_amd64-20160814T1213Z.gz Description: application/gzip influxdb_0.13.0+dfsg1-4_amd64-20160824T090803Z.gz Description: application/gzip influxdb_0.13.0+dfsg1-4_amd64-20160824T104824Z.gz Description: application/gzip influxdb_0.13.0+dfsg1-4_amd64-20160824T104832Z.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: influxdb Source-Version: 0.13.0+dfsg1-5 We believe that the bug you reported is fixed in the latest version of influxdb, 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 835...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Viau (supplier of updated influxdb 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, 15 Oct 2016 14:12:16 -0400 Source: influxdb Binary: golang-github-influxdb-influxdb-dev influxdb-dev influxdb influxdb-client Architecture: source all amd64 Version: 0.13.0+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Alexandre Viau Description: golang-github-influxdb-influxdb-dev - Scalable datastore for metrics, events, and real-time analytics. influxdb - Scalable datastore for metrics, events, and real-time analytics influxdb-client - command line interface for InfluxDB influxdb-dev - Transitional package for golang-github-influxdb-influxdb-dev Closes: 835336 840636 Changes: influxdb (0.13.0+dfsg1-5) unstable; urgency=medium . [ Alexandre Viau ] * Prepare upload * d/control: Add InfluxDB dependency on lsb-base (>= 3.0-6) * Remove unused hardening-no-relro override . [ Guillem Jover ] * Remove existing static files (Closes: #835336) * Improve and fix init script (Closes: #840636) . [ Tim Potter ] * Update influxdb-usage-client B-D to use backports Checksums-Sha1: f8f7c64aec0eb22a6183bdbede8cc196782a2450 3338 influxdb_0.13.0+dfsg1-5.dsc a0a521b062f29488d72e628e6f95c69aa01a91d4 120368 influxdb_0.13.0+dfsg1-5.debian.tar.xz b2c802149e3aea73c3ddf5181f401d6886477396 752358 golang-github-influxdb-influxdb-dev_0.13.0+dfsg1-5_all.deb 80a844247396ce3032e2e7cad8b5e3b1956f8209 1178060 influxdb-client_0.13.0+dfsg1-5_amd64.deb cd99eba09c82c0d197fd805ffb863f54b4f24970 43664 influxdb-dev_0.13.0+dfsg1-5_all.deb fe82e802b0ceade1fdb693b7e9e550f9d272a04c 2732742 influxdb_0.13.0+dfsg1-5_amd64.deb Checksums-Sha256: 288ebbd6faa1abfb493337fd11f04e6d779e8a1e4351b1fb877d767b81cbadf8 3338 influxdb_0.13.0+dfsg1-5.dsc f24eef5cb035e2cb02935a10d9f0e7cf949b8d6f6a1aa4dd61ac653d1c6998a8 120368 influxdb_0.13.0+dfsg1-5.debian.tar.xz 21d9c002f8157e90844b82019165929a7113f1a46c92db94a6445edc62a8f268 752358 golang-github-influxdb-influxdb-dev_0.13.0+dfsg1-5_all.deb c2ad35b1f79a67de58f0b7bc7c478434b482b357ff14e6dc6dcbe07ae0fd6594 1178060 influxdb-client_0.13.0+dfsg1-5_amd64.deb a3838bcd1b241f07ca95b9e1d272b2de9af0042722df392ce33b36b280ddab6a 43664 influxdb-dev_0.13.0+dfsg1-5_
Processed: Bug#835241 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 835241 pending Bug #835241 [src:pytest-mock] pytest-mock: FTBFS against pytest 3.0.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 835241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#835241: marked as pending
tag 835241 pending thanks Hello, Bug #835241 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/pytest-mock.git;a=commitdiff;h=f3e6ab3 --- commit f3e6ab3d77a427bf97e5fdcf11fdd1aa525439e9 Author: Vincent Bernat Date: Sat Sep 3 12:32:16 2016 +0200 New upstream release diff --git a/debian/changelog b/debian/changelog index 9e742d0..b4f4f0d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +pytest-mock (1.2-1) UNRELEASED; urgency=medium + + * New upstream release. ++ Still no support of pytest 3. Not closes: #835241. + + -- Vincent Bernat Sat, 03 Sep 2016 12:31:59 +0200 + pytest-mock (1.1-1) unstable; urgency=medium [ Vincent Bernat ]
Bug#835241: marked as done (pytest-mock: FTBFS against pytest 3.0.0)
Your message dated Sat, 15 Oct 2016 19:24:15 + with message-id and subject line Bug#835241: fixed in pytest-mock 1.2-1 has caused the Debian Bug report #835241, regarding pytest-mock: FTBFS against pytest 3.0.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 835241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-mock Version: 1.1-1 Severity: important Tags: sid stretch Usertags: pytest3.0.0 During a test build against pytest 3.0.0 from experimental pytest-mock failed to build: | PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x" dh_auto_test | I: pybuild base:184: python2.7 -m pytest -v -x | = test session starts == | platform linux2 -- Python 2.7.12+, pytest-3.0.0, py-1.4.31, pluggy-0.3.1 -- /usr/bin/python2.7 | cachedir: .cache | rootdir: /<>, inifile: | plugins: mock-1.1 | collecting ... collected 39 items | | test_pytest_mock.py::test_mock_patches[mock_fs0] PASSED | test_pytest_mock.py::test_mock_patches[mock_fs1] PASSED | test_pytest_mock.py::test_mock_patches[mock_fs2] PASSED | test_pytest_mock.py::test_mock_patch_dict PASSED | test_pytest_mock.py::test_mock_fixture_is_deprecated PASSED | test_pytest_mock.py::test_deprecated_mock PASSED | test_pytest_mock.py::test_mocker_aliases[MagicMock] PASSED | test_pytest_mock.py::test_mocker_aliases[PropertyMock] PASSED | test_pytest_mock.py::test_mocker_aliases[Mock] PASSED | test_pytest_mock.py::test_mocker_aliases[call] PASSED | test_pytest_mock.py::test_mocker_aliases[ANY] PASSED | test_pytest_mock.py::test_mocker_resetall PASSED | test_pytest_mock.py::TestMockerStub::test_call PASSED | test_pytest_mock.py::TestMockerStub::test_repr_with_no_name PASSED | test_pytest_mock.py::TestMockerStub::test_repr_with_name PASSED | test_pytest_mock.py::TestMockerStub::test_failure_message_with_no_name FAILED | | === FAILURES === | ___ TestMockerStub.test_failure_message_with_no_name ___ | | self = | mocker = | | def test_failure_message_with_no_name(self, mocker): | > self.__test_failure_message(mocker) | | test_pytest_mock.py:182: | _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ | | self = | mocker = , kwargs = {} | expected_name = 'mock', expected_message = 'Expected call: mock()\nNot called' | stub = | exc_info = | @py_assert1 = AssertionError('Expected call: mock()\nNot called',) | | def __test_failure_message(self, mocker, **kwargs): | expected_name = kwargs.get('name') or 'mock' | expected_message = 'Expected call: {0}()\nNot called'.format(expected_name) | stub = mocker.stub(**kwargs) | with pytest.raises(AssertionError) as exc_info: | stub.assert_called_with() | > assert exc_info.value.msg == expected_message | E AttributeError: 'exceptions.AssertionError' object has no attribute 'msg' | | test_pytest_mock.py:179: AttributeError | Interrupted: stopping after 1 failures | = 1 failed, 15 passed in 0.25 seconds == | E: pybuild pybuild:276: test: plugin custom failed with: exit code=2: python2.7 -m pytest -v -x For a full build log see https://people.debian.org/~sramacher/logs/pytest3.0.0/pytest-mock_amd64.log. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: pytest-mock Source-Version: 1.2-1 We believe that the bug you reported is fixed in the latest version of pytest-mock, 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 835...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Bernat (supplier of updated pytest-mock 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: Sat, 15 Oct 2016 20:58:02 +0200 Source: pytest-mock Binary: python-pytest-mock python3-pytest-mock Architecture: source all Version: 1.2-1 Distribution: unstable Urgency:
Bug#840725: Bug#840840: pocl: Does not build on several architectures
On Sat, Oct 15, 2016 at 08:39:08PM +0200, Andreas Beckmann wrote: > On 2016-10-15 19:57, Andreas Tille wrote: > > because libpoclu-dev is not available on most architectures. Since > > libhmsbeagle has build on all those architectures either the set of > > Build-Depends has changed (may be together with khronos-opencl-clhpp?) > > or there was a point in time when pocl has build on more architectures > > than currently. > > The outdated libhmsbeagle binary packages are from 2.1.2+20150609-1.1, > predating the use of libpoclu-dev (since 2.1.2+20151220-1). > So libhmsbeagle never built successfully with libpoclu-dev on more > architectures than currently (i.e. only on amd64). > > While theoretically pocl could be available on all architectures (that > support CPUs), that doesn't work right now and I don't know if anyone is > working on fixing this. > > > So if the fact remains that pocl does not build anywhere else than on > > intel I need to restrict the set of architectures for libhmsbeagle as > > well. > > Or just restrict the use of OpenCL to the architectures that have pocl? > > Andreas > -- http://fam-tille.de
Bug#840725: Bug#840840: pocl: Does not build on several architectures
On Sat, Oct 15, 2016 at 08:39:08PM +0200, Andreas Beckmann wrote: > > So if the fact remains that pocl does not build anywhere else than on > > intel I need to restrict the set of architectures for libhmsbeagle as > > well. > > Or just restrict the use of OpenCL to the architectures that have pocl? I'd like to do that - but how? I have no idea about all these things. Any hint? Kind regards Andreas. -- http://fam-tille.de
Bug#811560: marked as done (elasticache: FTBFS with nonexistant $HOME)
Your message dated Sat, 15 Oct 2016 23:39:58 +0300 with message-id <20161015203958.pmfke2rsnfsly...@bunk.spdns.de> and subject line elasticache has been removed from unstable has caused the Debian Bug report #811560, regarding elasticache: FTBFS with nonexistant $HOME 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.) -- 811560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: elasticache Version: 1.6.00-1 Severity: serious Justification: fails to build from source Current pbuilder changed the build environment to use a nonexistant $HOME directory. Neither the build process nor the build tools should have to access $HOME during the build. Also the (non-)existence of something in $HOME must not influence the build process. elasticache FTBFS in such a setup since it tries to 'cd' (with no args) to the $HOME: [...] I: Running cd /build/*/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us -uc -rfakeroot dpkg-buildpackage: source package elasticache dpkg-buildpackage: source version 1.6.00-1 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Ben Howard dpkg-source --before-build elasticache-1.6.00 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh clean --with_python2 dh_testdir -O--with_python2 dh_auto_clean -O--with_python2 make -j1 clean make[1]: Entering directory '/build/elasticache-1.6.00' Makefile:77: warning: overriding recipe for target 'build' Makefile:42: warning: ignoring old recipe for target 'build' cd /bin/sh: 1: cd: can't cd to /nonexistent Makefile:80: recipe for target 'clean' failed make[1]: *** [clean] Error 2 make[1]: Leaving directory '/build/elasticache-1.6.00' dh_auto_clean: make -j1 clean returned exit code 2 debian/rules:5: recipe for target 'clean' failed make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Andreas --- End Message --- --- Begin Message --- elasticache has been removed from unstable (#820695). cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#817689: marked as done (tendra-doc: Removal of debhelper compat 4)
Your message dated Sat, 15 Oct 2016 23:52:11 +0300 with message-id <20161015205211.3xftpytykio2y...@bunk.spdns.de> and subject line tendra-doc has been removed from unstable has caused the Debian Bug report #817689, regarding tendra-doc: Removal of debhelper compat 4 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.) -- 817689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tendra-doc Severity: important Usertags: compat-4-removal Hi, The package tendra-doc uses debhelper with a compat level of 4, which is deprecated and scheduled for removal. * Please bump the debhelper compat at your earliest convenience. on the 15th of June. - Compat 9 is recommended - Compat 5 is the bare minimum - If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Compat level 4 will be removed on the first debhelper upload after the 15th of June. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html --- End Message --- --- Begin Message --- tendra-doc has been removed from unstable (#831695). cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: Version tracking fixes
Processing commands for cont...@bugs.debian.org: > found 804272 1.13.0-2 Bug #804272 [akonadi-server] fails to synchronize caldav to OpenXChange without notice Marked as found in versions akonadi/1.13.0-2. > found 811974 2.2.0-1 Bug #811974 [tinyxml2] tinyxml2: FTBFS with GCC 6: symbol changes There is no source info for the package 'tinyxml2' at version '2.2.0-1' with architecture '' Unable to make a source version for version '2.2.0-1' Marked as found in versions 2.2.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 804272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804272 811974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#811974: marked as done (tinyxml2: FTBFS with GCC 6: symbol changes)
Your message dated Sun, 16 Oct 2016 00:07:10 +0300 with message-id <20161015210710.3rlnknru74kgp...@bunk.spdns.de> and subject line This bug has already been fixed has caused the Debian Bug report #811974, regarding tinyxml2: FTBFS with GCC 6: symbol changes 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.) -- 811974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tinyxml2 Version: 2.2.0-1.1 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-symbols This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in experimental. To build with GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly. You may be able to find out more about this issue at https://gcc.gnu.org/gcc-6/changes.html > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libtinyxml2-2/DEBIAN/symbols doesn't match > completely debian/libtinyxml2-2.symbols > --- debian/libtinyxml2-2.symbols (libtinyxml2-2_2.2.0-1.1_amd64) > +++ dpkg-gensymbolsfNDA_y 2016-01-19 14:51:13.415938052 + > @@ -157,15 +157,15 @@ > (c++)"tinyxml2::XMLUnknown::ToUnknown()@Base" 2.0.2 > (c++)"tinyxml2::XMLUnknown::XMLUnknown(tinyxml2::XMLDocument*)@Base" 2.0.2 > (c++)"tinyxml2::XMLUnknown::~XMLUnknown()@Base" 2.0.2 > - (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLComment const&)@Base" 2.0.2 > - (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLDeclaration const&)@Base" > 2.0.2 > - (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLText const&)@Base" 2.0.2 > - (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLUnknown const&)@Base" 2.0.2 > - (c++)"tinyxml2::XMLVisitor::VisitEnter(tinyxml2::XMLDocument const&)@Base" > 2.0.2 > - (c++)"tinyxml2::XMLVisitor::VisitEnter(tinyxml2::XMLElement const&, > tinyxml2::XMLAttribute const*)@Base" 2.0.2 > - (c++)"tinyxml2::XMLVisitor::VisitExit(tinyxml2::XMLDocument const&)@Base" > 2.0.2 > - (c++)"tinyxml2::XMLVisitor::VisitExit(tinyxml2::XMLElement const&)@Base" > 2.0.2 > - (c++)"tinyxml2::XMLVisitor::~XMLVisitor()@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLComment > const&)@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# > (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLDeclaration const&)@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLText > const&)@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# (c++)"tinyxml2::XMLVisitor::Visit(tinyxml2::XMLUnknown > const&)@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# > (c++)"tinyxml2::XMLVisitor::VisitEnter(tinyxml2::XMLDocument const&)@Base" > 2.0.2 > +#MISSING: 2.2.0-1.1# > (c++)"tinyxml2::XMLVisitor::VisitEnter(tinyxml2::XMLElement const&, > tinyxml2::XMLAttribute const*)@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# > (c++)"tinyxml2::XMLVisitor::VisitExit(tinyxml2::XMLDocument const&)@Base" > 2.0.2 > +#MISSING: 2.2.0-1.1# > (c++)"tinyxml2::XMLVisitor::VisitExit(tinyxml2::XMLElement const&)@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# (c++)"tinyxml2::XMLVisitor::~XMLVisitor()@Base" 2.0.2 > (c++)"typeinfo for tinyxml2::XMLAttribute@Base" 2.0.2 > (c++)"typeinfo for tinyxml2::XMLComment@Base" 2.0.2 > (c++)"typeinfo for tinyxml2::XMLDeclaration@Base" 2.0.2 > @@ -195,4 +195,4 @@ > (c++)"vtable for tinyxml2::XMLPrinter@Base" 2.0.2 > (c++)"vtable for tinyxml2::XMLText@Base" 2.0.2 > (c++)"vtable for tinyxml2::XMLUnknown@Base" 2.0.2 > - (c++|optional)"vtable for tinyxml2::XMLVisitor@Base" 2.0.2 > +#MISSING: 2.2.0-1.1# (c++|optional)"vtable for tinyxml2::XMLVisitor@Base" > 2.0.2 > dh_makeshlibs: failing due to earlier errors > debian/rules:21: recipe for target 'override_dh_makeshlibs' failed > make[1]: *** [override_dh_makeshlibs] Error 25 -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise --- End Message --- --- Begin Message --- Version: 4.0.1-1 This bug has already been fixed in unstable. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: Re: Bug#840610: UnicodeEncodeError: 'ascii' codec can't encode character
Processing commands for cont...@bugs.debian.org: > reassign 840610 python3 3.5.1-4 Bug #840610 [apt-listchanges] UnicodeEncodeError: 'ascii' codec can't encode character Bug reassigned from package 'apt-listchanges' to 'python3'. No longer marked as found in versions apt-listchanges/3.5. Ignoring request to alter fixed versions of bug #840610 to the same values previously set Bug #840610 [python3] UnicodeEncodeError: 'ascii' codec can't encode character Marked as found in versions python3-defaults/3.5.1-4. > retitle 840610 python inconsistently handles the LANGUAGE env var Bug #840610 [python3] UnicodeEncodeError: 'ascii' codec can't encode character Changed Bug title to 'python inconsistently handles the LANGUAGE env var' from 'UnicodeEncodeError: 'ascii' codec can't encode character'. > severity 840610 serious Bug #840610 [python3] python inconsistently handles the LANGUAGE env var Severity set to 'serious' from 'normal' > affects 840610 apt-listchanges Bug #840610 [python3] python inconsistently handles the LANGUAGE env var Added indication that 840610 affects apt-listchanges > thanks Stopping processing here. Please contact me if you need assistance. -- 840610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840900: zorp: FTBFS (vector: No such file or directory)
Package: src:zorp Version: 3.9.5-7.1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --with autoreconf,python2 --parallel dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_testdir -i -O--parallel dh_update_autotools_config -i -O--parallel dh_autoreconf -i -O--parallel libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:130: installing './compile' configure.ac:134: installing './config.guess' [... snipped ...] /usr/include/zorp/zorplibconfig.h:176:0: note: this is the location of the previous definition #define PACKAGE_STRING "" In file included from /<>/lib/zorp/zorp.h:44:0, from http.h:30, from http.c:33: /<>/lib/zorp/zorpconfig.h:110:0: warning: "PACKAGE_TARNAME" redefined #define PACKAGE_TARNAME "zorp" In file included from /usr/include/zorp/zorplib.h:23:0, from /usr/include/zorp/misc.h:13, from /<>/lib/zorp/zorp.h:41, from http.h:30, from http.c:33: /usr/include/zorp/zorplibconfig.h:179:0: note: this is the location of the previous definition #define PACKAGE_TARNAME "" In file included from /<>/lib/zorp/zorp.h:44:0, from http.h:30, from http.c:33: /<>/lib/zorp/zorpconfig.h:116:0: warning: "PACKAGE_VERSION" redefined #define PACKAGE_VERSION "3.9.5" In file included from /usr/include/zorp/zorplib.h:23:0, from /usr/include/zorp/misc.h:13, from /<>/lib/zorp/zorp.h:41, from http.h:30, from http.c:33: /usr/include/zorp/zorplibconfig.h:185:0: note: this is the location of the previous definition #define PACKAGE_VERSION "" In file included from http.c:45:0: /usr/include/zorp/random.h:13:18: fatal error: vector: No such file or directory #include ^ compilation terminated. Makefile:519: recipe for target 'http.lo' failed make[4]: *** [http.lo] Error 1 make[4]: Leaving directory '/<>/modules/http' Makefile:555: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/<>/modules/http' Makefile:393: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/<>/modules' Makefile:507: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 debian/rules:3: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 The relevant part of the build log is included above. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. Thanks.
Bug#840610: UnicodeEncodeError: 'ascii' codec can't encode character
Robert Luberda writes: > According to GNU gettext documentation[1]: "The variable LANGUAGE is > ignored if the locale is set to ‘C’." That exception was added on 2001-01-03, for glibc 2.2.1. In glibc 2.2, LANGUAGE used to override LC_ALL=C. In Python 2.0 (released on 2000-10-16), 2.7, and 3.5.0, gettext.py checks LANGUAGE first, like glibc 2.2. The loop that checks the environment variables is exactly the same in these three versions. I searched for "gettext" at bugs.python.org but it didn't find a bug report for the priority of LANGUAGE vs. LC_ALL=C in gettext. http://bugs.python.org/issue1166948 says 'LANGUAGE is honoured even if the default locale is "C"' but I think that refers to locale.getdefaultencoding, not to gettext.
Bug#840788: marked as done (vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev)
Your message dated Sat, 15 Oct 2016 22:47:10 + with message-id and subject line Bug#840788: fixed in vtk6 6.3.0+dfsg1-2 has caused the Debian Bug report #840788, regarding vtk6: Change libmysqlclient-dev build dependency to default-libmysqlclient-dev 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.) -- 840788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vtk6 Version: 6.3.0+dfsg1-1 Severity: important Tags: patch Dear Maintainer, Please change the libmysqlclient-dev build dependency to default-libmysqlclient-dev. The vtk6 build dependencies are no longer installable now that libgdal-dev depends on default-libmysqlclient-dev which is not co-installable with libmysqlclient-dev. Kind Regards, Bas --- debian/control.orig 2016-10-14 23:43:19.302315770 +0200 +++ debian/control 2016-10-14 23:40:54.050969558 +0200 @@ -30,7 +30,7 @@ libjpeg-dev, libjsoncpp-dev, libmrmpi-dev, - libmysqlclient-dev, + default-libmysqlclient-dev, libnetcdf-dev, libnetcdf-cxx-legacy-dev, libogg-dev, @@ -98,7 +98,7 @@ libhdf5-mpi-dev, libjpeg-dev, libjsoncpp-dev, - libmysqlclient-dev, + default-libmysqlclient-dev, libnetcdf-dev, libnetcdf-cxx-legacy-dev, libogg-dev, --- End Message --- --- Begin Message --- Source: vtk6 Source-Version: 6.3.0+dfsg1-2 We believe that the bug you reported is fixed in the latest version of vtk6, 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 840...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gert Wollny (supplier of updated vtk6 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: Sat, 15 Oct 2016 16:52:43 + Source: vtk6 Binary: libvtk6-dev libvtk6-qt-dev libvtk6.3 libvtk6.3-qt libvtk6-jni libvtk6-java python-vtk6 tcl-vtk6 vtk6 vtk6-doc vtk6-examples Architecture: source Version: 6.3.0+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Gert Wollny Description: libvtk6-dev - VTK header files libvtk6-java - Visualization Toolkit - A high level 3D visualization library - j libvtk6-jni - Visualization Toolkit - A high level 3D visualization library - j libvtk6-qt-dev - VTK header files, containing Qt files libvtk6.3 - VTK libraries libvtk6.3-qt - VTK libraries, Qt files python-vtk6 - Python bindings for VTK tcl-vtk6 - Tcl bindings for VTK vtk6 - Binaries for VTK6 vtk6-doc - VTK class reference documentation vtk6-examples - VTK examples Closes: 840788 Changes: vtk6 (6.3.0+dfsg1-2) unstable; urgency=medium . * [4f0b4c6] d/control: Update dependencies on mysqlclient-dev, Closes: #840788 Checksums-Sha1: 87895cfd534f30a12398e08f997ae6ee8776d2b6 3278 vtk6_6.3.0+dfsg1-2.dsc 95830a0601a83687ae053a856cdc6b5304b77f6d 28944 vtk6_6.3.0+dfsg1-2.debian.tar.xz Checksums-Sha256: 50bbdbe9ef9b3f57853b40149f4700fb4fc5c051a9a44144df7b7c47d767a679 3278 vtk6_6.3.0+dfsg1-2.dsc 2764bb1e87ab0ad17caa25b9e7a04d26691dacad7317bbec43dd475cd03dae14 28944 vtk6_6.3.0+dfsg1-2.debian.tar.xz Files: 73cea24c5d04a46ba4a97843f46ddb20 3278 graphics optional vtk6_6.3.0+dfsg1-2.dsc 465e40f259cd709dea70fbdf82218e8e 28944 graphics optional vtk6_6.3.0+dfsg1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQEcBAEBCAAGBQJYAoAyAAoJEPgeNoubJquYxdYIALyop0+K9hVwKWsMS2VUnIgk M2dy+78jUOhdjHuvvgeUo2G9TBmNk8Wd72Wk7K2iHt0tBemsQVGLDkHWKopfsHyV GTG3+1iwzKIJuuDzIbDkpeQZD9/gvf5M64lYxP9JO1BjQgFqEwo889/aTqX99j5A Ni2ZgvGgY46RSj/gTBLhKN4q6Y8YZBAZh0+LtPouud89poGyqNGMtG+PIePYYG6F 61RJh9E/x6u+9XX+FUyvTAUfJ8h5cxzIfUzHmUzH2JcgpY59TQH46iEzv6xiQ7qk 0GZXd18c0qIn07exwaHwZPHOtDksmp6qoRL69zgkhqtA65Hp2luT+Lk0KpmGa2I= =so7U -END PGP SIGNATURE End Message ---
Bug#840725: [Pkg-opencl-devel] Bug#840840: pocl: Does not build on several architectures
You shouldn't need libpoclu-dev to build OpenCL-using code, only ocl-icd-opencl-dev (which is available on all architectures). What does require an ICD is _running_ OpenCL code, including in the test suite (if any); as buildds are unlikely to have a GPU, build-time OpenCL-using tests can only be run on architectures with pocl-opencl-icd. You could build but not test the OpenCL-using part on the other architectures, but you may well not want to. There isn't a standard for how to turn off OpenCL (beyond the conventions applying to compile-time-optional features in general): check the git log for how you turned it on, and/or upstream's documentation.
Bug#840767: peg is in NEW
Hello, Thank you for reporting. Peg and all of its dependencies are currently in NEW. Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Bug#835760: marked as done (golang-golang-x-tools: FTBFS: Tests failures)
Your message dated Sun, 16 Oct 2016 01:36:14 + with message-id and subject line Bug#835760: fixed in golang-golang-x-tools 1:0.0~git20160826.0.a832035-1 has caused the Debian Bug report #835760, regarding golang-golang-x-tools: FTBFS: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 835760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-golang-x-tools Version: 1:0.0~git20160315.0.f42ec61-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160828 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): > Renamed 5 occurrences in 1 file in 1 package. > Renamed 3 occurrences in 1 file in 1 package. > Renamed 2 occurrences in 1 file in 1 package. > Renamed 1 occurrence in 1 file in 1 package. > Renamed 2 occurrences in 1 file in 1 package. > Renamed 1 occurrence in 1 file in 1 package. > Renamed 2 occurrences in 1 file in 1 package. > --- PASS: TestRewrites (0.01s) > === RUN TestDiff > --- PASS: TestDiff (1.24s) > PASS > okgolang.org/x/tools/refactor/rename 1.287s > ? golang.org/x/tools/refactor/satisfy [no test files] > dh_auto_test: go test -v -p 1 -test.short golang.org/x/tools/benchmark/parse > golang.org/x/tools/blog golang.org/x/tools/blog/atom > golang.org/x/tools/cmd/benchcmp golang.org/x/tools/cmd/bundle > golang.org/x/tools/cmd/callgraph golang.org/x/tools/cmd/digraph > golang.org/x/tools/cmd/eg golang.org/x/tools/cmd/fiximports > golang.org/x/tools/cmd/godex golang.org/x/tools/cmd/godoc > golang.org/x/tools/cmd/goimports golang.org/x/tools/cmd/gomvpkg > golang.org/x/tools/cmd/gorename golang.org/x/tools/cmd/gotype > golang.org/x/tools/cmd/guru golang.org/x/tools/cmd/guru/serial > golang.org/x/tools/cmd/html2article golang.org/x/tools/cmd/oracle > golang.org/x/tools/cmd/present golang.org/x/tools/cmd/ssadump > golang.org/x/tools/cmd/stress golang.org/x/tools/cmd/stringer > golang.org/x/tools/cmd/tip golang.org/x/tools/container/intsets > golang.org/x/tools/cover golang.org/x/tools/go/ast/astutil > golang.org/x/tools/go/buildutil golang.org/x/tools/go/callgraph > golang.org/x/tools/go/callgraph/cha golang.org/x/tools/go/callgraph/rta > golang.org/x/tools/go/callgraph/static golang.org/x/tools/go/exact > golang.org/x/tools/go/gccgoimporter golang.org/x/tools/go/gcimporter > golang.org/x/tools/go/gcimporter15 golang.org/x/tools/go/importer > golang.org/x/tools/go/loader golang.org/x/tools/go/pointer > golang.org/x/tools/go/ssa golang.org/x/tools/go/ssa/interp > golang.org/x/tools/go/ssa/ssautil golang.org/x/tools/go/types > golang.org/x/tools/go/types/typeutil golang.org/x/tools/go/vcs > golang.org/x/tools/godoc golang.org/x/tools/godoc/analysis > golang.org/x/tools/godoc/redirect golang.org/x/tools/godoc/static > golang.org/x/tools/godoc/util golang.org/x/tools/godoc/vfs > golang.org/x/tools/godoc/vfs/gatefs golang.org/x/tools/godoc/vfs/httpfs > golang.org/x/tools/godoc/vfs/mapfs golang.org/x/tools/godoc/vfs/zipfs > golang.org/x/tools/imports golang.org/x/tools/oracle > golang.org/x/tools/oracle/serial golang.org/x/tools/playground > golang.org/x/tools/playground/socket golang.org/x/tools/present > golang.org/x/tools/refactor/eg golang.org/x/tools/refactor/importgraph > golang.org/x/tools/refactor/rename golang.org/x/tools/refactor/satisfy > returned exit code 1 > cd /<> > debian/rules:63: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://people.debian.org/~lucas/logs/2016/08/28/golang-golang-x-tools_0.0~git20160315.0.f42ec61-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: golang-golang-x-tools Source-Version: 1:0.0~git20160826.0.a832035-1 We believe that the bug you reported is fixed in the latest version of golang-golang-x-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 835...@bu
Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked
Pirate Praveen writes: > jison is now in the archive and we don't need npm. Once jison clears > NEW, I'll upload a fixed version. Thanks. Alas, the new version is unbuildable on architectures that previously failed -- e.g., node-lex-parser build-depends on: - jison:arm64 jison depends on: - node-jison-lex:arm64 (>= 0.3~) node-jison-lex depends on missing: - node-lex-parser:arm64 (>= 0.1.0) Is there some reason node-lex-parser has an Architecture value of any rather than all? Its contents all appear to be architecture-independent at first glance. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked
On Sun, 16 Oct 2016 00:20:31 -0400 u...@debian.org (Aaron M. Ucko) wrote: > Is there some reason node-lex-parser has an Architecture value of any > rather than all? Its contents all appear to be architecture-independent > at first glance. Because it was created by dh-make as npm2deb was crashing (#840169). I have changed this to arch:all. signature.asc Description: OpenPGP digital signature
Bug#770492: linux-image-3.16.0-4-686-pae: chown removes security.capability xattr on other users' files
Control: tags -1 + fixed-upstream Hi This is now fixed upstream in v4.9-rc1: https://git.kernel.org/linus/030b533c4fd4d2ec3402363323de4bb2983c9cee Regards, Salvatore
Processed: Re: Bug#770492: linux-image-3.16.0-4-686-pae: chown removes security.capability xattr on other users' files
Processing control commands: > tags -1 + fixed-upstream Bug #770492 [src:linux] linux-image-3.16.0-4-686-pae: chown removes security.capability xattr on other users' files (CVE-2015-1350) Added tag(s) fixed-upstream. -- 770492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 837714 in 3.0.4-3, fixed 837714 in 3.0.4-3+wheezy4
Processing commands for cont...@bugs.debian.org: > found 837714 3.0.4-3 Bug #837714 {Done: Andreas Henriksson } [src:libarchive] libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite Marked as found in versions libarchive/3.0.4-3. > fixed 837714 3.0.4-3+wheezy4 Bug #837714 {Done: Andreas Henriksson } [src:libarchive] libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite The source 'libarchive' and version '3.0.4-3+wheezy4' do not appear to match any binary packages Marked as fixed in versions libarchive/3.0.4-3+wheezy4. > thanks Stopping processing here. Please contact me if you need assistance. -- 837714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems