Postings by Tom Hughes

Peer authentication failure with postgres tests on ppc64 only?

I have a number of packages which use %postgresql_tests_run to start
a postgres server in %check and they all seem to have failed during
the mass rebuild, for example:

<a href="" title=""></a>
<a href="" title=""></a>

The failure is in %postgresql_tests_run when, after it has started
the server it tries to create a database:

+ createdb -h /tmp mockbuild --owner mockbuild -p 36884
BUILDSTDERR: createdb: could not connect to database template1: FATAL:
Peer authentication failed for user "mockbuild"

That basically

Nonresponsive maintainer: devrim

I have been trying to resolve the FTBFS status of geos and related
issued in F24/Rawhide for two months now, without any success as the
maintainer, devrim, is not responding in any meaningful way.

Building packages with clang?

I have a package that struggles to build on 32 bit x86 and arm because
the compiler tends to use so much memory that the builder runs out of

Upstream is aware of the issue, and mentioned that clang uses
considerably less memory to build the problem file so I thought I would
see if building with clang would work.

Unfortunately although it works on F23 I always seem to get link errors
when building with rawhide:

clang++ -o test/standalone/agg_rasterizer_integer_overflow_test-bin
-pthread test/standalone/agg_rasterizer_integer_overflow_test.o
-Ldeps/agg -Lsrc -Lsrc/json -Lsrc/wk

Boost 1.60?

Are we expecting boost 1.60 to land in Rawhide today?

I see 1.60.0-1 built in the f24-boost side tag yesterday and then
1.60.0-2 this morning in the main f24 tag?

Obviously that has triggered a bunch of dependency failures in koschei.


mapnik soname bump in rawhide

An update of mapnik has just completed building in rawhide so the soname
has changed to and dependencies will need to be rebuilt.

It think all of the dependencies are mine anyway, so I shall be working
on rebuilding them now.


Koji read-only filesystem error?

I just had a build fail:

<a href="" title=""></a>

It seems that a filesystem has gone read-only:

Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/koji/", line 1161, in
response = (,)
File "/usr/lib/python2.7/site-packages/koji/", line 156, in run
File "/usr/lib/python2.7/site-packages/koji/", line 182, in
File "/usr/lib/python2.7/", line 150, in makedirs
makedirs(head, mode)
File "/

Updates not getting pushed?

I have updates for both F21 and F22 that were requested for testing on
the 22nd and still haven't been pushed, but I also can't change them
because trying to do so says:

"Unable to add or remove builds from an update that is currently being
pushed to the testing repository"

It's been saying that for at least 24 hours.

Have they got stuck somehow? or is there a general problem with pushing


ARM build error

I'm getting build errors on ARM relating to a memcpy symbol in glibc:

<a href="" title=""></a>

The actual error is:

make: Entering directory
CXX(target) Release/
CXX(target) Release/
CXX(target) Release/
SOLINK_MODULE(target) Release/
/usr/bin/ld: Release/ No symbol version

An everyday tale of dnf

So this morning I cloned an up to date rawhide VM and attempted to convert
it to F22 by using "dnf distro-sync" on it. Obviously that is a fairly advanced
use case but I think one tale of what happened at the end of that process will
highlight why I often find myself shouting WTF at dnf when going beyond basic
install/update of packages. There were other issues along the way before I got
to this point...

Having eventually completed the distro-sync I wanted to check for any orphans
that needed sorting out.

libproj soname bump

It appears the soname of libproj was changed in rawhide yesterday, so
any dependencies will need to be rebuilt.

I'm taking care of mapnik now.


libdwarf build failure with hardened builds

Does anybody have any clue what's going on here:

<a href="" title=""></a>

It's an update to libdwarf, but the actual cause appears to be that it
doesn't like the new hardened build options.

Duplicate packages in f21-updates

It seems I had multiple updates for a couple of packages queued for
stable on F21 and when the queued updates were processed yesterday all
the pending packages were tagged into f21-updates rather than just the
most recent versions.

libdwarf soname bump

I'm about to land a libdwarf update to version 20140519 in rawhide that
includes an soname bump to

There only appears to be one dependant package, dyninst, so that will
need to be rebuilt - a quick check suggests that it doesn't use the
interface that has changed to require the soname bump so a simple
rebuild should suffice.


fedora-review and/or pkgdb problem?

Attempts to run fedora-review seem to be failing today (it was working a
couple of days ago) when it tries to query pkgdb to see if there is
already a package with the same name:

02-23 14:44 requests.packages.urllib3.connectionpool DEBUG "POST
<a href="" title=""></a> HTTP/1.1" 200 1800
02-23 14:44 root DEBUG Exception down the road...
Traceback (most recent call last):
"/usr/lib/python2.7/site-packages/FedoraReview/", line
183, in run

Self Introduction

Having been a Fedora (and RedHat before that) user for more years then I
care to think about I have decided that it must be high time for me to
contribute my first package.

So I have opened a review request for libgxps with the aim of getting
support for XPS files into evince. The review request is here:

<a href="" title=""></a>

Now all I need is a sponsor and some reviews...