From owner-freebsd-questions@freebsd.org Sat Sep 16 12:24:38 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35992E139F5 for ; Sat, 16 Sep 2017 12:24:38 +0000 (UTC) (envelope-from sdb@ssr.com) Received: from mail.ssr.com (mail.ssr.com [199.4.235.6]) by mx1.freebsd.org (Postfix) with SMTP id 0670774A14 for ; Sat, 16 Sep 2017 12:24:37 +0000 (UTC) (envelope-from sdb@ssr.com) Received: (qmail 36824 invoked from network); 16 Sep 2017 12:17:55 -0000 Received: from unknown (HELO irelay.ssr.com) (sdb@74.73.182.128) by 199.4.235.6 with SMTP; 16 Sep 2017 12:17:55 -0000 Received: (qmail 1298 invoked by uid 103); 16 Sep 2017 12:17:55 -0000 Date: 16 Sep 2017 12:17:55 -0000 Message-ID: <20170916121755.1297.qmail@irelay.ssr.com> From: Scott Ballantyne To: freebsd-questions@freebsd.org Subject: Curious pkg upgrade behavior X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Sep 2017 12:24:38 -0000 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? Thanks, Scott -- sdb@ssr.com