Comments
pmatilai
Locally built rpm using the sequoia backend works fine. Thanks a lot for making this available on f36 too! It means we can start using sequoia on rpm upstream CI soon.
regex version mismatches are not related to this rpm update.
NAK, this is a bad design, see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CWQIAKEI6Q7VJJWNGFSRW7ZR47RLFLGY/
Please DO NOT submit updates to stable releases before this is all settled and agreed upon in rawhide.
NAK, this is a bad design, see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CWQIAKEI6Q7VJJWNGFSRW7ZR47RLFLGY/
Please DO NOT submit updates to stable releases before this is all settled and agreed upon in rawhide.
annobin-9.21-1.fc32.x86_64 got rid of the ICE: errors, but only after "ccache -C"
Dropped armv7 revert breaking ARMv7 on some devices.
So this isn't actually based on testing, is it?
These are the two patches I dropped in the rebase because they're in 4.15.1 and they're https://github.com/rpm-software-management/rpm/commit/03c56049a92e0f4f22e4e4f582c59c3f4802553d https://github.com/rpm-software-management/rpm/commit/8e70d0ae413a99fedf0d9b1a8469e641a1fb85d5
The third patch that reverts the detection is still in the Fedora package. So this stuff is exactly as it was in F31 GA.
Dropped armv7 revert breaking ARMv7 on some devices.
WHAT? The two dropped reverts are what went upstream as submitted by yourself, and are part of 4.15.1, the third revert that is in Fedora I left alone and is what I complained about upstream. If you applied some totally different patches to Fedora than what went upstream and didn't even bother to mention it upstream, I'm not going to have a whole lot of sympathy.
Working fine here. Certainly better than the non-installable version currently in F30...
@ignatenkobrain, you obsoleted a fairly critical security update with this nice-to-have enhancement update, invalidating the testing on the original package thus delaying it's route to stable, and dropping the security rating on the way. Damage already done on this one, but don't do that again! Please edit the type and severity on this one to security to match the original if bodhi still allows that.
No I can't:
Builds : pmatilai does not have commit access to rpm-ostree
Builds : Update for rpm-ostree-2018.7-3.fc28 already exists
I'd also prefer not to mix up rpm update testing with something else.
Just so that people know where things stand: this should NOT be pushed to stable yet despite the karma target reached already. This needs time and breadth of testing more than positive karma. If nothing comes up, I'll consider stable by end of next week.
Fixes #1532539, thanks for that.
FWIW the reason for unpushing is the just-emerged https://bugzilla.redhat.com/show_bug.cgi?id=1514608 which looks like a regression in hardlink handling, and the last thing we need right before EOL is a new regression.
This update has been unpushed.
jflory7, this update is not the cause of your problems, something else is. Possibly libsolv appearing older in f27 than f26, but that'd be some cache/mirror artifact because libsolv-0.6.30-1.fc27 exists for F27. But this is not the place to sort out such problems, and adding negative karma to an update pushed to stable already a month ago will not help either.
Working fine based on an evenings worth of general usage.
adamwill, yup - thanks for pointing it out. New update submitted for F25 (and rawhide).
Locally built rpm using this working fine. Thanks a lot for making this available on F37 too!