From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-electronics/kicad-packages3d/
Date: Thu, 8 Sep 2022 14:33:15 +0000 (UTC) [thread overview]
Message-ID: <1662647584.29883d3eae6de25f04a39778f00ec71d1060a8f2.ago@gentoo> (raw)
commit: 29883d3eae6de25f04a39778f00ec71d1060a8f2
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Thu Sep 8 14:33:04 2022 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Thu Sep 8 14:33:04 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=29883d3e
sci-electronics/kicad-packages3d: Stabilize 6.0.6 amd64, #869155
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
sci-electronics/kicad-packages3d/kicad-packages3d-6.0.6.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sci-electronics/kicad-packages3d/kicad-packages3d-6.0.6.ebuild b/sci-electronics/kicad-packages3d/kicad-packages3d-6.0.6.ebuild
index 1c1cdb3541fd..ec626e8dff33 100644
--- a/sci-electronics/kicad-packages3d/kicad-packages3d-6.0.6.ebuild
+++ b/sci-electronics/kicad-packages3d/kicad-packages3d-6.0.6.ebuild
@@ -19,7 +19,7 @@ else
SRC_URI="https://gitlab.com/kicad/libraries/${PN}/-/archive/${MY_PV}/${MY_P}.tar.gz -> ${P}.tar.gz"
if [[ ${PV} != *_rc* ]] ; then
- KEYWORDS="~amd64 ~arm64 ~riscv ~x86"
+ KEYWORDS="amd64 ~arm64 ~riscv ~x86"
fi
S="${WORKDIR}/${PN/3d/3D}-${MY_PV}-${MY_HASH}"
next reply other threads:[~2022-09-08 14:33 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 14:33 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-23 21:08 [gentoo-commits] repo/gentoo:master commit in: sci-electronics/kicad-packages3d/ Sam James
2024-11-07 11:59 Sam James
2024-09-24 5:22 Yixun Lan
2024-08-23 9:30 Joonas Niilola
2024-08-22 11:40 Yixun Lan
2024-08-09 3:05 Yixun Lan
2024-08-09 3:05 Yixun Lan
2024-08-09 3:05 Yixun Lan
2024-08-09 3:05 Yixun Lan
2024-06-11 20:45 Sam James
2024-05-03 13:13 Andrew Ammerlaan
2024-03-18 7:35 Joonas Niilola
2024-03-17 23:12 Yixun Lan
2024-03-17 23:12 Yixun Lan
2024-03-17 23:12 Yixun Lan
2024-03-17 23:12 Yixun Lan
2024-02-28 11:03 Yixun Lan
2024-01-31 10:22 Yixun Lan
2023-11-28 16:38 Joonas Niilola
2023-11-28 16:38 Joonas Niilola
2023-11-10 9:16 Joonas Niilola
2023-10-28 14:22 Yixun Lan
2023-09-23 9:50 Sam James
2023-09-23 9:50 Sam James
2023-09-23 9:50 Sam James
2023-09-23 9:50 Sam James
2023-07-18 19:15 Sam James
2023-07-18 19:15 Sam James
2023-07-18 19:15 Sam James
2023-04-25 0:35 Sam James
2023-04-19 17:50 Matthew Smith
2023-04-19 17:50 Matthew Smith
2023-02-17 5:14 Sam James
2023-02-17 5:14 Sam James
2023-02-17 5:14 Sam James
2023-02-08 23:54 Marek Szuba
2023-01-27 7:46 Joonas Niilola
2022-11-06 8:53 Matthew Smith
2022-11-06 8:53 Matthew Smith
2022-11-06 5:43 Sam James
2022-11-05 9:10 Matthew Smith
2022-08-25 10:33 Matthew Smith
2022-06-21 20:44 Sam James
2022-06-10 7:52 Sam James
2022-06-10 7:51 Sam James
2022-03-25 11:03 Joonas Niilola
2022-03-21 23:42 Sam James
2022-02-07 21:56 Ionen Wolkens
2022-01-21 19:11 Sam James
2021-12-27 1:08 Sam James
2021-12-04 11:31 Joonas Niilola
2021-12-04 11:31 Joonas Niilola
2021-11-29 2:01 Sam James
2021-11-29 1:58 Sam James
2021-11-23 17:27 Sam James
2021-11-23 17:16 Sam James
2021-11-23 17:15 Sam James
2021-11-23 17:15 Sam James
2021-11-23 17:15 Sam James
2021-11-17 10:54 Joonas Niilola
2021-06-04 23:22 Sam James
2021-02-22 18:57 Sam James
2021-01-18 10:14 David Seifert
2021-01-11 10:27 Alexey Shvetsov
2020-11-19 10:22 Joonas Niilola
2020-11-19 10:22 Joonas Niilola
2020-10-11 9:30 Joonas Niilola
2020-06-06 17:47 Alexey Shvetsov
2020-06-06 17:47 Alexey Shvetsov
2020-05-14 10:36 Alexey Shvetsov
2019-12-17 18:14 Joonas Niilola
2019-08-10 11:15 Joonas Niilola
2019-06-04 12:47 Virgil Dupras
2019-04-07 16:53 Alexey Shvetsov
2019-01-02 16:51 Amy Liffey
2018-09-07 3:03 Virgil Dupras
2018-09-07 3:03 Virgil Dupras
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=1662647584.29883d3eae6de25f04a39778f00ec71d1060a8f2.ago@gentoo \
--to=ago@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