Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: ccasciato@21sw.us, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 11/15] python3-flit-core: upgrade 3.11.0 -> 3.12.0
Date: Tue, 27 May 2025 18:00:56 +0200	[thread overview]
Message-ID: <08003f5c-5919-49ec-9e3e-15fa1e62f8f2@gmail.com> (raw)
In-Reply-To: <22894.1748353705199489095@lists.openembedded.org>

On 5/27/25 15:48, Clayton Casciato via lists.openembedded.org wrote:
> I also found this:
>  
> "[AUH] python3-flit-core: upgrading to 3.12.0 FAILED"
>  
> https://lists.openembedded.org/g/openembedded-core/message/214061

I tried to reproduce these errors in my env[1] with all your failing
packages, but they built successfully. I also tried with only oe-core,
without anything else, and that was successful too.
The AUH failure seems to match your error, but interestingly the patch
has survived autobuilder many times... I wonder if the error is rooted
in build host environment, or maybe even in sstate cache somehow? (I did
delete tmp folder, but reused sstate cache. I build my recipes in a
Debian 12 based Docker image)

[1]:
Build Configuration:
BB_VERSION           = "2.12.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "qemuarm"
DISTRO               = "poky"
DISTRO_VERSION       = "5.2"
TUNE_FEATURES        = "arm vfp cortexa15 neon thumb callconvention-hard"
TARGET_FPU           = "hard"
meta-firefox         = "master:685ae3023b8ad6e6378e41058520327439ffe6cf"
meta-clang           = "HEAD:02e254ba1fb4937530d94a154b4c713c904c2d06"
meta-firefox-test    = "master:7ac03919ed0036da95fa3eb6643627b41d8e73eb"
meta-multimedia      
meta-networking      
meta-oe              
meta-python          = "HEAD:1d6095b73fa21062fde2b347cd61b6c5104390d9"
meta                 
meta-poky            
meta-yocto-bsp       = "HEAD:9bc47d6a4d23bff5999b69fa2b99e1b32eaa62fb"



  reply	other threads:[~2025-05-27 16:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  0:51 [OE-core] [PATCH 01/15] curl: upgrade 8.12.1 -> 8.13.0 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 02/15] ell: upgrade 0.75 -> 0.76 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 03/15] gawk: upgrade 5.3.1 -> 5.3.2 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 04/15] harfbuzz: upgrade 11.0.0 -> 11.0.1 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 05/15] hwdata: upgrade 0.393 -> 0.394 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 06/15] libsolv: upgrade 0.7.31 -> 0.7.32 wangmy
2025-04-08  8:08   ` Alexander Kanavin
2025-04-08  0:51 ` [OE-core] [PATCH 07/15] lighttpd: upgrade 1.4.78 -> 1.4.79 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 08/15] llvm: upgrade 20.1.1 -> 20.1.2 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 09/15] meson: upgrade 1.7.1 -> 1.7.2 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 10/15] python3-calver: upgrade 2025.04.01 -> 2025.04.02 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 11/15] python3-flit-core: upgrade 3.11.0 -> 3.12.0 wangmy
2025-05-19  2:37   ` Clayton Casciato
2025-05-19  2:49     ` Clayton Casciato
2025-05-27 13:48       ` Clayton Casciato
2025-05-27 16:00         ` Gyorgy Sarvari [this message]
2025-05-27 18:57           ` Clayton Casciato
2025-04-08  0:51 ` [OE-core] [PATCH 12/15] python3-lxml: upgrade 5.3.1 -> 5.3.2 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 13/15] python3-typing-extensions: upgrade 4.13.0 -> 4.13.1 wangmy
2025-04-08  0:51 ` [OE-core] [PATCH 14/15] sbc: upgrade 2.0 -> 2.1 wangmy
2025-04-08 10:21   ` Gyorgy Sarvari
2025-04-08  0:51 ` [OE-core] [PATCH 15/15] systemd: upgrade 257.4 -> 257.5 wangmy
2025-04-08 11:17 ` [OE-core] [PATCH 01/15] curl: upgrade 8.12.1 -> 8.13.0 Mathieu Dubois-Briand

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=08003f5c-5919-49ec-9e3e-15fa1e62f8f2@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=ccasciato@21sw.us \
    --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