flatterrich

I also upgraded from bookworm to trixie and saw this warning. I can confirm that Igor's suggested workaround addresses it:
wget https://apt.armbian.com/armbian.key gpg --dearmor < armbian.key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null apt is now happy with the armbian repo.

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

@IgorI think the problem is caused by the way the packages are published. I think we ran the build for bookworm and jammy, but when publishing we updated the Package list of bullseye as well. Thats how bullseye is now getting armbian-bsp-cli package for 23.11 version. As build was not run for bullseye, the bullseye specific base-files package didn't got updated. I think we need to modify our repo updating job to also take account of what distributions to be updated, instead of updating all of the distributions. That should fix these kind of upgrade issues when we drop support for older OS. Lets disccuss this further in today's meeting