[opensuse-buildservice] Quick question on signing and importing RPMs
Hey, all. Two quick newbie questions. I've read all the documentation I can find, from the wiki pages to the api.opensuse.org docs, and I'm still unsure how to do the following tasks via the build service's web interface: 1. How do I take the GPG key I've created and sign packages with it? I can't tell where it should even be uploaded, much less how I should go about signing said packages via the web interface. 2. How do I take a package from another project and have the build service install it before building my package? I'm thinking specifically of Riggwelter's "giblib" package, which apparently isn't available from the standard repos. I've linked it into to my home project, but even though I have "giblib" and "giblib-devel" in the BuildRequires of my spec, it can't find the rpms to install. Thanks in advance. :) ~~ Andrew D. (andrewd18) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, May 11, 2007 at 09:53:27AM -0500, linuxnoob@wi.rr.com wrote:
Hey, all. Two quick newbie questions. I've read all the documentation I can find, from the wiki pages to the api.opensuse.org docs, and I'm still unsure how to do the following tasks via the build service's web interface:
1. How do I take the GPG key I've created and sign packages with it? I can't tell where it should even be uploaded, much less how I should go about signing said packages via the web interface.
Please don't tell me that you really want to upload your gpg secret-key into the buildservice... Currently, the build service signs all packages with the same key. We plan to implement two other features: 1) add a method to make the buildservice create a secret key for you which is used for signing. 2) add a way so you can re-sign built rpms via the API. This wouldn't be slow because for signing you only need to download the SHA1 sum of the rpm, the full rpm is not really needed.
2. How do I take a package from another project and have the build service install it before building my package? I'm thinking specifically of Riggwelter's "giblib" package, which apparently isn't available from the standard repos. I've linked it into to my home project, but even though I have "giblib" and "giblib-devel" in the BuildRequires of my spec, it can't find the rpms to install.
Linked packages are normally not the right way in that case, because you just link the sources and the build service has to rebuild all of the packages. It's often better to base your own repository on top of other repositories you need. Unfortunately this is a bit hidden in the web interface, you need to select "Advanced" in the "Add Repository" dialog and then select the repository you need. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Michael Schroeder wrote:
Please don't tell me that you really want to upload your gpg secret-key into the buildservice...
Currently, the build service signs all packages with the same key.
If it's signing it for me, it saves me work. Thanks for informing me.
Linked packages are normally not the right way in that case, because you just link the sources and the build service has to rebuild all of the packages. It's often better to base your own repository on top of other repositories you need. Unfortunately this is a bit hidden in the web interface, you need to select "Advanced" in the "Add Repository" dialog and then select the repository you need.
Thank you; I'll poke around there and ask for more info if I get lost. :) ~~ Andrew D. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
linuxnoob＠wi.rr.com -
Michael Schroeder