* Manuel Prinz [Tue, 17 Mar 2009 23:06:24 +0100]:
Am Dienstag, den 17.03.2009, 18:32 +0100 schrieb Adeodato Simó:
Okay; I think it’s reasonable to wait, as long as we make sure it gets
addressed at some point. Maybe we should open a separate bug report for
it?
Feel free to do so if you
* Manuel Prinz [Mon, 16 Mar 2009 21:49:23 +0100]:
Am Sonntag, den 15.03.2009, 16:14 +0100 schrieb Adeodato Simó:
Indeed, bumping the SONAME in 1.3.1 would be great if indeed ABI
compatibility has been broken. Thanks for pursuing this.
Upstream discusses the plans for future releases and
Am Dienstag, den 17.03.2009, 18:32 +0100 schrieb Adeodato Simó:
Okay; I think it’s reasonable to wait, as long as we make sure it gets
addressed at some point. Maybe we should open a separate bug report for
it?
Feel free to do so if you like; usually, they're very responsive and I
expect an
Am Dienstag, den 17.03.2009, 18:32 +0100 schrieb Adeodato Simó:
3.) Patch and build all dependant software.
4.) File bugs for all packages, including patches.
5.) NMU if no response in a reasonable time frame.
Uhm, what kind of patches are needed? Has the API changed as well
between 1.2
Am Sonntag, den 15.03.2009, 16:14 +0100 schrieb Adeodato Simó:
Indeed, bumping the SONAME in 1.3.1 would be great if indeed ABI
compatibility has been broken. Thanks for pursuing this.
Upstream discusses the plans for future releases and dealing with
SONAMEs on their development list. We'll see
* Manuel Prinz [Sat, 14 Mar 2009 22:31:45 +0100]:
Hi Adeodato!
Hello!
Am Freitag, den 13.03.2009, 21:41 +0100 schrieb Adeodato Simó:
Open MPI used to build fine on alpha, so this is probably a problem with
the new upstream release. Reassigning to Open MPI maintainers.
It’s been 2
Am Sonntag, den 15.03.2009, 12:23 +0100 schrieb Adeodato Simó:
There is an unfortunate problem with it, though: you can’t use an
architecture restriction like [arch1 !arch2] in Build-Depends. That
is, you can’t mix ! and non-!; if you stop to think about it, it
doesn’t make sense.
Just
* Manuel Prinz [Sun, 15 Mar 2009 15:47:26 +0100]:
Am Sonntag, den 15.03.2009, 12:23 +0100 schrieb Adeodato Simó:
There is an unfortunate problem with it, though: you can’t use an
architecture restriction like [arch1 !arch2] in Build-Depends. That
is, you can’t mix ! and non-!; if you stop
Manuel Prinz wrote:
Am Sonntag, den 15.03.2009, 12:23 +0100 schrieb Adeodato Simó:
Finally, what’s this business about maintainers not being happy about
Bin-NMUs of their packages?
Not sure if this was rethorical question or if you'd like to have more
information on that.
Certainly not
Hi Adeodato!
Am Freitag, den 13.03.2009, 21:41 +0100 schrieb Adeodato Simó:
Open MPI used to build fine on alpha, so this is probably a problem with
the new upstream release. Reassigning to Open MPI maintainers.
It’s been 2 months, and this issue has not been addressed. In the
meantime,
* Manuel Prinz [Mon, 05 Jan 2009 12:48:10 +0100]:
reassign 510845 openmpi 1.2.8-3
thanks
Hello, Manuel.
Am Montag, den 05.01.2009, 12:05 +0100 schrieb Adeodato Simó:
Package: mpi-defaults
Version: 0.2
Severity: serious
The latest version of openmpi failed to build from source on
reassign 510845 openmpi 1.2.8-3
thanks
Am Montag, den 05.01.2009, 12:05 +0100 schrieb Adeodato Simó:
Package: mpi-defaults
Version: 0.2
Severity: serious
The latest version of openmpi failed to build from source on alpha,
hence mpi-defaults can't be built there, because libopenmpi-dev is
Processing commands for cont...@bugs.debian.org:
reassign 510845 openmpi 1.2.8-3
Bug#510845: mpi-defaults: FTBFS/not available on alpha
Bug reassigned from package `mpi-defaults' to `openmpi'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
Package: mpi-defaults
Version: 0.2
Severity: serious
The latest version of openmpi failed to build from source on alpha,
hence mpi-defaults can't be built there, because libopenmpi-dev is not
installabe.
If mpi-defaults intends to provide packages for other packages to
build-depend on, it should
14 matches
Mail list logo
