Bug 1655700
Summary: | python3-yarg owns /usr/lib/python3.7/site-packages/tests/... | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | python-yarg | Assignee: | Dhanesh B. Sabane <dhanesh95> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | dhanesh95, edgar.hoch, mhroncok, pkopkan, surkum |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-yarg-0.1.9-4.fc29 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-20 12:06:56 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: |
Description
Miro Hrončok
2018-12-03 17:56:33 UTC
s/yarn/yarg/ "%exclude %{python3_sitelib}/tests" in SPEC file will do the trick. Dhanesh, are you available? i can co-maintain the package with you if you like. Hello Miro, (In reply to Miro Hrončok from comment #3) > Dhanesh, are you available? Thanks for waiting up on me. I'll fix this in a couple of days and notify here. > i can co-maintain the package with you if you like. That'll be great. On second thought, can we get someone who is looking to contribute to Fedora Packaging as a co-maintainer for this? Hello Miro and Juan, (In reply to Juan A. Burgos from comment #2) > "%exclude %{python3_sitelib}/tests" in SPEC file will do the trick. Thanks Juan for the tip. I've added the line in the spec file for the f29[1] and master[2] branches. The fedpkg builds against f29[3] and rawhide[4] are completing successfully. Shall I go ahead and submit an update? [1] https://src.fedoraproject.org/rpms/python-yarg/c/47afa5e6b913b3a5203c59c48bc14cc9c2849f02?branch=f29 [2] https://src.fedoraproject.org/rpms/python-yarg/c/47afa5e6b913b3a5203c59c48bc14cc9c2849f02?branch=master [3] https://koji.fedoraproject.org/koji/buildinfo?buildID=1179117 [4] https://koji.fedoraproject.org/koji/buildinfo?buildID=1179118 > Shall I go ahead and submit an update? Thanks. Please do. > On second thought, can we get someone who is looking to contribute to Fedora Packaging as a co-maintainer for this? Patrik is (cced), I am working on sponsoring him. I he'd be interested, you can hook him in after he gets sponsored. --- On a side note, could you please add the python-sig group to the package? yarg is used by pipenv now. Thanks. python-yarg-0.1.9-4.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-66b092cf2c (In reply to Miro Hrončok from comment #6) > > Shall I go ahead and submit an update? > > Thanks. Please do. > Done. [1] > > On second thought, can we get someone who is looking to contribute to Fedora Packaging as a co-maintainer for this? > > Patrik is (cced), I am working on sponsoring him. I he'd be interested, you > can hook him in after he gets sponsored. > Sounds good! > On a side note, could you please add the python-sig group to the package? > yarg is used by pipenv now. Thanks. I've added the group with commit access. Is that fine or shall I elevate the access to admin level? [1] https://bodhi.fedoraproject.org/updates/FEDORA-2019-66b092cf2c > I've added the group with commit access. Splendid :) > Is that fine or shall I elevate the access to admin level? That fine. python-yarg-0.1.9-4.fc29 has been pushed to the Fedora 29 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-2019-66b092cf2c python-yarg-0.1.9-4.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |