Processing changes file: cups_2.3.3op2-3+deb11u8_s390x-buildd.changes
ACCEPT
Processing changes file: indent_2.2.12-1+deb11u1_s390x-buildd.changes
ACCEPT
Processing changes file: runc_1.0.0~rc93+ds1-5+deb11u4_s390x-buildd.changes
ACCEPT
On Sunday, June 30th, 2024 at 5:33 AM, Jonathan Wiltshire
wrote:
>
>
> Hi,
>
> This request was approved for 11.10 but not uploaded in time; is it still
> relevant for 11.11, the planned final point release for bullseye?
>
> Thanks,
>
> --
> Jonathan Wiltshire j...@debian.org
> Debian
Processing changes file: cups_2.3.3op2-3+deb11u8_mips64el-buildd.changes
ACCEPT
Processing changes file: cups_2.3.3op2-3+deb11u8_mipsel-buildd.changes
ACCEPT
Processing changes file: indent_2.2.12-1+deb11u1_mips64el-buildd.changes
ACCEPT
Processing changes file:
Processing changes file: cups_2.3.3op2-3+deb11u8_all-buildd.changes
ACCEPT
Processing changes file: cups_2.3.3op2-3+deb11u8_amd64-buildd.changes
ACCEPT
Processing changes file: cups_2.3.3op2-3+deb11u8_arm64-buildd.changes
ACCEPT
Processing changes file:
Processing changes file: runc_1.0.0~rc93+ds1-5+deb11u5_amd64.changes
REJECT
Processing changes file: runc_1.0.0~rc93+ds1-5+deb11u4_amd64.changes
ACCEPT
package release.debian.org
tags 1072248 = 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: runc
Version:
Processing commands for cont...@bugs.debian.org:
> package release.debian.org
Limiting to bugs with field 'package' containing at least one of
'release.debian.org'
Limit currently set to 'package':'release.debian.org'
> tags 1072248 = bullseye pending
Bug #1072248 [release.debian.org]
Processing changes file: cups_2.3.3op2-3+deb11u8_source.changes
ACCEPT
Processing changes file: indent_2.2.12-1+deb11u1_source.changes
ACCEPT
Processing changes file: libvpx_1.12.0-1+deb12u3_source.changes
ACCEPT
Processing changes file: libvpx_1.12.0-1+deb12u3_all-buildd.changes
ACCEPT
Processing changes file: libvpx_1.12.0-1+deb12u3_amd64-buildd.changes
ACCEPT
Processing changes file: libvpx_1.12.0-1+deb12u3_arm64-buildd.changes
Your message dated Sat, 29 Jun 2024 21:35:35 +0100
with message-id
and subject line Re: Bug#1002956: New debdiff
has caused the Debian Bug report #1002956,
regarding bullseye-pu: package rabbitmq-server/3.8.9-3
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 21:35:35 +0100
with message-id
and subject line Re: Bug#1002956: New debdiff
has caused the Debian Bug report #1002956,
regarding bullseye-pu: package rabbitmq-server/3.8.9-3 CVE-2021-32718,
CVE-2021-32719
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> close 1037188
Bug #1037188 [release.debian.org] bullseye-pu: package git/2.30.2-1+deb11u3
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1037188:
Processing commands for cont...@bugs.debian.org:
> tags 1025518 - moreinfo
Bug #1025518 [release.debian.org] bullseye-pu: package capnproto/0.7.1-1+deb11u1
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1025518:
Hi,
This request was approved for 11.10 but not uploaded in time; is it still
relevant for 11.11, the planned final point release for bullseye?
Thanks,
--
Jonathan Wiltshire j...@debian.org
Debian Developer
Hi,
This request was approved for 11.10 but not uploaded in time; is it still
relevant for 11.11, the planned final point release for bullseye?
Thanks,
--
Jonathan Wiltshire j...@debian.org
Debian Developer
Hi,
This request was approved for 11.10 but not uploaded in time; is it still
relevant for 11.11, the planned final point release for bullseye?
Thanks,
--
Jonathan Wiltshire j...@debian.org
Debian Developer
Processing control commands:
> tag -1 confirmed
Bug #1021005 [release.debian.org] bullseye-pu: package dgit/9.16
Added tag(s) confirmed.
--
1021005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 confirmed
Hi,
If it's still desirable please go ahead with a backport of 9.16 as
9.16~deb11u1 and sorry for the extended delay. I'm mopping up old requests
and this is amongst them.
Thanks,
--
Jonathan Wiltshire j...@debian.org
Debian
Processing control commands:
> tag -1 confirmed
Bug #1074125 [release.debian.org] bullseye-pu: ntfs-3g/1:2017.3.23AR.3-4+deb11u4
Added tag(s) confirmed.
--
1074125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 confirmed
On Sun, Jun 23, 2024 at 03:26:15PM +0200, László Böszörményi wrote:
> [ Reason ]
> A use-after-free security issue was found. It is not a severe one, so
> no DSA will be released. But it would be good to have it fixed.
Please go ahead.
Thanks,
--
Jonathan Wiltshire
Processing control commands:
> tag -1 confirmed
Bug #1057330 [release.debian.org] bullseye-pu: package
midge/0.2.41+dfsg-1~deb11u1
Added tag(s) confirmed.
--
1057330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 confirmed
On Wed, Jun 19, 2024 at 05:24:32PM +0200, Andreas Beckmann wrote:
> Control: tag -1 - moreinfo
>
> On 19/12/2023 22.51, Jonathan Wiltshire wrote:
> > I'm fine with the changes but I'm a bit uncomfortable about the backwards
> > version history in debian/changelog.
Processing control commands:
> tag -1 confirmed
Bug #1074090 [release.debian.org] bullseye-pu: package cjson/1.7.14-1+deb11u1
Added tag(s) confirmed.
--
1074090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 confirmed
On Sun, Jun 23, 2024 at 03:36:21PM +0800, Maytham Alsudany wrote:
> [ Reason ]
> CVE-2023-50472, CVE-2023-50471, CVE-2024-31755
>
Please go ahead.
Thanks,
--
Jonathan Wiltshire j...@debian.org
Debian Developer
Processing control commands:
> tag -1 moreinfo
Bug #1072746 [release.debian.org] bullseye-pu: package pyroute2/0.5.14-2
Added tag(s) moreinfo.
--
1072746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 moreinfo
On Fri, Jun 07, 2024 at 04:11:56PM +0200, Thomas Goirand wrote:
> Hi,
>
> After further investigation, it looks like to me that the issue is only with
> newer kernel, like 6.1.0 (ie: currently backport kernels).
>
> Since during the lifetime of oldstable, it may be
Processing commands for cont...@bugs.debian.org:
> package release.debian.org
Limiting to bugs with field 'package' containing at least one of
'release.debian.org'
Limit currently set to 'package':'release.debian.org'
> tags 1074142 = bullseye pending
Bug #1074142 [release.debian.org]
Processing commands for cont...@bugs.debian.org:
> package release.debian.org
Limiting to bugs with field 'package' containing at least one of
'release.debian.org'
Limit currently set to 'package':'release.debian.org'
> tags 1074438 = bullseye pending
Bug #1074438 [release.debian.org]
package release.debian.org
tags 1074438 = 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: cups
Version:
package release.debian.org
tags 1074142 = 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: indent
Version:
Processing changes file: org-mode_9.4.0+dfsg-1+deb11u3_source.changes
ACCEPT
Processing changes file: org-mode_9.4.0+dfsg-1+deb11u3_all-buildd.changes
ACCEPT
Processing changes file: plasma-workspace_5.20.5-6+deb11u1_source.changes
ACCEPT
Processing changes file:
Processing changes file: snort_2.9.20-0+deb11u1_source.changes
REJECT
Processing changes file: snort_2.9.20-0+deb11u1_all-buildd.changes
REJECT
Processing changes file: snort_2.9.20-0+deb11u1_amd64-buildd.changes
REJECT
Processing changes file: snort_2.9.20-0+deb11u1_arm64-buildd.changes
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org
Dear Release Team,
We would like to upload the latest stable point release of systemd 252
to bookworm-p-u. Stable
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072716,
regarding bookworm-pu: package systemd/252.26-1~deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072817,
regarding bookworm-pu: package openrc/0.45.2-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, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072098,
regarding bookworm-pu: package systemd/252.26-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, 29 Jun 2024 10:47:47 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1072009,
regarding bullseye-pu: package systemd/247.3-7+deb11u5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1074019,
regarding bullseye-pu: package ngircd/26.1-1+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, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1074128,
regarding bullseye-pu: package python-stdnum/1.16-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1074018,
regarding bookworm-pu: package ngircd/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, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1074087,
regarding bookworm-pu: package debvm/0.2.10+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, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1074059,
regarding bookworm-pu: package nodejs/18.19.0+dfsg-6~deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1074054,
regarding bullseye-pu: package gdk-pixbuf/2.42.2+dfsg-1+deb11u2
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073967,
regarding bookworm-pu: package jose/11-2+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, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073966,
regarding bullseye-pu: package jose/10-3+deb11u1
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, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073923,
regarding bookworm-pu: package mobian-keyring/20230202.0+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073843,
regarding bookworm-pu: package kio/5.103.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, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073839,
regarding bookworm-pu: package libimage-imlib2-perl/2.03-1.2~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073838,
regarding bookworm-pu: package ruby-aws-partitions/1.653.0-3~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073262,
regarding bookworm-pu: package gnutls28/3.7.9-2+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073833,
regarding bullseye-pu: package nvidia-graphics-drivers/470.256.02-1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073817,
regarding bookworm-pu: package
nvidia-open-gpu-kernel-modules/535.183.01-1~deb12u1
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073556,
regarding bullseye-pu: package nano/5.4-2+deb11u3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073524,
regarding bookworm-pu: package pymongo/3.11.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, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073261,
regarding bookworm-pu: package dhcpcd5/9.4.1-24~deb12u4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073231,
regarding bullseye-pu: package sendmail/8.15.2-22+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073235,
regarding bookworm-pu: package bluez/5.66-1+deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073234,
regarding bookworm-pu: package gdk-pixbuf/2.42.10+dfsg-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073231,
regarding bullseye-pu: package sendmail/8.15.2-22+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073208,
regarding bookworm-pu: package nvidia-graphics-drivers/535.183.01-1~deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073206,
regarding bullseye-pu: package python-aiosmtpd/1.2.2-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073202,
regarding bookworm-pu: package python-aiosmtpd/1.4.3-1.1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073175,
regarding bookworm-pu: package lacme/0.8.2-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, 29 Jun 2024 10:46:21 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073194,
regarding bookworm-pu: package lxc-templates/3.0.4.48.g4765da8-1+deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073174,
regarding bullseye-pu: package lacme/0.8.0-2+deb11u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1073116,
regarding bookworm-pu: package python-idna/3.3-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, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1073115,
regarding bullseye-pu: package python-idna/2.10-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072984,
regarding bookworm-pu: package crowdsec-firewall-bouncer/0.0.25-4~deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072983,
regarding bookworm-pu: package golang-github-google-nftables/0.1.0-4~deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1072965,
regarding bullseye-pu: package
nvidia-graphics-drivers-tesla-470/470.256.02-1~deb11u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072856,
regarding bookworm-pu: package djangorestframework/3.14.0-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072919,
regarding bookworm-pu: package
nvidia-graphics-drivers-tesla-470/470.256.02-1~deb12u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1072680,
regarding bullseye-pu: package rust-cbindgen-web/0.26.0-3~deb11u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072626,
regarding bookworm-pu: package rust-cbindgen-web/0.26.0-3~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1072653,
regarding bullseye-pu: package dns-root-data/2024041801~deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072239,
regarding bookworm-pu: package intel-microcode/3.20240514.1~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072476,
regarding bookworm-pu: package lua5.4/5.4.4-3+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, 29 Jun 2024 10:47:48 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1072238,
regarding bullseye-pu: package intel-microcode/3.20240514.1~deb11u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072122,
regarding bookworm-pu: package cloud-init/22.4.2-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, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1072035,
regarding bookworm-pu: package dns-root-data/2024041801~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1071449,
regarding bookworm-pu: package sendmail/8.17.1.9-2+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1071826,
regarding bookworm-pu: package libreoffice/4:7.4.7-1+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1071920,
regarding bookworm-pu: package libseccomp/2.5.4-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1071574,
regarding bookworm-pu: package netcfg/1.187+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, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1071564,
regarding bookworm-pu: package aide/0.18.3-1+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1071266,
regarding bookworm-pu: package software-properties/0.99.30-4.1~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 29 Jun 2024 10:47:47 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1071161,
regarding bullseye-pu: package glib2.0/2.66.8-1+deb11u4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1071159,
regarding bookworm-pu: package glib2.0/2.74.6-2+deb12u3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 29 Jun 2024 10:46:20 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070856,
regarding bookworm-pu: package riseup-vpn/0.21.11+ds1-5+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:47:47 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1070799,
regarding bullseye-pu: package rustc-web/1.70.0+dfsg1-7~deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:47:47 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1070761,
regarding bullseye-pu: package bart-cuda/0.6.00-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 29 Jun 2024 10:47:47 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1070723,
regarding bullseye-pu: package bart/0.6.00-3+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, 29 Jun 2024 10:46:19 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070702,
regarding bookworm-pu: package nano/7.2-1+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, 29 Jun 2024 10:47:47 +
with message-id
and subject line Released with 11.10
has caused the Debian Bug report #1070670,
regarding bullseye-pu: package shim/15.8-1~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, 29 Jun 2024 10:46:19 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070466,
regarding bookworm-pu: package dm-writeboost/2.2.17-0.2~deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:19 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070484,
regarding bookworm-pu: package tryton-client/tryton-client_6.0.26-1+deb12u1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 29 Jun 2024 10:46:19 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070478,
regarding bookworm-pu: package tryton-server/tryton-server_6.0.29-2+deb12u2
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 29 Jun 2024 10:46:19 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070431,
regarding bookworm-pu: package php-composer-pcre/3.1.0-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:19 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070249,
regarding bookworm-pu: package python-jwcrypto/1.1.0-1+deb12u1
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 29 Jun 2024 10:46:19 +
with message-id
and subject line Released with 12.6
has caused the Debian Bug report #1070232,
regarding bookworm-pu: package python3.11/3.11.2-6+deb12u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
1 - 100 of 245 matches
Mail list logo
