From owner-freebsd-questions@freebsd.org Wed Sep 7 16:56:38 2016 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 71BB9BD0171 for ; Wed, 7 Sep 2016 16:56:38 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: from mail8.networktest.com (mail8.networktest.com [IPv6:2607:f740:c::a13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B415C2B for ; Wed, 7 Sep 2016 16:56:38 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: from mail8.networktest.com (localhost [127.0.0.1]) by mail8.networktest.com (Postfix) with ESMTP id BE95E672005 for ; Wed, 7 Sep 2016 09:56:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail8.networktest.com Received: from mail8.networktest.com ([127.0.0.1]) by mail8.networktest.com (mail8.networktest.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nRwBw1VdB7hl for ; Wed, 7 Sep 2016 09:56:36 -0700 (PDT) Received: from tejay.local (unknown [IPv6:2605:e000:141f:145:70a6:2896:9fc8:7dd5]) by mail8.networktest.com (Postfix) with ESMTPSA id EC033672004 for ; Wed, 7 Sep 2016 09:56:35 -0700 (PDT) To: freebsd-questions@freebsd.org From: David Newman Subject: Different pkg upgrade behavior on different machines Organization: Network Test Inc. Message-ID: Date: Wed, 7 Sep 2016 09:56:36 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Wed, 07 Sep 2016 16:56:38 -0000 Greetings. How to get pkg to upgrade a package with a security vulnerability? I have four identical virtual machines, all running 10.3-RELEASE and bind910 installed using pkg and not ports. The 'pkg audit' command reports a vulnerability in bind910-9.10.4P2. One of the four machines successfully upgrades to bind910-9.10.4P2_1 using the commands 'sudo pkg update && sudo pkg upgrade bind910'. The other three machines report all repositories and packages are up to date. This behavior has existed for at least a couple of weeks, so I don't think it's a repository sync issue. Thanks in advance for advice on getting the updated pkg on all four VMs. dn