

FredK
-
Posts
40 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
System successfully upgraded. No problems detected (so far). Thanks to the team.
-
@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?
-
@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.
-
@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.
-
@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
-
@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.
-
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?
-
Let me describe the solution of the problem, possibly for help another users of Helios4+OMV5+Nextcloud. The individual steps are mentioned in the OMV forum in the thread https://forum.openmediavault.org/index.php?thread/28242-nextcloud-with-letsencrypt-using-omv-and-docker-compose-q-a. User "Morlan" proposed to exchange linuxserver/mariadb by webhippie/mariadb, he prepared a how-to in post #533, I make minor amendments in #536. Now I'm "back in business", MariaDB version is 10.4.8.
-
Hm. Using the attached docker-compose.yml the build version "110.4.17mariabionic-ls9" is updated to the fresh "110.4.17mariabionic-ls10". But "inside" the mariadb container the version stayed at 10.1.47. # docker exec -it nextclouddb /bin/bash root@7f6f464c863c:/# apt list --installed | grep maria WARNING: apt does not have a stable CLI interface. Use with caution in scripts. mariadb-client-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] mariadb-client-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] mariadb-common/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local] mariadb-server/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local] mariadb-server-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] mariadb-server-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] What am I doing wrong? EDIT: See the following post in https://forum.openmediavault.org/index.php?thread/28242-nextcloud-with-letsencrypt-using-omv-and-docker-compose-q-a/&postID=265371#post265371 docker-compose.yml
-
OMV5 on Helios4 is on top of Armbian Buster (see my signature). OMV5 doesn't support nextcloud + MariaDB + swag(letsencrypt) directly. It supports docker plus portainer and yacht for container management. Docker version is: root@helios4:~# apt list --installed | grep docker WARNING: apt does not have a stable CLI interface. Use with caution in scripts. docker-ce-cli/buster,now 5:20.10.3~3-0~debian-buster armhf [installed,automatic] docker-ce/buster,now 5:20.10.3~3-0~debian-buster armhf [installed] docker-compose/stable,now 1.21.0-3 all [installed] golang-docker-credential-helpers/stable,now 0.6.1-2 armhf [installed,automatic] python3-docker/stable,now 3.4.1-4 all [installed,automatic] python3-dockerpty/stable,now 0.4.1-1 all [installed,automatic] python3-dockerpycreds/stable,now 0.3.0-1 all [installed,automatic] "Inside" the MariaDB container mariadb is 10.1.47: root@helios4:~# !494 docker exec -it nextclouddb /bin/bash root@6f5d32139adf:/# apt list --installed | grep maria WARNING: apt does not have a stable CLI interface. Use with caution in scripts. mariadb-client-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] mariadb-client-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] mariadb-common/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local] mariadb-server/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local] mariadb-server-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] mariadb-server-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local] The mariadb docker image is from bionic (ubuntu 18.04). build_version Linuxserver.io version:- 110.4.17mariabionic-ls9 Build-date:- 2021-01-30T06:00:22+00:00 Bionic was the last ubuntu release supporting 32bit. An apt-get update takes packages from "http://ports.ubuntu.com/ubuntu-ports bionic". And 10.1.47 is the latest available release.