Quoting Laura Arjona Reina (larj...@debian.org): > Hello all > I applied a patch to the dl10n repo in salsa, with a workaround for this > bug (adding the problematic packages to an exclusion list). > However, the material is not being updated, I think because the repo in > tye still uses alioth as origin. > > Can somebody in the debian-i18n group update the config in > /srv/i18n.debian.org/dl10n/git/ so it uses the salsa repo? > > (I'm not sure if manual git pull is needed too, or if there is some cron > script that auto-updates the repo at some time. I'm not in the > debian-i18n group so I think I cannot check...
Hi Laura, Thanks for your work. I logged in to i18n.d.o, then sudo'ed to debian-i18n, then moved to /srv/i18n.debian.org/dl10n/git "git pull" mentions that the local copy is up-to-date and "git log" says : commit d17144ddc047f48bc4609202bb6e48d04fe92f33 Author: David Prévot <da...@tilapin.org> Date: Wed Jan 7 12:12:43 2015 -0400 Workaround recent SSL breakage from DSA <1420638006.22794.18.ca...@debian.org>. So, it looks like I can't have your patch make its way to the server....:-( From what I remember, there is no auto update of the local git repository copy, it has to be pulled manually. debian-i18n@tye:/srv/i18n.debian.org/dl10n/git$ git remote -v origin git://anonscm.debian.org/debian-l10n/dl10n.git (fetch) origin git://anonscm.debian.org/debian-l10n/dl10n.git (push) I think that, indeed, it would be good if someone more active than me would apply to be included in the debian-i18n group
Description: PGP signature