From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Unresolved dependencies, missing libglapi-32bit
Date: Thu, 22 Apr 2021 07:39:02 +0200 [thread overview]
Message-ID: <20210422053902.6dKPXAZta4OtWspLK5r3yY8y_CbRzSb_AQZhLhd192c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30420@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/30420#issuecomment-824553477
Comment:
From https://build.voidlinux.org/builders/i686_builder/builds/32006/steps/shell_3/logs/stdio
```
=> Registering new packages to /host/binpkgs/multilib (x86_64)
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libglapi-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libgbm-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libOSMesa-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-vulkan-radeon-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-ati-dri-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-vulkan-intel-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-intel-dri-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/mesa-nouveau-dri-32bit-21.0.3_1.x86_64.xbps', skipping!
index: failed to read props.plist metadata for `/host/binpkgs/multilib/libxatracker-32bit-21.0.3_1.x86_64.xbps', skipping!
index: added `MesaLib-devel-32bit-21.0.3_1' (x86_64).
index: added `mesa-32bit-21.0.3_1' (x86_64).
index: added `mesa-XvMC-32bit-21.0.3_1' (x86_64).
index: added `mesa-dri-32bit-21.0.3_1' (x86_64).
index: added `mesa-opencl-32bit-21.0.3_1' (x86_64).
index: added `mesa-vaapi-32bit-21.0.3_1' (x86_64).
index: added `mesa-vdpau-32bit-21.0.3_1' (x86_64).
index: added `mesa-vmwgfx-dri-32bit-21.0.3_1' (x86_64).
index: added `mesa-vulkan-overlay-layer-32bit-21.0.3_1' (x86_64).
```
Something went wrong in the builders, trying to figure it out.
next prev parent reply other threads:[~2021-04-22 5:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 5:30 [ISSUE] " linkert
2021-04-22 5:39 ` ericonr [this message]
2021-04-22 5:58 ` ericonr
2021-04-22 6:01 ` ericonr
2021-04-22 6:05 ` Obsolete package removal on x86_64 builder can race with multilib generation on i686 builder ericonr
2021-04-22 6:05 ` ericonr
2021-04-22 6:15 ` the-maldridge
2021-04-22 6:31 ` Oreo639
2021-04-22 9:53 ` linkert
2021-04-22 9:53 ` [ISSUE] [CLOSED] " linkert
2021-04-22 9:54 ` linkert
2021-04-22 10:35 ` Duncaen
2021-04-22 10:35 ` Duncaen
2021-04-22 10:52 ` Duncaen
2021-04-22 10:55 ` Duncaen
2021-04-22 17:29 ` Duncaen
2021-04-22 21:55 ` Oreo639
2021-04-22 21:58 ` Oreo639
2021-04-22 21:59 ` Oreo639
2021-04-22 22:02 ` Oreo639
2021-04-22 22:03 ` Oreo639
2021-04-22 22:03 ` Duncaen
2021-04-22 22:04 ` Oreo639
2021-04-25 16:52 ` ericonr
2021-04-25 16:52 ` [ISSUE] [CLOSED] " ericonr
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=20210422053902.6dKPXAZta4OtWspLK5r3yY8y_CbRzSb_AQZhLhd192c@z \
--to=ericonr@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).