Woot! Thank you both for sorting this out. I'm completely lost in new job
things :)
Also I did a write up of the time on how to automate breaking half of CPAN:
https://chris.prather.org/breaking-cpan.html
-Chris
On Tue, Apr 6, 2021 at 5:34 PM Karen Etheridge wrote:
> cheers Neil!
>
> On Tue, A
cheers Neil!
On Tue, Apr 6, 2021 at 2:33 PM Neil Bowers wrote:
> Heh, the "Crixa Event" sounds like a meteorite hitting, which it sounds
> like it sorta was.
>
> I’ve transferred first-come from PERIGRIN to STEVAN (with PERIGRIN getting
> co-maint), so things are consistent again.
>
> Neil
>
Heh, the "Crixa Event" sounds like a meteorite hitting, which it sounds like it
sorta was.
I’ve transferred first-come from PERIGRIN to STEVAN (with PERIGRIN getting
co-maint), so things are consistent again.
Neil
Those permission entries might have been this way ever since the Crixa[1]
mishap, then... as I believe that the Moose distribution always excluded
them until 2.2014.
[1] sorry Chris, I know you'll never live this down... :D but for Neil:
several years ago there was a separate distribution release
> 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.
Ah, Checking META.json for 2.2013, these four packages were
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 wrote:
> Hi,
>
> I’ve got
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_inde
