Problem with cmake's PythonInterp in F29 and F28
by Artur Iwicki
I've got a package (colobot) which has a build-time dependency on Python3. The program had a new upstream release today, so I updated the spec file and fired up the builds.
Everything went smooth on rawhide and F30, whereas the F29 and F28 builds failed with a rather amusing error message:
>BUILDSTDERR: CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
>BUILDSTDERR: Could NOT find PythonInterp: Found unsuitable version "1.4", but required
>BUILDSTDERR: is at least "2.7" (found
>BUILDSTDERR: /builddir/build/BUILD/colobot-colobot-gold-0.1.12-alpha/build/%{__python3})
>BUILDSTDERR: Call Stack (most recent call first):
>BUILDSTDERR: /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:376 (_FPHSA_FAILURE_MESSAGE)
>BUILDSTDERR: /usr/share/cmake/Modules/FindPythonInterp.cmake:159 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
>BUILDSTDERR: data/CMakeLists.txt:6 (find_package)
>-- Configuring incomplete, errors occurred!
So, uh, is this in issue with cmake, python3, the project's CMakeLists, or something totally different?
For anyone interested in the koji builds:
rawhide: http://koji.fedoraproject.org/koji/buildinfo?buildID=1215429
fc30: http://koji.fedoraproject.org/koji/buildinfo?buildID=1215430
fc29: http://koji.fedoraproject.org/koji/buildinfo?buildID=1215433
fc28: http://koji.fedoraproject.org/koji/buildinfo?buildID=1215434
2 years
Koji Build Failure Due To Dependency EPEL Dependency Issue
by Chris
The error:
DEBUG util.py:490: BUILDSTDERR: Error:
DEBUG util.py:490: BUILDSTDERR: Problem: conflicting requests
DEBUG util.py:490: BUILDSTDERR: - nothing provides python2-oauthlib
needed by python2-requests-oauthlib-0.8.0-5.el7.noarch
DEBUG util.py:634: Child return code was: 1
This same package builds fine using copr (done so here):
https://copr.fedorainfracloud.org/coprs/lead2gold/apprise/
The spec file entry (that works fine for epel7 on Copr) is:
BuildRequires: python2-requests-oauthlib
BuildRequires: python2-oauthlib
This entry just produces an error that all requirements couldn't be met and
the scratch build aborts then too.
BuildRequires: python-oauthlib
It appears to be an upstream issue... a missing entry in the
python-oauthlib such as:
Provides: python2-oauthlib
I originally thought maybe i should be filing an issue with the oauthlib
group, but then if that were the case, it wouldn't have worked perfectly
fine on Copr.
Thoughts? Advice?
Chris
2 years
HEADS UP: libgif update problems
by Sandro Mani
Hi
I've pushed what looked like a harmless update from libgif-5.1.4 to
libgif-5.1.6 to rawhide/f30, but apparently the dependency generator
didn't like it, since it now dropped the libgif.so provides from
libgif-devel (despite the file being there) and it generated a
libgif.so.7.1.0 provides instead of the previous libgif.so.7 for libgif.
I'm looking into it. If necessary, I'll rebuild affected packages.
Apologies for the inconvenience.
Sandro
2 years
libqalculate - soname change
by Mukundan Ragavan
libqalculate soname bump is happening with v2.9. The following
packages are affected -
plasma-workspace
step
cantor
qalculate-kde
I will rebuild these packages and file bug reports if needed.
Mukundan.
2 years
Non-responsive maintainer: codeblock
by Richard Shaw
Is anyone able to contact Rick? A BZ ticket[1] has not gotten a response
from some time.
Use fedora-active-user it looks like he's logged in recently but all other
activity has been from last year:
$ ./fedora_active_user.py --user codeblock --email relrod(a)redhat.com
Last login in FAS:
codeblock 2019-02-20
Last action on koji:
Fri, 30 Nov 2018 package list entry created: apps-fp-o in f29-infra by
kevin [still active]
Last package update on bodhi:
2018-07-28 20:06:42 on package supybot-fedora-0.4.2-1.el7
Last actions performed according to fedmsg:
ERROR:active-user:This shouldn't happen.
- smooge's meeting titled "Infrastructure (2019-02-21)" ended in
#fedora-meeting-1 on 2019-02-21 09:59:31
I would like to use my provenpackager access to fix the package
python-requests-cache.
Thanks,
Richard
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1629795
2 years