From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/flex/
Date: Mon, 17 May 2021 22:36:06 +0000 (UTC) [thread overview]
Message-ID: <1621290866.714bfa983da16c9ab6cb10ce87cc135846e9ce61.sam@gentoo> (raw)
commit: 714bfa983da16c9ab6cb10ce87cc135846e9ce61
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun May 16 23:06:05 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon May 17 22:34:26 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=714bfa98
sys-devel/flex: drop dead sourceforge HOMEPAGE
Still keeping the remote-id for the (outdated)
site which is referenced in the README on github, though.
Closes: https://bugs.gentoo.org/708496
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-devel/flex/flex-2.6.4-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-devel/flex/flex-2.6.4-r1.ebuild b/sys-devel/flex/flex-2.6.4-r1.ebuild
index 9c73a8e03c3..592b017eec1 100644
--- a/sys-devel/flex/flex-2.6.4-r1.ebuild
+++ b/sys-devel/flex/flex-2.6.4-r1.ebuild
@@ -6,7 +6,7 @@ EAPI=7
inherit flag-o-matic libtool multilib-minimal toolchain-funcs
DESCRIPTION="The Fast Lexical Analyzer"
-HOMEPAGE="https://flex.sourceforge.net/ https://github.com/westes/flex"
+HOMEPAGE="https://github.com/westes/flex"
SRC_URI="https://github.com/westes/${PN}/releases/download/v${PV}/${P}.tar.gz"
LICENSE="FLEX"
next reply other threads:[~2021-05-17 22:36 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 22:36 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-06 8:46 [gentoo-commits] repo/gentoo:master commit in: sys-devel/flex/ Sam James
2024-03-04 11:09 Sam James
2023-04-22 12:13 Sam James
2023-04-07 6:56 Sam James
2023-04-07 6:38 Sam James
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-04-07 5:07 Sam James
2023-02-20 13:49 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-02 21:16 Sam James
2022-11-18 7:50 Arthur Zamarin
2022-11-18 4:54 Sam James
2022-11-18 4:54 Sam James
2022-11-18 4:54 Sam James
2022-11-18 4:54 Sam James
2022-11-18 4:54 Sam James
2022-11-18 4:54 Sam James
2022-11-18 4:26 Sam James
2022-10-28 2:02 Sam James
2022-10-28 1:54 Sam James
2022-09-26 4:16 Arthur Zamarin
2022-09-25 7:21 Arthur Zamarin
2022-09-25 6:25 Agostino Sarubbo
2022-09-25 6:24 Agostino Sarubbo
2022-09-25 4:43 Sam James
2022-09-25 4:43 Sam James
2022-09-25 4:35 Sam James
2022-09-25 4:35 Sam James
2022-06-17 12:11 Sam James
2021-03-23 20:58 Lars Wendler
2021-01-06 15:32 Fabian Groffen
2020-12-27 18:18 Fabian Groffen
2020-06-13 14:58 Mike Gilbert
2020-05-04 17:36 Thomas Deutschmann
2020-02-15 10:03 David Seifert
2019-05-04 19:51 Andreas K. Hüttel
2018-04-21 9:29 Mikle Kolyada
2018-04-14 21:33 Mart Raudsepp
2017-11-25 11:55 Markus Meier
2017-11-02 14:33 Tobias Klausmann
2017-10-24 19:23 Sergei Trofimovich
2017-10-24 18:56 Sergei Trofimovich
2017-10-23 20:51 Sergei Trofimovich
2017-10-23 18:42 Thomas Deutschmann
2017-10-23 13:11 Manuel Rüger
2017-09-09 8:28 Sergei Trofimovich
2017-05-07 18:55 Lars Wendler
2017-03-21 15:46 Michael Haubenwallner
2017-03-19 10:13 Fabian Groffen
2017-03-19 10:10 Fabian Groffen
2017-01-17 20:38 Mike Frysinger
2017-01-09 13:52 Jeroen Roovers
2016-12-30 21:18 Lars Wendler
2016-12-22 9:34 Agostino Sarubbo
2016-12-20 9:44 Agostino Sarubbo
2016-12-19 15:12 Agostino Sarubbo
2016-12-19 14:35 Agostino Sarubbo
2016-12-02 14:21 Tobias Klausmann
2016-11-30 19:34 Markus Meier
2016-11-29 11:23 Agostino Sarubbo
2016-11-29 11:22 Agostino Sarubbo
2016-10-26 8:06 Lars Wendler
2016-10-26 8:06 Lars Wendler
2016-04-02 21:55 Mike Frysinger
2015-12-20 18:04 Mike Frysinger
2015-11-23 11:02 Lars Wendler
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=1621290866.714bfa983da16c9ab6cb10ce87cc135846e9ce61.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