public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [AUH] Upgrade status: 2024-09-01
Date: Sun, 01 Sep 2024 23:44:37 +0100	[thread overview]
Message-ID: <4b6689079e150ffe0f015eae0c4f83d814898eb6.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj9fAgYHeJd2bpbR0LEG2cRg-tRf9Sp9kpLXK_6rbZa2dw@mail.gmail.com>

On Sun, 2024-09-01 at 21:21 +0200, Alexander Kanavin wrote:
> This AUH run was thwarted by a botched libtool update - it's one of
> those notorious corner cases that AUH hits occasionally. First,
> libtool update failed thusly:
> https://lists.openembedded.org/g/openembedded-core/topic/auh/108206634
> 
> (if I'm reading this right, libtool-native got upgraded first, but
> the
> outcome was a non-functional libtool-native for the purpose of tasks
> that 'devtool upgrade' needs to run)
> 
> Then, this somehow damaged the build dir so that no further builds in
> it could happen, but AUH cannot tell when that happens and carries on
> with the list of things to update:
> https://lists.openembedded.org/g/openembedded-core/topic/auh/108206638
> 
> libtool releases have historically been rare, and RP has issued an
> update for this one already. If new libtool releases continue to
> subvert AUH, we can probably mark it as needing manual updates.

There is a patch specific to libtool-cross and maybe some others but
not libtool-native and that needed to be rebased (fixinstall.patch). I
suspect that is what caused AUH the issues :/.

Cheers,

Richard


      reply	other threads:[~2024-09-01 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01  6:40 [AUH] Upgrade status: 2024-09-01 auh
2024-09-01 19:21 ` [OE-core] " Alexander Kanavin
2024-09-01 22:44   ` Richard Purdie [this message]

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=4b6689079e150ffe0f015eae0c4f83d814898eb6.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.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