From: auh@moto-timo.dev
To: openembedded-devel@lists.openembedded.org
Subject: [AUH] python3-pybind11: upgrading to 2687. FAILED
Date: Wed, 12 Jul 2023 05:31:30 +0000 (UTC) [thread overview]
Message-ID: <20230712053130.63F64EB64D9@smtp.lore.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3590 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pybind11* to *2687.* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-pybind11 -V 2687. -S 0c395cfe1fb6cabbaa429a96d20039861fc71524
NOTE: Starting bitbake server...
Loading cache...done.
Loaded 12791 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
Build Configuration (mc:default):
BB_VERSION = "2.4.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.2"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "master:a43fa36614977745fcbd6441d1c3c20321a8201d"
meta-oe
meta-python
meta-perl = "tmp-auh-upgrades:812973bf8c6e72c2944deb4e83269cc57b5b5440"
workspace = "<unknown>:<unknown>"
Build Configuration (mc:qemux86-musl):
BB_VERSION = "2.4.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "i686-poky-linux-musl"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "4.2"
TUNE_FEATURES = "m32 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "master:a43fa36614977745fcbd6441d1c3c20321a8201d"
meta-oe
meta-python
meta-perl = "tmp-auh-upgrades:812973bf8c6e72c2944deb4e83269cc57b5b5440"
workspace = "<unknown>:<unknown>"
Build Configuration (mc:qemuarm64):
BB_VERSION = "2.4.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "qemuarm64"
DISTRO = "poky"
DISTRO_VERSION = "4.2"
TUNE_FEATURES = "aarch64 armv8a crc cortexa57"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "master:a43fa36614977745fcbd6441d1c3c20321a8201d"
meta-oe
meta-python
meta-perl = "tmp-auh-upgrades:812973bf8c6e72c2944deb4e83269cc57b5b5440"
workspace = "<unknown>:<unknown>"
Initialising tasks...done.
Sstate summary: Wanted 10 Local 0 Mirrors 9 Missed 1 Current 10 (90% match, 95% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
ERROR: Revision 0c395cfe1fb6cabbaa429a96d20039861fc71524 was found on multiple branches:
Please provide the correct branch in the devtool command with "--srcbranch" or "-B" option.
Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
next reply other threads:[~2023-07-12 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 5:31 auh [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-31 5:09 [AUH] python3-pybind11: upgrading to 2687. FAILED auh
2023-08-05 7:39 auh
2023-11-04 1:38 auh
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=20230712053130.63F64EB64D9@smtp.lore.kernel.org \
--to=auh@moto-timo.dev \
--cc=openembedded-devel@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 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.