DevHeads.net

Summary/Minutes from today's FESCo Meeting (2018-01-12)

===================================
#fedora-meeting: FESCO (2018-01-12)
===================================

Meeting started by jforbes at 16:00:20 UTC. The full logs are available
at
<a href="https://meetbot.fedoraproject.org/fedora-meeting/2018-01-12/fesco.2018-01-12-16.00.log.html" title="https://meetbot.fedoraproject.org/fedora-meeting/2018-01-12/fesco.2018-01-12-16.00.log.html">https://meetbot.fedoraproject.org/fedora-meeting/2018-01-12/fesco.2018-0...</a>
.

Meeting summary
* #1767 F28 Self Contained Changes (jforbes, 16:02:39)
* LINK: <a href="https://pagure.io/fesco/issue/1767" title="https://pagure.io/fesco/issue/1767">https://pagure.io/fesco/issue/1767</a> (jforbes, 16:02:40)
* AGREED: Current self contained changes are approved (+7,0,-0)
(jforbes, 16:06:58)

* #1808 inclusion of crippled (but free?) AAC decoder (jforbes,
16:07:50)
* LINK: <a href="https://pagure.io/fesco/issue/1808" title="https://pagure.io/fesco/issue/1808">https://pagure.io/fesco/issue/1808</a> (jforbes, 16:07:51)
* AGREED: inclusion of crippled (but free?) AAC decoder is approved
(+7,0,-0) (jforbes, 16:15:38)

* #1810 Let's flip the switch on January 15th: gating in Fedora
(jforbes, 16:15:51)
* LINK: <a href="https://pagure.io/fesco/issue/1810" title="https://pagure.io/fesco/issue/1810">https://pagure.io/fesco/issue/1810</a> (jforbes, 16:16:05)
* LINK: <a href="https://src.fedoraproject.org/rpms/waiverdb" title="https://src.fedoraproject.org/rpms/waiverdb">https://src.fedoraproject.org/rpms/waiverdb</a> (pingou,
16:24:22)
* AGREED: Issue #1810: Let's flip the switch on January 15th: gating
in Fedora is approved (+8,0,-0) (jforbes, 16:25:08)

* #1811 F28 System Wide Change: GHC 8.2 (jforbes, 16:25:41)
* LINK: <a href="https://pagure.io/fesco/issue/1811" title="https://pagure.io/fesco/issue/1811">https://pagure.io/fesco/issue/1811</a> (jforbes, 16:25:41)
* AGREED: Issue #1811: F28 System Wide Change: GHC 8.2 is approved
(+9,0,-0) (jforbes, 16:27:57)

* #1812 F28 System Wide Change: Hardening Flags Updates for Fedora 28
(jforbes, 16:28:26)
* LINK: <a href="https://pagure.io/fesco/issue/1812" title="https://pagure.io/fesco/issue/1812">https://pagure.io/fesco/issue/1812</a> (jforbes, 16:28:26)
* AGREED: Issue #1812: F28 System Wide Change: Hardening Flags Updates
for Fedora 28 is approved (+9,0,-0) (jforbes, 16:35:28)
* LINK: <a href="https://pagure.io/fesco/issue/1813" title="https://pagure.io/fesco/issue/1813">https://pagure.io/fesco/issue/1813</a> (jforbes, 16:35:47)
* AGREED: Issue #1813: F28 System Wide Change: Strong crypto settings
is approved (+9,0,-0) (jforbes, 16:38:15)

* Next week's chair (jforbes, 16:38:28)
* maxamillion will chair next week (jforbes, 16:40:55)

* Open Floor (jforbes, 16:41:05)
* LINK: <a href="https://paste.fedoraproject.org/paste/McKrqEwKOyCNQPzoIVfTsA" title="https://paste.fedoraproject.org/paste/McKrqEwKOyCNQPzoIVfTsA">https://paste.fedoraproject.org/paste/McKrqEwKOyCNQPzoIVfTsA</a>
for january 2018 if I got it right. (nirik, 16:47:09)
* LINK:
<a href="https://lists.fedoraproject.org/archives/list/devel- ... at lists dot fedoraproject.org/message/UDXVXLT7JXCY6N7NRACN4GBS3KA6D4M6/" title="https://lists.fedoraproject.org/archives/list/devel- ... at lists dot fedoraproject.org/message/UDXVXLT7JXCY6N7NRACN4GBS3KA6D4M6/">https://lists.fedoraproject.org/archives/list/devel- ... at lists dot fedor...</a>
(and it sounds like feature if you want to use it, but totally
optional) (jforbes, 16:59:11)
* nirik will file a ticket to discussed batched policy (jforbes,
17:10:43)
* everyone should think about and discuss
<a href="https://fedoraproject.org/wiki/Changes/AArch64_Server_Promotion" title="https://fedoraproject.org/wiki/Changes/AArch64_Server_Promotion">https://fedoraproject.org/wiki/Changes/AArch64_Server_Promotion</a>
(nirik, 17:18:02)
* LINK: <a href="https://pagure.io/fesco/issue/1820" title="https://pagure.io/fesco/issue/1820">https://pagure.io/fesco/issue/1820</a> is the batched updates
ticket (nirik, 17:24:58)

Meeting ended at 17:25:48 UTC.

Action Items

Action Items, by person

People Present (lines said)

Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: <a href="http://wiki.debian.org/MeetBot" title="http://wiki.debian.org/MeetBot">http://wiki.debian.org/MeetBot</a>

Comments

Re: Summary/Minutes from today's FESCo Meeting (2018-01-12)

By Kevin Kofler at 01/12/2018 - 21:23

Justin Forbes wrote:
Uh, `dist.abicheck` produces a lot of false positives on:

* libraries that are internal and that nothing should depend on (e.g., in
QupZilla, package `qupzilla`),
* APIs explicitly documented as "private, can change at any version", as
common in all Qt modules (e.g., in QtWebEngine, package `qt5-qtwebengine`).

My packages often fail `dist.abicheck`. It is absolutely not realistic to
expect it to pass for all updates.

Kevin Kofler

Re: Summary/Minutes from today's FESCo Meeting (2018-01-12)

By Dodji Seketeli at 01/25/2018 - 05:45

Kevin Kofler <kevin. ... at chello dot at> a écrit:

For these two cases you can add a suppression specification file to your
package, telling dist.abicheck to not consider those libraries. The
file needs to end with the .abignore extension. This is similar to the
suppression mechanism of the Valgrind tool.

The syntax of a suppression specification file is documented at
<a href="https://sourceware.org/libabigail/manual/libabigail-concepts.html#suppression-specifications" title="https://sourceware.org/libabigail/manual/libabigail-concepts.html#suppression-specifications">https://sourceware.org/libabigail/manual/libabigail-concepts.html#suppre...</a>.

You can test all this by using the fedabipkgdiff[1] tool on your package
(before pushing it to koji) to compare its ABI against the one of the
already-released versions.

[1]: <a href="https://sourceware.org/libabigail/manual/fedabipkgdiff.html" title="https://sourceware.org/libabigail/manual/fedabipkgdiff.html">https://sourceware.org/libabigail/manual/fedabipkgdiff.html</a>

If you feel like they shouldn't fail despite the suppression
specification mechanism, then please file a bug and we'll see what we
can do. This ought to work.

Cheers,