Include:Upgrading to Edge: Difference between revisions

Revision as of 06:17, 16 September 2019

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 /etc/apk/repositories file. Here are some shortcuts for doing so:

Launch
setup-apkrepos
Enter e to edit /etc/apk/repositories. Change the version number (such as v3.2) to edge.
Or, edit the file in place:
sed -i -e 's/v[[:digit:]]\..*\//edge\//g' /etc/apk/repositories

The result should look like this:

Contents of /etc/apk/repositories

...
http://dl-3.alpinelinux.org/alpine/edge/main

Next, upgrade all your packages in one shot:

apk upgrade --update-cache --available

The --available 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:

sync reboot

To check your current release:

cat /etc/alpine-release

You will see the build date attached to the release.

@@ 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.
+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.)
-# Add the edge repository to ''/etc/apk/repositories'': {{Cmd|echo http://dl-3.alpinelinux.org/alpine/edge/main >> /etc/apk/repositories}} or just edit the file in-place (replace <var>v2.4</var> with your release): {{Cmd|sed -i -e 's/<var>v2.4</var>/edge/g' /etc/apk/repositories}}
+To begin, you need to update your {{Path|/etc/apk/repositories}} file. Here are some shortcuts for doing so:
-# Upgrade all packages in one shot: {{Cmd|apk upgrade -a -U}}
+:* 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'''.
-# Check your current release: {{Cmd|cat /etc/alpine-release}} You will see the build date attached to the release.
+:* Or, edit the file in place: {{Cmd|sed -i -e 's/v&#91;&#91;:digit:&#93;&#93;\..*\//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}}
 <!--
-cat /etc/alpine-release | cut -c 0-3
+After updating the repositories file, obtain the latest index (and available packages, if you've [[Local APK cache|enabled APK caching]]):
-This is not working at the moment
+{{Cmd|apk update --update-cache}}
-cat /etc/alpine-release | cut -c 0-3 | sed -i -e 's/v{}/edge/g' /etc/apk/repositories
+Next, ensure you have the latest available version of the Alpine Linux Package Manager first before upgrading anything else:
+{{Cmd|apk add --upgrade apk-tools}}
 -->
+Next, upgrade all your packages in one shot: {{Cmd|apk upgrade --update-cache --available}}
+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:Installation]]
 [[Category:Development]]