From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Manual.md: Add list of packages that should be rebuilt after bootstrap.
Date: Fri, 15 May 2020 23:06:28 +0200 [thread overview]
Message-ID: <20200515210628.NunJdeo-GhV1aWHBRU4qfnXfB02iSSefTjEZmJWAl7s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21232@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/21232#issuecomment-629484271
Comment:
The easiest and safest way actually is to rebuild the entire chroot. This ensures that nothing is missed which could potentially go wrong with packages being built with different options in case the chroot is not yet ready.
That is, after `./xbps-src bootstrap` is done and you have a bootstrapped chroot ready in your `masterdir`, remove all packages that were created (I think `rm -rf masterdir/binpkgs/*` or whererever you defined the masterdir with the `-m` option) and build `base-chroot` with your bootstrapped environment:
`./xbps-src -N pkg base-chroot`.
After this is done, you can then `./xbps-src binary-bootstrap` and everything should work as expected.
Also only after this step you should try to cross build `base-chroot` for other architectures like:
`./xbps-src -a i686 -N pkg base-chroot`.
next prev parent reply other threads:[~2020-05-15 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 0:35 [ISSUE] " fosslinux
2020-05-15 21:06 ` pullmoll [this message]
2020-09-19 23:39 ` pullmoll
2020-09-19 23:39 ` [ISSUE] [CLOSED] " pullmoll
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=20200515210628.NunJdeo-GhV1aWHBRU4qfnXfB02iSSefTjEZmJWAl7s@z \
--to=pullmoll@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).