sysadmin-bin issueshttps://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/issues2023-12-07T02:34:27Zhttps://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/issues/24Add a token in post-receive-notify-l10n to authenticate incoming requests2023-12-07T02:34:27ZGuillaume Bernardassociations@guillaume-bernard.frAdd a token in post-receive-notify-l10n to authenticate incoming requestsHi!
In the [`post-receive-notify-l10n`](https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/blob/master/git/post-receive-notify-l10n?ref_type=heads), I would like you to add an authentication token in the header of the API call. Some...Hi!
In the [`post-receive-notify-l10n`](https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/blob/master/git/post-receive-notify-l10n?ref_type=heads), I would like you to add an authentication token in the header of the API call. Something like a `Bearer` token.
I would like to add authentication in the ping mechanism in order to accept incoming requests from GitHub-hosted projects.
The idea is to store a tuple of `(hostname, token)` in Damned Lies to authenticate the incoming requests before triggering a refresh in Damned Lies backend.
We will have:
- a token for gitlab.gnome.org, share between all the projects because called using the `post-receive-notify-l10n` script.
- a token for each project hosted somewhere else on GitHub, Freedesktop, etc.https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/issues/23Add license file/headers2023-11-10T13:39:28ZDenis RoyAdd license file/headersWould it be possible to add a license header to the script? We'd like to use it, and perhaps collaborate with you on it.Would it be possible to add a license header to the script? We'd like to use it, and perhaps collaborate with you on it.https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/issues/17Make pre-receive-check-po validate syntax in translations via pyg3t's gtxml2020-09-19T09:31:08ZAndre KlapperMake pre-receive-check-po validate syntax in translations via pyg3t's gtxmlI've spent time manually fixing broken syntax in translations in .po files.
Picking one random example from the last weeks: https://gitlab.gnome.org/GNOME/hitori/-/commit/3a9c545a348ddb8aadd32175baaaf15e6273cb47
I'd love to see https:...I've spent time manually fixing broken syntax in translations in .po files.
Picking one random example from the last weeks: https://gitlab.gnome.org/GNOME/hitori/-/commit/3a9c545a348ddb8aadd32175baaaf15e6273cb47
I'd love to see https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/blob/master/git/pre-receive-check-po either refuse `.po` files which do not pass `pyg3t`'s `gtxml` (under the assumption that `gtxml` works reliable and does not trigger false positives preventing folks from getting their translations pushed), or at least notify committers of a likely problem with their po file.
Similar ticket though for end-user software: https://gitlab.gnome.org/GNOME/gtranslator/-/issues/101https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/issues/16Make pre-receive-check-po refuse non-ascii quotation marks in link syntax2020-09-19T09:31:03ZAndre KlapperMake pre-receive-check-po refuse non-ascii quotation marks in link syntaxhttps://gitlab.gnome.org/GNOME/gnome-devel-docs/-/issues/20 broke the build by accidentally using `“` and `“` (U+201C and U+201D) instead of `\"` (U+0022) for link syntax in a po file.
I wonder if https://gitlab.gnome.org/Infrastructure...https://gitlab.gnome.org/GNOME/gnome-devel-docs/-/issues/20 broke the build by accidentally using `“` and `“` (U+201C and U+201D) instead of `\"` (U+0022) for link syntax in a po file.
I wonder if https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/blob/master/git/pre-receive-check-po could catch that in some feasible and maintainable way.
If not, then please feel free to decline this ticket.https://gitlab.gnome.org/Infrastructure/sysadmin-bin/-/issues/13Handle other files than NEWS/ChangeLog for tarball updates2019-09-06T08:44:33ZCarlos GarnachoHandle other files than NEWS/ChangeLog for tarball updatesWe got https://gitlab.gnome.org/GNOME/tracker-miners/merge_requests/100 asking us to move to more recent formats and conventions to keep release logs. That of course will potentially tickle `ftpadmin` as NEWS/ChangeLog are diff'ed in ord...We got https://gitlab.gnome.org/GNOME/tracker-miners/merge_requests/100 asking us to move to more recent formats and conventions to keep release logs. That of course will potentially tickle `ftpadmin` as NEWS/ChangeLog are diff'ed in order to produce email notifications.
IMHO newer conventions are a fair thing to handle additionally, as NEWS/ChangeLog are relics from our CVS past.