omz13

Eeks! A new stable release of cvsnt has appeared.

I’ve bumped my ebuilds accordingly. I’ve also marked this as stable (i.e. x86) instead of the usual testing (i.e. ~x86).

As always, get this and all the other ebuilds for cvsnt into your local portage tree by doing:

# rsync -rztp --delete rsync://rsync.omz13.com/local-portage/dev-util/cvsnt /usr/local/portage/dev-util 

p.s. One slight niggle is that info seems a bit broken on Linux-servers… an assert hapens server side and the client will just say info isn’t available (although it is but its broke)… sorry folks, but I don’t have time to track this one down.

p.p.s. If you experienced problems with manifest digest/filesize mismatch when trying to emerge build 2382 please rsync once more and try again… it looks like the downstream tarball was updated… I’ve updated things back here and sanity is once again the norm.

cvsnt-2.5.03.2260.ebuild has now been marked stable (i.e. keyworded x86 from ~x86), as a result of an announcement in the cvsnt mailing list from Tony Hoyle, the maintainer of cvsnt:

This [CVSNT 2.5.03 Build 2260] will be the last 2.5.x series release with feature changes.  The roadmap includes a 2.5.04 release which is new features for the suite, but there are unlikely to be any changes to the cvsnt 2.5 core.  Future development will focus on 2.6.x, getting that to a production ready release.

The 2.5.x branch is stable (from build 2260) and fit for deployment; the 2.6.x branch is the unstable branch for new core features (and is for testing and not deployment).