From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: SourceForge URLs changed
Date: Sun, 17 Jul 2016 17:50:56 -0400 [thread overview]
Message-ID: <20160717215056.GA10792@jasmine> (raw)
In-Reply-To: <87eg6s0wqf.fsf@elephly.net>
On Sun, Jul 17, 2016 at 11:40:24PM +0200, Ricardo Wurmus wrote:
> I read claims on the #guix IRC channel that the URLs appear to change
> over time. Has this been confirmed yet? It would be sad if you or
> others waste time on changing the URLs only to have them change yet
> again.
I claim that claim ;)
I think I was mistaken.
Our requests were being redirected from HTTP -> HTTPS, so I changed the
mirror URLs to use HTTPS, and then forgot I'd made that change. [0]
Between tests with `curl`, `guix download`, and `guix lint --checker
source`, I became confused and made that claim.
But, things started to work when I reverted the mirror URL change and
began updating the various package source URLs.
Hopefully SourceForge does not change the URLs again. That would be
extremely annoying.
[0] This redirection only seems to occur for "bad" URLs.
next prev parent reply other threads:[~2016-07-17 21:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 23:00 SourceForge URLs changed Ludovic Courtès
2016-07-12 23:37 ` Alex Griffin
2016-07-13 10:16 ` Ludovic Courtès
2016-07-15 15:28 ` Alex Griffin
2016-07-15 17:58 ` Leo Famulari
2016-07-15 18:15 ` Alex Griffin
2016-07-16 12:17 ` Ludovic Courtès
2016-07-16 2:58 ` Leo Famulari
2016-07-16 3:00 ` Leo Famulari
2016-07-17 20:58 ` Leo Famulari
2016-07-17 21:40 ` Ricardo Wurmus
2016-07-17 21:50 ` Leo Famulari [this message]
2016-07-18 18:30 ` Alex Griffin
2016-07-18 22:21 ` Leo Famulari
2016-07-21 14:33 ` Leo Famulari
2016-07-21 15:32 ` Andreas Enge
2016-07-21 16:34 ` Ludovic Courtès
2016-07-21 20:41 ` Alex Griffin
2016-07-21 22:13 ` Leo Famulari
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=20160717215056.GA10792@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.