On Sun, 2023-03-26 at 22:37 +, Robin H. Johnson wrote:
>
> So you're implying that we are now responsible to fix the tests of
> every
> package in our dependency tree, and you'll just remove all dependent
> packages if we don't do that.
My answer would be yes, especially for packages
On Sun, 2023-03-26 at 21:39 +, Robin H. Johnson wrote:
To start with your last question since that is the most fundamental one
for me:
> So do we really remove packages because a 2nd-order test-only
> dependency
> fails it's own tests? (aruba:0 failing tests on Ruby 3 being the only
> reason
On Sun, 2023-03-26 at 22:37 +, Robin H. Johnson wrote:
> So you're implying that we are now responsible to fix the tests of
> every
> package in our dependency tree, and you'll just remove all dependent
> packages if we don't do that.
Yes, that's how being responsible works in volunteer
On Sun, Mar 26, 2023 at 11:57:00PM +0200, David Seifert wrote:
> There's a pattern here of infra or packages added for infra rotting with
> unattended bugs or otherwise not meeting modern standards and then panic
> at the 11th hour when they're last-rited.
The *infra* packages here work fine, and
On Sun, 2023-03-26 at 21:39 +, Robin H. Johnson wrote:
> On Sun, Mar 26, 2023 at 09:57:36AM +0200, Hans de Graaff wrote:
> > # Hans de Graaff (2023-03-26)
> > # Mask ruby27-only packages related to hiera-eyaml. These require a
> > now
> > # masked version of puppet and other obsolete
On Sun, Mar 26, 2023 at 09:57:36AM +0200, Hans de Graaff wrote:
> # Hans de Graaff (2023-03-26)
> # Mask ruby27-only packages related to hiera-eyaml. These require a now
> # masked version of puppet and other obsolete ruby27-only test
> # dependencies. Masked for removal on 2023-04-26.
>
# Hans de Graaff (2023-03-26)
# Mask ruby27-only packages related to hiera-eyaml. These require a now
# masked version of puppet and other obsolete ruby27-only test
# dependencies. Masked for removal on 2023-04-26.
dev-ruby/hiera-eyaml
dev-ruby/hiera-eyaml-gpg
signature.asc
Description: This is
