Date: Mon, 9 Aug 2010 16:06:28 +0200
From: andr...@an3as.eu
To: debian-med@lists.debian.org
Subject: Re: Clouds and NG sequencing
For pure educational purpose this might be a reasonable thing to do.
However, if it is rather to do some tie saving by trying to optimise for
speed my
On Tue, Aug 10, 2010 at 03:58:43PM +0530, PRAKHAR gaur wrote:
I do agree that this whole exercise might, turn out to be non-productive, in
terms of a result. But the knowledge I will gain is substantial, so I think
the time spent can be justified.
Sure. That's perfectly fine. I just
tag 558852 + help
thanks
Dear all,
I have problems with controlling how the emboss packages are linked to
libraries.
As you can see in http://bugs.debian.org/558852:
1) Some libraries that should be linked are not. In the bug report there are
some hints on how to iteratively figure out
On Tue, Aug 10, 2010 at 09:58:12PM +0900, Charles Plessy wrote:
I have problems with controlling how the emboss packages are linked to
libraries.
As you can see in http://bugs.debian.org/558852:
I might try to have a look into this but forewarding this problem to
debian-mentors (or
Background to the Question
When VistA is packaged and distributed, the package itself would be
installed on the system, in some location, say /abc/def. There may be
clinics PQR and XYZ that each want to run their own instances of VistA.
They will generally share the standard or common
Dear release team,
the embassy-* packages in testing all have serious bugs because they do not
build from source anymore. The reason is that they are strongly tied to the
emboss package, which version is 6.1 in Squeeze and 6.3 in Sid, and the
embassy-* packages are for 6.2. There are updates
On Wed, Aug 11, 2010 at 08:55:32 +0900, Charles Plessy wrote:
To put the emboss and embassy packages in consistency in Squeeze, here are
possible solutions:
- Remove the embassy-* packages from testing.
- Upload emboss 6.2 to testing-proposed-updates.
- Upgrade embassy-* packages with
7 matches
Mail list logo
