![]() ![]() The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. When you do an apt upgrade after apt update, it upgrades (or updates, whichever term you prefer) the installed packages to the newer version. The cookie is used to store the user consent for the cookies in the category "Other. This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. Because two days ago, I did a fresh install of antiX 19.1 and did sudo apt update with no problem after that gdebi error with zzzFM 32-bit. I get this invalid signature error only after a fresh install of either antiX 19.1 or 19.3. I changed to the US Lenexa, KA repo, and I still get this error. This reply was modified 2 years, 3 months ago by christophe. No active apt repos in: /etc/apt//various.list No active apt repos in: /etc/apt//onion.list Repos: Active apt repos in: /etc/apt//antix.listġ: deb https: //./linux/distributions/mx/packages/antix/buster/ buster main nonfree nosystemdĪctive apt repos in: /etc/apt//buster-backports.listġ: deb http: ///debian buster-backports main contrib non-freeĪctive apt repos in: /etc/apt//debian-stable-updates.listġ: deb http: //ftp.us./debian/ buster-updates main contrib non-freeĪctive apt repos in: /etc/apt//debian.listġ: deb http: //ftp.us./debian/ buster main contrib non-freeĢ: deb http: /// buster/updates main contrib non-free As you can see in the above picture, the command-line sudo apt-get update in question contains the command named apt-get and the sub-command named update and we have no options or arguments in this command line. ![]() I’m using the US/Lenexa, KS antiX mirror, if that helps. I just did an update/upgrade to test what you say. N: See apt-secure(8) manpage for repository creation and user configuration details. N: Updating from such a repository can’t be done securely, and is therefore disabled by default. W: GPG error: buster InRelease: The following signatures were invalid: EXPKEYSIG DB36CDF3452F0C20 antiX (antix repo) Į: The repository ‘ buster InRelease’ is not signed. The following signatures were invalid: EXPKEYSIG DB36CDF3452F0C20 antiX (antix repo) The other ones I tried include Chemnitz, Germany Madison, WI and Chicago, Il. I also tried changing to different repos and still getting invalid signatures. ![]() I am trying to do sudo apt update and I am getting invalid signatures. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |