From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/recover-broken-vdb/
Date: Sun, 3 Oct 2021 23:35:43 +0000 (UTC) [thread overview]
Message-ID: <1633304135.4e9255910ccab4ee1783fbaa17563d1a1b027400.sam@gentoo> (raw)
commit: 4e9255910ccab4ee1783fbaa17563d1a1b027400
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 3 23:35:07 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Oct 3 23:35:35 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4e925591
app-portage/recover-broken-vdb: add 0.0.9
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-portage/recover-broken-vdb/Manifest | 1 +
.../recover-broken-vdb-0.0.9.ebuild | 29 ++++++++++++++++++++++
2 files changed, 30 insertions(+)
diff --git a/app-portage/recover-broken-vdb/Manifest b/app-portage/recover-broken-vdb/Manifest
index 1c6822542e3..71ec1335bd7 100644
--- a/app-portage/recover-broken-vdb/Manifest
+++ b/app-portage/recover-broken-vdb/Manifest
@@ -1,3 +1,4 @@
DIST recover-broken-vdb-0.0.5.tar.gz 12739 BLAKE2B c818e1d24f2f6b049c42da7819ccbaab021e734ea92bef17b9201a48a039bb5b4c77002f85efc2cf1b1dfae36eb07b39b8dc0d1ac0acfeb00224945c98dbe149 SHA512 5b55a0296fb4c30b5173efa383ab7ffc8219bacb0366c19fdf8a636404829bda5ce501d8c6c436cacae954aa1b7bbc4426b9c5bf3a9cee0ab6159f25c1f919fb
DIST recover-broken-vdb-0.0.7.tar.gz 13336 BLAKE2B 0c7d2dc73ca6e525edf190caee56f76e918559a4c0da322bb93b5807554d214fd01b53b0cc5c983fa9009b98a5d71f5aac542b26fe6656b9f81989e159f20d8c SHA512 447effe9664781095e8fd9760ff7f63f8b10466299c002e20da3d226843fa9c24a50b2c8f9eebaaa07cecd75a17272757c0e2175dd81e8daf2a59fa7233bc4a3
DIST recover-broken-vdb-0.0.8.tar.gz 13867 BLAKE2B f756a8bd4e6227395a18f24fc872c057b3d826cf9752516919a86a6a5b860e5e1e01271d12574ebbcbaf0316a8c6597584c96ce82443c2abbeb2e7047f9f1e8c SHA512 207c17efc03c4d4e71ecc2eb36b1ac2a3d2d5f988dade0c643133c9080254beff24ed0430661336384b9bf40f953878b8ab00b335dcbeacc3716ee13ea2b6633
+DIST recover-broken-vdb-0.0.9.tar.gz 15410 BLAKE2B c8fffa07e817ef2ff825add92aac732036676dd08b2cbdcca60a7c1fa2fc740f0473be2147635701971fb9a0a871c65115a1fa9ea05486cffe747207e432d8fd SHA512 0fd9f5e0d046344ac6c86e446b7c52c11238b1d90cf330558da357b71b5fa577b157adfc6903e94f065de6afb0296df2ae191078836311792ec319f614e39d37
diff --git a/app-portage/recover-broken-vdb/recover-broken-vdb-0.0.9.ebuild b/app-portage/recover-broken-vdb/recover-broken-vdb-0.0.9.ebuild
new file mode 100644
index 00000000000..6bf73687516
--- /dev/null
+++ b/app-portage/recover-broken-vdb/recover-broken-vdb-0.0.9.ebuild
@@ -0,0 +1,29 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DISTUTILS_SINGLE_IMPL=1
+DISTUTILS_USE_SETUPTOOLS=pyproject.toml
+PYTHON_COMPAT=( python3_{8..10} )
+
+inherit distutils-r1
+
+DESCRIPTION="Check Portage's VDB for internal inconsistency on ELF metadata"
+HOMEPAGE="https://github.com/thesamesam/recover-broken-vdb"
+if [[ ${PV} == *9999 ]] ; then
+ inherit git-r3
+ EGIT_REPO_URI="https://github.com/thesamesam/recover-broken-vdb.git"
+else
+ SRC_URI="https://github.com/thesamesam/recover-broken-vdb/archive/refs/tags/${PV}.tar.gz -> ${P}.tar.gz"
+ KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+fi
+
+LICENSE="GPL-2"
+SLOT="0"
+
+# Require latest version of pax-utils to avoid users breaking their systems again
+# The tool itself works fine with older versions
+RDEPEND=">=app-misc/pax-utils-1.3.3
+ sys-apps/file
+ $(python_gen_cond_dep 'sys-apps/portage[${PYTHON_USEDEP}]')"
next reply other threads:[~2021-10-03 23:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 23:35 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-03 9:35 [gentoo-commits] repo/gentoo:master commit in: app-portage/recover-broken-vdb/ Sam James
2024-04-29 21:48 Sam James
2023-01-10 3:52 Sam James
2023-01-10 3:52 Sam James
2022-09-18 13:46 Michał Górny
2022-02-20 5:51 Sam James
2022-01-29 6:05 Sam James
2021-12-27 4:16 Sam James
2021-12-27 4:16 Sam James
2021-10-05 3:40 Sam James
2021-10-03 23:35 Sam James
2021-10-01 3:07 Sam James
2021-09-30 0:45 Sam James
2021-09-30 0:45 Sam James
2021-09-29 21:08 Sam James
2021-09-29 20:48 Sam James
2021-09-29 17:04 Sam James
2021-09-29 17:04 Sam James
2021-09-29 16:01 Sam James
2021-09-29 16:01 Sam James
2021-09-29 16:01 Sam James
2021-09-28 23:54 Sam James
2021-09-27 19:14 Sam James
2021-09-27 19:14 Sam James
2021-09-24 5:39 Sam James
2021-09-23 23:00 Sam James
2021-09-23 20:56 Sam James
2021-09-21 17:41 Sam James
2021-09-21 17:41 Sam James
2021-09-21 2:55 Sam James
2021-09-20 22:14 Sam James
2021-09-20 22:14 Sam James
2021-09-20 21:11 Sam James
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=1633304135.4e9255910ccab4ee1783fbaa17563d1a1b027400.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