Actions
action #14968
closedrepo-checker can miss cycles
Start date:
2016-11-23
Due date:
% Done:
0%
Estimated time:
Description
We had the case today where two packages, coming from the same devel repo (libpsl and publicsuffix) caused a cycle (also seen in the devel prj)
repo-checker 'approved' both independent, before they were added to a staging project
Once added to the staging, the group was not being re-checked and the cycle would have gone in unnoticed (I had a gut feeling on it and manually retested the group - the cycle was observed)
We need to come up with a different logic here, like maybe only doing repo-checker cycle tests once a package was added to any staging (be it adi or normal). Potentially a recheck would be needed when packages move between stagings?
The floor is open for discussion
Actions