Re: [benjamin.redelings@gmail.com: Bug#968739: igv will not run]
I created a "Java" tab on our spreadsheet. Would of course be great if
that sees some momentum. Took the freedom to also add Cytoscape. And if
I get this right, then also nextflow qualifies, which because of
"capsule" seems kind of stuck.
Best,
Steffen
On 24.08.20 21:58, Pierre Gruet wrote:
> Hi Andreas,
>
> Le 24/08/2020 à 12:39, Andreas Tille a écrit :
>> Hi Pierre,
>>
>> On Mon, Aug 24, 2020 at 12:08:28PM +0200, Pierre Gruet wrote:
>>> Contrarily to what I wrote a few days ago, I do not think we are ready
>>> to remove all included jars in igv.
>>> For instance we would have to package libgoby-java, I have just made
>>> some packaging effort on its new upstream version [0] after Andreas
>>> began but, as Olivier noticed before on a previous upstream version [1],
>>> there are still many jars missing in Debian.
>>>
>>> We would also need to have the huge Amazon AWS SDK packaged...
>> Well, I never claimed it will be an easy task. ;-)
>>
> True :-D Only I underestimated this.
>
>>
>>> I will thus work on #968739 and on the new upstream version but I am
>>> afraid we will have to keep igv in non-free for the moment :-(
>> Yep. Better have a working one in non-free than only a non-working one.
>>
> In fact, looking more closely at it, upstream has stopped bundling
> useful jars after version 2.6.3 (last upstream version is 2.8.10,
> current Debian-packaged one is 2.4.17). We currently do not have the
> right libs in Debian to package a version after v2.6.3.
> I think I will thus go back to v2.6.3 and package it, it will still be a
> progress, it is just 1 year old, and it will lead to a working package,
> still in non-free.
> Medium-term work should then allow to get the right dependencies
> packaged and hopefully to handle the last upstream version.
>
>>> All the best,
>> Same to you
>>
>> Andreas.
>>
>>
> Best regards,
> Pierre
>
Reply to: