From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] python3: update to 3.10.0
Date: Tue, 28 Sep 2021 19:42:51 +0200 [thread overview]
Message-ID: <20210928174251.ebmZI3ilp1RGVHLXJ3Uf3AchPQI4r_bvV89-VnhQrm8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33097@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/33097#issuecomment-929328525
Comment:
Except for the expected failures, builds on `x86_64-musl`, `aarch64` and `armv7l` have completed without issue. This means `caribou` is the only package that will not native compile on `x86_64*`. I am finished `armv6` and @zdykstra is working on `aarch64-musl`, then we'll move on the `i686` and `arm*musl`.
On `armv6l`, `PackageKit` fails with the following error (NB: this error occurs on master and is not related to the Python update):
```sh
=> PackageKit-1.2.2_2: running do_build ...
ninja: Entering directory `build'
[1/152] Generating org.freedesktop.packagekit.policy_policy_merge with a custom command
FAILED: policy/org.freedesktop.packagekit.policy
/usr/bin/meson --internal msgfmthelper ../policy/org.freedesktop.packagekit.policy.in policy/org.freedesktop.packagekit.policy xml /builddir/PackageKit-PACKAGEKIT_1_2_2/po
msgfmt: cannot locate ITS rules for ../policy/org.freedesktop.packagekit.policy.in
ninja: build stopped: subcommand failed.
=> ERROR: PackageKit-1.2.2_2: do_build: '${make_cmd} -C ${meson_builddir} ${makejobs} ${make_build_args} ${make_build_target}' exited with 1
=> ERROR: in do_build() at common/build-style/meson.sh:132
```
[Edit: update PackageKit error for armv6l with serial build.]
next prev parent reply other threads:[~2021-09-28 17:42 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 3:31 [PR PATCH] " ahesford
2021-09-25 14:46 ` [PR PATCH] [Updated] " ahesford
2021-09-25 19:35 ` ahesford
2021-09-25 20:30 ` ahesford
2021-09-26 1:50 ` ahesford
2021-09-26 3:47 ` ahesford
2021-09-26 14:04 ` ahesford
2021-09-26 18:58 ` ahesford
2021-09-26 19:54 ` ahesford
2021-09-26 21:28 ` ahesford
2021-09-26 21:31 ` ahesford
2021-09-26 21:47 ` ahesford
2021-09-26 22:19 ` ahesford
2021-09-26 22:19 ` [PR PATCH] [Updated] " ahesford
2021-09-27 1:23 ` ahesford
2021-09-27 1:33 ` ahesford
2021-09-27 1:59 ` ahesford
2021-09-27 2:03 ` ahesford
2021-09-27 2:03 ` ahesford
2021-09-27 2:11 ` ahesford
2021-09-27 2:31 ` ahesford
2021-09-27 2:35 ` [PR PATCH] [Updated] " ahesford
2021-09-27 10:56 ` leahneukirchen
2021-09-27 10:57 ` leahneukirchen
2021-09-27 12:21 ` [PR PATCH] [Updated] " ahesford
2021-09-27 12:23 ` ahesford
2021-09-27 12:29 ` ahesford
2021-09-27 12:29 ` ahesford
2021-09-27 13:28 ` ahesford
2021-09-27 14:01 ` ericonr
2021-09-27 15:14 ` [PR PATCH] [Updated] " ahesford
2021-09-27 15:40 ` ahesford
2021-09-27 15:50 ` ahesford
2021-09-27 16:15 ` ahesford
2021-09-27 22:02 ` ahesford
2021-09-27 22:08 ` paper42
2021-09-27 23:51 ` ahesford
2021-09-27 23:52 ` ahesford
2021-09-27 23:52 ` ahesford
2021-09-28 0:24 ` [PR PATCH] [Updated] " ahesford
2021-09-28 15:00 ` ahesford
2021-09-28 15:16 ` ahesford
2021-09-28 17:42 ` ahesford [this message]
2021-09-28 17:47 ` [PR PATCH] [Updated] " ahesford
2021-09-28 18:04 ` ahesford
2021-09-28 18:06 ` ahesford
2021-09-28 18:06 ` ahesford
2021-09-28 18:58 ` [PR PATCH] [Updated] " ahesford
2021-09-29 14:34 ` ahesford
2021-09-29 14:44 ` ahesford
2021-09-29 14:57 ` ahesford
2021-09-29 15:28 ` ahesford
2021-09-30 0:52 ` ahesford
2021-09-30 1:01 ` ahesford
2021-09-30 18:10 ` [PR REVIEW] " yopito
2021-10-04 2:38 ` [PR PATCH] [Updated] " ahesford
2021-10-05 17:57 ` ahesford
2021-10-06 0:57 ` ahesford
2021-10-06 0:57 ` ahesford
2021-10-08 13:54 ` [PR PATCH] [Updated] " ahesford
2021-10-09 0:40 ` ahesford
2021-10-09 0:48 ` ahesford
2021-10-09 1:44 ` ahesford
2021-10-09 12:13 ` ahesford
2021-10-09 12:13 ` [PR PATCH] [Closed]: " ahesford
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=20210928174251.ebmZI3ilp1RGVHLXJ3Uf3AchPQI4r_bvV89-VnhQrm8@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).