Re: status of DDTP and ftp mirror synchronization?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09-12-2007 21:56, Kenshi Muto wrote:
> Hi Grisu,
>
> At Sun, 9 Dec 2007 23:10:53 +0100,
> Michael Bramer wrote:
>> The FTP-Master can get the files from:
>> http://ddtp.debian.net/debian/Translations.tar.gz (all)
>> http://ddtp.debian.net/debian/dists/sid/main/i18n/ (per File)
>> http://ddtp.debian.net/debian/dists/etch/main/i18n/ (per File)
>> http://ddtp.debian.net/debian/dists/lenny/main/i18n/ (per File)
>
>>> So, what problem does block the synchronization?
>>> How can we solve it and push the newest DDTP production into official
>>> mirror?
>> The ftp-master should get the files once per week or we need a
>> interface to upload the files on request...
>
> OK, so how did you update the files until 16-May-2006?
> Can't we recover its procedure?
>
> IMHO because 'ddtp.debian.net' (and i18n.debian.net) isn't official
> Debian host yet, it's better to copy Translation data to official
> semi-permanent Debian host and let ftp-master takes it from there.
> Gluck is maybe the best place for such a purpose.
> (hm, /org/ddtp.debian.org/rsync has a similar data, but it's older
> than mirror's one ...)
>
> Plus, Debian prefers rsync rather than http for a synchronization.
> I think ftp-master will want a sync script is tested well and
> guaranteed not making any destruction of other files, if they haven't
> it yet.
If I'm not wrong, Anthony did the first upload of the
Translation files, I'm cc:ing him, he probably can add more
info on that.
I think we could use the BYHAND to upload Translation
files having some kind of DDTP Team, similar to debtags, but
I would still like to hear from Anthony if a package upload
would be better/worst than a rsync from someplace.
Kind regards,
- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHXKblCjAO0JDlykYRAvIvAKCETVnjjHtvGBd4dp1alVBwVMGelQCfQeAn
0LnUU19WvVSWYnV925EO7Fo=
=9VfC
-----END PGP SIGNATURE-----
Reply to: