Using "testing" repository for build

[remicollet]

For now, each build use the default buildroot for the target branch.

This is perfect for rawhide.

For stable branch, this means that only package in "stable" repository are used. So, if any update break something it will be discovered too late.

Proposal: use packages from testing repository to detect possible breakage as soon as possible, during the testing phase and before the package is in stable.

Workaround: a buildroot override allow Koschei to use the new package, but may have some bad side effects (if some dependent package are build using this package, and push to stable before it)

Issue open for discussion.

[voxik]

I am afraid that the buildroot overrides are the issue, since they might be expired any time. And they may cause build failures any time ...

Otherwise I would appreciate such feature as well ....

[remicollet]

Initial request was about using dependencies from testing repository

But koschei also check packages from "stable" repository, when latest version (in "testing") should be tested.

Example, after a long FTBFS Marathon (mostly for PHP 7.2):

• Today, Rawhide is "all green" https://apps.fedoraproject.org/koschei/groups/php?order_by=state%2C-started&collection=f28
• But F27 have lof of failure, https://apps.fedoraproject.org/koschei/groups/php?order_by=state%2C-started&collection=f27

Ex: https://apps.fedoraproject.org/koschei/package/php-phpunit-php-code-coverage5?collection=f27 Koschei test 5.2.2 from "stable", when FTBFS is fixed in 5.2.3

This make Koschei report (in F27) very hard to read.

[mizdebsk]

@remicollet This is a different thing, it's already tracked as issue #140

[mizdebsk]

Longer explanation:

1. Initial request - building package (from stable or testing) against build dependencies from testing is currently not possible in Koji - there are no build tagrets or repos for fNN-testing. Theoretically they could be created, but I assume that Fedora release engineers wouldn't be happy to do that. So that is very hard (read: practically impossible) to be implemented at this time.

2. Building SRPM from testing in stable+override buildroot would be quite easy to implement, but it could have other bad consequences. Example is available in #140.

[remicollet]

Theoretically they could be created, but I assume that Fedora release engineers wouldn't be happy to do that.

Perhaps you should try to ask them ?

[remicollet]

Here is an example of what should have been catch https://apps.fedoraproject.org/koschei/package/php-phpspec-prophecy?collection=f26

Because of "typo" not catch during "testing" phase, broken php-phpspec was badly push to stable... :(