Hi Robie!
On Wed, Feb 08, 2012 at 04:14:30PM +, Robie Basak wrote:
> In a sid amd64 chroot, I am satisfying build dependencies, then
> running debian/rules build, then running debian/rules clean. The
> clean target fails.
I am unable to reproduce this problem with the recent Open MPI version
On Sat, Dec 14, 2013 at 10:32:58PM +0100, Torquil Macdonald Sørensen wrote:
> So either there are memory leaks in OpenMPI that are triggered by
> that test program, or the OpenMPI Valgrind suppression file
> /usr/share/openmpi/openmpi-valgrind.supp is not complete.
The problem is reproducible. I'l
On Thu, Oct 20, 2011 at 03:46:02PM +0200, Mickaël Canévet wrote:
> Could you please fix bug #611454 in Debian squeeze, not only wheezy
> and sid ?
Since squeeze is oldstable by now, I simply close it.
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On Sun, Aug 18, 2013 at 02:09:31PM +0200, Michael Banck wrote:
> Right, I also see the trouble in sbuild now. It kinda worked fine just
> running the build manually, but even then, I noticed sometimes it
> skipped the test stage.
>
> Not sure why that is, I will investigate.
I just ran it severa
Hi Matthieu,
thanks for the report and the patch! It seems to be fixed in current
versions. I'll therefore close the bug.
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi Andreas!
Thanks for the patch! It's in SVN now and will be in the next upload.
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
tags 734096 + pending
thanks
On Sun, Jan 05, 2014 at 06:11:27PM +0100, Gilles Filippini wrote:
> Please find attached a patch proposal.
Thank you for the patch! I included it in SVN and it will be part of
the next upload.
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-re
Package: kanla
Version: 1.3-1
Severity: wishlist
File: kanla
Hi Michael,
after your great talk yesterday I played with kanla. I liked and already
recommended it to other people. It would be really great to have it in
wheezy-backports. This is the bugreport asked for in [1].
Thanks a lot for kanl
Hi Roderich!
On Sat, Feb 04, 2012 at 02:04:24PM +0100, Roderich Schupp wrote:
> Patch attached.
Thanks for the patch! I applied it to the SVN repo and it will be in
the next upload.
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "
Hi Michael!
On Thu, Sep 08, 2011 at 09:38:44PM +0200, Michael Banck wrote:
> Adding libmpi_f77 to the library list fixed this problem, but I
> believe this is not the right fix, so filing as a bug.
I tested this with the new version of Open MPI that I did upload to
experimental yesterday. libmpi_
On Wed, Sep 28, 2011 at 05:42:57PM +0300, Konstantinos Margaritis wrote:
> This bug may have been closed but there are no fixed packages in
> unstable since the fix (~5 months ago), causing some packages to fail
> on armhf: blacs-mpi, mpi4py, etc. Do you plan some upload to unstable
> any time soon
Hi Mark!
On Mon, Oct 31, 2011 at 05:54:33PM +, Mark Hymers wrote:
> This is a regression from lenny (openmpi 1.3 seems to have defaulted
> to building SGE support whereas 1.4 defaults to not doing it… sigh)
> and, wearing my SGE maintainer hat, I'd be interested in trying to
> get it fixed in
Am Freitag, den 02.09.2011, 16:24 +0200 schrieb Frederik Himpe:
> According to
> http://www.open-mpi.org/faq/?category=building#build-rte-sge it's enough
> to configure openmpi with the --with-sge parameter. I have added
> --with-sge to debian/rules and rebuilt the package and I can confirm
> that
Am Mittwoch, den 20.07.2011, 22:21 +0200 schrieb Jean-Louis Dupond:
> Package fails to build on Ubuntu due to a bug in debian/rules.
> The db_installdocs are twice called with --all, which shouldn't be the case.
Thanks for your report and the patch! I'm in the process of rewriting
the debian/rules
tags 628826 + moreinfo unreproducable
thanks
Hi Jakub,
I can build pdb2pqr without problems in i386 unstable chroots on
two different amd64 host. Can you please give details on your
build setup?
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Package: music
Severity: normal
Tags: patch
Hi Mikael,
the attached patch fixes the bug. This would allow openmpi to
drop all .la files.
Best regards,
Manuel
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64
Package: openmpi
Severity: wishlist
Reminder to myself: Remove .la files once music cleared
dependency_libs.
Best regards,
Manuel
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.3
Package: wnpp
Severity: wishlist
Owner: Manuel Prinz
* Package name: prank
Version : 100802
Upstream Author : Ari Loytynoja
* URL : http://www.ebi.ac.uk/goldman-srv/prank/src/prank/
* License : GPL2+
Programming Lang: C++
Description : Probabilistic
On Thu, May 19, 2011 at 08:08:39AM +0200, Anton Gladky wrote:
> Seems, that hurd-i386 is also supported by openmpi-bin and libopenmpi-dev.
> Please, consider an adding it to mpi-defaults as well?
I incorporated your patch, slightly modified. I'm targetting an upload to
experimental. The upload als
retitle 416269 ITP: pdb2pqr -- Converts Protein Data Bank (PDB) files to PQR
retitle 420734 RFP: propka -- Modifies the protonation state of protein
structures
owner 416269 !
owner 420734 !
thanks
PDB2PQR and PROPKA are packaged and waiting in NEW.
Thanks for this effort, nonetheless!
Best rega
On Sat, Jan 08, 2011 at 09:50:39AM +0100, Ralf Wildenhues wrote:
> And, I guess, upstream OpenMPI should be notified about this.
Done. And thanks a lot for taking the time to investigate this!
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a su
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Dear Release Team,
please remove pj from testing and unstable. It's outdated,
probably buggy and has a very low popcon (~10). I found it
particularly hard to contact upstream recently and I have
Am Dienstag, den 02.11.2010, 08:02 +0100 schrieb Lucas Nussbaum:
> Is the root cause for disabling it that it crashes on kFreeBSD, or that
> is it deemed experimental by upstream?
It was indeed deemed experimental upstream, so disabling it on certain
arches will not help much. It might very well b
Hi Lucas,
thanks for your report!
On Mon, Nov 01, 2010 at 10:18:14PM +0100, Lucas Nussbaum wrote:
> In debian/rules, there's a mention that threading support is disabled
> because it is broken according to #435581. That bug is really old, and
> I'm wondering whether we could revisit that decision
On Thu, Oct 21, 2010 at 01:54:37PM -0400, Jeff Squyres wrote:
> The right ticket to reference is probably this one:
>
> https://svn.open-mpi.org/trac/ompi/ticket/1241
Thanks! Did miss this one. I linked it to our BTS and tagged
the bug accordingly.
Best regards,
Manuel
--
To UNSUBSCRIBE,
Am Montag, den 11.10.2010, 14:26 -0500 schrieb Jeff Squyres:
> 3. We do know how to make our progression engine switch between
> blocking and busy-polling (i.e., we've had many discussions about it
> over the years -- shared memory message passing is the Big Problem).
> But no one has ever had the
Hi Aurelien,
thanks for the patch!
On Wed, Sep 08, 2010 at 10:14:14PM +0200, Aurelien Jarno wrote:
> openmpi fails to build from source of sparc64, simply because this
> architecture is not present in debian/control. The fix is very
> straightforward, as shown in the patch below. Could you please
On Sat, Oct 02, 2010 at 01:37:42PM -0700, Zack Weinberg wrote:
> I wrote a test MPI program that just calls MPI_Probe() once - this
> should block forever, since there are no sends happening. When run
> with
>
> $ mpirun -np 2 ./a.out
>
> MPI_Probe never returns and the processes spin through po
On Sat, Oct 02, 2010 at 03:56:04PM -0500, Dirk Eddelbuettel wrote:
> Nice work! That totally rhymes with what I recall from late in the 1.2.*
> cycle and would indeed be nice if we could get this tested and then
> documented.
Indeed. I will add a note in README.Debian when I get feedback from Za
Hi Zack!
On Sat, Oct 02, 2010 at 08:39:06AM -0700, Zack Weinberg wrote:
> On Sat, Oct 2, 2010 at 6:01 AM, Manuel Prinz wrote:
> >> On 29 September 2010 at 18:22, Zack Weinberg wrote:
> >> | (on an 8-core machine), CPU utilization jumps *immediately* from 98% idle
> >
Hi Rachel!
On Fri, Sep 03, 2010 at 10:05:17AM +0300, Rachel Gordon wrote:
> There are some good news,
> I added -pthread to both the compilation and link for running
> az_tutorial_with_MPI.f, and I also compiled aztec with -pthread
> Now the code runs O.K for np=1,2.
>
> Now bad news: when I try
> On 29 September 2010 at 18:22, Zack Weinberg wrote:
> | (on an 8-core machine), CPU utilization jumps *immediately* from 98% idle
> | to 20% user, 70% system, 12% idle. strace reveals that each slave is
> | spinning through poll() calls with timeout zero, rather than blocking
> | until a message
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package openmpi
The latest upload of Open MPI fixes one RC bug (#592892).
It also adds support for Torque. I'm aware this is wishlist,
but it's a minor change and h
Am Mittwoch, den 01.09.2010, 21:21 +0700 schrieb Ivan Shmakov:
> Hopefully, I will be able to get to the systems we had OpenMPI
> installed before the weekend.
>
> (And if not, I'll try to think something up.)
Cool! Thanks a lot for your support!
Best regards,
Manuel
--
T
Hi Rachel,
I'm not very familiar with Fortran, so I'm most likely of not too much
help here. I added Jeff to CC, maybe he can shed some lights into this.
Am Montag, den 09.08.2010, 12:59 +0300 schrieb Rachel Gordon:
> package: openmpi
>
> dpkg --search openmpi
> gromacs-openmpi: /usr/share/doc/
Am Freitag, den 13.08.2010, 12:16 -0400 schrieb Stephen Frost:
> Please add support for Torque to the OpenMPI packages.
Good to know that Torque made it into main, finally! We'll add support
for it. Thanks for you report!
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-req
Hi Ivan,
could you please provide feedback if the problem still exists? Neither
upstream nor I do have a working IPv6 setup, so we cannot test if the
patch really fixes the problem. You're help would be very much
appreciated!
In case you do not have time to do the testing, please let us know so w
tags 592892 + confirmed pending
thanks
Am Freitag, den 27.08.2010, 13:57 -0400 schrieb Jeff Squyres:
> This was the badness, as pointed out by Ralf here:
>
> http://www.open-mpi.org/community/lists/devel/2010/08/8292.php
>
> Fix will committed to upstream SVN this evening; a patch for the v1
tag 584699 + help
thanks
Hi Ivan,
thanks for the report! I also took this upstream, but unfortunately
neither upstream nor I can reproduce the bug since we do not have
multi-homed IPv6 hosts available for testing. If you could help us
testing and/or provide us with further information this would
tag 584699 + help
thanks
Hi Ivan,
thanks for the report! I also took this upstream, but unfortunately
neither upstream nor I can reproduce the bug since we do not have
multi-homed IPv6 hosts available for testing. If you could help us
testing and/or provide us with further information this would
Hi Ivan,
thanks for your report!
Am Sonntag, den 06.06.2010, 02:09 +0700 schrieb Ivan Shmakov:
> Package: openmpi-bin
> Version: 1.4.1-1
>
> RFC 3986 reads:
>
> --cut--
>A host identified by an Internet Protocol literal address, version 6
>[RFC3513] or later, is distinguished by e
Am Freitag, den 16.07.2010, 19:29 +0100 schrieb Julien Cristau:
> In case you've missed it, the new version also FTBFS on kfreebsd-i386:
> https://buildd.debian.org/fetch.cgi?pkg=openmpi;ver=1.4.2-1;arch=kfreebsd-i386;stamp=1279291631
I saw it but I have not looked into it yet. I'll probably uploa
Hi Julien!
Am Freitag, den 16.07.2010, 17:26 +0100 schrieb Julien Cristau:
> jcris...@merkel:~$ dpkg-deb -c
> /org/ftp.root/debian/pool/main/o/openmpi/libopenmpi1.3_1.4.2-1_amd64.deb |
> grep libmpi.so
> -rw-r--r-- root/root679992 2010-07-16 08:19
> ./usr/lib/openmpi/lib/libmpi.so.0.0.2
> l
Package: openmpi-bin
Version: 1.4.1-3
Severity: normal
Am Mittwoch, den 07.07.2010, 10:43 +0800 schrieb Changsheng Jiang:
> I have installled openmpi-bin=1.4.1-3 in Debian/sid, why there are no
> ompi-server, which, mentioned in MPI_Publish_name man pages, does
> exist in gentoo system.
Thanks fo
Am Donnerstag, den 08.04.2010, 18:22 -0500 schrieb Pavan Balaji:
> If we choose to do the first approach, what exactly needs to change in
> the mpich2 source? It looks like this is more of a packaging issue for
> Debian?
As Lucas already said, we're already happy with what MPICH2 provides.
But t
Am Mittwoch, den 07.04.2010, 13:12 -0500 schrieb Pavan Balaji:
> Ok, this is the part I didn't understand fully. Is MPICH2's build
> failing when includedir is specified as a different location? (I just
> tried that on my machine and it seems to work correctly for me.) Or did
> you mean some oth
Am Montag, den 05.04.2010, 17:22 +0200 schrieb Marc 'HE' Brockschmidt:
> So, did you spend this time on doing fixes already? :-)
Yes, I indeed did. Not as much as I'd liked too, but nevertheless.
> It would be great to see at least a few patches for the breaking
> packages before the new defaults
Am Donnerstag, den 25.03.2010, 18:28 +0100 schrieb Thibaut Paumard:
> No, with the prioriy of OpenMPI raised above that of MPICH2, and with
> the idea of switching from LAM to MPICH2 on the other arches, my patch
> does not bring any _immediate_ benefit. It's a proposal for a longer
> term so
Hi Thibaut,
thanks for clarifying! It seems to me that we share the same opinion in
(almost) all points but have a different view on the topic.
Am Donnerstag, den 25.03.2010, 16:57 +0100 schrieb Thibaut Paumard:
> Installing mpicc.default as an alternative is to make sure the default
> implemen
> Le 24 mars 10 à 16:59, Lucas Nussbaum a écrit :
> > Actually, the information I was missing is that some packages depend
> > on
> > mpi-default-dev. I thought that mpi-default-dev was only used as a
> > build-dependency. In that case, conflicting is indeed harmful, so the
> > only solution is t
Am Dienstag, den 23.03.2010, 19:30 +0100 schrieb Lucas Nussbaum:
> Given the low number of packages that FTBFS with mpich2 as mpi-default,
> I would say that this could be fixed in the failing packages' build
> system, no?
Sure. It might need some severe patching, though.
> "Fixing" that my provi
Am Samstag, den 20.03.2010, 14:01 +0100 schrieb Marc 'HE' Brockschmidt:
> Manuel Prinz writes:
> > This would enable to fix these in a timely fashion. I could start
> > doing that tomorrow night. How does that sound to you?
>
> Sounds good. Sorry for my delayed an
Am Mittwoch, den 17.03.2010, 13:24 +0100 schrieb Lucas Nussbaum:
> On 17/03/10 at 09:49 +0100, Marc 'HE' Brockschmidt wrote:
> > Lucas Nussbaum writes:
> > > So, it looks like it is mostly build system bugs, and it should not be
> > > too hard to fix.
> >
> > Good to know, thanks for your work.
Hi Samuel!
Am Sonntag, den 07.03.2010, 12:31 +0100 schrieb Samuel Thibault:
> I've just rebuilt 1.4.1-1 with it, at least an MPI_Barrier() call works
> fine.
Thanks for you feedback! I enabled the patch and added the necessary
autofoo stuff to debian/rules. I should work now.
Can you please try
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Dear release team,
as requested by Marc Brockschmidt in <87ocj81kt4@solon.marcbrockschmidt.de>,
I file this bug for the mpi-defaults transition.
As discussed on the Debian Science l
tags 552397 - pending
thanks
Hi Samuel!
Am Mittwoch, den 03.03.2010, 02:58 +0100 schrieb Samuel Thibault:
> The bug was marked pending with a changelog entry, and then 1.4.1-1 got
> uploaded with the patch disabled, is there a problem with it?
Yes, I could not get it to work on a porter box. The
Am Dienstag, den 02.03.2010, 10:25 + schrieb Alan Woodland:
> 2010/3/1 Fernando Tarlá Cardoso Lemos :
> > My suggested fix is to add /usr/bin/orte-checkpoint and
> > /usr/bin/orte-restart
> > to the list of files that are installed by this package.
> >
> Any ideas where these got to? They were
Package: grepmail
Severity: normal
Tags: patch confirmed
Hi,
this option is removed in Date::ManIp > 6, as it is now default. I attached
a trivial patch that should be backwards-compatible.
Several more tests fail due to this bug. I've not investigated #549782 as
of now.
Best regards,
Manuel
-
Hi Youhei!
Am Montag, den 21.12.2009, 17:08 +0900 schrieb Youhei SASAKI:
> It seems version mismatch about gcc-default version. The version of
> gcc-default is 4.4 now, but openmpi library build with gcc 4.3(maybe).
>
> Please rebuild openmpi package using gcc 4.4
This should be fixed with the m
Am Freitag, den 15.01.2010, 10:49 +0100 schrieb Salvatore Bonaccorso:
> Ok, if Alexey would not adopt mathgl by himself, then I will inject it
> in the debian-science team repository
That's a reasonable thing to do anyway. If mathgl was in Debian already,
we should preserve previous work and histo
Hi Salvatore!
Am Sonntag, den 10.01.2010, 15:55 +0100 schrieb Salvatore Bonaccorso:
> mathgl is a Dependency of udav. Thus I'm interested to keep matgl, and
> I would adopt it. But if there is some other interested too, I would
> also help comaintain it, or if there is a scientific team which want
Hi Riccardo!
Am Dienstag, den 04.08.2009, 17:11 +0200 schrieb Riccardo Stagni:
> A lot of development happened to gcx during last months!
> In addition to a gtk2 interface, there is support for raw images produced
> by DSLRs and a minimal support for INDI (for telescope, camera and guider
> contro
Hi Moritz!
Am Dienstag, den 08.12.2009, 22:28 +0100 schrieb Moritz Muehlenhoff:
> You can leave etch and lenny untouched, the impact doesn't warrant an
> update.
Thanks for clarifying!
Best regards
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
Hi Moritz!
Am Dienstag, den 08.12.2009, 20:35 +0100 schrieb Moritz Muehlenhoff:
> You should rather use the copy of libltdl currently in the
> archive or is there a technical reason, which prevents this?
I'm aware of that and discussed it with upstream. They said it would
require quite some chang
Fixed security issue in copy of libtool, see CVE-2009-3736.
+Closes: #559836.
+
+ -- Manuel Prinz Tue, 08 Dec 2009 00:58:02 +0100
+
openmpi (1.3.3-3.1) unstable; urgency=low
* Non-maintainer upload with the maintainer's permission.
diff -u openmpi-1.3.3/debian/patches/series openmpi-1.
Hi Michael!
Am Montag, den 07.12.2009, 00:06 -0500 schrieb Michael Gilbert:
> The following CVE (Common Vulnerabilities & Exposures) id was
> published for libtool. I have determined that this package embeds a
> vulnerable copy of the libtool source code. However, since this is a
> mass bug fili
Am Montag, den 07.12.2009, 09:30 +0100 schrieb Sylvestre Ledru:
> Manuel, are you going to handle this issue or do you want me to do it ?
I can take care of that. I've forwarded this upstream already. The best
option would be having a fixed libtool available, or trying to use the
backported patch
Hi Carlos!
Am Mittwoch, den 25.11.2009, 17:38 -0500 schrieb Carlos O'Donell:
> The hppa-linux-gnu target now has atomic builtins in gcc, and atomic.h
> functions exported by glibc.
That's really good news!
> What else is needed by openmpi?
IIRC this should be sufficient. I'll check with upstrea
Am Montag, den 23.11.2009, 00:10 +0100 schrieb Francesco Poli:
> is there anyone willing to package VisIt for Debian?
>
> My RFP (see bug #395573) was converted into an ITP, but later was
> converted back into an RFP...
I did not know about that but started packaging it a while ago. The
files are
Am Mittwoch, den 18.11.2009, 07:35 -0600 schrieb Lucas Nussbaum:
> Yeah, but the unconditional --removal-all looks a bit scary :-)
I know. There was discussion about that on the dpkg mailing list, IIRC.
Other packages had similar problems. The recommended solution was to
remove all and let u-a rec
Hi Lucas!
Am Dienstag, den 17.11.2009, 23:38 -0600 schrieb Lucas Nussbaum:
> I'm still not convinced. For example, in preinst, you probably shouldn't
> --remove-all mpirun.
> Attached is a patch that works (apparently). I plan to do something very
> similar in mpich2. Can you review/comment?
Tha
Hi Ben!
Am Mittwoch, den 11.11.2009, 22:34 + schrieb Ben Hutchings:
> Could you test this:
>
> --- a/include/linux/socket.h
> +++ b/include/linux/socket.h
> @@ -16,7 +16,12 @@ struct __kernel_sockaddr_storage {
> /* _SS_MAXSIZE value minus size of ss_family */
>
Am Mittwoch, den 11.11.2009, 09:26 -0700 schrieb dann frazier:
> > Several autoconf-scripts (notably strace) try to compile this program to
> > detect "linux/netlink.h" and consequently fail. Please revert the change
> > that
> > remove the sub-includes from linux/socket.h
I can confirm the bre
Am Mittwoch, den 11.11.2009, 14:13 +0100 schrieb Lucas Nussbaum:
> Let's fix the only really broken thing: the mpiexec/mpirun problem in
> openmpi and mpich2. After that, we can downgrade this bug and discuss
> the rest of it.
I uploaded a fixed package a few minutes ago that uses "mpirun" as
mast
As for the mpi.so thing: Forget about it, confusion on my part. Not a
problem at all.
On Wed, 2009-11-11 at 13:54 +0100, Lucas Nussbaum wrote:
> OK. That's really the first problem I'd like to solve, since it only
> affects OpenMPI and MPICH2. The other problems can be addressed after
> that.
>
>
On Wed, 2009-11-11 at 13:43 +0100, Lucas Nussbaum wrote:
> I would vote for keeping it as is, so we don't need to change LAM and
> mpich. It's not really exposed to users anyway.
I'm fine with that.
Best regards
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
wit
On Tue, 2009-11-10 at 15:29 -0600, Pavan Balaji wrote:
> MPICH2 and Open MPI should have the same priority, isn't it? They are
> just alternative implementations of MPI.
Thought about that too but I am unsure how update-alternatives handles
that case. The man page talks about only taking action if
Hi Lucas!
Am Montag, den 26.10.2009, 09:04 +0100 schrieb Lucas Nussbaum:
> Alternatives:
> - for compilation environment:
> all implementations have a single "mpi" alternative. The master
> controls the link from /usr/include/mpi, and has all the compilers
> wrappers as slaves.
> => That's
Package: mpi-defaults
Severity: normal
Reminder for myself (and others):
As discussed on the Debian Science mailing list, LAM should be made
obsolete in the near future. To ease the transistion, the default MPI
implementation on architectures not supported by Open MPI should be
moved from LAM to
Hi Niko!
Sorry for the late reply! I was offline for a few days and did forget to
mention that before.
Am Sonntag, den 18.10.2009, 21:05 +0300 schrieb Niko Tyni:
> It seems the standard way to go is with Inline::MakeMaker. Here's
> a lightly tested patch that seems to work for me, hope you find
>
Hi Niko,
thanks for your message and the included hints!
Am Donnerstag, den 15.10.2009, 09:05 +0300 schrieb Niko Tyni:
> I suppose a workaround could be to somehow generate dependencies like
> Depends: perl (>= 5.10.1), perl (<< 5.10.2~)
> and require binNMUs every time the perl version changes.
Am Donnerstag, den 15.10.2009, 10:50 +0100 schrieb Alan Woodland:
> Thanks for accepting it! Please feel free to send any bug reports
> relating to this my way, and I'll try to take a look. I have
> subscribed to the PTS, but I'll definitely notice something forwarded
> to my main mailbox :)
Thank
Hi Robert!
Am Mittwoch, den 14.10.2009, 15:37 -0600 schrieb Robert LeBlanc:
> We are finishing up reimaging our cluster and noticed that OpenMPI
> does not have the checkpointing enabled. We tracked down the problem
> to missing BLCR (which is not in Squeeze). I backported it to Lenny,
> and was g
Hi,
I have no idea where exactly the issue comes from, but after rebuilding
an unmodified version and installing the new package on my sid box
findimagedupes works like a charm. If someone could confirm that it
fixes the issue, I'll ask the release team to schedule a rebuild.
Best regards
Manuel
tag 545919 + pending
thanks
Hi Alan,
thanks very much for your patch! I applied it to our SVN repository with
minor modifications. I will upload a new package soon, but need to do
some testing before that.
Am Sonntag, den 13.09.2009, 10:59 +0100 schrieb Alan Woodland:
> The attached patch builds
Hi Giovanni!
Am Dienstag, den 06.10.2009, 21:05 +0200 schrieb Giovanni Mascellani:
> * Package name: mathpiper
[...]
> Description : A Java Computer Algebra System
>
> Mathpiper is part of the matrhrider suite, which is a mathematics computing
^
Hi Harald,
thanks for you bug report!
Am Samstag, den 03.10.2009, 14:51 +0200 schrieb Harald Dunkel:
> The other example using find doesn't work, either:
>
> % find -type f . -print0 | findimagedupes -0 -- -
> find: paths must precede expression: .
> Usage: find [-H] [-L] [-P]
Hi Andreas,
I had the same issue on one of my packages a while back, so I might be
able to give same help here.
Am Dienstag, den 29.09.2009, 22:19 +0200 schrieb Andreas Tille:
> Thanks for the bug report. Unfortunately I do not have access to such a
> machine and I wonder whether you are able to
Am Sonntag, den 27.09.2009, 13:30 +0200 schrieb Moritz Muehlenhoff:
> Can you please forward this upstream? I suppose net...@vger.kernel.org would
> be the best list to contact.
Done.
Best regards,
Manuel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Am Sonntag, den 20.09.2009, 16:32 +0200 schrieb Gaudenz Steinlin:
> I'll write to the upstream author about the nameing conflict.
Thanks for taking care of this!
> The best way to go would be to rename the upstream package. What's the
> purpose of the sinfo binary in the slurm-llnl package? If it
Hi Gaudenz!
As it seems, the executable is named "sinfo", which is already supplied
in the SLURM batch system package (slurm-llnl). Because both packages
are useful on clusters, a Conflicts does not make sense, so renaming
seems to be the best option. I CC'ed Gennaro (slurm-llnl maintainer) so
he
Am Dienstag, den 01.09.2009, 18:53 +0200 schrieb Moritz Muehlenhoff:
> On Sat, Jul 25, 2009 at 01:55:04PM +0200, Bastian Blank wrote:
> > Patches attached:
> > * Fix uio.h
> > * Remove socket.h backward compatibility code.
>
> uio.h has been marked __KERNEL__-only upstream in commit
> 812ed032cdc8
Am Sonntag, den 13.09.2009, 22:35 +0200 schrieb Michael Koch:
> I'm in contact with Manuel (the only uploader) and he is working on a
> new version.
The new version will be uploaded RSN. I hope suring the week, but might
take until the weekend. I guess we can afford to wait this; I don't mind
NMUi
Hi Alan!
Am Donnerstag, den 10.09.2009, 00:33 +0100 schrieb Alan Woodland:
> BLCR is now in main. It would be nice if openmpi were built using this
> where it is available.
>
> I've attached a short patch adding options to configure, and build-depends
Thanks a lot for the patch!
I did think abo
Hi Craig!
Am Dienstag, den 28.07.2009, 17:24 +1000 schrieb Craig Sanders:
> this seems to be a recurring problem.
Unfortunately, it is. I'm going to address this when the Open MPI
transition is finished. We decided to wait for 1.3.2 to migrate to
testing before we do more bug hunting to not affec
Am Mittwoch, den 15.07.2009, 16:04 +0200 schrieb Michael Banck:
> As pdb2pqr is tighlty coupled to apbs and thus pymol, which are already
> maintained by debichem, I think maintaining pdb2pqr in Debichem as well
> would make the most sense. And I would be certainly willing to
> co-maintain it
Tha
Am Mittwoch, den 15.07.2009, 14:58 +0200 schrieb Michael Banck:
> Any news about this?
I will have a look at the new upstream version this weekend, Open MPI
kept me busy. Preliminary packaging is still available in Debian Med,
though I'd prefer putting it in Debian Science or Debichem. Any
prefer
Am Mittwoch, den 24.06.2009, 16:16 +0100 schrieb David Ham:
> libopenmpi1 has been replaced by libopenmpi1.3 rendering
> libparmetis3.1 uninstalable. Rebuilding libparmetis3.1 from source is
> sufficient to update the dependency and fix this bug.
Rebuilds are scheduled by the release team as part
Hi Jeff! Hi Steve!
Thanks for implementing a solution and pushing it upstream!
The last NMU by Steve did not make it into Debian. I'm preparing an
upload at the moment, acknowleding the NMUs and fixing all RC bugs. I'll
upload later tonight or tomorrow.
Thanks again for working on the issue whil
Hi everyone!
On Fri, June 12, 2009 11:10 pm, Jeff Squyres wrote:
> Agreed. We thought that stat() was safe to call in the malloc init
> hook -- it seems to be in most other places, at least.
>
> If there's some other safe way to check that stat() is *not* safe,
> that would be great.
Unfortunate
1 - 100 of 271 matches
Mail list logo