[Pkg-java-kaffe] Re: Next challenges for the kaffe package

[Arnaud Vandyck]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ean Schuessler <ean@brainfood.com> writes:

> For reasons of protocol I think I should be the one who performs the uplo=
ad=20
> changing the Maintainer field. I would also like to see us agree on some=
=20
> ground rules for how decisions will be made in the group. Presumably ther=
e=20
> has been some work done in the X-Strike-Force to figure this out. I don't=
=20
> know how formal they are. One approach would be apache +1 style voting.

I don't care. Make this guide lines and I'll follow them. Make the
upload when you want.

<snip reason=3D"tired"/>

1=B0 You don't need to be a pkg-java administrator because you don't need
   to make administrative tasks on pkg-java (I already helped
   'classpath' and 'kaffe' upstream but don't need the commit right! So
   I never asked it but I don't think kaffe and classpath guys don't
   respect me because I don't have the write access to their cvs! Your
   arguments seem strange sometimes!). If you want to be the
   administrator of a project, create one:
   https://alioth.debian.org/register/projectinfo.php

   If you want kaffe to be maintained by something like a secret team,
   in a secret way, I'm not sure I'll be a part of it.

2=B0 If you don't want kaffe to be 'maintained' by pkg-java-kaffe, I don't
   care but, please, next time, don't agree with the idea and then
   change your mind, I'll spend less time doing 'administrative' things!

> ps. I can't find any reasonable documentation for CDBS. I can read the=20
> examples but that will take a little time. Doogie (aka Adam Heath) sits a=
bout=20
> 20 feet from me and that makes me a little biased towards original-formul=
a=20
> DBS. If someone can explain the benefits of CDBS vs DBS I would be gratef=
ul.

Not that much documentation ATM. Is it possible with DBS to get rid of
the tarball in the .orig.tar.gz? If yes, we can go on this way, I don't
care.

> I agree on #235937.

So you can resolve it when you'll upload the package with the new
maintainer field.

> I thought that the engine is supposed to default to interpreter on
> platforms  with incomplete JITs. Is that the case? Or does it default
> to the JIT for  ease of development. Dalibor?

Dalibor is re-synchronizing classpath and kaffe, not sure he'll have the
time to answer, but i got some other points bellow...

(snip my mail)

>> o can we close this bug (fixed in 1.1.4?) (#229740)?
>>   kaffe: typo in 'Can not found "/some/package/X" [JLS 7.5.2, 7.6]'

?

>> o can we close all the fixed in NMU bugs?

?

>> o when I upload kaffe, do I change the Maintainer field to:
>>   Kaffe Strikes Force <pkg-java-kaffe@lists.alioth.debian.org>
>>   and the Uploaders field to ean and I?

You'll do it.

>> o when the next package will be uploaded, let's see the buildd logs and
>>   close the RC bugs:
>>
>>   - #227739: kaffe FTBFS on buildd for alpha
>>   - #227740: kaffe FTBFS on buildd for hppa
>>   - #227741: kaffe FTBFS on buildd for ARM
>>   - #227742: kaffe FTBFS on buildd for ia64
>>   - #227744: kaffe FTBFS on buildd for m68k
>>   - #227745: kaffe FTBFS on buildd for s390
>>   - #227746: kaffe FTBFS on buildd for sparc

?

Now that Alioth is back on line, you can subscribe to pkg-java-kaffe,
it'll avoid to send the mail to everybody (that's why the list is for
;-))

Cheers,

=2D --=20
  .''`.=20
 : :' :rnaud
 `. `'=20=20
   `-=20=20=20=20
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFATG1N4vzFZu62tMIRAhgMAKCj5n/Ntj+1vkDqpAhpz6dIvyTU7ACgqgGe
5fwxrpfBTIfHsNgG2bW4cCs=3D
=3DrFw1
=2D----END PGP SIGNATURE-----