Postings by Ralf Corsepius

tracebacks while "git push"ing to Fedora's git


when "git push"ing updates to Fedora's git, I am currently encountering
this kind of tracebacks:

$ git push
Total 0 (delta 0), reused 0 (delta 0)
remote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 1 commits
remote: Traceback (most recent call last):
remote: File
"/usr/lib/python2.7/site-packages/pagure/hooks/", line 394,
in run_project_hooks
remote: changes=changes,
remote: File
"/usr/lib/python2.7/site-packages/pagure/hooks/", line 111,
in runhook
remote: changes=changes,
remote: File

Can't set initial passwd


I am facing a weird problem with creating a new user account:

Create a new user:
# adduser -m tester

Trying to change his passwd:
# passwd tester
Changing password for user tester.

At this point, passwd hangs and doesn't do anything.
I am not getting the "usual" passwd-prompt.

What's going on here?


GCC broken in rawhide?


ATM all rawhide builds are failing for me, because autoconf's tests for
CC are failing.

Digging into details led me to this error:
cc1: error: fail to initialize plugin
annobin: conftest.c: Error: plugin built for compiler version (7.3.1)
but run with compiler version (7.2.1)

AFAIS, GCC in rawhide was updated to GCC-7.3.1, but apparently annobin
wasn't rebuilt, resulting into rawhide now carrying an inconsistent


How to chainbuild in a build override?


I am trying to build a chain of packages in a build override?

I.e. a series of packages: A->B->C

I set up a build override for A, and B built successfully. Now, I would
have expect building C to pickup B from the A-override.

This does not seem to apply. C fails to build, apparently because
building doesn't pickup "B" from A's build override.

Is this a timing issue (Do I need to wait)?

SONAME bump: Update OpenSceneGraph to 3.4.1


I am going to update OpenSceneGraph from 3.4.0 to 3.4.1 on rawhide (for

This will be accompanied with SONAME bumps of various shared libs
supplied by OpenSceneGraph and thus will require rebuilds of several
packages depending on these libs. I intend to take care of these and to
rebuild them.

Unless this update encounters major problems, I am considering to
subsequently also update OpenSceneGraph on fc27.


rawhide packages not getting pushed?


For ca. 3 weeks (or more) buildsys nags me with warning mails on k3d:
k3d has broken dependencies in the rawhide tree:
On x86_64:
k3d- requires

Due to these, I bumped k3d's NEVR to k3d- and built it for
rawhide on 2017-09-11:
<a href="" title=""></a>

However, apparently this package never was pushed into rawhide and the
nag-mails continued.

Is going on?

fedpkg new-sources broken?


I seem to be unable to upload a new tarball for freefem++:

$ fedpkg new-sources freefem++-3.56.tar.gz
DeprecationWarning: fedora.client.bodhi has been deprecated. Please use
bodhi.client.bindings instead.
Uploading: freefem++-3.56.tar.gz
Could not execute new_sources: Fail to upload files.

Killing koji buildjobs


Is there a way to kill hanging koji-buildjobs?

These 2 build jobs (launched by me) seem to be hanging and don't seem to
be wanting to finish (or fail) for 3 days (for reasons unknown to me):

- A f27 real-build:
<a href="" title=""></a>

- A f26 scratch-build:
<a href="" title=""></a>


Intend to retire perl-Log-Any-Adapter-Dispatch


I intend to retire perl-Log-Any-Adapter-Dispatch for Fedora > 25.

- This package currently FTBFSs in fc26,
- This packages doesn't seem to be used by any other package in Fedora.
- Its upstream appears "semi-dead" (Last update from 2013).

If you still need this package, feel free to take over, otherwise I will
retire it for Fedora >= 25, pretty soon.


Headsup: qhull upgrade on rawhide


I intent to upgrade qhull to version 2015.2 on rawhide throughout the
next couple of days/near future.

This is a major upgrade, which will introduce API/ABI/SONAME changes and
likely packaging changes, as well.

Very late Koji certificate expiration warnings


Today (2016-02-29) I received a mail, seemingly having been sent last
night (2016-02-29 01:18 CET), entitled "Your Koji certificate expires
within a week"

This is an automated email sent to inform you that your Fedora Project Koji
certificate is about to expire. Koji certificates are valid for 6
months and
our records indicate that you last recreated yours about 5 months ago
on 2015-09-03.

OK, no mentioning of a accurate date and probably not taking short
months into account in calculation ;) ...

redhat bugzilla probs


When trying to file a BZ, bugzilla just greeter me with this:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /post_bug.cgi.

Reason: Error reading from remote server

Apache Server at Port 443


bodhi2: ACL validation mechanism was unable to determine ACLs


This morning, bodhi2 doesn't allow me to submit an update. After a
seemingly successful login-in, when trying to submit an update, a popup
pops up telling me:

"ACL validation mechanism was unable to determine ACLs"


Bizarre koji error


I am facing a bizarre f23-koji build breakdown:
<a href="" title=""></a>

The interesting part seems to be hidden in this file:
<a href="" title=""></a>

$ git clone -n git://
Cloning into '/var/lib/mock/f23-build-3655660-501262/root/tmp/scmroot/ht'...
fatal: read error: Connection reset by peer

Same result, when retrying:
<a href="" title=""></a>

An f24-build succeeded ca.

Discontinuing perl-Mail-GnuPG


I indent to discontinue and remove perl-Mail-GnuPG from Fedora.

It FTBFS on rawhide, because it seem to suffer from compatibility issues
with gnupg2 >= 2.1.5 [1].

AFAIS, nothing in Fedora uses it, so this step probably won't do much harm.

Should gnupg2 in Fedora < 23 be updated, perl-Mail-GnuPG will rendered
dysfunctional there. I could add "Requires: gnupg2 < 2.1.5" there but
this is something I'd rather not do.


[1] <a href="" title=""></a>

dnf Failed to synchronize cache for repo 'updates'


seems to me, as if "fedora 22 updates" is down:

# dnf --refresh update
RPM Fusion for Fedora 22 - Free - Updates
12 kB/s | 395 B 00:00
RPM Fusion for Fedora 22 - Nonfree - Updates
552 B/s | 395 B 00:00
RPM Fusion for Fedora 22 - Free
3.5 MB/s | 461 kB 00:00
Error: Failed to synchronize cache for repo 'updates' from
Cannot download repomd.xml: Cannot downloa

bodhi: Notified "can be pushed", but refuses to push


Another bodhi/koji issue:

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

bodhi send me an email, notifying me:
2015-02-28 21:56:01: "This update has reached 3 days in testing and can
be pushed to stable now if the maintainer wishes"

However, ATM (2015-03-01 06:33:00 UTC), can not push this update via
"Mark as stable" on
<a href="" title=""></a>

I receive a yellow box telling me: "This update has not yet met the
minimum testing requirements defined in the Package Update Accept

SIMVoleon, SoQt rebuilt against Coin3 on f22 and rawhide


as some already might have noticed, Coin3 is about to land in Fedora.

Therefore, I rebuilt SIMVoleon and SoQt (two addon-packages to Coin),
against Coin3 on rawhide and f22. I do not expect this to impose
problems to Fedora, because I can't spot any packages depending on these
in Fedora.

On Fedora <= 21 these packages will have to stay with Coin2 to avoid
breaking backward-compatibility.

Though it's thinkable to do so, I do not plan to provide Coin3-compiled
versions of these packages for fc20, f21 and Coin2-compiled versions for
fc22, f23, at the moment.

koji is broken


seems to me as if koji has seized operation:

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


Accessing/Logging into the pkgdb


for unknown reasons, I can't login to the pkgdb anymore.

What am I supposed to do? There is no "request reset password" button
nor other helpful information available on the login screen.


Upgrade OpenSceneGraph to 3.2.1


I intend to upgrade OpenSceneGraph to 3.2.1 (Jul 4th) on rawhide.

This change will introduce SONAME bumps in OpenSceneGraph-provided
libraries and thus is likely to introduce broken package dependencies.

I intend to take care about these and to launch rebuilds where necessary.

Depending on how well things work out, I am considering to also upgrade
on f21, but it's too early to have a strong opinion on this.


pkgdb2 acl change-mails contain invalid links


another issue with pkgdb2:

Today somebody processed some pending acl-changes, which caused me to
receive PkgDB-acl-change mails, similar to this:

user: silfreed changed point of contact of package: gpsbabel from:
silfreed to: corsepiu on branch: f20

To make changes to this package see:
<a href="" title=""></a>

The link provided in this mail
(<a href="" title=""></a>) seems invalid. It
returns a 404.


pkgdb2 package/owner CSV list


Before pkgdb2 it was possible to retrieve a plain text CSV list of
package/owners pairs.

What is the corrent URL to achieve the same with pgkdb2 or has this
feature been lost?


OpenSceneGraph-3.2.0/OpenSceneGraph SONAME bump


I intend to upgrade OpenSceneGraph on rawhide to OpenSceneGraph-3.2.0
throughout today.

As a consequence of this, all libraries provided by OpenSceneGraph will
see an SONAME bump, requiring all packages depending on them to be rebuilt.

May-be, I am missing some, but so far, I am aware about this change to
- SimGear
- osgal [1]

I'll rebuild these packages, once the OpenSceneGraph upgrade is in
rawhide (Local test-builts were successful).


[1] This package is orphan, seems dead upstream, the code is rottening,
but it is still in rawhide.

I think, osgal should be retir

F18 metalink urls pointing to development/18 instead of releases/18/Everything


the Fedora 18 metalink-urls as being used in /etc/yum.repo.d/*repo, e.g.$releasever&arch=$basearch,

are still pointing to */development/18
instead of */releases/18/Everything, as they should after a release.


Unexpanded rpm macros in "Requires"


Bug <a href="" title=""></a> has made me
look into some more packages and lets me come up with this finding:

There are several packages in Fedora, which carry unexpanded rpm-macros
in their "Requires" [1]:

beefy-miracle-backgrounds-kde >= %{backgrounds-kde-version}

libpng12(x86-32) = %{epoch}:1.2.50-1.fc18

gecko-libs >= %{gecko_version}

exo-devel >= %{exoversion}


No f18 in bodhi


f18 seems to be missing in bodhi.

I.e., ATM, it seems impossible to push packages to f18.


f17 repos in disorder?


I don't know what is going on, but from what I see, the f17 repositories
currently seem to contain multiple versions of packages and
binary/src.rpm mismatches:



There are several more similar such cases.


f15 koji buildroots broken?


I am observing weird build failures for f15:
<a href="" title=""></a>

The corresponding root.log
(<a href=";name=root.log" title=";name=root.log">;name=root.log</a>)

tells this:
DEBUG ['/usr/bin/yum', '--installroot',
'/var/lib/mock/dist-f15-build-1215765-195489/root/', 'groupinstall',
DEBUG Executing command: ['/usr/bin/yum', '--installroot',
'/var/lib/mock/dist-f15-build-1215765-195489/root/', 'groupinstall',
DEBUG Error: Package: nss-softokn-3.13.1-14.fc15.i686 (bu

Fedora 16 mirrorlist-URLs point to rawhide


Seems as if the f16 split wasn't reflected to the mirrorlists:

<a href=";arch=x86_64" title=";arch=x86_64">;arch=x86_64</a>

returns references to "development/rawhide"

instead of "development/16"