[opensuse-buildservice] Unable to build Fedora 31 64 bit packages locally
I am able to build 64 bit Wine packages for Fedora 31 on https://build.opensuse.org/package/show/Emulators:Wine:Fedora/wine-devel, but when I try to build them locally it fails with: Verifying integrity of cached packages using keys from Fedora:31 warning: /var/tmp/osbuild-packagecache/Fedora:31/standard/x86_64/acl-2.2.53-4.fc31.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 3c3359c4: NOKEY /var/tmp/osbuild-packagecache/Fedora:31/standard/x86_64/acl-2.2.53-4.fc31.x86_64.rpm : public key not available The last line is repeated for multiple packages. I can get past that by adding --no-verify to the command, but then the build fails with [1/68] preinstalling filesystem... [ 1s] bsdtar: Error opening archive: Unrecognized archive format [ 1s] [2/68] preinstalling libgcc... [ 1s] bsdtar: Error opening archive: Unrecognized archive format with the bsdtar error repeated for multiple packages. I am able to build Fedora 30 packages both locally and on the OBS using the same spec file. -- Rosanne DiMesio <dimesio@gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, Nov 24, 2019 at 6:56 PM Rosanne DiMesio <dimesio@gmail.com> wrote:
I am able to build 64 bit Wine packages for Fedora 31 on https://build.opensuse.org/package/show/Emulators:Wine:Fedora/wine-devel, but when I try to build them locally it fails with:
Verifying integrity of cached packages using keys from Fedora:31 warning: /var/tmp/osbuild-packagecache/Fedora:31/standard/x86_64/acl-2.2.53-4.fc31.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 3c3359c4: NOKEY /var/tmp/osbuild-packagecache/Fedora:31/standard/x86_64/acl-2.2.53-4.fc31.x86_64.rpm : public key not available
The last line is repeated for multiple packages.
I can get past that by adding --no-verify to the command, but then the build fails with
[1/68] preinstalling filesystem... [ 1s] bsdtar: Error opening archive: Unrecognized archive format [ 1s] [2/68] preinstalling libgcc... [ 1s] bsdtar: Error opening archive: Unrecognized archive format
with the bsdtar error repeated for multiple packages.
I am able to build Fedora 30 packages both locally and on the OBS using the same spec file.
You need obs-build >= 20190923 with zstd installed. Otherwise Fedora 31+ will fail, as they switched to zstd compression: https://fedoraproject.org/wiki/Changes/Switch_RPMs_to_zstd_compression -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, 24 Nov 2019 19:59:12 -0500 Neal Gompa <ngompa13@gmail.com> wrote:
You need obs-build >= 20190923 with zstd installed. Otherwise Fedora 31+ will fail, as they switched to zstd compression: https://fedoraproject.org/wiki/Changes/Switch_RPMs_to_zstd_compression
My local system is openSUSE Leap 15. There is no "obs-build" package for it, and AFAICT from https://software.opensuse.org/package/obs-build, that package is only available for non-openSUSE systems. What package do I need to upgrade on openSUSE? -- Rosanne DiMesio <dimesio@gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, Nov 24, 2019 at 9:46 PM Rosanne DiMesio <dimesio@gmail.com> wrote:
On Sun, 24 Nov 2019 19:59:12 -0500 Neal Gompa <ngompa13@gmail.com> wrote:
You need obs-build >= 20190923 with zstd installed. Otherwise Fedora 31+ will fail, as they switched to zstd compression: https://fedoraproject.org/wiki/Changes/Switch_RPMs_to_zstd_compression
My local system is openSUSE Leap 15. There is no "obs-build" package for it, and AFAICT from https://software.opensuse.org/package/obs-build, that package is only available for non-openSUSE systems. What package do I need to upgrade on openSUSE?
On openSUSE systems, the obs-build software is packaged as "build". You can get up to date versions from the openSUSE:Tools repository. Just as an FYI, Fedora systems name the package "obs-build" and do have the updated software[1][2]. [1]: Fedora 31: https://bodhi.fedoraproject.org/updates/FEDORA-2019-26fbf80b9e [2]: Fedora 30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-6ac9a4ad2c -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, 24 Nov 2019 21:50:55 -0500 Neal Gompa <ngompa13@gmail.com> wrote:
On openSUSE systems, the obs-build software is packaged as "build". You can get up to date versions from the openSUSE:Tools repository.
Thank you! That fixed the bsdtar error and the package built. I still had to do --no-verify, though, to get past the no public key issue. Any idea why? It doesn't happen with Fedora 30. -- Rosanne DiMesio <dimesio@gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, Nov 24, 2019 at 10:57 PM Rosanne DiMesio <dimesio@gmail.com> wrote:
On Sun, 24 Nov 2019 21:50:55 -0500 Neal Gompa <ngompa13@gmail.com> wrote:
On openSUSE systems, the obs-build software is packaged as "build". You can get up to date versions from the openSUSE:Tools repository.
Thank you! That fixed the bsdtar error and the package built. I still had to do --no-verify, though, to get past the no public key issue. Any idea why? It doesn't happen with Fedora 30.
Not sure. For me, I've always had to use --no-verify with everything but openSUSE and CentOS targets. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 25.11.19 um 04:58 schrieb Neal Gompa:
On Sun, Nov 24, 2019 at 10:57 PM Rosanne DiMesio <dimesio@gmail.com> wrote:
Thank you! That fixed the bsdtar error and the package built. I still had to do --no-verify, though, to get past the no public key issue. Any idea why? It doesn't happen with Fedora 30.
Not sure. For me, I've always had to use --no-verify with everything but openSUSE and CentOS targets.
This has been on the lists multiple times, and most of the time the answer is that this needs to be fixed inside the build.opensuse.org OBS. Adding Adrian to help out here... Other answers regarding "Import the pubkey into your local rpm database" did not work for me. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Montag, 25. November 2019, 09:42:28 CET Johannes Kastl wrote:
Am 25.11.19 um 04:58 schrieb Neal Gompa:
On Sun, Nov 24, 2019 at 10:57 PM Rosanne DiMesio <dimesio@gmail.com> wrote:
Thank you! That fixed the bsdtar error and the package built. I still had to do --no-verify, though, to get past the no public key issue. Any idea why? It doesn't happen with Fedora 30.
Not sure. For me, I've always had to use --no-verify with everything but openSUSE and CentOS targets.
This has been on the lists multiple times, and most of the time the answer is that this needs to be fixed inside the build.opensuse.org OBS.
Adding Adrian to help out here...
Other answers regarding "Import the pubkey into your local rpm database" did not work for me.
hm, it should actually. However, I have also update the latest fedora gpg keys. -- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Adrian Schröter -
Johannes Kastl -
Neal Gompa -
Rosanne DiMesio