>> >> What am I doing wrong now? >> > >> > Nothing. Binaries aren't available for the bleeding-edge cvs packages. >> >> But I didn't think that 0.3.2a was bleeding edge, it was released on 1/16. >> >> Unless there is a difference between 0.3.2a and 0.3.2a-cvs, if that is the >> case can I go back to 0.3.2a (no cvs)? > > Well, I guess the important thing here isn't really that 0.3.2a version, > but that your local copy of the CVS catalog is up to date. CVS is updated > continually, and the version information for the catalog isn't. By running > the CVS update command, you have brought your local catalog into sync with > the public one, and can begin upgrading your local software to, yes, the > bleeding edge versions of anything you have installed.
Ok, maybe I'm not asking the right question or maybe I don't really understand what I'm talking about (probably the latter. Or maybe the problem is that I'm currently sitting in an IETF meeting on IP storage and I'm trying to pay attention to the presentations as well as fix my problem at the same time :) What if I don't want to be bleeding edge? What if I just want to bring everything up to date with the last point relase 0.3.2a? The only reason I did the cvs update was because that was a suggestion to fix my last problem which started this thread and that was just trying to go from 0.3.1 to the point relase of 0.3.2a. -Rich
msg01175/pgp00000.pgp
Description: PGP signature
