Your message dated Thu, 1 Jun 2023 13:46:23 +0200 with message-id <06d94273-1062-bc5d-c1b0-3b8172be2701@debian.org> and subject line Re: Bug#1036982: unblock: debspawn/0.6.2-1 has caused the Debian Bug report #1036982, regarding unblock: debspawn/0.6.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1036982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036982 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: debspawn/0.6.2-1
- From: Matthias Klumpp <mak@debian.org>
- Date: Wed, 31 May 2023 14:53:29 +0200
- Message-id: <CAKNHny85Bh6z7kpH5KCoP3HJR42rE2VEcK9rn_hWkn43zqg4gg@mail.gmail.com>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package debspawn. [ Reason ] Packaging of the 0.6.2 bugfix release which contains three changes only: * Fixes issue where users could not build packages against NotAutomatic suites like Debian experimental when the "experimental"-like suite did not contain enough of the required dependencies (APT's solver was too limited) * Python 3.11 support (minimal changes) * Fixes a crash when regenerating an image with `update --recreate` in case the image had a custom name [ Impact ] People would not be able to build packages for experimental, using `update --recreate` for images with custom names would crash. [ Tests ] Tested by upstream, used in production at Purism already for a few weeks, so far no issues have been found. [ Risks ] The worst that could happen is that building experimental packages stays broken, so no regression would happen. Apart from that, this change is very small and should be fairly safe. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing Thank you! unblock debspawn/0.6.2-1Attachment: debspawn_0.6.1-1_to_0.6.2-1.debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: Matthias Klumpp <mak@debian.org>, 1036982-done@bugs.debian.org
- Subject: Re: Bug#1036982: unblock: debspawn/0.6.2-1
- From: Paul Gevers <elbrus@debian.org>
- Date: Thu, 1 Jun 2023 13:46:23 +0200
- Message-id: <06d94273-1062-bc5d-c1b0-3b8172be2701@debian.org>
- In-reply-to: <CAKNHny85Bh6z7kpH5KCoP3HJR42rE2VEcK9rn_hWkn43zqg4gg@mail.gmail.com>
- References: <CAKNHny85Bh6z7kpH5KCoP3HJR42rE2VEcK9rn_hWkn43zqg4gg@mail.gmail.com>
Hi, On 31-05-2023 14:53, Matthias Klumpp wrote:Tested by upstream, used in production at Purism already for a few weeks, so far no issues have been found.No need to answer, but why than have this upload and request so late?unblock debspawn/0.6.2-1unblocked and aged. PaulAttachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---