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

Dirk Eddelbuettel edd at debian.org
Fri Sep 28 17:23:13 UTC 2007


On Fri, Sep 28, 2007 at 07:02:02PM +0200, Manuel Prinz wrote:
> Am Freitag, den 28.09.2007, 10:32 -0500 schrieb Dirk Eddelbuettel:
> > It's a standard issue of moving files. I think you need versioned
> > Conflicts as well as Replace but Provides only if the 'replaced'
> > package is empty as a result of the move (not our case).  
> > 
> > Check the manuals, check other packages.  
> 
> 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...

> libopenmpi-dev: added "openmpi (<= 1.2.3)" to Replaces

Ok, but shouldn't it be 1.2.3-4 ?  


> The later was because of section 7.5.1 of the policy:
> 
> > Firstly, as mentioned before, it is usually an error for a package to
> > contain files which are on the system in another package.
> > 
> > However, if the overwriting package declares that it Replaces the one
> > containing the file being overwritten, then dpkg will replace the file
> > from the old package with that from the new. The file will no longer
> > be listed as "owned" by the old package.
> 
> I think that fits to our situation. 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.

Dirk

> trouble with getting piuparts to run but those are general and not
> related to the package.) I'll check in the modifications, not knowing if
> those are correct, though.
> 
> Best regards
> Manuel
> 

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



More information about the Pkg-openmpi-maintainers mailing list