Comments

15 Comments

Yeah, I vaguely remembered they want to finally move over to it (disclaimer: was using it in Gentoo -- uff -- more than a decade ago). Hence this step being a bit of a surprise to me.

karma

Rawhide WFM.

Out of curiosity, what led to disabling LTO?

BZ#1849276 kitty-0.18.0 is available

Re first comment, after some rethinking, it eventually becomes:

  2 Added variables:

    'const qb_version qb_ver'    {qb_ver}
    'const char* const qb_ver_str'    {qb_ver_str}

  1 Removed variable symbol not referenced by debug info:

    facilitynames

Regarding two previous comments, the reasoning was wrong, see https://bugzilla.redhat.com/show_bug.cgi?id=1487787#c12 that justifies the corosync build I've just added.

(also forgot to mention the impact ... pacemaker won't compile with such libqb, but it should we the upcoming respin)

Sorry, found out that the fix changes a precondition for a hardened run-time sanity check that is also included in the build (part of the same PR). Will need to do a respin.

  5 Added variables:

    'const uint8_t qb_ver_major'    {qb_ver_major}
    'const uint8_t qb_ver_micro'    {qb_ver_micro}
    'const uint8_t qb_ver_minor'    {qb_ver_minor}
    'const char* const qb_ver_rest'    {qb_ver_rest}
    'const char* const qb_ver_str'    {qb_ver_str}

  1 Removed variable symbol not referenced by debug info:

    facilitynames

Removed item was never in the header files/meant to be public API. It's expected nothing in the client space uses it.

Re

conflicting requests
nothing provides python3-clufter >= 0.70.0

it's to be known that respective packages are around the corner: https://bodhi.fedoraproject.org/updates/?packages=clufter

Note also that main libglvnd maintainer was not in favor of proceeding with such an update in Fedora 25: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AYQU3BAWGI5ICSAPAHD3DLYGMS7XSNPE/

That only implies that the impact of the update at the cons side is not evaluated, which it likely should as mesa is on critical path.

Objecting this update in Fedora 25 as it is disruptive for sway WM as discussed: https://bugzilla.redhat.com/show_bug.cgi?id=1413579#c14 and on.

It also violates the update policy, specifically

Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. 

Note that sbd had to be rebuilt to catch up on the library provided by pacemaker that got bumped as of https://bodhi.fedoraproject.org/updates/pacemaker-1.1.14-1.fc23. Anyway, that version of pacemaker should make it to the updates repository at about the same time this update makes it to testing, so the disruption should be minimal (you can install pacemaker from testing repository explicitly as a workaround).

Note that sbd had to be rebuilt to catch up on the library provided by pacemaker that got bumped as of this new version.