public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Daniel Weismüller" <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 95 release schedule
Date: Fri, 13 Nov 2015 08:46:53 +0100	[thread overview]
Message-ID: <5645956D.5040901@ipfire.org> (raw)
In-Reply-To: <1447355688.2699.132.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]

Hi Michael

As usual you're right. ;)

Here is what i found in /var/log/httpd/error_log

[Thu Nov 12 16:18:31 2015] [error] [client 192.168.55.108] can't exec : 
No such file or directory, referer: 
https://192.168.55.1:444/cgi-bin/mail.cgi
[Thu Nov 12 16:18:31 2015] [error] [client 192.168.55.108] error closing 
:  (exit 512), referer: https://192.168.55.1:444/cgi-bin/mail.cgi

I think there is already a bug for it.  See here 
https://bugzilla.ipfire.org/show_bug.cgi?id=10932

It is already closed but it seems that it is not fixed. So I reopened it.

- Daniel

Am 12.11.2015 um 20:14 schrieb Michael Tremer:
> Hi,
>
> On Thu, 2015-11-12 at 16:27 +0100, Daniel Weismüller wrote:
>> Hi,
>>
>> Core Update 95 installed succesfully without any abnormalities.
>>
>> If I try to send a testmail via the mail.cgi I'll get a blank white
>> screen and nothing else.
>> No error, no logentry and no mail.
> There must be something in the logs. Could you please check what the
> reason is and if applicable open a bug? You can probably assign this to
> Alex.
>
>> Is there someone else with that problem?
>>
>> - Daniel
> -Michael
>
>> Am 11.11.2015 um 00:26 schrieb Michael Tremer:
>>> Hello,
>>>
>>> this is just a short information about the upcoming Core Update.
>>>
>>> Core Update 95 has been branched and will only accept bug fixes. It
>>> will appear on the testing tree shortly and I *strongly* recommend
>>> to
>>> install the update as soon as possible and to give it a good test.
>>>
>>> Arne will be away for the next week and some time after that so
>>> that it
>>> would be very convenient if as many bugs can be found as possible
>>> before the end of this week.
>>>
>>> We would like to release this update in a bit over two weeks.
>>>
>>> See the Git repository for changes. A summarized changelog will
>>> follow
>>> on the IPFire Planet as usual.
>>>
>>> Best,
>>> -Michael


  parent reply	other threads:[~2015-11-13  7:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 23:26 Michael Tremer
2015-11-12 15:27 ` Daniel Weismüller
2015-11-12 19:14   ` Michael Tremer
2015-11-13  4:05     ` R. W. Rodolico
2015-11-13  7:53       ` Daniel Weismüller
2015-11-13  7:46     ` Daniel Weismüller [this message]
2015-11-13  4:48   ` R. W. Rodolico
2015-11-13  7:55     ` Daniel Weismüller
2015-11-13  8:57       ` Alexander Marx
2015-11-15 20:34         ` R. W. Rodolico
2015-11-13 16:39 ` Jan Lentfer

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=5645956D.5040901@ipfire.org \
    --to=daniel.weismueller@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