Switching the stable branch for docs.krita.org
Luigi Toscano
luigi.toscano at tiscali.it
Tue Aug 9 10:04:28 BST 2022
Halla Rempt ha scritto:
> I should have sent this mail last week... But we're on the verge of releasing krita 5.1, so we've switched the stable branch for docs.krita.org to krita/5.1, and now it looks like we're getting the wrong translations. I'm not sure what to do next :-(
Please make sure you create the branch when changing the settings in
sysadmin/repo-metadata.
Last month the branch was switched in sysadmin/repo-metadata:
https://commits.kde.org/sysadmin/repo-metadata/297c2cf080d1ae8f07bd0cc0faea0836b9bad14c
I didn't notice that immediately, my bad, but I've then tried to mirror that
change in scripty:
https://commits.kde.org/sysadmin/l10n-scripty/e4696df259201b5afb1c13798ca5d15f93fe3b98
and that didn't work, because the branch didn't exist yet:
fatal: ambiguous argument 'origin/krita/5.1': unknown revision or path not in
the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
ERROR: failed to switch to branch krita/5.1 for module websites-docs-krita-org.
https://logs.l10n.kde.org/220704.trunk_l10n-kf5
So I've reverted that change and kept tracking krita/5.0.
Then (sorry for that, my mistake) I forgot to write about this and ended up
ignoring the warning, until now.
I've now switched again to krita/5.1.
https://commits.kde.org/sysadmin/l10n-scripty/b8fb86f7516cc1abbaab57126c3726c0e0108a7b
--
Luigi
More information about the kde-i18n-doc
mailing list