Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
Set by moderator on 8 October 2016.
tbrowder .tell ugexe it still doesn't work and i have no idea what's wrong 00:09
01:29 FROGGS joined 01:48 ilbot3 joined
moderator Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
ugexe tbrowder: make sure to update zef - it points at a different mirror now 02:37
gist.github.com/ugexe/490275560764...e1-txt-L65
it installed fine for me at least 02:38
ecosystem-api.p6c.org/ there is an update.log and errors.json but they dont really tell you much 02:47
moritz is anything wrong with the projects.json from ecosystem-api.p6c.org? 05:30
07:12 domidumont joined 07:16 domidumont joined
tbrowder moritz: info for my module in that projects.json looks correct; for some reason it seems my zef doesn't update properly. looking into my local version now... 10:22
10:26 tadzik joined
tbrowder i update zef but no change in my module version. what is "zef update" supposed to do? update a local copy of the projects.json? should i reinstall zef? 10:44
okay, success! i deleted my $HOME/.zef directory, used zef to uninstall itself, used panda to install it, used zef to uninstall and install my module and got the current version. my belief is that the .zef dir was bad somehow. i'll try another version bump later and see if all is okay. 11:05
12:02 domidumont joined
ugexe tbrowder: oh, next time you can do `zef nuke StoreDir` to do remove the ~/.zef folder *or* do `zef --/cached install My::Module` 17:35
what i think happened is the cached versions (stored in ~/.zef/store) had some of those mixed up META6.json files (where the archived file did not match what ecosystem-api.p6c.org was given) 17:36
zef nuke StoreDir just deletes the cache directory, and --/cached just disabled using the cached directory as a content storage backend 17:37
you can see what you have cached with `zef --/p6c list` 17:47
tbrowder thanks! testing version bump now... 19:05
ugexe tbrowder: I imagine you want to leave the old version links in the ecosystem list - you just add a new one each time you bump the version. Othewise if someone does `"depends" : ["Net::IP::Lite:ver<0.1.2>"]` it won't be found (since you removed the previous link and replaced it entirely with 0.1.4) 20:46
tbrowder ugexe: okay, i can put them back. i wasn't sure from your comments to moritz whether multiple links were okay. 21:48
however, none of the code really changed, so, unless you insist, i will start adding instead of replacing links with the next release, okay? 22:05
but, now that i'm more fluent in ecosystem-speak, i'll try to get them back in and hope they don't break (if they do i will have to remove them). 22:11
i checked and i found only two good, working entries, so they sre now in the sys 22:33
list-- fingers crossed... 22:34