Include:Upgrading to Edge: Difference between revisions

From Alpine Linux
m (fixed sentences to add clarity and avoid repetitions)
(moved content from here to Repositories page)
Line 5: Line 5:
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/community
@testing http://dl-cdn.alpinelinux.org/alpine/edge/testing}}
@testing http://dl-cdn.alpinelinux.org/alpine/edge/testing}}
When using edge branch, [[Repositories#Testing|testing]] repository can be added as a [[Repositories#Tagged repository|tagged repository]] as shown above. Remember that, packages in [[Repositories#Testing|testing]] repository have no support.
{{Warning|Do not enable Main/Community repositories from both [[Repositories#Release Branches|'''stable''']] release branch and [[Repositories#Edge|'''edge''']] at the same time. This can break your system. Either use edge '''or''' stable. If you mix stable and edge repositories, you're on your own.}}
After upgrading to edge, the currently installed edge version i.e the build date that is attached to the '''edge''' release may be checked with command:{{Cmd|$ cat /etc/alpine-release}}

Revision as of 17:38, 3 October 2025

An upgrade of Alpine Linux from a stable version to the rolling development version edge basically requires the same steps as Upgrading to latest release.

The crucial difference is, that when editing the /etc/apk/repositories file, all referenced repository versions (such as v3.22 or latest-stable) therein need to be pointing to edge as follows.

Contents of /etc/apk/repositories

#/media/cdrom/apks http://dl-cdn.alpinelinux.org/alpine/edge/main http://dl-cdn.alpinelinux.org/alpine/edge/community @testing http://dl-cdn.alpinelinux.org/alpine/edge/testing