debian in meltdown?

[folderol]

There's something really weird going on over there. Almost the entire range of audio software is marked for removal in the package tracker! At the same time, it looks like they're planning a code freeze in October - presumably for the next release

[LAM]

There's something really weird going on over there. Almost the entire range of audio software is marked for removal in the package tracker! At the same time, it looks like they're planning a code freeze in October - presumably for the next release

Probably is just some core or lib update requiring many packages to get rebuilt with the new version.

I'm so happy being on Sid and not having to worry of the "next release".

[khz]

I have no problems updating a debian stable.
Can you post the output of "apt update && apt upgrade" here?

[tramp]

I have no problems updating a debian stable.

That wont affect debian stable, that is about the next stable release.
sid -> testing -> next stable release.

[sunrat]

Sounds like normal Sid/Testing modus operandi. A core library gets updated and every application that uses it must subsequently be updated as well. I'm sure the Debian Multimedia Maintainers are working frantically to make everything work again.

I'm with @khz here, Debian Stable for production (and everything else actually).

[LAM]

Sounds like normal Sid/Testing modus operandi.

Actually is more a Testing modus operandi.
https://release.debian.org/testing/freeze_policy.html

In Sid you may encounter some package problems during transitions, usually it never takes too long and happens rarely. Solution: wait some days to update.
https://release.debian.org/transitions/

[sadko4u]

It seems that support of GTK2 is being removed from many distros. And nested projects are affected.

[LAM]

It seems that support of GTK2 is being removed from many distros. And nested projects are affected.

Could be but I didn't encounter a removal for GTK2 in Debian yet. Do you know wich packages are affected in Debian?

However I did encounter a bug (wih high severity and reason for a removal) regarding jackd2, about a user not being able to start jackd2 and having pipewire installed.

Hope this is a joke.

https://bugs.debian.org/cgi-bin/bugrepo ... ug=1000293

[folderol]

Personally I find it extremely disturbing that people are wanting to throw out very stable software (Jack) because a new, still buggy system breaks everything around it

[khz]

Also with my debian testing the updaen runs without problems.
What is everything you entered in the /apt/source.list?

[tramp]

Also with my debian testing the updaen runs without problems.

Check the dates the warnings been mean for: jackd2 > 01 october, ardour 29 september and so on.
What did you expect to see about that now in apt?
And even if, you wont receive a notice for that, all what happen is that you dont get updates for that package any more. One day, then, they will refuse to start.

All that been news from the debian developers list, and properly you'll never notice that on your machine, because people working under the hood to solve that issues.
It's like @sunrat wrote, some core libs needs to be updated, some, indeed fail to build with gcc12, so been marked for removal. All packages depending on them, been in follow marked for removal. That's a automatic process. But, at least, it means, fix one bug and most packages been unmarked. Fix one other, and again 100 packages been saved.

[tramp]

Fun fact; even gcc-12 is marked for auto removal: https://tracker.debian.org/pkg/gcc-12
Here is the list of affected packages:

Your message contains 80388 characters.
The maximum number of allowed characters is 60000.

[LAM]

It's like @sunrat wrote, some core libs needs to be updated

Actually the first who suggested this in this thread was me. But jokes apart, don't panic, I trust Debian maintainers will sort most of the problems in the next weeks. As @sunrat wrote

[tramp]

I trust Debian maintainers will sort most of the problems in the next weeks.

Yea! They've already solved it. Most (if not all) marks for auto removal been gone.

[folderol]

Yes. We seem to be back to normal now. This sort of thing always makes me nervous. A few years ago, Yoshimi was taken off due to an error in FLTK. Even after that was corrected we were still off - for about 2 months overall, and I was jumping through hoops to try and find someone who could put this right.
Incidentally for several months now I've been trying to get some sense out of Wikipedia. The Yoshimi entry has several 'warnings' about our entry not being sufficiently objective or having independent verification - even after I pointed out that the article is completely factual, with links to the actual code along with the web page and advanced reference manual on both github and sourceforge