Comments
catanzaro
(F37 update is stable.)
No clue how this happened. The revision number is controlled by rpmautospec so it shouldn't be possible to move backwards like this.
I intended to build 1.13.1-1. I tried again and it is building properly now.
This update has been unpushed.
Sigh, thanks for noticing....
I'll keep this change in rawhide, but I'll send pull requests to affected packages.
I changed my mind. It's easier to just keep the Obsoletes.
This update has been unpushed.
Would you don't do this kind of compatibility change at this timing, or would you modify all dependent package not to break things? https://src.fedoraproject.org/rpms/webkit2gtk3/c/cd0667007e834434cfec9209a91e624f9f9b143f?branch=f35
Oh, wow. OK, I will respin this update to avoid breaking things in F35.
I'll keep this change in rawhide, but I'll send pull requests to affected packages.
Way too late to be bumping soname for F35. Please do this in rawhide only.
This update has been unpushed.
This update has been unpushed.
This update was a mistake. How should I revert this? make a 1.19.1-really-1.18.4 with the old version?
I think that is the best way to do it. It's either that, or bump the epoch.
Why did we update Fedora 34 to a devel release?
This is going badly in F34, lots of crashes. See https://retrace.fedoraproject.org/faf/problems/bthash/?bth=511790c6b67388266556962780207ea2333fe4e6&bth=0921dcbad9b37b444df67251fe6d12a8ae506efa&bth=0cf3749ca3956a288ad5ba34d6b1d5374b40ba29.
Seems ABRT is now crashing for many users when reporting bugs. See: https://retrace.fedoraproject.org/faf/problems/bthash/?bth=511790c6b67388266556962780207ea2333fe4e6&bth=0921dcbad9b37b444df67251fe6d12a8ae506efa&bth=0cf3749ca3956a288ad5ba34d6b1d5374b40ba29
Oops, this update breaks WebKit quite badly, but seems it is too late to pull it. My fault....
OK, since you removed your negative karma, I'll submit this to stable. The bug report will remain open since you report it's not properly fixed.
Needs more karma, or more days in testing.