On Thu, Feb 14, 2008 at 1:45 PM, Manuel Prinz <[EMAIL PROTECTED]> wrote: > reopen 464795 = > thanks > > [ Reopening the bug with Ondrej as submitter, so we can close it in the > changelog and Ondrej gets notified when the fix is in sid. Ondrej, hope > that's OK with you! ]
Sure. > Sorry for jumping in a little late, had no access to my mails > yesterday... > > Am Mittwoch, den 13.02.2008, 16:58 -0600 schrieb Dirk Eddelbuettel: > > So Manuel, could it be that the third line here > > > > update-alternatives \ > > --install /usr/include/mpi mpi /usr/lib/openmpi/include 5 \ > > --slave /usr/lib/libmpi.so libmpi.so > /usr/lib/openmpi/lib/libmpi.so.0 \ > > > > needs a fix to > > > > --slave /usr/lib/libmpi.so libmpi.so /usr/lib/openmpi/lib/libmpi.so \ > > This is on of the possible fixes. I applied that to SVN trunk, the > resulting packages seem to be fine and work for me. Wondering how that > slipped through unnoticed on my system... Anyway, I had a problem when > upgrading to the packages build from trunk. I had to *purge* the old > packages because the symlink was not updated. (Maybe a bug in > update-alternatives?) I'd be interested if this behaves the same way on > your system(s), maybe my one is just acting weird again. ;) I currently don't have time to play with it, but I don't think it's about some system acting weird - we should try to find the problem in update-alternatives and fix it. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
