[lug] apt-get errors

Paul E Condon pecondon at peakpeak.com
Fri Jan 30 11:10:33 MST 2004


On Fri, Jan 30, 2004 at 10:46:09AM -0700, Gary Hodges wrote:
> Paul E Condon wrote:
> 
> >It looks like your errors are all on non-US Sarge stuff. This
> >shouldn't be happening but the work around is easy:
> >
> >Eliminate non-US lines from sources.list.
> >
> 
> Thanks for your interest and comments/suggestions with all of this.  
> Commenting the non-US lines on both machines eliminated the errors 
> during "apt-get update."  Is there a way to easily identify and remove 
> any non-US software that may have been installed?  My concern is that I 
> may have something installed that won't get updated, potentially causing 
> a security risk down the line.
> 
> Gary
> 

I doubt that you have any installed because you seem to have failed to
download the catalog of available software which is a necessary precondition
to actually downloading the software.

I don't know of a quick way to identify the source repository for each
installed package. Look at man pages for dpkg and apt-get. 
dpkg --get-selections 
produces a list of all selected packages but doesn't identify the repository.
dpkg -l
produces a list that includes version numbers and one line descriptions.
Maybe some other dash option does what you want, but again, I doubt that
you downloaded anything by accident.

Maybe this: With the offending lines removed from sources.list, any installed
pachages that came from non-US will start showing up in the category "locally
generated" in aptitude (because aptitude can't find a source repository). If
there are any 'locally generated' packages on your system you should probably
worry because you surely have not had a chance to do program development yet.


-- 
Paul E Condon           
pecondon at peakpeak.com    




More information about the LUG mailing list