Bug#987507: marked as done (notion: binary-all FTBFS)
Your message dated Mon, 26 Apr 2021 07:03:25 + with message-id and subject line Bug#987507: fixed in notion 4.0.2+dfsg-5 has caused the Debian Bug report #987507, regarding notion: binary-all FTBFS 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.) -- 987507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: notion Version: 4.0.2+dfsg-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=notion&arch=all&ver=4.0.2%2Bdfsg-4&stamp=1619296702&raw=0 ... dh_missing -i dh_missing: warning: usr/share/man/man1/notion.1 exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/share/notion/notion.1") dh_missing: warning: usr/share/man/man1/notionflux.1 exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/share/notion/notionflux.1") dh_missing: error: missing files, aborting While detecting missing files, dh_missing noted some files with a similar name to those that were missing. This error /might/ be resolved by replacing references to the missing files with the similarly named ones that dh_missing found - assuming the content is identical. As an example, you might want to replace: * debian/tmp/usr/share/notion/notion.1 with: * usr/share/man/man1/notion.1 in a file in debian/ or as argument to one of the dh_* tools called from debian/rules. (Note it is possible the paths are not used verbatim but instead directories containing or globs matching them are used instead) Alternatively, add the missing file to debian/not-installed if it cannot and should not be used. The following debhelper tools have reported what they installed (with files per package) * dh_install: notion (15), notion-dev (7) * dh_installdocs: notion (8), notion-dev (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built If the omission is intentional or no other helper can take care of this consider adding the paths to debian/not-installed. make: *** [debian/rules:11: binary-indep] Error 25 --- End Message --- --- Begin Message --- Source: notion Source-Version: 4.0.2+dfsg-5 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of notion, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated notion 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: Sun, 25 Apr 2021 23:41:14 -0700 Source: notion Architecture: source Version: 4.0.2+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Dima Kogan Changed-By: Dima Kogan Closes: 987507 Changes: notion (4.0.2+dfsg-5) unstable; urgency=medium . * dh_missing now flags warnings not errors (Closes: #987507) Checksums-Sha1: f86fc7094d8ded89aa447edc71079e1b3fa2b4ac 2009 notion_4.0.2+dfsg-5.dsc 35e0a019bc6e0fbc39d122ba245b2199dd9dc356 30412 notion_4.0.2+dfsg-5.debian.tar.xz bc279e3da81c8a15f1b7fe7680bc9b44d09df482 8544 notion_4.0.2+dfsg-5_amd64.buildinfo Checksums-Sha256: 7cdd2ea3895b93e880e9d98072d438c8c5a8dcf01fbe21a7aa4fdf3a1a16ee04 2009 notion_4.0.2+dfsg-5.dsc 0edc698ab9bd45d0db9d38bba938da4c4272650afa86b3728d1a8fbea52caff4 30412 notion_4.0.2+dfsg-5.debian.tar.xz a10f7f52950cd052c6c4ab707de336699e71d1d68462801281c61ba561456672 8544 notion_4.0.2+dfsg-5_amd64.buildinfo Files: 53c83b004243e551013750fe57582eaf 2009 x11 optional notion_4.0.2+dfsg-5.dsc 25d833f9a77438030ee9abed3b3bcd1d 30412 x11 optional notion_4.0.2+dfsg-5.debian.tar.xz
Bug#986839: marked as done (mpv: CVE-2021-30145 - demux_mf: improve format string processing)
Your message dated Mon, 26 Apr 2021 07:33:30 + with message-id and subject line Bug#986839: fixed in mpv 0.32.0-3 has caused the Debian Bug report #986839, regarding mpv: CVE-2021-30145 - demux_mf: improve format string processing 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.) -- 986839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mpv Version: 0.32.0-2+b1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team Dear Maintainer, Version 0.33.1 was released on Mon, 5 Apr 2021. Apparently this fixes a security problem (CVE-2021-30145) that affects every version since 2002. A description of the problem can be found at: https://github.com/mpv-player/mpv/commit/cb3fa04bcb2ba9e0d25788480359157208c13e0b The release can be found at: https://github.com/mpv-player/mpv/releases Thanks, Wessel Dankers -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mpv depends on: ii libarchive13 3.4.3-2+b1 ii libasound21.2.4-1.1 ii libass9 1:0.15.0-1 ii libavcodec58 7:4.3.2-0+deb11u1 ii libavdevice58 7:4.3.2-0+deb11u1 ii libavfilter7 7:4.3.2-0+deb11u1 ii libavformat58 7:4.3.2-0+deb11u1 ii libavutil56 7:4.3.2-0+deb11u1 ii libbluray21:1.2.1-4 ii libc6 2.31-11 ii libcaca0 0.99.beta19-2.2 ii libcdio-cdda2 10.2+2.0.0-1+b2 ii libcdio-paranoia2 10.2+2.0.0-1+b2 ii libcdio19 2.1.0-2 ii libdrm2 2.4.104-1 ii libdvdnav46.1.0-1+b1 ii libegl1 1.3.2-1 ii libgbm1 20.3.4-1 ii libgl11.3.2-1 ii libjack-jackd2-0 [libjack-0.125] 1.9.17~dfsg-1 ii libjpeg62-turbo 1:2.0.6-4 ii liblcms2-22.12~rc1-2 ii liblua5.2-0 5.2.4-1.1+b3 ii libpulse0 14.2-2 ii librubberband21.9.0-1 ii libsdl2-2.0-0 2.0.14+dfsg2-3 ii libsmbclient 2:4.13.5+dfsg-1 ii libsndio7.0 1.5.0-3 ii libswresample37:4.3.2-0+deb11u1 ii libswscale5 7:4.3.2-0+deb11u1 ii libuchardet0 0.0.7-1 ii libva-drm22.10.0-1 ii libva-wayland22.10.0-1 ii libva-x11-2 2.10.0-1 ii libva22.10.0-1 ii libvdpau1 1.4-3 ii libwayland-client01.18.0-2~exp1.1 ii libwayland-cursor01.18.0-2~exp1.1 ii libwayland-egl1 1.18.0-2~exp1.1 ii libx11-6 2:1.7.0-2 ii libxext6 2:1.3.3-1.1 ii libxinerama1 2:1.1.4-2 ii libxkbcommon0 1.0.3-2 ii libxrandr22:1.5.1-1 ii libxss1 1:1.2.3-1 ii libxv12:1.0.11-1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages mpv recommends: pn xdg-utils pn youtube-dl mpv suggests no packages. -- no debconf information signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: mpv Source-Version: 0.32.0-3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of mpv, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated mpv package) (This message was generated automatically at their request; if you believe that there is a problem with i
Bug#987534: marked as done (soundtouch builds with -march=native and NEON on armhf)
Your message dated Mon, 26 Apr 2021 08:34:30 + with message-id and subject line Bug#987534: fixed in soundtouch 2.2+ds1-2 has caused the Debian Bug report #987534, regarding soundtouch builds with -march=native and NEON on armhf 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.) -- 987534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: soundtouch Version: 2.2+ds1-1 Severity: serious soundtouch builds with -march=native, which makes the code run only on machines compatible with whatever buildd happened to build the package. NEON is not part of the armhf baseline. --- End Message --- --- Begin Message --- Source: soundtouch Source-Version: 2.2+ds1-2 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of soundtouch, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated soundtouch 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, 26 Apr 2021 10:14:22 +0200 Source: soundtouch Architecture: source Version: 2.2+ds1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 987534 Changes: soundtouch (2.2+ds1-2) unstable; urgency=medium . * Team upload * debian/rules: Disable neon on armhf (Closes: #987534) Checksums-Sha1: 32cec376d1be5d280b0e684aba83ccb78577622d 2212 soundtouch_2.2+ds1-2.dsc 6e91e1bc284eeaefa22f46d9829084a2ae31b8ca 9140 soundtouch_2.2+ds1-2.debian.tar.xz Checksums-Sha256: e955e5caccb177ba731ba8d5278fb1fbbdefe71207d6dc2b2490c77b7f2807c1 2212 soundtouch_2.2+ds1-2.dsc b186578fa46e454a61aaf74b58a135c9cc0ec0b426b915172beabc05159d4912 9140 soundtouch_2.2+ds1-2.debian.tar.xz Files: b25414eda3e5c571bad4d0c09e02c87a 2212 libs optional soundtouch_2.2+ds1-2.dsc 9b20b1429736923e9eed7aefaeef2f87 9140 libs optional soundtouch_2.2+ds1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmCGd74ACgkQafL8UW6n GZMcNg//YU+87uQ8SPDPjKpkUT4QmxD6oAmEuVD5l/DY52Qmj6xgj1Dj7DLtDyVQ xCbLuR+f9jBR5ODzRzYwhGlIitDpbDX75E2tCAEN7PAIHAkso+T3+pcI7ThU7JnO suyzUPmuqDxlUJlXXaPIY+xeRa8dns1vJW1Mpad15WYn/Al2Xk6MNB70Tyh0tFfM XBhE0winFkVWx4suseT+yGJp/9nPuw3lE+tZgucO5OZ7/vthPKOo3YqEEMDa7Xxl cEb0P11RyiqGmyqjXtFuxs6vYKP98I/iX627U6585hPWJWqRE29LxfgSC7q28H8h Y5WOeD4f8dGufT9D6rxWsYFs3h+h/9LAOHE9FVVFTWRNKxT9q5x3Lpf8Z3UybDSE X/AZBZbrL/Ba3iMoEY/3WPTgIhoQr6WxwsR5TkfQVugtP9edFSuUaY2FIROGlDtB 6cX83rCS/wOMFiFhhiTvdnTyJl4zJpoHKDZeo3SyhVwzAVMO0eY1Sw/0xfe92VRO V7DE9LnRaMbR/EU+fHoQa3FP13pBK0KWEgkA0t0BIEf+Si6+s2fF6h2M766xkw0V rXrJ3QMF6ffp27a+reXE63gkc6KpqpnWm04XZrXIPRU2T0aJHIzSOKfUdC5z8Yiy R5avqoXRuABw1DbGuA/tP4b2zc8S5Tg85/dbGVw8BGYfuuLnVJM= =6PdY -END PGP SIGNATURE End Message ---
Bug#949767: arrayfire update fails in configure step
Hi, I personally have no interest in arrayfire but I realised that the Debian packaged version depends clblas (and is the only remaining package that needs cblas and I would like to see it removed from Debian due to bug #949767) Thus I tried to upgrade arrayfire to the latest upstream version in Git but unfortunately it fails with: ... /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_d9514.dir/link.txt --verbose=1 /usr/lib/ccache/cc -g -O2 -ffile-prefix-map=/builds/science-team/arrayfire/debian/output/source_dir=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-z,relro -Wl,-z,now CMakeFiles/cmTC_d9514.dir/CheckFunctionExists.c.o -o cmTC_d9514 -lpthreads /usr/bin/ld: cannot find -lpthreads Since I have switched on salsa-ci you can see the full build log[1] in salsa. Any help to build the package successfully would be welcome. Kind regards Andreas. [1] https://salsa.debian.org/science-team/arrayfire/-/pipelines/249962 -- http://fam-tille.de
Bug#929685: clone issue instead of reassigning to both packages
Control: clone -1 -2 Control: reassign -2 src:ca-certificates Control: block -1 by -2 Didn't notice that the re-assign didn't work. ca-certificates also has a pull request on gitlab.
Processed: clone issue instead of reassigning to both packages
Processing control commands: > clone -1 -2 Bug #929685 [ca-certificates-java,default-jre-headless,openjdk-11-jre-headless] ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of the circular dependency Bug 929685 cloned as bug 987602 987602 was blocked by: 922981 987602 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #987602 to the same blocks previously set > reassign -2 src:ca-certificates Bug #987602 [ca-certificates-java,default-jre-headless,openjdk-11-jre-headless] ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of the circular dependency Bug reassigned from package 'ca-certificates-java,default-jre-headless,openjdk-11-jre-headless' to 'src:ca-certificates'. No longer marked as found in versions java-common/0.71, openjdk-11-jre, openjdk-11/11.0.3+1-1, and ca-certificates-java/20190405. Ignoring request to alter fixed versions of bug #987602 to the same values previously set > block -1 by -2 Bug #929685 [ca-certificates-java,default-jre-headless,openjdk-11-jre-headless] ca-certificates-java,default-jre-headless,openjdk-11-jre-headless: get rid of the circular dependency 929685 was blocked by: 922981 929685 was not blocking any bugs. Added blocking bug(s) of 929685: 987602 -- 929685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929685 987602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952899: pillow: d/copyright issues
On 4/24/21 6:55 PM, Romain Porte wrote: > Hi, > > Please find attached the debdiff that should fix most of the issues > listed (enough that the issue should not be marked "serious" anymore, > thus unblock bullseye release). > > Thanks! > > Romain, on behalf on the Debian Saslzburg BSP. ahh, forgot about it after forwarding. thanks for the NMU.
Bug#987603: XKB layout variants not shown in the g-c-c menu of respective language but under Others
Package: src:gnome-desktop3 Version: 3.38.4-1 Severity: serious The GUI in gnome-control-center for adding input sources is broken. The XKB layout variants should be visible in the menu of respective language, but instead they are all shown under "Others". A cherry pick of this upstream commit should fix it: https://gitlab.gnome.org/GNOME/gnome-desktop/-/commit/a56f1349 Cheers, Gunnar Hjalmarsson OpenPGP_signature Description: OpenPGP digital signature
Bug#987603: marked as pending in gnome-desktop3
Control: tag -1 pending Hello, Bug #987603 in gnome-desktop3 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/gnome-team/gnome-desktop/-/commit/68f55fcad90d8e192ac973a7e2288d766a60bed5 Fix issue in g-c-c GUI for adding input source Closes: #987603 (this message was generated automatically) -- Greetings https://bugs.debian.org/987603
Processed: Bug#987603 marked as pending in gnome-desktop3
Processing control commands: > tag -1 pending Bug #987603 [src:gnome-desktop3] XKB layout variants not shown in the g-c-c menu of respective language but under Others Added tag(s) pending. -- 987603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987535: marked as done (ggcov FTBFS: 1/21 tests passed)
Your message dated Mon, 26 Apr 2021 11:18:28 + with message-id and subject line Bug#987535: fixed in ggcov 0.10-3 has caused the Debian Bug report #987535, regarding ggcov FTBFS: 1/21 tests passed 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.) -- 987535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ggcov Version: 0.10-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/ggcov.html ... (cd test && ./runtest) Running tests hostname: "ionos5-amd64" date: "20220526T043014" uname -s: "Linux" uname -m: "x86_64" uname -r: "5.10.0-0.bpo.5-amd64" head -1 /etc/os-release: "PRETTY_NAME="Debian GNU/Linux bullseye/sid"" CC: "g++" which g++: "/usr/bin/g++" g++ --version: "g++ (Debian 10.2.1-6) 10.2.1 20210110" CXX: "g++" which g++: "/usr/bin/g++" g++ --version: "g++ (Debian 10.2.1-6) 10.2.1 20210110" ERROR: (test000) testrunner failed, see log ERROR: (test001) no output files from tggcov ERROR: (test002) no output files from tggcov ERROR: (test004) no output files from tggcov ERROR: (test005.1) no output files from tggcov ERROR: (test006) no output files from tggcov ERROR: (test007) no output files from tggcov ERROR: (test008.0) no output files from tggcov ERROR: (test009) no output files from tggcov ERROR: (test010) no output files from tggcov ERROR: (test011.1) no output files from tggcov ERROR: (test013) no output files from tggcov ERROR: (test014) no output files from tggcov ERROR: (test015.a001) no output files from tggcov ERROR: (test016.1) no output files from tggcov PASS: (test021) unit test for libpopt / fakepopt.c ERROR: (test026) no output files from tggcov ERROR: (test029) no output files from tggcov ERROR: (test030) no output files from tggcov ERROR: (test033) no output files from tggcov ERROR: (test034) no output files from tggcov Total: 1/21 tests passed make[1]: *** [debian/rules:35: override_dh_auto_test] Error 1 --- End Message --- --- Begin Message --- Source: ggcov Source-Version: 0.10-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of ggcov, 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 987...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated ggcov 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, 26 Apr 2021 11:41:37 +0100 Source: ggcov Architecture: source Version: 0.10-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 987535 Changes: ggcov (0.10-3) unstable; urgency=medium . * Update compiler patch for gcc-10.2. Closes: #987535 Checksums-Sha1: 8fa52f8af69eb8bc779dbf625e18e9f25ca1da7b 1933 ggcov_0.10-3.dsc a77290fcadefdc0e48c9424a3a816e2d0624073c 19056 ggcov_0.10-3.debian.tar.xz Checksums-Sha256: 8c213d082d599b1f8205030e79efc82a90322a6310d79cf49564d4306a68fd92 1933 ggcov_0.10-3.dsc b7459ed84451e2f8dc98b6d6c18ced2469070ea57f1eb70f0657931282a7f908 19056 ggcov_0.10-3.debian.tar.xz Files: 518b8bfe90a1fbb53cb17bdc87abbe8f 1933 devel optional ggcov_0.10-3.dsc b81f6944fee5c167ddae4940fef5db66 19056 devel optional ggcov_0.10-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmCGnskACgkQy+a7Tl2a 06Vuxw//S5tlSgAb7mgNQ0tRFp30FrcuEEKgMCJzTk9OsDIZS/qUfGZhwqBrREYa 8lWi9ddfHN99xgijClnvA59WRLFAcFr8SNm5XUpTPQgFk7dThFtPtOF+QuthAKrj H/Jc9clvads1FYY9WTTLj2zm+dQEWjFOAA+7Tuf9KyYmaq95aLsO2thz90LOnXVy TfMFsLEPX3UVPT3u9YywB0HRpgQZfquf1wKd+Hf4VWRGN8NDcUup5d+fb+mG+SPA 4VBS8OtBP/dalPzRvuBUNUSpwlM0KabWfVAbqYy3qusK03WklFlPyYbm4qreqjEP fyvtAZVLTamqugiI3YKLY3gAAxMuFFBzpbuVcZ96Jkqp/a0cnfOzkT5wgQYS4YGM MFe+QzcagLiaTy0Jc3ajrg1ksdItnBWPLkFnzduN++Ouq53qa+Hq4NMDIZBsHg4r KLVQN3ELHWoacniXJY2SPdwAhusqxwoVPt5/a4wRO/rOOBLWMSuplp48/OHF6D/i jSPve3kMpJhIaV9pJEAi1J7hTLwF/kYz6qabxjsGvWvSQSCXue5LbhGy9e+7v77Y gXRQiMahuNVOG+jvmPgJDUo8/bJjAs7VR6pEgrodwRvC26t2VnhpD+wVjTFuvKeS KIUoNjC7+K+iase56J0+SpImOPTC/LJd3oosQvKIcIwI6icmFYU= =SGBw -END PGP SIGNATURE End Message ---
Bug#949767: arrayfire update fails in configure step
Andreas Tille writes: > Hi, > > I personally have no interest in arrayfire but I realised that the > Debian packaged version depends clblas (and is the only remaining > package that needs cblas and I would like to see it removed from Debian > due to bug #949767) Hi, FWIW: It seems that arrayfire (which I know nothing about in general) has support [1,2] for using clblast (with a t) as an alternative to clblas. We do have a clblast package [3]. Could that be a way forward? [1] https://github.com/arrayfire/arrayfire/pull/1727 [2] https://github.com/arrayfire/arrayfire/issues/1956 [3] https://tracker.debian.org/pkg/clblast -- Gard signature.asc Description: PGP signature
Bug#949767: arrayfire update fails in configure step
Andreas Tille writes: > /usr/bin/ld: cannot find -lpthreads Thanks for posting a link to the full log! AFAICT, the actual errors appear much earlier, on lines 1573-1593: CMake Error: File /builds/science-team/arrayfire/debian/output/source_dir/extern/forge/CMakeModules/version.h.in does not exist. CMake Error at CMakeModules/AFconfigure_forge_submodule.cmake:47 (configure_file): configure_file Problem configuring file Call Stack (most recent call first): CMakeLists.txt:117 (include) CMake Error at CMakeLists.txt:163 (add_subdirectory): add_subdirectory given source "extern/spdlog" which is not an existing directory. CMake Error at CMakeLists.txt:164 (add_subdirectory): add_subdirectory given source "extern/glad" which is not an existing directory. -- Performing Test has_ignored_attributes_flag -- Performing Test has_ignored_attributes_flag - Success -- Performing Test has_all_warnings_flag -- Performing Test has_all_warnings_flag - Success CMake Error at /usr/share/cmake-3.18/Modules/ExternalProject.cmake:2350 (message): error: could not find git for clone of clFFT-ext Call Stack (most recent call first): /usr/share/cmake-3.18/Modules/ExternalProject.cmake:3206 (_ep_add_download_command) CMakeModules/build_clFFT.cmake:33 (ExternalProject_Add) src/backend/opencl/CMakeLists.txt:15 (include) The subsequent output consists of dumps of CMake's internal logs, which sometimes provide additional clues but need to be taken in context; for instance, the -lpthreads error comes from -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE (ll. 1472-1480). -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Processed: Re: XKB layout variants not shown in the g-c-c menu of respective language but under Others
Processing commands for cont...@bugs.debian.org: > severity 987603 important Bug #987603 [src:gnome-desktop3] XKB layout variants not shown in the g-c-c menu of respective language but under Others Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 987603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984767: dh-virtualenv: Can't build packages with compat >= 12 as --buildsystem doesn't work
severity 984767 normal tag 984767 + moreinfo thanks ❦ 8 mars 2021 08:55 +01, Johann Queuniet: > I have issues with building packages with dh-virtualenv using a compat > of 12 or higher, ending up with the following error: > > ``` > debian/rules binary > dh binary --with python-virtualenv --python /usr/bin/python3 >dh_update_autotools_config -O--python=/usr/bin/python3 >dh_autoreconf -O--python=/usr/bin/python3 >dh_auto_configure -O--python=/usr/bin/python3 > dh_auto_configure: warning: Please use the third-party "pybuild" build system > instead of python-distutils > dh_auto_configure: error: This feature was removed in compat 12. > make: *** [debian/rules:4: binary] Error 255 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > ``` > > If I try to ask for pybuild with --buildsystem, the build goes a bit > further, but still fails: > > ``` > debian/rules binary > dh binary --with python-virtualenv --builtin-venv --python /usr/bin/python3 > --buildsystem=pybuild >dh_update_autotools_config -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild >dh_autoreconf -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild >dh_auto_configure -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild > I: pybuild base:232: python3.9 setup.py config > running config >create-stamp debian/debhelper-build-stamp >dh_testroot -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild >dh_prep -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild >dh_installdocs -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild >dh_installchangelogs -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild >dh_virtualenv -O--builtin-venv -O--python=/usr/bin/python3 > -O--buildsystem=pybuild > Usage: dh_virtualenv [options] > > dh_virtualenv: error: no such option: --buildsystem > make: *** [debian/rules:4: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > ``` I am able to build with compatibility 12: %: dh $@ --buildsystem=pybuild --with python-virtualenv override_dh_virtualenv: dh_virtualenv --python python3 I don't remember if you tried that. So, while it could work out of the box without overriding dh_virtualenv, it works good enough to be in a release, with two solutions: - use compatibility 11 - override dh_virtualenv invocation to not chocke on --buildsystem=pybuild Also, it seems you pass --builtin-venv to dh, you only need to pass it to dh_virtualenv. -- 10.0 times 0.1 is hardly ever 1.0. - The Elements of Programming Style (Kernighan & Plauger)
Processed: Re: Bug#984767: dh-virtualenv: Can't build packages with compat >= 12 as --buildsystem doesn't work
Processing commands for cont...@bugs.debian.org: > severity 984767 normal Bug #984767 [dh-virtualenv] dh-virtualenv: Can't build packages with compat >= 12 as --buildsystem doesn't work Severity set to 'normal' from 'serious' > tag 984767 + moreinfo Bug #984767 [dh-virtualenv] dh-virtualenv: Can't build packages with compat >= 12 as --buildsystem doesn't work Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 984767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973188: marked as done (virt-top: FTBFS: Error: Cannot find file camlheader_pic)
Your message dated Mon, 26 Apr 2021 13:03:29 + with message-id and subject line Bug#973188: fixed in virt-top 1.0.9-1.1 has caused the Debian Bug report #973188, regarding virt-top: FTBFS: Error: Cannot find file camlheader_pic 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.) -- 973188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: virt-top Version: 1.0.9-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 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 '/<>/src' > rm -f .depend .depend-t > ocamlfind ocamldep -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv collect.mli csv_output.mli > redraw.mli screen.mli stream_output.mli top.mli types.mli utils.mli > collect.ml csv_output.ml main.ml opt_calendar.ml opt_csv.ml opt_gettext.ml > opt_xml.ml redraw.ml screen.ml stream_output.ml top.ml types.ml utils.ml > version.ml | \ > sed 's/ :/:/' | \ > sed 's/ *$//' | \ > sed -e :a -e '/ *\\$/N; s/ *\\\n */ /; ta' | \ > sort > .depend-t > mv .depend-t .depend > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c version.ml > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c opt_gettext.ml > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c utils.mli > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c types.mli > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c screen.mli > pod2man -c "Virtualization Support" --release "virt-top-1.0.9" \ > virt-top.pod > virt-top.1 > pod2text virt-top.pod > virt-top.txt > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c utils.ml > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c types.ml > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c collect.mli > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c screen.ml > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c top.mli > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv -c opt_xml.ml > ocamlfind ocamlc -g -warn-error CDEFLMPSUVYZX-3 -ccopt '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' -package unix,extlib,curses,str,libvirt -package > gettext-stub -package xml-light -package csv
Processed: user debian...@lists.debian.org, usertagging 983429, severity of 983429 is serious ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 983429 piuparts There were no usertags set. Usertags are now: piuparts. > severity 983429 serious Bug #983429 [mosquitto] mosquitto: /run/mosquitto is on a tmpfs and should be created dynamically Severity set to 'serious' from 'minor' > found 983429 2.0.10-5 Bug #983429 [mosquitto] mosquitto: /run/mosquitto is on a tmpfs and should be created dynamically Marked as found in versions mosquitto/2.0.10-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 983429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987610: wims-lti: modifies shipped files: /var/lib/wims-lti/wimsLTI/config.py
Package: wims-lti Version: 0.4.4.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies shipped files. debsums reports modification of the following files, from the attached log (scroll to the bottom...): 0m52.5s ERROR: FAIL: debsums reports modifications inside the chroot: /var/lib/wims-lti/wimsLTI/config.py cheers, Andreas wims-lti_0.4.4.1-2.log.gz Description: application/gzip
Bug#987614: libica FTBFS with gcc 10
Source: libica Version: 3.2.0-3 Severity: serious Tags: ftbfs ... /usr/bin/ld: /tmp/ccGQQSb3.o:/home/bunk/build/libica-3.2.0/src/tests/libica_sha_test/./include/sha_tests.h:26: multiple definition of `silent'; /tmp/ccbkY0gZ.o:/home/bunk/build/libica-3.2.0/src/tests/libica_sha_test/./include/sha_tests.h:26: first defined here /usr/bin/ld: /tmp/ccGQQSb3.o:/home/bunk/build/libica-3.2.0/src/tests/libica_sha_test/../testcase.h:17: multiple definition of `verbosity_'; /tmp/ccbkY0gZ.o:/home/bunk/build/libica-3.2.0/src/tests/libica_sha_test/../testcase.h:17: first defined here collect2: error: ld returned 1 exit status make[2]: *** [Makefile:523: all] Error 1
Processed: Re: Bug#986779: preinst script misses dependency on dpkg-dev
Processing control commands: > tag -1 buster Bug #986779 [fwupd] preinst script misses dependency on dpkg-dev Added tag(s) buster. > severity -1 serious Bug #986779 [fwupd] preinst script misses dependency on dpkg-dev Severity set to 'serious' from 'normal' -- 986779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987388: Crash of amdgpu on Debian 11 Bullseye
I think I am also experiencing this bug. I'm seeing it manifest when I resume from sleep, none of my monitors wake up and I can't switch TTYs. On Thu, 22 Apr 2021 21:10:15 + "Maxime G." wrote: > Package: xserver-xorg-video-amdgpu > Version: 19.1.0-2 > Severity: critical > > Hi. > > Today I reinstalled a machine on Debian 11 Bullseye from testing (it was on Debian 10 Buster) and I had a crash of the AMD R9 380. > I could no longer change tty and Xorg was frozen, I could only move the mouse, the keyboard shortcut to reboot the kernel was not working. > After manual shutdown (electrical) I found undred lines of this in syslog: > > Apr 22 22:36:18 maxime-pc kernel: [18427.590382] amdgpu :01:00.0: amdgpu: 3fb1172e pin failed > Apr 22 22:36:18 maxime-pc kernel: [18427.590464] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 > Apr 22 22:36:18 maxime-pc kernel: [18427.605898] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed > Apr 22 22:36:18 maxime-pc kernel: [18427.606010] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 > Apr 22 22:36:18 maxime-pc kernel: [18427.609057] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed > Apr 22 22:36:18 maxime-pc kernel: [18427.609139] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 > Apr 22 22:36:18 maxime-pc kernel: [18427.610566] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed > Apr 22 22:36:18 maxime-pc kernel: [18427.610644] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 > Apr 22 22:36:18 maxime-pc kernel: [18427.644577] amdgpu :01:00.0: amdgpu: 3fb1172e pin failed > Apr 22 22:36:18 maxime-pc kernel: [18427.644659] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 > > [...] > > Apr 22 22:37:15 maxime-pc kernel: [18484.803085] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa > ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) > Apr 22 22:37:15 maxime-pc kernel: [18484.803096] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa > ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) > Apr 22 22:37:18 maxime-pc kernel: [18487.595072] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa > ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) > Apr 22 22:37:18 maxime-pc kernel: [18487.875072] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa > ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) > > (here I was typing on the emergency kernel reboot shortcut on keyboard) > > I don't know what could be the reason for this. > But the problem has never occurred on Debian 10 Buster. > > > Thanks. > Max. > >
Processed: forcibly merging 987588 987589
Processing commands for cont...@bugs.debian.org: > forcemerge 987588 987589 Bug #987588 [sshguard] sshguard: The sshguard package in the testing & stable branches is outdated and buggy Bug #987589 [sshguard] sshguard in both of stable and testing branches is buggy and outdated Merged 987588 987589 > thanks Stopping processing here. Please contact me if you need assistance. -- 987588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987588 987589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987504: imagemagick: attempt to perform an operation not allowed by the security policy `EPS'
On Mon, Apr 26, 2021 at 12:41:42PM +0800, Paul Wise wrote: >... > I think that switching the ImageMagick policy so that it allows writes > to PS/PS2/PS3/EPS/PDF/XPS/etc but not reads would fix the FTBFS and > possibly also stop security issues in GhostScript from being triggered? >From the Launchpad bug: 14:44 png -> ps should be safe. 14:44 yeah, unfortunately imagemagick doesn't allow disable only reading > bye, > pabs cu Adrian
Bug#986599: marked as done (libmpich-dev: leaves alternatives after purge: /etc/alternatives/mpi-)
Your message dated Mon, 26 Apr 2021 17:04:08 + with message-id and subject line Bug#986599: fixed in mpich 3.4.1-4 has caused the Debian Bug report #986599, regarding libmpich-dev: leaves alternatives after purge: /etc/alternatives/mpi- 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.) -- 986599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmpich-dev Version: 3.4.1-3 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-removal-and-or-configuration-purging The leftover files are actually alternatives that were installed by the package but have not been properly removed. While there is ongoing discussion how to remove alternatives correctly (see https://bugs.debian.org/71621 for details) the following strategy should work for regular cases: * 'postinst configure' always installs the alternative * 'prerm remove' removes the alternative * 'postrm remove' and 'postrm disappear' remove the alternative In all other cases a maintainer script is invoked (e.g. upgrade, deconfigure) the alternatives are not modified to preserve user configuration. Removing the alternative in 'prerm remove' avoids having a dangling link once the actual file gets removed, but 'prerm remove' is not called in all cases (e.g. unpacked but not configured packages or disappearing packages) so the postrm must remove the alternative again (update-alternatives gracefully handles removal of non-existing alternatives). Note that the arguments for adding and removing alternatives differ, for removal it's 'update-alternatives --remove '. Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 1m23.8s INFO: Warning: Package purging left files on system: /etc/alternatives/libmpi++.so-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libmpichcxx.so not owned /etc/alternatives/libmpi.so-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libmpich.so not owned /etc/alternatives/libmpicxx.so-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libmpichcxx.sonot owned /etc/alternatives/libmpif77.so-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libmpichfort.so not owned /etc/alternatives/libmpif90.so-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libmpichfort.so not owned /etc/alternatives/libmpifort.so-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libmpichfort.so not owned /etc/alternatives/mpi-c.pc-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/pkgconfig/mpich-c.pc not owned /etc/alternatives/mpi-cxx.pc-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/pkgconfig/mpich-cxx.pc not owned /etc/alternatives/mpi-fort.pc-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/pkgconfig/mpich-fort.pcnot owned /etc/alternatives/mpi-x86_64-linux-gnu -> /usr/include/x86_64-linux-gnu/mpich not owned /etc/alternatives/mpi.pc-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/pkgconfig/mpich.pc not owned This was observed after a buster->bullseye upgrade. cheers, Andreas libmpich-dev_3.4.1-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mpich Source-Version: 3.4.1-4 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of mpich, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated mpich 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, 26 Apr 2021 18:34:55 +0200 Source: mpich Architecture: source Version: 3.4.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Beckmann Closes: 985394 986599 Changes: mpich (3.4.1-4) unstable; urgency=medium . * Team upload. * libmpich-dev: Fix maintainer script genera
Processed: [bts-link] source package cinnamon-session
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package cinnamon-session > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #986099 (http://bugs.debian.org/986099) > # Bug title: cinnamon-session: Should not upload XDG_SESSION_ID to systemd > --user > # * https://github.com/linuxmint/cinnamon-session/issues/140 > # * remote status changed: open -> closed > # * closed upstream > tags 986099 + fixed-upstream Bug #986099 [cinnamon-session] cinnamon-session: Should not upload XDG_SESSION_ID to systemd --user Added tag(s) fixed-upstream. > usertags 986099 - status-open Usertags were: status-open. There are now no usertags set. > usertags 986099 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 986099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: linux-kbuild-5.10: please add Breaks: sl-modem-dkms (<< 2.9.11~20110321-16.0)
Processing control commands: > severity -1 important Bug #987575 [linux-kbuild-5.10] linux-kbuild-5.10: please add Breaks: sl-modem-dkms (<< 2.9.11~20110321-16.0) Severity set to 'important' from 'serious' -- 987575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987575: linux-kbuild-5.10: please add Breaks: sl-modem-dkms (<< 2.9.11~20110321-16.0)
Control: severity -1 important I don't believe this should be considered an RC bug in Linux packages, but we should still mitigate the problem. There are three different bugs involved: 1. linux-headers-*-common uses the upstream Makefile, which defaults to attempting a full kernel build. That will always fail, and potentially removes installed files as reported. 2. DKMS (and module-assistant?) do module builds as root by default. 3. Some OOT modules use the now-unsupported SUBDIRS variable instead of M or KBUILD_EXTMOD, triggering bug 1. Due to bug 2, this can remove root-owned files. Bug 3 does/did not only exist in the 2 known bad packages in Debian, but also probably in other older packages and unpackaged modules. So I think we cannot comprehensively fix it or avoid it by using "Breaks" relations. (And I would like to avoid the kernel team having to maintain a list of all currently broken OOT modules.) Bugs 1 and 2 should be fixed, but this probably isn't achievable before the bullseye release. So I propose a mitigation of bug 1: if the Makefile is invoked with SUBDIRS set but neither M nor KBUILD_EXTMOD is also set, we abort the build: https://salsa.debian.org/kernel-team/linux/-/merge_requests/353 Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Bug#981422: marked as done (xdg-utils: autopkgtest failure: make: dh: No such file or directory)
Your message dated Mon, 26 Apr 2021 18:03:55 + with message-id and subject line Bug#981422: fixed in xdg-utils 1.1.3-4.1 has caused the Debian Bug report #981422, regarding xdg-utils: autopkgtest failure: make: dh: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 981422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xdg-utils Version: 1.1.3-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package xdg-utils, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. Seems like your missing test dependencies. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=xdg-utils https://ci.debian.net/data/autopkgtest/testing/amd64/x/xdg-utils/9808301/log.gz autopkgtest [01:30:39]: test with-bash: [--- + debian/rules patch dh patch make: dh: No such file or directory make: *** [debian/rules:6: patch] Error 127 autopkgtest [01:30:39]: test with-bash: ---] autopkgtest [01:30:44]: test with-dash: [--- + debian/rules patch dh patch make: dh: No such file or directory make: *** [debian/rules:6: patch] Error 127 autopkgtest [01:30:44]: test with-dash: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: xdg-utils Source-Version: 1.1.3-4.1 Done: Roland Clobus We believe that the bug you reported is fixed in the latest version of xdg-utils, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Clobus (supplier of updated xdg-utils 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, 25 Apr 2021 16:00:00 +0200 Source: xdg-utils Architecture: source Version: 1.1.3-4.1 Distribution: unstable Urgency: medium Maintainer: Debian freedesktop.org maintainers Changed-By: Roland Clobus Closes: 981422 Changes: xdg-utils (1.1.3-4.1) unstable; urgency=medium . * Non-maintainer upload. * Simplified handling for ttyon and ttyoff, with thanks to Nicolas Boulenguez . (closes: 981422) Checksums-Sha1: 9b894b96bc741f85b9a33bbe1870b3faad70755f 1756 xdg-utils_1.1.3-4.1.dsc ae5f9afb9bcb23fb18e743b2104707f863626cb5 15660 xdg-utils_1.1.3-4.1.debian.tar.xz Checksums-Sha256: c54ae65034c4c3e9f2208a44990111d34fc5ed1e689efd3907a2a8e5e965ccac 1756 xdg-utils_1.1.3-4.1.dsc 0ea0b550719ab75f9a0fe58ed907673c5bcfc2bd87537845534694c502740aed 15660 xdg-utils_1.1.3-4.1.debian.tar.xz Files: bd72f442f1ae41959af723d79f7bd486 1756 utils optional xdg-utils_1.1.3-4.1.dsc d556a461933824b183ef261ff17e7bde 15660 utils optional xdg-utils_1.1.3-4.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmCG+d0ACgkQnFyZ6wW9 dQrmkgf+LS9ouZ+dVYxwj/H3o6DUVImlfobXMXAKFXCObMlEjs4FKYRTh+BeUu0H dR3xNbSVBbB/+MCO3EkjbQO8CZjZMe81JDbvPb9n/ttPJ+9SN8xa3VDtjNbdNS58 h+acnr5NFnoasbPVvR7nfHNhmCUitSVycndLG53k0M4q66Fl6fPl8ZEeLH2G4izh oWhNBaf10Nf/zNoQMRtFC6bxGp1KKBBeE1po7f7ldFer7AClIT8Bitjfj452RfMB zWiKbAgtqIcg0VffjzRHQ9BbvGYrSZZylmk8dogfTOI4dmhJMNbkGLLikY/yl1Gr WY0lQB0N7msZ1DjJ3GXDof5Vw+4rVQ== =qpG8 -END PGP SIGNATURE End Message ---
Bug#981422: NMU planned for DELAYED/5
Dear maintainers, On Sun, 25 Apr 2021 22:26:09 +0200 Roland Clobus wrote: > this ticket was handled during the BSP in Salzburg, which took place > this weekend. > > A simplified handling of ttyon and ttyoff was implemented. > Paul Gevers is planning to NMU the patch in MR5 [1] > tomorrow to DELAYED/5. Indeed, it was my intention to upload to DELAYED. However, unintentionally I forgot to add the right commands to dput and I failed calling the dcut in the right way (or quick enough). Sorry if I stepped on somebodies toes. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#987509: marked as done (libgranite6: missing Breaks+Replaces: libgranite5)
Your message dated Mon, 26 Apr 2021 15:16:34 -0400 with message-id <684cd3958c95d451b93a01bdf68069d0004146a9.ca...@debian.org> and subject line Bug fixed in recent upload has caused the Debian Bug report #987509, regarding libgranite6: missing Breaks+Replaces: libgranite5 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.) -- 987509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgranite6 Version: 6.0.0-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libgranite6_6.0.0-1~exp1_amd64.deb ... Unpacking libgranite6:amd64 (6.0.0-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libgranite6_6.0.0-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/share/metainfo/granite.appdata.xml', which is also in package libgranite5:amd64 5.5.0-1 Errors were encountered while processing: /var/cache/apt/archives/libgranite6_6.0.0-1~exp1_amd64.deb cheers, Andreas libgranite5=5.5.0-1_libgranite6=6.0.0-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 6.0.0-1~exp2 This is fixed in the most recent upload. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: severity of 987608 is grave
Processing commands for cont...@bugs.debian.org: > severity 987608 grave Bug #987608 [src:shibboleth-sp] shibboleth-sp: Session recovery feature contains a null pointer deference Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 987608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 987608
Processing commands for cont...@bugs.debian.org: > tags 987608 + fixed-upstream Bug #987608 [src:shibboleth-sp] shibboleth-sp: Session recovery feature contains a null pointer deference Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 987608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987496: marked as pending in salt
Control: tag -1 pending Hello, Bug #987496 in salt 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/salt-team/salt/-/commit/71f7f30851f9609bfda5a1b0f5b115d2743372cd Fix CVE-2021-31607 in snapper module In SaltStack Salt 2016.9 through 3002.6, a command injection vulnerability exists in the snapper module that allows for local privilege escalation on a minion. The attack requires that a file is created with a pathname that is backed up by snapper, and that the master calls the snapper.diff function (which executes popen unsafely). Cherry-pick the fix from pull request #59648 [1], but also fix the regression introduced by that commit [2]. [1] https://github.com/saltstack/salt/pull/59648 [2] https://github.com/saltstack/salt/issues/60046 Closes: #987496 Signed-off-by: Benjamin Drung (this message was generated automatically) -- Greetings https://bugs.debian.org/987496
Processed: Bug#987496 marked as pending in salt
Processing control commands: > tag -1 pending Bug #987496 [src:salt] salt: CVE-2021-31607 Added tag(s) pending. -- 987496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987631: micro-evtd FTBFS with glibc 2.30
Source: micro-evtd Version: 3.4-5 Severity: serious Tags: ftbfs bullseye sid ... src/micro-evtd.c:49:10: fatal error: sys/io.h: No such file or directory 49 | #include | ^~ compilation terminated. make[2]: *** [micro-evtd.mak:185: obj/micro-evtd.o] Error 1 Removing the #include fixes the build.
Bug#987636: libcxl FTBFS with make 4.3
Source: libcxl Version: 1.7-1 Severity: serious Tags: ftbfs bullseye sid patch Forwarded: https://github.com/ibm-capi/libcxl/pull/34 ... dh_auto_build -a make -j16 "INSTALL=install --strip-program=true" make[1]: Entering directory '/home/bunk/build/libcxl-1.7' Makefile:28: *** 'cxl.h is non-existant or out of date, Download from http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/include/uapi/misc/cxl.h and place in /home/bunk/build/libcxl-1.7/include/misc/cxl.h'. Stop. make[1]: Leaving directory '/home/bunk/build/libcxl-1.7' dh_auto_build: error: make -j16 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:8: build-arch] Error 25
Bug#987637: fenix FTBFS with gcc 10
Source: fenix Version: 0.92a.dfsg1-12 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/fenix.html ... gcc -g -O2 -fdebug-prefix-map=/build/fenix-0.92a.dfsg1=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-strict-aliasing -DUSE_GETTEXT -Wl,-z,relro -Wl,-z,defs -o fxc main.o main_div.o token.o identifier.o segment.o constants.o strings.o varspace.o procedure.o codeblock.o c_main.o c_data.o c_code.o c_debug.o dcbw.o messages.o error.o sysstub.o typedef.o files.o xctype.o -L/usr/lib/i386-linux-gnu -lSDL -Wl,-Bdynamic -lc -lz -lX11 -lm -ldl /usr/bin/ld: c_main.o:./fxc/src/c_main.c:185: multiple definition of `debug'; main.o:./fxc/src/main.c:60: first defined here collect2: error: ld returned 1 exit status make[4]: *** [Makefile:391: fxc] Error 1
Bug#987639: smlsharp FTBFS with gcc 10
Source: smlsharp Version: 1.2.0-2 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/smlsharp.html ... (cd precompiled/x86-linux \ && gcc -m32 -Wl,-z,relro -Wl,-z,now ../../src/runtime/smlsharp_entry.o \ `cat ../minismlsharp-files` \ ../../src/runtime/libsmlsharp.a \ -lpthread -ldl -lgmp -lm -o ../../minismlsharp) /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:364: multiple definition of `SMLN8SMLSharp12MatchCompBugE'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:364: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:363: multiple definition of `SMLN2OS6SysErrE'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:363: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:362: multiple definition of `SML4Fail'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:362: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:361: multiple definition of `SML6Domain'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:361: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:360: multiple definition of `SML3Div'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:360: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:359: multiple definition of `SML8Overflow'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:359: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:358: multiple definition of `SML4Size'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:358: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:357: multiple definition of `SML9Subscript'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:357: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:356: multiple definition of `SML5Match'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:356: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:355: multiple definition of `SML4Bind'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:355: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(heap_bitmap.o):./src/runtime/smlsharp.h:290: multiple definition of `sml_check_gc_flag'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:290: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:290: multiple definition of `sml_check_gc_flag'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:290: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:364: multiple definition of `SMLN8SMLSharp12MatchCompBugE'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:364: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:363: multiple definition of `SMLN2OS6SysErrE'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:363: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:362: multiple definition of `SML4Fail'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:362: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:361: multiple definition of `SML6Domain'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:361: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:360: multiple definition of `SML3Div'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:360: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:359: multiple definition of `SML8Overflow'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:359: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:358: multiple definition of `SML4Size'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:358: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:357: multiple definition of `SML9Subscript'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:357: first defined here /usr/bin/ld: ../../src/runtime/libsmlsharp.a(control.o):./src/runtime/smlsharp.h:356: multiple definition of `SML5Match'; ../../src/runtime/smlsharp_entry.o:././src/runtime/smlsharp.h:356: first defined here /usr/bin/ld: ../../sr
Bug#987640: zsnes FTBFS with gcc 10
Source: zsnes Version: 1.510+bz2-10 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/zsnes.html ... g++ -o zsnes cfg.o endmem.o init.o initc.o input.o md.o patch.o ui.o vcache.o version.o zloader.o zmovie.o zpath.o zstate.o ztime.o ztimec.o chips/c4emu.o chips/c4proc.o chips/dsp1emu.o chips/dsp1proc.o chips/dsp2proc.o chips/dsp3emu.o chips/dsp3proc.o chips/dsp4emu.o chips/dsp4proc.o chips/fxemu2.o chips/fxemu2b.o chips/fxemu2c.o chips/fxtable.o chips/obc1emu.o chips/obc1proc.o chips/sa1proc.o chips/sa1regs.o chips/sdd1emu.o chips/seta10.o chips/sfxproc.o chips/st10proc.o chips/7110proc.o chips/seta11.o chips/st11proc.o cpu/dma.o cpu/dsp.o cpu/dspproc.o cpu/execute.o cpu/executec.o cpu/irq.o cpu/memory.o cpu/memtable.o cpu/spc700.o cpu/stable.o cpu/table.o cpu/tablec.o debugasm.o debugger.o gui/gui.o gui/guifuncs.o gui/menu.o effects/burn.o effects/smoke.o effects/water.o jma/7zlzma.o jma/crc32.o jma/iiostrm.o jma/inbyte.o jma/jma.o jma/lzma.o jma/lzmadec.o jma/winout.o jma/zsnesjma.o mmlib/mm.o mmlib/linux.o video/makev16b.o video/makev16t.o video/makevid.o video/mode716.o video/mode716b.o video/mode716d.o video/mode716e.o video/mode716t.o video/mode7.o video/mode7ext.o video/mv16tms.o video/m716text.o video/newg162.o video/newgfx.o video/newgfx16.o video/newgfx2.o video/procvid.o video/procvidc.o video/sw_draw.o video/2xsaiw.o video/hq2x16.o video/hq2x32.o video/hq3x16.o video/hq3x32.o video/hq4x16.o video/hq4x32.o video/ntsc.o video/copyvwin.o linux/audio.o linux/battery.o linux/sdlintrf.o linux/sdllink.o linux/gl_draw.o linux/sw_draw.o linux/safelib.o zip/unzip.o zip/zpng.o -g -O2 -fdebug-prefix-map=/build/zsnes-1.510+bz2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -I. -I/usr/local/include -I/usr/include -D__UNIXSDL__ -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -D__OPENGL__ -march=i486 -O3 -fomit-frame-pointer -fprefetch-loop-arrays -fforce-addr -D__RELEASE__ -fno-rtti -Wl,-z,relro -Wl,--as-needed -lpthread -L/usr/local/lib -L/usr/lib -lz -L/usr/lib/i386-linux-gnu -lSDL -lpng -lm -lcurses -lGL /usr/bin/ld: initc.o:./src/initc.c:1499: multiple definition of `HacksDisable'; cfg.o:./src/cfg.c:269: first defined here ...
Bug#987641: e2fsprogs: FTBFS on armel/armhf with a 64-bit kernel
Source: e2fsprogs Version: 1.46.2-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source (but built successfully in the past) Forwarded: https://github.com/tytso/e2fsprogs/issues/65 e2fsprogs builds fine on armel/armhf when built on a machine with a 32-bit kernel. However it fails to build on a machine with a 64-bit kernel due to alignments issues which are not trapped by the kernel: A build log is available there: https://tests.reproducible-builds.org/debian/logs/unstable/armhf/e2fsprogs_1.46.2-1.build2.log.gz
Bug#987643: ne10 FTBFS with gcc 10
Source: ne10 Version: 1.2.1-4 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/arm64/ne10.html ... cd /build/ne10-1.2.1/obj-aarch64-linux-gnu/test && /usr/bin/cmake -E cmake_link_script CMakeFiles/NE10_imgproc_unit_test_static.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fdebug-prefix-map=/build/ne10-1.2.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -O2 -DNDEBUG -Wl,-z,relro -rdynamic CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_main.c.o CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_suite_resize.c.o CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_suite_rotate.c.o CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_suite_boxfilter.c.o CMakeFiles/NE10_imgproc_unit_test_static.dir/src/seatest.c.o CMakeFiles/NE10_imgproc_unit_test_static.dir/src/unit_test_common.c.o CMakeFiles/NE10_imgproc_unit_test_static.dir/src/NE10_random.c.o -o NE10_imgproc_unit_test_smoke ../modules/libNE10.a -lm -lrt -lstdc++ /usr/bin/ld: CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_suite_resize.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: multiple definition of `seatest_simple_test_result'; CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_main.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: first defined here /usr/bin/ld: CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_suite_rotate.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: multiple definition of `seatest_simple_test_result'; CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_main.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: first defined here /usr/bin/ld: CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_suite_boxfilter.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: multiple definition of `seatest_simple_test_result'; CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_main.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: first defined here /usr/bin/ld: CMakeFiles/NE10_imgproc_unit_test_static.dir/src/seatest.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: multiple definition of `seatest_simple_test_result'; CMakeFiles/NE10_imgproc_unit_test_static.dir/__/modules/imgproc/test/test_main.c.o:./obj-aarch64-linux-gnu/test/./test/include/seatest.h:23: first defined here [ 96%] Building C object test/CMakeFiles/NE10_dsp_unit_test_static.dir/src/seatest.c.o cd /build/ne10-1.2.1/obj-aarch64-linux-gnu/test && /usr/bin/cc -DSMOKE_TEST -I/build/ne10-1.2.1/inc -I/build/ne10-1.2.1/test/include -g -O2 -fdebug-prefix-map=/build/ne10-1.2.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -O2 -DNDEBUG -O0 -o CMakeFiles/NE10_dsp_unit_test_static.dir/src/seatest.c.o -c /build/ne10-1.2.1/test/src/seatest.c [ 97%] Building C object test/CMakeFiles/NE10_dsp_unit_test_static.dir/src/unit_test_common.c.o cd /build/ne10-1.2.1/obj-aarch64-linux-gnu/test && /usr/bin/cc -DSMOKE_TEST -I/build/ne10-1.2.1/inc -I/build/ne10-1.2.1/test/include -g -O2 -fdebug-prefix-map=/build/ne10-1.2.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -O2 -DNDEBUG -O0 -o CMakeFiles/NE10_dsp_unit_test_static.dir/src/unit_test_common.c.o -c /build/ne10-1.2.1/test/src/unit_test_common.c [ 98%] Building C object test/CMakeFiles/NE10_dsp_unit_test_static.dir/src/NE10_random.c.o cd /build/ne10-1.2.1/obj-aarch64-linux-gnu/test && /usr/bin/cc -DSMOKE_TEST -I/build/ne10-1.2.1/inc -I/build/ne10-1.2.1/test/include -g -O2 -fdebug-prefix-map=/build/ne10-1.2.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -O2 -DNDEBUG -O0 -o CMakeFiles/NE10_dsp_unit_test_static.dir/src/NE10_random.c.o -c /build/ne10-1.2.1/test/src/NE10_random.c collect2: error: ld returned 1 exit status make[3]: *** [test/CMakeFiles/NE10_imgproc_unit_test_static.dir/build.make:197: test/NE10_imgproc_unit_test_smoke] Error 1 make[3]: Leaving directory '/build/ne10-1.2.1/obj-aarch64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:281: test/CMakeFiles/NE10_imgproc_unit_test_static.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [ 99%] Linking C executable NE10_dsp_unit_test_smoke cd /build/ne10-1.2.1/obj-aarch64-linux-gnu/test && /usr/bin/cmake -E cmake_link_script CMakeFiles/NE10_dsp_unit_test_static.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/ne10-1.2.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -O2 -DNDEBUG -Wl,-z,relro -rdynamic CMakeFile
Bug#986565: marked as done (unusable with current git)
Your message dated Mon, 26 Apr 2021 21:18:25 + with message-id and subject line Bug#986565: fixed in git-flow 1.12.3-3 has caused the Debian Bug report #986565, regarding unusable with current git 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.) -- 986565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: git-flow Version: 1.12.3-1 Severity: grave Tags: patch Today 'flow' is not a supported git command: $git flow git: 'flow' is not a git command. See 'git --help'. The most similar commands are reflog show Running it under strace reveals that git looks for commands under /usr/libexec/git-core, while git-flow installs things under /usr/lib/git-core Perhaps this is caused by a change in the search path in git and git-flow needs to adapt. Replacing /usr/lib/git-core with /usr/libexec/git-core in debian/install.mk seems to fix the problem. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git-flow depends on: ii git [git-core] 1:2.31.0-1 ii git-core1:2.15.0~rc0-1 git-flow recommends no packages. git-flow suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Source: git-flow Source-Version: 1.12.3-3 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of git-flow, 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 986...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated git-flow 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, 26 Apr 2021 22:22:51 +0200 Source: git-flow Architecture: source Version: 1.12.3-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 986565 Changes: git-flow (1.12.3-3) unstable; urgency=medium . * Install git-flow commands to $PATH and not to Git internal directory (closes: #986565). Checksums-Sha1: a827bc00e586ea7ecf0115c60c60180c4f42ad98 2005 git-flow_1.12.3-3.dsc de87b17671d6d8ca4a7831ae5c40d2023c588e78 4656 git-flow_1.12.3-3.debian.tar.xz Checksums-Sha256: 6157241c859b66eff396c5643b120dee90f3e9a08690562e042f51cdd598c269 2005 git-flow_1.12.3-3.dsc 200efa7ee2a8e8cc5316d1bde5fb885cc364c017a20a0dbe6d796a42349f48cf 4656 git-flow_1.12.3-3.debian.tar.xz Files: 62fd27fb7087e975553ae77a7624ab38 2005 vcs optional git-flow_1.12.3-3.dsc 8431a021e49bed6426cae24dae9e0c7a 4656 vcs optional git-flow_1.12.3-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmCHJZgACgkQ3OMQ54ZM yL9DAQ//dFwalPPdcyDoRkXCt+Bz7maENga4wK7yN/D6ni8pbNd0gATid2LACMES 8pCtcnywhuwHPZCUSSvEVFIaOuQGUhnQgVpI+EOVMF5Yv/NeFAduCssQnQ7dyBk0 4WMSFOHMbLmjmpDO6Y6dpKCLwluknsut37ZzWbxvFvrgrJjdxBYA/LjzdNQwb7OH 0MHkpAmSO1i2Vc8KmQoOzz2UIC8h9ORIvMVcKr41ugvwpdUvqfNz/ncGXUyJaJ/U cweu5d1G8K9QWy9Xp8QMJXdBGYrjLrfjrmLElO8FTfTKhNuzpm4iTXFlCTox2WdH Dno9hZVeW9b/mHkTe/LqcMz9Yg23tTD96VMb6PvG9n9uhOSi036iryf584jzKys1 HD6rH1oQIQNw1Y4GqSS+dRD9OAn6AZhYLoKlU/Otyq0Nob7eP4tBiH2/HHoWUz/u Jw/wKMKUSKU6NzJg66O+VJwgt3b9EKg/L61eG6w4mz/KL1dubmxMU2cgF1eT6HZB wCTwPbpOMQQCI8F56ll5u8ABt3yAcekRvRIEkozaFtMDup85RyNU08a9PMJy0N7I uzyg9jQB1IlV0lw/gYpewUcWox5W/VJLvGCuz/VIht5RF2mBT7sfFks5ioqwgIkB bmcWQgp7H4MS0EcK958Zt/T6dAPoYpc2cY4w748SGek/3hWq9DM= =u2Pa -END PGP SIGNATURE End Message ---
Bug#987644: nomad will FTBFS after 2021-11-09 due to expired certificate
Source: nomad Version: 0.12.10+dfsg1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/nomad.html ... config_test.go:494: write err: x509: certificate has expired or is not yet valid: current time 2022-05-26T18:21:44Z is after 2021-11-09T19:48:00Z --- FAIL: TestConfig_outgoingWrapper_OK (0.00s) FAIL FAILgithub.com/hashicorp/nomad/helper/tlsutil 0.054s ...
Bug#987646: eclipse-titan: Frequent parallel FTBFS
Source: eclipse-titan Version: 7.2.0-1 Severity: serious Tags: ftbfs eclipse-titan (7.2.0-1) unstable; urgency=medium ... * debian/rules: ... - removed unnecessary --no-parallel option -- Gergely Pilisi Tue, 16 Feb 2021 10:25:17 +0100 Unfortunately --no-parallel is still necessary: https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/eclipse-titan.html ... Notify: Parsing TTCN-3 module `TitanLoggerControl.ttcn'... Notify: Checking modules... Notify: Generating code... Notify: None of the files needed update. Notify: Generating TTCN-3 modules... touch RT1/TitanLoggerControl.cc.compiled Notify: File 'TitanLoggerApi.ttcn' was generated. Notify: File `RT1/PreGenRecordOf.hh' was generated. Notify: Generating TTCN-3 modules... Notify: File 'TitanLoggerApi.ttcn' was generated. Notify: File `RT1/PreGenRecordOf.cc' was generated. Notify: 2 files were updated. sed -e 's/XSD.String/charstring/g;s/XSD.AnySimpleType/charstring/g;s/XSD.Integer/integer/g;s/XSD.Float/float/g;s/XSD.Double/float/g;s/XSD.Boolean/boolean/g;s/import from XSD all;//g' TitanLoggerApi.ttcn >TitanLoggerApi.ttcn_ touch RT1/PreGenRecordOf.cc.compiled sed -e 's/XSD.String/charstring/g;s/XSD.AnySimpleType/charstring/g;s/XSD.Integer/integer/g;s/XSD.Float/float/g;s/XSD.Double/float/g;s/XSD.Boolean/boolean/g;s/import from XSD all;//g' TitanLoggerApi.ttcn >TitanLoggerApi.ttcn_ mv TitanLoggerApi.ttcn_ TitanLoggerApi.ttcn mv TitanLoggerApi.ttcn_ TitanLoggerApi.ttcn mv: cannot stat 'TitanLoggerApi.ttcn_': No such file or directory make[4]: *** [Makefile:280: TitanLoggerApi.ttcn] Error 1 https://buildd.debian.org/status/fetch.php?pkg=eclipse-titan&arch=powerpc&ver=7.2.0-1&stamp=1613472632&raw=0 ... Notify: File `RT1/TitanLoggerControl.hh' was generated. Notify: Parsing TTCN-3 module `TitanLoggerControl.ttcn'... Notify: File `RT1/TitanLoggerControl.cc' was generated. Notify: 2 files were updated. touch RT1/TitanLoggerControl.cc.compiled Notify: Checking modules... Notify: Generating code... Notify: None of the files needed update. touch RT1/TitanLoggerControl.cc.compiled Notify: File `RT1/PreGenRecordOf.hh' was generated. Notify: File `RT1/PreGenRecordOf.cc' was generated. Notify: 2 files were updated. touch RT1/PreGenRecordOf.cc.compiled Notify: Generating TTCN-3 modules... Notify: File 'TitanLoggerApi.ttcn' was generated. Notify: None of the files needed update. sed -e 's/XSD.String/charstring/g;s/XSD.AnySimpleType/charstring/g;s/XSD.Integer/integer/g;s/XSD.Float/float/g;s/XSD.Double/float/g;s/XSD.Boolean/boolean/g;s/import from XSD all;//g' TitanLoggerApi.ttcn >TitanLoggerApi.ttcn_ touch RT1/PreGenRecordOf.cc.compiled Notify: Generating TTCN-3 modules... Notify: File 'TitanLoggerApi.ttcn' was generated. sed -e 's/XSD.String/charstring/g;s/XSD.AnySimpleType/charstring/g;s/XSD.Integer/integer/g;s/XSD.Float/float/g;s/XSD.Double/float/g;s/XSD.Boolean/boolean/g;s/import from XSD all;//g' TitanLoggerApi.ttcn >TitanLoggerApi.ttcn_ mv TitanLoggerApi.ttcn_ TitanLoggerApi.ttcn mkdir -p RT1 mv TitanLoggerApi.ttcn_ TitanLoggerApi.ttcn if ../compiler2/compiler -o RT1 TitanLoggerApi.ttcn - TitanLoggerApi.ttcn; then :; else mv TitanLoggerApi.ttcn TitanLoggerApi.ttcn.$$.bad; exit 1; fi mv: cannot stat 'TitanLoggerApi.ttcn_': No such file or directory make[4]: *** [Makefile:280: TitanLoggerApi.ttcn] Error 1
Processed: tagging 984490
Processing commands for cont...@bugs.debian.org: > tags 984490 + ftbfs Bug #984490 [src:mercurial] test-archive.t fails in the autopkg tests Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 984490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987650: ruby-rugged requires internet access during the build
Source: ruby-rugged Version: 1.1.0+ds-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/ruby-rugged.html ... 1) Error: OnlineLsTest#test_ls_over_https: Rugged::NetworkError: failed to resolve address for github.com: Temporary failure in name resolution /build/ruby-rugged-1.1.0+ds/test/online/ls_test.rb:22:in `ls' /build/ruby-rugged-1.1.0+ds/test/online/ls_test.rb:22:in `each' /build/ruby-rugged-1.1.0+ds/test/online/ls_test.rb:22:in `to_a' /build/ruby-rugged-1.1.0+ds/test/online/ls_test.rb:22:in `test_ls_over_https' /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' 2) Error: OnlineFetchTest#test_fetch_over_https: Rugged::NetworkError: failed to resolve address for github.com: Temporary failure in name resolution /build/ruby-rugged-1.1.0+ds/debian/ruby-rugged/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in `fetch' /build/ruby-rugged-1.1.0+ds/debian/ruby-rugged/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in `fetch' /build/ruby-rugged-1.1.0+ds/test/online/fetch_test.rb:20:in `test_fetch_over_https' /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' 3) Error: OnlineFetchTest#test_fetch_over_https_with_certificate_callback: Rugged::NetworkError: failed to resolve address for github.com: Temporary failure in name resolution /build/ruby-rugged-1.1.0+ds/debian/ruby-rugged/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in `fetch' /build/ruby-rugged-1.1.0+ds/debian/ruby-rugged/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in `fetch' /build/ruby-rugged-1.1.0+ds/test/online/fetch_test.rb:36:in `test_fetch_over_https_with_certificate_callback' /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_in
Bug#987652: surf does not start
Package: surf
Version: 2.0+git20201107-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
surf does not start anymore since version 2.0+git20201107.
Expected behaviour : surf should start.
Steps to reproduce :
$ /usr/bin/surf
output :
(WebKitWebProcess:94294): GLib-CRITICAL **: 02:49:52.728: the GVariant format
string '(ii)' has a type of '(ii)' but the given value has a type of 'i'
(WebKitWebProcess:94294): GLib-CRITICAL **: 02:49:52.728: g_variant_get:
assertion 'valid_format_string (format_string, TRUE, value)' failed
(WebKitWebProcess:94294): GLib-CRITICAL **: 02:49:52.729: the GVariant format
string '(ii)' has a type of '(ii)' but the given value has a type of 'i'
(WebKitWebProcess:94294): GLib-CRITICAL **: 02:49:52.729: g_variant_get:
assertion 'valid_format_string (format_string, TRUE, value)' failed
web process terminated: crashed
And surf crashes.
The problem can be traced back to this specific upstream commit :
e92fd1aa5f38c399f8fc5d263026fbd9d34ddfbb
Which can be found at
https://git.suckless.org/surf/commit/e92fd1aa5f38c399f8fc5d263026fbd9d34ddfbb.html
One possible fix/workaround is the following :
diff --git a/surf.c b/surf.c
index ac832ff..e84a538 100644
--- a/surf.c
+++ b/surf.c
@@ -1269,7 +1269,7 @@ initwebextensions(WebKitWebContext *wc, Client *c)
if (spair[1] < 0)
return;
- gv = g_variant_new("i", spair[1]);
+ gv = g_variant_new("(ii)", spair[1]);
webkit_web_context_set_web_extensions_initialization_user_data(wc, gv);
webkit_web_context_set_web_extensions_directory(wc, WEBEXTDIR);
diff --git a/webext-surf.c b/webext-surf.c
index d087219..da16ddf 100644
--- a/webext-surf.c
+++ b/webext-surf.c
@@ -95,7 +95,7 @@
webkit_web_extension_initialize_with_user_data(WebKitWebExtension *e,
webext = e;
- g_variant_get(gv, "i", &sock);
+ g_variant_get(gv, "(ii)", &sock);
gchansock = g_io_channel_unix_new(sock);
g_io_channel_set_encoding(gchansock, NULL, NULL);
But this workaround seems wrong when we look at the semantic of g_variant_new()
in
gvariant.c :
- sock and spair[1] are ints, and should work with "i".
- Similarly, "(ii)" should mean two extra arguments after the format, but only
&sock works.
And I don't know whether this fix breaks surf in another way.
One other way would be to revert to 2.0+git20181009-4, or some other version
inbetween.
Thank you in advance for your time,
Aymeric Agon-Rambosson
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-6-amd64 (SMP w/16 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages surf depends on:
ii libc62.31-11
ii libgcr-base-3-1 3.38.1-2
ii libgcr-ui-3-13.38.1-2
ii libglib2.0-0 2.66.8-1
ii libgtk-3-0 3.24.24-3
ii libjavascriptcoregtk-4.0-18 2.30.6-1
ii libwebkit2gtk-4.0-37 2.30.6-1
ii libx11-6 2:1.7.0-2
Versions of packages surf recommends:
ii curl 7.74.0-1.2
ii stterm [x-terminal-emulator] 0.8.4-1
ii suckless-tools46-1
ii x11-utils 7.7+5
Versions of packages surf suggests:
ii apparmor 2.13.6-10
-- Configuration Files:
/etc/apparmor.d/usr.bin.surf changed:
/usr/bin/surf flags=(complain) {
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
owner @{HOME}/.surf/ w,
owner @{HOME}/.surf/** rwkl,
owner @{HOME}/.cache/ rw,
@{PROC}/@{pid}/cmdline r,
@{PROC}/@{pid}/fd/ r,
@{PROC}/@{pid}/smaps r,
/dev/ r,
/sys/devices/pci[0-9]*/** r,
/sys/devices/platform/soc/soc:gpu/* r,
/usr/share/glib-2.0/schemas/gschemas.compiled r,
/usr/share/doc/** r,
# WebKit
/usr/lib/@{multiarch}/webkit2gtk-4.0/WebKit*Process ix,
/{dev,run}/shm/WK2SharedMemory.* rw,
/var/tmp/WebKit-Media-* rw,
/usr/share/publicsuffix/public_suffix_list.{dat,dafsa} r,
owner @{HOME}/.local/share/webkitgtk/ w,
owner @{HOME}/.local/share/webkitgtk/** rw,
owner @{HOME}/.cache/webkitgtk/ w,
owner @{HOME}/.cache/webkitgtk/** rwk,
# fontconfig
/usr/share/fontconfig/conf.avail/ r,
# dconf
owner @{HOME}/.cache/dconf/user rw,
owner /run/user/*/dconf/user rw,
/usr/bin/surf ix,
/{usr/,}bin/dash ix,
/{usr/,}bin/sed ix,
/usr/bin/dmenu ix,
/usr/bin/printf ix,
/usr/bin/xargs ix,
/usr/bin/xprop ix,
# for downloading files
/dev/ptmx rw,
/dev/pts/* rw,
/usr/bin/st ix,
# unconfined because it is called in (and downloading to) the cwd
/usr/bin/curl U
Bug#987608: shibboleth-sp: Session recovery feature contains a null pointer deference
Control: retitle -1 shibboleth-sp: CVE-2021-31826: Session recovery feature contains a null pointer deference Hi, On Mon, Apr 26, 2021 at 03:16:14PM +0200, Ferenc W??gner wrote: > Source: shibboleth-sp > Version: 3.0.2+dfsg1-1 > Severity: important > Tags: upstream patch security > Forwarded: https://issues.shibboleth.net/jira/browse/SSPCPP-927 > > Shibboleth Service Provider Security Advisory [26 April 2021] > > An updated version of the Service Provider software is now > available which corrects a denial of service vulnerability. > > Session recovery feature contains a null pointer deference > == > The cookie-based session recovery feature added in V3.0 contains a > flaw that is exploitable on systems *not* using the feature if a > specially crafted cookie is supplied. > > This manifests as a crash in the shibd daemon/service process. > > Because it is very simple to trigger this condition remotely, it > results in a potential denial of service condition exploitable by > a remote, unauthenticated attacker. > > Versions without this feature (prior to V3.0) are not vulnerable > to this particular issue. > > Recommendations > === > Update to V3.2.2 or later of the Service Provider software, which > is now available. > > In cases where this is not immediately possible, configuring a > DataSealer component in shibboleth2.xml (even if used for nothing) > will work around the vulnerability. > > For example: > > > > This workaround is only possible after having updated the > core configuration to the V3 XML namespace. > > Other Notes > === > The cpp-sp git commit containing the fix for this issue is > 5a47c3b9378f4c49392dd4d15189b70956f9f2ec MITRE has assigned CVE-2021-31826 for this issue. Regards, Salvatore
Processed: Re: Bug#987608: shibboleth-sp: Session recovery feature contains a null pointer deference
Processing control commands: > retitle -1 shibboleth-sp: CVE-2021-31826: Session recovery feature contains a > null pointer deference Bug #987608 [src:shibboleth-sp] shibboleth-sp: Session recovery feature contains a null pointer deference Changed Bug title to 'shibboleth-sp: CVE-2021-31826: Session recovery feature contains a null pointer deference' from 'shibboleth-sp: Session recovery feature contains a null pointer deference'. -- 987608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985765: openjdk-17: non-free PKCS#11 headers
Control: severity -1 important setting the priority back, as the bug submitter has chosen. Note this also applies to openjdk-11.
Processed: Re: openjdk-17: non-free PKCS#11 headers
Processing control commands: > severity -1 important Bug #985765 [src:openjdk-17] openjdk-17: non-free PKCS#11 headers Severity set to 'important' from 'serious' -- 985765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987608: shibboleth-sp: Session recovery feature contains a null pointer deference
Salvatore Bonaccorso writes: > MITRE has assigned CVE-2021-31826 for this issue. Thanks. I guess you don't want a new security upload for this, but I'll certainly include it in the changelog of the unstable upload. (And in the changelog of the next security upload, whenever that happens.) -- Feri
Bug#983429: marked as done (mosquitto: /run/mosquitto is on a tmpfs and should be created dynamically)
Your message dated Tue, 27 Apr 2021 06:34:39 + with message-id and subject line Bug#983429: fixed in mosquitto 2.0.10-6 has caused the Debian Bug report #983429, regarding mosquitto: /run/mosquitto is on a tmpfs and should be created dynamically 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.) -- 983429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mosquitto Version: 2.0.7-3 Severity: minor /run/mosquitto shows up in cruft-ng report as existing in dpkg database but missing from the filesystem, if service has been disabled before boot. please create /run/mosquitto dynamically on boot fix_permissions() in postinst seams not enough. Greetings, -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (501, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/2 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mosquitto depends on: ii adduser 3.118 ii libc62.31-9 ii libcjson11.7.14-1 ii libdlt2 2.18.6-1 ii libmosquitto12.0.7-3 ii libssl1.11.1.1j-1 ii libsystemd0 247.3-1 ii libwebsockets16 4.0.20-2 ii libwrap0 7.6.q-31 ii lsb-base 11.1.0 mosquitto recommends no packages. Versions of packages mosquitto suggests: pn apparmor -- no debconf information --- End Message --- --- Begin Message --- Source: mosquitto Source-Version: 2.0.10-6 Done: Roger A. Light We believe that the bug you reported is fixed in the latest version of mosquitto, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger A. Light (supplier of updated mosquitto 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, 26 Apr 2021 22:07:57 +0100 Source: mosquitto Architecture: source Version: 2.0.10-6 Distribution: unstable Urgency: medium Maintainer: Roger A. Light Changed-By: Roger A. Light Closes: 983429 Changes: mosquitto (2.0.10-6) unstable; urgency=medium . * Don't chown /run/mosquitto in mosquitto.postinst, this is done in the systemd unit file at run time. (closes: #983429). * systemd-run.patch: use /run/mosquitto instead of /var/run/mosquitto in systemd unit file. Checksums-Sha1: add3c14519a40cebe819ffa421ec94bcbce77bdf 2433 mosquitto_2.0.10-6.dsc be43205efcb71a6cfb7d1e5117c14333aa70d5b6 24196 mosquitto_2.0.10-6.debian.tar.xz f349793f1600744c92feeb1b75b7f2361e93027b 9402 mosquitto_2.0.10-6_source.buildinfo Checksums-Sha256: 53384e60c691d4c5b1ac97ff7ae732e00873d993e3e22cb19456db5b764cee9f 2433 mosquitto_2.0.10-6.dsc 7aa69806fbfb6c8fe2ef352440c15055499d83f8601d982fadcdafaa57e95423 24196 mosquitto_2.0.10-6.debian.tar.xz 291dc5c7891b302b17433dd504fc3b1bb2476d4aaf0bd2ec3f96c4b9c2bcfa75 9402 mosquitto_2.0.10-6_source.buildinfo Files: 62c084cef64a685f4d0e22efe7978626 2433 net optional mosquitto_2.0.10-6.dsc 0a47f4f55d821a88e5808050692bf751 24196 net optional mosquitto_2.0.10-6.debian.tar.xz fc57441208c32d9c2f7b65663ba3f2bf 9402 net optional mosquitto_2.0.10-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmCHriwACgkQ808JdE6f XdkF5A//SF0GaegDqZWpNcQUFJFaHgwrjNfRuhtTuvNxC8l1zZ/DepYUYGGzwwOh bwcDrYW844j3ERvh574UVKtDr9vFGi8SVx7qsxbE+XPG/6di5gGpWefx2/xg41gg KM2X+oi2b5O9NJ7+OCwnppBeoOEUacmr4zrOKxj+o4LNtK2kArGJecf5JrUota66 XEJimpLb7dPkJoFJFWQ8AE6TaMp5DKXR2RK6ABNoCK4K7Rn3pphqaBQC694WxlNm dmmn1pzUGhr1vUCC/pXmgwUAJaT6ASAAKlCELFq3FmwNBfZOCJ9uDHd6xo9B9K/W m9iNdkUjtGGtt0UL1Fw/TGorb5m+5Ozkhok7YQ4BtXJ+oSPku1NxjsPoZrYnZnFp lae4DCoZYKU9ctP2Ex/VCZyCuz8yp0ogePm6mtEpkYKjmtNzWjS8oOy3Iv+4EY0O KsJbX+e1Y+QBWMnqH/GcPaqV/pkv5jNZfSJCYpg0tFv6yip+3wfs/hIbuL+jjygp s6yy3F41Hq809ZMso4HFs4QA4feVQXgY/eIPPV4q2R9sFRHx3zk4QAXEh9VNdxsT Xriec4LofVbTIuaH/Fqw3Hwk498nzD43o0v7mrOSScCePLCWIT+hFGyXQKil+eD6 qeZaGFyfNijpfPDQ/or5LSd+Dvz+GwBVmgmsK5Z5FGS3Kot0Zqg= =ya
Bug#987608: shibboleth-sp: Session recovery feature contains a null pointer deference
Hi On Tue, Apr 27, 2021 at 08:16:52AM +0200, wf...@debian.org wrote: > Salvatore Bonaccorso writes: > > > MITRE has assigned CVE-2021-31826 for this issue. > > Thanks. I guess you don't want a new security upload for this, but I'll > certainly include it in the changelog of the unstable upload. (And in > the changelog of the next security upload, whenever that happens.) Yes exactly, there is no need to reject the package and reupload with the CVE identifier added, it is all enough how it is so far, we will just add it the the DSA itself. So all fine. Regards, Salvatore
