From: "Sobhan Mohammadpour" <sobhan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: mail-client/geary/
Date: Tue, 19 Mar 2019 11:21:18 +0000 (UTC) [thread overview]
Message-ID: <1552994454.c828c9200bbf6e9766422aa41129e9178e32173b.sobhan@gentoo> (raw)
commit: c828c9200bbf6e9766422aa41129e9178e32173b
Author: Sobhan Mohammadpour <sobhan <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 19 11:19:12 2019 +0000
Commit: Sobhan Mohammadpour <sobhan <AT> gentoo <DOT> org>
CommitDate: Tue Mar 19 11:20:54 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c828c920
mail-client/geary: fix Q&A and make dependency on libunwind optional
remove non existing function call,
closes: 680888
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Sobhan Mohammadpour <sobhan <AT> gentoo.org>
mail-client/geary/{geary-3.32.0.ebuild => geary-3.32.0-r1.ebuild} | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/mail-client/geary/geary-3.32.0.ebuild b/mail-client/geary/geary-3.32.0-r1.ebuild
similarity index 96%
rename from mail-client/geary/geary-3.32.0.ebuild
rename to mail-client/geary/geary-3.32.0-r1.ebuild
index 44c256f2c5a..dd806a26e5b 100644
--- a/mail-client/geary/geary-3.32.0.ebuild
+++ b/mail-client/geary/geary-3.32.0-r1.ebuild
@@ -39,7 +39,7 @@ DEPEND="
app-text/enchant
>=dev-libs/folks-0.11:0
dev-libs/json-glib
- >=sys-libs/libunwind-1.1:7
+ unwind? ( >=sys-libs/libunwind-1.1:7 )
"
RDEPEND="${DEPEND}
gnome-base/dconf
@@ -64,8 +64,6 @@ src_prepare() {
done
fi
- meson_src_prepare
- gnome2_src_prepare
vala_src_prepare
xdg_src_prepare
}
next reply other threads:[~2019-03-19 11:21 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 11:21 Sobhan Mohammadpour [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-20 20:37 [gentoo-commits] repo/gentoo:master commit in: mail-client/geary/ Arthur Zamarin
2024-07-15 19:22 Pacho Ramos
2024-07-15 19:22 Pacho Ramos
2023-10-29 22:23 Mart Raudsepp
2023-08-18 14:50 Matt Turner
2023-08-16 22:32 Matt Turner
2023-07-06 13:59 Matt Turner
2022-10-30 23:21 Matt Turner
2022-04-19 5:50 Matt Turner
2022-04-19 5:50 Matt Turner
2021-08-27 20:45 Sam James
2021-07-11 12:31 Mart Raudsepp
2021-07-11 12:31 Mart Raudsepp
2021-07-11 12:31 Mart Raudsepp
2021-07-11 9:49 Mart Raudsepp
2021-06-26 1:34 Sam James
2021-04-30 16:39 Matt Turner
2021-04-28 2:39 Matt Turner
2021-04-17 1:20 Matt Turner
2020-08-29 8:27 Mart Raudsepp
2020-08-29 8:27 Mart Raudsepp
2020-05-18 7:53 Mart Raudsepp
2020-03-29 9:19 Mart Raudsepp
2020-03-16 22:20 Mart Raudsepp
2020-02-16 18:06 Mart Raudsepp
2020-02-16 18:06 Mart Raudsepp
2020-02-16 18:06 Mart Raudsepp
2020-02-05 13:06 Mart Raudsepp
2020-02-05 13:06 Mart Raudsepp
2020-02-02 20:13 Mart Raudsepp
2020-02-02 19:35 Mart Raudsepp
2020-01-10 21:49 Mart Raudsepp
2020-01-10 19:35 Thomas Deutschmann
2019-12-12 1:50 Matt Turner
2019-12-04 20:41 Matt Turner
2019-07-28 6:42 Mart Raudsepp
2019-03-18 0:56 Sobhan Mohammadpour
2019-02-14 0:03 Mart Raudsepp
2019-02-13 23:37 Mart Raudsepp
2018-12-02 17:27 Mart Raudsepp
2018-07-16 9:41 Mart Raudsepp
2018-01-18 3:20 Mikle Kolyada
2017-12-09 15:09 Pacho Ramos
2017-01-15 16:44 Pacho Ramos
2016-12-05 13:52 Pacho Ramos
2016-12-05 13:52 Pacho Ramos
2015-08-14 20:23 Julian Ospald
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=1552994454.c828c9200bbf6e9766422aa41129e9178e32173b.sobhan@gentoo \
--to=sobhan@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