Bug 2039300
| Summary: | python-markups: FTBFS in Fedora Rawhide | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tomáš Hrnčiar <thrnciar> |
| Component: | python-markups | Assignee: | José Matos <jamatos> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | jamatos, mhroncok, thrnciar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-02-03 09:44:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1992484, 2016048 | ||
Sorry, this is not connected with Python 3.11. Please disregard the previous comment. I just noticed in Koschei that python-markups is FTBFS. Description of problem: Package python-markups fails to build from source in Fedora Rawhide. Version-Release number of selected component (if applicable): 3.0.0-5.fc35 Steps to Reproduce: koji build --scratch f36 python-markups-3.0.0-5.fc35.src.rpm Additional info: This package is tracked by Koschei. See: https://koschei.fedoraproject.org/package/python-markups FWIW the most recent version fixes that issue but fails on another test. I have already reported this upstream. The new version in rawhide already builds. I do not expect any breakage from Python 3.11 (famous last words, I know :-) ). https://bodhi.fedoraproject.org/updates/FEDORA-2022-1e8a5127f7 (In reply to José Matos from comment #3) > The new version in rawhide already builds. I do not expect any breakage from > Python 3.11 (famous last words, I know :-) ). > I can confirm, at least for alpha 3 it is true :). https://copr.fedorainfracloud.org/coprs/g/python/python3.11/build/3145504/ Thank you for confirming that. :-) |
python-markups fails to build with Python 3.11.0a3. ====================================================================== FAIL: test_basic (tests.test_restructuredtext.ReStructuredTextTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/builddir/build/BUILD/Markups-3.0.0/tests/test_restructuredtext.py", line 33, in test_basic self.assertEqual(text_expected, text) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError: '<div class="document" id="hello-world">\n<[170 chars]v>\n' != '<main id="hello-world">\n<h1 class="title"[155 chars]n>\n' - <div class="document" id="hello-world"> + <main id="hello-world"> <h1 class="title">Hello, world!</h1> <p class="subtitle" id="some-subtitle">Some subtitle</p> <p>This is an example <strong>reStructuredText</strong> document.</p> - </div> + </main> ---------------------------------------------------------------------- Ran 29 tests in 0.161s FAILED (failures=1) https://docs.python.org/3.11/whatsnew/3.11.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora-rawhide-x86_64/03138822-python-markups/ For all our attempts to build python-markups with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/python-markups/ 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.11: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/ Let us know here if you have any questions. Python 3.11 is planned to be included in Fedora 37. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.11. 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.