public inbox for dwarves@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: Domenico Andreoli <domenico.andreoli@linux.com>, dwarves@vger.kernel.org
Subject: Re: Is 1.30 released?
Date: Wed, 16 Apr 2025 16:34:45 -0300	[thread overview]
Message-ID: <aAAGVRUbj6_4YEWr@x1> (raw)
In-Reply-To: <aae20053-ce1e-4fa3-8c73-1f1a702d123c@oracle.com>

On Wed, Apr 16, 2025 at 08:51:59AM +0100, Alan Maguire wrote:
> On 15/04/2025 10:26, Domenico Andreoli wrote:
> > Hello,
> > 
> > I see from [0] that v1.30 has been tagged but I missed the announcement.
> > Additionally [1] does not show an updated (& signed) tarball.
> > 
> > Is everything in order here?
> >
> 
> Arnaldo got some late reports of build failures when we were finalizing
> the release; we're awaiting more data to determine what's happening.

You mean this report:

https://github.com/acmel/dwarves/issues/63

It is not something new, they say they started seeing the problem when
switching from 1.25 to 1.26, so not related to what is in 1.30.

And I _think_ this is just a correlation, the cause seems to be a change
in how they link software, they have LTO enabled, etc.

I did some analysis and updated that github issue.

Or are you talking about some other case?

If this is the case I think we can go ahead with releasing 1.30.

- Arnaldo

  reply	other threads:[~2025-04-16 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  9:26 Is 1.30 released? Domenico Andreoli
2025-04-16  7:51 ` Alan Maguire
2025-04-16 19:34   ` Arnaldo Carvalho de Melo [this message]
2025-04-17 15:38     ` Alan Maguire

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=aAAGVRUbj6_4YEWr@x1 \
    --to=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=domenico.andreoli@linux.com \
    --cc=dwarves@vger.kernel.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