https://bugzilla.redhat.com/show_bug.cgi?id=973084 --- Comment #26 from Björn Esser <bjoern.esser@xxxxxxxxx> --- (In reply to Marcin.Dulak from comment #25) > OK. i think i have those koji builds, what to do next, 'comps'? So all went fine so far and you now have ready-build pkgs for rawhide and F19. For rawhide your pkg gets imported automaticly after it's been built. If you're not familiar with `vim` as editor you probably want to use another, e.g. `nano`: `export EDITOR="$my_fav"` Replace $my_fav with your prefered editor. You can make this system-default by invoking `echo 'export EDITOR="$my_fav"' > /etc/profile.d/preferred_editor.sh` as root. For the F19 branch you need to tell "bodhi" to push it to the repo: http://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Submit_Package_as_Update_in_Bodhi `fedpkg switch-branch f19 ; fedpkg update` After invoking the commands your editor opens giving you a template to complete: [ htmlcleaner-2.2.1-2.fc19 ] # bugfix, security, enhancement, newpackage (required) type= <--- here goes the type of the update, in your case it's newpackage. enhancement is meant for new upstream release. bugfix and security are self explaining, I think. # testing, stable request=testing <--- keep the default here, directly pushing to stable repo is meant for really urgent security-fixes. (type=security) # Bug numbers: 1234,9876 bugs=973084,11 <--- just delete the `,11` here, bodhi will close your review-bug automatically then. See below. # Description of your update notes= <--- Here is where you give an explanation of your update. On newpkgs I'd propose %description, on enhancements or bugfixes %changelog. All in a row without manual line-breaks. # Enable request automation based on the stable/unstable karma thresholds autokarma=True <--- you can keep the defaults here. stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True <--- See above, bug numbers. # Suggest that users restart after update suggest_reboot=False <--- mostly needed for kernel-updates or some daemons. After you saved the modded template and close the editor your update-request will be send to bodhi. You'll need your FAS-password during progress. You can push your package to stable after 7 days in testing (bodhi will inform you by mail) or it gets auto-pushed when needed karma was reached (other packager-people may test your package and give +1/-1-votes). Adding libs to comps should be avoided, see: https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups?rd=PackageMaintainers/CompsXml#When_to_Edit_comps | Libraries should not be included - they will be pulled in via dependencies You surely want to add your package to Upstream Release Monitoring: http://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Watch_for_updates https://fedoraproject.org/wiki/Upstream_release_monitoring?rd=Upstream_Release_Monitoring If your package is added there, you'll get a new bug opened on bugzilla informing you by mail, everytime there's a new upstream version released. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Iml4fY7alE&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review