Re: pacman in testing can cause some issues for packagers
On 3/14/24 21:45, Morten Linderud wrote: Unless there is anything else that is cropping up pacman 6.1 is going to land in the stable repositories tomorrow. I've added a -2 rebuild with patches from the future 6.1.1 release of pacman. Hey, Do you think your bae9594a commit [1] can make it to a -3 rebuild before moving to stable? Thanks! [1] https://gitlab.archlinux.org/pacman/pacman/-/commit/bae9594ac1806ce30f2af1de27c49bb101a00d44 -- Regards, Robin Candau / Antiz OpenPGP_0xFDC3040B92ACA748.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: pacman in testing can cause some issues for packagers
Unless there is anything else that is cropping up pacman 6.1 is going to land in the stable repositories tomorrow. I've added a -2 rebuild with patches from the future 6.1.1 release of pacman. -- Morten Linderud PGP: 9C02FF419FECBE16 signature.asc Description: PGP signature
pacman in testing can cause some issues for packagers
Yo, With `pacman` in testing `[core-testing]` there might be some issues for packagers that use `makepkg --geninteg` or `updpkgsums` and submitting the source packages to build.archlinux.org. As the *sums=() array will contain an integrity check for git sources in pacman 6.1 and beyond the older pacman version on build.a.o is not going to understand this and fail the build. Just set the array to 'SKIP' as usual and it should build fine. I'm not aware of any other packager issues as of writing. -- Morten Linderud PGP: 9C02FF419FECBE16 signature.asc Description: PGP signature
