IRC channel logs
2024-09-24.log
back to list of logs
<oriansj>daddy: the stage0-posix release is done <daddy>can you get a release tarball as well? that's the part i'm having difficulty with, can't get submodules through GitHub archives <daddy>the github one doesn't include submodules, it looks like you uploaded one manually for 1.6.0 <daddy>that said, we're also considering whether we should allow use of release assets vs src assets, so this might not be how stagex moves forward in the future - we may choose to just download the submodules we need directly. if you'd rather wait until i can confirm if it's necessary, that's also fine. <matrix_bridge><Andrius Štikonas> oriansj: I think daddy wants make-dist tarballs <matrix_bridge><Andrius Štikonas> janneke added support for creating them to our makefiles <daddy>I think stagex consensus is to download all source tarballs and unpack manually so it's not as pressing an issue but it may help someone else who tries to download everything all in one go <Googulator>daddy: after the XZ incident, I'd argue against preferring source tarballs to Git repositories... <daddy>Googulator: in this case, i mean the ones automatically generated by GitHub <nimaje>the backdoor was added to the executable by a changed configure script (I think) (it was already in the repo as a binary "test file" (which was never used by the tests)) <janneke>that's why, when i add a `dist' target to make, i also make sure the tarball will be reproducible <janneke>gitlab's tarballs are not (guaranteed to be) reproducible <andydude>is there a wiki or readme for making reproducible tarballs? <andydude>like is there a --no-timestamps feature? <tobtoht_>`git ls-files --recurse-submodules` instead of `find` if you want to package a git repo including submodules and want to exclude .gitignored files <tobtoht_>`git archive` if you don't need submodules <matrix_bridge><Andrius Štikonas> tobtoht_: well, that's what make dist does there for stage0-posix <lrvick>oh okay. different filename threw me off <lrvick>and didn't see a make target for it, but that's fine <stikonas>also apprently that make target is only good if your worktree is empty... <stikonas>just ran it in my normal dev repo and it created 8 MiB tarball <stikonas>annoyingly to make release note page on github I have to manually reformat Changelog.org to markdown... <ekaitz>stikonas: what do you know about stagex? <ekaitz>it was mentioned to me by zig's author right now <stikonas>but my understanding is that it's largely live-bootstrap in docker <ekaitz>yeah, that's mostly what i understood yeah <stikonas>well, live-bootstrap supports a lot of different running modes <stikonas>natively in the repo there is already qemu / baremetal, chroot, bubblewrap... <stikonas>hopefully at some point we can have native 64-bit live-bootstrap <stikonas>but we are not there yet (mostly due to mescc->tinycc transition) <stikonas>though I think while working on building gcc with tcc on riscv64 we discovered that there are some 64-bit bugs in tcc too <stikonas>I think there was some fix that got merge in tcc but only for riscv64 <stikonas>we also don't have a release of bootstrappable tcc that works for both i386 and riscv64... <stikonas>now older snapshot only works on i386 and newer only on riscv64 <aggi>are there git-tag added to those? <stikonas>but you can always go back from snapshot to commit <stikonas>since (short) commit hash is in the name of the snapshot <stikonas>tcc-0.9.26-1157-gdd46e018.tar.gz means commit dd46e018 <ekaitz>now efraim is trying to integrate everything in guix so we can do some minieffort now to fix these things