public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.17 - Core Update 91 release schedule
Date: Sat, 13 Jun 2015 07:51:59 +0200	[thread overview]
Message-ID: <1434174719.1758.4.camel@ipfire.org> (raw)
In-Reply-To: <2529f05ce55c38f4c70d845553dd499b@mail01.ipfire.org>

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

Hello Arne,

just installed the new core update a couple of minutes ago.

I did some quick tests, hostapd now is starting again without any
problems and all of my VPN connections got established.

I will do some more testing and reporting if there are still any issues.

-Stefan
> Hello,
> 
> the OpenSSL Team has released a hotfix update for an ABI breakage short 
> after uploading the build to testing so we are forced to update the 
> core91 package.
> If you have installed core91 already please check the OpenSSL version. 
> If this is older than 1.0.2c please reinstall core91 by resetting
> /opt/pakfire/db/core/mine to 90 and upgrade again.
> 
> This hotfix will fix the hostapd and maybee more problems.
> 
> Arne
> 


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-13  5:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  8:51 Michael Tremer
2015-06-11 15:55 ` Rod Rodolico
2015-06-11 20:39   ` Michael Tremer
2015-06-12 15:15     ` Michael Tremer
2015-06-13 13:20       ` Arne Fitzenreiter
2015-06-12 20:42     ` Arne Fitzenreiter
2015-06-13  5:51       ` Stefan Schantl [this message]
     [not found] <6A691F9C-E1A7-480E-8D1E-12A37DD544C8@web.de>
2015-06-11  9:46 ` Michael Tremer
     [not found] <CAFHX57dDn27REQhoqBysqwZKCmTB72fxXKFtaFHPcqTW-wtqOg@mail.gmail.com>
2015-06-11 11:52 ` Michael Tremer
2015-06-12 16:10 Paul Simmons

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=1434174719.1758.4.camel@ipfire.org \
    --to=stefan.schantl@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