From: Leo Famulari <leo@famulari.name>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: SourceForge URLs changed
Date: Fri, 15 Jul 2016 13:58:19 -0400 [thread overview]
Message-ID: <20160715175819.GA19508@jasmine> (raw)
In-Reply-To: <1468596493.1316361.667333481.4DA63202@webmail.messagingengine.com>
On Fri, Jul 15, 2016 at 10:28:13AM -0500, Alex Griffin wrote:
> On Wed, Jul 13, 2016, at 05:16 AM, Ludovic Courtès wrote:
> > Alex Griffin <a@ajgrf.com> skribis:
> > > Their Twitter feed[1] says that they're investigating issues at the
> > > moment, so it's possible that all we need to do is wait.
> >
> > OK, we’ll see.
>
> So it has been a few days now, and it looks like I was probably wrong.
> I'm a little baffled that I couldn't find any other free software
> communities talking about this either, since I would have guessed a
> disruptive change like this would have affected other distros that
> automate source downloads (like NixOS, Arch Linux, Gentoo, etc.)
I contacted SourceForge to ask about this. They said that they did have
an outage that lasted for ~23 hours but that, otherwise, there has been
no change to the URLs from which they serve things.
Is anyone still noticing problems on our end? If so, can you give some
details that I can pass on to SourceForge?
next prev parent reply other threads:[~2016-07-15 17:58 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 [this message]
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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160715175819.GA19508@jasmine \
--to=leo@famulari.name \
--cc=a@ajgrf.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).