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: Feedback on IPFire 2.27 - Core Update 182 is available for testing
Date: Wed, 06 Dec 2023 14:51:47 +0000	[thread overview]
Message-ID: <920C43DF-3311-4B0E-A392-14299D17DE31@ipfire.org> (raw)
In-Reply-To: <d97d7f6f-4fbf-4416-a09e-dd6d349ccd81@ipfire.org>

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

I replied on the ticket.

> On 6 Dec 2023, at 13:42, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> After doing the reboot on my virtualbox vm's with CU182 all the nic interfaces disappeared.
> 
> I tried repeating the cloning of working CU181 system and upgrading to CU182 and the same happened.
> 
> I have raised a bug on this
> 
> https://bugzilla.ipfire.org/show_bug.cgi?id=13466
> 
> Another user on the forum has reported a similar result on their proxmox system with virtio drivers. They also tried changing to the intel drivers but had the same result.
> 
> Regards,
> Adolf.
> 
> 
> On 06/12/2023 11:13, Adolf Belka wrote:
>> Hi,
>> 
>> On 06/12/2023 11:07, Michael Tremer wrote:
>>> Good Morning,
>>> 
>>>> On 6 Dec 2023, at 09:59, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>> 
>>>> Hi All,
>>>> 
>>>> I have also found a problem with addons still linked to an old dbus library.
>>> 
>>> No problem.
>>> 
>>>> I supplied an updated dbus addon patch but missed needing to ship the following addons that depend on dbus:-
>>>> 
>>>> avahi
>>>> cups
>>>> ghostscript
>> ghostscript won't need to be bumped because it was bumped in 182 due to a version update.
>> 
>> Regards,
>> 
>> Adolf.
>> 
>>>> netatalk
>>>> 
>>>> I will submit patches for bumping the versions of these addons to ensure they ship.
>>> 
>>> Thank you, I will merge those as soon as possible.
>>> 
>>>> Sorry for that problem.
>>> 
>>> No need to be sorry, that is why we do this testing thing :)
>>> 
>>> -Michael
>>> 
>>>> Regards,
>>>> 
>>>> Adolf.
>>>> 
>>>> 
>>>> On 06/12/2023 10:45, Adolf Belka wrote:
>>>>> Hi Peter and all,
>>>>> 
>>>>> There is an error in the update.sh script.
>>>>> 
>>>>> There is a removal line for old libraries from xz
>>>>> 
>>>>> /usr/lib/liblzma.so.5.4*
>>>>> 
>>>>> but this line is removing both the old (5.4.4) and the new (5.4.5) libraries.
>>>>> 
>>>>> This is causing at least alsa to fail to work but also any other packages dependent on xz libraries.
>>>>> 
>>>>> I think the line neds to be
>>>>> 
>>>>> /usr/lib/liblzma.so.5.4.4
>>>>> 
>>>>> Regards,
>>>>> Adolf.
>>>>> 
>>>>> On 05/12/2023 18:15, IPFire Project wrote:
>>>>>> IPFire Logo
>>>>>> 
>>>>>> there is a new post from Michael Tremer on the IPFire Blog:
>>>>>> 
>>>>>> *IPFire 2.27 - Core Update 182 is available for testing*
>>>>>> 
>>>>>>      The last Core Update of the year, IPFire 2.27 - Core Update 182, is available for testing. Please help us to make it yet another successful release, so that we can all update and enjoy a quiet holiday time.
>>>>>> 
>>>>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-182-is-available-for-testing>
>>>>>> 
>>>>>> The IPFire Project
>>>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>>>>> 
>>> 
> 
> -- 
> Sent from my laptop
> 


  reply	other threads:[~2023-12-06 14:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <170179650558.1017810.9287558036661477115.ipfire@ipfire.org>
2023-12-06  9:45 ` Adolf Belka
2023-12-06  9:59   ` Adolf Belka
2023-12-06 10:07     ` Michael Tremer
2023-12-06 10:13       ` Adolf Belka
2023-12-06 13:42         ` Adolf Belka
2023-12-06 14:51           ` Michael Tremer [this message]
2023-12-23 21:08   ` Core Update 182 (testing) report Peter Müller

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=920C43DF-3311-4B0E-A392-14299D17DE31@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