Include:Upgrading to Edge: Difference between revisions

Revision as of 13:16, 5 July 2021

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.2 or latest-stable) therein need to be pointing to edge.

After the upgrade, the currently installed edge release may be checked with

cat /etc/alpine-release

and referring to the build date that is attached to the release.

Revision as of 13:16, 5 July 2021 (view source) Sb1 (talk \| contribs) m (replace replicated (duplicate) info with proper wiki link) ← Older edit		Revision as of 13:16, 5 July 2021 (view source) Sb1 (talk \| contribs) mNo edit summary Newer edit →
Line 1:		Line 1:

	An upgrade of Alpine Linux from a stable version to the rolling development version ''edge'' basically requires the same steps as [[Upgrading_Alpine#Upgrading_to_latest_release\|Upgrading to latest release]].		An upgrade of Alpine Linux from a stable version to the rolling development version ''edge'' basically requires the same steps as [[Upgrading_Alpine#Upgrading_to_latest_release\|Upgrading to latest release]].


	The crucial difference is, that when editing the {{Path\|/etc/apk/repositories}} file, all referenced repository versions (such as <var>v3.2</var> or <var>latest-stable</var>) therein need to be pointing to '''edge'''.		The crucial difference is, that when editing the {{Path\|/etc/apk/repositories}} file, all referenced repository versions (such as <var>v3.2</var> or <var>latest-stable</var>) therein need to be pointing to '''edge'''.