From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7042203840699957248 X-Received: by 2002:ac2:5f68:: with SMTP id c8mr3730206lfc.554.1639760208149; Fri, 17 Dec 2021 08:56:48 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:3d9e:: with SMTP id k30ls360615lfv.1.gmail; Fri, 17 Dec 2021 08:56:46 -0800 (PST) X-Google-Smtp-Source: ABdhPJwH3FbrM2b0Rqy3jOVrZMTp6g9O5scmW6CPqWfHbmWM8J1Wz51IsNu/seh7Lcil9IueJsCQ X-Received: by 2002:a19:7417:: with SMTP id v23mr3532367lfe.19.1639760206907; Fri, 17 Dec 2021 08:56:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1639760206; cv=none; d=google.com; s=arc-20160816; b=xTxI5gOWuhe+P+8I+kztMTeg6Af9vNypEEc+sRuHwsfdETFsRuniNxQ57thLczc6FU ijZWH+IRBTk2a5LK8fROXerGwhI1WOiR8XISnaeznw8HsEnUT3CkMpm2h1IGiZLRHKxD INDKTWXPq2Sp6QsLHnw9bLrbWJs+RQXbqWC0EZwr9u1UL64r6etsYjlG108mzpJcvb1p 7xJ8EPSsTmmoAIYwk8V/A8gWVgjprRY8SdpSvDesQ0/lhSnKyyOHkcs7RYoC7igetFsF i7f8qttWCvRHKXitGAKDuBCTXlbti6bqE7HZWhowCOfwosQP8SwfXTSc1/roHtiVyaic ekwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-language:content-transfer-encoding:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=RllOeEUA1LLjKToWj7DzfImZlYi5dA/QzxDU34kD1Pw=; b=1E5HkWq6eSLwMa481sykL1219wkLc+msXOsXklWCav5PovJXbKEjmlTUWEl81k6wX+ sxcGTsbEcL/+fEquniQyxU7RBU5PZGL7C6rUVQb9iqthXQsAI9gB3e+EmCgHJZJwuqfc +2KcUBAOIJj095F2go+ADH1cmPfRvKTeY2zPm1/fu2g8KosyAmJK2LpkA91+7x/HN+6F 9bsdtcJLz1NHkNMsu8KbhQd5hrel44y9RUGj/fppwSDQY4nLwhBT0Q1THazFC+MORwEX 8HNZge6dLdJis1sdAY1e1wkKc7/7uc48E+4cLopSa6PPm/4MGU+VYHsWgt8dOcfJrR/d 3/FA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id k15si245278lfv.10.2021.12.17.08.56.46 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 17 Dec 2021 08:56:46 -0800 (PST) Received-SPF: pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of amikan@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=amikan@ilbers.de Received: from [192.168.67.164] (mm-214-81-214-37.mgts.dynamic.pppoe.byfly.by [37.214.81.214] (may be forged)) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 1BHGugxh019333 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 17 Dec 2021 17:56:43 +0100 Subject: Re: Is it safe to remove debconf cache files in isar system To: Venkata.Pyla@toshiba-tsip.com, isar-users@googlegroups.com Cc: henning.schild@siemens.com, jan.kiszka@siemens.com, dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp, Baurzhan Ismagulov References: From: Anton Mikanovich Message-ID: <1a3ee03f-4749-859e-c6cb-7eb3e8cc11bc@ilbers.de> Date: Fri, 17 Dec 2021 19:56:37 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: ZbiaSrP3TOrH 16.12.2021 10:47, Venkata.Pyla@toshiba-tsip.com wrote: > Hi, > > 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. > > I am checking the reproducible failures as below: > $ cd isar > $ . isar-init-build-env build1 && bitbake mc:qemuamd64-buster-tgz:isar-image-base > $ . isar-init-build-env build2 && bitbake mc:qemuamd64-buster-tgz:isar-image-base > $ mkdir -p rootfs1 rootfs2 > $ tar -xzvf ./build1/tmp/deploy/images/qemuamd64/isar-image-base-debian-buster-qemuamd64.tar.gz -C ./rootfs1/ > $ tar -xzvf ./build2/tmp/deploy/images/qemuamd64/isar-image-base-debian-buster-qemuamd64.tar.gz -C ./rootfs2/ > $ rsync -nrclv ./rootfs1/ ./rootfs2/ > difference.txt > > Below is one reproducible problem I picked: > In debconf db file the contents were different after two subsequent builds, > > Part of the debconf db file where the difference is found (/var/cache/debconf/config.dat) > Build1: > Name: ucf/changeprompt > Template: ucf/changeprompt > Value: keep_current > Owners: ucf > Variables: > BASENAME = locale.nopurge > FILE = /etc/locale.nopurge > NEW = /etc/locale.nopurge.29308 > > Build2: > Name: ucf/changeprompt > Template: ucf/changeprompt > Value: keep_current > Owners: ucf > Variables: > BASENAME = locale.nopurge > FILE = /etc/locale.nopurge > 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 > > The first solution is easy, but I am worried if those package configuration files maybe required in future when the package is updating > The second solution would need more investigation at debconf package side. > > Any ideas or suggestion would be very grateful. > > Thanks, > Venkata. > Because both questions are not really Isar-related, but more Debian-related, maybe it's better to duplicate them on debian-user@lists.debian.org ? -- Anton Mikanovich Promwad Ltd. External service provider of ilbers GmbH Maria-Merian-Str. 8 85521 Ottobrunn, Germany +49 (89) 122 67 24-0 Commercial register Munich, HRB 214197 General Manager: Baurzhan Ismagulov