Pending Package Updates
6 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 :)
| Update Date | Base Package | Repo Version | Git Version | Status | |
|---|---|---|---|---|---|
| 2025-10-30 2025-10-30 21:18:12 (UTC) | mingw-w64-python-fastapi | 0.120.2-1 | → | 0.120.3-1 |
Ready for upload
|
| 2025-10-30 2025-10-30 17:43:41 (UTC) | mingw-w64-rio | 0.2.32-1 | → | 0.2.33-1 |
Ready for upload
|
| 2025-10-30 2025-10-30 17:07:13 (UTC) | mingw-w64-zed | 0.209.7-1 | → | 0.210.4-1 |
Ready for upload
|
| 2025-10-30 2025-10-30 17:07:01 (UTC) | gradle | 9.1.0-1 | → | 9.2.0-1 |
Ready for upload
|
| 2025-10-30 2025-10-30 16:58:35 (UTC) | mingw-w64-python-pyproj | 3.7.1-2 | → | 3.7.2-1 |
Ready for upload
|
| 2025-10-30 2025-10-30 07:02:38 (UTC) | mingw-w64-python-pillow | 12.0.0-1 | → | 12.0.0-2 |
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 |
|---|