Debian: apt-get upgrade says “The following packages have been kept back” for various mariadb packages
I am running Debian 9 (stretch) and have just tried to run apt-get update and apt-get upgrade in order to update my (test) webserver as part of regular maintenance.
apt-get upgrade says:
The following packages have been kept back:
linux-image-amd64 mariadb-client-10.1 mariadb-server mariadb-server-10.1 mariadb-server-core-10.1
I understand that apt-get upgrade is, sensibly, cautious about package updates, and will only update already installed packages, rather than bringing in any new additional dependencies already. (I have already seen this older related question.)
I know that I could instead run apt-get dist-upgrade in order to "force" the dependencies to be installed. I am just wondering if there is any particular reason why these MariaDB updates have been held back, and if there is any way to tell whether it might to risky to install them regardless?
(Yes, this is only a test server, so it would not be the worst thing if I tried the upgrade and it failed somehow (and I would then know that I should ignore those updates for the live server), but I am just wondering if there is any way to find out what the issue with these packages might be (such as finding out what version would be being expected to be installed, and whether there might be anything in the Debian package release notes that I could refer to)?)
Currently, I have the following versions installed:
- mysql Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
- Server version: 10.1.26-MariaDB-0+deb9u1 Debian 9.1
My main concern is to ensure that my server is up to date with security updates, as far as possible.
debian apt mariadb
asked Jan 7 at 16:10
dave559dave559
589
add a comment |
I am running Debian 9 (stretch) and have just tried to run apt-get update and apt-get upgrade in order to update my (test) webserver as part of regular maintenance.
apt-get upgrade says:
The following packages have been kept back:
linux-image-amd64 mariadb-client-10.1 mariadb-server mariadb-server-10.1 mariadb-server-core-10.1
I understand that apt-get upgrade is, sensibly, cautious about package updates, and will only update already installed packages, rather than bringing in any new additional dependencies already. (I have already seen this older related question.)
I know that I could instead run apt-get dist-upgrade in order to "force" the dependencies to be installed. I am just wondering if there is any particular reason why these MariaDB updates have been held back, and if there is any way to tell whether it might to risky to install them regardless?
(Yes, this is only a test server, so it would not be the worst thing if I tried the upgrade and it failed somehow (and I would then know that I should ignore those updates for the live server), but I am just wondering if there is any way to find out what the issue with these packages might be (such as finding out what version would be being expected to be installed, and whether there might be anything in the Debian package release notes that I could refer to)?)
Currently, I have the following versions installed:
- mysql Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
- Server version: 10.1.26-MariaDB-0+deb9u1 Debian 9.1
My main concern is to ensure that my server is up to date with security updates, as far as possible.
debian apt mariadb
asked Jan 7 at 16:10
dave559dave559
589
add a comment |
I am running Debian 9 (stretch) and have just tried to run apt-get update and apt-get upgrade in order to update my (test) webserver as part of regular maintenance.
apt-get upgrade says:
The following packages have been kept back:
linux-image-amd64 mariadb-client-10.1 mariadb-server mariadb-server-10.1 mariadb-server-core-10.1
I understand that apt-get upgrade is, sensibly, cautious about package updates, and will only update already installed packages, rather than bringing in any new additional dependencies already. (I have already seen this older related question.)
I know that I could instead run apt-get dist-upgrade in order to "force" the dependencies to be installed. I am just wondering if there is any particular reason why these MariaDB updates have been held back, and if there is any way to tell whether it might to risky to install them regardless?
(Yes, this is only a test server, so it would not be the worst thing if I tried the upgrade and it failed somehow (and I would then know that I should ignore those updates for the live server), but I am just wondering if there is any way to find out what the issue with these packages might be (such as finding out what version would be being expected to be installed, and whether there might be anything in the Debian package release notes that I could refer to)?)
Currently, I have the following versions installed:
- mysql Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
- Server version: 10.1.26-MariaDB-0+deb9u1 Debian 9.1
My main concern is to ensure that my server is up to date with security updates, as far as possible.
debian apt mariadb
asked Jan 7 at 16:10
dave559dave559
589
I am running Debian 9 (stretch) and have just tried to run apt-get update and apt-get upgrade in order to update my (test) webserver as part of regular maintenance.
apt-get upgrade says:
The following packages have been kept back:
linux-image-amd64 mariadb-client-10.1 mariadb-server mariadb-server-10.1 mariadb-server-core-10.1
I understand that apt-get upgrade is, sensibly, cautious about package updates, and will only update already installed packages, rather than bringing in any new additional dependencies already. (I have already seen this older related question.)
I know that I could instead run apt-get dist-upgrade in order to "force" the dependencies to be installed. I am just wondering if there is any particular reason why these MariaDB updates have been held back, and if there is any way to tell whether it might to risky to install them regardless?
(Yes, this is only a test server, so it would not be the worst thing if I tried the upgrade and it failed somehow (and I would then know that I should ignore those updates for the live server), but I am just wondering if there is any way to find out what the issue with these packages might be (such as finding out what version would be being expected to be installed, and whether there might be anything in the Debian package release notes that I could refer to)?)
Currently, I have the following versions installed:
- mysql Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
- Server version: 10.1.26-MariaDB-0+deb9u1 Debian 9.1
My main concern is to ensure that my server is up to date with security updates, as far as possible.
debian apt mariadb
debian apt mariadb
asked Jan 7 at 16:10
dave559dave559
589
asked Jan 7 at 16:10
dave559dave559
589
asked Jan 7 at 16:10
dave559dave559
589
asked Jan 7 at 16:10
dave559dave559
589
asked Jan 7 at 16:10
dave559dave559
589
589
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can find a package’s changelog by going to its package page (“https://packages.debian.org/packagename”), and looking for a link to the “Developer Information” on the right-hand side. (There’s also a “Debian Changelog” link, but it doesn’t always work.) On the resulting Package Tracker page, look for the latest stable security version on the left-hand side, and click on the icon with a checkmark. In your case, you’re missing:
these changes for MariaDB;
these changes for the kernel.
In both cases, as you suspect, apt-get upgrade isn’t upgrading because the upgrades require installing new packages; in MariaDB’s case, libconfig-inifiles-perl, and in the kernel’s case, the new kernel ABI packages. To install these new packages without going for a full dist-upgrade (which can also remove packages), run
apt-get upgrade --with-new-pkgs
or
apt upgrade
(apt upgrade behaves like apt-get upgrade --with-new-pkgs, favouring user-friendliness over consistency).
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
Thank you, that is so helpful! I was aware of the packages website, but didn't really know how to make use of it to find out more information (as you say, sometimes the Changelog link does not work). I also did not know aboutapt(as opposed toapt-get), very useful, and does sound potentially easier to use.
– dave559
Jan 7 at 16:39
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%2f493027%2fdebian-apt-get-upgrade-says-the-following-packages-have-been-kept-back-for-va%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
You can find a package’s changelog by going to its package page (“https://packages.debian.org/packagename”), and looking for a link to the “Developer Information” on the right-hand side. (There’s also a “Debian Changelog” link, but it doesn’t always work.) On the resulting Package Tracker page, look for the latest stable security version on the left-hand side, and click on the icon with a checkmark. In your case, you’re missing:
these changes for MariaDB;
these changes for the kernel.
In both cases, as you suspect, apt-get upgrade isn’t upgrading because the upgrades require installing new packages; in MariaDB’s case, libconfig-inifiles-perl, and in the kernel’s case, the new kernel ABI packages. To install these new packages without going for a full dist-upgrade (which can also remove packages), run
apt-get upgrade --with-new-pkgs
or
apt upgrade
(apt upgrade behaves like apt-get upgrade --with-new-pkgs, favouring user-friendliness over consistency).
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
Thank you, that is so helpful! I was aware of the packages website, but didn't really know how to make use of it to find out more information (as you say, sometimes the Changelog link does not work). I also did not know aboutapt(as opposed toapt-get), very useful, and does sound potentially easier to use.
– dave559
Jan 7 at 16:39
add a comment |
You can find a package’s changelog by going to its package page (“https://packages.debian.org/packagename”), and looking for a link to the “Developer Information” on the right-hand side. (There’s also a “Debian Changelog” link, but it doesn’t always work.) On the resulting Package Tracker page, look for the latest stable security version on the left-hand side, and click on the icon with a checkmark. In your case, you’re missing:
these changes for MariaDB;
these changes for the kernel.
In both cases, as you suspect, apt-get upgrade isn’t upgrading because the upgrades require installing new packages; in MariaDB’s case, libconfig-inifiles-perl, and in the kernel’s case, the new kernel ABI packages. To install these new packages without going for a full dist-upgrade (which can also remove packages), run
apt-get upgrade --with-new-pkgs
or
apt upgrade
(apt upgrade behaves like apt-get upgrade --with-new-pkgs, favouring user-friendliness over consistency).
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
Thank you, that is so helpful! I was aware of the packages website, but didn't really know how to make use of it to find out more information (as you say, sometimes the Changelog link does not work). I also did not know aboutapt(as opposed toapt-get), very useful, and does sound potentially easier to use.
– dave559
Jan 7 at 16:39
add a comment |
You can find a package’s changelog by going to its package page (“https://packages.debian.org/packagename”), and looking for a link to the “Developer Information” on the right-hand side. (There’s also a “Debian Changelog” link, but it doesn’t always work.) On the resulting Package Tracker page, look for the latest stable security version on the left-hand side, and click on the icon with a checkmark. In your case, you’re missing:
these changes for MariaDB;
these changes for the kernel.
In both cases, as you suspect, apt-get upgrade isn’t upgrading because the upgrades require installing new packages; in MariaDB’s case, libconfig-inifiles-perl, and in the kernel’s case, the new kernel ABI packages. To install these new packages without going for a full dist-upgrade (which can also remove packages), run
apt-get upgrade --with-new-pkgs
or
apt upgrade
(apt upgrade behaves like apt-get upgrade --with-new-pkgs, favouring user-friendliness over consistency).
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
You can find a package’s changelog by going to its package page (“https://packages.debian.org/packagename”), and looking for a link to the “Developer Information” on the right-hand side. (There’s also a “Debian Changelog” link, but it doesn’t always work.) On the resulting Package Tracker page, look for the latest stable security version on the left-hand side, and click on the icon with a checkmark. In your case, you’re missing:
these changes for MariaDB;
these changes for the kernel.
In both cases, as you suspect, apt-get upgrade isn’t upgrading because the upgrades require installing new packages; in MariaDB’s case, libconfig-inifiles-perl, and in the kernel’s case, the new kernel ABI packages. To install these new packages without going for a full dist-upgrade (which can also remove packages), run
apt-get upgrade --with-new-pkgs
or
apt upgrade
(apt upgrade behaves like apt-get upgrade --with-new-pkgs, favouring user-friendliness over consistency).
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
answered Jan 7 at 16:26
Stephen KittStephen Kitt
168k24378455
168k24378455
Thank you, that is so helpful! I was aware of the packages website, but didn't really know how to make use of it to find out more information (as you say, sometimes the Changelog link does not work). I also did not know aboutapt(as opposed toapt-get), very useful, and does sound potentially easier to use.
– dave559
Jan 7 at 16:39
add a comment |
Thank you, that is so helpful! I was aware of the packages website, but didn't really know how to make use of it to find out more information (as you say, sometimes the Changelog link does not work). I also did not know aboutapt(as opposed toapt-get), very useful, and does sound potentially easier to use.
– dave559
Jan 7 at 16:39
Thank you, that is so helpful! I was aware of the packages website, but didn't really know how to make use of it to find out more information (as you say, sometimes the Changelog link does not work). I also did not know about
apt (as opposed to apt-get), very useful, and does sound potentially easier to use.– dave559
Jan 7 at 16:39
Thank you, that is so helpful! I was aware of the packages website, but didn't really know how to make use of it to find out more information (as you say, sometimes the Changelog link does not work). I also did not know about
apt (as opposed to apt-get), very useful, and does sound potentially easier to use.– dave559
Jan 7 at 16:39
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%2f493027%2fdebian-apt-get-upgrade-says-the-following-packages-have-been-kept-back-for-va%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
