Curious pkg upgrade behavior

[Scott Ballantyne]

On Sat, Sep 16, 2017 at 08:03:43 -0500,  Adam Vande More
<amvandemore at gmail.com> wrote:
> 
> On Sat, Sep 16, 2017 at 7:17 AM, Scott Ballantyne <sdb at ssr.com> wrote:
> 
>  On a 10.3-RELEASE-p11 system here. I have been moving to pkg for
>  upgrades, and today tried a pkg upgrade, which upgraded several of the
>  ports. After this, Samba failed with an internal error. I'm running
>  Samba4, but this specific error seems to have been reported only with
>  versions of Samba36.
> 
>  After much head scratching, I noticed that pkg had actually not
>  upgraded Samba. So I tried running pkg upgrade again, which now
>  dutifully upgraded Samba and solved my problem.
> 
>  I was surprised by this. Not sure if this was my problem, a bug in
>  pkg, or just some mysterious phase of the moon situation.
> 
>  I would have thought pkg could have issued a message if it needed to
>  be run again?
> 
>  Any insight?
> 
> /var/log/messages will contain a log of what pkg did, but net/samba4x is not an upgrade to
> net/samba36 in terms of pkg's.

Yes, messages is where I first noticed it hadn't upgraded. I was running
samba43 prior to this. The second run of pkg uninstaled Samba
43-4.3.11 and installed samba44-4.4.15. It also upgraded gvfs. The
reason I mention samba3.6 is because that's the only place that bug
seems to have occurred, it never showed up here untiltoday.

I'm sure there's a reasonable explanation, I just have no idea what it
is.