Help needed with updating some Java libraries (netlib-java, libmtj-java)

Olivier Sallou olivier.sallou at irisa.fr
Fri Aug 29 07:21:46 UTC 2014


On 08/29/2014 08:22 AM, Olivier Sallou wrote:
> On 08/29/2014 02:38 AM, tony mancill wrote:
>> On 08/28/2014 07:01 AM, Andreas Tille wrote:
>>> Hi,
>>>
>>> when checking my Maintainer dashboard dashboard I realised that the
>>> watch file of netlib-java and libmtj-java became disfunctional and when
>>> tracking down the issue I noticed that both projects moved from SF to
>>> Github.  While I updated the URLs in SVN accordingly I noticed that the
>>> Build system has changed as well which just crosses my (low) level of
>>> Java competence (again).
>>>
>>> Since both packages are definitely not really in the field of Debian Med
>>> but just preconditions for some biological package (beast) I wonder
>>> whether this might be the right point in time to move the package to
>>> Debian Java.  I'd volunteer to inject the package into Debian Java Git
>>> but in turn I would need some help (starting with netlib-java).  I have
>>> the feeling that the amount of work for a skilled Java packager is low
>>> (but I really would not regard myself as such a person).
>>>
>>> BTW, the packages are hanging around in contrib since netlib depends
>>> from f2j (at least the current version).  I'll send a separate mail to
>>> f2j authors to try (again) to convince them to use a DFSG free license.
>>>
>>> Kind regards
>>>
>>>         Andreas.
>>>
>> Hello Andreas,
>>
>> If you're willing to migrate these to the pkg-java repo, I'll work on
>> updating them and uploading them as Java Team packages.
>>
>> Also, I've been meaning to send you a mail regarding libsnappy-java,
>> since we have an RC bug there.  

I have sent a patch to fix the bug on loading native library. However
this raises an other issue, it seems that Java lib is not matching
native lib on methods.
I have put details in the bug.

Olivier

>> The last commit makes it appear that you
>> were considering moving it debian-med in 2012.  Is that still the case?
> We have a libsnappy-java version available in DebianMed [0], but a
> specific release (certainly due to a package which needed this specific
> release and upstream broke its API).
> I do not know if we need to manage snappy by itself in DebianMed repo as
> it has nothing related to bio/med but is only a dependency.
>
> [0] https://packages.qa.debian.org/s/snappy1.0.3-java.html
>
> Olivier
>> Cheers,
>> tony
>>

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438




More information about the pkg-java-maintainers mailing list