“apt update” error on GPG signatures for archive.canonical.com repository

Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
Background
I'm running a Dell XPS with Ubuntu LTS 18.01 (Bionic)
Objective
Run sudo apt update to update my packages
Problem
I get the following error:
...
Ign:12 http://archive.canonical.com precise Release.gpg
Reading package lists... Done
W: GPG error: http://archive.canonical.com precise Release: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository 'http://archive.canonical.com precise Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Attempted Solutions
Attempt A
Regenerating the repository list, via
https://superuser.com/questions/1059346/apt-get-update-not-working-signing-verification-errors
and
Failing on apt-get update: The following signatures were invalid
Result A
Same Error
Attempt B
Commented out the offending repo link in /etc/apt/sources.list, specifically deb http://archive.canonical.com/ precise partner
Result B
It works! No more errors. But, I'm concerned I need this repository
Question
What is this error, and how do I fix it? Many thanks.
ubuntu apt repository gpg
add a comment |
up vote
-1
down vote
favorite
Background
I'm running a Dell XPS with Ubuntu LTS 18.01 (Bionic)
Objective
Run sudo apt update to update my packages
Problem
I get the following error:
...
Ign:12 http://archive.canonical.com precise Release.gpg
Reading package lists... Done
W: GPG error: http://archive.canonical.com precise Release: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository 'http://archive.canonical.com precise Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Attempted Solutions
Attempt A
Regenerating the repository list, via
https://superuser.com/questions/1059346/apt-get-update-not-working-signing-verification-errors
and
Failing on apt-get update: The following signatures were invalid
Result A
Same Error
Attempt B
Commented out the offending repo link in /etc/apt/sources.list, specifically deb http://archive.canonical.com/ precise partner
Result B
It works! No more errors. But, I'm concerned I need this repository
Question
What is this error, and how do I fix it? Many thanks.
ubuntu apt repository gpg
1
Why not use the equivalent bionic repository instead of end-of-lifed precise?
– A.B
Dec 9 at 1:08
There seems to be a signature...curl -s http://archive.canonical.com/dists/precise/Release.gpg | gpg --list-packets... which corresponds to keyid 40976eaf437d05b5 ... so, do you have the public key in your apt-key store ...apt-key list 40976eaf437d05b5
– RubberStamp
Dec 9 at 2:02
@RubberStamp, apparently I do!
– whearyou
Dec 10 at 21:45
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Background
I'm running a Dell XPS with Ubuntu LTS 18.01 (Bionic)
Objective
Run sudo apt update to update my packages
Problem
I get the following error:
...
Ign:12 http://archive.canonical.com precise Release.gpg
Reading package lists... Done
W: GPG error: http://archive.canonical.com precise Release: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository 'http://archive.canonical.com precise Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Attempted Solutions
Attempt A
Regenerating the repository list, via
https://superuser.com/questions/1059346/apt-get-update-not-working-signing-verification-errors
and
Failing on apt-get update: The following signatures were invalid
Result A
Same Error
Attempt B
Commented out the offending repo link in /etc/apt/sources.list, specifically deb http://archive.canonical.com/ precise partner
Result B
It works! No more errors. But, I'm concerned I need this repository
Question
What is this error, and how do I fix it? Many thanks.
ubuntu apt repository gpg
Background
I'm running a Dell XPS with Ubuntu LTS 18.01 (Bionic)
Objective
Run sudo apt update to update my packages
Problem
I get the following error:
...
Ign:12 http://archive.canonical.com precise Release.gpg
Reading package lists... Done
W: GPG error: http://archive.canonical.com precise Release: The following signatures were invalid: 630239CC130E1A7FD81A27B140976EAF437D05B5
E: The repository 'http://archive.canonical.com precise Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Attempted Solutions
Attempt A
Regenerating the repository list, via
https://superuser.com/questions/1059346/apt-get-update-not-working-signing-verification-errors
and
Failing on apt-get update: The following signatures were invalid
Result A
Same Error
Attempt B
Commented out the offending repo link in /etc/apt/sources.list, specifically deb http://archive.canonical.com/ precise partner
Result B
It works! No more errors. But, I'm concerned I need this repository
Question
What is this error, and how do I fix it? Many thanks.
ubuntu apt repository gpg
ubuntu apt repository gpg
asked Dec 9 at 0:40
whearyou
11
11
1
Why not use the equivalent bionic repository instead of end-of-lifed precise?
– A.B
Dec 9 at 1:08
There seems to be a signature...curl -s http://archive.canonical.com/dists/precise/Release.gpg | gpg --list-packets... which corresponds to keyid 40976eaf437d05b5 ... so, do you have the public key in your apt-key store ...apt-key list 40976eaf437d05b5
– RubberStamp
Dec 9 at 2:02
@RubberStamp, apparently I do!
– whearyou
Dec 10 at 21:45
add a comment |
1
Why not use the equivalent bionic repository instead of end-of-lifed precise?
– A.B
Dec 9 at 1:08
There seems to be a signature...curl -s http://archive.canonical.com/dists/precise/Release.gpg | gpg --list-packets... which corresponds to keyid 40976eaf437d05b5 ... so, do you have the public key in your apt-key store ...apt-key list 40976eaf437d05b5
– RubberStamp
Dec 9 at 2:02
@RubberStamp, apparently I do!
– whearyou
Dec 10 at 21:45
1
1
Why not use the equivalent bionic repository instead of end-of-lifed precise?
– A.B
Dec 9 at 1:08
Why not use the equivalent bionic repository instead of end-of-lifed precise?
– A.B
Dec 9 at 1:08
There seems to be a signature...
curl -s http://archive.canonical.com/dists/precise/Release.gpg | gpg --list-packets ... which corresponds to keyid 40976eaf437d05b5 ... so, do you have the public key in your apt-key store ... apt-key list 40976eaf437d05b5– RubberStamp
Dec 9 at 2:02
There seems to be a signature...
curl -s http://archive.canonical.com/dists/precise/Release.gpg | gpg --list-packets ... which corresponds to keyid 40976eaf437d05b5 ... so, do you have the public key in your apt-key store ... apt-key list 40976eaf437d05b5– RubberStamp
Dec 9 at 2:02
@RubberStamp, apparently I do!
– whearyou
Dec 10 at 21:45
@RubberStamp, apparently I do!
– whearyou
Dec 10 at 21:45
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486865%2fapt-update-error-on-gpg-signatures-for-archive-canonical-com-repository%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486865%2fapt-update-error-on-gpg-signatures-for-archive-canonical-com-repository%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Why not use the equivalent bionic repository instead of end-of-lifed precise?
– A.B
Dec 9 at 1:08
There seems to be a signature...
curl -s http://archive.canonical.com/dists/precise/Release.gpg | gpg --list-packets... which corresponds to keyid 40976eaf437d05b5 ... so, do you have the public key in your apt-key store ...apt-key list 40976eaf437d05b5– RubberStamp
Dec 9 at 2:02
@RubberStamp, apparently I do!
– whearyou
Dec 10 at 21:45