Include:Upgrading to latest release: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 7: | Line 7: | ||
:* 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, 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}} | ||
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 | 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 | ||
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: | {{Path|/etc/apk/repositories}} may also be edited manually: | ||
{{:Include:Using_Internet_Repositories_for_apk-tools}} | {{:Include:Using_Internet_Repositories_for_apk-tools}} | ||
If | If upgrading from a version of Alpine before 2.3.0_rc1, it is neccessary to have the latest available version of the Alpine Linux Package Manager installed first before upgrading anything else: | ||
{{Cmd|apk add --upgrade apk-tools}} | {{Cmd|apk add --upgrade apk-tools}} | ||
Revision as of 11:45, 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
- Launching the corresponding alpine setup script,
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.
/etc/apk/repositories 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
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
If upgrading from a version of Alpine before 2.3.0_rc1, it is neccessary to have the latest available version of the Alpine Linux Package Manager installed 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.
sync reboot