error: linux-pf-headers-skylake: signature is invalid

j1simon · 2019-10-05 12:13:13

I've added the unofficial user repository to install linux-pf kernel (https://wiki.archlinux.org/index.php/Un … um_kernels) but even though I imported the key correctly pacman shows error:

$ sudo pacman -S linux-pf-headers-skylake linux-pf-skylake   
...
debug: found cached pkg: /var/cache/pacman/pkg/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz
debug: sig data: iQEVAwUAXZg4mpXDV9KvXaidAQgv9wf9Hn5s/y6JBZp5kvSSG0DanfWNjGCoS6TMv4zaeMjJtZ/h+7yMTO73nJW1vtLqd69giiKv/cYGhgozWJIvfZeui4XnV7VU1COht6rXp5J775H7e5MmLHfDcR/28VP5rtb5i96aJg1RaTXuOP4nHiuNfOO4uqxlTerA4De3eMEFOAC5AqYSJ8sLrIJD45fy03Y7cu0V15bgyprqYkMR+lLXjgrXNKjdVT9m9srvQdHGhOFHZCTH6Ks4anEdYB0jM7R54GpTkSPy1odwqlWh5bTtcHdQZzuxT7Eh6XKC+uTXdYtfgYIRpCCySTOW3lCshAnUM5Bmi4grrsEoV/8EPQh/Vw==
debug: checking signature for /var/cache/pacman/pkg/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz
debug: 1 signatures returned
debug: fingerprint: 95C357D2AF5DA89D
debug: summary: red
debug: status: Bad signature
debug: timestamp: 0
debug: exp_timestamp: 0
debug: validity: unknown; reason: Success
debug: key: 4485C776B5F543DFE384EAC895C357D2AF5DA89D, home:post-factum OBS Project <home:post-factum@build.opensuse.org>, owner_trust unknown, disabled 0
debug: signature is not valid
error: linux-pf-headers-skylake: signature from "home:post-factum OBS Project <home:post-factum@build.opensuse.org>" is invalid
:: File /var/cache/pacman/pkg/linux-pf-headers-skylake-5.3.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
...

The key importation was succesful:

$ sudo pacman-key --recv-keys 95C357D2AF5DA89D                         ~
gpg: key 95C357D2AF5DA89D: 2 signatures not checked due to missing keys
gpg: key 95C357D2AF5DA89D: "home:post-factum OBS Project <home:post-factum@build.opensuse.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
==> Updating trust database...
gpg: next trustdb check due at 2019-10-12

$ sudo pacman-key --lsign 95C357D2AF5DA89D                             ~
  -> Locally signing key 95C357D2AF5DA89D...
==> Updating trust database...
gpg: next trustdb check due at 2019-10-12

$ sudo pacman-key --list-sigs 95C357D2AF5DA89D                                                                         ~
pub   rsa2048 2013-11-18 [SC] [expires: 2020-06-03]
      4485C776B5F543DFE384EAC895C357D2AF5DA89D
uid           [  full  ] home:post-factum OBS Project <home:post-factum@build.opensuse.org>
sig 3        95C357D2AF5DA89D 2018-03-26  home:post-factum OBS Project <home:post-factum@build.opensuse.org>
sig 3        3B3011B76B9D6523 2013-11-18  [User ID not found]
sig   L      0978BAF132617BA7 2019-10-05  Pacman Keyring Master Key <pacman@localhost>
sig          B709B2E679CB83D9 2019-03-28  [User ID not found]

What am I doing wrong?

Scimmia · 2019-10-05 15:01:07

j1simon wrote:

What am I doing wrong?

You're not, it looks like the sigs are bad.

post-factum · 2019-10-05 17:10:35

https://github.com/openSUSE/open-build- … ssues/4174

j1simon · 2019-10-05 18:02:49

post-factum wrote:

https://github.com/openSUSE/open-build- … ssues/4174

So what's the solution?

post-factum · 2019-10-05 18:44:55

j1simon wrote:

post-factum wrote:
https://github.com/openSUSE/open-build- … ssues/4174
So what's the solution?

I'm not aware of any except "SigLevel = Never" workaround.

Let me know if you manage to fix it properly.

j1simon · 2019-10-05 19:09:35

post-factum wrote:

j1simon wrote:
post-factum wrote:
https://github.com/openSUSE/open-build- … ssues/4174
So what's the solution?
I'm not aware of any except "SigLevel = Never" workaround.
Let me know if you manage to fix it properly.

That doesn't work:

$ cat /etc/pacman.conf
....
[home_post-factum_kernels_Arch]
SigLevel = Never
Server = https://download.opensuse.org/repositories/home:/post-factum:/kernels/Arch/$arch

$ sudo pacman -S linux-pf-skylake
...
Initializing download: https://download.opensuse.org/repositories/home:/post-factum:/kernels/Arch/x86_64/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz
File size: 81442288 bytes
Opening output file /var/cache/pacman/pkg/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz.part
Starting download

Connection 0 finished                                                           

Downloaded 77.6694 Megabyte(s) in 1 second(s). (55599.86 KB/s)
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
:: File /var/cache/pacman/pkg/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (checksum)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (checksum))
Errors occurred, no packages were upgraded.

WorMzy · 2019-10-05 20:26:02

Mod note: Moving to AUR Issues.

post-factum · 2019-10-05 21:09:16

j1simon wrote:

That doesn't work:

$ cat /etc/pacman.conf
....
[home_post-factum_kernels_Arch]
SigLevel = Never
Server = https://download.opensuse.org/repositories/home:/post-factum:/kernels/Arch/$arch

$ sudo pacman -S linux-pf-skylake
...
Initializing download: https://download.opensuse.org/repositories/home:/post-factum:/kernels/Arch/x86_64/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz
File size: 81442288 bytes
Opening output file /var/cache/pacman/pkg/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz.part
Starting download

Connection 0 finished                                                           

Downloaded 77.6694 Megabyte(s) in 1 second(s). (55599.86 KB/s)
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
:: File /var/cache/pacman/pkg/linux-pf-skylake-5.3.2-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (checksum)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (checksum))
Errors occurred, no packages were upgraded.

That seems to be another issue. OBS tends to rebuild packages often, and repo metadata may not match to the package that is rebuilt, but whose pkgrel wasn't changed. In this case just install it with pacman -U using pkg file from the cache folder.

I doubt I can do something about it since I'm not aware whether OBS can bump pkgrel automatically like it does for RPM specs. If you know the way, similarly, let me know.

post-factum · 2019-10-05 21:10:46

WorMzy wrote:

Mod note: Moving to AUR Issues.

I'm not a frequent guest here, so I do not know the rules, but FWIW, this topic has nothing to do with AUR.

jasonwryan · 2019-10-05 21:44:01

post-factum wrote:

WorMzy wrote:
Mod note: Moving to AUR Issues.
I'm not a frequent guest here, so I do not know the rules, but FWIW, this topic has nothing to do with AUR.

OP is sourcing an unsupported/community-provided repo, so it is in the same category as the AUR.

j1simon · 2019-10-06 07:38:07

post-factum wrote:

That seems to be another issue. OBS tends to rebuild packages often, and repo metadata may not match to the package that is rebuilt, but whose pkgrel wasn't changed. In this case just install it with pacman -U using pkg file from the cache folder.

If the OpenSuse repository has so many problems with Arch, what's the point of using it? Aren't there better and more compatible alternatives with Arch?

post-factum · 2019-10-06 07:41:19

j1simon wrote:

If the OpenSuse repository has so many problems with Arch, what's the point of using it? Aren't there better and more compatible alternatives with Arch?

Sure. Please suggest something that can build and host binary packages on a regular basis and for free, and I'll be more than happy to use it.

j1simon · 2019-10-07 07:58:41

Looking in other people's repositories I found these options:
https://osdn.net
https://sourceforge.net
https://github.com
https://bitbucket.org

I hope it helps.
Regards.

Lone_Wolf · 2019-10-07 11:30:46

For hosting those are useful, but do they offer the option to build in an archlinux environment ?

Last time I checked sourceforge & github didn't offer that (even for paying customers...) , no experience with the other two.

edit: typo

Last edited by Lone_Wolf (2019-10-07 11:36:38)

post-factum · 2019-10-07 11:35:08

Yes, those are not build systems unlike OBS.

metak · 2019-10-07 12:56:59

@post-factum Hi. I build binary packages for clearlinux kernels that I maintain in AUR in my OBS project. [1] After digging a bit deeper I believe that solution (at least for kernel) could be quite simple.

In your project page for kernels in Meta Configuration tab change `rebuild="transitive"` to `rebuild="local"`. This should trigger rebuild only when source is changed. [2]

[1]https://build.opensuse.org/project/show … ura:kernel
[2]https://openbuildservice.org/help/manua … 1.7.15.5.7

post-factum · 2019-10-07 13:12:04

metak wrote:

@post-factum Hi. I build binary packages for clearlinux kernels that I maintain in AUR in my OBS project. [1] After digging a bit deeper I believe that solution (at least for kernel) could be quite simple.
In your project page for kernels in Meta Configuration tab change `rebuild="transitive"` to `rebuild="local"`. This should trigger rebuild only when source is changed. [2]
[1]https://build.opensuse.org/project/show … ura:kernel
[2]https://openbuildservice.org/help/manua … 1.7.15.5.7

Thanks, applied.

And how do you deal with signatures?

metak · 2019-10-07 13:42:38

The only option right now is to ignore the warning about "unsupported signature format" (or use SigLevel = Never) and with that local rebuild there shouldn't be any more warnings about corrupted packages either. (This works for kernel which is self-contained, but then requires manual pkgrel bump if you're also building some kernel modules in the same repo, like virtualbox, wireguard etc.)
Code for building Archlinux packages in OBS was written as part of google summer of code project and it just barely works for the most part. ;-( Arch support is pretty low on their priority list.

Last edited by metak (2019-10-07 13:45:03)

Arch Linux

#1 2019-10-05 12:13:13

error: linux-pf-headers-skylake: signature is invalid

#2 2019-10-05 15:01:07

Re: error: linux-pf-headers-skylake: signature is invalid

#3 2019-10-05 17:10:35

Re: error: linux-pf-headers-skylake: signature is invalid

#4 2019-10-05 18:02:49

Re: error: linux-pf-headers-skylake: signature is invalid

#5 2019-10-05 18:44:55

Re: error: linux-pf-headers-skylake: signature is invalid

#6 2019-10-05 19:09:35

Re: error: linux-pf-headers-skylake: signature is invalid

#7 2019-10-05 20:26:02

Re: error: linux-pf-headers-skylake: signature is invalid

#8 2019-10-05 21:09:16

Re: error: linux-pf-headers-skylake: signature is invalid

#9 2019-10-05 21:10:46

Re: error: linux-pf-headers-skylake: signature is invalid

#10 2019-10-05 21:44:01

Re: error: linux-pf-headers-skylake: signature is invalid

#11 2019-10-06 07:38:07

Re: error: linux-pf-headers-skylake: signature is invalid

#12 2019-10-06 07:41:19

Re: error: linux-pf-headers-skylake: signature is invalid

#13 2019-10-07 07:58:41

Re: error: linux-pf-headers-skylake: signature is invalid

#14 2019-10-07 11:30:46

Re: error: linux-pf-headers-skylake: signature is invalid

#15 2019-10-07 11:35:08

Re: error: linux-pf-headers-skylake: signature is invalid

#16 2019-10-07 12:56:59

Re: error: linux-pf-headers-skylake: signature is invalid

#17 2019-10-07 13:12:04

Re: error: linux-pf-headers-skylake: signature is invalid

#18 2019-10-07 13:42:38

Re: error: linux-pf-headers-skylake: signature is invalid

Board footer