public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bernard Cafarelli" <voyageur@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/paperwork/
Date: Tue,  1 Jun 2021 19:27:28 +0000 (UTC)	[thread overview]
Message-ID: <1622575644.db48ef9ae8e400c4144b4e0314f1db3c53ff6f9b.voyageur@gentoo> (raw)

commit:     db48ef9ae8e400c4144b4e0314f1db3c53ff6f9b
Author:     Bernard Cafarelli <voyageur <AT> gentoo <DOT> org>
AuthorDate: Tue Jun  1 19:27:12 2021 +0000
Commit:     Bernard Cafarelli <voyageur <AT> gentoo <DOT> org>
CommitDate: Tue Jun  1 19:27:24 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=db48ef9a

app-text/paperwork: fix install with tesseract[opencl] and nvidia

Closes: https://bugs.gentoo.org/793446
Package-Manager: Portage-3.0.19, Repoman-3.0.3
Signed-off-by: Bernard Cafarelli <voyageur <AT> gentoo.org>

 app-text/paperwork/paperwork-2.0.3.ebuild | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/app-text/paperwork/paperwork-2.0.3.ebuild b/app-text/paperwork/paperwork-2.0.3.ebuild
index b9ec9918ccc..3095f01e5a0 100644
--- a/app-text/paperwork/paperwork-2.0.3.ebuild
+++ b/app-text/paperwork/paperwork-2.0.3.ebuild
@@ -36,6 +36,10 @@ PATCHES=( "${FILESDIR}"/${P}-desktop_file.patch )
 python_install_all() {
 	distutils-r1_python_install_all
 
+	# This queries tesseract languages and will fail sandbox with
+	# USE=opencl, bug #793446
+	addpredict /dev/nvidiactl
+
 	PYTHONPATH="src" "${EPYTHON}" src/paperwork_gtk/main.py install \
 		--icon_base_dir="${ED}"/usr/share/icons \
 		--data_base_dir="${ED}"/usr/share


             reply	other threads:[~2021-06-01 19:27 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 19:27 Bernard Cafarelli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-26  9:57 [gentoo-commits] repo/gentoo:master commit in: app-text/paperwork/ 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-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
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=1622575644.db48ef9ae8e400c4144b4e0314f1db3c53ff6f9b.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