From owner-freebsd-ports@freebsd.org  Sun Oct 21 20:46:11 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AE45FFFEC5
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Sun, 21 Oct 2018 20:46:11 +0000 (UTC)
 (envelope-from phascolarctos@protonmail.ch)
Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.protonmail.ch",
 Issuer "QuoVadis Global SSL ICA G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E8CD577160
 for <freebsd-ports@freebsd.org>; Sun, 21 Oct 2018 20:46:10 +0000 (UTC)
 (envelope-from phascolarctos@protonmail.ch)
Date: Sun, 21 Oct 2018 20:45:55 +0000
To: FreeBSD Ports <freebsd-ports@freebsd.org>
From: Lorenzo Salvadore <phascolarctos@protonmail.ch>
Reply-To: Lorenzo Salvadore <phascolarctos@protonmail.ch>
Subject: Re: Packages not updated?
Message-ID: <b5HUK-W0R6FlCacl7V0Tcb0NkYS0z3L0JWE_W6pGsKPHcookAYiL19JpXS2xvEflBp3KTIzkMZ7DvpJuDX6dgRdTVNa8iyjZg-8f0em8Cso=@protonmail.ch>
In-Reply-To: <20181021203127.GA65002@neutralgood.org>
References: <20181021203127.GA65002@neutralgood.org>
Feedback-ID: X6az_D2smWSR8MT5MHqXnWF0upxehDyHia7Id1cbayHNBUkRu3CIeusDsZHiivIIjmaKB1_OofpALrRUYjNz3w==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.1 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no
 version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.protonmail.ch
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2018 20:46:11 -0000

> So I just saw another post on this list that mentioned the "pkg version -=
vL=3D"
> command. Now, I've got a /usr/ports tree used by poudriere and run on the
> same machine. I svn updated my /usr/ports and kicked off poudriere. When =
it
> was done I ran "pkg upgrade". But the "pkg version -vL=3D" still shows th=
is:
>
> py27-ndg_httpsclient-0.4.2 < needs updating (port has 0.5.1)
> py27-pbr-1.8.1_1 < needs updating (port has 3.1.1)
> py27-pip-9.0.1 < needs updating (port has 9.0.3)
> py27-psutil-5.2.2 < needs updating (port has 5.4.7)
> py27-pyasn1-0.2.2 < needs updating (port has 0.4.2)
> py27-python2-pythondialog-3.4.0 < needs updating (port has 3.4.0_1)
> py27-werkzeug-0.12.2 < needs updating (port has 0.14.1)
> transmission-web-2.93_1 < needs updating (port has 2.94)
>
> The question is: why are these packages not getting upgraded when I run
> pkg upgrade?
>
> And, yes, pkg version is getting its info from my poudriere server. I'm
> looking at the web server logs in real time.
>
> Any ideas?

pkg upgrade is for upgrading packages and not ports, but pkg version is com=
paring
your version against the versions of the port tree, not of the package repo=
sitory.

To compare against the package repository, use the -R flag:

pkg version -RvL=3D

Lorenzo Salvadore.