It sounds fine to drop the older lower-cased name from the index and to
move the corresponding 0.01 release to backpan.

It also sounds like there's an issue with the newer
Dist-Zilla-PluginBundle-BioPerl releases -- since the 02packages index has:

Dist::Zilla::PluginBundle::BioPerl 0.20
C/CD/CDRAUG/Dist-Zilla-PluginBundle-BioPerl-0.20.tar.gz
Pod::Weaver::PluginBundle::BioPerl 0.23
C/CJ/CJFIELDS/Dist-Zilla-PluginBundle-BioPerl-0.23.tar.gz

What happened to Dist::Zilla::PluginBundle::BioPerl in versions 0.21 and
later? The 0.23 release does contain Dist::Zilla::PluginBundle::BioPerl
(see https://metacpan.org/release/Dist-Zilla-PluginBundle-BioPerl) -- why
is it not indexed? The package declaration in the module looks fine, and I
see no 'provides' or 'no_index' metadata. Perhaps CJFIELDS only got comaint
after the 0.23 release, in which case a force-reindexing on PAUSE should
clear this up.




On Mon, Jul 11, 2016 at 1:11 PM, Neil Bowers <neil.bow...@cogendo.com>
wrote:

> Hi AUGGY, ETHER, FLORA, RBUELS,
>
> I’m emailing you wearing my PAUSE admin hat: I’m working on resolving
> conflicts caused by PAUSE now considering package names case insensitively.
> This has left us with some situations where two or more people are owners
> of namespaces previously considered distinct, and now considered the same.
>
> FLORA has ownership of Dist::Zilla::PluginBundle::Bioperl, which was
> released by RBUELS, and is still in the CPAN index against the
> R/RB/RBUELS/Dist-Zilla-PluginBundle-Bioperl-0.01.tar.gz. This now conflicts
> with Dist::Zilla::PluginBundle::BioPerl, which is owned by BIOPERLML, and
> has a difference bunch of co-maints. That was last indexed on CPAN against
> the C/CD/CDRAUG/Dist-Zilla-PluginBundle-BioPerl-0.20.tar.gz — the module
> appears to have been renamed Pod::Weaver::PluginBundle::BioPerl, but the
> distribution name Dist-Zilla-PluginBundle-BioPerl retained.
>
> To resolve this I propose dropping all permissions against the older
> Dist::Zilla::PluginBundle::Bioperl. I suggest that Robert (RBUELS) should
> also delete the 0.01 from his author directory.
>
> I don’t think this will cause any problems, but wanted to check you’re all
> ok with this before I drop the permissions?
>
> PAUSE doesn’t let situations like this occur any more — I’m tidying up the
> existing cases.
>
> Thanks,
> Neil
>
>

Reply via email to