From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.29 - Core Update 183 is available for testing Date: Tue, 30 Jan 2024 14:25:03 +0100 Message-ID: <01d78313-1130-4186-bf21-d2bebbc89af6@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8471924272568214967==" List-Id: --===============8471924272568214967== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, Have been exercising CU183 Testing. Everything has gone fine. I tested out my existing OpenVPN RW and N2N connections and they worked=20 fine. Created new RW and N2N connections. The RW worked without any problems. The N2N connection worked but the client end download icon and status=20 area are not working. This is nothing to do with CU183 Testing. This=20 comes from the fix I did for bug 11048 and therefore has been present=20 since CU181. I have created a new bug entry for this (13548) which I have assigned to=20 myself. I have looked at the code and have figured out what the problem is and=20 will create a patch to test and fix it. Everything else that I have tested on CU183 has worked without issues. I=20 have not found any issue related to CU183 changes. A very quiet update. Regards, Adolf. On 23/01/2024 15:20, Michael Tremer wrote: > Thank you for the reminder=E2=80=A6 I will add that. >=20 > I am currently quite buried in a lot of things that I am trying to handle s= imultaneously. So, please, if things don=E2=80=99t look right, let me know :) >=20 > -Michael >=20 >> On 23 Jan 2024, at 14:19, Adolf Belka wrote: >> >> Hi, >> >> One thing I noticed with the Core Update 183 Testing announcement. It does= n't announce the EOL of the Icinga addon and its removal in Core Update 185 a= s we discussed in the last Video Call meeting. >> >> Regards, >> Adolf. >> >> On 23/01/2024 15:10, Michael Tremer wrote: >>>> On 23 Jan 2024, at 13:23, Adolf Belka wrote: >>>> >>>> Hi All, >>>> >>>> On 23/01/2024 14:20, Adolf Belka wrote: >>>>> Hi All, >>>>> >>>>> On 23/01/2024 13:11, Adolf Belka wrote: >>>>>> Hi All, >>>>>> >>>>>> First feedback is that the email notification of the Testing Release i= s great. The old version was always a bit dull and on my mobile it always end= ed up with dark writing on a dark background. >>>>>> >>>>>> Now the email notification looks the same on my desktop and my mobile = and is much more eye catching. >>>>>> >>>>>> On the top of the WUI page the IPFire_ has replaced the fiery penguin = but the underscoring indicating that it is a link ends up going above the und= erscore character. Was that intended? It's not a big thing and I can live wit= h it no problems but it did just look a bit peculiar at first glance. >>>>>> >>>>> >>>>> Ignore my comment. I had to refresh the browser page as it was keeping = most of it from the cache. I had not seen all the changes previously due to t= he cache. >>>>> >>>>> Not as simple as refreshing the browser page. One of my systems now has= the full new version but the other is still showing mostly the old version w= ith just the tux icon changed. >>>>> >>>> I had to go into firefox settings and tell it to clear the cached web co= ntent. Then the IPFire WUI is now fully updated. Sorry for the noise. >>> Ah I got you now=E2=80=A6 >>> I was wondering what we can do about this=E2=80=A6 Browsers will definite= ly cache the old CSS and so we might actually show a lot of garbage until thi= ngs get refreshed. >>> A lazy solution could simply be to rename the CSS file. That way, browser= s definitely will fetch it again. Otherwise, they should actually check every= time if the content they have is actually current as we do not send any long= time caching headers. But some people like to break RFCs in favour of =E2=80= =9Cperformance=E2=80=9D. >>> -Michael >>>> >>>> Regards, >>>> >>>> Adolf. >>>> >>>>> Regards, >>>>> >>>>> Adolf. >>>>> >>>>> >>>>>> The upgrade process went fine, including the reboot. Everything cam ba= ck with no issues. >>>>>> >>>>>> Will now start to look at the various screens and test things out. >>>>>> >>>>>> Regards, >>>>>> Adolf. >>>>>> >>>>>> On 23/01/2024 11:55, IPFire Project wrote: >>>>>>> It is time for testing the next version of IPFire - and it is going t= o be a big one: A new major version - IPFire 2.29 - Core Update 183. There is= an update of the design of the web user interface, a fresh kernel based on L= inux 6.6, a lot of package updates and improvements and bug fixes throughout = the entire system. >>>>>>> =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C= =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80= =8C =E2=80=8C =E2=80=8C =E2=80=8C >>>>>>> >>>>>>> >>>>>>> IPFire_ >>>>>>> >>>>>>> >>>>>>> IPFire 2.29 - Core Update 183 is available for testing >>>>>>> >>>>>>> It is time for testing the next version of IPFire - and it is going t= o be a big one: A new major version - IPFire 2.29 - Core Update 183. There is= an update of the design of the web user interface, a fresh kernel based on L= inux 6.6, a lot of package updates and improvements and bug fixes throughout = the entire system. >>>>>>> >>>>>>> Read The Full Post On Our Blog >>>>>>> >>>>>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstra=C3=9Fe = 8, 45711 Datteln, Germany >>>>>>> >>>>>>> Unsubscribe >=20 --=20 Sent from my laptop --===============8471924272568214967==--