Comments

60 Comments
karma

Oh, sorry, I didn't notice this...

karma

Looks okay.

BZ#1310318 lftp-4.6.5-3.fc24 immediately segfaults
karma

Let's revoke this updates, #1312659

@jportable

At least #1296817 seems fixed as expected. I guess at least some people can see working gphotoframe with this rpm, so I will push this anyway.

Unfortunately as I also see this gphotoframe working, I cannot debug your issue unless you provide some additional information (some more detailed procedure to reproduce your issue, including the DM you are using). Please open a new bug report for non-crashing issue, thank you.

karma

byebug 8.2.1 test suite needs this: it segfaults with ruby 2.2.3 (known issue)

karma

Also confirmed on F-22 that cppcheck / gui works again.

BZ#1278318 cppcheck gui package is missing
BZ#1280242 1.70 does not seem to report any warning
karma

cppcheck and -gui again work.

BZ#1278318 cppcheck gui package is missing
BZ#1280242 1.70 does not seem to report any warning
karma

Does not seem to work (missed reporting when -1 was in testing), bug 1280242 filed.

Breaks upgrade path (F22 -> F23, which also breaks perl dependency when upgrading F22 -> F23). Please submit F23 updatest request first.

karma

Error: Package: meld-3.14.0-2.fc22.noarch (updates-testing) Requires: python-gobject You could try using --skip-broken to work around the problem

python-gobject is available only from pygobject3-3.17.90-2.fc23, not available on F-22. So perhaps adding "Requires: python-gobject" is not the "right" solution even on F-23 (as I can use meld on F-22)

scroll issue is bug 1243203 , which should perhaps be fixed in 3.16.6 (as the upstream reverted the cause commit)

libtool rebuild is needed.

At least not only root but shogun build met with bug 1183242 issue. Every package using doxygen (actually dot) may begin to fail to build with this update and I don't think this is a small issue.

Yes, and still rebasing now on stable branch is dangerous.

Rather, can't the patch to fix _cairo_bentley_ottmann_tessellate_rectangula issue be backported to the curent cairo instead of fully rebasing to 1.14.0? Anyway I think this type of full rebase is dangerous to stable releases.

Why is this rebuild needed? Were there any soversion bump on Qt5 side? And if there was soversion bump on Qt5, the all dependant packages should have pushed altogether anyway - so currently I do not understand why these rebuild was needed.

User Icon mtasaka commented & provided feedback on sl-5.02-1.fc21 4 years ago
karma

sl still shows long irritating animation :)

Any reason why you don't use rubygem-sqlite3-ruby? koji says rubygem- sqlite3-ruby 1.2.4 is already in EL5. Also note that on F-12+ ruby-sqlite3 is blocked and ruby-sqlite3 binary rpm is generated as a subpackage of rubygem- sqlite3-ruby (see bug 472622)