Mikolaj Izdebski

This happened again a few days ago.

This happened again in production

Latest Koschei has been deployed in production in Fedora infrastructure. This upstream fix should be live in Fedora now.

I've established as follows: - In Koschei collection `f33` package `rubygem-actioncable` is marked as "unresolved" with dependency problem: `No package found for: rubygem(actionpack) = 5.2.3` - the lastest SRPM of...

Thanks for the report. Koschei polling service has been crashing recently: ``` # oc -n koschei get pod polling-1-5tkwh NAME READY STATUS RESTARTS AGE polling-1-5tkwh 0/1 CrashLoopBackOff 3194 (2m5s ago)...

First of all, Koschei strives to be agnostic of particular distribution it is used for. It does not have have knowledge of Fedora release schedule. Koschei admins configure it to...

Confirmed, there is inconsistency in database. Package state should always be equal to state of the latest build. For performance package state is stored in database as denormalized field, which...

In short: No, I don't think this is doable right now, but maybe @msimacek will have some ideas. There is no way to reliably detect from which git commit particular...

This behaviour is expected. From [Koschei documentation on Fedora Wiki](https://fedoraproject.org/wiki/Koschei): "Packages are rebuilt in Koji from the latest available SRPM". The latest python2 package in f30-build is python2-2.7.15-10.fc30 (you can...

What do you propose as a solution? Submit scratch-builds from latest SCM commit?