[SOLVED] Re: Issues with postmaster after freebsd-update

2014-02-23 Thread LuKreme
On 13 Feb 2014, at 16:39 , LuKreme wrote: > I was running FreeBSD 8-2 and used freebsd-update to update: OK, so final resolution: I reran freebsd update from the start and was still having problems. I made a couple of mistakes along the way (php55 and gcc49 seemed to be the most egregious of t

Re: Issues with postmaster after freebsd-update

2014-02-23 Thread Matthew Seaman
On 23/02/2014 02:40, Kevin Oberman wrote: > On Sat, Feb 22, 2014 at 5:38 PM, LuKreme wrote: > >> > On 13 Feb 2014, at 22:46 , Kevin Oberman wrote: >>> > > An easier way is to install sysutils/bsddfminscripts and use pkg_libchk >> > to >>> > > find what needs to be reinstalled. I use the command:

Re: Issues with postmaster after freebsd-update

2014-02-22 Thread LuKreme
On 22 Feb 2014, at 19:40 , Kevin Oberman wrote: > the purpose is to get a list of ports that still link to the old version of > libicu. Oh right, duh. `pkg_libchk -o` returns nothing now, after a rather long delay. Thanks to everyone for getting me through this. postmaster -af still has some

Re: Issues with postmaster after freebsd-update

2014-02-22 Thread Kevin Oberman
On Sat, Feb 22, 2014 at 5:38 PM, LuKreme wrote: > On 13 Feb 2014, at 22:46 , Kevin Oberman wrote: > > 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 >

Re: Issues with postmaster after freebsd-update

2014-02-22 Thread LuKreme
On 13 Feb 2014, at 22:46 , Kevin Oberman wrote: > 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` I

Re: Issues with postmaster after freebsd-update

2014-02-22 Thread LuKreme
On 21 Feb 2014, at 18:49 , Kevin Oberman wrote: > On Fri, Feb 21, 2014 at 3:52 PM, LuKreme wrote: > >> >> On Feb 21, 2014, at 6:55, Bryan Drewery wrote: >>> >>> I don't think your upgrade to 8.4 is actually complete. posix_fallocate >>> is in 8.4. >> >> How do I check? uname says its 8.4-R

Re: Issues with postmaster after freebsd-update

2014-02-21 Thread Kevin Oberman
On Fri, Feb 21, 2014 at 3:52 PM, LuKreme wrote: > > On Feb 21, 2014, at 6:55, Bryan Drewery wrote: > > > > I don't think your upgrade to 8.4 is actually complete. posix_fallocate > > is in 8.4. > > How do I check? uname says its 8.4-RELEASE > > How was the OS upgraded? If it was via freebsd-upd

Re: Issues with postmaster after freebsd-update

2014-02-21 Thread LuKreme
On Feb 21, 2014, at 6:55, Bryan Drewery wrote: > > I don't think your upgrade to 8.4 is actually complete. posix_fallocate > is in 8.4. How do I check? uname says its 8.4-RELEASE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mai

Re: Issues with postmaster after freebsd-update

2014-02-21 Thread Kevin Oberman
On Fri, Feb 21, 2014 at 1:32 AM, LuKreme wrote: > > On 13 Feb 2014, at 22:46 , Kevin Oberman wrote: > > > pkg_libchk -o | grep icu | cut -d: -f1 | sort | uniq > ~/reinstall-ports > > Sadly, pkg_libchk is part of pkgng and I haven't been able to get that to > compile. > No, pkg_libchk is a port

Re: Issues with postmaster after freebsd-update

2014-02-21 Thread Bryan Drewery
On 2/13/2014 5:39 PM, LuKreme wrote: > I was running FreeBSD 8-2 and used freebsd-update to update: > > FreeBSD 8.4-RELEASE-p7 #0: Sat Jan 11 01:45:47 UTC 2014 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > > the next step I was given was to run > > portmaster -af >

Re: Issues with postmaster after freebsd-update

2014-02-21 Thread LuKreme
On 13 Feb 2014, at 22:46 , Kevin Oberman wrote: > pkg_libchk -o | grep icu | cut -d: -f1 | sort | uniq > ~/reinstall-ports Sadly, pkg_libchk is part of pkgng and I haven't been able to get that to compile. /usr/ports/ports-mgmt/pkg/work/pkg-1.2.6/libpkg/../external/sqlite/sqlite3.c:23598: er

Re: Issues with postmaster after freebsd-update

2014-02-19 Thread LuKreme
On 13 Feb 2014, at 22:46 , Kevin Oberman wrote: > 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 Thanks, I will give that a try if t

Re: Issues with postmaster after freebsd-update

2014-02-14 Thread Kubilay Kocak
On 14/02/2014 11:27 AM, 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

Re: Issues with postmaster after freebsd-update

2014-02-13 Thread Kevin Oberman
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 >

Re: Issues with postmaster after freebsd-update

2014-02-13 Thread LuKreme
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

Re: Issues with postmaster after freebsd-update

2014-02-13 Thread Janky Jay, III
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