Bug 1851120
| Summary: | No package builds for rawhide? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ankur Sinha (FranciscoD) <sanjay.ankur> |
| Component: | python-pebble | Assignee: | Martin Liška <mliska> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | eclipseo, mliska, mpolacek |
| 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: | 2020-06-29 07:13:16 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: | 1843751, 1849706 | ||
|
Description
Ankur Sinha (FranciscoD)
2020-06-25 16:18:50 UTC
Sure, can you please advise me how to do that? Sure, you need to follow the same steps that you followed when you built for F32, but instead of the f32 branch, you work on the `master` branch in the git repo. More information here: https://fedoraproject.org/wiki/Package_maintenance_guide#Typical_fedpkg_session If you have specific questions, please feel free to e-mail your sponsor or ask folks on the development channels where lots of package maintainers hang out :) Cheers, Ankur Small howto for brand new package I suggest also to read Configure Your Git and Install the developer client tools here https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join#Configure_Your_Git I give you the following instructions as an example of how to manage a package if you had yours approved: Then you can request the repo for your package (and the branches you want at the same time): https://fedoraproject.org/wiki/ Join_the_package_collection_maintainers?rd=PackageMaintainers/Join#Add_Package_to_Source_Code_Management_.28SCM.29_system_and_Set_Owner Also read fedpkg request-repo --help and fedpkg request-branch --help (You might need to set up the API key for fedpkg to work) fedpkg request-repo python-pebble 1829340 fedpkg request-branch --repo python-pebble f32 fedpkg request-branch --repo python-pebble f31 (and so on) Then you can import your package as described afterward: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join#Check_out_the_module You can test a mockbuild (locally on a chroot) first: fedpkg --release f33 mockbuild --mock-config fedora-rawhide-x86_64 Or a scratch-build (in Koji for testing it builds on all arches correctly): fedpkg --release f33 scratch-build --srpm --fail-fast When your repo requests have been accepted (https://pagure.io/releng/fedora-scm-requests/issues), you can import your package: fedpkg clone python-pebble cd python-pebble fedpkg import pathtoSRPM.srpm git commit -sm "Initial import (#1829340)" fedpkg push fedpkg build Then other branches: fedpkg switch-branch f32 git merge master fedpkg push fedpkg build fedpkg update --type newpackage --bugs 1829340 This last command will push the update to Bodhi: https://bodhi.fedoraproject.org/users/marxin Thank you for the help, it's build now for rawhide: https://src.fedoraproject.org/rpms/python-pebble |