From: auh@moto-timo.dev
To: openembedded-devel@lists.openembedded.org
Subject: [AUH] python3-cvxopt: upgrading to 1.3.1 FAILED
Date: Mon, 31 Jul 2023 05:08:54 +0000 (UTC) [thread overview]
Message-ID: <20230731050854.D0126C04A94@smtp.lore.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cvxopt* to *1.3.1* has Failed(other errors).
Detailed error information:
'MACHINE=qemux86-64 bitbake python3-cvxopt' failed
Loading cache...done.
Loaded 12624 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Summary: There were 2 ERROR messages, returning a non-zero exit code.
ERROR: Nothing PROVIDES 'libgfortran' (but /home/auh/Projects/meta-openembedded/meta-oe/recipes-devtools/lapack/lapack_3.10.1.bb DEPENDS on or otherwise requires it)
libgfortran was skipped: libgfortran needs fortran support to be enabled in the compiler
ERROR: Required build target 'python3-cvxopt' has no buildable providers.
Missing or unbuildable dependency chain was: ['python3-cvxopt', 'lapack', 'libgfortran']
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-31 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 5:08 auh [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-05 7:38 [AUH] python3-cvxopt: upgrading to 1.3.1 FAILED auh
2023-07-12 5:30 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=20230731050854.D0126C04A94@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox