public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-dns/coredns/
Date: Mon, 25 Mar 2024 03:41:29 +0000 (UTC)	[thread overview]
Message-ID: <1711338042.ee1b98b319fe39920e33b11dd291261118176305.zmedico@gentoo> (raw)

commit:     ee1b98b319fe39920e33b11dd291261118176305
Author:     Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 25 03:35:36 2024 +0000
Commit:     Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Mon Mar 25 03:40:42 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ee1b98b3

net-dns/coredns: update 1.11.2 SRC_URI

Somehow the v1.11.2 tag went missing upstream, so refer to
a previously fetched copy in SRC_URI.

Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>

 net-dns/coredns/coredns-1.11.2.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/net-dns/coredns/coredns-1.11.2.ebuild b/net-dns/coredns/coredns-1.11.2.ebuild
index f565442b2546..89d7e8f271e2 100644
--- a/net-dns/coredns/coredns-1.11.2.ebuild
+++ b/net-dns/coredns/coredns-1.11.2.ebuild
@@ -12,7 +12,9 @@ if [[ ${PV} == 9999* ]]; then
 	inherit git-r3
 	EGIT_REPO_URI="https://github.com/coredns/coredns.git"
 else
-	SRC_URI="https://github.com/${PN}/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+	#SRC_URI="https://github.com/${PN}/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+	# The v1.11.2 tag went missing upstream, so use a previously fetched copy.
+	SRC_URI="https://dev.gentoo.org/~zmedico/dist/${P}.tar.gz"
 	SRC_URI+=" https://dev.gentoo.org/~zmedico/dist/${P}-deps.tar.xz"
 	KEYWORDS="amd64"
 fi


             reply	other threads:[~2024-03-25  3:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25  3:41 Zac Medico [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-01 19:38 [gentoo-commits] repo/gentoo:master commit in: net-dns/coredns/ Zac Medico
2024-11-14  0:55 Zac Medico
2024-05-12 21:14 Zac Medico
2024-05-12 21:14 Zac Medico
2024-05-12 21:06 Zac Medico
2024-05-11 15:16 Arthur Zamarin
2024-03-25  4:20 Zac Medico
2024-03-24 23:21 Zac Medico
2024-03-15 15:37 Arthur Zamarin
2024-02-28  3:05 Zac Medico
2024-02-28  3:05 Zac Medico
2024-02-28  3:05 Zac Medico
2023-11-10 16:35 Zac Medico
2023-11-10 16:35 Zac Medico
2023-05-01 13:36 Sam James
2023-04-11  4:36 Zac Medico
2022-10-18  2:48 Zac Medico
2022-10-18  2:48 Zac Medico
2022-05-28 17:42 Zac Medico
2022-05-16  4:02 Zac Medico
2022-05-16  4:02 Zac Medico
2021-09-01 16:42 William Hubbs
2021-06-29 16:22 Mike Gilbert
2021-04-04 14:41 Zac Medico
2021-03-24  6:19 Zac Medico
2021-03-21  1:04 Zac Medico
2020-07-22  7:48 Joonas Niilola
2020-05-04 19:26 William Hubbs
2020-04-29 11:40 Joonas Niilola
2019-01-15 19:26 Manuel Rüger
2019-01-15 19:26 Manuel Rüger
2018-08-21 20:29 Manuel Rüger
2018-07-24 13:52 Manuel Rüger
2018-04-01  1:25 Manuel Rüger
2018-04-01  1:25 Manuel Rüger
2018-02-21 15:04 Manuel Rüger
2017-10-27 11:37 Manuel Rüger
2017-10-27 11:37 Manuel Rüger
2017-08-12 12:25 Manuel Rüger
2017-08-06 21:31 Manuel Rüger
2017-08-06 21:31 Manuel Rüger
2017-07-19 15:06 Manuel Rüger
2017-03-22 14:42 Manuel Rüger

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=1711338042.ee1b98b319fe39920e33b11dd291261118176305.zmedico@gentoo \
    --to=zmedico@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