Julien BLACHE <[EMAIL PROTECTED]> wrote:
>> I was not able to access raptor (s390) and on casals (mips)
> I'll try and build it on mips. The machine is dist-upgrading at the
> moment.
Looks like you want a mipsel build and not a mips one.
As I don't have mipsel hardware, I can't help here. tbm
Andreas Tille <[EMAIL PROTECTED]> wrote:
Hi,
> I was not able to access raptor (s390) and on casals (mips)
> Is there any chance to move clustalw to testing?
I'll try and build it on mips. The machine is dist-upgrading at the
moment.
If someone beats me to it, please shout.
JB.
--
Julien B
> On Sat, 28 Oct 2006, Charles Plessy wrote:
> >I think that what happend to clustalw shows that the current unofficial
> >autobuilding process is very fragile. As if I understand correctly one
> >release manager is implicated in buildd.net,
Well, not directly...
Andreas Barth is managing the un
Hi,
I leave the fully quoted text below to enable debian-devel
readers to understand the problem.
I was not able to access raptor (s390) and on casals (mips)
I've got
$ apt-get source clustalw
Reading package lists... Done
Building dependency tree... Done
E: Unable to find a source package for
4 matches
Mail list logo
