Include:Upgrading to Edge: Difference between revisions

From Alpine Linux
(use path template)
m (fixed sentences to add clarity and avoid repetitions)
 
(12 intermediate revisions by 3 users not shown)
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 <code><nowiki>v3.2</nowiki></code> or <code><nowiki>latest-stable</nowiki></code>) therein need to be pointing to <code>'''edge'''</code> as in:
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 follows. {{cat|/etc/apk/repositories|#/media/cdrom/apks
 
http://dl-cdn.alpinelinux.org/alpine/edge/main
<code><nowiki>https://<mirror-server>/alpine/edge/main</nowiki></code>
http://dl-cdn.alpinelinux.org/alpine/edge/community
 
@testing http://dl-cdn.alpinelinux.org/alpine/edge/testing}}
{{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 {{Cmd|$ cat /etc/alpine-release}} and referring to the build date that is attached to the release.
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.


[[Category:Package Manager]]
{{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.}}
[[Category:Installation]]
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}}
[[Category:Development]]

Latest revision as of 16:54, 5 August 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

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