On Wed, 2008-07-02 at 14:33 +0800, Magicloud wrote: > >On Wed, 2008-07-02 at 14:01 +0800, Magicloud wrote: > >> I don't think so. Obviously, if the network is broken, it absolutely > >> does not mean that there is NO packages, just aptitude can not know. > > >That's by far the most round logic I've heard tonight. If it can't reach > the repository to know about the packages, how in the world do you expect > aptitude to know about the packages? > > No, no. If you do not know how to deal with it, keep it. > If aptitude could not separate "can not connect" with "get a list with > nothing in"..., I was stunned again.... If it can't connect, the source isn't valid anyway for the time being. Think twice before using clean or autoclean next time: Don't reap unless you know your repositories are working. -- Paul Johnson baloo@ursine.ca
Attachment:
signature.asc
Description: This is a digitally signed message part