From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Is it safe to remove debconf cache files in isar system
Date: Tue, 15 Feb 2022 17:13:04 +0100 [thread overview]
Message-ID: <20220215161304.GE4704@yssyq.m.ilbers.de> (raw)
In-Reply-To: <OSYPR01MB55422F9AABFB4B49B632AFC5A4339@OSYPR01MB5542.jpnprd01.prod.outlook.com>
On Mon, Feb 14, 2022 at 07:35:19PM +0000, Venkata.Pyla@toshiba-tsip.com wrote:
> >I am working to fix some reproducible build failures in isar system, as part of
> >this I wanted to know some ideas to fix it.
...
> >Part of the debconf db file where the difference is found
> >(/var/cache/debconf/config.dat)
> >Build1:
...
> > NEW = /etc/locale.nopurge.29308
> >
> >Build2:
...
> > NEW = /etc/locale.nopurge.19132
> >
> >The probable solution I am thinking of is:
> >1. remove the debconf cache files (rm -f /var/cache/debconf/*)
> >2. Fix the debconf in such a way it generates same package configuration on every build
For (1), https://debiananwenderhandbuch.de/debconf.html suggests that those may
be deleted, but questions would be asked during later package updates. If this
is important, maybe it could be workarounded by unattended installation.
(2) would be for sure a better approach. Debian does have a reproducible build
group and might be interested in that. That said, till now I've seen the effort
directed at reproducible packages, not a reproducible installation.
I think debconf people are the best who could answer this. If you don't like
debian-user, you may want to ask at
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds .
With kind regards,
Baurzhan.
prev parent reply other threads:[~2022-02-15 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 7:47 Venkata.Pyla
2021-12-17 16:56 ` Anton Mikanovich
2022-02-14 19:35 ` Venkata.Pyla
2022-02-15 16:13 ` Baurzhan Ismagulov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220215161304.GE4704@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox