Date: Thu, 5 Apr 2007 10:04:07 -0400 From: Kris Kennaway <kris@obsecurity.org> To: ports@freebsd.org, portmgr@freebsd.org Subject: Re: ruby port version going backwards? epoch Message-ID: <20070405140406.GA4850@xor.obsecurity.org> In-Reply-To: <20070405073142.GA5753@merlin.emma.line.org> References: <20070405073142.GA5753@merlin.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 05, 2007 at 09:31:42AM +0200, Matthias Andree wrote: > Greetings, >=20 > I just saw this after portsnap fetch update when running pkg_version -IvL= =3D: >=20 > ruby-1.8.5.12,1 > succeeds index (index has 1.8.6) >=20 > Please restore ruby's PORTEPOCH - and consider installing pre-commit check > scripts on the CVS master server that refuse Makefile commits that make > the version go backwards. This was fixed, but note that pre-commit checks wouldn't have helped: the change was made in one file (bsd.ruby.mk) but the effects felt in others. In order to catch it we'd have to iterate over the entire ports tree, which would delay each commit by a few tens of minutes, or a few hours depending on machine load :) Kris --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGFQHWWry0BWjoQKURAoI0AKCnuQv7e7W3UYRL24OYHsyXwSYWsgCcDV9B h6dQJdOTqNbh8WM6blZqfTg= =qeLE -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070405140406.GA4850>