Why is there a mismatch between “packages can be updated” and `apt list --upgradeable`?

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








up vote
2
down vote

favorite












When I login to my Ubuntu VM, I get the following message informing me that 8 packages are upgradeable:



Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-112-generic x86_64)

* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage

8 packages can be updated.
0 updates are security updates.


Last login: Mon Jan 29 14:55:34 2018 from 172.16.117.1


However, when I issue an apt list --upgradeable I get 26 packages.



$ apt list --upgradeable 
Listing... Done
cloud-initramfs-copymods/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
cloud-initramfs-dyn-netconf/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
cpp-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
distro-info-data/xenial-updates,xenial-updates 0.28ubuntu0.7 all [upgradable from: 0.28ubuntu0.3]
g++-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
gcc-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
gcc-5-base/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libasan2/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libatomic1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libcc1-0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libcilkrts5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libgcc-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libgnutls-openssl27/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
libgnutls30/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
libgomp1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libitm1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
liblsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libmpx0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libquadmath0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libseccomp2/xenial-updates 2.3.1-2.1ubuntu2~16.04.1 amd64 [upgradable from: 2.2.3-3ubuntu3]
libstdc++-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libstdc++6/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libtsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
libubsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
python3-update-manager/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]
update-manager-core/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]


Why the mismatch?







share|improve this question


























    up vote
    2
    down vote

    favorite












    When I login to my Ubuntu VM, I get the following message informing me that 8 packages are upgradeable:



    Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-112-generic x86_64)

    * Documentation: https://help.ubuntu.com
    * Management: https://landscape.canonical.com
    * Support: https://ubuntu.com/advantage

    8 packages can be updated.
    0 updates are security updates.


    Last login: Mon Jan 29 14:55:34 2018 from 172.16.117.1


    However, when I issue an apt list --upgradeable I get 26 packages.



    $ apt list --upgradeable 
    Listing... Done
    cloud-initramfs-copymods/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
    cloud-initramfs-dyn-netconf/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
    cpp-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    distro-info-data/xenial-updates,xenial-updates 0.28ubuntu0.7 all [upgradable from: 0.28ubuntu0.3]
    g++-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    gcc-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    gcc-5-base/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libasan2/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libatomic1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libcc1-0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libcilkrts5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libgcc-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libgnutls-openssl27/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
    libgnutls30/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
    libgomp1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libitm1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    liblsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libmpx0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libquadmath0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libseccomp2/xenial-updates 2.3.1-2.1ubuntu2~16.04.1 amd64 [upgradable from: 2.2.3-3ubuntu3]
    libstdc++-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libstdc++6/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libtsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    libubsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
    python3-update-manager/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]
    update-manager-core/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]


    Why the mismatch?







    share|improve this question
























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      When I login to my Ubuntu VM, I get the following message informing me that 8 packages are upgradeable:



      Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-112-generic x86_64)

      * Documentation: https://help.ubuntu.com
      * Management: https://landscape.canonical.com
      * Support: https://ubuntu.com/advantage

      8 packages can be updated.
      0 updates are security updates.


      Last login: Mon Jan 29 14:55:34 2018 from 172.16.117.1


      However, when I issue an apt list --upgradeable I get 26 packages.



      $ apt list --upgradeable 
      Listing... Done
      cloud-initramfs-copymods/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
      cloud-initramfs-dyn-netconf/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
      cpp-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      distro-info-data/xenial-updates,xenial-updates 0.28ubuntu0.7 all [upgradable from: 0.28ubuntu0.3]
      g++-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      gcc-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      gcc-5-base/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libasan2/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libatomic1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libcc1-0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libcilkrts5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libgcc-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libgnutls-openssl27/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
      libgnutls30/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
      libgomp1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libitm1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      liblsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libmpx0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libquadmath0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libseccomp2/xenial-updates 2.3.1-2.1ubuntu2~16.04.1 amd64 [upgradable from: 2.2.3-3ubuntu3]
      libstdc++-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libstdc++6/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libtsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libubsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      python3-update-manager/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]
      update-manager-core/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]


      Why the mismatch?







      share|improve this question














      When I login to my Ubuntu VM, I get the following message informing me that 8 packages are upgradeable:



      Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-112-generic x86_64)

      * Documentation: https://help.ubuntu.com
      * Management: https://landscape.canonical.com
      * Support: https://ubuntu.com/advantage

      8 packages can be updated.
      0 updates are security updates.


      Last login: Mon Jan 29 14:55:34 2018 from 172.16.117.1


      However, when I issue an apt list --upgradeable I get 26 packages.



      $ apt list --upgradeable 
      Listing... Done
      cloud-initramfs-copymods/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
      cloud-initramfs-dyn-netconf/xenial-updates,xenial-updates 0.27ubuntu1.5 all [upgradable from: 0.27ubuntu1.4]
      cpp-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      distro-info-data/xenial-updates,xenial-updates 0.28ubuntu0.7 all [upgradable from: 0.28ubuntu0.3]
      g++-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      gcc-5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      gcc-5-base/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libasan2/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libatomic1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libcc1-0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libcilkrts5/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libgcc-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libgnutls-openssl27/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
      libgnutls30/xenial-updates 3.4.10-4ubuntu1.4 amd64 [upgradable from: 3.4.10-4ubuntu1.3]
      libgomp1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libitm1/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      liblsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libmpx0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libquadmath0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libseccomp2/xenial-updates 2.3.1-2.1ubuntu2~16.04.1 amd64 [upgradable from: 2.2.3-3ubuntu3]
      libstdc++-5-dev/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libstdc++6/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libtsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      libubsan0/xenial-updates 5.4.0-6ubuntu1~16.04.6 amd64 [upgradable from: 5.4.0-6ubuntu1~16.04.5]
      python3-update-manager/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]
      update-manager-core/xenial-updates,xenial-updates 1:16.04.10 all [upgradable from: 1:16.04.7]


      Why the mismatch?









      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 30 at 20:27

























      asked Jan 30 at 17:09









      Stephen Rasku

      7511




      7511




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          They run at different times.



          Items are uploaded into the repositories at all hours (not once daily), so if you compare --upgradable at different times of day, you will get more and more results as the day goes on.



          Apt does NOT check for packages upon startup - that would needlessly delay startup. The login message (part of Message Of The Day [motd]) is generated during the daily run of apt-daily...during some previous session (like yesterday). The text is generated and saved for your next login. It's meant as a reminder, and that lack of accuracy is a well-known minor issue.






          share|improve this answer
















          • 1




            unattended-upgrades may change situation too. You can add it to answer. So we have four mechanisms: /etc/apt/apt.conf.d/10periodic + /etc/apt/apt.conf.d/20auto-upgrades, apt-daily systemd timers (systemctl list-timers --all | grep apt), unattended-upgrades (/lib/systemd/system/unattended-upgrades.service + /etc/apt/apt.conf.d/50unattended-upgrades) and user commands - apt-get/apt/aptitude update and so on.
            – N0rbert
            Jan 31 at 9:04











          • It seems to to have caught up now. I accept your answer.
            – Stephen Rasku
            Feb 1 at 15:06










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          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: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1001429%2fwhy-is-there-a-mismatch-between-packages-can-be-updated-and-apt-list-upgrad%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          3
          down vote



          accepted










          They run at different times.



          Items are uploaded into the repositories at all hours (not once daily), so if you compare --upgradable at different times of day, you will get more and more results as the day goes on.



          Apt does NOT check for packages upon startup - that would needlessly delay startup. The login message (part of Message Of The Day [motd]) is generated during the daily run of apt-daily...during some previous session (like yesterday). The text is generated and saved for your next login. It's meant as a reminder, and that lack of accuracy is a well-known minor issue.






          share|improve this answer
















          • 1




            unattended-upgrades may change situation too. You can add it to answer. So we have four mechanisms: /etc/apt/apt.conf.d/10periodic + /etc/apt/apt.conf.d/20auto-upgrades, apt-daily systemd timers (systemctl list-timers --all | grep apt), unattended-upgrades (/lib/systemd/system/unattended-upgrades.service + /etc/apt/apt.conf.d/50unattended-upgrades) and user commands - apt-get/apt/aptitude update and so on.
            – N0rbert
            Jan 31 at 9:04











          • It seems to to have caught up now. I accept your answer.
            – Stephen Rasku
            Feb 1 at 15:06














          up vote
          3
          down vote



          accepted










          They run at different times.



          Items are uploaded into the repositories at all hours (not once daily), so if you compare --upgradable at different times of day, you will get more and more results as the day goes on.



          Apt does NOT check for packages upon startup - that would needlessly delay startup. The login message (part of Message Of The Day [motd]) is generated during the daily run of apt-daily...during some previous session (like yesterday). The text is generated and saved for your next login. It's meant as a reminder, and that lack of accuracy is a well-known minor issue.






          share|improve this answer
















          • 1




            unattended-upgrades may change situation too. You can add it to answer. So we have four mechanisms: /etc/apt/apt.conf.d/10periodic + /etc/apt/apt.conf.d/20auto-upgrades, apt-daily systemd timers (systemctl list-timers --all | grep apt), unattended-upgrades (/lib/systemd/system/unattended-upgrades.service + /etc/apt/apt.conf.d/50unattended-upgrades) and user commands - apt-get/apt/aptitude update and so on.
            – N0rbert
            Jan 31 at 9:04











          • It seems to to have caught up now. I accept your answer.
            – Stephen Rasku
            Feb 1 at 15:06












          up vote
          3
          down vote



          accepted







          up vote
          3
          down vote



          accepted






          They run at different times.



          Items are uploaded into the repositories at all hours (not once daily), so if you compare --upgradable at different times of day, you will get more and more results as the day goes on.



          Apt does NOT check for packages upon startup - that would needlessly delay startup. The login message (part of Message Of The Day [motd]) is generated during the daily run of apt-daily...during some previous session (like yesterday). The text is generated and saved for your next login. It's meant as a reminder, and that lack of accuracy is a well-known minor issue.






          share|improve this answer












          They run at different times.



          Items are uploaded into the repositories at all hours (not once daily), so if you compare --upgradable at different times of day, you will get more and more results as the day goes on.



          Apt does NOT check for packages upon startup - that would needlessly delay startup. The login message (part of Message Of The Day [motd]) is generated during the daily run of apt-daily...during some previous session (like yesterday). The text is generated and saved for your next login. It's meant as a reminder, and that lack of accuracy is a well-known minor issue.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 30 at 18:04









          user535733

          5,66722436




          5,66722436







          • 1




            unattended-upgrades may change situation too. You can add it to answer. So we have four mechanisms: /etc/apt/apt.conf.d/10periodic + /etc/apt/apt.conf.d/20auto-upgrades, apt-daily systemd timers (systemctl list-timers --all | grep apt), unattended-upgrades (/lib/systemd/system/unattended-upgrades.service + /etc/apt/apt.conf.d/50unattended-upgrades) and user commands - apt-get/apt/aptitude update and so on.
            – N0rbert
            Jan 31 at 9:04











          • It seems to to have caught up now. I accept your answer.
            – Stephen Rasku
            Feb 1 at 15:06












          • 1




            unattended-upgrades may change situation too. You can add it to answer. So we have four mechanisms: /etc/apt/apt.conf.d/10periodic + /etc/apt/apt.conf.d/20auto-upgrades, apt-daily systemd timers (systemctl list-timers --all | grep apt), unattended-upgrades (/lib/systemd/system/unattended-upgrades.service + /etc/apt/apt.conf.d/50unattended-upgrades) and user commands - apt-get/apt/aptitude update and so on.
            – N0rbert
            Jan 31 at 9:04











          • It seems to to have caught up now. I accept your answer.
            – Stephen Rasku
            Feb 1 at 15:06







          1




          1




          unattended-upgrades may change situation too. You can add it to answer. So we have four mechanisms: /etc/apt/apt.conf.d/10periodic + /etc/apt/apt.conf.d/20auto-upgrades, apt-daily systemd timers (systemctl list-timers --all | grep apt), unattended-upgrades (/lib/systemd/system/unattended-upgrades.service + /etc/apt/apt.conf.d/50unattended-upgrades) and user commands - apt-get/apt/aptitude update and so on.
          – N0rbert
          Jan 31 at 9:04





          unattended-upgrades may change situation too. You can add it to answer. So we have four mechanisms: /etc/apt/apt.conf.d/10periodic + /etc/apt/apt.conf.d/20auto-upgrades, apt-daily systemd timers (systemctl list-timers --all | grep apt), unattended-upgrades (/lib/systemd/system/unattended-upgrades.service + /etc/apt/apt.conf.d/50unattended-upgrades) and user commands - apt-get/apt/aptitude update and so on.
          – N0rbert
          Jan 31 at 9:04













          It seems to to have caught up now. I accept your answer.
          – Stephen Rasku
          Feb 1 at 15:06




          It seems to to have caught up now. I accept your answer.
          – Stephen Rasku
          Feb 1 at 15:06












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1001429%2fwhy-is-there-a-mismatch-between-packages-can-be-updated-and-apt-list-upgrad%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491