Date: Mon, 03 Jul 2006 10:15:56 +0400 From: Sergey Matveychuk <sem@FreeBSD.org> To: Sergey Matveychuk <sem@freebsd.org>, dandee@volny.cz, ports@freebsd.org 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 ? Message-ID: <44A8B61C.6010003@FreeBSD.org> In-Reply-To: <20060703060759.GB51623@snoozy.vdgrift.org> References: <003201c69e25$43b56de0$6508280a@tocnet28.jspoj.czf> <44A8AFB7.5030304@FreeBSD.org> <20060703060759.GB51623@snoozy.vdgrift.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bert van de Grift wrote: > On Mon, Jul 03, 2006 at 09:48:39AM +0400, Sergey Matveychuk wrote: >> Daniel Dvor(a'k wrote: >>> >>> Fixing the pkgdb.db does not help me at all. >>> > >> It's a known issue. > >> Just remove the file and /usr/ports/INDEX*.db and run portupgrade >> again. Note, it's described on man page - if you found pkgdb.db >> seriously broken, just remove it. > > I have the same problem after upgrading portupgrade but when I go back > to the previous version (2.1.1,2) everything is ok... > See my HANDS-UP message a couples days ago at the list. Old (<=2.1.1,2) portupgrade use wrong (may be a right word will - "unexpected") database format. -- Dixi. Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44A8B61C.6010003>