Upgrading Alpine Linux to a new release branch

From Alpine Linux
Revision as of 12:25, 4 May 2012 by Fab (talk | contribs)
Warning: Make sure that you have a backup of your important data before continuing to update your system..


Upgrading an Alpine Linux Hard-disk installation

When Alpine Linux is installed to hard drive, upgrading the installation is simple.

Upgrading to latest release

Warning: Make sure that you have a backup of your important data before continuing to update your system..


Upgrading an Alpine Linux Hard-disk installation

When Alpine Linux is installed to hard drive, upgrading the installation is simple.

Upgrading to latest release

Template loop detected: Upgrading to latest release

Upgrading to Edge

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

When using edge branch, testing repository can be added as a tagged repository as shown above. Remember that, packages in testing repository have no support.

Warning: Do not enable Main/Community repositories from both stable release branch and 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:

$ cat /etc/alpine-release

Upgrading to Edge

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

When using edge branch, testing repository can be added as a tagged repository as shown above. Remember that, packages in testing repository have no support.

Warning: Do not enable Main/Community repositories from both stable release branch and 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:

$ cat /etc/alpine-release