From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>,
Steve Langasek <steve.langasek@canonical.com>
Cc: Bastian Germann <bastiangermann@fishpost.de>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/4] debian: Regenerate config.guess using debhelper
Date: Mon, 22 Feb 2021 13:23:12 -0600 [thread overview]
Message-ID: <957b9913-bcdb-b64c-4c33-6493a91b3838@sandeen.net> (raw)
In-Reply-To: <20210222024425.GP4662@dread.disaster.area>
On 2/21/21 8:44 PM, Dave Chinner wrote:
> On Sun, Feb 21, 2021 at 04:16:39PM -0800, Steve Langasek wrote:
>> On Mon, Feb 22, 2021 at 09:04:43AM +1100, Dave Chinner wrote:
>>
>>>> This upstream release ended up with an older version of config.guess in
>>>> the tarball. Specifically, it was too old to recognize RISC-V as an
>>>> architecture.
>>
>>> So was the RISC-V architecture added to the ubuntu build between the
>>> uploads of the previous version of xfsprogs and xfsprogs-5.10.0? Or
>>> is this an actual regression where the maintainer signed tarball had
>>> RISC-V support in it and now it doesn't?
>>
>> This is a regression. The previous tarball (5.6.0) had a newer config.guess
>> that recognized RISC-V, the newer one (5.10.0) had an older config.guess.
>
> Ok.
>
> Eric, did you change the machine you did the release build from?
I don't recall doing so, but I must have. I guess I remember this coming up
a while ago and maybe I failed to change process in a sticky way. :/
But - if my local toolchain can cause a regression in a major distro, it seems
like this patch to regenerate is the obvious path forward, to control
the distro-specific build, and not be subject to my personal toolchain whims.
Is that not best practice? (I honestly don't know.)
-Eric
next prev parent reply other threads:[~2021-02-22 19:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 12:16 [PATCH 0/4] debian: Integrate Debian/Ubuntu changes Bastian Germann
2021-02-20 12:16 ` [PATCH 1/4] debian: Drop trying to create upstream distribution Bastian Germann
2021-02-21 4:01 ` Dave Chinner
2021-02-23 3:07 ` Darrick J. Wong
2021-02-20 12:16 ` [PATCH 2/4] debian: Enable CET on amd64 Bastian Germann
2021-02-21 3:59 ` Dave Chinner
2021-02-21 4:02 ` NACK " Dimitri John Ledkov
2021-02-21 4:28 ` Dave Chinner
2021-02-21 4:32 ` Dimitri John Ledkov
2021-02-21 21:37 ` Dave Chinner
2021-02-20 12:16 ` [PATCH 3/4] debian: Regenerate config.guess using debhelper Bastian Germann
2021-02-21 4:11 ` Dave Chinner
2021-02-21 7:16 ` Steve Langasek
2021-02-21 22:04 ` Dave Chinner
2021-02-22 0:16 ` Steve Langasek
2021-02-22 2:44 ` Dave Chinner
2021-02-22 19:23 ` Eric Sandeen [this message]
2021-02-23 20:51 ` Dave Chinner
2021-02-20 12:16 ` [PATCH 4/4] debian: Build-depend on libinih-dev with udeb package Bastian Germann
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=957b9913-bcdb-b64c-4c33-6493a91b3838@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bastiangermann@fishpost.de \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=steve.langasek@canonical.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.