Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1791678 - otf2 fails to build in Fedora 32: missing sources and missing buildrequires (autoreconf)
Summary: otf2 fails to build in Fedora 32: missing sources and missing buildrequires (...
Alias: None
Product: Fedora
Classification: Fedora
Component: otf2
Version: 32
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Dave Love
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-01-16 11:12 UTC by Miro Hrončok
Modified: 2020-05-26 08:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-05-26 08:26:44 UTC
Type: Bug

Attachments (Terms of Use)

Description Miro Hrončok 2020-01-16 11:12:19 UTC
otf2 fails to build with Python 3.9.0a2:

+ echo 'Patch #0 (otf2-jinja2.patch):'
Patch #0 (otf2-jinja2.patch):
+ /usr/bin/patch --no-backup-if-mismatch -p1 -b --suffix .jinja2 --fuzz=0
patching file
+ echo 'Patch #1 (otf2-rpath.patch):'
Patch #1 (otf2-rpath.patch):
+ /usr/bin/patch --no-backup-if-mismatch -p1 -b --suffix .rpath --fuzz=0
patching file src/tools/otf2_config/
+ rm -r vendor/python/site-packages
+ autoreconf -fiv
/var/tmp/rpm-tmp.NhDQPt: line 48: autoreconf: command not found
error: Bad exit status from /var/tmp/rpm-tmp.NhDQPt (%prep)

I am quite confused why this errors pops up with Python 3.9 but not in

For the build logs, see:

For all our attempts to build otf2 with Python 3.9, see:

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9:

Let us know here if you have any questions.

Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Miro Hrončok 2020-01-16 11:33:02 UTC
Oh, it's not from git what koschei build, but latest SRPM.

This is not Python 3.9 related.

Koji even gives:

error: Bad file: /builddir/build/SOURCES/otf2-1.5.1.tar.gz: No such file or directory
    Bad file: /builddir/build/SOURCES/otf2-1.5.1.tar.gz: No such file or directory

Comment 2 Victor Stinner 2020-01-16 14:28:23 UTC
Is it a missing build dependency: "autoconf" (providing /usr/bin/autoreconf)?

Comment 3 Dave Love 2020-01-16 16:24:43 UTC
I suspect I cocked up a merge of the spec file; I'll look at it when I get a chance.  I
don't know why the last update apparently wasn't tested; perhaps it was
blocked by something else being broken and I forgot.

Comment 4 Ben Cotton 2020-02-11 17:34:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 5 Miro Hrončok 2020-05-25 13:02:38 UTC
This comment is mass posted to all bugs blocking the Python 3.9 tracker, sorry if it is not 100 % relevant. When in doubt, please ask.

The Python 3.9 rebuild is in progress in a Koji side tag.

If you fix this bug, please don't rebuild the package in regular rawhide, but do it in the side tag with:

    $ fedpkg build --target=f33-python

The rebuild is progressing slowly and it is possible this package won't have all the required build dependencies yet. If that's the case, please just leave the fix committed and pushed and we will eventually rebuild it for you.

You are not asked to go and try rebuild all the missing dependencies yourself. If you know there is a bootstrap loop in the dependencies, let me know and we can untangle it together.

If you want to test your fix or reproduce the failure, you can still use the Copr repo mentioned in the initial comment of this bug:

Comment 6 Dave Love 2020-05-26 08:26:44 UTC
I forgot to close this

Note You need to log in before you can comment on or make changes to this bug.