Aha, so the permission was just dropped as a result of my releases this
week, I see!

On Tue, Jul 25, 2023 at 2:14 AM Neil Bowers <ne...@neilb.org> wrote:

> There’s a latency between PAUSE changing permissions and when they’ll be
> reflected in 06perms.txt. I can’t remember if 06perms is updated hourly, or
> less frequently. PAUSE generates it and then the CPAN master has to mirror
> it. And then if you’re using MetaCPAN to look at it, that has a delay as
> well.
>
> Neil
> On 24 Jul 2023 at 19:21 +0100, Karen Etheridge <ka...@froods.org>, wrote:
>
> I was looking at that failure report yesterday and was confused, because I
> did see myself listed as having comaint in 06perms.txt... but still, my
> reindex request failed.
>
> But what you describe makes sense -- we'll have to assume I was looking at
> an old version of the perms file somehow? or could it be that the file that
> is being published is not the same as what pause itself is working with?
>
>
> On Mon, Jul 24, 2023 at 4:04 AM Neil Bowers <ne...@neilb.org> wrote:
>
>> Hi Karen,
>>
>> I noticed that you had a failed indexing message for
>> Moose::Meta::TypeConstraint::Role.
>>
>> Looking into this, all co-maint permissions were lost on that one package
>> in Moose. I have a copy of 06perms.txt from earlier this year, and could
>> see what the permissions should have been. I’ve restored them.
>>
>> I think this is probably down to https://github.com/andk/pause/issues/372
>> *, *the root cause of which is https://github.com/andk/pause/issues/406,
>> I think.
>>
>> I’ll  nudge Matt, Rik, and Andreas, to see if we can move that forward.
>> In the meantime, you should now be able to reindex your latest Moose
>> release, if you care about getting that one package correctly indexed.
>>
>> Neil
>>
>

Reply via email to