Report forwarded
to debian-bugs-dist@lists.debian.org, reproducible-builds@lists.alioth.debian.org, Debian Install System Team <debian-boot@lists.debian.org>: Bug#1019697; Package debootstrap.
(Tue, 13 Sep 2022 15:39:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Holger Levsen <holger@debian.org>:
New Bug report received and forwarded. Copy sent to reproducible-builds@lists.alioth.debian.org, Debian Install System Team <debian-boot@lists.debian.org>.
(Tue, 13 Sep 2022 15:39:04 GMT) (full text, mbox, link).
Package: debootstrap
Version: 1.0.127
Severity: wishlist
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Dear Maintainer,
using debootstrap 1.0.127 it's possible to reproducible bootstrap Debian,
provided one does three extra steps:
1. rm /var/log/dpkg.log /var/log/alternatives.log /var/log/bootstrap.log
2. rm /etc/machine-id /var/cache/ldconfig/aux-cache
3. SOURCE_DATE_EPOCH=$some_sane_value ; sudo tar --mtime="@$SOURCE_DATE_EPOCH" --clamp-mtime $SUITE -cf $SUITE.tar
This bug is about the first step. It would be really nice if debootstrap
had an option called --cleanup-logs which would delete those logs.
Step 2 (or rather it's first part) is tracked via #1018740: "debootstrap:
better initialisation of /etc/machine-id".
Step 3 would be another new feature for debootstrap, namely to create tar archives.
Thanks for maintaining debootstrap!
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
"I know what you're thinking" used to be an idiom but now it's a business model.
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>: Bug#1019697; Package debootstrap.
(Wed, 14 Sep 2022 09:03:03 GMT) (full text, mbox, link).
Acknowledgement sent
to "Chris Lamb" <lamby@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>.
(Wed, 14 Sep 2022 09:03:03 GMT) (full text, mbox, link).
To: "Holger Levsen" <holger@debian.org>,
"Debian Bug Tracking System" <1019697@bugs.debian.org>
Subject: Re: debootstrap: aid reproducible boostrapping by providing a --cleanup-logs
option
Date: Wed, 14 Sep 2022 10:00:32 +0100
Holger Levsen wrote:
> This bug is about the first step. It would be really nice if debootstrap
> had an option called --cleanup-logs which would delete those logs.
Would it be sensible to suggest that, instead of an explicit
command-line flag, that debootstrap would do this cleanup if
SOURCE_DATE_EPOCH is present?
If it helps, the idea of using the presence (or non-presence) of
SOURCE_DATE_EPOCH to slightly adjust the behaviour of a program is
already being used as a flag in other places.
(If it helps, the parallel bug for cdebootstrap is #1019698.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org 🍥 chris-lamb.co.uk
`-
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>: Bug#1019697; Package debootstrap.
(Wed, 14 Sep 2022 10:03:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Holger Levsen <holger@layer-acht.org>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>.
(Wed, 14 Sep 2022 10:03:02 GMT) (full text, mbox, link).
Hi Chris,
On Wed, Sep 14, 2022 at 10:00:32AM +0100, Chris Lamb wrote:
> > This bug is about the first step. It would be really nice if debootstrap
> > had an option called --cleanup-logs which would delete those logs.
> Would it be sensible to suggest that, instead of an explicit
> command-line flag, that debootstrap would do this cleanup if
> SOURCE_DATE_EPOCH is present?
I think that's an excellent idea! :)
> If it helps, the idea of using the presence (or non-presence) of
> SOURCE_DATE_EPOCH to slightly adjust the behaviour of a program is
> already being used as a flag in other places.
>
> (If it helps, the parallel bug for cdebootstrap is #1019698.)
Leaving the rest of your reply as I've cc:ed #1019698.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
"Climate change" is an euphenism. "Global warming" as well.
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Install System Team <debian-boot@lists.debian.org>: Bug#1019697; Package debootstrap.
(Wed, 14 Sep 2022 14:30:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Cyril Brulebois <kibi@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Install System Team <debian-boot@lists.debian.org>.
(Wed, 14 Sep 2022 14:30:03 GMT) (full text, mbox, link).
Chris Lamb <lamby@debian.org> (2022-09-14):
> Would it be sensible to suggest that, instead of an explicit
> command-line flag, that debootstrap would do this cleanup if
> SOURCE_DATE_EPOCH is present?
LGTM, and much better than the command line flag I was definitely not a
huge fan of (as mentioned initially).
It would probably make sense to have a tiny note in the manpage so that
people can check the difference in behaviour if they notice and wonder.
> If it helps, the idea of using the presence (or non-presence) of
> SOURCE_DATE_EPOCH to slightly adjust the behaviour of a program is
> already being used as a flag in other places.
Good to know, thanks.
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.