As said, for me the update was done in approx 20 Minutes
maybe you missed the linked page of me
For my understanding apt-get is not required any longer and replaced by “apt” in newer distributions.
I never used apt-get so far the last two years
As said, for me the update was done in approx 20 Minutes
maybe you missed the linked page of me
For my understanding apt-get is not required any longer and replaced by “apt” in newer distributions.
I never used apt-get so far the last two years
apt-listchanges: News
---------------------
apt (2.1.16) unstable; urgency=medium
Automatically remove unused kernels on apt {dist,full}-upgrade. To revert
to previous behavior, set APT::Get::AutomaticRemove::Kernels to false or
pass --no-auto-remove to the command. apt-get remains unchanged.
Packages files can now set the Phased-Update-Percentage field to restrict
update rollout to a specified percentage of machines. Previously, this has
only been available to users of Ubuntu's update-manager tool. See
apt_preferences(5) for details and how to configure multiple systems to get
the same updates. Phased updates are disabled in chroots for now to not
break buildd-style setups.
-- Julian Andres Klode <jak@debian.org> Fri, 08 Jan 2021 22:01:50 +0100
apt (1.9.11) experimental; urgency=medium
apt(8) now waits for the lock indefinitely if connected to a tty, or
for 120 seconds if not.
:
It shits itself. Ask me how I know
Not for me (20 characters)
Neither for me.
I have 2 Piaware SD Card Buster installs, both with graphs & many other feeders. I have upgraded both to Bullseye, and both are working very smoothly, without any issues, during upgrade process, as well as during normal operation.
By the way I used:
sudo apt update
sudo apt full-upgrade
Each microSD card took about 30~35 minutes to upgrade.
Ah, that is interesting. The new names are not so easy to remember as the classic names but apparently were aimed at desktop type computers where adaptors can be added therefore names may change.
Understand you can be changed to old legacy names if required.
Geoff
I think apt upgrade gives you a progress bar whilst it is doing so whereas apt-get upgrade leaves you guessing how long is left.
Geoff
After trying various upgrade commands, I have come to conclusion that using sudo apt full-upgrade
gives the best results, though it takes about 5 minutes more to upgrade.
This is how I do it:
(1) In file /etc/apt/sources.list
comment out line pointing to Buster repo, and add line pointing to Bullseye repo
(2) Issue following commands
sudo apt update
sudo apt full-upgrade
sudo apt autoremove
sudo reboot
Or simply change it. That’s what i did
Replacing “buster” with “bullseye” should not be that challenging, even if you need to revert it.
This is possible in Raspberry Pi OS Buster image.
I upgraded Piaware SD Card Buster image ver 6.1.
In this image the Buster repo is mirrored through Flightaware.
I changed Buster to Bullseye, but got warning during update that Bullseye repo does not exist in Flightaware mirror. I then commented out the line for Buster which was mirrored through Flightaware, and added line for Bullseye which was direct to raspberrypi.org repository
Oh, that’s what i did not read…
I upgraded 18 Pi’s and Orange Pi’s in the last few days
Upgraded from buster to bullseye without reimaging the cards.
Orange Pi’s went without a hitch ( 3 of them are flightfeeders) and were up and running in about 45 minutes.
Raspberry Pi’s complained all about an issue with libc6-dev package.
That could be fixed using sudo apt install gcc-8-base
After that a sudo apt full-update runs perfectly.
This sidestep took another 15 munites so raspberry’s were around 1 hour of upgrade time.
Longest time needed was for a Pi 2 upgrade, that took almost 4 hours to complete.
No reinstallation of any FA,FR24 or ADSB package was needed, all were up and running after the reboot.
1 Raspberry Pi to go but that will have to wait. My home automation depends on Phyton and the Bullseye version of 3.9.2 is not yet incorporated into the home automation software.
It knows version 3.4 and 3.5 but not 3.9
When that software is updated I can do the last upgrade from buster to bullseye.
I know I could do a remiage and work around the Phyton issue that way but It would be very time consuming to export and import all my Phyton scripts again
And i thought i have too much with four devices.
May i ask what they’re all doing?
You can answer per PN as it has nothing to do with the thread.
I am interested on other Raspberry projects for my spare devices
If Bullseye runs just fine on the PiAware SD card image build, why isn’t the upgrade available from the default FlightAware hosted repositories? Just curious.
This will be the case in version 7, when it will be relaxed, no indication yet.
That’s what I understand, when version 6.1 was released buster was the stable release and bullseye was still in the testing phase
My already bullsey-upgraded Raspberry 3 reports now the following packages are held back:
alsa-utils apt apt-utils aptitude aptitude-common build-essential cpp cpp-8 dh-python g++ g++-8 gcc gcc-8
gcc-8-base gdb gir1.2-glib-2.0 groff-base hardlink htop iproute2 iptables jq libalgorithm-diff-xs-perl
libasound2 libasound2-data libatlas-base-dev libatlas3-base libbrotli1 libc-bin libc-dev-bin libc6 libc6-dbg
libc6-dev libcairo2 libcommon-sense-perl libfcgi-perl libfile-fcntllock-perl libgcc-8-dev libgfortran5
libgirepository-1.0-1 libglib2.0-0 libhtml-parser-perl libhttp-message-perl libipc-sharelite-perl libiptc0
libiw30 libjq1 libjson-xs-perl liblcms2-2 liblocale-gettext-perl libluajit-5.1-2 libluajit-5.1-common
libpam-systemd libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpng16-16
libpolkit-agent-1-0 libpolkit-gobject-1-0 libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib
libpython3-dev libpython3-stdlib librrd8 librrds-perl libslang2 libsqlite3-0 libstdc++-8-dev libstdc++6
libsub-name-perl libsystemd0 libtext-charwidth-perl libtext-iconv-perl libtiff5 libudev1 libwbclient0 libwebp6
libwebpmux3 libxapian30 libxml2 libxtables12 locales luajit mawk mc mc-data perl perl-base pigz policykit-1
python2 python2-minimal python2.7 python2.7-minimal python3 python3-apt python3-cffi-backend python3-cheetah
python3-dev python3-distutils python3-gi python3-lib2to3 python3-minimal python3-pil python3-rpi.gpio
python3-six rpi.gpio-common rsyslog sqlite3 systemd udev wpasupplicant
This occurs on every usage of apt upgrade
. Usage of apt full-upgrade
was required to get them updated.
Just in case someone has the same problem
That is exactly why I posted following procedure twice
NOTE: The command apt full-upgrade
performs same function as apt-get dist-upgrade
After upgrading by command sudo apt full-upgrade
OR sudo apt-get dist-upgrade
, one must also issue command sudo apt autoremove
to cleanup packages which were installed, but are no longer required.
Time. It takes time to update and test new things.
We don’t mirror bullseye yet because no image configured to use that mirror would do anything with it - it’d just be a waste of bandwidth and storage.
Note that even after the sdcard image moves to bullseye, we have no plans to support an in-place update from buster to bullseye for existing installs.
It was working without the procedure. I never used “dist-upgrade”