On Sun, Aug 26, 2007 at 01:10:16PM +0800, Uwe Dippel wrote: > Wanting to find out which packages needed an update, I referred to FAQ 15: > "Invoking pkg_add(1) with the -u flag and no package name will just > examine all installed packages for updated versions." > This results here in > > ># pkg_add -u > >Candidates for updating bzip2-1.0.4 -> bzip2-1.0.4 bzip2-1.0.3 > >Ambiguous: bzip2-1.0.4 could be bzip2-1.0.3 bzip2-1.0.4 > >Candidates for updating gd-2.0.34p1 -> gd-2.0.33p3 gd-2.0.34p1 > >Ambiguous: gd-2.0.34p1 could be gd-2.0.33p3 gd-2.0.34p1 > >Candidates for updating pfstat-2.2 -> pfstat-2.2 > >Candidates for updating python-2.4.3p0 -> python-2.4.3p0 > >Candidates for updating webalizer-2.01.10p3 -> webalizer-2.01.10p3 > >Looking for updates: complete > >There are some ambiguities. Please run in interactive mode again. > >Running the equivalent of pkg_add -r pfstat-2.2 python-2.4.3p0 > >webalizer-2.01.10p3 > >pfstat-2.2 (extracting): complete > >pfstat-2.2 (deleting): complete > >pfstat-2.2 (installing): complete > >python-2.4.3p0 (extracting)|********************************* |77% > > Huh, this *does* update python, doesn't it? > I am running 4.0, and I do understand the word 'examine' as resulting in > a to-do list, not as in 'I done it for you'.
You obviously have a repository of packages that has various versions of packages in there. That doesn't work well. pkg_add assumes you have a snapshot-like structure of packages. Or maybe you have a rather long PKG_PATH. The specific issue of a long PKG_PATH was solved somewhere between 4.1 and 4.2. pkg_add(1) now stops at the first path element with valid candidates. The FAQ entry is ambiguous, even though the example is clear.
