That's been a problem for me too, but how does the glibc in testing actually 
work? I see from the changelog (2025/09/19) it's got a bunch of packages:

testing/packages/binutils-gcc-glibc/aaa_glibc-solibs-2.42-x86_64-1_slack15.0.txz:
 Added.
testing/packages/binutils-gcc-glibc/binutils-2.45-x86_64-1_slack15.0.txz: Added.
testing/packages/binutils-gcc-glibc/gcc-15.2.0-x86_64-1_slack15.0.txz: Added.
testing/packages/binutils-gcc-glibc/gcc-g++-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/gcc-gcobol-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/gcc-gdc-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/gcc-gfortran-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/gcc-gm2-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/gcc-gnat-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/gcc-go-15.2.0-x86_64-1_slack15.0.txz: Added.
testing/packages/binutils-gcc-glibc/gcc-objc-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/gcc-rust-15.2.0-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/glibc-2.42-x86_64-1_slack15.0.txz: Added.
testing/packages/binutils-gcc-glibc/glibc-i18n-2.42-x86_64-1_slack15.0.txz: 
Added.
testing/packages/binutils-gcc-glibc/glibc-profile-2.42-x86_64-1_slack15.0.txz: 
Added.

Is it as simple as upgradepkg on all of those? No special upgrade order?

Thanks,

--
Dave

On Fri, 8 May 2026, at 1:36 AM, Greg Tourte wrote:
> Hi,
> 
> I am getting more and more uncomfortable with not being able to have 
> signal-desktop updated.
> 
> I realise that versions above 8.1 do not work with vanilla stable but they do 
> work with the glibc in the testing folder in -stable (and of course they will 
> work in -current).
> 
> What I am proposing is to have a new signal-desktop-legacy package with the 
> latest version working on -stable without the testing glibc and keep the 
> signal-desktop package fully uptodate and a note in the README file.
> 
> Does this sound acceptable?
> 
> Cheers
> 
> Greg
> _______________________________________________
> SlackBuilds-users mailing list
> [email protected]
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
> 
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to