Announcement
Collapse
No announcement yet.
Debian 11 "Bullseye" To Begin Code Freeze In Early 2021
Collapse
X
-
Yay! That's fantastic. I've been on current stable for 2 years on my server and hardware I have is much better handled with backports kernel and other firmware. Now it will be working perfectly out of the box with new stable
-
Originally posted by andyprough View Post
Bullseye: Package: gnome (1:3.30+2) -- https://packages.debian.org/bullseye/gnome
Sid: amd64 1:3.30+2 -- https://packages.debian.org/sid/gnome
When I checked my rig(Debian Testing) I found that installed sub-packages (and actual programs) are mostly at version 3.34(47),
a couple were 3.36(7) even a couple at 3.28(6) or lower. I didn't even have the 'gnome' meta package installed.
That's not so ancient software for something that's going to become the next Debian Stable.
Debian's Gnome Team only update the packages if there is changed code included and meta packages are only version-bumped
when most the dependencies have been version-bumped. Saves on upgrade-spam which makes server-admins happier.
- Likes 1
Leave a comment:
-
Originally posted by andyprough View Post
That's rule #2. Rule #1 is blame RedHat and Poettering and systemd.
- Likes 3
Leave a comment:
-
Originally posted by 144Hz View Postandyprough Congratulations. First you want Canonical to break Stable, now you want Canonical to mess with meta-packages.
Sorry because but that’s not how Debian works. Look at packaging activities on GNOME.
That’s right Canonical people all over the place.
In fact you can’t do much better than Canonical GNOME Team. They provide long term careers for people who want to:
1) Develop at upstream GNOME.
2) Deploy at Debian, available to all derivatives.
3) Deploy at Ubuntu.
4) Maintain LTS for 5 years.
- Likes 1
Leave a comment:
-
Originally posted by jacob View Post
Rule #1: Blame Canonical. When everything else fails, you can always blame them for following the correct procedures...
- Likes 1
Leave a comment:
-
Originally posted by jacob View PostRule #1: Blame Canonical.
- Likes 2
Leave a comment:
-
Originally posted by 144Hz View Postandyprough You are looking at Debian Stable. That’s frozen and shouldn’t get bumped.
Blaming Canonical for not breaking procedures would be next level stupid. You are not doing that, right? Right?
The rest of us is talking about Debian Unstable/Testing. Which eventually will provide packages for next Debian Stable. This is where I demonstrated 3 Canonical developers did packaging work over a 4 hour time span.
- Likes 1
Leave a comment:
-
Originally posted by 144Hz View Postandyprough You are looking at Debian Stable. That’s frozen and shouldn’t get bumped.
Blaming Canonical for not breaking procedures would be next level stupid. You are not doing that, right? Right?
The rest of us is talking about Debian Unstable/Testing. Which eventually will provide packages for next Debian Stable. This is where I demonstrated 3 Canonical developers did packaging work over a 4 hour time span.
Sid: amd64 1:3.30+2 -- https://packages.debian.org/sid/gnome
I agree with your one point - I am next level stupid.
Leave a comment:
Leave a comment: