Hi,
I am new and trying local build on s390x with SLE_12_SP3 using the following command
sudo osc build
but I get the public key not available for many packages. You can see the output by clicking the following link
I know that I can use --noverify option to bypass this and builds complete successfully when I use --noverify option but how can I fix this? What will happen if I don't fix it?
-- Usman
Hi,
Usman Haider schrieb:
I am new and trying local build on s390x with SLE_12_SP3 using the following command
sudo osc build
but I get the public key not available for many packages. You can see the output by clicking the following link
Same for SP4 and SLES15, see my mail from some days ago: https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00045.html
Johannes Kastl schrieb:
Hi,
Usman Haider schrieb:
I am new and trying local build on s390x with SLE_12_SP3 using the following command
sudo osc build
but I get the public key not available for many packages. You can see the output by clicking the following link
Same for SP4 and SLES15, see my mail from some days ago: https://lists.opensuse.org/opensuse-buildservice/2018-06/msg00045.html
I still get the error for SLES12_SP3, SLES12_SP4 and SLES15 when building locally...
Kind Regards, Johannes
On Apr 08 2019, Johannes Kastl kastl@b1-systems.de wrote:
I still get the error for SLES12_SP3, SLES12_SP4 and SLES15 when building locally...
You need to import the SuSE Package Signing Key into your rpm database.
Andreas.
Hi Andreas,
Andreas Schwab schrieb:
On Apr 08 2019, Johannes Kastl kastl@b1-systems.de wrote:
I still get the error for SLES12_SP3, SLES12_SP4 and SLES15 when building locally...
You need to import the SuSE Package Signing Key into your rpm database.
I thought that last time this was discussed the outcome was that this needs to be adapted on the Buildservice.
Kind Regards, Johannes
Johannes Kastl schrieb:
Hi Andreas,
Andreas Schwab schrieb:
You need to import the SuSE Package Signing Key into your rpm database.
I thought that last time this was discussed the outcome was that this needs to be adapted on the Buildservice.
In addition, I imported the gpg-key found in .../packagecache/SUSE:SLE-12-SP4:GA/_pubkey into the rpm database, but still "no public key available"...
Johannes
Am 10.04.19 um 20:38 schrieb Johannes Kastl:
Johannes Kastl schrieb:
Andreas Schwab schrieb:
You need to import the SuSE Package Signing Key into your rpm database.
I thought that last time this was discussed the outcome was that this needs to be adapted on the Buildservice.
In addition, I imported the gpg-key found in .../packagecache/SUSE:SLE-12-SP4:GA/_pubkey into the rpm database, but still "no public key available"...
Same holds true for SLES15:SP1 and Leap 15.1...
Johannes
Am 06.06.19 um 11:18 schrieb Johannes Kastl:
Am 10.04.19 um 20:38 schrieb Johannes Kastl:
Johannes Kastl schrieb:
I thought that last time this was discussed the outcome was that this needs to be adapted on the Buildservice.
In addition, I imported the gpg-key found in .../packagecache/SUSE:SLE-12-SP4:GA/_pubkey into the rpm database, but still "no public key available"...
Same holds true for SLES15:SP1 and Leap 15.1...
SLES12 SP3: still no key SLES12 SP4: still no key SLES15 SP0: working SLES15 SP1: working
Johannes
On Montag, 25. November 2019, 09:55:12 CET Johannes Kastl wrote:
Am 06.06.19 um 11:18 schrieb Johannes Kastl:
Am 10.04.19 um 20:38 schrieb Johannes Kastl:
Johannes Kastl schrieb:
I thought that last time this was discussed the outcome was that this needs to be adapted on the Buildservice.
right.
In addition, I imported the gpg-key found in .../packagecache/SUSE:SLE-12-SP4:GA/_pubkey into the rpm database, but still "no public key available"...
Same holds true for SLES15:SP1 and Leap 15.1...
SLES12 SP3: still no key SLES12 SP4: still no key
I have set now the right gpg keys for SLE 12 projects.
Sorry, just as a background, this must be done manually when setting up a new SP project in OBS. And you don't notice this missing when doing KVM builds (like the server does) on your local build. Since trust checking is disabled there (because the VM protects you).
Am 27.11.19 um 09:27 schrieb Adrian Schröter:
I have set now the right gpg keys for SLE 12 projects.
Sorry, just as a background, this must be done manually when setting up a new SP project in OBS. And you don't notice this missing when doing KVM builds (like the server does) on your local build. Since trust checking is disabled there (because the VM protects you).
Thanks Adrian!
Works for me for SLES12 SP3 and SP4, both x86_64.
Johannes
buildservice@lists.opensuse.org
-
Adrian Schröter -
Andreas Schwab -
Johannes Kastl -
Usman Haider