[Pkg-openmpi-maintainers] Bug#444432: libopenmpi-dev: duplicate opalcc man page

[Dirk Eddelbuettel]

On 28 September 2007 at 19:48, Manuel Prinz wrote:
| Am Freitag, den 28.09.2007, 12:23 -0500 schrieb Dirk Eddelbuettel:
| > On Fri, Sep 28, 2007 at 07:02:02PM +0200, Manuel Prinz wrote:
| > > After checking those, I came up with the following:
| > > 
| > > openmpi-bin: added "openmpi-bin (<= 1.2.3)" to Conflicts and Replaces
| > 
| > Err, why this?   You declaring pkg foo to Conflict/Replace itself? 
| > I'm confused. Maybe I just need more coffee...
| 
| Because I'm quite unexperienced regarding these issues (and packaging in
| general) and you stated earlier in the BTS:
| 
| > So we need Conflicts: and Replaces: for openmpi-bin, and possible also
| > Provides: -- as I always forget this part, could someone check and
| > then test the upgrade from 1.2.3-4. 
| 
| I read it as "the Confilts/Replaces fields of openmpi-bin". Sorry if I
| didn't get that right! :(

Well I wrote fast and furiously making it easy to be misunderstood.
 
| It seemed to me like that's the way for openmpi-bin to declare "update
| me to the new version or uninstall me" which is what we want, isn't it?
| 
| Adding "Replaces: openmpi-bin" to libopenmpi-dev seemed strange, since

That's what we need. See below.

| it just partially replaces openmpi-bin. AFAICS, we had no dependency on
| openmpi-bin, so installation of -dev without -bin was possible. (Though
| useless, since the compilers were missing.) Wouldn't Replaces force
| openmpi-bin to be installed? I think that's not what we want, at least
| not for the 1.2.4 package.

Recall that the error was

   Unpacking replacement libopenmpi-dev ...
   dpkg: error processing /var/cache/apt/archives/libopenmpi-dev_1.2.4-0_i386.deb (--unpack):
     trying to overwrite `/usr/share/man/man1/opalcc.1.gz', which is also in package openmpi-bin

do dpkg that _libopenmpi-dev_ has a bug, because it wants to install a file
belonging to _openmpi-bin_ in the installed version.

The way around is to endow libopenmpi-dev with an attribute that allows it to
overwrie in openmpi-bin --- ie. this is what 
	'Replaces: openmpi-bin (<= 1.2.3-4)'
does.  

The open question is whether we need a Conflicts: too.  Possibly not --
question of testing, now from 1.2.3-4 to a new 1.2.4-0~2 or whatever you call
it in your tests.

| > > libopenmpi-dev: added "openmpi (<= 1.2.3)" to Replaces
| > 
| > Ok, but shouldn't it be 1.2.3-4 ?  
| 
| The problem exists with all Debian revisions prior to 1.2.4, meaning the
| whole 1.2.3 series, so I used just that part. I even thought about using
| "(<< 1.2.4)" but didn't see any advantage in that.

Just aesthetics -- should all mean the same here.
 
| Thinking about that now, shouldn't it be "(<< 1.2.4-1)"? The problem
| exists in 1.2.4-0 too, which is not covered by the above expression.

Correct. So make it (<= 1.2.4-0).  'Up and including the last buggy version'.

| > > I rebuild the package and had a smooth upgrade from 1.2.3-4 to
| > > 1.2.4-1~1 on my system. (I had some
| > 
| > Ok.
| 
| I'll have a try using just relationships in libopenmpi-dev. That seems
| to be like a better approach.

Yup.
 
| Best regards
| Manuel, confused and hungry

Get some food and some rest, we can finish this tomorrow or on Sunday.

Thanks for all your work, Dirk
 

-- 
Three out of two people have difficulties with fractions.