public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Feedback on IPFire 2.27 - Core Update 182 is available for testing
Date: Wed, 06 Dec 2023 10:45:45 +0100	[thread overview]
Message-ID: <87a92d05-0415-4692-8b07-5cd84a308736@ipfire.org> (raw)
In-Reply-To: <170179650558.1017810.9287558036661477115.ipfire@ipfire.org>

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

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>.
> 

       reply	other threads:[~2023-12-06  9:45 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 [this message]
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
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=87a92d05-0415-4692-8b07-5cd84a308736@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