![]() ![]() This will generally include the GNU C library for reasons already explained. Therefore this will pull in the unstable slrn's dependencies from unstable if they are of a higher version number, and they generally will be. This means: temporarily treat all packages in unstable on an equal footing with the packages in stable. ![]() This is much more likely to work, but you generally don't want to do it. One can also do apt-get install -t unstable slrn To be more precise, it uses priority numbers. Means: use the unstable slrn but for all other packages only use the versions from stable. Note that because a package has been compiled against a higher version of library does not necessarily require a higher version of that library, but it is often the case. Therefore the unstable slrn requires a higher numbered version of libc6 than is available for stable. ![]() The C library is central to any Unix-like operating system, and GNU C library is the version that Linux-based operating systems generally use.) So, what went wrong? The problem is that the version of libc6 that the unstable slrn was compiled against is different (and has a higher version number) than the one available on Debian stable. Slrn : Depends: libc6 (>= 2.15) but 2.13-38+deb7u1 is to be installedĮ: Unable to correct problems, you have held broken packages.ĭespite the error produced by apt, there are no broken packages here. The following packages have unmet dependencies: The following information may help to resolve the situation: Requested an impossible situation or if you are using the unstableĭistribution that some required packages have not yet been created Selected version '1.0.1-10' (Debian:testing ) for 'slrn' What would this look like? # apt-get install slrn/unstable What does this mean for the user? Suppose for example that you are trying to install say slrn from Debian unstable to Debian stable. Debian currently does not have a good way of making version dependencies "tight" - a shorthand way of saying that the version dependency is exactly as restrictive as necessary. ![]() Such operating systems depend heavily on shared libraries, and these dependencies are often very tightly version-dependent often much more so than necessary. The reason has to do with the nature of a Linux-based binary distribution like Debian. This will most likely not go well, unless testing/unstable happen to very close to stable at that moment. In general, this procedure will not work well.Ĭonsider for example the case where one is trying to install a binary package from testing/unstable directly on stable. This may or not work, depending on what version you are running, and how much newer the package is. The first thing that every beginner tries to do it to install the binary package directly on your version of Debian. You want a more recent version of a package than is available to you. Suppose you are running some version of a Debian-based distribution. Or, if you have sufficient rep, you can ping me in chat.) Directly installing binary packages from a newer version of Debian - not the answer. (If you have questions/comments about this answer, please add a comment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |