From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/tpm2-tools/
Date: Mon, 21 Jun 2021 22:44:30 +0000 (UTC) [thread overview]
Message-ID: <1624315457.c32180a825c18a528b3fc9552cbfa261462eb971.sam@gentoo> (raw)
commit: c32180a825c18a528b3fc9552cbfa261462eb971
Author: Christopher Byrne <salah.coronya <AT> gmail <DOT> com>
AuthorDate: Mon Jun 21 17:13:58 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jun 21 22:44:17 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c32180a8
app-crypt/tpm2-tools: Remove old
Bug: https://bugs.gentoo.org/793764
Package-Manager: Portage-3.0.20, Repoman-3.0.2
Signed-off-by: Christopher Byrne <salah.coronya <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/tpm2-tools/Manifest | 1 -
app-crypt/tpm2-tools/tpm2-tools-4.3.1.ebuild | 44 ----------------------------
2 files changed, 45 deletions(-)
diff --git a/app-crypt/tpm2-tools/Manifest b/app-crypt/tpm2-tools/Manifest
index 5ca8318994d..46ead7ebabd 100644
--- a/app-crypt/tpm2-tools/Manifest
+++ b/app-crypt/tpm2-tools/Manifest
@@ -1,4 +1,3 @@
-DIST tpm2-tools-4.3.1.tar.gz 891993 BLAKE2B d145fd542952ebbf59bb82640b9ac41cc777dcd8f526683447e3a3fd22fd4c46ab59899418ae52382d88e05418b772afd7f10093c5e0ef4cba685470cf7a7c8e SHA512 0104b6bca9e56ee30c033f3ddb2ab75b683b07ff917b800ff8fde49ce5cdc6d42e5fff63ed3ee9700f656dbf34bca76cee7408c256f1e30d92148c506b0032f2
DIST tpm2-tools-4.3.2.tar.gz 887708 BLAKE2B ee6fe3d0566138d6289d1a91252ccb106d36ff80d55f2d6f9ee30c8e16338d706e80085ac5f4f56a79bcb339e5dcb240efcf71d4003bcffdad366f3cd7a1165b SHA512 1aa47c62c3d2a83195ec649e50c0be2c8be39f926806d8d7cb96edc499c385d527661813e02024e98f83ae9ebcb22d7dadc507ddfab48be9bbe428d9439d7ee1
DIST tpm2-tools-5.0.tar.gz 990855 BLAKE2B 5d39bbef0bc6f0d84f37c64c697260343a9f9e134bce015a6b529176195adb907672f35b85382b0a4785e40e368030ac347083086c3799bdfe86dced1ac69848 SHA512 ea57a28a61e28b78cae7067ff58facd8754fafab7a2689fd93f8b3374073b6ac30301a75f8ff5c654800ab469ee6604d0b8a86c310631b9545b816ecaa05968e
DIST tpm2-tools-5.1.1.tar.gz 1044427 BLAKE2B 885ff61ad971c95d067bf8f9339de289f082f3103d1c382f45ac3ffbd4d5effc343ddc3c2c74b97b9d31f3f823d264991d1726c1f9c21d5c9b82ac1cdf714d3f SHA512 4e094dcffb66103773d85e866ab9ba8db5d0f205ff9658e08fe14e8e41250570a7f7274b4048934adf256ea41650fa498fc3d6da2786adc241a4bf2e8f7bf78e
diff --git a/app-crypt/tpm2-tools/tpm2-tools-4.3.1.ebuild b/app-crypt/tpm2-tools/tpm2-tools-4.3.1.ebuild
deleted file mode 100644
index 01663f80cd5..00000000000
--- a/app-crypt/tpm2-tools/tpm2-tools-4.3.1.ebuild
+++ /dev/null
@@ -1,44 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-inherit autotools
-
-DESCRIPTION="Tools for the TPM 2.0 TSS"
-HOMEPAGE="https://github.com/tpm2-software/tpm2-tools"
-SRC_URI="https://github.com/tpm2-software/${PN}/releases/download/${PV}/${P}.tar.gz"
-
-LICENSE="BSD"
-SLOT="0"
-KEYWORDS="~amd64"
-IUSE="+fapi"
-
-# Integration test are now run as part of the testing suite, which will fail
-# because none of the supported TPM emulators are in Portage. In a future
-# version of tpm2-tools, swtpm will be supported and the tests can be run.
-RESTRICT="test"
-
-RDEPEND="net-misc/curl:=
- >=app-crypt/tpm2-tss-2.4.0:=[fapi?]
- dev-libs/openssl:0="
-DEPEND="${RDEPEND}"
-BDEPEND="virtual/pkgconfig
- sys-devel/autoconf-archive"
-PATCHES=(
- "${FILESDIR}/${PN}-4.3.0-Remove-WError.patch"
-)
-
-src_prepare() {
- sed -i \
- "s/m4_esyscmd_s(\[git describe --tags --always --dirty\])/${PV}/" \
- "${S}/configure.ac" || die
- eautoreconf
- default
-}
-
-src_configure() {
- econf \
- $(use_enable fapi) \
- --enable-hardening
-}
next reply other threads:[~2021-06-21 22:44 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 22:44 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 6:24 [gentoo-commits] repo/gentoo:master commit in: app-crypt/tpm2-tools/ Sam James
2024-10-02 1:22 Sam James
2024-09-21 19:21 Sam James
2024-07-29 6:22 Joonas Niilola
2024-07-29 6:15 Joonas Niilola
2024-07-29 0:32 Sam James
2024-07-29 0:32 Sam James
2024-07-28 23:58 Jakov Smolić
2024-05-07 10:29 Sam James
2024-05-07 10:29 Sam James
2024-05-07 5:53 Joonas Niilola
2024-05-07 5:53 Joonas Niilola
2024-05-05 11:36 Sam James
2024-05-05 11:36 Sam James
2024-04-16 2:34 Sam James
2024-01-20 13:33 Sam James
2023-09-09 13:17 David Seifert
2023-04-05 20:16 Sam James
2023-04-05 20:16 Sam James
2023-04-05 20:16 Sam James
2023-04-05 20:03 Sam James
2023-04-05 20:03 Sam James
2023-03-15 17:07 Arthur Zamarin
2023-03-15 17:07 Arthur Zamarin
2023-03-15 17:05 Arthur Zamarin
2023-02-20 13:50 Sam James
2023-02-20 13:50 Sam James
2023-02-16 5:08 Sam James
2023-02-16 5:08 Sam James
2023-02-16 5:08 Sam James
2023-02-16 5:08 Sam James
2022-12-21 23:37 Sam James
2022-09-28 0:09 Sam James
2022-09-27 21:44 Sam James
2022-07-15 5:39 Joonas Niilola
2022-07-14 19:37 Arthur Zamarin
2022-07-14 19:37 Arthur Zamarin
2022-07-14 19:37 Arthur Zamarin
2022-07-14 19:37 Arthur Zamarin
2022-04-23 21:34 Sam James
2022-04-23 21:34 Sam James
2022-04-23 21:34 Sam James
2021-12-13 18:28 Arthur Zamarin
2021-12-13 0:06 Sam James
2021-12-13 0:06 Sam James
2021-10-04 14:24 Ionen Wolkens
2021-09-24 7:46 Joonas Niilola
2021-09-24 7:46 Joonas Niilola
2021-09-08 6:46 Sam James
2021-09-08 6:46 Sam James
2021-07-15 2:23 Ionen Wolkens
2021-07-14 6:25 Joonas Niilola
2021-06-21 22:44 Sam James
2021-06-21 22:44 Sam James
2021-06-21 22:44 Sam James
2021-06-09 6:08 Joonas Niilola
2021-06-09 6:08 Joonas Niilola
2021-05-02 16:40 Mikle Kolyada
2021-04-25 8:00 Michał Górny
2021-01-20 14:13 Joonas Niilola
2021-01-20 14:13 Joonas Niilola
2021-01-20 14:13 Joonas Niilola
2021-01-20 14:13 Joonas Niilola
2020-11-20 11:45 Joonas Niilola
2020-10-08 6:57 Joonas Niilola
2020-08-23 11:48 David Seifert
2020-02-26 16:17 Joonas Niilola
2019-05-30 23:46 Alon Bar-Lev
2018-12-30 21:00 Alon Bar-Lev
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=1624315457.c32180a825c18a528b3fc9552cbfa261462eb971.sam@gentoo \
--to=sam@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