On Sun, 2005-10-16 at 13:51 +0200, Frank Lichtenheld wrote:
> On Sun, Oct 16, 2005 at 04:40:31AM -0700, Steve Langasek wrote:
> > FWIW, we're very close now to being able to get everything into testing.
> > The remaining blockers are:
> >
> > rmpi needs built on arm and hppa
> > scalapack needs bu
On Sun, Oct 16, 2005 at 04:40:31AM -0700, Steve Langasek wrote:
> FWIW, we're very close now to being able to get everything into testing.
> The remaining blockers are:
>
> rmpi needs built on arm and hppa
> scalapack needs built on arm, hppa, mipsel, and sparc
> octave2.1 needs built on arm
> oct
On Wed, Sep 21, 2005 at 09:19:04PM +0900, Adam C Powell IV wrote:
> On Thu, 2005-09-08 at 20:18 -0400, Adam C Powell IV wrote:
> > Status report:
> > * petsc: done a long time ago
> > * parmetis: fixed and done last week.
> > * illuminator: finally got time to finish and upload ye
On Thu, 2005-09-08 at 20:18 -0400, Adam C Powell IV wrote:
> Status report:
> * petsc: done a long time ago
> * parmetis: fixed and done last week.
> * illuminator: finally got time to finish and upload yesterday;
> just fixed a bug which prevented building on alpha.
>
Russ Allbery <[EMAIL PROTECTED]> writes:
> I'll file bugs against the lam packages that need migrations this
> evening, asking that they be uploaded with a versioned build dependency
> on lam.
This has now been done.
I'm currently testing the lam patch to make sure that it really does
eliminate
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Wed, Sep 21, 2005 at 11:23:02AM -0700, Russ Allbery wrote:
>> The main thing that we're blocked on at the moment is lam. lam
>> currently FTBFS on m68k due to a gcc 4.0 bug. I'm going to provide a
>> patch today to lower the optimization to -O2 for
On Wed, Sep 21, 2005 at 11:23:02AM -0700, Russ Allbery wrote:
> The main thing that we're blocked on at the moment is lam. lam currently
> FTBFS on m68k due to a gcc 4.0 bug. I'm going to provide a patch today to
> lower the optimization to -O2 for all architectures, based on debian-devel
> comme
Adam C Powell IV <[EMAIL PROTECTED]> writes:
> So what else is left?
> * mpb: not built on m68k
> * hdf5: not built on m68k, waiting for lam with m68k build trouble
> * blacs-mpi: not built on m68k
> * scalapack: not built on arm, m68k, powerpc+
> * netpipe: needs new
On Tue, 2005-08-30 at 10:35 -0700, Russ Allbery wrote:
> Adam C Powell IV <[EMAIL PROTECTED]> writes:
>
> > I'm doing builds (and uploads) of the (non-free) parmetis and hypre as
> > we speak, will address this dependency issue in hypre. I'm also fixing
> > another couple of errors in parmetis, w
I didn't get as much done today as I was hoping, but some progress was
made. I've filed new RC bugs for the transition against:
blacs-mpi
scalapack
and have followed up to Bug#323744 with a more complete patch and an
additional note that this rebuild is needed for the transition.
I have
On Tue, Aug 30, 2005 at 01:16:43PM -0400, Adam C Powell IV wrote:
> > > - Get someone to hand-build the new illuminator package on a sparc
> > > running 2.6. The drawbacks of this are that it hides the buildd issue
> > > rather than ensuring it gets fixed, and that sparc porters are
> > > cu
Adam C Powell IV <[EMAIL PROTECTED]> writes:
> I'm doing builds (and uploads) of the (non-free) parmetis and hypre as
> we speak, will address this dependency issue in hypre. I'm also fixing
> another couple of errors in parmetis, which will make shared lib deps
> work better for that package.
E
Hello,
Just catching up on Debian stuff and found this email... Let me reply
to the parts relevant to my packages.
On Mon, 2005-08-29 at 20:02 -0700, Russ Allbery wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > Package: hypre
>
> Uses mpicc and therefore statically linked, and doesn'
Steve Langasek <[EMAIL PROTECTED]> writes:
> apt-cache rdepends can sometimes miss things, because it won't report
> reverse-dependencies for a package that it believes doesn't exist. A
> tool that gives more consistent results is grep-dctrl; i.e.,
> $ grep-dctrl -FDepends -sPackage libmpich1.0
Hi Russ,
On Sat, Aug 27, 2005 at 09:10:12PM -0700, Russ Allbery wrote:
> I've volunteered to try to help coordinate the mpich C++ transition. I'm
> still just learning how to do this, so this first message is just an
> outline of what I think the current state is and what actions are needed
> nex
Hello all,
I've volunteered to try to help coordinate the mpich C++ transition. I'm
still just learning how to do this, so this first message is just an
outline of what I think the current state is and what actions are needed
next so that more experienced people can correct me if I get any of it
16 matches
Mail list logo
