retitle 551752 mpich2: suggest mpich2-doc instead of recommending it thanks
On 20/10/09 at 18:50 +0200, Christian Engwer wrote: > On Tue, Oct 20, 2009 at 06:30:25PM +0200, Lucas Nussbaum wrote: > > On 20/10/09 at 14:29 +0200, christi wrote: > > > Package: mpich2-doc > > > Version: 1.2-2 > > > Severity: normal > > > > > > > > > mpich2-doc conflicht with lam4-dev. It is possible to install lam and > > > mich at the same time. Only the mpich2-doc package can't be installed > > > together with lam4-dev. Why? I can't a see any good reason. > > > > lam4-dev also ships the manpages for LAM, so there are file conflicts > > between mpich2-doc and lam4-dev, unfortunately. The solution would be to > > move all the docs from lam4-dev to (say) lam4-doc. > > > > But the LAM package is basically unmaintained, both in Debian and > > upstream. Are you still using it? Have you considered moving to openmpi > > or (now) mpich2? > > OpenMPI has a serious bug that prevents me from using it atm (it's > fixed upstream). Can you give a pointer to a bug report or something? If the bug is serious not just for you, it might be possible to backport the fix to Debian. > Actually I don't care which MPI-documentation I have installed. As > this problem persists I install lam4-doc. But the recommendation of > mpich2-doc results in the removal of lam4-dev as the prefered solution > of apt. This behaviour is imho strange for the average user. Yes, since it's only a "recommend", you could probably remove mpich2-doc and install lam4-dev back. I've changed the bug title accordingly, and I'll push the change -- I'll wait a few days first to see if something else shows up. > PS: Wouldn't a NMU of lam be a better solution to the manpage problem > than this conflict? It has already been NMUed 5 times... I'd prefer to invest time to make OpenMPI and MPICH2 rock in Debian, so we can phase out LAM/MPI and mpich1, rather than work on LAM and mpich... -- | Lucas Nussbaum | [email protected] http://www.lucas-nussbaum.net/ | | jabber: [email protected] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
