Your message dated Mon, 26 Dec 2022 16:47:18 +0100 with message-id <953e59c4-d3b3-e685-ecc4-9783248e4...@debian.org> and subject line Re: Bug#1027022: RM: puppet-beaker/4.30.0-2 has caused the Debian Bug report #1027022, regarding RM: puppet-beaker/4.30.0-2 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 ow...@bugs.debian.org immediately.) -- 1027022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: rm Please remove puppet-beaker from testing. It is orphaned, broken, outdated compared to upstream, and blocks the migration of ruby-net-scp (that's how I ran into it) I tried updating it to the latest upstream version but failed. Lucas
--- End Message ---
--- Begin Message ---Hi, On 26-12-2022 16:15, Lucas Nussbaum wrote:On 26/12/22 at 15:30 +0100, Paul Gevers wrote: I am mainly interested in restoring a clean state for ruby-net-scp (which cannot migrate without an update of puppet-beaker in testing, or a removal of puppet-beaker from testing). Someone with more interest in puppet-beaker than I have might be able to fix it, and then it could migrate again. So I'd rather keep it in unstable for now.Fair enough.autoremoval will remove it on 10 January (under normal circumstances). Can we wait until then?Yes, it can wait until Jan 10th (but then I need to remember to check that ruby-net-scp migrates after Jan 10th).A simple check showed no reverse (build) dependencies, so I've added a hint. PaulOpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---