Le 14.10.2013 16:38, Frank McCormick a écrit :
On 14/10/13 09:52 AM, berenger.mo...@neutralite.org wrote:
Le 13.10.2013 19:44, Frank McCormick a écrit :
On 13/10/13 01:02 PM, Chris Bannister wrote:
On Sat, Oct 12, 2013 at 01:10:14PM -0300, msl09 wrote:
Oh I have fond memories of aptitude breaking my system. Once it
suggested me to remove most of my system, including apt, I
thought it
was going to upgrade it so I confirmed it. I had to reinstall apt
from
the debian packages website.
In this new installation I gave it another try but when it
started
suggesting very weird plans(like remove all gnome packages) ...
It seems like aptitude has gotten a lot smarter lately. :)
Not this morning it wasn't.
Aptitude has been refusing to do a full upgrade on my Jessie
system
for the past two weeks because it said it needed xorg-video-abi-12
but
it said it is not installable. Well, not so. I tried running
Synaptic
this morning and it had no problem finding what it needed and
installing it. I still don't understand what the difference was but
Synaptic did what aptitude said it couldn't do. What could be the
difference ? Does Synaptic not use the same repo source files
aptitude
uses?
Cheers
Did you tried synaptic just after aptitude, without updating the
package
list? If not, then maybe the package which gave you problems with
aptitude was added by that update.
Immediately afterward. I still don't understand it...then again
after using Linux for 10+ years...there are a lot of things I still
don't understand :)
Cheers
Hum... are recommended packages automatically installed by both
softwares in your configuration? It may be the reason, if aptitude tries
to upgrade something which recommend a 2nd package, which depends on the
non-available package, so the recommended package is broken and you need
to fix the breakage.
If synaptic does not, then the recommended package is not installed,
and so not broken.
I do not really know, since I usually fix errors myself, by freezing or
purging packages (I see no real interest into simple removal) which
cause the problem... but I am really curious :)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/387fc00cab4b4aaa905ad90179d3e...@neutralite.org