Processed: unblock: doc-debian/11.3

Processing commands for cont...@bugs.debian.org: > reopen 1035710 Bug #1035710 {Done: Joost van Baal-Ilić } [release.debian.org] unblock: doc-debian/11.1 Bug reopened Ignoring request to alter fixed versions of bug #1035710 to the same values previously set > retitle 1035710 unblock: doc-debian/

Re: Bug#1034824: tomcat9 should not be released with Bookworm

Le 2023-05-13 22:38, Markus Koschany a écrit : The question is: If we ship libtomcat9-java in Bookworm and change the dependency from tomcat9-user to tomcat10-user, will a web application like dogtag-pki, which is designed for Tomcat 9, continue to work with Tomcat 10? I'm pretty sure it won

Bug#1036037: unblock: emacs/1:28.2+1-15

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: em...@packages.debian.org Control: affects -1 + src:emacs Please unblock package emacs The only changes are two bug fixes, one for a file conflict with bullseye emacs-bin-com

Processed: unblock: emacs/1:28.2+1-15

Processing control commands: > affects -1 + src:emacs Bug #1036037 [release.debian.org] unblock: emacs/1:28.2+1-15 Added indication that 1036037 affects src:emacs -- 1036037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036037 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Re: Bug#1034824: tomcat9 should not be released with Bookworm

Hi Salvatore, adding Timo Aaltonen, maintainer of dogtag-pki and tomcatjss, to CC Am Samstag, dem 13.05.2023 um 20:50 +0200 schrieb Salvatore Bonaccorso: > Hi Markus, > > On Sat, May 13, 2023 at 06:27:49PM +0200, Markus Koschany wrote: > > I have just pushed the necessary changes to our Git repo

Re: Bug#1034824: tomcat9 should not be released with Bookworm

Hi Markus, On Sat, May 13, 2023 at 06:27:49PM +0200, Markus Koschany wrote: > I have just pushed the necessary changes to our Git repository. > > https://salsa.debian.org/java-team/tomcat9/-/commit/adbd0b0711de66b67278b10e258c47c805e9b993 Do we need to have done more here? When Paul asked on #d

Processed: unblock: python-mitogen/0.3.3-9

Processing control commands: > affects -1 + src:python-mitogen Bug #1036031 [release.debian.org] unblock: python-mitogen/0.3.3-9 Added indication that 1036031 affects src:python-mitogen -- 1036031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036031 Debian Bug Tracking System Contact ow...

Bug#1036031: unblock: python-mitogen/0.3.3-9

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: python-mito...@packages.debian.org Control: affects -1 + src:python-mitogen Please unblock package python-mitogen [ Reason ] This resolves bug 1036018. Apparently ansible has

Bug#1036029: unblock: glewlwyd/2.7.5-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: debian-iot-maintain...@lists.alioth.debian.org Please unblock package glewlwyd 2.7.5-3 [ Reason ] This new version in unstable fixes #1035503 : glewlwyd-common: prompting due

Processed: unblock: kitty/0.26.5-5

Processing control commands: > affects -1 + src:kitty Bug #1036027 [release.debian.org] unblock: kitty/0.26.5-5 Added indication that 1036027 affects src:kitty -- 1036027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036027 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#1036027: unblock: kitty/0.26.5-5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ki...@packages.debian.org Control: affects -1 + src:kitty Please unblock package kitty [ Reason ] Kitty registers itself as a handler for various MIME types (via kitty-open.de

Bug#1036026: unblock: libssh/0.10.5-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: lib...@packages.debian.org Control: affects -1 + src:libssh Hello, a few days ago, a new libssh upstream microrelease [1] was published which fixes two CVEs. I packaged it for

Processed: unblock: libssh/0.10.5-1

Processing control commands: > affects -1 + src:libssh Bug #1036026 [release.debian.org] unblock: libssh/0.10.5-1 Added indication that 1036026 affects src:libssh -- 1036026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036026 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Processed: unblock: exim4/4.96-15

Processing control commands: > affects -1 + src:exim4 Bug #1036025 [release.debian.org] unblock: exim4/4.96-15 Added indication that 1036025 affects src:exim4 -- 1036025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036025 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#1036025: unblock: exim4/4.96-15

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ex...@packages.debian.org Control: affects -1 + src:exim4 Please unblock package exim4 This fixes an initialzation error which caused a crash in the smtp transport. See https:

Debian 8.3 Jessie KEYEXPIRED 11645052400

Hello, On Sat, May 13, 2023, 11:31 Pierre-Elliott Bécue wrote: > > The only way to avoid that would be to first add stretch to your > sources.list, update, install debian-archive-keyring, and then add > buster to your sources.list. > By the way, this is the recommended approach, please don't tr

Re: Debian 8.3 Jessie KEYEXPIRED 11645052400

Alan Homobono wrote on 13/05/2023 at 05:56:45+0200: > Trying to upgrade Debian 8.3 Jessie to Debian 10.13 Buster, I continue > getting "KEYEXPIRED" error message after run apt-get update, even renewing > expired keys: > > # apt-key list | grep -A 1 expired > pub 1024D/5072E1F5 2003-0