Include:Upgrading to latest release: Difference between revisions

From Alpine Linux
mNo edit summary
(rephrased sentence to make it easier to read)
 
(16 intermediate revisions by 7 users not shown)
Line 1: Line 1:
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.
=== Update Repositories File ===


==== Repository Settings ====
The Repositories file {{Path|/etc/apk/repositories}} can be updated using one of the following methods.


First thing is to to edit or check the {{Path|/etc/apk/repositories}} file.
==== Using setup-apkrepos script====
Launch the [[Alpine_setup_scripts#setup-apkrepos|<Code>setup-apkrepos</Code>]] script: {{Cmd|# setup-apkrepos}} Pressing {{Key|e}} will open the file to edit  using [[BusyBox#vi|'''vi''' editor]]. Edit the repository lines to reflect the new version number.


This may be done using one of the following shortcuts.
==== Using sed command ====
:* 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.
Use a one-line command to edit all version numbers in the file "in place". Here's how you'd change <var>v3.19</var> to <var>v3.20</var>: {{Cmd|# sed -i -e 's/<var>v3\.19</var>/<var>v3\.20</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, subsequent manual changes of the version numbers in {{Path|/etc/apk/repositories}} may be avoided for following releases, by having the repository lines refer to "latest-stable" instead of an absolute value:
==== Manual editing of {{Path|/etc/apk/repositories}}====
{{:Include:Using_Internet_Repositories_for_apk-tools}}


{{Cmd|http://dl-3.alpinelinux.org/alpine/latest-stable/main
==== Using '''latest-stable''' instead of version number====
Note, subsequent manual changes of the version numbers in {{Path|/etc/apk/repositories}} may be avoided for future release upgrades by having the repository lines refer to "latest-stable" instead of an absolute value:
 
{{Cat|/etc/apk/repositories|http://dl-3.alpinelinux.org/alpine/latest-stable/main
http://dl-3.alpinelinux.org/alpine/latest-stable/community}}
http://dl-3.alpinelinux.org/alpine/latest-stable/community}}
{{Warning|Changing the repositories to <code>latest-stable</code> may initiate unexpected release upgrades. So beware of the consequences of unexpected release upgrades, when using <code>latest-stable</code>.}}


However, beware of initiating unexpected release upgrades then.
=== Updating package lists ===
 
 
Manual editing of {{Path|/etc/apk/repositories}}:


{{:Include:Using_Internet_Repositories_for_apk-tools}}
With the correct repositories file in place, the latest index list of available packages can be obtained with:
{{Cmd|# apk update}}


{{Tip|Adding the <code>--update-cache</code> or <code>-U</code> to another apk command, as in <code>apk add -U ...</code> or <code>apk upgrade -U</code>, has the same effect as always running <code>apk update</code> immediately before the other apk command. Instead of auto-update it only if the index has not been updated recently.}}


==== Package upgrades ====
=== Upgrading packages ===


Sometimes it is required to first upgrade just the Alpine Linux Package Manager itself to the latest available version, i.e. before upgrading any other package. This was the case, for example, when upgrading from a version of Alpine before 2.3.0_rc1. But  always doing so should't hurt, either:
At times it is required to first upgrade just the Alpine Linux Package Manager itself to the latest available version, before upgrading any other package. This was the case, for example, when upgrading from a version of Alpine before 2.3.0_rc1. But  simply always doing so shouldn't hurt, either:
{{Cmd|apk add --upgrade apk-tools}}
{{Cmd|# apk add --upgrade apk-tools}}


Next, to upgrade all installed packages:
Next, to upgrade all installed packages:
{{Cmd|apk upgrade --available}}
{{Cmd|# apk upgrade --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 uClibc require doing this.
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 require doing this.


{{Note|All services that have been upgraded need to be restarted, to begin using the upgraded version. If the kernel is upgraded, it's required to reboot to begin using the upgraded version:
{{Note|All services that have been upgraded need to be restarted, to begin using the upgraded version. If the kernel is upgraded, it's required to reboot to begin using the upgraded version:
Line 36: Line 40:
reboot}}
reboot}}
}}
}}


[[Category:Package Manager]]
[[Category:Package Manager]]
[[Category:Installation]]
[[Category:Installation]]

Latest revision as of 06:15, 23 November 2024

Update Repositories File

The Repositories file /etc/apk/repositories can be updated using one of the following methods.

Using setup-apkrepos script

Launch the setup-apkrepos script:

# setup-apkrepos

Pressing e will open the file to edit using vi editor. Edit the repository lines to reflect the new version number.

Using sed command

Use a one-line command to edit all version numbers in the file "in place". Here's how you'd change v3.19 to v3.20:

# sed -i -e 's/v3\.19/v3\.20/g' /etc/apk/repositories

Manual editing of /etc/apk/repositories

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

Using latest-stable instead of version number

Note, subsequent manual changes of the version numbers in /etc/apk/repositories may be avoided for future release upgrades by having the repository lines refer to "latest-stable" instead of an absolute value:

Contents of /etc/apk/repositories

http://dl-3.alpinelinux.org/alpine/latest-stable/main http://dl-3.alpinelinux.org/alpine/latest-stable/community
Warning: Changing the repositories to latest-stable may initiate unexpected release upgrades. So beware of the consequences of unexpected release upgrades, when using latest-stable.


Updating package lists

With the correct repositories file in place, the latest index list of available packages can be obtained with:

# apk update

Tip: Adding the --update-cache or -U to another apk command, as in apk add -U ... or apk upgrade -U, has the same effect as always running apk update immediately before the other apk command. Instead of auto-update it only if the index has not been updated recently.

Upgrading packages

At times it is required to first upgrade just the Alpine Linux Package Manager itself to the latest available version, before upgrading any other package. This was the case, for example, when upgrading from a version of Alpine before 2.3.0_rc1. But simply always doing so shouldn't hurt, either:

# apk add --upgrade apk-tools

Next, to upgrade all installed 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 musl require doing this.

Note: All services that have been upgraded need to be restarted, to begin using the upgraded version. If the kernel is upgraded, it's required to reboot to begin using the upgraded version:

sync reboot