From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/libktorrent/
Date: Sun, 1 Sep 2019 21:26:02 +0000 (UTC) [thread overview]
Message-ID: <1567373152.23bc6b85817f2091b63c5a7ddb4ff2c5d9a8ef5d.asturm@gentoo> (raw)
commit: 23bc6b85817f2091b63c5a7ddb4ff2c5d9a8ef5d
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 1 21:23:51 2019 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Sun Sep 1 21:25:52 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=23bc6b85
net-libs/libktorrent: We still want that patch
Package-Manager: Portage-2.3.74, Repoman-2.3.17
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
net-libs/libktorrent/libktorrent-2.1.1.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net-libs/libktorrent/libktorrent-2.1.1.ebuild b/net-libs/libktorrent/libktorrent-2.1.1.ebuild
index b9e2994e0e4..d9c041e72e8 100644
--- a/net-libs/libktorrent/libktorrent-2.1.1.ebuild
+++ b/net-libs/libktorrent/libktorrent-2.1.1.ebuild
@@ -20,7 +20,6 @@ COMMON_DEPEND="
$(add_frameworks_dep karchive)
$(add_frameworks_dep kconfig)
$(add_frameworks_dep kcoreaddons)
- $(add_frameworks_dep kcrash)
$(add_frameworks_dep ki18n)
$(add_frameworks_dep kio)
$(add_frameworks_dep solid)
@@ -37,6 +36,8 @@ RDEPEND="${COMMON_DEPEND}
!dev-libs/botan[gmp(-)]
"
+PATCHES=( "${FILESDIR}/${PN}-2.1-unused-link.patch" ) # git master
+
src_prepare() {
kde5_src_prepare
next reply other threads:[~2019-09-01 21:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 21:26 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-09 16:49 [gentoo-commits] repo/gentoo:master commit in: net-libs/libktorrent/ Andreas Sturmlechner
2024-11-10 9:31 Andreas Sturmlechner
2024-11-10 9:31 Andreas Sturmlechner
2024-09-02 14:50 Andreas Sturmlechner
2024-05-20 11:39 Andreas Sturmlechner
2022-09-04 13:03 David Seifert
2021-08-04 9:01 Agostino Sarubbo
2021-08-04 8:40 Agostino Sarubbo
2021-04-06 6:31 Agostino Sarubbo
2020-10-16 17:46 Georgy Yakovlev
2020-07-20 6:42 Agostino Sarubbo
2020-07-11 11:29 Sam James
2020-07-11 1:25 Andreas Sturmlechner
2020-06-07 9:30 Andreas Sturmlechner
2020-01-04 13:55 Andreas Sturmlechner
2019-12-27 0:07 Andreas Sturmlechner
2019-11-08 16:54 Aaron Bauman
2019-11-03 13:29 Mikle Kolyada
2019-10-26 22:42 Andreas Sturmlechner
2019-09-01 20:43 Andreas Sturmlechner
2019-08-12 6:16 Andreas Sturmlechner
2019-08-11 21:30 Thomas Deutschmann
2019-07-22 8:48 Mikle Kolyada
2018-03-22 12:22 Andreas Sturmlechner
2017-09-30 12:44 Andreas Sturmlechner
2017-09-29 2:55 Michael Palimaka
2017-09-29 2:55 Michael Palimaka
2017-08-31 20:54 Andreas Sturmlechner
2017-08-20 9:25 Andreas Sturmlechner
2017-06-27 17:24 Andreas Sturmlechner
2017-06-27 17:24 Andreas Sturmlechner
2017-06-04 18:46 Andreas Sturmlechner
2017-01-04 17:22 Johannes Huber
2016-12-21 9:40 Tobias Klausmann
2016-07-07 17:52 Michael Palimaka
2016-06-26 18:07 Michael Palimaka
2016-06-15 17:59 Michael Palimaka
2016-04-20 10:34 Michael Palimaka
2016-04-16 13:43 Johannes Huber
2016-03-08 14:42 Michael Palimaka
2016-03-08 14:29 Michael Palimaka
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=1567373152.23bc6b85817f2091b63c5a7ddb4ff2c5d9a8ef5d.asturm@gentoo \
--to=asturm@gentoo.org \
--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