Dear all, Here is some information regarding the consequences of deploying pkgdb2: * The first and most annoying one is that PkgDB2 having a new API, it needs a new packagedb-cli [1] which is necessary to have `fedpkg retire` working. There is already a bug opened for it [2] but the solution is simply to update your local packagedb-cli F20: https://admin.fedoraproject.org/updates/FEDORA-2014-6393/packagedb-cli-2.2-1.fc20 F19: https://admin.fedoraproject.org/updates/FEDORA-2014-6375/packagedb-cli-2.2-1.fc19 EL6: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1418/packagedb-cli-2.2-1.el6 Note: packagedb-cli now provides a python interface for the pkgdb API ``import pkgdb2client` * The second item is simply based on the observation that so far we have had bug reports for pkgdb on the fedora-infrastructure trac, the bodhi trac as well as the pkgdb2 project on fedorahosted and github. If you could concentrate your bug reports to either of the two last ones it would help getting our attention :) * Finally, the form used in bugzilla to do SCM requests has been updated and now asks for the `Upstream URL` to be specified next to the `Package Name` and `Short Description`. So the template for SCM request is now: New Package SCM Request ======================= Package Name: Short Description: Upstream URL: Owners: Branches: InitialCC: See [3] http://fedoraproject.org/wiki/Package_SCM_admin_requests for more information and examples Thanks for your help! The Fedora Infrastructure development team [1] https://fedorahosted.org/packagedb-cli/ [2] https://bugzilla.redhat.com/1098462 _______________________________________________ devel-announce mailing list devel-announce@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
