Learn more about these different git repos.
Other Git URLs
We got a report that the centos-6 repo is not shown for some projects, while we should still support that chroot.
The problem is that we already sent the notification emails, and set the delete_notify field -> based on that field we consider that the file is mean to be removed soon, and not a candidate for enabling (and hence we don't render the repofile).
delete_notify
I believe this was fixed by https://pagure.io/copr/copr/blob/9eef4e30570fb8b297589dbdc0e80bfce658f6aa/f/frontend/coprs_frontend/commands/alter_chroot.py#_47-48
.. though I don't think we used that script for re-activating centos-6 chroots :-( because the code was not yet released, and people didn't want to wait that long.
That's why I'd like to execute the following custom SQL query:
coprdb=# select * from mock_chroot where os_release = 'epel' and os_version='6'; ┌────┬────────────┬────────────┬─────────┬───────────┬─────────────────────┬──────────────────────┬─────────┐ │ id │ os_release │ os_version │ arch │ is_active │ distgit_branch_name │ final_prunerepo_done │ comment │ ├────┼────────────┼────────────┼─────────┼───────────┼─────────────────────┼──────────────────────┼─────────┤ │ 70 │ epel │ 6 │ aarch64 │ f │ el6 │ t │ │ │ 5 │ epel │ 6 │ i386 │ t │ el6 │ f │ │ │ 6 │ epel │ 6 │ x86_64 │ t │ el6 │ f │ │ └────┴────────────┴────────────┴─────────┴───────────┴─────────────────────┴──────────────────────┴─────────┘ (3 rows) update copr_chroot set delete_notify=null where mock_chroot_id in (70, 5, 6);
@frostyx what do you think?
while we should still support that chroot.
And do we want to remove the data? If not, we should null also the delete_after field.
delete_after
That's something we already did before, I think. But good point.
edit: This gives empty output: Yes, select * from copr_chroot where mock_chroot_id in (70, 5, 6) and delete_after is not null;
@frostyx do I have ack to execute the query?
Yep, LGTM
Thanks: coprdb=# update copr_chroot set delete_notify=null where mock_chroot_id in (70, 5, 6); UPDATE 4415
Metadata Update from @praiskup: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.