Packages not updated?

[Kevin Oberman]

On Sun, Oct 21, 2018 at 1:32 PM Kevin P. Neal <kpn at neutralgood.org> 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 at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683