Difference between revisions of "Switching Branches"
From Manjaro
m (added languages and translate tags) |
(Do not use -Syyu) |
||
| (6 intermediate revisions by 5 users not shown) | |||
| Line 2: | Line 2: | ||
__TOC__ | __TOC__ | ||
<translate> | <translate> | ||
= Overview = | = Overview = <!--T:1--> | ||
{{Important|Manjaro specific packages downloaded and installed from the ''Testing branch'' or ''Unstable branch'' will, by nature, not have been fully tested, and may be unstable. | {{Important|Manjaro specific packages downloaded and installed from the ''Testing branch'' or ''Unstable branch'' will, by nature, not have been fully tested, and may be unstable. | ||
<!--T:2--> | |||
Please refer to [[System Maintenance]] Section for important maintenance information.}} | Please refer to [[System Maintenance]] Section for important maintenance information.}} | ||
One of the many features that sets Manjaro apart from other Arch-based distributions is that it uses its own dedicated software branches, rather than relying on those provided by Arch itself. In fact, to ensure continued stability and reliability, Manjaro actually uses three distinct branches: | One of the many features that sets Manjaro apart from other Arch-based distributions is that it uses its own dedicated software branches, rather than relying on those provided by Arch itself. In fact, to ensure continued stability and reliability, Manjaro actually uses three distinct branches: | ||
| Line 11: | Line 12: | ||
* '''Unstable branch''': Unstable is synced several times a day with Arch package releases. Only a subset of Arch packages are modified to suit Manjaro. Those that use ''Unstable'' need to have the skills to get themselves out of trouble when they move their system to this branch. They are the Manjaro users who are most likely to need to use such skills. Due to the feedback from the users of the ''Unstable'' repo, many issues are caught and fixed at this level. Although the very latest software will be located here, <u>using the ''unstable branch'' is usually safe but - in rare cases - may cause issues with your system!</u> | * '''Unstable branch''': Unstable is synced several times a day with Arch package releases. Only a subset of Arch packages are modified to suit Manjaro. Those that use ''Unstable'' need to have the skills to get themselves out of trouble when they move their system to this branch. They are the Manjaro users who are most likely to need to use such skills. Due to the feedback from the users of the ''Unstable'' repo, many issues are caught and fixed at this level. Although the very latest software will be located here, <u>using the ''unstable branch'' is usually safe but - in rare cases - may cause issues with your system!</u> | ||
<!--T:3--> | |||
'''Summing up''', Manjaro packages start their lives in the ''unstable'' branch. Once they are a deemed stable, they are moved to the ''testing'' branch, where more tests will be realized to ensure the package is ready to be submitted to the ''stable'' branch. | '''Summing up''', Manjaro packages start their lives in the ''unstable'' branch. Once they are a deemed stable, they are moved to the ''testing'' branch, where more tests will be realized to ensure the package is ready to be submitted to the ''stable'' branch. | ||
<!--T:4--> | |||
{{BoxSecondary|Note on unstable branch|'''Remember''': Manjaro specific packages such as kernels, kernel modules and Manjaro applications enter the repo on ''unstable'' branch and it is those packages which are considered unstable when they enter. | {{BoxSecondary|Note on unstable branch|'''Remember''': Manjaro specific packages such as kernels, kernel modules and Manjaro applications enter the repo on ''unstable'' branch and it is those packages which are considered unstable when they enter. | ||
<p>Unmodifed packages synced from Arch repo are considered stable as they have already been vetted by Archlinux Community.</p>}} | <p>Unmodifed packages synced from Arch repo are considered stable as they have already been vetted by Archlinux Community.</p>}} | ||
== Changing to another branch == | == Changing to another branch == <!--T:5--> | ||
{{BoxSuccess|Have you considered?|Why not become an active part of the Manjaro community by becoming a tester?}} | {{BoxSuccess|Have you considered?|Why not become an active part of the Manjaro community by becoming a tester?}} | ||
In order to access a branch, you need to change your pacman-mirrors configuration. | In order to access a branch, you need to change your pacman-mirrors configuration. | ||
You should substitute the <font color="green">value colored in green</font> (for illustrative purposes only) to one of the following: ''stable'', ''testing'' | <!--T:6--> | ||
You should substitute the <font color="green">value colored in green</font> (for illustrative purposes only) to one of the following: '''stable''', '''testing''' or '''unstable'''. | |||
sudo pacman-mirrors --api --set-branch <font color="green">{branch}</font> | sudo pacman-mirrors --api --set-branch <font color="green">{branch}</font> | ||
<!--T:7--> | |||
After you changed the branch, rebuild the mirrorlist and update your packages: | After you changed the branch, rebuild the mirrorlist and update your packages: | ||
{{UserCmd|command=sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu}} | |||
== Questions == | == Questions == <!--T:8--> | ||
=== How do I go back after changing to one of the testing branches? === | === How do I go back after changing to one of the testing branches? === | ||
Going back to the stable branch is easy. All you have to do is to repeat the above, and use ''stable'' as the branch value. | Going back to the stable branch is easy. All you have to do is to repeat the above, and use ''stable'' as the branch value. | ||
<!--T:9--> | |||
'''Be aware''' that after switching to a more stable branch you will receive messages from pacman, informing about newer packages installed than available in the repo. Don't be alarmed as the situation will resolve itself when the packages reaches your current branch. | '''Be aware''' that after switching to a more stable branch you will receive messages from pacman, informing about newer packages installed than available in the repo. Don't be alarmed as the situation will resolve itself when the packages reaches your current branch. | ||
<!--T:10--> | |||
If for whatever reason you ''do'' wish to also 'downgrade' packages while changing branches add an extra ''u'' to the pacman command: | If for whatever reason you ''do'' wish to also 'downgrade' packages while changing branches add an extra ''u'' to the pacman command: | ||
{{UserCmd|command=sudo pacman -Syuu}} | |||
=== How do I check, which branch I am currently on? === <!--T:11--> | |||
{{UserCmd|command=pacman-mirrors -G}} | |||
</translate> | </translate> | ||
[[Category:Contents Page{{#translation:}}]] | [[Category:Contents Page{{#translation:}}]] | ||
Latest revision as of 21:52, 9 October 2023
Overview
One of the many features that sets Manjaro apart from other Arch-based distributions is that it uses its own dedicated software branches, rather than relying on those provided by Arch itself. In fact, to ensure continued stability and reliability, Manjaro actually uses three distinct branches:
- Stable branch: The packages that come to stable have gone through roughly a couple of weeks testing by the users of the Unstable/Testing repos, before they get the packages. These packages are usually free of any problems.
- Testing branch: This is the second line of defense. Being a larger number of users than those using Unstable, they refine the work done prior to them by providing feedback on the packages they recieve on updates.
- Unstable branch: Unstable is synced several times a day with Arch package releases. Only a subset of Arch packages are modified to suit Manjaro. Those that use Unstable need to have the skills to get themselves out of trouble when they move their system to this branch. They are the Manjaro users who are most likely to need to use such skills. Due to the feedback from the users of the Unstable repo, many issues are caught and fixed at this level. Although the very latest software will be located here, using the unstable branch is usually safe but - in rare cases - may cause issues with your system!
Summing up, Manjaro packages start their lives in the unstable branch. Once they are a deemed stable, they are moved to the testing branch, where more tests will be realized to ensure the package is ready to be submitted to the stable branch.
Changing to another branch
In order to access a branch, you need to change your pacman-mirrors configuration.
You should substitute the value colored in green (for illustrative purposes only) to one of the following: stable, testing or unstable.
sudo pacman-mirrors --api --set-branch {branch}
After you changed the branch, rebuild the mirrorlist and update your packages:
user $ sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu
Questions
How do I go back after changing to one of the testing branches?
Going back to the stable branch is easy. All you have to do is to repeat the above, and use stable as the branch value.
Be aware that after switching to a more stable branch you will receive messages from pacman, informing about newer packages installed than available in the repo. Don't be alarmed as the situation will resolve itself when the packages reaches your current branch.
If for whatever reason you do wish to also 'downgrade' packages while changing branches add an extra u to the pacman command:
user $ sudo pacman -Syuu
How do I check, which branch I am currently on?
user $ pacman-mirrors -G