From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 134 test
Date: Wed, 03 Jul 2019 11:08:23 +0200
Message-ID: <4c3de7e941379419bfbc9ae60f7ec24e@ipfire.org>
In-Reply-To: <001d01d52c79$00f13390$02d39ab0$@net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2706459606601489240=="
List-Id: <development.lists.ipfire.org>

--===============2706459606601489240==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On 2019-06-27 01:43, Mentalic wrote:
> Core 134 Geoip had the same string of geoip boot errors as Core update
> 133 does. Tried the  missing folder fix I found for core update 133
> but if fails on to fix core update 134. So somewhat different problem.
> 
If you have installed core134 before the kernel update to 4.14.131 the 
geoip modules was still missing and the old 4.14.121 modules from older 
cores will not work with 4.14.129... so reinstall the update by setting 
/opt/pakfire/db/core/mine back to 133

--===============2706459606601489240==--