Hello,
in the past I used to install rpms from GUI without any problem, but since two weeks ago I started to get this error:
http://s28.postimg.org/fj6h2i1zh/image.png
I haven’t aboterted the install… so I’ve run zypper from terminal and I’ve found that the abort reason is the missing key:
http://s29.postimg.org/nx008xd5z/image.png
Well, this is not a big problem, but I’d like to be able to install the packages from GUI again… Is there a way to fix this ?
Many thanks
On 2015-08-09 15:06, Luca91 wrote:
> Well, this is not a big problem, but I’d like to be able to install the
> packages from GUI again… Is there a way to fix this ?
No.
Known problem.
You have to use another GUI: ie, use YaST.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
thank you for your reply robin_listas, so is this actually a bug ? I was thinking that this was a sort of “secure” feature
On 2015-08-09 17:06, Luca91 wrote:
>
> thank you for your reply robin_listas, so is this actually a bug ? I was
> thinking that this was a sort of “secure” feature
Yes, it is a bug. I don’t remember if it is in packagekit or apper.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
You can configure your repo to not do a certificate check
zypper ar --no-gpgcheck *repo_URI repo_name *
So, for example I just modified the instructions to Elasticsearch repos on my wiki
https://en.opensuse.org/User:Tsu2/elasticsearch_logstash_official_repos
The reason why the gpgcheck needs to be invalidated is because apparently the ES repos upgraded to the latest version YUM repos while zypper hasn’t upgraded to support the new repo format yet.
TSU
This happens only installing rpms downloaded from the net (not from repository).
Ok I’ll wait for a zypper update then.
Thank you 
On 2015-08-10 15:16, Luca91 wrote:
>
> This happens only installing rpms downloaded from the net (not from
> repository).
Meaning that they don’t have a PGP/GPG key, or as in this case, that you
did not manually import the key used to sign the package, in advance,
into the rpm database.
> Ok I’ll wait for a zypper update then.
No, zypper update will not solve that.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
It is only a warning it should allow an install
Note Appr is more picky and won’t use Yast or zypper
On 2015-08-10 15:28, I wrote:
> On 2015-08-10 15:16, Luca91 wrote:
>>
>> This happens only installing rpms downloaded from the net (not from
>> repository).
>
> Meaning that they don’t have a PGP/GPG key, or as in this case, that you
> did not manually import the key used to sign the package, in advance,
> into the rpm database.
Have a look at “man rpmkeys”, it says how to import the keys.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Wait a moment, you are right that they don’t have PGP/GPG key, but that shouldn’t be an “ABORTED BY USER” error…
I remember that I was able to install those rpms without problems in the past using apper.
On 2015-08-10 17:26, Luca91 wrote:
> Wait a moment, you are right that they don’t have PGP/GPG key, but that
> shouldn’t be an “ABORTED BY USER” error…
Because THAT’S the bug in apper I was talking about…
There is a problem with that and with solving dependencies, when the
user has to choose. Also there is another problem where the popup
message goes behind every window, and apper itself does not respond and
seems stuck.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)