May I ask what exactly is preventing this bug from being fixed? As I
told two months ago, it seems that the problem is only that upstream's
64-bit sources aren't used by the package on amd64. When I applied the
changes between the 32-bit and 64-bit upstream sources to the build
tree, everything
On 5/4/06, Lauri Alanko [EMAIL PROTECTED] wrote:
May I ask what exactly is preventing this bug from being fixed? As I
told two months ago, it seems that the problem is only that upstream's
64-bit sources aren't used by the package on amd64. When I applied the
changes between the 32-bit and
On Thu, May 04, 2006 at 09:19:55AM -0600, Shaun Jackman wrote:
For the intents of a Debian maintainer, upstream essentially does not
release a source package of SWT *at all*, since it does not contain
the necessary scripts to actually build the package.
Ah, right. Essentially you're saying
Processing commands for [EMAIL PROTECTED]:
tag 354358 +confirmed
Bug#354358: libswt-gtk-3.1-java: Unusable on amd64 (ia32-specific sources used)
There were no tags set.
Tags added: confirmed
severity 354358 serious
Bug#354358: libswt-gtk-3.1-java: Unusable on amd64 (ia32-specific sources used
Package: libswt-gtk-3.1-java
Version: 3.1-3
Severity: grave
Justification: renders package unusable
Azureus hasn't been working on AMD64 Debian out of the box ever, I think.
This seems to be why.
From a Sun Hotspot 1.5.0_05 error log after a sigsegv when starting
Azureus:
Stack:
tag 354358 +confirmed
severity 354358 serious
retitle 322897 azureus: unusable on AMD64
retitle 331723 azureus: unusable on AMD64
block 322897 on 354358
thanks
On 2/25/06, Lauri Alanko [EMAIL PROTECTED] wrote:
Package: libswt-gtk-3.1-java
Version: 3.1-3
Severity: grave
Justification: renders
6 matches
Mail list logo
