I used MX Repo Manager to select the fastest MX repo near my usual VPN server location. Did the same In the Debian repo list. And in the Individual sources I unchecked the ' *deb https://riot.im/packages/debian/artful main.
Then reloaded but still got errors, so went back and re-checked *deb https://riot.im/packages/debian/artful main.
Reloading results in this message:
W: GPG error: https://riot.im artful InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E019645248E8F4A1
At present there are 3 broken packages and 6 to install/upgrade.
I cannot fix the broken packages using Edit>Fix Broken Packages.
E: Unable to correct problems, you have held broken packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
MX16 update problem SOLVED
Re: MX16 update problem
Checkaptgpg should fix the NO_PUBKEY error. (I'll let someone else deliver the FrankenDebian lecture)bazzaman wrote: ↑Mon Mar 18, 2019 9:59 am W: GPG error: https://riot.im artful InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E019645248E8F4A1
Code: Select all
$ sudo checkaptgpg
Checking dl.google.com_linux_chrome_deb_dists_stable_Release
Good GPG signature found.
Checking riot.im_packages_debian_dists_artful_Release
gpg: requesting key 48E8F4A1 from hkp server keyserver.ubuntu.com
gpg: key 48E8F4A1: public key "riot.im (Package Signing key) <packages@riot.im>" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
Checking mxrepo.com_mx_repo_dists_mx16_InRelease
Good GPG signature found. ...
Re: MX16 update problem
thank you... checkaptgpg did it. After reloading synaptic package manager message reads "Successfully fixed dependency problems"
Re: MX16 update problem SOLVED
I already posted the Checkaptgpg suggestion in post #7, AND delivered a mild FrankenDebian lecture.
@bazzaman, you might also wish to know that the checkaptgpg app can also be applied graphically from MX Tools without needing a
command in terminal.
@bazzaman, you might also wish to know that the checkaptgpg app can also be applied graphically from MX Tools without needing a
Code: Select all
sudo checkaptgpg
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX16 update problem SOLVED
Sorry asqwerth, I missed that. I wasn't aware of the MX Tools option. I wasn't exaggerating too much with the senility remark... I'm slowing down.
Had to look up 'FrankenDebian'. The thing is I don't think I ever installed anything outside of the MX repos. And I have no idea what that riot.im key was for. (except for 1 AppImage, could that be it?)
Anyway it's all good now. Thanks to all here for your help and patience.
Had to look up 'FrankenDebian'. The thing is I don't think I ever installed anything outside of the MX repos. And I have no idea what that riot.im key was for. (except for 1 AppImage, could that be it?)
Anyway it's all good now. Thanks to all here for your help and patience.