Processed: saods9 --> tcl-signal
Processing commands for cont...@bugs.debian.org: > reassign 993547 tcl-signal 1.4.4.1-1 Bug #993547 [saods9] saods9: Error in startup script Bug reassigned from package 'saods9' to 'tcl-signal'. No longer marked as found in versions saods9/8.3~b1+repack-1. Ignoring request to alter fixed versions of bug #993547 to the same values previously set Bug #993547 [tcl-signal] saods9: Error in startup script Marked as found in versions tcl-signal/1.4.4.1-1. > affects 993547 saods9 Bug #993547 [tcl-signal] saods9: Error in startup script Added indication that 993547 affects saods9 > severity 993547 serious Bug #993547 [tcl-signal] saods9: Error in startup script Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 993547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993560: FTBFS on arch-any
Package: linux Version: 5.14-1~exp1 Severity: serious Hi, unfortunately the 5.14-1~exp1 upload failed to build on all architectures (except for 'all'). Regards, Daniel ---snip--- make[5]: Leaving directory '/<>/tools/perf' make[4]: Leaving directory '/<>/tools/perf' rm -f /<>/debian/linux-perf-5.14/usr/bin/trace_5.14 mkdir -p /<>/debian/linux-perf-5.14/usr/share/bash-completion/ mv /<>/debian/linux-perf-5.14/etc/bash_completion.d \ /<>/debian/linux-perf-5.14/usr/share/bash-completion/completions rmdir --ignore-fail-on-non-empty /<>/debian/linux-perf-5.14/etc cd /<>/debian/linux-perf-5.14 && ! find \! -type d \! -path '*[_-]5.14*' | grep . ./usr/include/perf/perf_dlfilter.h make[3]: *** [/<>/debian/rules.d/tools/perf/Makefile:57: install] Error 1 make[3]: Leaving directory '/<>/debian/build/build-tools/tools/perf' make[2]: *** [debian/rules.real:730: install-perf] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules.gen:34: binary-arch_amd64_real] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:43: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 ---snap---
Bug#980692: closing 980692
close 980692 2021.01.0+dfsg-1 thanks I forgot to close this bug. the doc package does build now.
Processed: closing 980692
Processing commands for cont...@bugs.debian.org: > close 980692 2021.01.0+dfsg-1 Bug #980692 [src:dask] dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/html5shiv.min.js is missing Ignoring request to alter fixed versions of bug #980692 to the same values previously set Bug #980692 [src:dask] dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/html5shiv.min.js is missing Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 980692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991323: marked as done (dovecot: CVE-2020-28200)
Your message dated Thu, 02 Sep 2021 22:33:30 + with message-id and subject line Bug#991323: fixed in dovecot 1:2.3.16+dfsg1-1 has caused the Debian Bug report #991323, regarding dovecot: CVE-2020-28200 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.) -- 991323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dovecot X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for dovecot. CVE-2021-33515[0]: | The submission service in Dovecot before 2.3.15 allows STARTTLS | command injection in lib-smtp. Sensitive information can be redirected | to an attacker-controlled address. https://dovecot.org/pipermail/dovecot-news/2021-June/000462.html https://www.openwall.com/lists/oss-security/2021/06/28/2 CVE-2021-29157[1]: | Dovecot before 2.3.15 allows ../ Path Traversal. An attacker with | access to the local filesystem can trick OAuth2 authentication into | using an HS256 validation key from an attacker-controlled location. | This occurs during use of local JWT validation with the posix fs | driver. https://dovecot.org/pipermail/dovecot-news/2021-June/000461.html https://www.openwall.com/lists/oss-security/2021/06/28/1 CVE-2020-28200[2]: | The Sieve engine in Dovecot before 2.3.15 allows Uncontrolled Resource | Consumption, as demonstrated by a situation with a complex regular | expression for the regex extension. https://dovecot.org/pipermail/dovecot-news/2021-June/000460.html https://www.openwall.com/lists/oss-security/2021/06/28/3 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-33515 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33515 [1] https://security-tracker.debian.org/tracker/CVE-2021-29157 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29157 [2] https://security-tracker.debian.org/tracker/CVE-2020-28200 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28200 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: dovecot Source-Version: 1:2.3.16+dfsg1-1 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of dovecot, 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 991...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated dovecot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Sep 2021 13:22:16 -0700 Source: dovecot Architecture: source Version: 1:2.3.16+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Dovecot Maintainers Changed-By: Noah Meyerhans Closes: 983510 991323 Changes: dovecot (1:2.3.16+dfsg1-1) unstable; urgency=medium . [ Christian Göttsche ] * [ff4a227] New upstream version 2.3.14+dfsg1 * [963fa3b] New upstream version 2.3.15+dfsg1 (Closes: #991323, #983510) * [5e0c898] d/watch: adjust dversionmangle for dfsg suffix * [9ffb0f5] d/patches: update * [850e1d6] New upstream version 2.3.16+dfsg1 * [7140b87] d/patches: rebase patches * [fb1b77e] d/rules: enable LTO * [ce7055d] d/control: add libsystemd-dev dependency * [db93263] d/copyright: drop unused section * [aeec1e8] d/rules: update how to set systemdsystemunitdir * [ebe9709] d/patches: resolve compiler warnings * [19b2bb0] d/changelog: bump to 1:2.3.16+dfsg1-1 * [58a4078] d/patches: update 32bit warnings patch . [ Noah Meyerhans ] * [f217c2e] Fix indexer crash * [b075317] Import upstream patch for indexer crash on client disconnect * [36e8740] drop debian/dovecot-core.maintscript Checksums-Sha1: 0d06f55332ac921c0d33e3fbc48eccbb59f394cf 4019 dovecot_2.3.16+dfsg1-1.dsc 00a378d9a12a0bbeafec9915f75344d8c26e9c9d 1626913 dovecot_2.3.16+dfsg1.orig-pigeonhole.tar.gz b5c598ae8b9901bfabdf2c93271f57cde0bde73e 7650008 dovecot_2.3.16+dfsg1.orig.tar.gz
Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs
* Paul Gevers: > On Thu, 2 Sep 2021 10:17:22 +0200 Sascha Steinbiss wrote: >> I think this is done now. With YARA 4.1.2 and >> golang-github-hillu-go-yara 4.1.0 now in unstable, the build works again >> as the build-time tests complete fine. >> >> @Hilko any other comments? > > If there are incompatible API changes, the soname needs to be bumped. The soname was bumped, from 4 to 8. Cheers, -Hilko
Processed: tagging 991323
Processing commands for cont...@bugs.debian.org: > tags 991323 + pending Bug #991323 [src:dovecot] dovecot: CVE-2020-28200 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 991323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992971: marked as done (grilo: CVE-2021-39365)
Your message dated Thu, 02 Sep 2021 21:47:21 + with message-id and subject line Bug#992971: fixed in grilo 0.3.7-1+deb10u1 has caused the Debian Bug report #992971, regarding grilo: CVE-2021-39365 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.) -- 992971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grilo Version: 0.3.13-1 Severity: important Tags: security upstream Forwarded: https://gitlab.gnome.org/GNOME/grilo/-/issues/146 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.3.7-1 Hi, The following vulnerability was published for grilo. CVE-2021-39365[0]: | In GNOME grilo though 0.3.13, grl-net-wc.c does not enable TLS | certificate verification on the SoupSessionAsync objects it creates, | leaving users vulnerable to network MITM attacks. NOTE: this is | similar to CVE-2016-20011. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-39365 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39365 [1] https://gitlab.gnome.org/GNOME/grilo/-/issues/146 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: grilo Source-Version: 0.3.7-1+deb10u1 Done: Alberto Garcia We believe that the bug you reported is fixed in the latest version of grilo, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Garcia (supplier of updated grilo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 26 Aug 2021 22:49:03 +0200 Source: grilo Architecture: source Version: 0.3.7-1+deb10u1 Distribution: buster-security Urgency: high Maintainer: Alberto Garcia Changed-By: Alberto Garcia Closes: 992971 Changes: grilo (0.3.7-1+deb10u1) buster-security; urgency=high . * fix-tls-cert-validation.patch: - Fix TLS cert validation not being done for any network call (Closes: #992971, CVE-2021-39365). Checksums-Sha1: 5f3c0e4f4664526774e1ffd71e4b7d217b936c5d 2307 grilo_0.3.7-1+deb10u1.dsc 86ca172869e03c21d665f89e3e8b959f599b16cd 232636 grilo_0.3.7.orig.tar.xz ac7133cbbfb0bb4f395f2aa2143f88ef9e56936b 8836 grilo_0.3.7-1+deb10u1.debian.tar.xz a14129befef79857b4580a9ac10965e618f1c2e9 15556 grilo_0.3.7-1+deb10u1_source.buildinfo Checksums-Sha256: 259914b8b523a2ae6fb71dc68502f5acafd722c154f34e37de091a3a9f411042 2307 grilo_0.3.7-1+deb10u1.dsc c55e14f41623db8ab5299db31aba237706b64cb2a8e04624c2b9378d0219ab18 232636 grilo_0.3.7.orig.tar.xz 21242d290de261ea973fcd976f97721b92ac2e6ee84313cbdac6db5008a56520 8836 grilo_0.3.7-1+deb10u1.debian.tar.xz b1de4b9a6c26fe8c66f3cde70edd2119d84f096f0ddfc52deee084491ed1b305 15556 grilo_0.3.7-1+deb10u1_source.buildinfo Files: 71293c96a09c3662a40635b307825934 2307 libs optional grilo_0.3.7-1+deb10u1.dsc 8c2da79735a5dc7040e5b84d06af2eb4 232636 libs optional grilo_0.3.7.orig.tar.xz efa50968990b95c58f7f5f5b48ca4d39 8836 libs optional grilo_0.3.7-1+deb10u1.debian.tar.xz de39fc78c326dd50d62a838848abfabc 15556 libs optional grilo_0.3.7-1+deb10u1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYrwugQBKzlHMYFizAAyEYu0C2AIFAmEoDmoACgkQAAyEYu0C 2AJr9A//ZlvnS7mRppUCibanO6xDB/nxZvI3ybv4sKoGRqSlD+CIUNlTALC78/9m Fknqx0CfA6CghoTmUXs+FLMG4zYZtomybCEbraGeLBo2NRaG/98cBnx8nRd93xuK vUkGavsINE95gGxN+aBkjcdNeN10FKvetU1N2gEHe1j85+K5Xrcpu7Gps1ovxQlt I1iz/OIZ2/N/002ENXOQv2OgE9f5h1Y4++BkSifRdDvIpSk/TpIYxCpLlKcdJHmm VPPY3p2ShdQbSwWDXLzCnqE3lM7aXgPZERrfIMnMEvEuLHLNtvcjjzKaGN9+ySEW qtfpHmSIpVTugk4J+HdQ5kt2ZBhxjL5LNi/8u1hFnvMhCw/ZwWX2lyur/4k/Eu7Y qFWJokGnm8GEpzHvrX7uzf2NRHEWWOIOmcKF8kXbUNlWdQfpdOwk7iQKhOQFMBO2 DNQEk6ygsdwr0sDB6zzg2bb9CGFgsBDvWpvF1pmFgKMFQkNveHfciWjx7fyo531b 2AMyxWGhsxSySjaGWQjQyGPia6gT0jIPeTa1sNe+Vu61LxG9mwSnWJ87jeyahoVk NPC2TBfC5b7tV7nptAjPKNAGUjkG14ALcgijKajMsfFK95EkfISlsdKSyGYCBDwk yDiZBFB0FyVPzvT06JmHtKz8zk+KhcILIqI+F8ZPGDwidMHP02w= =VZAy -END PGP
Bug#993547: saods9: Error in startup script
Package: saods9
Version: 8.3~b1+repack-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Launching ds9 from the command line, result in an output error :
Error in startup script: cannot find symbol "Signal_Init":
/usr/lib/tcltk/x86_64-linux-gnu/Signal1.4.4.1/libSignal1.4.4.1.so:
undefined symbol: _Signal_Init
while executing
"load /usr/lib/tcltk/x86_64-linux-gnu/Signal1.4.4.1/libSignal1.4.4.1.so
Signal"
("package ifneeded Signal 1.4.4.1" script)
invoked from within
"package require Signal"
(file "/usr/share/saods9/library/ds9.tcl" line 229)
instead of launching the program
a.
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 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 saods9 depends on:
ii libtk-img 1:1.4.13+dfsg-1
ii tcl-awthemes 10.4.0-1
ii tcl-signal 1.4.4.1-1
ii tcl-tls1.7.22-2
ii tcl-ttkthemes 3.2.2-1
ii tcl-xpa2.1.20-1
ii tclfitsy 8.2+repack-2
ii tcliis 8.2+repack-2
ii tcllib 1.20+dfsg-1
ii tclxml 1:3.2.7-5
ii tk 8.6.11+1
ii tk-html1 1.04-2
ii tk-mpeg1.0.9-1
ii tk-table 2.10.7-1
ii tkblt 3.2.23-1
ii tkcon 2:2.7.10-2
ii tksao 8.2+repack-2
Versions of packages saods9 recommends:
ii saods9-doc 8.2+repack-2
Versions of packages saods9 suggests:
pn python3-pyds9
pn xpa-tools
-- no debconf information
Processed: grilo: diff for NMU version 0.3.13-1.1
Processing control commands:
> tags 992971 + patch
Bug #992971 {Done: Alberto Garcia } [src:grilo] grilo:
CVE-2021-39365
Added tag(s) patch.
> tags 992971 + pending
Bug #992971 {Done: Alberto Garcia } [src:grilo] grilo:
CVE-2021-39365
Added tag(s) pending.
--
992971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#992971: grilo: diff for NMU version 0.3.13-1.1
Control: tags 992971 + patch Control: tags 992971 + pending Hi Alberto, I've prepared an NMU for grilo (versioned as 0.3.13-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. It is basically just a rebuild of your upload for bullseye-security to have the fix as well in unstable/testing. Regards, Salvatore diff -Nru grilo-0.3.13/debian/changelog grilo-0.3.13/debian/changelog --- grilo-0.3.13/debian/changelog 2020-09-06 12:51:05.0 +0200 +++ grilo-0.3.13/debian/changelog 2021-09-02 23:05:13.0 +0200 @@ -1,3 +1,14 @@ +grilo (0.3.13-1.1) unstable; urgency=medium + + * Non-maintainer upload. + + [ Alberto Garcia ] + * fix-tls-cert-validation.patch: +- Fix TLS cert validation not being done for any network call + (Closes: #992971, CVE-2021-39365). + + -- Salvatore Bonaccorso Thu, 02 Sep 2021 23:05:13 +0200 + grilo (0.3.13-1) unstable; urgency=medium [ Alberto Garcia ] diff -Nru grilo-0.3.13/debian/patches/fix-tls-cert-validation.patch grilo-0.3.13/debian/patches/fix-tls-cert-validation.patch --- grilo-0.3.13/debian/patches/fix-tls-cert-validation.patch 1970-01-01 01:00:00.0 +0100 +++ grilo-0.3.13/debian/patches/fix-tls-cert-validation.patch 2021-08-26 23:10:58.0 +0200 @@ -0,0 +1,17 @@ +From: Bastien Nocera +Subject: Fix TLS cert validation not being done for any network call (CVE-2021-39365) +Bug: https://gitlab.gnome.org/GNOME/grilo/-/issues/146 +Bug-Debian: https://bugs.debian.org/992971 +Origin: https://gitlab.gnome.org/GNOME/grilo/-/commit/cd2472e506dafb1bb8ae510e34ad4797f63e263e +Index: grilo/libs/net/grl-net-wc.c +=== +--- grilo.orig/libs/net/grl-net-wc.c grilo/libs/net/grl-net-wc.c +@@ -314,6 +314,7 @@ grl_net_wc_init (GrlNetWc *wc) + wc->priv = grl_net_wc_get_instance_private (wc); + + wc->priv->session = soup_session_async_new (); ++ g_object_set (G_OBJECT (wc->priv->session), "ssl-use-system-ca-file", TRUE, NULL); + wc->priv->pending = g_queue_new (); + + set_thread_context (wc); diff -Nru grilo-0.3.13/debian/patches/series grilo-0.3.13/debian/patches/series --- grilo-0.3.13/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ grilo-0.3.13/debian/patches/series 2021-08-26 23:10:58.0 +0200 @@ -0,0 +1 @@ +fix-tls-cert-validation.patch
Processed: retitle 988386 to ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-392
Processing commands for cont...@bugs.debian.org: > retitle 988386 ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 > CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 > CVE-2021-39251 CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 > CVE-2021-39256 CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 > CVE-2021-39261 CVE-2021-39262 CVE-2021-39263 Bug #988386 [ntfs-3g] Reporting CVE's from upstream Changed Bug title to 'ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 CVE-2021-39256 CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 CVE-2021-39261 CVE-2021-39262 CVE-2021-39263' from 'Reporting CVE's from upstream'. > severity 988386 grave Bug #988386 [ntfs-3g] ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 CVE-2021-39256 CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 CVE-2021-39261 CVE-2021-39262 CVE-2021-39263 Severity set to 'grave' from 'normal' > found 988386 1:2017.3.23AR.3-4 Bug #988386 [ntfs-3g] ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 CVE-2021-39256 CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 CVE-2021-39261 CVE-2021-39262 CVE-2021-39263 Marked as found in versions ntfs-3g/1:2017.3.23AR.3-4. > tags 988386 + upstream fixed-upstream Bug #988386 [ntfs-3g] ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 CVE-2021-39256 CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 CVE-2021-39261 CVE-2021-39262 CVE-2021-39263 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 988386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993541: libbpp-core FTBFS: symbol differences
Source: libbpp-core Version: 2.4.1-5 Severity: serious Tags: ftbfs libbpp-core fails to build from source on amd64 in unstable due to symbol differences: |dh_makeshlibs -a | dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below | dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below | dpkg-gensymbols: warning: debian/libbpp-core4/DEBIAN/symbols doesn't match completely debian/libbpp-core4.symbols.amd64 | --- debian/libbpp-core4.symbols.amd64 (libbpp-core4_2.4.1-5_amd64) | +++ dpkg-gensymbolsrnSTfQ 2021-09-02 11:05:37.839656815 + | @@ -2086,66 +2086,79 @@ | _ZNSt15_Sp_counted_ptrIPN3bpp12MathOperatorELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp12MathOperatorELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp12MathOperatorELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 2.4.1 | + _ZNSt15_Sp_counted_ptrIPN3bpp12MathOperatorELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 2.4.1-5 | _ZNSt15_Sp_counted_ptrIPN3bpp13TreeGraphImplINS0_11GlobalGraphEEELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp13TreeGraphImplINS0_11GlobalGraphEEELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp13TreeGraphImplINS0_11GlobalGraphEEELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp13TreeGraphImplINS0_11GlobalGraphEEELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp13TreeGraphImplINS0_11GlobalGraphEEELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 2.4.1 | + _ZNSt15_Sp_counted_ptrIPN3bpp13TreeGraphImplINS0_11GlobalGraphEEELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 2.4.1-5 | _ZNSt15_Sp_counted_ptrIPN3bpp14BinaryOperatorELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp14BinaryOperatorELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp14BinaryOperatorELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp14BinaryOperatorELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp14BinaryOperatorELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 2.4.1 | + _ZNSt15_Sp_counted_ptrIPN3bpp14BinaryOperatorELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 2.4.1-5 | _ZNSt15_Sp_counted_ptrIPN3bpp16ConstantOperatorELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16ConstantOperatorELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16ConstantOperatorELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16ConstantOperatorELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16ConstantOperatorELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 2.4.1 | + _ZNSt15_Sp_counted_ptrIPN3bpp16ConstantOperatorELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 2.4.1-5 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_19DerivableFirstOrderEEELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_19DerivableFirstOrderEEELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_19DerivableFirstOrderEEELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_19DerivableFirstOrderEEELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_19DerivableFirstOrderEEELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 2.4.1 | + _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_19DerivableFirstOrderEEELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 2.4.1-5 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_20DerivableSecondOrderEEELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_20DerivableSecondOrderEEELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_20DerivableSecondOrderEEELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_20DerivableSecondOrderEEELN9__gnu_cxx12_Lock_policyE2EED0Ev@Base 2.4.1 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_20DerivableSecondOrderEEELN9__gnu_cxx12_Lock_policyE2EED1Ev@Base 2.4.1 | + _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_20DerivableSecondOrderEEELN9__gnu_cxx12_Lock_policyE2EED2Ev@Base 2.4.1-5 | _ZNSt15_Sp_counted_ptrIPN3bpp16FunctionOperatorINS0_8FunctionEEELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base 2.4.1 |
Bug#992971: marked as done (grilo: CVE-2021-39365)
Your message dated Thu, 02 Sep 2021 19:47:13 + with message-id and subject line Bug#992971: fixed in grilo 0.3.13-1+deb11u1 has caused the Debian Bug report #992971, regarding grilo: CVE-2021-39365 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.) -- 992971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grilo Version: 0.3.13-1 Severity: important Tags: security upstream Forwarded: https://gitlab.gnome.org/GNOME/grilo/-/issues/146 X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.3.7-1 Hi, The following vulnerability was published for grilo. CVE-2021-39365[0]: | In GNOME grilo though 0.3.13, grl-net-wc.c does not enable TLS | certificate verification on the SoupSessionAsync objects it creates, | leaving users vulnerable to network MITM attacks. NOTE: this is | similar to CVE-2016-20011. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-39365 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39365 [1] https://gitlab.gnome.org/GNOME/grilo/-/issues/146 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: grilo Source-Version: 0.3.13-1+deb11u1 Done: Alberto Garcia We believe that the bug you reported is fixed in the latest version of grilo, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Garcia (supplier of updated grilo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 26 Aug 2021 23:10:58 +0200 Source: grilo Architecture: source Version: 0.3.13-1+deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Alberto Garcia Changed-By: Alberto Garcia Closes: 992971 Changes: grilo (0.3.13-1+deb11u1) bullseye-security; urgency=high . * fix-tls-cert-validation.patch: - Fix TLS cert validation not being done for any network call (Closes: #992971, CVE-2021-39365). Checksums-Sha1: 754753bdf24c79917eb0ae70bae86dd98d4f5bfc 2335 grilo_0.3.13-1+deb11u1.dsc aa5f1fd521727c4aeb02b7c6af46930b12183083 236420 grilo_0.3.13.orig.tar.xz 9f9377a46611144938b3d1b756ec2a8b0673231b 9356 grilo_0.3.13-1+deb11u1.debian.tar.xz 6d896e5c78718954b0d79936bf553084f39fd171 15560 grilo_0.3.13-1+deb11u1_source.buildinfo Checksums-Sha256: 95e51c234a1627cc8346caec98e3c7a100f4179a3914391bdfe6baad1735b79d 2335 grilo_0.3.13-1+deb11u1.dsc d14837f22341943ed8a189d9f0827a17016b802d18d0ed080e1413de0fdc927b 236420 grilo_0.3.13.orig.tar.xz ed49e0a9989983f89a3bd9ff4ad05c6a86693a80942200378c87639f79f34cbe 9356 grilo_0.3.13-1+deb11u1.debian.tar.xz d69259858dfc1f9d2c3fcb5d67020cf222c329ca0d428a56db221f25e561df86 15560 grilo_0.3.13-1+deb11u1_source.buildinfo Files: 3bd6646fcaa839c2b5452b5670704e6c 2335 libs optional grilo_0.3.13-1+deb11u1.dsc 737b76fc194878eac2ca45a78175aa9f 236420 libs optional grilo_0.3.13.orig.tar.xz 88014c4aee1aea6b5085f5e4cb3ebd88 9356 libs optional grilo_0.3.13-1+deb11u1.debian.tar.xz 9b42e4e84d74f27cd314568844584319 15560 libs optional grilo_0.3.13-1+deb11u1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYrwugQBKzlHMYFizAAyEYu0C2AIFAmEoBMoACgkQAAyEYu0C 2AIYCxAAifgZ8Et4kolufWQm+40xHmXYdUOBPlxlhqn7Vcm11ZIoDIpWSfdHkmzK iQSkyPX9F6er6OaMguUrbeNgQ9wmuALhSq8+dD1qC9rMenHpL85P87GQbG1JslX7 FWUOZg47hhefs6gh6qfp2AqwyIrkCx6cJ+rzPGeg4OY7NhrvL19ItjVQzTwdFm6O gqL+gCr8kguqQ+sufxwuD/F/ffIpDLJ0u8/MHOWYI4+66KlnXwK3Wk71kWQheRuq el/Yo9f8htg1tv2s26CgFqq9WMgLstnj37h3064h+viOKJYGyGd1fuGEb3WmcJck rQ/w29jJctusLa3cXBNx0txvhPPUYwcP1T96r7jhyVyneekbtSYYDYNMo9yalgEI l6KlqTPpUZ1S6Jx47JADBvEz5JTUY6s+2GHFygSa4AgB8Po2GydewNyZQCTwFpdp 3A3vOW4RTl9inzJRt6mdzlLEeOJ/XbTDV9orr4dZdfd2gveAOz8Vvf+HAMithUCX P5erabfMQV3PifREWbHpTEwjepIDRymMLi3FqLoHF17eqOvteJrvpB1jQqbG9yCP xfI8pi9Al0i3VwDXgNOllBSx3ZNcWIybH6hhY0Xj9K0euLPPW2SY1qJgGXwfuzQL tYRazJpCDFC/2+ar9RREmLHJXKcTL0YeZrC+iuruysEunDCfUKQ= =dWHO
Bug#993534: 389-ds-base breaks dogtag-pki autopkgtest: CA spawn failed
Source: 389-ds-base, dogtag-pki
Control: found -1 389-ds-base/1.4.4.16-1
Control: found -1 dogtag-pki/10.10.2-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of 389-ds-base the autopkgtest of dogtag-pki fails
in testing when that autopkgtest is run with the binary packages of
389-ds-base from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
389-ds-basefrom testing1.4.4.16-1
dogtag-pki from testing10.10.2-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of 389-ds-base to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
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=389-ds-base
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dogtag-pki/14986372/log.gz
autopkgtest [09:10:45]: test pkispawn: [---
IP address is 192.168.122.100
Hostname was:
/etc/hosts now has:
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
192.168.122.100 autopkgtest.debci autopkgtest
Starting installation...
Completed installation for pki-tomcat
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for autopkgtest.debci has no
`subjectAltName`, falling back to check for a `commonName` for now. This
feature is being removed by major browsers and deprecated by RFC 2818.
(See https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
Loading deployment configuration from debian/tests/deploy.cfg.
Installation log: /var/log/pki/pki-ca-spawn.20210902091106.log
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed:
HTTP Status 404 – Not
Foundbody
{font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b
{color:white;background-color:#525D76;} h1 {font-size:22px;} h2
{font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a
{color:black;} .line
{height:1px;background-color:#525D76;border:none;}HTTP
Status 404 – Not FoundType Status
ReportMessage The requested resource
[caadmincagetStatus] is not
availableDescription The origin server did not find a
current representation for the target resource or is not willing to
disclose that one exists.Apache Tomcat/9.0.43
(Debian)
Please check the CA logs in /var/log/pki/pki-tomcat/ca.
CA spawn failed:
autopkgtest [09:12:24]: test pkispawn: ---]
OpenPGP_signature
Description: OpenPGP digital signature
Processed: 389-ds-base breaks dogtag-pki autopkgtest: CA spawn failed
Processing control commands: > found -1 389-ds-base/1.4.4.16-1 Bug #993534 [src:389-ds-base, src:dogtag-pki] 389-ds-base breaks dogtag-pki autopkgtest: CA spawn failed Marked as found in versions 389-ds-base/1.4.4.16-1. > found -1 dogtag-pki/10.10.2-3 Bug #993534 [src:389-ds-base, src:dogtag-pki] 389-ds-base breaks dogtag-pki autopkgtest: CA spawn failed Marked as found in versions dogtag-pki/10.10.2-3. -- 993534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993169: fixed in eckit 1.17.1-2
Dear Alastair, On Sun, 29 Aug 2021 12:03:45 + Debian FTP Masters wrote: >* Drop support for 32-bit archs. Closes: #993169 Don't forget to ask ftp-master to remove the existing binaries on those architectures where it built in the past. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#993532: libpod: autopkgtest regression between 29 Aug 2021 and 2 Sep 2021
Source: libpod Version: 3.0.1+dfsg1-3 Severity: serious User: debian...@lists.debian.org Usertags: regression X-Debbugs-CC: debian...@lists.debian.org Dear maintainer(s), Your package has an autopkgtest, great! However, somewhere between four days ago and today it started to fail [1]. Unfortunately our migration setup didn't catch this because it's either caused by something external to the archive, or the package that caused it is in not a direct (build) dependency of your packages. Looking at the error, I have no clue why. Can you fix the situation? Paul [1] https://ci.debian.net/packages/libp/libpod/ https://ci.debian.net/data/autopkgtest/testing/amd64/libp/libpod/14990105/log.gz dh_auto_build: error: cd _output && go install -trimpath -v -p 2 -tags apparmor,ostree,seccomp,selinux,systemd -ldflags "-X main.buildInfo=3.0.1+dfsg1-3" github.com/containers/podman/cmd/podman github.com/containers/podman/cmd/podman/common github.com/containers/podman/cmd/podman/completion github.com/containers/podman/cmd/podman/containers github.com/containers/podman/cmd/podman/generate github.com/containers/podman/cmd/podman/healthcheck github.com/containers/podman/cmd/podman/images github.com/containers/podman/cmd/podman/inspect github.com/containers/podman/cmd/podman/manifest github.com/containers/podman/cmd/podman/networks github.com/containers/podman/cmd/podman/parse github.com/containers/podman/cmd/podman/play github.com/containers/podman/cmd/podman/pods github.com/containers/podman/cmd/podman/registry github.com/containers/podman/cmd/podman/system github.com/containers/podman/cmd/podman/system/connection github.com/containers/podman/cmd/podman/utils github.com/containers/podman/cmd/podman/validate github.com/containers/podman/cmd/podman/volumes github.com/containers/podman/libpod github.com/containers/podman/libpod/common github.com/containers/podman/libpod/define github.com/containers/podman/libpod/driver github.com/containers/podman/libpod/events github.com/containers/podman/libpod/image github.com/containers/podman/libpod/layers github.com/containers/podman/libpod/linkmode github.com/containers/podman/libpod/lock github.com/containers/podman/libpod/lock/file github.com/containers/podman/libpod/lock/shm github.com/containers/podman/libpod/logs github.com/containers/podman/libpod/logs/reversereader github.com/containers/podman/libpod/network github.com/containers/podman/libpod/plugin github.com/containers/podman/libpod/shutdown github.com/containers/podman/pkg/annotations github.com/containers/podman/pkg/api/handlers github.com/containers/podman/pkg/api/handlers/compat github.com/containers/podman/pkg/api/handlers/libpod github.com/containers/podman/pkg/api/handlers/swagger github.com/containers/podman/pkg/api/handlers/utils github.com/containers/podman/pkg/api/server github.com/containers/podman/pkg/api/server/idle github.com/containers/podman/pkg/api/types github.com/containers/podman/pkg/auth github.com/containers/podman/pkg/autoupdate github.com/containers/podman/pkg/bindings github.com/containers/podman/pkg/bindings/containers github.com/containers/podman/pkg/bindings/generate github.com/containers/podman/pkg/bindings/generator github.com/containers/podman/pkg/bindings/images github.com/containers/podman/pkg/bindings/manifests github.com/containers/podman/pkg/bindings/network github.com/containers/podman/pkg/bindings/play github.com/containers/podman/pkg/bindings/pods github.com/containers/podman/pkg/bindings/system github.com/containers/podman/pkg/bindings/util github.com/containers/podman/pkg/bindings/volumes github.com/containers/podman/pkg/cgroups github.com/containers/podman/pkg/channel github.com/containers/podman/pkg/checkpoint github.com/containers/podman/pkg/copy github.com/containers/podman/pkg/criu github.com/containers/podman/pkg/ctime github.com/containers/podman/pkg/domain/entities github.com/containers/podman/pkg/domain/entities/reports github.com/containers/podman/pkg/domain/filters github.com/containers/podman/pkg/domain/infra github.com/containers/podman/pkg/domain/infra/abi github.com/containers/podman/pkg/domain/infra/abi/parse github.com/containers/podman/pkg/domain/infra/abi/terminal github.com/containers/podman/pkg/domain/infra/tunnel github.com/containers/podman/pkg/domain/utils github.com/containers/podman/pkg/env github.com/containers/podman/pkg/errorhandling github.com/containers/podman/pkg/hooks github.com/containers/podman/pkg/hooks/0.1.0 github.com/containers/podman/pkg/hooks/1.0.0 github.com/containers/podman/pkg/hooks/exec github.com/containers/podman/pkg/inspect github.com/containers/podman/pkg/kubeutils github.com/containers/podman/pkg/lookup github.com/containers/podman/pkg/namespaces github.com/containers/podman/pkg/netns github.com/containers/podman/pkg/parallel github.com/containers/podman/pkg/parallel/ctr github.com/containers/podman/pkg/ps github.com/containers/podman/pkg/ps/define github.com/containers/podman/pkg/registrar github.com/containers/podman/pkg/registries
Processed: [bts-link] source package src:pan
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pan > # 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 #992329 (http://bugs.debian.org/992329) > # Bug title: pan: FTBFS with GLib 2.68: error: template with C linkage > # * https://gitlab.gnome.org/GNOME/pan/-/issues/128 > # * remote status changed: opened -> closed > # * closed upstream > tags 992329 + fixed-upstream Bug #992329 [src:pan] pan: FTBFS with GLib 2.68: error: template with C linkage Added tag(s) fixed-upstream. > usertags 992329 - status-opened Usertags were: status-opened. There are now no usertags set. > usertags 992329 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 992329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992439: libconfig-model-dpkg-perl: blocks fails autopkgtest with recent licensecheck
On Thu, 02 Sep 2021 12:41:03 +0200, Dominique Dumont wrote: > Actually, this is related to: > > https://salsa.debian.org/perl-team/modules/packages/libconfig-model-dpkg-perl/-/commit/fb4dbe585de59a8aeb5d01904869a7f3415e35a5 > > (Note: I found this commit while checking the history of t/scanner/examples/ > scikit-learn.out) Merci bien ! I looked again into this issue yesterday and didn't find anything … (I also didn't go back far enough in history.) > > And I still can't reproduce the failure locally. > > *sigh* > I can reproduce this bug locally with libregexp-pattern-license-perl_3.4.0-1 > which is the version used in the FTBS build. Oh; that explains why I didn't see it in pure unstable chroots. Cheers, gregor (PS: Sorry about the mess I created in git and the archive with the upload of the same version number when I missed the interim releases into experimental.) -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Ludwig Hirsch: Der Dorftrottel signature.asc Description: Digital Signature
Bug#993172: marked as done (gcc-11-base: i386 (Geode LX): latest testing migration produces sig ILL (due to #993162 ?))
Your message dated Thu, 02 Sep 2021 14:34:23 + with message-id and subject line Bug#993172: fixed in gcc-11 11.2.0-4 has caused the Debian Bug report #993172, regarding gcc-11-base: i386 (Geode LX): latest testing migration produces sig ILL (due to #993162 ?) 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.) -- 993172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-11-base Version: 11.2.0-3 Severity: grave Justification: renders package unusable Hello! During today's upgrade, apt-listbugs[^NOTE] warned me that upgrading libc6 (2.31-13 -> 2.31-17) would produce sig ILL on Geode LX i386 CPUs. See bug [#993162]. Since I have a Geode LX based box (a Soekris net5501), I decided to pin libc6 to version 2.31-13, in order to avoid issues, while waiting for a fixed version of libc6 to migrate to Debian testing (bookworm). Despite this, I began to see sig ILL (for instance, the smartd daemon could not be restarted), after the upgrade. Some tests revealed that these issues were caused by the upgrades of libstdc++6, libgcc-s1, and libgomp1 (10.2.1-6->11.2.0-3), allowed by the new installation of gcc-11-base. Downgrading those three packages and removing gcc-11-base seems to avoid the sig ILL issues. I am therefore filing this bug report against gcc-11-base, as a courtesy to other apt-listbugs users (who will thus be warned about the need to avoid installing gcc-11-base on Geode LX systems). Please do not close, reassign, or downgrade the severity of this bug report, until a proper fix is in place in libc6 and its effects have propagated to binary packages generated from gcc-11. Feel free to block this bug report by 993162, if appropriate. Thanks for your understanding and patience! [^NOTE]: for the record, I am the current maintainer of apt-listbugs and, yes, that package is useful to me as well (of course!) [#993162]: <https://bugs.debian.org/993162> -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 5.10.0-8-686 (SMP w/1 CPU thread) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11.2.0-4 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Sep 2021 12:23:43 +0200 Source: gcc-11 Architecture: source Version: 11.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 993162 993172 Changes: gcc-11 (11.2.0-4) unstable; urgency=medium . * Update to git 20210902 from the gcc-11 branch. - Fix PR target/101472 (x86), PR target/99744 (x86), PR target/101492 (x86), PR target/101549 (x86), PR target/101471 (x86), PR target/102035 (ARM), PR target/102035 (ARM), PR middle-end/101949, PR ipa/97565, PR debug/101905, PR gcov-profile/89961, PR fortran/87737, PR fortran/46691, PR fortran/99819, PR fortran/98411, PR libstdc++/101965, PR libstdc++/100682, PR libstdc++/100285, PR libstdc++/100180, PR libstdc++/100286, PR libstdc++/100351, PR libstdc++/100286, PR libstdc++/100285, PR libstdc++/100180, PR c++/101592, PR tree-optimization/102124, PR target/101472 (x86), PR target/99744 (x86), PR target/101492 (x86), PR target/101549 (x86), PR target/101471 (x86), PR target/102035 (ARM), PR target/102035 (ARM), PR middle-end/101949, PR ipa/97565, PR debug/101905, PR gcov-profile/89961, PR fortran/87737, PR fortran/46691, PR fortran/99819, PR fortran/98411, PR libstdc++/101965, PR libstdc++/100682
Bug#993162: marked as done (libgcc-s1: i386 (Geode LX): latest push to Bookwork produces multiple sig ILL)
Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 993162 993172 Changes: gcc-11 (11.2.0-4) unstable; urgency=medium . * Update to git 20210902 from the gcc-11 branch. - Fix PR target/101472 (x86), PR target/99744 (x86), PR target/101492 (x86), PR target/101549 (x86), PR target/101471 (x86), PR target/102035 (ARM), PR target/102035 (ARM), PR middle-end/101949, PR ipa/97565, PR debug/101905, PR gcov-profile/89961, PR fortran/87737, PR fortran/46691, PR fortran/99819, PR fortran/98411, PR libstdc++/101965, PR libstdc++/100682, PR libstdc++/100285, PR libstdc++/100180, PR libstdc++/100286, PR libstdc++/100351, PR libstdc++/100286, PR libstdc++/100285, PR libstdc++/100180, PR c++/101592, PR tree-optimization/102124, PR target/101472 (x86), PR target/99744 (x86), PR target/101492 (x86), PR target/101549 (x86), PR target/101471 (x86), PR target/102035 (ARM), PR target/102035 (ARM), PR middle-end/101949, PR ipa/97565, PR debug/101905, PR gcov-profile/89961, PR fortran/87737, PR fortran/46691, PR fortran/99819, PR fortran/98411, PR libstdc++/101965, PR libstdc++/100682, PR libstdc++/100285, PR libstdc++/100180, PR libstdc++/100286, PR libstdc++/100351, PR libstdc++/100286, PR libstdc++/100285, PR libstdc++/100180. * Again, for armhf configure --with-arch=+fp, dropping the --with-fpu= option; keep the old configure options for backports. * Update libgcc-s1 symbols file for sh4. * Remove trailing spaces in symbols files. * Don't configure with --enable-cet on x86 for Debian (old hardware is more valued than recent security features). Closes: #993162, #993172. * Don't run the tests with the installed libstdc++ on slow buildds. * Build again for mipsel and mips64el, too much hassle with separate sources. * Disable the lto build on sparc64, memory issues on the buildd. Checksums-Sha1: d8a969dbdcc879b62ae8e2ce6a6b22e2b8d251c5 27453 gcc-11_11.2.0-4.dsc eb2a6855c4d1ffbb049aa37bf466a6587138d0d9 1773932 gcc-11_11.2.0-4.debian.tar.xz 94a590b05c7784b827f1b448fb9cf04f6c68a2fd 8519 gcc-11_11.2.0-4_source.buildinfo Checksums-Sha256: f4e8d3990915550274b1daaad4776a9d15ded0038fa049274b81f3c0a472384e 27453 gcc-11_11.2.0-4.dsc 0f2f76372131d97ca943bf68c9193b939e254f77c788efce4888486591c0b8cf 1773932 gcc-11_11.2.0-4.debian.tar.xz e4882556a0d95e0d157ed4d015f1f92279f461b0b21e4306455bd2cd2245b2f9 8519 gcc-11_11.2.0-4_source.buildinfo Files: 4db7d137087527ea0d137c117ab64310 27453 devel optional gcc-11_11.2.0-4.dsc f28a98e0eefe73cd5f125b5a92faa7f1 1773932 devel optional gcc-11_11.2.0-4.debian.tar.xz c5e183f7aa97d142f35d32d05df759d8 8519 devel optional gcc-11_11.2.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmEw12MQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9ZSoEACd1jfvjkJarNkmU3CtYycp4WaYAyIAw30k LDBklv/ZdXOf0NeGfyIZPYjM1zaMQhz5/KQLeRUPXk0XQ0w1Oh4I2i0jf4vMXIrF 3dg4zILtymsGZYoiRoowrghgsjZXX3mqsbq2HguwTMVvaEdFF9LEDMSRwQp9Wp/j TJxm2bqSJsn82vFbjEDT4MNXEhvDKRywNlgE9Hxwxdh88xg/9sD24RihwJg+9ruB Fusn61AMSx3gnXvUjYKZ314feBAxmmh+G+58qmZleSaov0IMRTcQA0g/LshirBfo ISIBU+xNBqRd6BQJutTNZwWGWMnNfvMC3VdfWaeX2n9VQ6e3t51QAPtALzPIPLwO eU4rzktX0HTQdBYfRxm2fhvy3ZO3tWbUfj0mK7iky6H4vvz1BWIM48PiqFVaKyJ5 N0ZUeSvkv24xZmDMQJxhxvzkRLZ4hsvU7ZDpUXviVkQHcnVW0fUt9vNC3ddESDrR n/ADRDVUzp4gbdeD5wp9rw9TeybTnW8bnhc2pEV9c9yT0aID6TRQx4cKKwQJOmSI ZvQMpLcWIREe4PVoTL2LNKD3Wr2aR+q7gJqoGv3kQNWa/jNUs+DTK7jj93QE3tZJ aahBQ3kYe2GLitSDpaziDr4DJI7A13rwchipRjJuKSipP2CUdHKZmqxI1YjP/uw4 L2Pi+n9y3w== =xzyI -END PGP SIGNATURE End Message ---
Bug#982177: Bullseye has been released
Hi Just a reminder that Bullseye has been released, so I think this blocking bug should be closed Best regards Carlos
Processed: Re: bzip2: Use tempfile in /usr/bin/bzexe, which is no longer available
Processing control commands: > tags -1 + pending Bug #992442 [bzip2] bzip2: Use tempfile in /usr/bin/bzexe, which is no longer available Added tag(s) pending. -- 992442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992442: bzip2: Use tempfile in /usr/bin/bzexe, which is no longer available
Control: tags -1 + pending On Wed, 18 Aug 2021 12:34:23 -0400 Boyuan Yang wrote: > Package: bzip2 > Severity: grave > Version: 1.0.8-4 > Control: tags -1 sid > X-Debbugs-CC: santi...@debian.org santi...@debian.org > > Dear Debian bzip2 package maintainers, > > As discussed in https://bugs.debian.org/992396 , the tempfile command has been > removed from debianutils package. However, it looks like the bzexe command > provided by Debian still uses it: > > https://sources.debian.org/src/bzip2/1.0.8-4/debian/bzexe/#L123 > > > set -C > umask=`umask` > umask 77 > tmpfile=`tempfile -p gztmp -d /tmp` || exit 1 > > > Please consider switching to mktemp(1) provided by GNU coreutils. > > Thanks, > Boyuan Yang Fixed in git. signature.asc Description: PGP signature
Bug#979041: marked as done (libopempi3: aborts python code due to libfabric fork() issues)
Your message dated Thu, 02 Sep 2021 13:50:02 + with message-id and subject line Bug#979041: fixed in openmpi 4.1.1-4 has caused the Debian Bug report #979041, regarding libopempi3: aborts python code due to libfabric fork() issues 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.) -- 979041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenmpi3 Version: 4.1.0-3 Severity: serious The revert of pmix has fixed some issues, but python packages still show autopkgtest regressions in dolfin[1], gpaw[2], gyoto[3] and mshr[4] . The error is always like this: |A process has executed an operation involving a call |to the fork() system call to create a child process. | |As a result, the libfabric EFA provider is operating in |a condition that could result in memory corruption or |other system errors. | |For the libfabric EFA provider to work safely when fork() |is called, you will need to set the following environment |variable: | RDMAV_FORK_SAFE | |However, setting this environment variable can result in |signficant performance impact to your application due to |increased cost of memory registration. | |You may want to check with your application vendor to see |if an application-level alternative (of not using fork) |exists. | |Your job will now abort. If I export RDMAV_FORK_SAFE=1, the tests run fine, but (i) it seems something in OpenMPI has changed so that those programs no longer run and (ii) the warnings about performance issues are to be considered. Also note that it seems those errors only happen on amd64/i386, the ARM ports run fine, maybe because of missing libfabric-related features/packages? Michael [1] https://ci.debian.net/data/autopkgtest/testing/amd64/d/dolfin/9184050/log.gz [2] https://ci.debian.net/data/autopkgtest/testing/amd64/g/gpaw/9302177/log.gz [3] https://ci.debian.net/data/autopkgtest/testing/amd64/g/gyoto/9303088/log.gz [4] https://ci.debian.net/data/autopkgtest/testing/amd64/m/mshr/9300183/log.gz --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 4.1.1-4 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of openmpi, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated openmpi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Sep 2021 13:31:02 +0100 Source: openmpi Architecture: source Version: 4.1.1-4 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 979041 Changes: openmpi (4.1.1-4) unstable; urgency=medium . * Don't ship libopen-orted-mpir.so. Patch from upstream for 4.1.2 internal lib only. * Also exclude mtl ofi to deal with libfabric fork in tests. Closes: #979041 Checksums-Sha1: 9d57f09686a0e63f30ddace5319af34361fc405c 2670 openmpi_4.1.1-4.dsc 7d8a3153513b53b89d037e2140d00ec731ccb43b 68228 openmpi_4.1.1-4.debian.tar.xz Checksums-Sha256: 7493a2e12cb4f336e3172358bd6bae9e61871216214f97e25366a21d4d66c21c 2670 openmpi_4.1.1-4.dsc c7fe79181f432a7eac47cd0cd0ab7662883b755f1abd18d6649c296151de81c8 68228 openmpi_4.1.1-4.debian.tar.xz Files: 020b26d6112e653db3a184ed99278620 2670 net optional openmpi_4.1.1-4.dsc a7e96cb6f1ff140d007afef518b397e5 68228 net optional openmpi_4.1.1-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmEw06MACgkQy+a7Tl2a 06WNZQ/9F5HvKIhQC6Z2i+QY9y58j+LN8bWXQhObeTA3nVvKnPRXOfcF6p7OV9/5 x3yGXKZ/Y20JVmTeT5ezgsIJ/z0dQWy3t4YUYgdye0Po+0RSWOAbli83a2cXtTgl 9cmmu9xIHjs76VkfnpYWrtVZ19Z8ahg8u/al8e2s5U2k92/D3eSxA79T/Jw8nbX8 2EOaUDyFBUAF4DRycVzG54m2WFqZ3xHC/+HQzfsUxSYoscy9mVvpPnqfpQJfsx3y S/Y1D+wOnkDVwDSKYz9gZg13089N43d7Qu9Jd9xVymnvPLvKV0cxQSC/1fV5xvF+ mtSlSo5+2ogotXYMjn4nGZb7Uwp3lbiXhNOTVvbuW1EgpgSwiH/KqDSBhkKJW0MD 7nFMlVYUiGRKtxfWfUE6hXSVW/VxpYalUz7CWY+n3jph0QJR3OqzcuYHlboiNCYH /uXN0R5GwQWgdBBJQe8ybOyK2x5kRYkkEBvtSOiRlMtzGkdVmqoi1WLiTVHPnkcf
Bug#993514: perl/experimental FTBFS with gdbm 1.20
Source: perl Version: 5.34.0-1 Severity: serious Tags: ftbfs fixed-upstream Forwarded: https://github.com/Perl/perl5/issues/18915 https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/perl.html https://buildd.debian.org/status/package.php?p=perl=experimental ... Failed 1 test out of 2544, 99.96% okay. ../ext/GDBM_File/t/gdbm.t ... make[2]: *** [makefile:808: test] Error 1
Bug#992439: libconfig-model-dpkg-perl: blocks fails autopkgtest with recent licensecheck
Quoting Dominique Dumont (2021-09-02 12:41:03) > On Fri, 20 Aug 2021 02:57:28 +0200 gregor herrmann wrote: > > Right, there is e.g. > > https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libconfig-model-dpkg-perl/14728439/log.gz > > with libconfig-model-dpkg-perl/2.147 licensecheck/3.2.11-1 and > > > > #v+ > > not ok 7 - check scikit-learn copyright > > > > # Failed test 'check scikit-learn copyright' > > # at t/scanner/scan-copyright.t line 27. > > # --- t/scanner/examples/scikit-learn.out Thu Aug 19 00:15:51 2021 > > # +++ /tmp/cKnQzIwFn2 Thu Aug 19 14:57:19 2021 > > # @@ -2,3 +2,7 @@ > > # Copyright: 2007-2019, The scikit-learn developers. > > # License: BSD-3-clause > > # > > # +Files: sklearn/* > > # +Copyright: no-info-found > > # +License: BSD-3-clause > > # + > > #v- > > Actually, this is related to: > > https://salsa.debian.org/perl-team/modules/packages/libconfig-model-dpkg-perl/-/commit/fb4dbe585de59a8aeb5d01904869a7f3415e35a5 > > (Note: I found this commit while checking the history of t/scanner/examples/ > scikit-learn.out) > > > And I still can't reproduce the failure locally. > > *sigh* > > I can reproduce this bug locally with libregexp-pattern-license-perl_3.4.0-1 > which is the version used in the FTBS build. > > This bug is gone after installing libregexp-pattern-license-perl/unstable. Thanks for looking into this, Dominique. Licensecheck does not promise any specific detection, so if your tool rely on specific detection then I guess it should declare tight dependencies on both App::Licensecheck and Regexp::Pattern::License. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs
Hi, On Thu, 2 Sep 2021 10:17:22 +0200 Sascha Steinbiss wrote: > I think this is done now. With YARA 4.1.2 and > golang-github-hillu-go-yara 4.1.0 now in unstable, the build works again > as the build-time tests complete fine. > > @Hilko any other comments? If there are incompatible API changes, the soname needs to be bumped. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#992439: libconfig-model-dpkg-perl: blocks fails autopkgtest with recent licensecheck
On Fri, 20 Aug 2021 02:57:28 +0200 gregor herrmann wrote: > Right, there is e.g. > https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libconfig-model-dpkg-perl/14728439/log.gz > with libconfig-model-dpkg-perl/2.147 licensecheck/3.2.11-1 and > > #v+ > not ok 7 - check scikit-learn copyright > > # Failed test 'check scikit-learn copyright' > # at t/scanner/scan-copyright.t line 27. > # --- t/scanner/examples/scikit-learn.out Thu Aug 19 00:15:51 2021 > # +++ /tmp/cKnQzIwFn2 Thu Aug 19 14:57:19 2021 > # @@ -2,3 +2,7 @@ > # Copyright: 2007-2019, The scikit-learn developers. > # License: BSD-3-clause > # > # +Files: sklearn/* > # +Copyright: no-info-found > # +License: BSD-3-clause > # + > #v- Actually, this is related to: https://salsa.debian.org/perl-team/modules/packages/libconfig-model-dpkg-perl/-/commit/fb4dbe585de59a8aeb5d01904869a7f3415e35a5 (Note: I found this commit while checking the history of t/scanner/examples/ scikit-learn.out) > And I still can't reproduce the failure locally. > *sigh* I can reproduce this bug locally with libregexp-pattern-license-perl_3.4.0-1 which is the version used in the FTBS build. This bug is gone after installing libregexp-pattern-license-perl/unstable. HTH
Bug#993470: marked as done (gcc-10 rejected)
Your message dated Thu, 02 Sep 2021 10:33:32 + with message-id and subject line Bug#993470: fixed in gcc-10 10.3.0-9 has caused the Debian Bug report #993470, regarding gcc-10 rejected 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.) -- 993470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-10 Version: 10.3.0-8 Severity: serious Your upload included the binary package lib32atomic1, version 10.3.0-8, for mips64el, however unstable already has version 11.2.0-3+b1. --- End Message --- --- Begin Message --- Source: gcc-10 Source-Version: 10.3.0-9 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-10, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-10 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Sep 2021 12:00:51 +0200 Source: gcc-10 Architecture: source Version: 10.3.0-9 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 993470 Changes: gcc-10 (10.3.0-9) unstable; urgency=medium . * Update to git 20210902 from the gcc-10 branch. - Fix PR fortran/46691, PR fortran/99819, PR fortran/99818, PR fortran/93924, PR fortran/93925, PR fortran/93794, PR fortran/99125. * Remove trailing spaces in symbols files. * Fix not building the common packages on mipsen. Closes: #993470. * Don't run the tests with the installed libstdc++ on slow buildds. Checksums-Sha1: ab14ce6263ab661852d5ea8843d885a33141ed79 22010 gcc-10_10.3.0-9.dsc a4760562af2972e7fd08c9fcc0807f69cf221a01 772752 gcc-10_10.3.0-9.debian.tar.xz f55b99a7221c549a202339f597e6fe4ab113d0d5 8519 gcc-10_10.3.0-9_source.buildinfo Checksums-Sha256: 1c0a0f5d46b573e1455e28826956a76e271818f504350bc10d8a5c45d830fd6a 22010 gcc-10_10.3.0-9.dsc 4577aa7e96d3bfb1e1e2a537a130a682fc1e0b30f57035031a2a88de0fa670e0 772752 gcc-10_10.3.0-9.debian.tar.xz 48ff3e976bee16ccb6355060134cc259dd3129d6cff8c4a2d2443641fd312de1 8519 gcc-10_10.3.0-9_source.buildinfo Files: 771c4f1c44d55dadbcd636b7f4155f8b 22010 devel optional gcc-10_10.3.0-9.dsc 873cff11f7e44a2eeaf346cf7429941c 772752 devel optional gcc-10_10.3.0-9.debian.tar.xz e8f12cdfef1ed27a498b8f57ca152276 8519 devel optional gcc-10_10.3.0-9_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmEwpDkQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9aWDEAC8MZPs9d0XxpO+Nq9VYy7vfK1Yj7VSmOtB eneEuBpB7ddlAKey4jJkFJXhwya0aNe5jkv1oxVWA6k7w8hFRX4WP2yr8V6Sh1Vx BCUTEUJ3A2RS/tXEATJYRSDPm3vh6rGfzdUhBam0FJ1jvDrqEGQFLQylfZxI7GxX 54n+5Zu2TDRn0gxGrnM2yAuD+7pal1z876Xh3fqxSDYCn6D2hbqLaIMPLdhdX4yB KFjcwW/hwBEvrJc+w3HOBoUShBXs6GELbraQLWQqcxFOY9IwnRhqtogc0Qd+P2zf 3T0p2CuNb/vhO//a875U9teq8612oLNfmtF9X6D+9hcdd874Kco6xQhYkXLcWyug /V7CiYlhwd74u4569zC7Du11CGpusetY6z9dLeAcxxOhNAHBSxMeWpFtTqb0rd45 yu6Dmkw724KZio4xlgk5/6DSiYLl6Uw6GZHReR69h6PzB1EstR0dM4XkRNmG45d5 lTtCU3ZSwkcNBPudzTH6NPzZrzUgLXKk6hw1T8toDX8imWtAwxTCydRYZKqIj6Ma 3hjNczpP4Vw7/HsY4W9/O+sbyvYPkVpdWoVA7QT1YhkCym69r6OFTZsGQKfyJOse Z5Vw6k3pgEsw0jzp9b/OM5Z0594aq2cCEtiflf6NeRQsruWExsPiAc4bTU3pbBZm nY56sLEDPA== =lEnh -END PGP SIGNATURE End Message ---
Bug#993505: netgen-lvs FTBFS: configure: error: cannot find required auxiliary files: install-sh config.guess config.sub
Source: netgen-lvs
Version: 1.5.133-1
Severity: serious
Tags: ftbfs
netgen-lvs fails to build from source. A build on amd64 ends as follows:
|dh_autoreconf
| autoreconf: warning: autoconf input should be named 'configure.ac', not
'configure.in'
| aclocal: warning: autoconf input should be named 'configure.ac', not
'configure.in'
| configure.in:9: warning: The macro `AC_CANONICAL_SYSTEM' is obsolete.
| configure.in:9: You should run autoupdate.
| ./lib/autoconf/general.m4:2081: AC_CANONICAL_SYSTEM is expanded from...
| configure.in:9: the top level
| configure.in:25: warning: The macro `AC_ISC_POSIX' is obsolete.
| configure.in:25: You should run autoupdate.
| ./lib/autoconf/specific.m4:550: AC_ISC_POSIX is expanded from...
| configure.in:25: the top level
| configure.in:149: warning: The macro `AC_HEADER_STDC' is obsolete.
| configure.in:149: You should run autoupdate.
| ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
| configure.in:149: the top level
| configure.in:171: warning: The macro `AC_TRY_LINK' is obsolete.
| configure.in:171: You should run autoupdate.
| ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
| configure.in:171: the top level
| configure.in:184: warning: The macro `AC_TRY_LINK' is obsolete.
| configure.in:184: You should run autoupdate.
| ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
| configure.in:184: the top level
| configure.in:874: warning: $as_echo is obsolete; use AS_ECHO(["message"])
instead
| configure.in:1293: warning: AC_OUTPUT should be used without arguments.
| configure.in:1293: You should run autoupdate.
| configure.in:1293: warning: AC_C_BIGENDIAN should be used with
AC_CONFIG_HEADERS
|debian/rules override_dh_auto_configure
| make[1]: Entering directory '/<>'
| dh_auto_configure -- --libdir=\${prefix}/lib
| ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libdir=\${prefix}/lib
| configure: error: cannot find required auxiliary files: install-sh
config.guess config.sub
| dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libdir=\${prefix}/lib
returned exit code 1
| make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:15: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Bug#993503: gcc-11-base: coinstallation error for mipsel
Package: gcc-11-base Version: 11.2.0-3 Severity: serious Justification: dpkg unpack error gcc-11-base's changelog.Debian.gz is different on mipsel than everywhere else. Indeed, the version is duplicate in the changelog. As such, gcc-11-base:mipsel fails to coinstall with everything else despite being marked Multi-Arch: same. | Unpacking gcc-11-base:mipsel (11.2.0-3) ... | dpkg: error processing archive /tmp/apt-dpkg-install-kpSb1U/012-gcc-11-base_11.2.0-3_mipsel.deb (--unpack): | trying to overwrite shared '/usr/share/doc/gcc-11-base/changelog.Debian.gz', which is different from other instances of package gcc-11-base:mipsel The cause seems to be a binary upload. Any normal upload should fix this issue without further changes. Helmut
Bug#993099: marked as done (libprelude arch-only FTBFS: Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293.)
Your message dated Thu, 02 Sep 2021 09:49:22 + with message-id and subject line Bug#993099: fixed in libprelude 5.2.0-4 has caused the Debian Bug report #993099, regarding libprelude arch-only FTBFS: Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293. 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.) -- 993099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libprelude Version: 5.2.0-3 Severity: serious Tags: ftbfs libprelude fails to build from source in an arch-only build. The log ends with: |dh_autoreconf -a | libtoolize: putting auxiliary files in '.'. | libtoolize: copying file './ltmain.sh' | libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. | libtoolize: copying file 'm4/libtool.m4' | libtoolize: copying file 'm4/ltargz.m4' | libtoolize: copying file 'm4/ltdl.m4' | libtoolize: copying file 'm4/ltoptions.m4' | libtoolize: copying file 'm4/ltsugar.m4' | libtoolize: copying file 'm4/ltversion.m4' | libtoolize: copying file 'm4/lt~obsolete.m4' | libtoolize: putting libltdl files in LT_CONFIG_LTDL_DIR, 'libltdl'. | libtoolize: copying file 'libltdl/COPYING.LIB' | libtoolize: creating file 'libltdl/Makefile.am' | libtoolize: copying file 'libltdl/README' | libtoolize: creating file 'libltdl/Makefile.in' | libtoolize: copying file 'libltdl/libltdl/lt__alloc.h' | libtoolize: copying file 'libltdl/libltdl/lt__argz_.h' | libtoolize: copying file 'libltdl/libltdl/lt__dirent.h' | libtoolize: copying file 'libltdl/libltdl/lt__glibc.h' | libtoolize: copying file 'libltdl/libltdl/lt__private.h' | libtoolize: copying file 'libltdl/libltdl/lt__strl.h' | libtoolize: copying file 'libltdl/libltdl/lt_dlloader.h' | libtoolize: copying file 'libltdl/libltdl/lt_error.h' | libtoolize: copying file 'libltdl/libltdl/lt_system.h' | libtoolize: copying file 'libltdl/libltdl/slist.h' | libtoolize: copying file 'libltdl/loaders/dld_link.c' | libtoolize: copying file 'libltdl/loaders/dlopen.c' | libtoolize: copying file 'libltdl/loaders/dyld.c' | libtoolize: copying file 'libltdl/loaders/load_add_on.c' | libtoolize: copying file 'libltdl/loaders/loadlibrary.c' | libtoolize: copying file 'libltdl/loaders/preopen.c' | libtoolize: copying file 'libltdl/loaders/shl_load.c' | libtoolize: copying file 'libltdl/lt__alloc.c' | libtoolize: copying file 'libltdl/lt__argz.c' | libtoolize: copying file 'libltdl/lt__dirent.c' | libtoolize: copying file 'libltdl/lt__strl.c' | libtoolize: copying file 'libltdl/lt_dlloader.c' | libtoolize: copying file 'libltdl/lt_error.c' | libtoolize: copying file 'libltdl/ltdl.c' | libtoolize: copying file 'libltdl/ltdl.h' | libtoolize: copying file 'libltdl/slist.c' | Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293. | autoreconf: error: gtkdocize failed with exit status: 2 | dh_autoreconf: error: autoreconf -f -i returned exit code 2 | make: *** [debian/rules:57: binary-arch] Error 25 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 A quick fix likely is moving gtk-doc-tools from B-D-I to B-D, but Andreas Metzler found a way of avoiding that in gnutls28 and libtasn1-6. Helmut --- End Message --- --- Begin Message --- Source: libprelude Source-Version: 5.2.0-4 Done: Thomas Andrejak We believe that the bug you reported is fixed in the latest version of libprelude, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Andrejak (supplier of updated libprelude package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Aug 2021 20:53:39 +0200 Source: libprelude Architecture: source Version: 5.2.0-4 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier Changed-By: Thomas Andrejak Closes: 991100 993099 Changes: libprelude (5.2.0-4) unstable; urgency=medium . [ Helmut Grohne ] * Improve cross satisfiability. (Closes: #991100) + Drop unnecessary versioned g++ dependency. + Build-Depends:
Processed: tagging 978893
Processing commands for cont...@bugs.debian.org: > tags 978893 + ftbfs Bug #978893 [src:ripperx] ripperx: ftbfs with autoconf 2.70 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 978893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 978911
Processing commands for cont...@bugs.debian.org: > tags 978911 + ftbfs Bug #978911 [src:transmission] transmission: ftbfs with autoconf 2.70 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 978911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 993052 with 993491
Processing commands for cont...@bugs.debian.org: > block 993052 with 993491 Bug #993052 [release.debian.org] transition: tracker 993052 was blocked by: 993361 993430 993412 993052 was not blocking any bugs. Added blocking bug(s) of 993052: 993491 > thanks Stopping processing here. Please contact me if you need assistance. -- 993052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs
Hi, I think this is done now. With YARA 4.1.2 and golang-github-hillu-go-yara 4.1.0 now in unstable, the build works again as the build-time tests complete fine. @Hilko any other comments? Cheers Sascha
Bug#979041: libopempi3: aborts python code due to libfabric fork() issues
On 02/09/21 at 00:16 +0200, Lucas Nussbaum wrote: > reopen 979041 > notfixed 979041 4.1.0-7 > thanks > > Hi, > > I ran into this problem with 4.1.0-7. The ofi BTL was disabled, but not > the ofi MTL. In some cases, both need to be disabled. > > You need something like: > mtl = ^ofi > in addition to: > btl = ^ofi > > (I ran into this with https://github.com/LLNL/mpiGraph and > libhwloc-contrib-plugins, and CUDA installed -- let me know if you need > help reproducing) Thinking about this again, I wonder if instead of disabling OFI/libfabric in OpenMPI, we shouldn't instead disable the EFA provider in libfabric, since it seems to be the only one causing the error on fork(). Alternatively, fork() support has been added to the libfabric EFA provider (https://github.com/ofiwg/libfabric/issues/6332), but this is unlikely to be accepted in a stable update. Given that OFI was not really disabled in OpenMPI anyway, keeping it enabled and disabling EFA in libfabric is actually a minor change. For context, EFA is an AWS-specific provider, see https://www.hpcworkshops.com/07-efa/00-efa-basics.html Lucas
Bug#993494: thunderbird FTBFS with autoconf 2.71
Source: thunderbird Version: 1:78.4.0-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=thunderbird=sid https://buildd.debian.org/status/package.php?p=thunderbird=experimental ... debian/rules binary-arch dh binary-arch dh_update_autotools_config -a dh_autoreconf -a autoreconf: warning: autoconf input should be named 'configure.ac', not 'configure.in' autoreconf: error: configure.in: AC_INIT not found; not an autoconf script? dh_autoreconf: error: autoreconf -f -i returned exit code 1
Bug#993109: marked as done (src:gdisk: fails to migrate to testing for too long: ftbfs on s390x)
Your message dated Thu, 2 Sep 2021 08:00:30 +0200 with message-id <9b54d643-b1f7-f24e-3c31-f31bf29f6...@debian.org> and subject line New upload to unstable has caused the Debian Bug report #993109, regarding src:gdisk: fails to migrate to testing for too long: ftbfs on s390x 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.) -- 993109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdisk Version: 1.0.6-1.1 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:gdisk has been trying to migrate for 142 days [2] (yes I know, mostly during the freeze). Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=gdisk OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- New version has been uploaded to unstable, and this package should now migrate just fine.--- End Message ---
Processed: tagging 993491
Processing commands for cont...@bugs.debian.org: > tags 993491 + sid bookworm Bug #993491 [src:grilo-plugins] grilo-plugins: Please switch to tracker 3 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 993491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
