On Fri, Dec 05, 2014 at 10:37:39AM +0800, Paul Wise wrote:
On Thu, Dec 4, 2014 at 11:16 PM, Corentin Desfarges wrote:
The file is just used by one of the unit tests. But there are more than 20
unit tests which need their own specific data to work.
Personally I'm now leaning towards you
Hi
With the authorization of the responsibles of the project, I published the
file here [2]
It contains the names of one patient and his birth date so that
probably wasn't a good idea. This file appears to contain CT scan
results in a custom format? I can't view the scan itself as the
On Thu, Dec 4, 2014 at 10:17 PM, Corentin Desfarges wrote:
It's not about a real patient...
So I don't think that there is any problem of confidentiality in this case.
Fair enough.
I guess that this new orig.tar.gz would be created by using uscan (if the
link is added in d/watch) ?
Uscan
Hi
Can you link to the file we are talking about?
With the authorization of the responsibles of the project, I published the file
here [2]
[2]http://goo.gl/53sAzM
this looks a bit weird. I guess this google thing allows you to inspect the
content of zip files?
Yes indeed. I simply
I guess that this new orig.tar.gz would be created by using uscan (if the
link is added in d/watch) ?
Uscan requires the file to be on a webserver somewhere. I think you
would just create it manually using this:
tar Jcf fw4spl_0.1.orig-testdata.tar.xz md_1.jsonz
Then add a
On Thu, Dec 4, 2014 at 11:16 PM, Corentin Desfarges wrote:
The file is just used by one of the unit tests. But there are more than 20
unit tests which need their own specific data to work.
Ok, that makes this a bit more complicated, especially since the
amount of data could grow over time.
Hi and thank you for your answer
I'm working on the packaging of fw4spl (a medical software), and I'm faced
with a new problematic : One of the unit tests needs to load an important
data file, which has a big size (~200 Mo).
I assume you mean 200MB here.
Yes, I do.
Should I simply remove
On Tue, Dec 02, 2014 at 11:12:35AM +0100, Corentin Desfarges wrote:
What license is the file under?
It hasn't any license.
Then it's license is the default all rights reserved, you can't redistribute
it, you can't change it, you can't do anything, and you can't use it without
explicit
Then it's license is the default all rights reserved, you can't redistribute
it, you can't change it, you can't do anything, and you can't use it without
explicit permission from it's copyright holder.
Of course you can't upload it to the debian archive (see DFSG).
Please check better, given
On Tue, Dec 2, 2014 at 6:12 PM, Corentin Desfarges wrote:
It is a .jsonz file.
I assume that is a gzip compressed JSON file.
Actually the file isn't into the source package. I've the choice, and it's
why I would use the best practice.
Please keep it separate then, it is better for Debian to
I don't know enough about the software and the file we are talking
about to answer that.
The software (fw4spl) is a framework focused on processing and visualization
of medical images.
Here, the repository of the project : [1]
Can you link to the file we are talking about?
With the
Hi,
Quoting Corentin Desfarges (2014-12-02 17:29:12)
Can you link to the file we are talking about?
With the authorization of the responsibles of the project, I published the
file here [2]
[2] http://goo.gl/53sAzM
this looks a bit weird. I guess this google thing allows you to inspect the
On Wed, Dec 3, 2014 at 12:29 AM, Corentin Desfarges wrote:
With the authorization of the responsibles of the project, I published the
file here [2]
It contains the names of one patient and his birth date so that
probably wasn't a good idea. This file appears to contain CT scan
results in a
Dear Mentors,
I'm working on the packaging of fw4spl (a medical software), and I'm faced
with a new problematic : One of the unit tests needs to load an important
data file, which has a big size (~200 Mo).
Should I simply remove this test, or can I include the data file in the
package ?
Thank
On Mon, Dec 1, 2014 at 10:01 PM, Corentin Desfarges wrote:
I'm working on the packaging of fw4spl (a medical software), and I'm faced
with a new problematic : One of the unit tests needs to load an important
data file, which has a big size (~200 Mo).
I assume you mean 200MB here.
Should I
Hi,
Quoting Paul Wise (2014-12-01 17:03:39)
Should I simply remove this test, or can I include the data file in the
package ?
Can you include more details about this data file?
What data format is the file in?
depending on the answer to this question it might be very simple to compress
Le lundi 01 décembre 2014 à 17:28 +0100, Johannes Schauer a écrit :
Hi,
Quoting Paul Wise (2014-12-01 17:03:39)
Should I simply remove this test, or can I include the data file in the
package ?
Can you include more details about this data file?
What data format is the file in?
17 matches
Mail list logo
