From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016
Date: Sat, 24 Dec 2016 16:38:06 +0200 [thread overview]
Message-ID: <1482590286.26277.0.camel@gentoo.org> (raw)
In-Reply-To: <CAGDaZ_oX4j6+T_sJsFf1xQ1dKFOaEtheOFoH8KJCCpbsTQ_iBw@mail.gmail.com>
Ühel kenal päeval, L, 24.12.2016 kell 02:29, kirjutas Raymond Jennings:
> I hope this isn't a stupid question...but can we safely assume that
> all such google code SRC_URI's have *already* been mirrored?
>
> If I understand the mirrors correctly, they serve as a sort of cache
> of sorts of upstream distfile sources. Is there such a thing as a
> "cache miss" that could lead to a 404 if the mirrors themselves have
> to fetch from a dead upstream they've never fetched from before?
https://devmanual.gentoo.org/general-concepts/mirrors/
next prev parent reply other threads:[~2016-12-24 14:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 23:54 [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016 Jonas Stein
2016-11-05 0:20 ` Rich Freeman
2016-11-05 0:23 ` M. J. Everitt
2016-11-05 0:30 ` M. J. Everitt
2016-11-05 1:20 ` Rich Freeman
2016-11-05 1:29 ` M. J. Everitt
2016-11-05 1:21 ` Jonas Stein
2016-11-05 1:36 ` Jonas Stein
2016-11-05 3:09 ` Mike Gilbert
2016-11-05 4:45 ` Kent Fredric
2016-11-05 4:51 ` M. J. Everitt
2016-11-06 0:16 ` Robin H. Johnson
2016-12-25 1:13 ` Gokturk Yuksek
2016-12-25 5:54 ` Daniel Campbell
2016-11-05 7:38 ` Paweł Hajdan, Jr.
2016-11-05 7:47 ` Michał Górny
2016-12-20 22:57 ` Jonas Stein
2016-12-21 8:42 ` Gokturk Yuksek
2016-12-21 12:41 ` Kent Fredric
2016-12-21 20:54 ` Andreas K. Huettel
2016-12-24 10:29 ` Raymond Jennings
2016-12-24 14:38 ` Mart Raudsepp [this message]
2016-11-05 11:05 ` Sergei Trofimovich
2016-12-20 22:35 ` Jonas Stein
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=1482590286.26277.0.camel@gentoo.org \
--to=leio@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