#175 Translations update from Weblate
Closed by rcritten. Opened by weblatebot.
weblatebot/certmonger weblate-certmonger-master  into  master

Translations update from Weblate for certmonger/master.

Current translation status:

Weblate translation status

hum, interesting, first time I see this way of listing language (a script).

Weblate can handle language addition, so keeping it simple may be a good option you may wish to apply (build scripts are complex enough).

if you don't wish to have this, fine, I can deactivate the plugins which provides LINGUAS support

rebased onto 9800c9f3cc557d065cccc216d6a12f1719dedd8f

rebased onto 313b91f0ef5c5126b8240d61898c3560eaadcd7b

rebased onto 977797eadc5b2d3afa1384bcbd3309e855d14add

rebased onto 6b1cc1c981d5ed5b756a8902880fa19a7f113ef4

I'm fine with hardcoding the set of LINGUAS. It isn't something that will change too often.

Given that, safe to merge?

yes, it's safe to merge.

Weblate will open a new PR if a contributor translates something.
Until it is merged, Weblate will reuse the current PR.

oh, I just checked, you have too many PR from Weblate, while this isn't a major issue, please wait a moment I'll report the bug to Weblate devs.

the bugs you have with duplicated PR is fixed: https://github.com/WeblateOrg/weblate/commit/8358d20cea64c5e3caca743af7c5fe015f49dd6b

I'm waiting for weblate's support for advice on how to solve the situation (which PR to merge/close and if we can do it right now).

Ok cool, thanks.

Just following up. Do we have an answer on which one(s) to merge?

Michal said: "You can close all the duplicated PRs, Weblate really doesn't care about them."

I understand this means you merge the first one and close all others, but you have more dev experience than me.

(thanks a lot for your patience, your kind reminders are really welcome)

I don't know why Pagure thinks this needs a rebase but I pushed it manually ok.

Marking as done.

Pull-Request has been closed by rcritten