From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: FYI: patchwork.ipfire.org returns "500 internal server error"
Date: Wed, 04 Oct 2017 20:54:56 +0100 [thread overview]
Message-ID: <1507146896.433.29.camel@ipfire.org> (raw)
In-Reply-To: <20171004214835.26f6b60e.peter.mueller@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
Hi,
yes, I am updating some parts of our infrastructure.
Unfortunately these web applications are all quite fragile so that every time
the OS is updated, the dependencies don't match any more and the applications
won't run. It's horrible :(
Hold tight. I will try to get this fixed as soon as possible.
Best,
-Michael
On Wed, 2017-10-04 at 21:48 +0200, Peter Müller wrote:
> Hello Michael, hello list (if interested),
>
> http://patchwork.ipfire.org/ returns a "500 internal server error"
> message here.
>
> Just thought you might want to know. :-)
>
> Best regards,
> Peter Müller
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-04 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 19:48 Peter Müller
2017-10-04 19:54 ` Michael Tremer [this message]
2017-10-04 20:30 ` Michael Tremer
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=1507146896.433.29.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