public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Inform users about the eol of i?86
Date: Mon, 29 Nov 2021 10:16:29 +0000	[thread overview]
Message-ID: <4443FD09-F63A-437B-B449-9CC5D79F9700@ipfire.org> (raw)
In-Reply-To: <4dc5a0ad-13b0-3985-1bc8-78b7ddb16378@leo-andres.de>

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

Hello,

Indeed. Good catch.

I think this would be fine without the link. We will send an announcement which people hopefully won’t miss.

@Jonatan: Are you going to resubmit this patch?

Best,
-Michael

> On 28 Nov 2021, at 20:09, Leo Hofmann <hofmann(a)leo-andres.de> wrote:
> 
> Hi Jonatan,
> 
> Am 28.11.2021 um 16:43 schrieb Jonatan Schlag:
>> The warning point to a wiki page which is currently in construction.
>> This should give us the opportunity to add further information for
>> these users even if we do not provide updates anymore.
>> 
>> Signed-off-by: Jonatan Schlag <jonatan.schlag(a)ipfire.org>
>> ---
>>  html/cgi-bin/index.cgi | 4 ++--
>>  langs/de/cgi-bin/de.pl | 1 +
>>  langs/en/cgi-bin/en.pl | 1 +
>>  3 files changed, 4 insertions(+), 2 deletions(-)
>> 
>> diff --git a/html/cgi-bin/index.cgi b/html/cgi-bin/index.cgi
>> index 948fdde55..90e2daff0 100644
>> --- a/html/cgi-bin/index.cgi
>> +++ b/html/cgi-bin/index.cgi
>> @@ -541,10 +541,10 @@ if ( ! -e "/var/ipfire/main/send_profile") {
>>  	$warnmessage .= "<li><a style='color: white;' href='fireinfo.cgi'>$Lang::tr{'fireinfo please enable'}</a></li>";
>>  }
>>  -# Legacy architecture
>> +# EOL architecture
>>  my ($sysname, $nodename, $release, $version, $machine) = &POSIX::uname();
>>  if ($machine =~ m/^i.86$/) {
>> -	$warnmessage .= "<li>$Lang::tr{'legacy architecture warning'}</li>";
>> +	$warnmessage .= "<li href='https://wiki.ipfire.org/hardware/eol-architectures'>$Lang::tr{'eol architecture warning'}</li>";
> The "href" attribute isn't officially allowed in <li> elements, this link may not work with picky browsers.
> Here you can see which elements support "href": https://www.w3schools.com/tags/att_href.asp
> 
> Best regards
> Leo
> 
>>  }
>>    # Memory usage warning
>> diff --git a/langs/de/cgi-bin/de.pl b/langs/de/cgi-bin/de.pl
>> index e350bc651..c81b28fea 100644
>> --- a/langs/de/cgi-bin/de.pl
>> +++ b/langs/de/cgi-bin/de.pl
>> @@ -989,6 +989,7 @@
>>  'enter data' => 'Geben Sie die Daten ein <br /> und klicken Sie danach auf <i>Speichern</i>.',
>>  'entropy' => 'Entropie',
>>  'entropy graphs' => 'Entropiegraphen',
>> +'eol architecture warning' => 'Sie betreiben ein IPFire System auf einer Architektur, welche nicht mehr unterstützt wird. Sie werden keine Updates mehr erhalten. Das ist ein Sicherheitsrisiko.',
>>  'err bk 1' => 'Fehler beim Erzeugen des Archivs',
>>  'err bk 10 password' => 'Fehler beim Datensicherungs-Passwort',
>>  'err bk 2 key' => 'Fehler beim Erzeugen der Schlüsseldatei',
>> diff --git a/langs/en/cgi-bin/en.pl b/langs/en/cgi-bin/en.pl
>> index 4c05dcf76..a92bb07f8 100644
>> --- a/langs/en/cgi-bin/en.pl
>> +++ b/langs/en/cgi-bin/en.pl
>> @@ -1015,6 +1015,7 @@
>>  'enter data' => 'Enter your settings <br /> and then press <i>Save</i>.',
>>  'entropy' => 'Entropy',
>>  'entropy graphs' => 'Entropy Graphs',
>> +'eol architecture warning' => 'You are running an architecture of IPFire which reached its end of life. You will not receive updates anymore. This is a security risk.',
>>  'err bk 1' => 'Error creating archive',
>>  'err bk 10 password' => 'Error with backup password',
>>  'err bk 2 key' => 'Error creating key file',


  reply	other threads:[~2021-11-29 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 15:43 Jonatan Schlag
2021-11-28 19:50 ` Bernhard Bitsch
2021-11-28 20:09 ` Leo Hofmann
2021-11-29 10:16   ` Michael Tremer [this message]
2021-11-29 10:30     ` Michael Tremer
2021-11-29 10:49       ` Bernhard Bitsch
2021-12-10 13:55         ` Michael Tremer
2021-12-10 14:05           ` Bernhard Bitsch
2021-11-29 19:32     ` Jonatan Schlag

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=4443FD09-F63A-437B-B449-9CC5D79F9700@ipfire.org \
    --to=michael.tremer@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