From: "Bernard Cafarelli" <voyageur@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/paperwork/
Date: Fri, 12 Jan 2018 17:57:51 +0000 (UTC) [thread overview]
Message-ID: <1515779858.d8a23f63326011668aa1c7a86372ed6f4df05462.voyageur@gentoo> (raw)
commit: d8a23f63326011668aa1c7a86372ed6f4df05462
Author: Bernard Cafarelli <voyageur <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 12 17:56:01 2018 +0000
Commit: Bernard Cafarelli <voyageur <AT> gentoo <DOT> org>
CommitDate: Fri Jan 12 17:57:38 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d8a23f63
app-text/paperwork: shell needs pyxdg
Thanks Sven Hesse <drmccoy <AT> drmccoy.de> in bug #636790
Package-Manager: Portage-2.3.19, Repoman-2.3.6
app-text/paperwork/paperwork-1.2.2.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/app-text/paperwork/paperwork-1.2.2.ebuild b/app-text/paperwork/paperwork-1.2.2.ebuild
index 23d0921fdd5..ca20baeb28f 100644
--- a/app-text/paperwork/paperwork-1.2.2.ebuild
+++ b/app-text/paperwork/paperwork-1.2.2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -24,6 +24,7 @@ RDEPEND="~app-text/paperwork-backend-${PV}[${PYTHON_USEDEP}]
dev-python/pygobject:3[${PYTHON_USEDEP}]
dev-python/pyinsane:2[${PYTHON_USEDEP}]
>=dev-python/pyocr-0.3.0[${PYTHON_USEDEP}]
+ dev-python/pyxdg[${PYTHON_USEDEP}]
dev-python/simplebayes[${PYTHON_USEDEP}]
x11-libs/gtk+:3[introspection]
x11-libs/libnotify[introspection]"
next reply other threads:[~2018-01-12 17:58 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 17:57 Bernard Cafarelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-31 6:45 [gentoo-commits] repo/gentoo:master commit in: app-text/paperwork/ Bernard Cafarelli
2025-03-31 6:45 Bernard Cafarelli
2024-09-26 9:57 Bernard Cafarelli
2024-09-26 9:57 Bernard Cafarelli
2024-06-14 10:47 Bernard Cafarelli
2024-06-14 10:47 Bernard Cafarelli
2024-05-06 23:05 Bernard Cafarelli
2024-05-06 23:05 Bernard Cafarelli
2023-11-07 19:39 Bernard Cafarelli
2023-11-07 19:15 Bernard Cafarelli
2023-11-07 14:51 Bernard Cafarelli
2023-11-07 14:51 Bernard Cafarelli
2023-05-20 6:26 Michał Górny
2023-02-01 7:59 Bernard Cafarelli
2023-02-01 7:59 Bernard Cafarelli
2023-02-01 7:58 Bernard Cafarelli
2022-09-20 16:55 Michał Górny
2022-06-29 9:05 Bernard Cafarelli
2022-02-04 12:24 Bernard Cafarelli
2021-12-30 10:04 Bernard Cafarelli
2021-12-22 13:09 Bernard Cafarelli
2021-06-01 19:27 Bernard Cafarelli
2021-05-20 10:27 Bernard Cafarelli
2021-01-02 10:58 Bernard Cafarelli
2020-12-29 16:42 Bernard Cafarelli
2020-04-19 12:25 Bernard Cafarelli
2020-03-17 10:32 Bernard Cafarelli
2020-03-17 10:32 Bernard Cafarelli
2019-12-30 14:00 Bernard Cafarelli
2019-08-23 16:54 Bernard Cafarelli
2019-03-08 14:24 Bernard Cafarelli
2019-03-08 11:27 Bernard Cafarelli
2018-09-27 13:14 Bernard Cafarelli
2018-09-27 13:14 Bernard Cafarelli
2018-07-26 13:42 Manuel Rüger
2018-04-09 10:15 Bernard Cafarelli
2018-02-18 19:24 Bernard Cafarelli
2018-01-12 17:57 Bernard Cafarelli
2017-11-17 16:38 Bernard Cafarelli
2017-11-06 13:08 Bernard Cafarelli
2017-07-26 11:26 Bernard Cafarelli
2017-07-25 11:26 Bernard Cafarelli
2017-07-25 11:26 Bernard Cafarelli
2017-03-28 12:20 Bernard Cafarelli
2017-02-13 16:06 Bernard Cafarelli
2017-02-13 16:06 Bernard Cafarelli
2017-02-03 9:27 Bernard Cafarelli
2017-01-02 11:18 Bernard Cafarelli
2017-01-02 11:18 Bernard Cafarelli
2016-11-28 12:49 Bernard Cafarelli
2016-11-21 13:22 Bernard Cafarelli
2016-11-14 15:18 Bernard Cafarelli
2016-11-10 14:28 Bernard Cafarelli
2016-11-10 13:27 Bernard Cafarelli
2016-11-10 10:33 Bernard Cafarelli
2016-04-17 17:27 Manuel Rüger
2016-02-16 21:09 Bernard Cafarelli
2016-02-16 21:09 Bernard Cafarelli
2015-12-02 13:33 Bernard Cafarelli
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=1515779858.d8a23f63326011668aa1c7a86372ed6f4df05462.voyageur@gentoo \
--to=voyageur@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