From owner-freebsd-questions@FreeBSD.ORG Sat Oct 23 00:59:02 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A04D106566B for ; Sat, 23 Oct 2010 00:59:02 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 0EE198FC08 for ; Sat, 23 Oct 2010 00:59:01 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id o9N0x1QU031377; Fri, 22 Oct 2010 18:59:01 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id o9N0x0LM031374; Fri, 22 Oct 2010 18:59:01 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 22 Oct 2010 18:59:00 -0600 (MDT) From: Warren Block To: Justin Victoria In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (wonkity.com [127.0.0.1]); Fri, 22 Oct 2010 18:59:01 -0600 (MDT) Cc: justin.victoria@gmail.com, freebsd-questions@freebsd.org Subject: Re: 4.5.4 Upgrading Ports (Handbook) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Oct 2010 00:59:02 -0000 On Fri, 22 Oct 2010, Justin Victoria wrote: > Ok, so let me get this straight. Here is what Ive deduced using the > handbook: > > Step 1: run pkg_version -v > > will just stick with samba for now: > > [vic@hbca ~]$ pkg_version -v | grep -i samba > samba-3.0.37_1,1 = up-to-date with index > samba34-libsmbclient-3.4.8 < needs updating (port has 3.4.9) > > > pkg_version -v is telling me samba is up-to-date with index > samba34-libsmbclient-3.4.8 needs updating.. > > ok. step 2, check /usr/ports/UPDATING > > hbca# grep samba-3.0.37 /usr/ports/UPDATING Grepping for specific things in UPDATING is bound to miss big updates that affect lots of ports, like gettext. Look at what's new in that file since the last time you updated ports. > hbca# pkgdb -F > ---> Checking the package registry database > Stale origin: 'net/samba3': perhaps moved or obsoleted. > -> The port 'net/samba3' was removed on 2010-10-18 because: > "Has expired: Unsupported by the upstream. Please, consider to > upgrade." > -> Hint: samba-3.0.37_1,1 is not required by any other package > -> Hint: checking for overwritten files... > -> No files installed by samba-3.0.37_1,1 have been overwritten by other > packages. > Deinstall samba-3.0.37_1,1 ? [no] no > Duplicated origin: security/libgcrypt - libgcrypt-1.4.5_1 libgcrypt-1.4.6 > Unregister any of them? [no] no Looks like you've already missed some notes in UPDATING: % less +/20100727 /usr/ports/UPDATING > Since samba is very to configure, I can simply deinstall samba all together > and reinstall.. What exactly is the point of portupgrade then? Automating the process of updating a web of dependencies. The article link speaks about this a bit: http://www.wonkity.com/~wblock/docs/html/portupgrade.html PS: please don't top-post, it makes responding more difficult.