Bug#1027022: RM: puppet-beaker/4.30.0-2

2022-12-26 Thread Lucas Nussbaum 
On 26/12/22 at 15:30 +0100, Paul Gevers wrote:
> Hi Lucas,
> 
> On 26-12-2022 14:55, Lucas Nussbaum wrote:
> > Please remove puppet-beaker from testing.
> 
> Normally that's handled by requesting removal from unstable as removal there
> is synced to testing.
> 
> > It is orphaned, broken, outdated compared to upstream, and blocks the
> > migration of ruby-net-scp (that's how I ran into it)
> 
> Have you considered requesting removal from unstable? If not, why not?

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.

> 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).

Lucas

Bug#1027022: RM: puppet-beaker/4.30.0-2

2022-12-26 Thread Paul Gevers 

Hi Lucas,

On 26-12-2022 14:55, Lucas Nussbaum wrote:

Please remove puppet-beaker from testing.


Normally that's handled by requesting removal from unstable as removal 
there is synced to testing.



It is orphaned, broken, outdated compared to upstream, and blocks the
migration of ruby-net-scp (that's how I ran into it)


Have you considered requesting removal from unstable? If not, why not? 
autoremoval will remove it on 10 January (under normal circumstances). 
Can we wait until then?


In other words, should this bug be reassigned to ftp.debian.org?

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027022: RM: puppet-beaker/4.30.0-2

2022-12-26 Thread Lucas Nussbaum 
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