https://bugzilla.redhat.com/show_bug.cgi?id=1473314 --- Comment #4 from Till Maas <opensource@xxxxxxxxx> --- (In reply to Robert-André Mauchin from comment #3) > I have almost packaged all of the bundle. Awesome work, you are great! > Thus, how shall I proceed? Open a Review request for each package? And then > try to import them in pkgdb? In the end there will have to be one review request for each package. Initially I would suggest to update your copr repo to include all the packages including an updated rclone package that used the dependencies. Then it would be good to start with a few review request of the dependencies to see if there are any common errors. You can mark the review requests to block this bug to make it clear that they are dependencies. > Another question, if you may help, if a package depends on another packages > not yet included like golang-googlegolangorg-api above, how should one > proceed to generate a mock build or a koji scratch build? Wait for the > dependency to be imported via pkgdb, and then only afterwards try the mock > build or koji build? Using copr is the easiest way. AFAIK you can first build your dependencies in copr and then use them to build the next packages. > Also, it says pkgdb is retiring soon, replaced by pagure.io and fedrepo_req, > is there detailed explanation on how to proceed to add a package then? I > read https://pagure.io/fedrepo_req but it's still a bit confusing. This is currently work in progress. Once pkgdb is retired there will be better documentation. Your sponsor or other developers will help you to figure this out. It would be great if you could show your packaging skills by preliminary reviewing other package reviews as documented here: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Show_Your_Expertise_by_Commenting_on_other_Review_Requests This helps sponsors to get convinced that you are ready to be sponsored. -- 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
