Re: Bug#900918: debian-installer: Please make the generated images reproducible
On 1/22/2019 7:08 AM, Cyril Brulebois wrote: >> Alternatively, we could make pigz a strict build requirement but >> that sounds a little antisocial. > Right. In what way do you consider this antisocial and what's speaking against doing that? If it's about CPU time, then maybe it should obey the parallelization setting of the build process. But then it's already a build process and if you want that to not be detrimental to your desktop performance, you nice it. Apart from that thing I really struggle to find something "antisocial" in that build-dependency. Kind regards and thanks Philipp Kern
Re: Bug#900918: debian-installer: Please make the generated images reproducible
Philipp, > > > Alternatively, we could make pigz a strict build requirement but > > > that sounds a little antisocial. > > > > Right. > > In what way do you consider this antisocial and what's speaking against > doing that? I was using this word in a somewhat romantic sense; fewer dependencies are "better" in some aesthetic or poetic sense. Please do not read too much into it. :) (I had also slightly assumed that pigz was only on some archs, but I am clearly mistaken there...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Bug#900918: debian-installer: Please make the generated images reproducible
Hi Cyril, > I think I'd prefer closing this very bug report whenever what's in > git gets uploaded That would definitely work for me. Indeed, it would probably help separate discussions/issues correctly as any followups are likely = to be much more specific. > half the build time is spent waiting for gzip to finish its work on > a single core. Reproducibility is very nice but I would definitely > hate to lose this huge speed-up. Absolutely, hence my regret at suggesting a fallback to gzip. *nod* > > Perhaps we need to record the environment after all […] > Ah right, pigz isn't in Build-Depends, so it's not included in the > .buildinfo file… "the .buildinfo"? As I understood it we are not recording any explicit debian-installer build attestation document that records the environment at the moment. Again, will reload this all into my head soon and come up with a suggested solution if required in another bug report. Thanks again. :) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Bug#900918: debian-installer: Please make the generated images reproducible
On Tue, 2019-01-22 at 10:53 +0100, Philipp Kern wrote: > On 1/22/2019 7:08 AM, Cyril Brulebois wrote: > > > Alternatively, we could make pigz a strict build requirement but > > > that sounds a little antisocial. > > Right. > In what way do you consider this antisocial and what's speaking > against > doing that? If it's about CPU time, then maybe it should obey the > parallelization setting of the build process. [...] The general way to communicate this is by wrapping the build in "taskset", and pigz will surely follow that. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman signature.asc Description: This is a digitally signed message part
Bug#920244: cdimage.debian.org: Please add LXQt and Standard builds for live Buster images
Package: cdimage.debian.org Severity: wishlist Tags: patch Debian Images Team, Now that live-tasks includes live-task-lxqt and live-task-standard, please add LXQt and Standard builds for live Buster images. This would fix Bug #876428 - No 'standard' image of Debian-Live: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876428 Untested patch for live-setup/available/run-30live-wrapper is attached. Thank you! Daniel Lewart --- a/available/run-30live-wrapper 2019-01-12 03:58:15.0 -0600 +++ b/available/run-30live-wrapper 2019-01-23 00:00:00.0 -0600 @@ -30,9 +30,12 @@ if [ "$BUILDS"x = ""x ] ; then case "$CODENAME" in - stretch|buster) + stretch) BUILDS="cinnamon gnome kde lxde mate xfce" ;; + buster) + BUILDS="cinnamon gnome kde lxde lxqt mate standard xfce" + ;; *) log " ABORTING: Don't know what to build for \"$CODENAME\"" exit 1
