`/etc/armbian-image-release` is not updated...

[umlaeute]

Back in the days, i've installed armbian on my "Odroid XU4".

those where the days when "buster" was still a thing.

 

In the meantime, I've updated the system (change apt repos; run 'apt full-upgrade'), and I'm now running "bookworm":

# lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Armbian 24.5.5 bookworm
Release:    12
Codename:    bookworm

 

unfortunately, /etc/armbian-image-release still thinks i'm running buster (and armbian-20.02.7):

# PLEASE DO NOT EDIT THIS FILE
BOARD=odroidxu4
BOARD_NAME="Odroid XU4"
BOARDFAMILY=odroidxu4
BUILD_REPOSITORY_URL=https://github.com/armbian/rkbin
BUILD_REPOSITORY_COMMIT=3e533c9
DISTRIBUTION_CODENAME=buster
DISTRIBUTION_STATUS=supported
VERSION=20.02.7
LINUXFAMILY=odroidxu4
BRANCH=legacy
ARCH=arm
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=Image
IMAGE_UUID=164e4ab3-9157-48a3-bbe1-6525c2b9a086

 

i wouldn't mind very much, if the login-screen wouldn't scream everytime i log in:

Welcome to Armbian 24.5.5 *Buster* with Linux 6.6.31-current-odroidxu4
No end-user support: unsupported (buster) userspace!

 

I'm a bit mystified, why it wrongly says *Buster*, and at the same time reports the correct kernel and armbian version.

 

Anyhow: How can I fix this?

 

 

 

note: there's already a similar topic here (from 2 years ago), but since it is so old, i was asked to start a new thread:

 

Edited August 5 by umlaeute

[umlaeute]

i'm also a bit mystified, what the motd says *buster* and at the same time correctly reports the armbian and kernel version

[Igor]

Armbian kernel can be used on any userspace, but we only sent kernel updates to supported ones. Buster is EOL by Debian.

 

Can you provide:

armbianmonitor -u

so we know more about your image.

 

You are probably running Buster BSP package. That is not replace with upgrade.

[umlaeute]

certainly: https://paste.armbian.com/wujesuqaro

 

also, i would have guessed that `lsb_release -a` would show me the userland.

 

'bash' seems to come from bookworm as well:

 

# apt show bash
Package: bash
Version: 5.2.15-2+b7
Priority: required
Essential: yes
Section: shells
Source: bash (5.2.15-2)
Maintainer: Matthias Klose <doko@debian.org>
Installed-Size: 6,904 kB
Pre-Depends: libc6 (>= 2.36), libtinfo6 (>= 6)
Depends: base-files (>= 2.1.12), debianutils (>= 5.6-0.1)
Recommends: bash-completion (>= 20060301-0)
Suggests: bash-doc
Conflicts: bash-completion (<< 20060301-0)
Replaces: bash-completion (<< 20060301-0), bash-doc (<= 2.05-1)
Homepage: http://tiswww.case.edu/php/chet/bash/bashtop.html
Tag: admin::TODO, devel::TODO, devel::interpreter, implemented-in::c,
 interface::shell, interface::text-mode, role::program,
 scope::application, suite::gnu, uitoolkit::ncurses
Download-Size: 1,422 kB
APT-Manual-Installed: yes
APT-Sources: http://deb.debian.org/debian bookworm/main armhf Packages
Description: GNU Bourne Again SHell

and my apt sources only list "bookworm":

# find /etc/apt/sources.list* -name "*.list" -exec sed -e 's/#.*//' -e 's/ *//' -e '/^$/d' {} +
deb http://apt.armbian.com bookworm main bookworm-utils bookworm-desktop
deb     http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
deb     http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
deb     http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware

 

Edited August 5 by umlaeute

[callegar]

Same issue here. I originally installed a bullseye image and then updated to buster. However /etc/armbian-image-release does not get updated and unfortunately, it is the sole place where motd 10-armbian-header can find information about the distribution codename. In fact:

- first /etc/armbian-image-release is read that contains DISTRIBUTION_CODENAME from the original image (which I think is OK because I understand that file should always keep info from the image employed for the initial installation);

- then /etc/armbian-release is read, but does not contain anything about the DISTRIBUTION_CODENAME (this does not seem OK to me).

- finally no other info is gathered because DISTRIBUTION_CODENAME is already set

Edited October 17 by callegar