Bororo Posted Friday at 05:00 PM Posted Friday at 05:00 PM Armbianmonitor: https://paste.armbian.com/aleviwuver Hey, guys, I just upgraded my OrangePi Zero. Everything seems to be working, but I'm disturbed by incorrect information on the home page: v25.2.3 for Orange Pi Zero running Armbian Linux 6.12.20-current-sunxi Packages: Debian end of life (buster), possible distro upgrade (bookworm) Support: DIY (community maintained) Please advise me how to make Armbian correctly display the installed version. Thank you. 0 Quote
Werner Posted Friday at 05:39 PM Posted Friday at 05:39 PM https://docs.armbian.com/User-Guide_FAQ/#can-i-upgrade-my-userspace-flavor-like-bullseye-to-bookworm-or-jammy-to-noble There is some package (base-files or rootfs, bsp, whatever, cannot remember) that contains this information. Yours is probably outdated. Replace accordingly. 0 Quote
eselarm Posted Friday at 05:46 PM Posted Friday at 05:46 PM On my NanoPi-NEOs I have seen this several times/years /etc# grep -d skip buster * armbian-distribution-status:buster=eos;upgrade=bullseye,bookworm,trixie,testing armbian-image-release:DISTRIBUTION_CODENAME=buster mime.types:application/rpki-ghostbusters gbr grep: motd: No such file or directory So I guess those files need some other text 0 Quote
eselarm Posted yesterday at 10:57 AM Posted yesterday at 10:57 AM I did this: sed -i 's/buster/bookworm/g' armbian-image-release sed -i 's/21.05.1/25.2.3/g' armbian-image-release But I have motd stuff all muted as all is CLI/remote/ssh/unattended only. It is only for the case that in 1 or 2 years from now I don't get confused by 'buster' again. But I think this file gets orphaned for people doing in-place upgrades (not wiping SD with new image at least. I use it only to see when and how I got the new SBC and architecture/SoC running first time when not knowing much about a platform. For the 5 NanoPi-NEOs, they are all copied/cloned from just the first one I bought and got working and modified so it is a partition structure (Btrfs for root at least) that fits my regeneration-from-backup-NAS script for all Linux clients. After the clone action, the package tooling (and sources.list* contents) determine versions. What matters for me is MACaddress essentially (and some other keys and UUIDs). I only use os-release to see what distro flavor it is. And sometimes 'hostnamectl status' to see what is running. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.