[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libsnappy (Was: Bug#662513: RM: emboss/6.3.1-6)



Hi Andreas and Olivier,

Le Mon, Mar 05, 2012 at 03:08:39PM +0100, Andreas Tille a écrit :
> 
> Strange my clone builds perfectly with git-buildpackage as well as a
> freshly created one using
> 
>    git clone git+ssh://tille@git.debian.org/git/users/plessy/snappy-java.git

First, I confirm that the package builds well in a chroot (but not on my dirty
machine).

> In my last mail about this[1] I mentioned my upload to
> 
>    http://lists.debian.org/debian-med/2012/02/msg00005.html
> 
> I would regard a test whether it works with your final target
> picard-tools as a useful precondition for a final upload.  Could you
> please confirm that it works as expected?  If yes, just tell me how to
> proceed.  I'm pretty proud about my ability to break Git archives and
> injecting a *changed* upstream source into an existing repository with
> an existing pristine-tar seems like even less gifted people than me
> could succeed in breaking it.  Because the package in in a private
> Git archive of yours anyway (is this correct or are there other clones
> hanging around??) we have the following options:
> 
>    1. Create a fresh Git archive (in Debian Med) with the *changed*
>       upstream tarball?
>    2. Inject the packaging into SVN

I am neutral for the final location and container for the package.  But maybe
it would be best to have it in pkg-java (Git or Svn).  Moving the Git package
is the easiest, but using svn-inject is trivial.

Because there is something broken with Java building on my computer I could not
check picard-tools yet, but I will try on another computer later.

However, the main problem with snappy-java is not yet solved: it contains a
convenience binary object for the “Snappy” C library, which means it is not
free as it is.  One possibility is to simply paste the source somewhere, but
that is bad practice as it increases workload in case a bug is found is Snappy,
and the other solution is to make libsnappy-java use Debian's snappy C library,
which requires knowing about “JNI” and other things.

This is where I would need help again.

Cheers

-- 
Charles


Reply to: