On Thu, Apr 29, 2004 at 11:01:56PM -0400, Grzegorz B. Prokopski wrote:
Yes, this is definitely going to require a hint; I just hadn't gotten to
the point yet of figuring out what the hint needed to look like.
I now have a hint in place for sablevm-classlib 1.1.3-1.
Sounds good, but
Steve Langasek writes:
So the issue is that libsablevm-native1 is built on all architectures,
but sablevm hasn't been built on mips and mipsel, resulting in an
unsatisfiable dependency.
It's the build dependency on libffi2-dev, which is still missing on
mips/mipsel. If/when gcc-3.4 moves to
On (02/05/04 21:56), Matthias Klose wrote:
Steve Langasek writes:
So the issue is that libsablevm-native1 is built on all architectures,
but sablevm hasn't been built on mips and mipsel, resulting in an
unsatisfiable dependency.
agrh... now i remember - I tightened the inter-dependencies
On Sun, May 02, 2004 at 06:01:36PM -0400, Grzegorz B. Prokopski wrote:
On (02/05/04 21:56), Matthias Klose wrote:
Steve Langasek writes:
So the issue is that libsablevm-native1 is built on all architectures,
but sablevm hasn't been built on mips and mipsel, resulting in an
On (27/04/04 22:33), Steve Langasek wrote:
Hi Grzegorz,
On Tue, Apr 27, 2004 at 01:36:58PM -0400, Grzegorz B. Prokopski wrote:
sorry for bothering you, but there's something wrong (again) w/ migration
of SableVM packages to testing. Last time 1.1.0-5 was hinted, so I
though that the
Hi,
sorry for bothering you, but there's something wrong (again) w/ migration
of SableVM packages to testing. Last time 1.1.0-5 was hinted, so I
though that the hint is permanent and it would work this time also.
But the packages seem to be stalled again and for a reason no better
than
Hi Grzegorz,
On Tue, Apr 27, 2004 at 01:36:58PM -0400, Grzegorz B. Prokopski wrote:
sorry for bothering you, but there's something wrong (again) w/ migration
of SableVM packages to testing. Last time 1.1.0-5 was hinted, so I
though that the hint is permanent and it would work this time also.
7 matches
Mail list logo
