Re: IPFire 2.17 - Core Update 91 release schedule

[Michael Tremer <michael.tremer@ipfire.org>]

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

That looks fine what you did. We just have not built and uploaded the
update yet.

As the email says we are waiting for the OpenSSL update and will need
some time to do the build.

-Michael

On Thu, 2015-06-11 at 12:44 +0200, Jacques Hylkema wrote:
> Hi,
> 
> 
> I tried to follow the guide, but it doesn't work:
> 
> 
> [root(a)fw-test ~]# cat /opt/pakfire/etc/pakfire.conf
> ...
> $version = "2.17.1";
> 
> 
> $mainserver = "pakfire.ipfire.org";
> 
> 
> $cachedir = "/opt/pakfire/cache";
> $dbdir = "/opt/pakfire/db";
> $coredir = "/opt/pakfire/db/core";
> $tmpdir = "/opt/pakfire/tmp";
> $logdir = "/opt/pakfire/logs";
> ...
> 
> 
> 
> 
> [root(a)fw-test ~]# pakfire update --force
> 
> server-list.db       100.00% |=============================>|   312.00
> B
> packages_list.db     100.00% |=============================>|    3.52
> KB
> core-list.db         100.00% |=============================>|   248.00
> B
> [root(a)fw-test ~]# pakfire upgrade --force
> CORE ERROR: No new upgrades available. You are on release 90.
> [root(a)fw-test ~]# cat /opt/pakfire/db/core/mine
> 90
> [root(a)fw-test ~]#
> 
> 
> 
> Met vriendelijke groet,
> With kind regards,
> 
> Jacques Hylkema
> ICT Manager
> Tel +31 (0)342-407040
> E-mail j.hylkema(a)intronics.nl
> 
> LinkedIn
> 
> Email
> 
> Website
> 
> Intronics
> Member of the TKH-group
> Intronics
> Postbus 123, 3770
> AC
> Koolhovenstraat
> 1E
> 3772
> MT  Barneveld
> Computer
> Connectivity
> Industrial
> Connectivity
> Audio/Video
> Retail
> Tel. +31
> (0)342-407040
> Tel. +31
> (0)342-407080
> Tel. +31
> (0)342-407040
> Tel. +31
> (0)46-4269000
> Fax +31
> (0)342-412114
> sales(a)intronics.nl
> www.intronics.nl
> 
> 
> Disclaimer:
> This message (including any attachments) is confidential and may be
> privileged. If you have received it by mistake please notify the
> sender by return e-mail and delete this message from your system. Any
> unauthorised use or dissemination of this message in whole or in part
> is strictly prohibited. Please note that e-mails are susceptible to
> change. Intronics shall not be liable for the improper or incomplete
> transmission of the information contained in this communication nor
> for any delay in its receipt or damage to your system. Intronics does
> not guarantee that the integrity of this communication has been
> maintained nor that this communication is free of viruses,
> interceptions or interference.
> 
> P
> Please consider the environment
> before printing this e-mail
> 
> 
> 
> 
> 
> 
> 
> 2015-06-11 11:46 GMT+02:00 Michael Tremer <michael.tremer(a)ipfire.org>:
>         Hello,
>         
>         just follow this guide:
>         
>         http://wiki.ipfire.org/en/configuration/ipfire/pakfire/testing
>         
>         -Michael
>         
>         On Thu, 2015-06-11 at 11:44 +0200, Jan Lentfer wrote:
>         > Hi, could you shortly describe (possibly once more) how can
>         follow the testing branch instead of the stable branch? TIA
>         Jan
>         >
>         > Von meinem iPad gesendet
>         >
>         > > Am 11.06.2015 um 10:51 schrieb Michael Tremer
>         <michael.tremer(a)ipfire.org>:
>         > >
>         > > Hello,
>         > >
>         > > I just wanted to update you quickly about the upcoming
>         Core Update 91
>         > > release plan.
>         > >
>         > > There will be a new OpenSSL release at some time today
>         (Thursday) which
>         > > fixes several security vulnerabilities in this library. We
>         do not know
>         > > much about the severity of those vulnerabilities, yet, but
>         we will
>         > > release a new Core Update any ways.
>         > >
>         > > The changes that have been pushed into the next branch
>         will be released
>         > > as well with an exception of Python. The Python package
>         won't build on
>         > > some systems and due to lack of time to debug this
>         properly the Python
>         > > update has been postponed.
>         > >
>         > > As soon as the OpenSSL update is released we will start
>         the build. We
>         > > expect this to be late at night (as it has been in the
>         past) and
>         > > therefore the will be a build available Friday
>         morning/noon European
>         > > time. The ARM build will take much longer to complete
>         though.
>         > >
>         > > We will push that build to the testing tree so that as
>         many people can
>         > > help testing as possibly can.
>         > >
>         > > If everything goes well we intend to release the final
>         update 24 hours
>         > > after that - which will be Saturday some time after mid
>         day.
>         > >
>         > > Best,
>         > > -Michael
>         > >
>         > > P.S. I was asked to send a short release plan for Core
>         Updates on this
>         > > list because it is not so easy to find out what the
>         current status is
>         > > sometimes. I would like your feedback about if this is a
>         good idea and
>         > > if this is helping. I am hoping that it is helping us to
>         engage more
>         > > testers into the testing procedure of new Core Updates and
>         let you plan
>         > > some time for doing that.
> 
> 

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