Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 1069437 libnginx-mod-http-set-misc Bug #1069437 [nginx] libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Added indication that 1069437 affects libnginx-mod-http-set-misc > affects 1069437 - libnginx-mod-http-lua Bug #1069437 [nginx] libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Removed indication that 1069437 affects libnginx-mod-http-lua > thank you Stopping processing here. Please contact me if you need assistance. -- 1069437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 1069525 libnginx-mod-http-srcache-filter Bug #1069525 [nginx] libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Added indication that 1069525 affects libnginx-mod-http-srcache-filter > affects 1069525 - libnginx-mod-http-lua Bug #1069525 [nginx] libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Removed indication that 1069525 affects libnginx-mod-http-lua > thank you Stopping processing here. Please contact me if you need assistance. -- 1069525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 1069525 nginx Bug #1069525 [src:libnginx-mod-http-srcache-filter] libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Bug reassigned from package 'src:libnginx-mod-http-srcache-filter' to 'nginx'. No longer marked as found in versions libnginx-mod-http-srcache-filter/0.33-3. Ignoring request to alter fixed versions of bug #1069525 to the same values previously set > affects 1069525 libnginx-mod-http-lua Bug #1069525 [nginx] libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Added indication that 1069525 affects libnginx-mod-http-lua > fixed 1069525 nginx/1.26.0-1 Bug #1069525 [nginx] libnginx-mod-http-srcache-filter: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Marked as fixed in versions nginx/1.26.0-1. > thank you Stopping processing here. Please contact me if you need assistance. -- 1069525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 1069437 nginx Bug #1069437 [src:libnginx-mod-http-set-misc] libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Bug reassigned from package 'src:libnginx-mod-http-set-misc' to 'nginx'. No longer marked as found in versions libnginx-mod-http-set-misc/0.33-5. Ignoring request to alter fixed versions of bug #1069437 to the same values previously set > affects 1069437 libnginx-mod-http-lua Bug #1069437 [nginx] libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Added indication that 1069437 affects libnginx-mod-http-lua > fixed 1069437 nginx/1.26.0-1 Bug #1069437 [nginx] libnginx-mod-http-set-misc: FTBFS on armhf: make: *** [debian/rules:6: binary] Error 25 Marked as fixed in versions nginx/1.26.0-1. > thank you Stopping processing here. Please contact me if you need assistance. -- 1069437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070476: openjdk-21: autopkgtest on i386: /usr/bin/ld: /usr/lib/jvm/java-21-openjdk-i386/lib/server/libjvm.so: undefined reference to `_SafeFetch32_impl'
Source: openjdk-21 Version: 21.0.3+9-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org openjdk-21 is unable to migrate since the version in unstable fails its autopkgtests on i386. https://ci.debian.net/packages/o/openjdk-21/testing/i386/46308616/#S21 9507s autopkgtest [09:27:46]: test jni-link.sh: [--- 9507s /usr/lib/jvm/java-21-openjdk-i386/lib/server 9507s /usr/bin/ld: /usr/lib/jvm/java-21-openjdk-i386/lib/server/libjvm.so: undefined reference to `_SafeFetch32_impl' 9507s collect2: error: ld returned 1 exit status 9508s autopkgtest [09:27:47]: test jni-link.sh: ---] Cheers -- Sebastian Ramacher
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 1069482 nginx Bug #1069482 [src:libnginx-mod-http-lua] libnginx-mod-http-lua: FTBFS on armhf: module "/usr/share/nginx/modules/ndk_http_module.so" is not binary compatible Bug reassigned from package 'src:libnginx-mod-http-lua' to 'nginx'. No longer marked as found in versions libnginx-mod-http-lua/1:0.10.26-2. Ignoring request to alter fixed versions of bug #1069482 to the same values previously set > affects 1069482 libnginx-mod-http-lua Bug #1069482 [nginx] libnginx-mod-http-lua: FTBFS on armhf: module "/usr/share/nginx/modules/ndk_http_module.so" is not binary compatible Added indication that 1069482 affects libnginx-mod-http-lua > fixed 1069482 nginx/1.26.0-1 Bug #1069482 [nginx] libnginx-mod-http-lua: FTBFS on armhf: module "/usr/share/nginx/modules/ndk_http_module.so" is not binary compatible Marked as fixed in versions nginx/1.26.0-1. > thank you Stopping processing here. Please contact me if you need assistance. -- 1069482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070421: marked as done (src:mac-widgets: unsatisfied build dependency in testing: libjgoodies-forms-java-doc)
Your message dated Mon, 06 May 2024 04:19:21 + with message-id and subject line Bug#1070421: fixed in mac-widgets 0.10.0+svn416-dfsg1-4 has caused the Debian Bug report #1070421, regarding src:mac-widgets: unsatisfied build dependency in testing: libjgoodies-forms-java-doc 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.) -- 1070421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mac-widgets Version: 0.10.0+svn416-dfsg1-3 Severity: serious Tags: sid trixie ftbfs User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. src:libjgoodies-forms-java stopped building libjgoodies-forms-java-doc in it's latest upload, so your package can no longer be build in unstable either. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: mac-widgets Source-Version: 0.10.0+svn416-dfsg1-4 Done: tony mancill We believe that the bug you reported is fixed in the latest version of mac-widgets, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated mac-widgets 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, 05 May 2024 20:56:09 -0700 Source: mac-widgets Architecture: source Version: 0.10.0+svn416-dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 1070421 Changes: mac-widgets (0.10.0+svn416-dfsg1-4) unstable; urgency=medium . * Team upload. * Drop libmac-widgets-doc (Closes: #1070421) * Update Vcs URLs to point to Salsa Checksums-Sha1: 3a062b3348c7af71b7769e6c4acd59a17f3fe92e 2139 mac-widgets_0.10.0+svn416-dfsg1-4.dsc 008f263640802c1e59253bdf160bce5cd3ac3904 3464 mac-widgets_0.10.0+svn416-dfsg1-4.debian.tar.xz d57cf227cf9de9a4100fa3a59066c1a81ca3e045 12410 mac-widgets_0.10.0+svn416-dfsg1-4_amd64.buildinfo Checksums-Sha256: ae2dcfcfc79c112f133d4bfc93dd6dc4e6b78b9a310e2480ce724800a41e32d1 2139 mac-widgets_0.10.0+svn416-dfsg1-4.dsc f8fc286aa3fb1fb12e6b0d52a8037a78850ab18fe4c2287455c45068b881b67a 3464 mac-widgets_0.10.0+svn416-dfsg1-4.debian.tar.xz c3fee93ad7c043d167f0fcde7b450a7695c8e1a348e9c6052e0d7018657ce333 12410 mac-widgets_0.10.0+svn416-dfsg1-4_amd64.buildinfo Files: 5ab27ddc0e31d010fadd2857c3464def 2139 java optional mac-widgets_0.10.0+svn416-dfsg1-4.dsc 1ec8f573719d13d960fb75f52828611a 3464 java optional mac-widgets_0.10.0+svn416-dfsg1-4.debian.tar.xz 269cd1fef0592f32a2004498352cc741 12410 java optional mac-widgets_0.10.0+svn416-dfsg1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmY4WDkUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZjPxAAsszF0rx6X+tI091KRrrkZ1y2EQ+F 3eWPja9mLJr0G/SijNxgy9Op+I5xFQogTk+tDp5FM/8cDl9LUyDJkwsjHoowWvEL 8AoTsx1NYI4D1CO9EghOgGtF9Zflb9IGjvaltD+I42TJI5Y1HeNNu/CnJ1S9bKjE TtxsitjCX7r8r19xhEIm5x1VOubaYed7F0RaQEHHQPTmdWU0GcaxVkKpIwTLnNQn
Processed: Bug#1070421 marked as pending in mac-widgets
Processing control commands: > tag -1 pending Bug #1070421 [src:mac-widgets] src:mac-widgets: unsatisfied build dependency in testing: libjgoodies-forms-java-doc Added tag(s) pending. -- 1070421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070421: marked as pending in mac-widgets
Control: tag -1 pending Hello, Bug #1070421 in mac-widgets reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/mac-widgets/-/commit/3fc653d3c0b9e886d5bf9f78d901e17b8b1139df Import Debian changes 0.10.0+svn416-dfsg1-4 mac-widgets (0.10.0+svn416-dfsg1-4) unstable; urgency=medium . * Team upload. * Drop libmac-widgets-doc (Closes: #1070421) * Update Vcs URLs to point to Salsa (this message was generated automatically) -- Greetings https://bugs.debian.org/1070421
Bug#1070472: Uses the obsolete /sbin/route without a dependency
Package: miniupnpd
Version: 2.3.1-1
Severity: serious
Tags: patch
Pseudo-patch for miniupnpd.config:
- MiniUPnPd_EXTERNAL_INTERFACE=$(LC_ALL=C /sbin/route | grep -m 1 default
| awk -- '{ print $8 }')
+ MiniUPnPd_EXTERNAL_INTERFACE=$(LC_ALL=C ip -o route show | sed -nre
'/^default /s/^default .*dev ([^ ]+).*/\1/p')
--
ciao,
Marco
signature.asc
Description: PGP signature
Bug#1070300: pmix_psquash_base_select failed during MPI_INIT on 32bit architectures
Samuel Thibault, le sam. 04 mai 2024 11:49:40 +0200, a ecrit: > Samuel Thibault, le ven. 03 mai 2024 19:00:22 +0200, a ecrit: > > This has been posing migration issues for quite some time, I have > > uploaded the attached fix to delayed/0. > > Some of the components depend on libmca_common_libdstore which also > needs to be installed, otherwise openmpi emits some text on stderr, > which some autopkgtest don't like, I have uploaded the attached changes > to delayed/0 Sorry it seems my tests had gone bogus, I do remember testing the result but apparently obviously failed to. I have double-checked my changes this time, as attached and uploaded to delayed/0 (now that openmpi got a bit force-migrated to testing) Samuel diff -Nru openmpi-4.1.6/debian/changelog openmpi-4.1.6/debian/changelog --- openmpi-4.1.6/debian/changelog 2024-05-04 11:32:26.0 +0200 +++ openmpi-4.1.6/debian/changelog 2024-05-05 20:38:36.0 +0200 @@ -1,3 +1,10 @@ +openmpi (4.1.6-13.3) unstable; urgency=medium + + * Non-maintainer Upload + * Really install libmca_common_dstore. + + -- Samuel Thibault Sun, 05 May 2024 20:38:36 +0200 + openmpi (4.1.6-13.2) unstable; urgency=medium * Non-maintainer Upload diff -Nru openmpi-4.1.6/debian/rules openmpi-4.1.6/debian/rules --- openmpi-4.1.6/debian/rules 2024-05-04 11:32:26.0 +0200 +++ openmpi-4.1.6/debian/rules 2024-05-05 20:38:36.0 +0200 @@ -289,10 +289,11 @@ dh_install -p libopenmpi3t64 $(LIBDIR)/openmpi/lib/libpmix.so.2.2.35 $(LIBDIR) ; \ dh_install -p libopenmpi3t64 /usr/share/pmix ; \ dh_install -p libopenmpi3t64 "/usr/lib/$(DEB_HOST_MULTIARCH)/openmpi/lib/pmix/*.so" ; \ - if test -f $(DESTDIR)/$(LIBDIR)/openmpi/lib/libmca_common_libdstore.so.1.0.2 ; then \ - dh_install -p libopenmpi3t64 $(LIBDIR)/libmca_common_libdstore.so.1.0.2 ; \ - dh_link -p libopenmpi3t64 $(LIBDIR)/libmca_common_libdstore.so.1.0.2 $(LIBDIR)/libmca_common_libdstore.so.1 ; \ - dh_link -p libopenmpi-dev $(LIBDIR)/libmca_common_libdstore.so.1 $(LIBDIR)/libmca_common_libdstore.so ; \ + if test -f $(DESTDIR)/$(LIBDIR)/openmpi/lib/libmca_common_dstore.so.1.0.2 ; then \ + dh_install -p libopenmpi3t64 $(LIBDIR)/openmpi/lib/libmca_common_dstore.so.1.0.2 $(LIBDIR) ; \ + dh_link -p libopenmpi3t64 $(LIBDIR)/libmca_common_dstore.so.1.0.2 $(LIBDIR)/libmca_common_dstore.so.1 ; \ + dh_link -p libopenmpi-dev $(LIBDIR)/libmca_common_dstore.so.1 $(LIBDIR)/openmpi/lib/libmca_common_dstore.so ; \ + dh_link -p libopenmpi-dev $(LIBDIR)/libmca_common_dstore.so.1 $(LIBDIR)/libmca_common_dstore.so ; \ fi ; \ dh_link -p libopenmpi3t64 $(LIBDIR)/libpmix.so.2.2.35 $(LIBDIR)/libpmix.so.2 ; \ dh_link -p libopenmpi-dev $(LIBDIR)/libpmix.so.2 $(LIBDIR)/openmpi/lib/libpmix.so ; \
Bug#1069432: mpi4py: FTBFS on armhf: ld: cannot find -llmpe: No such file or directory
Source: mpi4py Followup-For: Bug #1069432 There have been ongoing issues with OpenMPI on 32-bit architectures, partly related to drop of 32-bit support by pmix. This bug is likely related to that i.e. not a bug in mpi4py itself.
Bug#1065725: marked as done (adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0)
Your message dated Sun, 05 May 2024 22:34:10 +
with message-id
and subject line Bug#1065725: fixed in adns 1.6.1-1
has caused the Debian Bug report #1065725,
regarding adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT
- lines of syscall remaining 0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adns
Version: 1.6.0-2.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=adns=armhf=1.6.0-2.1=1709082246=0
make[2]: Entering directory '/<>/regress'
--- ./case-1stservbroken.out2020-06-11 15:01:23.0 +
+++ output-1stservbroken.out2024-02-28 01:04:01.650317863 +
@@ -5,7 +5,7 @@
adns debug: TCP connected (NS=172.18.45.2)
adns warning: TCP connection failed: read: Broken pipe (NS=172.18.45.2)
adns debug: TCP connected (NS=172.18.45.6)
-trunc.test.iwj.relativity.greenend.org.uk flags 0 type PTR(raw): OK; nrrs=30;
cname=$; owner=$; ttl=60
+trunc.test.iwj.relativity.greenend.org.uk flags 0 type PTR(raw): OK; nrrs=30;
cname=$; owner=$; ttl=57
long.domain.to.force.truncation.0.test.iwj.relativity.greenend.org.uk
long.domain.to.force.truncation.1.test.iwj.relativity.greenend.org.uk
long.domain.to.force.truncation.2.test.iwj.relativity.greenend.org.uk
FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0
make[2]: *** [Makefile:78: check-1stservbroken] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: adns
Source-Version: 1.6.1-1
Done: Ian Jackson
We believe that the bug you reported is fixed in the latest version of
adns, 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 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ian Jackson (supplier of updated adns 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, 05 May 2024 23:11:24 +0100
Source: adns
Architecture: source
Version: 1.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson
Changed-By: Ian Jackson
Closes: 1028112 1061866 1065725
Changes:
adns (1.6.1-1) unstable; urgency=medium
.
* New upstream version. Closes: #1028112, #1065725.
* Fix d/shlibs.local for t64. Closes: #1061866.
[Patch from Matthias Klose]
Checksums-Sha1:
f8d49e51e88ac040367773f2826e628ceeaebe3d 1733 adns_1.6.1-1.dsc
a3192f4bce7969e0b3fa2bc814b64773fc4fb097 322439 adns_1.6.1.orig.tar.gz
3d39c43fa3d19722b69c32dd22b9acf326ed347f 6860 adns_1.6.1-1.debian.tar.xz
Checksums-Sha256:
dd1702734e985f38715fc8127903ca694e0ae4d3bc64cd27ae93f65b490109b5 1733
adns_1.6.1-1.dsc
7138b3789b7506bd683f451d4f7d853077a91803b7b35d86ec667f0f9cd401cd 322439
adns_1.6.1.orig.tar.gz
089e75b5c681fea5cc7208111ee344c28981d8bf937279d29ce9a61546f0bdcf 6860
adns_1.6.1-1.debian.tar.xz
Files:
ccd700d1361ce95904aa8274c14be5a2 1733 devel optional adns_1.6.1-1.dsc
dfd46495001615819cc3a1852ce0d2e1 322439 devel optional adns_1.6.1.orig.tar.gz
ca74c7058f0c8850c7277a192ae4f81a 6860 devel optional adns_1.6.1-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmY4BIIACgkQ4+M5I0i1
DTmnNQf/e/ICbp200GfNTWMzOy03klMa6GAa9Zfh6IqS3sTjlr1x5aO78QxKgsMo
uZcB7DDrDAB/I3yKAc4YEIrzOl3HF5R8wsdmW8SOyJCarAntN+u8Xr1dyaIilv2z
d1l7ircj29mUS/4KC6SKQwOd+mclqnOZ83TFB6nVgtYgI5xk1ROqliM2faALTW+6
Bfh7/7JBRcLyQW3CIv4Zk/GSHBjobsEEJ/iRLqyZk8uNzh37VXHNgu1uYNS2zKPi
cgSrxwFden48pg5vH94BsCKTe1eMrHM541af41pzeDhBJVxo95wFCmW4KFabFyoi
uXfKyUbNjuityiJ2sp6kx44HNxCJgw==
=DgXB
-END PGP SIGNATURE-
pgpMZVmflBeZJ.pgp
Description: PGP signature
--- End Message ---
Bug#1065725: adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0
Dan Bungert writes ("Bug#1065725: adns: FTBFS on arm{el,hf}: FAILED
./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0"):
> I took a look at this bug today.
> I found that the regress testsuite make use of some negative offsets, which
> seem to perplex the reader on 32 bit systems.
>
> Please see the attached patch, which has allowed this to build for Ubuntu.
Thanks. I fixed the problem a little differently, in an upstream
release. (Your patch didn't work for me.)
I have just uploaded to Debian too. You may wish to pick up upstream
1.6.1 via Debian's 1.6.1-1 (or wait for it to build and migrate, maybe).
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Sun, 5 May 2024 at 04:33, Shmerl wrote: > May be for rustc? It's worth filing the bug if it's not clear what the > root cause is. If it's not really rustc, developers will point that out. Filed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070470
Processed: closing 1070458
Processing commands for cont...@bugs.debian.org: > # fallout from the fix of #22 in xneur > close 1070458 Bug #1070458 [src:gxneur] gxneur: FTBFS: Package 'libpcre', required by 'xnconfig', not found Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1070458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066278: marked as done (xnee: FTBFS: xnee_fake.c:809:15: error: implicit declaration of function ‘xnee_check_key’; did you mean ‘xnee_check_true’? [-Werror=implicit-function-declaration])
Your message dated Sun, 05 May 2024 21:43:42 +
with message-id
and subject line Bug#1066278: fixed in xnee 3.19-9.2
has caused the Debian Bug report #1066278,
regarding xnee: FTBFS: xnee_fake.c:809:15: error: implicit declaration of
function ‘xnee_check_key’; did you mean ‘xnee_check_true’?
[-Werror=implicit-function-declaration]
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.)
--
1066278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xnee
Version: 3.19-9.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../include -g -DUSE_VERBOSE
> -DNO_BUF_VERBOSE -DHAVE_XOSD -DXNEE_XINPUT_SUPPORT -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c -o xnee_fake.lo xnee_fake.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -I../include -g -DUSE_VERBOSE -DNO_BUF_VERBOSE
> -DHAVE_XOSD -DXNEE_XINPUT_SUPPORT -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c xnee_fake.c -fPIC -DPIC -o
> .libs/xnee_fake.o
> In file included from ../include/libxnee/print.h:24,
> from xnee_fake.c:28:
> xnee_fake.c: In function ‘xnee_fake_motion_event_impl’:
> xnee_fake.c:675:25: warning: cast from pointer to integer of different size
> [-Wpointer-to-int-cast]
> 675 | (int) xd->fake,
> | ^
> ../include/libxnee/print_varargs.h:55:39: note: in definition of macro
> ‘xnee_verbose’
>55 | #define xnee_verbose(a) xnee_verbosef a
> | ^
> xnee_fake.c:676:25: warning: cast from pointer to integer of different size
> [-Wpointer-to-int-cast]
> 676 | (int) xdevice,
> | ^
> ../include/libxnee/print_varargs.h:55:39: note: in definition of macro
> ‘xnee_verbose’
>55 | #define xnee_verbose(a) xnee_verbosef a
> | ^
> xnee_fake.c: In function ‘xnee_type_file’:
> xnee_fake.c:804:25: warning: format ‘%d’ expects argument of type ‘int’, but
> argument 3 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
> 804 | xnee_verbose ((xd," xnee_type_file loop read size="
> SIZE_T_PRINTF_FMT " \"%s\"\n",
> | ^~
> 805 | strlen(tmp),tmp));
> | ~~~
> | |
> | size_t {aka long unsigned int}
> ../include/libxnee/print_varargs.h:55:39: note: in definition of macro
> ‘xnee_verbose’
>55 | #define xnee_verbose(a) xnee_verbosef a
> | ^
> xnee_fake.c:809:15: error: implicit declaration of function ‘xnee_check_key’;
> did you mean ‘xnee_check_true’? [-Werror=implicit-function-declaration]
> 809 | if (xnee_check_key (xd)==XNEE_GRAB_DATA)
> | ^~
> | xnee_check_true
> xnee_fake.c:811:22: error: implicit declaration of function
> ‘xnee_handle_rec_key’; did you mean ‘xnee_handle_meta_data’?
> [-Werror=implicit-function-declaration]
> 811 | mode = xnee_handle_rec_key(xd);
> | ^~~
> | xnee_handle_meta_data
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:634: xnee_fake.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/xnee_3.19-9.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current
Processed: Re: transition: jpeg-xl
Processing control commands: > block -1 by 1061627 Bug #1053866 [release.debian.org] transition: jpeg-xl 1053866 was not blocked by any bugs. 1053866 was not blocking any bugs. Added blocking bug(s) of 1053866: 1061627 -- 1053866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070446: rocm-hipamd: arm64 FTBFS with glibc 2.38
Tags: patch Hi Graham, On 2024-05-05 07:31, Graham Inggs wrote: As can be seen in reproducible builds [1], rocm-hipamd FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider it a bug in glibc. There is nothing that can be done in rocm-hipamd to address this bug, aside from removing arm64 from the rocm-hipamd architecture list. The incompatibility is not with the HIP runtime, but with the HIP language. This is a disagreement that glibc and llvm will need to resolve between themselves. [1]https://tests.reproducible-builds.org/debian/rb-pkg/rocm-hipamd.html [2]https://sourceware.org/bugzilla/show_bug.cgi?id=30909 In file included from /tmp/hip_pch.724714/hip_pch.h:1: In file included from /build/reproducible-path/rocm-hipamd-5.7.1/hip/include/hip/hip_runtime.h:62: In file included from /build/reproducible-path/rocm-hipamd-5.7.1/hipamd/include/hip/amd_detail/amd_hip_runtime.h:76: In file included from /usr/lib/gcc/aarch64-linux-gnu/13/../../../../include/c++/13/cmath:47: In file included from /usr/include/math.h:40: /usr/include/aarch64-linux-gnu/bits/math-vector.h:40:9: error: unknown type name '__SVFloat32_t' 40 | typedef __SVFloat32_t __sv_f32_t; | ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:41:9: error: unknown type name '__SVFloat64_t' 41 | typedef __SVFloat64_t __sv_f64_t; | ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:42:9: error: unknown type name '__SVBool_t' 42 | typedef __SVBool_t __sv_bool_t; | ^ This compilation error is when building device code when the host architecture is aarch64. LLVM only defines __SVFloat32_t, __SVFloat64_t and __SVBool_t when building host code, but not when building device code. To me this seems reasonable because GPUs do not support SVE instructions. However, the math.h header (on aarch64 at least) is not aware of the concept of the distinction between host code and device code. As such, it fails when compiling device code. The glibc argument is that GCC always supports these types, but I'm not convinced. I'm curious how GCC handles the math headers for OpenMP GPU offloading [3]. In any case, I've attached a patch for glibc that would fix this bug. Perhaps my suggestion would be more palatable to upstream than the previously rejected patch. If not, it's up to glibc or LLVM to find a solution. If they cannot, then we will have to drop arm64 support for the HIP language. Sincerely, Cory Bloor [3]: https://gcc.gnu.org/wiki/Offloading From: Cordell Bloor Date: Wed, 10 Apr 2024 16:49:24 -0600 Subject: [PATCH] arm64/math-vec.h: drop SVE vector types in device code These headers get included when building HIP libraries on the aarch64 platform. The headers are used when building both CPU code and GPU code, but the SVE vector types are not supported on the GPU. The clang compiler sets __HIP_DEVICE_COMPILE__ when it is building code for the GPU, so disable __SVE_VEC_MATH_SUPPORTED when that macro is detected. Bug-Debian: https://bugs.debian.org/1070446 Bug-Ubuntu: https://bugs.launchpad.net/glibc/+bug/2032624 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30909 Forwarded: No Index: glibc/sysdeps/aarch64/fpu/bits/math-vector.h === --- glibc.orig/sysdeps/aarch64/fpu/bits/math-vector.h +++ glibc/sysdeps/aarch64/fpu/bits/math-vector.h @@ -101,7 +101,8 @@ typedef __attribute__ ((__neon_vector_ty typedef __attribute__ ((__neon_vector_type__ (2))) double __f64x2_t; #endif -#if __GNUC_PREREQ(10, 0) || __glibc_clang_prereq(11, 0) +#if (__GNUC_PREREQ(10, 0) || __glibc_clang_prereq(11, 0)) \ + && !defined(__HIP_DEVICE_COMPILE__) # define __SVE_VEC_MATH_SUPPORTED typedef __SVFloat32_t __sv_f32_t; typedef __SVFloat64_t __sv_f64_t;
Bug#1070387: marked as done (gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391)
Your message dated Sun, 05 May 2024 20:42:20 + with message-id and subject line Bug#1070387: fixed in gdcm 3.0.24-1 has caused the Debian Bug report #1070387, regarding gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391 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.) -- 1070387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdcm X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for gdcm. These are fixed in 3.0.24: CVE-2024-25569[0]: | An out-of-bounds read vulnerability exists in the | RAWCodec::DecodeBytes functionality of Mathieu Malaterre Grassroot | DICOM 3.0.23. A specially crafted DICOM file can lead to an out-of- | bounds read. An attacker can provide a malicious file to trigger | this vulnerability. https://talosintelligence.com/vulnerability_reports/TALOS-2024-1944 CVE-2024-22373[1]: | An out-of-bounds write vulnerability exists in the | JPEG2000Codec::DecodeByStreamsCommon functionality of Mathieu | Malaterre Grassroot DICOM 3.0.23. A specially crafted DICOM file can | lead to a heap buffer overflow. An attacker can provide a malicious | file to trigger this vulnerability. https://talosintelligence.com/vulnerability_reports/TALOS-2024-1935 CVE-2024-22391[2]: | A heap-based buffer overflow vulnerability exists in the | LookupTable::SetLUT functionality of Mathieu Malaterre Grassroot | DICOM 3.0.23. A specially crafted malformed file can lead to memory | corruption. An attacker can provide a malicious file to trigger this | vulnerability. https://talosintelligence.com/vulnerability_reports/TALOS-2024-1924 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-2024-25569 https://www.cve.org/CVERecord?id=CVE-2024-25569 [1] https://security-tracker.debian.org/tracker/CVE-2024-22373 https://www.cve.org/CVERecord?id=CVE-2024-22373 [2] https://security-tracker.debian.org/tracker/CVE-2024-22391 https://www.cve.org/CVERecord?id=CVE-2024-22391 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: gdcm Source-Version: 3.0.24-1 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of gdcm, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated gdcm 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, 05 May 2024 16:45:36 +0200 Source: gdcm Architecture: source Version: 3.0.24-1 Distribution: unstable Urgency: high Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1070387 Changes: gdcm (3.0.24-1) unstable; urgency=high . * Team upload. * d/watch: fix scan broken by github release page changes. This switches to git mode, to stabilise to ls-remote "API". * New upstream version 3.0.24 This version addresses CVE-2024-22373, CVE-2024-22391 and CVE-2024-25569. Closes: #1070387 * 02_fixhurd.patch: unfuzz. * Deleted 6631a74c39145b71dedcbe07c43bd6b1631b100d.patch. It is applied upstream. * d/control: declare compliance to standards version 4.7.0. * d/libgdcm-tools.lintian-overrides: refresh mismatched override. * d/libvtkgdcm-9.1t64.lintian-overrides: update mismatched override. * d/libgdcm3.0t64.lintian-overrides: remove mismatched override. * d/copyright: remove superfluous file patterns. * d/watch: single out tag v3.1.0 upstream. Checksums-Sha1: 62c45338fc8721d107e052b0fe1ea6980195759a 3726 gdcm_3.0.24-1.dsc e66cd70d0dc8f813f8dc1d90e23ebeab6aa81cd7 2613432 gdcm_3.0.24.orig.tar.xz 21eae7cdac92769eb2203a0e96d228c5e1492c18 278280 gdcm_3.0.24-1.debian.tar.xz Checksums-Sha256: 158cd0312d82dd99a7dc6aa6487d8448942d80ce8d19ff1c5a647fcd73177dfe 3726 gdcm_3.0.24-1.dsc
Processed: Re: [Debian-med-packaging] Bug#1070387: gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391
Processing control commands: > found -1 3.0.21-1 Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391 Marked as found in versions gdcm/3.0.21-1. > found -1 3.0.8-2 Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391 Marked as found in versions gdcm/3.0.8-2. > fixed -1 3.0.24-1 Bug #1070387 [src:gdcm] gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391 The source 'gdcm' and version '3.0.24-1' do not appear to match any binary packages Marked as fixed in versions gdcm/3.0.24-1. -- 1070387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070387: [Debian-med-packaging] Bug#1070387: gdcm: CVE-2024-25569 CVE-2024-22373 CVE-2024-22391
Control: found -1 3.0.21-1 Control: found -1 3.0.8-2 Control: fixed -1 3.0.24-1 Hi Moritz, Thanks for the tracking and the triaging of these issues! Moritz Mühlenhoff, on 2024-05-04: > Please adjust the affected versions in the BTS as needed. Done with the present email; an upload of 3.0.24-1 is on the way in unstable. I'm afraid I'm not sure how to test those vulnerabilities, but mitigations brought by Mathieu apply with no fuzz, or just a little, to gdcm in stable and oldstable (and possibly oldoldstable), so I'm inclined to assume they are affected. Hi Mathieu, don't hesitate to chime in if you have some insights on applying the mitigations on older versions. I'm still running extensive tests at the moment against (build) reverse dependencies, but there were no issues directly induced by the newer gdcm version so far. I'm considering liaising with Stable Release Managers to get gdcm fixed there too in upcoming point releases, if that helps. Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `-on air: Alta Forma - Apocalyptus signature.asc Description: PGP signature
Bug#1070455: ayatana-indicator-display: FTBFS: Errors while running CTest
Control: forwarded -1
https://github.com/AyatanaIndicators/ayatana-indicator-display/pull/96
Hi Santiago,
On So 05 Mai 2024 18:50:27 CEST, Santiago Vila wrote:
Package: src:ayatana-indicator-display
Version: 24.1.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DENABLE_TESTS=ON -DENABLE_COVERAGE=OFF
-DENABLE_LOMIRI_FEATURES=ON -DENABLE_COLOR_TEMP=ON
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DFETCHCONTENT_FULLY_DISCONNECTED=ON
-DCMAKE_INSTALL_RUNSTATEDIR=/run
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DENABLE_TESTS=ON
-DENABLE_COVERAGE=OFF -DENABLE_LOMIRI_FEATURES=ON
-DENABLE_COLOR_TEMP=ON ..
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
[... snipped ...]
2: member -> 'AddMatch'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body:
("type='signal',sender='org.freedesktop.Accounts',interface='org.freedesktop.DBus.Properties',member='PropertiesChanged',path='/org/freedesktop/Accounts/User924',arg0='org.freedesktop.DBus.Properties'",)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: RECEIVED D-Bus message (169 bytes)
2: Type:signal
2: Flags: no-reply-expected
2: Version: 0
2: Serial: 2
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'NameAcquired'
2: destination -> ':1.0'
2: sender -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body: (':1.0',)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Signal:
2: RECEIVED SIGNAL org.freedesktop.DBus.NameAcquired
2: on object /org/freedesktop/DBus
2: sent by name org.freedesktop.DBus
2:
2: GDBus-debug:Message:
2: SENT D-Bus message (281 bytes)
2: Type:method-call
2: Flags: none
2: Version: 0
2: Serial: 3
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'AddMatch'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body:
("type='signal',sender='org.freedesktop.Accounts',interface='org.freedesktop.DBus.Properties',path='/org/freedesktop/Accounts/User924'",)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: SENT D-Bus message (312 bytes)
2: Type:method-call
2: Flags: none
2: Version: 0
2: Serial: 4
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'AddMatch'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body:
("type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0='org.freedesktop.Accounts'",)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: RECEIVED D-Bus message (72 bytes)
2: Type:method-return
2: Flags: no-reply-expected
2: Version: 0
2: Serial: 3
2: Headers:
2: reply-serial -> uint32 2
2: destination -> ':1.0'
2: sender -> 'org.freedesktop.DBus'
2: Body: ()
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: SENT D-Bus message (188 bytes)
2: Type:method-call
2: Flags: none
2: Version: 0
2: Serial: 5
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'StartServiceByName'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 'su'
2: Body: ('org.freedesktop.Accounts', uint32 0)
2: UNIX File Descriptors:
2: (none)
2:
Bug#1070457: dino-im: FTBFS: error: ‘struct _gpgme_key’ has no member named ‘subkeys_length1’
I found this bug at upstream project: Dino 0.4.3 fails to compile after Vala-c update to 0.56.17 https://github.com/dino/dino/issues/1576 -- Stefan
Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)
Your message dated Sun, 05 May 2024 19:18:13 + with message-id and subject line Bug#1068938: fixed in less 551-2+deb11u2 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths 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.) -- 1068938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2024-32487[0]: | less through 653 allows OS command execution via a newline character | in the name of a file, because quoting is mishandled in filename.c. | Exploitation typically requires use with attacker-controlled file | names, such as the files extracted from an untrusted archive. | Exploitation also requires the LESSOPEN environment variable, but | this is set by default in many common cases. 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-2024-32487 https://www.cve.org/CVERecord?id=CVE-2024-32487 [1] https://www.openwall.com/lists/oss-security/2024/04/12/5 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 551-2+deb11u2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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 May 2024 20:29:26 +0200 Source: less Architecture: source Version: 551-2+deb11u2 Distribution: bullseye-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 1069681 Changes: less (551-2+deb11u2) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. . [ Milan Kupcevic ] * Fix incorrect display when filename contains control chars (Closes: #1069681) . less (551-2+deb11u1) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: 284666aff7d0a3e0719eb2675eb7fc8db39a5520 1968 less_551-2+deb11u2.dsc 70af3c8dfa2c3611b16691acaaead33d6ca5e885 20696 less_551-2+deb11u2.debian.tar.xz Checksums-Sha256: 19f72b42c4f99c402d30c52bb0fc10b0084ff69f50e7482fb64091a75065fdd1 1968 less_551-2+deb11u2.dsc d1679210766e0cd7280411d1d55138633076fb47af5fadb58e1341fedef834ec 20696 less_551-2+deb11u2.debian.tar.xz Files: 57c11d84044eb3e10a896a02e94129f5 1968 text important less_551-2+deb11u2.dsc 20d9522502289f5ed6706604ec0e020f 20696 text important less_551-2+deb11u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYz285fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ez1QP/je0Iu60GbbZypElGvy3S618tU94Ishy vkawxYkAKCUEdZ4ACPbKZyJ5DLJJk0Rs+Bmi2SUqUAWRLo9fsBnxLDTFU3xFfaW2 UJOtT0CJdJb6VNIDJLjGg7Gh4d0oKL1eff/+DJziJQVfH4X6hDzJm4mcYqvDiXU4 PJFZs0GQL77gYu3GasXOI0qcHpZ2lZIBeuAJapQTkwPvBQ5v9k5xGgWXxgUgjAs6 kD947R42wYPUdJe2tZDwR3xyRaVCtY42hIIS3jV7+pkyOiLxpSAYXO+Yi17Drpq9 gt3nzjRl8exA7vXbeQFw5j4IPf/FI5/KZ8VRX3TDhVaUbSf8SyAGrFCbDTHcDPd1 KABTJcMIIXOY0uwHx03QEvBPwMaqs7QwytDYL/4iQcTndigoZzv7bL5zIUJs6BsL VM+WayVfRqIdX3rkUaOI9hhFziOH73mIn9qeV6PTwjSGBe3SnT5+T6e4PR5A25Zi yzfpvvm5JWP2/cATYgQP7BfkZLrMFR0AXITnc1AOZWeufA1DyNnRRijfDhDBSu1V /juuaAo9aWZl+tZtMqNbYTPQ3ZXaVy4riRqnm3reX+Eyn26wGjUgEunElBM64ctk
Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)
Your message dated Sun, 05 May 2024 19:18:09 + with message-id and subject line Bug#1068938: fixed in less 551-2+deb11u1 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths 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.) -- 1068938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2024-32487[0]: | less through 653 allows OS command execution via a newline character | in the name of a file, because quoting is mishandled in filename.c. | Exploitation typically requires use with attacker-controlled file | names, such as the files extracted from an untrusted archive. | Exploitation also requires the LESSOPEN environment variable, but | this is set by default in many common cases. 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-2024-32487 https://www.cve.org/CVERecord?id=CVE-2024-32487 [1] https://www.openwall.com/lists/oss-security/2024/04/12/5 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 551-2+deb11u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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: Fri, 19 Apr 2024 21:37:35 +0200 Source: less Architecture: source Version: 551-2+deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 Changes: less (551-2+deb11u1) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: 04e598880c888e5706eb9dea18268fbaaabc6ca5 1968 less_551-2+deb11u1.dsc 7a2dbccd46697ba17189b1e19f75eee5115c19a2 347007 less_551.orig.tar.gz 6ed143fe69989f24a9585805fe744f083695f989 19904 less_551-2+deb11u1.debian.tar.xz Checksums-Sha256: 6a718a7318c6cecab36041ad1c4530ae69f587b0a81a9fe32cc2c3f2d7e15508 1968 less_551-2+deb11u1.dsc ff165275859381a63f19135a8f1f6c5a194d53ec3187f94121ecd8ef0795fe3d 347007 less_551.orig.tar.gz 3566c26aae5116cffa32367684f4ab3dd12d1ed0a61d8b6cc6cf3f5f8812eae9 19904 less_551-2+deb11u1.debian.tar.xz Files: 79a23b31100af8999f52630778a72878 1968 text important less_551-2+deb11u1.dsc 4ad4408b06d7a6626a055cb453f36819 347007 text important less_551.orig.tar.gz ca4fb7b6ad73983f7318c1fd11d77c2f 19904 text important less_551-2+deb11u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYiyTBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ew1kP/jkiPYkaOXyrkKr5vNAIdCQ48vVEduZO wL3bBOOQm0bqB4fpdC1NG4VsWlY15rFzuwBG56ZDzQPmV6BQb5lbwjMApxR3LJ10 zixjczhyoaJxqmXKBFcQw+/fJLTSdFSghvCRFFMuBU5pSJu56uHjlgpN0txSJ+1U ikD09oFhqAdrGxkLWW/nb2o3qRKbf8/KMOH9nKmLKPzp4GNAy0t3u3MIUA+uTxhT XouJxctxBugt0hju8ZTUjkoE0GaXdvXJvI/lLbuO15QnsuvXkrTEcEZYg/dzk5gp C9dr44d9GjdHAxy6QJpY+7UhEO8y1kgLy7IzH/9nJ01j6x0PDqO0GESocyCX/pER ITKrkpFSxhI/U/pbsYGDfvZgj4fBhWjxCPVfbzF7za9PGwFl3EWuMhztiwltJhki JYpgiTJRUN4qf9r5EcmWtUxJaHNebjmFv53ADtev0QZiyNYxEH5A+cBEsOuTRcKc onS1dLQ430m4G7vLARi95BVYKAbGBDrjWiEMSuoFdqZCTtXtXbR1IdqDUcA3mGlm 3nW+H2Nel5cKUPRquZIAxO9TBpzHVmCrpjbTMzYF8j/3UxSyf5pmqatlKDMOkZTb
Bug#1068412: marked as done (apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709)
Your message dated Sun, 05 May 2024 19:17:41 + with message-id and subject line Bug#1068412: fixed in apache2 2.4.59-1~deb11u1 has caused the Debian Bug report #1068412, regarding apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709 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.) -- 1068412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apache2 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for apache2. CVE-2024-27316[0]: https://www.kb.cert.org/vuls/id/421644 https://www.openwall.com/lists/oss-security/2024/04/04/4 CVE-2024-24795[1]: https://www.openwall.com/lists/oss-security/2024/04/04/5 CVE-2023-38709[2]: https://www.openwall.com/lists/oss-security/2024/04/04/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-2024-27316 https://www.cve.org/CVERecord?id=CVE-2024-27316 [1] https://security-tracker.debian.org/tracker/CVE-2024-24795 https://www.cve.org/CVERecord?id=CVE-2024-24795 [2] https://security-tracker.debian.org/tracker/CVE-2023-38709 https://www.cve.org/CVERecord?id=CVE-2023-38709 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.59-1~deb11u1 Done: Yadd We believe that the bug you reported is fixed in the latest version of apache2, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated apache2 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: Fri, 05 Apr 2024 16:08:04 +0400 Source: apache2 Binary: apache2 apache2-bin apache2-bin-dbgsym apache2-data apache2-dev apache2-doc apache2-ssl-dev apache2-suexec-custom apache2-suexec-custom-dbgsym apache2-suexec-pristine apache2-suexec-pristine-dbgsym apache2-utils apache2-utils-dbgsym libapache2-mod-md libapache2-mod-proxy-uwsgi Architecture: source amd64 all Version: 2.4.59-1~deb11u1 Distribution: bullseye-security Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Yadd Description: apache2- Apache HTTP Server apache2-bin - Apache HTTP Server (modules and other binary files) apache2-data - Apache HTTP Server (common files) apache2-dev - Apache HTTP Server (development headers) apache2-doc - Apache HTTP Server (on-site documentation) apache2-ssl-dev - Apache HTTP Server (mod_ssl development headers) apache2-suexec-custom - Apache HTTP Server configurable suexec program for mod_suexec apache2-suexec-pristine - Apache HTTP Server standard suexec program for mod_suexec apache2-utils - Apache HTTP Server (utility programs for web servers) libapache2-mod-md - transitional package libapache2-mod-proxy-uwsgi - transitional package Closes: 1068412 Changes: apache2 (2.4.59-1~deb11u1) bullseye-security; urgency=medium . * New upstream version 2.4.58 (Closes: CVE-2023-31122, CVE-2023-43622, CVE-2023-45802) * Drop 2.4.56-regression patches * New upstream version 2.4.59 (Closes: #1068412 CVE-2024-27316 CVE-2024-24795 CVE-2023-38709) * Install NOTICE files * Update test framework * Refresh patches Checksums-Sha1: b0c553ee2f9076ab255d36f6f77a4155e8f5180d 3539 apache2_2.4.59-1~deb11u1.dsc 7a118baaed0f2131e482f93f5057038ca6c021be 9843252 apache2_2.4.59.orig.tar.gz 837cdf46898d962c4c05642745566249fc91e52b 833 apache2_2.4.59.orig.tar.gz.asc 8d3d9c0ec949faa3683bc395b0955584347323a6 895172 apache2_2.4.59-1~deb11u1.debian.tar.xz 651b4de4722fb3cf7331e0df7147738b7015bf89 3308712 apache2-bin-dbgsym_2.4.59-1~deb11u1_amd64.deb 46176b8ad83ca0e991d575f498d67871b2c2e1d6 1447660 apache2-bin_2.4.59-1~deb11u1_amd64.deb 2cd7eef5039ed029710efc9edb1c8b8d3822381b 160212 apache2-data_2.4.59-1~deb11u1_all.deb 7ae879f3f9fd07d0b0faff14e40af9d955e11a3d 374820 apache2-dev_2.4.59-1~deb11u1_amd64.deb
Bug#1064293: marked as done (less: CVE-2022-48624)
Your message dated Sun, 05 May 2024 19:18:13 + with message-id and subject line Bug#1064293: fixed in less 551-2+deb11u2 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 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.) -- 1064293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2022-48624[0]: | close_altfile in filename.c in less before 606 omits shell_quote | calls for LESSCLOSE. 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-2022-48624 https://www.cve.org/CVERecord?id=CVE-2022-48624 [1] https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 551-2+deb11u2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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 May 2024 20:29:26 +0200 Source: less Architecture: source Version: 551-2+deb11u2 Distribution: bullseye-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 1069681 Changes: less (551-2+deb11u2) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. . [ Milan Kupcevic ] * Fix incorrect display when filename contains control chars (Closes: #1069681) . less (551-2+deb11u1) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: 284666aff7d0a3e0719eb2675eb7fc8db39a5520 1968 less_551-2+deb11u2.dsc 70af3c8dfa2c3611b16691acaaead33d6ca5e885 20696 less_551-2+deb11u2.debian.tar.xz Checksums-Sha256: 19f72b42c4f99c402d30c52bb0fc10b0084ff69f50e7482fb64091a75065fdd1 1968 less_551-2+deb11u2.dsc d1679210766e0cd7280411d1d55138633076fb47af5fadb58e1341fedef834ec 20696 less_551-2+deb11u2.debian.tar.xz Files: 57c11d84044eb3e10a896a02e94129f5 1968 text important less_551-2+deb11u2.dsc 20d9522502289f5ed6706604ec0e020f 20696 text important less_551-2+deb11u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYz285fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ez1QP/je0Iu60GbbZypElGvy3S618tU94Ishy vkawxYkAKCUEdZ4ACPbKZyJ5DLJJk0Rs+Bmi2SUqUAWRLo9fsBnxLDTFU3xFfaW2 UJOtT0CJdJb6VNIDJLjGg7Gh4d0oKL1eff/+DJziJQVfH4X6hDzJm4mcYqvDiXU4 PJFZs0GQL77gYu3GasXOI0qcHpZ2lZIBeuAJapQTkwPvBQ5v9k5xGgWXxgUgjAs6 kD947R42wYPUdJe2tZDwR3xyRaVCtY42hIIS3jV7+pkyOiLxpSAYXO+Yi17Drpq9 gt3nzjRl8exA7vXbeQFw5j4IPf/FI5/KZ8VRX3TDhVaUbSf8SyAGrFCbDTHcDPd1 KABTJcMIIXOY0uwHx03QEvBPwMaqs7QwytDYL/4iQcTndigoZzv7bL5zIUJs6BsL VM+WayVfRqIdX3rkUaOI9hhFziOH73mIn9qeV6PTwjSGBe3SnT5+T6e4PR5A25Zi yzfpvvm5JWP2/cATYgQP7BfkZLrMFR0AXITnc1AOZWeufA1DyNnRRijfDhDBSu1V /juuaAo9aWZl+tZtMqNbYTPQ3ZXaVy4riRqnm3reX+Eyn26wGjUgEunElBM64ctk kDmLyUviiBcP5wfWbBmwUTehIwbAlQCgqVim0skUfYYbz5VSDwCWXLdU1R35P9Dg Zzzr6rpPA2RZ =QMuU -END PGP SIGNATURE- pgppdAT1GCl4v.pgp Description: PGP signature --- End Message ---
Bug#1064989: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078)
Your message dated Sun, 05 May 2024 19:18:20 + with message-id and subject line Bug#1064989: fixed in nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 has caused the Debian Bug report #1064989, regarding nvidia-graphics-drivers-tesla-470: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078 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.) -- 1064989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078 Control: tag -5 + wontfix Control: close -5 450.248.02-4 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2024-0074, CVE-2022-42265, CVE-2024-0078 Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2024-0074, CVE-2024-0075, CVE-2024-0078 Control: found -8 515.48.07-1 Control: found -8 525.60.13-1 Control: tag -8 + wontfix Control: close -8 525.147.05-6 Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2024-0074, CVE-2024-0075, CVE-2024-0078 Control: found -9 520.56.06-1 Control: found -9 525.85.12-1 Control: found -9 530.30.02-1 Control: found -9 535.43.02-1 Control: found -9 545.23.06-1 Control: found -9 550.40.07-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: found -1 535.43.02-1 Control: found -1 545.23.06-1 Control: found -1 550.40.07-1 Control: fixed -7 470.239.06-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5520 CVE-2024-0074 NVIDIA GPU Display Driver for Linux contains a vulnerability where an attacker may access a memory location after the end of the buffer. A successful exploit of this vulnerability may lead to denial of service and data tampering. CVE-2024-0075 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability where a user may cause a NULL-pointer dereference by accessing passed parameters the validity of which has not been checked. A successful exploit of this vulnerability may lead to denial of service and limited information disclosure. CVE-2024-0078 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a user in a guest can cause a NULL-pointer dereference in the host, which may lead to denial of service. CVE-2022-42265 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause integer overflow, which may lead to denial of service, information disclosure, and data tampering. Linux Driver Branch CVE IDs Addressed R550, R545, R535CVE-2024-0074, CVE-2024-0075 R470CVE-2024-0074, CVE-2022-42265 Driver Branch Affected Driver VersionsUpdated Driver Version R550All driver versions prior to 550.54.14 550.54.14 R535All driver versions prior to 535.161.07 535.161.07 R470All driver versions prior to 470.239.06 470.239.06 R470All driver versions prior to 470.223.02 470.223.02
Bug#1064293: marked as done (less: CVE-2022-48624)
Your message dated Sun, 05 May 2024 19:18:09 + with message-id and subject line Bug#1064293: fixed in less 551-2+deb11u1 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 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.) -- 1064293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2022-48624[0]: | close_altfile in filename.c in less before 606 omits shell_quote | calls for LESSCLOSE. 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-2022-48624 https://www.cve.org/CVERecord?id=CVE-2022-48624 [1] https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 551-2+deb11u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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: Fri, 19 Apr 2024 21:37:35 +0200 Source: less Architecture: source Version: 551-2+deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 Changes: less (551-2+deb11u1) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: 04e598880c888e5706eb9dea18268fbaaabc6ca5 1968 less_551-2+deb11u1.dsc 7a2dbccd46697ba17189b1e19f75eee5115c19a2 347007 less_551.orig.tar.gz 6ed143fe69989f24a9585805fe744f083695f989 19904 less_551-2+deb11u1.debian.tar.xz Checksums-Sha256: 6a718a7318c6cecab36041ad1c4530ae69f587b0a81a9fe32cc2c3f2d7e15508 1968 less_551-2+deb11u1.dsc ff165275859381a63f19135a8f1f6c5a194d53ec3187f94121ecd8ef0795fe3d 347007 less_551.orig.tar.gz 3566c26aae5116cffa32367684f4ab3dd12d1ed0a61d8b6cc6cf3f5f8812eae9 19904 less_551-2+deb11u1.debian.tar.xz Files: 79a23b31100af8999f52630778a72878 1968 text important less_551-2+deb11u1.dsc 4ad4408b06d7a6626a055cb453f36819 347007 text important less_551.orig.tar.gz ca4fb7b6ad73983f7318c1fd11d77c2f 19904 text important less_551-2+deb11u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYiyTBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ew1kP/jkiPYkaOXyrkKr5vNAIdCQ48vVEduZO wL3bBOOQm0bqB4fpdC1NG4VsWlY15rFzuwBG56ZDzQPmV6BQb5lbwjMApxR3LJ10 zixjczhyoaJxqmXKBFcQw+/fJLTSdFSghvCRFFMuBU5pSJu56uHjlgpN0txSJ+1U ikD09oFhqAdrGxkLWW/nb2o3qRKbf8/KMOH9nKmLKPzp4GNAy0t3u3MIUA+uTxhT XouJxctxBugt0hju8ZTUjkoE0GaXdvXJvI/lLbuO15QnsuvXkrTEcEZYg/dzk5gp C9dr44d9GjdHAxy6QJpY+7UhEO8y1kgLy7IzH/9nJ01j6x0PDqO0GESocyCX/pER ITKrkpFSxhI/U/pbsYGDfvZgj4fBhWjxCPVfbzF7za9PGwFl3EWuMhztiwltJhki JYpgiTJRUN4qf9r5EcmWtUxJaHNebjmFv53ADtev0QZiyNYxEH5A+cBEsOuTRcKc onS1dLQ430m4G7vLARi95BVYKAbGBDrjWiEMSuoFdqZCTtXtXbR1IdqDUcA3mGlm 3nW+H2Nel5cKUPRquZIAxO9TBpzHVmCrpjbTMzYF8j/3UxSyf5pmqatlKDMOkZTb XEWWUbg3z3PR6ENX8TK7PSudhS1eFwl1BCWX3XPVtdXPtA7JYT2KlDQxw4rkqB2E az50ivdbFVgm =d1zP -END PGP SIGNATURE- pgpL1pNXonQLr.pgp Description: PGP signature --- End Message ---
Bug#1063706: marked as done (linux-image-6.1.0-18-amd64: nvidia-tesla-470 doesn't build in 6.1.0-18 kernel)
Your message dated Sun, 05 May 2024 19:18:20 + with message-id and subject line Bug#1063361: fixed in nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 has caused the Debian Bug report #1063361, regarding linux-image-6.1.0-18-amd64: nvidia-tesla-470 doesn't build in 6.1.0-18 kernel 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.) -- 1063361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: normal Tags: ftbfs Dear Maintainer, nvidia-tesla-470 module doesn't build in 6.1.0-18 kernel. # apt upgrade ... Building module: Cleaning build area... env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=6.1.0-18-amd64(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult /var/lib/dkms/nvidia-tesla-470/470.223.02/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-18-amd64 failed! ... E: Sub-process /usr/bin/dpkg returned an error code (1) -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Micro-Star International Co., Ltd. product_name: MS-7C51 product_version: 1.0 chassis_vendor: Micro-Star International Co., Ltd. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: 1.30 board_vendor: Micro-Star International Co., Ltd. board_name: A320M-A PRO (MS-7C51) board_version: 1.0 ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Wani [Radeon R5/R6/R7 Graphics] [1462:7c51] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: amdgpu 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio [1002:9840] Subsystem: Micro-Star International Co., Ltd. [MSI] Kabini HDMI/DP Audio [1462:9c51] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge [1022:157b] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.5 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port [1022:157c] (prog-if 00 [Normal decode]) Subsystem: Micro-Star International Co., Ltd. [MSI] Family 15h (Models 60h-6fh) Processor Root Port [1462:7c51] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge [1022:157b] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use:
Bug#1063361: marked as done (nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux)
Your message dated Sun, 05 May 2024 19:18:20 + with message-id and subject line Bug#1063361: fixed in nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 has caused the Debian Bug report #1063361, regarding nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux 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.) -- 1063361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers-tesla-470 Version: 470.223.02-3 Severity: serious X-Debbugs-CC: li...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:linux Dear maintainer(s), With a recent upload of linux the autopkgtest of nvidia-graphics-drivers-tesla-470 fails in testing when that autopkgtest is run with the binary packages of linux from unstable. It passes when run with only packages from testing. In tabular form: passfail linux from testing6.6.15-2 nvidia-graphics-drivers-tesla-470 from testing470.223.02-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 linux to testing [1]. Of course, linux shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in linux was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from linux should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. 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=linux https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-graphics-drivers-tesla-470/42735534/log.gz 320s # MODPOST /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers 320sscripts/mod/modpost -M -m -o /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers -T /var/lib/dkms/nvidia-tesla-470/470.223.02/build/modules.order -i Module.symvers -e 320s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_unlock' 320s ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_lock' 320s make[4]: *** [/usr/src/linux-headers-6.6.15-common/scripts/Makefile.modpost:145: /var/lib/dkms/nvidia-tesla-470/470.223.02/build/Module.symvers] Error 1 OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-470 Source-Version: 470.239.06-1~deb11u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-470, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla-470 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 24 Apr 2024 05:18:12 +0200 Source: nvidia-graphics-drivers-tesla-470 Architecture: source Version: 470.239.06-1~deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1063361 1064983 1064989 Changes: nvidia-graphics-drivers-tesla-470 (470.239.06-1~deb11u1) bullseye; urgency=medium . * Rebuild for bullseye. . nvidia-graphics-drivers-tesla-470 (470.239.06-1~deb12u1) bookworm; urgency=medium . * Rebuild for bookworm. . nvidia-graphics-drivers-tesla-470 (470.239.06-1) unstable; urgency=medium . * New upstream long term support branch release 470.239.06 (2024-02-22). * Fixed CVE-2024-0074,
Processed: severity of 1064991 is serious
Processing commands for cont...@bugs.debian.org:
> severity 1064991 serious
Bug #1064991 {Done: Andreas Beckmann }
[src:nvidia-open-gpu-kernel-modules] nvidia-open-gpu-kernel-modules:
CVE-2024-0074, CVE-2024-0075, CVE-2024-0078
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1064991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068755: docker.io: FTBFS: failing tests
Turns out that backporting https://github.com/moby/moby/commit/97921915a801dd82b1f5a70e0a69353539c1e3ae.patch seems to actually make the test pass I'm not sure why that worked before, but I've pushed a backport of that patch to https://salsa.debian.org/go-team/packages/docker/-/commit/d33659365984dbb47b6aac2836727e507c1ce737 to let the salsa pipeline work on it. I plan to make a team-upload tomorrow or later in the week. Please let me know if you have concerns or thoughts on this. Thanks -rt On Sun, May 5, 2024 at 11:20 AM Reinhard Tartler wrote: > I've been looking at this test failure, but remain puzzled. > > Basically, the source for this test is here: > https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-2/engine/distribution/xfer/download_test.go/#L364-L429. > This test is testing code in > https://sources.debian.org/src/docker.io/20.10.25+dfsg1-2/engine/distribution/xfer/download.go > which has only two external dependencies > (golang-github-docker-distribution-dev) and > (golang-github-sirupsen-logrus-dev). > > I've checked the build log of the previous build at > https://buildd.debian.org/status/fetch.php?pkg=docker.io=amd64=20.10.25%2Bdfsg1-2%2Bb3=1704672923=0 > and note that the same test passes in that build. This also uses the same > package versions of golang-github-docker-distribution-dev==2.8.2+ds1-1 and > golang-github-sirupsen-logrus-dev==1.9.0-1 > > I also note that the old build was using golang 1.21, and the FTBFS was > introduced after upgrading unstable to golang 1.22. > > Shengjing, I believe you handled the recent update of the golang toolchain > from 1.21 to 1.22. Have you seen similar "mysterious" test failures that > resulted from using a newer golang compiler? > > I am considering just disabling this test, as the rest of the testsuite > seem to pass, but I'm getting nervous that this wouldn't just paper over a > real issue. > > Thanks, > > > -- > regards, > Reinhard > -- regards, Reinhard
Bug#1068755: marked as pending in docker.io
Control: tag -1 pending Hello, Bug #1068755 in docker.io reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/docker/-/commit/d33659365984dbb47b6aac2836727e507c1ce737 fix test TestMaxDownloadAttempts, closes: #1068755 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068755
Processed: Bug#1068755 marked as pending in docker.io
Processing control commands: > tag -1 pending Bug #1068755 [src:docker.io] docker.io: FTBFS: failing tests Added tag(s) pending. -- 1068755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064003: patch for c-t-b build
Control: tags -1 + patch
Hi Matthias,
I'm attaching a patch for the c-t-b FTBFS. Note that due to the
glibc/2.38 upload c-t-b has become completely uninstallable. Hence, a
timely upload is appreciated. Due to linux-libc-dev currently providing
the -$arch-cross packages, we have to remove the Build-Conflicts or make
rename the Provides on linux-libc-dev. I'm ok with both approaches and
offer dropping the conflict here.
Helmut
diff --minimal -Nru cross-toolchain-base-68/debian/changelog
cross-toolchain-base-68+nmu1/debian/changelog
--- cross-toolchain-base-68/debian/changelog2023-10-31 09:50:26.0
+0100
+++ cross-toolchain-base-68+nmu1/debian/changelog 2024-05-04
09:23:39.0 +0200
@@ -1,3 +1,12 @@
+cross-toolchain-base (68+nmu1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Build using linux 6.7. Closes: #1064003, #1067370.
+ * Build using glibc 2.38.
+ * Remove linux-libc-dev-ARCH-cross from GLIBC_BUILD_CONFLICTS.
+
+ -- Helmut Grohne Sat, 04 May 2024 09:23:39 +0200
+
cross-toolchain-base (68) unstable; urgency=medium
* Build using linux 6.5.8. Closes: #1042118.
diff --minimal -Nru cross-toolchain-base-68/debian/control
cross-toolchain-base-68+nmu1/debian/control
--- cross-toolchain-base-68/debian/control 2023-10-31 09:50:26.0
+0100
+++ cross-toolchain-base-68+nmu1/debian/control 2024-05-04 09:23:39.0
+0200
@@ -9,9 +9,9 @@
Build-Depends: binutils-multiarch,
dpkg (>= 1.21.17), rdfind, symlinks, lsb-release,
binutils-source (>= 2.41-6~),
- glibc-source (>= 2.37-3~),
+ glibc-source (>= 2.38),
gcc-12-source (>= 12.3.0-11~), g++-12 (>= 12.3.0-11~),
- linux-source-6.5 (>= 6.5.8), linux-libc-dev (>= 6.5.8),
+ linux-source-6.7 (>= 6.7.0), linux-libc-dev (>= 6.7.0),
autoconf (>= 2.69), autoconf2.69, autogen,
automake, bison (>= 1:2.3), chrpath, debhelper-compat (= 13),
dpkg-dev (>= 1.15.3.1), fakeroot, file, flex,
@@ -27,7 +27,7 @@
libjansson-dev, pkg-config,
Build-Conflicts: dpkg-cross, libdebian-dpkgcross-perl,
binutils-x86-64-linux-gnu [!amd64], binutils-i686-linux-gnu [!i386],
binutils-s390x-linux-gnu [!s390x], binutils-powerpc64le-linux-gnu [!ppc64el],
binutils-aarch64-linux-gnu [!arm64], binutils-arm-linux-gnueabihf [!armhf],
binutils-arm-linux-gnueabi [!armel], binutils-riscv64-linux-gnu [!riscv64],
- libc6-amd64-cross, linux-libc-dev-amd64-cross, libc6-i386-cross,
linux-libc-dev-i386-cross, libc6-s390x-cross, linux-libc-dev-s390x-cross,
libc6-ppc64el-cross, linux-libc-dev-ppc64el-cross, libc6-arm64-cross,
linux-libc-dev-arm64-cross, libc6-armhf-cross, linux-libc-dev-armhf-cross,
libc6-armel-cross, linux-libc-dev-armel-cross, libc6-riscv64-cross,
linux-libc-dev-riscv64-cross,
+ libc6-amd64-cross, libc6-i386-cross, libc6-s390x-cross, libc6-ppc64el-cross,
libc6-arm64-cross, libc6-armhf-cross, libc6-armel-cross, libc6-riscv64-cross,
libc6-amd64 [i386 x32], libc6-i386 [amd64 x32], libc6-x32 [amd64 i386]
Package: linux-libc-dev-amd64-cross
diff --minimal -Nru cross-toolchain-base-68/debian/rules
cross-toolchain-base-68+nmu1/debian/rules
--- cross-toolchain-base-68/debian/rules2023-10-31 09:50:26.0
+0100
+++ cross-toolchain-base-68+nmu1/debian/rules 2024-05-04 09:23:39.0
+0200
@@ -61,8 +61,8 @@
CROSS_GNU_TYPE = $(call _gnu_type,${CROSS_ARCH})
CROSS_PKG_GNU_TYPE = $(subst _,-,$(call _gnu_type,${CROSS_ARCH}))
-MIN_VER_GLIBC := 2.37-3~
-MIN_VER_LINUX := 6.5.8
+MIN_VER_GLIBC := 2.38
+MIN_VER_LINUX := 6.7.0
MIN_VER_GCC:= 12.3.0-11~
MIN_VER_BINUTILS := 2.41-6~
VER_GCC_BASE := 12
@@ -110,7 +110,7 @@
# FIXME: No conflict for the host == cross case ...
BINUTILS_BUILD_CONFLICTS = $(foreach a,$(CROSS_ARCHS),binutils-$(subst
_,-,$(call _gnu_type,$(a))) [!$(a)]$(,))
-GLIBC_BUILD_CONFLICTS = $(foreach a,$(CROSS_ARCHS),libc6-$(a)-cross$(,)
linux-libc-dev-$(a)-cross$(,))
+GLIBC_BUILD_CONFLICTS = $(foreach a,$(CROSS_ARCHS),libc6-$(a)-cross$(,))
# taken from gcc packaging
define unpack_tarball
Processed: patch for c-t-b build
Processing control commands: > tags -1 + patch Bug #1067370 [src:cross-toolchain-base] cross-toolchain-base: FTBFS: unsatisfiable build-dependencies Added tag(s) patch. -- 1067370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: patch for c-t-b build
Processing control commands: > tags -1 + patch Bug #1064003 [src:cross-toolchain-base] src:cross-toolchain-base: unsatisfied build dependency in testing: linux-source-6.5 (>= 6.5.8) Added tag(s) patch. -- 1064003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067016: nvidia-settings 470.239.06-1 flagged for acceptance
package release.debian.org tags 1067016 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-settings Version: 470.239.06-1 Explanation: new upstrem bugfix release; build for ppc64el
Bug#1064293: marked as done (less: CVE-2022-48624)
Your message dated Sun, 05 May 2024 18:48:09 + with message-id and subject line Bug#1064293: fixed in less 590-2.1~deb12u2 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 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.) -- 1064293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2022-48624[0]: | close_altfile in filename.c in less before 606 omits shell_quote | calls for LESSCLOSE. 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-2022-48624 https://www.cve.org/CVERecord?id=CVE-2022-48624 [1] https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 590-2.1~deb12u2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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 May 2024 20:30:51 +0200 Source: less Architecture: source Version: 590-2.1~deb12u2 Distribution: bookworm-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 1069681 Changes: less (590-2.1~deb12u2) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. . [ Milan Kupcevic ] * Fix incorrect display when filename contains control chars (Closes: #1069681) . less (590-2.1~deb12u1) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. * Rebuild for bookworm-security . less (590-2.1) unstable; urgency=medium . * Non-maintainer upload. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: 683da794f9203c803fa4690c9fc643e05e6b20df 2228 less_590-2.1~deb12u2.dsc 6a6d4f2cbe18bce3db8dc9f4337c2b35f32c76f4 23852 less_590-2.1~deb12u2.debian.tar.xz Checksums-Sha256: 1a4219f8ec9342851805089d9ee5ec7c0150287d5722ecc914c50790673ad9a6 2228 less_590-2.1~deb12u2.dsc 4a54c48a25cabb5408af6d7bc174cad96614e540b47d2b8962b3e13819fd9b30 23852 less_590-2.1~deb12u2.debian.tar.xz Files: 7dc4c944e5b41d3004e4eaa7be2c2134 2228 text important less_590-2.1~deb12u2.dsc 2d60b4f47bdb42a8e75be462aa417d1c 23852 text important less_590-2.1~deb12u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYz3JZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EWlIP/2noXgRJDkAvk7sxtArXPXg//lNiY/vu eb4KDvjfCqa3Vmnk/TRf1+tXfo3pUM6CHr0JQmZQL4LwSdp61C45KnQwRXX1HWdK RYqIoerrXp59TvXX65+oNPNh3DJlVbguOhvalg4g3+jc6K8CQAOZYVC2P4akpcbU 3/y2aEF+tdBgmq99H0uMo9KgY0pIQGaWcxYZQbf9LCOttw+iPGv+4uZxv/SKeuqg nsJBiZw5Zuy9AjlTuTHwTOIgS6xsk7L1RlJ9b0vv/UaQUN05Qo/6k3XM65j6WwC+ 3WGu3sIPo54ap26Pwjjf3dR19lGrZABh9IAdrgQlp0rm/pmI4G30+PVEy3dNInSL QqkcW8oUA239xs/XzXeKACMreTCFFx+NhKN0UeJuru1awVZXEWp0BHoFn9HDfS5p O+yPNFH4sT09JDAc2dFLzJRGOO+8TgRjJ01Ylcs2cCktNp4Tgzw1JzMHDAsJJEXg QNg6ekYvlmpsqokAamBlXQTyET7GC/ur6TYuGVX6H6Rq3YJ6v/aLiC2RRijB3AiQ vdt5tr3fRNAGKxiPfR6bEpSunYISjmgZPYRYcP+nsId8oMFsstfpJCRtGosyI/cj lOHZuBmgxyikxYbxX5LxzDlCUWR9r51k93F3z/oQesrZbMIvCkZ+8QqPe56q1mI1 0krKZsOhjiTM =Bqc3 -END PGP SIGNATURE- pgpmhaoFDo0O4.pgp Description: PGP signature --- End Message ---
Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)
Your message dated Sun, 05 May 2024 18:48:09 + with message-id and subject line Bug#1068938: fixed in less 590-2.1~deb12u2 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths 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.) -- 1068938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2024-32487[0]: | less through 653 allows OS command execution via a newline character | in the name of a file, because quoting is mishandled in filename.c. | Exploitation typically requires use with attacker-controlled file | names, such as the files extracted from an untrusted archive. | Exploitation also requires the LESSOPEN environment variable, but | this is set by default in many common cases. 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-2024-32487 https://www.cve.org/CVERecord?id=CVE-2024-32487 [1] https://www.openwall.com/lists/oss-security/2024/04/12/5 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 590-2.1~deb12u2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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 May 2024 20:30:51 +0200 Source: less Architecture: source Version: 590-2.1~deb12u2 Distribution: bookworm-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 1069681 Changes: less (590-2.1~deb12u2) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. . [ Milan Kupcevic ] * Fix incorrect display when filename contains control chars (Closes: #1069681) . less (590-2.1~deb12u1) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. * Rebuild for bookworm-security . less (590-2.1) unstable; urgency=medium . * Non-maintainer upload. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: 683da794f9203c803fa4690c9fc643e05e6b20df 2228 less_590-2.1~deb12u2.dsc 6a6d4f2cbe18bce3db8dc9f4337c2b35f32c76f4 23852 less_590-2.1~deb12u2.debian.tar.xz Checksums-Sha256: 1a4219f8ec9342851805089d9ee5ec7c0150287d5722ecc914c50790673ad9a6 2228 less_590-2.1~deb12u2.dsc 4a54c48a25cabb5408af6d7bc174cad96614e540b47d2b8962b3e13819fd9b30 23852 less_590-2.1~deb12u2.debian.tar.xz Files: 7dc4c944e5b41d3004e4eaa7be2c2134 2228 text important less_590-2.1~deb12u2.dsc 2d60b4f47bdb42a8e75be462aa417d1c 23852 text important less_590-2.1~deb12u2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYz3JZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EWlIP/2noXgRJDkAvk7sxtArXPXg//lNiY/vu eb4KDvjfCqa3Vmnk/TRf1+tXfo3pUM6CHr0JQmZQL4LwSdp61C45KnQwRXX1HWdK RYqIoerrXp59TvXX65+oNPNh3DJlVbguOhvalg4g3+jc6K8CQAOZYVC2P4akpcbU 3/y2aEF+tdBgmq99H0uMo9KgY0pIQGaWcxYZQbf9LCOttw+iPGv+4uZxv/SKeuqg nsJBiZw5Zuy9AjlTuTHwTOIgS6xsk7L1RlJ9b0vv/UaQUN05Qo/6k3XM65j6WwC+ 3WGu3sIPo54ap26Pwjjf3dR19lGrZABh9IAdrgQlp0rm/pmI4G30+PVEy3dNInSL QqkcW8oUA239xs/XzXeKACMreTCFFx+NhKN0UeJuru1awVZXEWp0BHoFn9HDfS5p O+yPNFH4sT09JDAc2dFLzJRGOO+8TgRjJ01Ylcs2cCktNp4Tgzw1JzMHDAsJJEXg
Bug#1068938: marked as done (less: CVE-2024-32487: with LESSOPEN mishandles \n in paths)
Your message dated Sun, 05 May 2024 18:48:05 + with message-id and subject line Bug#1068938: fixed in less 590-2.1~deb12u1 has caused the Debian Bug report #1068938, regarding less: CVE-2024-32487: with LESSOPEN mishandles \n in paths 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.) -- 1068938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2024-32487[0]: | less through 653 allows OS command execution via a newline character | in the name of a file, because quoting is mishandled in filename.c. | Exploitation typically requires use with attacker-controlled file | names, such as the files extracted from an untrusted archive. | Exploitation also requires the LESSOPEN environment variable, but | this is set by default in many common cases. 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-2024-32487 https://www.cve.org/CVERecord?id=CVE-2024-32487 [1] https://www.openwall.com/lists/oss-security/2024/04/12/5 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 590-2.1~deb12u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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: Fri, 19 Apr 2024 20:58:00 +0200 Source: less Architecture: source Version: 590-2.1~deb12u1 Distribution: bookworm-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 Changes: less (590-2.1~deb12u1) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. * Rebuild for bookworm-security . less (590-2.1) unstable; urgency=medium . * Non-maintainer upload. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: d2ce563d0f5b51c8437a4cd6776c0f88738e415f 2228 less_590-2.1~deb12u1.dsc 82188f425b5197c24b834ae80b95ec07be442c78 352574 less_590.orig.tar.gz ef145bfa44358173e9c405bdc3df92f3493dc805 163 less_590.orig.tar.gz.asc 6c1ef3c34ee2493a2f8349b188af22b5dcdfb252 23144 less_590-2.1~deb12u1.debian.tar.xz Checksums-Sha256: 38c3a11ac9080ba82f5ae897def68b7dca58d21505cfa738e65afb84a6d66508 2228 less_590-2.1~deb12u1.dsc 6aadf54be8bf57d0e2999a3c5d67b1de63808bb90deb8f77b028eafae3a08e10 352574 less_590.orig.tar.gz 1bd54dbadb45eeaeaf58cee2b7b4a701c634c11866082bc494752838af37c3db 163 less_590.orig.tar.gz.asc 682c04edfc35ea4d5877a1e7f6d2a6ef7264bfd5737747a3b91878b23a7bef54 23144 less_590-2.1~deb12u1.debian.tar.xz Files: e1ea4e4f6a213baa11d89e0147152a45 2228 text important less_590-2.1~deb12u1.dsc f029087448357812fba450091a1172ab 352574 text important less_590.orig.tar.gz 4b0250a232d475c4e37f569360d7c3d1 163 text important less_590.orig.tar.gz.asc c896396417c56e4f5e4de19e8cd67e62 23144 text important less_590-2.1~deb12u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYiv5BfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EiUcP/0GqrDLfjxRXezgqCMap/Brd0TiQHzX/ /JDErOWxLtfEycTYdKXfxx/ugSESYhB0dcHT1wTvDenXjbFAroq217/67oORy/Xb UgtyVz7iVN2h0qN+vUYGAsMujckONPAXeCsy2OrxA7XOO/QvmTnzG1as5v0jRLcY cUE0ddul5iQAfjmcn3wE9E63aFHfSXotOPEE9pWdHlWrdHfftW8WZmkwU51MmgMp
Bug#1064293: marked as done (less: CVE-2022-48624)
Your message dated Sun, 05 May 2024 18:48:05 + with message-id and subject line Bug#1064293: fixed in less 590-2.1~deb12u1 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 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.) -- 1064293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: less Version: 590-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for less. CVE-2022-48624[0]: | close_altfile in filename.c in less before 606 omits shell_quote | calls for LESSCLOSE. 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-2022-48624 https://www.cve.org/CVERecord?id=CVE-2022-48624 [1] https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: less Source-Version: 590-2.1~deb12u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of less, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated less 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: Fri, 19 Apr 2024 20:58:00 +0200 Source: less Architecture: source Version: 590-2.1~deb12u1 Distribution: bookworm-security Urgency: high Maintainer: Milan Kupcevic Changed-By: Salvatore Bonaccorso Closes: 1064293 1068938 Changes: less (590-2.1~deb12u1) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. * Rebuild for bookworm-security . less (590-2.1) unstable; urgency=medium . * Non-maintainer upload. * Shell-quote filenames when invoking LESSCLOSE (CVE-2022-48624) (Closes: #1064293) * Fix bug when viewing a file whose name contains a newline (CVE-2024-32487) (Closes: #1068938) Checksums-Sha1: d2ce563d0f5b51c8437a4cd6776c0f88738e415f 2228 less_590-2.1~deb12u1.dsc 82188f425b5197c24b834ae80b95ec07be442c78 352574 less_590.orig.tar.gz ef145bfa44358173e9c405bdc3df92f3493dc805 163 less_590.orig.tar.gz.asc 6c1ef3c34ee2493a2f8349b188af22b5dcdfb252 23144 less_590-2.1~deb12u1.debian.tar.xz Checksums-Sha256: 38c3a11ac9080ba82f5ae897def68b7dca58d21505cfa738e65afb84a6d66508 2228 less_590-2.1~deb12u1.dsc 6aadf54be8bf57d0e2999a3c5d67b1de63808bb90deb8f77b028eafae3a08e10 352574 less_590.orig.tar.gz 1bd54dbadb45eeaeaf58cee2b7b4a701c634c11866082bc494752838af37c3db 163 less_590.orig.tar.gz.asc 682c04edfc35ea4d5877a1e7f6d2a6ef7264bfd5737747a3b91878b23a7bef54 23144 less_590-2.1~deb12u1.debian.tar.xz Files: e1ea4e4f6a213baa11d89e0147152a45 2228 text important less_590-2.1~deb12u1.dsc f029087448357812fba450091a1172ab 352574 text important less_590.orig.tar.gz 4b0250a232d475c4e37f569360d7c3d1 163 text important less_590.orig.tar.gz.asc c896396417c56e4f5e4de19e8cd67e62 23144 text important less_590-2.1~deb12u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYiv5BfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EiUcP/0GqrDLfjxRXezgqCMap/Brd0TiQHzX/ /JDErOWxLtfEycTYdKXfxx/ugSESYhB0dcHT1wTvDenXjbFAroq217/67oORy/Xb UgtyVz7iVN2h0qN+vUYGAsMujckONPAXeCsy2OrxA7XOO/QvmTnzG1as5v0jRLcY cUE0ddul5iQAfjmcn3wE9E63aFHfSXotOPEE9pWdHlWrdHfftW8WZmkwU51MmgMp E5d8pMV3vs9ohtgaGD5G9Ex2LhUlvybyXXFMvWhNqC+K/U+r1DEBOswDTeF3ylCY kDs0LJCI2PguX2ugtLj1m8ctufmBX4OvbcFI9bNTCQxgGzTITVeph80fCJ4/XThr DwQyHWqTdQd6AtIeB7z05Y/4DUvsEbQ18ogbw5A2+jPjBuHoUDdSrRgWclwMhDFS cWIxLKCRoHyGDHvKJ4NCAThNDDrtq2bG/B14EHb+e4WuXSRfiqXoBLOvtEIIfKPG tCF1BXElK8gzt7/pPpLppr7FtfHoTLjkj7Y+W0XBgOZeh022xNZ/DgIi5KUVBgSz
Bug#1063879: marked as done (linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18)
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18 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.) -- 1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Upgrading from linux-image 6.1.0-17 to 6.1.0-18 fails to complete due to nvidia compile error. ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_lock' ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_unlock' * What led up to the situation? routine kernel upgrade using meta package linux-image-amd64 * What exactly did you do (or not do) that was effective (or ineffective)? used synaptic. Also attempted on commandline $ apt install linux-image-amd64 * What was the outcome of this action? Cleaning build area... env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=6.1.0-18-amd64..(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ... dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-6.1.0-18-amd64 linux-headers-6.1.0-18-amd64 linux-image-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) * What outcome did you expect instead? kernel upgraded -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: HP product_name: HP Pavilion Laptop 15-cs3xxx product_version: Type1ProductConfigId chassis_vendor: HP chassis_version: Chassis Version bios_vendor: Insyde bios_version: F.21 board_vendor: HP board_name: 86E2 board_version: 95.36 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Ice Lake-LP Processor Host Bridge/DRAM Registers [8086:8a12] (rev 03) Subsystem: Hewlett-Packard Company Ice Lake-LP Processor Host Bridge/DRAM Registers [103c:86e2] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 IOMMU group: 1 Capabilities: Kernel driver in use: icl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86e2] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 139 IOMMU group: 0 Region 0: Memory at 601600 (64-bit, non-prefetchable) [size=16M] Region 2: Memory at 40 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 8000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Processor Power and Thermal Controller [8086:8a03] (rev 03) Subsystem: Hewlett-Packard Company Processor Power and Thermal Controller [103c:86e2] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 Interrupt: pin A routed to IRQ 16 IOMMU group: 2 Region 0: Memory at 601710 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:14.0 USB controller [0c03]: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller [8086:34ed] (rev 30) (prog-if 30 [XHCI]) Subsystem: Hewlett-Packard Company Ice Lake-LP USB 3.1 xHCI Host Controller [103c:86e2] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0 Interrupt: pin A routed to
Bug#1064034: marked as done (FTBFS: Expired test certificate)
Your message dated Sun, 05 May 2024 18:49:19 + with message-id and subject line Bug#1064034: fixed in ruby3.1 3.1.2-7+deb12u1 has caused the Debian Bug report #1064034, regarding FTBFS: Expired test certificate 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.) -- 1064034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby3.1 Version: 3.1.2-8 Severity: serious Tags: ftbfs A build of ruby3.1 fails on the test stage, since multiple test/net/http/test_https.rb tests return > "ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 peeraddr=(null) state=error: sslv3 alert certificate expired\n" where no error was expected. Failing tests: TestNetHTTPS#test_get, TestNetHTTPS#test_skip_hostname_verification, TestNetHTTPS#test_skip_hostname_verification, TestNetHTTPS#test_post, TestNetHTTPS#test_min_version, TestNetHTTPS#test_get_SNI, TestNetHTTPS#test_get, TestNetHTTPS#test_post, TestNetHTTPS#test_min_version, TestNetHTTPS#test_get_SNI The actual reason is that the certificate it uses (file test/net/fixtures/server.crt) *IS* expired: $ openssl x509 -in test/net/fixtures/server.crt -text Certificate: Data: Version: 3 (0x2) Serial Number: 2 (0x2) Signature Algorithm: sha256WithRSAEncryption Issuer: C = JP, ST = Shimane, L = Matz-e city, O = Ruby Core Team, CN = Ruby Test CA, emailAddress = secur...@ruby-lang.org Validity Not Before: Jan 2 03:27:13 2019 GMT Not After : Jan 1 03:27:13 2024 GMT Subject: C = JP, ST = Shimane, O = Ruby Core Team, OU = Ruby Test, CN = localhost This was fixed upstream on https://github.com/ruby/ruby/commit/d3933fc753187a055a4904af82f5f3794c88c416 --- End Message --- --- Begin Message --- Source: ruby3.1 Source-Version: 3.1.2-7+deb12u1 Done: Moritz Mühlenhoff We believe that the bug you reported is fixed in the latest version of ruby3.1, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Mühlenhoff (supplier of updated ruby3.1 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: Fri, 26 Apr 2024 09:47:47 +0200 Source: ruby3.1 Architecture: source Version: 3.1.2-7+deb12u1 Distribution: bookworm-security Urgency: medium Maintainer: Debian Ruby Team Changed-By: Moritz Mühlenhoff Closes: 1064034 Changes: ruby3.1 (3.1.2-7+deb12u1) bookworm-security; urgency=medium . * CVE-2024-27280 / CVE-2024-27281 / CVE-2024-27282 * Cherrypick changes from 3.1.2-8.2 upload to sid: * Update test certificates from ruby 3.2.3. (Closes: #1064034) * Disable test needing a working DNS resolver. Checksums-Sha1: 7f14017ddc58d15190bf308efcb60030ec3c0b26 2595 ruby3.1_3.1.2-7+deb12u1.dsc 9a0840a5a26dcdbd9e9eebe3354598375a4a6b6d 12885596 ruby3.1_3.1.2.orig.tar.xz dcf086fd43032b9ec0b8c975e2e6baa810408749 80764 ruby3.1_3.1.2-7+deb12u1.debian.tar.xz bf19498a307a05e8e312fe33bb9a525a25706a7f 8628 ruby3.1_3.1.2-7+deb12u1_amd64.buildinfo Checksums-Sha256: a04e26298ae7202d46a45587dc7ce4fb696aa2d3df2699e1684ccf126b6f6840 2595 ruby3.1_3.1.2-7+deb12u1.dsc 350013ef6640f15c42eae48d25c035999dcbb32e4be038d27ad891cb48d685a5 12885596 ruby3.1_3.1.2.orig.tar.xz c2687c741a45046b9652f84734ceb83554b1583c88acc6ac94660d1d504d14a8 80764 ruby3.1_3.1.2-7+deb12u1.debian.tar.xz b92d271efacaa6c4bbeb7e8a06d58a90eb0a0848f4445a17d11c7ce65601b17f 8628 ruby3.1_3.1.2-7+deb12u1_amd64.buildinfo Files: 7bd09d163012362edf54a117ff937926 2595 ruby optional ruby3.1_3.1.2-7+deb12u1.dsc 69cf9ca520a804bff39ab22e1b798b4b 12885596 ruby optional ruby3.1_3.1.2.orig.tar.xz 85e50f242976d9f3706fcada55d13f24 80764 ruby optional ruby3.1_3.1.2-7+deb12u1.debian.tar.xz a6b17b3f8bf8f52363eaad9234e5bf38 8628 ruby optional ruby3.1_3.1.2-7+deb12u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmYraMcACgkQEMKTtsN8 TjaHJg//YH99gZzNbYuqw9kkhZ9yxCjLirfgOOMRKpQLZvqYcDzcDvyDnfClat7A VHMfXPpYl9WcPu6agx0r4JMXGBouY27W1DvSZRNl+Eg1CANos5Zg/gTfeS58QUDh
Bug#1063729: marked as done (Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot)
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot 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.) -- 1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-6.1.0-18-amd64 Version: 6.1.76-1: amd64 Severity: critical Bug Description: Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot. Look "Kernel panic after update.txt" in attachment for details. Look message booting display in attachment for more details. Please correct this urgently !!! Regards. Philipperoot@station:~# apt update && apt dist-upgrade Atteint :1 https://security.debian.org/debian-security bookworm-security InRelease Atteint :2 http://ppa.launchpad.net/vincent-vandevyvre/vvv/ubuntu focal InRelease Atteint :3 https://deb.debian.org/debian bookworm InRelease Atteint :4 https://deb.debian.org/debian bookworm-updates InRelease Atteint :5 https://deb.debian.org/debian-security bookworm-security InRelease Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Tous les paquets sont à jour. Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Calcul de la mise à jour... Fait Le paquet suivant a été installé automatiquement et n'est plus nécessaire : linux-headers-6.1.0-16-common Veuillez utiliser « apt autoremove » pour le supprimer. Les paquets suivants seront ENLEVÉS : linux-headers-6.1.0-16-amd64 linux-image-6.1.0-16-amd64 0 mis à jour, 0 nouvellement installés, 2 à enlever et 0 non mis à jour. 4 partiellement installés ou enlevés. Après cette opération, 412 Mo d'espace disque seront libérés. Souhaitez-vous continuer ? [O/n] o (Lecture de la base de données... 416726 fichiers et répertoires déjà installés. ) Suppression de linux-headers-6.1.0-16-amd64 (6.1.67-1) ... Suppression de linux-image-6.1.0-16-amd64 (6.1.67-1) ... /etc/kernel/prerm.d/dkms: dkms: removing: nvidia-current 525.147.05 (6.1.0-16-amd64) (x86_64) Module nvidia-current-525.147.05 for kernel 6.1.0-16-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. nvidia-current.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-modeset.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-drm.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-uvm.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-peermem.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.1.0-16-amd64 /etc/kernel/postrm.d/zz-update-grub: Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-6.1.0-18-amd64 Found linux image: /boot/vmlinuz-6.1.0-17-amd64 Found initrd image: /boot/initrd.img-6.1.0-17-amd64 Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for UEFI Firmware Settings ... done Paramétrage de linux-image-6.1.0-18-amd64 (6.1.76-1) ... I:
Bug#1063689: marked as done (linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU)
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU 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.) -- 1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: important X-Debbugs-Cc: s...@weilnetz.de Dear Maintainer, on a server with NVIDIA GPU, nvidia-kernel-dkms fails to build the required kernel modules after a kernel update with linux-image-6.1.0-18-amd64 and linux-headers-6.1.0-18-amd64. It looks like the new kernel includes changes that cause a conflict between the non-GPL NVIDIA code and two GPL'ed functions which are now used, but were not used with the previous kernel from Debian stable. Best regards Stefan Weil -- Package-specific info: ** Model information sys_vendor: primeLine Solutions product_name: egino s-Series egino BTO product_version: 0123456789 chassis_vendor: Supermicro chassis_version: 0123456789 bios_vendor: American Megatrends Inc. bios_version: 2.1 board_vendor: Supermicro board_name: H11SSL-i board_version: 2.00 ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] Subsystem: Super Micro Computer Inc Starship/Matisse Root Complex [15d9:1a03] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: Super Micro Computer Inc H12SSL-i [15d9:790b] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 01:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA [1022:1498] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA [1022:1498] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 02:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA [1022:1498] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA [1022:1498] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 02:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] (prog-if 30 [XHCI]) Subsystem: Super Micro Computer Inc
Bug#1063717: marked as done (cuda-drivers: Build of module nvidia.ko fails)
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding cuda-drivers: Build of module nvidia.ko fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cuda-drivers Version: 545.23.08-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: matte.mb2006.9...@gmail.com Dear Maintainer, Compiling the cuda driver for kernel 6.1.0-18 fails with this error: " ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_lock' ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__rcu_read_unlock' " -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-17-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 cuda-drivers depends on: ii cuda-drivers-545 545.23.08-1 cuda-drivers recommends no packages. cuda-drivers suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers Source-Version: 535.161.08-2~deb12u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers, 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 1062...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers 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: Fri, 03 May 2024 07:19:01 +0200 Source: nvidia-graphics-drivers Architecture: source Version: 535.161.08-2~deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1013462 1032647 1033602 1033774 1039678 1041991 1042081 1050809 1050935 1053562 1055136 1059339 1061269 1061597 1062932 1063363 1063881 1064194 1064983 Changes: nvidia-graphics-drivers (535.161.08-2~deb12u1) bookworm; urgency=medium . * Rebuild for bookworm. . nvidia-graphics-drivers (535.161.08-2) unstable; urgency=medium . * nvidia-driver-full: libnvidia-fbc1 and libnvidia-rtcore are not available on ppc64el. * Add autopkgtest testing the installation of the full driver suite. . nvidia-graphics-drivers (535.161.08-1) unstable; urgency=medium . * New upstream Tesla branch release 535.161.08 (2024-03-18). (Closes: #1061269, #1061597, #1059339) * Upload to unstable. . nvidia-graphics-drivers (535.161.07-1) experimental; urgency=medium . * New upstream LTS and Tesla branch release 535.161.07 (2024-02-22). * Fixed CVE-2024-0074, CVE-2024-0075, CVE-2024-0078. (Closes: #1064983) https://nvidia.custhelp.com/app/answers/detail/a_id/5520 * Improved compatibility with recent Linux kernels. . [ Andreas Beckmann ] * Refresh patches. * Update nv-readme.ids. . nvidia-graphics-drivers (535.154.05-1) experimental; urgency=medium . * New upstream LTS and Tesla branch release 535.154.05 (2024-01-16). * Improved compatibility with recent Linux kernels. * New upstream long term support branch release 535.146.02 (2023-12-07). - Fixed a bug that could cause some multi-GPU systems to crash on suspend. - Fixed a bug that could cause the system to crash when an application is run with __NV_PRIME_RENDER_OFFLOAD=1. - Fixed a bug which prevented application profiles from getting applied to PRIME Render Offloaded applications running via Wine. - Disabled PRIME Display Offload Sink support for virtual
Bug#1063713: marked as done (linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem with building modules)
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem with building modules 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.) -- 1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.76-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: gnomedeu...@gmail.com -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: VivoBook S13 X330FN_S330FN product_version: 1.0 chassis_vendor: ASUSTeK COMPUTER INC. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: X330FN.304 board_vendor: ASUSTeK COMPUTER INC. board_name: X330FN board_version: 1.0 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM Controller [8086:3e34] (rev 0c) Subsystem: ASUSTeK Computer Inc. Coffee Lake HOST and DRAM Controller [1043:1631] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) DeviceName: VGA Subsystem: ASUSTeK Computer Inc. WhiskeyLake-U GT2 [UHD Graphics 620] [1043:1d1e] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1043:1631] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [1043:1631] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Point-LP Thermal Controller [8086:9df9] (rev 30) Subsystem: ASUSTeK Computer Inc. Cannon Point-LP Thermal Controller [1043:1631] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:14.0 USB controller [0c03]: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller [8086:9ded] (rev 30) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Cannon Point-LP USB 3.1 xHCI Controller [1043:201f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Intel Corporation Cannon Point-LP Shared SRAM [8086:7270] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:14.3 Network controller [0280]: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:9df0] (rev 30) DeviceName: WLAN
Bug#1063668: marked as done (linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues)
Your message dated Sun, 05 May 2024 18:48:20 + with message-id and subject line Bug#1062932: fixed in nvidia-graphics-drivers 535.161.08-2~deb12u1 has caused the Debian Bug report #1062932, regarding linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 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.) -- 1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-6.1.0-18-amd64 Version: linux-image-6.1.0-18 Severity: important X-Debbugs-Cc: joshua.beckwith@gmail.com Dear Maintainer, I have noticed some issues pertaining to both packages, namely linux- image-6.1.0-18-amd64 & linux-headers-6.1.0-18-amd64-common. The repository Nvidia Driver 525.147.05-4 fails to build the module for this Kernel with exit code: 10. I hope this isn't too much of a problem. Kind regards Joshua Beckwith -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.4-1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 linux-image-6.1.0-18-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-18-amd64 recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-18-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.06-13+deb12u1 pn linux-doc-6.1 --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers Source-Version: 535.161.08-2~deb12u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers, 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 1062...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers 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: Fri, 03 May 2024 07:19:01 +0200 Source: nvidia-graphics-drivers Architecture: source Version: 535.161.08-2~deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1013462 1032647 1033602 1033774 1039678 1041991 1042081 1050809 1050935 1053562 1055136 1059339 1061269 1061597 1062932 1063363 1063881 1064194 1064983 Changes: nvidia-graphics-drivers (535.161.08-2~deb12u1) bookworm; urgency=medium . * Rebuild for bookworm. . nvidia-graphics-drivers (535.161.08-2) unstable; urgency=medium . * nvidia-driver-full: libnvidia-fbc1 and libnvidia-rtcore are not available on ppc64el. * Add autopkgtest testing the installation of the full driver suite. . nvidia-graphics-drivers (535.161.08-1) unstable; urgency=medium . * New upstream Tesla branch release 535.161.08 (2024-03-18). (Closes: #1061269, #1061597, #1059339) * Upload to unstable. . nvidia-graphics-drivers (535.161.07-1) experimental; urgency=medium . * New upstream LTS and Tesla branch release 535.161.07 (2024-02-22). * Fixed CVE-2024-0074, CVE-2024-0075, CVE-2024-0078. (Closes: #1064983) https://nvidia.custhelp.com/app/answers/detail/a_id/5520 * Improved compatibility with recent Linux kernels. . [ Andreas Beckmann ] * Refresh patches. * Update nv-readme.ids. . nvidia-graphics-drivers (535.154.05-1) experimental; urgency=medium . * New upstream LTS and Tesla branch release 535.154.05 (2024-01-16). * Improved compatibility with recent Linux kernels. * New upstream long term support branch release 535.146.02 (2023-12-07). - Fixed a bug that could cause some multi-GPU systems to crash on suspend.
Bug#1055144: marked as done (nvidia-open-gpu-kernel-modules: CVE-2023-31022)
Your message dated Sun, 05 May 2024 18:48:21 + with message-id and subject line Bug#1055144: fixed in nvidia-open-gpu-kernel-modules 535.161.08-1~deb12u1 has caused the Debian Bug report #1055144, regarding nvidia-open-gpu-kernel-modules: CVE-2023-31022 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.) -- 1055144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: normal Tags: security X-Debbugs-Cc: Debian Security Team Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-31022 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-31022 Control: tag -3 + wontfix Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-31022 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-31022 Control: tag -5 + wontfix Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-31022 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-31022 Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-31022 Control: found -8 515.48.07-1 Control: found -8 525.60.13-1 Control: found -8 535.54.03-1 Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-31022 Control: found -9 520.56.06-1 Control: found -9 525.85.12-1 Control: found -9 530.30.02-1 Control: found -9 535.43.02-1 Control: found -9 545.23.06-1 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 Control: found -1 520.56.06-1 Control: found -1 525.53-1 Control: found -1 530.30.02-1 Control: found -1 535.43.02-1 Control: found -1 545.23.06-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5491 CVE-2023-31022 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a NULL-pointer dereference may lead to denial of service. Linux Driver Branch CVE IDs Addressed R545, R535, R525, R470 CVE-2023-31022 Driver Branch Affected Driver VersionsUpdated Driver Version R545All driver versions prior to 545.29.02 545.29.02 R535All driver versions prior to 535.129.03 535.129.03 R525All driver versions prior to 525.147.05 525.147.05 R470All driver versions prior to 470.223.02 470.223.02 Andreas --- End Message --- --- Begin Message --- Source: nvidia-open-gpu-kernel-modules Source-Version: 535.161.08-1~deb12u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-open-gpu-kernel-modules, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-open-gpu-kernel-modules 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, 28 Mar 2024 17:15:50 +0100 Source: nvidia-open-gpu-kernel-modules Architecture: source Version: 535.161.08-1~deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1033783 1039686 1055144 1064991 Changes: nvidia-open-gpu-kernel-modules (535.161.08-1~deb12u1) bookworm; urgency=medium . * Rebuild for bookworm. .
Bug#1069586: marked as done (Chromium native Wayland support broken)
Your message dated Sun, 05 May 2024 18:47:39 + with message-id and subject line Bug#1069586: fixed in chromium 124.0.6367.78-1~deb12u1 has caused the Debian Bug report #1069586, regarding Chromium native Wayland support broken 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.) -- 1069586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 124.0.6367.60-1~deb12u1 Since the last update, Chromium does work with native Wayland. It is starting up, but it is displaying an invisible window. It is listed in the window switchers (Alt+Tab), Gnome Shell etc., but invisible. Note: The default configuration uses X11 via XWayland and is working. The setting can be managed via command line arguments or by typing chrome://flags into the URL bar (filter for ozone). Available settings: default -> X11works auto-> Wayland if available does not work x11 works wayland does not work I have been using Chromium with native Wayland for many months without problems until the last update. I reproduced this with a completely new browser profile. Regards Stephan --- End Message --- --- Begin Message --- Source: chromium Source-Version: 124.0.6367.78-1~deb12u1 Done: Andres Salomon We believe that the bug you reported is fixed in the latest version of chromium, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andres Salomon (supplier of updated chromium 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, 25 Apr 2024 19:07:35 -0400 Source: chromium Architecture: source Version: 124.0.6367.78-1~deb12u1 Distribution: bookworm-security Urgency: high Maintainer: Debian Chromium Team Changed-By: Andres Salomon Closes: 1069586 Changes: chromium (124.0.6367.78-1~deb12u1) bookworm-security; urgency=high . * New upstream security release. - CVE-2024-4058: Type Confusion in ANGLE. Reported by Toan (suto) Pham and Bao (zx) Pham of Qrious Secure. - CVE-2024-4059: Out of bounds read in V8 API. Reported by Eirik. - CVE-2024-4060: Use after free in Dawn. Reported by wgslfuzz. . chromium (124.0.6367.60-2~deb12u1) bookworm-security; urgency=high . * d/patches/ppc64le: - third_party/0001-Add-PPC64-support-for-boringssl.patch: update for upstream boringssl changes and reenable - third_party/0003-third_party-ffmpeg-Add-ppc64-generated-config.patch: regenerate from new ffmpeg source tree - third_party/skia-vsx-instructions.patch: update for upstream changes . [ Andres Salomon ] * d/patches: - fixes/arm64-ftbfs.patch: add arm64-specific ftbfs fix for libdav1d. - upstream/ozone1.patch, upstream/ozone2.patch: backport fixes for broken wayland support (closes: #1069586). Checksums-Sha1: 203ade13c5ac6e96012acc54fd621444af7aab95 3722 chromium_124.0.6367.78-1~deb12u1.dsc 5f5853205ae35cfddfbdaf827223d2c588453796 848031104 chromium_124.0.6367.78.orig.tar.xz d06256f779f99a25a36667912bc9ae98474cacf3 418756 chromium_124.0.6367.78-1~deb12u1.debian.tar.xz a2b3033cbbe407f9fe77d11a3ff5abc95616b88e 21670 chromium_124.0.6367.78-1~deb12u1_source.buildinfo Checksums-Sha256: 70279f08ce9d9b96fa735f6bf0ed54fdc8ce07bc92121107989fd165982d742d 3722 chromium_124.0.6367.78-1~deb12u1.dsc 2a29c4c8904c24633254fb219b06faa4f4caa5e39e9d9b396f0e9b5f5771607a 848031104 chromium_124.0.6367.78.orig.tar.xz dc8b7c91e42f621f19d6b7a9a3d8d5dbef96b7d2c84f519a832d904e7e873258 418756 chromium_124.0.6367.78-1~deb12u1.debian.tar.xz b368f867827c26907bb3289663498d2eaddd72cae359a0bf74f2c357c5992bd4 21670 chromium_124.0.6367.78-1~deb12u1_source.buildinfo Files: 8c5bcd97f51eb354ae636370efd4de9e 3722 web optional chromium_124.0.6367.78-1~deb12u1.dsc bee1189de5fa76a318f3ea2bd13bdf28 848031104 web optional chromium_124.0.6367.78.orig.tar.xz 952a5c6348750db95f50159dbdbb7690 418756 web optional chromium_124.0.6367.78-1~deb12u1.debian.tar.xz
Bug#1068412: marked as done (apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709)
Your message dated Sun, 05 May 2024 18:47:10 + with message-id and subject line Bug#1068412: fixed in apache2 2.4.59-1~deb12u1 has caused the Debian Bug report #1068412, regarding apache2: CVE-2024-27316 CVE-2024-24795 CVE-2023-38709 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.) -- 1068412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apache2 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for apache2. CVE-2024-27316[0]: https://www.kb.cert.org/vuls/id/421644 https://www.openwall.com/lists/oss-security/2024/04/04/4 CVE-2024-24795[1]: https://www.openwall.com/lists/oss-security/2024/04/04/5 CVE-2023-38709[2]: https://www.openwall.com/lists/oss-security/2024/04/04/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-2024-27316 https://www.cve.org/CVERecord?id=CVE-2024-27316 [1] https://security-tracker.debian.org/tracker/CVE-2024-24795 https://www.cve.org/CVERecord?id=CVE-2024-24795 [2] https://security-tracker.debian.org/tracker/CVE-2023-38709 https://www.cve.org/CVERecord?id=CVE-2023-38709 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.59-1~deb12u1 Done: Yadd We believe that the bug you reported is fixed in the latest version of apache2, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated apache2 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: Fri, 05 Apr 2024 16:02:26 +0400 Source: apache2 Binary: apache2 apache2-bin apache2-bin-dbgsym apache2-data apache2-dev apache2-doc apache2-ssl-dev apache2-suexec-custom apache2-suexec-custom-dbgsym apache2-suexec-pristine apache2-suexec-pristine-dbgsym apache2-utils apache2-utils-dbgsym libapache2-mod-md libapache2-mod-proxy-uwsgi Architecture: source amd64 all Version: 2.4.59-1~deb12u1 Distribution: bookworm-security Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Yadd Description: apache2- Apache HTTP Server apache2-bin - Apache HTTP Server (modules and other binary files) apache2-data - Apache HTTP Server (common files) apache2-dev - Apache HTTP Server (development headers) apache2-doc - Apache HTTP Server (on-site documentation) apache2-ssl-dev - Apache HTTP Server (mod_ssl development headers) apache2-suexec-custom - Apache HTTP Server configurable suexec program for mod_suexec apache2-suexec-pristine - Apache HTTP Server standard suexec program for mod_suexec apache2-utils - Apache HTTP Server (utility programs for web servers) libapache2-mod-md - transitional package libapache2-mod-proxy-uwsgi - transitional package Closes: 1068412 Changes: apache2 (2.4.59-1~deb12u1) bookworm-security; urgency=medium . * New upstream version 2.4.58 (Closes: CVE-2023-31122, CVE-2023-43622, CVE-2023-45802) * New upstream version 2.4.59 (Closes: #1068412 CVE-2024-27316 CVE-2024-24795 CVE-2023-38709) * Refresh patches * Update test framework Checksums-Sha1: 0ff1bbe49e7266429e3ea5f8df651776b961902e 3520 apache2_2.4.59-1~deb12u1.dsc 7a118baaed0f2131e482f93f5057038ca6c021be 9843252 apache2_2.4.59.orig.tar.gz 837cdf46898d962c4c05642745566249fc91e52b 833 apache2_2.4.59.orig.tar.gz.asc 59cd2b140a3e313345acb675f4792a63ecad7403 820804 apache2_2.4.59-1~deb12u1.debian.tar.xz d854f4e07f350cf3b067caf1ed78edbde3c76031 3734744 apache2-bin-dbgsym_2.4.59-1~deb12u1_amd64.deb f6a264c3f91353e88233eaec66f997d86be150ad 1379912 apache2-bin_2.4.59-1~deb12u1_amd64.deb 16d3d3d8aa25fea0c7755efc8b9685e70cc70b21 160264 apache2-data_2.4.59-1~deb12u1_all.deb 5b643339c2a9ec14872873e41772a91f73031c3d 312108 apache2-dev_2.4.59-1~deb12u1_amd64.deb 4ec40752b1f22964802957e6a59187ec7dce83ea 4022328
Bug#999922: marked as done (xneur: depends on obsolete pcre3 library)
Your message dated Sun, 05 May 2024 17:50:31 + with message-id and subject line Bug#22: fixed in xneur 0.20.0-3.3 has caused the Debian Bug report #22, regarding xneur: depends on obsolete pcre3 library 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.) -- 22: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xneur Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: xneur Source-Version: 0.20.0-3.3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of xneur, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated xneur 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, 05 May 2024 19:41:29 +0200 Source: xneur Architecture: source Version: 0.20.0-3.3 Distribution: unstable Urgency: medium Maintainer: Alexander GQ Gerasiov Changed-By: Sebastian Ramacher Closes: 22 Changes: xneur (0.20.0-3.3) unstable; urgency=medium . * Non-maintainer upload. * debian/patches: Really fix pkgconfig file after porting to PCRE2 (Closes: #22) Checksums-Sha1: c8a85177295ec4f1f428e52d6554823ff723ea1d 1465 xneur_0.20.0-3.3.dsc fb4c39521af4fc2e6b217526b455b14ba9302ced 11592 xneur_0.20.0-3.3.debian.tar.xz 395a5d5ec237fdefb02febd2fb73dce12060300e 10020 xneur_0.20.0-3.3_source.buildinfo Checksums-Sha256: 8ec5739d16625c3e7456794f05e53437606ca65c2ddf4de8cd1f6ca57bde745f 1465 xneur_0.20.0-3.3.dsc 9ac02918503129f79ac670a225599614ea71bf49c525d97c7a1ea9fe38fd8464 11592 xneur_0.20.0-3.3.debian.tar.xz 0084d148a13cc97a879c95b631b41fb384d092b37f46a3f82cd058a3157f96da 10020 xneur_0.20.0-3.3_source.buildinfo Files: 20c83c15ba7cd84562e9518ce970ed59 1465 x11 optional xneur_0.20.0-3.3.dsc b58f16d90ad0ca510cae8b576300f586 11592 x11 optional xneur_0.20.0-3.3.debian.tar.xz 5dd9c57aed4e8a2215304c1b6dcdc1d6 10020 x11 optional xneur_0.20.0-3.3_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZjfE6AAKCRAhk2s2YA/N ibubAP9/ReAk4PSxoEFIUYZtCxw3mMNGCz2UMvpkwEJngfb/bwD+OAyTa5gfwWBZ dXLXjsW9RABAI3zwAVraQ+hg8du1/QM= =T6qX -END PGP SIGNATURE- pgpPv7KkX8bc0.pgp Description: PGP signature --- End Message ---
Processed: unarchiving 1008010, fixed 1008010 in 7.5.1-1.1+deb10u2, archiving 1008010, unarchiving 1016978 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 1008010
Bug #1008010 {Done: David Lamparter } [src:frr] frr:
CVE-2022-26125 CVE-2022-26126 CVE-2022-26127 CVE-2022-26128 CVE-2022-26129
Unarchived Bug 1008010
> fixed 1008010 7.5.1-1.1+deb10u2
Bug #1008010 {Done: David Lamparter } [src:frr] frr:
CVE-2022-26125 CVE-2022-26126 CVE-2022-26127 CVE-2022-26128 CVE-2022-26129
The source 'frr' and version '7.5.1-1.1+deb10u2' do not appear to match any
binary packages
Marked as fixed in versions frr/7.5.1-1.1+deb10u2.
> archive 1008010
Bug #1008010 {Done: David Lamparter } [src:frr] frr:
CVE-2022-26125 CVE-2022-26126 CVE-2022-26127 CVE-2022-26128 CVE-2022-26129
archived 1008010 to archive/10 (from 1008010)
> unarchive 1016978
Bug #1016978 {Done: David Lamparter } [src:frr] frr:
CVE-2022-37035
Unarchived Bug 1016978
> fixed 1016978 7.5.1-1.1+deb10u2
Bug #1016978 {Done: David Lamparter } [src:frr] frr:
CVE-2022-37035
The source 'frr' and version '7.5.1-1.1+deb10u2' do not appear to match any
binary packages
Marked as fixed in versions frr/7.5.1-1.1+deb10u2.
> archive 1016978
Bug #1016978 {Done: David Lamparter } [src:frr] frr:
CVE-2022-37035
archived 1016978 to archive/78 (from 1016978)
> unarchive 1055852
Bug #1055852 {Done: Daniel Baumann }
[src:frr] frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753
CVE-2023-47234 CVE-2023-47235
Unarchived Bug 1055852
> fixed 1055852 7.5.1-1.1+deb10u2
Bug #1055852 {Done: Daniel Baumann }
[src:frr] frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753
CVE-2023-47234 CVE-2023-47235
The source 'frr' and version '7.5.1-1.1+deb10u2' do not appear to match any
binary packages
Marked as fixed in versions frr/7.5.1-1.1+deb10u2.
> archive 1055852
Bug #1055852 {Done: Daniel Baumann }
[src:frr] frr: CVE-2023-38407 CVE-2023-41361 CVE-2023-46752 CVE-2023-46753
CVE-2023-47234 CVE-2023-47235
archived 1055852 to archive/52 (from 1055852)
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1008010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008010
1016978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016978
1055852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 1066108, fixed 1066108 in 3.20240312.1~deb10u1, fixed 1066108 in 3.20240312.1~deb9u1 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 1066108
Bug #1066108 {Done: Henrique de Moraes Holschuh }
[src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368
CVE-2023-38575 CVE-2023-22655 CVE-2023-28746
Unarchived Bug 1066108
> fixed 1066108 3.20240312.1~deb10u1
Bug #1066108 {Done: Henrique de Moraes Holschuh }
[src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368
CVE-2023-38575 CVE-2023-22655 CVE-2023-28746
The source 'intel-microcode' and version '3.20240312.1~deb10u1' do not appear
to match any binary packages
Marked as fixed in versions intel-microcode/3.20240312.1~deb10u1.
> fixed 1066108 3.20240312.1~deb9u1
Bug #1066108 {Done: Henrique de Moraes Holschuh }
[src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368
CVE-2023-38575 CVE-2023-22655 CVE-2023-28746
The source 'intel-microcode' and version '3.20240312.1~deb9u1' do not appear to
match any binary packages
Marked as fixed in versions intel-microcode/3.20240312.1~deb9u1.
> fixed 1066108 3.20240312.1~deb8u1
Bug #1066108 {Done: Henrique de Moraes Holschuh }
[src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368
CVE-2023-38575 CVE-2023-22655 CVE-2023-28746
The source 'intel-microcode' and version '3.20240312.1~deb8u1' do not appear to
match any binary packages
Marked as fixed in versions intel-microcode/3.20240312.1~deb8u1.
> archive 1066108
Bug #1066108 {Done: Henrique de Moraes Holschuh }
[src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368
CVE-2023-38575 CVE-2023-22655 CVE-2023-28746
archived 1066108 to archive/08 (from 1066108)
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1066108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999922: xneur: diff for NMU version 0.20.0-3.3
Dear maintainer, I've prepared an NMU for xneur (versioned as 0.20.0-3.3). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru xneur-0.20.0/debian/changelog xneur-0.20.0/debian/changelog --- xneur-0.20.0/debian/changelog 2024-05-05 15:23:15.0 +0200 +++ xneur-0.20.0/debian/changelog 2024-05-05 19:41:29.0 +0200 @@ -1,3 +1,11 @@ +xneur (0.20.0-3.3) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches: Really fix pkgconfig file after porting to PCRE2 (Closes: +#22) + + -- Sebastian Ramacher Sun, 05 May 2024 19:41:29 +0200 + xneur (0.20.0-3.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch --- xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch 2024-05-05 15:20:35.0 +0200 +++ xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch 2024-05-05 19:41:07.0 +0200 @@ -115,7 +115,7 @@ Name: xnconfig Description: XNeur config library -Requires: libpcre -+Requires: libpcre2 ++Requires: libpcre2-8 Version: @VERSION@ Libs: -L@libdir@ -lxnconfig @PCRE_LIBS@ @LDFLAGS@ @ADDITIONAL_LIBS@ Cflags: -I@includedir@
Bug#1069997: marked as done (nginx: NGX_MODULE_SIGNATURE has changed on 32-bit t64 architectures, but the ${nginx:abi} substvar has not)
Your message dated Sun, 05 May 2024 17:36:23 +
with message-id
and subject line Bug#1069997: fixed in nginx 1.26.0-1
has caused the Debian Bug report #1069997,
regarding nginx: NGX_MODULE_SIGNATURE has changed on 32-bit t64 architectures,
but the ${nginx:abi} substvar has not
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.)
--
1069997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nginx
Version: 1.24.0-2
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t
X-Debbugs-Cc: Sebastian Ramacher , Steve Langasek
Control: block 1069482 with -1
While looking into #1069482 (libnginx-mod-http-lua: FTBFS on armhf) I
noticed that nginx has a NGX_MODULE_SIGNATURE string which is required
to match between server and modules. This string has been changed by the
t64 transition, but the substvar ${nginx:abi} describing the abi for
package relationships has not been changed.
nginx_1.24.0-2+b1_armhf.deb -> 4,4,4,0001011100
nginx_1.24.0-2+b2_armhf.deb -> 4,4,8,0001011100
(I used 'strings usr/sbin/nginx | grep 111' to get them from the
binaries)
NGX_MODULE_SIGNATURE is defined in src/core/ngx_module.h and starts with
ngx_value(NGX_PTR_SIZE) "," \
ngx_value(NGX_SIG_ATOMIC_T_SIZE) "," \
ngx_value(NGX_TIME_T_SIZE) ","
I'd suggest bumping the substvar in debian/libnginx-mod.abisubstvars to
e.g. nginx-abi-1.24.0-1t64 and rebuilding all modules. Maybe that's
already sufficient for fixing #1069482.
Andreas
PS: could something automatically generated from $(DEB_VERSION_UPSTREAM)
and NGX_MODULE_SIGNATURE (s/,/-/g) (and maybe an optional suffix) be
used for the abi substvar?
--- End Message ---
--- Begin Message ---
Source: nginx
Source-Version: 1.26.0-1
Done: Jan Mojžíš
We believe that the bug you reported is fixed in the latest version of
nginx, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jan Mojžíš (supplier of updated nginx 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, 05 May 2024 18:48:05 +0200
Source: nginx
Architecture: source
Version: 1.26.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nginx Maintainers
Changed-By: Jan Mojžíš
Closes: 1063659 1069997
Changes:
nginx (1.26.0-1) unstable; urgency=medium
.
* New upstream version 1.26.0
* nginx ABI release: nginx-abi-1.26.0-1 (Closes: 1069997)
* d/libnginx-mod.abisubstvars: remove third-party modules version constraints
* d/u/signing-key.asc add Roman Arutyunyan’s PGP public key,
the key is used to sign the 1.26.0 release
* d/p/CVE-2023-44487.patch remove, fixed in upstream
* d/ufw/nginx update, add QUICK, thanks Marcus Bointon
* d/conf/mime.types add application/xslt+xml, thanks K. Widholm
* d/copyright: updated copyright related to new upstream version
* d/copyright: bump my copyright year
* d/conf/nginx.conf: add worker_cpu_affinity auto (Closes: 1063659)
* d/gbp.conf: add sign-tags = True, [pull] track-missing = True,
[import-orig] merge-mode = replace
Checksums-Sha1:
7511055323408af7e522341aa65e93d1c81bed84 3554 nginx_1.26.0-1.dsc
798390eae26a25e91d158891b341596eaddd0dea 1244118 nginx_1.26.0.orig.tar.gz
78f4e6330489fe2a51738b2ae42fa3c35f2e45ee 74204 nginx_1.26.0-1.debian.tar.xz
787462ceced979367070f71dc1461322d283ecc3 8908 nginx_1.26.0-1_source.buildinfo
Checksums-Sha256:
128f18a7de6cabe53f981ad254f7a70da81a778319a793764318500a803988a8 3554
nginx_1.26.0-1.dsc
d2e6c8439d6c6db5015d8eaab2470ab52aef85a7bf363182879977e084370497 1244118
nginx_1.26.0.orig.tar.gz
03dc71d97584a5cb7d914d68b1aa73e482042b4f731f17b7120a8b764e1a22a5 74204
nginx_1.26.0-1.debian.tar.xz
30ddb883ed9e2013b6f0a723a63d86fd658280ef1b90be3596cf5f39351ecab0 8908
nginx_1.26.0-1_source.buildinfo
Files:
00f09dc859d9efec27d6e0ea3efe3c1c 3554 httpd optional nginx_1.26.0-1.dsc
bb1b92cf7d72efcc0da343b057f23516 1244118 httpd
Bug#1070463: gnome-remote-desktop: 46 has failing build tests
Source: gnome-remote-desktop Version: 46.1-1 Severity: serious Tags: ftbfs experimental Control: block 1050237 by -1 X-Debbugs-CC: ma...@ubuntu.com gnome-remote-desktop's build tests are failing. This is blocking the GNOME Shell 46 transition since GNOME Shell & GNOME Remote Desktop should have the same major version, at least while the projects are under heavy development. The build tests were passing with version 45. It is not clear to me why the tests are failing in Debian Experimental but passing in Ubuntu 24.04 LTS. Thank you, Jeremy Bícha
Processed: gnome-remote-desktop: 46 has failing build tests
Processing control commands: > block 1050237 by -1 Bug #1050237 [release.debian.org] transition: mutter/gnome-shell 45 1050237 was blocked by: 1050241 1040005 1052414 1052145 1050237 was not blocking any bugs. Added blocking bug(s) of 1050237: 1070463 -- 1050237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050237 1070463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070461: marked as done (uhttpmock0: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration)
Your message dated Sun, 5 May 2024 13:06:41 -0400 with message-id and subject line Re: Bug#1070461: uhttpmock0: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration has caused the Debian Bug report #1070461, regarding uhttpmock0: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:uhttpmock0 Version: 0.5.5-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -Dauto_features=disabled -Dintrospection=false cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 -Dauto_features=disabled -Dintrospection=false The Meson build system Version: 1.4.0 Source dir: /<> Build dir: /<>/obj-x86_64-linux-gnu Build type: native build Project name: uhttpmock Project version: 0.5.5 C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-24) 13.2.0") C linker for the host machine: cc ld.bfd 2.42 Host machine cpu family: x86_64 Host machine cpu: x86_64 Configuring uhm-version.h using configuration Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 Run-time dependency glib-2.0 found: YES 2.80.0 Run-time dependency gio-2.0 found: YES 2.80.0 Run-time dependency libsoup-2.4 found: YES 2.74.3 Compiler for C supports link arguments -Wl,--version-script,/<>/libuhttpmock/libuhttpmock.map: YES Configuring version.xml using configuration Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj) Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb) Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml) Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref) Build targets in project: 5 uhttpmock 0.5.5 User defined options auto_features : disabled buildtype : plain libdir: lib/x86_64-linux-gnu localstatedir : /var prefix: /usr sysconfdir: /etc wrap_mode : nodownload python.bytecompile: -1 introspection : false Found ninja-1.11.1 at /usr/bin/ninja make[1]: Leaving directory '/<>' dh_auto_build cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v [1/8] cc -Ilibuhttpmock/libuhttpmock-0.0.so.0.2.3.p -Ilibuhttpmock -I../libuhttpmock -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread '-DG_LOG_DOMAIN="libuhttpmock"' -MD -MQ libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-resolver.c.o -MF libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-resolver.c.o.d -o libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-resolver.c.o -c ../libuhttpmock/uhm-resolver.c [2/8] cc -Ilibuhttpmock/tests/server.p -Ilibuhttpmock/tests -I../libuhttpmock/tests -Ilibuhttpmock -I../libuhttpmock -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pthread '-DTEST_FILE_DIR="/<>/libuhttpmock/tests/"' '-DG_LOG_DOMAIN="libuhttpmock-tests"'
Bug#1070460: translate-toolkit: FTBFS: failing tests
Package: src:translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.12_translate
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
[... snipped ...]
unit.makeobsolete()
assert str(unit) == ""
E assert '#~ msgid "te...~ msgstr ""\n' == ''
E
E + #~ msgid "test"
E + #~ msgstr ""
tests/translate/storage/test_po.py:449: AssertionError
- Captured stdout call -
b'#. The automatic one\n#: test.c\nmsgid "test"\nmsgstr ""\n'
TestXWikiFullPage.test_remove _
self =
@mark.xfail(reason="removal not working in full page")
def test_remove(self):
super().test_remove()
tests/translate/storage/test_properties.py:1614:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
def test_remove(self):
"""Tests removing a unit with a source string."""
store = self.StoreClass()
unit = store.addsourceunit("Test String")
# Some storages (MO, OmegaT) serialize only translated units
unit.target = "Test target"
assert headerless_len(store.units) == 1
withunit = bytes(store)
print(withunit)
store.removeunit(unit)
assert headerless_len(store.units) == 0
withoutunit = bytes(store)
print(withoutunit)
assert withoutunit != withunit
E assert
Bug#1070459: psortb: FTBFS: binding.c:52:13: error: implicit declaration of function ‘free’
Package: src:psortb Version: 3.0.6+dfsg-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' cp -a psort/bin/psort psort/bin/psort.debsave dh_auto_configure /usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-z,relro -Wl,-z,now" External Module XML::RPC, XML Based RPC client, is not installed on this computer. The XML::RPC in PSortb needs it for making calls to remote PSortb servers, if you don't plan to do this, ignore this warning We think we've found blastall, please enter the path if this isn't correct [/usr/bin/] /usr/bin/ We think we've found pfscan, please enter the path if this isn't correct [/usr/bin/] /usr/bin/ Where do you plan to install the psort configuration files? [/usr/local/psortb] /usr/local/psortb Checking if your kit is complete... Looks good hmmer was not found in the dynamic linker path, is there somewhere else we should check? [/usr/local/lib64] /usr/local/lib64 We're still not finding hmmer either in your dynamic linker path (/etc/ld.so.conf) or in /usr/local/lib64. Do you want to continue anyways? [Y/n] [Y] Y squid was not found in the dynamic linker path, is there somewhere else we should check? [/usr/local/lib64] /usr/local/lib64 We're still not finding squid either in your dynamic linker path (/etc/ld.so.conf) or in /usr/local/lib64. Do you want to continue anyways? [Y/n] [Y] Y Checking if your kit is complete... Looks good Writing MYMETA.yml and MYMETA.json svmloc was not found in the dynamic linker path, is there somewhere else we should check? [/usr/local/lib64] /usr/local/lib64 We're still not finding svmloc either in your dynamic linker path (/etc/ld.so.conf) or in /usr/local/lib64. Do you want to continue anyways? [Y/n] [Y] Y Checking if your kit is complete... Looks good Writing MYMETA.yml and MYMETA.json modhmm was not found in the dynamic linker path, is there somewhere else we should check? [/usr/local/lib64] /usr/local/lib64 We're still not finding modhmm either in your dynamic linker path (/etc/ld.so.conf) or in /usr/local/lib64. Do you want to continue anyways? [Y/n] [Y] Y Writing MYMETA.yml and MYMETA.json Generating a Unix-style Makefile Writing Makefile for Bio::Tools::PSort Writing MYMETA.yml and MYMETA.json Updating psort/bin/psort with path hints Making sclblast databases Building a new DB, current time: 05/05/2024 12:55:03 New DB name: /<>/psort/conf/analysis/sclblast/gramneg/sclblast New DB title: sclblast Sequence type: Protein Keep MBits: T Maximum file size: 10B Error: NCBI C++ Exception: T0 "c++/include/corelib/ncbidiag.hpp", line 2490: Error: (CSeqIdException::eFormat) ncbi::objects::CSeq_id::Set() - Malformatted ID 15596049[Extracellular] Program failed, try executing the command manually. Building a new DB, current time: 05/05/2024 12:55:04 New DB name: /<>/psort/conf/analysis/sclblast/grampos/sclblast New DB title: sclblast Sequence type: Protein Keep MBits: T Maximum file size: 10B BLAST Database creation error: Error: Duplicate seq_ids are found: LCL|145559529 Program failed, try executing the command manually. Building a new DB, current time: 05/05/2024 12:55:04 New DB name: /<>/psort/conf/analysis/sclblast/archaea/sclblast New DB title: sclblast Sequence type: Protein Keep MBits: T Maximum file size: 10B FASTA-Reader: Ignoring invalid residues at position(s): On line 46049: 38 FASTA-Reader: Ignoring invalid residues at position(s): On line 87237: 23 FASTA-Reader: Title ends with at least 50 valid amino acid characters. Was the sequence accidentally put in the title line? FASTA-Reader: Ignoring invalid residues at position(s): On line 87252: 4 FASTA-Reader: Ignoring invalid residues at position(s): On line 87263: 8 BLAST Database creation error: Error: Duplicate seq_ids are found: LCL|15596641 Program failed, try executing the command manually. Ready for make, next steps you must run: $ make $ make test $ make install RECOMMENDED: cp -r psort /usr/local/psortb PSortb will then be available at /usr/local/psortb/bin/psort or in your path depending on your configuration make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' # hack around the issue that configure injects wrong root dir
Bug#1070461: uhttpmock0: FTBFS: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration
Package: src:uhttpmock0 Version: 0.5.5-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -Dauto_features=disabled -Dintrospection=false cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 -Dauto_features=disabled -Dintrospection=false The Meson build system Version: 1.4.0 Source dir: /<> Build dir: /<>/obj-x86_64-linux-gnu Build type: native build Project name: uhttpmock Project version: 0.5.5 C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-24) 13.2.0") C linker for the host machine: cc ld.bfd 2.42 Host machine cpu family: x86_64 Host machine cpu: x86_64 Configuring uhm-version.h using configuration Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 Run-time dependency glib-2.0 found: YES 2.80.0 Run-time dependency gio-2.0 found: YES 2.80.0 Run-time dependency libsoup-2.4 found: YES 2.74.3 Compiler for C supports link arguments -Wl,--version-script,/<>/libuhttpmock/libuhttpmock.map: YES Configuring version.xml using configuration Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj) Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb) Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml) Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref) Build targets in project: 5 uhttpmock 0.5.5 User defined options auto_features : disabled buildtype : plain libdir: lib/x86_64-linux-gnu localstatedir : /var prefix: /usr sysconfdir: /etc wrap_mode : nodownload python.bytecompile: -1 introspection : false Found ninja-1.11.1 at /usr/bin/ninja make[1]: Leaving directory '/<>' dh_auto_build cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v [1/8] cc -Ilibuhttpmock/libuhttpmock-0.0.so.0.2.3.p -Ilibuhttpmock -I../libuhttpmock -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread '-DG_LOG_DOMAIN="libuhttpmock"' -MD -MQ libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-resolver.c.o -MF libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-resolver.c.o.d -o libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-resolver.c.o -c ../libuhttpmock/uhm-resolver.c [2/8] cc -Ilibuhttpmock/tests/server.p -Ilibuhttpmock/tests -I../libuhttpmock/tests -Ilibuhttpmock -I../libuhttpmock -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pthread '-DTEST_FILE_DIR="/<>/libuhttpmock/tests/"' '-DG_LOG_DOMAIN="libuhttpmock-tests"' -DLIBUHTTPMOCK_DISABLE_DEPRECATED -MD -MQ libuhttpmock/tests/server.p/server.c.o -MF libuhttpmock/tests/server.p/server.c.o.d -o libuhttpmock/tests/server.p/server.c.o -c ../libuhttpmock/tests/server.c [3/8] cc -Ilibuhttpmock/libuhttpmock-0.0.so.0.2.3.p -Ilibuhttpmock -I../libuhttpmock -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu99 -Wno-unused-parameter -Wno-missing-field-initializers -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread '-DG_LOG_DOMAIN="libuhttpmock"' -MD -MQ libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-server.c.o -MF libuhttpmock/libuhttpmock-0.0.so.0.2.3.p/uhm-server.c.o.d -o
Bug#1070458: gxneur: FTBFS: Package 'libpcre', required by 'xnconfig', not found
Package: src:gxneur
Version: 0.20.0-2.2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with autoreconf
dh_update_autotools_config
cp -an --reflink=auto config.guess
debian/.debhelper/bucket/files/8f48881bdc7f19036aeee45dd75b999aff372af0ac0c4b6a048e3d80d1162464.tmp
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
mv
debian/.debhelper/bucket/files/8f48881bdc7f19036aeee45dd75b999aff372af0ac0c4b6a048e3d80d1162464.tmp
debian/.debhelper/bucket/files/8f48881bdc7f19036aeee45dd75b999aff372af0ac0c4b6a048e3d80d1162464
cp -f /usr/share/misc/config.guess ./config.guess
cp -an --reflink=auto config.sub
debian/.debhelper/bucket/files/75d5d255a2a273b6e651f82eecfabf6cbcd8eaeae70e86b417384c8f4a58d8d3.tmp
cp: warning: behavior of -n is non-portable and may change in future; use
--update=none instead
mv
debian/.debhelper/bucket/files/75d5d255a2a273b6e651f82eecfabf6cbcd8eaeae70e86b417384c8f4a58d8d3.tmp
debian/.debhelper/bucket/files/75d5d255a2a273b6e651f82eecfabf6cbcd8eaeae70e86b417384c8f4a58d8d3
cp -f /usr/share/misc/config.sub ./config.sub
dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o
-type l -printf "symlink %p
" > debian/autoreconf.before
[... snipped ...]
cc1: warning: command-line option '-fno-rtti' is valid for C++/D/ObjC++ but not
for C
configure:11458: $? = 0
configure:11471: result: no
configure:11835: checking for gcc option to produce PIC
configure:11843: result: -fPIC -DPIC
configure:11851: checking if gcc PIC flag -fPIC -DPIC works
configure:11870: gcc -c -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection
-Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DPIC -DPIC
conftest.c >&5
configure:11874: $? = 0
configure:11887: result: yes
configure:11916: checking if gcc static flag -static works
configure:11945: result: yes
configure:11960: checking if gcc supports -c -o file.o
configure:11982: gcc -c -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection
-Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -o
out/conftest2.o conftest.c >&5
configure:11986: $? = 0
configure:12008: result: yes
configure:12016: checking if gcc supports -c -o file.o
configure:12064: result: yes
configure:12097: checking whether the gcc linker (/usr/bin/ld -m elf_x86_64)
supports shared libraries
configure:13371: result: yes
configure:13408: checking whether -lc should be explicitly linked in
configure:13417: gcc -c -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection
-Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
>&5
configure:13420: $? = 0
configure:13435: gcc -shared -fPIC -DPIC conftest.o -v -Wl,-soname -Wl,conftest -o conftest
2\>\&1 \| /usr/bin/grep -lc \>/dev/null 2\>\&1
configure:13438: $? = 0
configure:13452: result: no
configure:13612: checking dynamic linker characteristics
configure:14194: gcc -o conftest -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection
-Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro
-Wl,-rpath -Wl,/foo conftest.c >&5
configure:14194: $? = 0
configure:14445: result: GNU/Linux ld.so
configure:14567: checking how to hardcode library paths into programs
configure:14592: result: immediate
configure:15144: checking whether stripping libraries is possible
configure:15153: result: yes
configure:15195: checking if libtool supports shared libraries
configure:15197: result: yes
configure:15200: checking whether to build shared libraries
configure:15225: result: yes
configure:15228: checking whether to build static libraries
configure:15232: result: yes
configure:15272: checking for XNEURCONF
configure:15280: $PKG_CONFIG --exists --print-errors "xnconfig = 0.20.0"
Package libpcre was not found in the pkg-config search path.
Perhaps you should add the directory containing `libpcre.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libpcre', required by 'xnconfig', not found
configure:15283: $? = 1
configure:15298: $PKG_CONFIG --exists --print-errors "xnconfig = 0.20.0"
Package libpcre was not found in the pkg-config search path.
Perhaps you should add the directory containing `libpcre.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libpcre', required by 'xnconfig', not found
configure:15301: $? = 1
Package 'libpcre',
Bug#1070456: crystal: FTBFS: failing tests
Package: src:crystal
Version: 1.11.2+dfsg-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- release=1 verbose=1 progress=1 threads=2
CRYSTAL_CONFIG_PATH="lib:/usr/lib/crystal/lib" CRYSTAL_CACHE_DIR="/tmp/crystal"
interpreter=1
make -j2 "INSTALL=install --strip-program=true" release=1 verbose=1
progress=1 threads=2 CRYSTAL_CONFIG_PATH=lib:/usr/lib/crystal/lib
CRYSTAL_CACHE_DIR=/tmp/crystal interpreter=1
make[2]: Entering directory '/<>'
Using /usr/bin/llvm-config-17 [version= 17.0.6]g++ -c -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o
src/llvm/ext/llvm_ext.o src/llvm/ext/llvm_ext.cc -I/usr/lib/llvm-17/include -std=c++17
-fno-exceptions -funwind-tables -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
CRYSTAL_CONFIG_BUILD_COMMIT="" CRYSTAL_CONFIG_PATH=lib:/usr/lib/crystal/lib
SOURCE_DATE_EPOCH="1709233884" CRYSTAL_CONFIG_LIBRARY_PATH='$ORIGIN/../lib/crystal' ./bin/crystal
build -D strict_multi_assign -D preview_overload_order --release --progress --threads 2
--link-flags="-Wl,-z,relro" -o .build/crystal src/compiler/crystal.cr -D without_openssl -D
without_zlib -D use_pcre2
[1/13] Parse
[1/13] Parse
[... snipped ...]
"out"
"out"
"%w"
"%w"
"1 /2"
"1 /2"
"foo"
"foo"
"then"
"then"
"def //"
"def //"
"1 || 2"
"1 || 2"
"def +"
"def +"
"1 ! 2"
"1 ! 2"
"def []="
"def []="
"def >"
"def >"
"foo bar"
"foo bar"
"1 &-= 2"
"1 &-= 2"
"1 != 2"
"1 != 2"
"%(foo)"
"%(foo)"
"$1"
"$1"
"1 [] 2"
"1 [] 2"
"def =="
"def =="
"def >="
"def >="
"a /b/"
"a /b/"
"# foo\n# bar\n"
"# foo\n# bar\n"
"1 &*= 2"
"1 &*= 2"
"def <=>"
"def <=>"
"1 <= 2"
"1 <= 2"
"# foo"
"# foo"
"while"
"while"
"asm"
"asm"
"uninitialized"
"uninitialized"
"require"
"require"
"1 * 2"
"1 * 2"
"'a'"
"'a'"
"include"
"include"
"foo\nbar"
"foo\nbar"
"break"
"break"
"foo, bar = <<-FOO, <<-BAR\n foo\n FOO\n bar\n BAR"
"foo, bar = <<-FOO, <<-BAR\n foo\n FOO\n bar\n BAR"
"instance_alignof"
"instance_alignof"
"false"
"false"
"offsetof"
"offsetof"
"3.14"
"3.14"
"def !="
"def !="
#highlight!
"\"foo"
"\"foo"
"foo, bar = <<-FOO, <<-BAR\n foo"
"foo, bar = <<-FOO, <<-BAR\n foo"
"foo, bar = <<-FOO, <<-BAR\n foo\n FOO"
"foo, bar = <<-FOO, <<-BAR\n foo\n FOO"
"%i[foo"
"%i[foo"
"%w[foo"
"%w[foo"
"foo = bar(\"baz\#{PI + 1}\") # comment"
"foo = bar(\"baz\#{PI + 1}\") # comment"
Process::Status
#normal_exit?
#normal_exit?
#exit_signal
#exit_signal
#exit_reason
returns Interrupted
returns Interrupted
returns BadMemoryAccess
returns BadMemoryAccess
returns Aborted
returns Aborted
returns AccessViolation
returns AccessViolation
returns Normal
returns Normal
returns Breakpoint
returns Breakpoint
returns FloatException
returns FloatException
returns BadInstruction
returns BadInstruction
#signal_exit?
#signal_exit?
#exit_code
#exit_code
#success?
#success?
#inspect
with exit status
with exit status
with exit signal
with exit signal
#signal_exit? with signal code
#signal_exit? with signal code
equality
equality
#normal_exit? with signal code
#normal_exit? with signal code
#to_s
with exit signal
with exit signal
with exit status
with exit status
IO::Hexdump
read
prints hexdump
prints hexdump
write
prints hexdump
prints hexdump
WeakRef(T)
FinalizeState counts released objects
FinalizeState counts released objects
Referenced object should not be released
Referenced object should not be released
Unhandled exception in spawn: SSL_read: I/O error (OpenSSL::SSL::Error)
from src/io.cr:121:11 in 'unbuffered_read'
from src/io/buffered.cr:264:5 in 'peek'
from src/http/request.cr:180:15 in 'process'
from src/http/server.cr:506:5 in '->'
from src/fiber.cr:146:11 in 'run'
from ???
Caused by: SSL_read: Resource temporarily unavailable (RuntimeError)
should get dereferenced object
should get dereferenced object
Weak referenced object should be released if no other reference
Weak referenced object should be released if no other reference
should not crash with object in data section during GC
should not crash with object in data section during GC
should get
Bug#1070455: ayatana-indicator-display: FTBFS: Errors while running CTest
Package: src:ayatana-indicator-display
Version: 24.1.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DENABLE_TESTS=ON -DENABLE_COVERAGE=OFF
-DENABLE_LOMIRI_FEATURES=ON -DENABLE_COLOR_TEMP=ON
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DENABLE_TESTS=ON -DENABLE_COVERAGE=OFF
-DENABLE_LOMIRI_FEATURES=ON -DENABLE_COLOR_TEMP=ON ..
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
[... snipped ...]
2: member -> 'AddMatch'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body:
("type='signal',sender='org.freedesktop.Accounts',interface='org.freedesktop.DBus.Properties',member='PropertiesChanged',path='/org/freedesktop/Accounts/User924',arg0='org.freedesktop.DBus.Properties'",)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: RECEIVED D-Bus message (169 bytes)
2: Type:signal
2: Flags: no-reply-expected
2: Version: 0
2: Serial: 2
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'NameAcquired'
2: destination -> ':1.0'
2: sender -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body: (':1.0',)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Signal:
2: RECEIVED SIGNAL org.freedesktop.DBus.NameAcquired
2: on object /org/freedesktop/DBus
2: sent by name org.freedesktop.DBus
2:
2: GDBus-debug:Message:
2: SENT D-Bus message (281 bytes)
2: Type:method-call
2: Flags: none
2: Version: 0
2: Serial: 3
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'AddMatch'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body:
("type='signal',sender='org.freedesktop.Accounts',interface='org.freedesktop.DBus.Properties',path='/org/freedesktop/Accounts/User924'",)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: SENT D-Bus message (312 bytes)
2: Type:method-call
2: Flags: none
2: Version: 0
2: Serial: 4
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'AddMatch'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 's'
2: Body:
("type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0='org.freedesktop.Accounts'",)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: RECEIVED D-Bus message (72 bytes)
2: Type:method-return
2: Flags: no-reply-expected
2: Version: 0
2: Serial: 3
2: Headers:
2: reply-serial -> uint32 2
2: destination -> ':1.0'
2: sender -> 'org.freedesktop.DBus'
2: Body: ()
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: SENT D-Bus message (188 bytes)
2: Type:method-call
2: Flags: none
2: Version: 0
2: Serial: 5
2: Headers:
2: path -> objectpath '/org/freedesktop/DBus'
2: interface -> 'org.freedesktop.DBus'
2: member -> 'StartServiceByName'
2: destination -> 'org.freedesktop.DBus'
2: signature -> signature 'su'
2: Body: ('org.freedesktop.Accounts', uint32 0)
2: UNIX File Descriptors:
2: (none)
2:
2: GDBus-debug:Message:
2: RECEIVED D-Bus message (72 bytes)
2: Type:method-return
2: Flags: no-reply-expected
2:
Bug#1064486: rnp: FTBFS: Errors while running CTest
On 2024-05-04 Santiago Vila wrote: > found 1064486 0.16.3-1 > tags 1064486 + ftbfs bookworm trixie sid > thanks > El 20/4/24 a las 14:12, Andreas Metzler escribió: > > FWIW I also get testsuite errors on current sid on amd64 > > The following tests FAILED: > > 83 - rnp_tests.test_ffi_decrypt_wrong_mpi_bits (Failed) > > 90 - rnp_tests.test_ffi_security_profile (Failed) > > 174 - rnp_tests.test_key_add_userid (Failed) > > 254 - cli_tests-EncryptElgamal (Failed) > Hello. This is also happening in bookworm, I assume that for the same > underlying reason, > so I'm adding the bookworm version. [...] Hmm. Perhaps a timebomb, i.e. one of the keys used in the testsuite expired. cu Andreas
Bug#1070428: marked as done (bin86,elks-libc: copyright file missing (policy 12.5))
Your message dated Sun, 05 May 2024 16:21:03 + with message-id and subject line Bug#1070428: fixed in linux86 0.16.17-3.6 has caused the Debian Bug report #1070428, regarding bin86,elks-libc: copyright file missing (policy 12.5) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bin86,elks-libc Version: 0.16.17-3.5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts X-Debbugs-Cc: Bastian Germann Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information MISSING COPYRIGHT FILE: /usr/share/doc/bin86/copyright # ls -lad /usr/share/doc/bin86 drwxr-xr-x 3 root root 140 May 3 05:19 /usr/share/doc/bin86 # ls -la /usr/share/doc/bin86/ total 28 drwxr-xr-x 3 root root 140 May 3 05:19 . drwxr-xr-x 89 root root 1820 May 3 05:19 .. -rw-r--r-- 1 root root 670 Aug 31 2003 Contributors.gz -rw-r--r-- 1 root root 2656 Jan 24 2004 README.gz -rw-r--r-- 1 root root 4311 Feb 21 13:47 changelog.Debian.gz -rw-r--r-- 1 root root 10255 Jun 21 2004 changelog.gz drwxr-xr-x 2 root root60 May 3 05:19 examples MISSING COPYRIGHT FILE: /usr/share/doc/elks-libc/copyright # ls -lad /usr/share/doc/elks-libc drwxr-xr-x 2 root root 160 May 4 16:59 /usr/share/doc/elks-libc # ls -la /usr/share/doc/elks-libc/ total 36 drwxr-xr-x 2 root root 160 May 4 16:59 . drwxr-xr-x 89 root root 1820 May 4 16:59 .. -rw-r--r-- 1 root root 670 Aug 31 2003 Contributors.gz -rw-r--r-- 1 root root 2656 Jan 24 2004 README.gz -rw-r--r-- 1 root root 375 Apr 23 1996 README.libbsd.gz -rw-r--r-- 1 root root 1279 Jan 19 2002 README.libc.gz -rw-r--r-- 1 root root 4311 Feb 21 13:47 changelog.Debian.gz -rw-r--r-- 1 root root 10255 Jun 21 2004 changelog.gz cheers, Andreas --- End Message --- --- Begin Message --- Source: linux86 Source-Version: 0.16.17-3.6 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of linux86, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated linux86 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, 05 May 2024 15:26:06 + Source: linux86 Architecture: source Version: 0.16.17-3.6 Distribution: unstable Urgency: medium Maintainer: Juan Cespedes Changed-By: Bastian Germann Closes: 1070428 Changes: linux86 (0.16.17-3.6) unstable; urgency=medium . * Non-maintainer upload. * Move the package build directory. Closes: #1070428 Checksums-Sha1: 1c4f2ab208b15f260ee0f3f4229dbebc806cefa2 1625 linux86_0.16.17-3.6.dsc 920106e080fe2c347e4e02faf2b158f3b4fd9871 11612 linux86_0.16.17-3.6.debian.tar.xz 50412d16cc2a1b83291dbbde31ad1b98e1dd05e2 5467 linux86_0.16.17-3.6_source.buildinfo Checksums-Sha256: cd6a7272d09b3c1bd2b51bc1ec0ddb0081a2f28d7d08fdf995b450af1eb26f1f 1625 linux86_0.16.17-3.6.dsc 807aac3e7ff06282c7d63205875a8e2cb55c0deb3b8f7d0fe400f4ca4721f820 11612 linux86_0.16.17-3.6.debian.tar.xz e834dc9643a0d2a5d12e46f4737a8b17c991408f4b1f1f8950cec05c924c6c13 5467 linux86_0.16.17-3.6_source.buildinfo Files: 2bd643feb5a8820361f85b05a29d9f9b 1625 devel optional linux86_0.16.17-3.6.dsc c1ba61d4ebbae2828ebae63b0386c012 11612 devel optional linux86_0.16.17-3.6.debian.tar.xz d55b84a2d383fd87b14b68599029ad6e 5467 devel optional linux86_0.16.17-3.6_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmY3re4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFLoCDACqXKa7/GOdP9bAOVrR+XKGzGxXJPCwoZyz mb+ritwBYKgiw9EjSYEa6SUC9Tin76YNjt85nqYq8uttBYZ0yS7X6iXrL8sd3Qkj vObR3w9f20aI2areo5cxHWAqtOhtqZM0J1uPmG5u2B8quGpckRhsqG/TKhIid1Ua BeYmgZKvTi/I6FNkPwD3z6mC95chx1TURFre7q2X1ZxkZwDhmI38ZX2EJM726sVK oKYsG0iFsSwd6crq0JhXehc+AdhUS6qs3ACty5ivyerqFGMduivumre7LyPLq6D6
Bug#1070270: riseup-vpn: client no longer works due to cert verification problem
On Sat, May 04, 2024 at 08:59:19PM +0530, Nilesh Patra wrote: > Hi Matt, > > Quoting Matt Taggart: > > Package: riseup-vpn > > Version: 0.21.11+ds1-5+b1 > > Severity: grave > > > > When attempting to run the bookworm riseup-vpn package, it fails to > > connect to riseup's servers and gives the following output: > > > > 2024/05/01 18:21:23 Error fetching eip v3 > > json:https://api.black.riseup.net/3/config/eip-service.json > > > > My understanding is that this is due to the package failing to be able > > to verify the current LetsEncrypt cert that host is using. More details at > > > > https://0xacab.org/leap/bitmask-vpn/-/issues/768 > > > > (supposedly the current upstream snap has this fixed, but I haven't > > tried it) > > > > As this breaks what the package is supposed to do (at least when using > > riseup as provider, maybe there is a way to point it elsewhere?) I think > > this is grave. Also I think it might be a good candidate for being fixed > > in a stable release update. > > If I am not mistaken, as per the said, issue, it is fixed in the commit > referenced here, right? > > > https://0xacab.org/leap/bitmask-vpn/-/commit/14cf64b10a97c29688f252a7d9d3481c8484aa1d > > I tried this in my testing system and it seems I am able to connect to the VPN > with this patch applied. Can you confirm? I tried with this commit using my stable `.deb` in a fresh stable VM and it seems things are working. > Consequently, I also did some work to cherry-pick this and prepare a > stable-p-u > upload (not yet uploaded, will do after confirmation) and pushed my changes > at[1]. I have also compiled the `.deb` for stable and it is ready to be > consumed[2]. Do you think you could ask someone to check the same? > > Other than that, I also tried to update the package in unstable to the latest > version to fixup this properly. I was able to build it, pushed my changes > here[3] and the `.deb` is available here[4]. Again, if you/someone else could > try this, it'd be great. It is working for me on my debian/testing system. I asked a friend to check on their testing system and it seems to be working as well. I will proceed to upload these in a week or so. Until then I am awaiting your response. > I would have attemped the update much sooner but unfortunately an update with > 0xacab's gitlab broke my d/watch file and I did not notice a new version is > out > there sooner. > > I was thinking to go ahead with an upload, but there are a few things that I > would like to clarify before I do so (btw thanks to the maintainers for > committing a patch to use with qt6.4): > > 1. Why is the default provider set to "provider = bitmask" in > providers/vendor.conf? This leads to building the binary called bitmask-vpn > instead of riseup-vpn. Is there a thought of changing the binary name? > > In current stage it points to just dummy APIs and hence I overrode it in > d/rules > to build riseup-vpn instead. > > 2. In the vendor/gitlab.com/yawning/obfs4.git/ package, there are 3 license. > BSD-2-Clause, BSD-3-Clause and also GPL-3 for > vendor/gitlab.com/yawning/obfs4.git/internal/x25519ell2/x25519ell2.go - so > what > exactly is the exact license? Is it redistributable under all the three? (I > don't think so?) > > [1]: > https://salsa.debian.org/go-team/packages/riseup-vpn/-/tree/debian/bookworm-pu?ref_type=heads > [2]: https://people.debian.org/~nilesh/riseup-vpn-stable/ > [3]: > https://salsa.debian.org/go-team/packages/riseup-vpn/-/tree/debian/sid?ref_type=heads > [4]: https://people.debian.org/~nilesh/riseup-vpn-0.24.5/ > > Best, > Nilesh Best, Nilesh signature.asc Description: PGP signature
Bug#1070428: bin86,elks-libc: copyright file missing (policy 12.5)
I am uploading another NMU to fix this issue. Sorry about that.
See the attached debdiff.diff -Nru
linux86-0.16.17/debian/.debhelper/generated/bin86/installed-by-dh_installman
linux86-0.16.17/debian/.debhelper/generated/bin86/installed-by-dh_installman
---
linux86-0.16.17/debian/.debhelper/generated/bin86/installed-by-dh_installman
1970-01-01 00:00:00.0 +
+++
linux86-0.16.17/debian/.debhelper/generated/bin86/installed-by-dh_installman
2024-05-05 15:26:06.0 +
@@ -0,0 +1,8 @@
+./debian/man/ar86.1
+./debian/man/objdump86.1
+./debian/man/ar86.1
+./debian/man/objdump86.1
+./debian/man/ar86.1
+./debian/man/objdump86.1
+./debian/man/ar86.1
+./debian/man/objdump86.1
diff -Nru linux86-0.16.17/debian/changelog linux86-0.16.17/debian/changelog
--- linux86-0.16.17/debian/changelog2024-02-21 13:47:40.0 +
+++ linux86-0.16.17/debian/changelog2024-05-05 15:26:06.0 +
@@ -1,3 +1,10 @@
+linux86 (0.16.17-3.6) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Move the package build directory. Closes: #1070428
+
+ -- Bastian Germann Sun, 05 May 2024 15:26:06 +
+
linux86 (0.16.17-3.5) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru linux86-0.16.17/debian/rules linux86-0.16.17/debian/rules
--- linux86-0.16.17/debian/rules2024-02-21 13:47:40.0 +
+++ linux86-0.16.17/debian/rules2024-05-05 15:26:06.0 +
@@ -16,98 +16,95 @@
rm -f build
make realclean
rm -f ld/ar.h
- rm -rf debian/tmp*
+ rm -rf debian/bcc debian/bin86 debian/elks-libc debian/tmp
rm -f debian/files debian/substvars
binary:binary-indep binary-arch
binary-common: build
@test 0 = `id -u` || { echo "Error: not super-user"; exit 1; }
- rm -rf debian/tmp*
+ rm -rf debian/bcc debian/bin86 debian/elks-libc
install -d debian/tmp
make install DIST=`pwd`/debian/tmp
# exit 5
gzip -9f debian/tmp/usr/man/man?/*
binary-indep: binary-common
- install -d debian/tmp-elks-libc/DEBIAN
+ install -d debian/elks-libc/DEBIAN
# ``elks-libc'' specific things:
- install -d debian/tmp-elks-libc/usr/lib/bcc/kinclude
- mv debian/tmp/usr/lib/bcc/*.* debian/tmp-elks-libc/usr/lib/bcc
- mv debian/tmp/usr/lib/bcc/include
debian/tmp-elks-libc/usr/lib/bcc
- install -d debian/tmp-elks-libc/usr/lib/bcc/kinclude
- cp -a libc/kinclude/linuxmt
debian/tmp-elks-libc/usr/lib/bcc/kinclude/linuxmt
- cp -a libc/kinclude/arch
debian/tmp-elks-libc/usr/lib/bcc/kinclude/arch
- touch debian/tmp-elks-libc/usr/lib/bcc/*include/*/
- mv debian/tmp/usr/lib/bcc/i386 debian/tmp-elks-libc/usr/lib/bcc
+ install -d debian/elks-libc/usr/lib/bcc/kinclude
+ mv debian/tmp/usr/lib/bcc/*.* debian/elks-libc/usr/lib/bcc
+ mv debian/tmp/usr/lib/bcc/include debian/elks-libc/usr/lib/bcc
+ install -d debian/elks-libc/usr/lib/bcc/kinclude
+ cp -a libc/kinclude/linuxmt
debian/elks-libc/usr/lib/bcc/kinclude/linuxmt
+ cp -a libc/kinclude/arch
debian/elks-libc/usr/lib/bcc/kinclude/arch
+ touch debian/elks-libc/usr/lib/bcc/*include/*/
+ mv debian/tmp/usr/lib/bcc/i386 debian/elks-libc/usr/lib/bcc
#
- install -d debian/tmp-elks-libc/usr/share/doc/elks-libc
- cp -p Changes
debian/tmp-elks-libc/usr/share/doc/elks-libc/changelog
- cp -p Contributors README
debian/tmp-elks-libc/usr/share/doc/elks-libc/
- cp -p libc/README
debian/tmp-elks-libc/usr/share/doc/elks-libc/README.libc
- cp -p libbsd/README.HLU
debian/tmp-elks-libc/usr/share/doc/elks-libc/README.libbsd
- cp -p debian/changelog
debian/tmp-elks-libc/usr/share/doc/elks-libc/changelog.Debian
- install -d debian/tmp-elks-libc/usr/share/lintian/overrides
- cp -p debian/lintian.overrides
debian/tmp-elks-libc/usr/share/lintian/overrides/elks-libc
- gzip -9f debian/tmp-elks-libc/usr/share/doc/elks-libc/*
+ install -d debian/elks-libc/usr/share/doc/elks-libc
+ cp -p Changes debian/elks-libc/usr/share/doc/elks-libc/changelog
+ cp -p Contributors README
debian/elks-libc/usr/share/doc/elks-libc/
+ cp -p libc/README
debian/elks-libc/usr/share/doc/elks-libc/README.libc
+ cp -p libbsd/README.HLU
debian/elks-libc/usr/share/doc/elks-libc/README.libbsd
+ cp -p debian/changelog
debian/elks-libc/usr/share/doc/elks-libc/changelog.Debian
+ install -d debian/elks-libc/usr/share/lintian/overrides
+ cp -p debian/lintian.overrides
Processed: Re: Bug#1063026: helvum: Upcoming gtk update
Processing control commands:
> severity -1 serious
Bug #1063026 {Done: Jonas Smedegaard } [src:helvum] Upcoming gtk
update
Severity set to 'serious' from 'normal'
> tags -1 + ftbfs
Bug #1063026 {Done: Jonas Smedegaard } [src:helvum] Upcoming gtk
update
Added tag(s) ftbfs.
--
1063026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068755: docker.io: FTBFS: failing tests
I've been looking at this test failure, but remain puzzled. Basically, the source for this test is here: https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-2/engine/distribution/xfer/download_test.go/#L364-L429. This test is testing code in https://sources.debian.org/src/docker.io/20.10.25+dfsg1-2/engine/distribution/xfer/download.go which has only two external dependencies (golang-github-docker-distribution-dev) and (golang-github-sirupsen-logrus-dev). I've checked the build log of the previous build at https://buildd.debian.org/status/fetch.php?pkg=docker.io=amd64=20.10.25%2Bdfsg1-2%2Bb3=1704672923=0 and note that the same test passes in that build. This also uses the same package versions of golang-github-docker-distribution-dev==2.8.2+ds1-1 and golang-github-sirupsen-logrus-dev==1.9.0-1 I also note that the old build was using golang 1.21, and the FTBFS was introduced after upgrading unstable to golang 1.22. Shengjing, I believe you handled the recent update of the golang toolchain from 1.21 to 1.22. Have you seen similar "mysterious" test failures that resulted from using a newer golang compiler? I am considering just disabling this test, as the rest of the testsuite seem to pass, but I'm getting nervous that this wouldn't just paper over a real issue. Thanks, -- regards, Reinhard
Bug#1070225: marked as done (Built from wrong version (3.2 instead of 7.2))
Your message dated Sun, 05 May 2024 14:37:06 + with message-id and subject line Bug#1070172: fixed in gcovr 7.2+really-1.1 has caused the Debian Bug report #1070172, regarding Built from wrong version (3.2 instead of 7.2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1070172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcovr Version: 7.2-1 Severity: important installing the Debian package gcovr_7.2 actually install version 3.2 because gcovr_7.2.orig.tar.gz contains the wrong version of the source code. This broke my CI tests because some options were unsupported 10 years ago. --- End Message --- --- Begin Message --- Source: gcovr Source-Version: 7.2+really-1.1 Done: Guido Günther We believe that the bug you reported is fixed in the latest version of gcovr, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guido Günther (supplier of updated gcovr 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 May 2024 15:43:35 +0200 Source: gcovr Architecture: source Version: 7.2+really-1.1 Distribution: unstable Urgency: medium Maintainer: Wolfgang Silbermayr Changed-By: Guido Günther Closes: 1070172 Changes: gcovr (7.2+really-1.1) unstable; urgency=medium . * Non-maintainer upload. * Really use upstream version 7.2 (not 3.2 as was previously imported). In order to have a new upstream version we temporarily add `+really'. Closes: #1070172 * Drop patch. Readme isn't copied anymore * d/control: Add new build dependencies Checksums-Sha1: c47767262127109182261e9b12380a0fc1861ef6 1983 gcovr_7.2+really-1.1.dsc 029b82f226892d1b87e6bd384a5dea78cc553903 2800014 gcovr_7.2+really.orig.tar.gz d735c217b34948532242551e1fde15637a0d147e 8880 gcovr_7.2+really-1.1.debian.tar.xz 2b11899c9c6427c12e83099d36e430d3e94316e7 7027 gcovr_7.2+really-1.1_amd64.buildinfo Checksums-Sha256: 2f1b9ccd73357d3dc0f94ab0f21358b2c157eedfe7e43ff9e25fd7fa9525cf5c 1983 gcovr_7.2+really-1.1.dsc 17d3014b2dcfdfd155a8c38ef808ad6da11502cbb156e58172af259631e9b4ad 2800014 gcovr_7.2+really.orig.tar.gz 677e9ae1a31f566d805548c29ed0ae0e5173874f67b937cd2586f496fdfc 8880 gcovr_7.2+really-1.1.debian.tar.xz 802ca211f81f418038848bd8d1b8cfd02b9acc508427d326e3ccde98fa5bd81d 7027 gcovr_7.2+really-1.1_amd64.buildinfo Files: 4ff03e3124d21f55926495cd9aedf96e 1983 devel optional gcovr_7.2+really-1.1.dsc 453d0dafc91af6297781c0ccba7c79a7 2800014 devel optional gcovr_7.2+really.orig.tar.gz ca2a95caca654050b94f665ad74290c4 8880 devel optional gcovr_7.2+really-1.1.debian.tar.xz 524292e2d9c352374a0679947de57cee 7027 devel optional gcovr_7.2+really-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEY/bM35YinQkoayrDJb+GUkr8weMFAmYznIoACgkQJb+GUkr8 wePJ1A//WkRe5w2Z/F92maQeGbNyAmD16EcKCg/RoH8Ugbfz1K4y6R/LB2f6RNLm g0eY0vUwL7SbVnVMTU6bw5EgxFuFqWG6gf5Dcrv9bYURVC6XuMiE4v5F94R78/1z siKrBw9x6ORblZ5pMD9PK3/U/bH8cdaADNtoIfaJZwuWc8BI1jShPFFnJ4iBiFwc x9dNvlNlAKU27/EdqNSAGVpWQ+dhmg8RRKEZsRWlLWwiKbEVGhniNjiERWFO1Z0y zxn780As/V/vrsXkrl+YTFI828OKnNKcIZVoPx9s72YWaUKGa84t+QfUtZGb6nHv KCMkE20Io0jt31+JqxHU+hmry2al2vJ2PSdIJnqE590I22Y935NLk6sjEtKRn8K6 J12vv9F5X4CJjaKwHz6c2ZFTfZMPAlQmwF9MwBsQcmGS3XiHdlBRVfshYh2zHMxd 28rRGMsDO4IdeYHcqpwjW7u9IFQm8La+Td+yBla1BbyDXHts3ADFuIg3nANY5io2 /utOMbQi8quWO3CaPpZ5yLCTlLr92LxkSi5RcB9wg/yB8brlDUfYk+HoAcRXmCLB +NkmKRCVhNHlwgBhoovDUOM1oFNjCZabK7Hkzs36BuY8fvN6qHpQu9b7zCnM7ipY yzfIJ8CqL7baHTgghbdQlm+LviXfRQe67KEA1txMd1+ufwJnl34= =GP21 -END PGP SIGNATURE- pgp7bG3WGu7eC.pgp Description: PGP signature --- End Message ---
Bug#1070172: marked as done (Built from wrong version (3.2 instead of 7.2))
Your message dated Sun, 05 May 2024 14:37:06 +
with message-id
and subject line Bug#1070172: fixed in gcovr 7.2+really-1.1
has caused the Debian Bug report #1070172,
regarding Built from wrong version (3.2 instead of 7.2)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1070172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcovr
Version: 7.2-1
Severity: grave
Hi,
invoking gcovr 7.2 in an empty directory fails like
$ gcovr
--
GCC Code Coverage Report
Traceback (most recent call last):
File "/usr/bin/gcovr", line 1972, in
print_text_report(covdata)
File "/usr/bin/gcovr", line 822, in print_text_report
OUTPUT.write("Directory: "+options.root+"\n")
~^
TypeError: can only concatenate str (not "NoneType") to str
This makes meson think gcovr is not available, e.g.:
https://gitlab.gnome.org/World/Phosh/phosh-mobile-settings/-/jobs/3839480#L3265
I've marked this as grave as it breaks CI pipelines.
Cheers,
-- Guido
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64
Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 gcovr depends on:
ii python33.11.6-1
ii python3-pkg-resources 68.1.2-2
gcovr recommends no packages.
gcovr suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcovr
Source-Version: 7.2+really-1.1
Done: Guido Günther
We believe that the bug you reported is fixed in the latest version of
gcovr, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guido Günther (supplier of updated gcovr 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 May 2024 15:43:35 +0200
Source: gcovr
Architecture: source
Version: 7.2+really-1.1
Distribution: unstable
Urgency: medium
Maintainer: Wolfgang Silbermayr
Changed-By: Guido Günther
Closes: 1070172
Changes:
gcovr (7.2+really-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Really use upstream version 7.2 (not 3.2 as was previously imported).
In order to have a new upstream version we temporarily add `+really'.
Closes: #1070172
* Drop patch. Readme isn't copied anymore
* d/control: Add new build dependencies
Checksums-Sha1:
c47767262127109182261e9b12380a0fc1861ef6 1983 gcovr_7.2+really-1.1.dsc
029b82f226892d1b87e6bd384a5dea78cc553903 2800014 gcovr_7.2+really.orig.tar.gz
d735c217b34948532242551e1fde15637a0d147e 8880
gcovr_7.2+really-1.1.debian.tar.xz
2b11899c9c6427c12e83099d36e430d3e94316e7 7027
gcovr_7.2+really-1.1_amd64.buildinfo
Checksums-Sha256:
2f1b9ccd73357d3dc0f94ab0f21358b2c157eedfe7e43ff9e25fd7fa9525cf5c 1983
gcovr_7.2+really-1.1.dsc
17d3014b2dcfdfd155a8c38ef808ad6da11502cbb156e58172af259631e9b4ad 2800014
gcovr_7.2+really.orig.tar.gz
677e9ae1a31f566d805548c29ed0ae0e5173874f67b937cd2586f496fdfc 8880
gcovr_7.2+really-1.1.debian.tar.xz
802ca211f81f418038848bd8d1b8cfd02b9acc508427d326e3ccde98fa5bd81d 7027
gcovr_7.2+really-1.1_amd64.buildinfo
Files:
4ff03e3124d21f55926495cd9aedf96e 1983 devel optional gcovr_7.2+really-1.1.dsc
453d0dafc91af6297781c0ccba7c79a7 2800014 devel optional
gcovr_7.2+really.orig.tar.gz
ca2a95caca654050b94f665ad74290c4 8880 devel optional
gcovr_7.2+really-1.1.debian.tar.xz
524292e2d9c352374a0679947de57cee 7027 devel optional
gcovr_7.2+really-1.1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
Bug#1069789: test_bluetooth_hidpp_mouse autopkgtest fails
Control: severity -1 important Seems to pass pretty reliably on debci, thus downgrading to important. https://ci.debian.net/packages/u/upower/ Regards, Michael On Wed, 24 Apr 2024 23:34:48 +0500 Andrey Rakhmatullin wrote: Package: upower Version: 1.90.3-1 Severity: serious Control: forwarded -1 https://gitlab.freedesktop.org/upower/upower/-/issues/228 Control: tags -1 + upstream https://ci.debian.net/packages/u/upower/unstable/amd64/45053064/ 217s == 217s ERROR: test_bluetooth_hidpp_mouse (__main__.Tests.test_bluetooth_hidpp_mouse) 217s Logitech Bluetooth LE mouse with HID++ kernel support 217s -- 217s Traceback (most recent call last): 217s File "/usr/libexec/upower/integration-test.py", line 2337, in test_bluetooth_hidpp_mouse 217s self.assertEqual(self.get_dbus_dev_property(bat0_up, 'Model'), alias) 217s 217s File "/usr/libexec/upower/integration-test.py", line 273, in get_dbus_dev_property 217s return self.dbus.call_sync(UP, device, 217s^^^ 217s gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/freedesktop/UPower/devices/mouse_dev_11_22_33_44_AA_BB” (19) -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 upower depends on: ii dbus 1.14.10-4+b1 ii libc6 2.37-18 ii libglib2.0-0t642.78.4-7 ii libgudev-1.0-0 238-5 ii libimobiledevice6 1.3.0-7.1+b1 ii libplist3 2.2.0-7+b1 ii libupower-glib31.90.3-1 ii udev 255.4-1+b1 Versions of packages upower recommends: ii polkitd 124-2 upower suggests no packages. -- debconf-show failed OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Re: test_bluetooth_hidpp_mouse autopkgtest fails
Processing control commands: > severity -1 important Bug #1069789 [upower] test_bluetooth_hidpp_mouse autopkgtest fails Severity set to 'important' from 'serious' -- 1069789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070450: qm-dsp: autopkgtest regression on arm64, ppc64el and s390x
Source: qm-dsp
Version: 1.7.1-8
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
qm-dsp currently fails to migrate due to autopkgtest failures on arm64,
ppc64el and s390x.
https://ci.debian.net/packages/q/qm-dsp/testing/arm64/46236204/
112s for t in test-mathutilities test-window test-fft test-pvoc test-resampler
test-medianfilter; do echo "Running $t"; valgrind -q ./"$t" || exit 1; done
112s Running test-mathutilities
114s Running 11 test cases...
114s
114s ␛[1;32;49m*** No errors detected
114s ␛[0;39;49mRunning test-window
115s Running 9 test cases...
115s
115s ␛[1;32;49m*** No errors detected
115s ␛[0;39;49mRunning test-fft
116s Running 21 test cases...
116s
116s ␛[1;32;49m*** No errors detected
117s ␛[0;39;49mRunning test-pvoc
118s Running 2 test cases...
118s TestPhaseVocoder.cpp(188): ␛[1;31;49merror: in "TestFFT/overlapping":
absolute value of phase[cmp_i] - phaseExpected2[cmp_i]{1.5297327490291485e-07}
exceeds 9.9995e-08␛[0;39;49m
118s TestPhaseVocoder.cpp(191): ␛[1;31;49merror: in "TestFFT/overlapping":
absolute value of unw[cmp_i] - unwExpected2[cmp_i]{1.5297327493613011e-07}
exceeds 9.9995e-08␛[0;39;49m
118s
118s ␛[1;31;49m*** 2 failures are detected in the test module "Master Test
Suite"
118s ␛[0;39;49mmake: *** [Makefile:13: all] Error 1
I've added a hint to get the t64 changes into testing.
Cheers
--
Sebastian Ramacher
Bug#999922: marked as done (xneur: depends on obsolete pcre3 library)
Your message dated Sun, 05 May 2024 13:36:39 + with message-id and subject line Bug#22: fixed in xneur 0.20.0-3.2 has caused the Debian Bug report #22, regarding xneur: depends on obsolete pcre3 library 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.) -- 22: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xneur Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: xneur Source-Version: 0.20.0-3.2 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of xneur, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated xneur 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, 05 May 2024 15:23:15 +0200 Source: xneur Architecture: source Version: 0.20.0-3.2 Distribution: unstable Urgency: medium Maintainer: Alexander GQ Gerasiov Changed-By: Sebastian Ramacher Closes: 22 Changes: xneur (0.20.0-3.2) unstable; urgency=medium . * Non-maintainer upload. * debian/patches: Fix pkgconfig file after porting to PCRE2 (Closes: #22) Checksums-Sha1: 94ff4b64acae8eb368f426004f6af02e75e2e012 1465 xneur_0.20.0-3.2.dsc 29064c075fa23eec71c56116099698b0c29e78d0 11580 xneur_0.20.0-3.2.debian.tar.xz 475637956c1334b7a5c59bca8a3ade67855077c5 11359 xneur_0.20.0-3.2_amd64.buildinfo Checksums-Sha256: 3ce85e769fbf6bf983f33833cebb4a60c24526f2205096b9c323b88c58db67c4 1465 xneur_0.20.0-3.2.dsc fc8fc703fe810dbf69d9a98732e52c6a4cb7dd1ea739f5cd9669257833e1b4f7 11580 xneur_0.20.0-3.2.debian.tar.xz 6332ccd848e26a5208b5b1b08d502611d5408c3e9740baf648811a24df81e962 11359 xneur_0.20.0-3.2_amd64.buildinfo Files: 5f075b7b3f5641529b1760cc8546b374 1465 x11 optional xneur_0.20.0-3.2.dsc 86e919a4a190a78094ea57b55673f6ec 11580 x11 optional xneur_0.20.0-3.2.debian.tar.xz 41583e501e81d62595beebb6c5cd772f 11359 x11 optional xneur_0.20.0-3.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZjeJmwAKCRAhk2s2YA/N ibh2AQC8pjGPnepaJWrvjgpeAa4PlsILjVuqQQs/7kr9FskwUgD/TZwFkH+JqnGf wzmZxHERxsPCcscIeRsHAmn9aIgJhgE= =hRb2 -END PGP SIGNATURE- pgpnd5tKGMime.pgp Description: PGP signature --- End Message ---
Bug#1063948: marked as done (ipyparallel: autopkgtest regression with pytest 8)
Your message dated Sun, 05 May 2024 13:35:48 + with message-id and subject line Bug#1063948: fixed in ipyparallel 8.8.0-1~exp1 has caused the Debian Bug report #1063948, regarding ipyparallel: autopkgtest regression with pytest 8 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.) -- 1063948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ipyparallel Version: 7.1.0-5 Severity: important User: debian-pyt...@lists.debian.org Usertags: pytest-8 Dear maintainer, your package has a autopkgtest regression with pytest 8. Typically, packages will start failing if they - have deprecation warnings of type PytestRemovedIn8Warning, or - assume a particular pytest stdout/stderr output which might have changed, or - rely on implementation details of the pytest test collector, in particular the pytest.Package class, which has been redesigned for pytest 8. Please refer to the upstream changelog [1] for a complete list of breaking changes and the pytest (pseudo-)excuses [2] related to your package for details of the regression. It is possible that the autopkgtest regression is not directly caused by ipyparallel, but by one of its dependencies. In that case, feel free to reassign the bug and mark your package as affected, but do not close the bug until the autopkgtest passes. Cheers Timo [1] https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023- 12-30 [2] https://qa.debian.org/excuses.php?experimental=1=pytest --- End Message --- --- Begin Message --- Source: ipyparallel Source-Version: 8.8.0-1~exp1 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of ipyparallel, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated ipyparallel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 May 2024 18:00:12 -0300 Source: ipyparallel Architecture: source Version: 8.8.0-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Python Team Changed-By: Emmanuel Arias Closes: 1061744 1063948 Changes: ipyparallel (8.8.0-1~exp1) experimental; urgency=medium . [ Alexandre Detiste ] * Team upload. * New upstream version 8.8.0 (Closes: #1063948, #1061744) * wrap-and-sort -sa * disable JS extension * use new dh-sequence-python3 * update build dependencies: - python3-mock + python3-myst-nb + python3-myst-parser + python3-pydata-sphinx-theme + python3-sphinxext-rediraffe deps . [ Emmanuel Arias ] * d/salsa-ci.yml: Change release variable to experimental. * d/control: Add pybuild-plugin-pyproject as B-Depends. * d/control: Remove python3-setuptool from build dendencies, it was removed by upstream. - Add python3-hatchling and python3-entrypoints as build dependencies. * d/rules: Use dh_auto_test instead of run pytest directly. - Ignore RuntimeWarnings and DeprecationWarnings during the tests. * d/rules: Remove override_dh_auto_test it is not longer needed. * d/control: Remove python3-pytest-cov from build dependency it not needed. * d/rules: Add PYBUILD_AFTER_INSTALL to move configuraiton files from /usr/etc/jupyter to /etc/jupyter. * d/control: Bump Standards-Version to 4.7.0 (from 4.6.0; no further changes needed). Checksums-Sha1: 0833e3a3d41ff80b76e6a015bf491bf7abc84b93 3086 ipyparallel_8.8.0-1~exp1.dsc 50aa6237597573e8d13e6ca9a9fe6d7301e20de4 6792438 ipyparallel_8.8.0.orig.tar.gz cce5a9aa677c2139ca9a20288f39bbcca7e398a1 11088 ipyparallel_8.8.0-1~exp1.debian.tar.xz ed3e58c57b3bb1dfcc39c26c797978aa1ee7bbfd 14543 ipyparallel_8.8.0-1~exp1_amd64.buildinfo Checksums-Sha256: ea52e9160146e0571977a531e5319da9d5afd681fc5a2c36478122e63f6da2c3 3086 ipyparallel_8.8.0-1~exp1.dsc 0f608ce256b739c5e9dcde45ae4d1ca55b6806dc2cb6f286190b3bdc07d2f398 6792438 ipyparallel_8.8.0.orig.tar.gz 8e5e3560081774fc76807f9167c154f26f74a541d9b43e93422fb84c747a5c21 11088 ipyparallel_8.8.0-1~exp1.debian.tar.xz
Bug#1061744: marked as done (ipyparallel ftbfs with Python 3.12 as default)
Your message dated Sun, 05 May 2024 13:35:48 +
with message-id
and subject line Bug#1061744: fixed in ipyparallel 8.8.0-1~exp1
has caused the Debian Bug report #1061744,
regarding ipyparallel ftbfs with Python 3.12 as default
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.)
--
1061744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipyparallel
Version: 7.1.0-5
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
With python3-defaults from experimental, the package fails to build:
[...]
=== FAILURES
===
_ test_disambiguate_ip
_
warn_mock =
@mock.patch('warnings.warn')
def test_disambiguate_ip(warn_mock):
# garbage in, garbage out
assert util.disambiguate_ip_address('garbage') == 'garbage'
assert util.disambiguate_ip_address('0.0.0.0',
socket.gethostname()) == localhost()
wontresolve = 'this.wontresolve.dns'
assert util.disambiguate_ip_address('0.0.0.0', wontresolve) ==
wontresolve
assert warn_mock.called_once_with(
'IPython could not determine IPs for {}: '
'[Errno -2] Name or service not known'.format(wontresolve),
RuntimeWarning,
> )
ipyparallel/tests/test_util.py:21:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = , name =
'called_once_with'
def __getattr__(self, name):
if name in {'_mock_methods', '_mock_unsafe'}:
raise AttributeError(name)
elif self._mock_methods is not None:
if name not in self._mock_methods or name in _all_magics:
raise AttributeError("Mock object has no attribute %r"
% name)
elif _is_magic(name):
raise AttributeError(name)
if not self._mock_unsafe and (not self._mock_methods or name
not in self._mock_methods):
if name.startswith(('assert', 'assret', 'asert', 'aseert',
'assrt')) or name in _ATTRIB_DENY_LIST:
> raise AttributeError(
f"{name!r} is not a valid assertion. Use a spec "
f"for the mock if {name!r} is meant to be an
attribute.")
E AttributeError: 'called_once_with' is not a valid
assertion. Use a spec for the mock if 'called_once_with' is meant to be
an attribute.. Did you mean: 'assert_called_once_with'?
/usr/lib/python3.12/unittest/mock.py:663: AttributeError
--- End Message ---
--- Begin Message ---
Source: ipyparallel
Source-Version: 8.8.0-1~exp1
Done: Emmanuel Arias
We believe that the bug you reported is fixed in the latest version of
ipyparallel, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Arias (supplier of updated ipyparallel package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 04 May 2024 18:00:12 -0300
Source: ipyparallel
Architecture: source
Version: 8.8.0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Emmanuel Arias
Closes: 1061744 1063948
Changes:
ipyparallel (8.8.0-1~exp1) experimental; urgency=medium
.
[ Alexandre Detiste ]
* Team upload.
* New upstream version 8.8.0 (Closes: #1063948, #1061744)
* wrap-and-sort -sa
* disable JS extension
* use new dh-sequence-python3
* update build dependencies:
- python3-mock
+ python3-myst-nb
+ python3-myst-parser
+ python3-pydata-sphinx-theme
+ python3-sphinxext-rediraffe deps
.
[ Emmanuel Arias ]
* d/salsa-ci.yml: Change release variable to experimental.
* d/control: Add pybuild-plugin-pyproject as B-Depends.
* d/control: Remove python3-setuptool from build dendencies, it was removed
by upstream.
- Add python3-hatchling and python3-entrypoints as build dependencies.
* d/rules: Use dh_auto_test instead of run pytest directly.
- Ignore RuntimeWarnings
Bug#1070447: sdpa: dependency generation does not account for t64 changes
Source: sdpa
Version: 7.3.16+dfsg-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Dependencies on libmumps-seq are produced using ${mumps-seq:Version}
which does not include the changes from the t64 transition. Please adopt
the dependency generation accordingly.
Cheers
--
Sebastian Ramacher
Bug#999922: xneur: diff for NMU version 0.20.0-3.2
Dear maintainer, I've prepared an NMU for xneur (versioned as 0.20.0-3.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru xneur-0.20.0/debian/changelog xneur-0.20.0/debian/changelog --- xneur-0.20.0/debian/changelog 2024-04-24 23:52:01.0 +0200 +++ xneur-0.20.0/debian/changelog 2024-05-05 15:23:15.0 +0200 @@ -1,3 +1,11 @@ +xneur (0.20.0-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches: Fix pkgconfig file after porting to PCRE2 (Closes: +#22) + + -- Sebastian Ramacher Sun, 05 May 2024 15:23:15 +0200 + xneur (0.20.0-3.1) unstable; urgency=medium [ Andreas Rönnquist ] diff -Nru xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch --- xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch 2024-04-24 23:44:13.0 +0200 +++ xneur-0.20.0/debian/patches/0004-Port-to-PCRE2.patch 2024-05-05 15:20:35.0 +0200 @@ -9,11 +9,9 @@ lib/misc/regexp.c | 50 -- 2 files changed, 33 insertions(+), 19 deletions(-) -diff --git a/configure.ac b/configure.ac -index 5cae4f4..dcb6207 100644 --- a/configure.ac +++ b/configure.ac -@@ -143,7 +143,7 @@ if test "x$with_debug" == "xyes"; then +@@ -143,7 +143,7 @@ AC_DEFINE(WITH_DEBUG, 1, [Define if you want debug support]) fi @@ -22,8 +20,6 @@ AC_ARG_WITH(keylogger, [ --without-keylogger Compile without keylogger function]) if test "x$with_keylogger" != "xno"; then -diff --git a/lib/misc/regexp.c b/lib/misc/regexp.c -index 728036e..aea6029 100644 --- a/lib/misc/regexp.c +++ b/lib/misc/regexp.c @@ -21,7 +21,8 @@ @@ -112,3 +108,14 @@ return TRUE; } +--- a/xnconfig.pc.in b/xnconfig.pc.in +@@ -5,7 +5,7 @@ + + Name: xnconfig + Description: XNeur config library +-Requires: libpcre ++Requires: libpcre2 + Version: @VERSION@ + Libs: -L@libdir@ -lxnconfig @PCRE_LIBS@ @LDFLAGS@ @ADDITIONAL_LIBS@ + Cflags: -I@includedir@
Bug#1070446: rocm-hipamd: arm64 FTBFS with glibc 2.38
Source: rocm-hipamd Version: 5.7.1-3 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], rocm-hipamd FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider it a bug in glibc. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/rocm-hipamd.html [2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909 In file included from /tmp/hip_pch.724714/hip_pch.h:1: In file included from /build/reproducible-path/rocm-hipamd-5.7.1/hip/include/hip/hip_runtime.h:62: In file included from /build/reproducible-path/rocm-hipamd-5.7.1/hipamd/include/hip/amd_detail/amd_hip_runtime.h:76: In file included from /usr/lib/gcc/aarch64-linux-gnu/13/../../../../include/c++/13/cmath:47: In file included from /usr/include/math.h:40: /usr/include/aarch64-linux-gnu/bits/math-vector.h:40:9: error: unknown type name '__SVFloat32_t' 40 | typedef __SVFloat32_t __sv_f32_t; | ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:41:9: error: unknown type name '__SVFloat64_t' 41 | typedef __SVFloat64_t __sv_f64_t; | ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:42:9: error: unknown type name '__SVBool_t' 42 | typedef __SVBool_t __sv_bool_t; | ^ 3 errors generated when compiling for . CMake Error at hipamd/src/CMakeLists.txt:182 (message): Failed to embed PCH
Bug#999922: xneur: depends on obsolete pcre3 library
Control: reopen -1 On 2024-04-25 00:50:36 +0200, Andreas Rönnquist wrote: > > Hi! > > I intend to nmu xneur shortly, fixing the two RC bugs (#22, > #1037902, which has been open 7 months and 2,5 years) using the fixes > that have been posted to the bugs, to help the progress of the time_t > transition. See the attached debdiff for the full list of changes. The fixes were incomplete. xnconfig.pc also needs to point to libpcre2 instead of libpcre. Uploading a fix in a bit. Cheers -- Sebastian Ramacher
Processed: Re: Bug#999922: xneur: depends on obsolete pcre3 library
Processing control commands:
> reopen -1
Bug #22 {Done: Andreas Rönnquist } [src:xneur] xneur:
depends on obsolete pcre3 library
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions xneur/0.20.0-3.1.
--
22: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070444: cxref: arm64 FTBFS with glibc 2.38
Source: cxref
Version: 1.6e-5
Severity: serious
Tags: ftbfs trixie sid
Hi Maintainer
As can be seen in reproducible builds [1], cxref FTBFS on arm64 with
glibc 2.38. I've copied what I hope is the relevant part of the log
below.
A bug was filed against glibc [2], but it seems glibc upstream do not
consider it a bug in glibc.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/cxref.html
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909
../src/cxref -D_Float128='long double' -O. -NREADME-TMP -xref README.c
/usr/include/aarch64-linux-gnu/bits/math-vector.h:30: cxref: syntax error
The previous 10, current and next 10 symbols are:
-10 | 258 : IDENTIFIER : __overflow
-9 | 40 : '(' : (
-8 | 259 :TYPE_NAME : FILE
-7 | 42 : '*' : *
-6 | 44 : ',' : ,
-5 | 296 : INT : int
-4 | 41 : ')' : )
-3 | 59 : ';' : ;
-2 | 285 : TYPEDEF : typedef
-1 | 258 : IDENTIFIER : __Float32x4_t
0 | 258 : IDENTIFIER : __f32x4_t
1 | 59 : ';' : ;
2 | 285 : TYPEDEF : typedef
3 | 258 : IDENTIFIER : __Float64x2_t
4 | 258 : IDENTIFIER : __f64x2_t
5 | 59 : ';' : ;
6 | 285 : TYPEDEF : typedef
7 | 258 : IDENTIFIER : __SVFloat32_t
8 | 258 : IDENTIFIER : __sv_f32_t
9 | 59 : ';' : ;
10 | 285 : TYPEDEF : typedef
Bug#1070443: aspectc++: arm64 FTBFS with glibc 2.38
Source: aspectc++ Version: 1:2.3+git20230726-1 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], aspectc++ FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider it a bug in glibc. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/aspectc++.html [2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909 Weaving aspects into PreExprParser.cc... Weaving aspects into PreParser.cc... Generating library header files... In file included from cpp/PreExprParser.lem:56: In file included from /usr/include/c++/13/math.h:36: In file included from /usr/include/c++/13/cmath:47: In file included from /usr/include/math.h:40: /usr/include/aarch64-linux-gnu/bits/math-vector.h:30:9: error: unknown type name '__Float32x4_t' typedef __Float32x4_t __f32x4_t; ^ /usr/include/aarch64-linux-gnu/bits/math-vector.h:31:9: error: unknown type name '__Float64x2_t' typedef __Float64x2_t __f64x2_t; ^
Bug#1066549: marked as done (geki2: FTBFS: misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ [-Werror=implicit-function-declaration])
Your message dated Sun, 05 May 2024 13:19:41 + with message-id and subject line Bug#1066549: fixed in geki2 2.0.8-1 has caused the Debian Bug report #1066549, regarding geki2: FTBFS: misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ [-Werror=implicit-function-declaration] 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.) -- 1066549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: geki2 Version: 2.0.3-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"geki2-KXL\" > -DVERSION=\"2.0.3\" -DHAVE_LIBKXL=1 -DHAVE_LIBKXL=1 -DHAVE_SYS_TYPES_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 > -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 > -DHAVE_UNISTD_H=1 -DDATA_PATH=\"/usr/share/games/geki2/data\" > -DBMP_PATH=\"/usr/share/games/geki2/bmp\" > -DWAV_PATH=\"/usr/share/games/geki2/wav\" -DTITLE=\"geki2-KXL\ 2.0.3\" -I. > -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c misc.c > misc.c: In function ‘ClearAndGameOver’: > misc.c:127:7: error: implicit declaration of function ‘ScoreRanking’ > [-Werror=implicit-function-declaration] > 127 | ScoreRanking(); > | ^~~~ > misc.c:132:5: error: implicit declaration of function ‘UnLoadStageData’; did > you mean ‘LoadStageData’? [-Werror=implicit-function-declaration] > 132 | UnLoadStageData(); > | ^~~ > | LoadStageData > cc1: some warnings being treated as errors > make[2]: *** [Makefile:233: misc.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/geki2_2.0.3-10_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: geki2 Source-Version: 2.0.8-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of geki2, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated geki2 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, 05 May 2024 14:59:28 +0200 Source: geki2 Architecture: source Version: 2.0.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Alexandre Detiste Closes: 1053095 1066549 Changes: geki2 (2.0.8-1) unstable; urgency=medium . * New upstream version 2.0.8 (Closes: #1053095, #1066549) * Adopt package * Update watch file * Change homepage to fork at https://github.com/Quipyowert2/geki2 * Bump debhelper from old 10 to 13. * Set debhelper-compat version in Build-Depends. * Update standards version to
Bug#1070441: cmbc: arm64 FTBFS with glibc 2.38
Source: cbmc Version: 5.95.1-4 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], cbmc FTBFS on arm64 with glibc 2.38. I've copied what I hope is the relevant part of the log below. A bug was filed against glibc [2], but it seems glibc upstream do not consider it a bug in glibc. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/cbmc.html [2] https://sourceware.org/bugzilla/show_bug.cgi?id=30909 [31mTests failed [0m 10 of 1114 tests failed, 60 tests skipped Failed test: Float-div2 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-div3 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-equality2 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: (Starting CEGAR Loop|VCC\(s\), 0 remaining after simplification$) [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] ^EXIT=0$ [FAILED] Failed test: Float-flags-no-simp1 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-flags-simp1 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float-no-simp9 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: Float21 CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0 Failed test.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] Failed test: float-nan-check CBMC version 5.95.1 (cbmc-5.95.1) 64-bit arm64 linux Parsing main.c file /usr/include/aarch64-linux-gnu/bits/math-vector.h line 30: syntax error before '__f32x4_t' PARSING ERROR EXIT=6 SIGNAL=0
Bug#1070438: liblirc-dev: unhandled symlink to directory conversion: /usr/include/lirc/media
Package: liblirc-dev Version: 0.10.2-0.8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: bookworm -> trixie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 0m35.3s ERROR: installs objects over existing directory symlinks: /usr/include/lirc/media/lirc.h (liblirc-dev) != /usr/include/lirc/include/media/lirc.h (?) /usr/include/lirc/media -> include/media cheers, Andreas liblirc-dev_0.10.2-0.8.log.gz Description: application/gzip
Processed: Re: Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multipli
Processing commands for cont...@bugs.debian.org: > retitle 1069357 cpp-httplib: FTBFS: Test > SSLClientServerTest.ClientCertPresent fails with timeout Bug #1069357 [src:cpp-httplib] cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-args=--gtest_filter=-\*_Online returned exit code 1 Changed Bug title to 'cpp-httplib: FTBFS: Test SSLClientServerTest.ClientCertPresent fails with timeout' from 'cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-args=--gtest_filter=-\*_Online returned exit code 1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-arg
retitle 1069357 cpp-httplib: FTBFS: Test SSLClientServerTest.ClientCertPresent fails with timeout thanks El 26/4/24 a las 6:59, Julian Gilbey escribió: It looks like it's just that arm64 is slow (as are several other archs). Note: I can reproduce this on amd64 as well (using m6a.large instances from AWS, not really supposed to be "slow"). If anybody needs access to such instances to reproduce this, please contact me privately. Thanks.
Bug#1055297: marked as done (ruby3.1: fails to build against glibc 2.38)
Your message dated Sun, 5 May 2024 12:26:40 +0200 with message-id and subject line Re: Bug#1055297: ruby3.1: fails to build against glibc 2.38 has caused the Debian Bug report #1055297, regarding ruby3.1: fails to build against glibc 2.38 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.) -- 1055297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby3.1 Version: 3.1.2-7 Severity: important Tags: patch Hello, ruby3.1 fails to build against glibc 2.38: dpkg-gensymbols -plibruby3.1 -Idebian/libruby3.1.symbols -Pdebian/libruby3.1 -edebian/libruby3.1/usr/lib/x86_64-gnu/libruby-3.1.so.3.1.2 dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libruby3.1/DEBIAN/symbols doesn't match completely debian/libruby3.1.symbols --- debian/libruby3.1.symbols (libruby3.1_3.1.2-7_hurd-amd64) +++ dpkg-gensymbols5L9SYx 2023-11-03 17:57:31.0 + [...] @@ -1818,5 +1818,5 @@ ruby_xrealloc2@Base 3.1.0~preview1 ruby_xrealloc@Base 3.1.0~preview1 setproctitle@Base 3.1.0~preview1 - strlcat@Base 3.1.0~preview1 - strlcpy@Base 3.1.0~preview1 +#MISSING: 3.1.2-7# strlcat@Base 3.1.0~preview1 +#MISSING: 3.1.2-7# strlcpy@Base 3.1.0~preview1 strlcat and strlcpy were indeed added to glibc in version 2.38, so it's not surprising that ruby3.1 doesn't define its internal versions any more, and the attached patch can probably be applied? Samuel -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 ruby3.1 depends on: ii libc6 2.37-12 ii libcrypt1 1:4.4.36-2 ii libgmp10 2:6.3.0+dfsg-2 ii libruby3.13.1.2-7 ii rubygems-integration 1.18 ii zlib1g1:1.2.13.dfsg-3 Versions of packages ruby3.1 recommends: ii fonts-lato2.015-1 ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 ruby3.1 suggests no packages. -- no debconf information -- Samuel --- Pour une évaluation indépendante, transparente et rigoureuse ! Je soutiens la Commission d'Évaluation de l'Inria. --- debian/libruby3.1.symbols.original 2023-11-03 18:01:01.0 + +++ debian/libruby3.1.symbols 2023-11-03 18:01:23.0 + @@ -1818,5 +1818,5 @@ ruby_xrealloc2@Base 3.1.0~preview1 ruby_xrealloc@Base 3.1.0~preview1 setproctitle@Base 3.1.0~preview1 - strlcat@Base 3.1.0~preview1 - strlcpy@Base 3.1.0~preview1 + (optional)strlcat@Base 3.1.0~preview1 + (optional)strlcpy@Base 3.1.0~preview1 --- End Message --- --- Begin Message --- Version: 3.1.2-8 Hi again, On 2024-05-05 12:18, Aurelien Jarno wrote: > control: severity -1 serious > > Hi, > > On 2023-11-03 19:45, Samuel Thibault wrote: > > Package: ruby3.1 > > Version: 3.1.2-7 > > Severity: important > > Tags: patch > > > > Hello, > > > > ruby3.1 fails to build against glibc 2.38: > > > > dpkg-gensymbols -plibruby3.1 -Idebian/libruby3.1.symbols > > -Pdebian/libruby3.1 > > -edebian/libruby3.1/usr/lib/x86_64-gnu/libruby-3.1.so.3.1.2 > > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > > file: see diff output below > > dpkg-gensymbols: warning: debian/libruby3.1/DEBIAN/symbols doesn't match > > completely debian/libruby3.1.symbols > > --- debian/libruby3.1.symbols (libruby3.1_3.1.2-7_hurd-amd64) > > +++ dpkg-gensymbols5L9SYx 2023-11-03 17:57:31.0 + > > [...] > > @@ -1818,5 +1818,5 @@ > > ruby_xrealloc2@Base 3.1.0~preview1 > > ruby_xrealloc@Base 3.1.0~preview1 > > setproctitle@Base 3.1.0~preview1 > > - strlcat@Base 3.1.0~preview1 > > - strlcpy@Base 3.1.0~preview1 > > +#MISSING: 3.1.2-7# strlcat@Base 3.1.0~preview1 > > +#MISSING: 3.1.2-7# strlcpy@Base 3.1.0~preview1 > > > >
Bug#1070434: python-guizero-doc: unhandled symlink to directory conversion: /usr/share/doc/python3-guizero/html
Package: python-guizero-doc Version: 1.5.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: bookworm -> trixie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 1m17.4s ERROR: installs objects over existing directory symlinks: /usr/share/doc/python3-guizero/html/404.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/404.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/alerts.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/alerts.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/app.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/app.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/blocking.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/blocking.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/book.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/book.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/box.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/box.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/buttongroup.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/buttongroup.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/changelog.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/changelog.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/checkbox.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/checkbox.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/colors.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/colors.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/combo.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/combo.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html ... /usr/share/doc/python3-guizero/html/usingtk.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/usingtk.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/usingwidgets.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/usingwidgets.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/waffle.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/waffle.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/widgetoverview.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/widgetoverview.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html /usr/share/doc/python3-guizero/html/window.html (python-guizero-doc) != /usr/share/doc/python-guizero-doc/html/window.html (?) /usr/share/doc/python3-guizero/html -> ../python-guizero-doc/html cheers, Andreas
Processed: Re: Bug#1055297: ruby3.1: fails to build against glibc 2.38
Processing control commands: > severity -1 serious Bug #1055297 [ruby3.1] ruby3.1: fails to build against glibc 2.38 Severity set to 'serious' from 'important' -- 1055297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration]
Processing control commands: > tag -1 pending Bug #1066721 [src:netcat] netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066721: netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration]
Followup-For: Bug #1066721 Control: tag -1 pending I've now uploaded the NMU to DELAYED/5. Please let me know if I should delay it lonegr. Andreas
Processed: user debian...@lists.debian.org, usertagging 1060896, found 1060896 in 1.8.10-2.1 ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 1060896 piuparts There were no usertags set. Usertags are now: piuparts. > found 1060896 1.8.10-2.1 Bug #1060896 [openafs-modules-dkms] openafs-modules-dkms: module build fails for Linux 6.7: osi_file.c:178:42: error: 'struct inode' has no member named 'i_mtime' Marked as found in versions openafs/1.8.10-2.1. > usertags 1069945 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1069878 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1070327 piuparts There were no usertags set. Usertags are now: piuparts. > affects 1070327 + libauparse0t64 Bug #1070327 [src:audit] libauparse0t64 fails piuparts: missing postrm for /usr-move mitigation Added indication that 1070327 affects libauparse0t64 > thanks Stopping processing here. Please contact me if you need assistance. -- 1060896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060896 1070327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
