[Pkg-openmpi-maintainers] Bug#452047: Bug#452047: gromacs-openmpi: Package depends on lam4c2

[Manuel Prinz]

Am Dienstag, den 11.12.2007, 10:00 -0600 schrieb Dirk Eddelbuettel:
> Maybe we should release a new openmpi to fix the few trivial bugs, and maybe
> add a NEWS or README item indicating this open issue with the alternatives --
> and how our hands are tied by update-alternatives -- to give this some more
> visibility.  I think that would improve over more packages still building
> with lam 'just because they always did'.  Thoughts?

I think a new upload is definitely a good idea. I also thought of
removing all blocks from our bug first, and directly block the bug in
gromacs by dpkg. (Reassigning the blocking bug, so to say.) TTBOMK,
we're "out" of this since we fixed the bug. It not working effectively
in gromacs is a problem that exists because of a broken alternatives,
not openmpi. As far as I understand the BTS, we can't close our bug with
an upload because the dpkg need to be closed first. By unblocking first,
we circumvent that. (As said, it's not an openmpi bug per se.)

Dirk, what do you think about that? It fixes at least one of the bugs.
I'll help Nicholas with the others because I care about gromacs as well,
but that's a different story; I see no point in waiting for all RC bugs
fixed at the same time. (Meaning, I agree with you here.)

I can write the needed mail to control at b.d.o later, if you think that's
the way to go. But before uploading, we should make a test build again,
since I'm not sure what's the situation with the shlibs issue.

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/20071211/dab76186/attachment-0002.pgp