public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-forensics/sleuthkit/
Date: Thu, 26 Nov 2020 03:26:48 +0000 (UTC)	[thread overview]
Message-ID: <1606361165.75391f0ce1d6c44f7288e8a059bb2b1b39743c04.gokturk@gentoo> (raw)

commit:     75391f0ce1d6c44f7288e8a059bb2b1b39743c04
Author:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 26 03:26:05 2020 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Thu Nov 26 03:26:05 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=75391f0c

app-forensics/sleuthkit: fix failure due to non-existing ivy home #756766

Closes: https://bugs.gentoo.org/756766
Package-Manager: Portage-3.0.10, Repoman-3.0.1
Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org>

 app-forensics/sleuthkit/sleuthkit-4.10.1.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/app-forensics/sleuthkit/sleuthkit-4.10.1.ebuild b/app-forensics/sleuthkit/sleuthkit-4.10.1.ebuild
index 92f8ae71990..0056a2c4872 100644
--- a/app-forensics/sleuthkit/sleuthkit-4.10.1.ebuild
+++ b/app-forensics/sleuthkit/sleuthkit-4.10.1.ebuild
@@ -262,6 +262,8 @@ src_compile() {
 }
 
 src_install() {
+	# Give it an existing bogus ivy home #756766
+	local -x IVY_HOME="${T}"
 	local f
 
 	if use java; then


             reply	other threads:[~2020-11-26  3:26 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26  3:26 Göktürk Yüksek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-11 17:47 [gentoo-commits] repo/gentoo:master commit in: app-forensics/sleuthkit/ Arthur Zamarin
2024-09-11 14:15 Sam James
2024-09-05 12:22 Sam James
2024-09-05 12:22 Sam James
2024-08-05  7:26 Göktürk Yüksek
2024-08-05  7:19 Göktürk Yüksek
2024-07-30 23:44 Jakov Smolić
2024-07-30 18:00 Arthur Zamarin
2024-07-30 18:00 Arthur Zamarin
2024-01-07  7:52 Göktürk Yüksek
2023-06-27  4:11 Göktürk Yüksek
2023-06-27  4:11 Göktürk Yüksek
2022-09-07  6:51 Jakov Smolić
2022-09-06 12:51 Agostino Sarubbo
2022-09-06 12:50 Agostino Sarubbo
2022-06-09  6:45 Sam James
2022-06-08  8:46 Agostino Sarubbo
2022-06-08  8:44 Agostino Sarubbo
2022-06-08  8:42 Agostino Sarubbo
2022-05-09 18:58 Florian Schmaus
2022-05-09 18:58 Florian Schmaus
2022-05-09 18:58 Florian Schmaus
2022-02-16  2:53 Göktürk Yüksek
2021-08-11  6:43 Agostino Sarubbo
2021-08-10 15:36 Agostino Sarubbo
2021-08-10  6:42 Agostino Sarubbo
2021-08-09 23:53 Göktürk Yüksek
2021-08-09 23:16 Göktürk Yüksek
2021-08-09 23:16 Göktürk Yüksek
2021-08-09 23:16 Göktürk Yüksek
2021-06-23 15:41 Göktürk Yüksek
2021-06-23  8:13 Miroslav Šulc
2021-06-23  8:13 Miroslav Šulc
2021-06-23  8:13 Miroslav Šulc
2021-06-23  8:13 Miroslav Šulc
2021-06-23  8:13 Miroslav Šulc
2020-11-25  2:29 Göktürk Yüksek
2020-06-20  1:11 Aaron Bauman
2020-06-18  2:46 Aaron Bauman
2020-06-09 13:53 Agostino Sarubbo
2020-06-09 13:49 Agostino Sarubbo
2020-06-09 13:45 Agostino Sarubbo
2020-05-09 19:43 Sergei Trofimovich
2020-05-06  0:51 Göktürk Yüksek
2020-05-06  0:07 Göktürk Yüksek
2020-01-25  0:54 Göktürk Yüksek
2019-10-15 23:21 Göktürk Yüksek
2019-08-05  4:43 Göktürk Yüksek
2019-08-05  4:43 Göktürk Yüksek
2019-06-05  0:02 Göktürk Yüksek
2019-01-24 20:18 Göktürk Yüksek
2018-12-19 17:08 Göktürk Yüksek
2018-11-29 18:00 Göktürk Yüksek
2018-04-22 19:18 Matt Turner
2018-04-04 11:24 Göktürk Yüksek
2018-03-03 22:16 Sergei Trofimovich
2017-11-29 18:52 Thomas Deutschmann
2017-11-29 11:19 Agostino Sarubbo
2017-11-09  0:06 Göktürk Yüksek
2017-11-08 23:56 Göktürk Yüksek
2017-11-08 23:53 Göktürk Yüksek
2017-08-16 22:53 Göktürk Yüksek
2017-08-16  3:07 Göktürk Yüksek
2017-08-16  3:07 Göktürk Yüksek
2017-08-11 17:38 Michał Górny
2015-08-28  0:14 Manuel Rüger

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=1606361165.75391f0ce1d6c44f7288e8a059bb2b1b39743c04.gokturk@gentoo \
    --to=gokturk@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