From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: xbps-src: base-chroot-v2 (reduce artifacts/deps)
Date: Fri, 03 Jan 2020 13:07:03 +0100 [thread overview]
Message-ID: <20200103120703.RYnqr6msex13jMBAVy7hrKk2ppsz88MQismyNp7bjj0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17969@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/17969#issuecomment-570555104
Comment:
It seems `binpkgs/multilib` is missing from the repo paths scanned for `x86_64`:
```
$ ./xbps-src -N -t pkg gcc-multilib
=> xbps-src: updating repositories for host (x86_64)...
=> xbps-src: cleaning up / masterdir...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> gcc-multilib-9.2.0_1: building for x86_64...
[host] perl-5.30.1_1: found (/host/binpkgs)
[host] flex-2.6.4_3: found (/host/binpkgs)
[host] zip-3.0_5: found (/host/binpkgs)
[host] unzip-6.0_13: found (/host/binpkgs)
=> ERROR: gcc-multilib-9.2.0_1: target dependency 'glibc-32bit' does not exist!
```
```
ls -l /work/void/binpkgs/multilib/glibc*
-rw-r--r-- 1 jbu jbu 6997544 2. Jan 23:22 glibc-32bit-2.30_1.x86_64.xbps
-rw-r--r-- 1 jbu jbu 512 2. Jan 23:23 glibc-32bit-2.30_1.x86_64.xbps.sig
-rw-r--r-- 1 jbu jbu 1269892 2. Jan 23:21 glibc-devel-32bit-2.30_1.x86_64.xbps
-rw-r--r-- 1 jbu jbu 512 2. Jan 23:23 glibc-devel-32bit-2.30_1.x86_64.xbps.sig
```
next prev parent reply other threads:[~2020-01-03 12:07 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 10:37 [PR PATCH] " voidlinux-github
2020-01-01 10:41 ` voidlinux-github
2020-01-01 10:46 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-01 10:50 ` voidlinux-github
2020-01-01 10:59 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-01 11:05 ` voidlinux-github
2020-01-01 11:11 ` voidlinux-github
2020-01-01 11:22 ` voidlinux-github
2020-01-01 11:25 ` voidlinux-github
2020-01-01 11:29 ` voidlinux-github
2020-01-01 11:40 ` voidlinux-github
2020-01-01 11:42 ` voidlinux-github
2020-01-01 11:48 ` voidlinux-github
2020-01-01 11:53 ` voidlinux-github
2020-01-01 11:56 ` voidlinux-github
2020-01-01 11:58 ` voidlinux-github
2020-01-01 12:02 ` voidlinux-github
2020-01-01 12:07 ` voidlinux-github
2020-01-01 12:12 ` voidlinux-github
2020-01-01 12:13 ` voidlinux-github
2020-01-01 12:14 ` voidlinux-github
2020-01-01 12:16 ` voidlinux-github
2020-01-01 12:18 ` voidlinux-github
2020-01-01 12:19 ` voidlinux-github
2020-01-01 12:19 ` voidlinux-github
2020-01-01 12:22 ` voidlinux-github
2020-01-01 12:25 ` voidlinux-github
2020-01-01 12:28 ` voidlinux-github
2020-01-01 12:30 ` voidlinux-github
2020-01-01 12:36 ` voidlinux-github
2020-01-01 21:14 ` voidlinux-github
2020-01-01 21:32 ` voidlinux-github
2020-01-01 21:32 ` voidlinux-github
2020-01-01 21:33 ` voidlinux-github
2020-01-01 21:34 ` voidlinux-github
2020-01-01 21:35 ` voidlinux-github
2020-01-01 21:35 ` voidlinux-github
2020-01-01 21:37 ` voidlinux-github
2020-01-01 21:37 ` voidlinux-github
2020-01-01 21:38 ` voidlinux-github
2020-01-01 23:29 ` voidlinux-github
2020-01-01 23:32 ` voidlinux-github
2020-01-02 11:18 ` voidlinux-github
2020-01-02 17:48 ` voidlinux-github
2020-01-02 20:32 ` voidlinux-github
2020-01-02 20:34 ` voidlinux-github
2020-01-02 20:37 ` voidlinux-github
2020-01-02 22:20 ` voidlinux-github
2020-01-02 22:29 ` voidlinux-github
2020-01-03 1:18 ` voidlinux-github
2020-01-03 1:51 ` voidlinux-github
2020-01-03 1:53 ` voidlinux-github
2020-01-03 7:40 ` voidlinux-github
2020-01-03 8:24 ` voidlinux-github
2020-01-03 9:29 ` voidlinux-github
2020-01-03 11:51 ` voidlinux-github
2020-01-03 12:07 ` voidlinux-github [this message]
2020-01-03 12:58 ` voidlinux-github
2020-01-03 13:12 ` voidlinux-github
2020-01-03 13:16 ` voidlinux-github
2020-01-03 13:21 ` voidlinux-github
2020-01-03 13:24 ` voidlinux-github
2020-01-03 13:28 ` voidlinux-github
2020-01-03 13:29 ` voidlinux-github
2020-01-03 13:30 ` voidlinux-github
2020-01-03 13:31 ` voidlinux-github
2020-01-03 13:32 ` voidlinux-github
2020-01-03 13:34 ` voidlinux-github
2020-01-03 13:35 ` voidlinux-github
2020-01-03 13:36 ` voidlinux-github
2020-01-03 13:38 ` voidlinux-github
2020-01-03 15:26 ` voidlinux-github
2020-01-04 8:02 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-04 8:31 ` voidlinux-github
2020-01-04 10:19 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-04 10:46 ` voidlinux-github
2020-01-04 10:54 ` voidlinux-github
2020-01-04 11:12 ` voidlinux-github
2020-01-04 11:16 ` voidlinux-github
2020-01-04 11:19 ` voidlinux-github
2020-01-04 11:20 ` voidlinux-github
2020-01-04 11:25 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-04 11:32 ` voidlinux-github
2020-01-04 11:39 ` voidlinux-github
2020-01-04 11:46 ` voidlinux-github
2020-01-04 12:03 ` voidlinux-github
2020-01-04 12:29 ` voidlinux-github
2020-01-05 6:49 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-05 7:21 ` voidlinux-github
2020-01-05 7:25 ` voidlinux-github
2020-01-05 7:32 ` voidlinux-github
2020-01-05 7:54 ` voidlinux-github
2020-01-05 8:44 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-05 8:53 ` voidlinux-github
2020-01-05 9:12 ` voidlinux-github
2020-01-05 9:25 ` voidlinux-github
2020-01-05 9:36 ` voidlinux-github
2020-01-05 9:37 ` voidlinux-github
2020-01-05 9:44 ` [PR PATCH] [Merged]: " voidlinux-github
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=20200103120703.RYnqr6msex13jMBAVy7hrKk2ppsz88MQismyNp7bjj0@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).