RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

*** This bug has been marked as a duplicate of bug 2018384 ***

Seems like typo indeed, I've sent https://github.com/cockpit-project/cockpit/pull/16727
When it lands, I'll sync into weblate and let you know when it is ready to be translated.

Thanks Ludek! Would you be okay with closing this as a duplicate of bug #2016998? IMHO it does not make much sense to have *two* tracking bugs for "update translations in RHEL 8.6".

If a separate bug is more useful for you, I'll unduplicate.

But either way, this will be picked up by our next automatic translation refresh. Thanks!

*** This bug has been marked as a duplicate of bug 2016998 ***

Thanks for closing this duplicate.