#87: new post-bodhi-update hook
----------------------+-----------------------------------------------------
Reporter: wwoods | Owner: wwoods
Type: task | Status: assigned
Priority: major | Milestone: autoqa depcheck
Component: harness | Version: 1.0
Resolution: | Keywords:
----------------------+-----------------------------------------------------
Comment (by wwoods):
So it turns out there's currently no way to distinguish between 'New' and
'Requested' and there's no difference between 'Requested' and
'Pending'
''except'' for critpath updates.
According to lmacken on IRC:
{{{
The only statuses in bodhi are: pending, testing, stable, obsolete.
The only requests are: testing, stable, obsolete.
}}}
Normal updates start with {status: pending, request: (testing or stable)}.
request defaults to 'testing'.
Critpath updates start with {status: pending, request: None}, and once
they have gotten enough karma, the submitter is then allowed to actually
make the request.
Once pushed, they have (status: (testing or stable)).
This means that we currently have no way of knowing what request (i.e.
which repo) a pending update is targeting.
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/87#comment:8>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project