Pending Package Updates
5 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-02-13 2026-02-13 13:35:51 (UTC) | mingw-w64-python-pymupdf | 1.26.7-3 | → | 1.27.1-1 |
Ready for upload
|
| 2026-02-13 2026-02-13 13:35:51 (UTC) | mingw-w64-mupdf | 1.27.0-4 | → | 1.27.1-1 |
Ready for upload
|
| 2026-02-13 2026-02-13 13:35:10 (UTC) | mingw-w64-python-filelock | 3.20.3-2 | → | 3.21.2-1 |
Ready for upload
|
| 2026-02-13 2026-02-13 13:34:47 (UTC) | mingw-w64-benchmark | 1.9.4-1 | → | 1.9.5-1 |
Ready for upload
|
| 2026-02-13 2026-02-13 13:34:17 (UTC) | mingw-w64-thorvg | 1.0.0-1 | → | 1.0.1-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 = NeverPending Package Removals
0 packages which are in the pacman repository, but no longer in the Git repository and can be removed
| Update Date | Repo | Package | Status |
|---|