portversion doesn't seem to know what's out of date

RW rwmaillists at googlemail.com
Sun Jul 27 15:12:06 UTC 2014

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 at beaglebone:/usr/home/jbirch  # portsnap fetch
>     ...
>     root at 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 at 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.

More information about the freebsd-questions mailing list