Is the 28 rawhide repo broken?

[George R Goffe]

Hi,
I haven't seen updates from the rawhide repo in over a week. Is it that the "freeipa" situation clogging things up?
Thanks,
George...

This is what I see pending for my system:
Available Upgrades
emacs-auctex.noarch                        12.1-1.fc28                   rawhide
emacs-auctex-doc.noarch                    12.1-1.fc28                   rawhide
emacs-gettext.noarch                       0.19.8.1-13.fc28              rawhide
freeipa-client.x86_64                      4.6.3-1.fc28                  rawhide
freeipa-client-common.noarch               4.6.3-1.fc28                  rawhide
freeipa-common.noarch                      4.6.3-1.fc28                  rawhide
freeipa-server.x86_64                      4.6.3-1.fc28                  rawhide
freeipa-server-common.noarch               4.6.3-1.fc28                  rawhide
freeipa-server-trust-ad.x86_64             4.6.3-1.fc28                  rawhide
python2.x86_64                             2.7.14-9.fc28                 rawhide
python2-brotli.x86_64                      1.0.1-2.fc28                  rawhide
python2-devel.x86_64                       2.7.14-9.fc28                 rawhide
python2-fedora.noarch                      0.10.0-1.fc28                 rawhide
python2-ipaclient.noarch                   4.6.3-1.fc28                  rawhide
python2-ipalib.noarch                      4.6.3-1.fc28                  rawhide
python2-ipaserver.noarch                   4.6.3-1.fc28                  rawhide
python2-kobo.noarch                        0.7.0-6.fc28                  rawhide
python2-kobo-rpmlib.noarch                 0.7.0-6.fc28                  rawhide
python2-libs.x86_64                        2.7.14-9.fc28                 rawhide
python2-mutagen.noarch                     1.40.0-1.fc28                 rawhide
python2-scipy.x86_64                       1.0.0-6.fc28                  rawhide
python2-tkinter.x86_64                     2.7.14-9.fc28                 rawhide
python2-tools.x86_64                       2.7.14-9.fc28                 rawhide
python2-xlrd.noarch                        1.0.0-7.fc28                  rawhide
python3.x86_64                             3.6.4-11.fc28                 rawhide
python3-brotli.x86_64                      1.0.1-2.fc28                  rawhide
python3-devel.x86_64                       3.6.4-11.fc28                 rawhide
python3-ipalib.noarch                      4.6.3-1.fc28                  rawhide
python3-isort.noarch                       4.3.1-1.fc28                  rawhide
python3-kobo.noarch                        0.7.0-6.fc28                  rawhide
python3-kobo-rpmlib.noarch                 0.7.0-6.fc28                  rawhide
python3-libs.x86_64                        3.6.4-11.fc28                 rawhide
python3-mutagen.noarch                     1.40.0-1.fc28                 rawhide
python3-scipy.x86_64                       1.0.0-6.fc28                  rawhide
python3-tkinter.x86_64                     3.6.4-11.fc28                 rawhide
python3-tools.x86_64                       3.6.4-11.fc28                 rawhide
python3-xlrd.noarch                        1.0.0-7.fc28                  rawhide
tex-preview.noarch                         12.1-1.fc28                   rawhide

[Bruno Wolff III]

On Thu, Feb 15, 2018 at 18:54:43 +0000,
  George R Goffe  wrote:
> Hi,
> I haven't seen updates from the rawhide repo in over a week. Is it that the "freeipa" situation clogging things up?
> Thanks,
> George...

There hasn't been a fully successful compose since the 4th. The tentative 
ones almost always produce a repo suitable for updates. Right now there 
are some conflicts from what looks like a poppler upgrade. There were 
also more failures than usual for the gcc 8 mass rebuild.

The rawhide composes are accessible at:
https://kojipkgs.fedoraproject.org/compose/rawhide/

I'm using the following for using the one from this morning:
(You might not want to disable gpgcheck or sslverify though.)
[compose]
name=Compose - Specific compose repo
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/$basearch/os/
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=$basearch
baseurl=https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20180215.n...
enabled=1
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
sslverify=False

[Adam Williamson]

On Thu, 2018-02-15 at 12:58 -0600, Bruno Wolff III wrote:
> On Thu, Feb 15, 2018 at 18:54:43 +0000,
>   George R Goffe  wrote:
> > Hi,
> > I haven't seen updates from the rawhide repo in over a week. Is it that the "freeipa" situation clogging things up?
> > Thanks,
> > George...
>
> There hasn't been a fully successful compose since the 4th.

This is the problem, yes. We've got into a classic situation where a
whole pile of different issues has backed up while composes have been
failing; we fixed the *initial* bug days ago, we're now onto something
like the sixth or seventh.

The initial big change that broke stuff was a new major version of
pykickstart showed up; several other components involved in image
builds turned out to need to be updated against it.

By the time we had that mess unpicked, the mass rebuild had happened
and caused a bunch more fun, and now the inadvertent libevent soname
bump is causing trouble too.

The latest problem we've hit is that qt5-qtwebengine needs rebuilding
for the libevent soname bump, but is failing to build with a pretty
cryptic chromium build problem that also affects the build of the
chromium package (qt5-qtwebengine has its own embedded chromium). I'm
currently trying to debug that, but not getting anywhere terribly fast.
See the failures:

https://koji.fedoraproject.org/koji/taskinfo?taskID=25045527
https://koji.fedoraproject.org/koji/buildinfo?buildID=1023240

We may well wind up needing spot to sort this out, but I'm trying...

[stan]

On Thu, 15 Feb 2018 18:54:43 +0000 (UTC)
George R Goffe  wrote:
> Hi,
> I haven't seen updates from the rawhide repo in over a week. Is it
> that the "freeipa" situation clogging things up? Thanks,
> George...

I think this is due to the mass rebuild, and some changes to
infrastructure.  Someone else here can probably answer more
authoritatively.