It appears it was tagged for -release more than a week ago:
$ cbs list-history --build rh-postgresql12-postgresql-12.7-1.el7 Thu Jun 17 15:40:44 2021 rh-postgresql12-postgresql-12.7-1.el7 tagged into sclo7-rh-postgresql12-rh-candidate by jstanek [still active] Fri Jun 18 14:25:49 2021 rh-postgresql12-postgresql-12.7-1.el7 tagged into sclo7-rh-postgresql12-rh-testing by jstanek [still active] Wed Jun 30 10:54:51 2021 rh-postgresql12-postgresql-12.7-1.el7 tagged into sclo7-rh-postgresql12-rh-release by jstanek [still active]
I also saw that https://ci.centos.org/view/SCLo-pkgs-cbs/job/SCLo-pkg-rh-postgresql12-rh-C7-release-x86_64/94 was green.
However, I don't see it installable for me using the release repo. On #centos-devel it was advised to open an issue.
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, high-gain, medium-trouble
Had a quick look (normally away/PTO mode) but the SCLo case is a little bit different from other SIGs, as all tags are combined into one for sign/push/release
The distRepo task in copy was complaining about unsigned pkgs from other SCL collections (see https://cbs.centos.org/kojifiles/work/tasks/2038/2502038/missing_signatures.log)
So I processed the sclo7-rh-ruby27-release and sclo7-rh-postgresql13-rh-release (where there were unsigned pkgs) and once they were signed, the whole sclo7-rh-all-release tag was able to be composed and so should be pushed out (including the pkgs from the rh-postgresql12 collection)
sclo7-rh-ruby27-release
sclo7-rh-postgresql13-rh-release
Thanks for the report as it helped finding another small issue in our monitoring solution, as signing (unprivileged user) couldn't read the needed cert for zabbix encryption (pushing) to central server, so it seems that it tried to inform monitoring that there was an issue but was silently discarded as we enforced TLS everywhere for that too (now fixed to allow signing service to use it)
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks! I can confirm I now see the new releases on the mirrors.
Log in to comment on this ticket.