Bug#1070761: bullseye-pu: package bart-cuda/0.6.00-1+deb11u1
On Tue, 2024-05-14 at 20:51 +0200, Santiago Vila wrote: > > > As bart-cuda build-depends on nvidia-cuda-toolkit, which is in > > > non- > > > free, bart-cuda is not buildable on the buildd network, so this > > > will > > > also need a binary upload to be performed. > > > > Ok, what's the best way to solve this? Can you reject the upload > > so that I do it again including .debs? > > Nevermind. I see that the upload was already accepted, and what is > missing is a binary-only upload matching the already existing source. > Yes, sorry if I wasn't clear enough about that. > I'll make the missing binary upload. Thanks. Regards, Adam
Bug#1070761: bullseye-pu: package bart-cuda/0.6.00-1+deb11u1
On Wed, 2024-05-08 at 17:18 +0200, Santiago Vila wrote: > This upload fixes Bug #1070757 FTBFS in bullseye. > Note: A similar request for a similar bug has been made for package > "bart". > > [ Impact ] > Anybody who try to build the package from source may find > that the package FTBFS unexpectedly. As bart-cuda build-depends on nvidia-cuda-toolkit, which is in non- free, bart-cuda is not buildable on the buildd network, so this will also need a binary upload to be performed. Regards, Adam
Bug#1065013: nvidia-graphics-drivers 470.239.06-1 flagged for acceptance
On Wed, 2024-05-08 at 18:22 +0100, Adam D. Barratt wrote: > On Wed, 2024-05-08 at 19:18 +0200, Andreas Beckmann wrote: > > On 05/05/2024 20.52, Adam D Barratt wrote: > > > Package: nvidia-graphics-drivers > > > Version: 470.239.06-1 > > > > > Explanation: upstream security fixes [CVE-2022-42265 CVE-2024- > > > 0074 > > > CVE-2024-0078] > > > > Can we push these packages to bullseye-updates? > > The kernel change that recently caused problems for the nvidia > > modules > > in bookworm has now reached bullseye, too: #1070726, but the new > > upstream already sitting in bullseye-pu is sufficient to fix that. > > Would wording similar to > https://lists.debian.org/debian-stable-announce/2024/02/msg2.html > be accurate / suitable? (With the 12.5 reference changed to the > relevant DSA number.) Not sure if you saw the previous mail, but see below for suggested SUA text. Regards, Adam === This update addresses problems in three non-free driver packages supporting nVidia graphics cards. The Linux kernel released in DSA 5681-1 changed an inlined function to call two GPL-only symbols, making that function inaccessible to non-free kernel modules. As a result, the nVidia kernel modules cannot be built via DKMS at installation time for the updated kernel. The following packages have been updated to correct the problem: Source package Fixed version == = nvidia-graphics-drivers470.239.06-1 nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 nvidia-settings470.239.06-1 If you use the affected packages, we recommend you upgrade to these versions. ===
Bug#1070670: shim-helpers-i386-signed 1+15.8+1~deb11u1 flagged for acceptance
package release.debian.org tags 1070670 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: shim-helpers-i386-signed Version: 1+15.8+1~deb11u1 Explanation: rebuild against shim 15.8.1
Bug#1070670: shim-helpers-arm64-signed 1+15.8+1~deb11u1 flagged for acceptance
package release.debian.org tags 1070670 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: shim-helpers-arm64-signed Version: 1+15.8+1~deb11u1 Explanation: rebuild against shim 15.8.1
Bug#1070660: shim-helpers-i386-signed 1+15.8+1~deb12u1 flagged for acceptance
package release.debian.org tags 1070660 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: shim-helpers-i386-signed Version: 1+15.8+1~deb12u1 Explanation: rebuild against shim 15.8.1
Bug#1070670: shim-helpers-amd64-signed 1+15.8+1~deb11u1 flagged for acceptance
package release.debian.org tags 1070670 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: shim-helpers-amd64-signed Version: 1+15.8+1~deb11u1 Explanation: rebuild against shim 15.8.1
Bug#1070660: shim-helpers-arm64-signed 1+15.8+1~deb12u1 flagged for acceptance
package release.debian.org tags 1070660 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: shim-helpers-arm64-signed Version: 1+15.8+1~deb12u1 Explanation: rebuild against shim 15.8.1
Bug#1070660: shim-helpers-amd64-signed 1+15.8+1~deb12u1 flagged for acceptance
package release.debian.org tags 1070660 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: shim-helpers-amd64-signed Version: 1+15.8+1~deb12u1 Explanation: rebuild against shim 15.8.1
Bug#1070660: shim 15.8-1~deb12u1 flagged for acceptance
package release.debian.org tags 1070660 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: shim Version: 15.8-1~deb12u1 Explanation: new upstream release
Bug#1070670: shim 15.8-1~deb11u1 flagged for acceptance
package release.debian.org tags 1070670 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: shim Version: 15.8-1~deb11u1 Explanation: new upstream release
Bug#1065013: nvidia-graphics-drivers 470.239.06-1 flagged for acceptance
On Wed, 2024-05-08 at 19:18 +0200, Andreas Beckmann wrote: > On 05/05/2024 20.52, Adam D Barratt wrote: > > Package: nvidia-graphics-drivers > > Version: 470.239.06-1 > > > Explanation: upstream security fixes [CVE-2022-42265 CVE-2024-0074 > > CVE-2024-0078] > > Can we push these packages to bullseye-updates? > The kernel change that recently caused problems for the nvidia > modules > in bookworm has now reached bullseye, too: #1070726, but the new > upstream already sitting in bullseye-pu is sufficient to fix that. Would wording similar to https://lists.debian.org/debian-stable-announce/2024/02/msg2.html be accurate / suitable? (With the 12.5 reference changed to the relevant DSA number.) Regards, Adam
Bug#1067106: bullseye-pu: package nvidia-settings/470.239.06-1
Control: tags -1 + pending On Mon, 2024-05-06 at 20:29 +0200, Andreas Beckmann wrote: > while accepting the nvidia stack yesterday (many thanks for that!) > you missed to tag etc. this bug, while the package was accepted > (perhaps attributed to a different bug?). Yep, the metadata in the comment file had a typo in the bug number. Fixed now, thanks. Regards, Adam
Bug#1070490: libc6: Unpacking libc6:amd64 2.28-10+deb10u3 over 2.28-10+deb10u2 breaks system
On Mon, 2024-05-06 at 13:02 +0200, Jan Krčmář wrote: > Package: libc6 > Version: 2.28-10+deb10u3 > > Upgrading the system (Debian 10/Buster) causes corrupted system, > ending with kernel panic and unbootable system. > [...] > The following packages will be upgraded: > apt apt-transport-https apt-utils base-files ca-certificates The fact that APT is being upgraded here seems strange - APT hasn't changed in buster for 3 years. What's your base system? > [...] > Unpacking libc6:amd64 (2.28-10+deb10u3) over (2.28-10+deb10u2) ... > Replaced by files in installed package libcrypt1:amd64 (1:4.4.18-4) > ... This, on the other hand, looks like you've done something odd to your system. libcrypt1 doesn't exist until bullseye, so at some point you have partially upgraded your base system. In conjunction with your pre- upgrade system apparently having an APT version that's /older/ than the one in buster, this feels odd. Regards, Adam
Bug#1067016: nvidia-settings 470.239.06-1 flagged for acceptance
package release.debian.org tags 1067016 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-settings Version: 470.239.06-1 Explanation: new upstrem bugfix release; build for ppc64el
Bug#1065053: nvidia-graphics-drivers-tesla-470 470.239.06-1~deb11u1 flagged for acceptance
package release.debian.org tags 1065053 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-graphics-drivers-tesla-470 Version: 470.239.06-1~deb11u1 Explanation: new upstream LTS release [CVE-2024-0074 CVE-2024-0078 CVE-2022-42265]
Bug#1065013: nvidia-graphics-drivers 470.239.06-1 flagged for acceptance
package release.debian.org tags 1065013 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nvidia-graphics-drivers Version: 470.239.06-1 Explanation: upstream security fixes [CVE-2022-42265 CVE-2024-0074 CVE-2024-0078]
Bug#1067843: nvidia-open-gpu-kernel-modules 535.161.08-1~deb12u1 flagged for acceptance
package release.debian.org tags 1067843 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-open-gpu-kernel-modules Version: 535.161.08-1~deb12u1 Explanation: update to 535 series LTS drivers [CVE-2023-0180 CVE-2023-0183 CVE-2023-0184 CVE-2023-0185 CVE-2023-0187 CVE-2023-0188 CVE-2023-0189 CVE-2023-0190 CVE-2023-0191 CVE-2023-0194 CVE-2023-0195 CVE-2023-0198 CVE-2023-0199 CVE-2023-25515 CVE-2023-25516 CVE-2023-31022 CVE-2024-0074 CVE-2024-0075 CVE-2024-0078]
Bug#1067821: nvidia-graphics-drivers 535.161.08-2~deb12u1 flagged for acceptance
package release.debian.org tags 1067821 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-graphics-drivers Version: 535.161.08-2~deb12u1 Explanation: new upstream stable release [CVE-2023-0180 CVE-2023-0183 CVE-2023-0184 CVE-2023-0185 CVE-2023-0187 CVE-2023-0188 CVE-2023-0189 CVE-2023-0190 CVE-2023-0191 CVE-2023-0194 CVE-2023-0195 CVE-2023-0198 CVE-2023-0199 CVE-2023-25515 CVE-2023-25516 CVE-2023-31022 CVE-2024-0074 CVE-2024-0075 CVE-2024-0078]
Bug#1067745: nvidia-settings 535.171.04-1~deb12u1 flagged for acceptance
package release.debian.org tags 1067745 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-settings Version: 535.171.04-1~deb12u1 Explanation: new upstream LTS release
Bug#1067742: nvidia-xconfig 535.171.04-1~deb12u1 flagged for acceptance
package release.debian.org tags 1067742 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-xconfig Version: 535.171.04-1~deb12u1 Explanation: new upstream LTS release
Bug#1065653: nvidia-modprobe 535.161.07-1~deb12u1 flagged for acceptance
package release.debian.org tags 1065653 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-modprobe Version: 535.161.07-1~deb12u1 Explanation: prepare to switch to 535 series LTS drivers
Bug#1067739: nvidia-persistenced 535.171.04-1~deb12u1 flagged for acceptance
package release.debian.org tags 1067739 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-persistenced Version: 535.171.04-1~deb12u1 Explanation: switch to 535 series LTS drivers; update list of supported drivers
Bug#1070202: RM: rust-atk-sys/experimental -- ROM; RoM; unmaintained library
On Wed, 2024-05-01 at 21:15 +0200, Matthias Geiger wrote: > I uploaded an experimental version some time ago that wasn't picked > up by dak apperantly when it was removing it from unstable. For reference, that's expected - the removal command operates on a single suite, so removals from more than one suite need a bug for each. Regards, Adam
Bug#1070175: RM: salt/3002.6+dfsg1-4+deb11u1
On Wed, 2024-05-01 at 19:46 +0200, Moritz Muehlenhoff wrote: > On Wed, May 01, 2024 at 06:29:29PM +0100, Adam D. Barratt wrote: > > On Wed, 2024-05-01 at 13:02 +0200, Moritz Muehlenhoff wrote: > > > Please remove salt in the next Bullseye point release. > > > It was already removed frm unstable for being unsupportable > > > and unmaintained (https:://bugs.debian.org/1069654). > > > > > > There are two related packages which need to be removed > > > alongside, since salt-common depends on them (but which > > > have no other dependencies outside of salt): > > > > > > pytest-salt-factories 0.93.0-1 > > > pytest-testinfra 6.1.0-1 > > > > I'm not doubting whether at least the former should be removed, but > > "salt-common depends on them" isn't a reason to remove things in > > itself. A relationship in the opposite direction certainly would be > > (i.e. "they depend on salt-common"). > > It's actually build dependencies, both pytest-salt-factories and > pytest-testinfra build depend on salt-common. Ah, that makes more sense. Thanks for the clarification. Regards, Adam
Bug#1070175: RM: salt/3002.6+dfsg1-4+deb11u1
On Wed, 2024-05-01 at 13:02 +0200, Moritz Muehlenhoff wrote: > Please remove salt in the next Bullseye point release. > It was already removed frm unstable for being unsupportable > and unmaintained (https:://bugs.debian.org/1069654). > > There are two related packages which need to be removed > alongside, since salt-common depends on them (but which > have no other dependencies outside of salt): > > pytest-salt-factories 0.93.0-1 > pytest-testinfra 6.1.0-1 I'm not doubting whether at least the former should be removed, but "salt-common depends on them" isn't a reason to remove things in itself. A relationship in the opposite direction certainly would be (i.e. "they depend on salt-common"). Regards, Adam
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-2~deb12u1
On Sun, 2024-04-28 at 13:43 +0200, Andreas Beckmann wrote: > Please reject nvidia-graphics-drivers/535.161.08-1~deb12u1, nvidia- > driver-full is uninstallable on ppc64el (but that was hidden by the > other t64 transition blockers). Done, thanks for letting us know. Regards, Adam
Bug#1070005: mirror submission for mirrors.hostico.ro
On Sun, 2024-04-28 at 13:28 +, Hostico wrote: > Package: mirrors > Severity: wishlist > User: mirr...@packages.debian.org > Usertags: mirror-submission > > Submission-Type: new > Site: mirrors.hostico.ro This is *not* a new submission. Please do not submit duplicate details for already listed mirrors. You were already advised two days ago to allow a few days for your mirror to automatically return to the published listing and that you did not need to resubmit. That advice has not changed in the meantime. If the intent was to change some details, the submission form has an "update" option; highlighting which details you believe have changed via a comment helps in such cases. Regards, Adam
Bug#1069640: lintian still links to lintian.debian.org but it is gone
Package: lintian Version: 2.117.0 Severity: normal X-Debbugs-Cc: deb...@voltagex.org Dear Maintainer, This is related to #1053710 (but apparently Affects: isn't the right tag here? There should be a Related: tag IMO) * What led up to the situation? Lintian produces messages like "E: mypackage: no-copyright-file" where no-copyright-file is a link to https://lintian.debian.org/tags/no-copyright-file. lintian.debian.org is gone as of 2023 so these URLs should be changed. * What outcome did you expect instead? Being able to click the hyperlink (TIL OSC8) and find out what the warning / note means -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.9.0-rc3 (SMP w/64 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils2.42-4 ii bzip2 1.0.8-5.1 ii diffstat1.66-1 ii dpkg1.22.4 ii dpkg-dev1.22.4 ii file1:5.45-2+b1 ii gettext 0.21-14+b1 ii gpg 2.2.40-1.1+b1 ii intltool-debian 0.35.0+20060710.6 ii iso-codes 4.16.0-1 ii libapt-pkg-perl 0.1.40+b3 ii libarchive-zip-perl 1.68-1 ii libberkeleydb-perl 0.64-2+b2 ii libcapture-tiny-perl0.48-2 ii libclass-xsaccessor-perl1.19-4+b2 ii libclone-perl 0.46-1+b1 ii libconfig-tiny-perl 2.30-1 ii libconst-fast-perl 0.014-2 ii libcpanel-json-xs-perl 4.37-1+b1 ii libdata-dpath-perl 0.59-1 ii libdata-validate-domain-perl0.10-1.1 ii libdata-validate-uri-perl 0.07-3 ii libdevel-size-perl 0.83-2+b2 pn libdigest-sha-perl ii libdpkg-perl1.22.4 ii libemail-address-xs-perl1.05-1+b2 ii libfile-basedir-perl0.09-2 ii libfile-find-rule-perl 0.34-3 ii libfont-ttf-perl1.06-2 ii libhtml-html5-entities-perl 0.004-3 ii libhtml-tokeparser-simple-perl 3.16-4 ii libio-interactive-perl 1.025-1 ii libipc-run3-perl0.049-1 ii libjson-maybexs-perl1.004005-1 ii liblist-compare-perl0.55-2 ii liblist-someutils-perl 0.59-1 ii liblist-utilsby-perl0.12-2 ii libmldbm-perl 2.05-4 ii libmoo-perl 2.005005-1 ii libmoox-aliases-perl0.001006-2 ii libnamespace-clean-perl 0.27-2 ii libpath-tiny-perl 0.144-1 ii libperlio-gzip-perl 0.20-1+b2 ii libperlio-utf8-strict-perl 0.010-1+b1 ii libproc-processtable-perl 0.636-1+b1 ii libregexp-wildcards-perl1.05-3 ii libsereal-decoder-perl 5.004+ds-1+b1 ii libsereal-encoder-perl 5.004+ds-1+b1 ii libsort-versions-perl 1.62-3 ii libsyntax-keyword-try-perl 0.29-1+b1 ii libterm-readkey-perl2.38-2+b2 ii libtext-levenshteinxs-perl 0.03-5+b2 ii libtext-markdown-discount-perl 0.16-1+b1 ii libtext-xslate-perl 3.5.9-1+b3 ii libtime-duration-perl 1.21-2 ii libtime-moment-perl 0.44-2+b2 ii libtimedate-perl2.3300-2 ii libunicode-utf8-perl0.62-2+b1 ii liburi-perl 5.28-1 ii libwww-mechanize-perl 2.18-1 ii libwww-perl 6.77-1 ii libxml-libxml-perl 2.0207+dfsg+really+2.0134-1+b2 ii libyaml-libyaml-perl0.89+ds-1 ii lzop1.04-2 ii man-db 2.12.0-3 ii patchutils 0.4.2-1 ii perl [libencode-perl] 5.38.2-3 ii plzip [lzip-decompressor] 1.11-1 ii t1utils 1.41-4 ii unzip 6.0-28 ii xz-utils5.6.1+really5.4.5-1 lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarch pn libtext-template-perl -- no debconf information
Bug#1068895:
was requested [ 95.339430] iwlwifi :01:00.0: FW error in SYNC CMD SCAN_REQ_UMAC [ 95.339449] CPU: 3 PID: 798 Comm: iwlist Not tainted 6.1.0-18-amd64 #1 Debian 6.1.76-1 [ 95.339458] Hardware name: AZW U59/U59, BIOS JTKT001 05/05/2022 [ 95.339463] Call Trace: [ 95.339470] [ 95.339477] dump_stack_lvl+0x44/0x5c [ 95.339497] iwl_trans_txq_send_hcmd+0x376/0x380 [iwlwifi] [ 95.339555] ? cpuusage_read+0x10/0x10 [ 95.339567] iwl_trans_send_cmd+0x62/0xf0 [iwlwifi] [ 95.339612] iwl_mvm_send_cmd+0x12/0x40 [iwlmvm] [ 95.339653] iwl_mvm_reg_scan_start+0x398/0x490 [iwlmvm] [ 95.339710] iwl_mvm_mac_hw_scan+0x4a/0x70 [iwlmvm] [ 95.339747] drv_hw_scan+0x40/0x130 [mac80211] [ 95.339879] __ieee80211_start_scan+0x255/0x6f0 [mac80211] [ 95.340004] ? cfg80211_wext_siwscan+0xb9/0x3f0 [cfg80211] [ 95.340047] ieee80211_request_scan+0x2b/0x50 [mac80211] [ 95.340082] rdev_scan+0x25/0xd0 [cfg80211] [ 95.340115] cfg80211_wext_siwscan+0x2d6/0x3f0 [cfg80211] [ 95.340148] ioctl_standard_iw_point+0x221/0x3b0 [ 95.340152] ? cfg80211_unlink_bss+0xd0/0xd0 [cfg80211] [ 95.340184] ioctl_standard_call+0xa6/0xd0 [ 95.340187] wext_handle_ioctl+0x156/0x190 [ 95.340190] sock_ioctl+0x1d2/0x330 [ 95.340194] __x64_sys_ioctl+0x8d/0xd0 [ 95.340198] do_syscall_64+0x58/0xc0 [ 95.340200] ? exit_to_user_mode_prepare+0x40/0x1e0 [ 95.340203] ? syscall_exit_to_user_mode+0x27/0x40 [ 95.340206] ? do_syscall_64+0x67/0xc0 [ 95.340207] ? do_syscall_64+0x67/0xc0 [ 95.340209] ? do_syscall_64+0x67/0xc0 [ 95.340210] ? do_syscall_64+0x67/0xc0 [ 95.340212] ? exit_to_user_mode_prepare+0x40/0x1e0 [ 95.340214] entry_SYSCALL_64_after_hwframe+0x64/0xce [ 95.340218] RIP: 0033:0x7f373ccafc5b [ 95.340221] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 95.340223] RSP: 002b:7ffccd1fa560 EFLAGS: 0246 ORIG_RAX: 0010 [ 95.340226] RAX: ffda RBX: 55dab7c8b2a0 RCX: 7f373ccafc5b [ 95.340227] RDX: 7ffccd1fa630 RSI: 8b18 RDI: 0003 [ 95.340229] RBP: 7ffccd1fa6d0 R08: 0009 R09: [ 95.340230] R10: 7f373cbc9358 R11: 0246 R12: [ 95.340231] R13: 0003 R14: R15: 7ffccd1fac30 [ 95.340234] [ 95.340245] iwlwifi :01:00.0: Scan failed! ret -5 Thanks, Adam
Bug#1068895: iwlwifi: Scanning twice on AX210 card causes crash
Package: src:linux
Version: 6.1.76-1
Severity: important
X-Debbugs-Cc: deb...@voltagex.org
Dear Maintainer,
* What led up to the situation?
Running iwlist scanning twice causes this crash - first invocation works,
second time I get "wlp1s0Interface doesn't support scanning : Input/output
error"
* What exactly did you do (or not do) that was effective (or
ineffective)?
Removing the module and modprobing it again restores the functionality - for
one scan only.
This machine has Ethernet connected so it's not a huge issue
* What was the outcome of this action?
Some kind of panic
* What outcome did you expect instead?
Scanning twice to work fine.
-- Package-specific info:
** Version:
Linux version 6.1.0-18-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64
root=UUID=5cf14832-bc35-4527-9493-ac0719d68469 ro quiet
** Tainted: WOE (12800)
* kernel issued warning
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
No idea what I've loaded but it's not related to this card.
** Kernel log:
[4570550.548134] iwlwifi :01:00.0: 0x001F010D | last host cmd
[4570550.548141] iwlwifi :01:00.0: 0x | isr status reg
[4570550.548170] iwlwifi :01:00.0: IML/ROM dump:
[4570550.548177] iwlwifi :01:00.0: 0x0B03 | IML/ROM error/state
[4570550.548205] iwlwifi :01:00.0: 0x7FFC | IML/ROM data1
[4570550.548231] iwlwifi :01:00.0: 0x0090 | IML/ROM WFPM_AUTH_KEY_0
[4570550.548260] iwlwifi :01:00.0: Fseq Registers:
[4570550.548277] iwlwifi :01:00.0: 0x6100 | FSEQ_ERROR_CODE
[4570550.548302] iwlwifi :01:00.0: 0x00440007 | FSEQ_TOP_INIT_VERSION
[4570550.548327] iwlwifi :01:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION
[4570550.548353] iwlwifi :01:00.0: 0xA652 | FSEQ_OTP_VERSION
[4570550.548371] iwlwifi :01:00.0: 0x0002 | FSEQ_TOP_CONTENT_VERSION
[4570550.548396] iwlwifi :01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[4570550.548421] iwlwifi :01:00.0: 0x00400410 | FSEQ_CNVI_ID
[4570550.548439] iwlwifi :01:00.0: 0x00400410 | FSEQ_CNVR_ID
[4570550.548458] iwlwifi :01:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP
[4570550.548478] iwlwifi :01:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP
[4570550.548499] iwlwifi :01:00.0: 0x9061 |
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[4570550.548526] iwlwifi :01:00.0: 0x0061 |
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[4570550.548717] iwlwifi :01:00.0: WRT: Collecting data: ini trigger 4
fired (delay=0ms).
[4570550.548731] ieee80211 phy13: Hardware restart was requested
[4570550.548757] iwlwifi :01:00.0: FW error in SYNC CMD SCAN_REQ_UMAC
[4570550.548776] CPU: 2 PID: 3800801 Comm: iwlist Tainted: GW OE
6.1.0-18-amd64 #1 Debian 6.1.76-1
[4570550.548787] Hardware name: AZW U59/U59, BIOS JTKT001 05/05/2022
[4570550.548792] Call Trace:
[4570550.548800]
[4570550.548808] dump_stack_lvl+0x44/0x5c
[4570550.548830] iwl_trans_txq_send_hcmd+0x376/0x380 [iwlwifi]
[4570550.548890] ? cpuusage_read+0x10/0x10
[4570550.548902] iwl_trans_send_cmd+0x62/0xf0 [iwlwifi]
[4570550.548948] iwl_mvm_send_cmd+0x12/0x40 [iwlmvm]
[4570550.548990] iwl_mvm_reg_scan_start+0x398/0x490 [iwlmvm]
[4570550.549047] iwl_mvm_mac_hw_scan+0x4a/0x70 [iwlmvm]
[4570550.549083] drv_hw_scan+0x40/0x130 [mac80211]
[4570550.549204] __ieee80211_start_scan+0x255/0x6f0 [mac80211]
[4570550.549310] ? cfg80211_wext_siwscan+0xb9/0x3f0 [cfg80211]
[4570550.549435] ieee80211_request_scan+0x2b/0x50 [mac80211]
[4570550.549542] rdev_scan+0x25/0xd0 [cfg80211]
[4570550.549656] cfg80211_wext_siwscan+0x2d6/0x3f0 [cfg80211]
[4570550.549768] ioctl_standard_iw_point+0x221/0x3b0
[4570550.549781] ? cfg80211_unlink_bss+0xd0/0xd0 [cfg80211]
[4570550.549892] ioctl_standard_call+0xa6/0xd0
[4570550.549903] wext_handle_ioctl+0x156/0x190
[4570550.549914] sock_ioctl+0x1d2/0x330
[4570550.549926] __x64_sys_ioctl+0x8d/0xd0
[4570550.549936] do_syscall_64+0x58/0xc0
[4570550.549945] ? exit_to_user_mode_prepare+0x40/0x1e0
[4570550.549954] ? syscall_exit_to_user_mode+0x27/0x40
[4570550.549962] ? do_syscall_64+0x67/0xc0
[4570550.549968] ? exit_to_user_mode_prepare+0x40/0x1e0
[4570550.549976] entry_SYSCALL_64_after_hwframe+0x64/0xce
[4570550.549988] RIP: 0033:0x7f184baf8c5b
[4570550.549997] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d
00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[4570550.550004] RSP: 002b:7ffcb4407b90 EFLAGS: 0246 ORIG_RAX:
0010
[4570550.550014] RAX: ffda RBX: 55cad3c522a0 RCX:
7f184baf8c5b
[4570550.550019] RDX: 7ffcb4407c60 RSI: 8b18 RDI:
0003
[4570550.550023] RBP: 7ffcb4407d00 R08: 0009 R09:
Bug#1068798: bookworm-pu: package fdroidserver/2.2.1-1
Control: tags -1 + moreinfo On Thu, 2024-04-11 at 11:36 +0200, Jochen Sprickerhof wrote: > [ ] the issue is verified as fixed in unstable > [...] > Upstream is still working on a long term fix that will be uploaded to > unstable later. I agreed with upstream to use use the patch provided > in the mail on oss-security already now. In any case, assuming that the issue affects unstable (which appears to be the case), it should be fixed there first. Regards, Adam
Bug#1066346: sc: FTBFS: sc.c:1301:46: error: implicit declaration of function ‘list_frames’; did you mean ‘list_ranges’? [-Werror=implicit-function-declaration]
On 2024-04-07 05:23, Ying-Chun Liu (PaulLiu) wrote: I've fixed the bug. And I'll do NMU if no one object in 10 days. I'll upload it to the delay/10 queue. Attachment is the debdiff. Please review it. Thanks, looks good - Adam
Bug#1068686: xserver-xorg-input-wacom: Can't switch from "All Displays" on Intuos BT to one display
Package: xserver-xorg-input-wacom Version: 1.2.1-1 Severity: important X-Debbugs-Cc: gekit...@gmail.com Dear Maintainer, * What led up to the situation? Connected my Intuos bluetooth tablet to my computer the pen works fine but the tablet is mapped to both of my monitors. * What exactly did you do (or not do) that was effective (or ineffective)? When I go into "Wacom Tablet" in Gnome Settings I can see the option for "All Displays" or each of the monitors but when I change the dropdown the tablet stays mapped to both montors. If I change the drop down and leave the app then come back it will say "All Displays" again. * What was the outcome of this action? No change * What outcome did you expect instead? I expected it to map to a single monitor -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xserver-xorg-input-wacom depends on: ii libc6 2.37-15.1 ii libudev1 255.4-1+b1 ii libx11-6 2:1.8.7-1 ii libxi6 2:1.8.1-1 ii libxinerama1 2:1.1.4-3 ii libxrandr2 2:1.5.4-1 ii xserver-xorg-core [xorg-input-abi-24] 2:21.1.11-3 xserver-xorg-input-wacom recommends no packages. Versions of packages xserver-xorg-input-wacom suggests: pn xinput -- no debconf information
Bug#1051024: bookworm-pu: package igtf-policy-bundle/1.22-1~deb12u1
On Mon, 2024-04-08 at 14:26 +0200, Dennis van Dok wrote: > I've uploaded a new version since unstable is already at 1.128-1. The package you've uploaded is versioned 1.128-1+deb12u1, which is higher than the version in unstable. The stable upload needs to have a lower version number, conventionally 1.128-1~deb12u1. It appears you've also uploaded a 1.128-1~deb12u1 package, which confusingly seems to be a rebuild of 1.12_7_-1 from unstable. I'm going to flag both uploads for rejection. Once you get confirmation of that having been actioned, if what you're actually aiming for is to get a rebuild of 1.128-1 into stable then please: - use 1.128-1~deb12u1 as the package version - attach a revised debdiff to this bug Regards, Adam
Bug#1068569: RM: nfs-ganesha-ceph [armel armhf i386] -- NBS; ceph dropped 32 bit support
On Mon, 2024-04-08 at 11:42 +0200, Christoph Martin wrote: > Hi Sebastian, > > the packages are already removed from testing and unstable. > Where do you see a problem? I'm not Sebastian, but the archive disagrees with you about the packages having been removed from unstable. adsb@coccia:~$ dak ls -s unstable -a armel,armhf,i386 nfs-ganesha-ceph nfs-ganesha-rados-grace nfs-ganesha-rgw nfs-ganesha-ceph| 4.3-5 | unstable | armel, armhf, i386 nfs-ganesha-rados-grace | 4.3-5 | unstable | armel, armhf, i386 nfs-ganesha-rgw | 4.3-5 | unstable | armel, armhf, i386 Regards, Adam
Bug#1068310: network-manager-openvpn: regression in 1.10.2-4+ does not accept a saved password from network-manager.
Package: network-manager-openvpn Version: 1.10.2-2 Severity: important Dear Maintainer, * What led up to the situation? Upgraded to network-manager-openvpn to 1.10.2-4 in testing which resulted in network-manager not accepting a saved password for setting up a openvpn connection. (password-flags=0). Syslog error message: NetworkManager[415994]: [1712096590.8934] vpn[]: secrets: failed to request VPN secrets #4: No agents were available for this request. * What exactly did you do (or not do) that was effective (or ineffective)? Upgraded to 1.10.2-4+b1 in unstable which also had the same issue. Eventually downgraded back to 1.10.2-2 which resolved the issue. * What was the outcome of this action? Downgrading to 1.10.2-2 resolved the issue and allowed for saved passwords to work in network-manager for openvpn connections. * What outcome did you expect instead? Expected password-flags=0 with username and password defined to work. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-openvpn depends on: ii adduser 3.137 ii libc6 2.37-15 ii libglib2.0-0t64 [libglib2.0-0] 2.78.4-6 ii libnm0 1.46.0-1 ii network-manager 1.46.0-1 ii openvpn 2.6.7-1 network-manager-openvpn recommends no packages. network-manager-openvpn suggests no packages. -- no debconf information
Bug#1022073: Update to 1.3.0
I created merge requests in 2022 to update this package with a patchlevel update, and offered to do more updates, but I was unable to get any response. I tried reaching out multiple times to the two previous maintainers via email and IRC, emailing the the authentication team, finding a mentor on IRC, pinging people via salsa, and even trying to track down anyone who could help on ActivityPub. If someone is willing to find or be a mentor to me, and help with the release process, I'm still willing to put in the work to update the packages and make sure all the build tests continue to pass. For reference, here are the merge requests that I submitted: https://salsa.debian.org/auth-team/pam-u2f/-/merge_requests/8 https://salsa.debian.org/auth-team/pam-u2f/-/merge_requests/9 https://salsa.debian.org/auth-team/pam-u2f/-/merge_requests/10 I'm fairly new to creating packages and completely new to the release procedures, but I've been writing software and using Debian for decades, so after the first round of merges, I don't expect to require much of the mentor's time. Thanks, Adam On 4/2/24 2:19 PM, Patrick Winnertz wrote: retitle 1022073 new upstream release 1.3.0 is available thanks The last update of the u2f library is nearly 4 years(!) old. Please update to the latest version. If you need help, please don't hesitate to ask, I'm happy to help here as I'm using yubikeys for all authentication processes. With best regards Patrick
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1
On Thu, 2024-03-28 at 18:40 +0100, Andreas Beckmann wrote: > On 27/03/2024 21.10, Adam D. Barratt wrote: > > Please go ahead, bearing in mind that the window for 12.6 closes > > over > > the coming weekend. > > The whole nvidia stack has now been uploaded, > src:nvidia-graphics-drivers is sitting in NEW. It's now in stable-new. We have a bit of an issue in terms of accepting / shipping the 535 bookworm stack, however. The upload of 535 to unstable is blocked from migration to testing by openssl, which is in turn blocked by dpkg, which is manually blocked for the time64 transition. Would we be better to ship the 525 packages that are already in p-u and revisit 535 for 12.7, or skip those updates as well and just include 535 when we can? Regards, Adam
Bug#1067980: bookworm-pu: package gpaste/43.1-3+deb12u1
Control: tags -1 + confirmed On Fri, 2024-03-29 at 15:57 +0100, Andreas Beckmann wrote: > In order to smoothen upgrade paths I'd like to add some > Breaks+Replaces > to bookworm. This avoids a file conflict in case libgpaste6 (last > released with stretch) is still installed. Please go ahead. Regards, Adam
Bug#1068016: bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2
Control: tags -1 + confimred On Fri, 2024-03-29 at 17:41 +0100, Andreas Beckmann wrote: > To smoothen some upgrade paths from buster -> bullseye -> bookworm we > need to add some Breaks+Replaces against obsolete packages. Please go ahead. Regards, Adam
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1
Control: tags -1 + confirmed On Wed, 2024-03-27 at 09:51 +0100, Andreas Beckmann wrote: > In order to receive further upstream support (i.e. CVE fixes), we > need > to switch src:nvidia-graphics-drivers from the 525 series (EoL > 12/2023) > to the 535 series, a new LTSB branch sufficient for the lifetime of > bookworm. (The first 535 beta appeared during deep freeze of > bookworm.) > This driver supports a superset of the GPUs supported by the 525 > drivers, no GPUs have been dropped. > [...] > I'm currently doing interoperability tests with > src:nvidia-open-gpu-kernel-modules. (These two source packages > need to be updated together due to the strict firmware > dependency.) An upload to bookworm will only happen after the > package is in sid. Please go ahead, bearing in mind that the window for 12.6 closes over the coming weekend. Regards, Adam
Bug#1067843: bookworm-pu: package nvidia-open-gpu-kernel-modules/535.161.08-1~deb12u1
Control: tags -1 + confirmed On Wed, 2024-03-27 at 14:43 +0100, Andreas Beckmann wrote: > We need to update src:nvidia-open-gpu-kernel-modules to a new > upstream > version to stay in sync with src:nvidia-graphics-drivers (for a > matching > firmware-nvidia-gsp upstream version) and to fix some CVEs. [...] > [ ] the issue is verified as fixed in unstable > I'm currently doing interoperability tests with > src:nvidia-graphics-drivers. (These two source packages > need to be updated together due to the strict firmware > dependency.) An upload to bookworm will only happen after the > package is in sid. Please go ahead, bearing in mind that the window for 12.6 closes over the coming weekend. Regards, Adam
Bug#1067745: bookworm-pu: package nvidia-settings/535.171.04-1~deb12u1
Control: tags -1 + confirmed On Tue, 2024-03-26 at 11:09 +0100, Andreas Beckmann wrote: > In order to upgrade src:nvidia-graphics-drivers to the 535 LTS series > (the 525 series currently in stable is already EoL), we need to > update > some additional packages (some driver components can be built from > source and reside in contrib). Please go ahead. Regards, Adam
Bug#1067742: bookworm-pu: package nvidia-xconfig/535.171.04-1~deb12u1
Control: tags -1 + confirmed On Tue, 2024-03-26 at 10:51 +0100, Andreas Beckmann wrote: > In order to upgrade src:nvidia-graphics-drivers to the 535 LTS series > (the 525 series currently in stable is already EoL), we need to > update > some additional packages (some driver components can be built from > source and reside in contrib). Please go ahead. Regards, Adam
Bug#1067739: bookworm-pu: package nvidia-persistenced/535.171.04-1~deb12u1
Control: tags -1 + confirmed On Tue, 2024-03-26 at 10:40 +0100, Andreas Beckmann wrote: > In order to upgrade src:nvidia-graphics-drivers to the 535 LTS series > (the 525 series currently in stable is already EoL), we need to > update > some additional packages (some driver components can be built from > source and reside in contrib). Please go ahead. Regards, Adam
Bug#1050049:
Still occurring in 1:14.0-55.7~deb12u1. Seems to be fixed in 1:16.0-57. Can we please get a backport?
Bug#1067564: bookworm-pu: package cpu/1.4.3-14~deb12u1
Control: tags -1 + confirmed On Sat, 2024-03-23 at 18:40 +0100, Andreas Beckmann wrote: > The last QA upload four years ago fixed a FTBFS (multiple definitions > of > a global variable) by replacing that variable with an extern > declaration > and zero definitions. This didn't result in a linker error (missing > symbol) because it happens in a plugin library and thus is only > detected > at runtime when the plugin gets loaded (i.e. always). Oh dear... Please go ahead. Regards, Adam
Bug#1067149: bookworm-pu: package hovercraft/2.7-6~deb12u1
Control: tags -1 + confirmed On Tue, 2024-03-19 at 12:03 +0100, Andreas Beckmann wrote: > hovercraft is unusable w/o python3-setuptools > > [ Impact ] > hovercraft is unusable without manual installation of additional > packages. Please go ahead. Regards, Adam
Bug#1066096: bookworm-pu: package libpod/4.3.1+ds1-8+deb12u1
Control: tags -1 + confirmed On Tue, 2024-03-12 at 10:24 -0400, Jérôme Charaoui wrote: > podman in bookworm suffers from a race condition which causes the > "network ls" command to fail intermittently in certain scenarios Please go ahead. Regards, Adam
Bug#1065052: nvidia-graphics-drivers-tesla-470 470.239.06-1~deb12u1 flagged for acceptance
package release.debian.org tags 1065052 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-graphics-drivers-tesla-470 Version: 470.239.06-1~deb12u1 Explanation: new upstream stable release; improve compatibility with newer kernel versions; security fixes [CVE-2022-42265 CVE-2024-0074 CVE-2024-0078]
Bug#1065653: bookworm-pu: package nvidia-modprobe/535.161.07-1~deb12u1
Control: tags -1 + confirmed On Fri, 2024-03-08 at 09:42 +0100, Andreas Beckmann wrote: > In preparation to switching bookworm from the nvidia-graphics-drivers > 525.* series (production branch, EoL) to the 535.* series (long term > support branch, receives updates until July 2026), we need to update > nvidia-modprobe again. We already have a 535 release in bookworm, but > there was recently a new option being added. Please go ahead. Regards, Adam
Bug#1065264: bookworm-pu: package phpseclib/1.0.20-1+deb12u2
Control: tags -1 + confirmed On Sat, 2024-03-02 at 11:19 +0100, David Prévot wrote: > I’d like to see CVE-2024-27354 and CVE-2024-27355 addressed in the > next > point release. We agreed with the security team that these issues are > not worth a DSA. This update also fixes an issue in dependency > loading > similar to CVE-2024-24821 as fixed in composer/DSA-5632-1. > Please go ahead. Regards, Adam
Bug#1065263: bookworm-pu: package php-phpseclib/2.0.42-1+deb12u2
Control: tags -1 + confirmed On Sat, 2024-03-02 at 11:17 +0100, David Prévot wrote: > I’d like to see CVE-2024-27354 and CVE-2024-27355 addressed in the > next > point release. We agreed with the security team that these issues are > not worth a DSA. Please go ahead. Regards, Adam
Bug#1065261: bookworm-pu: package php-phpseclib3/3.0.19-1+deb12u3
Control: tags -1 + confirmed On Sat, 2024-03-02 at 11:15 +0100, David Prévot wrote: > I’d like to see CVE-2024-27354 and CVE-2024-27355 addressed in the > next > point release. We agreed with the security team that these issues are > not worth a DSA. This update also fixes an issue in dependency > loading > similar to CVE-2024-24821 as fixed in composer/DSA-5632-1. Please go ahead. Regards, Adam
Bug#1065068: bookworm-pu: package php-doctrine-deprecations/1.0.0-2+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 12:12 +0100, David Prévot wrote: > This is a follow up from composer/DSA-5632-1 (the last one for > Bookworm). > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next > point release. Please go ahead. Regards, Adam
Bug#1065067: bookworm-pu: package php-doctrine-lexer/2.1.0-2+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 12:08 +0100, David Prévot wrote: > This is a follow up from composer/DSA-5632-1. > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next > point release. Again the branch name probably wants adjusting. Please go ahead. Regards, Adam
Bug#1065065: bookworm-pu: package php-doctrine-annotations/2.0.1-1+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 12:05 +0100, David Prévot wrote: > This is a follow up from composer/DSA-5632-1. > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next > point release. Please go ahead. Regards, Adam
Bug#1065062: bookworm-pu: package php-zend-code/4.8.0-1+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 11:58 +0100, David Prévot wrote: > This is a follow up from composer/DSA-5632-1. > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next > point release. Please go ahead. Regards, Adam
Bug#1065060: bookworm-pu: package php-proxy-manager/2.11.1+1.0.14-1+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 11:50 +0100, David Prévot wrote: > This is a follow up from composer/DSA-5632-1. > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next > point release. Please go ahead. Regards, Adam
Bug#1065059: bookworm-pu: package symfony/5.4.23+dfsg-1+deb12u2
Control: tags -1 + confirmed On Thu, 2024-02-29 at 11:54 +0100, David Prévot wrote: > Hi, > > Le Thu, Feb 29, 2024 at 11:40:25AM +0100, David Prévot a écrit : > > [x] attach debdiff against the package in (old)stable > > Now it’s true. Please go ahead. Regards, Adam
Bug#1065058: bookworm-pu: package php-symfony-contracts/2.5.2-1+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 11:31 +0100, David Prévot wrote: > This is a follow up from composer/DSA-5632-1, #1065056 and #1065057. > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next > point release. Please go ahead. Regards, Adam
Bug#1065057: bookworm-pu: package php-composer-xdebug-handler/3.0.3-2+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 11:18 +0100, David Prévot wrote: > This is a follow up from composer/DSA-5632-1. > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next > point release. + * Track debian/bookworm-security Even though this update isn't going to the security archive? Please go ahead. Regards, Adam
Bug#1065056: bookworm-pu: package php-composer-class-map-generator/1.0.0-2+deb12u1
Control: tags -1 + confirmed On Thu, 2024-02-29 at 11:10 +0100, David Prévot wrote: > [1/9 for bookworm] > > This is a follow up from composer/DSA-5632-1. > > In order to fix a Debian-specific issue related to CVE-2024-24821, we > agreed with the security team to push related dependencies via the > next point release. All 9 of them. :-/ Please go ahead. Regards, Adam
Bug#1051774: PySNMP / asyncio bugfix
Hello guys Any news regarding this bugfix ? Regards, Adam.
Bug#1066928: ovn 23.03.1-1~deb12u2 flagged for acceptance
package release.debian.org tags 1066928 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: ovn Version: 23.03.1-1~deb12u2 Explanation: fix insufficient validation of incoming BFD packets [CVE-2024-2182]
Bug#1065413: openssl 3.0.13-1~deb12u1 flagged for acceptance
package release.debian.org tags 1065413 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: openssl Version: 3.0.13-1~deb12u1 Explanation: new upstream stable release; fix excessive time taken issues [CVE-2023-5678 CVE-2023-6237], vector register corruption issue on PowerPC [CVE-2023-6129], PKCS12 Decoding crashes [CVE-2024-0727]
Bug#1067206: amavisd-new 2.13.0-3+deb12u1 flagged for acceptance
package release.debian.org tags 1067206 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: amavisd-new Version: 2.13.0-3+deb12u1 Explanation: handle multiple boundary parameters that contain conflicting values [CVE-2024-28054]; fix race condition in postinst
Bug#1065562: postfix 3.7.11-0+deb12u1 flagged for acceptance
package release.debian.org tags 1065562 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: postfix Version: 3.7.11-0+deb12u1 Explanation: new upstream stable release
Bug#1065376: libxml-stream-perl 1.24-4+deb12u1 flagged for acceptance
package release.debian.org tags 1065376 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: libxml-stream-perl Version: 1.24-4+deb12u1 Explanation: fix compatibility with IO::Socket::SSL >= 2.078
Bug#1064993: systemd 252.23-1~deb12u1 flagged for acceptance
package release.debian.org tags 1064993 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: systemd Version: 252.23-1~deb12u1 Explanation: new upstream stable release; fix denial of service issues [CVE-2023-50387 CVE-2023-50868]
Bug#1052455: freetype 2.12.1+dfsg-5+deb12u3 flagged for acceptance
package release.debian.org tags 1052455 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: freetype Version: 2.12.1+dfsg-5+deb12u3 Explanation: disable COLRv1 support again; fix function existence check when calling get_colr_glyph_paint()
Bug#1064588: glibc 2.36-9+deb12u5 flagged for acceptance
package release.debian.org tags 1064588 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: glibc Version: 2.36-9+deb12u5 Explanation: revert fix to always call destructors in reverse constructor order due to unforeseen application compatibility issues; fix a DTV corruption due to a reuse of a TLS module ID following dlclose with unused TLS
Bug#1065413: bookworm-pu: package openssl/3.0.13-1~deb12u1
On Mon, 2024-03-04 at 07:38 +0100, Sebastian Andrzej Siewior wrote: > This is an update to the current stable OpenSSL release in the 3.0.x > series. It addresses the following CVE reports which were postponed > due to low severity: [...] > I'm not aware of a problems/ regression at this point. Sorry for not getting to this sooner. Is this still the case? Regards, Adam
Bug#1053191: mirror submission for mirror.kpfu.ru
Control: tags -1 + moreinfo Hi, Apologies for the delay in getting back to you. On Fri, 2023-09-29 at 06:50 +, kpfu.ru wrote: > Site: mirror.kpfu.ru > Archive-architecture: amd64 i386 Our automated checks noticed an issue with your mirror: o The trace file at http://mirror.kpfu.ru/debian/project/trace/mirror.kpfu.ru is missing some required information. We expect at least the Maintainer and Upstream-mirror values to be filled in, and your trace file is missing one or both of them. As an additional note, is there a reason that you only mirror amd64 packages? In general users will expect mirrors to carry all architectures. Regards, Adam
Bug#1058071: mirror submission for mirrors.cat.pdx.edu
Control: tags -1 + moreinfo Hi, Apologies for the delay in getting back to you. On Mon, 2023-12-11 at 23:52 +, Sage Imel wrote: > Site: mirrors.cat.pdx.edu > Archive-architecture: amd64 arm64 armhf hurd-amd64 i386 riscv64 Our automated checks noticed an issue with your mirror: o The trace file at http://mirrors.cat.pdx.edu/debian/project/trace/mirrors.cat.pdx.edu is missing some required information. We expect at least the Maintainer and Upstream-mirror values to be filled in, and your trace file is missing one or both of them. As an additional note, is there a reason that you only mirror a subset of Debian's official architectures? Architectures-Configuration: EXCLUDE alpha arm armel hppa hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc s390 s390x sh sparc armel, mipsel and s390x are all currently supported architectures and would be expected to appear on all Debian mirrors. Regards, Adam
Bug#1063915: mirror submission for debian.mirrors.ovh.net
Control: tags -1 + moreinfo On Wed, 2024-02-14 at 20:03 +, OVHcloud wrote: > Site: debian.mirrors.ovh.net > Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd- > amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x > Archive-http: /debian/ > Maintainer: OVHcloud > Country: FR France > Location: Anycast (Gravelines, Roubaix and Strasbourg) I know there was some discussion on IRC, so apologies if I'm rehashing here, but: - are the individual backends exposed in any way? - how do you ensure that the backends are in sync with each other? - what are the chances of users seeing inconsistent state if they hit different backends which aren't at the same stage of updating? Regards, Adam
Bug#1067488: mirror listing update for mirror.lon.macarne.com
Control: tags -1 + moreinfo On Fri, 2024-03-22 at 10:36 +, Arne wrote: > Submission-Type: update > Site: mirror.lon.macarne.com > Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd- > amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x > Archive-http: /debian/ > Archive-rsync: debian/ > Maintainer: Arne The only change here from #1067086 seems to be that the original request has: Maintainer: Macarne LLC Do you want it changing to the individual address instead? Regards, Adam
Bug#1064431: mirror submission for mirror.fra.macarne.com
Control: forcemerge 1067082 -1 Hi, This has been handled in the duplicate #1067082. Regards, Adam On Fri, 2024-02-23 at 07:59 +0800, Arne Ruhnau wrote: > Hi, should be fixed thanks. Arne > > > On Feb 23, 2024, at 2:24 AM, Adam D. Barratt > > wrote: > > > > Control: tags -1 + moreinfo > > > > On Wed, 2024-02-21 at 23:45 +, Macarne LLC wrote: > > > Submission-Type: new > > > Site: mirror.fra.macarne.com > > > > Our automated checks found an issue with your mirror: > > > > o The trace file at > > > > http://mirror.fra.macarne.com/debian/project/trace/mirror.fra.macarn > > e.com > > is missing some required information. > > > > We expect at least the Maintainer and Upstream-mirror values to be > > filled in, > > and your trace file is missing one or both of them. > > > > > > Please fix that and let us know once it's done. > > > > Regards, > > > > Adam >
Bug#1066021: pbuilder: debconf crashes while configuring pbuilder in debian:12.5 docker container
Package: pbuilder Version: 0.231 Severity: normal X-Debbugs-Cc: deb...@voltagex.org Dear Maintainer, I'm not sure if this should be filed against debconf or pbuilder or both (does the Package line support multiple packages?) It was also not clear how to report bugs against the official Debian Docker image A Dockerfile with the following: FROM debian:12.5 RUN apt update && apt install --no-install-recommends -y pbuilder will loop the following: #5 3.737 Setting up pbuilder (0.231) ... #5 3.774 debconf: unable to initialize frontend: Dialog #5 3.774 debconf: (TERM is not set, so the dialog frontend is not usable.) #5 3.774 debconf: falling back to frontend: Readline #5 3.780 debconf: unable to initialize frontend: Readline #5 3.780 debconf: (This frontend requires a controlling tty.) #5 3.780 debconf: falling back to frontend: Teletype #5 3.790 Configuring pbuilder #5 3.790 #5 3.790 #5 3.790 Default mirror not found #5 3.790 #5 3.790 Mirror information detection failed and the user provided no mirror #5 3.790 information. #5 3.790 #5 3.790 Please enter valid mirror information. #5 3.790 #5 3.790 Please enter the default mirror you want to be used by pbuilder. #5 3.790 #5 3.790 If you leave this field blank, there will be one attempt to autodetect this #5 3.790 information. If this attempt fails, you will be prompted again to insert some #5 3.790 valid mirror information. #5 3.790 #5 3.790 Here is a valid mirror example: http://deb.debian.org/debian I believe this is due to deb822 format sources lists being used in the container If I change the Dockerfile to read FROM debian:12.5 RUN echo "deb http://deb.debian.org/debian/ stable main contrib" > /etc/apt/sources.list && rm /etc/apt/sources.list.d/debian.sources RUN apt update && apt install --no-install-recommends -y pbuilder Then the package installs correctly -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.7-200.fc39.x86_64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages pbuilder depends on: ii debconf [debconf-2.0] 1.5.82 ii debootstrap1.0.128+nmu2+deb12u1 ii dpkg-dev 1.21.22 Versions of packages pbuilder recommends: pn devscripts pn eatmydata pn fakeroot pn net-tools | iproute2 pn sudo Versions of packages pbuilder suggests: pn cowdancer pn gdebi-core -- debconf information excluded
Bug#1063621: clamav 1.0.5+dfsg-1~deb12u1 flagged for acceptance
package release.debian.org tags 1063621 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: clamav Version: 1.0.5+dfsg-1~deb12u1 Explanation: new upstream stable release; fix possible heap overflow issue [CVE-2024-20290], possible command injection issue [CVE-2024-20328]
Bug#1063621: bookworm-pu: package clamav/clamav_1.0.5+dfsg-1~deb12u1
On Fri, 2024-02-09 at 23:12 +0100, Sebastian Andrzej Siewior wrote: > This is an update to the latest clamav release in the 1.0.x series. One small thing you may want to fix for any follow-up updates: +clamav (1.0.5+dfsg-1~deb12u1) bookworm; urgency=medium + + * Import 1.0.4 (Closes: #1063479). Regards, Adam
Bug#1064031: rustc-web 1.70.0+dfsg1-7~deb12u2 flagged for acceptance
package release.debian.org tags 1064031 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: rustc-web Version: 1.70.0+dfsg1-7~deb12u2 Explanation: fix build issues and file conflicts
Bug#1064031: rustc-web 1.70.0+dfsg1-7~deb12u1 flagged for acceptance
On Sat, 2024-03-02 at 03:54 -0500, Andres Salomon wrote: > rustc-web (1.70.0+dfsg1-7~deb12u2) bookworm; urgency=medium > > * Non-maintainer upload. > * Increase allowed test failures on armhf and ppc64el to fix > FTBFS. > * Provide Conflicts/Replaces for rust*-mozilla*, which could still > be > installed from oldstable (closes: #1064562). > * Add Provides/Conflicts/Replaces for libstd-rust-1.70 (closes: > #1064563). Please go ahead. Regards, Adam
Bug#1065390: xkeystone: depedency on nickle not available
Package: x11-xserver-utils Version: 7.7+10 There seems to be a dependency missing, or at least a recommends if a strict dependency would pull in too many things $ xkeystone /usr/bin/env: ‘nickle’: No such file or directory $ head /usr/bin/xkeystone #!/usr/bin/env nickle To make this utility work, had to install cairo-5c, nickle
Bug#1064371: mirror.xeonbd.com at https://www.debian.org/mirror/list#per-country
[Removed owner@bugs from CC, this has absolutely nothing to do with them] On Sun, 2024-02-25 at 05:11 +0600, XeonBD Admin wrote: > Recently through Bug#1064371 mirror.xeonbd.com was approved as a > Debian mirror but the mirror is not listed at > https://www.debian.org/mirror/list#per-country > > Is there anything else we need to do to add the mirror.xeonbd.com on > https://www.debian.org/mirror/list#per-country You need to have more patience. Re-submitting your details is not going to help. The public mirror list is automatically generated by filtering the underlying source list for mirrors with a high enough "score". You can see the current status of your mirror at https://mirror-master.debian.org/status/mirror-info/mirror.xeonbd.com.html Once it reaches at least +50 your mirror should be included in the public listing automatically. Regards, Adam
Bug#1065169: debsources: incomplete support for non-free-firmware
Package: qa.debian.org User: qa.debian@packages.debian.org Usertag: debsources Severity: important Hi, While waiting for an update run on sor.d.o to finish earlier today (so I could add a little disk space to /srv) I noticed some errors in the logs relating to non-free-firmware packages; e.g.: 2024-03-01 08:59:19 updater:ERROR failed to add nvidia-graphics-drivers/525.147.05-7~deb12u1 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 609, in do_execute cursor.execute(statement, parameters) psycopg2.errors.StringDataRightTruncation: value too long for type character varying(8) This appears to be because MR!6 didn't change the size of the field in lib/debsources/models.py and "non-free-firmware" is obviously larger than 8 characters. I assume this needs a database migration as well as a change to models.py, but it's not completely clear to me how/when those get applied, particularly as 011-to-012.sql has existed since early 2020 but models.py still specifies DB_SCHEMA_VERSION as 11. Regards, Adam
Bug#1064031: rustc-web 1.70.0+dfsg1-7~deb12u1 flagged for acceptance
On Tue, 2024-02-27 at 15:00 -0500, Andres Salomon wrote: > So it looks like I'll need a new upload to fix two bookworm > architecture > build failures (armhf and ppc64el), and also to fix #1064562. Should > I > file a new release.d.o bug, or continue using this one? Given that both issues are related to the initial upload tracked in this bug, re-using this one is ifne. Regards, Adam
Bug#1064031: rustc-web 1.70.0+dfsg1-7~deb12u1 flagged for acceptance
package release.debian.org tags 1064031 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: rustc-web Version: 1.70.0+dfsg1-7~deb12u1 Explanation: new source package to support builds of web browsers
Bug#1060214: mirror listing update for repository.su
Control: tags -1 + moreinfo On Sun, 2024-01-07 at 17:42 +, repository.su wrote: > Submission-Type: update > Site: repository.su [...] > Comment: This address is a replacement for the existing mirror > mirror.surf The tracefile still contains: Running on host: mirror.surf Please fix that and let us know when done. (Likely be changing the MIRRORNAME variable in your ftpsync config.) Regards, Adam
Bug#1063635: mirror listing update for mirror.limda.net
Control: tags -1 + moreinfo On Sat, 2024-02-10 at 08:09 +, Limda Host wrote: > Submission-Type: update > Site: mirror.limda.net > Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd- > amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x > Archive-http: /debian/ > Archive-rsync: debian/ > Maintainer: Limda Host > Country: BD Bangladesh > Location: Dhaka > Sponsor: Limda Host https://www.limda.net Please could you clarify what has changed relative to your current listing? Regards, Adam
Bug#1064289: mirror submission for elmirror.cl
Control: tags -1 + moreinfo On Mon, 2024-02-19 at 18:57 +, https://elmirror.cl wrote: > Site: elmirror.cl > Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd- > amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x > Archive-http: /debian/ Our automated checks noticed an issue with your setup: o The trace file at http://elmirror.cl/debian/project/trace/elmirror.cl is missing some required information. We expect at least the Maintainer and Upstream-mirror values to be filled in, and your trace file is missing one or both of them. Please fix that and let us know once it's done. Regards, Adam
Bug#1064371: mirror submission for mirror.xeonbd.com
On Tue, 2024-02-20 at 22:14 +, XeonBD wrote: > Site: mirror.xeonbd.com > Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd- > amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x > Archive-http: /debian/ > Maintainer: XeonBD > Country: BD Bangladesh > Location: Bangladesh > Sponsor: XeonBD https://www.xeonbd.com Our automated checks noticed an issue with your setup: o We recommend mirrors not sync directly from service aliases such as ftp..debian.org (only HTTP is guaranteed to be available at ftp. sites). Maybe change your config to sync from the site currently backing the ftp..debian.org service you sync from? Regards, Adam
Bug#1064431: mirror submission for mirror.fra.macarne.com
Control: tags -1 + moreinfo On Wed, 2024-02-21 at 23:45 +, Macarne LLC wrote: > Submission-Type: new > Site: mirror.fra.macarne.com Our automated checks found an issue with your mirror: o The trace file at http://mirror.fra.macarne.com/debian/project/trace/mirror.fra.macarne.com is missing some required information. We expect at least the Maintainer and Upstream-mirror values to be filled in, and your trace file is missing one or both of them. Please fix that and let us know once it's done. Regards, Adam
Bug#1064031: chromium and rustc in bookworm
Control: tags -1 + confirmed On Thu, 2024-02-15 at 19:25 -0500, Andres Salomon wrote: > Chromium now requires a Rust compiler to build, and it specifically > needs a rustc with profiler support built into it. This package can > hopefully be shared with firefox and other browser/web engines that > end up needing a newer rustc. Please go ahead. Regards, Adam
Bug#1064343: tput sgr0 adds uncalled-for codes
On Tue, Feb 20, 2024 at 07:41:42PM +0100, Sven Joachim wrote: > > On Tue, Feb 20, 2024 at 04:15:30PM +0800, Paul Wise wrote: > >>$ tput sgr0 | hd > >> 1b 28 42 1b 5b 6d |.(B.[m| > > > > Here's the culprit. The code you asked for is "\e[0m" -- shortenable to > > non-canonical but valid "\e[m", which is the second half of tput's output. > > > > What you did not ask for, is "\e(B", which is not allowed in UTF-8 mode, > > and in non-Unicode world would switch to an ancient "US" charset. > > Maybe that is true for the Linux console, but we are talking about xterm > here. It's not a property of the terminal, but of ECMA-35. And what "xterm" are you talking about? tput has no way to know the terminal on the other side, as the string TERM=xterm (and TERM=xterm-256color) applies to over a hundred different terminals using tens of different code bases. And you can't even blame their authors, as: * most Unices stopped maintaining their terminfo databases (eg. Solaris still hasn't learned about TERM=linux. Solaris is no longer relevant now but was relevant for most of that time frame.) * even if the databases were maintained, a new terminal would become useful only several years after it gets released (as the terminfo entry would need to be deployed on every box you might possibly ssh into, with failure mode being complete breakage of any terminfo-using program) Thus, putting aside historic terminals, there are only three TERM values: * linux * rxvt (used by its derivatives like aterm) * xterm (everything else) (Skipping decorations like -256color which most programs hard-code anyway. I thus had to implement 256 color fallbacks in the kernel in 2016; it seems that eg. 24-bit color is moving the same way.) > > Putting aside arguments if this code is allowed or not (eg. the author of > > Putty has strong feelings on the matter), it's very clearly not what you > > asked for, thus the real bug is on tput's side. > > Thus: > > "tput sgr0" should produce sgr0, not setusg0 sgr0. > > It does of course produce sgr0, i.e. it emits whatever escape sequence > $TERM's terminfo entry declares as sgr0. In the case of xterm-256color, > sgr0=\E(B\E[m. And it's that entry what's wrong. sgr0 means "\e[0m" (or "\e[m"); see eg. docs for real xterm: https://www.xfree86.org/current/ctlseqs.html > The reason for including \E(B here is that sgr0 should cancel the > effects of a previous smacs (start alternate character set) sequence and > thus includes the rmacs (end alternate character set) escape sequence. Then it combines two completely different concepts in one label. SGR is for character attributes, G0/G1 are for encoding. > People are relying on this behavior, see #595484 for instance. Seems like an XKCD 1172 case. > Closing the bug, because everything works as intended. ... Well, I'm not going to fight a BTS war, but I don't agree with your decision. I'll work around this misbehaviour (as it's no extra work for me: I need to handle legitimately occuring G0/G1 changes anyway). Still, it is a bug even if its severity is negligible: thanks to PuTTY's author's stubborness no maintained software uses G0/G1 anymore. Thus, the only real fallout is bloating terminal output. It's still too slow on serial links or inferior terminals (I felt bad about Scaleway's web console just hours ago); saving three bytes per sgr0 is not much but it is a very frequently used sequence. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!? ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din ⠈⠳⣄
Bug#1064341: colorized-logs: ansi2txt/ansi2html turn sgr0 into B instead of empty string
Control: clone -1 -2 Control: retitle -2 tput sgr0 adds uncalled-for codes Control: reassign -2 ncurses-bin On Tue, Feb 20, 2024 at 04:15:30PM +0800, Paul Wise wrote: > ansi2txt/ansi2html turn sgr0 into 'B' instead of an empty string. >$ echo $TERM >xterm-256color > >$ tput sgr0 | hd > 1b 28 42 1b 5b 6d |.(B.[m| Here's the culprit. The code you asked for is "\e[0m" -- shortenable to non-canonical but valid "\e[m", which is the second half of tput's output. What you did not ask for, is "\e(B", which is not allowed in UTF-8 mode, and in non-Unicode world would switch to an ancient "US" charset. Putting aside arguments if this code is allowed or not (eg. the author of Putty has strong feelings on the matter), it's very clearly not what you asked for, thus the real bug is on tput's side. I'm reassigning to ncurses-bin as I believe that terminfo is merely an implementation detail here -- and a grossly obsolete one as the very concept of terminfo has stopped working by mid-1980's -- but ncurses-bin and ncurses-base come from the same source package so this hardly matters. Thus: "tput sgr0" should produce sgr0, not setusg0 sgr0. --- There's a second bug, though, this time on my side: >$ tput sgr0 | ansi2txt ; echo >B > >$ tput sgr0 | ansi2html --no-header > style="color:#bbb;white-space:pre-wrap;word-wrap:break-word;overflow-wrap:break-word">B When the text being parsed contains G0/G1 settings, whether intentional or not, they should be recognized and either implemented or ignored. ansi2txt promises to remove all ANSI codes, not merely ones that would make sense in the given context. It's probably not worth the effort to implement charset conversions anymore as non-Unicode is thoroughly dead by now; I'll thus ignore these codes. I guess other codes should be looked at, too... Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Quis trollabit ipsos trollos? ⠈⠳⣄
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On Mon, 2024-02-12 at 17:59 +, Jonathan Wiltshire wrote: > The point release dates go to > debian-stable-annou...@lists.debian.org which > is very low traffic. Actually, that's one place they *don't* go in advance. The first mail to -stable-announce is at the point that processing of uploads is already frozen. (They do go to -project@ldo, amongst others, which is also generally not too busy.) Sending to d-d-a would require a second mail in each case, as the main announcement is to debian-release@ BCCed to several other lists and team aliases. From memory of previous discussions, dda was avoided both for that reason and because it doesn't really capture the right audience (not everyone who cares about point releases is a DD, and "many" DDs don't particularly care about stable updates). If it would help, we could easily add an additional address to the notification list. Regards, Adam
Bug#1062044: qemu 7.2+dfsg-7+deb12u5 flagged for acceptance
package release.debian.org tags 1062044 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: qemu Version: 7.2+dfsg-7+deb12u5 Explanation: revert patch causing regressions in suspend / resume functionality
Bug#1062044: qemu 7.2+dfsg-7+deb12u4 flagged for acceptance
On Tue, 2024-02-06 at 20:49 +0300, Michael Tokarev wrote: > 06.02.2024 20:33, Adam D. Barratt: > > On Tue, 2024-02-06 at 19:37 +0300, Michael Tokarev wrote: > > > problematic upstream commit (on master) is this one: > > > https://gitlab.com/qemu-project/qemu/-/commit/effd60c878176bcaf97fa7ce2b12d04bb8ead6f7 > > > Technically we already froze p-u for 12.5 on Sunday evening, as > > previously announced. If you could get an upload just fixing that > > single issue with a small change uploaded today then I'd be tempted > > to > > accept it anyway. > > Oh. I knew we're getting late, but not *that* late. > The point release(s) are on Saturday, and we always freeze a week beforehand. > The change isn't small per se, as the commit is rather large (mostly > due to many changed tests, - it changes order of output in quite some > places). Here's the diffstat: > > monitor/qmp.c | 17 + > qapi/qmp-dispatch.c | 24 +- > -- This is the relevant bit for size IMO. If you're happy with the result then please upload as soon as you're ready. Regards, Adam
