The phrase, “Imported from arch”, means Arch’s core (vs AUR), correct?
If a package is imported directly from Arch, why would a Manjaro user need to request an update? Wouldn’t the package be automatically updated and go through the Manjaro cycle of Unstable, Testing, Stable.
These updates would be packages from AUR, git, sourceforge or other?
For example, take tzclock (pacman -Si tzclock), it is in the community repo, version 4.2, and the packager is @manjaro.
By happenstance, I saw the tzclock news, “25/feb/2022: current version is 4.3”. It is 4.3 in the AUR. Using branch-compare, it is 4.2 in Unstable, Testing, and Stable. Will Manjaro update this package in the future without any user notification?
If the packager is neither a @arch id or @manjaro id, what does that mean for the package and future updates? I think I counted 37 different domains, including “Unknown Packager” and “Xyne” in the Manjaro sync repository.
AUR has nothing to do with it. Is Arch linux: core, community, extra and multilib.
Some have overlay packages, some have less dependencies and can be pushed right away to stable, some might have security fixes, so, someone from the team has to trigger those updates manually so the mirrors get updated. At least that is how i understand it.
That package is maintained by @linux-aarhus … So you could ask to be updated in
Care to give exact examples? The thing is:
So, would be interesting to know either you rebuild some packages by yourself, or what exact packages you notice to have the Unknown Packager …
Malformed email on Packager