Re: Problem with indexing module

2017-06-14 Thread Ron Savage
Hi Andreas Thanx! On 14/06/17 14:29, Andreas Koenig wrote: On Wed, 14 Jun 2017 14:12:53 +1000, Ron Savage said: > Hi Andreas > Then would it be possible for the error msg to include that link, or a > useful summary thereof, when a version # issue is detected?

Re: Problem with indexing module

2017-06-13 Thread Andreas Koenig
> On Wed, 14 Jun 2017 14:12:53 +1000, Ron Savage said: > Hi Andreas > Then would it be possible for the error msg to include that link, or a > useful summary thereof, when a version # issue is detected? Maybe. I've opened an issue

Re: Problem with indexing module

2017-06-13 Thread Ron Savage
Hi Andreas Then would it be possible for the error msg to include that link, or a useful summary thereof, when a version # issue is detected? On 13/06/17 07:17, Andreas Koenig wrote: On Sun, 11 Jun 2017 09:59:54 +1000, Ron Savage said: > Hi Alexandr > Your module

Re: Problem with indexing module

2017-06-12 Thread Andreas Koenig
> On Sun, 11 Jun 2017 09:59:54 +1000, Ron Savage said: > Hi Alexandr > Your module starts off with: > package Devel::Camelcadedb; > our $VERSION = "2017.1"; No, you seem to have picked the wrong file. I find this version declaration in the file: our $VERSION

Problem with indexing module

2017-06-10 Thread Ron Savage
Hi Alexandr Your module starts off with: package Devel::Camelcadedb; our $VERSION = "2017.1"; # http://perldoc.perl.org/DB.html # http://perldoc.perl.org/perldebug.html # http://perldoc.perl.org/perldebtut.html # http://perldoc.perl.org/perldebguts.html package DB; The error is 'No

Problem with indexing module

2017-06-08 Thread Alexandr Evstigneev
Got an error from pause: The following report has been written by the PAUSE namespace indexer. Please contact modules@perl.org if there are any open questions. User: HURRICUP () Distribution file: Devel-Camelcadedb-v2017.100.1.tar.gz Number of files: 12 *.pm files: 1 README:

Re: Problem with indexing

2016-06-11 Thread Johan Vromans
On Thu, 9 Jun 2016 13:49:37 + Matt S Trout wrote: > Yes, it should. Poor phrasing on my part, by "don't need to index" I meant > "don't need to go through the dist looking for files" - at which point > having no_index at all is unnecessary, and no_index-ing lib/ is just

Re: Problem with indexing

2016-06-09 Thread Matt S Trout
On Tue, Jun 07, 2016 at 07:51:04PM +0200, Johan Vromans wrote: > On Tue, 7 Jun 2016 17:02:03 + > Matt S Trout wrote: > > > provides means "you don't need to index this dist at all", > > With all respect, according to CPAN:::Meta::Spec: > > "you shouldn't be indexing

Re: Problem with indexing

2016-06-08 Thread Johan Vromans
On Tue, 7 Jun 2016 17:02:03 + Matt S Trout wrote: > provides means "you don't need to index this dist at all", With all respect, according to CPAN:::Meta::Spec: "you shouldn't be indexing anything in the first place - just use that"

Re: Problem with indexing

2016-06-07 Thread Matt S Trout
On Tue, Jun 07, 2016 at 11:11:52AM +0200, Johan Vromans wrote: > > It seems to be crucial to avoid no_index/provides conflicts, since these > are dealt with in opposite ways by CPAN (right) and MetaCPAN (wrong). provides means "you don't need to index this dist at all", so while not an error,

Re: Problem with indexing

2016-06-07 Thread Johan Vromans
On Tue, 07 Jun 2016 00:16:48 +0200 Andreas Koenig wrote: > I would suggest to bring this issue to > https://github.com/CPAN-API/metacpan-web/issues This issue is already known to MetaCPAN, as Neil writes in his reply. > I cannot see anything wrong with

Re: Problem with indexing

2016-06-07 Thread Andreas Koenig
> On Mon, 6 Jun 2016 08:42:18 +0200, Johan Vromans > said: > Hi y'all, Hi Johan, I would suggest to bring this issue to https://github.com/CPAN-API/metacpan-web/issues It looks to me like a genuine metacpan bug. > I've uploaded a new package,

Re: Problem with indexing

2016-06-07 Thread Neil Bowers
Hi Johan, > I've uploaded a new package, App-Music-ChordPro. It has gone through several > uploads for the last couple of days. The first version was 0.51, the most > recent upload is 0.52.2. > > The packages appears in the CPAN collection (www.cpan.org) a couple > of hours after each upload,

Problem with indexing

2016-06-06 Thread Ron Savage
Hi Johan I wouldn't assume you've made a mistake, but I would assume the MetaCPAN processing is just taking longer than your expect. -- Ron Savage - savage.net.au

Problem with indexing

2016-06-06 Thread Johan Vromans
Hi y'all, I've uploaded a new package, App-Music-ChordPro. It has gone through several uploads for the last couple of days. The first version was 0.51, the most recent upload is 0.52.2. The packages appears in the CPAN collection (www.cpan.org) a couple of hours after each upload, but they still