https://bugzilla.redhat.com/show_bug.cgi?id=2192597 --- Comment #23 from Carl George 🤠 <carl@xxxxxxxxxx> --- `fedpkg import` is only used for the initial import from a reviewed SRPM. Going forward, you can use `fedpkg mockbuild` to do a local test, but it's not strictly required. The routine package update workflow would look like this: 1. Edit the spec file. 2. Download the new source tarball, usually with `spectool -g python-setuptools-gettext.spec`. 3. Verify it builds with `fedpkg mockbuild` (optional). 4. `git add python-setuptools-gettext.spec` 5. Upload the new sources to the lookaside cache with `fedpkg new-sources setuptools-gettext-*.tar.gz`. This will also modify the sources and .gitignore files and add them to the git stage. 6. `git commit` 7. `git push` 8. `fedpkg build` 9. `fedpkg update` (if not on the rawhide branch) These commands are described in more detail in the package maintenance guide. https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/ -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2192597 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
