public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Steve Langasek <steve.langasek@canonical.com>
Cc: Bastian Germann <bastiangermann@fishpost.de>,
	linux-xfs@vger.kernel.org,
	Steve Langasek <steve.langasek@ubuntu.com>
Subject: Re: [PATCH 3/4] debian: Regenerate config.guess using debhelper
Date: Mon, 22 Feb 2021 09:04:43 +1100	[thread overview]
Message-ID: <20210221220443.GO4662@dread.disaster.area> (raw)
In-Reply-To: <840CCF3D-7A20-4E35-BA9C-DEC9C05EE70A@canonical.com>

On Sat, Feb 20, 2021 at 11:16:57PM -0800, Steve Langasek wrote:
> 
> 
> On February 20, 2021 8:11:39 PM PST, Dave Chinner <david@fromorbit.com> wrote:
> >On Sat, Feb 20, 2021 at 01:16:08PM +0100, Bastian Germann wrote:
> >> This is a change introduced in 5.10.0-2ubuntu2 with the changelog:
> >> 
> >> > xfsprogs upstream has regressed config.guess, so use
> >> > dh_update_autotools_config.
> >
> >What regression?
> >
> >The xfsprogs build generates config.guess with the libtool
> >infrastructure installed on the build machine. So I'm not sure
> >how/what we've regressed here, because AFAIK we haven't changed
> >anything here recently...
> 
> 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?

FWIW, where are you getting the tarballs from? Are you downloading
the maintainer signed tarballs from here:

https://mirrors.edge.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/

Or pulling the git.kernel.org built tarball that is autogenerated
from the release tag?

> >>  	@echo "== dpkg-buildpackage: configure" 1>&2
> >>  	$(checkdir)
> >>  	AUTOHEADER=/bin/true dh_autoreconf
> >> +	dh_update_autotools_config
> >>  	$(options) $(MAKE) $(PMAKEFLAGS) include/platform_defs.h
> >
> >Why would running at tool that does a search-n-replace of built
> >config.guess files do anything when run before the build runs
> >libtoolize to copy in the config.guess file it uses? I'm a bit
> >confused by this...
> 
> Autoreconf was not copying in a newer version of config.guess from the system, because of the specific subset of autotools used by this project.

That sounds wrong. AIUI, autoreconf doesn't copy in anything.

$ man 7 dh-autoreconf
....
CAVEATS
       dh_autoreconf is mostly a superset of the
       dh_update_autotools_config debhelper command included in
       debhelper since version 9.20160115. When using the dh
       sequencer, dh_update_autotools_config is run before
       dh_autoreconf and updates the config.guess and config.sub
       files. This is required in cases where autoreconf does not
       update config.guess and config.sub itself.

So isn't the dh_update_autotools_config call in the wrong place
here?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2021-02-21 22:06 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 [this message]
2021-02-22  0:16         ` Steve Langasek
2021-02-22  2:44           ` Dave Chinner
2021-02-22 19:23             ` Eric Sandeen
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=20210221220443.GO4662@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=bastiangermann@fishpost.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=steve.langasek@canonical.com \
    --cc=steve.langasek@ubuntu.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