Processing commands for cont...@bugs.debian.org:
> reassign 1063668 nvidia-kernel-dkms
Bug #1063668 [src:nvidia-graphics-drivers] linux-image-6.1.0-18-amd64: Nvidia
525.147.05-4 issues
Bug reassigned from package 'src:nvidia-graphics-drivers' to
'nvidia-kernel-dkms'.
Ignoring request to alter
Processing control commands:
> tag -1 confirmed
Bug #1063675 [release.debian.org] bookworm-pu: package
nvidia-graphics-drivers/525.147.05-6~deb12u1
Added tag(s) confirmed.
--
1063675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063675
Debian Bug Tracking System
Contact
Control: tag -1 confirmed
On Sat, Feb 10, 2024 at 11:00:58PM +0100, Andreas Beckmann wrote:
> [ Reason ]
> 1) A backported (by upstream) change in Linux 6.1.76 (included in
> today's point release) broke compilation of the non-free nvidia kernel
> module. A patched version of the driver is
Control: tags -1 - moreinfo
On Wednesday, February 7th, 2024 at 3:06 AM, Jonathan Wiltshire
wrote:
>
>
> Hi,
>
> On Tue, Jan 16, 2024 at 08:30:52AM +, Daniel Markstedt wrote:
>
> > 2024年1月16日 (火) 02:53, Adam D. Barratt
> > <[a...@adam-barratt.org.uk](mailto:2024年1月16日 (火) 02:53, Adam
Processing control commands:
> tags -1 - moreinfo
Bug #1060774 [release.debian.org] bullseye-pu: netatalk/3.1.12~ds-8+deb11u2
Removed tag(s) moreinfo.
--
1060774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> affects -1 + src:xeus
Bug #1063680 [release.debian.org] nmu: xeus_3.1.3-1
Added indication that 1063680 affects src:xeus
--
1063680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: x...@packages.debian.org, gor...@chronitis.net
Control: affects -1 + src:xeus
xeus exposes the interface of nlohmann::json as part of its ABI
(unfortunately), and changes in
Processing control commands:
> affects -1 + src:nvidia-graphics-drivers
Bug #1063675 [release.debian.org] bookworm-pu: package
nvidia-graphics-drivers/525.147.05-6~deb12u1
Added indication that 1063675 affects src:nvidia-graphics-drivers
> block 1063363 with -1
Bug #1063363 {Done: Andreas
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 + src:nvidia-graphics-drivers
Control: block 1063363 with -1
Control: block 1062932 with -1
[ Reason ]
1) A backported (by upstream) change in Linux 6.1.76
Processing changes file: libgit2_1.1.0+dfsg.1-4+deb11u2_source.changes
ACCEPT
Processing changes file: libgit2_1.1.0+dfsg.1-4+deb11u2_all-buildd.changes
ACCEPT
Processing changes file: libgit2_1.1.0+dfsg.1-4+deb11u2_amd64-buildd.changes
ACCEPT
Processing changes file:
Processing changes file: chromium_121.0.6167.160-1~deb12u1_source.changes
ACCEPT
Processing changes file: chromium_121.0.6167.160-1~deb12u1_all-buildd.changes
ACCEPT
Processing changes file: chromium_121.0.6167.160-1~deb12u1_amd64-buildd.changes
ACCEPT
Processing changes file:
Hi,
Considering the version in unstable is currently
0.0+git20231103-1
should the upload be versioned
0.0+git20231103-0+deb12u1 (like originally proposed) or
0.0+git20231103-1~deb12u1
As originally proposed please. You're not backporting 0.0+git20231103-1
directly as far as I know, because
Hello,
I've just made the upgrade from Debian Bookworm 12.4 to Debian 12.5 and
have a NVIDIA card which requires proprietary drivers.
Unfortunately, du to #1062932, upgrading kernel is not possible.
Fix has been uploaded but only to unstable.
Best regards,
--
Patrick ZAJDA
Processing commands for cont...@bugs.debian.org:
> tags 1037188 + moreinfo
Bug #1037188 [release.debian.org] bullseye-pu: package git/2.30.2-1+deb11u3
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1037188:
On Tue, Feb 06, 2024 at 10:02:20PM +0100, Bernhard Schmidt wrote:
> Hi Jonathan,
>
> > On Tue, Nov 14, 2023 at 11:26:54PM +0100, Bernhard Schmidt wrote:
> > > [ Reason ]
> > > openvpn-dco-dkms packages an accelerator kernel module for OpenVPN
> > > (OpenVPN
> > > data channel offload). There is
On Sat, Feb 10, 2024 at 12:23:06AM +1100, Hugh McMaster wrote:
> Hi Jonathan,
>
> On Wed, 7 Feb 2024 at 04:47, Jonathan Wiltshire wrote:
>
> > What's your plan at this point? We have skipped this update in two point
> > releases now and it needs a resolution.
>
>
> Thanks for following up. I’d
On Fri, Feb 09, 2024 at 06:48:34PM -1000, Romain Tartière wrote:
> Hi Jonathan,
>
> On Tue, Feb 06, 2024 at 05:59:10PM +, Jonathan Wiltshire wrote:
> > This request was approved but not uploaded in time for the previous point
> > releases (11.8 and 11.9). Should it be included in 11.10, or
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061587,
regarding bookworm-pu: package systemd/252.22-1~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1063005,
regarding bookworm-pu: package tzdata/2024a-0+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1063035,
regarding bookworm-pu: package xen/4.17.3+10-g091466ba55-1~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062660,
regarding bookworm-pu: package pypy3/7.3.11+dfsg-2+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062475,
regarding bookworm-pu: package debian-edu-fai/2024.02.01.2~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062469,
regarding bookworm-pu: package debian-edu-config/2.12.44~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062686,
regarding bookworm-pu: package libdatetime-timezone-perl/1:2.60-1+2024a
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062435,
regarding bookworm-pu: package indent/2.2.12-4+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062233,
regarding bookworm-pu: package debian-edu-doc/2.12.23~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061624,
regarding bookworm-pu: package postfix/3.7.9-0+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062063,
regarding bookworm-pu: package monitoring-plugins/2.3.3-5+deb12u2
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062175,
regarding bookworm-pu: package debian-edu-install/2.12.10~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1062004,
regarding bookworm-pu: package usb.ids/2024.01.20-0+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061652,
regarding bookworm-pu: package rss-glx/0.9.1-6.4+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061607,
regarding bookworm-pu: package compton/compton_1-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:22 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061579,
regarding bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u2
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061523,
regarding bookworm-pu: package tzdata/2023d-0+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061549,
regarding bookworm-pu: package dropbear/2022.83-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061487,
regarding bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061473,
regarding bookworm-pu: package tinyxml/2.6.2-6+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061407,
regarding bookworm-pu: package debian-ports-archive-keyring/2024.01.05~deb12u1
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061465,
regarding bookworm-pu: package usbutils/014-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061189,
regarding bookworm-pu: package gnutls28/3.7.9-2+deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061176,
regarding bookworm-pu: package tar/1.34+dfsg-1.2+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1061161,
regarding bookworm-pu: package pypdf2/2.12.1-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060851,
regarding bookworm-pu: package pypdf/3.4.1-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060767,
regarding bookworm-pu: package proftpd-mod-proxy/0.9.2-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060688,
regarding bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060433,
regarding bookworm-pu: package apktool/2.7.0+dfsg-6+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060186,
regarding bookworm-pu: libde265/1.0.11-1+deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060668,
regarding bookworm-pu: package calibre/6.13.0+repack-2+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060129,
regarding bookworm-pu: package libmateweather/1.26.0-1.1+deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060417,
regarding bookworm-pu: package proftpd-dfsg/1.3.8+dfsg-4+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060122,
regarding bookworm-pu: package atril/1.26.0-2+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:21 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1060132,
regarding bookworm-pu: package mate-settings-daemon/1.26.0-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059846,
regarding bookworm-pu: package isl/0.25-1.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059696,
regarding bookworm-pu: package mate-utils/1.26.0-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059705,
regarding bookworm-pu: package pluma/1.26.0-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059694,
regarding bookworm-pu: package filezilla/filezilla_3.63.0-1+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059402,
regarding bookworm-pu: package postfix/3.7.6-0+deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059656,
regarding bookworm-pu: package espeak-ng/1.51+dfsg-10+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059524,
regarding bookworm-pu: package mate-screensaver/1.26.1-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059609,
regarding bookworm-pu: package engrampa/1.26.0-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059522,
regarding bookworm-pu: package caja/1.26.1-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059344,
regarding bookworm-pu: package libdatetime-timezone-perl/1:2.60-1+2023d
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059343,
regarding bookworm-pu: package libfirefox-marionette-perl/1.35-1+deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059291,
regarding bookworm-pu: package spip/4.1.9+dfsg-1+deb12u4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1059235,
regarding bookworm-pu: package fish/3.6.0-3.1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1058615,
regarding bookworm-pu: package node-yarnpkg/1.22.19+~cs24.27.18-2+deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1058938,
regarding bookworm-pu: package onionprobe/1.0.0+ds-2.1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1058928,
regarding bookworm-pu: package cryptsetup/2:2.6.1-4~deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:11:20 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1058458,
regarding bookworm-pu: package nextcloud-desktop/3.7.3-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1057089,
regarding bookworm-pu: package usrmerge/37~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1057179,
regarding bookworm-pu: package mariadb-10.6 1:10.11.6-0+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1056969,
regarding bookworm-pu: package swupdate/2022.12+dfsg-4+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1056222,
regarding bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1056222,
regarding bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1056358,
regarding bookworm-pu: package needrestart/3.6-4+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1055248,
regarding bookworm-pu: pipewire/0.3.65-3+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1054488,
regarding bookworm-pu: package netplan.io/0.106-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1054466,
regarding bookworm-pu: package localslackirc/1.17-1.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1054446,
regarding bookworm-pu: package wolfssl/5.5.4-2+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:11:19 +
with message-id
and subject line Released with 12.5
has caused the Debian Bug report #1054386,
regarding bookworm-pu: package fssync/1.6-1.1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1063017,
regarding bullseye-pu: package tzdata/2024a-0+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1062685,
regarding bullseye-pu: package libdatetime-timezone-perl/1:2.47-1+2024a
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1062006,
regarding bullseye-pu: package glibc/2.31-13+deb11u8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061983,
regarding bullseye-pu: package debian-security-support/1:11+2024.01.30
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1062005,
regarding bullseye-pu: package usb.ids/2024.01.20-0+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061625,
regarding bullseye-pu: package postfix/3.5.23-0+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061608,
regarding bullseye-pu: package compton/compton_1-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:02:59 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061578,
regarding bullseye-pu: package libspreadsheet-parsexlsx-perl/0.27-2.1+deb11u2
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061572,
regarding bullseye-pu: package unadf/0.7.11a-4+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061556,
regarding bullseye-pu: package dropbear/2020.81-3+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061472,
regarding bullseye-pu: package tinyxml/2.6.2-4+deb11u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061471,
regarding bullseye-pu: package xerces-c/3.2.3+debian-3+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061408,
regarding bullseye-pu: package debian-ports-archive-keyring/2024.01.05~deb11u1
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061177,
regarding bullseye-pu: package tar/1.34+dfsg-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1061096,
regarding bullseye-pu: package ruby-aws-sdk-core/3.104.3-3+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1060689,
regarding bullseye-pu: package libspreadsheet-parsexlsx-perl/0.27-2.1+deb11u1
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1060185,
regarding bullseye-pu: libde265/1.0.11-0+deb11u3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1060130,
regarding bullseye-pu: package libmateweather/1.24.1-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1059693,
regarding bullseye-pu: package filezilla/filezilla_3.52.2-3+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 10 Feb 2024 13:02:58 +
with message-id
and subject line Released with 11.9
has caused the Debian Bug report #1059804,
regarding bullseye-pu: package exuberant-ctags/1:5.9~svn20110310-14+deb11u1
to be marked as done.
This means that you claim that the problem has been
1 - 100 of 150 matches
Mail list logo
