How to fix update problems with debian 9?

I had debian jessie installed and just perform an update with the command:

sudo apt-get update && apt-get upgrade

The problem is that I upgrade to version 9 of debian and now when I run the same command to update (debian9) it throws me errors of public keys, repository not found or unsigned.

Is there any way to get back to version 8.7 of debian or to fix this error without uninstalling?

Thanks!

asked Mar 24 '17 at 6:22

SmithBit

bumped to the homepage by Community♦ 14 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

1

What is the error message?
– daisy
Mar 24 '17 at 6:29

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
– SmithBit
Mar 24 '17 at 6:41

Please edit here by adding the whole error message
– GAD3R
Mar 24 '17 at 14:01

Note that in sudo apt-get update && apt-get upgrade, the sudo command affects only the apt-get update part.
– telcoM
Oct 25 '18 at 6:59

add a comment |

I had debian jessie installed and just perform an update with the command:

sudo apt-get update && apt-get upgrade

The problem is that I upgrade to version 9 of debian and now when I run the same command to update (debian9) it throws me errors of public keys, repository not found or unsigned.

Is there any way to get back to version 8.7 of debian or to fix this error without uninstalling?

Thanks!

asked Mar 24 '17 at 6:22

SmithBit

bumped to the homepage by Community♦ 14 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

1

What is the error message?
– daisy
Mar 24 '17 at 6:29

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
– SmithBit
Mar 24 '17 at 6:41

Please edit here by adding the whole error message
– GAD3R
Mar 24 '17 at 14:01

Note that in sudo apt-get update && apt-get upgrade, the sudo command affects only the apt-get update part.
– telcoM
Oct 25 '18 at 6:59

add a comment |

I had debian jessie installed and just perform an update with the command:

sudo apt-get update && apt-get upgrade

The problem is that I upgrade to version 9 of debian and now when I run the same command to update (debian9) it throws me errors of public keys, repository not found or unsigned.

Is there any way to get back to version 8.7 of debian or to fix this error without uninstalling?

Thanks!

asked Mar 24 '17 at 6:22

SmithBit

I had debian jessie installed and just perform an update with the command:

sudo apt-get update && apt-get upgrade

The problem is that I upgrade to version 9 of debian and now when I run the same command to update (debian9) it throws me errors of public keys, repository not found or unsigned.

Is there any way to get back to version 8.7 of debian or to fix this error without uninstalling?

Thanks!

linux debian repository gpg

asked Mar 24 '17 at 6:22

SmithBit

asked Mar 24 '17 at 6:22

SmithBit

asked Mar 24 '17 at 6:22

SmithBit

asked Mar 24 '17 at 6:22

SmithBit

asked Mar 24 '17 at 6:22

SmithBit

bumped to the homepage by Community♦ 14 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

bumped to the homepage by Community♦ 14 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

1

What is the error message?
– daisy
Mar 24 '17 at 6:29

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
– SmithBit
Mar 24 '17 at 6:41

Please edit here by adding the whole error message
– GAD3R
Mar 24 '17 at 14:01

Note that in sudo apt-get update && apt-get upgrade, the sudo command affects only the apt-get update part.
– telcoM
Oct 25 '18 at 6:59

add a comment |

1

What is the error message?
– daisy
Mar 24 '17 at 6:29

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
– SmithBit
Mar 24 '17 at 6:41

Please edit here by adding the whole error message
– GAD3R
Mar 24 '17 at 14:01

Note that in sudo apt-get update && apt-get upgrade, the sudo command affects only the apt-get update part.
– telcoM
Oct 25 '18 at 6:59

What is the error message?
– daisy
Mar 24 '17 at 6:29

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
– SmithBit
Mar 24 '17 at 6:41

Please edit here by adding the whole error message
– GAD3R
Mar 24 '17 at 14:01

Note that in sudo apt-get update && apt-get upgrade, the sudo command affects only the apt-get update part.
– telcoM
Oct 25 '18 at 6:59

add a comment |

1 Answer
1

active

oldest

votes

If your repository links in /etc/apt are stale, have a look at them and change them to more current links.

To ensure up-to-date public keys, use aptitude or apt-get to force an upgrade of all the keyring packages, especially debian-keyring.

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

add a comment |

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',
autoActivateHeartbeat: false,
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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f353501%2fhow-to-fix-update-problems-with-debian-9%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

If your repository links in /etc/apt are stale, have a look at them and change them to more current links.

To ensure up-to-date public keys, use aptitude or apt-get to force an upgrade of all the keyring packages, especially debian-keyring.

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

add a comment |

If your repository links in /etc/apt are stale, have a look at them and change them to more current links.

To ensure up-to-date public keys, use aptitude or apt-get to force an upgrade of all the keyring packages, especially debian-keyring.

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

add a comment |

If your repository links in /etc/apt are stale, have a look at them and change them to more current links.

To ensure up-to-date public keys, use aptitude or apt-get to force an upgrade of all the keyring packages, especially debian-keyring.

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

If your repository links in /etc/apt are stale, have a look at them and change them to more current links.

To ensure up-to-date public keys, use aptitude or apt-get to force an upgrade of all the keyring packages, especially debian-keyring.

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

answered Mar 24 '17 at 6:42

dirkt

16.7k21336

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Yrurtj