Include:Upgrading to latest release: Difference between revisions

Revision as of 11:42, 5 July 2021

When Alpine Linux is installed ins sys mode, e.g. on a hard drive, upgrading to a newer stable version is a straightforward package manager operation.

First thing is to to edit or check the /etc/apk/repositories file.

This may be done using one of the following shortcuts.

Launching the corresponding alpine setup script,
setup-apkrepos
and pressing e to edit /etc/apk/repositories. Then adjusting (changing) the repository lines to the new version number by hand.
Or, use a one-liner command to edit (change) all versions in the file "in place". This is how you'd change v2.5 to v2.6:
sed -i -e 's/v2\.5/v2.6/g' /etc/apk/repositories

Note, all subsequent manual changes to the version numbers in

/etc/apk/repositories} to upgrade to following releases may also be avoided, by having the repository lines refer to "latest-stable" instead of an absolute value:

http://dl-3.alpinelinux.org/alpine/latest-stable/main

http://dl-3.alpinelinux.org/alpine/latest-stable/community

However, beware of initiating unexpected release upgrades then.

{Path may also be edited manually:

Edit the /etc/apk/repositories file using any editor of your choice (nano for instance) to edit the Alpine Linux package repositories.

Contents of /etc/apk/repositories

http://dl-3.alpinelinux.org/alpine/v3.19/main
http://dl-3.alpinelinux.org/alpine/v3.19/community

In the above file, to upgrade Alpine Linux from version 3.19 to 3.20, simply replace the number 3.19 by 3.20 in all the places, so that the updated repositories file looks like below:

Contents of /etc/apk/repositories

http://dl-3.alpinelinux.org/alpine/v3.20/main
http://dl-3.alpinelinux.org/alpine/v3.20/community

If you're upgrading from a version of Alpine before 2.3.0_rc1, ensure you have the latest available version of the Alpine Linux Package Manager first before upgrading anything else:

apk add --upgrade apk-tools

Next, upgrade all your packages:

apk upgrade --available

The --available switch is used to force all packages to be upgraded, even if they have the same version numbers. Sometimes changes in uClibc require 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

@@ Line 1: / Line 1: @@
-When Alpine Linux is installed to hard drive, upgrading to a newer stable version is straightforward.
+When Alpine Linux is installed ins '''sys''' mode, e.g. on a hard drive, upgrading to a newer stable version is a straightforward package manager operation.
-To begin, you need to update your {{Path|/etc/apk/repositories}} file. Here are some shortcuts for doing so:
+First thing is to to edit or check the {{Path|/etc/apk/repositories}} file.
-:* Launch {{Cmd|setup-apkrepos}} Enter {{Key|e}} to edit {{Path|/etc/apk/repositories}}. Change the version number by hand.
-:* Or, edit the file in place. This is how you'd change <var>v2.5</var> to <var>v2.6</var>: {{Cmd|sed -i -e 's/<var>v2\.5</var>/<var>v2.6</var>/g' /etc/apk/repositories}}
-:* Or set directly the last stable release on the repository file {{Path|/etc/apk/repositories}} and avoid jump the release number each time: {{Cmd|http://dl-3.alpinelinux.org/alpine/latest-stable/main}} {{Cmd|http://dl-3.alpinelinux.org/alpine/latest-stable/community}}
+This may be done using one of the following shortcuts.
+:* Launching the corresponding alpine setup script, {{Cmd|setup-apkrepos}} and pressing {{Key|e}} to edit {{Path|/etc/apk/repositories}}. Then adjusting (changing) the repository lines to the new version number by hand.
+:* Or, use a one-liner command to edit (change) all versions in the file "in place". This is how you'd change <var>v2.5</var> to <var>v2.6</var>: {{Cmd|sed -i -e 's/<var>v2\.5</var>/<var>v2.6</var>/g' /etc/apk/repositories}}
-Or you could do this manually: {{:Include:Using_Internet_Repositories_for_apk-tools}}
+Note, all subsequent manual changes to the version numbers in {{Path|/etc/apk/repositories} to upgrade to following releases may also be avoided, by having the repository lines refer to "latest-stable" instead of an absolute value: {{Cmd|http://dl-3.alpinelinux.org/alpine/latest-stable/main}} {{Cmd|http://dl-3.alpinelinux.org/alpine/latest-stable/community}} However, beware of initiating unexpected release upgrades then.
+{Path|/etc/apk/repositories}} may also be edited manually:
+{{:Include:Using_Internet_Repositories_for_apk-tools}}
 If you're upgrading from a version of Alpine before 2.3.0_rc1, ensure you have the latest available version of the Alpine Linux Package Manager first before upgrading anything else: