Renaming trusted.gpg to trusted.gpg-broken

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

I ran a fresh install of Debian stretch 9.8.0 and all was well. I then ran

sudo apt update

and I get an output which hits the ftp.debian.stretch server for the update thing is it tells me

unable to retrieve update trusted.gpg keys unauthorised

So I do a bit of research and came across a post, it said

Rename trusted.gpg to trusted.gpg-broken

And now I can sudo apt update and basically get what ever I want as standard, but I don’t understand why after a fresh install the trusted keys were not found in the file?

And I also don’t understand what changing trusted.gpg to trusted.gpg-broken actually did to the keys.

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

asked Mar 8 at 9:57

Curiouskangaroo

112

This post?

– RoVo
Mar 8 at 10:23

That’s the one I followed to get it working, but I want info on why this fixes it and what does -broken acctually do? Nice1 Rovo

– Curiouskangaroo
Mar 8 at 11:52

-broken doesn't mean anything. You can call it -backup or simply delete it to have the same effect. Renaming the file is just to get the old one out of the way but don't delete it for backup reasons. I think when the file is missing, apt will somehow regenerate (and thus fix) it. Why it happens in the first place, I don't know.

– RoVo
Mar 8 at 12:39

Sweet so just the renaming of it basically. When apt looks for the keys can not locate the directory so bypass that step I take it.

– Curiouskangaroo
Mar 8 at 12:47

add a comment |

I ran a fresh install of Debian stretch 9.8.0 and all was well. I then ran

sudo apt update

and I get an output which hits the ftp.debian.stretch server for the update thing is it tells me

unable to retrieve update trusted.gpg keys unauthorised

So I do a bit of research and came across a post, it said

Rename trusted.gpg to trusted.gpg-broken

And now I can sudo apt update and basically get what ever I want as standard, but I don’t understand why after a fresh install the trusted keys were not found in the file?

And I also don’t understand what changing trusted.gpg to trusted.gpg-broken actually did to the keys.

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

asked Mar 8 at 9:57

Curiouskangaroo

112

This post?

– RoVo
Mar 8 at 10:23

That’s the one I followed to get it working, but I want info on why this fixes it and what does -broken acctually do? Nice1 Rovo

– Curiouskangaroo
Mar 8 at 11:52

-broken doesn't mean anything. You can call it -backup or simply delete it to have the same effect. Renaming the file is just to get the old one out of the way but don't delete it for backup reasons. I think when the file is missing, apt will somehow regenerate (and thus fix) it. Why it happens in the first place, I don't know.

– RoVo
Mar 8 at 12:39

Sweet so just the renaming of it basically. When apt looks for the keys can not locate the directory so bypass that step I take it.

– Curiouskangaroo
Mar 8 at 12:47

add a comment |

I ran a fresh install of Debian stretch 9.8.0 and all was well. I then ran

sudo apt update

and I get an output which hits the ftp.debian.stretch server for the update thing is it tells me

unable to retrieve update trusted.gpg keys unauthorised

So I do a bit of research and came across a post, it said

Rename trusted.gpg to trusted.gpg-broken

And now I can sudo apt update and basically get what ever I want as standard, but I don’t understand why after a fresh install the trusted keys were not found in the file?

And I also don’t understand what changing trusted.gpg to trusted.gpg-broken actually did to the keys.

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

asked Mar 8 at 9:57

Curiouskangaroo

112

I ran a fresh install of Debian stretch 9.8.0 and all was well. I then ran

sudo apt update

and I get an output which hits the ftp.debian.stretch server for the update thing is it tells me

unable to retrieve update trusted.gpg keys unauthorised

So I do a bit of research and came across a post, it said

Rename trusted.gpg to trusted.gpg-broken

And now I can sudo apt update and basically get what ever I want as standard, but I don’t understand why after a fresh install the trusted keys were not found in the file?

And I also don’t understand what changing trusted.gpg to trusted.gpg-broken actually did to the keys.

debian apt gpg

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

asked Mar 8 at 9:57

Curiouskangaroo

112

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

asked Mar 8 at 9:57

Curiouskangaroo

112

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

edited Mar 8 at 12:18

Rui F Ribeiro

41.9k1483142

asked Mar 8 at 9:57

Curiouskangaroo

112

asked Mar 8 at 9:57

Curiouskangaroo

112

asked Mar 8 at 9:57

Curiouskangaroo

112

This post?

– RoVo
Mar 8 at 10:23

That’s the one I followed to get it working, but I want info on why this fixes it and what does -broken acctually do? Nice1 Rovo

– Curiouskangaroo
Mar 8 at 11:52

-broken doesn't mean anything. You can call it -backup or simply delete it to have the same effect. Renaming the file is just to get the old one out of the way but don't delete it for backup reasons. I think when the file is missing, apt will somehow regenerate (and thus fix) it. Why it happens in the first place, I don't know.

– RoVo
Mar 8 at 12:39

Sweet so just the renaming of it basically. When apt looks for the keys can not locate the directory so bypass that step I take it.

– Curiouskangaroo
Mar 8 at 12:47

add a comment |

This post?

– RoVo
Mar 8 at 10:23

That’s the one I followed to get it working, but I want info on why this fixes it and what does -broken acctually do? Nice1 Rovo

– Curiouskangaroo
Mar 8 at 11:52

-broken doesn't mean anything. You can call it -backup or simply delete it to have the same effect. Renaming the file is just to get the old one out of the way but don't delete it for backup reasons. I think when the file is missing, apt will somehow regenerate (and thus fix) it. Why it happens in the first place, I don't know.

– RoVo
Mar 8 at 12:39

Sweet so just the renaming of it basically. When apt looks for the keys can not locate the directory so bypass that step I take it.

– Curiouskangaroo
Mar 8 at 12:47

This post?

– RoVo
Mar 8 at 10:23

That’s the one I followed to get it working, but I want info on why this fixes it and what does -broken acctually do? Nice1 Rovo

– Curiouskangaroo
Mar 8 at 11:52

-broken doesn't mean anything. You can call it -backup or simply delete it to have the same effect. Renaming the file is just to get the old one out of the way but don't delete it for backup reasons. I think when the file is missing, apt will somehow regenerate (and thus fix) it. Why it happens in the first place, I don't know.

– RoVo
Mar 8 at 12:39

Sweet so just the renaming of it basically. When apt looks for the keys can not locate the directory so bypass that step I take it.

– Curiouskangaroo
Mar 8 at 12:47

add a comment |

0

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',
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

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505095%2frenaming-trusted-gpg-to-trusted-gpg-broken%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

0

active

oldest

votes

0

active

oldest

votes

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.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu