On Mon, Sep 08, 2014 at 11:55:06AM +0200, Pierre-Yves Chibon wrote:
On Mon, Sep 08, 2014 at 11:31:58AM +0200, Tomas Tomecek wrote:
> Quoting Pierre-Yves Chibon (2014-09-05 17:08:39)
> > New procedure
> > =============
> >
> > * packager opens a review-request on bugzilla
> > * reviewer sets the fedora-review flag to ?
> > * reviewer does the review
> > * reviewer sets the fedora-review flag to +
> > * packager goes to pkgdb2 to request new package and specifies:
> > - package name
> > - package summary
>
> How about taking this from specfile? (and therefore provide a tool for
> maintaining specfiles & srpms for reviews)
That would imply parsing the bugzilla ticket to find the spec file and then
parse it again which itself implies knowing the bugzilla ticket number.
I think it's just as easy to ask the user to do it.
Note that we have an API endpoint to edit a package's information:
https://admin.fedoraproject.org/pkgdb/api/#edit_a_package
and a script to do it in pkgdb2:
https://git.fedorahosted.org/cgit/pkgdb2.git/tree/utility/update_package_...
In case you did not notice, know that the cron has been deployed and is now
running for two weeks on a weekly basis.
So pkgdb's information about packages is now up to date with the information
contained in yum's meta-data fom the rawhide repo (yes that does mean that
packages retired from repo or present only in epel aren't up to date atm).
By curiousity:
The first time we ran the script:
16638 packages checked
15723 packages updated
Last week's run:
16690 packages checked
50 packages updated
Piere