Difference between revisions of "System Maintenance"
→Quote from Arch Wiki
imported>Fhdk |
imported>Fhdk |
||
| Line 7: | Line 7: | ||
Arch Linux [Manjaro] is a rolling release distribution. That means when new library versions are pushed to the repos, all developers and packagers, rebuild all packages against the libraries. For example, if two packages depend on the same library, upgrading only one package might also upgrade library (as a dependency), which might then break the other package which depends on an older version of the library. | Arch Linux [Manjaro] is a rolling release distribution. That means when new library versions are pushed to the repos, all developers and packagers, rebuild all packages against the libraries. For example, if two packages depend on the same library, upgrading only one package might also upgrade library (as a dependency), which might then break the other package which depends on an older version of the library. | ||
That is why partial upgrades are '''not supported'''. do not use <code> pacman -Sy [package] </code> or any equivalent such as <code> pacman -Sy </code> followed by <code> pacman -S [package] </code>. '''Always''' upgrade (with <code> pacman -Syu </code>) before installing a package. Be very careful when using <code> IgnorePkg </code> and <code> IgnoreGroup </code> for the same reason. If the system has locally installed packages (such as AUR packages), users will need to rebuild them when their dependices | That is why partial upgrades are '''not supported'''. do not use <code> pacman -Sy [package] </code> or any equivalent such as <code> pacman -Sy </code> followed by <code> pacman -S [package] </code>. '''Always''' upgrade (with <code> pacman -Syu </code>) before installing a package. Be very careful when using <code> IgnorePkg </code> and <code> IgnoreGroup </code> for the same reason. If the system has locally installed packages (such as AUR packages), users will need to rebuild them when their dependices receive a soname bump. | ||
If a partial upgrade scenario has been created, and binaries are broken because they cannot find the libraries they are linked against, do not "fix" the problem simply by symlinking. Libraries receive soname bumps when they are not backwards compatible. A simple <code> pacman -Syu </code> to a properly synced mirror will fix the problem as long as pacman is not broken. | If a partial upgrade scenario has been created, and binaries are broken because they cannot find the libraries they are linked against, do not "fix" the problem simply by symlinking. Libraries receive soname bumps when they are not backwards compatible. A simple <code> pacman -Syu </code> to a properly synced mirror will fix the problem as long as pacman is not broken. | ||