You did it, okay, thank you, but late :( I always before upgrading something, go to /usr/ports and watch the UPDATING file, simple there was nothing about portupgrade, nothing at the bigging of June nothing at the end of June or at the bigging of July.
I am sorry that I do not read almost everything, but I thought ... I have a idea that UPDATING file is the MAIN place where comments MUST BE. Sorry, this fact the handbook teached me. :) Daniel > -----Original Message----- > From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] > Sent: Monday, July 03, 2006 10:21 AM > To: Hajimu UMEMOTO > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: FreeBSD Port: portupgrade-2.1.3.2, 2 - help me > please, the port in short time is broken again, what does it > all mean ? > > Hajimu UMEMOTO wrote: > > Hi, > > > >>>>>> On Mon, 03 Jul 2006 10:15:56 +0400 Sergey Matveychuk > >>>>>> <[EMAIL PROTECTED]> said: > > > > sem> See my HANDS-UP message a couples days ago at the list. > > sem> Old (<=2.1.1,2) portupgrade use wrong (may be a right > word will - > > sem> "unexpected") database format. > > > > I don't think that old portupgrade uses wrong database format. You > > changed the default version of Berkeley DB, silently: > > > > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/portupgrade/Makef > > ile.diff?r1=1.224&r2=1.225 > > > > It broke backward compatibility of .db files. > > You should be meant I forgot add an entry to UPDATING? Yes, I > forgot it. > I'll do. > > -- > Dixi. > Sem. > _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
