On Wed, Oct 05, 2005 at 11:03:47AM -0600, Shaun Jackman wrote: > 2005/9/28, Nathanael Nerode <[EMAIL PROTECTED]>: > > >These excuses seem to be circular between swingwt and swt-gtk. > > Classic "hint" situation. They both have to go in together; the > > excuses are showing that if you move only one in, it breaks the > > other. Send a message to debian-release@lists.debian.org asking for > > them to add a "hint" so that the two packages can go in > > simultaneously.
> > No point doing so until the hppa build problem is dealt with though; > > a "hint" specifies particular version numbers, so if you have to > > make a new upload, you need to ask for a new hint. > swt-gtk 3.1-2 is all ready to move into testing [1], but it's being > held back by swingwt, which it make "uninstallable on arm". swingwt is > a library that, so far, no other packages use. To me, getting swt-gtk > into testing is far more important waiting for swingwt to get sorted. > swingwt has a couple issues that may take a while, such as a GCJ > internal compiler error on HPPA. Can swt-gtk 3.1-2 be pushed into > testing? By removing swingwt from testing, yes. I've added a hint to do this. On Wed, Oct 05, 2005 at 07:52:54PM +0200, Matthias Klose wrote: > If it ICE's on hppa, why should it be pushed to testing, especially if > there are no apps depending on it? AFAIK the Java Packaging Team > wants to build these libs from the eclipse source anyway, so the > packages would vanish soon again. He's asked for swt-gtk to be pushed in, not swingwt; AIUI, the swingwt failure is a swingwt problem, not an swt-gtk problem, right? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
