#116: Clarify https://fedoraproject.org/wiki/QA:Testcase_Mediakit_FileConflicts to say that explicit Conflicts: are acceptable -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: rhe Type: defect | Status: reopened Priority: major | Milestone: Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by jlaska): Replying to [comment:13 adamwill]: > kparal: "How do we check "available for selection"? We can't crawl through all the package lists to see whether a package is available for selection or not." > > For the groups that you can pick during install (where you pick 'desktop' or 'minimal' or whatever), simple - just do an install and try picking each. > > For manual package selection, I'm told only packages listed in comps and marked as 'visible' are available there. It should be trivial to generate that list and compare it against the list of packages we find are conflicting. This seems like non-trivial work for what should be a trivial test. As Toshio points out, leeway for fixing explicit conflicts exists. In this case, leeway was granted since systemd and upstart aren't expected to exist on the media come F-14-Final. As I understand it, they are both present now as a temporary measure to ensure there is a fallback while systemd is tested. I recommend we don't change the test, but we continue to report this failure with the goal of correcting the problem at some point during the F-14 release. I'd rather not go through large hoops to adjust the conflicts test for something that has been granted temporary leeway. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/116#comment:14> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
