@petersen, if you want to deliver this breaking change into F40, create a side-tag, place the build in it and summon other maintainers to rebuilt their packages there.
Do you mean bulding from rawhide commits into F40 so that you don't need to push into dist-git? That could work but f40 dist-git branches would left behind. Don't do it please. We should use real commits into f40 branches and do builds against updated pkgconfg in F40 side-tag. I think I will be able to find free time to do it if you don'y know ho to do it.
I tagged pkgconf-2.1.1-1.fc40 into f40-build-side-90987.
So you want to build your perl packages that would be fine,
otherwise I can do it together with a build2 bump.
This update has been submitted for testing by petersen.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
petersen edited this update.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
2.1.1 breaks ABI. struct pkgconf_client_t changed a size. E.g. perl-PkgConfig-LibPkgConf segfaults now.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Works without issues till now
Works without issues till now
@ppisar: I left a comment upstream https://github.com/pkgconf/pkgconf/issues/347#issuecomment-2144996153
So I guess:
build2 perl-Alien-pkgconf perl-PkgConfig-LibPkgConf
need to be rebuilt.
I deliberately updated to 2.1.1 rather than 2.2.0 to avoid a soname bump :palmface:
@petersen, if you want to deliver this breaking change into F40, create a side-tag, place the build in it and summon other maintainers to rebuilt their packages there.
I guess I can do those builds myself using the rawhide builds, right? Only problem is that build2 got rebuilt already...
Do you mean bulding from rawhide commits into F40 so that you don't need to push into dist-git? That could work but f40 dist-git branches would left behind. Don't do it please. We should use real commits into f40 branches and do builds against updated pkgconfg in F40 side-tag. I think I will be able to find free time to do it if you don'y know ho to do it.
No I don't - I am proven packager...
I meant, "No I don't mean that"...
I tagged pkgconf-2.1.1-1.fc40 into f40-build-side-90987. So you want to build your perl packages that would be fine, otherwise I can do it together with a build2 bump.
This update has been unpushed.
Replaced by FEDORA-2024-3f18243dbe