From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Sources are not availible
Date: Tue, 05 Jul 2016 20:58:26 +0200 [thread overview]
Message-ID: <1467745106.19586.5.camel@ipfire.org> (raw)
In-Reply-To: <1467712896.1574.1@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
Hi,
yeah the web server had some issues with mounting all shares where this
data is stored on.
Had to mount that manually and all files are back now.
Best,
-Michael
On Tue, 2016-07-05 at 12:01 +0200, Jonatan Schlag wrote:
> Hi,
> http://source.ipfire.org
> did not work so it is not possible to download the sources to build
> IPFire.
> It seem to be a problem with the webserver because i can browse the
> directory via ssh.
>
> regards Jonatan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
parent reply other threads:[~2016-07-05 18:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1467712896.1574.1@mail01.ipfire.org>]
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=1467745106.19586.5.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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