Hello

 

I'm just wondering that there are two release files in /etc and why they have different VERSION values.

 

In armbian-image-release file, VERSION is 20.08.1

 

But it is 21.08.8 in armbian-relase file.

 

 

armbian-config and welcome massages also show version as 21.08.8

 

So I think 21.08.8 is correct one, but then why armbian-image-release has incorrect version value?

 

Is it a bug? Or am I missing something?

 

Please help me.

 

Thank you.

Hm interesting. As you can see here both files should be identical with minor diff. Maybe related to a mistake in a rootfs update or whatever.

Thank you for answer.

 

Now I looked into another SoC running on armbian and it also has different version values in those two files.

 

The file date 'Sep 4 2020(above)' and 'May 8 2021(below)' of armbian-image-release files probably indicate the day of first time installation of armbian.

 

It looks like that those two armbian-image-release files were not changed at all after first time installation.

 

I only have done apt update & upgrade occasionally and did not manually upgrade (if exists) armbian version.

 

Should I do something more to upgrade armbian version normally?

 

Or there is any missing somethings in apt update & upgrade procedures?

 

Or this is normal behavior if armbian is upgraded via apt?

 

addendum) one more thing please. IMAGE_TYPE changed to user-built from stable. All I did was apt update & upgrade only. Is it normal?

 

Please help me.

 

Thank you.

It looks like /etc/armbian-image-release shows information from the originally installed image and /etc/armbian-release shows information from current/running version:

 

I originally flashed "Armbian_21.08.3_Bananapipro_buster_current_5.10.60.img" on my Banana Pi Pro so my outputs look like this:

 

pi@bananapipro:~$ cat /etc/armbian-image-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=bananapipro
BOARD_NAME="Banana Pi Pro"
BOARDFAMILY=sun7i
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=bc7dfd1dd-dirty
DISTRIBUTION_CODENAME=buster
DISTRIBUTION_STATUS=supported
VERSION=21.08.3
LINUXFAMILY=sunxi
ARCH=arm
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=Image
IMAGE_UUID=ed469859-95ae-4de6-a728-16ae30cf6eda
pi@bananapipro:~$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=bananapipro
BOARD_NAME="Banana Pi Pro"
BOARDFAMILY=sun7i
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=92a1c729d-dirty
VERSION=22.02.1
LINUXFAMILY=sunxi
ARCH=arm
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=Image
BRANCH=current
pi@bananapipro:~$

 

> "IMAGE_TYPE changed to user-built from stable."

 

Guess your installation (buster on nanopi-r4s) was put to csc status. Check status of buster in /etc/armbian-distribution-status.

 

Edit:

According to  https://github.com/armbian/build/blob/master/config/targets.conf only bullseye and focal are officially supported on nanopi-r4s now.

 

39 minutes ago, blacki2 said:

According to  https://github.com/armbian/build/blob/master/config/targets.conf only bullseye and focal are officially supported on nanopi-r4s now.

Board target listed there does not necessarily mean it is supported. This is just a list of images that are being automatically build by CI.

2 hours ago, blacki2 said:

It looks like /etc/armbian-image-release shows information from the originally installed image and /etc/armbian-release shows information from current/running version:

Then it seems that I can safely ignore the contents of armbian-image-release. 

 

2 hours ago, blacki2 said:

Guess your installation (buster on nanopi-r4s) was put to csc status. Check status of buster in /etc/armbian-distribution-status.

I upgraded buster to bullseye and IMAGE_TYPE became stable again! Thank you.