March 3, 20224 yr I'm using Armbian 21.08.8 (Bullseye). I want to upgrade to Armbian 22.02.1 but "apt-get update" doesn't offer anything. Reason seems to be that <mirror>/apt/dists is from Feb 1st 2022. OTOH <mirror>/dl contains the new release but "starting from scratch" (download image, write SDcard) implies that I have to rebuild my OMV6 on top of Armbian. Question: When can I expect that <mirror>/apt/dists will be refreshed? Or is there any other way to upgrade my installation?
March 3, 20224 yr Board has no maintainer and therefore support has been dropped. You can use the build script to create your own packages: https://docs.armbian.com/Developer-Guide_Build-Preparation/
March 3, 20224 yr Author @Werner @Heisath According to https://docs.armbian.com/Release_Board-Maintainers heisath is the maintainer for helios4 and the new release is available at <mirror>/dl/helios4/archive. But the problem is not helios4-centric: <mirror>/apt/dists is from Feb 1, so I think the "inline" upgrade problem is valid for all platforms.
March 3, 20224 yr Oh, my bad, I though you were talking about Helios64. Never mind then. Though no clue why packages are missing.
March 3, 20224 yr Author @Werner Because this problem is a generic one and affects all supported platforms, I recommend to move this thread to a more general and more active forum. The question is: How to upgrade bullseye from armbian 21.08.8 to armbian 22.02.1 via apt as long as the apt/dists branch of a armbian mirror is frozen at Feb 1st 2022? Thank you in advance
March 3, 20224 yr Helios4 is supported and I am the maintainer, thats correct. I tested bullseye on the device, it works as expected. On the issue on not existing packages I can't help unfortunately. I did confirm this issue though: root@cfp-router:~# apt update Get:1 http://security.debian.org bullseye-security InRelease [44.1 kB] Hit:2 http://deb.debian.org/debian bullseye InRelease Get:3 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB] Get:4 http://deb.debian.org/debian bullseye-backports InRelease [44.2 kB] Hit:5 http://armbian.12z.eu/apt bullseye InRelease Get:6 http://deb.debian.org/debian bullseye-backports/main armhf Packages.diff/Index [63.3 kB] Get:7 http://deb.debian.org/debian bullseye-backports/main all Contents (deb).diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian bullseye-backports/main armhf Contents (deb).diff/Index [63.5 kB] Get:9 http://deb.debian.org/debian bullseye-backports/contrib armhf Packages.diff/Index [14.0 kB] Get:10 http://deb.debian.org/debian bullseye-backports/main armhf Packages T-2022-03-02-1402.19-F-2022-02-27-0802.11.pdiff [7,572 B] Get:11 http://deb.debian.org/debian bullseye-backports/main all Contents (deb) T-2022-03-02-1402.19-F-2022-02-27-1401.47.pdiff [1,125 B] Get:12 http://deb.debian.org/debian bullseye-backports/main armhf Contents (deb) T-2022-03-02-0201.01-F-2022-02-27-0802.11.pdiff [402 B] Get:10 http://deb.debian.org/debian bullseye-backports/main armhf Packages T-2022-03-02-1402.19-F-2022-02-27-0802.11.pdiff [7,572 B] Get:11 http://deb.debian.org/debian bullseye-backports/main all Contents (deb) T-2022-03-02-1402.19-F-2022-02-27-1401.47.pdiff [1,125 B] Get:12 http://deb.debian.org/debian bullseye-backports/main armhf Contents (deb) T-2022-03-02-0201.01-F-2022-02-27-0802.11.pdiff [402 B] Get:13 http://deb.debian.org/debian bullseye-backports/contrib armhf Packages T-2022-03-02-0201.01-F-2022-03-01-2001.26.pdiff [418 B] Get:13 http://deb.debian.org/debian bullseye-backports/contrib armhf Packages T-2022-03-02-0201.01-F-2022-03-01-2001.26.pdiff [418 B] Fetched 342 kB in 18s (18.6 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@cfp-router:~# apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@cfp-router:~# apt list --installed | grep linux WARNING: apt does not have a stable CLI interface. Use with caution in scripts. binutils-arm-linux-gnueabihf/stable,now 2.35.2-2 armhf [installed,automatic] console-setup-linux/stable,now 1.205 all [installed,automatic] libselinux1/stable,now 3.1-3 armhf [installed] linux-base/stable,now 4.6 all [installed] linux-dtb-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-headers-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-image-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-libc-dev/now 21.11.0-trunk.2 armhf [installed,local] linux-u-boot-clearfogpro-current/bullseye,now 21.08.8 armhf [installed] util-linux/stable-security,now 2.36.1-8+deb11u1 armhf [installed] root@cfp-router:~# EDIT: It seems like Repo rebuild is still in progress: https://github.com/armbian/build/actions/runs/1927292054
March 3, 20224 yr Author @Heisath Thank you for your clarification. Than I practice patience until the repo rebuild will be completed. In the meantime I'm observing the build train #267.
March 3, 20224 yr http://armbian.hosthatch.com/apt/pool/main/l/linux-5.15.25-mvebu/ Checking there, it seems like the packages for 5.15 mvebu already exist. Maybe mirrors are still syncing.
March 3, 20224 yr 3 hours ago, Heisath said: It seems like Repo rebuild is still in progress: That goes to beta.armbian.com ... stable repository needs few days to get in sync. First files are synced then after i think 48h index ...
March 5, 20224 yr Seems weird or really kinda broken. Its been now 5days(?) since release, I ran those commands, no newer versions found: root@cfp-router:~# apt update Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://deb.debian.org/debian bullseye-backports InRelease Hit:5 http://mirror.armbian.de/apt bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@cfp-router:~# apt list linux-image-current-mvebu Listing... Done linux-image-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] N: There are 5 additional versions. Please use the '-a' switch to see them. root@cfp-router:~# apt list linux-image-current-mvebu -a Listing... Done linux-image-current-mvebu/now 21.11.0-trunk.1 armhf [installed,local] linux-image-current-mvebu/bullseye 21.08.1 armhf linux-image-current-mvebu/bullseye 21.08 armhf linux-image-current-mvebu/bullseye 21.05.1 armhf linux-image-current-mvebu/bullseye 21.02.3 armhf linux-image-current-mvebu/bullseye 21.02.2 armhf If I check the mirror apt was using manually: http://mirror.armbian.de/apt/pool/main/l/linux-5.15.25-mvebu/ there clearly are current files 22.02.1 which should be used. Still calling apt with explicit version gives: root@cfp-router:~# apt install linux-image-current-mvebu=22.02.1 Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Version '22.02.1' for 'linux-image-current-mvebu' was not found
March 5, 20224 yr Author @Heisath > Seems weird or really kinda broken. Its been now 5days(?) since release If I have a look at any mirror the situation is: - The "dl" subtree is up-to-date. - The "apt/pool" subtree is up-to-date. - The "apt/dists" (where apt-get is looking for updates) subtree is of Feb 1st.
March 5, 20224 yr Some packages form 22.02 are present in the index, some not. I think its related to this: I have re-added those packages but dunno if it will help. Manual recreation of repository, as a known workaround, takes hours, which I can't possibly find just like that ...
March 5, 20224 yr Author @Igor I just used http://imola.armbian.com/apt for the upgrade and at the end the system rebooted successfully (Linux 5.15.25-mvebu | Armbian 22.02.1). Thank you for your help. I conclude that I'm the only one on any platform to upgrade a running system to 22.02 now using apt-get. Or, is there any other method for upgrading without starting from scratch with a release package?
March 5, 20224 yr 2 hours ago, FredK said: Or, is there any other method for upgrading without starting from scratch with a release package? No, this is correct way. The problem was on (our) server side.
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.