Include:Upgrading to Edge: Difference between revisions
Prabuanand (talk | contribs) (added main and community to /etc/apk/repositories) |
Prabuanand (talk | contribs) No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| 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 {{ic|v{{#expr:{{AlpineLatest}}}}}} or {{ic|latest-stable}}) therein need to be pointing to <code>'''edge'''</code> | 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>. | ||
When using edge branch, '''testing''' repository can be added if the packages that one needs are available only in '''testing''' repository. | |||
{{Note|Remember that, packages in [[Repositories#Testing|testing]] repository have no support.}} | |||
{{cat|/etc/apk/repositories|#/media/cdrom/apks | {{cat|/etc/apk/repositories|#/media/cdrom/apks | ||
http://dl-cdn.alpinelinux.org/alpine/edge/main | http://dl-cdn.alpinelinux.org/alpine/edge/main | ||
http://dl-cdn.alpinelinux.org/alpine/edge/community}} | http://dl-cdn.alpinelinux.org/alpine/edge/community | ||
http://dl-cdn.alpinelinux.org/alpine/edge/testing | |||
}} | |||
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. | |||
{{Warning|Do not enable stable and edge repos 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.}} | {{Warning|Do not enable stable and edge repos 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:Package Manager]] | [[Category:Package Manager]] | ||
[[Category:Installation]] | [[Category:Installation]] | ||
[[Category:Development]] | [[Category:Development]] | ||
Latest revision as of 18:19, 5 September 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.
When using edge branch, testing repository can be added if the packages that one needs are available only in testing repository.
Note: Remember that, packages in testing repository have no support.
Contents of /etc/apk/repositories
#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing
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.
Warning: Do not enable stable and edge repos 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.