From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Test of cleanup branch
Date: Thu, 01 Aug 2024 12:50:19 +0200 [thread overview]
Message-ID: <a99644e4-34f6-4153-a698-8e61dc4740d7@ipfire.org> (raw)
In-Reply-To: <fd1ad818-3739-416b-b134-1b03308a63fd@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]
Hi Michael,
On 25/07/2024 12:28, Adolf Belka wrote:
> Hi Michael,
>
> On 25/07/2024 10:44, Michael Tremer wrote:
>> Hello Adolf,
>>
>> Thank you for getting back on this so quickly.
>>
Maybe I got back too quickly!!
I have just done a build with next for a bugfix patch and installed it into my vm and the pages look quite different with some things missing, like the green and red colours for if services are running or not and some graph titles are incorrect.
I took the iso from the latest directory in the nightly build but it looks like it was still linked to the previous version when I downloaded it as the b2 sum is for build 6460dbbf from the day before.
Downloading the iso today from the latest directory gives me the build ed2c97b7.
I am going to install that version now but I suspect it will show the same as I found with my build.
So it looks like my original review was based on the version before the cleanup branch changes were included.
I will come back with new feedback of what I find from the latest branch that I have now downloaded.
Sorry. In future maybe I should wait till the following day, or download from the build named directory instead of the directory named latest.
Regards,
Adolf
>> I suppose this also means that the ISO in the next branch boots just fine, too?
>
> Yes, that is correct. I used the iso from the nightly next latest directory. No problems with the install at all.
> This tested out raid and all 4 interfaces.
>
> Regards,
> Adolf.
>
>>
>> Best,
>> -Michael
>>
>>> On 25 Jul 2024, at 09:07, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>
>>> Hi Michael,
>>>
>>> I installed CU188 from the nightly onto a vm system and looked though all the WUI pages and everything looked fine.
>>>
>>> I then restored a CU187 backup from my testing and then checked the OpenVPN RW and N2N. Both worked fine with no problems. Also the logging for that all worked with no problems.
>>>
>>> Also checked out the IPS, IP Blocklists, Firewall groups and rules, DNS ...
>>>
>>> Everything I have looked at shows no impact from the cleanup branch changes. It looks good to me.
>>>
>>> Of course good for others to also evaluate.
>>>
>>> Regards,
>>>
>>> Adolf.
>>>
>>
next prev parent reply other threads:[~2024-08-01 10:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 8:07 Adolf Belka
2024-07-25 8:44 ` Michael Tremer
2024-07-25 10:28 ` Adolf Belka
2024-08-01 10:50 ` Adolf Belka [this message]
[not found] <22c69b40-ca43-4488-913d-57437870eb04@ipfire.org>
2024-08-01 15:45 ` Adolf Belka
2024-08-01 17:09 ` Adolf Belka
2024-08-01 20:38 ` Adolf Belka
[not found] <cd722e8e-ef1f-4cda-a9b6-e414f61bb935@ipfire.org>
2024-08-02 17:13 ` Michael Tremer
[not found] <0c9e1da9-17e1-49e2-9d1c-2862f0370094@ipfire.org>
2024-08-06 15:52 ` Michael Tremer
[not found] <1c956778-8370-4616-b329-e284420be89d@ipfire.org>
2024-08-07 12:04 ` Adolf Belka
2024-08-07 12:12 ` Adolf Belka
2024-08-07 12:18 ` Michael Tremer
2024-08-07 12:19 ` Michael Tremer
[not found] <cc70b68c-d3ac-438d-ac1b-03cdefe290cf@ipfire.org>
2024-08-07 14:50 ` Michael Tremer
2024-08-08 12:03 ` Adolf Belka
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=a99644e4-34f6-4153-a698-8e61dc4740d7@ipfire.org \
--to=adolf.belka@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