From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Olaf Mandel <o.mandel@menlosystems.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Cc: Marek Vasut <marex@denx.de>
Subject: Re: [bitbake-devel] [PATCH v3] fetch2/git: stop generated tarballs from leaking info
Date: Tue, 05 Apr 2022 15:29:16 +0100 [thread overview]
Message-ID: <cbe0db4fa9db0352b148eeaa7d10db6540ef5e81.camel@linuxfoundation.org> (raw)
In-Reply-To: <e5d525bf-e18a-6129-8d62-c3e33ec4b218@menlosystems.com>
On Tue, 2022-04-05 at 13:38 +0200, Olaf Mandel wrote:
> Hello,
>
> Am 28.03.2022 um 19:36 schrieb Olaf Mandel:
> > When using BB_GENERATE_MIRROR_TARBALLS="1" to generate mirror tarballs
> > of git repositories, they leaked local information: username, group and
> > time of the last fetch. Remove all these by setting fixed information:
> >
> > * uname = pokybuild (6000)
> > * gname = users (100)
>
> it was pointed out to me by Marek that instead of using pokybuild:users,
> which seems to be an artifact of the YP autobuilder, I should use the
> "canonical" combination oe:oe. But that raises the question: which
> numerical IDs should I use then?
I was happy to get a consistent value, I'm less worried about what that value is
but if we want something different I'm ok with that...
Cheers,
Richard
next prev parent reply other threads:[~2022-04-05 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 16:47 [PATCH] fetch2/git: stop generated tarballs from leaking info Olaf Mandel
2022-03-28 17:33 ` [PATCH v2] " Olaf Mandel
2022-03-28 17:36 ` [PATCH v3] " Olaf Mandel
2022-04-05 11:38 ` Olaf Mandel
2022-04-05 13:19 ` [bitbake-devel] " Alexandre Belloni
2022-04-05 14:29 ` Richard Purdie [this message]
2022-04-08 14:50 ` [PATCH] fetch2/git: canonicalize ids in generated tarballs Olaf Mandel
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=cbe0db4fa9db0352b148eeaa7d10db6540ef5e81.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=marex@denx.de \
--cc=o.mandel@menlosystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.