Bug#431891: status of DDTP and ftp mirror synchronization?

2008-06-01 Thread Kenshi Muto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

At Wed, 26 Mar 2008 12:37:16 -0300,
Felipe Augusto van de Wiel (faw) wrote:
  Any updates to the this DDTP-update issue?
  Is the byhand script still waiting for reviews?
 
   Not exactly, I would like to have some input from
 Anthony about where we should go next, specially after his
 first review, last time I pinged him he was somewaht busy.
 
   I know he has working in dak recently, but not sure
 what is missing for the next step, probably update the
 byhand to follow his recommendations, but it is still
 unclear to me some of the points, that's why I asked for
 his help. :)

I'm sorry to nag again, but are there any updates?
I'm afraid ajt's resignation from ftpteam has stopped this
progress also.

Thanks,
- -- 
Kenshi Muto
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ http://mailcrypt.sourceforge.net/

iEYEARECAAYFAkhCqUsACgkQQKW+7XLQPLEljACfZ20j9fgnydlY1CS69PKYDIlI
2bgAn3mmWPSwna8nQl749oiAG+vp0uBa
=Pnkn
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2008-03-26 Thread Kobayashi Noritada
Hi,

Any updates to the this DDTP-update issue?
Is the byhand script still waiting for reviews?

From: Felipe Augusto van de Wiel (faw)
Subject: Re: status of DDTP and ftp mirror synchronization?
Date: Fri, 11 Jan 2008 16:47:41 -0200

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 18-12-2007 10:42, Anthony Towns wrote:
  On Sat, Dec 15, 2007 at 10:23:50AM -0200, Felipe Augusto van de Wiel wrote:
 I finished working on the scripts that will generate the
  files, we add some tests during the package build to reduce the
  checks on the archive side. The package, .dsc and byhand-ddtp
  are here: http://people.debian.org/~faw/ddtp/
  
  That should be a .changes file, not a .dsc file. You could use the
  tag-overrides changes on merkel as an example; look in:
  
   /srv/ftp.debian.org/queue/done/tag-overrides_200712071325_all.changes
 
   Ooops, sorry.
 
   With the holidays and being busy with the end of the year
 it took me some time to reply, sorry for the delay. I updated the
 package, the script that generates it and I also generate a .changes
 file now. Hope it is OK. :)
 
 http://people.debian.org/~faw/ddtp/ddtp-translations_20080111-1_all.changes
 
 
  The byhand script only allows translations for main, not contrib/non-free.
  That seems odd?
 
   Yes, I discussed that with Michael Bramer and others during
 the meeting in Extremadura, and the contrib should be added, but we
 are unsure about non-free descriptions, it could be under a license
 that allows distributions but doesn't allow translations.
 
   I didn't add the checks for contrib because I was expecting
 a first review to see if I was in the right direction. I will add
 them on the new version.
 
 
  If the filename looks like Translations-xx_YY-blah it will pass through
  without complaint. FNL=$(echo ${FN} | cut -d'-' f2-) would fix that.
  Using ${FN%%-*} and ${FN#*-} rather than the echo/cut subshells would
  work too.
 
   True. I'm used to implement such things using echo/cut
 to make it easier to read, but I can change that if it is more
 recommended or preferred.
 
 
  Only extracting files that you've guaranteed are okay might be safer, ie:
  (untested)
 [...]
  tar tzf ${TBALL} | while read f; do
if is_name_okay $f;
  tar -C ${TEMPDIR} -xzf ${TBALL} $f
fi
  done
 
   The above is missing a then and a quote:
 
 tar tzf ${TBALL} | while read f; do
   if is_name_okay $f; then
   tar -C ${TEMPDIR} -xzf ${TBALL} $f
   fi
 done
 
   What I couldn't understood was the logic behind to
 sequential extracts. I was thinking about returning is_name_okay
 to a variable and test it to see the action, if everything OK we
 could already extract the file.
 
   I'm also unsure about at which point we should remove
 the old translation files. If I change the old byhand-ddtp with
 the new function it fails for Translation-ca but still extracts
 the files. I put the script here:
 
  http://people.debian.org/~faw/ddtp/byhand-ddtp-aj
 
 
   Since I would prefer to understand first why Translation-ca
 is failing (and something obvious is escaping me) and check why we
 should 'tar tzvf' 2 times, I would wait for your comments before
 trying to change it.
 
   I also remove the trap and the old checks since this new
 function seems to do most of what we want and can be improved it
 needed.
 
 
 
  There's no code to move from the TEMPDIR into the dists/ directory? Or
  are you meaning for TEMPDIR to be replaced by the real dest?
 
   That's the other thing that I was unsure about how to
 handle, if we should extract to a TEMPDIR, remove old
 translations and them move from TEMPDIR to DESTDIR. Or if we
 should hit a point were everything is OK then we remove old
 translations and unpack the new ones in the right place.

Thanks,

-nori


pgpZkaEIOW8Qu.pgp
Description: PGP signature


Bug#431891: status of DDTP and ftp mirror synchronization?

2008-03-26 Thread Felipe Augusto van de Wiel (faw)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 26-03-2008 12:26, Kobayashi Noritada wrote:
 Hi,
 
 Any updates to the this DDTP-update issue?
 Is the byhand script still waiting for reviews?

Not exactly, I would like to have some input from
Anthony about where we should go next, specially after his
first review, last time I pinged him he was somewaht busy.

I know he has working in dak recently, but not sure
what is missing for the next step, probably update the
byhand to follow his recommendations, but it is still
unclear to me some of the points, that's why I asked for
his help. :)

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

iD8DBQFH6m2sCjAO0JDlykYRArjeAJ4+TzNoV0D9H6skUBwlR813JezldACgjSun
dJq8d81rxVMNBWq8+wxfdV0=
=vGMf
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2008-01-11 Thread Felipe Augusto van de Wiel (faw)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 18-12-2007 10:42, Anthony Towns wrote:
 On Sat, Dec 15, 2007 at 10:23:50AM -0200, Felipe Augusto van de Wiel wrote:
  I finished working on the scripts that will generate the
 files, we add some tests during the package build to reduce the
 checks on the archive side. The package, .dsc and byhand-ddtp
 are here: http://people.debian.org/~faw/ddtp/
 
 That should be a .changes file, not a .dsc file. You could use the
 tag-overrides changes on merkel as an example; look in:
 
  /srv/ftp.debian.org/queue/done/tag-overrides_200712071325_all.changes

Ooops, sorry.

With the holidays and being busy with the end of the year
it took me some time to reply, sorry for the delay. I updated the
package, the script that generates it and I also generate a .changes
file now. Hope it is OK. :)

http://people.debian.org/~faw/ddtp/ddtp-translations_20080111-1_all.changes


 The byhand script only allows translations for main, not contrib/non-free.
 That seems odd?

Yes, I discussed that with Michael Bramer and others during
the meeting in Extremadura, and the contrib should be added, but we
are unsure about non-free descriptions, it could be under a license
that allows distributions but doesn't allow translations.

I didn't add the checks for contrib because I was expecting
a first review to see if I was in the right direction. I will add
them on the new version.


 If the filename looks like Translations-xx_YY-blah it will pass through
 without complaint. FNL=$(echo ${FN} | cut -d'-' f2-) would fix that.
 Using ${FN%%-*} and ${FN#*-} rather than the echo/cut subshells would
 work too.

True. I'm used to implement such things using echo/cut
to make it easier to read, but I can change that if it is more
recommended or preferred.


 Only extracting files that you've guaranteed are okay might be safer, ie:
 (untested)
[...]
 tar tzf ${TBALL} | while read f; do
   if is_name_okay $f;
 tar -C ${TEMPDIR} -xzf ${TBALL} $f
   fi
 done

The above is missing a then and a quote:

tar tzf ${TBALL} | while read f; do
if is_name_okay $f; then
tar -C ${TEMPDIR} -xzf ${TBALL} $f
fi
done

What I couldn't understood was the logic behind to
sequential extracts. I was thinking about returning is_name_okay
to a variable and test it to see the action, if everything OK we
could already extract the file.

I'm also unsure about at which point we should remove
the old translation files. If I change the old byhand-ddtp with
the new function it fails for Translation-ca but still extracts
the files. I put the script here:

 http://people.debian.org/~faw/ddtp/byhand-ddtp-aj


Since I would prefer to understand first why Translation-ca
is failing (and something obvious is escaping me) and check why we
should 'tar tzvf' 2 times, I would wait for your comments before
trying to change it.

I also remove the trap and the old checks since this new
function seems to do most of what we want and can be improved it
needed.



 There's no code to move from the TEMPDIR into the dists/ directory? Or
 are you meaning for TEMPDIR to be replaced by the real dest?

That's the other thing that I was unsure about how to
handle, if we should extract to a TEMPDIR, remove old
translations and them move from TEMPDIR to DESTDIR. Or if we
should hit a point were everything is OK then we remove old
translations and unpack the new ones in the right place.

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

iD8DBQFHh7nNCjAO0JDlykYRAlkqAJ9HjFs7RA7VyC1HL7ZfmbuZ3kxGCQCgrxBN
xXV7RbpDMRjBtaqiDTFDZ48=
=UMGc
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-18 Thread Anthony Towns
On Sat, Dec 15, 2007 at 10:23:50AM -0200, Felipe Augusto van de Wiel wrote:
   I finished working on the scripts that will generate the
 files, we add some tests during the package build to reduce the
 checks on the archive side. The package, .dsc and byhand-ddtp
 are here: http://people.debian.org/~faw/ddtp/

That should be a .changes file, not a .dsc file. You could use the
tag-overrides changes on merkel as an example; look in:

 /srv/ftp.debian.org/queue/done/tag-overrides_200712071325_all.changes

The byhand script only allows translations for main, not contrib/non-free.
That seems odd?

If the filename looks like Translations-xx_YY-blah it will pass through
without complaint. FNL=$(echo ${FN} | cut -d'-' f2-) would fix that.
Using ${FN%%-*} and ${FN#*-} rather than the echo/cut subshells would
work too.

Only extracting files that you've guaranteed are okay might be safer, ie:
(untested)

is_name_okay () {
  local f
  f=$1
  f=${f#./}# trime leading ./ if present
  c=${f%%/*}   # component should appear first
  if [ x$c != xmain -a x$c != xcontrib -a x$c != xnon-free ]
  then
return 1
  fi
  f=${f#*/}

  if [ x$f = x ]; then return 2; fi # directory name, ignore it

  # i18n/ should appear next
  if [ ${f#i18n/} = $f ]; then
return 1
  fi
  f=${f#*/}

  if [ x$f = x ]; then return 2; fi # directory name, ignore it

  case $f in
Translation-[a-z][a-z][a-z]_[A-Z][A-Z]) return 0 ;;
Translation-[a-z][a-z]_[A-Z][A-Z]) return 0 ;;
Translation-[a-z][a-z][a-z]) return 0 ;;
Translation-[a-z][a-z]) return 0 ;;
  esac

  return 1
}

tar tzf ${TBALL} | while read f; do
  if ! is_name_okay $f  [ $? -ne 2 ]; then
true
  else
echo Bad name in tarball: $f
exit 1
  fi
done

tar tzf ${TBALL} | while read f; do
  if is_name_okay $f;
tar -C ${TEMPDIR} -xzf ${TBALL} $f
  fi
done

There's no code to move from the TEMPDIR into the dists/ directory? Or
are you meaning for TEMPDIR to be replaced by the real dest?

Cheers,
aj



signature.asc
Description: Digital signature


Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-17 Thread Felipe Augusto van de Wiel (faw)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 16-12-2007 04:45, Anthony Towns wrote:
 On Sat, Dec 15, 2007 at 10:23:50AM -0200, Felipe Augusto van de Wiel (faw) 
 wrote:
[...]
  * When we upload a new file removing a translation, how would we
remove that from the archive? byhand-ddtp should take care of that?
 
 Uploading a set of translations for unstable will replace /all/
 the translations for unstable, IMO. So if you have some new Turkish
 translations you have to re-upload all the old Spanish translations
 even if they haven't changed -- if you don't, we'll assume Spanish is
 no longer a useful language and will drop translations for them.
 
 So, yes, byhand-ddtp should take care of that, afaics.

Ah, ok, that's what I was imagining but was unsure about that.
So, once I got your feedback about the package and the script I think
we can move to the next steps and bit adjustments (specially because
the paths on ftp-master are not entirely clear for me). Thanks.


  * We were concern about the version format system, but I think the
package is not going to appear on the archive,
 
 That's largely correct. You can use a different package name / version
 format if you have a better one. You can also upload a source and binary
 package if you think that's useful (it is for debian-maintainers, eg).

Some translators and other projects seems to have interest in
having access to all the translations, but since it is just a repack
of the original tarball to fit the BYHAND upload, IMHO, I don't think
it is necessary to provide a binary, if somebody else would think it
is interesting, then I probably would bother you again to get help on
implement and upload both binary and source ddtp-translations. :-)


  * Can we close bugs using debian/changelog like on a normal package?
Because we could close #431891 when this upload happens. :)
 
 Yes, afaik that works fine.

Nice.


  I also tried to implement the check of allowed uploads, but
 it seems that it needs to be done on archive side, I don't have the
 necessary understanding of projectb to implement that, but we would
 like to restrict who can upload the new translations.
 
 Why would you want to do that? Tag uploads aren't restricted, eg, nor
 are glibc uploads. Why are translations more special than either of those?

Sorry, probably that was just my misunderstanding of how the
autobyhand works, the package would be under the same rules of all
other packages in Debian (keyring check and so on), so if it was
upload by someone else it would be considered an NMU, for some reason
I had the impression that it needs to be checked apart. Sorry, now it
is clear that dak will threat ddtp-translation as a regular package,
it just don't go to the archive as a binary .deb.

Thanks for all the info and help on this.

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

iD8DBQFHZlCICjAO0JDlykYRAkXFAJ9n68b+oyxT72c81uAe4vaqOnFcxwCg0oPl
+PSwB5vpjlN88MycP2xq3nI=
=9jHI
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-16 Thread Anthony Towns
On Sat, Dec 15, 2007 at 10:23:50AM -0200, Felipe Augusto van de Wiel (faw) 
wrote:
 The package, .dsc and byhand-ddtp
 are here: http://people.debian.org/~faw/ddtp/

(I haven't looked at this yet)

   Some doubts appear in the process, while writing the byhand
 I realize that you (or other ftpmaster) probably would need to adjust
 the necessary bits like paths and make sure that 'rm -rf' do not
 erase the entire archive.

Yup.

 We tried to check the consistence of the
 tarball and also the names, we plan to add other checks, and I hope
 it would be not too hard to update it in the future. We decide to
 take care of the enconding on our side, before the upload.

Good.

  * When we upload a new file removing a translation, how would we
remove that from the archive? byhand-ddtp should take care of that?

Uploading a set of translations for unstable will replace /all/
the translations for unstable, IMO. So if you have some new Turkish
translations you have to re-upload all the old Spanish translations
even if they haven't changed -- if you don't, we'll assume Spanish is
no longer a useful language and will drop translations for them.

So, yes, byhand-ddtp should take care of that, afaics.

  * We were concern about the version format system, but I think the
package is not going to appear on the archive,

That's largely correct. You can use a different package name / version
format if you have a better one. You can also upload a source and binary
package if you think that's useful (it is for debian-maintainers, eg).

  * Can we close bugs using debian/changelog like on a normal package?
Because we could close #431891 when this upload happens. :)

Yes, afaik that works fine.

   I also tried to implement the check of allowed uploads, but
 it seems that it needs to be done on archive side, I don't have the
 necessary understanding of projectb to implement that, but we would
 like to restrict who can upload the new translations.

Why would you want to do that? Tag uploads aren't restricted, eg, nor
are glibc uploads. Why are translations more special than either of those?

Cheers,
aj



signature.asc
Description: Digital signature


Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-15 Thread Felipe Augusto van de Wiel (faw)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11-12-2007 07:18, Anthony Towns wrote:
 So I'd say:
 
  - prepare a byhand upload
  - targetted at unstable (ie Distribution: unstable)
  - with a byhand file called ddtp-translations_2007.12.12-1_all.tar.gz
or similar (different package name or version, eg)
  - section should be raw-translations
  - that tarball should contains:
   main/i18n/Translation-xx_XX
   contrib/i18n/Translation-xx_XX
   non-free/i18n/Translation-xx_XX
 ie, translations for all components and languages, uncompressed
 
 Workable?
 If you can upload all that somewhere I can have a look at it and make
 sure it's workable, rather than directly to the archive, that'd seem
 like a good next step.

I finished working on the scripts that will generate the
files, we add some tests during the package build to reduce the
checks on the archive side. The package, .dsc and byhand-ddtp
are here: http://people.debian.org/~faw/ddtp/


 Any suggestions/scripts for validating the uploaded file would be
 good too.

Some doubts appear in the process, while writing the byhand
I realize that you (or other ftpmaster) probably would need to adjust
the necessary bits like paths and make sure that 'rm -rf' do not
erase the entire archive. We tried to check the consistence of the
tarball and also the names, we plan to add other checks, and I hope
it would be not too hard to update it in the future. We decide to
take care of the enconding on our side, before the upload.

So, a few doubts/questions:

 * When we upload a new file removing a translation, how would we
   remove that from the archive? byhand-ddtp should take care of that?

 * We were concern about the version format system, but I think the
   package is not going to appear on the archive, so we decided to
   use MMDD as you suggested, without the dots, and with a Debian
   revision, even knowing it is a Debian native package, it has some
   relation to how we will manage the debian/changelog. If we need to
   do a second upstream release on the same date, we will just push
   a new dedian revision.

 * Can we close bugs using debian/changelog like on a normal package?
   Because we could close #431891 when this upload happens. :)


I also tried to implement the check of allowed uploads, but
it seems that it needs to be done on archive side, I don't have the
necessary understanding of projectb to implement that, but we would
like to restrict who can upload the new translations.

So, this should be the first step, so we can get ready for
the next one.

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

iD8DBQFHY8dVCjAO0JDlykYRArKeAKDAf0fXe8dLofxObvxJBwtZ/m9M3ACgxTkc
mDc+L8cJvsKAxHGxqzI55JE=
=C4Tp
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-11 Thread Felipe Augusto van de Wiel (faw)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11-12-2007 07:18, Anthony Towns wrote:
 On Mon, Dec 10, 2007 at 12:39:34AM -0200, Felipe Augusto van de Wiel (faw) 
 wrote:
  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.
 
 Yup; the autobyhand stuff we have now (used by debtags and
 debian-maintainers) makes that easy to work with too.

Cool. :)


 I'm still not entirely comfortable with having something outside of
 ftpmaster determine which translations should be in which suites,
 but that's something that'll probably need changes in apt-ftparchive
 to improve, and can be left 'til later.

Ok, we would like to help with that, so we can have it in
Lenny. Not sure exactly what is required and all the details, but
would be great if we could cooperate to find the best solution to
fulfill ftpmaster requirements.


 So I'd say:
 
  - prepare a byhand upload
  - targetted at unstable (ie Distribution: unstable)
  - with a byhand file called ddtp-translations_2007.12.12-1_all.tar.gz
or similar (different package name or version, eg)
  - section should be raw-translations
  - that tarball should contains:
   main/i18n/Translation-xx_XX
   contrib/i18n/Translation-xx_XX
   non-free/i18n/Translation-xx_XX
 ie, translations for all components and languages, uncompressed
 
 Workable?

Yes, we can do that during the i18n Extremadura meeting that
will start in two days. We could even prepare some sort of semi
automatic tests on our side, before get it ready to upload.


 If you can upload all that somewhere I can have a look at it and make
 sure it's workable, rather than directly to the archive, that'd seem
 like a good next step.

Ok, as soon as we hit this stage we will let you know.


 Any suggestions/scripts for validating the uploaded file would be
 good too.

Are there examples/references for what is done/tested/checked
by debian-maintainer and debtags?

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

iD8DBQFHXuocCjAO0JDlykYRAoKbAJ92d9hNQ2FeR+ddZy5HS2xhKnfE1gCfQJZr
HXkwXwaLl5fUM0xJTw5r5n0=
=D1H5
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-11 Thread Anthony Towns
On Tue, Dec 11, 2007 at 05:50:52PM -0200, Felipe Augusto van de Wiel wrote:
  I'm still not entirely comfortable with having something outside of
  ftpmaster determine which translations should be in which suites,
  but that's something that'll probably need changes in apt-ftparchive
  to improve, and can be left 'til later.
   Ok, we would like to help with that, so we can have it in
 Lenny. Not sure exactly what is required and all the details, but
 would be great if we could cooperate to find the best solution to
 fulfill ftpmaster requirements.

Having it be upload the translations; have some archiving tool pull
out the relevant ones for stable/testing/unstable/experimental when
generating the Packages files would make me happier. That way updated
translations would migrate automatically to testing, and translations
of old descriptions wouldn't stick around in the archive. But I don't
think that's your problem.

  Any suggestions/scripts for validating the uploaded file would be
  good too.
   Are there examples/references for what is done/tested/checked
 by debian-maintainer and debtags?

d-m checks who can upload it, debtags checks that there aren't any invalid
entries in the tags files.

The scripts to validate and accept those are at:

   http://ftp-master.debian.org/bzr/ftpmaster-dak/scripts/debian/byhand-tag
   http://ftp-master.debian.org/bzr/ftpmaster-dak/scripts/debian/byhand-dm

Cheers,
aj


signature.asc
Description: Digital signature


Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-11 Thread Michael Bramer
On Mon, Dec 10, 2007 at 12:39:34AM -0200, Felipe Augusto van de Wiel (faw) 
wrote:
 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 ...)

We can use ddtp.debian.org for this. This no problem. We have the
domain and access to this host. 

  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.

Yes, Anthony make it per hand in the past.

   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.

ok, Anthony?

Gruss
Grisu
-- 
Michael Bramer  -   http://www.feuerwehr.kreuzau.de/wiki/
PGP: finger [EMAIL PROTECTED]  -- Linux Sysadmin   -- Use Debian Linux
Free Software is like sex: You don't know what you're missing until
you've tried it.


pgpS5z1HwULVq.pgp
Description: PGP signature


Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-11 Thread Anthony Towns
On Mon, Dec 10, 2007 at 12:39:34AM -0200, Felipe Augusto van de Wiel (faw) 
wrote:
   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.

Yup; the autobyhand stuff we have now (used by debtags and
debian-maintainers) makes that easy to work with too.

I'm still not entirely comfortable with having something outside of
ftpmaster determine which translations should be in which suites,
but that's something that'll probably need changes in apt-ftparchive
to improve, and can be left 'til later.

So I'd say:

 - prepare a byhand upload
 - targetted at unstable (ie Distribution: unstable)
 - with a byhand file called ddtp-translations_2007.12.12-1_all.tar.gz
   or similar (different package name or version, eg)
 - section should be raw-translations
 - that tarball should contains:
  main/i18n/Translation-xx_XX
  contrib/i18n/Translation-xx_XX
  non-free/i18n/Translation-xx_XX
ie, translations for all components and languages, uncompressed

Workable?

If you can upload all that somewhere I can have a look at it and make
sure it's workable, rather than directly to the archive, that'd seem
like a good next step.

Any suggestions/scripts for validating the uploaded file would be
good too.

Cheers,
aj



signature.asc
Description: Digital signature


Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-10 Thread Christian Perrier
Quoting Michael Bramer ([EMAIL PROTECTED]):

  #431891 is still left and no one cares.
 
 yes, unfortunately

I suggest going through rt.debian.org if the issue is related to the
admin of Debian machines (which I can't check right now).




signature.asc
Description: Digital signature


Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-09 Thread Michael Bramer
On Mon, Dec 10, 2007 at 12:21:26AM +0900, Kenshi Muto wrote:
 I'd like to know when Translation-* of ftp mirror will sync with
 of http://ddtp.debian.org/debian/dists/.
 
 #431891 is still left and no one cares.

yes, unfortunately

 Although I understand that bug report gave very poor information for FTP
 masters, current status (provides very old translations with an old
 encoding) is making a problem.

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)
 
 At least for Japanese, Translation-ja in official mirror is encoded
 with EUC-JP. Because APT tool try to treat it as UTF-8 internally,
 all of APT tools (eg. apt-cache, aptitude, or synaptic) shows a broken
 screen.
 Translation-ja in ddtp.debian.org/debian/dists is already encoded
 with UTF-8, that's correct for APT, it provides a right result.

This is right.

 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...

Gruss
Grisu
-- 
Michael Bramer  - a Debian Linux Developer  http://www.debsupport.de
PGP: finger [EMAIL PROTECTED]  -- Linux Sysadmin   -- Use Debian Linux
Das Schlimme am Pessimismus ist eigentlich, meistens Recht zu
 bekommen. -- Michael Olbricht in dasr 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-09 Thread Kenshi Muto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

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.

Thanks,
- -- 
Kenshi Muto
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ http://mailcrypt.sourceforge.net/

iEYEARECAAYFAkdcgLwACgkQQKW+7XLQPLEv/ACgjobraWGKACQmlTzwTayZUduK
6vMAnjP8cAdRzCBQaURfYIYzDlF+T62m
=cwfU
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431891: status of DDTP and ftp mirror synchronization?

2007-12-09 Thread Felipe Augusto van de Wiel (faw)
-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-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]