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: IPFire 2.25 core141 build and put into new 2.25 pakfire trees
Date: Wed, 05 Feb 2020 10:18:52 +0000	[thread overview]
Message-ID: <442AF733-D208-4B8B-9169-B0259D4E3F16@ipfire.org> (raw)
In-Reply-To: <65a5b7c3ee8d6fd012ac748901b5074d39757090.camel@ipfire.org>

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

Hello,

I just installed the update on the firewall in my office.

So far I cannot report any more bugs. Good work guys!

When we are pushing this release to 2.23.1?

-Michael

> On 4 Feb 2020, at 18:15, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Hello Arne,
> 
> thanks for your hint. I've reinstalled core 141 for the latest changes
> on my dad's IPFire with PPPoE dialin and so far everything runs smooth.
> 
> No problems during reboot or any kind of DNS issue.
> 
> Best regards,
> 
> -Stefan
>> Hi
>> 
>> i have build IPFire core141 after some late changes and put the
>> images 
>> in my people folder and
>> the updates to pakfire 2.25 trees for testing.
>> Because the critical dns changes i have not put into the 2.23.1
>> testing 
>> trees yet. I hope i can do this
>> after some feedback. So please help testing.
>> 
>> Make sure your installations are on core139 before change the tree
>> from 
>> 2.23(.1) to 2.25 for updater testing!
>> 
>> Arne
>> 
>> 


  reply	other threads:[~2020-02-05 10:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 18:05 Arne Fitzenreiter
2020-02-04 18:15 ` Stefan Schantl
2020-02-05 10:18   ` Michael Tremer [this message]
2020-02-05 12:26   ` Daniel Weismüller
2020-02-05 13:50     ` Michael Tremer
2020-02-06 11:23       ` Daniel Weismüller
2020-02-06 11:25         ` Michael Tremer
     [not found] <e23b18138732dc26f1ffe3239e9a3451@ipfire.org>
2020-02-06 10:47 ` Michael Tremer
     [not found] <f3c7ad86-ac3f-f1d7-369b-b0f7675589bd@ipfire.org>
2020-02-06 13:30 ` Arne Fitzenreiter
2020-02-07 14:37   ` Michael Tremer
2020-02-07 15:18     ` Tom Rymes
2020-02-07 15:36       ` Michael Tremer

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=442AF733-D208-4B8B-9169-B0259D4E3F16@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