[Pkg-openmpi-maintainers] Bug#455886: Bug#455886: Fwd: Bug#455886: mpicc seems missing on buildbots

[Manuel Prinz]

Hi Ondrej!

Am Mittwoch, den 12.12.2007, 14:04 +0100 schrieb Ondrej Certik:
> Unfortunately, that's not the case, see my closed bug report about that:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450518

I remember your bug report. At that time, we didn't know about that this
affects everyone building against openmpi. We are aware of that now
because of the groamacs package and yours, and already working on a
solution.

> I purged everything (as buildbots do), then installed openmpi, but the
> alternatives are broken and the solution is to run:
> 
> sudo update-alternatives --remove-all mpicc
> 
> for all the mpi* commands.

On installation and removal of openmpi packages, u-a is called the right
way. I'll try to reproduce that behavior but wasn't able last time. As I
said, you're probably experiencing a bug in u-a, so there's probably
nothing we can do about that. I'm trying to fix the bug in u-a but it's
not as easy as thought.

> Would it be please possible to execute that command
> (update-alternatives) above in the openmpi before installing?

No, because we use u-a the way it's supposed to work. Due to bugs it
unfortunately doesn't. Calling "--removeall" in pre* scripts seems like
an awkward hack. It would get rid of the symptomps but you don't solve
the problem.

> Do you think that g++ isn't installed? I doubt. But in realite I don't
> need g++, but mpicxx. And mpicxx doesn't seem to exist - exactly the
> same problem happened to me, when I had lam/mpich installed, then
> purged everything and then installed openmpi. The solution is to
> execute the update-alternatives command in between - this needs to be
> automated.

I don't know if adding g++ to build depends would change anything. It
may, but it's definetly not related to this bug.

> If what I wrote is true, then I think it's a very serious bug, which
> prevents libmesh (and possibly other packages) to build.

Yes, it is. You are experiencing the same as Nicholas did with his
gromacs package, and your bug is related to #452047 which is marked
"serious". We'll upload a solution to that but as I said, we need a
patch to dpkg's update-alternatives.

Dirk, what's the best way to deal with that? Blocking the bugs?
Reassigning them to dpkg? Raising the dpkg bugs to "serious"? I'm not
sure what is the correct procedure here. But as this affects every
package that wants a) move to openmpi or b) builds packages for more
than one MPI flavor, the u-a bugs should be fixed soon. (Which I work
on.)

Best regards
Manuel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-openmpi-maintainers/attachments/20071212/d302db48/attachment-0002.pgp