Bug 1793497 - ursa-major fails to build with Python 3.9: no configuration for profile name: koji
Summary: ursa-major fails to build with Python 3.9: no configuration for profile name:...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ursa-major
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Qixiang Wan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON39
TreeView+ depends on / blocked
 
Reported: 2020-01-21 13:40 UTC by Miro Hrončok
Modified: 2020-03-17 09:54 UTC (History)
4 users (show)

Fixed In Version: 0.4.1-1.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-17 09:54:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2020-01-21 13:40:15 UTC
ursa-major fails to build with Python 3.9.0a2:

+ py.test-3
============================= test session starts ==============================
platform linux -- Python 3.9.0a2, pytest-4.6.9, py-1.8.0, pluggy-0.13.0
rootdir: /builddir/build/BUILD/ursa-major-0.3.1
collected 57 items
tests/test_add_module.py FFFFFF.....                                     [ 19%]
tests/test_add_tag_handler.py .....                                      [ 28%]
tests/test_check_config.py FFFFF                                         [ 36%]
tests/test_cli.py ....                                                   [ 43%]
tests/test_koji_service.py .............                                 [ 66%]
tests/test_mbs.py ......                                                 [ 77%]
tests/test_remove_module.py FFFF                                         [ 84%]
tests/test_utils.py .........                                            [100%]
=================================== FAILURES ===================================
...
E           koji.ConfigurationError: no configuration for profile name: koji
...
===================== 15 failed, 42 passed in 2.81 seconds =====================




For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01170188-ursa-major/

For all our attempts to build ursa-major with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/ursa-major/

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:
https://copr.fedorainfracloud.org/coprs/g/python/python3.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 if this package is required a lot, 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 Ben Cotton 2020-02-11 17:31:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 2 Miro Hrončok 2020-03-16 13:26:20 UTC
Qixiang, could you please have look and report this upstream (is that also you?) if needed? Thanks.

Comment 3 Qixiang Wan 2020-03-16 14:16:57 UTC
I have no idea why the tests failed for the old build, however there was a new build passed (built in F32 branch): https://koji.fedoraproject.org/koji/buildinfo?buildID=1462841
So I think we can close this.

Comment 4 Miro Hrončok 2020-03-16 14:23:14 UTC
I've scheduled a build in https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/ursa-major/ to see if it builds with Python 3.9. F32 branch (and rawhide) has Python 3.8.

Comment 5 Miro Hrončok 2020-03-16 14:26:28 UTC
Still fails with koji.ConfigurationError: no configuration for profile name: koji

+ py.test-3
============================= test session starts ==============================
platform linux -- Python 3.9.0a4, pytest-4.6.9, py-1.8.0, pluggy-0.13.0
rootdir: /builddir/build/BUILD/ursa-major-0.3.1
collected 57 items

tests/test_add_module.py FFFFFF.....                                     [ 19%]
tests/test_add_tag_handler.py .....                                      [ 28%]
tests/test_check_config.py FFFFF                                         [ 36%]
tests/test_cli.py ....                                                   [ 43%]
tests/test_koji_service.py .............                                 [ 66%]
tests/test_mbs.py ......                                                 [ 77%]
tests/test_remove_module.py FFFF                                         [ 84%]
tests/test_utils.py .........                                            [100%]

Comment 6 Qixiang Wan 2020-03-16 16:02:49 UTC
(In reply to Miro Hrončok from comment #5)
> Still fails with koji.ConfigurationError: no configuration for profile name:

Hi Miro,

I have no idea why the tests failed due to missing the default 'koji' profile, I tried to get a local env to reproduce that, but unable to find python3-3.9 from koji.

Anyway, we actually disabled unit-tests in the latest build due to another issue (libmodulemd v1 is not available in buildroot), so the test failure should not block building under python3.9 if you rebuild the package with the latest version.

Could you try with 0.4.1 [1] instead of 0.3.1? 

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1462841

Comment 7 Miro Hrončok 2020-03-16 16:12:12 UTC
Do you mind pushing that to master? The copr will pick it.

Comment 8 Miro Hrončok 2020-03-16 16:13:14 UTC
> I tried to get a local env to reproduce that, but unable to find python3-3.9 from koji

Instructions to building in mock: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/

Do `dnf install python3.9` for local venv checks.

Comment 9 Qixiang Wan 2020-03-17 04:13:41 UTC
I've pushed the latest version to master branch.

Comment 10 Miro Hrončok 2020-03-17 09:54:06 UTC
And it builds. Thank You.


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