From owner-freebsd-stable@FreeBSD.ORG Sat Sep 6 05:32:07 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E0EDFE8 for ; Sat, 6 Sep 2014 05:32:07 +0000 (UTC) Received: from mproxy19.sbb.rs (mproxy19.sbb.rs [89.216.2.104]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.sbb.rs", Issuer "PositiveSSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86AF11542 for ; Sat, 6 Sep 2014 05:32:05 +0000 (UTC) Received: from knossos (cable-178-148-97-46.dynamic.sbb.rs [178.148.97.46]) by mproxy19.sbb.rs (8.14.4/8.14.4) with ESMTP id s865A0EQ009963 for ; Sat, 6 Sep 2014 07:10:00 +0200 X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.6 at SBB mail Received: from localhost (1000@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 180576f0; for ; Sat, 6 Sep 2014 07:09:44 +0200 (CEST) Date: Sat, 6 Sep 2014 07:09:44 +0200 From: Zoran Kolic To: freebsd-stable@freebsd.org Subject: update to pkg 1.3.7 Message-ID: <20140906050944.GA4460@knossos> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mproxy19.sbb.rs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2014 05:32:07 -0000 After being away for a while, I found posts on new pkg and problems with upgrading packages. I assume the correct way nowadays would be to first upgrade pkg to >=1.3.7. Then to issue pkg update -f. Then to make "pkg install whatever", just as it should be like before? Sorry to look like falling from Mars, but I found a lot of users posting problems. Best regards Zoran