Hi, we've been using a special component for RHEL localization on Weblate for blivet project[1]. The component should be named blivet-rhel8[2] but Weblate now claims the component doesn't exist. I tried to re-create it but Weblate says project with this name already exists so I assume I just don't have access rights for it. Can you please make the component public (if this really is the problem). I can create a new component, everything is on our upstream github[3] so it's not a big deal, but I thought it might be easier to ask for help here first. Thanks in advance.
[1] https://translate.fedoraproject.org/projects/blivet/ [2] https://translate.fedoraproject.org/projects/blivet/blivet-rhel8/ [3] https://github.com/storaged-project/blivet-weblate
I can see the component in weblate and can't see any error, where do you see an error? what are you trying to do and can't?
When I try to access the component I get following error (I'm logged in with my Fedora account.):
The page you are looking for was not found. The project you are looking for does not exist or is not publicly available.
<img alt="Screenshot_2021-03-27_blivet.png" src="/fedora-l10n/tickets/issue/raw/files/20cdf1a4bfc29d3691e480d569a10696c1ed71adb12b014955bb3813daa8284b-Screenshot_2021-03-27_blivet.png" />
<img alt="Screenshot_2021-03-27_blivet_blivet-rhel8.png" src="/fedora-l10n/tickets/issue/raw/files/1cf55b6598fe2ed5605855fe139c114a47032a9a6d1bf51683b81bfb4cc7fa43-Screenshot_2021-03-27_blivet_blivet-rhel8.png" />
I can't see any issue, please share more links/screenshot/debug info
<img alt="Screenshot_20210406_151602.png" src="/fedora-l10n/tickets/issue/raw/files/618b5a804e88773c914d61ba4b89c545a9833b9eb7bfe1261c7bd05de8640389-Screenshot_20210406_151602.png" />
Not sure what can I add more for debugging. I'm logged in and I can't access https://translate.fedoraproject.org/projects/blivet/blivet-rhel8/
If you can remove the blivet-rhel8 component, it might be the easiest way to fix this issue. All strings are on GitHub so I can simply re-create the component.
ok, then it was probably because the component was restricted, it should have been fixed now, please try
I can now access the component, thank you.
Metadata Update from @vtrefny: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.