[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Listing packages



On Wed, 2007-10-17 at 19:08 -0700, David Fox wrote:
> David wrote:
> 
> 
> > dpkg --get-selections |while read pkg dummy; do src=$(apt-cache policy
> > $pkg |grep -A1 ' \*' |sed 1d | tr -s "[:blank:]" ); [ -n "$src" ] &&
> > echo $pkg: $(apt-cache policy |grep -A1 "$src" |grep -oE '(a|
> > l)=[A-Za-z-]+'); done
> 
> That's a useful script! :)
> 
> One question though:
> 
> I run a mostly texting box. There are very few packages from unstable,
> mostly related to the nvidia proprietary drivers and the related x.org
> video drivers. And that's because I explicitly asked for those.
> 
> However, there are a few packages where the repository is "now" (a=now
> comes up for a dozen or so packages). I've been in debian for a while,
> and I have never heard of a "now" repository, so where are these
> coming from? I can understand in the case of a few packages I've
> gotten from non-standard repositories (opera, for instance) that 'now'
> might be the best choice, but I know from experience that I shouldn't
> have as many packages with the "now" as a source repository as I seem
> to have.
> 

My *guess* is that these packages are installed on your machine, but are
not available from any source in your sources list.

If you run apt-cache on each of those "now" packages, my guess is you'll
see that they are all either etch leftovers, or something which you
manually installed using dpkg, or that came from a source that is no
longer in your list.

To do this, just tack:  

|grep now |cut -d: -f1 |xargs apt-cache policy

on to the end of that previous string of commands.

-davidc

-- 
gpg-key: http://www.zettazebra.com/files/key.gpg

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: