Bug#290018: charva FTBFS (was: Re: Contrib packages that probably should be forced into testing)

2005-01-12 Thread Arnaud Vandyck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: charva Severity: critical Wed, 12 Jan 2005 02:52:20 -0800, Steve Langasek <[EMAIL PROTECTED]> wrote: >> Anyway, I've just try to build it on x86 and it FTBFS :( > > Is this still the case? Is this related to the bugs in kaffe on i386? I

Re: Contrib packages that probably should be forced into testing

2005-01-12 Thread Steve Langasek
On Wed, Jan 05, 2005 at 11:11:40AM +0100, Arnaud Vandyck wrote: > Wed, 5 Jan 2005 01:20:37 -0800, > Steve Langasek <[EMAIL PROTECTED]> wrote: > > On Wed, Jan 05, 2005 at 09:48:02AM +0100, Arnaud Vandyck wrote: > >> Wed, 5 Jan 2005 02:02:29 +0100, > >> Jeroen van Wolffelaar <[EMAIL PROTECTED]> w

Bug#290018: charva FTBFS (was: Re: Contrib packages that probably should be forced into testing)

2005-01-12 Thread Arnaud Vandyck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: charva Severity: critical Wed, 12 Jan 2005 02:52:20 -0800, Steve Langasek <[EMAIL PROTECTED]> wrote: >> Anyway, I've just try to build it on x86 and it FTBFS :( > > Is this still the case? Is this related to the bugs in kaffe on i386? I

Re: Contrib packages that probably should be forced into testing

2005-01-12 Thread Steve Langasek
On Wed, Jan 05, 2005 at 11:11:40AM +0100, Arnaud Vandyck wrote: > Wed, 5 Jan 2005 01:20:37 -0800, > Steve Langasek <[EMAIL PROTECTED]> wrote: > > On Wed, Jan 05, 2005 at 09:48:02AM +0100, Arnaud Vandyck wrote: > >> Wed, 5 Jan 2005 02:02:29 +0100, > >> Jeroen van Wolffelaar <[EMAIL PROTECTED]> w

Re: Contrib packages that probably should be forced into testing

2005-01-08 Thread Anthony Towns
Steve Langasek wrote: The testing scripts only check the installability of arch: all packages on one of our architectures -- for obvious reasons, that architecture is i386. It's more the other way around: the testing scripts would check the installability of arch: all packages on all architect

Re: Contrib packages that probably should be forced into testing

2005-01-05 Thread Jeroen van Wolffelaar
On Wed, Jan 05, 2005 at 09:48:02AM +0100, Arnaud Vandyck wrote: > About all the other java packages, I'd like to move a lot of them in > main but even if kaffe (and sablevm) made good steps, they are not > stable (kaffe)/complete (both) enough to move them to main at the > moment. I don't think the

Re: Contrib packages that probably should be forced into testing

2005-01-05 Thread Arnaud Vandyck
Wed, 5 Jan 2005 01:20:37 -0800, Steve Langasek <[EMAIL PROTECTED]> wrote: > On Wed, Jan 05, 2005 at 09:48:02AM +0100, Arnaud Vandyck wrote: >> Wed, 5 Jan 2005 02:02:29 +0100, >> Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote: > >> > * charva (- to 1.0.1-3) >> > + Maintainer: De

Re: Contrib packages that probably should be forced into testing

2005-01-05 Thread Arnaud Vandyck
Tue, 4 Jan 2005 17:30:35 -0800, mbc <[EMAIL PROTECTED]> wrote: > I'm working on a new version of this package now. It depends on > java2-runtime because it uses swing. Is there a different virtual > dependency that I can use to resolve the problem and get it into > testing? If you have never see

Re: Contrib packages that probably should be forced into testing

2005-01-05 Thread Steve Langasek
On Wed, Jan 05, 2005 at 09:48:02AM +0100, Arnaud Vandyck wrote: > Wed, 5 Jan 2005 02:02:29 +0100, > Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote: > > * charva (- to 1.0.1-3) > > + Maintainer: Debian Java Maintainers > > + Section: contrib/libs > > + 342 days

Re: Contrib packages that probably should be forced into testing

2005-01-05 Thread Arnaud Vandyck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wed, 5 Jan 2005 02:02:29 +0100, Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote: > * charva (- to 1.0.1-3) > + Maintainer: Debian Java Maintainers > + Section: contrib/libs > + 342 days old (needed 10 days) >

Re: Contrib packages that probably should be forced into testing

2005-01-04 Thread mbc
I'm working on a new version of this package now. It depends on java2-runtime because it uses swing. Is there a different virtual dependency that I can use to resolve the problem and get it into testing? If you have never seen it, it's an X app that has a fairly complicated interface. Is there