On 2024/07/15 13:52, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Jul 15, 2024 at 01:26:09PM +0200, Petr Pisar wrote:
V Mon, Jul 15, 2024 at 08:45:53AM +0000, Zbigniew Jędrzejewski-Szmek napsal(a):
Maybe I conflate installability tests with rpmdeplint tests. We need both:
A test which checks that each package is separately installable. And a test
which tcgecks that wanted combinations of packages can be installed together.
I cannot see how "exclude the packages from this set which are known
to be not co-installable" can be achieved automatically. Either the test will
examine package metadata for Conflicts to exclude the conflicting packages, or
someone will have to maintain the good set of combinanations.
Yes, I think those sets would need to be declared. The natural place
for this declaration would be in dist-git of the package.
For the others on the list (and Petr?), we have chatted a bit in the
Fedora-ci matrix room. Basically `installability` already partitions and
tries to run install/remove/upgrade etc. on individual packages +
projects. The main issue Zbyszek found is that the `installability` test
was run on `systemd` which is a fundamental project that is already
installed on the runner. I have opened an issue [1] to see how this can
be handled.
The other issue is with sti/tmt tests where testing-farm tries to
install all packages defined in a project even if there are conflicts
between each other. This is difficult because it requires quite a bit of
refactoring. I think the relevant discussion to track is [2]. This would
not require any special config file, just defining separate tmt plans
(granted it is yet another yaml configuration).
[1]: https://github.com/fedora-ci/mini-tps/issues/64
[2]: https://github.com/teemtee/tmt/discussions/2226
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
