[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] [PM] vivaldi 2.1.1337.51-lp151.1.2 (openSUSE_Leap 15.1/x86_64) -- Update

2021-10-28 Diskussionsfäden Stefan Seyfried
On 28.10.21 12:18, Edgar Aichinger wrote: Am Mittwoch, 27. Oktober 2021, 21:40:04 CEST schrieb Ulf Bartholomäus: Strange, why vivaldi is i586 and not a x86_64 package? The way I understood this discussion that you should NOT use this very old and unmaintained package, but install from the

Re: [packman] [PM] vivaldi 2.1.1337.51-lp151.1.2 (openSUSE_Leap 15.1/x86_64) -- Update

2021-10-28 Diskussionsfäden Edgar Aichinger
Am Mittwoch, 27. Oktober 2021, 21:40:04 CEST schrieb Ulf Bartholomäus: > Hi :-) > > for some minutes, I received an update, but still the same issue. > > Then I do after > # zypper dup > > # zypper se -si vival > Loading repository data... > Reading installed packages... > > S | Name|

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

[packman] [PM] vivaldi 2.1.1337.51-lp151.1.2 (openSUSE_Leap 15.1/x86_64) -- Update

2021-10-28 Diskussionsfäden Ulf Bartholomäus
Hi :-) for some minutes, I received an update, but still the same issue. Then I do after # zypper dup # zypper se -si vival Loading repository data... Reading installed packages... S | Name| Type| Version | Arch | Repository

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,