Ok, so it should all boil down to waiting a few days (hopefully). I think I will follow this waiting policy, hoping that in the meanwhile the python 2.4 vs 2.5 issue gets sorted out. I understand this must be a pain for the maintainers of dolfin! Cheers
Lorenzo On 19/09/2007, LUK ShunTim <[EMAIL PROTECTED]> wrote: > Lorenzo Isella wrote: > > Hello Åsmund > > I think there is a misunderstanding here: I left as a comment that I am > > using Debian unstable, but actually I am using testing, if you look in > > detail at the repositories' web addresses. > > I noticed the following: for debian libumfpack4 is "there": > > http://packages.debian.org/unstable/libumfpack4 > > but for testing something funny happens: > > http://packages.debian.org/testing/libumfpack4 > > Now, I am finding out now about virtual packages, so I won't be much > > help here. > > Even in stable there is a "normal" package: > > http://packages.debian.org/stable/libumfpack4 > > Hello Lorenzo, > > It's libsuitesparse which provides libumfpack4 but unfortunately when I > checked it last night at home on an i386 box, it provides libumfpack4 > without a version, while dolfin requires a version number. These little > differences between debian and ubuntu sometimes make you mad. :-( > > In official debian, packages will migrate from unstable/sid to testing > after some time if no critical bugs are found. > > Regards, > ST > -- > > > _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
