DevHeads.net

Postings by Adam Williamson

2018-04-09 @ 16:00 UTC - Fedora 28 Blocker Review Meeting

# F28 Blocker Review meeting
# Date: 2018-04-09
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have 6 proposed blockers and 2 proposed freeze exception
issues for Final to review, so let's have a review meeting on Monday.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

2018-04-09 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2018-04-09
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We didn't look at the pending release criteria proposals last week as
several folks were on vacation, so let's look at them tomorrow! That's
all I really have for the agenda, so it could be a quick meeting.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Criteria proposals
3.

2018-04-02 @ 15:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2018-04-02
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We didn't meet for the last few weeks due to Beta work, so let's get
together and check in on where we're at.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 28 status
3. Test Day status
4. Criteria proposals
5. Open floor

2018-04-02 @ 16:00 UTC - Fedora 28 Blocker Review Meeting

# F28 Blocker Review meeting
# Date: 2018-04-02
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have 3 proposed blockers and 4 proposed freeze exception
issues for Final to review, so let's have a review meeting on Monday.

If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

2018-03-26 @ 16:00 UTC - Fedora 28 Blocker Review Meeting

# F28 Blocker Review meeting
# Date: 2018-03-26
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have several proposed blockers and freeze exception issues
to review, so let's have a review meeting on Monday.

If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

Proposal to CANCEL: 2018-03-26 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. Once again,
F28 Beta validation will be the focus this week: go/no-go is on Thursday
(again), and we'll be trying to get things in shape by then (again).

If anyone would like to have a meeting, and is willing to run it in my
place, please just go ahead and send an announcement mail (and, of
course, show up to run the meeting on Monday). Thanks!

There *will* be a blocker review meeting, of course.

Unannounced soname bump (Rawhide): poppler (libpoppler.so.73 -> libpoppler.so.74)

poppler was updated from 0.62.0-2 to 0.63.0-1 in Rawhide on 2018-03-23.
This update bumped the soname from libpoppler.so.73 to libpoppler.so.74.
This soname bump was not announced, as it is supposed to be.

poppler has many dependencies. This is the list dtardon posted last
time he correctly announced an soname bump:

boomaga
calligra
cups-filters
evas-generic-loaders
gambas3
gdal
gdcm
inkscape
kf5-kfilemetadata
libreoffice
okular
pdf2djvu
poppler-sharp
texlive
texworks

These and their dependencies are now all broken.

Call for testing: more Fedora 28 Beta blocker-fixing updates

Hey folks! Just a note that there are some more F28 Beta blocker-fixing
updates that could use some testing and feedback:

1. <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c066076a2" title="https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c066076a2">https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c066076a2</a>

This is an anaconda update that fixes a bug in recent versions: if you
did a live install and both created a user account and set a root
password, the root account wound up locked.

2018-03-19 @ ** 16:00 ** UTC - Fedora 28 Blocker Review Meeting

# F28 Blocker Review meeting
# Date: 2018-03-19
# Time: ** 16:00 ** UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks!

Proposal to CANCEL: 2018-03-19 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. We'll be
mainly in F28 Beta validation mode this week: go/no-go is on Thursday
and we'll be trying to get things in shape by then.

If anyone would like to have a meeting, and is willing to run it in my
place, please just go ahead and send an announcement mail (and, of
course, show up to run the meeting on Monday). Thanks!

Call for testing: Fedora 28 blocker / FE updates

Hi folks!

I'm not doing a full blocker status mail right now (it's Saturday...),
but we do have several updates intended to fix proposed or accepted
blocker or FE issues ATM. It'd be great if we could get testing on
these updates so they're ready to go (or, of course, if you find
issues, we know *not* to send them out). Here they are:

1. <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2018-9877df9844" title="https://bodhi.fedoraproject.org/updates/FEDORA-2018-9877df9844">https://bodhi.fedoraproject.org/updates/FEDORA-2018-9877df9844</a>

This is for shim-signed, part of UEFI booting, especially Secure Boot
booting.

2018-03-12 @ ** 16:00 ** UTC - Fedora 28 Blocker Review Meeting

# F28 Blocker Review meeting
# Date: 2018-03-12
# Time: ** 16:00 ** UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have four proposed blockers and nine proposed freeze
exceptions for Fedora 28 Beta, so let's have a review meeting tomorrow.

Note that daylight savings time started in North America (mostly)
today, so the meeting is now an hour earlier in UTC. If you changed
your clocks forward today, the meeting will be at the same local time
as before.

2018-03-12 @ ** 15:00 ** UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2018-03-12
# Time: ** 15:00 ** UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We're kind of in the crunch time for Fedora 28 now, and things aren't
looking great, so I figured it'd be a good idea to have a meeting to
sync up on current status and plans for Beta.

Note that daylight savings time started in North America (mostly)
today, so the meeting is now an hour earlier in UTC.

On Ye Olde Foreste of Anciente LLVM Versiones

While rebuilding stuff for "GCC 8 ABI change on x86_64", I noticed we
have a rather magnificent collection of ancient llvm versions:

llvm34
llvm35
llvm3.9
llvm4.0
llvm5.0

None of these is retired (llvm33 and llvm3.7 also exist, but *are*
retired). llvm34 and llvm35 don't build successfully and haven't for
some time. The more recent ones mostly look like they should build,
except they have issues with exhausting RAM on the i686 and armhfp
builders.

Do we actually need all of these for anything? Can we kill some of
them?

Unannounced soname bump (Rawhide): brotli (libbrotli{common,enc,dec}.so.1.0.1 -> libbrotli{common,enc,dec}.so.1)

brotli was updated from 1.0.1-3 to 1.0.3-1 in Rawhide on 2018-03-03.
This update bumped the sonames from libbrotli{common,enc,dec}.so.1.0.1
to libbrotli{common,enc,dec}.so.1 (not a typo, that's really the change).
This soname bump was not announced, as it is supposed to be.

httpd (Apache) and webkit2gtk3 (via woff2) depend on these libs.

php-facedetect license change (BSD to PHP)

I've just bumped php-facedetect to the latest git code on Rawhide and
F28 (to make it build against OpenCV 3.4). This comes with a license
change back from BSD to PHP. Don't think this should affect any
dependencies.

2018-03-05 @ 17:00 UTC - Fedora 28 Blocker Review Meeting

# F28 Blocker Review meeting
# Date: 2018-03-05
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have two proposed blockers for Fedora 28 Beta and we're
entering the freeze, so let's have a review meeting tomorrow.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

2018-03-05 @ 16:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2018-03-05
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's been a couple of weeks since we had a meeting, and we've
had exciting times in release engineering, plus we are now getting
close to the planned Beta release and there's a few other things to
discuss.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

Unannounced soname bump (Rawhide): qpdf (libqpdf.so.18 -> libqpdf.so.21)

qpdf was updated from 7.1.1-4 to 8.0.0-1 in Rawhide on 2018-02-26.
This update bumped the soname from libqpdf.so.18 to libqpdf.so.21 .
This soname bump was not announced, as it is supposed to be, and
dependent packages were not rebuilt.

cups-filters depends on qpdf, so anything that includes cups-filters is
now broken. This includes at least the Astronomy_KDE live image, per
<a href="https://pagure.io/dusty/failed-composes/issue/24#comment-496381" title="https://pagure.io/dusty/failed-composes/issue/24#comment-496381">https://pagure.io/dusty/failed-composes/issue/24#comment-496381</a> .

Once again, folks, *please* announce your soname bumps, and co-ordinate
rebuilds.

Proposal to CANCEL: 2018-02-26 blocker review meeting

Hi folks! I'm proposing we cancel the blocker review meeting for
Monday. There's only one proposed blocker at this time. Obviously the
ongoing troubles with getting composes working are blocking, but we
don't really need a blocker meeting to talk about that :) We'll keep
working on it.

Proposal to CANCEL: 2018-02-26 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
think there are any urgent topics at this time. I won't be around to
run one at that time either, as it happens.

If anyone would like to have a meeting, and is willing to run it in my
place, please just go ahead and send an announcement mail (and, of
course, show up to run the meeting on Monday). Thanks!

2018-02-19 @ 16:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2018-02-19
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

Apologies for the late notice, but we haven't met for a few weeks, so I
thought we could do the meeting tomorrow - there's a few topics we
could talk about.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 28 status and branching
3. TCMSes again
4. Available tickets
5. Open floor

Proposal to CANCEL: 2018-02-12 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. It's a
public holiday here in Canada, and I don't think there are any urgent
topics at this time. We'll definitely catch up with a meeting next
week.

If anyone would like to have a meeting, and is willing to run it in my
place, please just go ahead and send an announcement mail (and, of
course, show up to run the meeting on Monday). Thanks!

Proposal to CANCEL: 2018-02-12 blocker review meeting

Hi folks! I'm proposing we cancel the blocker review meeting for
Monday. Once again there are no proposed blockers for Beta or Final
at this time, so nothing to talk about. Thanks!

Proposal to CANCEL: 2018-02-05 blocker review meeting

Hi folks! I'm proposing we cancel the blocker review meeting for
Monday. There are no proposed blockers for Beta or Final at this
time, so nothing to talk about. Thanks!

Proposal to CANCEL: 2018-02-05 Fedora QA Meeting

Hi folks! I'm proposing we cancel the QA meeting on Monday. I'll be
traveling again, and I don't think there are any urgent topics at this
time.

If anyone would like to have a meeting, and is willing to run it in my
place, please just go ahead and send an announcement mail (and, of
course, show up to run the meeting on Monday). Thanks!

2018-01-29 @ 17:00 UTC - Fedora 28 Blocker Review Meeting

# F28 Blocker Review meeting
# Date: 2018-01-29
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net

Hi folks! We have two proposed blockers for Fedora 28 Beta and one
for Fedora 28 Final, so let's have a review meeting today.

If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: <a href="https://qa.fedoraproject.org/blockerbugs/" title="https://qa.fedoraproject.org/blockerbugs/">https://qa.fedoraproject.org/blockerbugs/</a> .

We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed.

2018-01-29 @ 16:00 UTC - Fedora QA Meeting

# Fedora Quality Assurance Meeting
# Date: 2018-01-29
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

Apologies for the late notice, but we haven't met for a few weeks, so I
thought we could do the meeting tomorrow - there's a few topics we
could talk about.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 28 mass rebuild
3. Update gating (and other gating)
4.

Update gating: status update and info for owners of blocked updates

Hi folks!

So, I just wrote a note updating the status of the update gating
situation, in the FESCo ticket where turning the gating on was
approved.

DNF crashes on group operations in Fedora 27

Just a quick note if you've been seeing strange errors this morning,
like dnf crashing when doing something like a 'groupinstall' or a
'group update': it seems there was a storage issue during
synchronization of repodata for the most recent update push, and that's
causing problems like this. releng is doing an emergency push to get
the data regenerated, which should clean this up.