From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/prefix-toolkit/
Date: Fri, 26 May 2023 06:25:57 +0000 (UTC) [thread overview]
Message-ID: <1685082328.40925478f0552e5e63c325232b9e66e143540af3.sam@gentoo> (raw)
commit: 40925478f0552e5e63c325232b9e66e143540af3
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri May 26 06:25:28 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri May 26 06:25:28 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=40925478
app-portage/prefix-toolkit: add 10, drop 9
Only change is that this is the first "new" tag post-conversion (and so
doesn't have the ebuild in the repo->tag->tarball fetched, which is a bit
icky).
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-portage/prefix-toolkit/Manifest | 2 +-
.../{prefix-toolkit-9.ebuild => prefix-toolkit-10.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-portage/prefix-toolkit/Manifest b/app-portage/prefix-toolkit/Manifest
index da79406b5d2b..ebd30aa764bd 100644
--- a/app-portage/prefix-toolkit/Manifest
+++ b/app-portage/prefix-toolkit/Manifest
@@ -1 +1 @@
-DIST prefix-toolkit-9.tar.bz2 8642 BLAKE2B b81a2c5af56e123b74434512660783273a5af1ea3c193e97c48f4bcf84eaafce3b95df432f5571ef049f56a7f2fefa7a1da603a14bc3a3cef9465559e519e948 SHA512 45f7718e5ef72f05a6bd5ef3bdda3f62076c925b414bd8f2ca54207deb515adab37612c571e5e92b2a1ec400b3780043804814e1c1243f8ace90dca6a1ad2035
+DIST prefix-toolkit-10.tar.bz2 5715 BLAKE2B fe8b4642fc4f8fa97bd8c9dc4f9e907dd0ca464ddc20e28d2888354f766fce04dd6ebc3bfae23bc776c59986c8167cc94510fb950124917874c5dde4f68cddfe SHA512 58f7fabab8ce5e2c3b2f0725733d02e340efb714ecf3556c27dbe95e7cf9c4b2f4ae658c44749cf2c62111d1135c60c333bbf93ee1c7b79ea11b908cc923c730
diff --git a/app-portage/prefix-toolkit/prefix-toolkit-9.ebuild b/app-portage/prefix-toolkit/prefix-toolkit-10.ebuild
similarity index 100%
rename from app-portage/prefix-toolkit/prefix-toolkit-9.ebuild
rename to app-portage/prefix-toolkit/prefix-toolkit-10.ebuild
next reply other threads:[~2023-05-26 6:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:25 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-03 11:50 [gentoo-commits] repo/gentoo:master commit in: app-portage/prefix-toolkit/ Fabian Groffen
2025-05-03 11:50 Fabian Groffen
2025-01-13 20:03 Fabian Groffen
2023-05-27 10:44 Fabian Groffen
2023-05-27 10:15 Fabian Groffen
2023-05-27 9:29 Sam James
2023-05-26 6:23 Sam James
2023-05-26 6:23 Sam James
2023-05-26 6:23 Sam James
2023-04-24 20:15 Sam James
2023-04-24 20:15 Sam James
2023-04-24 20:13 Sam James
2022-07-11 20:19 Jakov Smolić
2021-06-02 19:01 Sam James
2021-01-06 13:23 Fabian Groffen
2020-12-27 14:01 Fabian Groffen
2020-03-13 14:35 Michael Haubenwallner
2020-03-13 14:35 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2019-09-05 10:30 Michael Haubenwallner
2019-09-04 10:31 Michael Haubenwallner
2019-09-04 10:31 Michael Haubenwallner
2019-06-25 9:21 Michael Haubenwallner
2019-06-17 9:44 Michael Haubenwallner
2019-06-12 15:32 Michael Haubenwallner
2019-06-05 15:39 Michael Haubenwallner
2019-05-21 8:48 Michael Haubenwallner
2019-03-26 16:11 Michael Haubenwallner
2019-03-26 15:58 Michael Haubenwallner
2019-03-25 14:19 Michael Haubenwallner
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=1685082328.40925478f0552e5e63c325232b9e66e143540af3.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