OrangePi3LTS - update /upgrade error

[kris777]

I think I messed something up in the system, maybe with the repositories, but I get this message when updating...

apt update
Stary:1 http://deb.debian.org/debian bookworm InRelease
Stary:2 http://security.debian.org bookworm-security InRelease                                                          
Stary:3 https://download.docker.com/linux/debian bookworm InRelease                                                     
Stary:4 http://deb.debian.org/debian bookworm-updates InRelease                                                         
Stary:5 http://deb.debian.org/debian bookworm-backports InRelease                                                       
Stary:6 https://dtcooper.github.io/raspotify raspotify InRelease                                                        
Stary:7 https://github.armbian.com/configng stable InRelease                                                            
Stary:8 http://armbian.lv.auroradev.org/beta bookworm InRelease                                       
Czytanie list pakietów... Gotowe                         
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe   
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@orangepi3-lts:~# apt list --upgradable
Listing... Gotowe
armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49]
N: There is 1 additional version. Please use the '-a' switch to see it
root@orangepi3-lts:~# apt list --upgradable -a
Listing... Gotowe
armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49]
armbian-bsp-cli-orangepi3-lts-current/now 25.8.0-trunk.49 arm64 [installed,upgradable to: 25.11.0-trunk.401]

maybe someone has already dealt with this message and error?

[laibsch]

Please prepend the commands with LC_ALL=C like "LC_ALL=C apt update" and post the output again.

[kris777]

 LC_ALL=C apt update
Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease                                                                     
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease                                                             
Hit:4 https://download.docker.com/linux/debian bookworm InRelease                                                         
Hit:5 http://deb.debian.org/debian bookworm-backports InRelease                                                           
Hit:6 https://github.armbian.com/configng stable InRelease                                                                
Hit:7 https://dtcooper.github.io/raspotify raspotify InRelease      
Hit:8 http://fi.mirror.armbian.de/beta bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@orangepi3-lts:~# apt list --upgradable
Listing... Gotowe
armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.439 arm64 [upgradable from: 25.8.0-trunk.49]
N: There is 1 additional version. Please use the '-a' switch to see it

 

[kris777]

Quote

It is likely that the team (or person) responsible for preparing the armbian-bsp-cli-orangepi3-lts-current package for version $25.8.2$ uploaded it to the repository before or without making sure that the required version of base-files ($25.8.2$) was already available there. This is why none of the standard commands (upgrade, full-upgrade, install) worked until we forced the installation with dpkg --ignore-depends.

This is the hint I got from AI 🙂

I changed the repositories from beta to stable and installed:

 

sudo sed -i 's|beta.armbian.com|apt.armbian.com|g' /etc/apt/sources.list.d/armbian.list

 

and

 

sudo apt download armbian-bsp-cli-orangepi3-lts-current
sudo dpkg --install --ignore-depends=base-files armbian-bsp-cli-orangepi3-lts-current_25.8.2_arm64.deb

 

Now it's OK....but is this the right approach?

Edited yesterday at 07:03 PM by kris777

[Werner]

didn't even realize you were on beta repo. Well when you use bleeding edge, you have to be prepared for breakage since it is expected ;).

[kris777]

I gave some information  ..... Hit:8 http://fi.mirror.armbian.de/beta bookworm InRelease ? 🙂