public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
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: Wed, 29 Sep 2021 17:04:19 +0000 (UTC)	[thread overview]
Message-ID: <1632935049.a03bbf1de5c8e7a5c7caf06cedc7234d35fe455c.sam@gentoo> (raw)

commit:     a03bbf1de5c8e7a5c7caf06cedc7234d35fe455c
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 29 17:03:59 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Sep 29 17:04:09 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a03bbf1d

app-portage/recover-broken-vdb: stabilize 0.0.5

Bug: https://bugs.gentoo.org/815373
Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-portage/recover-broken-vdb/recover-broken-vdb-0.0.5.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-portage/recover-broken-vdb/recover-broken-vdb-0.0.5.ebuild b/app-portage/recover-broken-vdb/recover-broken-vdb-0.0.5.ebuild
index 6bf73687516..ce233e99dd6 100644
--- a/app-portage/recover-broken-vdb/recover-broken-vdb-0.0.5.ebuild
+++ b/app-portage/recover-broken-vdb/recover-broken-vdb-0.0.5.ebuild
@@ -16,7 +16,7 @@ if [[ ${PV} == *9999 ]] ; then
 	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"
+	KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86"
 fi
 
 LICENSE="GPL-2"


             reply	other threads:[~2021-09-29 17:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 17:04 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-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 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=1632935049.a03bbf1de5c8e7a5c7caf06cedc7234d35fe455c.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