From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/gtk-vnc/
Date: Mon, 14 Sep 2015 17:18:38 +0000 (UTC) [thread overview]
Message-ID: <1442251108.ced44c5400323d2a057dfafec99ae2930d823d89.pacho@gentoo> (raw)
commit: ced44c5400323d2a057dfafec99ae2930d823d89
Author: Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 14 17:17:59 2015 +0000
Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Mon Sep 14 17:18:28 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ced44c54
net-libs/gtk-vnc: It needs to be rebuilt with libgcrypt subslot bumps
Package-Manager: portage-2.2.20.1
net-libs/gtk-vnc/gtk-vnc-0.5.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-libs/gtk-vnc/gtk-vnc-0.5.4.ebuild b/net-libs/gtk-vnc/gtk-vnc-0.5.4.ebuild
index 11b6c5a..a72ab51 100644
--- a/net-libs/gtk-vnc/gtk-vnc-0.5.4.ebuild
+++ b/net-libs/gtk-vnc/gtk-vnc-0.5.4.ebuild
@@ -27,7 +27,7 @@ REQUIRED_USE="
# glib-2.30.1 needed to avoid linking failure due to .la files (bug #399129)
COMMON_DEPEND="
>=dev-libs/glib-2.30.1:2
- >=dev-libs/libgcrypt-1.4.2:0
+ >=dev-libs/libgcrypt-1.4.2:0=
dev-libs/libgpg-error
>=net-libs/gnutls-2.12
>=x11-libs/cairo-1.2
next reply other threads:[~2015-09-14 17:18 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 17:18 Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-11 19:00 [gentoo-commits] repo/gentoo:master commit in: net-libs/gtk-vnc/ Gilles Dartiguelongue
2016-09-11 19:00 Gilles Dartiguelongue
2016-10-19 22:02 Gilles Dartiguelongue
2017-05-24 8:38 Pacho Ramos
2017-05-24 8:38 Pacho Ramos
2017-09-12 6:51 Gilles Dartiguelongue
2017-10-03 0:42 Thomas Deutschmann
2017-10-20 14:51 Manuel Rüger
2017-10-28 8:43 Pacho Ramos
2018-04-14 22:41 Mart Raudsepp
2018-04-20 10:36 Mart Raudsepp
2018-04-20 10:36 Mart Raudsepp
2018-04-20 10:36 Mart Raudsepp
2018-04-26 17:15 Thomas Deutschmann
2018-04-26 22:32 Aaron Bauman
2018-04-29 0:08 Mart Raudsepp
2018-08-02 13:50 Mart Raudsepp
2018-11-02 12:54 Mart Raudsepp
2018-12-02 10:12 Mikle Kolyada
2018-12-02 14:29 Mikle Kolyada
2018-12-02 17:27 Mart Raudsepp
2018-12-09 16:04 Gilles Dartiguelongue
2019-03-07 21:14 Mart Raudsepp
2019-03-22 13:29 Mart Raudsepp
2019-05-18 23:05 Mart Raudsepp
2019-08-04 19:26 Aaron Bauman
2020-04-04 20:48 Mart Raudsepp
2020-04-04 21:15 Mart Raudsepp
2020-04-05 13:23 Mart Raudsepp
2020-06-28 14:19 Thomas Deutschmann
2020-06-29 15:42 Mikle Kolyada
2020-07-04 15:07 Mart Raudsepp
2021-04-28 4:21 Matt Turner
2021-04-28 4:21 Matt Turner
2021-05-07 13:28 Sam James
2021-05-07 13:29 Sam James
2021-05-08 20:27 Matt Turner
2021-12-17 1:22 Matt Turner
2021-12-31 3:42 Yixun Lan
2022-01-20 10:02 Jakov Smolić
2022-01-24 3:39 Sam James
2022-07-10 19:59 Sam James
2022-07-10 22:28 Sam James
2022-07-10 23:15 Sam James
2022-07-10 23:52 Sam James
2022-07-16 21:28 Matt Turner
2022-07-21 2:04 Matt Turner
2022-09-12 16:00 Sam James
2022-09-12 16:01 Sam James
2022-09-19 1:38 Sam James
2022-10-14 14:29 Matt Turner
2022-10-31 14:28 Matt Turner
2023-09-24 9:02 WANG Xuerui
2024-01-04 18:11 Arthur Zamarin
2024-06-03 7:00 Sam James
2024-06-10 13:55 Stefan Strogin
2024-08-06 0:20 Eli Schwartz
2024-08-09 17:19 Sam James
2024-08-09 17:19 Sam James
2024-08-26 22:57 Sam James
2024-12-04 18:10 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
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=1442251108.ced44c5400323d2a057dfafec99ae2930d823d89.pacho@gentoo \
--to=pacho@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