[SOLVED] how to make apt-get ignore broken packages

gujedan · 04-21-2011, 05:08 PM

what should not be mentioned:
*disabling "Automatically fix broken packages before installing or removing" in aptitude -- because it does not work

*editing /var/lib/dkpg/status -- not related to apt-get really

* -m or -f options of apt-get -- because they do not help me in any way

* downloading the package manually and using dpkg --force-depends-version -i <package> -- again, not apt-get

I need the --just shut the fuck up and dl&install the darn package
option immediately.

alan_ri · 04-21-2011, 05:37 PM

What do you want to install?

gujedan · 04-21-2011, 05:43 PM

Quote:

Originally Posted by alan_ri

What do you want to install?

I would like to be able to dl&install any package at all without apt giving me that shit about broken packages

TobiSGD · 04-21-2011, 05:48 PM

It would help if you actually tell us why

Code:

apt-get install aria2

doesn't work on your system. Because that is just the

Quote:

--just shut the f*** up and dl&install the darn package
option

gujedan · 04-21-2011, 05:54 PM

Code:

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

TobiSGD · 04-21-2011, 05:57 PM

Please post your /etc/apt/sources.list.

gujedan · 04-21-2011, 06:00 PM

deb http://security.debian.org/ squeeze/updates main contrib
deb-src http://security.debian.org/ squeeze/updates main contrib
deb http://http.us.debian.org/debian/ squeeze non-free contrib main
deb http://www.lamaresh.net/apt squeeze main

TobiSGD · 04-21-2011, 06:07 PM

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.

gujedan · 04-21-2011, 06:12 PM

Quote:

Originally Posted by TobiSGD

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?

TobiSGD · 04-21-2011, 06:20 PM

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.

gujedan · 04-21-2011, 06:24 PM

Quote:

Originally Posted by TobiSGD

Apt-get has no option to ignore broken packages.

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)

TobiSGD · 04-21-2011, 06:29 PM

Quote:

Originally Posted by gujedan

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.

gujedan · 04-22-2011, 04:39 AM

Quote:

Originally Posted by TobiSGD

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.

TobiSGD · 04-22-2011, 04:50 AM

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.

gujedan · 04-22-2011, 05:20 AM

those things require way too much work, I'm probably just gonna go with rewriting the necessary components of a major distro