00:57 jjatria left 01:10 jjatria joined 01:44 sjn left 01:45 deoac left 01:46 sjn joined 02:07 toddr left, toddr joined 02:24 sibl joined 02:25 coleman left 02:26 kylese joined, coleman joined 02:27 Guest4062 left, hulk left, Guest693 joined 02:30 sibl left, sibl joined 02:38 bd3i left, bd3i joined 02:56 sibl left 03:09 human_blip left 03:11 human_blip joined 03:15 kylese left, kylese joined 03:28 apogee_ntv joined
apogee_ntv Just pushed 0.2.0 of LLM::Character, I can see it at 360.zef.pm but when I do a zef update it still sees latest as 0.1.3 03:30
What am I forgetting?
nemokosch well, what do you run? 03:31
apogee_ntv zef update && zef install LLM::Character 03:32
No reason to proceed. Use --force-install to continue anyway 03:33
I tried that and still no update
nemokosch it does retrieve 0.2.0 for me but to tell you the truth, I have also had issues like that - even issues where zef would outright claim something is installed and then they would be missing at runtime 03:34
what if you specifically install LLM::Character:ver<0.2.0> ? 03:35
apogee_ntv % zef install LLM::Character:ver<0.2.0> !7591 03:37
zsh: parse error near `\n'
aruniecrisps whats a good website to post snippets? 03:38
i wanna post an error snippet but i forgot the most popular one for a while 03:39
nemokosch apogee_ntv: perhaps you want to use apostrophes
aruniecrisps nvm
got it
nemokosch < > stuff has special meaning for shell probably
apogee_ntv ===> Searching for: LLM::Character:ver<0.2.0>
No candidates found matching identity: LLM::Character:ver<0.2.0>
nemokosch is it reassuring if I say that the problem is on your end? 😅 03:41
aruniecrisps @SmokeMachine: I was wondering if you ever ran into this issue: pastebin.com/jzckrrSY
I'm currently trying to use UUID ids but I'm running into this weird error 03:42
nemokosch to be honest, no amount of incantations could get me zef 1.0, either, still using 0.22.7 which seems to come with rakubrew and Rakudo 2026.01 03:44
ugexe apogee_ntv: have you tried running zef update again since? when you run `zef update --debug` how many distributions does it show for fez? if you try to curl the url it shows when updating fez what do you see reasonable looking json you curl it (i.e. curl 360.zef.pm)? if the answers to those things look sane, do the contents of ~/.zef/store/fez/fez.json look to be the same as the json from the 03:49
url you curled?
apogee_ntv Zef::Repository::Ecosystems<fez>|6964 03:50
Zef::Repository::Ecosystems<rea>|14031
Zef::Repository::LocalCache |53
ugexe i see Zef::Repository::Ecosystems<fez>|6965 03:51
if you manually curl that url, how many distributions does the json object have?
nemokosch Zef::Repository::Ecosystems<fez>|6965
apogee_ntv How would I count from a curl? 03:52
ugexe curl --silent 360.zef.pm | jq length
apogee_ntv 6965
ugexe hmmm 03:54
my $proc = Zef::zrun-async($cmd, '--silent', '-L', '-z', $save-as.absolute, '-o', $save-as.absolute, $uri);
that is the command zef uses. notable is it uses -z
apogee_ntv If I just curl the URL manually to ~/.zef/store/fez/fez.json would that work? 03:55
aruniecrisps never mind @SmokeMachine got it working it looks like
ugexe yeah, or you can use `zef nuke StoreDir` to delete that whole ~/.zef/store directory. i suspect it works fine when the file doesnt exist
it could be interesting to see what the timestamps look like that curl would be acting this way though 03:56
since it might be worth removing that flag in zef
apogee_ntv Thanks works after nuke StoreDir. I imagine the old timestamps are ~5mo old, I dont use this machine much 03:57
But maybe I did the first update too early
And then got very new timestamp
ugexe shouldn't have been that old, it had all but 1 distribution that i saw
apogee_ntv Yeah that was after the first update though 03:58
About 40 mins ago
ugexe but yeah maybe when doing `zef update` it shouldn't use `-z`. it should maybe only do that optionally when it auto-updates for e.g. `zef install ...`
apogee_ntv According to raku.land I pushed the module 54 mins ago
Whats -z? My brain wants to say thats SSL but I'm guessing its not lol
ugexe -z, --time-cond <time> Transfer based on a time condition 04:00
-z <time|file> / --time-cond <...>: make the request conditional on modification time (“only if newer”).
If the remote resource has not changed since the given time, the server may respond 304 Not Modified and curl won’t download the body.