https://bugs.kde.org/show_bug.cgi?id=469749
Jonathan Riddell changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=469749
Nick changed:
What|Removed |Added
CC||nick.craig@gmail.com
--- Comment #5 from Nick ---
https://bugs.kde.org/show_bug.cgi?id=469749
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to Jonathan Riddell from comment #1)
> ... once neon-settings-2 is upgraded.
Yes, if I first do a:
pkcon update neon-settings-2
then the:
pkcon update
works fine...
Thank you
--
https://bugs.kde.org/show_bug.cgi?id=469749
--- Comment #3 from Moltke ---
(In reply to Jonathan Riddell from comment #1)
> I think this was due to the new gpgme while the old one from Ubuntu still
> has an apt pin. Please try upgrading now. You may need to do so twice as
> the new pin will
https://bugs.kde.org/show_bug.cgi?id=469749
tagwer...@innerjoin.org changed:
What|Removed |Added
CC||tagwer...@innerjoin.org
--- Comment
https://bugs.kde.org/show_bug.cgi?id=469749
--- Comment #1 from Jonathan Riddell ---
I think this was due to the new gpgme while the old one from Ubuntu still has
an apt pin. Please try upgrading now. You may need to do so twice as the new
pin will only be installed once neon-settings-2 is
