Bug#106911: apt still seriously broken
>--[Anthony Towns]--<aj@azure.humbug.org.au>
> First, if you're doing a major upgrade, you should be using dist-upgrade,
> not just upgrade.
Using dselect would break as well.
> Second, if you're having problems like this you should try to diagnose
> them a little bit, rather than just dumping some logs and demanding
apt-get install'ing any package whose dependencies touch any of those
packages mentioned.
> I'm not sure why you think
You must have mind reading capabilities. Unfortunately, they're as broken as
apt.
> will help resolve your problem when none of the other reports did.
The hint given in the mail linked in one of the bug report responses to
reduce the size of the sources.list is the wrong hint. The point is not the
size but the simple fact to have different releases - I had all of stable,
testing and unstable. Having just unstable works, as well as having only
unstable and testing. stable and unstable seem to work as well ("seem"
because there have been no new packages with fulfillable dependencies since
yesterday).
So if apt would refuse to run with a proper error message if more than two
releases are used in the sources.list, it would at least be a work-around.
Getting it in the freeze in the 'quality' it is now in with breaking and
giving no serious hint at why is, well, questionable.
Reply to: