Bug 1785943
| Summary: | Pykka 2.0.2 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tobias <t-fedora> | ||||||
| Component: | pykka | Assignee: | Fabian Affolter <mail> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | mk, projects.rg, t-fedora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://src.fedoraproject.org/rpms/pykka/pull-request/2 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | pykka-2.0.2-2.fc30 pykka-2.0.2-2.fc31 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-01-24 18:51:07 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: | 1787429 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Tobias
2019-12-22 17:00:52 UTC
Just a confirmation that the spec file I've attached yesterday works nicely with the mopidy-3.0.1 package i'm currently working on.
You might want to have a look at the "%package -n python3-%{modname}" (and other sections) lines: the resulting package is named python3-Pykka (note the upper case letter).
Created attachment 1647505 [details]
updated spec (v2)
just noticed that I put my old email in the changelog; fixed. (sorry for the noise)
Comment on attachment 1647505 [details] updated spec (v2) submitted as PR as recommended in #fedora-devel. https://src.fedoraproject.org/rpms/pykka/pull-request/2 Pull request: https://src.fedoraproject.org/rpms/pykka/pull-request/2 As written, I miss the time to actively maintain this package and therefore will go to orphan and announce on the devel mailing list. This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component. I've seen that you have pushed 2.0.2 to rawhide; thanks. I've got some questions still: - should I close the PR now? - are we keeping the name of the python package with an upper case letter (python3-Pykka)? this was changed only a year ago. - looking at the koji build, it looks like the docs package name has changed now too? (to pykka-python-Pykka-doc) - is it possible to get builds for fc30/31 made? Sorry, my bad. I took the package without checking if there are open issues and PRs. Yes, I updated the package to 2.0.2 and build it. Then I saw that you made changes which are improving the package far more than my changes did. I tried to include your work. At the moment (2.0.2-2) the package is not building because of the mentioned issue with python-gevent. - should I close the PR now? Not sure, it would require that you rebase to make it mergable. I suggest to get release that we can build and then go from there. - are we keeping the name of the python package with an upper case letter (python3-Pykka)? this was changed only a year ago. The package name (python3-Pykka) is like the upstream name and this is what the dependency generator will pick up (I assume). - looking at the koji build, it looks like the docs package name has changed now too? (to pykka-python-Pykka-doc) That change was a mistake. Should be fixed with 2.0.2-2. The intention was to use the same style as other packages do for the documentation but then I realize that I'm not allow to do this without the proper mechanism in place. - is it possible to get builds for fc30/31 made? Sure Please tell me when you are in the packager group then I can add you as a co-maintainer. No worries, you've pretty much included everything from my PR anyways. I think I'll repurpose it to work around the test failure (by skipping it)--you decide if you want to merge that (otherwise just close it).
> The package name (python3-Pykka) is like the upstream name and this is what the dependency generator will pick up (I assume).
I haven't considered this. I'm OK with keeping the name as is in order to not break things.
Quick follow up, Fabian: Can you please build pykka 2.0.2 for fc30/31? Done, sorry for the delay. pykka-2.0.2-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-720045b062 pykka-2.0.2-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-74bd8bc3fb pykka-2.0.2-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. pykka-2.0.2-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |