From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/confuse/
Date: Tue, 19 Dec 2017 10:35:47 +0000 (UTC) [thread overview]
Message-ID: <1513679730.676b5b93230159f7e5016755b1843227060fdba9.jer@gentoo> (raw)
commit: 676b5b93230159f7e5016755b1843227060fdba9
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 19 10:35:30 2017 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Tue Dec 19 10:35:30 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=676b5b93
dev-libs/confuse: Update HOMEPAGE.
Package-Manager: Portage-2.3.19, Repoman-2.3.6
dev-libs/confuse/confuse-3.2.1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-libs/confuse/confuse-3.2.1.ebuild b/dev-libs/confuse/confuse-3.2.1.ebuild
index 0dfcf2c0b2f..958f49730e8 100644
--- a/dev-libs/confuse/confuse-3.2.1.ebuild
+++ b/dev-libs/confuse/confuse-3.2.1.ebuild
@@ -6,8 +6,8 @@ EAPI=6
inherit eutils multilib-minimal
DESCRIPTION="a configuration file parser library"
-HOMEPAGE="http://www.nongnu.org/confuse/"
-SRC_URI="https://github.com/martinh/libconfuse/releases/download/v${PV}/${P}.tar.xz"
+HOMEPAGE="https://github.com/martinh/libconfuse"
+SRC_URI="${HOMEPAGE}/releases/download/v${PV}/${P}.tar.xz"
LICENSE="ISC"
SLOT="0/2.0.0"
next reply other threads:[~2017-12-19 10:35 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 10:35 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 20:49 [gentoo-commits] repo/gentoo:master commit in: dev-libs/confuse/ Petr Vaněk
2023-06-04 16:19 Arthur Zamarin
2023-04-19 5:28 Sam James
2023-04-19 5:28 Sam James
2023-04-19 5:28 Sam James
2023-04-19 5:28 Sam James
2023-04-19 5:28 Sam James
2023-04-19 5:28 Sam James
2023-04-19 5:28 Sam James
2023-02-26 19:37 Arthur Zamarin
2023-02-24 16:59 Sam James
2023-02-24 16:58 Arthur Zamarin
2023-02-24 16:58 Arthur Zamarin
2023-02-24 16:30 Arthur Zamarin
2023-02-24 16:25 Arthur Zamarin
2023-02-24 16:23 Arthur Zamarin
2023-02-14 11:19 Sergey Popov
2023-01-11 13:39 Sam James
2023-01-10 19:20 Mike Frysinger
2021-07-16 1:31 Yixun Lan
2021-01-11 12:07 Sergey Popov
2021-01-05 20:51 Sam James
2021-01-03 12:10 Sergei Trofimovich
2021-01-03 11:51 Sergei Trofimovich
2021-01-03 9:14 Sam James
2020-12-29 21:26 Sam James
2020-12-29 21:24 Sam James
2020-12-27 22:39 Sam James
2020-11-02 9:47 Sam James
2020-10-20 7:04 Sergei Trofimovich
2020-10-20 7:02 Sergei Trofimovich
2020-10-20 6:57 Sergei Trofimovich
2020-10-20 6:51 Sergei Trofimovich
2020-10-19 0:13 Sam James
2020-10-18 18:51 Thomas Deutschmann
2020-10-17 23:49 Sam James
2020-10-16 8:05 Sergey Popov
2019-08-15 9:30 Sergey Popov
2018-11-26 10:19 Jeroen Roovers
2018-11-26 10:18 Jeroen Roovers
2017-11-21 9:54 Jeroen Roovers
2017-11-21 9:53 Jeroen Roovers
2017-08-10 12:46 Jeroen Roovers
2017-08-10 12:46 Jeroen Roovers
2017-05-24 14:47 Jeroen Roovers
2017-05-18 22:38 Michael Weber
2017-05-17 14:45 Manuel Rüger
2017-01-29 16:07 Fabian Groffen
2016-12-30 11:12 Agostino Sarubbo
2016-12-28 11:12 Sergey Popov
2016-10-05 18:54 Markus Meier
2016-10-01 14:16 Jeroen Roovers
2016-09-24 13:47 Agostino Sarubbo
2016-09-22 8:36 Tobias Klausmann
2016-06-03 8:38 Jeroen Roovers
2016-01-27 15:11 Sergey Popov
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=1513679730.676b5b93230159f7e5016755b1843227060fdba9.jer@gentoo \
--to=jer@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