Domas Posted January 9 Posted January 9 Hello, not sure if this should go under beginners, or this section but trying here. I have now set my armbian-config to rolling updates so I get the good beta stuff. Situation: I have no hard evidence of how often this actually happens, but it seems that every time i go and do armbian-upgrade, which I have performed yesterday and today, but also few days ago, I get the same 9 updates every time, armbian-bsp-cli-orangepiplus-current armbian-config armbian-firmware-full armbian-zsh base-files linux-dtb-current-sunxi linux-headers-current-sunxi linux-image-current-sunxi linux-u-boot-orangepiplus-current Is this normal with rolling updates? or my apt somehow loses the version information and reinstalls the new packages. Of course it does not happen if I run -upgrade twice. It compiles kernel etc, so a bit lengthy upgrade but no big deal. I am asking this because I was also performing a userspace upgrade unsuccessfully recently (also in same frequency as I do this armbian-upgrade) which fails for some reason. Just trying to find out if this is related. But this is not a part of this thread. 0 Quote
Solution Igor Posted January 9 Solution Posted January 9 3 hours ago, Domas said: Is this normal with rolling updates? Yes. Rolling updates gets updates all the time. Here: https://github.com/armbian/os/actions/workflows/repository-update.yml you can see when beta repository is updated. If nothing breaks, every day, sometimes more then once per day, when the code changes. We can not distinguish if fixes are for certain board as they (32b Allwinner in this case) share kernel. tl;dr; There is nothing to worry about. You can also disable https://docs.armbian.com/User-Guide_Armbian-Config/System/#disable-armbian-kernel-upgrades this and only keep upgrading user-space packages or switch to stable repository https://docs.armbian.com/User-Guide_Armbian-Config/System/#switch-system-to-stable-packages-repository Sadly I can't tell you if this will make any change to this particular hardware, but you won't be bothered for upgrade until next point release. We keep those boards on rolling because we have no resources / funding to tag them officially stable. 0 Quote
Domas Posted January 9 Author Posted January 9 Quote Yes. Rolling updates gets updates all the time. Here: https://github.com/armbian/os/actions/workflows/repository-update.yml you can see when beta repository is updated. If nothing breaks, every day, sometimes more then once per day, when the code changes. We can not distinguish if fixes are for certain board as they (32b Allwinner in this case) share kernel. Wow, unbelievable. But happy to see it is so actively maintained. Quote tl;dr; There is nothing to worry about. You can also disable https://docs.armbian.com/User-Guide_Armbian-Config/System/#disable-armbian-kernel-upgrades this and only keep upgrading user-space packages or switch to stable repository https://docs.armbian.com/User-Guide_Armbian-Config/System/#switch-system-to-stable-packages-repository Sadly I can't tell you if this will make any change to this particular hardware, but you won't be bothered for upgrade until next point release. We keep those boards on rolling because we have no resources / funding to tag them officially stable. I don't mind being on beta for time being and I am fine with updating this often. I actually enjoy receiving updates, since I decided to switch to beta and keep the kernel unfrozen. Worst case scenario - if some beta breaks my back, I will just restore whole SD card to a few month old backup and update to latest stable. I do not have anything useful on my board that changes over time. Lets consider this topic closed. 1 Quote
Domas Posted Sunday at 08:34 AM Author Posted Sunday at 08:34 AM Hey - just reopening this question. I have a related issue. This continues updating whenever I run the updates (at least once a week) I have noticed that it receives 9-12 of the same updates very often as stated in original post. But it seems that none of the other software is being updated. Is this normal? I remember back in the day if I run apt updates rarely, like once a month there would be a 40-ish packages to be updated. What happened was I did a lot of fiddling around ir sources.list.d and I probably broke something there. Or this is normal with beta on? This is my sources content: orangepiplus:~:% grep -Erh '^deb ' /etc/apt/sources.list* deb [arch=armhf signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com jammy main jammy-utils jammy-desktop deb [arch=armhf signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com jammy main jammy-utils jammy-desktop deb [signed-by=/usr/share/keyrings/armbian.gpg] https://github.armbian.com/configng stable main deb http://ports.ubuntu.com/ focal main restricted universe multiverse deb http://ports.ubuntu.com/ focal-security main restricted universe multiverse deb http://ports.ubuntu.com/ focal-updates main restricted universe multiverse deb http://ports.ubuntu.com/ focal-backports main restricted universe multiverse orangepiplus:~:% This is my apt-cache policy output: orangepiplus:~:% apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 100 http://ports.ubuntu.com jammy-backports/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 100 http://ports.ubuntu.com jammy-backports/main armhf Packages release v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/multiverse armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=multiverse,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/restricted armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-security/main armhf Packages release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/multiverse armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=multiverse,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/restricted armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy-updates/main armhf Packages release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/multiverse armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/universe armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/restricted armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=armhf origin ports.ubuntu.com 500 http://ports.ubuntu.com jammy/main armhf Packages release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=armhf origin ports.ubuntu.com 500 http://beta.armbian.com jammy/jammy-desktop all Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-desktop,b=all origin beta.armbian.com 500 http://beta.armbian.com jammy/jammy-desktop armhf Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-desktop,b=armhf origin beta.armbian.com 500 http://beta.armbian.com jammy/jammy-utils all Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-utils,b=all origin beta.armbian.com 500 http://beta.armbian.com jammy/jammy-utils armhf Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=jammy-utils,b=armhf origin beta.armbian.com 500 http://beta.armbian.com jammy/main all Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=main,b=all origin beta.armbian.com 500 http://beta.armbian.com jammy/main armhf Packages release o=Armbian,a=jammy,n=jammy,l=Armbian,c=main,b=armhf origin beta.armbian.com 500 https://github.armbian.com/configng stable/main armhf Packages release o=armbian.github.io/configurator,n=stable,l=armbian.github.io/configurator,c=main,b=armhf origin github.armbian.com Pinned packages: orangepiplus:~:% Also attaching putty home screen to show what I am on now, also showing update window where I get those reocurring updates. 0 Quote
Igor Posted Sunday at 10:53 AM Posted Sunday at 10:53 AM 2 hours ago, Domas said: But it seems that none of the other software is being updated. Is this normal? Yes. If you stay with Jammy, you are on old stable user-space, updated directly from Ubuntu, kernels from us. Packages on (old) stable base are rarely updated, usually only if some security problem is detected. If you want to have all packages updating, you need to use Plucky nightly build for your board - accessible at the bottom of download pages. There much more packages will be receiving updates, daily, but that also means bigger risk for running into troubles. 0 Quote
laibsch Posted 12 hours ago Posted 12 hours ago Yes, I would not recommend plucky unless you know you need it. In my humble opinion, and I say this as someone who officially maintains packages in both Debian and Ubuntu, LTS is the way to go. That would be either Jammy or Noble at the moment. I personally have made the switch to noble and that would also be my recommendation. Don't expect a large number of updates on LTS and that is a good thing. Personally, I am not happy about Armbian always updating their kernel on a daily or even more frequent basis. But obviously, as Igor said, there is currently no way to make targeted, manual per-board kernel and firmware releases. So, as of now, if it builds, it gets shipped, even if nothing changed for your board in question. 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.