From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dolphin: add missing build dependency
Date: Sat, 29 Feb 2020 19:48:43 +0100 [thread overview]
Message-ID: <20200229184843.C0O6VvPAQLUJUbQR72pJMm9uQJ8LZfAi5IpWnfGPeq0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19587@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/19587#issuecomment-592981186
Comment:
kparts-devel depends on them, so they should be installed automatically. Is it reproducible? If so, could you apply following to void-packages and attach log of build?
``` diff
diff --git common/xbps-src/shutils/build_dependencies.sh common/xbps-src/shutils/build_dependencies.sh
index b5b6161601..d7233cd38e 100644
--- common/xbps-src/shutils/build_dependencies.sh
+++ common/xbps-src/shutils/build_dependencies.sh
@@ -72,7 +72,7 @@ install_pkg_from_repos() {
cmd=$XBPS_INSTALL_CMD
[[ $cross ]] && cmd=$XBPS_INSTALL_XCMD
- $cmd -Ay "$@" >$tmplogf 2>&1
+ $cmd -Ayd "$@" # >$tmplogf 2>&1
rval=$?
case "$rval" in
```
next prev parent reply other threads:[~2020-02-29 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19587@inbox.vuxu.org>
2020-02-28 7:59 ` Hoshpak
2020-02-28 10:43 ` toluschr
2020-02-28 10:44 ` toluschr
2020-02-29 18:48 ` Chocimier [this message]
2020-02-29 20:26 ` toluschr
2020-02-29 20:26 ` [PR PATCH] [Closed]: " toluschr
2020-04-04 18:23 ` toluschr
2020-04-04 18:23 ` toluschr
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=20200229184843.C0O6VvPAQLUJUbQR72pJMm9uQJ8LZfAi5IpWnfGPeq0@z \
--to=chocimier@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).