|
|
| Line 1: |
Line 1: |
| An upgrade of Alpine Linux from a stable version to the rolling development version, ''edge'' can be done in a few simple steps. (These instructions assume that Alpine Linux is installed to a hard drive, rather than run-from-RAM.)
| |
|
| |
|
| To begin, you need to update your {{Path|/etc/apk/repositories}} file. Here are some shortcuts for doing so:
| | 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]]. |
| :* Launch {{Cmd|setup-apkrepos}} Enter {{Key|e}} to edit {{Path|/etc/apk/repositories}}. Change the version number (such as <var>v3.2</var>) to '''edge'''.
| |
| :* Or, edit the file in place: {{Cmd|sed -i -e 's/v[[:digit:]]\..*\//edge\//g' /etc/apk/repositories}}
| |
| <!--
| |
| cat /etc/alpine-release | cut -c 0-3
| |
| This is not working at the moment
| |
| cat /etc/alpine-release | cut -c 0-3 | sed -i -e 's/v{}/edge/g' /etc/apk/repositories
| |
| -->
| |
| The result should look like this:
| |
| {{Cat|/etc/apk/repositories|...
| |
| http://dl-3.alpinelinux.org/alpine/edge/main}}
| |
|
| |
|
| <!--
| |
| After updating the repositories file, obtain the latest index (and available packages, if you've [[Local APK cache|enabled APK caching]]):
| |
| {{Cmd|apk update --update-cache}}
| |
|
| |
|
| Next, ensure you have the latest available version of the Alpine Linux Package Manager first before upgrading anything else:
| | 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'''. |
| {{Cmd|apk add --upgrade apk-tools}} | |
| -->
| |
|
| |
|
| Next, upgrade all your packages in one shot: {{Cmd|apk upgrade --update-cache --available}}
| | After the upgrade, the currently installed edge release may be checked with {{Cmd|cat /etc/alpine-release}} and referring to the build date that is attached to the release. |
| The <code>--available</code> switch is used to force all packages to be upgraded, even if they have the same version numbers. Sometimes changes in musl-libc have required doing this.
| |
| | |
| {{Note|You will need to restart any services that have been upgraded to begin using the upgraded versions. If the kernel is upgraded, you will need to reboot to begin using the upgraded version:
| |
| {{Cmd|sync
| |
| reboot}}
| |
| }}
| |
| | |
| To check your current release: {{Cmd|cat /etc/alpine-release}} You will see the build date attached to the release.
| |
|
| |
|
| [[Category:Package Manager]] | | [[Category:Package Manager]] |
| [[Category:Installation]] | | [[Category:Installation]] |
| [[Category:Development]] | | [[Category:Development]] |
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.