https://bugzilla.redhat.com/show_bug.cgi?id=1822971 --- Comment #42 from David Cantrell <dcantrell@xxxxxxxxxx> --- Yeah, sorry about that. The review process states that you need to post both a spec file and an SRPM file. Personally, I just need the SRPM file. I think posting the spec file just makes it easier for reviewers to start by looking at that. When the git repo is created for the package on src.fedoraproject.org, you will import the SRPM using fedpkg. For example: fedpkg co notcurses cd notcurses fedpkg import NOTCURSES.src.rpm Then git status and make sure the files are queued for a commit. Then your first commit on master (which == rawhide) can be done with: fedpkg ci -c -p -s The -c option will generate a "clog", which takes the diff of the %changelog in the spec file since the last commit and uses that for the git commit message. The package git repo commit history is mostly garbage, but I do this since it's mostly consistent with what other people do. I view the package git repo as purely downstream especially if it's for something I maintain. The -p option does a "fedpkg push" after the commit. The -s option adds -s to the git commit to get a signed-off by. We didn't do that when wee migrated pkg-cvs to pkg-git, but it's there now and I try to use it. I do recommend checking your git user.name and user.email and make sure those are set to what you want to use in Fedora. After the ci, you can build: fedpkg build If the upstream notcurses project can generate an SRPM on release, then you can automate the process of doing Fedora builds using the steps above. If you want to go further and set up automatic builds each time you commit to your upstream repo, you can do that with a Copr repository. I do that for my project (rpminspect) so that there's a repo with the latest available development build for people to install. When I make a versioned release, I drop that in the main Fedora repos. See https://github.com/rpminspect/rpminspect for how that integration works. I bundled all of my garbage scripts together that help me automate this stuff at https://github.com/dcantrell/continuous-goodies. Steal, share, etc. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ 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
