On Fri, Jan 23, 2015 at 05:48:29AM +0000, Potter, Tim (Cloud Services) wrote: > Hi everyone. I’ve finally beat the packaging bug I had for the latest > version of jffi. Just wondering what to do with it next - should I > just splat it on top of the existing jffi version (1.0.2 - very old). > The jffi package is a dependency for a handful of jnr-* packages > required by the latest JRuby. > > I’ve uploaded the new packaging as jffi-1.2.7 to the pkg-java > repository: > > http://anonscm.debian.org/cgit/pkg-java/jffi-1.2.7.git/ > > There’s also a jffi-1.2.6 version which hasn’t been packaged properly > and is nearly two years old. Can we delete that at some stage?
Hi Tim, In terms of the packaging repo, there's no reason not to use the existing jffi repo [1]. All of the packaging history is there and intact as tags for both the debian and upstream versions. If you'd like a review of the packaging before the import, I'll be happy to do that. Then we can git-import-dsc your package into jffi.git (or get fancy if you'd like to preserve individual commits from your workflow on 1.2.7) and upload to experimental. Looking at /git/pkg-java/, jffi is definitely well-represented: tmarble-guest Mar 18 2013 jffi-1.2.6.git tpot-guest Jan 23 01:43 jffi-1.2.7.git twerner Mar 18 2013 jffi.git tpot-guest Nov 26 05:38 jnr-jffi.git It looks like we can drop at least jnr-jffi.git and jffi-1.2.7.git once we've merged into jffi.git. (And unless Tom yells, we can drop jffi-1.2.6 too.) Cheers, tony
signature.asc
Description: Digital signature
