From: WhyTea <whytea@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Development] Core Update 57
Date: Tue, 21 Feb 2012 20:31:31 +0100 [thread overview]
Message-ID: <4F43F113.2020608@ipfire.org> (raw)
In-Reply-To: <1329846093.1070.26.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Installed Core 57 no problems with installing and no problems after reboot.
Am 21.02.2012 18:41, schrieb Michael Tremer:
> On Tue, 2012-02-21 at 16:53 +0000, Arne Fitzenreiter wrote:
>> The vpn update was moved to core58 because the update has still bugs
>> (not deleting routes). Libpng also comes with core58 because Michael and
>> i has forgotten it to pull it to the master branch before build.
> Oops. I just checked in some new bug reports regarding the update of
> Strongswan. No security fixes, but feature enhancements.
> https://bugzilla.ipfire.org/show_bug.cgi?id=10037
>
>
> Core Update 57 is up and running since a couple of days now and I have
> found no regressions. I also don't expect to find any.
>
> Michael
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
--
You need a firewall?
Easy to use? Powerful? Modular? For free?
www.ipfire.org
An Open Source Firewall Solution
next prev parent reply other threads:[~2012-02-21 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 10:21 Michael Tremer
2012-02-21 11:19 ` Daniel Weismüller
2012-02-21 16:53 ` Arne Fitzenreiter
2012-02-21 17:41 ` Michael Tremer
2012-02-21 19:31 ` WhyTea [this message]
[not found] <4F478D00.3080406@ipfire.org>
2012-02-24 20:06 ` Michael Tremer
2012-02-25 18:59 ` 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=4F43F113.2020608@ipfire.org \
--to=whytea@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