Prev: Taucs 2.2.4 build failure
Next: X.org, dlopen and -current problem
From: Laganakos Vassilis on 1 Feb 2007 21:58
That worked :D

I updated portupgrade and then the portupgrade was smooth!

Thanx!

Vassilis

On Thu, Feb 01, 2007 at 09:46:59PM +0300, Sergey Matveychuk wrote:
> Have you updated portupgrade to the last one (2.2.2_3,2)? Do it please.
>
> Laganakos Vassilis wrote:
> > Hi,
> >
> > Done that too (pkgdb -fu) , but didn't work for me... :(
> > I use FreeBSD6-stable
> >
> > Vassilis
> >
> > On Thu, Feb 01, 2007 at 01:45:55AM +0100, Csaba Molnar wrote:
> >> 2007. February 1. 00.34 d?tummal Joachim Bethke ezt ?rta:
> >>> Hallo,
> >>>
> >>> I get the same error on two machines too. Have someone a practical idea
> >>> <http://dict.leo.org/ende?lp=ende&p=/gQPU.&search=idea> how to fix it.
> >>>
> >>> Joachim
> >>
> >> I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, and
> >> that seems to have worked.
> >>
> >> While I was updating ports before this error showed up, the options screen for
> >> portupgrade showed up - and option WITH_BDB4 was unchecked. I changed that
> >> (so portupgrade was now built with bdb4) - and the problems began right after
> >> this update.
>
> --
> Dixi.
> Sem.

--

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: Taucs 2.2.4 build failure
Next: X.org, dlopen and -current problem