From owner-freebsd-ports@FreeBSD.ORG Fri Feb 14 05:46:22 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 977DC24A for ; Fri, 14 Feb 2014 05:46:22 +0000 (UTC) Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6AE9C1156 for ; Fri, 14 Feb 2014 05:46:22 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id md12so11827367pbc.12 for ; Thu, 13 Feb 2014 21:46:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XDDg7kYsXGxkT2HkoQAyewxvVPhPx5Qdx2OYohh5Kz0=; b=XKJS2337tg5rLVPw9/fYNt1kLdwLd0Rcg//1EuZKlgMOdqyHfj9Cb6UsB11uXTyv/x nqxsm5ipSNJcsJBtmzwoly4iFrqpnbTQes7qSDBPnw9UI8HWQpiQqGqDZVK2eLGrg/Nw bNWGNCMopmZD7ls9SicS5jdxSVfMpovSC+EXv29Rryi0PdUvmI6KitBeiPwwcg+C3lGw gQxEhu/eCvemwtIDdYZvujg6jXjKPz28UwEjQNw4zMH7sB9UdsUw5EDcH850DCFSV3YK XJRgUzT4uawpE6PHBqJTvDbUPpo1Ba688g1kxRUjD3sscpmxT1F9jmfv43M+opiboRvG /m5Q== MIME-Version: 1.0 X-Received: by 10.68.130.234 with SMTP id oh10mr6725132pbb.136.1392356781328; Thu, 13 Feb 2014 21:46:21 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.30.1 with HTTP; Thu, 13 Feb 2014 21:46:21 -0800 (PST) In-Reply-To: References: <49D3D50F-9FBF-4247-81D6-5425B8FEBA2D@kreme.com> <52FD5D54.1090000@unfs.us> Date: Thu, 13 Feb 2014 21:46:21 -0800 X-Google-Sender-Auth: mkeJWQBAAKE6GoYDUoer32KA7Z4 Message-ID: Subject: Re: Issues with postmaster after freebsd-update From: Kevin Oberman To: LuKreme Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 05:46:22 -0000 On Thu, Feb 13, 2014 at 4:27 PM, LuKreme wrote: > > On 13 Feb 2014, at 17:03 , Janky Jay, III wrote: > > > Hello, > > > > I've ran into a few of these same sort of issues in the paste. > > > > What I did to fix it: > > > > 1) Migrate to pkgng. It looks like you already have based on the > ports-mgmt/pkg udpate. But, then I see your "pkg_install" error which leads > me to believe you haven't fully migrated. Just take a quick peek athttp:// > www.freebsd.org/doc/handbook/pkgng-intro.html and maybe try it again. > > I have tried several times. I thought I had changed successfully under > 8.2, but evidently not. I can't get it to compile now, and postmaster > doesn't see it. > > # portmaster -l | grep pkg > pkg: not found > ===>>> pkgconf-0.9.3 > > > 2) Manually deinstall the problematic port. IE...: > > > > # cd /usr/ports/graphics/py-clutter && make deinstall > > The directory does not exist. Portmaster does not see the port as being > installed. It seems to me that it is listed as a dependency by something > else. > > # portmaster -l | grep clutt > pkg: not found > ===>>> clutter-1.0.10_2 > ===>>> clutter-gtk-0.10.2_5 > ===>>> py26-clutter-1.0.0_2 > ===>>> py26-cluttergtk-0.9.3_2 > ===>>> clutter-cairo-0.8.2_1 > > I suppose I can delete py26-clutter (or heck, all of them). The problem is most likely the update to icu. It required the rebuilding of a lot of ports and clutter (and py-clutter) seems to run into most of them. Sorting them out is a royal pain. An easier way is to install sysutils/bsddfminscripts and use pkg_libchk to find what needs to be reinstalled. I use the command: pkg_libchk -o | grep icu | cut -d: -f1 | sort | uniq > ~/reinstall-ports portmaster -D `cat ~/reinstall-ports` When all of the ports reported have been re-installed: rm ~/reinstall-ports pkg_libchk -o The last command is to be sure that these are not any other missing libraries. (I hit three or four that required updating for libtasn1.) It is possible that I am misdiagnosing this, but it looks just like what I hit. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com