Date: Mon, 19 Jun 2006 17:16:03 +0300 From: Adi Pircalabu <apircalabu@bitdefender.com> To: matt@genesi-usa.com Cc: freebsd-ports@freebsd.org, 'Sergey Matveychuk' <sem@FreeBSD.org> Subject: Re: Dealing with downgraded ports Message-ID: <20060619171603.49756042@apircalabu.dsd.ro> In-Reply-To: <02ae01c693aa$172c2410$99dfdfdf@bakuhatsu.net> References: <4496AF32.9000002@FreeBSD.org> <02ae01c693aa$172c2410$99dfdfdf@bakuhatsu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Jun 2006 09:10:12 -0500 Matt Sealey wrote: > That's what I meant. 2.1.1 is less than 2.1.4 isn't it? 2.1.1 is less than 2.1.4, but 2.1.1,2 is greater in port version terms than 2.1.4_5,1. Note the value after the coma, it's called PORTEPOCH: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-naming.html > But it whines that 2.1.4_5,1 is still available but won't install it. > I just want to silence that.. You'd better fix it :) Just cvsup and portupgrade -fv portupgrade > > > -----Original Message----- > > From: Sergey Matveychuk [mailto:sem@FreeBSD.org] > > Sent: Monday, June 19, 2006 9:06 AM > > To: matt@genesi-usa.com > > Cc: freebsd-ports@freebsd.org > > Subject: Re: Dealing with downgraded ports > > > > Matt Sealey wrote: > > > I downgraded portupgrade and everything works again. > > > > > > > You should not downgrade. portupgrade-2.1.1,2 > > > portupgrade-2.1.4_5,1 > > -- Adi Pircalabu (PGP Key ID 0x04329F5E) -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060619171603.49756042>