I recall that there was a metadata change between releases 2.2013 and 2.2014 (last year) to allow some internal modules to be indexed. I did those releases.. how did PERIGRIN end up with first-come? that seems like a pause bug.
On Tue, Apr 6, 2021 at 8:58 AM Neil Bowers <neil.bow...@cogendo.com> wrote: > Hi, > > I’ve got a script that tells me if a distribution ends up with split > first-come permissions. > > Moose now has this, as a result of the following packages, which have > PERIGRIN as first-come: > > Moose::Util::TypeConstraints::Builtins > Moose::Meta::Method::Accessor::Native::Array::first_index > Moose::Meta::Method::Accessor::Native::Hash::shallow_clone > Moose::Meta::Method::Accessor::Native::Array::shallow_clone > > This usually happens when a distribution is subsumed by a bigger one. > > Assuming the right fix here is for PERIGRIN to transfer first-come to > STEVAN, but wanted to check with you first. You can make the move Chris, or > I’m happy to do it for you. > > Neil >
