From owner-freebsd-ports@freebsd.org Sun Oct 21 20:42:10 2018 Return-Path: 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 99FEEFFFD27 for ; Sun, 21 Oct 2018 20:42:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D2C676FD4 for ; Sun, 21 Oct 2018 20:42:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x32d.google.com with SMTP id c23so36261835otl.9 for ; Sun, 21 Oct 2018 13:42:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+q064NORVA7QRfcYsw27zeLHwjP6Aiqw3XklGGTWDOc=; b=sj8H5v8mP+42z2gk2AYfzj9zTl9J28r3ocEjjvZJTywkuUYXrWrECTfQFP6+7lnrUi dXGBGQrW6t/7yDrTgddPFms1LpnptfLsz3bFxc8OCfOQHWmWK3gxNkxJ0hYNNcGQDRQT 3lu65KjLniOLY08MnwKtaGzlc3r+iTxmgngrDq1XAz6uvbXTZcZn0dzOZcy95VJqk6YY qffmDmY2Yme1NR7xVmjr4epflbtvWhedvCm0Sm1NpoYWjvG2X4bq6azLsohxjXjh5l+s 8oZl+w0MPUnaL7AW0CPIwZ8pdJZth3uMLkHBVb4rub7GgPMxI7Gws2DM1+kdDxVAQxdv PZbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+q064NORVA7QRfcYsw27zeLHwjP6Aiqw3XklGGTWDOc=; b=YDwwUal7ayCqvt5dbBFioN+ZDvEkfhDIulli2oqYAVVlbIfxSt/+cg33MvR8tmxXiH BNbWdNUfvYTbK28PrKtRjvnWO3/oL8eVvkibYScUw/scjYKk2FrqI4epoZsRA9WRZvAy mqFsMLVyWJgzaaajgJgRif/1IGXfyc/x9KyPl3OQI3XgS4I45U+mtoT3QhFKoUqEKWLt 0HrGSOeb6FlNxd5Gv7hiya4F4tM2VQXEvWENgZ6iKib83gZ/9qv3ey59BKOENakgYTpR TlA9OQKQOkQuGweQ5uQd0ycFt+0U8KQVzkmGTXJi6/bctsutxir+sedo7uMxpkM/CJyP G6Rw== X-Gm-Message-State: ABuFfojB+lKt1qU4SAMdUfzqMJLausGhAN+N1JwTtMHvQOt/L2qaqk0/ ZhRf7KHSB8HeotPzhXk3K8tAjFstpLyh8Z+55+/oPMB1 X-Google-Smtp-Source: ACcGV60AtZ5WNndPTf0U03zsSrJwBSXr1FlqBQoKA0LtkWzkEl4YaITIUbCIu+c/F1oDleg+Houk99eP0HL/83TRRpQ= X-Received: by 2002:a9d:256e:: with SMTP id j43mr27874211otd.367.1540154529320; Sun, 21 Oct 2018 13:42:09 -0700 (PDT) MIME-Version: 1.0 References: <20181021203127.GA65002@neutralgood.org> In-Reply-To: <20181021203127.GA65002@neutralgood.org> From: Kevin Oberman Date: Sun, 21 Oct 2018 13:41:51 -0700 Message-ID: Subject: Re: Packages not updated? To: kpn@neutralgood.org Cc: FreeBSD Ports ML Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2018 20:42:10 -0000 On Sun, Oct 21, 2018 at 1:32 PM Kevin P. Neal wrote: > So I just saw another post on this list that mentioned the "pkg version > -vL=" > 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=" still shows this: > > 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? > -- > Kevin P. Neal http://www.pobox.com/~kpn/ > The packages get rebuilt by periodic batch jobs and always lag by about 2-4 days. This assumes that you are updating from head and not the quarterly. There have been issues where a package build run hung and had to be at least kicked and perhaps more that delayed things. It's been 10 days since the last head package update, so I suspect something is hung up. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683