[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: is the whole unstable still broken by gcc-5?

Виталий Филиппов <vitalif@yourcmc.ru> writes:

> apt-get dist-upgrade tries to remove the following packages:

There's tons of noise in there that actually should be removed, like most
of the libraries (which have newer, conflicting versions), but also some
stuff that really shouldn't be removed.

What does apt-get upgrade do for you right now?  Does it make any forward
progress?  You tried three commands, but none of them were that one, which
is my go-to as the first step.

> My sources.list contains sid, experimental and jessie-updates (+ oibaf
> graphics-drivers ppa)

Do you have experimental there for a specific reason?  If not, I'd try
taking it out.  If the resolver is getting confused and deciding to try to
install experimental packages, that could send it down blind alleys, since
perl in experimental is not installable at the moment (IIRC).

I'm somewhat worried that your problems are actually caused by the oibaf
graphics-drivers PPA, although I'm not sure.  Most of the removals look
like removing all of KDE, which makes me think something isn't working
right with the Qt upgrades.  I'm not using KDE, so that might explain why
I'm not seeing the same thing.

> If I request 'apt-get install libreoffice' it says:

> 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:

Thanks, this bit of output is the part that's actually useful.
Unfortunately, none of these indicates an actual root problem, just "is
not going to be installed".  One thing that can be helpful is to chase
these dependencies down with apt-get install so that you can get more
specific errors.  For example, try:

% apt-get install libreoffice-base

and see *why* it's not going to be installed.  It's probably going to list
several other packages that it depends on that won't be installed, and you
will hopefully either get an actual error, like a conflict, or a tractable
problem that the resolver can figure out by removing some libraries and
installing some new ones.

> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused
> by held packages.

Do you have any held packages?  The resolver might be arriving at really
bad solutions because it's trying to work around your holds.

>> 2. Don't use apt-get dist-upgrade routinely.  There's a reason why it's
>> not the default!  Usually apt-get upgrade is what you want, at least
>> until you get down to just a few lingering packages.  Then, you can try
>> dist-upgrade and see if it's just a few conflicting libraries.  That's
>> the way I always handle upgrades, and I rarely have any of these
>> problems.

> Ok, I understand that... I always verify what apt-get wants to do before
> applying it.

apt-get upgrade will also do that.  It's strictly more conservative than
apt-get dist-upgrade.

When there are large and complex upgrades, it often helps the resolver to
run apt-get upgrade to completion first, repeatedly if necessary until it
doesn't find more to do, and then try dist-upgrade.  Often the resolver
does better with less variables to try to track.

Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Reply to: