Pending Package Updates
8 packages which have a newer version in the Git repository than in the pacman repository
Packages get automatically built via msys2/msys2-autobuild.
Maintainers can control the build pipeline here.
After the packages are built they still need to be manually signed and uploaded to the pacman repo, so please be patient :)
Active Jobs: -
| Update Date | Base Package | Repo Version | Git Version | Status | |
|---|---|---|---|---|---|
| 2026-10-26 2026-10-26 11:32:04 (UTC) | filesystem | 2026.10.17-1 | → | 2026.10.18-2 |
Ready for upload
|
| 2026-10-26 2026-10-26 09:36:27 (UTC) | nsinstall | 4.39-1 | → | 4.40-1 |
Ready for upload
|
| 2026-10-26 2026-10-26 08:14:58 (UTC) | python | 3.12.15-1 | → | 3.12.16-1 |
Ready for upload
|
| 2026-10-25 2026-10-25 17:33:50 (UTC) | python-wcwidth | 0.9.3-1 | → | 0.9.4-1 |
Ready for upload
|
| 2026-10-25 2026-10-25 17:31:28 (UTC) | python-merge3 | 0.0.16-1 | → | 1.0.0-1 |
Ready for upload
|
| 2026-10-25 2026-10-25 08:26:00 (UTC) | pass | 1.7.4-1 | → | 1.7.4-2 |
Ready for upload
|
| 2026-10-24 2026-10-24 22:15:34 (UTC) | crosstool-ng | 1.28.0-1 | → | 1.29.0-1 |
Ready for upload
|
| 2026-10-24 2026-10-24 22:14:26 (UTC) | pkgfile | 26-1 | → | 27-1 |
Ready for upload
|
The packages above marked "Ready for upload" are also available in a
special staging pacman
repo. Note that using the staging repo might result in some packages
being broken from time to time as it can contain partial build results
of multi-package rebuilds. To use it add the following to the top of
/etc/pacman.conf:
[staging]
Server = https://repo.msys2.org/staging/
SigLevel = Never
Pending Package Removals
0 packages which are in the pacman repository, but no longer in the Git repository
| Update Date | Repo | Package | Status |
|---|