Ok well I'm able to post artifacts however this still requires posting my private key to bintray to have it signed.
I don't see how this is a viable solution since this requires us to post our private keys to this service. You mentioned there is a way to simply post our existing directories, maybe that's what we should do... On Thu, Jan 15, 2015 at 8:00 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > And an update! > > "Signing via API with transient key/pass just went live. You need to call > the metadata calculation API for a (deb) repo, passing the subject to sign > with, and api key and an optional passphrase, as described here." > > Lemme know how it works! > > A. > > On Thu, Jan 15, 2015 at 7:00 AM, Andrew Bayer <andrew.ba...@gmail.com> > wrote: >> >> Sorry for not emailing - JFrog is investigating the work involved in >> getting users able to sign organization Debian repository metadata. I'll >> ping them for an update. >> >> A. >> >> >> On Thursday, January 15, 2015, Jake Luciani <j...@apache.org> wrote: >>> >>> Any update? >>> >>> On Fri, Jan 9, 2015 at 12:53 PM, Andrew Bayer <andrew.ba...@gmail.com> >>> wrote: >>> > I'm investigating this now - will update when I have more information. >>> > >>> > A. >>> > >>> > On Fri, Jan 9, 2015 at 7:54 AM, Jake Luciani <j...@apache.org> wrote: >>> > >>> >> The docs seems to indicate signing happens at the organization level >>> >> >>> >> >>> >> >>> >> https://bintray.com/docs/usermanual/interacting/interacting_gpgsigningforbintrayorganizations.html >>> >> >>> >> Am I able to sign artifacts with my user GPG? I'm not sure if >>> >> everyone is comfortable uploading their private gpg key to bintray. >>> >> >>> >> On Wed, Jan 7, 2015 at 1:40 PM, Andrew Bayer <andrew.ba...@gmail.com> >>> >> wrote: >>> >> > See https://bintray.com/docs/api/#_debian_upload for how to >>> >> > upload/sign >>> >> > artifacts with the Bintray API. Your release managers will need to >>> >> > get >>> >> > accounts on Bintray and then open INFRA tickets to get added to the >>> >> > Cassandra team in the Apache org there, at which point you'll have >>> >> > full >>> >> > admin rights over the cassandra repo there. If you want to start >>> >> > playing >>> >> > with it, go ahead and create an account and let me know the username >>> >> > so I >>> >> > can invite/add you. >>> >> > >>> >> > reprepro isn't relevant here - the Bintray Debian repos don't >>> >> > support the >>> >> > full range of reprepro's functionality by a long shot, but for what >>> >> you're >>> >> > doing, I don't think you need anything that's not available through >>> >> > the >>> >> > Bintray API. Alternatively, if that turns out to not work for you, >>> >> > you >>> >> can >>> >> > use a generic repo that allows you to just upload files/directories, >>> >> > so >>> >> you >>> >> > could keep doing what you're doing now but upload to Bintray rather >>> >> > than >>> >> > dist. >>> >> > >>> >> > Others on the Infra team will know for sure, but I'm pretty >>> >> > confident >>> >> that a >>> >> > redirect from dist to bintray is feasible. >>> >> > >>> >> > A. >>> >> > >>> >> > On Wed, Jan 7, 2015 at 10:17 AM, Jake Luciani <j...@apache.org> >>> >> > wrote: >>> >> >> >>> >> >> We have a distr per minor version. You can see them here (we only >>> >> >> currently use the last 3 major releases 21x, 20x and 12x) you can >>> >> >> see >>> >> them >>> >> >> here >>> >> >> https://dist.apache.org/repos/dist/release/cassandra/debian/dists/ >>> >> >> >>> >> >> The release managers have a local repo with our reprepro settings. >>> >> >> We >>> >> >> deploy the artifact and export locally then copy the whole thing >>> >> >> over >>> >> to the >>> >> >> apache dist server. >>> >> >> Here is the relevant section of the release script >>> >> >> >>> >> >>> >> https://github.com/tjake/cassandra-release/blob/master/finish_release.sh#L161 >>> >> >> >>> >> >> As our wiki shows, users add the maintainer keys and the specific >>> >> >> dist >>> >> >> they want >>> >> >> https://wiki.apache.org/cassandra/DebianPackaging >>> >> >> >>> >> >> Ideally, we can redirect the existing location to the new one but >>> >> >> I'm >>> >> not >>> >> >> sure if that's possible. >>> >> >> >>> >> >> How can we replicate this setup with bintray? >>> >> >> >>> >> >> -Jake >>> >> >> >>> >> >> >>> >> >> On Wed, Jan 7, 2015 at 12:41 PM, Andrew Bayer >>> >> >> <andrew.ba...@gmail.com> >>> >> >> wrote: >>> >> >>> >>> >> >>> Great! So to start, can you give us a sense of what your needs for >>> >> >>> the >>> >> >>> repo are? What are you putting in it? Are you splitting it up by >>> >> distro at >>> >> >>> all or just putting new versions of Cassandra in each time? >>> >> >>> >>> >> >>> A. >>> >> >>> >>> >> >>> On Wed, Jan 7, 2015 at 7:15 AM, Jake Luciani <j...@apache.org> >>> >> >>> wrote: >>> >> >>>> >>> >> >>>> Hi Andrew, >>> >> >>>> >>> >> >>>> I'm happy to help. >>> >> >>>> >>> >> >>>> -Jake >>> >> >>>> >>> >> >>>> On Tue, Jan 6, 2015 at 2:19 PM, Andrew Bayer <aba...@apache.org> >>> >> wrote: >>> >> >>>>> >>> >> >>>>> Hi Cassandra team - >>> >> >>>>> >>> >> >>>>> So as you're probably aware, the Cassandra Debian packages >>> >> >>>>> currently >>> >> on >>> >> >>>>> dist need to be moved off there. The Infra team has been working >>> >> >>>>> on a >>> >> >>>>> solution for that - we've got an organization for ASF on >>> >> >>>>> bintray.com >>> >> , >>> >> >>>>> which >>> >> >>>>> can store and serve Debian repositories. We'd like to work with >>> >> >>>>> you >>> >> all >>> >> >>>>> on >>> >> >>>>> moving the existing packages over to bintray, and figuring out >>> >> >>>>> what >>> >> >>>>> needs >>> >> >>>>> to be done to get a working process for you to post new Debian >>> >> packages >>> >> >>>>> going forward. Could someone from Cassandra (or some set of >>> >> >>>>> someones) >>> >> >>>>> be >>> >> >>>>> available to work with us on this? Thanks! >>> >> >>>>> >>> >> >>>>> A. >>> >> >>>> >>> >> >>>> >>> >> >>> >>> >> >> >>> >> > >>> >> > >
