From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] sanity: Add check for tar older than 1.28
Date: Thu, 21 Nov 2019 17:50:18 +0200 [thread overview]
Message-ID: <20191121155018.GB28013@localhost> (raw)
In-Reply-To: <20191121150207.3657-3-richard.purdie@linuxfoundation.org>
On Thu, Nov 21, 2019 at 03:02:07PM +0000, Richard Purdie wrote:
> Older versions break opkg-build when reproducible builds are enabled.
> Rather than trying to be selective based on which features are enabled,
> lets just make this a minimum version.
>...
> + if LooseVersion(version) < LooseVersion("1.28"):
> + return "Your version of tar is older than 1.28 and does not have the support needed to enable reproducible builds. Please install a newer version of tar.\n"
>...
How does "Please install a newer version of tar" work in practice
on a supported host distribution like CentOS 7 ?
As user I would expect such things to just work when using
a distribution that is documented as supported.
cu
Adrian
next prev parent reply other threads:[~2019-11-21 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 15:02 [PATCH 1/3] opkg: Add upstream fixes Richard Purdie
2019-11-21 15:02 ` [PATCH 2/3] opkg-utils: Fix silent empty/broken opkg package creation Richard Purdie
2019-11-21 15:02 ` [PATCH 3/3] sanity: Add check for tar older than 1.28 Richard Purdie
2019-11-21 15:50 ` Adrian Bunk [this message]
2019-11-21 16:54 ` Richard Purdie
2019-11-21 17:02 ` Alexander Kanavin
2019-11-21 17:09 ` Adrian Bunk
2019-11-21 18:09 ` Richard Purdie
2019-11-21 19:14 ` Mark Hatle
2019-11-21 19:33 ` Richard Purdie
2019-11-22 0:27 ` [PATCH 1/3] opkg: Add upstream fixes Khem Raj
2019-11-22 8:58 ` Richard Purdie
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=20191121155018.GB28013@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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