Include:Upgrading to Edge: Difference between revisions
(use path template) |
m (Removed unneeded <nowiki> tags, use ic templates and just use the current branch version from {{AlpineLatest}}) |
||
| Line 2: | Line 2: | ||
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 | The crucial difference is, that when editing the {{Path|/etc/apk/repositories}} file, all referenced repository versions (such as {{ic|v{{#expr:{{AlpineLatest}}}}}} or {{ic|latest-stable}}) therein need to be pointing to <code>'''edge'''</code> as in: | ||
<code><nowiki>https://<mirror-server>/alpine/edge/main</nowiki></code> | <code><nowiki>https://<mirror-server>/alpine/edge/main</nowiki></code> | ||
Revision as of 07:29, 12 January 2024
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 as in:
https://<mirror-server>/alpine/edge/main
Warning: Do not enable stable and edge repos at the same time. This can break your system. Either use edge or stable.
After upgrading to edge, the currently installed edge version may be checked with
$ cat /etc/alpine-release
and referring to the build date that is attached to the release.