IRC chat logs for #ltsp on irc.libera.chat (webchat)


Channel log from 5 February 2022   (all times are UTC)

00:45vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
04:38woernie has joined IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de)
05:02vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)
07:21woernie has left IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de, Quit: No Ping reply in 180 seconds.)
07:22woernie has joined IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de)
07:45ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
11:12usuario^abalar20 has joined IRC (usuario^abalar20!~usuario^a@84.123.130.64.dyn.user.ono.com)
11:13usuario^abalar20 has left IRC (usuario^abalar20!~usuario^a@84.123.130.64.dyn.user.ono.com, Client Quit)
11:15
<sunweaver>
alkisg: no problem at all.
11:15
vagrantc: if alkisg approves #659 upstream, could you cherry-pick that change to make "ltsp kernel" work for people who have /tmp on tmpfs? Thanks.
11:16
(cherry-pick to LTSP in Debian, that is)
17:57vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
19:41
<vagrantc>
heh. was looking into the reproducibility issue with ltsp and lamby beat me to it :)
19:48
<alkisg>
A perfect job too, with an upstream pr...
21:08
Although it might make sense for the build environment to take care about dates and timezones, instead of each separate developer code
21:10
<vagrantc>
normalizing the build environment is definitely useful, but building code reproducibly shouldn't depend on it
21:10
(or in this case, manpages)
21:11
it's also nigh-impossible to force a date ... you can set the build to a starting time, but depending on how long the build takes, the amount of parallelism, etc. you might end up embedding a different timestamp
21:12
fixing things in the toolchains ... e.g. fixing go-md2man is an option
21:12
and if you try to freeze the date to a specific time, various buildsystems will fail to work
21:13
alkisg: i wonder if the switch to go-md2man was what changed ... earlier it "just worked"
21:14
other than a fluke, ltsp has been building reproducibly for quite a while https://tests.reproducible-builds.org/debian/history/amd64/ltsp.html
22:19
alkisg: so ... should i release a new upstream version or fork the debian packaging to include the patch?
22:20* vagrantc can even fork it into a debian/sid branch
22:42ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:15woernie has left IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
23:15woernie has joined IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de)
23:20woernie has left IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
23:45
<vagrantc>
uploaded a -2 version to debian unstable, made a debian/bookworm branch (since it's targeting bookworm), and cherry-picked the relevent commits into the main branch