I don't think this is an apt-get problem. I use aptitude exclusively, and I
get the same problem. The behavior started only recently, so I think the
problem lies in some package that both apt-get and aptitude depend on. The
issue won't really be solved until the real source of the issue is discovered
and corrected.
I don't think this is an apt-get problem. I use aptitude exclusively, and I
get the same problem. The behavior started only recently, so I think the
problem lies in some package that both apt-get and aptitude depend on. The
issue won't really be solved until the real source of the issue is discovered
and corrected.
Loye Young