Bug#1018718: marked as pending in apache2
Hey. Thanks for the fix. Am I right that this *generally* does not longer enable apache2- doc.conf per default (i.e. also on fresh installs)? Causes that would also make it fix #977014. Cheers, Chris.
Bug#1033408: marked as done (apache2: Segmentation fault + 503 on frontpage on 2.4.56-1)
Your message dated Sun, 02 Apr 2023 03:19:14 + with message-id and subject line Bug#1033408: fixed in apache2 2.4.56-2 has caused the Debian Bug report #1033408, regarding apache2: Segmentation fault + 503 on frontpage on 2.4.56-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apache2 Version: 2.4.56-1~deb11u1 Severity: important X-Debbugs-Cc: t...@security.debian.org Unattended-upgrades applied this new version on 22 march @ 6AM. Had Segmentation faults since then, 503 for customers on websites. Since we reverted back to 2.4.54, we've no more issues. Couldn't make any sense of coredump but can provide one if necessary. -- Package-specific info: -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-18-amd64 (SMP w/32 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apache2 depends on: ii apache2-bin 2.4.56-1~deb11u1 ii apache2-data 2.4.56-1~deb11u1 ii apache2-utils2.4.56-1~deb11u1 ii dpkg 1.20.12 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ii mime-support 3.66 ii perl 5.32.1-4+deb11u2 ii procps 2:3.3.17-5 Versions of packages apache2 recommends: ii ssl-cert 1.1.0+nmu1 Versions of packages apache2 suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom ii lynx [www-browser] 2.9.0dev.6-3~deb11u1 Versions of packages apache2-bin depends on: ii libapr1 1.7.0-6+deb11u2 ii libaprutil1 1.6.1-5+deb11u1 ii libaprutil1-dbd-sqlite3 1.6.1-5+deb11u1 ii libaprutil1-ldap 1.6.1-5+deb11u1 ii libbrotli1 1.0.9-2+b2 ii libc62.31-13+deb11u5 ii libcrypt11:4.4.18-4 ii libcurl4 7.74.0-1.3+deb11u7 ii libjansson4 2.13.1-1.1 ii libldap-2.4-22.4.57+dfsg-3+deb11u1 ii liblua5.3-0 5.3.3-1.1+b1 ii libnghttp2-141.43.0-1 ii libpcre3 2:8.44-2+0~20210301.9+debian11~1.gbpa278ad ii libssl1.11.1.1n-0+deb11u4 ii libxml2 2.9.14+dfsg-0+0~20220524.12+debian11~1.gbpc5dc45 ii perl 5.32.1-4+deb11u2 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 Versions of packages apache2-bin suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom ii lynx [www-browser] 2.9.0dev.6-3~deb11u1 Versions of packages apache2 is related to: ii apache2 2.4.56-1~deb11u1 ii apache2-bin 2.4.56-1~deb11u1 -- Configuration Files: /etc/apache2/apache2.conf changed [not included] /etc/apache2/mods-available/mpm_event.conf changed [not included] /etc/apache2/ports.conf changed [not included] /etc/apache2/sites-available/000-default.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.56-2 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 1033...@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: Sun, 02 Apr 2023 06:54:25 +0400 Source: apache2 Built-For-Profiles: nocheck Architecture: source Version: 2.4.56-2 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Yadd Closes: 1033284 1033408 Changes: apache2 (2.4.56-2) unstable; urgency=medium . * Fix regression in mod_rewrite introduced in version
Processed: Bug#1033408 marked as pending in apache2
Processing control commands: > tag -1 pending Bug #1033408 [apache2] apache2: Segmentation fault + 503 on frontpage on 2.4.56-1 Added tag(s) pending. -- 1033408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1018718 marked as pending in apache2
Processing control commands: > tag -1 pending Bug #1018718 [apache2-doc] apache2-doc: despite having been disabled, apache2-doc.conf gets rather silently re-enabled automatically Added tag(s) pending. -- 1018718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033408: marked as pending in apache2
Control: tag -1 pending Hello, Bug #1033408 in apache2 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/apache-team/apache2/-/commit/1f69bd10ac680a0b95e60c8c5a66e0d5633508c3 Fix regressions introduced in 2.4.56 (Closes: #1033408, #1033284) (this message was generated automatically) -- Greetings https://bugs.debian.org/1033408
Bug#1018718: marked as pending in apache2
Control: tag -1 pending Hello, Bug #1018718 in apache2 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/apache-team/apache2/-/commit/330c94476d5801bdf8b4cea1200add1b84fcf6f3 Don't automatically enable apache2-doc.conf Closes: #1018718 (this message was generated automatically) -- Greetings https://bugs.debian.org/1018718
Bug#1028421: salt upstream lifecycle details
Adding to this thread/bug-report per salt project and Debian packaging, salt is unfortunately probably not a good candidate for the Debian ecosystem. The salt project current (2023-04) published lifecycle only lists 1.5 years of support for typical releases. After that their "extended life support" is really "best-effort technical support for customers" with "No bug fixes, [or] security fixes". This is clearly short of the Debian stable target support period of 3 years. https://docs.saltproject.io/salt/install-guide/en/latest/topics/salt-version-support-lifecycle.html#salt-version-support-lifecycle Salt Project Product support lifecycle excerpt: Salt versionPhase 1 support endsPhase 2 support endsPhase 3 support endsExtended life support 3005Feb 25, 2023Aug 25, 2023Feb 25, 2024 Feb 25, 2025 3004Apr 18, 2022Oct 18, 2022Apr 18, 2023 Apr 18, 2024 3003Sep 30, 2021Mar 31, 2022Sep 30, 2022 Sep 30, 2023 3002Apr 21, 2021Oct 21, 2021Apr 21, 2022 Apr 21, 2023 3001Dec 31, 2020Jun 30, 2021Dec 31, 2021 Dec 31, 2022 3000Aug 31, 2020Feb 28, 2021Aug 31, 2021 Aug 31, 2022 2019.2 Sep 30, 2019Mar 31, 2020Sep 30, 2020 Sep 30, 2021 2018.3 Oct 31, 2018Apr 30, 2019Oct 31, 2019 Oct 31, 2020 2017.7 Jan 31, 2018Jun 30, 2018Aug 30, 2019 Dec 31, 2019 2016.3 Nov 30, 2016May 31, 2017Nov 30, 2017 Nov 30, 2018 2015.8 Mar 31, 2016Sep 30, 2016Mar 31, 2017 Mar 31, 2018 2015.5 Nov 31, 2015May 31, 2016Nov 30, 2016 Nov 30, 2017 2014.7 May 31, 2015Nov 30, 2015May 31, 2016 May 31, 2017 regards, donfede signature.asc Description: PGP signature
Bug#1032989: marked as done (Liferea 1.14.1-1 segfaults on startup when trying to read gsettings)
On 2023-04-01 19:57, Paul Gevers wrote: I have uploaded a new upstream version that includes the fix for this issue, as well as fixes for some more crashes. I would appreciate it a lot if you could install the version from unstable once it's build and report back what your experience with that version is. I'm not Grzegorz but I also had the problem and it is fixed with 1.14.4-1. Thanks!
Processed: Remove moreinfo tag
Processing commands for cont...@bugs.debian.org: > tags 1033732 - moreinfo Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message Removed tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 1033732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Processing control commands: > tag -1 upstream Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message Added tag(s) upstream. -- 1033732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Control: tag -1 upstream On Saturday, 1 April 2023 22:47:35 CEST Guy Durrieu wrote: > I just finished to build the patched kernel. Well done! > After installing it, the system 6.1.0-7 boots again and run fine. > Thus the source was well identified by Bjørn Mork. This is great :-) > I just had problems trying to install > linux-headers-6.1.0-7-amd64_6.1.20-1a~test_amd64.deb, for dependencies > reasons not so clear for me. It is not mandatory anyway. Yeah, there are some improvements to be made for the procedure. > Thanks a lot to all of you for your help ! You're welcome and thanks for doing this. > What next ? 1) Now you get to brag to all your family and friends that you build a Linux kernel :-D 2) The commit that Bjørn identified also contained a "Link:" tag: https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com The best thing to do is to respond to that thread and explain the issue you ran into. At the bottom of the page you can find instructions on how to do that. The To/CC list is quite large, but don't be alarmed by that, that's rather common with kernel development. It's probably a good idea to add 1033...@bugs.debian.org to that list. The instructions also contain this part: "Avoid top-posting and favor interleaved quoting" That's what I've been doing and is considered rather important, so try your best to do that too. In your reply you should put the following things: 1) Your system worked find with kernel 6.1.15, but stopped booting after upgrading to 6.1.20 and resulted in a kernel panic 2) Copy the part between "" from your initial report so that it shows the kernel panic, your motherboard info and the stack trace 3) Indicate that Bjørn identified ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b from the linux-6.1.y branch as the likely culprit 4) After building a 6.1.20 kernel with just that commit reverted, your system booted normally again. 5) You reported that all to https://bugs.debian.org/1033732 and were asked to report the issue 'upstream' (which is what that mail is). It could be that they'll ask you to test a patch. If it's just a simple/single patch you should be able to try that with the same procedure as you've already done, but replace the patch I provided with one they provide. If you don't understand what they're asking or f.e. the kernel build is/seems too complicated, feel free to ask for help in (just) this bug. Good luck and thanks in advance :-) signature.asc Description: This is a digitally signed message part.
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Hello everybody, I just finished to build the patched kernel. After installing it, the system 6.1.0-7 boots again and run fine. Thus the source was well identified by Bjørn Mork. I just had problems trying to install linux-headers-6.1.0-7-amd64_6.1.20-1a~test_amd64.deb, for dependencies reasons not so clear for me. It is not mandatory anyway. Thanks a lot to all of you for your help ! What next ? Best regards. -- Guy Le 01/04/2023 à 19:48, Guy Durrieu a écrit : Thanks for your help ! That was more or less my conclusion, but it would indeed be useful to clarify that 4.1 and 4.21. are mutually exclusive. And I must admit that the # vs $ steps had escaped me :( Best regards. -- Guy Le 01/04/2023 à 18:56, Diederik de Haas a écrit : On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote: I am in trouble... I first did "Obtaining the kernel source", and at the end I got a /root/linux-source-6.1/ directory. Then I did "Rebuilding official Debian kernel packages" and "Preparation", and then I got among others a /root/linux-source-6.1/linux-6.1.20 the content of which is similar to the parent one, and where I can find, by the way, a debian directory. It seems strange to me, is it correct? No, this is not correct. No worries though as this is a great way to learn how we can improve the documentation :-) With "Preparation" I meant paragraph 4.2.1 and you don't need to follow 4.1. Also worth noting is that command prefixed by `#` should be done as root, but the commands prefixed by `$` should be done as (normal) user. So this is what you need to do: # apt-get install build-essential fakeroot # apt-get build-dep linux While we're 'root', do this too: # apt-get install devscripts And then (as user): $ apt-get source linux $ cd linux-6.1.20 If you then do ``ls -lh`` you will see a ``debian`` directory. So now you can run this: $ bash debian/bin/test-patches And now it should build a patched kernel for you. If it is correct, in what order to do the patches (debian patches and the revert patch)? When you look at the output of the ``apt-get source linux`` you'll see it download the linux source code and (automatically) applies the debian patches which are always applied when building a debian kernel. This is excluding the patch I send earlier, but that gets applied when you run the ``bash debian/bin/test-patches`` command. HTH, Diederik
Processed: bug 1033805 is forwarded to https://github.com/trusteddomainproject/OpenDMARC/issues/183
Processing commands for cont...@bugs.debian.org: > forwarded 1033805 https://github.com/trusteddomainproject/OpenDMARC/issues/183 Bug #1033805 [opendmarc] opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers Set Bug forwarded-to-address to 'https://github.com/trusteddomainproject/OpenDMARC/issues/183'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1033805 in 1.4.2-2
Processing commands for cont...@bugs.debian.org: > found 1033805 1.4.2-2 Bug #1033805 [opendmarc] opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers Marked as found in versions opendmarc/1.4.2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033806: libntru: autopkgtest regression: undefined reference
Source: libntru Version: 0.5-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] I'm slightly worried that this test failure points at a real problem with the library, but because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. Please remove the bookworm-ignore tag if the library is broken as it is. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/libn/libntru/32095885/log.gz autopkgtest [16:23:12]: test benchmark: [--- /usr/bin/ld: /tmp/cc3rAheI.o: warning: relocation against `EES761EP1' in read-only section `.text.startup' /usr/bin/ld: /tmp/cc3rAheI.o: in function `main': bench.c:(.text.startup+0x39): undefined reference to `ntru_rand_default_init' /usr/bin/ld: bench.c:(.text.startup+0x40): undefined reference to `ntru_rand_default_generate' /usr/bin/ld: bench.c:(.text.startup+0x54): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x5c): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x63): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x6b): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0x7a): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x89): undefined reference to `EES401EP1' /usr/bin/ld: bench.c:(.text.startup+0x98): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xa7): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xb5): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xc4): undefined reference to `EES449EP1' /usr/bin/ld: bench.c:(.text.startup+0xd3): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xe2): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xf0): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0xff): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0x10e): undefined reference to `EES677EP1' /usr/bin/ld: bench.c:(.text.startup+0x11d): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x141): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x149): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x151): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x158): undefined reference to `EES1087EP2' /usr/bin/ld: bench.c:(.text.startup+0x167): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x176): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x185): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x194): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x1a2): undefined reference to `EES541EP1' /usr/bin/ld: bench.c:(.text.startup+0x1b1): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1c0): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1cf): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1dd): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1ec): undefined reference to `EES613EP1' /usr/bin/ld: bench.c:(.text.startup+0x1fb): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x20a): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x22e): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x235): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x23d): undefined reference to `EES887EP1' /usr/bin/ld: bench.c:(.text.startup+0x245): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x24d): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x255): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x264): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x26b): undefined reference to `EES1171EP1' /usr/bin/ld: bench.c:(.text.startup+0x27a): undefined reference to `EES659EP1' /usr/bin/ld: bench.c:(.text.startup+0x289): undefined reference to `EES659EP1' /usr/bin/ld: bench.c:(.text.startup+0x297): undefined reference to `EES659EP1' /usr/bin/ld: bench.c:(.text.startup+0x2a6): undefined reference to
Processed: libntru: autopkgtest regression: undefined reference
Processing control commands: > tags -1 bookworm-ignore Bug #1033806 [src:libntru] libntru: autopkgtest regression: undefined reference Added tag(s) bookworm-ignore. -- 1033806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033805: opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers
Package: opendmarc Version: 1.4.0~beta1+dfsg-6+deb11u1 Severity: serious Tags: upstream patch Justification: Maintainer designation Currently opendmarc in Stable, Testing, and Unstable will crash if they key used in an ARC header field is 3072 bit RSA or longer. This really needs to be fixed prior to release since, in normal usage, when a milter crashes it stops all mail flow on the system. Since the key size is an attribute decided by the sending domain, there's no work around on the receiver side to avoid the specific keys at issue. Longer RSA keys are becoming more common and this trend will continue through Bookworm's life, so the impact will only grow. Patch available in the upstream GitHub repository: https://github.com/trusteddomainproject/OpenDMARC/issues/183 Scott K
Bug#1029215: marked as done (debian-archive-keyring: bookworm SRM key)
Your message dated Sat, 01 Apr 2023 18:32:08 + with message-id and subject line Bug#1029215: fixed in debian-archive-keyring 2021.1.1+deb11u1 has caused the Debian Bug report #1029215, regarding debian-archive-keyring: bookworm SRM key 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.) -- 1029215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debian-archive-keyring Version: 2021.1.1 Severity: serious X-Debbugs-Cc: debian-rele...@lists.debian.org Hi, We need an SRM key for bookworm, so that we can include it in the release. Regards, Adam --- End Message --- --- Begin Message --- Source: debian-archive-keyring Source-Version: 2021.1.1+deb11u1 Done: Jonathan Wiltshire We believe that the bug you reported is fixed in the latest version of debian-archive-keyring, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Wiltshire (supplier of updated debian-archive-keyring 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, 18 Mar 2023 14:53:41 + Source: debian-archive-keyring Architecture: source Version: 2021.1.1+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian Release Team Changed-By: Jonathan Wiltshire Closes: 1029214 1029215 Changes: debian-archive-keyring (2021.1.1+deb11u1) bullseye; urgency=medium . * Update my key and refresh signature * Remove stretch's keys (automatic and release) * Add Debian Stable Release Key (12/bookworm) (ID: 0xF8D2585B8783D481) (Closes: #1029215) * Add automatic signing keys for bookworm (Closes: #1029214) * Add debian/gbp.conf to make future maintenance easier Checksums-Sha1: f169b4e058d39b5aaddab3fd26756b0fe44c39bb 1301 debian-archive-keyring_2021.1.1+deb11u1.dsc 493c46c890db47a95b468130a8df5917b4efafae 174768 debian-archive-keyring_2021.1.1+deb11u1.tar.xz cfdfdf8a1ed0ea2ff36c80760626f60f852088f1 9601 debian-archive-keyring_2021.1.1+deb11u1_source.buildinfo Checksums-Sha256: afde187bdb36b807ab71eb0a5803d35a0a19265ff9ca47cb140f9f26aef2d6dd 1301 debian-archive-keyring_2021.1.1+deb11u1.dsc 7beff096d7293d019de8007d3425dbbcb18009b5780e6d0e172f57f5b6b300ae 174768 debian-archive-keyring_2021.1.1+deb11u1.tar.xz e1b77624b6690c850cdbf10b111801afbba641893fce351cd88c731fec8940c3 9601 debian-archive-keyring_2021.1.1+deb11u1_source.buildinfo Files: a2f12238f9a4248bf2710745ccf1ff31 1301 misc important debian-archive-keyring_2021.1.1+deb11u1.dsc a5604f50247c54cab2636618e8dc 174768 misc important debian-archive-keyring_2021.1.1+deb11u1.tar.xz 8dc687d0fefff2a72eb992289f846923 9601 misc important debian-archive-keyring_2021.1.1+deb11u1_source.buildinfo -BEGIN PGP SIGNATURE- iIUEARYKAC0WIQTdFzjfLGn8URFmteMDXuYJgEtROQUCZBXWdg8cam13QGRlYmlh bi5vcmcACgkQA17mCYBLUTmZtgEAmtuQ/yC/VrjI3nZwnNJG4o36twXkWJ42s6iv 0RI6ahAA/0eaU6odNlEuih9XZ02RVGDyFz7c3iFCkLgihxdK3ywO =XOIB -END PGP SIGNATURE End Message ---
Bug#1029214: marked as done (debian-archive-keyring: bookworm archive signing keys)
Your message dated Sat, 01 Apr 2023 18:32:08 + with message-id and subject line Bug#1029214: fixed in debian-archive-keyring 2021.1.1+deb11u1 has caused the Debian Bug report #1029214, regarding debian-archive-keyring: bookworm archive signing keys 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.) -- 1029214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debian-archive-keyring Version: 2021.1.1 Severity: serious X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org Hi, We need new archive signing keys for bookworm, so that we can include them in the release. Regards, Adam --- End Message --- --- Begin Message --- Source: debian-archive-keyring Source-Version: 2021.1.1+deb11u1 Done: Jonathan Wiltshire We believe that the bug you reported is fixed in the latest version of debian-archive-keyring, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Wiltshire (supplier of updated debian-archive-keyring 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, 18 Mar 2023 14:53:41 + Source: debian-archive-keyring Architecture: source Version: 2021.1.1+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian Release Team Changed-By: Jonathan Wiltshire Closes: 1029214 1029215 Changes: debian-archive-keyring (2021.1.1+deb11u1) bullseye; urgency=medium . * Update my key and refresh signature * Remove stretch's keys (automatic and release) * Add Debian Stable Release Key (12/bookworm) (ID: 0xF8D2585B8783D481) (Closes: #1029215) * Add automatic signing keys for bookworm (Closes: #1029214) * Add debian/gbp.conf to make future maintenance easier Checksums-Sha1: f169b4e058d39b5aaddab3fd26756b0fe44c39bb 1301 debian-archive-keyring_2021.1.1+deb11u1.dsc 493c46c890db47a95b468130a8df5917b4efafae 174768 debian-archive-keyring_2021.1.1+deb11u1.tar.xz cfdfdf8a1ed0ea2ff36c80760626f60f852088f1 9601 debian-archive-keyring_2021.1.1+deb11u1_source.buildinfo Checksums-Sha256: afde187bdb36b807ab71eb0a5803d35a0a19265ff9ca47cb140f9f26aef2d6dd 1301 debian-archive-keyring_2021.1.1+deb11u1.dsc 7beff096d7293d019de8007d3425dbbcb18009b5780e6d0e172f57f5b6b300ae 174768 debian-archive-keyring_2021.1.1+deb11u1.tar.xz e1b77624b6690c850cdbf10b111801afbba641893fce351cd88c731fec8940c3 9601 debian-archive-keyring_2021.1.1+deb11u1_source.buildinfo Files: a2f12238f9a4248bf2710745ccf1ff31 1301 misc important debian-archive-keyring_2021.1.1+deb11u1.dsc a5604f50247c54cab2636618e8dc 174768 misc important debian-archive-keyring_2021.1.1+deb11u1.tar.xz 8dc687d0fefff2a72eb992289f846923 9601 misc important debian-archive-keyring_2021.1.1+deb11u1_source.buildinfo -BEGIN PGP SIGNATURE- iIUEARYKAC0WIQTdFzjfLGn8URFmteMDXuYJgEtROQUCZBXWdg8cam13QGRlYmlh bi5vcmcACgkQA17mCYBLUTmZtgEAmtuQ/yC/VrjI3nZwnNJG4o36twXkWJ42s6iv 0RI6ahAA/0eaU6odNlEuih9XZ02RVGDyFz7c3iFCkLgihxdK3ywO =XOIB -END PGP SIGNATURE End Message ---
Bug#1027954: marked as done (cppad: binary-all FTBFS)
Your message dated Sat, 01 Apr 2023 18:00:12 + with message-id and subject line Bug#1027954: fixed in cppad 2023.00.00.0-2 has caused the Debian Bug report #1027954, regarding cppad: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cppad Version: 2023.00.00.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=cppad=all=2023.00.00.0-1=1672887350=0 ... dh_installdocs -i -O--buildsystem=cmake dh_installdocs: error: Cannot find (any matches for) "doc.omh" (tried in ., debian/tmp) make: *** [debian/rules:6: binary-indep] Error 25 --- End Message --- --- Begin Message --- Source: cppad Source-Version: 2023.00.00.0-2 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of cppad, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated cppad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Mar 2023 09:46:00 +0100 Source: cppad Binary: libcppad-dev libcppad-doc libcppad-lib1456.0 libcppad-lib1456.0-dbgsym Architecture: source amd64 all Version: 2023.00.00.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Barak A. Pearlmutter Description: libcppad-dev - Automatic Differentiation of C++ algorithms, dev files libcppad-doc - Automatic Differentiation of C++ algorithms, documentation libcppad-lib1456.0 - Automatic Differentiation of C++ algorithms, shared library Closes: 1027954 Changes: cppad (2023.00.00.0-2) unstable; urgency=medium . * Stop trying to install old format ohm documentation (closes: #1027954) * Don't try to build documents from new format xrst documentation * Change soname, rename libcppad-lib 340.3 to 1456.0 * Update debian/copyright * Update relationship to old cppad package per lintian Checksums-Sha1: 5dad2959741c58b5c52643674f6b38e4f9845c19 2146 cppad_2023.00.00.0-2.dsc 668f0083da1f22b9181a624da61de1482db2931c 7992 cppad_2023.00.00.0-2.debian.tar.xz 31515a3f1c8326506d8012c23aaf8ed9a802791b 14337 cppad_2023.00.00.0-2_amd64.buildinfo b752ee8b2e34e1cf894aa3e584437ec7b98bc82a 379456 libcppad-dev_2023.00.00.0-2_amd64.deb 41ff576a1e9e45b04e9100e5bc2d6ebddf61c2a4 7308 libcppad-doc_2023.00.00.0-2_all.deb fce0c6f536e7d7cfa0c8e8d16b92467c5059b27d 750048 libcppad-lib1456.0-dbgsym_2023.00.00.0-2_amd64.deb 2ec00671143342fcfeda5bfde7e47f372e43911e 57224 libcppad-lib1456.0_2023.00.00.0-2_amd64.deb Checksums-Sha256: bd7ff29c01b6f27298878de27d1abf384deb15d8cb4bc1b24f8da3de757a5baf 2146 cppad_2023.00.00.0-2.dsc 137086b4fd158da7b693b9c58bcce0350f6f335d90c7a48f38437437b04be2da 7992 cppad_2023.00.00.0-2.debian.tar.xz 6bf96e5be874c5969a42f8c0006d6bf6f04f56034b11bc57888168d7b9faadd4 14337 cppad_2023.00.00.0-2_amd64.buildinfo b707a4ab8dd732424d0f59f042a3e3ea5a2856b941e81b7138530f5608649e98 379456 libcppad-dev_2023.00.00.0-2_amd64.deb b9e93d7f69b671743d792438634894901f79315412f62e4334396b06dc3199c4 7308 libcppad-doc_2023.00.00.0-2_all.deb 84f5eea57927cbb69bd25e0af4286453d5dbba37d6c0ebf4e26bb43a9382110c 750048 libcppad-lib1456.0-dbgsym_2023.00.00.0-2_amd64.deb a47746e5f085a4088ec617788eeed548adfa1f3188cded940fa3531c5956ff99 57224 libcppad-lib1456.0_2023.00.00.0-2_amd64.deb Files: 1d7c6baa52c433d4c58b05206a076384 2146 devel optional cppad_2023.00.00.0-2.dsc dec9b3e82bc7f55d6cd33035cf2aeda7 7992 devel optional cppad_2023.00.00.0-2.debian.tar.xz 53c1fa54bd72aa422de72488cb1a4b23 14337 devel optional cppad_2023.00.00.0-2_amd64.buildinfo 36da377bbef0e1f88a4ab8201c315141 379456 libdevel optional libcppad-dev_2023.00.00.0-2_amd64.deb 728864610bfab59f5b5d446b27689824 7308 doc optional libcppad-doc_2023.00.00.0-2_all.deb 91ea1f808e799c7fd7fa374613ef139a 750048 debug optional libcppad-lib1456.0-dbgsym_2023.00.00.0-2_amd64.deb f5006f977d577f2935bbebbbca1ce003 57224 libs optional
Bug#1032989: marked as done (Liferea 1.14.1-1 segfaults on startup when trying to read gsettings)
Hi Grzegorz, H.-Dirk On 01-04-2023 19:54, Debian Bug Tracking System wrote: This means that you claim that the problem has been dealt with. I have uploaded a new upstream version that includes the fix for this issue, as well as fixes for some more crashes. I would appreciate it a lot if you could install the version from unstable once it's build and report back what your experience with that version is. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: libdancer2-plugin-database-perl: FTBFS randomly (failing tests)
Processing control commands: > severity -1 serious Bug #923824 [src:libdancer2-plugin-database-perl] libdancer2-plugin-database-perl: FTBFS randomly (failing tests) Severity set to 'serious' from 'important' > tags -1 bookworm-ignore Bug #923824 [src:libdancer2-plugin-database-perl] libdancer2-plugin-database-perl: FTBFS randomly (failing tests) Added tag(s) bookworm-ignore. -- 923824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032989: marked as done (Liferea 1.14.1-1 segfaults on startup when trying to read gsettings)
Your message dated Sat, 01 Apr 2023 17:50:26 + with message-id and subject line Bug#1032989: fixed in liferea 1.14.4-1 has caused the Debian Bug report #1032989, regarding Liferea 1.14.1-1 segfaults on startup when trying to read gsettings 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.) -- 1032989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: liferea Version: 1.14.1-1 Dear Maintainer, After I have upgraded liferea from 1.14.0-1 to 1.14.1-1 today, it no longer starts, segfaulting when trying to read the "enable-reader-mode" setting. I have attached (liferea.crash) the result of the following command: gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' -ex 'thread apply all bt full' --args liferea from which the short summary is: Thread 1 "liferea" received signal SIGSEGV, Segmentation fault. 0x55577a6e in conf_get_bool_value_from_schema (gsettings=, gsettings@entry=0x0, key=key@entry=0x555cb33a "enable-reader-mode", value=value@entry=0x54) at ../conf.c:258 258 *value = g_settings_get_boolean (gsettings,key); Let me know if there is more info I can provide to help. -- Grzegorz Szymaszek [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffebdff6c0 (LWP 202012)] [New Thread 0x7fffeb5fe6c0 (LWP 202013)] [New Thread 0x7fffeadfd6c0 (LWP 202014)] [New Thread 0x7fffea5fc6c0 (LWP 202015)] [Detaching after fork from child process 202016] [New Thread 0x7fffdbfff6c0 (LWP 202017)] [Thread 0x7fffdbfff6c0 (LWP 202017) exited] [New Thread 0x7fffdbfff6c0 (LWP 202018)] [New Thread 0x7fffdb7fe6c0 (LWP 202019)] [Thread 0x7fffdbfff6c0 (LWP 202018) exited] [Thread 0x7fffdb7fe6c0 (LWP 202019) exited] [New Thread 0x7fffdb7fe6c0 (LWP 202020)] [New Thread 0x7fffdbfff6c0 (LWP 202021)] [Thread 0x7fffdb7fe6c0 (LWP 202020) exited] [Thread 0x7fffdbfff6c0 (LWP 202021) exited] [New Thread 0x7fffdbfff6c0 (LWP 202022)] [New Thread 0x7fffdb7fe6c0 (LWP 202023)] [Thread 0x7fffdbfff6c0 (LWP 202022) exited] [Thread 0x7fffdb7fe6c0 (LWP 202023) exited] [New Thread 0x7fffdb7fe6c0 (LWP 202024)] [New Thread 0x7fffdbfff6c0 (LWP 202025)] [Thread 0x7fffdb7fe6c0 (LWP 202024) exited] [Thread 0x7fffdbfff6c0 (LWP 202025) exited] [New Thread 0x7fffdbfff6c0 (LWP 202026)] [New Thread 0x7fffdb7fe6c0 (LWP 202027)] [Thread 0x7fffdbfff6c0 (LWP 202026) exited] [Thread 0x7fffdb7fe6c0 (LWP 202027) exited] Thread 1 "liferea" received signal SIGSEGV, Segmentation fault. 0x55577a6e in conf_get_bool_value_from_schema (gsettings=, gsettings@entry=0x0, key=key@entry=0x555cb33a "enable-reader-mode", value=value@entry=0x54) at ../conf.c:258 258 *value = g_settings_get_boolean (gsettings,key); #0 0x55577a6e in conf_get_bool_value_from_schema (gsettings=, gsettings@entry=0x0, key=key@entry=0x555cb33a "enable-reader-mode", value=value@entry=0x54) at ../conf.c:258 #1 0x555a74fd in liferea_browser_update (browser=0x0, mode=1) at ./src/ui/liferea_browser.c:727 #2 0x555a54e7 in itemview_update () at ./src/ui/itemview.c:297 #3 0x555851cd in itemlist_merge_itemset (itemSet=itemSet@entry=0x564b7740) at ../itemlist.c:299 #4 0x55585405 in itemlist_load (node=node@entry=0x55eb2cc0) at ../itemlist.c:354 #5 0x5558170d in feedlist_selection_changed (obj=, nodeId=0x56438d20 "jnwlxys", data=) at ../feedlist.c:585 #9 0x73c8ffd8 in (instance=0x55b45400, detailed_signal=detailed_signal@entry=0x555c04ce "selection-changed") at ../../../gobject/gsignal.c:3648 #6 0x73c763b0 in g_closure_invoke (closure=0x55fdc420, return_value=return_value@entry=0x0, n_param_values=2, param_values=param_values@entry=0x7fffb770, invocation_hint=invocation_hint@entry=0x7fffb6f0) at ../../../gobject/gclosure.c:832 #7 0x73c89076 in signal_emit_unlocked_R (node=node@entry=0x55840800, detail=detail@entry=0, instance=instance@entry=0x55b45400, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffb770) at ../../../gobject/gsignal.c:3796 #8 0x73c8fbf5 in g_signal_emit_valist (instance=instance@entry=0x55b45400, signal_id=signal_id@entry=282, detail=, var_args=var_args@entry=0x7fffb928) at ../../../gobject/gsignal.c:3549 #10 0x555a2fdd in feed_list_view_selection_changed_cb (selection=, data=) at ./src/ui/feed_list_view.c:134 #11
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Thanks for your help ! That was more or less my conclusion, but it would indeed be useful to clarify that 4.1 and 4.21. are mutually exclusive. And I must admit that the # vs $ steps had escaped me :( Best regards. -- Guy Le 01/04/2023 à 18:56, Diederik de Haas a écrit : On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote: I am in trouble... I first did "Obtaining the kernel source", and at the end I got a /root/linux-source-6.1/ directory. Then I did "Rebuilding official Debian kernel packages" and "Preparation", and then I got among others a /root/linux-source-6.1/linux-6.1.20 the content of which is similar to the parent one, and where I can find, by the way, a debian directory. It seems strange to me, is it correct? No, this is not correct. No worries though as this is a great way to learn how we can improve the documentation :-) With "Preparation" I meant paragraph 4.2.1 and you don't need to follow 4.1. Also worth noting is that command prefixed by `#` should be done as root, but the commands prefixed by `$` should be done as (normal) user. So this is what you need to do: # apt-get install build-essential fakeroot # apt-get build-dep linux While we're 'root', do this too: # apt-get install devscripts And then (as user): $ apt-get source linux $ cd linux-6.1.20 If you then do ``ls -lh`` you will see a ``debian`` directory. So now you can run this: $ bash debian/bin/test-patches And now it should build a patched kernel for you. If it is correct, in what order to do the patches (debian patches and the revert patch)? When you look at the output of the ``apt-get source linux`` you'll see it download the linux source code and (automatically) applies the debian patches which are always applied when building a debian kernel. This is excluding the patch I send earlier, but that gets applied when you run the ``bash debian/bin/test-patches`` command. HTH, Diederik
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Thanks for your help ! That was more or less my conclusion, but it would indeed be useful to clarify that 4.1 and 4.21. are mutually exclusive. And I must admit that the # vs $ steps had escaped me :( Best regards. -- Guy Le 01/04/2023 à 18:56, Diederik de Haas a écrit : On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote: I am in trouble... I first did "Obtaining the kernel source", and at the end I got a /root/linux-source-6.1/ directory. Then I did "Rebuilding official Debian kernel packages" and "Preparation", and then I got among others a /root/linux-source-6.1/linux-6.1.20 the content of which is similar to the parent one, and where I can find, by the way, a debian directory. It seems strange to me, is it correct? No, this is not correct. No worries though as this is a great way to learn how we can improve the documentation :-) With "Preparation" I meant paragraph 4.2.1 and you don't need to follow 4.1. Also worth noting is that command prefixed by `#` should be done as root, but the commands prefixed by `$` should be done as (normal) user. So this is what you need to do: # apt-get install build-essential fakeroot # apt-get build-dep linux While we're 'root', do this too: # apt-get install devscripts And then (as user): $ apt-get source linux $ cd linux-6.1.20 If you then do ``ls -lh`` you will see a ``debian`` directory. So now you can run this: $ bash debian/bin/test-patches And now it should build a patched kernel for you. If it is correct, in what order to do the patches (debian patches and the revert patch)? When you look at the output of the ``apt-get source linux`` you'll see it download the linux source code and (automatically) applies the debian patches which are always applied when building a debian kernel. This is excluding the patch I send earlier, but that gets applied when you run the ``bash debian/bin/test-patches`` command. HTH, Diederik
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote: > I am in trouble... I first did "Obtaining the kernel source", and at the > end I got a /root/linux-source-6.1/ directory. > > Then I did "Rebuilding official Debian kernel packages" and > "Preparation", and then I got among others a > /root/linux-source-6.1/linux-6.1.20 the content of which is similar to > the parent one, and where I can find, by the way, a debian directory. > > It seems strange to me, is it correct? No, this is not correct. No worries though as this is a great way to learn how we can improve the documentation :-) With "Preparation" I meant paragraph 4.2.1 and you don't need to follow 4.1. Also worth noting is that command prefixed by `#` should be done as root, but the commands prefixed by `$` should be done as (normal) user. So this is what you need to do: # apt-get install build-essential fakeroot # apt-get build-dep linux While we're 'root', do this too: # apt-get install devscripts And then (as user): $ apt-get source linux $ cd linux-6.1.20 If you then do ``ls -lh`` you will see a ``debian`` directory. So now you can run this: $ bash debian/bin/test-patches And now it should build a patched kernel for you. > If it is correct, in what order to do the patches (debian patches and > the revert patch)? When you look at the output of the ``apt-get source linux`` you'll see it download the linux source code and (automatically) applies the debian patches which are always applied when building a debian kernel. This is excluding the patch I send earlier, but that gets applied when you run the ``bash debian/bin/test-patches`` command. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1033431: marked as done (cookiecutter: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)
Your message dated Sat, 01 Apr 2023 16:03:55 +
with message-id
and subject line Bug#1033431: fixed in cookiecutter 1.7.3-3
has caused the Debian Bug report #1033431,
regarding cookiecutter: FTBFS in testing: dh_auto_test: error: pybuild --test
-i python{version} -p 3.11 returned exit code 13
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.)
--
1033431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cookiecutter
Version: 1.7.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm
Hi,
During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/hooks.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/extensions.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/__main__.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/main.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/exceptions.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/__init__.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/prompt.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/config.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/log.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/repository.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/generate.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/replay.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/find.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/vcs.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/zipfile.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/cli.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/utils.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/environment.py ->
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> running egg_info
> creating cookiecutter.egg-info
> writing cookiecutter.egg-info/PKG-INFO
> writing dependency_links to cookiecutter.egg-info/dependency_links.txt
> writing entry points to cookiecutter.egg-info/entry_points.txt
> writing requirements to cookiecutter.egg-info/requires.txt
> writing top-level names to cookiecutter.egg-info/top_level.txt
> writing manifest file 'cookiecutter.egg-info/SOURCES.txt'
> reading manifest file 'cookiecutter.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'AUTHORS.rst'
> warning: no files found matching 'CONTRIBUTING.rst'
> warning: no files found matching 'HISTORY.rst'
> warning: no files found matching 'README.rst'
> warning: no previously-included files matching '__pycache__' found under
> directory '*'
> warning: no previously-included files matching '*.py[co]' found under
> directory '*'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.md'
> writing manifest file 'cookiecutter.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd
> /<>/.pybuild/cpython3_3.11_cookiecutter/build; python3.11 -m
> pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack --
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>, configfile: setup.cfg
> plugins: mock-3.8.2, cov-4.0.0
> collecting ... collected 276 items
>
>
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
I am in trouble... I first did "Obtaining the kernel source", and at the end I got a /root/linux-source-6.1/ directory. Then I did "Rebuilding official Debian kernel packages" and "Preparation", and then I got among others a /root/linux-source-6.1/linux-6.1.20 the content of which is similar to the parent one, and where I can find, by the way, a debian directory. It seems strange to me, is it correct? If it is correct, in what order to do the patches (debian patches and the revert patch)? Thanks in advance for your help ! Best regards. -- Guy Le 01/04/2023 à 16:55, Diederik de Haas a écrit : > > On April 1, 2023 4:31:49 PM GMT+02:00, Guy Durrieu > wrote: >> Thanks for your help ! >> >> There is something not clear for me in the section 4.2.2. Simple >> patching and building... >> >> I ran apt-get install devscripts but I can't find any debian >> directory nor patches. Is it sufficient to apply the patch given by >> Diederik de Haas ? > > I'm guessing you forgot to do the Preparation from 4.2.1 > >> Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit : >>> Hi, >>> >>> On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote: Hello, This is something I have never done, but I can try. However some time ago, for solving a previous issue, a guy from Debian compiled for me an unofficial release including the patch to be tested, along with some credentials. I know this is not the recommended procedure :) but it worked. >>> Seems there was a race on responding. If you look at the >>> documentation referenced by Diederik there are instructions on >>> how to do it with a single patch applied on top. If you run into >>> trouble let us know though. >>> >>> Regards, Salvatore >> >
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
On April 1, 2023 4:31:49 PM GMT+02:00, Guy Durrieu wrote: >Thanks for your help ! > >There is something not clear for me in the section 4.2.2. Simple patching and >building... > >I ran apt-get install devscripts but I can't find any debian directory nor >patches. Is it sufficient to apply the patch given by Diederik de Haas ? I'm guessing you forgot to do the Preparation from 4.2.1 >Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit : >> Hi, >> >> On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote: >>> Hello, >>> >>> This is something I have never done, but I can try. >>> >>> However some time ago, for solving a previous issue, a guy from Debian >>> compiled for me an unofficial release including the patch to be tested, >>> along with some credentials. I know this is not the recommended procedure :) >>> but it worked. >> Seems there was a race on responding. If you look at the documentation >> referenced by Diederik there are instructions on how to do it with a >> single patch applied on top. If you run into trouble let us know >> though. >> >> Regards, >> Salvatore > -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#1029588: bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed
Hi I've created a merge request [1] on devscript to fix this issue All the best [1] https://salsa.debian.org/debian/devscripts/-/merge_requests/343
Processed: tagging 1029588
Processing commands for cont...@bugs.debian.org: > tags 1029588 + patch Bug #1029588 [devscripts] bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033785: irssi: CVE-2023-29132
On Sat, Apr 01, 2023 at 10:36:56AM +0200, Salvatore Bonaccorso wrote: > Source: irssi > Version: 1.4.3-1 > Severity: grave > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > The following vulnerability was published for irssi. > > CVE-2023-29132[0]: > | Irssi SA-2023-03 / Use after free in printing routine Just to be clear, the following are mitigating facts: The precondition for this issue is printing a non-formatted line during the printing of a formatted line. This is unlikely to happen without scripts, and is obscured by the slice allocator when using GLib before version 2.77. *but* I still filled it for now as RC, as the fix is very isolated, and good to be included in bookworm already. Regards, Salvatore
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Thanks for your help ! There is something not clear for me in the section 4.2.2. Simple patching and building... I ran apt-get install devscripts but I can't find any debian directory nor patches. Is it sufficient to apply the patch given by Diederik de Haas ? Regards. -- Guy Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit : Hi, On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote: Hello, This is something I have never done, but I can try. However some time ago, for solving a previous issue, a guy from Debian compiled for me an unofficial release including the patch to be tested, along with some credentials. I know this is not the recommended procedure :) but it worked. Seems there was a race on responding. If you look at the documentation referenced by Diederik there are instructions on how to do it with a single patch applied on top. If you run into trouble let us know though. Regards, Salvatore
Bug#995156: easy-rsa: vars Autodetection
Bump to avoid auto removal while the fixed version ages in unstable.
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Hi, On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote: > Hello, > > This is something I have never done, but I can try. > > However some time ago, for solving a previous issue, a guy from Debian > compiled for me an unofficial release including the patch to be tested, > along with some credentials. I know this is not the recommended procedure :) > but it worked. Seems there was a race on responding. If you look at the documentation referenced by Diederik there are instructions on how to do it with a single patch applied on top. If you run into trouble let us know though. Regards, Salvatore
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Salvatore Bonaccorso writes: > AFAIK there is no commit upstream with fixes tag on that commit. But > Bjorn suspects that might be the suspicious commit introducing the > issue. Yes, I noticed that, so I could very well be wrong... But it stood out as the only change to any x86 IOAPIC stuff since Linux 6.1.0-6-amd64. That's of course not any guarantee. But worth testing. Bjørn
Bug#1033607: [Pkg-sogo-maintainers] Bug#1033607: sogo: /usr/bin/sogo linked against wrong version of libgnustep-base
Hi Phil, On Sat, 01 Apr 2023 02:41:05 +0200, Phil Gruber wrote: > > Thanks for getting back to me. > > Here's what this looks like for me: > > > $ /usr/sbin/sogod > > /usr/sbin/sogod: error while loading shared libraries: > > libgnustep-base.so.1.24: cannot open shared object file: No such file or > > directory > > $ ldd -r /usr/sbin/sogod | grep gnustep > > libgnustep-base.so.1.27 => /usr/lib/libgnustep-base.so.1.27 > > (0x7f6c6428f000) > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > libgnustep-base.so.1.24 => not found > > I just removed and re-installed the sogo package, but it didn't make a > difference. Can you use objdump to figure out which files have the dependency on libgnustep-base.so.1.24? objdump -p /usr/sbin/sogod | grep NEEDED If that doesn't list libgnustep-base.so.1.24 then try libSOGo.so.5 and all the other libraries listed by ldd. Kind regards, Jeroen Dekkers
Bug#1033667: marked as done (verilator: Uninstallable in sid because of ${sphinxdoc:Built-Using} dependency)
Your message dated Sat, 01 Apr 2023 10:05:18 +
with message-id
and subject line Bug#1033667: fixed in verilator 5.008-1
has caused the Debian Bug report #1033667,
regarding verilator: Uninstallable in sid because of ${sphinxdoc:Built-Using}
dependency
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.)
--
1033667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: verilator
Version: 5.006-2
Severity: serious
Tags: patch
Dear Maintainer,
In a clean sid chroot, verilator is not installable:
# apt install verilator
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
verilator : Depends: sphinx (= 5.3.0-3)
E: Unable to correct problems, you have held broken packages.
This is because that package has ${sphinxdoc:Built-Using} among its
dependencies.
That substitution variable is intended to be used in Built-Using field of
architecture-dependent packages, NOT in Depends field.
I have created a merge request [1] on salsa to fix this.
[1]: https://salsa.debian.org/electronics-team/verilator/-/merge_requests/3
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: verilator
Source-Version: 5.008-1
Done: Carsten Schoenert
We believe that the bug you reported is fixed in the latest version of
verilator, 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 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Carsten Schoenert (supplier of updated verilator
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, 30 Mar 2023 19:48:21 +0200
Source: verilator
Architecture: source
Version: 5.008-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team
Changed-By: Carsten Schoenert
Closes: 1030913 1031711 1033667
Changes:
verilator (5.008-1) experimental; urgency=medium
.
* Team upload
[ Dmitry Shachnev ]
* [38e486b] Move ${sphinxdoc:Built-Using} to the correct field.
(Closes: #1033667)
.
[ Carsten Schoenert ]
* [0a50071] New upstream version 5.008
(Closes: #1030913)
* [bb4558b] Rebuild patch queue from patch-queue branch
Removed patches (included upstream):
Add-SOURCE_DATE_EPOCH-for-docs-guide-conf.py-3918.patch
(Closes: #1031711)
Checksums-Sha1:
2a60dc75f6eb7a37563bb5b034a4b99cf5d6c57c 2198 verilator_5.008-1.dsc
7cf4d4c35c7c163f09a3fa8f625da0298f7a0c21 3177491 verilator_5.008.orig.tar.gz
cc1bf912f7d435f4071f37e218cd8cc359b165a4 12040 verilator_5.008-1.debian.tar.xz
1d83fde42927cb4789a617e0922cec1e9f784612 9843 verilator_5.008-1_amd64.buildinfo
Checksums-Sha256:
b30665d937a0b6cc0f3b2427e3932f13199fb7bec78759c9e74cf506558cdc6d 2198
verilator_5.008-1.dsc
d9fcbbecac2f2e2be7e5d0224f0695ad547279110340c79ef67c88395c0f75a9 3177491
verilator_5.008.orig.tar.gz
7df1d77085fa9c178cbe209eb3ef9db1e3c312ccab3ddd23a49ef9962ee54b69 12040
verilator_5.008-1.debian.tar.xz
d0c3cd32f6b8e75bb32d1ce320262d706515acd537bb10c4b1532e75bc274b82 9843
verilator_5.008-1_amd64.buildinfo
Files:
35507609e717856bf49dbebb68ec7652 2198 electronics optional
verilator_5.008-1.dsc
631e70c0f1744ca31f24853bdaec47c8 3177491 electronics optional
verilator_5.008.orig.tar.gz
86560c47c13f5d9d8d7b2ff51bc19bf3 12040 electronics optional
verilator_5.008-1.debian.tar.xz
fc503fbcb2fa3a45ca83c9bba31a66e4 9843 electronics optional
verilator_5.008-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmQn+90ACgkQgwFgFCUd
HbDb6Q//Q9gTQ2pO5IGnL54K4HGFh/GMKVVkpP+HQEiBwe2y7zDBvy/DRtqJlWXd
n6jBoDahONlB5g95JI8Q5tlOW9X+4yWYtFfgDaK+eEeShesblK/yCGxuwKb002my
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Hello, This is something I have never done, but I can try. However some time ago, for solving a previous issue, a guy from Debian compiled for me an unofficial release including the patch to be tested, along with some credentials. I know this is not the recommended procedure :) but it worked. Best regards, -- Guy Le 01/04/2023 à 11:00, Salvatore Bonaccorso a écrit : Control: tags -1 + moreinfo Hi Guy, On Sat, Apr 01, 2023 at 10:09:09AM +0200, Guy Durrieu wrote: Hello, Thanks for your answer ! Before receiving it I tried to update my BIOS to the last available version (F51h). Without any effect. I am not sure I understand everything that is said in your link, except I must wait for the next updates... Right ? AFAIK there is no commit upstream with fixes tag on that commit. But Bjorn suspects that might be the suspicious commit introducing the issue. Would you be able to build a kernel 6.1.20 with that patch reverted on top and see if it resolved your issue? Regards, Salvatore
Bug#1033784: marked as done (FTBFS: mbimbf.t fails with libmath-bigint-perl 1.999838)
Your message dated Sat, 01 Apr 2023 09:04:00 +
with message-id
and subject line Bug#1033784: fixed in libmath-bigint-gmp-perl 1.6011-3
has caused the Debian Bug report #1033784,
regarding FTBFS: mbimbf.t fails with libmath-bigint-perl 1.999838
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.)
--
1033784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Version: 1.6011-2
Severity: serious
Tags: ftbfs, patch
Dear Maintainer,
yesterday I uploaded libmath-bigint-perl 1.999838-1, which fixes RC
bugs.
Bug with this version of libmath-bigint-perl now
libmath-bigint-gmp-perl fails to build, since two test cases in
t/mbimbf.t fail:
ok 729 - $x has A of 42
ok 730 - $x has A from global
not ok 731 - $x has still A of 42
ok 732 - $x has A of 42
ok 733 - $x has A from global
not ok 734 - $x has still A of 42
t/mbimbf.t in libmath-bigint-perl and libmath-bigint-gmp-perl where
identical except
-use Math::BigInt only => 'Calc';
+use Math::BigInt only => 'GMP';
before the update of libmath-bigint-perl, but Upstream
extended/changed mbimbf.t in 1.999838, so IMHO it should be changed in
libmath-bigint-gmp-perl accordingly.
The attached patch merges mbimbf.t changes from libmath-bigint-perl
1.999838.
With this patch libmath-bigint-gmp-perl builds with a working test
suite.
Greetings
Roland
From: Roland Rosenfeld
Subject: Adapt mbimbf.t to the one from Math::BigInt 1.999838
Date: Sat, 01 Apr 2023 09:57:20 +0200
--- a/t/mbimbf.t
+++ b/t/mbimbf.t
@@ -7,7 +7,7 @@ use strict;
use warnings;
use Test::More tests => 712 # tests in require'd file
-+ 26; # tests in this file
++ 52; # tests in this file
use Math::BigInt only => 'GMP';
use Math::BigFloat;
@@ -58,24 +58,71 @@ foreach my $class (qw/Math::BigInt Math:
}
foreach my $class (qw/Math::BigInt Math::BigFloat/) {
-$class->accuracy(42);
+my $x;
-# $x gets A of 42, too!
-my $x = $class->new(123);
+# Accuracy
-# really?
-is($x->accuracy(), 42, '$x has A of 42');
+# set and check the class accuracy
+$class->accuracy(1);
+is($class->accuracy(), 1, "$class has A of 1");
-# $x has no A, but the global is still in effect for $x so the return value
-# of that operation should be 42, not undef
-is($x->accuracy(undef), 42, '$x has A from global');
+# a new instance gets the class accuracy
+$x = $class->new(123);
+is($x->accuracy(), 1, '$x has A of 1');
-# so $x should still have A = 42
-is($x->accuracy(), 42, '$x has still A of 42');
+# set and check the instance accuracy
+$x->accuracy(2);
+is($x->accuracy(), 2, '$x has A of 2');
-# reset for further tests
+# change the class accuracy
+$class->accuracy(3);
+is($class->accuracy(), 3, "$class has A of 3");
+
+# verify that the instance accuracy hasn't changed
+is($x->accuracy(), 2, '$x still has A of 2');
+
+# change the instance accuracy
+$x->accuracy(undef);
+is($x->accuracy(), undef, '$x now has A of undef');
+
+# check the class accuracy
+is($class->accuracy(), 3, "$class still has A of 3");
+
+# change the class accuracy again
$class->accuracy(undef);
+is($class->accuracy(), undef, "$class now has A of undef");
+
+# Precision
+
+# set and check the class precision
+$class->precision(1);
+is($class->precision(), 1, "$class has A of 1");
+
+# a new instance gets the class precision
+$x = $class->new(123);
+is($x->precision(), 1, '$x has A of 1');
+
+# set and check the instance precision
+$x->precision(2);
+is($x->precision(), 2, '$x has A of 2');
+
+# change the class precision
+$class->precision(3);
+is($class->precision(), 3, "$class has A of 3");
+
+# verify that the instance precision hasn't changed
+is($x->precision(), 2, '$x still has A of 2');
+
+# change the instance precision
+$x->precision(undef);
+is($x->precision(), undef, '$x now has A of undef');
+
+# check the class precision
+is($class->precision(), 3, "$class still has A of 3");
+
+# change the class precision again
$class->precision(undef);
+is($class->precision(), undef, "$class now has A of undef");
}
# bug with blog(Math::BigFloat, Math::BigInt)
--- End Message ---
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Source-Version: 1.6011-3
Done: Roland Rosenfeld
We believe that the bug you reported is fixed in
Processed: Re: Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Processing control commands: > tags -1 + moreinfo Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message Added tag(s) moreinfo. -- 1033732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Control: tags -1 + moreinfo Hi Guy, On Sat, Apr 01, 2023 at 10:09:09AM +0200, Guy Durrieu wrote: > Hello, > > Thanks for your answer ! > > Before receiving it I tried to update my BIOS to the last available version > (F51h). Without any effect. > > I am not sure I understand everything that is said in your link, except I > must wait for the next updates... Right ? AFAIK there is no commit upstream with fixes tag on that commit. But Bjorn suspects that might be the suspicious commit introducing the issue. Would you be able to build a kernel 6.1.20 with that patch reverted on top and see if it resolved your issue? Regards, Salvatore
Bug#1033757: marked as done (ghostscript: CVE-2023-28879)
Your message dated Sat, 01 Apr 2023 08:49:12 + with message-id and subject line Bug#1033757: fixed in ghostscript 10.0.0~dfsg-11 has caused the Debian Bug report #1033757, regarding ghostscript: CVE-2023-28879 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.) -- 1033757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghostscript Version: 10.0.0~dfsg-9 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=706494 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ghostscript. CVE-2023-28879[0]: | In Artifex Ghostscript through 10.01.0, there is a buffer overflow | leading to potential corruption of data internal to the PostScript | interpreter, in base/sbcp.c. This affects BCPEncode, BCPDecode, | TBCPEncode, and TBCPDecode. If the write buffer is filled to one byte | less than full, and one then tries to write an escaped character, two | bytes are written. I'm preparing an update for this issue. 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-2023-28879 https://www.cve.org/CVERecord?id=CVE-2023-28879 [1] https://bugs.ghostscript.com/show_bug.cgi?id=706494 (not public) Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 10.0.0~dfsg-11 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of ghostscript, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ghostscript 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, 01 Apr 2023 09:48:32 +0200 Source: ghostscript Architecture: source Version: 10.0.0~dfsg-11 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Salvatore Bonaccorso Closes: 1033757 Changes: ghostscript (10.0.0~dfsg-11) unstable; urgency=medium . * QA upload. * Prevent buffer overrun in (T)BCP encoding (CVE-2023-28879) (Closes: #1033757) Checksums-Sha1: d979e4f9cc8f632fc786f69bbc715a10757ce093 2987 ghostscript_10.0.0~dfsg-11.dsc 7946dd26efb4274e62d31d6d955a839f34f135c5 85428 ghostscript_10.0.0~dfsg-11.debian.tar.xz 7f47fd6c6a2baa5f0772ff6454ed61b7525cc239 7081 ghostscript_10.0.0~dfsg-11_source.buildinfo Checksums-Sha256: e4e6af2e982228ea452f5dbd64f29f79db10f731571174adf3b37b0b913a5c97 2987 ghostscript_10.0.0~dfsg-11.dsc 41861b53c348ce9b9cbe64cac2ecbba44d3bbb16c87a8cb807336f3107fc4650 85428 ghostscript_10.0.0~dfsg-11.debian.tar.xz dd83d1e03ac9b7d8cf139ab182a49843cd1acadbf84239970b2a8bf9aaf2e804 7081 ghostscript_10.0.0~dfsg-11_source.buildinfo Files: 202c53a276ed471f7e7333c15ae6f99b 2987 text optional ghostscript_10.0.0~dfsg-11.dsc 360c629443995dd5aee569a840efe8cf 85428 text optional ghostscript_10.0.0~dfsg-11.debian.tar.xz 4cf2a2c9332621fb66e496d7f7a16b39 7081 text optional ghostscript_10.0.0~dfsg-11_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmQn7XFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EP6YP/RFxxbXSCnNnNnFsKiF/dn6jV3+JLwir wuiBweug4zyGhAcFd1m6+nyVlLg/PHQxDNREF792XWoNl2wrU4hTSq/uovvkMHTQ w3Dk3X/t0lrcXfsIOofjAbYWQX0zVhn8Ood1DCTuhtzk1i3AThlZb1xNSI3IWEVp UvBBBuKm4nPFOtlTRyHuz0tOYmDhh52mgCNbmNek4fI14bqHOLw/rev+L8eeVtJz /7zHk/fTc4+O8GXCufrcvAGCvUDxso7F9arbNUJ0we3GgU6F7P+TxyIs5SfLwsMw NNuSWYZaj6eBxh5Cl+NZx7dx6dRyvq96DkrGsjIM14PyYDV/LfPFi+eSdPKQ9yzs +0IK5dvISzZHMH5eXUpkjTwUo3Tr5f/YoXstL/MmMGzFYruqfvNvmkV4AJLiN/JO hvQgLS6Eq7N5xt69X0y+GFvDU1IsnRf2rrm/UY42EK/NFN3ztXyuBD+kxyCeeQR0 xvsz5hu5j5YztmdkTGLjp2IYFayez+NKpTvSFRSI4Q6zvlhkiBKJ41tRBp8nKK8N
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
On Saturday, 1 April 2023 10:09:09 CEST Guy Durrieu wrote:
> Le 01/04/2023 à 09:25, Bjørn Mork a écrit :
> > Guy Durrieu writes:
> >>
> >> [ 0.117782] Kernel panic — not syncing: timer doesn’t work through
> >> Interrupt-
> >> remapped I0-APIC
> >> [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1
> >> Debian
> >> 6.1.20-1
> >> [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming
> >> 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020
> >> [ 0.117982] Call Trace:
> >> [ 0.118634]
> >> [ 0.118685] dump_stack_lvl+0x44/0x5c
> >> [ 0.118143] panic+0x118/0x2ed
> >> [ 0.118198] panic_if_irq_remap.cold+0x5/0x5
> >> [ 0.118256] setup_I0_APIC+0x3db/0x64b
> >> [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40
> >> [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240
> >> [ 0.118429] apic_intr_node_init+0x101/0x106
> >> [ 0.118485] x86_late_time_init+0x20/0x34
> >> [ 0.118542] start_kerne1+0x667/0x727
> >> [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb
> >> [ 0.118658]
> >> [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work
> >> through
> >> Interrupt-remapped IO-APIC J---
> >>
> >
> > Extremely suspiscious commit in the v6.1.15..v6.1.20 update:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > /commit/?id=ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b
>
> I am not sure I understand everything that is said in your link, except
> I must wait for the next updates... Right ?
When triaging a bug, we usually try to find the upstream commit which *caused*
the issue and Bjørn thinks it's the one referenced.
To test whether that's indeed the case, there's a procedure here:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.1
These are preliminary steps to the actual one which is para 4.2.2 and I have
attached a patch which reverts the referenced commit and that .patch file is
what you give as an argument to `bash debian/bin/test-patches`.
If you could try that to see if that indeed fixes the issue, that would be
very helpful.
HTH
>From 2e6223080905caf4c775680201700b243caa91a9 Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Sat, 1 Apr 2023 10:32:31 +0200
Subject: [PATCH] Revert "x86/acpi/boot: Do not register processors that cannot
be onlined for x2APIC"
This reverts commit ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b.
---
arch/x86/kernel/acpi/boot.c | 19 +++
1 file changed, 3 insertions(+), 16 deletions(-)
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
index 518bda50068c..907cc98b1938 100644
--- a/arch/x86/kernel/acpi/boot.c
+++ b/arch/x86/kernel/acpi/boot.c
@@ -188,17 +188,6 @@ static int acpi_register_lapic(int id, u32 acpiid, u8 enabled)
return cpu;
}
-static bool __init acpi_is_processor_usable(u32 lapic_flags)
-{
- if (lapic_flags & ACPI_MADT_ENABLED)
- return true;
-
- if (acpi_support_online_capable && (lapic_flags & ACPI_MADT_ONLINE_CAPABLE))
- return true;
-
- return false;
-}
-
static int __init
acpi_parse_x2apic(union acpi_subtable_headers *header, const unsigned long end)
{
@@ -223,10 +212,6 @@ acpi_parse_x2apic(union acpi_subtable_headers *header, const unsigned long end)
if (apic_id == 0x)
return 0;
- /* don't register processors that cannot be onlined */
- if (!acpi_is_processor_usable(processor->lapic_flags))
- return 0;
-
/*
* We need to register disabled CPU as well to permit
* counting disabled CPUs. This allows us to size
@@ -265,7 +250,9 @@ acpi_parse_lapic(union acpi_subtable_headers * header, const unsigned long end)
return 0;
/* don't register processors that can not be onlined */
- if (!acpi_is_processor_usable(processor->lapic_flags))
+ if (acpi_support_online_capable &&
+ !(processor->lapic_flags & ACPI_MADT_ENABLED) &&
+ !(processor->lapic_flags & ACPI_MADT_ONLINE_CAPABLE))
return 0;
/*
--
2.40.0
signature.asc
Description: This is a digitally signed message part.
Processed: bug 1033784 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=147484
Processing commands for cont...@bugs.debian.org: > forwarded 1033784 https://rt.cpan.org/Ticket/Display.html?id=147484 Bug #1033784 [src:libmath-bigint-gmp-perl] FTBFS: mbimbf.t fails with libmath-bigint-perl 1.999838 Set Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=147484'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033785: irssi: CVE-2023-29132
Source: irssi Version: 1.4.3-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for irssi. CVE-2023-29132[0]: | Irssi SA-2023-03 / Use after free in printing routine 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-2023-29132 https://www.cve.org/CVERecord?id=CVE-2023-29132 [1] https://irssi.org/security/irssi_sa_2023_03.txt [2] https://github.com/irssi/irssi/commit/c554a45738712219c066897b09a44d99afeb4240 Regards, Salvatore
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Hello, Thanks for your answer ! Before receiving it I tried to update my BIOS to the last available version (F51h). Without any effect. I am not sure I understand everything that is said in your link, except I must wait for the next updates... Right ? Best regards. -- Guy Le 01/04/2023 à 09:25, Bjørn Mork a écrit : Guy Durrieu writes: [ 0.117782] Kernel panic — not syncing: timer doesn’t work through Interrupt- remapped I0-APIC [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 Debian 6.1.20-1 [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020 [ 0.117982] Call Trace: [ 0.118634] [ 0.118685] dump_stack_lvl+0x44/0x5c [ 0.118143] panic+0x118/0x2ed [ 0.118198] panic_if_irq_remap.cold+0x5/0x5 [ 0.118256] setup_I0_APIC+0x3db/0x64b [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40 [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240 [ 0.118429] apic_intr_node_init+0x101/0x106 [ 0.118485] x86_late_time_init+0x20/0x34 [ 0.118542] start_kerne1+0x667/0x727 [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb [ 0.118658] [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through Interrupt-remapped IO-APIC J--- Extremely suspiscious commit in the v6.1.15..v6.1.20 update: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b Bjørn
Bug#1033784: FTBFS: mbimbf.t fails with libmath-bigint-perl 1.999838
Source: libmath-bigint-gmp-perl
Version: 1.6011-2
Severity: serious
Tags: ftbfs, patch
Dear Maintainer,
yesterday I uploaded libmath-bigint-perl 1.999838-1, which fixes RC
bugs.
Bug with this version of libmath-bigint-perl now
libmath-bigint-gmp-perl fails to build, since two test cases in
t/mbimbf.t fail:
ok 729 - $x has A of 42
ok 730 - $x has A from global
not ok 731 - $x has still A of 42
ok 732 - $x has A of 42
ok 733 - $x has A from global
not ok 734 - $x has still A of 42
t/mbimbf.t in libmath-bigint-perl and libmath-bigint-gmp-perl where
identical except
-use Math::BigInt only => 'Calc';
+use Math::BigInt only => 'GMP';
before the update of libmath-bigint-perl, but Upstream
extended/changed mbimbf.t in 1.999838, so IMHO it should be changed in
libmath-bigint-gmp-perl accordingly.
The attached patch merges mbimbf.t changes from libmath-bigint-perl
1.999838.
With this patch libmath-bigint-gmp-perl builds with a working test
suite.
Greetings
Roland
From: Roland Rosenfeld
Subject: Adapt mbimbf.t to the one from Math::BigInt 1.999838
Date: Sat, 01 Apr 2023 09:57:20 +0200
--- a/t/mbimbf.t
+++ b/t/mbimbf.t
@@ -7,7 +7,7 @@ use strict;
use warnings;
use Test::More tests => 712 # tests in require'd file
-+ 26; # tests in this file
++ 52; # tests in this file
use Math::BigInt only => 'GMP';
use Math::BigFloat;
@@ -58,24 +58,71 @@ foreach my $class (qw/Math::BigInt Math:
}
foreach my $class (qw/Math::BigInt Math::BigFloat/) {
-$class->accuracy(42);
+my $x;
-# $x gets A of 42, too!
-my $x = $class->new(123);
+# Accuracy
-# really?
-is($x->accuracy(), 42, '$x has A of 42');
+# set and check the class accuracy
+$class->accuracy(1);
+is($class->accuracy(), 1, "$class has A of 1");
-# $x has no A, but the global is still in effect for $x so the return value
-# of that operation should be 42, not undef
-is($x->accuracy(undef), 42, '$x has A from global');
+# a new instance gets the class accuracy
+$x = $class->new(123);
+is($x->accuracy(), 1, '$x has A of 1');
-# so $x should still have A = 42
-is($x->accuracy(), 42, '$x has still A of 42');
+# set and check the instance accuracy
+$x->accuracy(2);
+is($x->accuracy(), 2, '$x has A of 2');
-# reset for further tests
+# change the class accuracy
+$class->accuracy(3);
+is($class->accuracy(), 3, "$class has A of 3");
+
+# verify that the instance accuracy hasn't changed
+is($x->accuracy(), 2, '$x still has A of 2');
+
+# change the instance accuracy
+$x->accuracy(undef);
+is($x->accuracy(), undef, '$x now has A of undef');
+
+# check the class accuracy
+is($class->accuracy(), 3, "$class still has A of 3");
+
+# change the class accuracy again
$class->accuracy(undef);
+is($class->accuracy(), undef, "$class now has A of undef");
+
+# Precision
+
+# set and check the class precision
+$class->precision(1);
+is($class->precision(), 1, "$class has A of 1");
+
+# a new instance gets the class precision
+$x = $class->new(123);
+is($x->precision(), 1, '$x has A of 1');
+
+# set and check the instance precision
+$x->precision(2);
+is($x->precision(), 2, '$x has A of 2');
+
+# change the class precision
+$class->precision(3);
+is($class->precision(), 3, "$class has A of 3");
+
+# verify that the instance precision hasn't changed
+is($x->precision(), 2, '$x still has A of 2');
+
+# change the instance precision
+$x->precision(undef);
+is($x->precision(), undef, '$x now has A of undef');
+
+# check the class precision
+is($class->precision(), 3, "$class still has A of 3");
+
+# change the class precision again
$class->precision(undef);
+is($class->precision(), undef, "$class now has A of undef");
}
# bug with blog(Math::BigFloat, Math::BigInt)
Processed: nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194,
Processing control commands: > clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 Bug #1033774 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Bug 1033774 cloned as bugs 1033775-1033783 > reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Bug #1033775 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-legacy-340xx'. Ignoring request to alter found versions of bug #1033775 to the same values previously set Ignoring request to alter fixed versions of bug #1033775 to the same values previously set Bug #1033775 [src:nvidia-graphics-drivers-legacy-340xx] nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.76-6. > retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-0184, > CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, > CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Bug #1033775 [src:nvidia-graphics-drivers-legacy-340xx] nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Changed Bug title to 'nvidia-graphics-drivers-legacy-340xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191' from 'nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191'. > tag -2 + wontfix Bug #1033775 [src:nvidia-graphics-drivers-legacy-340xx] nvidia-graphics-drivers-legacy-340xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Added tag(s) wontfix. > reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Bug #1033776 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-legacy-390xx'. Ignoring request to alter found versions of bug #1033776 to the same values previously set Ignoring request to alter fixed versions of bug #1033776 to the same values previously set Bug #1033776 [src:nvidia-graphics-drivers-legacy-390xx] nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Marked as found in versions nvidia-graphics-drivers-legacy-390xx/390.48-4. > retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-0184, > CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, > CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Bug #1033776 [src:nvidia-graphics-drivers-legacy-390xx] nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Changed Bug title to 'nvidia-graphics-drivers-legacy-390xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191' from 'nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191'. > tag -3 + wontfix Bug #1033776 [src:nvidia-graphics-drivers-legacy-390xx] nvidia-graphics-drivers-legacy-390xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Added tag(s) wontfix. > reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Bug #1033777 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2023-0184,
Bug#1033774: nvidia-graphics-drivers: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-019
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 -10 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 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-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 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-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 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-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 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-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: tag -8 + wontfix Control: close -8 510.85.02-2 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -9 515.48.07-1 Control: found -9 525.60.13-1 Control: reassign -10 src:nvidia-open-gpu-kernel-modules 515.43.04-1 Control: retitle -10 nvidia-open-gpu-kernel-modules: CVE-2023-0184, CVE-2023-0189, CVE-2023-0180, CVE-2023-0183, CVE-2023-0185, CVE-2023-0187, CVE-2023-0198, CVE-2023-0199, CVE-2023-0188, CVE-2023-0190, CVE-2023-0194, CVE-2023-0195, CVE-2023-0191 Control: found -10 520.56.06-1 Control: found -10 525.85.12-1 Control: found -10 530.30.02-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: fixed -1 530.41.03-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5452 CVE-2023-0189 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. CVE-2023-0184 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer handler, which may lead to denial of service, escalation of privileges, information disclosure, and data tampering. CVE-2023-0181 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in a kernel mode layer handler, where memory permissions are not correctly checked, which may lead to denial of service and data tampering. CVE-2023-0191 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer handler, where an out-of-bounds access may lead to denial of service or data tampering. CVE-2023-0183 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer where an out-of-bounds write can lead to denial of service and data tampering. CVE-2023-0180 NVIDIA GPU Display Driver for Linux contains a vulnerability in a kernel mode layer handler, which may lead to denial of service or information disclosure. CVE-2023-0185 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Guy Durrieu writes: > > [ 0.117782] Kernel panic — not syncing: timer doesn’t work through > Interrupt- > remapped I0-APIC > [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 > Debian > 6.1.20-1 > [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming > 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020 > [ 0.117982] Call Trace: > [ 0.118634] > [ 0.118685] dump_stack_lvl+0x44/0x5c > [ 0.118143] panic+0x118/0x2ed > [ 0.118198] panic_if_irq_remap.cold+0x5/0x5 > [ 0.118256] setup_I0_APIC+0x3db/0x64b > [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40 > [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240 > [ 0.118429] apic_intr_node_init+0x101/0x106 > [ 0.118485] x86_late_time_init+0x20/0x34 > [ 0.118542] start_kerne1+0x667/0x727 > [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb > [ 0.118658] > [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through > Interrupt-remapped IO-APIC J--- > Extremely suspiscious commit in the v6.1.15..v6.1.20 update: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b Bjørn
Bug#1012233: marked as done (python3-ml-collections: overly generic python module name: /usr/lib/python3/dist-packages/docs/conf.py)
Your message dated Sat, 01 Apr 2023 06:34:15 + with message-id and subject line Bug#1012233: fixed in python-ml-collections 0.1.1-2 has caused the Debian Bug report #1012233, regarding python3-ml-collections: overly generic python module name: /usr/lib/python3/dist-packages/docs/conf.py 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.) -- 1012233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-ml-collections Version: 0.1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package uses a very generic python module name that now clashes with other packages: /usr/lib/python3/dist-packages/docs/conf.py Andreas --- End Message --- --- Begin Message --- Source: python-ml-collections Source-Version: 0.1.1-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of python-ml-collections, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated python-ml-collections package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Apr 2023 11:29:28 +0530 Source: python-ml-collections Architecture: source Version: 0.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Nilesh Patra Closes: 1012233 Changes: python-ml-collections (0.1.1-2) unstable; urgency=medium . * Team Upload. * Remove docs before building (Closes: #1012233) * Bump Standards-Version to 4.6.2 (no changes needed) * Add python-is-python3 to test-deps * Add Suggests on python-is-python3 * Update copyright years * d/lintian-overrides: Override FP Checksums-Sha1: dea404ebee39ad8b44137dcc7ab0a094697e65a1 1702 python-ml-collections_0.1.1-2.dsc e67e423f196f5e9fc93a117b9b0b6da1f951eb25 4628 python-ml-collections_0.1.1-2.debian.tar.xz 2384cc32b5118225079ad6dc0d4057c13d737cd4 5863 python-ml-collections_0.1.1-2_amd64.buildinfo Checksums-Sha256: 90c5a89f76f8a90db11d73773580deaeb443066c23d810b62f76f24e5eff631d 1702 python-ml-collections_0.1.1-2.dsc 5c9cf40cd23f0311ee46e1308997fdb31445137ba2ed8047ff2968141f1722d0 4628 python-ml-collections_0.1.1-2.debian.tar.xz bea12610bf33a4deec463e428d840c3bf525316753baba19c3a2e16b3e30e55a 5863 python-ml-collections_0.1.1-2_amd64.buildinfo Files: cecf4a907532ad7d37063d84827d23ac 1702 python optional python-ml-collections_0.1.1-2.dsc a38ff5aa4da86a613fe870999792a87d 4628 python optional python-ml-collections_0.1.1-2.debian.tar.xz f5330496f49fb2c21ec675d6ccd12325 5863 python optional python-ml-collections_0.1.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZCfKJwAKCRAqJ5BL1yQ+ 2qOhAQDdMrzIONZi47fC6EpklpTO06JBar7+KmAi7hvyBv2wMQEAsVeZoi9RBLfJ 3tlGFkrNVgF4+TMW+iXKDEXMSmFPtgk= =VxTm -END PGP SIGNATURE End Message ---
