From: "Julien Roy" <julien@jroy.ca>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-util/mock-core-configs/
Date: Mon, 20 May 2024 00:18:49 +0000 (UTC) [thread overview]
Message-ID: <1716092957.41b5362202439fe66a4810919f5fa9aed56f070f.julien@gentoo> (raw)
commit: 41b5362202439fe66a4810919f5fa9aed56f070f
Author: Takuya Wakazono <pastalian46 <AT> gmail <DOT> com>
AuthorDate: Sun May 19 04:29:17 2024 +0000
Commit: Julien Roy <julien <AT> jroy <DOT> ca>
CommitDate: Sun May 19 04:29:17 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=41b53622
dev-util/mock-core-configs: add 40.4
Signed-off-by: Takuya Wakazono <pastalian46 <AT> gmail.com>
dev-util/mock-core-configs/Manifest | 1 +
.../mock-core-configs/mock-core-configs-40.4.ebuild | 17 +++++++++++++++++
2 files changed, 18 insertions(+)
diff --git a/dev-util/mock-core-configs/Manifest b/dev-util/mock-core-configs/Manifest
index 4070d37be9..5492a068d5 100644
--- a/dev-util/mock-core-configs/Manifest
+++ b/dev-util/mock-core-configs/Manifest
@@ -1 +1,2 @@
DIST mock-core-configs-40.3.tar.gz 44864 BLAKE2B 5321613c5b8c11c1c686a6919d1f394ced243b70ebc092f2f28ccc43f0634a8ccdfbf10ba7074276da8719920b9cf92f7a2c7648b2f3b4a3ea2fe87bd5131f49 SHA512 74f85e626be3291b8ad4797c65fed8e8df992640f0a4403378908064e6748dacd6fa2bfbe108d2c8d50ff139a7fcc51d24aa3fdbeec02d38a235c4d789992c06
+DIST mock-core-configs-40.4.tar.gz 45904 BLAKE2B 8aad350476811709562be71d9ee13aac156d1451b65b83f6bd303b6ff7c1f6dd96c8de499ccca46567abeb6d8459d7403036beab52cd5c0866138e8d82e0cd61 SHA512 b09af09c8d367928a9bed2f86fe3740e0d44ac6d130506debefd08c719da386dd410dd221ee9fd4913bee06e2b5bb327065fab40b0a43791f5e9ee8e160fb05a
diff --git a/dev-util/mock-core-configs/mock-core-configs-40.4.ebuild b/dev-util/mock-core-configs/mock-core-configs-40.4.ebuild
new file mode 100644
index 0000000000..b53e863563
--- /dev/null
+++ b/dev-util/mock-core-configs/mock-core-configs-40.4.ebuild
@@ -0,0 +1,17 @@
+# Copyright 2023-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DESCRIPTION="Mock core config files basic chroots"
+HOMEPAGE="https://rpm-software-management.github.io/mock/ https://github.com/rpm-software-management/mock"
+SRC_URI="https://github.com/rpm-software-management/mock/releases/download/${P}-1/${P}.tar.gz"
+
+LICENSE="GPL-2+"
+SLOT="0"
+KEYWORDS="~amd64"
+
+src_install() {
+ insinto /etc/mock
+ doins -r etc/mock/*
+}
next reply other threads:[~2024-05-20 0:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 0:18 Julien Roy [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-28 15:12 [gentoo-commits] repo/proj/guru:master commit in: dev-util/mock-core-configs/ David Roman
2025-02-28 15:12 David Roman
2025-01-17 14:16 Julien Roy
2025-01-17 14:16 Julien Roy
2024-12-21 15:24 Julien Roy
2024-12-21 15:24 Julien Roy
2024-10-02 13:59 David Roman
2024-10-02 13:59 David Roman
2024-09-27 17:02 David Roman
2024-09-27 17:02 David Roman
2024-08-17 10:16 David Roman
2024-08-17 10:16 David Roman
2024-05-20 0:18 Julien Roy
2024-04-10 10:57 Julien Roy
2024-04-10 10:57 Julien Roy
2024-02-17 10:35 Haelwenn Monnier
2024-02-17 10:35 Haelwenn Monnier
2024-02-15 14:58 David Roman
2024-02-15 14:58 David Roman
2023-12-20 9:10 David Roman
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=1716092957.41b5362202439fe66a4810919f5fa9aed56f070f.julien@gentoo \
--to=julien@jroy.ca \
--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