From: "David Roman" <davidroman96@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: net-p2p/dogecoin-qt/
Date: Tue, 18 Feb 2025 14:01:15 +0000 (UTC) [thread overview]
Message-ID: <1739868103.3cc576a66e18247f7e95cbb7ac3a3aa85f9fb5c8.davidroman@gentoo> (raw)
commit: 3cc576a66e18247f7e95cbb7ac3a3aa85f9fb5c8
Author: Victor Skovorodnikov <victor3.14 <AT> yandex <DOT> com>
AuthorDate: Tue Feb 18 08:39:09 2025 +0000
Commit: David Roman <davidroman96 <AT> gmail <DOT> com>
CommitDate: Tue Feb 18 08:41:43 2025 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=3cc576a6
net-p2p/dogecoin-qt: drop 1.14.8
- removed BDEPEND to fix nonsolvable depset failure
Signed-off-by: Victor Skovorodnikov <victor3.14 <AT> yandex.com>
net-p2p/dogecoin-qt/dogecoin-qt-1.14.9.ebuild | 5 -----
net-p2p/dogecoin-qt/dogecoin-qt-9999.ebuild | 5 -----
2 files changed, 10 deletions(-)
diff --git a/net-p2p/dogecoin-qt/dogecoin-qt-1.14.9.ebuild b/net-p2p/dogecoin-qt/dogecoin-qt-1.14.9.ebuild
index 06c5064dd..a28479918 100644
--- a/net-p2p/dogecoin-qt/dogecoin-qt-1.14.9.ebuild
+++ b/net-p2p/dogecoin-qt/dogecoin-qt-1.14.9.ebuild
@@ -52,11 +52,6 @@ RDEPEND="${DEPEND}
)
"
-BDEPEND="
- dev-build/autoconf
- dev-build/automake
-"
-
pkg_pretend() {
if use intel-avx2 && [[ ! -e "${ROOT}"/etc/portage/patches/app-crypt/intel-ipsec-mb/remove_digest_init.patch ]]; then
diff --git a/net-p2p/dogecoin-qt/dogecoin-qt-9999.ebuild b/net-p2p/dogecoin-qt/dogecoin-qt-9999.ebuild
index 163e7190f..ad589d5e6 100644
--- a/net-p2p/dogecoin-qt/dogecoin-qt-9999.ebuild
+++ b/net-p2p/dogecoin-qt/dogecoin-qt-9999.ebuild
@@ -50,11 +50,6 @@ RDEPEND="${DEPEND}
)
"
-BDEPEND="
- dev-build/autoconf
- dev-build/automake
-"
-
pkg_pretend() {
if use intel-avx2 && [[ ! -e "${ROOT}"/etc/portage/patches/app-crypt/intel-ipsec-mb/remove_digest_init.patch ]]; then
eerror "${ROOT}/etc/portage/patches/app-crypt/intel-ipsec-mb/remove_digest_init.patch does not exist!"
next reply other threads:[~2025-02-18 14:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 14:01 David Roman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-18 14:01 [gentoo-commits] repo/proj/guru:master commit in: net-p2p/dogecoin-qt/ David Roman
2025-02-18 14:01 David Roman
2025-02-18 14:01 David Roman
2024-12-02 10:48 David Roman
2024-09-01 15:53 David Roman
2024-08-10 20:34 Lucio Sauer
2024-08-10 15:41 Lucio Sauer
2024-08-07 23:36 Lucio Sauer
2024-07-08 16:47 David Roman
2024-03-02 18:02 Julien Roy
2024-03-02 7:10 Arthur Zamarin
2024-03-02 7:10 Arthur Zamarin
2024-02-28 7:19 Florian Schmaus
2024-02-28 7:19 Florian Schmaus
2024-02-28 7:19 Florian Schmaus
2024-02-28 7:19 Florian Schmaus
2024-02-13 16:32 David Roman
2023-10-28 1:15 David Roman
2023-09-26 12:43 David Roman
2023-07-25 4:59 Haelwenn Monnier
2023-07-25 4:59 Haelwenn Monnier
2023-07-25 4:59 Haelwenn Monnier
2023-07-25 4:59 Haelwenn Monnier
2023-07-21 4:12 Viorel Munteanu
2023-07-19 8:49 Haelwenn Monnier
2023-07-18 9:14 Viorel Munteanu
2023-07-18 9:14 Viorel Munteanu
2023-07-16 6:18 Haelwenn Monnier
2023-07-16 6:18 Haelwenn Monnier
2023-07-13 9:42 David Roman
2023-07-12 5:39 Viorel Munteanu
2023-07-12 5:39 Viorel Munteanu
2023-07-12 4:58 [gentoo-commits] repo/proj/guru:dev " Viorel Munteanu
2023-07-12 5:39 ` [gentoo-commits] repo/proj/guru:master " Viorel Munteanu
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=1739868103.3cc576a66e18247f7e95cbb7ac3a3aa85f9fb5c8.davidroman@gentoo \
--to=davidroman96@gmail.com \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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