-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
„Weblate“, a lot of errors, missing files, old files conflicting, as they no longer exist. (Migration problem to 24.X) #7528
Comments
This is the result of removing the English translations, since they're identical to the GUI. |
Do we need a maintainer with Weblate access to configure it properly then? I assume it's a consequence of 0ca52eb? |
It is due to that commit, but it just highlighted the underlying problem that a dozen apps in Weblate have been configured to have en .po file as template, instead of proper templates .pot It requires manual config for those faulty apps in Weblate config. |
But so far 24.10 is already equal to master, so there is no backport need. |
I fixed the wrong template path |
Please note that some of the warnings are shown for historical reasons, e.g. in your screenshot "appeared month ago, last seen a month ago". But I still re-opened the issue as you wish. |
From my understanding, this is a bug in „Weblate“, it thinks that there is a file, that no longer exists, as such, shows an error. |
It thought so, a month ago. But not any more. Like it says in the screenshots. I do not find any actual errors in the system admin console. And naturally we have no real insight into Weblate internals. We are just a downstream user of the service. |
Try doing what the error message says on top of that: „Please fix this by removing duplicated strings with same identifier from the translation files.“ Try checking the ID for the place of this string (IPv4) and removing it, then re-adding it. My guess, why it doesn't show an error in administration, is most likely because, it doesn't exist and „Weblate“ developers did not account for this type of bug to happen. |
Actually, like I predicted, the announcements about old errors got timed out and went away. Now there is just a "normal" conflict. |
Actually, I opened a ticket with weblate 😉 They opened this: |
Ideally, issues should only be closed when fixed, since the entire component is locked from any edits. Hopefully this will be fixed in a timely manner. |
Feel free to author a fix PR for the firmware wizard git repo, and then hope that somebody with merge rights there merges it in. You have just as much power in that repo as I do. |
Is there an existing issue for this?
screenshots or captures
Actual behaviour
Errors are shown, appeared a month ago.
Expected behaviour
None of these should appear.
Steps to reproduce
Additional Information
What browsers do you see the problem on?
Firefox
Relevant log output
No response
The text was updated successfully, but these errors were encountered: