Date: Sun, 27 Jul 2014 16:12:00 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: portversion doesn't seem to know what's out of date Message-ID: <20140727161200.01eec19d@gumby.homeunix.com> In-Reply-To: <CAA=KUhte1_4mkitm2LDrnnk9MKX2cN=iKXpDZ2Q=MC1=iTYg6A@mail.gmail.com> References: <CAA=KUhte1_4mkitm2LDrnnk9MKX2cN=iKXpDZ2Q=MC1=iTYg6A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 27 Jul 2014 20:51:56 +1000 Jason Birch wrote: > I built FreeBSD for my Beaglebone Black a couple of weeks ago, and > went to do an update just then. After updating /usr/ports, I ran > `portversion | grep \<` to see a list of what could be updated. > Knowing that this takes a bit longer and needing to run out the door, > I also type `portupgrade -aF` afterwards, to fetch anything that > might need upgrading. > > When I returned, I found that portversion seemed to think everything > was up to date, but ... > > root@beaglebone:/usr/home/jbirch # portsnap fetch > ... > root@beaglebone:/usr/home/jbirch # uname -a > FreeBSD beaglebone 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r268309: > Sun Jul 6 22:13:49 EST 2014 > jbirch@267801:/usr/home/jbirch/crochet-freebsd/work/obj/arm.armv6/usr/src/sys/BEAGLEBONE > arm > > > Has anyone seen this behaviour before, or can point me forward? Try running portsdb -Fu. I don't think portsnap fetches an INDEX file for current. portupgrade -aF doesn't need to know about versions, so it's not affected.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140727161200.01eec19d>