Manjaro Linux is an Arch-based operating system that installs a continuing package set from Manjaro’s own repositories. The installed system moves forward through package transactions instead of waiting for a replacement release image. A desktop update therefore changes the operating system, libraries and installed programs together. Manjaro Linux adds graphical package and settings controls around that model, but the package state still follows rolling-release rules.
Repository branches control when a package set arrives
Manjaro Linux maintains Stable, Testing and Unstable branches. A branch changes when a tested package set reaches the machine; it is not a switch between separate operating systems. Changing branches requires a mirror refresh and a complete system synchronization. Moving to a slower branch can leave installed packages newer than the selected repositories until that branch catches up.
Mirror choice creates another layer. Manjaro Linux maintains a mirror list that the package manager consults. Changing a branch or mirror does not complete the package transaction by itself. The documented next step synchronizes repository metadata and installed packages with pamac update or pacman -Syu.
A package install can become a partial upgrade
Manjaro Linux does not support partial upgrades. The package database and installed packages need to move together. A metadata-only refresh changes the active package database without completing the installed-package upgrade, which is outside the supported update path.
The documented Pacman path uses pacman -Syu to synchronize metadata and upgrade the installed package set in one transaction. The checkupdates command can list available upgrades without pulling new metadata into the active package database. This distinction matters when the user only wants to inspect pending changes.
Configuration files can require a manual merge
A package upgrade may place a new default configuration beside the existing file with a .pacnew suffix. A removal or replacement can leave a .pacsave copy. Manjaro Linux does not decide automatically that the new default should replace local edits. The pacdiff workflow can show a difference, skip it, remove the new file or overwrite the old one.
Neither automatic choice is safe in every case. Keeping the old file can break a program when its configuration syntax changed. Overwriting it can erase the user’s settings. Some upgrades therefore require a manual merge between the installed configuration and the new default.
The AUR follows a separate support path
The Arch User Repository contains user-maintained build recipes rather than Manjaro repository packages. Building one may require Git and the base-devel tools. Dependencies can also require separate work. Manjaro does not support the resulting AUR package.
An AUR build can request a dependency that the current Manjaro branch does not carry. Updating every repository package does not guarantee that a user-maintained recipe still builds against that branch.
Several kernels can share the boot menu
Manjaro Linux can keep several kernels and select one at startup. Retaining an older working kernel supplies a fallback when a newer one cannot start the hardware. Installing another kernel does not change the kernel in the running session; the machine must reboot into it.
The running kernel must remain installed. Another installed kernel becomes the active one only after the computer reboots into it, so adding a kernel does not replace the kernel used by the current session.
