Why I'm unable to install a package with apt











up vote
1
down vote

favorite












On Debian 9 I want to install the package libicu57 (repository), but for some reason I can't:



$ sudo apt install libicu57
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu57 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu57' has no installation candidate


In my /etc/apt/sources.list is this (beside others):



deb http://ftp.cvut.cz/debian/ testing main non-free contrib


What is the problem and how to solve it?










share|improve this question


















  • 3




    Testing is Debian 10 and frequent hiccups is the reason many people keeps on stable for production vms
    – Rui F Ribeiro
    Nov 27 at 22:23






  • 3




    Do you need the testing version? It's also available in stable: packages.debian.org/stretch/libicu57
    – K7AAY
    Nov 27 at 23:00






  • 2




    testing is not Debian 9, it's 10, which doesn't contain libicu57, because it was replaced by libicu60 and libicu63.
    – Ipor Sircer
    Nov 27 at 23:24












  • packages.debian.org/buster/libicu57 Buster is Testing right?
    – Michael Prokopec
    Nov 27 at 23:28






  • 3




    @Michael look at the architectures for which that package is available (at the bottom of the page).
    – Stephen Kitt
    Nov 28 at 5:30















up vote
1
down vote

favorite












On Debian 9 I want to install the package libicu57 (repository), but for some reason I can't:



$ sudo apt install libicu57
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu57 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu57' has no installation candidate


In my /etc/apt/sources.list is this (beside others):



deb http://ftp.cvut.cz/debian/ testing main non-free contrib


What is the problem and how to solve it?










share|improve this question


















  • 3




    Testing is Debian 10 and frequent hiccups is the reason many people keeps on stable for production vms
    – Rui F Ribeiro
    Nov 27 at 22:23






  • 3




    Do you need the testing version? It's also available in stable: packages.debian.org/stretch/libicu57
    – K7AAY
    Nov 27 at 23:00






  • 2




    testing is not Debian 9, it's 10, which doesn't contain libicu57, because it was replaced by libicu60 and libicu63.
    – Ipor Sircer
    Nov 27 at 23:24












  • packages.debian.org/buster/libicu57 Buster is Testing right?
    – Michael Prokopec
    Nov 27 at 23:28






  • 3




    @Michael look at the architectures for which that package is available (at the bottom of the page).
    – Stephen Kitt
    Nov 28 at 5:30













up vote
1
down vote

favorite









up vote
1
down vote

favorite











On Debian 9 I want to install the package libicu57 (repository), but for some reason I can't:



$ sudo apt install libicu57
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu57 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu57' has no installation candidate


In my /etc/apt/sources.list is this (beside others):



deb http://ftp.cvut.cz/debian/ testing main non-free contrib


What is the problem and how to solve it?










share|improve this question













On Debian 9 I want to install the package libicu57 (repository), but for some reason I can't:



$ sudo apt install libicu57
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu57 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu57' has no installation candidate


In my /etc/apt/sources.list is this (beside others):



deb http://ftp.cvut.cz/debian/ testing main non-free contrib


What is the problem and how to solve it?







debian apt






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 27 at 22:11









Martin Heralecký

440514




440514








  • 3




    Testing is Debian 10 and frequent hiccups is the reason many people keeps on stable for production vms
    – Rui F Ribeiro
    Nov 27 at 22:23






  • 3




    Do you need the testing version? It's also available in stable: packages.debian.org/stretch/libicu57
    – K7AAY
    Nov 27 at 23:00






  • 2




    testing is not Debian 9, it's 10, which doesn't contain libicu57, because it was replaced by libicu60 and libicu63.
    – Ipor Sircer
    Nov 27 at 23:24












  • packages.debian.org/buster/libicu57 Buster is Testing right?
    – Michael Prokopec
    Nov 27 at 23:28






  • 3




    @Michael look at the architectures for which that package is available (at the bottom of the page).
    – Stephen Kitt
    Nov 28 at 5:30














  • 3




    Testing is Debian 10 and frequent hiccups is the reason many people keeps on stable for production vms
    – Rui F Ribeiro
    Nov 27 at 22:23






  • 3




    Do you need the testing version? It's also available in stable: packages.debian.org/stretch/libicu57
    – K7AAY
    Nov 27 at 23:00






  • 2




    testing is not Debian 9, it's 10, which doesn't contain libicu57, because it was replaced by libicu60 and libicu63.
    – Ipor Sircer
    Nov 27 at 23:24












  • packages.debian.org/buster/libicu57 Buster is Testing right?
    – Michael Prokopec
    Nov 27 at 23:28






  • 3




    @Michael look at the architectures for which that package is available (at the bottom of the page).
    – Stephen Kitt
    Nov 28 at 5:30








3




3




Testing is Debian 10 and frequent hiccups is the reason many people keeps on stable for production vms
– Rui F Ribeiro
Nov 27 at 22:23




Testing is Debian 10 and frequent hiccups is the reason many people keeps on stable for production vms
– Rui F Ribeiro
Nov 27 at 22:23




3




3




Do you need the testing version? It's also available in stable: packages.debian.org/stretch/libicu57
– K7AAY
Nov 27 at 23:00




Do you need the testing version? It's also available in stable: packages.debian.org/stretch/libicu57
– K7AAY
Nov 27 at 23:00




2




2




testing is not Debian 9, it's 10, which doesn't contain libicu57, because it was replaced by libicu60 and libicu63.
– Ipor Sircer
Nov 27 at 23:24






testing is not Debian 9, it's 10, which doesn't contain libicu57, because it was replaced by libicu60 and libicu63.
– Ipor Sircer
Nov 27 at 23:24














packages.debian.org/buster/libicu57 Buster is Testing right?
– Michael Prokopec
Nov 27 at 23:28




packages.debian.org/buster/libicu57 Buster is Testing right?
– Michael Prokopec
Nov 27 at 23:28




3




3




@Michael look at the architectures for which that package is available (at the bottom of the page).
– Stephen Kitt
Nov 28 at 5:30




@Michael look at the architectures for which that package is available (at the bottom of the page).
– Stephen Kitt
Nov 28 at 5:30










1 Answer
1






active

oldest

votes

















up vote
0
down vote













Issue at Hand



You wish to install libicu57 from the testing repo. However, if you are using x86 or amd64 you cannot install this package as it is only available in testing for armel mips and mipsel.



You have in your sources.list an entry for Debian Testing (Buster or 10). You report that you are using Debian 9 (Stretch or Stable). You have created FrankenDebian. You need to configure your sources.list properly remove this entry and rollback or remove any packages you have installed from the testing repo to correct this.



After you have done this, if it is the ARM variant of libicu57 that you require you can look into cross compiling solutions or better yet virtualization.



Fix sources.list



First step is to verify that your repositories to your /etc/apt/sources.list are good. I would recommend you use /etc/apt/sources.list.d/ where each repository is it's own file, but you can do this in just one file.



#stable.list
deb http://deb.debian.org stable main contrib non-free
deb-src http://deb.debian.org stable main contrib non-free

#updates.list
deb http://deb.debian.org stable-updates main contrib non-free
deb-src http://deb.debian.org stable-updates main contrib non-free

#security.list
deb http://deb.debian.org/debian-secruity stable/updates main contrib non-free
deb-src http://deb.debian.org/debian-secruity stable/updates main contrib non-free


Your sources.list should look something like this. You can change the exact http address to match your desired mirror. If you must absolutely have a testing repo, add the entry in a similar manner as above and use apt preferences to maintain some level of sanity. Apt-pinning should be used sparingly as it can lead to the creation of FrankenDebian.



Install software



Now all that is left is installing your package, which can be done with this command:



 apt-get install libicu57


or



apt-get install -t stable libicu57 **or** apt-get install libicu57/stable


You can also choose to install the package you desire from source or download it and its dependencies from the Debian Packages site and install them with dpkg -i [packageName].deb



This should install libicu57. Please comment if there is another error and we con look further into solutions. The next part is going to cover if you absolutely require the ARM or MIPS versions of software you can look into cross-compiling, or creating a virtual environment with the appropriate instruction set to safely use this version of the library.



Here is the Debian Wiki entry on Multiarch and here is the Wiki for cross-compiling. You can follow these steps to make the appropriate configuration changes to dpkg and what not to cross-compile.



However you cannot have multiple versions of the same software installed!



So if the ARM version requires dependencies and libraries that you already have a version of in x86 or amd64 then you cannot do this. The alternative is to create a virtual machine of Debian for ARM using the virtualization solution of your choice that uses the correct instruction set.



KVM is a good choice but you can use whatever solution best fits your use case.



Conclusion



Please read over this in its entirety. In fact, please make sure you read over all the links I have provided thoroughly before running any commands. If you have any questions or concerns about this post, do not hesitate to ask me. If there are any corrections or misconceptions in this answer please inform me. I can update the post as necessary.



Best of Luck!






share|improve this answer



















  • 2




    Installing libicu57 from testing isn’t going to work, it’s not available there.
    – Stephen Kitt
    Nov 28 at 5:33










  • @StephenKitt, holy moly I did not pay attention. Let me correct that. Is is even possible to create a FrankenDebian of different instruction sets?
    – kemotep
    Nov 28 at 12:18






  • 1




    You can’t create a FrankenMultiArchDebian ;-) because all arches have to match up — so you can create a multi-arch FrankenDebian, but you can’t install packages with different versions for different architectures. However I don’t think that’s the problem here; I think the OP removed all stable repositories from the available sources, so your answer is mostly on track.
    – Stephen Kitt
    Nov 28 at 12:56












  • @StephenKitt I will clean it up. Thanks for the additional context.
    – kemotep
    Nov 28 at 13:37











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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484534%2fwhy-im-unable-to-install-a-package-with-apt%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








up vote
0
down vote













Issue at Hand



You wish to install libicu57 from the testing repo. However, if you are using x86 or amd64 you cannot install this package as it is only available in testing for armel mips and mipsel.



You have in your sources.list an entry for Debian Testing (Buster or 10). You report that you are using Debian 9 (Stretch or Stable). You have created FrankenDebian. You need to configure your sources.list properly remove this entry and rollback or remove any packages you have installed from the testing repo to correct this.



After you have done this, if it is the ARM variant of libicu57 that you require you can look into cross compiling solutions or better yet virtualization.



Fix sources.list



First step is to verify that your repositories to your /etc/apt/sources.list are good. I would recommend you use /etc/apt/sources.list.d/ where each repository is it's own file, but you can do this in just one file.



#stable.list
deb http://deb.debian.org stable main contrib non-free
deb-src http://deb.debian.org stable main contrib non-free

#updates.list
deb http://deb.debian.org stable-updates main contrib non-free
deb-src http://deb.debian.org stable-updates main contrib non-free

#security.list
deb http://deb.debian.org/debian-secruity stable/updates main contrib non-free
deb-src http://deb.debian.org/debian-secruity stable/updates main contrib non-free


Your sources.list should look something like this. You can change the exact http address to match your desired mirror. If you must absolutely have a testing repo, add the entry in a similar manner as above and use apt preferences to maintain some level of sanity. Apt-pinning should be used sparingly as it can lead to the creation of FrankenDebian.



Install software



Now all that is left is installing your package, which can be done with this command:



 apt-get install libicu57


or



apt-get install -t stable libicu57 **or** apt-get install libicu57/stable


You can also choose to install the package you desire from source or download it and its dependencies from the Debian Packages site and install them with dpkg -i [packageName].deb



This should install libicu57. Please comment if there is another error and we con look further into solutions. The next part is going to cover if you absolutely require the ARM or MIPS versions of software you can look into cross-compiling, or creating a virtual environment with the appropriate instruction set to safely use this version of the library.



Here is the Debian Wiki entry on Multiarch and here is the Wiki for cross-compiling. You can follow these steps to make the appropriate configuration changes to dpkg and what not to cross-compile.



However you cannot have multiple versions of the same software installed!



So if the ARM version requires dependencies and libraries that you already have a version of in x86 or amd64 then you cannot do this. The alternative is to create a virtual machine of Debian for ARM using the virtualization solution of your choice that uses the correct instruction set.



KVM is a good choice but you can use whatever solution best fits your use case.



Conclusion



Please read over this in its entirety. In fact, please make sure you read over all the links I have provided thoroughly before running any commands. If you have any questions or concerns about this post, do not hesitate to ask me. If there are any corrections or misconceptions in this answer please inform me. I can update the post as necessary.



Best of Luck!






share|improve this answer



















  • 2




    Installing libicu57 from testing isn’t going to work, it’s not available there.
    – Stephen Kitt
    Nov 28 at 5:33










  • @StephenKitt, holy moly I did not pay attention. Let me correct that. Is is even possible to create a FrankenDebian of different instruction sets?
    – kemotep
    Nov 28 at 12:18






  • 1




    You can’t create a FrankenMultiArchDebian ;-) because all arches have to match up — so you can create a multi-arch FrankenDebian, but you can’t install packages with different versions for different architectures. However I don’t think that’s the problem here; I think the OP removed all stable repositories from the available sources, so your answer is mostly on track.
    – Stephen Kitt
    Nov 28 at 12:56












  • @StephenKitt I will clean it up. Thanks for the additional context.
    – kemotep
    Nov 28 at 13:37















up vote
0
down vote













Issue at Hand



You wish to install libicu57 from the testing repo. However, if you are using x86 or amd64 you cannot install this package as it is only available in testing for armel mips and mipsel.



You have in your sources.list an entry for Debian Testing (Buster or 10). You report that you are using Debian 9 (Stretch or Stable). You have created FrankenDebian. You need to configure your sources.list properly remove this entry and rollback or remove any packages you have installed from the testing repo to correct this.



After you have done this, if it is the ARM variant of libicu57 that you require you can look into cross compiling solutions or better yet virtualization.



Fix sources.list



First step is to verify that your repositories to your /etc/apt/sources.list are good. I would recommend you use /etc/apt/sources.list.d/ where each repository is it's own file, but you can do this in just one file.



#stable.list
deb http://deb.debian.org stable main contrib non-free
deb-src http://deb.debian.org stable main contrib non-free

#updates.list
deb http://deb.debian.org stable-updates main contrib non-free
deb-src http://deb.debian.org stable-updates main contrib non-free

#security.list
deb http://deb.debian.org/debian-secruity stable/updates main contrib non-free
deb-src http://deb.debian.org/debian-secruity stable/updates main contrib non-free


Your sources.list should look something like this. You can change the exact http address to match your desired mirror. If you must absolutely have a testing repo, add the entry in a similar manner as above and use apt preferences to maintain some level of sanity. Apt-pinning should be used sparingly as it can lead to the creation of FrankenDebian.



Install software



Now all that is left is installing your package, which can be done with this command:



 apt-get install libicu57


or



apt-get install -t stable libicu57 **or** apt-get install libicu57/stable


You can also choose to install the package you desire from source or download it and its dependencies from the Debian Packages site and install them with dpkg -i [packageName].deb



This should install libicu57. Please comment if there is another error and we con look further into solutions. The next part is going to cover if you absolutely require the ARM or MIPS versions of software you can look into cross-compiling, or creating a virtual environment with the appropriate instruction set to safely use this version of the library.



Here is the Debian Wiki entry on Multiarch and here is the Wiki for cross-compiling. You can follow these steps to make the appropriate configuration changes to dpkg and what not to cross-compile.



However you cannot have multiple versions of the same software installed!



So if the ARM version requires dependencies and libraries that you already have a version of in x86 or amd64 then you cannot do this. The alternative is to create a virtual machine of Debian for ARM using the virtualization solution of your choice that uses the correct instruction set.



KVM is a good choice but you can use whatever solution best fits your use case.



Conclusion



Please read over this in its entirety. In fact, please make sure you read over all the links I have provided thoroughly before running any commands. If you have any questions or concerns about this post, do not hesitate to ask me. If there are any corrections or misconceptions in this answer please inform me. I can update the post as necessary.



Best of Luck!






share|improve this answer



















  • 2




    Installing libicu57 from testing isn’t going to work, it’s not available there.
    – Stephen Kitt
    Nov 28 at 5:33










  • @StephenKitt, holy moly I did not pay attention. Let me correct that. Is is even possible to create a FrankenDebian of different instruction sets?
    – kemotep
    Nov 28 at 12:18






  • 1




    You can’t create a FrankenMultiArchDebian ;-) because all arches have to match up — so you can create a multi-arch FrankenDebian, but you can’t install packages with different versions for different architectures. However I don’t think that’s the problem here; I think the OP removed all stable repositories from the available sources, so your answer is mostly on track.
    – Stephen Kitt
    Nov 28 at 12:56












  • @StephenKitt I will clean it up. Thanks for the additional context.
    – kemotep
    Nov 28 at 13:37













up vote
0
down vote










up vote
0
down vote









Issue at Hand



You wish to install libicu57 from the testing repo. However, if you are using x86 or amd64 you cannot install this package as it is only available in testing for armel mips and mipsel.



You have in your sources.list an entry for Debian Testing (Buster or 10). You report that you are using Debian 9 (Stretch or Stable). You have created FrankenDebian. You need to configure your sources.list properly remove this entry and rollback or remove any packages you have installed from the testing repo to correct this.



After you have done this, if it is the ARM variant of libicu57 that you require you can look into cross compiling solutions or better yet virtualization.



Fix sources.list



First step is to verify that your repositories to your /etc/apt/sources.list are good. I would recommend you use /etc/apt/sources.list.d/ where each repository is it's own file, but you can do this in just one file.



#stable.list
deb http://deb.debian.org stable main contrib non-free
deb-src http://deb.debian.org stable main contrib non-free

#updates.list
deb http://deb.debian.org stable-updates main contrib non-free
deb-src http://deb.debian.org stable-updates main contrib non-free

#security.list
deb http://deb.debian.org/debian-secruity stable/updates main contrib non-free
deb-src http://deb.debian.org/debian-secruity stable/updates main contrib non-free


Your sources.list should look something like this. You can change the exact http address to match your desired mirror. If you must absolutely have a testing repo, add the entry in a similar manner as above and use apt preferences to maintain some level of sanity. Apt-pinning should be used sparingly as it can lead to the creation of FrankenDebian.



Install software



Now all that is left is installing your package, which can be done with this command:



 apt-get install libicu57


or



apt-get install -t stable libicu57 **or** apt-get install libicu57/stable


You can also choose to install the package you desire from source or download it and its dependencies from the Debian Packages site and install them with dpkg -i [packageName].deb



This should install libicu57. Please comment if there is another error and we con look further into solutions. The next part is going to cover if you absolutely require the ARM or MIPS versions of software you can look into cross-compiling, or creating a virtual environment with the appropriate instruction set to safely use this version of the library.



Here is the Debian Wiki entry on Multiarch and here is the Wiki for cross-compiling. You can follow these steps to make the appropriate configuration changes to dpkg and what not to cross-compile.



However you cannot have multiple versions of the same software installed!



So if the ARM version requires dependencies and libraries that you already have a version of in x86 or amd64 then you cannot do this. The alternative is to create a virtual machine of Debian for ARM using the virtualization solution of your choice that uses the correct instruction set.



KVM is a good choice but you can use whatever solution best fits your use case.



Conclusion



Please read over this in its entirety. In fact, please make sure you read over all the links I have provided thoroughly before running any commands. If you have any questions or concerns about this post, do not hesitate to ask me. If there are any corrections or misconceptions in this answer please inform me. I can update the post as necessary.



Best of Luck!






share|improve this answer














Issue at Hand



You wish to install libicu57 from the testing repo. However, if you are using x86 or amd64 you cannot install this package as it is only available in testing for armel mips and mipsel.



You have in your sources.list an entry for Debian Testing (Buster or 10). You report that you are using Debian 9 (Stretch or Stable). You have created FrankenDebian. You need to configure your sources.list properly remove this entry and rollback or remove any packages you have installed from the testing repo to correct this.



After you have done this, if it is the ARM variant of libicu57 that you require you can look into cross compiling solutions or better yet virtualization.



Fix sources.list



First step is to verify that your repositories to your /etc/apt/sources.list are good. I would recommend you use /etc/apt/sources.list.d/ where each repository is it's own file, but you can do this in just one file.



#stable.list
deb http://deb.debian.org stable main contrib non-free
deb-src http://deb.debian.org stable main contrib non-free

#updates.list
deb http://deb.debian.org stable-updates main contrib non-free
deb-src http://deb.debian.org stable-updates main contrib non-free

#security.list
deb http://deb.debian.org/debian-secruity stable/updates main contrib non-free
deb-src http://deb.debian.org/debian-secruity stable/updates main contrib non-free


Your sources.list should look something like this. You can change the exact http address to match your desired mirror. If you must absolutely have a testing repo, add the entry in a similar manner as above and use apt preferences to maintain some level of sanity. Apt-pinning should be used sparingly as it can lead to the creation of FrankenDebian.



Install software



Now all that is left is installing your package, which can be done with this command:



 apt-get install libicu57


or



apt-get install -t stable libicu57 **or** apt-get install libicu57/stable


You can also choose to install the package you desire from source or download it and its dependencies from the Debian Packages site and install them with dpkg -i [packageName].deb



This should install libicu57. Please comment if there is another error and we con look further into solutions. The next part is going to cover if you absolutely require the ARM or MIPS versions of software you can look into cross-compiling, or creating a virtual environment with the appropriate instruction set to safely use this version of the library.



Here is the Debian Wiki entry on Multiarch and here is the Wiki for cross-compiling. You can follow these steps to make the appropriate configuration changes to dpkg and what not to cross-compile.



However you cannot have multiple versions of the same software installed!



So if the ARM version requires dependencies and libraries that you already have a version of in x86 or amd64 then you cannot do this. The alternative is to create a virtual machine of Debian for ARM using the virtualization solution of your choice that uses the correct instruction set.



KVM is a good choice but you can use whatever solution best fits your use case.



Conclusion



Please read over this in its entirety. In fact, please make sure you read over all the links I have provided thoroughly before running any commands. If you have any questions or concerns about this post, do not hesitate to ask me. If there are any corrections or misconceptions in this answer please inform me. I can update the post as necessary.



Best of Luck!







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 28 at 14:07

























answered Nov 28 at 1:34









kemotep

1,8773617




1,8773617








  • 2




    Installing libicu57 from testing isn’t going to work, it’s not available there.
    – Stephen Kitt
    Nov 28 at 5:33










  • @StephenKitt, holy moly I did not pay attention. Let me correct that. Is is even possible to create a FrankenDebian of different instruction sets?
    – kemotep
    Nov 28 at 12:18






  • 1




    You can’t create a FrankenMultiArchDebian ;-) because all arches have to match up — so you can create a multi-arch FrankenDebian, but you can’t install packages with different versions for different architectures. However I don’t think that’s the problem here; I think the OP removed all stable repositories from the available sources, so your answer is mostly on track.
    – Stephen Kitt
    Nov 28 at 12:56












  • @StephenKitt I will clean it up. Thanks for the additional context.
    – kemotep
    Nov 28 at 13:37














  • 2




    Installing libicu57 from testing isn’t going to work, it’s not available there.
    – Stephen Kitt
    Nov 28 at 5:33










  • @StephenKitt, holy moly I did not pay attention. Let me correct that. Is is even possible to create a FrankenDebian of different instruction sets?
    – kemotep
    Nov 28 at 12:18






  • 1




    You can’t create a FrankenMultiArchDebian ;-) because all arches have to match up — so you can create a multi-arch FrankenDebian, but you can’t install packages with different versions for different architectures. However I don’t think that’s the problem here; I think the OP removed all stable repositories from the available sources, so your answer is mostly on track.
    – Stephen Kitt
    Nov 28 at 12:56












  • @StephenKitt I will clean it up. Thanks for the additional context.
    – kemotep
    Nov 28 at 13:37








2




2




Installing libicu57 from testing isn’t going to work, it’s not available there.
– Stephen Kitt
Nov 28 at 5:33




Installing libicu57 from testing isn’t going to work, it’s not available there.
– Stephen Kitt
Nov 28 at 5:33












@StephenKitt, holy moly I did not pay attention. Let me correct that. Is is even possible to create a FrankenDebian of different instruction sets?
– kemotep
Nov 28 at 12:18




@StephenKitt, holy moly I did not pay attention. Let me correct that. Is is even possible to create a FrankenDebian of different instruction sets?
– kemotep
Nov 28 at 12:18




1




1




You can’t create a FrankenMultiArchDebian ;-) because all arches have to match up — so you can create a multi-arch FrankenDebian, but you can’t install packages with different versions for different architectures. However I don’t think that’s the problem here; I think the OP removed all stable repositories from the available sources, so your answer is mostly on track.
– Stephen Kitt
Nov 28 at 12:56






You can’t create a FrankenMultiArchDebian ;-) because all arches have to match up — so you can create a multi-arch FrankenDebian, but you can’t install packages with different versions for different architectures. However I don’t think that’s the problem here; I think the OP removed all stable repositories from the available sources, so your answer is mostly on track.
– Stephen Kitt
Nov 28 at 12:56














@StephenKitt I will clean it up. Thanks for the additional context.
– kemotep
Nov 28 at 13:37




@StephenKitt I will clean it up. Thanks for the additional context.
– kemotep
Nov 28 at 13:37


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484534%2fwhy-im-unable-to-install-a-package-with-apt%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Entries order in /etc/network/interfaces

新発田市

Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)