Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Jul 2014 20:51:56 +1000
From:      Jason Birch <jbirch@jbirch.net>
To:        "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>,  "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   portversion doesn't seem to know what's out of date
Message-ID:  <CAA=KUhte1_4mkitm2LDrnnk9MKX2cN=iKXpDZ2Q=MC1=iTYg6A@mail.gmail.com>

Next in thread | Raw E-Mail | Index | Archive | Help
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 `portupgrade -aF` had found and downloaded upgrades to ruby,
pkg, Net-SSLeay, gnutls, and emacs-nox11. Checking the verbose output of
portversion, I saw that portversion seemed to think the out-of-date version
was up to date with the port...

    root@beaglebone:/usr/home/jbirch  # portsnap fetch
    Looking up portsnap.FreeBSD.org mirrors... none found.
    Fetching snapshot tag from portsnap.FreeBSD.org... done.
    Fetching snapshot metadata... done.
    Updating from Thu Jul 10 04:42:24 UTC 2014 to Sun Jul 27 05:09:26 UTC
2014.
    ....
    Fetching 63 new ports or files... done.

    root@beaglebone:/usr/home/jbirch # portsnap update
    Removing old files and directories... done.
    Extracting new files:
    /usr/ports/CHANGES
    ....
    /usr/ports/editors/emacs-nox11/
    ....
    /usr/ports/lang/ruby19/
    ....
    /usr/ports/ports-mgmt/pkg/
    ....
    /usr/ports/security/gnutls/
    ....
    /usr/ports/security/p5-Net-SSLeay/
    ....

    root@beaglebone:/usr/home/jbirch # portversion | grep \<
    [Reading data from pkg(8) ... - 63 packages found - done]

    root@beaglebone:/usr/home/jbirch # portupgrade -aF
    [Reading data from pkg(8) ... - 63 packages found - done]
    --->  Fetching the distfile(s) for 'ruby-1.9.3.547,1' (lang/ruby19)
    ....
    --->  Fetching the distfile(s) for 'pkg-1.3.1' (ports-mgmt/pkg)
    ....
    --->  Fetching the distfile(s) for 'p5-Net-SSLeay-1.65'
(security/p5-Net-SSLeay)
    ....
    --->  Fetching the distfile(s) for 'gnutls-3.2.16_1' (security/gnutls)
    ....
    --->  Fetching the distfile(s) for 'emacs-nox11-24.3_11,3'
(editors/emacs-nox11)
    ....

    root@beaglebone:/usr/home/jbirch # portversion -v
    [Reading data from pkg(8) ... - 63 packages found - done]
    ....
    emacs-nox11-24.3_10,3       =  up-to-date with port
    ....
    gnutls-2.12.23_6            =  up-to-date with port
    ....
    p5-Net-SSLeay-1.64          =  up-to-date with port
    ....
    pkg-1.2.7_4                 =  up-to-date with port
    ....
    ruby-1.9.3.484_2,1          =  up-to-date with port
    ....

    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

I'm trying to update just pkg for the moment to see if that helps the
situation, but it seems to be stuck in some sort of configure loop when
building from ports. I'll leave it for the night, as each loop seems to
compile something different.

pkg check is offering no hints as to if anything is awry -- it just looks
like portversion is looking at something completely different, or not
looking at anything at all.

Has anyone seen this behaviour before, or can point me forward?

JB



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CAA=KUhte1_4mkitm2LDrnnk9MKX2cN=iKXpDZ2Q=MC1=iTYg6A>