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:55:31 +0100 [thread overview]
Message-ID: <56459773.4040908@ipfire.org> (raw)
In-Reply-To: <56456B82.6090405@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]
Here it is...
[root(a)ipfire ~]# find / -name sendmail
/usr/sbin/sendmail
/usr/share/logwatch/scripts/services/sendmail
[root(a)ipfire ~]# ls -ablph /usr/sbin/sendmail
lrwxrwxrwx 1 root root 26 Nov 11 01:10 /usr/sbin/sendmail ->
/etc/alternatives/sendmail
[root(a)ipfire ~]# ls /etc/alternatives
ls: cannot access /etc/alternatives: No such file or directory
[root(a)ipfire ~]#
- Daniel
Am 13.11.2015 um 05:48 schrieb R. W. Rodolico:
> I ran a test on my machine. Daniel, can you verify the following happens
> on yours also?
>
> [root(a)dd-router httpd]# find / -name sendmail
> /usr/share/logwatch/scripts/services/sendmail
> /usr/sbin/sendmail
>
> [root(a)dd-router httpd]# ls -ablph /usr/sbin/sendmail
> lrwxrwxrwx 1 root root 26 Nov 10 18:10 /usr/sbin/sendmail ->
> /etc/alternatives/sendmail
>
> [root(a)dd-router httpd]# ls /etc/alternatives
> ls: cannot access /etc/alternatives: No such file or directory
>
> basically, /usr/sbin/sendmail is a symbolic link to
> /etc/alternatives/sendmail, and /etc/alternatives does not exist.
>
> Rod
>
> On 11/12/2015 09:27 AM, 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.
>>
>> Is there someone else with that problem?
>>
>> - Daniel
>>
>> 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
next prev parent reply other threads:[~2015-11-13 7:55 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
2015-11-13 4:48 ` R. W. Rodolico
2015-11-13 7:55 ` Daniel Weismüller [this message]
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=56459773.4040908@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