From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `./xbps-src bootstrap' fails
Date: Fri, 16 Oct 2020 02:20:15 +0200 [thread overview]
Message-ID: <20201016002015.F0Q93rX60ovmznj20CO69sSTpVIAVmt0_TB-duW01X4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25604@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/25604#issuecomment-709349377
Comment:
> Wonder if this is still relevant in light of your comment.
ahesford said:
> When bootstrapping from source, it takes a few iterations to remove host artifacts from the masterdir.
Yes, it's still relevant, a few iterations includes *stage0*, *stage1*, *stage2*, and final masterdir
> Could you please provide a sequence of commands to achieve this?
```sh
$ # make sure we start from nothing
$ rm -rf /path/to/hostdir /path/to/masterdir
$ # build stage0
$ ./xbps-src -N -H /path/to/hostdir -m /path/to/masterdir bootstrap
$ # L165: use the resulting stage 0 container to rebuild all `bootstrap` packages again
$ rm -rf /path/to/hostdir/binpkgs
$ ./xbps-src -N -H /path/to/hostdir -m /path/to/masterdir pkg base-chroot
$ # L166: then use `binary-bootstrap` (stage 1)
$ rm -rf /path/to/masterdir
$ ./xbps-src -N -H /path/to/hostdir -m /path/to/masterdir binary-bootstrap
$ # L166: and rebuild the `bootstrap` packages once more
$ rm -rf /path/to/hostdir/binpkgs
$ ./xbps-src -N -H /path/to/hostdir -m /path/to/masterdir pkg base-chroot
$ # L167: then use `binary-bootstrap` again
$ rm -rf /path/to/masterdir
$ ./xbps-src -N -H /path/to/hostdir -m /path/to/masterdir binary-bootstrap
```
next prev parent reply other threads:[~2020-10-16 0:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 18:27 [ISSUE] " ev-ermakov
2020-10-15 0:14 ` ahesford
2020-10-15 0:25 ` sgn
2020-10-15 0:26 ` sgn
2020-10-15 1:50 ` ev-ermakov
2020-10-15 14:06 ` sgn
2020-10-15 23:00 ` travankor
2020-10-16 0:20 ` sgn [this message]
2020-10-16 13:26 ` ev-ermakov
2020-10-16 13:44 ` ev-ermakov
2020-11-01 11:09 ` sgn
2020-12-11 1:17 ` [ISSUE] [CLOSED] " sgn
2021-02-12 16:32 ` RossComputerGuy
2021-02-12 16:40 ` RossComputerGuy
2021-02-12 17:21 ` Duncaen
2021-02-12 17:24 ` RossComputerGuy
2021-02-12 17:45 ` Duncaen
2021-02-12 17:47 ` RossComputerGuy
2021-02-12 17:57 ` RossComputerGuy
2021-02-12 17:57 ` RossComputerGuy
2021-02-12 18:03 ` Duncaen
2021-02-12 18:05 ` RossComputerGuy
2021-02-12 20:37 ` RossComputerGuy
2021-02-12 21:10 ` RossComputerGuy
2021-02-12 21:25 ` Duncaen
2021-02-12 21:28 ` RossComputerGuy
2021-02-12 21:29 ` Duncaen
2021-02-12 21:58 ` RossComputerGuy
2021-02-12 22:01 ` Duncaen
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=20201016002015.F0Q93rX60ovmznj20CO69sSTpVIAVmt0_TB-duW01X4@z \
--to=sgn@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).