From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-calculators/bc-gh/
Date: Sat, 19 Nov 2022 06:04:19 +0000 (UTC) [thread overview]
Message-ID: <1668837804.90ba515866bc943a546856ea028ee843374e98ca.ionen@gentoo> (raw)
commit: 90ba515866bc943a546856ea028ee843374e98ca
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 19 05:59:04 2022 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Sat Nov 19 06:03:24 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=90ba5158
sci-calculators/bc-gh: revbump for pre-strip fix
Not super important, but people could be missing e.g. splitdebug,
and it's quick to build.
Bug: https://bugs.gentoo.org/881779
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
sci-calculators/bc-gh/{bc-gh-6.1.1.ebuild => bc-gh-6.1.1-r1.ebuild} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/sci-calculators/bc-gh/bc-gh-6.1.1.ebuild b/sci-calculators/bc-gh/bc-gh-6.1.1-r1.ebuild
similarity index 100%
rename from sci-calculators/bc-gh/bc-gh-6.1.1.ebuild
rename to sci-calculators/bc-gh/bc-gh-6.1.1-r1.ebuild
next reply other threads:[~2022-11-19 6:04 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 6:04 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-19 23:54 [gentoo-commits] repo/gentoo:master commit in: sci-calculators/bc-gh/ Eli Schwartz
2024-09-02 5:08 Sam James
2024-08-23 4:10 Eli Schwartz
2024-08-23 4:10 Eli Schwartz
2024-07-08 3:19 Eli Schwartz
2024-02-28 2:32 Ionen Wolkens
2024-02-12 13:05 Sam James
2024-02-12 13:05 Sam James
2024-02-12 8:55 Sam James
2024-02-12 8:55 Sam James
2024-02-12 8:55 Sam James
2024-02-12 8:55 Sam James
2024-02-12 8:55 Sam James
2024-01-10 13:12 Andrew Ammerlaan
2024-01-10 13:12 Andrew Ammerlaan
2023-10-27 8:17 Andrew Ammerlaan
2023-10-01 7:34 Sam James
2023-10-01 7:34 Sam James
2023-09-22 6:51 Arthur Zamarin
2023-06-04 3:47 Sam James
2023-06-04 3:47 Sam James
2023-06-04 3:47 Sam James
2023-04-16 7:18 Sam James
2023-04-16 6:56 Sam James
2023-04-16 6:56 Sam James
2023-04-16 6:56 Sam James
2023-04-16 6:56 Sam James
2023-04-16 6:56 Sam James
2023-04-16 6:41 Joonas Niilola
2023-04-16 6:41 Joonas Niilola
2023-03-19 3:22 Sam James
2023-03-10 6:53 Sam James
2023-03-10 6:53 Sam James
2023-02-28 5:34 Sam James
2023-02-19 19:56 Sam James
2023-02-13 3:41 Matt Turner
2023-02-01 7:27 Sam James
2023-01-01 21:10 Sam James
2023-01-01 21:10 Sam James
2022-12-28 0:33 Sam James
2022-12-27 19:53 Sam James
2022-12-27 19:45 Sam James
2022-12-27 13:40 Sam James
2022-12-27 11:31 Sam James
2022-12-18 11:45 James Le Cuirot
2022-12-18 1:50 Yixun Lan
2022-12-16 21:19 Arthur Zamarin
2022-12-16 21:19 Arthur Zamarin
2022-12-16 21:19 Arthur Zamarin
2022-12-16 18:26 Arthur Zamarin
2022-11-19 6:04 Ionen Wolkens
2022-11-18 8:17 Joonas Niilola
2022-06-24 13:04 Andrew Ammerlaan
2022-06-24 13:04 Andrew Ammerlaan
2021-11-28 0:20 Ionen Wolkens
2021-11-10 10:59 Ionen Wolkens
2021-11-10 10:59 Ionen Wolkens
2021-10-19 3:04 Ionen Wolkens
2021-08-10 9:51 Ionen Wolkens
2021-06-02 12:59 Joonas Niilola
2021-06-02 12:59 Joonas Niilola
2021-05-04 13:30 Joonas Niilola
2021-03-19 7:35 Joonas Niilola
2021-03-19 7:35 Joonas Niilola
2021-03-05 16:18 Joonas Niilola
2021-03-04 14:09 Joonas Niilola
2021-03-04 14:09 Joonas Niilola
2021-02-22 14:47 Joonas Niilola
2021-02-10 14:55 Joonas Niilola
2020-12-09 9:42 Joonas Niilola
2020-12-09 9:42 Joonas Niilola
2020-11-03 9:17 Joonas Niilola
2020-10-13 12:06 Joonas Niilola
2020-10-13 12:06 Joonas Niilola
2020-08-21 7:15 Joonas Niilola
2020-08-11 8:35 Sam James
2020-07-20 12:33 Joonas Niilola
2020-05-17 16:42 Joonas Niilola
2020-05-17 16:42 Joonas Niilola
2020-05-05 8:47 Joonas Niilola
2020-04-16 8:11 Joonas Niilola
2020-04-16 8:11 Joonas Niilola
2020-04-14 8:35 Joonas Niilola
2020-02-20 13:27 Joonas Niilola
2019-11-28 16:34 Joonas Niilola
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=1668837804.90ba515866bc943a546856ea028ee843374e98ca.ionen@gentoo \
--to=ionen@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