Here is the entire error message i get. How do i solve this? 😫
and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386', W:GPG error: https://dl.winehq.org/wine-builds/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F, E:The repository 'https://dl.winehq.org/wine-builds/ubuntu jammy InRelease' is not signed.
#W:Updating from such a repository can't be done securely.
26 messages · Page 1 of 1 (latest)
- W: See apt-secure(8) manpage for repository creation and user configuration details.,
- W: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com/ stable InRelease' doesn't support architecture 'i386',
- W: GPG error: https://dl.winehq.org/wine-builds/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F,
- E: The repository 'https://dl.winehq.org/wine-builds/ubuntu jammy InRelease' is not signed.
W = warning
E = error
the second warning is about 32-bit stuff. disregard
third warning is re: keys. u can fix that in Mint Sources tool in the keys section
brave doesn't support 32bit
remove any problematic repos and re-add them looking at the web resource insofar as what to point your system at rather than just copying the text back in there
Thank you I am looking at the Authentication keys what do i do with this. Sorry I am a newbie
Thank you. How do i "remove any problematic repos?
there is a gui for software sources available with mint
i was just looking at the auth, keys again and IU see more keys now than before.
'add missing keys' it was there in first pic
don't remove the brave repo. that's how u get updates for the brave browser
maybe it added them, since u did mention u saw more keys later
should be fine now, and ignore the 386 thing for 32-bit
Okay thank you. I will look in to it tomorrow
this is an error that i received after updating within the software sources
W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386', W:GPG error: https://dl.winehq.org/wine-builds/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F, E:The repository 'https://dl.winehq.org/wine-builds/ubuntu jammy InRelease' is not signed.
i just restarted the pc, and i refreshed the update manager and i got this error. W:GPG error: https://dl.winehq.org/wine-builds/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F, E:The repository 'https://dl.winehq.org/wine-builds/ubuntu jammy InRelease' is not signed.
same shyte
just add the key manually then from terminal. wine hq site/google is ur friend
Please forgive me but 'Google is your friend'?