Issues with postmaster after freebsd-update
Kevin Oberman
rkoberman at gmail.com
Fri Feb 14 05:46:22 UTC 2014
On Thu, Feb 13, 2014 at 4:27 PM, LuKreme <kremels at kreme.com> wrote:
>
> On 13 Feb 2014, at 17:03 , Janky Jay, III <jankyj at unfs.us> 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 at gmail.com
More information about the freebsd-ports
mailing list