Difference between revisions of "Koji Testbed"
From PDP/Grid Wiki
Jump to navigationJump to search (fix the ascii art) |
|||
| Line 117: | Line 117: | ||
+-f16-release (24) | +-f16-release (24) | ||
+-f16-testing (23) | +-f16-testing (23) | ||
| − | + | +-f16-build (45) | |
And this one: | And this one: | ||
| Line 123: | Line 123: | ||
$ koji list-tag-inheritance f19-build | $ koji list-tag-inheritance f19-build | ||
f19-build (36) <- the "build target" "build tag" | f19-build (36) <- the "build target" "build tag" | ||
| − | + | +-f19 (34) <- package names only (first sense) | |
| − | + | | +-f18 (27) <- all the way | |
| − | + | | +-f17 (9) <- down to | |
| − | + | | +-f16 (7) <- here | |
| − | + | +-f19-basedeps (35) <- these contain the 'groups' | |
| − | + | +-f18-basedeps (28) <- actually inherited from | |
| − | + | +-f17-basedeps (10) <- here | |
A build for F19 ends up in the tag f19-candidates. From there, it needs to be manually moved. If it is a build dependency for other packages, it has to go to f19-build. Otherwise, it eventually goes to f19-testing and from there to f19-release, or directly to f19-release. A rotten product should have its candidacy stripped and ends up with no tags. In any case, no package should remain a candidate for too long. | A build for F19 ends up in the tag f19-candidates. From there, it needs to be manually moved. If it is a build dependency for other packages, it has to go to f19-build. Otherwise, it eventually goes to f19-testing and from there to f19-release, or directly to f19-release. A rotten product should have its candidacy stripped and ends up with no tags. In any case, no package should remain a candidate for too long. | ||
