Tie::Cycle was indexed in Acme-OCEORA-Utils

[briandfoy]

This distro distributes a copy of Tie::Cycle:

http://search.cpan.org/~oceora/Acme-OCEORA-Utils-0.03/

I've already released a new version, so that should fix that issue in a couple of hours.

Somehow, OCEORA and DZYNERR were co-maintainers. I can't find a record of me making them such (I see nothing in the pause mail (search at https://github.com/briandfoy/pause_replay) ). I figure they are working on the exercises in Intermediate Perl and copied my Tie::Cycle distro. I've deleted their co-maintainer permissions, so it's not causing a problem now. I do wonder how they got it without an automated message going into modules@.

Beyond that, OCEORA's version of Tie::Cycle (1.224) was indexed despite being the same version number as mine.

• I uploaded 1.224 on April 18, 2017
• OCEORA's first upload was on June 24, 2017

I suppose the entire distro and everything in it was indexed because the main module version had increased.

[andk]

>>>> On Sun, 09 Jul 2017 10:49:47 -0700, brian d foy ***@***.***> said:

And, somehow, OCEORA and DZYNERR are co-maintainers. We had a very unfortunate bug in the pause code that's now fixed. Just read commits around the time of the perl Toolchain Summit and you will see. The bug is fixed, the broken permissions it caused will accompany us for a while:( Please fix all the permissions that you can identify as being broken and let us know. Sorry for the inconvenience, -- andreas

[briandfoy]

I've fixed the permissions and reuploaded. If this is really something fixed and I hadn't noticed until today, I think that solves it.

To fill out the report though, the conference was May 14-17.

The only commit I see that might be related is a08b836.

[karenetheridge]

11th to 14th. This is the relevant PR, which also links to the original commit that introduced the issue, and the commit that fixes it -- #234

…

On Sun, Jul 9, 2017 at 4:15 PM, brian d foy ***@***.***> wrote: I've fixed the permissions and reuploaded. If this is really something fixed and I hadn't noticed until today, I think that solves it. To fill out the report though, the conference <http://act.qa-hackathon.org/qa2017/> was May 14-17. The only commit I see that might be related is a08b836 <a08b836> . — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#248 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASfy-jnVZS2kub4PuONuPSlOGLTuwRYks5sMV70gaJpZM4OSId9> .