[packman] does packman have a new key or what is going on?

2021-10-29 Diskussionsfäden S.
On Fri Oct 29 16:10:47 CEST 2021 Stefan Seyfried wrote: I did not suggest to report the bug upstream, but against Leap 15.3 Yes, I understood. But I still think that openSUSE devs will not be very eager to revert a change that makes rpm not conform to the cryptography spec just to make it

Re: [packman] does packman have a new key or what is going on?

2021-10-29 Diskussionsfäden Stefan Seyfried
On 29.10.21 15:34, S. wrote: On Fri Oct 29 08:28:36 CEST 2021 Stefan Seyfried wrote: probably rpm needs to be fixed to again accept keys that were totally fine before the update. So I'd suggest filing a bug against 15.3 rpm package. I very much agree with you that this appears to be an

[packman] does packman have a new key or what is going on?

2021-10-29 Diskussionsfäden S.
On Fri Oct 29 08:28:36 CEST 2021 Stefan Seyfried wrote: probably rpm needs to be fixed to again accept keys that were totally fine before the update. So I'd suggest filing a bug against 15.3 rpm package. I very much agree with you that this appears to be an unnecessary problem caused by

Re: [packman] does packman have a new key or what is going on?

2021-10-29 Diskussionsfäden Stefan Seyfried
On 29.10.21 01:21, S. wrote: On Thu Oct 28 11:40:34 CEST 2021 Marcel Kühlhorn wrote: Interestingly, this only works with zypper, dnf and plain rpm fail to import the key I'm running into the same issue trying to build an image with Kiwi and manually importing the Packman key. I confirm that

[packman] does packman have a new key or what is going on?

2021-10-28 Diskussionsfäden S.
On Thu Oct 28 11:40:34 CEST 2021 Marcel Kühlhorn wrote: Interestingly, this only works with zypper, dnf and plain rpm fail to import the key I'm running into the same issue trying to build an image with Kiwi and manually importing the Packman key. I confirm that Zypper/YaST can import the

Re: [packman] does packman have a new key or what is going on?

2021-10-28 Diskussionsfäden Marcel Kühlhorn
On Thu, 2021-10-28 at 08:12 +0200, Simon Vogl wrote: > I managed to solve this by listing all rpm keys with > > rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n' > > and then removing the packman key with > > sudo rpm -e gpg-pubkey- > > afterwards, I removed the Packman

Re: [packman] does packman have a new key or what is going on?

2021-10-28 Diskussionsfäden Mathias Homann
Am 2021-10-28 08:12, schrieb Simon Vogl: I managed to solve this by listing all rpm keys with rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n' and then removing the packman key with sudo rpm -e gpg-pubkey- afterwards, I removed the Packman repo, re-added it and got a

Re: [packman] does packman have a new key or what is going on?

2021-10-28 Diskussionsfäden Simon Vogl
I managed to solve this by listing all rpm keys with rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n' and then removing the packman key with sudo rpm -e gpg-pubkey- afterwards, I removed the Packman repo, re-added it and got a new key trust prompt. Once i accepted that,

Re: [packman] does packman have a new key or what is going on?

2021-10-27 Diskussionsfäden Mathias Homann
Am Mittwoch, 27. Oktober 2021, 19:56:05 CEST schrieb Mathias Homann: > Hi, > > I just got a ton of updated packages from packman on tumbleweed 20211025 and > with every package zypper gave me a NOKEY warning but installed it all the > same... > > now, when I run something like "rpm -Vvv

[packman] does packman have a new key or what is going on?

2021-10-27 Diskussionsfäden Mathias Homann
Hi, I just got a ton of updated packages from packman on tumbleweed 20211025 and with every package zypper gave me a NOKEY warning but installed it all the same... now, when I run something like "rpm -Vvv vlc-codec-gstreamer" I see the same NOKEY warning appear: D: read h# 68693 Header V4