Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-22 Thread Neil Bowers via modules
Hi Steve,
> Just to wrap this all up: libapreq2-2.16 is now uploaded and iscorrectly 
> indexed:
> https://metacpan.org/release/SHAY/libapreq2-2.16

Great — thanks for that, and for letting us know.

Cheers,
Neil



Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-22 Thread Steve Hay via modules
On Mon, 8 Mar 2021 at 16:46, Steve Hay  wrote:
>
> On Mon, 8 Mar 2021 at 13:57, Neil Bowers  wrote:
> >
> > Hi Steve,
> >
> > Sorry we hadn’t got back to you before now.
> >
> > The problem here was the "provides" section in META.yml. Because it’s 
> > missing the file: line for each module, it’s now considered an invalid 
> > metadata file. So CPAN::Meta refuses to load it. When that happens, 
> > MetaCPAN construct a new metadata file for the distribution, which ends up 
> > pulling all of the packages found in the tarball.
> >
> > You don’t have permissions on all of them (because PAUSE thinks they’re not 
> > candidates for indexing).
> >
> > Andreas and I have been emailing back and forth trying to agree the right / 
> > best way to resolve this.
> >
> > The cleanest way would be for you to do a new release that has a valid 
> > META.yml. If that’s not possible at the moment, Andreas and I will resolve 
> > it another way for now, and you can fix META.yml for your next release.
> >
>
> Ok, thanks.
>
> I've committed a change that I hope will fix the META.yml file when a
> release is next done:
> https://svn.apache.org/viewvc?view=revision=1887336
>
> And on the previously cited d...@httpd.apache.org list thread I've
> asked about the possibility of making a new release to resolve this
> matter. Hopefully this will occur sooner or later, so we shouldn't
> have to trouble you any more over this.
>
> Thanks again,
> Steve

Just to wrap this all up: libapreq2-2.16 is now uploaded and is
correctly indexed:

https://metacpan.org/release/SHAY/libapreq2-2.16


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-08 Thread Steve Hay via modules
On Mon, 8 Mar 2021 at 13:57, Neil Bowers  wrote:
>
> Hi Steve,
>
> Sorry we hadn’t got back to you before now.
>
> The problem here was the "provides" section in META.yml. Because it’s missing 
> the file: line for each module, it’s now considered an invalid metadata file. 
> So CPAN::Meta refuses to load it. When that happens, MetaCPAN construct a new 
> metadata file for the distribution, which ends up pulling all of the packages 
> found in the tarball.
>
> You don’t have permissions on all of them (because PAUSE thinks they’re not 
> candidates for indexing).
>
> Andreas and I have been emailing back and forth trying to agree the right / 
> best way to resolve this.
>
> The cleanest way would be for you to do a new release that has a valid 
> META.yml. If that’s not possible at the moment, Andreas and I will resolve it 
> another way for now, and you can fix META.yml for your next release.
>

Ok, thanks.

I've committed a change that I hope will fix the META.yml file when a
release is next done:
https://svn.apache.org/viewvc?view=revision=1887336

And on the previously cited d...@httpd.apache.org list thread I've
asked about the possibility of making a new release to resolve this
matter. Hopefully this will occur sooner or later, so we shouldn't
have to trouble you any more over this.

Thanks again,
Steve


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-08 Thread Neil Bowers via modules
Hi Steve,

Sorry we hadn’t got back to you before now.

The problem here was the "provides" section in META.yml. Because it’s missing 
the file: line for each module, it’s now considered an invalid metadata file. 
So CPAN::Meta refuses to load it. When that happens, MetaCPAN construct a new 
metadata file for the distribution, which ends up pulling all of the packages 
found in the tarball.

You don’t have permissions on all of them (because PAUSE thinks they’re not 
candidates for indexing).

Andreas and I have been emailing back and forth trying to agree the right / 
best way to resolve this.

The cleanest way would be for you to do a new release that has a valid 
META.yml. If that’s not possible at the moment, Andreas and I will resolve it 
another way for now, and you can fix META.yml for your next release.

Cheers,
Neil



Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-08 Thread Steve Hay via modules
On Wed, 3 Mar 2021 at 14:01, Neil Bowers  wrote:
>
> Hi Steve,
>
> Thanks for this. I'm happy to see that this release now appears on
>
> MetaCPAN, but numerous modules within it are listed as "UNAUTHORIZED"
>
> when I look at https://metacpan.org/release/SHAY/libapreq2-2.15.
>
>
> The previous release at
>
> https://metacpan.org/release/ISAAC/libapreq2-2.13 does not have this
>
> problem, so there is still a gremlin hiding somewhere in the system.
>
>
> Ah.  When I gave you co-maint, it didn’t give you co-maint on all the 
> packages. I’ll go through them one-by-one tonight, and fix this. I’ll shout 
> when it’s all sorted.
>

Any luck with this yet? MetaCPAN is still showing unauthorized at the moment.


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-03 Thread Neil Bowers via modules
Hi Steve,
> Thanks for this. I'm happy to see that this release now appears on
> MetaCPAN, but numerous modules within it are listed as "UNAUTHORIZED"
> when I look at https://metacpan.org/release/SHAY/libapreq2-2.15.
>
> The previous release at
> https://metacpan.org/release/ISAAC/libapreq2-2.13 does not have this
> problem, so there is still a gremlin hiding somewhere in the system.

Ah.  When I gave you co-maint, it didn’t give you co-maint on all the packages. 
I’ll go through them one-by-one tonight, and fix this. I’ll shout when it’s all 
sorted.

Neil


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-03 Thread Steve Hay via modules
On Wed, 3 Mar 2021 at 07:17, Andreas Koenig
 wrote:
>
> > On Tue, 2 Mar 2021 17:44:06 +, Steve Hay via modules 
> >  said:
>
>   > On Tue, 2 Mar 2021 at 17:24, Andreas Koenig
>   >  wrote:
>  >>
>  >> > On Tue, 2 Mar 2021 08:41:11 +, Steve Hay via modules 
>  said:
>  >>
>  >> > On Mon, 1 Mar 2021 at 22:26, Neil Bowers  
> wrote:
>  >> >>
>  >> >> Hi Steve,
>  >> >>
>  >> >> Ah, I forgot to mention — you’ll need to force PAUSE to re-index the 
> tarball you uploaded.
>  >> >>
>  >> >> When you log in to PAUSE, in the life sidebar you’ll see "Force
>  >> >> Reindexing", under "Utils" (3rd section). When you click on that
>  >> >> you’ll get a list of the files in your upload directory. Click the
>  >> >> checkbox next to libapreq2-2.15.tar.gz and then click on "Reindex".
>  >> >> You’ll get an email within the hour with the results of the
>  >> >> reindexing.
>  >> >>
>  >> >> That will make your release appear in the CPAN Index. MetaCPAN will 
> need to reindex it as well — I’ll give them a nudge once your reindexing is 
> done.
>  >> >>
>  >>
>  >> > Ok, thanks. I see Andreas has actually done this for me already: I
>  >> > have an email saying that it will be reindexed in about 20min from
>  >> > now, so if you could give MetaCPAN a nudge for me when that's done
>  >> > then that would be brilliant.
>  >>
>  >> > Many thanks to you & Andreas for sorting this all out for me :-)
>  >>
>  >> You're welcome. Unfortunately we are not yet through with this. Later I
>  >> got an error message that the indexing failed. I suppose you received it
>  >> as well, but it gives no clue. At the moment I have no idea yet, how to
>  >> work around some built-in spell.
>
>   > Yes, I saw the message. It ended with "Nothing in this distro has been
>   > indexed, because according to META.yml this package does not provide
>   > any modules." but comparing the META.yml with that in libapreq2-2.13
>   > (which presumably is indexed since it appears on MetaCPAN?) I see
>   > nothing but the expected differences. In particular, they both list
>   > the same set of "provided modules", with just the versions bumped from
>   > 2.13 to 2.15.
>
> Too many years in between and too much code changes on PAUSE to have a
> clear view what might be the cause. My current theory is that it's to do
> with a weakness in this META.yml: the "provides" entries in the META.yml
> all have no "file" attribute:
>
>  : provides:
>  :   Apache2::Request:
>  : version: 2.15
>  :   Apache2::Cookie:
>  : version: 2.15
>
> Compare this with:
>
>  : provides:
>  :   Acme::Godot:
>  : file: lib/Acme/Godot.pm
>  : version: '0.001010'
>
> I think it's worth trying to provide the "file" with the provides
> attribute next time you come around with a release.

I will certainly do my best to ensure the "file" attributes are
present for the next release, whenever that might be.


>
> Now you ask why did it work with 2.13. I don't know, offhand, it's just
> an unproven theory anyway.
>
> What I now did was a very dirty manual operation in the DB directly:
>
>  : update packages set version=2.15,
>  : dist='S/SH/SHAY/libapreq2-2.15.tar.gz',
>  : file='missing file attrib in META.yaml/provides; ed. by andk'
>  : where dist like '%libapreq2%' ;
>
> So now 2.15 is indexed and no code on PAUSE was changed for that. Let me
> know when I overlooked anything.

Thanks for this. I'm happy to see that this release now appears on
MetaCPAN, but numerous modules within it are listed as "UNAUTHORIZED"
when I look at https://metacpan.org/release/SHAY/libapreq2-2.15.

The previous release at
https://metacpan.org/release/ISAAC/libapreq2-2.13 does not have this
problem, so there is still a gremlin hiding somewhere in the system.

If you think it would be easier to just do another release now, with
the "file" attributes added, and all the indexing done in the usual
way now that I have the correct permissions to start with then let me
know; I don't want to be any trouble. (The problem is that I can't
avoid being trouble to someone because these releases have to go
through voting at d...@httpd.apache.org and apreq-...@httpd.apache.org
before being uploaded. I was trying to avoid that just for the sake of
an indexing problem on CPAN, but I'm happy to do it if this is causing
you more headaches than voting for a new release would be for the
folks at Apache!)


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-02 Thread Neil Bowers via modules
> Too many years in between and too much code changes on PAUSE to have a
> clear view what might be the cause. My current theory is that it's to do
> with a weakness in this META.yml: the "provides" entries in the META.yml
> all have no "file" attribute:

That was my guess too, when looking at it last night. But then I noticed that 
the .13 release is similar, so I decided to sleep on it.

I just looked at the Changes file for CPAN::Meta, and there have been some 
changes / bug fixes related to handling of provides. So maybe the version being 
used by PAUSE when the .13 release was fine with that?

I just checked the spec (CPAN::Meta::Spec), which says that the "file" key is 
required (https://metacpan.org/pod/CPAN::Meta::Spec#file1). Can you do a .16 
release please Steve, with a file: key for each module listed in the provides: 
section.

Neil


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-02 Thread Andreas Koenig
> On Tue, 2 Mar 2021 17:44:06 +, Steve Hay via modules 
>  said:

  > On Tue, 2 Mar 2021 at 17:24, Andreas Koenig
  >  wrote:
 >> 
 >> > On Tue, 2 Mar 2021 08:41:11 +, Steve Hay via modules 
 >> >  said:
 >> 
 >> > On Mon, 1 Mar 2021 at 22:26, Neil Bowers  wrote:
 >> >>
 >> >> Hi Steve,
 >> >>
 >> >> Ah, I forgot to mention — you’ll need to force PAUSE to re-index the 
 >> >> tarball you uploaded.
 >> >>
 >> >> When you log in to PAUSE, in the life sidebar you’ll see "Force
 >> >> Reindexing", under "Utils" (3rd section). When you click on that
 >> >> you’ll get a list of the files in your upload directory. Click the
 >> >> checkbox next to libapreq2-2.15.tar.gz and then click on "Reindex".
 >> >> You’ll get an email within the hour with the results of the
 >> >> reindexing.
 >> >>
 >> >> That will make your release appear in the CPAN Index. MetaCPAN will need 
 >> >> to reindex it as well — I’ll give them a nudge once your reindexing is 
 >> >> done.
 >> >>
 >> 
 >> > Ok, thanks. I see Andreas has actually done this for me already: I
 >> > have an email saying that it will be reindexed in about 20min from
 >> > now, so if you could give MetaCPAN a nudge for me when that's done
 >> > then that would be brilliant.
 >> 
 >> > Many thanks to you & Andreas for sorting this all out for me :-)
 >> 
 >> You're welcome. Unfortunately we are not yet through with this. Later I
 >> got an error message that the indexing failed. I suppose you received it
 >> as well, but it gives no clue. At the moment I have no idea yet, how to
 >> work around some built-in spell.

  > Yes, I saw the message. It ended with "Nothing in this distro has been
  > indexed, because according to META.yml this package does not provide
  > any modules." but comparing the META.yml with that in libapreq2-2.13
  > (which presumably is indexed since it appears on MetaCPAN?) I see
  > nothing but the expected differences. In particular, they both list
  > the same set of "provided modules", with just the versions bumped from
  > 2.13 to 2.15.

Too many years in between and too much code changes on PAUSE to have a
clear view what might be the cause. My current theory is that it's to do
with a weakness in this META.yml: the "provides" entries in the META.yml
all have no "file" attribute:

 : provides:
 :   Apache2::Request:
 : version: 2.15
 :   Apache2::Cookie:
 : version: 2.15

Compare this with:

 : provides:
 :   Acme::Godot:
 : file: lib/Acme/Godot.pm
 : version: '0.001010'

I think it's worth trying to provide the "file" with the provides
attribute next time you come around with a release.

Now you ask why did it work with 2.13. I don't know, offhand, it's just
an unproven theory anyway.

What I now did was a very dirty manual operation in the DB directly:

 : update packages set version=2.15,
 : dist='S/SH/SHAY/libapreq2-2.15.tar.gz',
 : file='missing file attrib in META.yaml/provides; ed. by andk'
 : where dist like '%libapreq2%' ;

So now 2.15 is indexed and no code on PAUSE was changed for that. Let me
know when I overlooked anything.

Greetings,
-- 
andreas


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-02 Thread Steve Hay via modules
On Tue, 2 Mar 2021 at 17:24, Andreas Koenig
 wrote:
>
> > On Tue, 2 Mar 2021 08:41:11 +, Steve Hay via modules 
> >  said:
>
>   > On Mon, 1 Mar 2021 at 22:26, Neil Bowers  wrote:
>  >>
>  >> Hi Steve,
>  >>
>  >> Ah, I forgot to mention — you’ll need to force PAUSE to re-index the 
> tarball you uploaded.
>  >>
>  >> When you log in to PAUSE, in the life sidebar you’ll see "Force
>  >> Reindexing", under "Utils" (3rd section). When you click on that
>  >> you’ll get a list of the files in your upload directory. Click the
>  >> checkbox next to libapreq2-2.15.tar.gz and then click on "Reindex".
>  >> You’ll get an email within the hour with the results of the
>  >> reindexing.
>  >>
>  >> That will make your release appear in the CPAN Index. MetaCPAN will need 
> to reindex it as well — I’ll give them a nudge once your reindexing is done.
>  >>
>
>   > Ok, thanks. I see Andreas has actually done this for me already: I
>   > have an email saying that it will be reindexed in about 20min from
>   > now, so if you could give MetaCPAN a nudge for me when that's done
>   > then that would be brilliant.
>
>   > Many thanks to you & Andreas for sorting this all out for me :-)
>
> You're welcome. Unfortunately we are not yet through with this. Later I
> got an error message that the indexing failed. I suppose you received it
> as well, but it gives no clue. At the moment I have no idea yet, how to
> work around some built-in spell.

Yes, I saw the message. It ended with "Nothing in this distro has been
indexed, because according to META.yml this package does not provide
any modules." but comparing the META.yml with that in libapreq2-2.13
(which presumably is indexed since it appears on MetaCPAN?) I see
nothing but the expected differences. In particular, they both list
the same set of "provided modules", with just the versions bumped from
2.13 to 2.15.

>
> Will try again later,,,

Thanks again :-)


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-02 Thread Andreas Koenig
> On Tue, 2 Mar 2021 08:41:11 +, Steve Hay via modules 
>  said:

  > On Mon, 1 Mar 2021 at 22:26, Neil Bowers  wrote:
 >> 
 >> Hi Steve,
 >> 
 >> Ah, I forgot to mention — you’ll need to force PAUSE to re-index the 
 >> tarball you uploaded.
 >> 
 >> When you log in to PAUSE, in the life sidebar you’ll see "Force
 >> Reindexing", under "Utils" (3rd section). When you click on that
 >> you’ll get a list of the files in your upload directory. Click the
 >> checkbox next to libapreq2-2.15.tar.gz and then click on "Reindex".
 >> You’ll get an email within the hour with the results of the
 >> reindexing.
 >> 
 >> That will make your release appear in the CPAN Index. MetaCPAN will need to 
 >> reindex it as well — I’ll give them a nudge once your reindexing is done.
 >> 

  > Ok, thanks. I see Andreas has actually done this for me already: I
  > have an email saying that it will be reindexed in about 20min from
  > now, so if you could give MetaCPAN a nudge for me when that's done
  > then that would be brilliant.

  > Many thanks to you & Andreas for sorting this all out for me :-)

You're welcome. Unfortunately we are not yet through with this. Later I
got an error message that the indexing failed. I suppose you received it
as well, but it gives no clue. At the moment I have no idea yet, how to
work around some built-in spell.

Will try again later,,,
-- 
andreas


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-02 Thread Steve Hay via modules
On Mon, 1 Mar 2021 at 22:26, Neil Bowers  wrote:
>
> Hi Steve,
>
> Ah, I forgot to mention — you’ll need to force PAUSE to re-index the tarball 
> you uploaded.
>
> When you log in to PAUSE, in the life sidebar you’ll see "Force Reindexing", 
> under "Utils" (3rd section). When you click on that you’ll get a list of the 
> files in your upload directory. Click the checkbox next to 
> libapreq2-2.15.tar.gz and then click on "Reindex". You’ll get an email within 
> the hour with the results of the reindexing.
>
> That will make your release appear in the CPAN Index. MetaCPAN will need to 
> reindex it as well — I’ll give them a nudge once your reindexing is done.
>

Ok, thanks. I see Andreas has actually done this for me already: I
have an email saying that it will be reindexed in about 20min from
now, so if you could give MetaCPAN a nudge for me when that's done
then that would be brilliant.

Many thanks to you & Andreas for sorting this all out for me :-)

Steve


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-01 Thread Neil Bowers via modules
Hi Steve,

Ah, I forgot to mention — you’ll need to force PAUSE to re-index the tarball 
you uploaded.

When you log in to PAUSE, in the life sidebar you’ll see "Force Reindexing", 
under "Utils" (3rd section). When you click on that you’ll get a list of the 
files in your upload directory. Click the checkbox next to 
libapreq2-2.15.tar.gz and then click on "Reindex". You’ll get an email within 
the hour with the results of the reindexing.

That will make your release appear in the CPAN Index. MetaCPAN will need to 
reindex it as well — I’ll give them a nudge once your reindexing is done.

Cheers,
Neil


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-01 Thread Steve Hay via modules
On Mon, 1 Mar 2021 at 21:02, Neil Bowers  wrote:
>
> I’ve just given you co-maint on libapreq2. That includes all the packages in 
> the distribution, and the pseudo-package "libapreq2", permissions on which 
> are required for you to do a release.
>

Thanks, Neil.

Does this mean that my recent upload of libapreq2-2.15 will soon
appear on metacpan.org? If not then is there any way to fix that?
Perhaps I need to contact someone at metacpan.org instead now?


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-03-01 Thread Neil Bowers via modules
Hi Steve,

I’ve just given you co-maint on libapreq2. That includes all the packages in 
the distribution, and the pseudo-package "libapreq2", permissions on which are 
required for you to do a release.

Cheers,
Neil


Re: Failed: PAUSE indexer report SHAY/libapreq2-2.15.tar.gz

2021-02-23 Thread Steve Hay via modules
Hi,

Regarding the failed indexer job below, is it possible to get
permission to upload this new libapreq2 release? (Or more specifically
to get it indexed, since I see it has been uploaded here:
https://cpan.metacpan.org/authors/id/S/SH/SHAY/).

I have perms to upload mod_perl2 releases, but haven't done a
libapreq2 before. It appears I don't have the necessary perms for
this. (The PAUSE View Permissions page for libapreq2 says that the
special APML name has comaint, which I thought might confer perms to
me, but it obviously doesn't work like that!)

I offered to do this on behalf of Joe Orton, who put the release on
Apache servers (see http://httpd.apache.org/apreq/download.cgi) but
he's never done CPAN uploads before. He confirmed he's happy for me to
do it on his behalf here:
https://lists.apache.org/thread.html/rc729a2b2a857963f6c03a99217f8946f2981fe5ffc5a7cbcd0d0ab18%40%3Cdev.httpd.apache.org%3E

Thanks,
Steve

On Tue, 23 Feb 2021 at 13:28, PAUSE  wrote:
>
> The following report has been written by the PAUSE namespace indexer.
> Please contact modules@perl.org if there are any open questions.
>
>   User: SHAY (Steve Hay)
>   Distribution file: libapreq2-2.15.tar.gz
>   Number of files: 312
>   *.pm files: 24
>   README: libapreq2-2.15/README
>   META-File: libapreq2-2.15/META.yml
>   META-Parser: Parse::CPAN::Meta 1.4414
>   META-driven index: yes
>   Timestamp of file: Tue Feb 23 13:26:47 2021 UTC
>   Time of this run: Tue Feb 23 13:28:39 2021 UTC
>
> This distribution name will only be indexed when uploaded by users with
> permission for the package libapreq2. Either someone else has ownership
> over that package name, or this is a brand new distribution and that
> package name was neither listed in the 'provides' field in the META file
> nor found inside the distribution's modules. Therefore, no modules will
> be indexed.
>
> Further details on the indexing attempt follow.
>
> Nothing in this distro has been
> indexed, because according to META.yml this
> package does not provide any modules.
>
> __END__