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 bugzilla.redhat.com.
Bug 1721671
Summary: | mraa fails to build in Fedora rawhide/31 (blocks the Python 3.8 rebuild) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | mraa | Assignee: | Peter Robinson <pbrobinson> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | besser82, fzatlouk, mplch, pbrobinson, sgallagh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | mraa-2.1.0-1.fc32 mraa-2.1.0-1.fc31 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-23 18:02:22 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: | 1700317, 1750908, 1750909, 1686977, 1705306, 1719968, 1732841, 1736936, 1773380, 1785415 |
Description
Miro Hrončok
2019-06-18 20:37:22 UTC
this might be related to the nodejs update from 1:10.16.0-3.fc31 to 1:12.4.0-1.fc31. Reported upstream at https://github.com/intel-iot-devkit/mraa/issues/969 This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. The coordinated rebuild of Python 3.8 has started in the `f32-python` side tag. If you figure out how to rebuild this package, please don't rebuild it in regular rawhide, but use the side tag instead: on branch master: $ fedpkg build --target=f32-python To wait for a build to show up in the side tag, do: $ koji wait-repo f32-python --build=<nvr> Where <nvr> is name-version-release of the source package, e.g. python-foo-1.1-2.fc32. An updated mock config is posted at: http://copr.fedorainfracloud.org/coprs/g/python/python3.8/ Note that it will take a while before the essential packages are rebuilt, so don't expect all your dependencies to be available right away. Thanks. Let us know if you need up to date info, or if you have any questions. PS this message is mass posted to all the bugs that block the PYTHON38 bug. If this is also a Fedora 31 FTBFS bug and you manage to fix it, you can do a f31 build as usual: on branch f31: $ fedpkg build The f32-python side tag has been merged. In order to rebuild the package, do it in regular rawhide, but please wait until python3-3.8 is tagged: $ koji wait-repo f32-build --build python3-3.8.0~b3-3.fc32 If your built already started in f32-python, after it is finished, please tag it to rawhide with: $ koji tag-build f32-pending <nvr> For example: $ koji tag-build f32-pending libreoffice-6.3.0.4-3.fc32 Thanks! (This comment is mass posted to all bugzillas blocking the PYTHON38 tracking bug.) (Python 3.8 has landed in the rawhide buildroot.) Dear Maintainer, your package has not been built successfully in 31. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 31 will be retired. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule Awaiting upstream This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. AFAIK this is a problem with the nodejs bindings. Since neither the nodejs- nor python3- subpackages of mraa and upm can be installed on Fedora 32, would it make sense to temporarily disable the nodejs- packages in order to rebuild the packages, so at least the python3- ones can be installed? (In reply to Miro Hrončok from comment #11) > AFAIK this is a problem with the nodejs bindings. Since neither the nodejs- > nor python3- subpackages of mraa and upm can be installed on Fedora 32, > would it make sense to temporarily disable the nodejs- packages in order to > rebuild the packages, so at least the python3- ones can be installed? Since the real issue comes from SWIG not supporting Nodejs >= 12, I have disabled the Nodejs package for now and opened a separate bug [1] to keep track of this issue. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1824339 FEDORA-2020-8eea868056 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8eea868056 FEDORA-2020-a4f4210b2b has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a4f4210b2b I'd like the update to be pushed to Fedora 32 stable to avoid broken deps on Python 3.7 in the GA repo. The current version does not even install. If the current RC is go, feel free to scratch this. (In reply to Miro Hrončok from comment #15) > I'd like the update to be pushed to Fedora 32 stable to avoid broken deps on > Python 3.7 in the GA repo. > The current version does not even install. Can it go out as a zero day update? I don't believe this is pulled into any of the compose media. It can if the freeze exception would be to dangerous or whatnot. My motivation is not the compose media, but the GA repo (repoqueries and such would return packages dependning on Python 3.7 for the entire lifetime of Fedora 32). It is a minor issue and if QA/releng decides the FE is not worth it, I am fine with that. I'm +1 FE on this, but right now it looks like RC 1.3 may be accepted as GA. If not, I don't have a problem with this being included in the GA repos. BTW I've added the depended upm package to the F32 bodhi update. My request is meant for both of them together. FEDORA-2020-8eea868056 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8eea868056` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8eea868056 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. +1 FE, counting 2, setting to AcceptedFE. FEDORA-2020-a4f4210b2b has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a4f4210b2b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a4f4210b2b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-8eea868056 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-a4f4210b2b has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. |