You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at rubygem-actioncable and possibly several other packages from the same update, it seems they don't have proper status for F33. Could it be caused by merging side tag, where there were some issues?
The text was updated successfully, but these errors were encountered:
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 rubygem-actioncable in f33-build Koji tag is rubygem-actioncable-6.0.3.1-1.fc33.src
the SRPM does not have BuildRequires on rubygem(actionpack) = 5.2.3, it requires rubygem(actionpack) = 6.0.3.1
the latest version-release known by Koschei is 5.2.3-4.fc33:
koschei=> select p.id, version, release from build b join package p on b.id=p.last_complete_build_id join collection c on c.id=p.collection_id where p.name='rubygem-actioncable' and c.name='f33';
id | version | release
--------+---------+---------
324641 | 5.2.3 | 4.fc33
(1 row)
Koschei knows about the 6.0.3.1-1.fc33 build, but it does not consider it latest:
koschei=> select id, version, release, real, started, last_complete from build where package_id=324641 ;
id | version | release | real | started | last_complete
---------+---------+---------+------+----------------------------+---------------
8838928 | 5.2.3 | 4.fc33 | f | 2020-08-16 22:06:38.991268 | t
8808192 | 5.2.3 | 4.fc33 | f | 2020-08-09 12:58:14.845246 | f
8846684 | 6.0.3.1 | 1.fc33 | t | 2020-08-07 08:42:13.565842 | f
8790281 | 5.2.3 | 4.fc33 | f | 2020-08-02 17:40:47.1889 | f
8763260 | 5.2.3 | 3.fc32 | f | 2020-07-31 19:29:23.618542 | f
8773970 | 5.2.3 | 4.fc33 | t | 2020-07-29 06:04:31.691981 | f
8748062 | 5.2.3 | 3.fc32 | f | 2020-07-23 21:34:25.642138 | f
(7 rows)
the latest complete build is scratch build.
I suspect that Koschei is using last complete build, possibly scratch build, to determine latest SRPM version, while it should consider only non-scratch builds.
I will continue the investigation later.
Looking at rubygem-actioncable and possibly several other packages from the same update, it seems they don't have proper status for F33. Could it be caused by merging side tag, where there were some issues?
The text was updated successfully, but these errors were encountered: