On 07/07/13 18:01, Ansgar Burchardt wrote:
Anton Gladky gl...@debian.org writes:
2013/7/4 Torquil Macdonald Sørensen torq...@gmail.com:
However, I have a question concerning multiarch and update-alternatives:
In libmpich-dev.postinst, update-alternatives requires the library file
paths
build-rdeps to check, whether
they are happy with updated package.
Thanks,
Anotn
2013/6/18 Torquil Macdonald Sørensen torq...@gmail.com:
That sounds great! I'm going camping for a few days, but I'll be able to
test it this weekend.
Torquil
On 18/06/13 22:15, Anton Gladky wrote:
Hi,
I have done
should prepare for the renaming.
Anton
2013/5/28 Torquil Macdonald Sørensen torq...@gmail.com:
Hi Anton!
Yes, I would appreciate the help, so that is very kind of you.
Btw, your second point (regarding dh) is something we had planned. But even
though the package has potential for improvement
5) postinst and prerm scripts should be inspected.
If you want, I can try to help with some of points.
Regards,
Anton
2013/5/26 Torquil Macdonald Sørensen torq...@gmail.com:
Yes, I have uploaded the mpich 3.0.3 sources to the upstream branch in the
git repository, as well as made some changes
Hi!
I am a maintainer of the mpich2 package. My goal is to package Mpich
3.0.4 and get someone from the Debian Science team to upload it to Sid.
Before Lucas Nussbaum stepped down as a maintainer, we decided that it
would be a good idea to change the source package name from mpich2 to
mpich
On 26/05/13 20:55, Anton Gladky wrote:
Ho Torquil,
I think it OK, to use mpich as the source package name for mpich version
3. But it is my personal point of view.
We just need to coordinate a transition (if it is necessary). Do you
have already done some packaging on mpich 3?
Yes, I have
On 26/05/13 21:32, Yann Pouillon wrote:
Hi,
IMHO there is absolutely no problem in updating the version of mpich
suggested by science-nanoscale-phases. Actually, it still points to
mpich because I hadn't noticed that the version had not been updated.
I'll gladly put there whichever name
Hi!
I am in the process of renaming the source package mpich2 to mpich, as well
as to upgrade it to version 3.0.3.
The current GIT path is:
git://git.debian.org/debian-science/packages/mpich2.git
According to Debian Science Policy,
On 02/04/13 15:55, Aaron M. Ucko wrote:
Torquil Macdonald Sørensen torq...@gmail.com writes:
Can I simply move the repository, thus making the old GIT path invalid?
Good question. You can move it and leave a compatibility symlink.
Thanks, but the file system seems to be read only
On 02/04/13 20:35, PICCA Frédéric-Emmanuel wrote:
torquil-guest@wagner:/git/debian-science/packages$ mv mpich2.git mpich.git
mv: cannot move `mpich2.git' to `mpich.git': Read-only file system
ok, I move the rrepository and created the symbolic link
Cheers
Fred
Thanks, that was very nice of
On 02/04/13 20:35, PICCA Frédéric-Emmanuel wrote:
torquil-guest@wagner:/git/debian-science/packages$ mv mpich2.git mpich.git
mv: cannot move `mpich2.git' to `mpich.git': Read-only file system
ok, I move the rrepository and created the symbolic link
Cheers
Fred
Oops, it seems that you have
Hi!
Anyone here have an idea if the Debian Boost MPI library can be used
with MPICH2? I'm not sure if I can report this as a wishlist bug or
not, so that's why I'm aksing here.
It seems to me that /usr/lib/libboost_mpi-mt.so is linked to
libmpi.so.0 and libmpi_cxx.so.0, which both come from the
12 matches
Mail list logo
