Bug#952268: [Pkg-ayatana-devel] Bug#952268: appmenu-gtk-module: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/u
Hi Logan, On Mo 24 Feb 2020 04:24:43 CET, Logan Rosen wrote: Package: appmenu-gtk-module Version: 0.7.3-1 Followup-For: Bug #952268 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on gtk-doc-tools to fix FTBFS. Thanks for considering the patch. Logan Thanks. I have just uploaded a fixed version. Please re-enable sync from Debian to Ubuntu for this pkg. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpUKDZ2N60j4.pgp Description: Digitale PGP-Signatur
Bug#952049: pekka-kana-2: FTBFS: SDL_image.h:100:24: error: missing binary operator before token "("
Hi, Thank you very much for notifying me about the bug and the fix. I made a new version of pekka-kana-2/1.2.6-1[1] fixing this bug and improvements. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952422 See you later! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
Processed: Set found version correctly
Processing commands for cont...@bugs.debian.org:
> found 951980 0.5.2-1
Bug #951980 {Done: Jonathan McDowell } [libsigrok-dev]
Missing bluetooth + hidapi deps on -dev package cause FTBFSes
Bug #952272 {Done: Jonathan McDowell } [libsigrok-dev]
pulseview: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
returned exit code 1
Marked as found in versions libsigrok/0.5.2-1.
Marked as found in versions libsigrok/0.5.2-1.
> found 952272 0.5.2-1
Bug #952272 {Done: Jonathan McDowell } [libsigrok-dev]
pulseview: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
returned exit code 1
Bug #951980 {Done: Jonathan McDowell } [libsigrok-dev]
Missing bluetooth + hidapi deps on -dev package cause FTBFSes
Ignoring request to alter found versions of bug #952272 to the same values
previously set
Ignoring request to alter found versions of bug #951980 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
951980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951980
952272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#952197: marked as pending in node-optionator
Control: tag -1 pending Hello, Bug #952197 in node-optionator reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-optionator/commit/8b16f71359fde2dd5b373cca334529048499b476 Replace old-style mocha files Closes: #952197 (this message was generated automatically) -- Greetings https://bugs.debian.org/952197
Processed: Bug#952197 marked as pending in node-optionator
Processing control commands: > tag -1 pending Bug #952197 [src:node-optionator] node-optionator: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 952197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952268: marked as done (appmenu-gtk-module: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=
Your message dated Mon, 24 Feb 2020 08:47:24 + with message-id and subject line Bug#952268: fixed in appmenu-gtk-module 0.7.3-2 has caused the Debian Bug report #952268, regarding appmenu-gtk-module: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu 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.) -- 952268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: appmenu-gtk-module Version: 0.7.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=meson >dh_update_autotools_config -O--buildsystem=meson >dh_autoreconf -O--buildsystem=meson >dh_auto_configure -O--buildsystem=meson > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.53.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: appmenu-gtk-module > Project version: 0.7 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 9.2.1 "cc (Debian 9.2.1-29) 9.2.1 > 20200220") > C linker for the host machine: cc GNU ld.bfd 2.34 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29) > Run-time dependency gio-unix-2.0 found: YES 2.62.4 > Run-time dependency gtk+-2.0 found: YES 2.24.32 > Run-time dependency gtk+-3.0 found: YES 3.24.13 > Run-time dependency systemd found: YES 244 > Configuring appmenu-gtk-module.service using configuration > Configuring gtkdocentities.ent using configuration > > docs/meson.build:19:6: ERROR: Program(s) ['gtkdoc-scan'] not found or not > executable > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2020-02-23T02:48:00.079679 > Main binary: /usr/bin/python3 > Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.53.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: appmenu-gtk-module > Project version: 0.7 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.c -o > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 9.2.1 "cc (Debian 9.2.1-29) 9.2.1 > 20200220") > C linker for the build machine: cc GNU ld.bfd 2.34 > Appending CFLAGS from environment: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Appending LDFLAGS from environment: ['-Wl,-z,relro', '-Wl,-z,now'] > Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2' > Sanity testing C co
Bug#951922: marked as done (advi: FTBFS: configure: error: kpsexpand not found, check your PATH)
Your message dated Mon, 24 Feb 2020 08:47:15 + with message-id and subject line Bug#951922: fixed in advi 1.10.2-6 has caused the Debian Bug report #951922, regarding advi: FTBFS: configure: error: kpsexpand not found, check your PATH 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.) -- 951922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: advi Version: 1.10.2-5 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking X11/extensions/Xinerama.h usability... yes > checking X11/extensions/Xinerama.h presence... yes > checking for X11/extensions/Xinerama.h... yes > checking for XineramaQueryScreens in -lXinerama... yes > checking for kpsexpand... no > configure: error: kpsexpand not found, check your PATH > make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2020/02/22/advi_1.10.2-5_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: advi Source-Version: 1.10.2-6 Done: Ralf Treinen We believe that the bug you reported is fixed in the latest version of advi, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated advi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Feb 2020 22:03:49 +0100 Source: advi Architecture: source Version: 1.10.2-6 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Ralf Treinen Closes: 951922 Changes: advi (1.10.2-6) unstable; urgency=medium . * Add build-dependency texlive-extra-utils (closes: #951922) * Build-depend on debhelper-compat, drop file debian/compat * Debhelper compatibility level 12 * Rename debian/TODO.Debian to debian/TODO * Standards-Version 4.5.0 (no change) Checksums-Sha1: 1976c2be158ab9c09fe93b80174d3464b2db14fc 2252 advi_1.10.2-6.dsc 3463ae180534953613c124ae11c59a7c7a30b948 27016 advi_1.10.2-6.debian.tar.xz 430d543432ea78ae0912b648f98f03c64bce790f 10113 advi_1.10.2-6_source.buildinfo Checksums-Sha256: 9a4cb26190cb715cec1f210d7a96d3f161cf809d36ff70682e47f8ca0c1aa837 2252 advi_1.10.2-6.dsc fe1ee63252b4b7f2454aec4490ec0b9f850578ed66539c0f987fcec8c104 27016 advi_1.10.2-6.debian.tar.xz c7e5b15893a8047502c73124056d708e9cdfd8c266d5aad2a4b3a2a3c83ffbab 10113 advi_1.10.2-6_source.buildinfo Files: 4baa2339e8793c6a1bdd94674fa05a8b 2252 tex optional advi_1.10.2-6.dsc a465f759659a9451887a3b4ed748d9c7 27016 tex optional advi_1.10.2-6.debian.tar.xz 1248d1660c72dc3c5108a5ad9373ccb2 10113 tex optional advi_1.10.2-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAl5TfpQACgkQdFxHZtTK zf8YcQ/9FXw4v3nM4zqycIyMEyMDspn2O5DCd0rFOKsA1IgI0YZdpXkP1pTdreei WcUCJ1ixxTyWs/UWKl+AgdTpvgggbMKOHdyjaicDkleFwS4MaAJX3+8jn410sP9M h05wpCPJxVFkI5FWamDw/4GwJvqetDu6X53q5VSas7hD+qWCelH9UN2TIUZUpjqP pLKolhL3GMwvP+vP/PiVIWNSu8fON2xABs+ILtsKr4vFqPW8VBfBiAhUEU8ilM0d OnP7GWlu0vycnx2j2/ydA35seceR59lpbMhgb3xIPpJv9Pz469AVu0FPssI0H5wy PzP7xvxB0+LRR/EWJVz0tFnAemyOlplSvCQF/6gaktgiUBKSwP/t9DlcED2kpSOl 6cjLKhQ4y2bPvF1kIaxFeuwMofR0RSWP/jKJcxeTW6cRh9+2dQFlHpPIflL6Wvyw hsNBBzj8pjAttzJR+u7iLAHDYFtxghcfVw42hh1wGampFWEhZlo8sGFnIJIrk7Fs 0tNIOxP78GkyRnC3+NUtiG6NKoBPxV7jN0qT65o4sAlm6Uhebhbgj6T9eji1D4sg isRbTN3T1qT9Wkf+S9DM2FdKqStx8MZVshbMV2KpAnJ41lAfLcguqKH3EEQCvHWC YjQd0hb7jt/iKy746vMt5oEsP1uiEb/KWkRNyWi55Tdha8ooF8A= =DXgy -END PGP SIGNATURE End Message ---
Bug#909559: marked as done (Ships empty zipfile /usr/psychojs.zip)
Your message dated Mon, 24 Feb 2020 08:55:42 + with message-id and subject line Bug#909559: fixed in psychopy 2020.1.1+dfsg-1 has caused the Debian Bug report #909559, regarding Ships empty zipfile /usr/psychojs.zip 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.) -- 909559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: psychopy Version: 1.85.3.dfsg-1 Severity: serious psychopy ships a file in the inappropriate location /usr/psychojs.zip . This file appears to be an *empty* zipfile. (There's another copy of the same empty file in ./usr/lib/python2.7/dist-packages/psychopy/psychojs.zip .) --- End Message --- --- Begin Message --- Source: psychopy Source-Version: 2020.1.1+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of psychopy, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated psychopy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2020 08:56:57 +0100 Source: psychopy Architecture: source Version: 2020.1.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 866455 878930 909559 912497 937330 Changes: psychopy (2020.1.1+dfsg-1) unstable; urgency=medium . * Team upload. * Moved package to Debian Med team * New upstream version Closes: #909559, #878930 * debhelper-compat 12 * Point Vcs fields to salsa.debian.org * Standards-Version: 4.4.1 * Do not manually unpack upstream source but use Files-Excluded instead * Remove old debian menu file and old style debian/py* files * Switch to Python3 Closes: #937330, #912497, #866455 * Build-Depends / Recommends: python3-questplus, python3-distro * Standards-Version: 4.5.0 (routine-update) * Secure URI in copyright format (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) * Remove trailing whitespace in debian/copyright (routine-update) * Do not parse d/changelog (routine-update) * Trim trailing whitespace. * Use secure URI in Homepage field. * Remove patch wxpython3.0.patch that is missing from debian/patches/series. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Remove deprecated Encoding key from desktop file debian/psychopy.desktop. * Fix link to examples * Drop automatically generated sphinx files from upstream source Checksums-Sha1: 78dedf22e574cb8a667b783b2a664ff04a75eb1e 2593 psychopy_2020.1.1+dfsg-1.dsc 9bfdedaf8e2b98c86a8fceb3ca73dcd8068bbd23 14612488 psychopy_2020.1.1+dfsg.orig.tar.xz 842b44537aadfa9413431bcae8651c7230d9cb23 12844 psychopy_2020.1.1+dfsg-1.debian.tar.xz b6047fda2a21938ffedc9b3ce65e0b719440b77a 19197 psychopy_2020.1.1+dfsg-1_amd64.buildinfo Checksums-Sha256: ff84c89e01098fbb5f233dfadce63b1b5efe900aa36ae0f2128cdb3bd58588b1 2593 psychopy_2020.1.1+dfsg-1.dsc 57dbaf3131b1814ec2039fd2368610c9ae30e8e51cbf566b0ea2f99369e1eebf 14612488 psychopy_2020.1.1+dfsg.orig.tar.xz 12780cf4d1bac0b0978693f1fa918433b132434d457e1c4a4f9e4817a9dfa235 12844 psychopy_2020.1.1+dfsg-1.debian.tar.xz 5f33edf291183612613694ccaf4339270a2cd8b28d7fb399402c80c0f3415457 19197 psychopy_2020.1.1+dfsg-1_amd64.buildinfo Files: 0bde0607bc73fbe78a067d96e54df098 2593 science optional psychopy_2020.1.1+dfsg-1.dsc fca57b19883ca64c125e5fe75df3e753 14612488 science optional psychopy_2020.1.1+dfsg.orig.tar.xz 20c537171df061d0fb24fad55e8c46bb 12844 science optional psychopy_2020.1.1+dfsg-1.debian.tar.xz 44a4ccce310a99de19e55b5a418c846d 19197 science optional psychopy_2020.1.1+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl5ThSwRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtG3QQ//QJ1j9hxm/3GHoxfOB6Goh9803KdmVfaI 6DRuFW7xg1IpR5haUqMjd2xvFHG3DEAnWaf16N1+GBiqWS7fMKRuKAOtUUog7hz3 /9RlGBJeO1hQ+t3bCSem5ptUqItf138egb5lc1mEy1vu0fpBoNC9ASNDOm3dxyKn 1F2AmV3T3SvAllqqlZnEG
Bug#866455: marked as done (psychopy: depends on obsolete python-imaging (replace with python3-pil or python-pil))
Your message dated Mon, 24 Feb 2020 08:55:42 + with message-id and subject line Bug#866455: fixed in psychopy 2020.1.1+dfsg-1 has caused the Debian Bug report #866455, regarding psychopy: depends on obsolete python-imaging (replace with python3-pil or python-pil) 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.) -- 866455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:psychopy Version: 1.83.04.dfsg-2 Severity: important Tags: sid buster User: d...@debian.org Usertags: imaging-pillow One or more binary packages built from this source depends on or recommends python-imaging, which is obsolete for some years now. Please build the source using the python-pil package. If your package doesn't need to be built with Python2, please consider using Python3 and depend on python3-pil. Planning to remove python-imaging for the buster release, so the severity of this issues might be raised. --- End Message --- --- Begin Message --- Source: psychopy Source-Version: 2020.1.1+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of psychopy, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated psychopy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2020 08:56:57 +0100 Source: psychopy Architecture: source Version: 2020.1.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 866455 878930 909559 912497 937330 Changes: psychopy (2020.1.1+dfsg-1) unstable; urgency=medium . * Team upload. * Moved package to Debian Med team * New upstream version Closes: #909559, #878930 * debhelper-compat 12 * Point Vcs fields to salsa.debian.org * Standards-Version: 4.4.1 * Do not manually unpack upstream source but use Files-Excluded instead * Remove old debian menu file and old style debian/py* files * Switch to Python3 Closes: #937330, #912497, #866455 * Build-Depends / Recommends: python3-questplus, python3-distro * Standards-Version: 4.5.0 (routine-update) * Secure URI in copyright format (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) * Remove trailing whitespace in debian/copyright (routine-update) * Do not parse d/changelog (routine-update) * Trim trailing whitespace. * Use secure URI in Homepage field. * Remove patch wxpython3.0.patch that is missing from debian/patches/series. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Remove deprecated Encoding key from desktop file debian/psychopy.desktop. * Fix link to examples * Drop automatically generated sphinx files from upstream source Checksums-Sha1: 78dedf22e574cb8a667b783b2a664ff04a75eb1e 2593 psychopy_2020.1.1+dfsg-1.dsc 9bfdedaf8e2b98c86a8fceb3ca73dcd8068bbd23 14612488 psychopy_2020.1.1+dfsg.orig.tar.xz 842b44537aadfa9413431bcae8651c7230d9cb23 12844 psychopy_2020.1.1+dfsg-1.debian.tar.xz b6047fda2a21938ffedc9b3ce65e0b719440b77a 19197 psychopy_2020.1.1+dfsg-1_amd64.buildinfo Checksums-Sha256: ff84c89e01098fbb5f233dfadce63b1b5efe900aa36ae0f2128cdb3bd58588b1 2593 psychopy_2020.1.1+dfsg-1.dsc 57dbaf3131b1814ec2039fd2368610c9ae30e8e51cbf566b0ea2f99369e1eebf 14612488 psychopy_2020.1.1+dfsg.orig.tar.xz 12780cf4d1bac0b0978693f1fa918433b132434d457e1c4a4f9e4817a9dfa235 12844 psychopy_2020.1.1+dfsg-1.debian.tar.xz 5f33edf291183612613694ccaf4339270a2cd8b28d7fb399402c80c0f3415457 19197 psychopy_2020.1.1+dfsg-1_amd64.buildinfo Files: 0bde0607bc73fbe78a067d96e54df098 2593 science optional psychopy_2020.1.1+dfsg-1.dsc fca57b19883ca64c125e5fe75df3e753 14612488 science optional psychopy_2020.1.1+dfsg.orig.tar.xz 20c537171df061d0fb24fad55e8c46bb 12844 science optional psychopy_2020.1.1+dfsg-1.debian.tar.xz 44a4ccce310a99de19e55b5a418c846d 19197 science optional psychopy_2020.1.1+dfsg-1_amd64.buildinfo -BEGIN P
Bug#952426: digikam: digkam experimental not correctly instalable
Package: digikam Version: 4:7.0.0~beta2+dfsg-1 Severity: grave Justification: renders package unusable digikam digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot open shared object file: No such file or directory Has already been reported. But in addition, LANG="C" apt-get -t experimental install libhdf5-hl-100 Reading package lists... Done Building dependency tree Reading state information... Done 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: libhdf5-hl-100 : Depends: libhdf5-103-1 but it is not going to be installed E: Unable to correct problems, you have held broken packages. tri-yann4:~# LANG="C" apt-get -t experimental install libhdf5-hl-100 libhdf5-103-1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dvgrab libarmadillo9 libarpack2 libavresample4 libcharls2 libdap25 libdapclient6v5 libepsilon1 libfyba0 libgdcm3.0 libgeotiff5 libhdf4-0-alt libkmlbase1 libkmldom1 libkmlengine1 libmlt-data libmovit8 libodbc1 libogdi4.1 libqhull7 libqtav1 libqtavwidgets1 librtaudio6 librttr-core0.9.6 libsocket++1 libsuperlu5 odbcinst odbcinst1debian2 Use 'apt autoremove' to remove them. The following packages will be REMOVED: digikam digikam-private-libs enblend enfuse hugin hugin-tools kdenlive libgdal26 libhdf5-103 libmlt++3 libmlt6 libnetcdf-c++4 libnetcdf15 libopencv-calib3d4.2 libopencv-contrib4.2 libopencv-features2d4.2 libopencv-highgui4.2 libopencv-imgcodecs4.2 libopencv-objdetect4.2 libopencv-shape4.2 libopencv-stitching4.2 libopencv-superres4.2 libopencv-video4.2 libopencv-videoio4.2 libopencv-videostab4.2 libopencv-viz4.2 libvigraimpex11 libvtk6.3 melt showfoto The following NEW packages will be installed: libhdf5-103-1 libhdf5-hl-100 0 upgraded, 2 newly installed, 30 to remove and 67 not upgraded. Need to get 1265 kB of archives. After this operation, 212 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.21 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages digikam depends on: ii digikam-data 4:7.0.0~beta2+dfsg-1 ii digikam-private-libs 4:7.0.0~beta2+dfsg-1 ii libc6 2.30-0experimental2 ii libgcc-s1 10-20200222-1 ii libkf5configcore5 5.62.0-1+b1 ii libkf5coreaddons5 5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libmagick++-6.q16-8 8:6.9.10.23+dfsg-2.1+b2 ii libqt5core5a 5.12.5+dfsg-8 ii libqt5gui55.12.5+dfsg-8 ii libqt5sql55.12.5+dfsg-8 ii libqt5sql5-mysql 5.12.5+dfsg-8 ii libqt5sql5-sqlite 5.12.5+dfsg-8 ii libqt5widgets55.12.5+dfsg-8 ii libstdc++610-20200222-1 ii perl 5.30.1~rc1-1 Versions of packages digikam recommends: ii ffmpegthumbs4:19.12.2-1 ii firefox-esr [www-browser] 68.5.0esr-1+b1 ii google-chrome-stable [www-browser] 80.0.3987.116-1 ii links2 [www-browser]2.20.2-1+b1 ii lynx [www-browser] 2.9.0dev.4-1 ii w3m [www-browser] 0.5.3-37+b1 Versions of packages digikam suggests: pn digikam-doc ii systemsettings 4:5.17.5-2 -- no debconf information
Bug#952305: marked as pending in libpdl-io-matlab-perl
Control: tag -1 pending Hello, Bug #952305 in libpdl-io-matlab-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libpdl-io-matlab-perl/commit/c814c85967ef5f5e7989c0fe1c4e9d7f6da7be16 Add patch to fix FTBFS due to pod sections embedded in pp_addxs commands. (closes: #952305) (this message was generated automatically) -- Greetings https://bugs.debian.org/952305
Processed: Bug#952305 marked as pending in libpdl-io-matlab-perl
Processing control commands: > tag -1 pending Bug #952305 [src:libpdl-io-matlab-perl] libpdl-io-matlab-perl: FTBFS: Error: OUTPUT =pod not an argument in Matlab.xs, line 230 Added tag(s) pending. -- 952305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952197: marked as done (node-optionator: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 24 Feb 2020 09:22:45 +
with message-id
and subject line Bug#952197: fixed in node-optionator 0.8.3+dfsg-2
has caused the Debian Bug report #952197,
regarding node-optionator: FTBFS: dh_auto_test: error: /bin/sh -e
debian/tests/pkg-js/test 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.)
--
952197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-optionator
Version: 0.8.3+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir lib/
> /usr/bin/lsc --compile --output lib "src/help.ls"
> /usr/bin/lsc --compile --output lib "src/index.ls"
> /usr/bin/lsc --compile --output lib "src/util.ls"
> /usr/bin/lsc --compile package.json.ls
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
>
> Run tests with Mocha
>
> Rules & Behavior
> --allow-uncaught Allow uncaught errors to propagate
> [boolean]
> --async-only, -A Require all tests to use a callback (async) or
> return a Promise
> [boolean]
> --bail, -b Abort ("bail") after first test failure
> [boolean]
> --check-leaks Check for global variable leaks
> [boolean]
> --delayDelay initial execution of root suite
> [boolean]
> --exit Force Mocha to quit after tests complete
> [boolean]
> --forbid-only Fail if exclusive test(s) encountered
> [boolean]
> --forbid-pending Fail if pending test(s) encountered
> [boolean]
> --global, --globalsList of allowed global variables
> [array]
> --retries Retry failed tests this many times
> [number]
> --slow, -s Specify "slow" test threshold (in milliseconds)
> [string] [default:
> 75]
> --timeout, -t, --timeouts Specify test timeout threshold (in milliseconds)
> [string] [default:
> 2000]
> --ui, -u Specify user interface[string] [default:
> "bdd"]
>
> Reporting & Output
> --color, -c, --colors Force-enable color output
> [boolean]
> --diffShow diff on failure
>[boolean] [default:
> true]
> --full-trace Display full stack traces
> [boolean]
> --growl, -G Enable Growl notifications
> [boolean]
> --inline-diffsDisplay actual/expected
> differences
> inline within each string
> [boolean]
> --reporter, -RSpecify reporter to use
> [string] [default:
> "spec"]
> --reporter-option, --reporter-options,Reporter-specific options
> -O()
> [array]
>
> Configuration
> --config Path to config file [string] [default: (nearest rc
> file)]
> --opts Path to `mocha.opts` (DEPRECATED)
> [string] [default:
> "./test/mocha.opts"]
> --package Path to package.json for config
> [string]
>
> File Handling
> --extension File extension(s) to load [array] [default:
> js]
> --file Specify file(s) to be loaded prior to root suite
>execution [array] [default:
> (none)]
> --ignore, --exclude Ignore file(s) or glob pattern(s)
>[array] [default:
> (none)]
> --recursive Look for tests in subdirectories
> [boolean]
> --require, -rRequire module [array] [default:
> (none)]
> --sort, -S Sort test files
> [boolean]
> --watch, -w Watch files in the current working directory for
> changes
>
Bug#952191: marked as done (node-levn: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 24 Feb 2020 09:22:37 +
with message-id
and subject line Bug#952191: fixed in node-levn 0.3.0+dfsg-4
has caused the Debian Bug report #952191,
regarding node-levn: FTBFS: dh_auto_test: error: /bin/sh -e
debian/tests/pkg-js/test 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.)
--
952191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-levn
Version: 0.3.0+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p lib/
> /usr/bin/lsc --compile --output lib "src/cast.ls"
> /usr/bin/lsc --compile --output lib "src/index.ls"
> /usr/bin/lsc --compile --output lib "src/parse-string.ls"
> /usr/bin/lsc --compile package.json.ls
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
>
> Run tests with Mocha
>
> Rules & Behavior
> --allow-uncaught Allow uncaught errors to propagate
> [boolean]
> --async-only, -A Require all tests to use a callback (async) or
> return a Promise
> [boolean]
> --bail, -b Abort ("bail") after first test failure
> [boolean]
> --check-leaks Check for global variable leaks
> [boolean]
> --delayDelay initial execution of root suite
> [boolean]
> --exit Force Mocha to quit after tests complete
> [boolean]
> --forbid-only Fail if exclusive test(s) encountered
> [boolean]
> --forbid-pending Fail if pending test(s) encountered
> [boolean]
> --global, --globalsList of allowed global variables
> [array]
> --retries Retry failed tests this many times
> [number]
> --slow, -s Specify "slow" test threshold (in milliseconds)
> [string] [default:
> 75]
> --timeout, -t, --timeouts Specify test timeout threshold (in milliseconds)
> [string] [default:
> 2000]
> --ui, -u Specify user interface[string] [default:
> "bdd"]
>
> Reporting & Output
> --color, -c, --colors Force-enable color output
> [boolean]
> --diffShow diff on failure
>[boolean] [default:
> true]
> --full-trace Display full stack traces
> [boolean]
> --growl, -G Enable Growl notifications
> [boolean]
> --inline-diffsDisplay actual/expected
> differences
> inline within each string
> [boolean]
> --reporter, -RSpecify reporter to use
> [string] [default:
> "spec"]
> --reporter-option, --reporter-options,Reporter-specific options
> -O()
> [array]
>
> Configuration
> --config Path to config file [string] [default: (nearest rc
> file)]
> --opts Path to `mocha.opts` (DEPRECATED)
> [string] [default:
> "./test/mocha.opts"]
> --package Path to package.json for config
> [string]
>
> File Handling
> --extension File extension(s) to load [array] [default:
> js]
> --file Specify file(s) to be loaded prior to root suite
>execution [array] [default:
> (none)]
> --ignore, --exclude Ignore file(s) or glob pattern(s)
>[array] [default:
> (none)]
> --recursive Look for tests in subdirectories
> [boolean]
> --require, -rRequire module [array] [default:
> (none)]
> --sort, -S Sort test files
> [boolean]
> --watch, -w Watch files in the current working directory for
> changes
>
Bug#951864: marked as done (pygalmesh fails it's own autopkg tests)
Your message dated Mon, 24 Feb 2020 09:23:12 + with message-id and subject line Bug#951864: fixed in pygalmesh 0.5.2-1 has caused the Debian Bug report #951864, regarding pygalmesh fails it's own autopkg tests 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.) -- 951864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pygalmesh Version: 0.5.0-4 Severity: serious Tags: sid bullseye pygalmesh fails it's own autopkg tests: [...] autopkgtest [18:10:53]: test command1: pytest-3 autopkgtest [18:10:53]: test command1: [--- = test session starts == platform linux -- Python 3.7.6, pytest-4.6.9, py-1.8.1, pluggy-0.13.0 rootdir: /tmp/autopkgtest-lxc.c4_o_0a3/downtmp/build.k44/src collected 26 items test/test_inr.py F [ 3%] test/test_periodic.py . [ 7%] test/test_surface_mesh.py . [ 11%] test/test_volume_from_surface.py . [ 15%] test/test_volume_mesh.py .. [100%] === FAILURES === ___ test_inr ___ def test_inr(): this_dir = os.path.dirname(os.path.abspath(__file__)) mesh = pygalmesh.generate_from_inr( os.path.join(this_dir, "meshes", "skull_2.9.inr"), cell_size=5.0, verbose=False ) tol = 2.0e-3 ref = [2.031053e02, 3.739508e01, 2.425594e02, 2.558910e01, 2.300883e02, 1.775010e00] assert abs(max(mesh.points[:, 0]) - ref[0]) < tol * ref[0] assert abs(min(mesh.points[:, 0]) - ref[1]) < tol * ref[1] assert abs(max(mesh.points[:, 1]) - ref[2]) < tol * ref[2] assert abs(min(mesh.points[:, 1]) - ref[3]) < tol * ref[3] assert abs(max(mesh.points[:, 2]) - ref[4]) < tol * ref[4] > assert abs(min(mesh.points[:, 2]) - ref[5]) < tol * ref[5] E assert 0.0294994218444824 < (0.002 * 1.77501) E+ where 0.0294994218444824 = abs((1.7455106 - 1.77501)) E+where 1.7455106 = min(array([115.045494, 116.24661 , 122.3319 , ..., 63.492596, 101.66734 ,\n 169.07079 ], dtype=float32)) test/test_inr.py:20: AssertionError = 1 failed, 25 passed in 28.42 seconds = --- End Message --- --- Begin Message --- Source: pygalmesh Source-Version: 0.5.2-1 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of pygalmesh, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated pygalmesh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2020 11:54:01 +0800 Source: pygalmesh Architecture: source Version: 0.5.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 951864 Changes: pygalmesh (0.5.2-1) unstable; urgency=medium . * New upstream release. - versioned Build-Depends: python3-meshio (>= 4) * Update debian patch relax_test_tolerance.patch to relax upstream tolerance only for ref[5]. Closes: #951864. Checksums-Sha1: 8c4cc177a279201d703c51561591a12e1db7a6db 2211 pygalmesh_0.5.2-1.dsc 3f457dacef1aecff8d1e9c873337db2973d04a04 1030588 pygalmesh_0.5.2.orig.tar.xz ccf8c78d39037770b548d1c22a606cac0f970712 4848 pygalmesh_0.5.2-1.debian.tar.xz 63c90adbe732cfca76bba12d5255b4ea86b33d24 8216 pygalmesh_0.5.2-1_source.buildinfo Checksums-Sha256: 43da235b9daeb0b6785ac8b2be76a4841cdeec8aadf3ef2820e4399f77b0323e 2211 pygalmesh_0.5.2-1.dsc 87da1ee487136d68cffaf28aab9102139ac082c0d0b138da3f11818aa9aca0cb 1030588 pygalmesh_0.5.2.orig.tar.xz d02a22cda8b823295cc1bf45c1f3a9e8dfc5337c1d9d7dd823ef797919fcc8b1 4848 pygalmesh_0.5.2-1.debian.tar.xz f2717f90ebf14b0cf360157396b12735907
Bug#952183: marked as done (node-serve-static: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 24 Feb 2020 09:22:51 +
with message-id
and subject line Bug#952183: fixed in node-serve-static 1.14.1-3
has caused the Debian Bug report #952183,
regarding node-serve-static: FTBFS: dh_auto_test: error: /bin/sh -e
debian/tests/pkg-js/test 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.)
--
952183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-serve-static
Version: 1.14.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-serve-static
> dpkg-buildpackage: info: source version 1.14.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
> rm -rf ./node_modules/.cache
>dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-serve-static using existing
> ./node-serve-static_1.14.1.orig.tar.gz
> dpkg-source: info: building node-serve-static in
> node-serve-static_1.14.1-2.debian.tar.xz
> dpkg-source: info: building node-serve-static in
> node-serve-static_1.14.1-2.dsc
> debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
>
> Run tests with Mocha
>
> Rules & Behavior
> --allow-uncaught Allow uncaught errors to propagate
> [boolean]
> --async-only, -A Require all tests to use a callback (async) or
> return a Promise
> [boolean]
> --bail, -b Abort ("bail") after first test failure
> [boolean]
> --check-leaks Check for global variable leaks
> [boolean]
> --delayDelay initial execution of root suite
> [boolean]
> --exit Force Mocha to quit after tests complete
> [boolean]
> --forbid-only Fail if exclusive test(s) encountered
> [boolean]
> --forbid-pending Fail if pending test(s) encountered
> [boolean]
> --global, --globalsList of allowed global variables
> [array]
> --retries Retry failed tests this many times
> [number]
> --slow, -s Specify "slow" test threshold (in milliseconds)
> [string] [default:
> 75]
> --timeout, -t, --timeouts Specify test timeout threshold (in milliseconds)
> [string] [default:
> 2000]
> --ui, -u Specify user interface[string] [default:
> "bdd"]
>
> Reporting & Output
> --color, -c, --colors Force-enable color output
> [boolean]
> --diffShow diff on failure
>[boolean] [default:
> true]
> --full-trace Display full stack traces
> [boolean]
> --growl, -G Enable Growl notifications
> [boolean]
> --inline-diffsDisplay actual/expected
> differences
> inline within each string
> [boolean]
> --reporter, -RSpecify reporter to use
> [string] [default:
> "spec"]
> --reporter-option, --reporter-options,Reporter-specific options
> -O()
> [array]
>
> Configuration
> --config Path to config file [string] [default: (nearest rc
> file)]
> --opts Path to `mocha.opts` (DEPRECATED)
> [string] [default:
> "./test/mocha.opts"]
> --package Path to package.json for config
Bug#952224: marked as pending in node-sinon
Control: tag -1 pending Hello, Bug #952224 in node-sinon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-sinon/commit/c647025a2e412947febfa9e6878f7c46f703cf66 Fix after hook for recent mocha Closes: #952224 (this message was generated automatically) -- Greetings https://bugs.debian.org/952224
Processed: Bug#952224 marked as pending in node-sinon
Processing control commands: > tag -1 pending Bug #952224 [src:node-sinon] node-sinon: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 952224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943451: Is that bug really pplpy's problem?
Hi, yes, it also looks more like doxygen bug to me. I didn't reassign yet because if doxygen upstream does not want to fix it, a workaround in ppl (not pplpy) might be needed. Best, Tobias On 2/23/20 8:46 PM, Julien Puydt wrote: > Hi, > > it looks more like a doxygen 1.8.16 bug than a pplpy issue, isn't it? > > If that is so, then it should be marked as affecting pplpy, but > assigned to doxygen. > > Thanks, > > JP >
Bug#952305: marked as done (libpdl-io-matlab-perl: FTBFS: Error: OUTPUT =pod not an argument in Matlab.xs, line 230)
Your message dated Mon, 24 Feb 2020 09:35:53 +
with message-id
and subject line Bug#952305: fixed in libpdl-io-matlab-perl 0.005-4
has caused the Debian Bug report #952305,
regarding libpdl-io-matlab-perl: FTBFS: Error: OUTPUT =pod not an argument in
Matlab.xs, line 230
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.)
--
952305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdl-io-matlab-perl
Version: 0.005-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> "/usr/bin/perl" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" "-MPDL::PP
> qw[PDL::IO::Matlab PDL::IO::Matlab Matlab]" matlab.pd
> Useless use of a constant ("\n=cut\n") in void context at matlab.pd line 617.
> cp Matlab.pm blib/lib/PDL/IO/Matlab.pm
> Running Mkbootstrap for Matlab ()
> chmod 644 "Matlab.bs"
> "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Matlab.bs
> blib/arch/auto/PDL/IO/Matlab/Matlab.bs 644
> "/usr/bin/perl" "/usr/share/perl/5.30/ExtUtils/xsubpp" -typemap
> '/usr/share/perl/5.30/ExtUtils/typemap' -typemap
> '/usr/lib/x86_64-linux-gnu/perl5/5.30/PDL/Core/typemap.pdl' -typemap
> '/<>/typemap' Matlab.xs > Matlab.xsc
> Error: OUTPUT =pod not an argument in Matlab.xs, line 230
> Error: OUTPUT =cut not an argument in Matlab.xs, line 240
> Code is not inside a function (maybe last function was ended by a blank line
> followed by a statement on column one?) in Matlab.xs, line 250
> make[1]: *** [Makefile:366: Matlab.c] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/libpdl-io-matlab-perl_0.005-3_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: libpdl-io-matlab-perl
Source-Version: 0.005-4
Done: Bas Couwenberg
We believe that the bug you reported is fixed in the latest version of
libpdl-io-matlab-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 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bas Couwenberg (supplier of updated libpdl-io-matlab-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: Mon, 24 Feb 2020 09:35:24 +0100
Source: libpdl-io-matlab-perl
Architecture: source
Version: 0.005-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: Bas Couwenberg
Closes: 952305
Changes:
libpdl-io-matlab-perl (0.005-4) unstable; urgency=medium
.
* Team upload.
.
[ Bas Couwenberg ]
* Bump Standards-Version to 4.5.0, no changes.
* Update watch file to use releases instead of tags.
* Update gbp.conf to use --source-only-changes by default.
* Add patch to fix FTBFS due to pod sections embedded in pp_addxs commands.
(closes: #952305)
.
[ gregor herrmann ]
* debian/control: update Build-Depends for cross builds.
* debian/watch: use uscan version 4.
Checksums-Sha1:
752c70502a0f660887615f2cf410ea2ab0c4e1f1 2191 libpdl-io-matlab-perl_0.005-4.dsc
075c31814ccd8addcdb8850a691c47205266ec5d 6992
libpdl-io-matlab-perl_0.005-4.debian.tar.xz
d0611a7754f8a99517d5337a9ee6c14b67fc81ec 8021
libpdl-io-matlab-perl_0.005-4_amd64.buildinfo
Checksums-Sha256:
c9c717e9c9fe3fe5a80ed95880728534c9d9ca84986f940c89ec2af7617ea902 2191
libpdl-io-matlab-perl_0.005-4.dsc
27450907c3d37ddfc3cfb2d429d55f3df6d3193663c92aae15048fd5d2f6c0ba 6992
libpdl-io-matlab-perl_0.005-4.debian.tar.xz
04a76ace202ff21d9ed5894948b1d08c74ca01821879b60c6929877f85b17624 8021
libpdl-io-matlab-perl_0.005-4_amd64.buildinfo
Files:
54684a7d6edc3080d1e5a27b7f492841 2191 perl optional
libpdl-io-matlab-per
Bug#952201: marked as pending in node-type-check
Control: tag -1 pending Hello, Bug #952201 in node-type-check reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-type-check/commit/bb89af2e50bce0d0bffaee1c6833fb6a9de746e4 Replace old-style mocha test files Closes: #952201 (this message was generated automatically) -- Greetings https://bugs.debian.org/952201
Processed: Bug#952201 marked as pending in node-type-check
Processing control commands: > tag -1 pending Bug #952201 [src:node-type-check] node-type-check: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 952201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951329: FTBFS in buster with linux-source-4.19 4.19.98-1
Hi Santiago, Do you have the MR ready ? Your bug report against the package in Buster has caused a trigger to auto-remove UML from Debian Testing. I don't know how removing the package from testing solves any problem with the package in Buster. If you have the MR done, can we please get it merged and get done with this bug report ? Thanks, Ritesh On Tue, 2020-02-18 at 13:33 +0530, Ritesh Raj Sarraf wrote: > Hi Santiago, > > On Fri, 2020-02-14 at 15:46 +0100, Santiago R.R. wrote: > > BTW, I will prepare a git branch in my personal salsa namespace. > > But > > I > > am not sure against which branch should I propose a MR. > > Thank you for taking care of the packages in Buster. I just created a > branch for Buster. You can prepare your changes against that branch. > > https://salsa.debian.org/uml-team/user-mode-linux/tree/buster > > -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#952426: digikam: digkam experimental not correctly instalable
On Mon, 24 Feb 2020 10:14:54 +0100 Eric Valette wrote: > digikam > digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot open shared object file: No such file or directory > > Has already been reported. Did you just copy the error message from there, or did this error come up with the package from experimental installed? > But in addition, > > LANG="C" apt-get -t experimental install libhdf5-hl-100 That package isn't in experimental, so the error you get is entirely expected. Digikam in experimental (4:7.0.0~beta2+dfsg-1) does depend on hdf, but a different version: i digikam Depends digikam-private-libs (= 4:7.0.0~beta2+dfsg-1) i A digikam-private-libs Depends libopencv-imgcodecs4.2 (>= 4.2.0+dfsg) i A libopencv-imgcodecs4.2 Depends libgdal26 (>= 2.0.1) i A libgdal26 Depends libhdf5-103 The error message you quote refers to so-version 100, while the required one is 103. That suggests you aren't running the digikam binary from the package, but something else (maybe you self-compiled at some point?). Check the output of which digikam.
Bug#952224: marked as done (node-sinon: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 24 Feb 2020 09:50:15 + with message-id and subject line Bug#952224: fixed in node-sinon 8.1.0+ds-2 has caused the Debian Bug report #952224, regarding node-sinon: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test 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.) -- 952224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-sinon Version: 8.1.0+ds-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-sinon > dpkg-buildpackage: info: source version 8.1.0+ds-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Xavier Guimard > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with nodejs >dh_auto_clean --buildsystem=nodejs > rm -rf ./node_modules/.cache > rm -rf bane/node_modules/.cache > rm -rf just-extend/node_modules/.cache > rm -rf nise/node_modules/.cache > rm -rf sinonjscommons/node_modules/.cache > rm -rf sinonjsformatio/node_modules/.cache > rm -rf sinonjsreferee/node_modules/.cache > rm -rf sinonjsreferee-sinon/node_modules/.cache > rm -rf sinonjssamsam/node_modules/.cache > rm -rf sinonjstext-encoding/node_modules/.cache >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-bane.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-just-extend.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-nise.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-sinonjscommons.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-sinonjsformatio.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-sinonjsreferee-sinon.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-sinonjsreferee.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-sinonjssamsam.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig-sinonjstext-encoding.tar.xz > dpkg-source: info: building node-sinon using existing > ./node-sinon_8.1.0+ds.orig.tar.xz > dpkg-source: info: building node-sinon in node-sinon_8.1.0+ds-1.debian.tar.xz > dpkg-source: info: building node-sinon in node-sinon_8.1.0+ds-1.dsc > debian/rules binary > dh binary --with nodejs >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > mkdir node_modules > ln -s ../bane node_modules/bane > ln -s ../just-extend node_modules/just-extend > ln -s ../nise node_modules/nise > mkdir -p node_modules/\@sinonjs > ln -s ../../sinonjscommons node_modules/\@sinonjs/commons > ln -s ../../sinonjsformatio node_modules/\@sinonjs/formatio > ln -s ../../sinonjsreferee node_modules/\@sinonjs/referee > ln -s ../../sinonjsreferee-sinon node_modules/\@sinonjs/referee-sinon > ln -s ../../sinonjssamsam node_modules/\@sinonjs/samsam > ln -s ../../sinonjstext-encoding node_modules/\@sinonjs/text-encoding >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > /bin/sh -e debian/tests/pkg-js/test > > > assert > ✓ is object > ✓ supports proxy property > .fail > ✓ throws exception > ✓ throws configured exception type > with stubs > .match > ✓ fails when arguments to not match > ✓ passes when argumens match > .called > ✓ should fail with non-function fake > ✓ fails when method does not exist > ✓ fails when method is not stub > ✓ fails when method was not called > ✓ fails w
Bug#951329: FTBFS in buster with linux-source-4.19 4.19.98-1
Sorry. I hadn't realized that you already had MRs on Salsa. But I wasn't aware of the extra configuration needed for notifications. Please go ahead with the upload. Thanks, Ritesh On Mon, 2020-02-24 at 15:16 +0530, Ritesh Raj Sarraf wrote: > Hi Santiago, > > Do you have the MR ready ? > > Your bug report against the package in Buster has caused a trigger to > auto-remove UML from Debian Testing. I don't know how removing the > package from testing solves any problem with the package in Buster. > > > If you have the MR done, can we please get it merged and get done > with > this bug report ? > > Thanks, > Ritesh -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#952201: marked as done (node-type-check: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 24 Feb 2020 10:08:37 +
with message-id
and subject line Bug#952201: fixed in node-type-check 0.3.2+dfsg-3
has caused the Debian Bug report #952201,
regarding node-type-check: FTBFS: dh_auto_test: error: /bin/sh -e
debian/tests/pkg-js/test 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.)
--
952201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-type-check
Version: 0.3.2+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p lib/
> /usr/bin/lsc --compile --output lib "src/check.ls"
> /usr/bin/lsc --compile --output lib "src/index.ls"
> /usr/bin/lsc --compile --output lib "src/parse-type.ls"
> /usr/bin/lsc --compile package.json.ls
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> /bin/sh -e debian/tests/pkg-js/test
> mocha inspect [spec..]
>
> Run tests with Mocha
>
> Rules & Behavior
> --allow-uncaught Allow uncaught errors to propagate
> [boolean]
> --async-only, -A Require all tests to use a callback (async) or
> return a Promise
> [boolean]
> --bail, -b Abort ("bail") after first test failure
> [boolean]
> --check-leaks Check for global variable leaks
> [boolean]
> --delayDelay initial execution of root suite
> [boolean]
> --exit Force Mocha to quit after tests complete
> [boolean]
> --forbid-only Fail if exclusive test(s) encountered
> [boolean]
> --forbid-pending Fail if pending test(s) encountered
> [boolean]
> --global, --globalsList of allowed global variables
> [array]
> --retries Retry failed tests this many times
> [number]
> --slow, -s Specify "slow" test threshold (in milliseconds)
> [string] [default:
> 75]
> --timeout, -t, --timeouts Specify test timeout threshold (in milliseconds)
> [string] [default:
> 2000]
> --ui, -u Specify user interface[string] [default:
> "bdd"]
>
> Reporting & Output
> --color, -c, --colors Force-enable color output
> [boolean]
> --diffShow diff on failure
>[boolean] [default:
> true]
> --full-trace Display full stack traces
> [boolean]
> --growl, -G Enable Growl notifications
> [boolean]
> --inline-diffsDisplay actual/expected
> differences
> inline within each string
> [boolean]
> --reporter, -RSpecify reporter to use
> [string] [default:
> "spec"]
> --reporter-option, --reporter-options,Reporter-specific options
> -O()
> [array]
>
> Configuration
> --config Path to config file [string] [default: (nearest rc
> file)]
> --opts Path to `mocha.opts` (DEPRECATED)
> [string] [default:
> "./test/mocha.opts"]
> --package Path to package.json for config
> [string]
>
> File Handling
> --extension File extension(s) to load [array] [default:
> js]
> --file Specify file(s) to be loaded prior to root suite
>execution [array] [default:
> (none)]
> --ignore, --exclude Ignore file(s) or glob pattern(s)
>[array] [default:
> (none)]
> --recursive Look for tests in subdirectories
> [boolean]
> --require, -rRequire module [array] [default:
> (none)]
> --sort, -S Sort test files
> [boolean]
> --watch, -w Watch files in the current working directory for
> changes
>
Bug#952158: marked as done (pkwalify: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Mon, 24 Feb 2020 10:09:32 + with message-id and subject line Bug#952158: fixed in pkwalify 1.23-1 has caused the Debian Bug report #952158, regarding pkwalify: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2 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.) -- 952158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pkwalify Version: 1.22.99~git3d3f0ea-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/compat.t ... > 1..2 > # Running under perl version 5.03 for linux > # Current time local: Sun Feb 23 02:53:08 2020 > # Current time GMT: Sun Feb 23 02:53:08 2020 > # Using Test.pm version 1.31 > ok 1 > ok 2 > ok > [/mapping/recursive_hash/name] Expected subschema (a hash) > # Looks like your test exited with 2 just after 38. > t/Kwalify.t .. > 1..100 > ok 1 - use Kwalify; > ok 2 - use Schema::Kwalify; > ok 3 - sequence of str > ok 4 - sequence with default type (str) > ok 5 - Non valid data, int in sequence of str > ok 6 > ok 7 - mapping > ok 8 - invalid mapping > ok 9 > ok 10 > ok 11 > ok 12 - sequence of mapping > ok 13 > ok 14 > ok 15 > ok 16 > ok 17 - mapping of sequence > ok 18 > ok 19 > ok 20 > ok 21 - Many rules > ok 22 > ok 23 > ok 24 > ok 25 > ok 26 > ok 27 > ok 28 > ok 29 > ok 30 > ok 31 > ok 32 > ok 33 - unique > ok 34 > ok 35 > ok 36 > ok 37 > ok 38 > Dubious, test returned 2 (wstat 512, 0x200) > Failed 62/100 subtests > t/pkwalify.t . > 1..31 > ok 1 - No warnings in -f /<>/t/testdata/schema05.yaml > /<>/t/testdata/document05a.yaml > ok 2 - Nothing in STDERR > ok 3 - -f /<>/t/testdata/schema05.yaml > /<>/t/testdata/document05a.yaml > ok 4 - There are warnings in -f /<>/t/testdata/schema05.yaml > /<>/t/testdata/document05b.yaml > ok 5 - Nothing in STDERR > ok 6 - -f /<>/t/testdata/schema05.yaml > /<>/t/testdata/document05b.yaml > ok 7 - There are warnings in -f /tmp/QV38FfTp6i.yaml > /<>/t/testdata/document05a.yaml > ok 8 - Nothing in STDERR > ok 9 - -f /tmp/QV38FfTp6i.yaml /<>/t/testdata/document05a.yaml > ok 10 - There are warnings in -f /<>/t/testdata/schema05.yaml > /tmp/6JFDIqePS6.yaml > ok 11 - Nothing in STDERR > ok 12 - -f /<>/t/testdata/schema05.yaml /tmp/6JFDIqePS6.yaml > ok 13 - No warnings in -f /<>/t/testdata/schema05.yaml > /tmp/FJpq_6CJwN.yaml > ok 14 - Nothing in STDERR > ok 15 - -f /<>/t/testdata/schema05.yaml /tmp/FJpq_6CJwN.yaml > ok 16 - There are warnings in -f /<>/t/testdata/schema05.yaml > /tmp/tMs89tttnt.yaml > ok 17 - Nothing in STDERR > ok 18 - -f /<>/t/testdata/schema05.yaml /tmp/tMs89tttnt.yaml > ok 19 - No success without options > ok 20 - usage -f > ok 21 - Invalid option > ok 22 - got usage > ok 23 - Missing data file > ok 24 - usage datafile > ok 25 - No YAML/JSON file > ok 26 - cannot parse file > ok 27 - Success with -s > ok 28 - silent output > ok 29 - Success without -s > ok 30 - non-silent output for validity > ok 31 - /<>/t/../blib/script/pkwalify compiles OK > ok > t/required-no.t .. > 1..1 > ok 1 > ok > > Test Summary Report > --- > t/Kwalify.t(Wstat: 512 Tests: 38 Failed: 0) > Non-zero exit status: 2 > Parse errors: Bad plan. You planned 100 tests but ran 38. > Files=4, Tests=72, 1 wallclock secs ( 0.03 usr 0.00 sys + 0.42 cusr 0.07 > csys = 0.52 CPU) > Result: FAIL > Failed 1/4 test programs. 0/72 subtests failed. > make[1]: *** [Makefile:852: test_dynamic] Error 255 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/pkwalify_1.22.99~git3d3f0ea-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: pkwalify Source-Version: 1.23-1 Done: Victor Seva We believe that the bug you reported
Processed: Re: libgpiod: ftbfs; needs explicit dependency on dh-python
Processing commands for cont...@bugs.debian.org: > tags 949919 + fixed pending Bug #949919 [src:libgpiod] libgpiod: ftbfs; needs explicit dependency on dh-python Added tag(s) pending and fixed. > End of message, stopping processing here. Please contact me if you need assistance. -- 949919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951994: marked as done (ayatana-indicator-messages: FTBFS: im-accounts-service.c:63:13: error: G_ADD_PRIVATE [-Werror])
Your message dated Mon, 24 Feb 2020 10:19:21 + with message-id and subject line Bug#951994: fixed in ayatana-indicator-messages 0.6.1-1 has caused the Debian Bug report #951994, regarding ayatana-indicator-messages: FTBFS: im-accounts-service.c:63:13: error: G_ADD_PRIVATE [-Werror] 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.) -- 951994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ayatana-indicator-messages Version: 0.6.0-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/accountsservice-1.0 -I../common -Wall > -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -Werror > -Wno-error=deprecated-declarations > -DG_LOG_DOMAIN=\"Ayatana-Indicator-Messages\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o > ayatana_indicator_messages_service-im-accounts-service.o `test -f > 'im-accounts-service.c' || echo './'`im-accounts-service.c > im-accounts-service.c: In function ‘im_accounts_service_class_init’: > im-accounts-service.c:54:2: warning: ‘g_type_class_add_private’ is deprecated > [-Wdeprecated-declarations] >54 | g_type_class_add_private (klass, sizeof (ImAccountsServicePrivate)); > | ^~~~ > In file included from /usr/include/glib-2.0/gobject/gobject.h:24, > from /usr/include/glib-2.0/gobject/gbinding.h:29, > from /usr/include/glib-2.0/glib-object.h:23, > from > /usr/include/accountsservice-1.0/act/act-user-enum-types.h:7, > from /usr/include/accountsservice-1.0/act/act.h:24, > from im-accounts-service.c:24: > /usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here > 1308 | void g_type_class_add_private (gpointer > g_class, > | ^~~~ > im-accounts-service.c: In function ‘im_accounts_service_init’: > im-accounts-service.c:63:13: error: G_ADD_PRIVATE [-Werror] >63 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(self); > | ^~~ > im-accounts-service.c: In function ‘im_accounts_service_dispose’: > im-accounts-service.c:81:13: error: G_ADD_PRIVATE [-Werror] >81 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(object); > | ^~~ > im-accounts-service.c: In function ‘user_changed’: > im-accounts-service.c:107:13: error: G_ADD_PRIVATE [-Werror] > 107 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); > | ^~~ > im-accounts-service.c: In function ‘security_privacy_ready’: > im-accounts-service.c:138:13: error: G_ADD_PRIVATE [-Werror] > 138 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); > | ^~~ > im-accounts-service.c: In function ‘on_user_manager_loaded’: > im-accounts-service.c:149:13: error: G_ADD_PRIVATE [-Werror] > 149 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data); > | ^~~ > im-accounts-service.c: In function ‘im_accounts_service_set_draws_attention’: > im-accounts-service.c:183:13: error: G_ADD_PRIVATE [-Werror] > 183 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(service); > | ^~~ > im-accounts-service.c: In function ‘im_accounts_service_get_show_on_greeter’: > im-accounts-service.c:209:13: error: G_ADD_PRIVATE [-Werror] > 209 | ImAccountsServicePrivate * priv = > IM_ACCOUNTS_SERVICE_GET_PRIVATE(service); > | ^~~ > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/accountsservice-1.0 -I../common -Wall > -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -Werror > -Wno-error=deprecated-declarations > -DG_LOG_DOMAIN=\"Ayatana-Indicator-Messages\" -g -O2 > -fdebug-prefix-map=/<>=. -
Bug#952428: Security flaws in CSRF prevention
package: sympa
severity: critical
version: 6.2.40~dfsg-3
tags: patch
A vulnerability has been discovered in Sympa web interface that can
cause denial of service (DoS) attack.
By submitting requests with malformed parameters, this flaw allows to
create junk files in Sympa's directory for temporary files. And
particularly by tampering token to prevent CSRF, it allows to originate
excessive notification messages to listmasters.
Full advisory:
https://sympa-community.github.io/security/2020-001.html
Regards
Racke
--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.
From 9b86fb3f0337d70221d63392db7d1a52b439dc8f Mon Sep 17 00:00:00 2001
From: IKEDA Soji
Date: Tue, 11 Feb 2020 17:52:22 +0900
Subject: [PATCH] Sympa SA 2020-001 (candidate). Denial of service caused by
malformed CSRF token.
---
src/cgi/wwsympa.fcgi.in | 25 +++--
1 file changed, 3 insertions(+), 22 deletions(-)
diff --git a/src/cgi/wwsympa.fcgi.in b/src/cgi/wwsympa.fcgi.in
index 2eb8aec..c7b5195 100644
--- a/src/cgi/wwsympa.fcgi.in
+++ b/src/cgi/wwsympa.fcgi.in
@@ -992,9 +992,6 @@ our %in_regexp = (
# Role
'role' => 'member|editor|owner',
-
-## CSRF token is a lower case MD5 hash
-'csrftoken' => '^[0-9a-f]{32}$',
);
## Regexp applied on incoming parameters (%in)
@@ -1262,8 +1259,6 @@ while ($query = CGI::Fast->new) {
# affected to another anonymous session.
undef $ENV{'HTTP_COOKIE'};
unless (defined $session) {
-Sympa::send_notify_to_listmaster($robot,
-'failed_to_create_web_session', {});
wwslog('info', 'Failed to create session');
$session = Sympa::WWW::Session->new($robot, {});
}
@@ -2149,32 +2144,18 @@ sub get_parameters {
if ($one_p !~ /^$regexp$/s
|| (defined $negative_regexp && $one_p =~ /$negative_regexp/s)
) {
-## Dump parameters in a tmp file for later analysis
-my $dump_file =
- Conf::get_robot_conf($robot, 'tmpdir')
-. '/sympa_dump.'
-. time . '.'
-. $PID;
-unless (open DUMP, ">$dump_file") {
-wwslog('err', 'Failed to create %s: %s',
-$dump_file, $ERRNO);
-}
-Sympa::Tools::Data::dump_var(\%in, 0, \*DUMP);
-close DUMP;
-
Sympa::WWW::Report::reject_report_web('user', 'syntax_errors',
{p_name => $p},
'', '');
wwslog(
'err',
-'Syntax error for parameter %s value "%s" not conform to regexp:%s; dumped vars in %s',
+'Syntax error for parameter %s value "%s" not conform to regexp:%s',
$pname,
$one_p,
-$regexp,
-$dump_file
+$regexp
);
$in{$p} = '';
-next;
+last;
}
}
}
--
1.8.3.1
signature.asc
Description: OpenPGP digital signature
Bug#952426: digikam: digkam experimental not correctly instalable
On 24/02/2020 10:50, Simon Frei wrote: Did you just copy the error message from there, or did this error come up with the package from experimental installed? The experimental version installed type digikam digikam est /usr/bin/digikam valette@tri-yann4:~$ digikam --version digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot open shared object file: No such file or directory valette@tri-yann4:~$ dpkg -S /usr/bin/digikam digikam: /usr/bin/digikam apt-cache policy digikam digikam: Installé : 4:7.0.0~beta2+dfsg-1 Candidat : 4:7.0.0~beta2+dfsg-1 Table de version : *** 4:7.0.0~beta2+dfsg-1 100 1 http://ftp.fr.debian.org/debian experimental/main amd64 Packages 100 /var/lib/dpkg/status 4:6.4.0+dfsg-3 500 500 http://ftp.fr.debian.org/debian unstable/main amd64 Packages valette@tri-yann4:~$ dpkg -s digikam Package: digikam Status: install ok installed Priority: optional Section: kde Installed-Size: 4048 Maintainer: Debian KDE Extras Team Architecture: amd64 Version: 4:7.0.0~beta2+dfsg-1 Depends: digikam-private-libs (= 4:7.0.0~beta2+dfsg-1), libc6 (>= 2.14), libgcc-s1 (>= 3.0), libkf5configcore5 (>= 4.97.0), libkf5coreaddons5 (>= 4.100.0), libkf5i18n5 (>= 4.97.0), libmagick++-6.q16-8, libqt5core5a (>= 5.12.2), libqt5gui5 (>= 5.4.0) | libqt5gui5-gles (>= 5.4.0), libqt5sql5 (>= 5.4.0), libqt5widgets5 (>= 5.4.0), libstdc++6 (>= 4.1.1), perl:any, libqt5sql5-sqlite, libqt5sql5-mysql, digikam-data (= 4:7.0.0~beta2+dfsg-1) Recommends: www-browser, ffmpegthumbs Suggests: digikam-doc, systemsettings Description: digital photo management application for KDE Digital photo management program designed to import, organize, enhance, search and export your digital images to and from your computer. . It provides a simple interface which makes importing and organizing digital photographs a "snap". digiKam enables you to manage large numbers of digital photographs in albums and to organize these photographs for easy retrieval using tags (keywords), captions, collections, dates, geolocation and searches. It has many features for viewing, organizing, processing and sharing your images. Thus, digiKam is a formidable digital asset management (DAM) software including powerful image editing functions. . An easy-to-use camera interface is provided, that will connect to your digital camera and download photographs directly into digiKam albums. More than 1000 digital cameras are supported by the gphoto2 library. Of course, any media or card reader supported by your operating system will interface with digiKam. . digiKam incorporates a fast Image Editor with many image editing tools. You can use the Image Editor to view your photographs, comment and rate them, correct, enhance and alter them. The editing power can be easily extended by a set of plugins, the KDE Image Plugins Interface (manual) . While digiKam remains easy to use, it provides professional level features by the dozens. It is fully 16 bit enabled including all available plugins, supports RAW format conversion through libraw, DNG export and ICC color management work flow. Homepage: http://www.digikam.org The error message you quote refers to so-version 100, while the required one is 103. That suggests you aren't running the digikam binary from the package, but something else (maybe you self-compiled at some point?). Check the output of which digikam. Did you just test your packages before uploading? ldd /usr/bin/digikam | grep libhd libhdf5_serial.so.103 => /usr/lib/x86_64-linux-gnu/libhdf5_serial.so.103 (0x7fd2c60f2000) libhdf5_serial_hl.so.100 => not found This bug has already been reported by me and fixed for 6.4 --eric
Bug#939455: marked as done (link-grammar fails the autopkg tests (unrecognized gcc option))
Your message dated Mon, 24 Feb 2020 11:48:59 +0100 with message-id and subject line Fixed in 5.7.0-2 has caused the Debian Bug report #939455, regarding link-grammar fails the autopkg tests (unrecognized gcc option) 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.) -- 939455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:link-grammar Version: 5.6.2-1 Severity: serious Tags: sid bullseye as seen at https://ci.debian.net/data/autopkgtest/testing/amd64/l/link-grammar/2887534/log.gz autopkgtest [20:20:24]: test unit-tests: - - - - - - - - - - results - - - - - - - - - - unit-tests FAIL stderr: cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ autopkgtest [20:20:24]: test unit-tests: - - - - - - - - - - stderr - - - - - - - - - - cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ autopkgtest [20:20:24]: summary unit-tests FAIL stderr: cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ --- End Message --- --- Begin Message --- Version: 5.7.0-2--- End Message ---
Bug#952243: marked as done (jmodeltest: FTBFS: ! LaTeX Error: File `letltxmacro.sty' not found.)
Your message dated Mon, 24 Feb 2020 11:08:22 + with message-id and subject line Bug#952243: fixed in jmodeltest 2.1.10+dfsg-8 has caused the Debian Bug report #952243, regarding jmodeltest: FTBFS: ! LaTeX Error: File `letltxmacro.sty' 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.) -- 952243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jmodeltest Version: 2.1.10+dfsg-7 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > ant -Duser.name debian > Buildfile: /<>/build.xml > > compile: > [mkdir] Created dir: /<>/build/classes > [javac] Compiling 75 source files to /<>/build/classes > [javac] warning: [path] bad path element "/usr/share/java/xalan.jar": no > such file or directory > [javac] warning: [path] bad path element > "/usr/share/java/AbsoluteLayout.jar": no such file or directory > [javac] warning: [options] bootstrap class path not set in conjunction > with -source 6 > [javac] warning: [options] source value 6 is obsolete and will be removed > in a future release > [javac] warning: [options] target value 1.6 is obsolete and will be > removed in a future release > [javac] warning: [options] To suppress warnings about obsolete options, > use -Xlint:-options. > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/Distributor.java:23: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhymlMPJ.java:24: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhymlMPJ.java:25: > warning: [deprecation] Observer in java.util has been deprecated > [javac] import java.util.Observer; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhyml.java:28: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhyml.java:29: > warning: [deprecation] Observer in java.util has been deprecated > [javac] import java.util.Observer; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/MultipleDistributor.java:24: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhymlHybrid.java:24: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhymlHybrid.java:25: > warning: [deprecation] Observer in java.util has been deprecated > [javac] import java.util.Observer; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/PhymlParallelModel.java:23: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/PhymlParallelModel.java:24: > warning: [deprecation] Observer in java.util has been deprecated > [javac] import java.util.Observer; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/PhymlSingleModel.java:24: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhymlClustering.java:22: > warning: [deprecation] Observable in java.util has been deprecated > [javac] import java.util.Observable; > [javac] ^ > [javac] > /<>/src/main/java/es/uvigo/darwin/jmodeltest/exe/RunPhymlClustering.java:23: > warning: [deprecation] Observer in java.util has been deprecated > [javac] import java.util.Observer; > [javac]
Bug#952248: marked as done (libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 24 Feb 2020 11:08:29 + with message-id and subject line Bug#952248: fixed in libbpp-popgen 2.4.1-3 has caused the Debian Bug report #952248, regarding libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 952248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-popgen Version: 2.4.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > --> libbpp-seq-dev package exists. > set -e > install -d -m 755 debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.a > debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so > debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8 > debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > mv > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8.0.0 > debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-popgen-dev > PKGSHL=libbpp-popgen8 > install -d -m 755 debian/libbpp-popgen-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-popgen-dev/usr/include > install -d -m 755 debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz >dh_strip >dh_makeshlibs > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-popgen8/DEBIAN/symbols doesn't match > completely debian/libbpp-popgen8.symbols.amd64 > --- debian/libbpp-popgen8.symbols.amd64 (libbpp-popgen8_2.4.1-2_amd64) > +++ dpkg-gensymbolstUa40O 2020-02-23 02:45:26.493958486 + > @@ -910,8 +910,8 @@ > > _ZNSt5dequeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base > 2.4.1 > > _ZNSt6vectorIN3bpp19GeneMapperCsvExport6AlleleESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base > 2.4.1 > > _ZNSt6vectorIN3bpp9LocusInfoESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base > 2.4.1 > - _ZNSt6vectorIN3bpp9LocusInfoESaIS1_EED1Ev@Base 2.4.1 > - _ZNSt6vectorIN3bpp9LocusInfoESaIS1_EED2Ev@Base 2.4.1 > +#MISSING: 2.4.1-2# _ZNSt6vectorIN3bpp9LocusInfoESaIS1_EED1Ev@Base 2.4.1 > +#MISSING: 2.4.1-2# _ZNSt6vectorIN3bpp9LocusInfoESaIS1_EED2Ev@Base 2.4.1 > > _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base > 2.4.1 > > _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_default_appendEm@Base > 2.4.1 > > _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base > 2.4.1 > dh_makeshlibs: error: failing due to earlier errors > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/02/22/libbpp-popgen_2.4.1-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: libbpp-popgen Source-Version: 2.4.1-3 Done: Andreas Tille We believe that the bug you repo
Bug#951991: bali-phy: FTBFS: detected.hpp:52:7: error: invalid use of incomplete type ‘struct nlohmann::detail::detector
Control: tags -1 upstream
Control: forwarded -1 Benjamin Redelings
Hi Benjamin,
can you please have a look?
Thanks a lot
Andreas.
On Sun, Feb 23, 2020 at 08:31:45AM +0100, Lucas Nussbaum wrote:
> Source: bali-phy
> Version: 3.4.1+dfsg-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: buster sid
> Usertags: ftbfs-20200222 ftbfs-buster
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > c++ -Isrc/25a6634@@bali-phy@exe -Isrc -I../src -I. -I../
> > -I/usr/include/eigen3 -fdiagnostics-color=always -pipe
> > -D_FILE_OFFSET_BITS=64 -std=c++14 -DHAVE_CONFIG_H -Wall -Wextra
> > -Wno-sign-compare -Woverloaded-virtual -Wstrict-aliasing
> > -Wno-unknown-pragmas -Wno-maybe-uninitialized -DNDEBUG -DNDEBUG_DP -O3
> > -funroll-loops -ffast-math -g -O2 -fdebug-prefix-map=/<>=.
> > -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time
> > -D_FORTIFY_SOURCE=2 -MD -MQ 'src/25a6634@@bali-phy@exe/util_ptree.cc.o' -MF
> > 'src/25a6634@@bali-phy@exe/util_ptree.cc.o.d' -o
> > 'src/25a6634@@bali-phy@exe/util_ptree.cc.o' -c ../src/util/ptree.cc
> > In file included from /usr/include/nlohmann/detail/meta/type_traits.hpp:11,
> > from
> > /usr/include/nlohmann/detail/conversions/from_json.hpp:19,
> > from /usr/include/nlohmann/adl_serializer.hpp:5,
> > from /usr/include/nlohmann/json.hpp:51,
> > from ../src/util/json.hh:3,
> > from ../src/util/ptree.H:12,
> > from ../src/util/ptree.cc:1:
> > /usr/include/nlohmann/detail/meta/detected.hpp: In substitution of
> > ‘template class Op, class ... Args>
> > using is_detected_exact = std::is_same > nlohmann::detail::detector > ...>::type> [with Expected = void; Op = nlohmann::detail::to_json_function;
> > Args = {nlohmann::basic_json<>::json_serializer,
> > nlohmann::basic_json > std::__cxx11::basic_string,
> > std::allocator >, bool, long int, long unsigned int, double,
> > std::allocator, nlohmann::adl_serializer>&, ptree}]’:
> > /usr/include/nlohmann/detail/meta/type_traits.hpp:121:27: required from
> > ‘constexpr const bool nlohmann::detail::has_to_json,
> > ptree, void>::value’
> > /usr/include/nlohmann/detail/meta/type_traits.hpp:353:27: required from
> > ‘constexpr const bool
> > nlohmann::detail::is_compatible_type_impl, ptree,
> > void>::value’
> > /usr/include/nlohmann/json.hpp:1299:55: required by substitution of
> > ‘template > nlohmann::detail::is_basic_json::value) &&
> > nlohmann::detail::is_compatible_type, U>::value),
> > int>::type >
> > nlohmann::basic_json<>::basic_json(CompatibleType&&) [with CompatibleType =
> > ptree; U = ptree; typename std::enable_if<((!
> > nlohmann::detail::is_basic_json::value) &&
> > nlohmann::detail::is_compatible_type, U>::value),
> > int>::type = ]’
> > /usr/include/c++/9/type_traits:883:12: required from ‘struct
> > std::is_constructible, ptree>’
> > /usr/include/nlohmann/detail/conversions/to_json.hpp:305:123: required by
> > substitution of ‘template > std::enable_if<(std::is_constructible > CompatibleNumberIntegerType>::value && std::is_constructible > T2>::value), int>::type > void
> > nlohmann::detail::to_json(BasicJsonType&, const std::pair<_Tp1, _Tp2>&)
> > [with BasicJsonType = nlohmann::basic_json<>; T1 =
> > std::__cxx11::basic_string; T2 = ptree; typename
> > std::enable_if<(std::is_constructible > CompatibleNumberIntegerType>::value && std::is_constructible > T2>::value), int>::type = ]’
> > /usr/include/nlohmann/detail/conversions/to_json.hpp:335:24: [ skipping
> > 12 instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ]
> > /usr/include/nlohmann/adl_serializer.hpp:43:36: required by substitution
> > of ‘template static decltype
> > ((nlohmann::{anonymous}::to_json(j, forward(val)), void()))
> > nlohmann::adl_serializer::to_json > ValueType>(BasicJsonType&, ValueType&&) [with BasicJsonType =
> > nlohmann::basic_json<>; ValueType = ptree]’
> > /usr/include/nlohmann/detail/meta/detected.hpp:52:7: recursively required
> > by substitution of ‘template class Op,
> > class ... Args> struct nlohmann::detail::detector > nlohmann::detail::make_void >::type, Op, Args ...> [with
> > Default = nlohmann::detail::nonesuch; Op =
> > nlohmann::detail::to_json_function; Args = {nlohmann::adl_serializer > void>, nlohmann::basic_json > std::__cxx11::basic_string,
> > std::allocator >, bool, long int, long unsigned int, double,
> > std::allocator, nlohmann::adl_serializer>&, ptree}]’
> > /usr/include/nlohmann/detail/meta/detected.hpp:52:7: required by
> > substitution of ‘template class Op,
> > class ... Args> using is_detected_exact = std::is_same > nlohmann::detail::detector > ...>::type> [with Expected = void; Op = nlohmann::detail::to_json_function;
> > Args = {nlohmann::basic_json<>::json_serializer,
> > nlohmann::basic_json > std::__cxx11
Bug#952426: digikam: digkam experimental not correctly instalable
On 24/02/2020 11:38, Eric Valette wrote: > On 24/02/2020 10:50, Simon Frei wrote: > >> one is 103. That suggests you aren't running the digikam binary from the >> package, but something else (maybe you self-compiled at some point?). >> Check the output of which digikam. > > > Did you just test your packages before uploading? > > ldd /usr/bin/digikam | grep libhd > libhdf5_serial.so.103 => > /usr/lib/x86_64-linux-gnu/libhdf5_serial.so.103 (0x7fd2c60f2000) > libhdf5_serial_hl.so.100 => not found > Firstly: I don't upload digikam to debian. I am just a user interested in having it packaged and very occasional contributor upstream. By helping to triage and clarify bugs I hope to remove some workload from Steve (uploader), which hopefully makes it more likely to keep getting packages from him (thanks a lot for that!). And my bad, apparently libhdf5-103 still ships the .100 lib: libhdf5-103: /usr/lib/x86_64-linux-gnu/libhdf5_serial_hl.so.100 At least it does in testing. I now upgraded libhdf5-103 to experimental and I do get the same error you do. Maybe at the time the experimental build was done the old version of hdf5 was still in experimental. Anyway the fix for you is to downgrade libhdf5-103 to unstable and for the package probably as simple as a rebuild (which in my opinion isn't really necessary unless there's another change, e.g. beta3).
Processed: Re: Bug#951991: bali-phy: FTBFS: detected.hpp:52:7: error: invalid use of incomplete type ‘struct nlohmann::detail::detector
Processing control commands: > tags -1 upstream Bug #951991 [src:bali-phy] bali-phy: FTBFS: detected.hpp:52:7: error: invalid use of incomplete type ‘struct nlohmann::detail::detector, nlohmann::basic_json, std::allocator >, bool, long int, long unsigned int, double, std::allocator, nlohmann::adl_serializer>&, ptree>’ Added tag(s) upstream. > forwarded -1 Benjamin Redelings Bug #951991 [src:bali-phy] bali-phy: FTBFS: detected.hpp:52:7: error: invalid use of incomplete type ‘struct nlohmann::detail::detector, nlohmann::basic_json, std::allocator >, bool, long int, long unsigned int, double, std::allocator, nlohmann::adl_serializer>&, ptree>’ Set Bug forwarded-to-address to 'Benjamin Redelings '. -- 951991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952220: marked as done (bcel: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.mu
Your message dated Mon, 24 Feb 2020 11:19:19 + with message-id and subject line Bug#952220: fixed in bcel 6.4.1-1 has caused the Debian Bug report #952220, regarding bcel: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test 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.) -- 952220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bcel Version: 6.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibbcel-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [WARNING] > [WARNING] Some problems were encountered while building the effective model > for org.apache.bcel:bcel:jar:6.3 > [WARNING] 'build.plugins.plugin.version' for > org.apache.felix:maven-bundle-plugin is missing. @ > org.apache.commons:commons-parent:debian, > /<>/debian/maven-repo/org/apache/commons/commons-parent/debian/commons-parent-debian.pom, > line 310, column 12 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they > threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support > building such malformed projects. > [WARNING] > [WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is > missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-site-plugin:3.3: Plugin > org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies > could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2) in offline mode and the artifact > org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded > from it before. > [WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 is > missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin > org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies > could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2) in offline mode and the artifact > org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 has not been downloaded > from it before. > [WARNING] The POM for > org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 is missing, no > dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin > org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its > dependencies could not be resolved: Cannot access central > (https://repo.maven.apache.org/maven2
Processed: retitle 952220 to bcel: FTBFS caused by test failure in BCELifierTestCase.testJavapCompare
Processing commands for cont...@bugs.debian.org:
> retitle 952220 bcel: FTBFS caused by test failure in
> BCELifierTestCase.testJavapCompare
Bug #952220 {Done: Emmanuel Bourg } [src:bcel] bcel: FTBFS:
dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/<>
-Dclassworlds.conf=/etc/maven/m2-debian.conf
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test
returned exit code 1
Changed Bug title to 'bcel: FTBFS caused by test failure in
BCELifierTestCase.testJavapCompare' from 'bcel: FTBFS: dh_auto_test: error:
/usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/<>
-Dclassworlds.conf=/etc/maven/m2-debian.conf
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test
returned exit code 1'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#952351 marked as pending in plexus-build-api
Processing control commands: > tag -1 pending Bug #952351 [src:plexus-build-api] plexus-build-api: FTBFS: [ERROR] /<>/src/main/java/org/sonatype/plexus/build/incremental/EmptyScanner.java:[23,8] org.sonatype.plexus.build.incremental.EmptyScanner is not abstract and does not override abstract method setFilenameComparator(java.util.Comparator) in org.codehaus.plexus.util.Scanner Added tag(s) pending. -- 952351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952351: marked as pending in plexus-build-api
Control: tag -1 pending Hello, Bug #952351 in plexus-build-api reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/plexus-build-api/commit/5a5212d965505bc8fd1861b04bcc5110b2695bb3 Fixed the compatibility with plexus-utils 3.3 (Closes: #952351) (this message was generated automatically) -- Greetings https://bugs.debian.org/952351
Processed: Security flaw found in stable version as well
Processing commands for cont...@bugs.debian.org: > found 952428 6.2.40~dfsg-1 Bug #952428 [sympa] Security flaws in CSRF prevention Marked as found in versions sympa/6.2.40~dfsg-1. > -- Stopping processing here. Please contact me if you need assistance. -- 952428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952328: marked as done (jss: FTBFS: test failed: 58 - SSLClientAuth_FIPSMODE (Failed))
Your message dated Mon, 24 Feb 2020 11:50:29 + with message-id and subject line Bug#952328: fixed in jss 4.6.3-1 has caused the Debian Bug report #952328, regarding jss: FTBFS: test failed: 58 - SSLClientAuth_FIPSMODE (Failed) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 952328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jss Version: 4.6.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd build && ctest --output-on-failure > Test project /<>/build > Start 1: Clean_Data_Dir > 1/66 Test #1: Clean_Data_Dir Passed > 0.01 sec > Start 2: Create_Data_Dir > 2/66 Test #2: Create_Data_Dir ... Passed > 0.01 sec > Start 3: TestBufferPRFD > 3/66 Test #3: TestBufferPRFD Passed > 0.00 sec > Start 4: Clean_Setup_DBs > 4/66 Test #4: Clean_Setup_DBs ... Passed > 0.01 sec > Start 5: Create_Setup_DBs > 5/66 Test #5: Create_Setup_DBs .. Passed > 0.01 sec > Start 6: Setup_DBs > 6/66 Test #6: Setup_DBs . Passed > 0.24 sec > Start 7: Clean_FIPS_Setup_DBs > 7/66 Test #7: Clean_FIPS_Setup_DBs .. Passed > 0.01 sec > Start 8: Create_FIPS_Setup_DBs > 8/66 Test #8: Create_FIPS_Setup_DBs . Passed > 0.01 sec > Start 9: Setup_FIPS_DBs > 9/66 Test #9: Setup_FIPS_DBs Passed > 0.28 sec > Start 10: Test_UTF-8_Converter > 10/66 Test #10: Test_UTF-8_Converter .. Passed > 0.07 sec > Start 11: JSS_DER_Encoding_of_Enumeration_regression_test > 11/66 Test #11: JSS_DER_Encoding_of_Enumeration_regression_test ... Passed > 0.67 sec > Start 12: JSS_Test_DER_Encoding_Functionality > 12/66 Test #12: JSS_Test_DER_Encoding_Functionality ... Passed > 0.05 sec > Start 13: JSS_Test_Empty_DER_Value > 13/66 Test #13: JSS_Test_Empty_DER_Value .. Passed > 0.05 sec > Start 14: BigObjectIdentifier > 14/66 Test #14: BigObjectIdentifier ... Passed > 0.06 sec > Start 15: JSS_Test_PR_FileDesc > 15/66 Test #15: JSS_Test_PR_FileDesc .. Passed > 0.16 sec > Start 16: JSS_Test_Raw_SSL > 16/66 Test #16: JSS_Test_Raw_SSL .. Passed > 0.14 sec > Start 17: JSS_Test_Buffer > 17/66 Test #17: JSS_Test_Buffer ... Passed > 0.15 sec > Start 18: JUnit_BMPStringTest > 18/66 Test #18: JUnit_BMPStringTest ... Passed > 0.37 sec > Start 19: JUnit_IA5StringTest > 19/66 Test #19: JUnit_IA5StringTest ... Passed > 0.34 sec > Start 20: JUnit_PrintableStringTest > 20/66 Test #20: JUnit_PrintableStringTest . Passed > 0.27 sec > Start 21: JUnit_TeletexStringTest > 21/66 Test #21: JUnit_TeletexStringTest ... Passed > 0.28 sec > Start 22: JUnit_UniversalStringTest > 22/66 Test #22: JUnit_UniversalStringTest . Passed > 0.41 sec > Start 23: JUnit_UTF8StringTest > 23/66 Test #23: JUnit_UTF8StringTest .. Passed > 0.31 sec > Start 24: buffer_size_1 > 24/66 Test #24: buffer_size_1 . Passed > 0.00 sec > Start 25: buffer_size_4 > 25/66 Test #25: buffer_size_4 . Passed > 0.00 sec > Start 26: JUnit_ChainSortingTest > 26/66 Test #26: JUnit_ChainSortingTest Passed > 0.29 sec > Start 27: Generate_known_RSA_cert_pair > 27/66 Test #27: Generate_known_RSA_cert_pair .. Passed > 5.39 sec > Start 28: Generate_known_ECDSA_cert_pair > 28/66 Test #28: Generate_known_ECDSA_cert_pair Passed > 0.72 sec > Start 29: Generate_known_DSS_cert_pair > 29/66 Test #29: Generate_known_DSS_c
Bug#952351: marked as done (plexus-build-api: FTBFS: [ERROR] /<>/src/main/java/org/sonatype/plexus/build/incremental/EmptyScanner.java:[23,8] org.sonatype.plexus.build.incremental.EmptySc
Your message dated Mon, 24 Feb 2020 11:51:50 + with message-id and subject line Bug#952351: fixed in plexus-build-api 0.0.7-4 has caused the Debian Bug report #952351, regarding plexus-build-api: FTBFS: [ERROR] /<>/src/main/java/org/sonatype/plexus/build/incremental/EmptyScanner.java:[23,8] org.sonatype.plexus.build.incremental.EmptyScanner is not abstract and does not override abstract method setFilenameComparator(java.util.Comparator) in org.codehaus.plexus.util.Scanner 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.) -- 952351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plexus-build-api Version: 0.0.7-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibplexus-build-api-java --debian-build > --keep-pom-version --maven-repo=/<>/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] < org.sonatype.plexus:plexus-build-api > > > [INFO] Building plexus-build-api 0.0.7 > [INFO] [ jar > ]- > [WARNING] The artifact org.codehaus.plexus:plexus-container-default:jar:1.5.5 > has been relocated to org.codehaus.plexus:plexus-container-default:jar:debian > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > plexus-build-api --- > [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. > build is platform dependent! > [WARNING] Please take a look into the FAQ: > https://maven.apache.org/general.html#encoding-warning > [WARNING] Using platform encoding (UTF-8 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ > plexus-build-api --- > [INFO] Changes detected - recompiling the module! > [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. > build is platform dependent! > [INFO] Compiling 4 source files to /<>/target/classes > Use of target 1.4 is no longer supported, switching to 1.7 > Use of source 1.4 is no longer supported, switching to 1.7 > [INFO] > /<>/src/main/java/org/sonatype/plexus/build/incremental/ThreadBuildContext.java: > > /<>/src/main/java/org/sonatype/plexus/build/incremental/ThreadBuildContext.java > uses unchecked or unsafe operations. > [INFO] > /<>/src/main/java/org/sonatype/plexus/build/incremental/ThreadBuildContext.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /<>/src/main/java/org/sonatype/plexus/build/incremental/EmptyScanner.java:[23,8] > org.sonatype.plexus.build.incremental.EmptyScanner is not abstract and does > not override abstract method > setFilenameComparator(java.util.Comparator) in > org.codehaus.plexus.util.Scanner > [INFO] 1 error > [INFO] - > [INFO] > -
Bug#952426: digikam: digkam experimental not correctly instalable
On 24/02/2020 12:09, Simon Frei wrote: Firstly: I don't upload digikam to debian. I am just a user interested in having it packaged and very occasional contributor upstream. By helping to triage and clarify bugs I hope to remove some workload from Steve (uploader), which hopefully makes it more likely to keep getting packages from him (thanks a lot for that!). Well one way to avoid having bugs is to follow the rules for building using up-to-date packages environment (hdf5 had a version in experimental long before digikam was build and 6.4 build procedure removed the dependency completely) and obviously the automatic shared libs dependencies are wrong as I got the bug twice in raw (5.9 and then 7.0.0) And my bad, apparently libhdf5-103 still ships the .100 lib: libhdf5-103: /usr/lib/x86_64-linux-gnu/libhdf5_serial_hl.so.100 Which by the way is quite curious and probably buggy as well. Note that 6.4 ldd digikam does no even list libhdf5_serial_hl.so.100 or even libhdf5* as dynamic library dependency anymore (if you look at the bug report, Austin mail, that is why I closed it). So the way 7.0.0 has been build is probably based on an old9 build procedure (or the build instruction for 7.0 have changed again At least it does in testing. I now upgraded libhdf5-103 to experimental and I do get the same error you do. Maybe at the time the experimental build was done the old version of hdf5 was still in experimental. No because digikam 67.0.0 appered 2020-02-18. The day it appeared, the bug was present. And https://tracker.debian.org/pkg/hdf5 say a diffrent story about hdf5 in experimental. One could argue that building for experimental does not formally require using experimental version of packages but as soon as someone do an experimental upgrade things go wrong so it is wise to use the packages that are already in experimental even if it can prevent upgrading longer. Anyway the fix for you is to downgrade libhdf5-103 to unstable and for the package probably as simple as a rebuild (which in my opinion isn't really necessary unless there's another change, e.g. beta3). I can rebuild myself indeed, I even build manually digikam in the past but it 1) does not fix the bug for others, 2) If I do not rebuild, I will need to freeze the package as I always do experimental update on a regular basis (if not everyday). -- eric
Bug#952426: digikam: digkam experimental not correctly instalable
On Mon, Feb 24, 2020 at 12:09:58PM +0100, Simon Frei wrote: > On 24/02/2020 11:38, Eric Valette wrote: > > On 24/02/2020 10:50, Simon Frei wrote: > > > >> one is 103. That suggests you aren't running the digikam binary from the > >> package, but something else (maybe you self-compiled at some point?). > >> Check the output of which digikam. > > > > > > Did you just test your packages before uploading? > > > > ldd /usr/bin/digikam | grep libhd > > libhdf5_serial.so.103 => > > /usr/lib/x86_64-linux-gnu/libhdf5_serial.so.103 (0x7fd2c60f2000) > > libhdf5_serial_hl.so.100 => not found > > > Firstly: I don't upload digikam to debian. I am just a user interested > in having it packaged and very occasional contributor upstream. By > helping to triage and clarify bugs I hope to remove some workload from > Steve (uploader), which hopefully makes it more likely to keep getting > packages from him (thanks a lot for that!). > > And my bad, apparently libhdf5-103 still ships the .100 lib: > > libhdf5-103: /usr/lib/x86_64-linux-gnu/libhdf5_serial_hl.so.100 > > At least it does in testing. I now upgraded libhdf5-103 to experimental > and I do get the same error you do. Maybe at the time the experimental > build was done the old version of hdf5 was still in experimental. Anyway > the fix for you is to downgrade libhdf5-103 to unstable and for the > package probably as simple as a rebuild (which in my opinion isn't > really necessary unless there's another change, e.g. beta3). Hi, According to https://packages.debian.org/source/experimental/hdf5 there is a new "libhdf5-hl-100" package in experimental. Looking into it, seems that libhdf5_serial_hl.so.100 has been moved there, so installing that new package should help in experimental. I still wonder what is pulling it during build. Regards, -- Agustin
Bug#951494: marked as pending in procps
Hi Craig, On Tue, 18 Feb 2020 00:34:26 + Craig Small wrote: > Control: tag -1 pending > > Hello, > > Bug #951494 in procps reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/debian/procps/commit/c35a627e92cee8585e5ada867a94c2a6ae8ebcfe > > > Fix symlink to new soname Closes: #951494 > > > (this message was generated automatically) > -- > Greetings > > https://bugs.debian.org/951494 > > can you please upload the above fix? There are several packages that FTBFS because of bug #951494. Or are there reasons for holding back the upload? Thanks+Greets, Mike
Bug#952426: digikam: digkam experimental not correctly instalable
On 24/02/2020 12:57, Agustin Martin wrote: Hi, According to https://packages.debian.org/source/experimental/hdf5 there is a new "libhdf5-hl-100" package in experimental. Looking into it, seems that libhdf5_serial_hl.so.100 has been moved there, so installing that new package should help in experimental. I still wonder what is pulling it during build. Except that if you llok at the beginning of the bug report it cannot be installed in conjunction with digikam. That why I opened this new bug. Thanks for helping anyway. -- eric
Bug#952426: digikam: digkam experimental not correctly instalable
On Mon, Feb 24, 2020 at 11:38:40AM +0100, Eric Valette wrote: > On 24/02/2020 10:50, Simon Frei wrote: > > > The error message you quote refers to so-version 100, while the required > > one is 103. That suggests you aren't running the digikam binary from the > > package, but something else (maybe you self-compiled at some point?). > > Check the output of which digikam. > > Did you just test your packages before uploading? > > ldd /usr/bin/digikam | grep libhd > libhdf5_serial.so.103 => > /usr/lib/x86_64-linux-gnu/libhdf5_serial.so.103 (0x7fd2c60f2000) > libhdf5_serial_hl.so.100 => not found Hi, I think this should have triggered an error at build time. So digikam probably built and installed well at that time. > This bug has already been reported by me and fixed for 6.4 To be honest, it just disappeared for 6.4, bit I could not find an action leading to that. According to "ldd -v /usr/bin/digikam" output digikam 5.9.0 had a dependency on libhdf5_serial_hl.so.100, but 6.4.0 does not. I may have missed it, but I do not see any change on debian/control leading to this change. Not to mention that it seems present again in experimental 7.0. My guess is that digikam is being affected by some obscure dependency changes in the build chain about the libhdf5 stuff and what is pulling it. digikam seems to use this hdf5 stuff if present and not use it otherwise. I wonder what is the benefit of using it, 6.4.0 works without it. Regards, PS: Like Simon, I am just tring to help triaging bug reports and make maintenance easier for real maintainers. -- Agustin
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 952126 + help Bug #952126 [src:emacs-bind-map] emacs-bind-map: FTBFS: Errors while processing: elpa-evil sbuild-build-depends-main-dummy Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 952126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952426: digikam: digkam experimental not correctly instalable
On 24/02/2020 12:47, Agustin Martin wrote: This bug has already been reported by me and fixed for 6.4 To be honest, it just disappeared for 6.4, bit I could not find an action leading to that. According to "ldd -v /usr/bin/digikam" output digikam 5.9.0 had a dependency on libhdf5_serial_hl.so.100, but 6.4.0 does not. I may have missed it, but I do not see any change on debian/control leading to this change. Not to mention that it seems present again in experimental 7.0. As bug that you do not understand why it is fixed has good chance to reappear at the worse moment ;-) My guess is that digikam is being affected by some obscure dependency changes in the build chain about the libhdf5 stuff and what is pulling it. digikam seems to use this hdf5 stuff if present and not use it otherwise. I wonder what is the benefit of using it, 6.4.0 works without it. Probably because the symbol table was correctly upgraded... This is what does the dependency utimately. -- eric
Processed: Re: Bug#952007: veyon: FTBFS: ld: final link failed: bad value
Processing control commands: > reassign -1 libprocps-dev Bug #952007 [src:veyon] veyon: FTBFS: ld: final link failed: bad value Bug reassigned from package 'src:veyon' to 'libprocps-dev'. No longer marked as found in versions veyon/4.3.1+repack1-2. Ignoring request to alter fixed versions of bug #952007 to the same values previously set > forcemerge 951494 -1 Bug #951494 [libprocps-dev] libprocps-dev: dead symlink point to the old soname Bug #952271 [libprocps-dev] apitrace: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libprocps.so', needed by 'glretrace'. Stop. Bug #952007 [libprocps-dev] veyon: FTBFS: ld: final link failed: bad value Severity set to 'grave' from 'serious' Marked as found in versions procps/2:3.3.16-1. Added tag(s) pending and ftbfs. Bug #952271 [libprocps-dev] apitrace: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libprocps.so', needed by 'glretrace'. Stop. Merged 951494 952007 952271 -- 951494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951494 952007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952007 952271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945567: network-manager-strongswan FTBFS: error: G_ADD_PRIVATE
There is a new version 1.4.5-1 on salsa. Apparently it builds fine on Sid. Hopefully my sponsor finds a few minutes for a review.
Bug#952295: marked as pending in freecol
Control: tag -1 pending Hello, Bug #952295 in freecol reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/games-team/freecol/commit/3e56efa7eee3694711a9b1a8e20fb4eb6a74b573 Build-depend on texlive-latex-extra to fix FTBFS. Closes: #952295 (this message was generated automatically) -- Greetings https://bugs.debian.org/952295
Processed: Bug#952295 marked as pending in freecol
Processing control commands: > tag -1 pending Bug #952295 [src:freecol] freecol: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/FreeCol.html" (tried in ., debian/tmp) Added tag(s) pending. -- 952295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952007: veyon: FTBFS: ld: final link failed: bad value
Control: reassign -1 libprocps-dev Control: forcemerge 951494 -1 On So 23 Feb 2020 08:29:45 CET, Lucas Nussbaum wrote: Source: veyon Version: 4.3.1+repack1-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): relocation R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: bad value collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/veyon_4.3.1+repack1-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. This is caused by #951494 in libprocps-dev. Thus, reassigning and force-merging. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpFkHpzuKUES.pgp Description: Digitale PGP-Signatur
Bug#952295: marked as done (freecol: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/FreeCol.html" (tried in ., debian/tmp))
Your message dated Mon, 24 Feb 2020 12:35:46 + with message-id and subject line Bug#952295: fixed in freecol 0.11.6+dfsg2-3 has caused the Debian Bug report #952295, regarding freecol: FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/FreeCol.html" (tried in ., debian/tmp) 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.) -- 952295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freecol Version: 0.11.6+dfsg2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with javahelper --buildsystem=ant >dh_testroot -O--buildsystem=ant >dh_prep -O--buildsystem=ant >dh_auto_install -O--buildsystem=ant >dh_install -O--buildsystem=ant >jh_installjavadoc -O--buildsystem=ant >dh_installdocs -O--buildsystem=ant > dh_installdocs: error: Cannot find (any matches for) "doc/FreeCol.html" > (tried in ., debian/tmp) > > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/02/22/freecol_0.11.6+dfsg2-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: freecol Source-Version: 0.11.6+dfsg2-3 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of freecol, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated freecol 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: Mon, 24 Feb 2020 13:00:43 +0100 Source: freecol Architecture: source Version: 0.11.6+dfsg2-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Closes: 907756 917023 952295 Changes: freecol (0.11.6+dfsg2-3) unstable; urgency=medium . * Switch to debhelper-compat = 12. * Declare compliance with Debian Policy 4.5.0. * Use canonical VCS URI. * Remove get-orig-source target. * Build-depend on texlive-latex-extra to fix FTBFS. (Closes: #952295) * Fix CVE-2018-1000825: XML External Entity (XXE) vulnerability. (Closes: #917023) * valid-appdata.patch: Fix all appstream errors. (Closes: #907756) Checksums-Sha1: 4463eef26a92a123fe99cdbdb1b03c77977bbdb4 2319 freecol_0.11.6+dfsg2-3.dsc 0cfa9bcbfa159145c2ee758fb48b4a25ce89fb31 17464 freecol_0.11.6+dfsg2-3.debian.tar.xz f57353057959e51b7fd6e78aa781b556d97bbd33 12149 freecol_0.11.6+dfsg2-3_amd64.buildinfo Checksums-Sha256: 6105e921418d5468766469edda5994a7c4027bfc77d36bd7a188e4fbb886629a 2319 freecol_0.11.6+dfsg2-3.dsc 76a4d37d141a1f8036218bdd8ce259851e04fcf5e1d8591616cebc9671cf0d06 17464 freecol_0.11.6+dfsg2-3.debian.tar.xz aef683280cd4f9dc230c688d5e49413e968d6b79754373f9a28e7e9315a53db3 12149 freecol_0.11.6+dfsg2-3_amd64.buildinfo Files: 89509d82950e0c9b2c28b33c2c0e7935 2319 games optional freecol_0.11.6+dfsg2-3.dsc 4b9c5c550b7cfd016e14a0b23f0c9eda 17464 games optional freecol_0.11.6+dfsg2-3.debian.tar.xz 16a3636a06e8da715ec29b2aef60b9ff 12149 games optional freecol_0.11.6+dfsg2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl5Tv/hfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkIGUQAIZVhDEg5LuZmzUJ1e/iFiunl2A5gfTi3p4w GA0ewAt/lbKXgDgLgBlFCZXpoZPeuW1JlYnJR/X2uCrVlVCr5dbhiGLZP6I7k0YR jQJHx+4pebTGAqulsMXcxfrs/hfpYx9Le2pfMKMW0lKexOoL9fzs5rnpBAyFuXz0 F/BtGKCXBk8NaKHnIIi/MtFpR52X9C9ss1o8g6+HZYZl8WcibBX
Bug#952013: marked as done (cogl: FTBFS: configure: error: Package requirements ( cairo >= 1.10 gobject-2.0 gmodule-no-export-2.0 gdk-pixbuf-2.0 >= 2.0 wayland-egl >= 1.0.0 wayland-client >= 1.0.0 gbm
Your message dated Mon, 24 Feb 2020 12:49:14 + with message-id and subject line Bug#952013: fixed in cogl 1.22.4-4 has caused the Debian Bug report #952013, regarding cogl: FTBFS: configure: error: Package requirements ( cairo >= 1.10 gobject-2.0 gmodule-no-export-2.0 gdk-pixbuf-2.0 >= 2.0 wayland-egl >= 1.0.0 wayland-client >= 1.0.0 gbm libdrm wayland-server >= 1.1.90 egl x11 xext xfixes >= 3 xdamage xcomposite >= 0.4 xrandr >= 1.2) were not met 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.) -- 952013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cogl Version: 1.22.4-3 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for GNU gettext in libc... yes > checking whether to use NLS... yes > checking where the gettext function comes from... libc > checking for linguas... an ar as ast be bg bs ca ca@valencia cs da de el > en_CA en_GB eo es eu fa fr fur gl he hi hr hu id it ja km kn ko lt lv ml nb > ne nl oc or pa pl pt pt_BR ro ru sk sl sr sr@latin sv ta te th tr ug uk vi > zh_CN zh_HK zh_TW > checking for COGL_DEP... no > configure: error: Package requirements ( cairo >= 1.10 gobject-2.0 > gmodule-no-export-2.0 gdk-pixbuf-2.0 >= 2.0 wayland-egl >= 1.0.0 > wayland-client >= 1.0.0 gbm libdrm wayland-server >= 1.1.90 egl x11 xext > xfixes >= 3 xdamage xcomposite >= 0.4 xrandr >= 1.2) were not met > > No package 'libdrm' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables COGL_DEP_CFLAGS > and COGL_DEP_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/cogl_1.22.4-3_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: cogl Source-Version: 1.22.4-4 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of cogl, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated cogl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2020 11:39:47 + Source: cogl Architecture: source Version: 1.22.4-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 952013 Changes: cogl (1.22.4-4) unstable; urgency=medium . * Team upload * Explicitly build-depend on libdrm-dev on Linux platforms. Presumably this was previously pulled in by some other dependency, but configure.ac checks for it so we should build-depend on it ourselves. (Closes: #952013) * Explicitly build-depend on libegl-dev, libx11-dev, libxext-dev for the same reason. * d/p/Fix-building-against-libglvnd-provided-EGL-headers.patch: Add patch from upstream merge request !17 to fix build when using libglvnd's EGL headers. * d/upstream/metadata: Add * Drop transition for old debug package migration. The -dbg packages were removed before Debian 9 'stretch' (oldstable). * d/copyright: Fix license name syntax for SGI-B-2.0. The file format does not allow spaces in license names, so use the SPDX identifier for this license, moving its formal name into the license text. * d/copyright: Make short license name for debian/* consistent with license grant * d/copyright: Add details of cut-down GLib in deps/.
Bug#950962: Upstream issue number and possible fixes
This is related to a change in json 2.3.0 and has been reported upstream: https://github.com/getsentry/raven-ruby/issues/947 Possible fixes are discussed here: https://github.com/getsentry/raven-ruby/pull/952 https://github.com/getsentry/raven-ruby/pull/946 Seems upstream went with disabling/removing the test. So we can do the same. Regards, Daniel
Processed: reassign 950174 to gvfs-daemons, affects 950174
Processing commands for cont...@bugs.debian.org: > reassign 950174 gvfs-daemons 1.42.2-1 Bug #950174 [udisks2] missing schema files makes udisks monitor crash Bug reassigned from package 'udisks2' to 'gvfs-daemons'. No longer marked as found in versions udisks2/2.8.4-1. Ignoring request to alter fixed versions of bug #950174 to the same values previously set Bug #950174 [gvfs-daemons] missing schema files makes udisks monitor crash Marked as found in versions gvfs/1.42.2-1. > affects 950174 udisks2 Bug #950174 [gvfs-daemons] missing schema files makes udisks monitor crash Added indication that 950174 affects udisks2 > thanks Stopping processing here. Please contact me if you need assistance. -- 950174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950772: Patch: swupdate: FTBFS during separate arch/indep builds
When you take a closer look, please also consider my changes in #911821 (mtd-utils).
Processed: bug 951832 is forwarded to https://github.com/Cacti/cacti/issues/3285
Processing commands for cont...@bugs.debian.org: > forwarded 951832 https://github.com/Cacti/cacti/issues/3285 Bug #951832 [src:cacti] cacti: CVE-2020-8813 Set Bug forwarded-to-address to 'https://github.com/Cacti/cacti/issues/3285'. > thanks Stopping processing here. Please contact me if you need assistance. -- 951832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952435: icingaweb2-module-nagvis: depends on removed nagvis
Source: icingaweb2-module-nagvis Version: 1.1.1-1 Severity: serious Hi Maintainer icingaweb2-module-nagvis has a dependency on nagvis, which was removed from testing, see #851771. Regards Graham
Bug#951329: FTBFS in buster with linux-source-4.19 4.19.98-1
El 24/02/20 a las 15:29, Ritesh Raj Sarraf escribió: > Sorry. I hadn't realized that you already had MRs on Salsa. But I > wasn't aware of the extra configuration needed for notifications. Mmm, maybe I had to continue using the BTS, instead of the MR. At least for communicating with you. > > Please go ahead with the upload. Thanks! I've just filed a bug report against release.d.o to ask for an OK from the RMs. ... > On Mon, 2020-02-24 at 15:16 +0530, Ritesh Raj Sarraf wrote: > > Hi Santiago, > > > > Do you have the MR ready ? > > > > Your bug report against the package in Buster has caused a trigger to > > auto-remove UML from Debian Testing. I don't know how removing the > > package from testing solves any problem with the package in Buster. ... Good question. But anyway, I hope I will be able to upload before the automatic auto-removal deadline. Cheers, - srr signature.asc Description: PGP signature
Bug#945567: new network-manager-strongswan package [and 1 more messages]
Harald Dunkel writes ("Re: new network-manager-strongswan package"):
> https://afaics.de/git/network-manager-strongswan.git
> https://afaics.de/download/
Harald Dunkel writes ("Re: network-manager-strongswan FTBFS: error:
G_ADD_PRIVATE"):
> There is a new version 1.4.5-1 on salsa. Apparently it builds fine
> on Sid. Hopefully my sponsor finds a few minutes for a review.
Hi. For those reading the bug, I'm the sponsor Harald refers to.
I decided to reply here.
I looked at the diff etc. and I have some observations:
* It would be nice to add a Vcs-Git header.
* I noticed you changed the Build-Depends. There is a change to
debhelper, which is expected. But there are also changes to the
network-manager build-dependencies. I looked for some file in
upstream wqher etehse requirements are documented, and/or something
in the debian/changelog to explain or document the change, but
found nothing. Can you please explain ?
* Please can you consider providing an explanation of the patch
glib-private.patch *inside* that patch file. (Ideally patches
should be in git-format-patch format or or DEP-3 format.)
None of these observations look like blockers to me but I would like
to at least ask you for answers before I just upload it.
More on administrativia:
* Since you have already committed your finalised 1.4.5-1 version, it
would be best not to make more commits before bumping the changelog
version again. So, if in response to this review you would like to
make changes, rather than give explanations, please use 1.4.5-2 for
your next revision.
* In future, I am very happy to sponsor directly from git, especially
from salsa. I see we have pristine tar and everything. So just
push your branch (including pristine-tar) to salsa and email me.
There is no need for you to make a dsc and email me attachments.
In my review above I ignored your attachments and just worked with
the git branch (from your private server).
* Indeed, there is no need for you to make a signed tag. Because
salsa is access controlled I feel I can trust it enough for this, at
least as a baseline for review. If you like, feel free to leave the
changelog as UNRELEASED; I am happy to do that change to `unstable'
as part of the upload and push to salsa. If you would like to work
this way, please give user `iwj' access to the repo.
* If it's OK with you I like doing reviews in public. I think a "new
upstream version" bug against the package is a good place because it
means that if either of us drops it, our work is easily available as
a starting point for others.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#952096: marked as done (ukwm: FTBFS: cogl-texture-2d.c:432:43: error: ‘EGL_WAYLAND_BUFFER_WL’ undeclared (first use in this function))
Your message dated Mon, 24 Feb 2020 14:53:59 + with message-id and subject line Bug#952096: fixed in ukwm 1.2.0-1 has caused the Debian Bug report #952096, regarding ukwm: FTBFS: cogl-texture-2d.c:432:43: error: ‘EGL_WAYLAND_BUFFER_WL’ undeclared (first use in this function) 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.) -- 952096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ukwm Version: 1.1.14-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I.. -I.. -I./deprecated -I./winsys -I./driver/gl -I./driver/gl/gl > -I./driver/gl/gles -DG_LOG_DOMAIN=\"Cogl\" -DCOGL_COMPILATION > -DCOGL_GL_LIBNAME=\"libGL.so.1\" -DCOGL_GLES1_LIBNAME=\"\" > -DCOGL_GLES2_LIBNAME=\"\" -DCOGL_LOCALEDIR=\""/usr/share/locale"\" > -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libdrm > -DCOGL_GL_DEBUG -DCOGL_OBJECT_DEBUG -DCOGL_ENABLE_DEBUG -Wall -Wcast-align > -Wformat -Wformat-security -Werror=uninitialized -Werror=empty-body > -Werror=init-self -Werror=undef -Werror=declaration-after-statement > -Werror=vla -Werror=pointer-arith -Werror=missing-declarations > -Werror=maybe-uninitialized -Wno-error=sign-compare -DG_DISABLE_DEPRECATED > -DG_DISABLE_SINGLE_INCLUDES -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > cogl-texture-2d-sliced.lo cogl-texture-2d-sliced.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I./deprecated > -I./winsys -I./driver/gl -I./driver/gl/gl -I./driver/gl/gles > -DG_LOG_DOMAIN=\"Cogl\" -DCOGL_COMPILATION -DCOGL_GL_LIBNAME=\"libGL.so.1\" > -DCOGL_GLES1_LIBNAME=\"\" -DCOGL_GLES2_LIBNAME=\"\" > -DCOGL_LOCALEDIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 > -pthread -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/libdrm -DCOGL_GL_DEBUG -DCOGL_OBJECT_DEBUG -DCOGL_ENABLE_DEBUG > -Wall -Wcast-align -Wformat -Wformat-security -Werror=uninitialized > -Werror=empty-body -Werror=init-self -Werror=undef > -Werror=declaration-after-statement -Werror=vla -Werror=pointer-arith > -Werror=missing-declarations -Werror=maybe-uninitialized > -Wno-error=sign-compare -DG_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c cogl-texture-2d-sliced.c -fPIC -DPIC -o > .libs/cogl-texture-2d-sliced.o > cogl-texture-2d.c: In function ‘cogl_wayland_texture_2d_new_from_buffer’: > cogl-texture-2d.c:394:11: warning: implicit declaration of function > ‘_cogl_egl_query_wayland_buffer’ [-Wimplicit-function-declaration] > 394 | if (_cogl_egl_query_wayland_buffer (ctx, > | ^~ > cogl-texture-2d.c:432:43: error: ‘EGL_WAYLAND_BUFFER_WL’ undeclared (first > use in this function) > 432 | EGL_WAYLAND_BUFFER_WL, > | ^ > cogl-texture-2d.c:432:43: note: each undeclared identifier is reported only > once for each function it appears in > make[7]: *** [Makefile:1457: cogl-texture-2d.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/ukwm_1.1.14-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: ukwm Source-Version: 1.2.0-1 Done: handsome_feng We believe that the bug you reported is fixed in the latest version of ukwm, which is due to be installed in th
Processed: Re: create directory for nfsdcltrack
Processing control commands: > found -1 1.3.4-2.5 Bug #867067 [nfs-kernel-server] nfs-kernel-server: nfsdcltrack fails to init database There is no source info for the package 'nfs-kernel-server' at version '1.3.4-2.5' with architecture '' Unable to make a source version for version '1.3.4-2.5' Marked as found in versions 1.3.4-2.5. > severity -1 grave Bug #867067 [nfs-kernel-server] nfs-kernel-server: nfsdcltrack fails to init database Severity set to 'grave' from 'important' -- 867067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952365: marked as done (zeroinstall-injector: FTBFS: Error: This record expression is expected to have type Migrate_parsetree.Ast_407.Parsetree.pattern The field ppat_loc_stack does not belong to
Your message dated Mon, 24 Feb 2020 15:09:42 +
with message-id
and subject line Re: Bug#952365: zeroinstall-injector: FTBFS: Error: This
record expression is expected to have type
Migrate_parsetree.Ast_407.Parsetree.pattern The field ppat_loc_stack does not
belong to type Migrate_parsetree.Ast_407.Parsetree.pattern menhir
vendor/obus-1.2.0/src/idl/parser.{ml,mli}
has caused the Debian Bug report #952365,
regarding zeroinstall-injector: FTBFS: Error: This record expression is
expected to have type Migrate_parsetree.Ast_407.Parsetree.pattern The field
ppat_loc_stack does not belong to type
Migrate_parsetree.Ast_407.Parsetree.pattern menhir
vendor/obus-1.2.0/src/idl/parser.{ml,mli}
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.)
--
952365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeroinstall-injector
Version: 2.15-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dune build --root=. --profile=release @install
> File "vendor/obus-1.2.0/src/ppx/ppx_obus.ml", line 28, characters 10-232:
> 28 | ..[%stri
> 29 | let () =
> 30 | let module M =
> 31 | Register(struct
> 32 | let name = [%e expr]
> 33 | exception E of [%t typ]
> 34 | end)
> 35 | in ()
> 36 | ]
> Error: This record expression is expected to have type
> Migrate_parsetree.Ast_407.Parsetree.pattern
>The field ppat_loc_stack does not belong to type
> Migrate_parsetree.Ast_407.Parsetree.pattern
> menhir vendor/obus-1.2.0/src/idl/parser.{ml,mli}
> Warning: one state has shift/reduce conflicts.
> Warning: one state has reduce/reduce conflicts.
> Warning: 2 shift/reduce conflicts were arbitrarily resolved.
> make[1]: *** [Makefile:44: all] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/zeroinstall-injector_2.15-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 2.15.1-1
obus is now back in Debian and the new version builds against that,
which fixes the problem.
--
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D 6A51 7513 3C8F 94F6 E0CC--- End Message ---
Bug#951905: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #951905 in qtwebengine-opensource-src reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/qt/qtwebengine/commit/302aa1162348eb0bc5e5502d9870cd5e85f43ad2 Update debian/libqt5webenginecore5.symbols. Some symbols disappeared for unknown reason, probably changes in compiler. Closes: #951905. (this message was generated automatically) -- Greetings https://bugs.debian.org/951905
Processed: Bug#951905 marked as pending in qtwebengine-opensource-src
Processing control commands: > tag -1 pending Bug #951905 [src:qtwebengine-opensource-src] qtwebengine-opensource-src FTBFS: symbols disappeared Added tag(s) pending. -- 951905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 950999 is forwarded to https://github.com/kiokudb/kiokudb/issues/17
Processing commands for cont...@bugs.debian.org: > forwarded 950999 https://github.com/kiokudb/kiokudb/issues/17 Bug #950999 [src:libkiokudb-perl] libkiokudb-perl: FTBFS with recent YAML* packages Set Bug forwarded-to-address to 'https://github.com/kiokudb/kiokudb/issues/17'. > thanks Stopping processing here. Please contact me if you need assistance. -- 950999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950999: libkiokudb-perl: FTBFS with recent YAML* packages
On Sun, 09 Feb 2020 15:44:25 +0100, gregor herrmann wrote: > libkiokudb-perl fails to build (and probably also to run) after the > upgrade of the various YAML* packages which by default stop loading > objects: > http://blogs.perl.org/users/tinita/2020/01/making-yamlpm-yamlsyck-and-yamlxs-safer-by-default.html > > https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkiokudb-perl/4227070/log.gz Now also on cpantesters: http://www.cpantesters.org/cpan/report/e4e0584c-5590-11ea-8652-aa4d1f24ea8f Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#949733: python-pip: 'pip install' don't work for python2 in Debian10
Hi, I've seen this before and I'm fairly sure that it's an issue from the system version of pip interacting badly with a pip-installed version of pip. However, I also cannot reproduce it now. It has been discussed upstream [1] and a compatibility layer has been added to avoid it [2][3]. That may explain why it is seemingly unreproducible now. Instead of the error, I'm now receiving this when running a newer pip-installed version through the system-installed version: WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip. Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue. To avoid this problem you can invoke Python with '-m pip' instead of running pip directly. All in all, I think the error in this bug is likely not caused by the packaged version itself. The wrapper should probably be changed at some point, though. [1] https://github.com/pypa/pip/issues/5599 [2] https://github.com/pypa/pip/issues/7498 [3] https://github.com/pypa/pip/commit/3f4bb75 Regards, Robin
Bug#952173: golang-gopkg-gorethink-gorethink.v3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 returned exit code 1
On Mon, Feb 24, 2020 at 2:33 PM Anthony Fok wrote:
[...]
> + cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4
> +can't load package: package .: no Go files in
> /home/foka/debian/go-team/gopkg/golang-gopkg-gorethink-gorethink.v3/obj-x86_64-linux-gnu
> +dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v
> -p 4 returned exit code 1
> +make[1]: *** [debian/rules:17: override_dh_auto_test] Error 25
>
> And I wonder why other Go packages are apparently not affected by this.
>
> I will continue to investigate and hopefully come up with a fix soon.
I take a look too... but it's too weird...
If you apply this to dh-golang,
diff --git a/lib/Debian/Debhelper/Buildsystem/golang.pm
b/lib/Debian/Debhelper/Buildsystem/golang.pm
index c856f7d..2df380d 100644
--- a/lib/Debian/Debhelper/Buildsystem/golang.pm
+++ b/lib/Debian/Debhelper/Buildsystem/golang.pm
@@ -589,6 +589,7 @@ sub test {
# Go 1.10 started calling “go vet” when running “go test”. This
breaks tests
# of many not-yet-fixed upstream packages, so we disable it for the time
# being.
+my ($minor) = (qx(go version) =~ /go version go1\.([0-9]+)/);
if (_go1_has_minor(10)) {
$this->doit_in_builddir("go", "test", "-vet=off", "-v", @_,
get_targets());
} else {
This package can be built.
But how could this line affect the result.
--
Shengjing Zhu
Bug#945567: new network-manager-strongswan package [and 1 more messages]
Hi Ian, Sorry for the confusion. Of course n-m-s is not in salsa (yet). I was working on mg (my other package) in parallel, which *is* in salsa. On 2/24/20 3:02 PM, Ian Jackson wrote: I looked at the diff etc. and I have some observations: * It would be nice to add a Vcs-Git header. I am OK with this, but I would suggest to wait for the move to salsa, see below. * I noticed you changed the Build-Depends. There is a change to debhelper, which is expected. But there are also changes to the network-manager build-dependencies. I looked for some file in upstream wqher etehse requirements are documented, and/or something in the debian/changelog to explain or document the change, but found nothing. Can you please explain ? The version numbers of the dependencies have been changed according to the packages found in Buster. I didn't feel confident with the old Network Manager version numbers. n-m-s 1.4.5-1 has never been built or tested with these anicient versions. Sorry, I forgot to mention it in the changelog. * Please can you consider providing an explanation of the patch glib-private.patch *inside* that patch file. (Ideally patches should be in git-format-patch format or or DEP-3 format.) About glib-private.patch: I am not quite sure what you mean. I don't see a nested patch, just debian/patches/glib-private.patch. Apparently it *is* in git format. None of these observations look like blockers to me but I would like to at least ask you for answers before I just upload it. More on administrativia: * Since you have already committed your finalised 1.4.5-1 version, it would be best not to make more commits before bumping the changelog version again. So, if in response to this review you would like to make changes, rather than give explanations, please use 1.4.5-2 for your next revision. Sorry about that. Since nobody except you knows the current git repo for n-m-s, do you think it would be possible to delete the unwanted signed tag, using git push --delete origin tagName ? * In future, I am very happy to sponsor directly from git, especially from salsa. I see we have pristine tar and everything. So just push your branch (including pristine-tar) to salsa and email me. There is no need for you to make a dsc and email me attachments. In my review above I ignored your attachments and just worked with the git branch (from your private server). It would be nice to start with 1.4.5-1 on salsa. But AFAIK I need a sponsor (somebody with a full functional account) for either creating a repo for an official Debian package, or for getting a real account. Currently, if I try to create a project, then it gets a funny looking URL https://salsa.debian.org/harri-guest/ instead of the expected https://salsa.debian.org/debian/network-manager-strongswan :-( * Indeed, there is no need for you to make a signed tag. Because salsa is access controlled I feel I can trust it enough for this, at least as a baseline for review. If you like, feel free to leave the changelog as UNRELEASED; I am happy to do that change to `unstable' as part of the upload and push to salsa. If you would like to work this way, please give user `iwj' access to the repo. I am not sure about the UNRELEASED. Usually I push the package to my own repositories run by reprepro. It doesn't like the UNRELEASED. * If it's OK with you I like doing reviews in public. I think a "new upstream version" bug against the package is a good place because it means that if either of us drops it, our work is easily available as a starting point for others. Thats fine with me. Regards Harri
Bug#952363: marked as done (node-jsonminify: FTBFS: ERROR: describe is not defined)
Your message dated Mon, 24 Feb 2020 16:08:16 +
with message-id
and subject line Bug#952363: fixed in node-jsonminify 0.4.1+dfsg1-2
has caused the Debian Bug report #952363,
regarding node-jsonminify: FTBFS: ERROR: describe is not defined
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.)
--
952363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-jsonminify
Version: 0.4.1+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mocha -r should test/test-*.js
> mocha inspect [spec..]
>
> Run tests with Mocha
>
> Rules & Behavior
> --allow-uncaught Allow uncaught errors to propagate
> [boolean]
> --async-only, -A Require all tests to use a callback (async) or
> return a Promise
> [boolean]
> --bail, -b Abort ("bail") after first test failure
> [boolean]
> --check-leaks Check for global variable leaks
> [boolean]
> --delayDelay initial execution of root suite
> [boolean]
> --exit Force Mocha to quit after tests complete
> [boolean]
> --forbid-only Fail if exclusive test(s) encountered
> [boolean]
> --forbid-pending Fail if pending test(s) encountered
> [boolean]
> --global, --globalsList of allowed global variables
> [array]
> --retries Retry failed tests this many times
> [number]
> --slow, -s Specify "slow" test threshold (in milliseconds)
> [string] [default:
> 75]
> --timeout, -t, --timeouts Specify test timeout threshold (in milliseconds)
> [string] [default:
> 2000]
> --ui, -u Specify user interface[string] [default:
> "bdd"]
>
> Reporting & Output
> --color, -c, --colors Force-enable color output
> [boolean]
> --diffShow diff on failure
>[boolean] [default:
> true]
> --full-trace Display full stack traces
> [boolean]
> --growl, -G Enable Growl notifications
> [boolean]
> --inline-diffsDisplay actual/expected
> differences
> inline within each string
> [boolean]
> --reporter, -RSpecify reporter to use
> [string] [default:
> "spec"]
> --reporter-option, --reporter-options,Reporter-specific options
> -O()
> [array]
>
> Configuration
> --config Path to config file [string] [default: (nearest rc
> file)]
> --opts Path to `mocha.opts` (DEPRECATED)
> [string] [default:
> "./test/mocha.opts"]
> --package Path to package.json for config
> [string]
>
> File Handling
> --extension File extension(s) to load [array] [default:
> js]
> --file Specify file(s) to be loaded prior to root suite
>execution [array] [default:
> (none)]
> --ignore, --exclude Ignore file(s) or glob pattern(s)
>[array] [default:
> (none)]
> --recursive Look for tests in subdirectories
> [boolean]
> --require, -rRequire module [array] [default:
> (none)]
> --sort, -S Sort test files
> [boolean]
> --watch, -w Watch files in the current working directory for
> changes
>
> [boolean]
> --watch-filesList of paths or globs to watch
> [array]
> --watch-ignore List of paths or globs to exclude from watching
> [array] [default:
> ["node_modules",".git"]]
>
> Test Filters
> --fgrep, -f Only run tests containing this string
Bug#952341: marked as done (node-depd: FTBFS: ERROR: Cannot find module '/<>/test')
Your message dated Mon, 24 Feb 2020 16:08:10 +
with message-id
and subject line Bug#952341: fixed in node-depd 2.0.0-1
has caused the Debian Bug report #952341,
regarding node-depd: FTBFS: ERROR: Cannot find module '/<>/test'
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.)
--
952341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-depd
Version: 1.1.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mocha --reporter spec --bail --require should test/
> mocha inspect [spec..]
>
> Run tests with Mocha
>
> Rules & Behavior
> --allow-uncaught Allow uncaught errors to propagate
> [boolean]
> --async-only, -A Require all tests to use a callback (async) or
> return a Promise
> [boolean]
> --bail, -b Abort ("bail") after first test failure
> [boolean]
> --check-leaks Check for global variable leaks
> [boolean]
> --delayDelay initial execution of root suite
> [boolean]
> --exit Force Mocha to quit after tests complete
> [boolean]
> --forbid-only Fail if exclusive test(s) encountered
> [boolean]
> --forbid-pending Fail if pending test(s) encountered
> [boolean]
> --global, --globalsList of allowed global variables
> [array]
> --retries Retry failed tests this many times
> [number]
> --slow, -s Specify "slow" test threshold (in milliseconds)
> [string] [default:
> 75]
> --timeout, -t, --timeouts Specify test timeout threshold (in milliseconds)
> [string] [default:
> 2000]
> --ui, -u Specify user interface[string] [default:
> "bdd"]
>
> Reporting & Output
> --color, -c, --colors Force-enable color output
> [boolean]
> --diffShow diff on failure
>[boolean] [default:
> true]
> --full-trace Display full stack traces
> [boolean]
> --growl, -G Enable Growl notifications
> [boolean]
> --inline-diffsDisplay actual/expected
> differences
> inline within each string
> [boolean]
> --reporter, -RSpecify reporter to use
> [string] [default:
> "spec"]
> --reporter-option, --reporter-options,Reporter-specific options
> -O()
> [array]
>
> Configuration
> --config Path to config file [string] [default: (nearest rc
> file)]
> --opts Path to `mocha.opts` (DEPRECATED)
> [string] [default:
> "./test/mocha.opts"]
> --package Path to package.json for config
> [string]
>
> File Handling
> --extension File extension(s) to load [array] [default:
> js]
> --file Specify file(s) to be loaded prior to root suite
>execution [array] [default:
> (none)]
> --ignore, --exclude Ignore file(s) or glob pattern(s)
>[array] [default:
> (none)]
> --recursive Look for tests in subdirectories
> [boolean]
> --require, -rRequire module [array] [default:
> (none)]
> --sort, -S Sort test files
> [boolean]
> --watch, -w Watch files in the current working directory for
> changes
>
> [boolean]
> --watch-filesList of paths or globs to watch
> [array]
> --watch-ignore List of paths or globs to exclude from watching
> [array] [default:
> ["node_modules",".git"]]
>
> Test Filters
> --fgrep, -f Only run tests containing this string
Bug#950962: marked as done (FTBFS: "JSON blows up on circular references" test fails)
Your message dated Mon, 24 Feb 2020 16:14:30 +
with message-id
and subject line Bug#950962: fixed in ruby-sentry-raven 2.13.0-1
has caused the Debian Bug report #950962,
regarding FTBFS: "JSON blows up on circular references" test fails
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.)
--
950962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sentry-raven
Version: 2.9.0-1
Severity: serious
Tags: ftbfs bullseye sid
Justification: fails to build from source
Failures:
1) JSON blows up on circular references
Failure/Error: expect { JSON.dump(data) }.to raise_error(SystemStackError)
expected SystemStackError, got # with backtrace:
# ./spec/raven/json_spec.rb:75:in `block (2 levels) in '
Find atteched the full build log
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
ruby-sentry-raven_amd64.build.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-sentry-raven
Source-Version: 2.13.0-1
Done: Lucas Kanashiro
We believe that the bug you reported is fixed in the latest version of
ruby-sentry-raven, 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 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lucas Kanashiro (supplier of updated
ruby-sentry-raven package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 24 Feb 2020 12:14:29 -0300
Source: ruby-sentry-raven
Architecture: source
Version: 2.13.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Lucas Kanashiro
Closes: 950962
Changes:
ruby-sentry-raven (2.13.0-1) unstable; urgency=medium
.
* Team upload.
.
[ Utkarsh Gupta ]
* Add salsa-ci.yml
.
[ Pirate Praveen ]
* New upstream version 2.13.0
.
[ Lucas Kanashiro ]
* Add patch to skip failing JSON related test as recommended by upstream
(Closes: #950962)
* Bump debhelper compatibility level to 12
* Declare compliance with Debian Policy 4.5.0
* d/controle: rules does not require root
* Do not runtime depend on ruby interpreter
* d/copyright: use secure url in Format field
Checksums-Sha1:
f1f71689052e827e09b59117c06372ec3495d941 2305 ruby-sentry-raven_2.13.0-1.dsc
0b4e707c82cf5628b6c1d5eaab2fb01e3758dd9b 89668
ruby-sentry-raven_2.13.0.orig.tar.gz
281a9a40fc1ae15d204ac7aba0a0d8944e6462be 3952
ruby-sentry-raven_2.13.0-1.debian.tar.xz
Checksums-Sha256:
1e0d9998b9493f2a90b9fc66a807d24cfd8f5563e0f2bf4da3b263b67423f815 2305
ruby-sentry-raven_2.13.0-1.dsc
5504734e7697b266c88f98518353bd7cf8a647599e6b28a2b9eb8dcddeb1357c 89668
ruby-sentry-raven_2.13.0.orig.tar.gz
a02eb20bc58fa6af9dbb980a363db323f61699a27ded4de7b49298092543994b 3952
ruby-sentry-raven_2.13.0-1.debian.tar.xz
Files:
4dabdbd13f18330839d2330151b23953 2305 ruby optional
ruby-sentry-raven_2.13.0-1.dsc
2fc171218ca4011bc313dadddb8a220c 89668 ruby optional
ruby-sentry-raven_2.13.0.orig.tar.gz
d135b3ed544826b6f5c04aebdc84a0ad 3952 ruby optional
ruby-sentry-raven_2.13.0-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJSBAEBCAA8FiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl5T73keHGx1Y2FzLmth
bmFzaGlyb0BjYW5vbmljYWwuY29tAAoJEPgjonKYg8l8To8P/3RlGrP2XoQ7QY6k
31EPiLUXiK1TMgwS+lNegsE8aq58coxjQl/dS1gOfF3yFnxrnNjkTP52uR9yKq1d
zvMjpkoyuzecIzCWieRT3DPXRTcmGKzXrl+pSy0KL2HKG9HSayZG4YFAoi0D8RLF
/qIQvDiFifjEE0typk8dBP83dDWqFf7Ur74DShJkgj+ecRK0Q7Xw1VYzHxz3toPO
S66I4qRkRliAIc+czPkthDEqKl2RCpN0FCKFgFHV16kgwP1R3p3hR2RZlMwKCYVu
SWKsyRw8+LYfSJMoJWFflcF4UBaLkw+3TamSrpYSZF5AEiGnM+sq8d3UiEp+6eFq
W6lmV2nfVAYuI3ySGFGGxwq/TIIs8e
Bug#951905: marked as done (qtwebengine-opensource-src FTBFS: symbols disappeared)
Your message dated Mon, 24 Feb 2020 16:14:20 + with message-id and subject line Bug#951905: fixed in qtwebengine-opensource-src 5.12.5+dfsg-7 has caused the Debian Bug report #951905, regarding qtwebengine-opensource-src FTBFS: symbols disappeared 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.) -- 951905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qtwebengine-opensource-src Version: 5.12.5+dfsg-6 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qtwebengine-opensource-src.html ... dh_makeshlibs dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libqt5webenginecore5/DEBIAN/symbols doesn't match completely debian/libqt5webenginecore5.symbols --- debian/libqt5webenginecore5.symbols (libqt5webenginecore5_5.12.5+dfsg-6_amd64) +++ dpkg-gensymbolsMc4x8E 2021-03-25 19:04:23.418762620 -1200 @@ -17,10 +17,10 @@ (optional=gold)Qt_5@Qt_5 5.7.1 (optional=gold)Qt_5_PRIVATE_API@Qt_5_PRIVATE_API 5.7.1 1 (arch=mipsel)SyscallAsm@Qt_5 5.9.1 - _ZGRN2ui12_GLOBAL__N_115kSkipThresholdsE_@Qt_5 5.12.5 - _ZGRN2ui12_GLOBAL__N_118kLatencyThresholdsE_@Qt_5 5.12.5 - _ZGRN2ui12_GLOBAL__N_123kLatencySpeedThresholdsE_@Qt_5 5.12.5 - _ZGRN2ui12_GLOBAL__N_130kLatencyAccelerationThresholdsE_@Qt_5 5.12.5 +#MISSING: 5.12.5+dfsg-6# _ZGRN2ui12_GLOBAL__N_115kSkipThresholdsE_@Qt_5 5.12.5 +#MISSING: 5.12.5+dfsg-6# _ZGRN2ui12_GLOBAL__N_118kLatencyThresholdsE_@Qt_5 5.12.5 +#MISSING: 5.12.5+dfsg-6# _ZGRN2ui12_GLOBAL__N_123kLatencySpeedThresholdsE_@Qt_5 5.12.5 +#MISSING: 5.12.5+dfsg-6# _ZGRN2ui12_GLOBAL__N_130kLatencyAccelerationThresholdsE_@Qt_5 5.12.5 _ZN11QtWebEngine11processMainEiPPKc@Qt_5 5.7.1 _ZN14WebEngineError15toQtErrorDomainEi@Qt_5 5.7.1 _ZN14WebEngineError16UserAbortedErrorE@Qt_5 5.7.1 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:56: binary] Error 25 --- End Message --- --- Begin Message --- Source: qtwebengine-opensource-src Source-Version: 5.12.5+dfsg-7 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of qtwebengine-opensource-src, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qtwebengine-opensource-src 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: Mon, 24 Feb 2020 18:10:27 +0300 Source: qtwebengine-opensource-src Binary: qtwebengine5-dev qtwebengine5-private-dev libqt5webengine5 libqt5webenginecore5 libqt5webenginewidgets5 libqt5webengine-data qml-module-qtwebengine qtwebengine5-dev-tools qtwebengine5-examples qtwebengine5-doc qtwebengine5-doc-html Architecture: source Version: 5.12.5+dfsg-7 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Description: libqt5webengine-data - Web content engine library for Qt - Data libqt5webengine5 - Web content engine library for Qt libqt5webenginecore5 - Web content engine library for Qt - Core libqt5webenginewidgets5 - Web content engine library for Qt - Widget qml-module-qtwebengine - Qt WebEngine QML module qtwebengine5-dev - Web content engine library for Qt - development files qtwebengine5-dev-tools - Qt WebEngine tools qtwebengine5-doc - Qt 5 webengine documentation qtwebengine5-doc-html - Qt 5 webengine HTML documentation qtwebengine5-examples - Qt WebEngine - Examples qtwebengine5-private-dev - Web content engine library for Qt - private development files Closes: 951905 Changes: qtwebengine-opensource-src (5.12.5+dfsg-7) unstable; urgency=medium . [ Dmitry Shachnev ] * Limit Ubuntu arm64 builds to -j2. * Update debian/libqt5webenginecore5.symbols (closes: #951905). . [ Gianfranco Costamagna ] * Depend on python2 instead of python, also tweak the patch to change the calls to python binary. Checksums-Sha1: e473bd8a723e819d9624e504cc098640581e173f 4744 qtwebengine-opensource-src_5.12.5+dfs
Bug#950999: marked as pending in libkiokudb-perl
Control: tag -1 pending Hello, Bug #950999 in libkiokudb-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libkiokudb-perl/commit/9c950e2682865030f9aa59a6543d56f8c6035a4c Add patch to allow object loading with YAML::XS. Closes: #950999 (this message was generated automatically) -- Greetings https://bugs.debian.org/950999
Processed: Bug#950999 marked as pending in libkiokudb-perl
Processing control commands: > tag -1 pending Bug #950999 [src:libkiokudb-perl] libkiokudb-perl: FTBFS with recent YAML* packages Added tag(s) pending. -- 950999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945567: new network-manager-strongswan package [and 1 more messages]
Harald Dunkel writes ("Re: new network-manager-strongswan package [and 1 more
messages]"):
> Sorry for the confusion. Of course n-m-s is not in salsa (yet). I was
> working on mg (my other package) in parallel, which *is* in salsa.
Ah. No problem.
> It would be nice to start with 1.4.5-1 on salsa. But AFAIK I need a
> sponsor (somebody with a full functional account) for either creating a
> repo for an official Debian package, or for getting a real account.
> Currently, if I try to create a project, then it gets a funny looking
> URL
> https://salsa.debian.org/harri-guest/
>
> instead of the expected
>
> https://salsa.debian.org/debian/network-manager-strongswan
> :-(
Let me work on this first.
...
Fixed I think. I have created this:
https://salsa.debian.org/debian/network-manager-strongswan
and made you ("harri-guest") a maintainer of it.
I think you can do all the rest of the setup yourself. Let me know if
you want anything else doing.
> On 2/24/20 3:02 PM, Ian Jackson wrote:
> >
> > I looked at the diff etc. and I have some observations:
> >
> > * It would be nice to add a Vcs-Git header.
>
> I am OK with this, but I would suggest to wait for the move to salsa,
> see below.
OK.
> > * I noticed you changed the Build-Depends. There is a change to
> >debhelper, which is expected. But there are also changes to the
> >network-manager build-dependencies. I looked for some file in
> >upstream wqher etehse requirements are documented, and/or something
> >in the debian/changelog to explain or document the change, but
> >found nothing. Can you please explain ?
> >
>
> The version numbers of the dependencies have been changed according to
> the packages found in Buster. I didn't feel confident with the old Network
> Manager version numbers. n-m-s 1.4.5-1 has never been built or tested
> with these anicient versions. Sorry, I forgot to mention it in the
> changelog.
I guess this is up to you. My personal preference is not to update
B-D unless I know of a reason why it wouldn't work. But I know many
people adopt your approach. Thanks for the explanation.
> > * Please can you consider providing an explanation of the patch
> >glib-private.patch *inside* that patch file. (Ideally patches
> >should be in git-format-patch format or or DEP-3 format.)
>
> About glib-private.patch: I am not quite sure what you mean. I don't
> see a nested patch, just debian/patches/glib-private.patch. Apparently
> it *is* in git format.
No, I mean: inside the patch file, there should be an explanation.
$ head -3 debian/patches/glib-private.patch
diff --git a/src/frontends/gnome/properties/nm-strongswan.c
b/src/frontends/gnome/properties/nm-strongswan.c
index de15c4271..d261dcb7a 100644
Compare:
$ head -13
/home/ian/things/Debian/Psutils/psutils/debian/patches/psnup1-remove-a-confusing-and-unnecessar
From: Reuben Thomas
Date: Sat, 21 Jan 2017 19:37:28 +
X-Dgit-Generated: 1.17.dfsg-4 45990e7c75dde21ad20a9e6e22b2d8e980b92459
Subject: psnup(1): Remove a confusing and unnecessary qualification about units.
Apropos of #695179.
---
--- psutils-1.17.dfsg.orig/psnup.man
+++ psutils-1.17.dfsg/psnup.man
@@ -54,10 +54,7 @@ option gives the paper height,
normally specified in
> > * Since you have already committed your finalised 1.4.5-1 version, it
> >would be best not to make more commits before bumping the changelog
> >version again. So, if in response to this review you would like to
> >make changes, rather than give explanations, please use 1.4.5-2 for
> >your next revision.
> >
>
> Sorry about that. Since nobody except you knows the current git repo
> for n-m-s, do you think it would be possible to delete the unwanted
> signed tag, using
>
> git push --delete origin tagName
> ?
IMO there is nothing wrong with just going to a new version, -2. This
will all be much less confusing and not involve deleting tags,
etc. etc. Integers are cheap.
> > * Indeed, there is no need for you to make a signed tag. Because
> >salsa is access controlled I feel I can trust it enough for this, at
> >least as a baseline for review. If you like, feel free to leave the
> >changelog as UNRELEASED; I am happy to do that change to `unstable'
> >as part of the upload and push to salsa. If you would like to work
> >this way, please give user `iwj' access to the repo.
>
> I am not sure about the UNRELEASED. Usually I push the package to my
> own repositories run by reprepro. It doesn't like the UNRELEASED.
Ah. Well, another tactic is to add a ~pre to the Debian revision. Eg
1.4.5-1~pre2
or something. But this is up to you. All I'm really going to insisti
on is that I shouldn't need to delete tags.
I can bump the version myself if you like but then you'll have to pull
from me (or salsa, once the code is there).
Should I push 1.4.5-1 right away or should I expect revisions ?
Regards,
Ian.
--
Ian JacksonThese opinions are
Bug#950732: Issue stil persists in actual stable distros
Hello. Are there any plant to backport the fix for older versions in Stretch and Buster? The bug is now closed and I can see no related information. It is high security issue, that is already fixed in all main distributions. https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1712 https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1712.html https://lists.centos.org/pipermail/centos-announce/2020-February/035631.html https://bugzilla.suse.com/show_bug.cgi?id=CVE-2020-1712 -- С уважением, Василий Лихачёв Технический отдел FASTVPS Respectfully, Vasiliy Likhachev FASTVPS technical department
Bug#867067: create directory for nfsdcltrack
Control: severity -1 important On Mon, 2020-02-24 at 16:01 +0100, Elimar Riesebieter wrote: > Control: found -1 1.3.4-2.5 > Control: severity -1 grave > > Hi all, > > this bug causes kernel panics at least on i386 and x86-64 running > nfsv4 servers so set severity to grave. [...] This bug is assigned to nfs-kernel-server, which only contains the programs used to *configure* the NFS server in the kernel. The kernel crash needs to be assigned to the kernel, i.e. src:linux. You should open a separate bug for that, using "reportbug kernel". Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#867067: create directory for nfsdcltrack
Processing control commands: > severity -1 important Bug #867067 [nfs-kernel-server] nfs-kernel-server: nfsdcltrack fails to init database Severity set to 'important' from 'grave' -- 867067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952320: marked as done (mocassin: FTBFS: Error: Variable ‘gploc’ at (1) not definable inside loop beginning at (2) as INTENT(INOUT) argument to subroutine ‘energypacketdriver’ source/iteration_mod
Your message dated Mon, 24 Feb 2020 16:35:26 + with message-id and subject line Bug#952320: fixed in mocassin 2.02.73-2 has caused the Debian Bug report #952320, regarding mocassin: FTBFS: Error: Variable ‘gploc’ at (1) not definable inside loop beginning at (2) as INTENT(INOUT) argument to subroutine ‘energypacketdriver’ source/iteration_mod.f90:537:45: 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.) -- 952320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mocassin Version: 2.02.73-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/constants_mod.f90 -c -o source/constants_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/vector_mod.f90 -c -o source/vector_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/common_mod.f90 -c -o source/common_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/interpolation_mod.f90 -c -o > source/interpolation_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/set_input_mod.f90 -c -o source/set_input_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/hydro_mod.f90 -c -o source/hydro_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/ph_mod.f90 -c -o source/ph_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/composition_mod.f90 -c -o > source/composition_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/continuum_mod.f90 -c -o source/continuum_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/ionization_mod.f90 -c -o > source/ionization_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/pathIntegration_mod.f90 -c -o > source/pathIntegration_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-line-length-0 -lm -DPREFIX=\"/usr\" > -I/usr/include/mpich -O2 source/grid_mod.f90 -c -o source/grid_mod.o > f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ > [-Wmissing-include-dirs] > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -cpp -Jsource/ -ffree-l
Bug#952189: sphinx: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 2.7 returned exit code 13
Control: tags -1 unreproducible
Hi Lucas!
On Sun, Feb 23, 2020 at 02:14:25PM +0100, Lucas Nussbaum wrote:
> Source: sphinx
> Version: 1.8.5-5
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200222 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
>
> > === FAILURES
> > ===
> > ___ test_correct_year[expect_date1]
> >
> >
> > expect_date = '2006-2011', app =
> >
> > @pytest.mark.sphinx('html', testroot='correct-year')
> > def test_correct_year(expect_date, app):
> > app.build()
> > content = (app.outdir / 'contents.html').text()
> > > assert expect_date in content
> > E assert '2006-2011' in '\n > 1.0 Transitional//EN"\n
> > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitiona... > href="_sources/contents.rst.txt"\n rel="nofollow">Page
> > source\n\n\n\n\n\n \n'
> >
> > tests/test_correct_year.py:37: AssertionError
I cannot reproduce this, neither in a chroot (pbuilder) nor in Salsa pipeline.
Is there anything specific to your environment that could cause this?
The test deals with SOURCE_DATE_EPOCH, but the test sets (or unsets) it
manually anyway, so the external setting should not affect anything.
I also thought about time zones, but for me the tests pass even when I am
not using the UTC time zone (I use +0300).
--
Dmitry Shachnev
signature.asc
Description: PGP signature
Bug#950966: marked as done (netty: CVE-2019-20444)
Your message dated Mon, 24 Feb 2020 16:36:10 + with message-id and subject line Bug#950966: fixed in netty 1:4.1.45-1 has caused the Debian Bug report #950966, regarding netty: CVE-2019-20444 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.) -- 950966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netty Version: 1:4.1.33-3 Severity: grave Tags: security upstream Forwarded: https://github.com/netty/netty/issues/9866 Hi, The following vulnerability was published for netty. CVE-2019-20444[0]: | HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header | that lacks a colon, which might be interpreted as a separate header | with an incorrect syntax, or might be interpreted as an "invalid | fold." If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-20444 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444 [1] https://github.com/netty/netty/issues/9866 [2] https://github.com/netty/netty/commit/a7c18d44b46e02dadfe3da225a06e5091f5f328e Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: netty Source-Version: 1:4.1.45-1 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of netty, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated netty 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: Mon, 24 Feb 2020 17:10:37 +0100 Source: netty Architecture: source Version: 1:4.1.45-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 950966 950967 Changes: netty (1:4.1.45-1) unstable; urgency=medium . * Team upload. * New upstream release - Fixes CVE-2019-20444, CVE-2019-20445 and CVE-2020-7238 (Closes: #950966, #950967) - Refreshed the patches - Updated the Maven rules - Depend on libnetty-tcnative-java (>= 2.0.28) - Disabled the native image support due to missing dependencies - Disabled the BlockHound integration * Standards-Version updated to 4.5.0 Checksums-Sha1: c9a8b5821a1200f5efb944ae5be1fa45c1e5b17e 2464 netty_4.1.45-1.dsc 41b68b4a6070a1dc56d0d7e116f08ec2e4be0ca3 1653104 netty_4.1.45.orig.tar.xz ab699101ffc596f53d6663a4442489c82a775a85 14632 netty_4.1.45-1.debian.tar.xz 0cb7aaa68058d7e582e06f4637e468b692f49d44 14126 netty_4.1.45-1_source.buildinfo Checksums-Sha256: e97c4293fee763bbef84afb172c590cf2e96139743ffcc36eb59eb3496e7e0e9 2464 netty_4.1.45-1.dsc 5727926d042670c1ac7c19588bd2ca8bd87d3894336b93192d93a53363604a84 1653104 netty_4.1.45.orig.tar.xz ea555a3d91eae86e00de7af00c0ce0eb8686c0c5a397cdabc4c8595f7f922430 14632 netty_4.1.45-1.debian.tar.xz 4ee5a73e055009bd39e34f0beeff24ffaf93e3d84aedf453940cd2ed3399978e 14126 netty_4.1.45-1_source.buildinfo Files: eeebf196519105b02d596e17fbdc1db1 2464 java optional netty_4.1.45-1.dsc 96ba6b5ae4a042255fbdff11d865759c 1653104 java optional netty_4.1.45.orig.tar.xz 29a5219df99af60ed0cf986c4731d2b7 14632 java optional netty_4.1.45-1.debian.tar.xz 001f4ff697f9a852aacf2114a536c9f6 14126 java optional netty_4.1.45-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl5T93QSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsri4P/3zerX0Pqa8b3eJ3AGUA/2D/kc9gS7bA lpnUPmtGjRU7aq3i7UJgw2qsdzRdRY+elmld1qseWl0PRAEmzYEEr1Bt1+G3mma+ Nk8ptCq1fZuz2TOc7u+L0pKJZQ6WawvL1dP0ohc9v8BNk8ED/E1To1LfwfxT8sXQ 5PgKnvqZkDmO1xuSrYIGVQaLcdeDNkhj5OUjXMj+MiTDdGQGhTNWJuqk4WSaZWl3 m9Cu4+64VbFA+jJr9HDfJuQbyBSKQkATmgJPQQxIB0jYqqhRmEQq+Nxw9QynZDJR JW2iTujmxKKsbCbJWKiFPjBv82Suao1vqo16FBUfoOMGxMpNkNCFaziTMRJFkZIT fvySAzsnlVu2XSfozK2832WMWaUSxMKsb7uGLnFfX4Xqur3NHbgrGBPanKVLXPK+ XkdlxODPLhWVhJQPlJ+lOvhYqGptJevlEUUuKl+QRoLFAEGuUDmt0pu0bmCR0YYG dcWvycvxDFmGzxFO8j1h3HP2q7OfVsUsQ+GPVO30gjtG+Fu5
Bug#951919: marked as done (montage-wrapper: FTBFS: Failed: [pytest] section in setup.cfg files is no longer supported, change to [tool:pytest] instead.)
Your message dated Mon, 24 Feb 2020 16:35:32 +
with message-id
and subject line Bug#951919: fixed in montage-wrapper 0.9.9-4
has caused the Debian Bug report #951919,
regarding montage-wrapper: FTBFS: Failed: [pytest] section in setup.cfg files
is no longer supported, change to [tool:pytest] instead.
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.)
--
951919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: montage-wrapper
Version: 0.9.9-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.8 setup.py test -vv --args -v
> running test
> installing to temporary directory: /tmp/montage_wrapper-test-sgqt_n6r
> /usr/lib/python3/dist-packages/astropy/config/configuration.py:557:
> ConfigurationMissingWarning: Configuration defaults will be used due to
> FileNotFoundError:2 on None
> warn(ConfigurationMissingWarning(msg))
> Traceback (most recent call last):
> File "", line 1, in
> File
> "/tmp/montage_wrapper-test-sgqt_n6r/lib/python3.8/site-packages/montage_wrapper/_astropy_init.py",
> line 107, in test
> return test_runner.run_tests(
> File "/usr/lib/python3/dist-packages/astropy/tests/runner.py", line 611, in
> run_tests
> return super().run_tests(**kwargs)
> File "/usr/lib/python3/dist-packages/astropy/tests/runner.py", line 248, in
> run_tests
> return pytest.main(args=args, plugins=plugins)
> File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 63,
> in main
> config = _prepareconfig(args, plugins)
> File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 206,
> in _prepareconfig
> return pluginmanager.hook.pytest_cmdline_parse(
> File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286, in __call__
> return self._hookexec(self, self.get_hookimpls(), kwargs)
> File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92, in
> _hookexec
> return self._inner_hookexec(hook, methods, kwargs)
> File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83, in
>
> self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
> File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 203, in
> _multicall
> gen.send(outcome)
> File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line 94, in
> pytest_cmdline_parse
> config = outcome.get_result()
> File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in
> get_result
> raise ex[1].with_traceback(ex[2])
> File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in
> _multicall
> res = hook_impl.function(*args)
> File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 739,
> in pytest_cmdline_parse
> self.parse(args)
> File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 947,
> in parse
> self._preparse(args, addopts=addopts)
> File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 881,
> in _preparse
> self._initini(args)
> File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 808,
> in _initini
> r = determine_setup(
> File "/usr/lib/python3/dist-packages/_pytest/config/findpaths.py", line
> 127, in determine_setup
> rootdir, inifile, inicfg = getcfg([ancestor], config=config)
> File "/usr/lib/python3/dist-packages/_pytest/config/findpaths.py", line 49,
> in getcfg
> fail(
> File "/usr/lib/python3/dist-packages/_pytest/outcomes.py", line 119, in fail
> raise Failed(msg=msg, pytrace=pytrace)
> Failed: [pytest] section in setup.cfg files is no longer supported, change to
> [tool:pytest] instead.
> /usr/lib/python3/dist-packages/astropy/config/configuration.py:557:
> ConfigurationMissingWarning: Configuration defaults will be used due to
> FileNotFoundError:2 on None
> warn(ConfigurationMissingWarning(msg))
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:161:
> AstropyDeprecationWarning: The package argument to generate_version_py has
> been deprecated and will be removed in future. Specify the package name in
> setup.cfg instead
> warnings.warn('The package argument to generate_version_py has '
> /usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:166:
> AstropyDepreca
Bug#950967: marked as done (netty: CVE-2019-20445 CVE-2020-7238)
Your message dated Mon, 24 Feb 2020 16:36:11 + with message-id and subject line Bug#950967: fixed in netty 1:4.1.45-1 has caused the Debian Bug report #950967, regarding netty: CVE-2019-20445 CVE-2020-7238 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.) -- 950967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netty Version: 1:4.1.33-3 Severity: grave Tags: security upstream Forwarded: https://github.com/netty/netty/issues/9861 Hi, The following vulnerabilities were published for netty. CVE-2019-20445[0]: | HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length | header to be accompanied by a second Content-Length header, or by a | Transfer-Encoding header. CVE-2020-7238[1]: | Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles | Transfer-Encoding whitespace (such as a [space]Transfer- | Encoding:chunked line) and a later Content-Length header. This issue | exists because of an incomplete fix for CVE-2019-16869. Both appears to be fixed with the same fix upstream, as per [2]. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-20445 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20445 [1] https://security-tracker.debian.org/tracker/CVE-2020-7238 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7238 [2] https://github.com/netty/netty/issues/9861 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: netty Source-Version: 1:4.1.45-1 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of netty, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated netty 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: Mon, 24 Feb 2020 17:10:37 +0100 Source: netty Architecture: source Version: 1:4.1.45-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 950966 950967 Changes: netty (1:4.1.45-1) unstable; urgency=medium . * Team upload. * New upstream release - Fixes CVE-2019-20444, CVE-2019-20445 and CVE-2020-7238 (Closes: #950966, #950967) - Refreshed the patches - Updated the Maven rules - Depend on libnetty-tcnative-java (>= 2.0.28) - Disabled the native image support due to missing dependencies - Disabled the BlockHound integration * Standards-Version updated to 4.5.0 Checksums-Sha1: c9a8b5821a1200f5efb944ae5be1fa45c1e5b17e 2464 netty_4.1.45-1.dsc 41b68b4a6070a1dc56d0d7e116f08ec2e4be0ca3 1653104 netty_4.1.45.orig.tar.xz ab699101ffc596f53d6663a4442489c82a775a85 14632 netty_4.1.45-1.debian.tar.xz 0cb7aaa68058d7e582e06f4637e468b692f49d44 14126 netty_4.1.45-1_source.buildinfo Checksums-Sha256: e97c4293fee763bbef84afb172c590cf2e96139743ffcc36eb59eb3496e7e0e9 2464 netty_4.1.45-1.dsc 5727926d042670c1ac7c19588bd2ca8bd87d3894336b93192d93a53363604a84 1653104 netty_4.1.45.orig.tar.xz ea555a3d91eae86e00de7af00c0ce0eb8686c0c5a397cdabc4c8595f7f922430 14632 netty_4.1.45-1.debian.tar.xz 4ee5a73e055009bd39e34f0beeff24ffaf93e3d84aedf453940cd2ed3399978e 14126 netty_4.1.45-1_source.buildinfo Files: eeebf196519105b02d596e17fbdc1db1 2464 java optional netty_4.1.45-1.dsc 96ba6b5ae4a042255fbdff11d865759c 1653104 java optional netty_4.1.45.orig.tar.xz 29a5219df99af60ed0cf986c4731d2b7 14632 java optional netty_4.1.45-1.debian.tar.xz 001f4ff697f9a852aacf2114a536c9f6 14126 java optional netty_4.1.45-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl5T93QSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsri4P/3zerX0Pqa8b3eJ3AGUA/2D/kc9gS7bA lpnUPmtGjRU7aq3i7UJgw2qsdzRdRY+elmld1qseWl0PRAEmzYEEr1Bt1+G3mma+ Nk8ptCq1fZuz2TOc7u+L0pKJZQ6WawvL1dP0ohc9v8BNk8ED/E1To1LfwfxT8sXQ 5PgKnvqZkD
Processed: Re: Bug#952189: sphinx: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 2.7 returned exit code 13
Processing control commands:
> tags -1 unreproducible
Bug #952189 [src:sphinx] sphinx: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 2.7 returned exit code 13
Added tag(s) unreproducible.
--
952189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#952173: marked as pending in dh-golang
Control: tag -1 pending Hello, Bug #952173 in dh-golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/dh-golang/commit/6f3b968aa4b9e39d83d0de9b70d33f9d64de2eb2 Skip empty pattern when check target lists (Closes: #952173) If the PATTERN evaluates to the empty string, the last successfully matched regular expression is used instead Thanks @lilydjwg (this message was generated automatically) -- Greetings https://bugs.debian.org/952173
Processed: Bug#952173 marked as pending in dh-golang
Processing control commands: > tag -1 pending Bug #952173 [dh-golang] golang-gopkg-gorethink-gorethink.v3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 returned exit code 1 Added tag(s) pending. -- 952173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#952173 marked as pending in dh-golang
Processing control commands: > tag -1 pending Bug #952173 [dh-golang] golang-gopkg-gorethink-gorethink.v3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 returned exit code 1 Ignoring request to alter tags of bug #952173 to the same tags previously set -- 952173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952173: marked as pending in dh-golang
Control: tag -1 pending Hello, Bug #952173 in dh-golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/dh-golang/commit/b4acd2b737b28a30a5868ae8fc0b80f0796628bf Skip empty pattern when check target lists (Closes: #952173) If the PATTERN evaluates to the empty string, the last successfully matched regular expression is used instead Thanks @lilydjwg (this message was generated automatically) -- Greetings https://bugs.debian.org/952173
Bug#952212: marked as pending in node-vhost
Control: tag -1 pending Hello, Bug #952212 in node-vhost reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-vhost/commit/e8354208f6040c0f572f03f416a79bc76e7b02b4 Fix test for mocha ≥ 7 Closes: #952212 (this message was generated automatically) -- Greetings https://bugs.debian.org/952212
Processed: Bug#952212 marked as pending in node-vhost
Processing control commands: > tag -1 pending Bug #952212 [src:node-vhost] node-vhost: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 7 Added tag(s) pending. -- 952212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952453: arbitrary command execution vulnerability
Package: opensmtpd Version: 6.6.2p1-1 Severity: critical Tags: upstream OpenBSD 6.6 errata 021, February 24, 2020: An out of bounds read in smtpd allows an attacker to inject arbitrary commands into the envelope file which are then executed as root. Separately, missing privilege revocation in smtpctl allows arbitrary commands to be run with the _smtpq group. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages opensmtpd depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.73 ii ed 1.16-1 ii init-system-helpers1.57 ii libasr01.0.2-2+b1 ii libc6 2.29-6 ii libcrypt1 1:4.4.10-7 ii libdb5.3 5.3.28+dfsg1-0.6 ii libevent-2.1-7 2.1.11-stable-1 ii libpam0g 1.3.1-5 ii libssl1.1 1.1.1d-2 ii lsb-base 11.1.0 ii zlib1g 1:1.2.11.dfsg-1.2 Versions of packages opensmtpd recommends: ii opensmtpd-extras 6.6.0-1 Versions of packages opensmtpd suggests: ii ca-certificates 20190110 -- Configuration Files: /etc/smtpd.conf changed [not included] -- debconf information excluded -- |)|/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Bug#951941: marked as done (slop: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:11: undefined reference to `pthread_create')
Your message dated Mon, 24 Feb 2020 17:12:15 + with message-id and subject line Bug#951941: fixed in slop 7.4-2 has caused the Debian Bug report #951941, regarding slop: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:11: undefined reference to `pthread_create' 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.) -- 951941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slop Version: 7.4-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_26376.dir/src.cxx.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:11: > undefined reference to `pthread_create' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:12: > undefined reference to `pthread_detach' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:13: > undefined reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/slop_7.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: slop Source-Version: 7.4-2 Done: =?utf-8?q?Antoine_Beaupr=C3=A9?= We believe that the bug you reported is fixed in the latest version of slop, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antoine Beaupré (supplier of updated slop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Feb 2020 11:38:34 -0500 Source: slop Architecture: source Version: 7.4-2 Distribution: unstable Urgency: medium Maintainer: Antoine Beaupré Changed-By: Antoine Beaupré Closes: 951941 Changes: slop (7.4-2) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/rules: Remove trailing whitespaces . [ Antoine Beaupré ] * fix FTBFS, thanks Sebastian Ramacher! (Closes: #951941) Checksums-Sha1: cce6e63899cf32c32432f3e03303f1834c8a7cd4 1529 slop_7.4-2.dsc 231453fce67e7449fa4061efd0ad7b35fb830b35 2716 slop_7.4-2.debian.tar.xz abc52aba40b682baf586f8e0e133b69f4038731b 8473 slop_7.4-2_amd64.buildinfo Checksums-Sha256: 3bd7a023b8e39d428f56bf9fab7c7cff75b81a73010122ea8ab82e2b5aedddf2 1529 slop_7.4-2.dsc 8decc61debf9b648b92e41b9de1d7e03b7570902478cbdb5d5712f8879a07868 2716 slop_7.4-2.debian.tar.xz 892aaa447ad10b609033c6660f89a7f592b59798e1b8798e7232393992760b2d 8473 slop_7.4-2_amd64.buildinfo Files: a1a81989d4f1e6ffc6b0ac7e1c0f275d 1529 x11 optional slop_7.4-2.dsc 16ceec59d7924625881ad4e34e10107a 2716 x11 optional slop_7.4-2.debian.tar.xz 614b22d8d7068612a56bed70762d3ae6 8473 x11 optional slop_7.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl5UAE4ACgkQPqHd3bJh 2XsmDwgArzJC/226X1db7hgYSe87ngSgiNvcZSF4BDwEs8DcjcSiE7/LFUBgXscI hDBLgmSifd7MWrksk8px2qNHvw9CnbIYYBw3m7tvFmtS+Ux/TmLR0XyxIIi4f8Ry OozhYIv3o+E+zzJ4A110cOakxCurLxOQShNG/HNkH0/YAwwQAuwMRnt3HIFAB2z2 GztRBSaxIjGDLy/4RfozfVBMLRcDjZmn8RsCu7X3jI4gene2W6vuyPNdd67fh7Dq TJkoVCdPX8cRX+NTv4q7TVjOrx7YS0xrHTrEYOqCJoubq7F48WRmQOwNcJ5kU/on rz7MiuL+SPdjgg0Vo5hFjlZBLl7TbQ== =TlpF -END PGP SIGNATURE End Message ---
