public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Moessbauer, Felix (T CED INW-CN)" <felix.moessbauer@siemens.com>
Cc: "Bovensiepen,
	Daniel (bovi) (T CED INW-CN)" <daniel.bovensiepen@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan (T CED)" <jan.kiszka@siemens.com>,
	"venkata.pyla@toshiba-tsip.com" <venkata.pyla@toshiba-tsip.com>
Subject: Re: [PATCH 04/11] remove non-portable ldconfig aux-cache
Date: Wed, 11 Jan 2023 13:52:00 +0100	[thread overview]
Message-ID: <20230111135200.1d349074@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <f08af585d3f1693dce6b192493dca4502be77601.camel@siemens.com>

Am Wed, 11 Jan 2023 09:31:00 +0100
schrieb "Moessbauer, Felix (T CED INW-CN)"
<felix.moessbauer@siemens.com>:

> On Wed, 2023-01-11 at 09:19 +0100, Henning Schild wrote:
> > Am Wed, 11 Jan 2023 04:11:33 +0000
> > schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:
> >  
> > > This patch removes the ldconfig aux-cache from the final rootfs.
> > > The cache is both not portable across file systems, as well as non
> > > reproducible.
> > >
> > > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > > ---
> > >  meta/classes/rootfs.bbclass | 7 +++++++
> > >  1 file changed, 7 insertions(+)
> > >
> > > diff --git a/meta/classes/rootfs.bbclass
> > > b/meta/classes/rootfs.bbclass
> > > index 325e7ae..226fa8b 100644
> > > --- a/meta/classes/rootfs.bbclass
> > > +++ b/meta/classes/rootfs.bbclass
> > > @@ -258,6 +258,13 @@ rootfs_postprocess_clean_pycache() {
> > >      sudo find ${ROOTFSDIR}/usr -type d -name '__pycache__'
> > > -delete -print }
> > >
> > > +ROOTFS_POSTPROCESS_COMMAND +=
> > > "rootfs_postprocess_clean_ldconfig_cache"
> > > +rootfs_postprocess_clean_ldconfig_cache() {
> > > +    # the ldconfig aux-cache is not portable and breaks
> > > reproducability
> > > +    # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845034#49
> > > +    sudo rm -f ${ROOTFSDIR}/var/cache/ldconfig/aux-cache
> > > +}  
> >
> > Should this not be enabled by default?  
> 
> Yes, this is always enabled.

A right. I somehow missed that first line where it gets enabled.

Henning

> But it did not really fit into any other postprocess command, so I
> decided to add a dedicated one.
> 
> Felix
> 
> >
> > Henning
> >  
> > >  ROOTFS_POSTPROCESS_COMMAND +=
> > > "${@bb.utils.contains('ROOTFS_FEATURES', 'generate-manifest',
> > > 'rootfs_generate_manifest', '', d)}" rootfs_generate_manifest () {
> > > mkdir -p ${ROOTFS_MANIFEST_DEPLOY_DIR}  
> >  
> 


  reply	other threads:[~2023-01-11 12:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  4:11 [PATCH 00/11] Make rootfs build reproducible Felix Moessbauer
2023-01-11  4:11 ` [PATCH 01/11] fix rebuild of rootfs_finalize task Felix Moessbauer
2023-01-11  4:11 ` [PATCH 02/11] image.bbclass: fix non-reproducible file time-stamps inside rootfs Felix Moessbauer
2023-01-11  4:11 ` [PATCH 03/11] rootfs postprocess: clean python cache Felix Moessbauer
2023-01-11  8:06   ` Henning Schild
2023-01-11  8:23     ` Moessbauer, Felix
2023-01-11 12:47       ` Henning Schild
2023-01-11 13:18         ` Moessbauer, Felix
2023-01-11 13:23           ` Jan Kiszka
2023-01-11  4:11 ` [PATCH 04/11] remove non-portable ldconfig aux-cache Felix Moessbauer
2023-01-11  8:19   ` Henning Schild
2023-01-11  8:31     ` Moessbauer, Felix
2023-01-11 12:52       ` Henning Schild [this message]
2023-01-11  4:11 ` [PATCH 05/11] generate deterministic clear-text password hash Felix Moessbauer
2023-01-11  8:21   ` Henning Schild
2023-01-11  4:11 ` [PATCH 06/11] update debian initramfs in deterministic mode Felix Moessbauer
2023-01-11  8:23   ` Henning Schild
2023-01-11  8:39     ` Moessbauer, Felix
2023-01-11 12:55       ` Henning Schild
2023-01-11  4:11 ` [PATCH 07/11] create custom " Felix Moessbauer
2023-01-11  4:11 ` [PATCH 08/11] make deb_add_changelog idempotent Felix Moessbauer
2023-01-11  4:11 ` [PATCH 09/11] deb_add_changelog: set timestamp to valid epoch Felix Moessbauer
2023-01-11  4:11 ` [PATCH 10/11] deb_add_changelog: use SOURCE_DATE_EPOCH Felix Moessbauer
2023-01-11  8:49   ` Henning Schild
2023-01-11  9:06     ` Moessbauer, Felix
2023-01-11  4:11 ` [PATCH 11/11] make custom linux-image bit-by-bit reproducible Felix Moessbauer
2023-01-11  6:51 ` [PATCH 00/11] Make rootfs build reproducible Jan Kiszka
2023-01-11  9:04 ` Venkata.Pyla

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=20230111135200.1d349074@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=daniel.bovensiepen@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=venkata.pyla@toshiba-tsip.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