How to fix update problems with debian 9?











up vote
0
down vote

favorite












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







share|improve this question














bumped to the homepage by Community♦ 2 days 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 at 6:59

















up vote
0
down vote

favorite












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







share|improve this question














bumped to the homepage by Community♦ 2 days 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 at 6:59















up vote
0
down vote

favorite









up vote
0
down vote

favorite











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







share|improve this question













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




linux debian repository gpg






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 24 '17 at 6:22









SmithBit

12




12





bumped to the homepage by Community♦ 2 days 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♦ 2 days 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 at 6:59
















  • 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 at 6:59










1




1




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




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




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




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 at 6:59






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












1 Answer
1






active

oldest

votes

















up vote
0
down vote













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.






share|improve this answer





















    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
    });


    }
    });














    draft saved

    draft discarded


















    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















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    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.






    share|improve this answer

























      up vote
      0
      down vote













      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.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        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.






        share|improve this answer












        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 24 '17 at 6:42









        dirkt

        16.4k21335




        16.4k21335






























            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














            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















            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







            -

            Popular posts from this blog

            Accessing regular linux commands in Huawei's Dopra Linux

            Image
            4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel
            Read more

            Can't connect RFCOMM socket: Host is down

            Image
            up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2
            Read more

            Kernel panic - not syncing: Fatal Exception in Interrupt

            Image
            0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment
            Read more