Failure to install aptitude using apt because of missing dependency even though dependency is installed
Clash Royale CLAN TAG#URR8PPP
When trying to install aptitude
with apt
this error is thrown:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
aptitude : Depends: libapt-pkg5.0 (>= 1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
However, when I attempt to install libapt-pkg5.0
it shows this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libapt-pkg5.0 is already the newest version (1.8.0~alpha3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I am on Debian 9.6.
debian apt dependencies aptitude
add a comment |
When trying to install aptitude
with apt
this error is thrown:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
aptitude : Depends: libapt-pkg5.0 (>= 1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
However, when I attempt to install libapt-pkg5.0
it shows this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libapt-pkg5.0 is already the newest version (1.8.0~alpha3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I am on Debian 9.6.
debian apt dependencies aptitude
2
Your installed version oflibapt-pkg5.0
comes from unstable; are you sure you’re using Debian 9.6?
– Stephen Kitt
Jan 26 at 18:02
Just checked, it appears I am using 9.7. I frequently get errors like this, how can I install the stable versions of all packages? My sources.list only has stable right now, but I did have to use unstable at some point.
– xcqforeva
Jan 26 at 18:13
add a comment |
When trying to install aptitude
with apt
this error is thrown:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
aptitude : Depends: libapt-pkg5.0 (>= 1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
However, when I attempt to install libapt-pkg5.0
it shows this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libapt-pkg5.0 is already the newest version (1.8.0~alpha3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I am on Debian 9.6.
debian apt dependencies aptitude
When trying to install aptitude
with apt
this error is thrown:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
aptitude : Depends: libapt-pkg5.0 (>= 1.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
However, when I attempt to install libapt-pkg5.0
it shows this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libapt-pkg5.0 is already the newest version (1.8.0~alpha3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I am on Debian 9.6.
debian apt dependencies aptitude
debian apt dependencies aptitude
edited Jan 26 at 16:25
Jeff Schaller
41.4k1056131
41.4k1056131
asked Jan 26 at 16:06
xcqforevaxcqforeva
83
83
2
Your installed version oflibapt-pkg5.0
comes from unstable; are you sure you’re using Debian 9.6?
– Stephen Kitt
Jan 26 at 18:02
Just checked, it appears I am using 9.7. I frequently get errors like this, how can I install the stable versions of all packages? My sources.list only has stable right now, but I did have to use unstable at some point.
– xcqforeva
Jan 26 at 18:13
add a comment |
2
Your installed version oflibapt-pkg5.0
comes from unstable; are you sure you’re using Debian 9.6?
– Stephen Kitt
Jan 26 at 18:02
Just checked, it appears I am using 9.7. I frequently get errors like this, how can I install the stable versions of all packages? My sources.list only has stable right now, but I did have to use unstable at some point.
– xcqforeva
Jan 26 at 18:13
2
2
Your installed version of
libapt-pkg5.0
comes from unstable; are you sure you’re using Debian 9.6?– Stephen Kitt
Jan 26 at 18:02
Your installed version of
libapt-pkg5.0
comes from unstable; are you sure you’re using Debian 9.6?– Stephen Kitt
Jan 26 at 18:02
Just checked, it appears I am using 9.7. I frequently get errors like this, how can I install the stable versions of all packages? My sources.list only has stable right now, but I did have to use unstable at some point.
– xcqforeva
Jan 26 at 18:13
Just checked, it appears I am using 9.7. I frequently get errors like this, how can I install the stable versions of all packages? My sources.list only has stable right now, but I did have to use unstable at some point.
– xcqforeva
Jan 26 at 18:13
add a comment |
1 Answer
1
active
oldest
votes
You installed an ex- testing/unstable package on your Debian 9 (stretch) system, which was not supposed to be done.
You can force a downgrade to stable by appending /stable
to the blocking package. But take note that downgrading packages is not supported. Downgrading parts of the packaging management system is thus dangerous: if something goes wrong, you might lose access to the apt-get
command.
This can be used multiple times with multiples packages in the same line if there are multiple related dependencies to solve at once (in case you upgraded all of apt
's related packages). By the way, 1.8.0~alpha3
has still the recent Debian vulnerability since it was fixed for buster in 1.8.0~alpha3.1
. This combined with the risk of a failure leads to:
apt-get -o Acquire::http::AllowRedirect=false update
apt-get -o Acquire::http::AllowRedirect=false -o APT::Clean-Installed=false install libapt-pkg5.0/stable
You'll probably have to add other related packages ( apt/stable
and possibly others) on the last line. This command should tell what packages have this same version 1.8.0~alpha3
, so would probably need to be added in the command above:
dpkg -l|awk '/^.i/ && $3 == "1.8.0~alpha3"'
After any such downgrade, it's prudent to reinstall again the same package(s) in a 2nd command:
apt-get --reinstall install libapt-pkg5.0
In the really unexpected case where this downgrade broke the apt-get
command, you still have the dpkg
command available and packages still in /var/cache/apt/archives/
to save you.
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%2f496900%2ffailure-to-install-aptitude-using-apt-because-of-missing-dependency-even-though%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 installed an ex- testing/unstable package on your Debian 9 (stretch) system, which was not supposed to be done.
You can force a downgrade to stable by appending /stable
to the blocking package. But take note that downgrading packages is not supported. Downgrading parts of the packaging management system is thus dangerous: if something goes wrong, you might lose access to the apt-get
command.
This can be used multiple times with multiples packages in the same line if there are multiple related dependencies to solve at once (in case you upgraded all of apt
's related packages). By the way, 1.8.0~alpha3
has still the recent Debian vulnerability since it was fixed for buster in 1.8.0~alpha3.1
. This combined with the risk of a failure leads to:
apt-get -o Acquire::http::AllowRedirect=false update
apt-get -o Acquire::http::AllowRedirect=false -o APT::Clean-Installed=false install libapt-pkg5.0/stable
You'll probably have to add other related packages ( apt/stable
and possibly others) on the last line. This command should tell what packages have this same version 1.8.0~alpha3
, so would probably need to be added in the command above:
dpkg -l|awk '/^.i/ && $3 == "1.8.0~alpha3"'
After any such downgrade, it's prudent to reinstall again the same package(s) in a 2nd command:
apt-get --reinstall install libapt-pkg5.0
In the really unexpected case where this downgrade broke the apt-get
command, you still have the dpkg
command available and packages still in /var/cache/apt/archives/
to save you.
add a comment |
You installed an ex- testing/unstable package on your Debian 9 (stretch) system, which was not supposed to be done.
You can force a downgrade to stable by appending /stable
to the blocking package. But take note that downgrading packages is not supported. Downgrading parts of the packaging management system is thus dangerous: if something goes wrong, you might lose access to the apt-get
command.
This can be used multiple times with multiples packages in the same line if there are multiple related dependencies to solve at once (in case you upgraded all of apt
's related packages). By the way, 1.8.0~alpha3
has still the recent Debian vulnerability since it was fixed for buster in 1.8.0~alpha3.1
. This combined with the risk of a failure leads to:
apt-get -o Acquire::http::AllowRedirect=false update
apt-get -o Acquire::http::AllowRedirect=false -o APT::Clean-Installed=false install libapt-pkg5.0/stable
You'll probably have to add other related packages ( apt/stable
and possibly others) on the last line. This command should tell what packages have this same version 1.8.0~alpha3
, so would probably need to be added in the command above:
dpkg -l|awk '/^.i/ && $3 == "1.8.0~alpha3"'
After any such downgrade, it's prudent to reinstall again the same package(s) in a 2nd command:
apt-get --reinstall install libapt-pkg5.0
In the really unexpected case where this downgrade broke the apt-get
command, you still have the dpkg
command available and packages still in /var/cache/apt/archives/
to save you.
add a comment |
You installed an ex- testing/unstable package on your Debian 9 (stretch) system, which was not supposed to be done.
You can force a downgrade to stable by appending /stable
to the blocking package. But take note that downgrading packages is not supported. Downgrading parts of the packaging management system is thus dangerous: if something goes wrong, you might lose access to the apt-get
command.
This can be used multiple times with multiples packages in the same line if there are multiple related dependencies to solve at once (in case you upgraded all of apt
's related packages). By the way, 1.8.0~alpha3
has still the recent Debian vulnerability since it was fixed for buster in 1.8.0~alpha3.1
. This combined with the risk of a failure leads to:
apt-get -o Acquire::http::AllowRedirect=false update
apt-get -o Acquire::http::AllowRedirect=false -o APT::Clean-Installed=false install libapt-pkg5.0/stable
You'll probably have to add other related packages ( apt/stable
and possibly others) on the last line. This command should tell what packages have this same version 1.8.0~alpha3
, so would probably need to be added in the command above:
dpkg -l|awk '/^.i/ && $3 == "1.8.0~alpha3"'
After any such downgrade, it's prudent to reinstall again the same package(s) in a 2nd command:
apt-get --reinstall install libapt-pkg5.0
In the really unexpected case where this downgrade broke the apt-get
command, you still have the dpkg
command available and packages still in /var/cache/apt/archives/
to save you.
You installed an ex- testing/unstable package on your Debian 9 (stretch) system, which was not supposed to be done.
You can force a downgrade to stable by appending /stable
to the blocking package. But take note that downgrading packages is not supported. Downgrading parts of the packaging management system is thus dangerous: if something goes wrong, you might lose access to the apt-get
command.
This can be used multiple times with multiples packages in the same line if there are multiple related dependencies to solve at once (in case you upgraded all of apt
's related packages). By the way, 1.8.0~alpha3
has still the recent Debian vulnerability since it was fixed for buster in 1.8.0~alpha3.1
. This combined with the risk of a failure leads to:
apt-get -o Acquire::http::AllowRedirect=false update
apt-get -o Acquire::http::AllowRedirect=false -o APT::Clean-Installed=false install libapt-pkg5.0/stable
You'll probably have to add other related packages ( apt/stable
and possibly others) on the last line. This command should tell what packages have this same version 1.8.0~alpha3
, so would probably need to be added in the command above:
dpkg -l|awk '/^.i/ && $3 == "1.8.0~alpha3"'
After any such downgrade, it's prudent to reinstall again the same package(s) in a 2nd command:
apt-get --reinstall install libapt-pkg5.0
In the really unexpected case where this downgrade broke the apt-get
command, you still have the dpkg
command available and packages still in /var/cache/apt/archives/
to save you.
answered Jan 26 at 19:25
A.BA.B
4,9421726
4,9421726
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%2f496900%2ffailure-to-install-aptitude-using-apt-because-of-missing-dependency-even-though%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
2
Your installed version of
libapt-pkg5.0
comes from unstable; are you sure you’re using Debian 9.6?– Stephen Kitt
Jan 26 at 18:02
Just checked, it appears I am using 9.7. I frequently get errors like this, how can I install the stable versions of all packages? My sources.list only has stable right now, but I did have to use unstable at some point.
– xcqforeva
Jan 26 at 18:13