IRC channel logs

<stikonas>fossy: yeah, I think so

<stikonas>hmm, so my download issue is intermittent

<stikonas>maybe it's worth adding retry on download

<stikonas>oh there is...

<stikonas>so even retries=2 didn't help somehow

<fossy>hm, should we up the default

<stikonas>maybe 3 would make some sense

<stikonas>and perhaps a short 1s sleep between retries?

<fossy>oh sleep would be smart

<stikonas>otherwise it might be the same transient problem

<fossy>ok, there we go

<stikonas>thanks

<stikonas>I guess good to merge

<fossy>merged :D

<stikonas>I haven't set automatic updates on my mirror yet...

<fossy>neither, just needs a simple cron though

<stikonas>just the first 2 points from your readme...

<stikonas>we'll see how frequently tarballs change...

<stikonas>fossy: do we need some way to communicate list of available mirrors?

<stikonas>well, I guess it will be mostly obsolete if we manage to get p2p working...

<fossy>stikonas: maybe we could add a wiki page https://github.com/fosslinux/live-bootstrap/wiki and let people put their mirrors there?

<stikonas>yeah, that could work for now

<stikonas>(hopefully we won't get spam...)

<ztrawhcse>stikonas, lanodan: wearing my hat as part of the Reproducible Builds project I can confirm GNU gzip has stable (== deterministic) output and that I was personally involved in arranging that BusyBox gzip shall now produce the same output as GNU gzip. Github has used GNU gzip since forever and the only times checksums broke have been a) rare occasions when git-archive changed their tar stream

<ztrawhcse>format, b) when git-archive started using an internal gzip impl which emits a different output stream than GNU gzip

<ztrawhcse>fossy: git-archive is deterministic iff a) they don't change the tar stream format, which they rarely do and have a soft commitment to refrain from doing since it "breaks the universe", b) the compressor is stable

<ztrawhcse>in practice, this combination means there is very rarely an issue

<stikonas>fossy: there is a minor bug with urls:

<stikonas>/bash-5.2.15.tar.gz HTTP/1.1" 200 10951843 "-" "curl/8.5.0" "-"

<stikonas>argh, irc ate double slash

<stikonas>anyway it is //bash-5.2.15.tar.gz HTTP/1.1" 200 10951843 "-" "curl/8.5.0" "-"

<stikonas>that must be in helpers.sh...

<fossy>stikonas: what were you passing as your mirror argument?

<fossy>does the double slash matter

<stikonas>oh yes, I had shash at the end...

<stikonas>it it doesn't matter...

<stikonas>nginx copes with double shash just fine

<fossy>i'm think let's just leave it, and if theres some weird web server out there that doesn't support it , people just need to ensure they don't use trailing slash

<fossy>but i can't think of one that doesn't

<lanodan>ztrawhcse: Oooh nice to know for busybox, guess could also check if pigz (default gzip implementation here) matches

<ztrawhcse>lanodan: https://github.com/mirror/busybox/commit/c660cc1b7714fffbac95c9378ff4b73de650a6de

<ztrawhcse>general discussion: https://lists.reproducible-builds.org/pipermail/rb-general/2021-October/002422.html

IRC channel logs

2025-02-03.log