From: 5p9 <5p9@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Guardian 2.0 Testversion 011
Date: Thu, 14 May 2015 11:15:11 +0200 [thread overview]
Message-ID: <5554679F.5050006@ipfire.org> (raw)
In-Reply-To: <1431458375.7691.11.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2873 bytes --]
Hi,
after downgrade 11er Version and update-lang-cache run my System normal.
And Guardian2 looks like good! Thx for your Work Stefan...very nice.
BG, 5p9
Am 12.05.2015 um 21:19 schrieb Stefan Schantl:
> Hi 5p9,
>
> when you have installed the guardian 2.0 - 012 version on your
> IPFire system with core update 89 you have brick your system.
>
>>> IMPORTANT: You MUST NOT install/update to the new version if
>>> you are using IPFire 2 - Core 89 or an older version!
>
> If you still have access to it, downgrade guardian to version 011
> or upgrade the system to core 90 and reinstall guardian 012
> afterwards otherwise it will be really hard to get your system
> working again.
>
> Best regards,
>
> -Stefan
>> Hi Stefan,
>>
>> thx for updateing Guardian2. I use Core89 but the installversion
>> 012 is done with internal error by update the cache lang - do
>> you need more information?
>>
>> #update-lang-cache
>>
>> update-lang-cache Can't locate Locale/Codes/Country.pm in @INC
>> (@INC contains:
>> /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi
>> /usr/lib/perl5/site_perl/5.12.3
>> /usr/lib/perl5/5.12.3/i586-linux-thread-multi
>> /usr/lib/perl5/5.12.3 .) at /var/ipfire/general-functions.pl
>> line 20. BEGIN failed--compilation aborted at
>> /var/ipfire/general-functions.pl line 20. Compilation failed in
>> require at //var/ipfire/lang.pl line 12. Compilation failed in
>> require at -e line 1.
>>
>>
>> The WUI say:
>>
>> Internal Server Error The server encountered an internal error
>> or misconfiguration and was unable to complete your request.
>> Please contact the server administrator, root(a)localhost and
>> inform them of the time the error occurred, and anything you
>> might have done that may have caused the error. More information
>> about this error may be available in the server error log.
>> Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1m PHP/5.3.27
>> Server at 192.168.XYZ.XYZ Port 444
>>
>> On 10.05.2015 10:08, Stefan Schantl wrote:
>>
>>> Hello again,
>>>
>>> as promised I recently have uploaded a new test version of
>>> guardian 2.0 (012).
>>>
>>> It mainly contains updated language and system files to pay
>>> attention to the latest development efforts of IPFire core
>>> update 90.
>>>
>>> As usual the new version can be downloaded from
>>> http://people.ipfire.org/~stevee/guardian-2.0/
>>>
>>> The installation / update works in the same way as described
>>> in the planet post:
>>> http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire
>>>
>>>
>>>
>>>
IMPORTANT: You MUST NOT install/update to the new version if you are
>>> using IPFire 2 - Core 89 or an older version!
>>>
>>> Please also create a backup of your files stored in
>>> "/var/ipfire/guardian/", otherwise the will be overwritten by
>>> the update!
>>>
>>> Best regards,
>>>
>>> -Stefan
next prev parent reply other threads:[~2015-05-14 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5551C5AC.6030909@ipfire.org>
2015-05-12 19:19 ` Stefan Schantl
2015-05-14 9:15 ` 5p9 [this message]
2015-05-28 22:32 ` 5p9
2015-05-28 23:28 ` Matthias Fischer
2015-05-28 23:40 ` 5p9
[not found] <1425131435.2685.24.camel@ipfire.org>
2015-05-10 8:08 ` Stefan Schantl
[not found] <934634537.3431881425296755846.JavaMail.root@ip-10-41-150-66.ec2.internal>
2015-03-05 18:37 ` Stefan Schantl
2015-03-02 19:51 Matthias Fischer
2015-03-02 20:20 ` Stefan Schantl
2015-03-02 20:43 ` Matthias Fischer
2015-03-02 20:59 ` Matthias Fischer
[not found] <DUB120-W2840AF412EFCF1DA7249F69C100@phx.gbl>
2015-03-02 18:35 ` Stefan Schantl
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=5554679F.5050006@ipfire.org \
--to=5p9@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