Include:Upgrading to latest release: Difference between revisions
Dubiousjim (talk | contribs) (refine instructions about first upgrading apk-tools, also remove -U from apk upgrade) |
Prabuanand (talk | contribs) (rephrased sentence to make it easier to read) |
||
(25 intermediate revisions by 12 users not shown) | |||
Line 1: | Line 1: | ||
=== Update Repositories File === | |||
The Repositories file {{Path|/etc/apk/repositories}} can be updated using one of the following methods. | |||
==== 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. | |||
==== Using sed command ==== | |||
{{Cmd| | 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}} | ||
==== Manual editing of {{Path|/etc/apk/repositories}}==== | |||
{{:Include:Using_Internet_Repositories_for_apk-tools}} | |||
{{ | ==== 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}} | |||
{{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>.}} | |||
=== Updating package lists === | |||
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.}} | |||
=== 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: | |||
{{Cmd|# apk add --upgrade apk-tools}} | |||
Next, to upgrade all installed packages: | |||
{{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 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: | |||
{{Cmd|sync | {{Cmd|sync | ||
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
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
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
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
--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.
sync reboot