[SOLVED] how to make apt-get ignore broken packages
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
gnome : Depends: totem-mozilla but it is not going to be installed
Depends: epiphany-extensions but it is not going to be installed
gnome-core : Depends: epiphany-browser (>= 2.30) but it is not going to be installed or
gnome-www-browser
Depends: totem (>= 2.30) but it is not going to be installed
gnome-desktop-environment : Depends: ekiga (>= 3.2.6) but it is not going to be installed
Depends: empathy (>= 2.30) but it is not going to be installed
Depends: totem-plugins (>= 2.30) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
I am not sure, but I think that I read somewhere that the US-mirrors have problems in the last time. Change it to a different mirror, update the database and try it again.
I am not sure, but I think that I read somewhere that the US-mirrors have problems in the last time. Change it to a different mirror, update the database and try it again.
I'm sorry but I cannot see how the sources file is relevant to my question at all. And all the US-mirrors work just fine as I have previously installed quite a few packages with apt-get.
My questions stands: how do I make apt-get skip checking for broken packages and just dl&install what I want?
Apt-get has no option to ignore broken packages. And it seems to me that either your package database or your mirror is not containing all the packages, since it is obvious that apt-get can't find packages that should be available even if you had only enabled the main repositories. Therefore the question for your sources.list and the recommendation to change the mirror.
okay finally we get to the root of this thing. So I just need to rewrite apt-get or find another distro. And who the hell was stupid enough to not add apt-get an ignore option? (rhetorical question, I can read it from the man page)
And who the hell was stupid enough to not add apt-get an ignore option? (rhetorical question, I can read it from the man page)
This makes absolutely no sense. Why should a package manager have an option to maintain a broken system? Wouldn't it be better to actually fix the system, instead of simply ignoring the symptoms? If you have broken dependencies your system is very likely to malfunction in a specific function, simply ignoring that will not help you.
This makes absolutely no sense. Why should a package manager have an option to maintain a broken system? Wouldn't it be better to actually fix the system, instead of simply ignoring the symptoms? If you have broken dependencies your system is very likely to malfunction in a specific function, simply ignoring that will not help you.
The reason I use linux is because it enables me to do stuff I want. I don't care if it should or should not be done, but the bottom line is that I must be able to do it. If I want to screw up my fs by running fsck on a mounted partition then that is what I'm gonna do and that functionality has to be provided (and is, although you are given a warning before continuing).
There is nothing that pisses me off more than seeing "Access denied", "You can't do that" and other shit like that on my own system. What I want to do, I do. And if I want to maintain a broken system then that is exactly what I'm going to do.
Then go for a LFS install, you will have the absolute power to break your system. Or use Slackware, dependency management on that system has to be done by the user. It is not the fault of the distro or the package-manager. You have chosen a distro that has, amongst others, stability as main goal. If you want to willfully break your system I would consider that a rather poor choice.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.