I noticed that "-letter" was dropped from the list at about the same time psutils became ambiguous... Don't know if that's related.
On Wed, Apr 18, 2012 at 1:47 PM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2012/04/18 21:14, Jan Stary wrote: >> I upgraded my current/amd64 and now I am upgrading the packages >> with pkg_add -ui; psutils gets upgraded as a dependency of a2ps: >> >> Ambiguous: choose package for psutils-1.17p3-a4 >> a 0: <None> >> 1: psutils-1.17p3 >> 2: psutils-1.17p3-a4 >> >> I just answer '2' and everything goes on smoothly, >> but why is this an ambiguity? Is this expected? >> In fact, psutils-1.17p3-a4->psutils-1.17p3-a4 >> >> Jan >> > > A few of us have spotted this and I agree it doesn't seem to be ambiguous, > I've had a play with adjusting @pkgpath markers to no avail (though they > already look correct to me), not sure quite what is going on. > > Proper verbose output from pkg_add:- > > Update candidates: a2ps-4.14p5-a4 -> a2ps-4.14p5-a4 (ok) > Comparing full signature for a2ps-4.14p5-a4 > "a2ps-4.14p5-a4,c.64.0,gettext-0.18.1p1,iconv.6.0,intl.6.0,libiconv-1.14,m.7.0,psutils-1.17p3-a4" > vs. > "a2ps-4.14p5-a4,c.63.0,gettext-0.18.1p1,iconv.6.0,intl.6.0,libiconv-1.14,m.7.0,psutils-1.17p3-a4":less > parsing a2ps-4.14p5-a4 > Comparing full signature for a2ps-4.14p5-a4 > "a2ps-4.14p5-a4,c.64.0,gettext-0.18.1p1,iconv.6.0,intl.6.0,libiconv-1.14,m.7.0,psutils-1.17p3-a4" > vs. > "a2ps-4.14p5-a4,c.63.0,gettext-0.18.1p1,iconv.6.0,intl.6.0,libiconv-1.14,m.7.0,psutils-1.17p3-a4":less > Direct dependencies for a2ps-4.14p5-a4->a2ps-4.14p5-a4 resolve to > libiconv-1.14 psutils-1.17p3-a4 gettext-0.18.1p1 (todo: psutils-1.17p3-a4-> > libiconv-1.14-> gettext-0.18.1p1->) > Update candidates: psutils-1.17p3-a4 -> psutils-1.17p3-a4 psutils-1.17p3 (ok) > Ambiguous: choose package for psutils-1.17p3-a4 > a 0: <None> > 1: psutils-1.17p3 > 2: psutils-1.17p3-a4 >
