Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2014-03-23

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:45 klapperl joined #metacpan
04:27 ether_ joined #metacpan
06:53 ether_ joined #metacpan
09:19 neilb joined #metacpan
10:29 punter joined #metacpan
10:33 rashi joined #metacpan
16:07 metacpan joined #metacpan
16:07 metacpan [metacpan-developer] jchain opened pull request #14: Updated to vagrant v2 config (master...master) http://git.io/IxEupw
16:07 metacpan left #metacpan
16:07 dipsy [ Updated to vagrant v2 config by jchain · Pull Request #14 · CPAN-API/metacpan-developer · GitHub ]
16:22 metacpan joined #metacpan
16:22 metacpan [metacpan-developer] oalders pushed 2 new commits to master: http://git.io/ifegRw
16:22 metacpan metacpan-developer/master 7e88204 John Chain: Updated to vagrant v2 config
16:22 metacpan metacpan-developer/master 2c97ab6 Olaf Alders: Merge pull request #14 from jchain/master...
16:22 metacpan left #metacpan
16:22 dipsy [ Comparing 576459213ee1...2c97ab60aa3e · CPAN-API/metacpan-developer · GitHub ]
16:42 punter joined #metacpan
17:07 neilb joined #metacpan
18:58 neilb joined #metacpan
19:56 grantm joined #metacpan
20:31 ether_ joined #metacpan
20:40 cjm Can anybody tell me why https://metacpan.org/release/Pod-Loom points to version 0.05?
20:40 dipsy [ Pod-Loom-0.05 - Weave pseudo-POD into real POD - metacpan.org ]
20:40 cjm https://metacpan.org/release/CJM/Pod-Loom-0.06 looks ok
20:41 dipsy [ Pod-Loom-0.06 - Weave pseudo-POD into real POD - metacpan.org ]
20:41 cjm but https://metacpan.org/release/CJM/Pod-Loom-0.07 (released yesterday) is blank
20:41 dipsy [ Pod-Loom-0.07 - Weave pseudo-POD into real POD - metacpan.org ]
20:49 ether cjm: https://github.com/CPAN-API/cpan-api/issues/307
20:49 dipsy [ Indexer fails on Pod-Loom-0.07 · Issue #307 · CPAN-API/cpan-api · GitHub ]
20:49 ether metacpan is trying to parse your weird test data in t/, and falling over
20:50 ether which obviously it shouldn't :)
20:55 cjm makes sense
20:55 cjm that test file does violate the POD spec, but I never intended it to be parsed for POD
21:00 ether indeed
21:09 cjm I've converted that test to escape the =encoding lines
21:09 cjm I'll try releasing a new version and see if that helps
21:37 rashi joined #metacpan
21:43 SineSwiper_ joined #metacpan
22:00 cjm looks like version 0.08 indexed properly.  Thanks, ether++
22:49 neilb When you look at the page for a module, there's a list of dependencies on the right. Sometimes it says "and possibly others", but sometimes not. I'm guessing you list what the metadata says, but are also parsing for dependencies using some module, and if it finds modules not listed in the metadata, then you add "and possibly others"?
23:04 ether interesting, I thought "and possibly others" was always listed
23:05 grantm I think it doesn't say that if "dynamic_config" is 0/false in the metadata
23:15 haarg it's entirely based on dynamic_config
23:15 haarg try hovering over it
23:39 neilb haarg: ah!
23:39 haarg it's something i've thought about trying to link to a faq page or something
23:39 neilb What does a grey module name mean in MetaCPAN? (there's no tooltip text :-)
23:40 neilb I recently adopted Time::Duration::Parse, which was appearing fine in MC, but now appears to have been dropped from the module index...
23:43 nbezzala joined #metacpan
23:44 haarg it means it's a non-indexed release
23:45 haarg the colors need some adjustment and clarification
23:45 neilb does "non-indexed release" mean you haven't seen it in 02packages.details.txt (yet)?
23:47 haarg it means it isn't listed as 'latest' in the metacpan index
23:47 haarg which is meant to correspond to what's in 02packages, but isn't always correct
23:52 neilb Ok. Thanks. (it's turned black now)

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary