Does aptitude use safe-upgrade or full-upgrade in visual mode?
Sometimes I use Aptitude in visual mode[1] to install and upgrade packages.
When I upgrade from the command line using apt or aptitude I often use full-upgrade instead of safe-upgrade[2] because I run the testing flavour of Debian, but which one is used in Aptitude visual mode?
Basically, what really happens when I press U?
If it's one way or another, is there a way to configure the default behaviour, or to decide manually which one to use?
[1] The GUI. Some call this a TUI.
[2] Formerly called upgrade and dist-upgrade respectively.
debian upgrade aptitude
asked Jun 12 '17 at 17:00
pipepipe
316115
add a comment |
Sometimes I use Aptitude in visual mode[1] to install and upgrade packages.
When I upgrade from the command line using apt or aptitude I often use full-upgrade instead of safe-upgrade[2] because I run the testing flavour of Debian, but which one is used in Aptitude visual mode?
Basically, what really happens when I press U?
If it's one way or another, is there a way to configure the default behaviour, or to decide manually which one to use?
[1] The GUI. Some call this a TUI.
[2] Formerly called upgrade and dist-upgrade respectively.
debian upgrade aptitude
asked Jun 12 '17 at 17:00
pipepipe
316115
add a comment |
Sometimes I use Aptitude in visual mode[1] to install and upgrade packages.
When I upgrade from the command line using apt or aptitude I often use full-upgrade instead of safe-upgrade[2] because I run the testing flavour of Debian, but which one is used in Aptitude visual mode?
Basically, what really happens when I press U?
If it's one way or another, is there a way to configure the default behaviour, or to decide manually which one to use?
[1] The GUI. Some call this a TUI.
[2] Formerly called upgrade and dist-upgrade respectively.
debian upgrade aptitude
asked Jun 12 '17 at 17:00
pipepipe
316115
Sometimes I use Aptitude in visual mode[1] to install and upgrade packages.
When I upgrade from the command line using apt or aptitude I often use full-upgrade instead of safe-upgrade[2] because I run the testing flavour of Debian, but which one is used in Aptitude visual mode?
Basically, what really happens when I press U?
If it's one way or another, is there a way to configure the default behaviour, or to decide manually which one to use?
[1] The GUI. Some call this a TUI.
[2] Formerly called upgrade and dist-upgrade respectively.
debian upgrade aptitude
debian upgrade aptitude
asked Jun 12 '17 at 17:00
pipepipe
316115
asked Jun 12 '17 at 17:00
pipepipe
316115
edited Jun 13 '17 at 8:49
pipe
asked Jun 12 '17 at 17:00
pipepipe
316115
asked Jun 12 '17 at 17:00
pipepipe
316115
asked Jun 12 '17 at 17:00
pipepipe
316115
316115
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Neither.
When you press U, every package which can be upgraded is flagged for upgrade, except for packages that are held back or would be upgraded to a forbidden version. This isn’t the same as either safe-upgrade or full-upgrade on the command line, because conflicts aren’t resolved fully: the upgrade flagging can result in (tentatively) broken packages, which you’ll see indicated by the number of broken packages, but Aptitude won’t do anything about those breakages simply as a result of pressing U. You can resolve any conflicts manually, or you can ask Aptitude to show you the various resolution possibilities using e, . and , to navigate, and ! to apply a resolution.
In the code itself, the U handling is closer to safe-upgrade than to full-upgrade, because it ignores removals initially. But as mentioned above, it’s not quite the same.
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f370708%2fdoes-aptitude-use-safe-upgrade-or-full-upgrade-in-visual-mode%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
Neither.
When you press U, every package which can be upgraded is flagged for upgrade, except for packages that are held back or would be upgraded to a forbidden version. This isn’t the same as either safe-upgrade or full-upgrade on the command line, because conflicts aren’t resolved fully: the upgrade flagging can result in (tentatively) broken packages, which you’ll see indicated by the number of broken packages, but Aptitude won’t do anything about those breakages simply as a result of pressing U. You can resolve any conflicts manually, or you can ask Aptitude to show you the various resolution possibilities using e, . and , to navigate, and ! to apply a resolution.
In the code itself, the U handling is closer to safe-upgrade than to full-upgrade, because it ignores removals initially. But as mentioned above, it’s not quite the same.
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
add a comment |
Neither.
When you press U, every package which can be upgraded is flagged for upgrade, except for packages that are held back or would be upgraded to a forbidden version. This isn’t the same as either safe-upgrade or full-upgrade on the command line, because conflicts aren’t resolved fully: the upgrade flagging can result in (tentatively) broken packages, which you’ll see indicated by the number of broken packages, but Aptitude won’t do anything about those breakages simply as a result of pressing U. You can resolve any conflicts manually, or you can ask Aptitude to show you the various resolution possibilities using e, . and , to navigate, and ! to apply a resolution.
In the code itself, the U handling is closer to safe-upgrade than to full-upgrade, because it ignores removals initially. But as mentioned above, it’s not quite the same.
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
add a comment |
Neither.
When you press U, every package which can be upgraded is flagged for upgrade, except for packages that are held back or would be upgraded to a forbidden version. This isn’t the same as either safe-upgrade or full-upgrade on the command line, because conflicts aren’t resolved fully: the upgrade flagging can result in (tentatively) broken packages, which you’ll see indicated by the number of broken packages, but Aptitude won’t do anything about those breakages simply as a result of pressing U. You can resolve any conflicts manually, or you can ask Aptitude to show you the various resolution possibilities using e, . and , to navigate, and ! to apply a resolution.
In the code itself, the U handling is closer to safe-upgrade than to full-upgrade, because it ignores removals initially. But as mentioned above, it’s not quite the same.
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
Neither.
When you press U, every package which can be upgraded is flagged for upgrade, except for packages that are held back or would be upgraded to a forbidden version. This isn’t the same as either safe-upgrade or full-upgrade on the command line, because conflicts aren’t resolved fully: the upgrade flagging can result in (tentatively) broken packages, which you’ll see indicated by the number of broken packages, but Aptitude won’t do anything about those breakages simply as a result of pressing U. You can resolve any conflicts manually, or you can ask Aptitude to show you the various resolution possibilities using e, . and , to navigate, and ! to apply a resolution.
In the code itself, the U handling is closer to safe-upgrade than to full-upgrade, because it ignores removals initially. But as mentioned above, it’s not quite the same.
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
edited Jan 31 at 16:39
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
answered Jun 12 '17 at 18:29
Stephen KittStephen Kitt
171k24386462
171k24386462
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f370708%2fdoes-aptitude-use-safe-upgrade-or-full-upgrade-in-visual-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
