Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian Bullseye | General testing #3009

Closed
MichaIng opened this issue Jul 26, 2019 · 1 comment
Closed

Debian Bullseye | General testing #3009

MichaIng opened this issue Jul 26, 2019 · 1 comment

Comments

@MichaIng
Copy link
Owner

MichaIng commented Jul 26, 2019

We'll going to include Bullseye into regular testing sessions from now on. Currently it is quite very similar to Buster, but that way when further changes occur, we'll be able to recognise issues due to larger changes earlier.

Ref: #3015

Who wants to help:

sed -i 's|buster|bullseye|' /etc/apt/sources.list
sed -i 's|bullseye/updates|bullseye-security|' /etc/apt/sources.list # Scheme has changed
G_AGUP
apt upgrade
apt full-upgrade # Currently does not include any further, thus no dependency changes yet
G_AGA

Additionally DietPi-PREP can now be used to create Bullseye DietPi systems: https://raw.githubusercontent.com/MichaIng/DietPi/dev/PREP_SYSTEM_FOR_DIETPI.sh


Just dist-upgraded my RPi server, so far no issues besides (again) some repo inconsistency. Some GPG package has forgotten to be updated in the repo to the version that matches all other GPG packages. I still don't get how this can happen, or in case why this is wanted... However APT will skip those on non-interactive calls as long as no --allow-remove-essential is added. But if it was, if would purge e.g. APT itself...
As it was before on Buster during testing phase, this is again no issue on Debian, only Raspbian 😉.

@MichaIng
Copy link
Owner Author

MichaIng commented Sep 2, 2019

I will mark this as closed. Changes/fixes for Bullseye will be implemented when recognised, differences to Buster are not yet large, as mentioned. A more complete testing session will be done in 2 years, when official release comes close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant