From: "Julien Roy" <julien@jroy.ca>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: sci-electronics/verible/
Date: Sat, 24 Feb 2024 17:13:01 +0000 (UTC) [thread overview]
Message-ID: <1708793816.6d590e5f8fce69def95e4ad13215ed35f6478fad.julien@gentoo> (raw)
Message-ID: <20240224171301.-eCy1T5DQpx2mLph__rXuYzDKUUVjXCRxK1fAgROnDY@z> (raw)
commit: 6d590e5f8fce69def95e4ad13215ed35f6478fad
Author: Julien Roy <julien <AT> jroy <DOT> ca>
AuthorDate: Sat Feb 24 16:56:56 2024 +0000
Commit: Julien Roy <julien <AT> jroy <DOT> ca>
CommitDate: Sat Feb 24 16:56:56 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6d590e5f
sci-electronics/verible: comment-out invalid eclass
Signed-off-by: Julien Roy <julien <AT> jroy.ca>
sci-electronics/verible/verible-0.0.3420.ebuild | 6 ++++--
sci-electronics/verible/verible-0.0.3430.ebuild | 6 ++++--
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/sci-electronics/verible/verible-0.0.3420.ebuild b/sci-electronics/verible/verible-0.0.3420.ebuild
index e2ab50b528..6e0fdb6334 100644
--- a/sci-electronics/verible/verible-0.0.3420.ebuild
+++ b/sci-electronics/verible/verible-0.0.3420.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI="8"
@@ -6,7 +6,9 @@ EAPI="8"
# From release tag name
MY_PV="0.0-3420-g5be583bb"
-inherit bazel
+# Eclass dropped from ::gentoo
+# https://github.com/gentoo/gentoo/commit/8876dc1db3205682d1ed8543b7fef1ce2b619874
+# inherit bazel
DESCRIPTION="SystemVerilog parser, style-linter, and formatter"
HOMEPAGE="
diff --git a/sci-electronics/verible/verible-0.0.3430.ebuild b/sci-electronics/verible/verible-0.0.3430.ebuild
index d134e40091..6f345e0b46 100644
--- a/sci-electronics/verible/verible-0.0.3430.ebuild
+++ b/sci-electronics/verible/verible-0.0.3430.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI="8"
@@ -6,7 +6,9 @@ EAPI="8"
# From release tag name
MY_PV="0.0-3430-g060bde0f"
-inherit bazel
+# Eclass dropped from ::gentoo
+# https://github.com/gentoo/gentoo/commit/8876dc1db3205682d1ed8543b7fef1ce2b619874
+# inherit bazel
DESCRIPTION="SystemVerilog parser, style-linter, and formatter"
HOMEPAGE="
next reply other threads:[~2024-02-24 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 16:57 Julien Roy [this message]
2024-02-24 17:13 ` [gentoo-commits] repo/proj/guru:master commit in: sci-electronics/verible/ Julien Roy
-- strict thread matches above, loose matches on Subject: below --
2024-02-25 16:05 [gentoo-commits] repo/proj/guru:dev " Rui Huang
2023-12-14 8:56 Rui Huang
2023-10-12 4:51 [gentoo-commits] repo/proj/guru:master " Rui Huang
2023-10-12 4:45 ` [gentoo-commits] repo/proj/guru:dev " Rui Huang
2023-10-12 4:51 [gentoo-commits] repo/proj/guru:master " Rui Huang
2023-10-12 4:45 ` [gentoo-commits] repo/proj/guru:dev " Rui Huang
2023-04-03 9:01 Rui Huang
2023-04-01 7:09 Rui Huang
2022-09-07 4:34 Rui Huang
2022-09-06 9:18 Rui Huang
2022-07-08 5:03 Rui Huang
2022-07-08 5:03 Rui Huang
2022-07-08 5:01 Rui Huang
2022-04-19 14:55 Rui Huang
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=1708793816.6d590e5f8fce69def95e4ad13215ed35f6478fad.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