![]() ![]() *The following packages could receive security updates with UA Infra: ESM service enabled: The following package was automatically installed and is no longer required:Ġ uuendatud, 0 värskelt paigaldatud, 0 eemaldada ja 0 uuendamata. Perhaps I missed something, but that's where I'm stopping this investigation. Here again, both binaries with either command perform the same steps. Resolver_fail = APT::Upgrade::Upgrade(Cache, UpgradeMode, &Progress) If (distUpgradeMode = true || UpgradeMode != APT::Upgrade::ALLOW_EVERYTHING) Later in the callstack there's this interesting part in DoCacheManipulationFromCommandLine() line 681: bool const distUpgradeMode = strcmp(CmdL.FileList, "dist-upgrade") = 0 || strcmp(CmdL.FileList, "full-upgrade") = 0 The DispatchCommandLine function then ends up calling the DoDistUpgrade handler. _config->MoveSubTree(conf.c_str(), nullptr) applies options prefixed by Binary::apt::apt or Binary::apt::apt-get depending on the binary used. Theĭownloaded debs will be kept in the cache directory after theyīinar圜ommandSpecificConfiguration(argv, CmdCalled) both binaries do the same thing for all these commands: "upgrade", "dist-upgrade", "full-upgrade". Please note that the behavior of apt-get is unchanged. Removed from the /var/cache/apt/archives cache directory. This is an actual difference between apt and apt-get and is explained in the NEWS file:Īfter packages are successfully installed by apt(8), ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |