SamantazFox has quit [Killed (NickServ (GHOST command used by SamantazFox_))]
SamantazFox_ has joined #crystal-lang
_ht has joined #crystal-lang
<frojnd>
mps: I use Alpine as a daily driver for my laptop, maybe I should also contact contributors for crystal pkg. spuun I just use irc. But is'nt discord bridged to irc?
<mps>
frojnd: though I'm not official maintainer of crystal for alpine practically I maintain it last few years
<spuun>
frojnd: at least no bridge now, dunno in the past. A lot of activity in the discord, so maybe worth joining it. Or use the forum.
<mps>
isn't discord closed source and non-free?
<mps>
frojnd: just checked and I see I'm contributor for crystal on alpine
<frojnd>
mps: will open an issue there. In the mantime, I'm trying to build it myself but I get a bunch of python errors after adding interpreter=1 to the build section: https://termbin.com/aiwp I don't understand where is this coming from as I don't see python being a dependency?
<frojnd>
Not sure what's going in my case (am also using edge build virtual machine) but as if python3~3.12 is too new for this? (I've updated alpine build machine)
<frojnd>
Also did you add python3 as dependency?
<frojnd>
I'm building on edge for: 1.10.1-r0 with interpreter=1 flag
<mps>
python 3.12 is installed on my machine
<frojnd>
On my isn't. And even if I add it to makedepends section I get the same error.
<frojnd>
So it's needed package I guess?
<mps>
now I will try with my bare builder in chroot to see
<frojnd>
Hm I've installed it with apk but it still fails
<mps>
ah, python3 is installed as dependency by `abuild deps`
<mps>
but I don't have machine with 3.19 alpine release to check
<frojnd>
What is odd is that... I'm trying this on edge :D
<frojnd>
Also Crystal 1.12 fails with same error
<mps>
on edge it works in my case`abuild deps unpack prepare build`
<mps>
I'm using aarch64 machine
<frojnd>
I'm using x86_64
<mps>
shouldn't be difference because I've built crystal 1.12 few weeks ago and pushed to alpine. It passed my dev macines, alpine CI and builders
<frojnd>
I think it's my build machine issuse
<frojnd>
Probably still have things depending on python 3.11
<mps>
that could be problem
<frojnd>
llvm16-test-utils
<frojnd>
But looking at /etc/apk/world isn't there
<frojnd>
I'll just del it and see
<mps>
`apk upgrade -s` will show some info
<frojnd>
Not much heh: OK: 761 MiB in 177 packages
<mps>
and 'EXPERIMENTAL SOFTWARE: if you find a bug, please consider opening an issue in ...'
<mps>
risky, but in such cases I run something like `apk del pkgname` and apk shows why it can't delete pkg
<frojnd>
Hm no changes
<frojnd>
Have checked if any installed packages depends on python: `while read p; do apk info -R "$p"; done < /etc/apk/world |grep python` but nothing
<mps>
you can then remove python
<mps>
python3
<frojnd>
I don't have it :)
<frojnd>
That's the weird thing
<frojnd>
I mean at lest not int /etc/apk/worls
<frojnd>
Woops
<frojnd>
I think I should dive into apk list -I isntead of the /etc/apk/world
<mps>
yes
<mps>
what is in your /etc/apk/repositories
<mps>
3.19 or edge
<frojnd>
It was the orphaned packages since are not shown from world.. Have removed them and now is cimpiling
<frojnd>
s/cimpiling/compiling
<frojnd>
mps: how long does it take to hit pkg from edge to main?
<mps>
you mean from edge to new stable release?
<mps>
edge is development 'branch', something like rolling release
<frojnd>
mps: yeah... what's the deciding factor from pkg to hit main branch on alpine? Talking for crystal pkg.
<mps>
in main repo goes mostly important packages
<frojnd>
We are announcing a new patch release of the Crystal 1.12 series with an important bugfix.
<mps>
crystal is in community because it needs to be upgraded more often
<frojnd>
I wasn't clear enough. I'm not talking about repositories main/community/testing but edge branch vs 3.19
<mps>
ah. stable releases have to be maintained for two years at least
<mps>
that means, bugfixes, sec issue etc
<mps>
community only 6 months
<mps>
bbl
<frojnd>
tyt
<frojnd>
Hm interesting, I was not able to build with: `abuild -r` there was a runtime ssl error. But with: `abuild deps unpack prepare build` I was able to build.