On Thu, Jun 9, 2016 at 8:50 PM, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > On Thu, Jun 9, 2016 at 4:29 PM, Noah Watkins <noahwatkins@xxxxxxxxx> wrote: >> I'm trying to track down why the Java Debian packages are not showing >> up in the Jewel repository: >> >> Looking in the repository for jewel I see the JNI bindings deb: >> >> http://download.ceph.com/debian-jewel/pool/main/c/ceph/ >> libcephfs-jni_10.2.1-1trusty_amd64.deb 13-May-2016 23:53 20368086 >> >> but not the deb file containing the Java bits (libcephfs-java). > > Hmm, that's the official release packages, which I think aren't > produced using all the same stuff as the gitbuilders. Does > libcephfs-java get built the same way as the JNI bindings? I know we > have a separate gitbuilder for Hadoop JARs... The release packages are not produced using the same process as gitbuilders. This is an example output of Trusty building Jewel: https://jenkins.ceph.com/job/ceph-build/ARCH=x86_64,DIST=trusty,MACHINE_SIZE=huge/133/consoleFull At the end of the build, the process looks for files in: `release/$VERSION` which in the previous case would be `release/10.2.2` All binaries are placed there and that is what ends up being consumed. This is the actual file that builds debs for upstream releases: https://github.com/ceph/ceph-build/blob/master/ceph-build/build/build_deb The part that actually calls pbuilder to produce the binaries and then copy them to our centralized binary store is: https://github.com/ceph/ceph-build/blob/master/ceph-build/build/build_deb#L165-L194 > > -Greg > >> However, it looks like the gitbuilder is producing them: >> >> http://gitbuilder.ceph.com/ceph-deb-trusty-x86_64-basic/ref/jewel/pool/main/c/ceph/ >> ===> libcephfs-java_10.2.1-135-g50143ed-1trusty_all.deb2016-06-09 15:191.0M >> libcephfs-jni_10.2.1-135-g50143ed-1trusty_amd64.deb2016-06-09 15:1919M >> >> I grepped around the autobuilders and don't see any special cases for >> Java. Any clues? >> >> Thanks, >> Noah >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
