From: RicArch97 <RicArch97@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: gamemode-1.6
Date: Thu, 06 Jan 2022 05:06:39 +0100 [thread overview]
Message-ID: <20220106040639.0wNNBobYPHDKYqfHF2IVmbfcRoD-yYIegsDpTp6No-o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22291@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3249 bytes --]
New comment by RicArch97 on void-packages repository
https://github.com/void-linux/void-packages/pull/22291#issuecomment-1006268397
Comment:
Pulled the changes to test them locally, but ran into a dependency conflict;
```console
$ ./xbps-src pkg gamemode
=> xbps-src: updating repositories for host (x86_64)...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/debug/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/x86_64-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/multilib/nonfree/x86_64-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> gamemode-1.6_1: removing autodeps, please wait...
=> gamemode-1.6_1: building [meson] for x86_64...
[host] pkg-config-0.29.2_2: found (/host/binpkgs)
[host] meson-0.55.3_1: not found
[target] inih-devel-51_1: not found
[target] dbus-devel-1.12.20_1: found (https://alpha.de.repo.voidlinux.org/current)
[target] elogind-devel-243.4_3: not found
[runtime] libgamemode-1.6_1: not found (subpkg, ignored)
[runtime] libgamemode-1.6_1: not found (subpkg, ignored)
[runtime] libgamemode-1.6_1: not found (subpkg, ignored)
=> meson-0.55.3_1: building [python3-module] (dependency of gamemode) for x86_64...
[host] python3-devel-3.8.5_1: not found
[host] python3-setuptools-50.3.0_1: not found
[target] python3-3.8.5_1: not found
[runtime] ninja-1.10.1_1: not found
[runtime] python3-setuptools-50.3.0_1: not found
=> python3-3.8.5_1: building (dependency of meson) for x86_64...
[host] pkgconf-1.7.3_1: found (/host/binpkgs)
[target] libffi-devel-3.3_2: found (https://alpha.de.repo.voidlinux.org/current)
[target] readline-devel-8.0.004_1: not found
[target] gdbm-devel-1.18.1_1: not found
[target] libressl-devel-3.1.4_1: not found
[target] expat-devel-2.2.9_1: not found
[target] sqlite-devel-3.33.0_1: not found
[target] bzip2-devel-1.0.8_1: found (https://alpha.de.repo.voidlinux.org/current)
[target] zlib-devel-1.2.11_3: not found
[target] liblzma-devel-5.2.5_1: not found
[runtime] ca-certificates-20200601_1: not found
[runtime] python3-3.8.5_1: not found (self, ignored)
=> libreadline8-8.0.004_1: building [gnu-configure] (dependency of python3) for x86_64...
[target] ncurses-devel-6.2_3: found (/host/binpkgs)
[runtime] ncurses-devel-6.2_3: found (/host/binpkgs)
[runtime] libreadline8-8.0.004_1: not found (self, ignored)
[runtime] libhistory8-8.0.004_1: not found (subpkg, ignored)
=> libreadline8-8.0.004_1: installing target dependencies: ncurses-devel-6.2_3 ...
=> libreadline8-8.0.004_1: removing autodeps, please wait...
=> ERROR: libreadline8-8.0.004_1: failed to install 'ncurses-devel-6.2_3' dependency! (error 19)
ncurses-libs-6.2_3 in transaction breaks installed pkg `ncurses-6.2_4'
Transaction aborted due to unresolved dependencies.
=> ERROR: Please see above for the real error, exiting...
```
next prev parent reply other threads:[~2022-01-06 4:06 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 17:59 [PR PATCH] New package: gamemode-1.5.1 toluschr
2020-05-25 18:10 ` [PR PATCH] [Updated] " toluschr
2020-05-25 18:10 ` toluschr
2020-09-12 13:56 ` RoundDuckKira
2020-09-12 13:57 ` RoundDuckKira
2020-09-13 15:37 ` toluschr
2020-09-13 16:06 ` [PR REVIEW] " ericonr
2020-09-13 16:06 ` ericonr
2020-09-13 16:06 ` ericonr
2020-09-13 16:06 ` ericonr
2020-09-13 16:06 ` ericonr
2020-09-13 16:06 ` ericonr
2020-09-13 16:07 ` ericonr
2020-09-13 16:08 ` ericonr
2020-09-13 17:46 ` [PR PATCH] [Updated] " toluschr
2020-09-13 17:46 ` [PR REVIEW] " toluschr
2020-09-13 17:48 ` toluschr
2020-09-13 17:50 ` [PR PATCH] [Updated] " toluschr
2020-09-13 17:52 ` [PR REVIEW] " toluschr
2020-09-13 17:52 ` toluschr
2020-09-13 17:55 ` kostadin04
2020-09-13 17:55 ` [PR PATCH] [Updated] " toluschr
2020-09-13 17:56 ` toluschr
2020-09-13 17:57 ` kostadin04
2020-09-13 18:24 ` [PR REVIEW] New package: gamemode-1.6 ericonr
2020-09-13 18:25 ` ericonr
2020-09-13 18:29 ` toluschr
2020-09-13 18:30 ` toluschr
2020-09-13 18:30 ` toluschr
2020-09-13 18:30 ` toluschr
2020-09-13 18:39 ` ericonr
2020-09-13 18:49 ` [PR PATCH] [Updated] " toluschr
2020-09-14 5:01 ` RoundDuckKira
2020-09-14 11:10 ` [PR PATCH] [Updated] " toluschr
2020-09-29 2:10 ` ericonr
2020-09-30 8:43 ` toluschr
2020-09-30 8:47 ` toluschr
2022-01-06 4:06 ` RicArch97 [this message]
2022-01-06 22:16 ` paper42
2022-01-07 4:08 ` [PR REVIEW] " RicArch97
2022-01-07 4:08 ` RicArch97
2022-01-07 4:08 ` RicArch97
2022-04-07 16:07 ` kedodrill
2022-04-07 20:43 ` paper42
2022-04-07 21:00 ` RicArch97
2022-04-07 21:24 ` kedodrill
2022-04-07 21:24 ` kedodrill
2022-04-07 21:27 ` RicArch97
2022-04-09 10:16 ` [PR PATCH] [Closed]: " paper42
2022-04-09 10:16 ` paper42
2022-04-07 21:15 [PR PATCH] " kedodrill
2022-04-07 21:20 ` RicArch97
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=20220106040639.0wNNBobYPHDKYqfHF2IVmbfcRoD-yYIegsDpTp6No-o@z \
--to=ricarch97@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).