[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#813128: Fwd: Bug#813128: transition: openmpi



On Tue, Feb 16, 2016 at 11:37:19AM +0100, Thibaut Paumard wrote:
> > then mpi-defaults would need a sourceful uploads every single time
> > a new architecture is added (and we want to support MPI there and
> > openmpi builds), and also suddenly file a dozen RC bugs (as all
> > packages using such a system would start to fail). Yes, we can do
> > it, though.

See
https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.git/commit/?id=07ef8a6
https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.git/commit/?id=4fa28c2
https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.git/commit/?id=d9656b2

> So, what we want if to render RC buggy some packages that need a
> source upload whenever OPENMPI_ARCHITECTURES or MPICH_ARCHITECTURES
> change.

Somebody needs to do that.  I can also have mpi-defaults provide a
script to be called by the packages at build time, if somebody provides
it.

> An easier way would be for those packages to have a versioned
> dependency on mpi-default-dev and bump this version when either
> variable changes, e.g.
> 
> Build-Depends: mpi-default-dev (>= 1.3), mpi-default-dev (<< 1.4~)

umh, looks messy.

> This is assuming the minor part of the version of mpi-default-dev
> changes when either variable changes. The version can then have also a
> micro digit, to allow for new versions that don't change these variables

in the past mpi-defaults was binNMUed to change defaults; don't rely on
that.

> Actually a versioned dependency seems required anyway since you know
> your new package will FTBFS with earlier versions of mpi-default-dev.

*shrugs*

> The only thing is that you can also predict that later versions of
> mpi-default-dev will break your package.
> 
> This discussion getting off-topic for this bug, should we move
> somewhere else?

indeed.
probably better suited for a mpi-defaults bug; feel free to open one and
report a summary of what said here.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: