Debian testing added to sources.list, how to undo the upgrades?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












2















Another sysadmin added the following to sources.list:



deb http://ftp.de.debian.org/debian testing main


At some point in time a apt-get upgrade was run, causing most packages to be updated a alpha or beta package. For example apt:



$ apt-cache policy apt
apt:
Installed: 1.8.0~alpha3
Candidate: 1.8.0~beta1
Version table:
1.8.0~beta1 500
500 http://ftp.de.debian.org/debian testing/main amd64 Packages
*** 1.8.0~alpha3 100
100 /var/lib/dpkg/status
1.0.9.8.5 500
500 http://security.debian.org jessie/updates/main amd64 Packages
1.0.9.8.4 500
500 http://debian.mirrors.ovh.net/debian jessie/main amd64 Packages


I do not have a list of packages which have been upgraded,
this wouldn't be really much of an issue however, if I now disable the testing source and try to install anything there's many dispensary issues from mismatching version numbers.



Is there a way to downgrade all packages to the best candidate for the jessie source? Or get a list of all packaged that are installed from the tested source?










share|improve this question















migrated from askubuntu.com Feb 7 at 19:32


This question came from our site for Ubuntu users and developers.













  • 4





    fyi: debian jessie is 8, testing or buster is 10. Your testing packages are from two versions ahead of the old-stable or jessie packages. Even if you push packages back, some of your .conf (config) files may have been upgraded beyond what the old release can handle (I've had this occur before, new options are set that old version couldn't cope with)

    – guiverc
    Feb 7 at 9:54











  • @A.B Fixed for Jessie , stretch , buster and Sid.

    – GAD3R
    Feb 7 at 21:04















2















Another sysadmin added the following to sources.list:



deb http://ftp.de.debian.org/debian testing main


At some point in time a apt-get upgrade was run, causing most packages to be updated a alpha or beta package. For example apt:



$ apt-cache policy apt
apt:
Installed: 1.8.0~alpha3
Candidate: 1.8.0~beta1
Version table:
1.8.0~beta1 500
500 http://ftp.de.debian.org/debian testing/main amd64 Packages
*** 1.8.0~alpha3 100
100 /var/lib/dpkg/status
1.0.9.8.5 500
500 http://security.debian.org jessie/updates/main amd64 Packages
1.0.9.8.4 500
500 http://debian.mirrors.ovh.net/debian jessie/main amd64 Packages


I do not have a list of packages which have been upgraded,
this wouldn't be really much of an issue however, if I now disable the testing source and try to install anything there's many dispensary issues from mismatching version numbers.



Is there a way to downgrade all packages to the best candidate for the jessie source? Or get a list of all packaged that are installed from the tested source?










share|improve this question















migrated from askubuntu.com Feb 7 at 19:32


This question came from our site for Ubuntu users and developers.













  • 4





    fyi: debian jessie is 8, testing or buster is 10. Your testing packages are from two versions ahead of the old-stable or jessie packages. Even if you push packages back, some of your .conf (config) files may have been upgraded beyond what the old release can handle (I've had this occur before, new options are set that old version couldn't cope with)

    – guiverc
    Feb 7 at 9:54











  • @A.B Fixed for Jessie , stretch , buster and Sid.

    – GAD3R
    Feb 7 at 21:04













2












2








2








Another sysadmin added the following to sources.list:



deb http://ftp.de.debian.org/debian testing main


At some point in time a apt-get upgrade was run, causing most packages to be updated a alpha or beta package. For example apt:



$ apt-cache policy apt
apt:
Installed: 1.8.0~alpha3
Candidate: 1.8.0~beta1
Version table:
1.8.0~beta1 500
500 http://ftp.de.debian.org/debian testing/main amd64 Packages
*** 1.8.0~alpha3 100
100 /var/lib/dpkg/status
1.0.9.8.5 500
500 http://security.debian.org jessie/updates/main amd64 Packages
1.0.9.8.4 500
500 http://debian.mirrors.ovh.net/debian jessie/main amd64 Packages


I do not have a list of packages which have been upgraded,
this wouldn't be really much of an issue however, if I now disable the testing source and try to install anything there's many dispensary issues from mismatching version numbers.



Is there a way to downgrade all packages to the best candidate for the jessie source? Or get a list of all packaged that are installed from the tested source?










share|improve this question
















Another sysadmin added the following to sources.list:



deb http://ftp.de.debian.org/debian testing main


At some point in time a apt-get upgrade was run, causing most packages to be updated a alpha or beta package. For example apt:



$ apt-cache policy apt
apt:
Installed: 1.8.0~alpha3
Candidate: 1.8.0~beta1
Version table:
1.8.0~beta1 500
500 http://ftp.de.debian.org/debian testing/main amd64 Packages
*** 1.8.0~alpha3 100
100 /var/lib/dpkg/status
1.0.9.8.5 500
500 http://security.debian.org jessie/updates/main amd64 Packages
1.0.9.8.4 500
500 http://debian.mirrors.ovh.net/debian jessie/main amd64 Packages


I do not have a list of packages which have been upgraded,
this wouldn't be really much of an issue however, if I now disable the testing source and try to install anything there's many dispensary issues from mismatching version numbers.



Is there a way to downgrade all packages to the best candidate for the jessie source? Or get a list of all packaged that are installed from the tested source?







debian apt package-management upgrade






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 7 at 20:12









Seth

1,1791121




1,1791121










asked Feb 7 at 8:17









Tonis F. PiipTonis F. Piip

1111




1111




migrated from askubuntu.com Feb 7 at 19:32


This question came from our site for Ubuntu users and developers.









migrated from askubuntu.com Feb 7 at 19:32


This question came from our site for Ubuntu users and developers.









  • 4





    fyi: debian jessie is 8, testing or buster is 10. Your testing packages are from two versions ahead of the old-stable or jessie packages. Even if you push packages back, some of your .conf (config) files may have been upgraded beyond what the old release can handle (I've had this occur before, new options are set that old version couldn't cope with)

    – guiverc
    Feb 7 at 9:54











  • @A.B Fixed for Jessie , stretch , buster and Sid.

    – GAD3R
    Feb 7 at 21:04












  • 4





    fyi: debian jessie is 8, testing or buster is 10. Your testing packages are from two versions ahead of the old-stable or jessie packages. Even if you push packages back, some of your .conf (config) files may have been upgraded beyond what the old release can handle (I've had this occur before, new options are set that old version couldn't cope with)

    – guiverc
    Feb 7 at 9:54











  • @A.B Fixed for Jessie , stretch , buster and Sid.

    – GAD3R
    Feb 7 at 21:04







4




4





fyi: debian jessie is 8, testing or buster is 10. Your testing packages are from two versions ahead of the old-stable or jessie packages. Even if you push packages back, some of your .conf (config) files may have been upgraded beyond what the old release can handle (I've had this occur before, new options are set that old version couldn't cope with)

– guiverc
Feb 7 at 9:54





fyi: debian jessie is 8, testing or buster is 10. Your testing packages are from two versions ahead of the old-stable or jessie packages. Even if you push packages back, some of your .conf (config) files may have been upgraded beyond what the old release can handle (I've had this occur before, new options are set that old version couldn't cope with)

– guiverc
Feb 7 at 9:54













@A.B Fixed for Jessie , stretch , buster and Sid.

– GAD3R
Feb 7 at 21:04





@A.B Fixed for Jessie , stretch , buster and Sid.

– GAD3R
Feb 7 at 21:04










1 Answer
1






active

oldest

votes


















0














Backup your data, then edit your /etc/apt/sources.list by removing the testing repository.



Create a preferences file :



editor /etc/apt/preferences


Then past the following lines:



Package: *
Pin: release a=oldstable
Pin-Priority: 1001



AptPreferences



Note that a priority above 1000 will allow even downgrades no matter the version of the prioritary package. This means that you can use priority 1001 for a stable source if you want to downgrade to the stable versions of the packages you have installed (let's say from testing) on the system. this is not recommended unless the number of changes are minimal.




Save your file then run:



apt update
apt upgrade
apt dist-upgrade
apt autoremove


Emergency downgrading




Downgrading is not officially supported by the Debian by design. It should be done only as a part of emergency recovery process. Despite of this situation, it is known to work well in many incidents. For critical systems, you should backup all important data on the system after the recovery operation and re-install the new system from the scratch.







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',
    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%2f499346%2fdebian-testing-added-to-sources-list-how-to-undo-the-upgrades%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









    0














    Backup your data, then edit your /etc/apt/sources.list by removing the testing repository.



    Create a preferences file :



    editor /etc/apt/preferences


    Then past the following lines:



    Package: *
    Pin: release a=oldstable
    Pin-Priority: 1001



    AptPreferences



    Note that a priority above 1000 will allow even downgrades no matter the version of the prioritary package. This means that you can use priority 1001 for a stable source if you want to downgrade to the stable versions of the packages you have installed (let's say from testing) on the system. this is not recommended unless the number of changes are minimal.




    Save your file then run:



    apt update
    apt upgrade
    apt dist-upgrade
    apt autoremove


    Emergency downgrading




    Downgrading is not officially supported by the Debian by design. It should be done only as a part of emergency recovery process. Despite of this situation, it is known to work well in many incidents. For critical systems, you should backup all important data on the system after the recovery operation and re-install the new system from the scratch.







    share|improve this answer





























      0














      Backup your data, then edit your /etc/apt/sources.list by removing the testing repository.



      Create a preferences file :



      editor /etc/apt/preferences


      Then past the following lines:



      Package: *
      Pin: release a=oldstable
      Pin-Priority: 1001



      AptPreferences



      Note that a priority above 1000 will allow even downgrades no matter the version of the prioritary package. This means that you can use priority 1001 for a stable source if you want to downgrade to the stable versions of the packages you have installed (let's say from testing) on the system. this is not recommended unless the number of changes are minimal.




      Save your file then run:



      apt update
      apt upgrade
      apt dist-upgrade
      apt autoremove


      Emergency downgrading




      Downgrading is not officially supported by the Debian by design. It should be done only as a part of emergency recovery process. Despite of this situation, it is known to work well in many incidents. For critical systems, you should backup all important data on the system after the recovery operation and re-install the new system from the scratch.







      share|improve this answer



























        0












        0








        0







        Backup your data, then edit your /etc/apt/sources.list by removing the testing repository.



        Create a preferences file :



        editor /etc/apt/preferences


        Then past the following lines:



        Package: *
        Pin: release a=oldstable
        Pin-Priority: 1001



        AptPreferences



        Note that a priority above 1000 will allow even downgrades no matter the version of the prioritary package. This means that you can use priority 1001 for a stable source if you want to downgrade to the stable versions of the packages you have installed (let's say from testing) on the system. this is not recommended unless the number of changes are minimal.




        Save your file then run:



        apt update
        apt upgrade
        apt dist-upgrade
        apt autoremove


        Emergency downgrading




        Downgrading is not officially supported by the Debian by design. It should be done only as a part of emergency recovery process. Despite of this situation, it is known to work well in many incidents. For critical systems, you should backup all important data on the system after the recovery operation and re-install the new system from the scratch.







        share|improve this answer















        Backup your data, then edit your /etc/apt/sources.list by removing the testing repository.



        Create a preferences file :



        editor /etc/apt/preferences


        Then past the following lines:



        Package: *
        Pin: release a=oldstable
        Pin-Priority: 1001



        AptPreferences



        Note that a priority above 1000 will allow even downgrades no matter the version of the prioritary package. This means that you can use priority 1001 for a stable source if you want to downgrade to the stable versions of the packages you have installed (let's say from testing) on the system. this is not recommended unless the number of changes are minimal.




        Save your file then run:



        apt update
        apt upgrade
        apt dist-upgrade
        apt autoremove


        Emergency downgrading




        Downgrading is not officially supported by the Debian by design. It should be done only as a part of emergency recovery process. Despite of this situation, it is known to work well in many incidents. For critical systems, you should backup all important data on the system after the recovery operation and re-install the new system from the scratch.








        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Feb 7 at 20:55

























        answered Feb 7 at 20:50









        GAD3RGAD3R

        26.9k1756111




        26.9k1756111



























            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














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499346%2fdebian-testing-added-to-sources-list-how-to-undo-the-upgrades%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

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?