From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] xwinwrap-0.9: update checksum
Date: Sat, 01 Oct 2022 12:58:57 +0200 [thread overview]
Message-ID: <20221001105857.ARdSV5qCah7XUxdAE-okMJwX9qVRtiW_nWNyBdgXuVM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39575@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
New review comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/39575#discussion_r985083246
Comment:
Try removing grep from build dependencies, zap, binary-bootstrap and build again. You can not currently add grep to build dependencies because if you do, it replaces chroot-grep from base-chroot and gets removed when the package is finished building. This breaks your chroot and you start having issues like this which can be solved by breaking it in more places.
next prev parent reply other threads:[~2022-10-01 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 9:25 [PR PATCH] " ajtcode71
2022-10-01 9:29 ` [PR REVIEW] " classabbyamp
2022-10-01 9:29 ` classabbyamp
2022-10-01 9:29 ` classabbyamp
2022-10-01 10:16 ` [PR PATCH] [Updated] " ajtcode71
2022-10-01 10:21 ` [PR REVIEW] " ajtcode71
2022-10-01 10:27 ` [PR PATCH] [Updated] " ajtcode71
2022-10-01 10:31 ` ajtcode71
2022-10-01 10:34 ` [PR REVIEW] " paper42
2022-10-01 10:37 ` [PR PATCH] [Updated] " ajtcode71
2022-10-01 10:39 ` ajtcode71
2022-10-01 10:58 ` paper42 [this message]
2022-10-01 21:02 ` ajtcode71
2022-10-01 21:03 ` ajtcode71
2022-10-01 21:05 ` [PR REVIEW] " ajtcode71
2022-10-01 21:14 ` [PR PATCH] [Merged]: " classabbyamp
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=20221001105857.ARdSV5qCah7XUxdAE-okMJwX9qVRtiW_nWNyBdgXuVM@z \
--to=paper42@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).