[Touch-packages] [Bug 1912526] Re: cannot import new keys if another malformed key exists

2021-06-30 Thread Christian Rauch
I have to say that it is quite a shame that Canonical does not provide a proper solution for this problem, as it has quite a big impact if you cannot update packages with security fixes anymore. Anyway, I managed to solve the problem. From an earlier repo installation I had a file "isv:ownCloud:de

[Touch-packages] [Bug 1912526] Re: cannot import new keys if another malformed key exists

2021-06-30 Thread Christian Rauch
I have to say that it is quite a shame that Canonical does not provide a proper solution for this problem, as it has quite a big impact if you cannot update packages with security fixes anymore. Anyway, I managed to solve the problem. From an earlier repo installation, I had a key file with the tr

[Touch-packages] [Bug 1912526] Re: cannot import new keys if another malformed key exists

2021-01-21 Thread Christian Rauch
It's in the latest Ubuntu LTS and will stay be there until 2025. If it is legacy and deprecated, maybe it should have been removed? In its current state, this apt-key issue has some security implications: First, the Ubuntu update GUI is not very intuitive in handling this issue. It presents the u

[Touch-packages] [Bug 1912526] Re: cannot import new keys if another malformed key exists

2021-01-21 Thread Julian Andres Klode
It's a legacy tool nobody should be using anymore. It's been like what, half a decade or so, we've been telling people to stop it, and drop files into trusted.gpg.d. It will go away in 2022. So I'm not super excited about spending time investigating and fixing this, but I guess I'll have a crack a