Re: pkgsrc-2015Q3 released
On Wed 30 Sep 2015 at 10:29:16 -0400, Greg Troxel wrote: > Basically yes. Howver, you may want to do a final update of the tree > From sourceforge and verify you have no uncommitted changes that you > want to keep. (If so, you will have to manage them manually.) which currently gives errors about "cannot close CVS/Entries" and "No space left on device"... precisely the sort of reasons we moved away from there of course. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for \X/ rhialto/at/xs4all.nl-- 'this bath is too hot.' pgpoN9Y81jqSp.pgp Description: PGP signature
Re: pkgsrc-2015Q3 released
"Thomas Mueller"writes: > Now that pkgsrc-wip has been moved to a git repository, how does a user who > already has pkgsrc-wip by cvs update? > > I checked the URL, http://pkgsrc.org/wip/ , and this was not discussed. > > Or does the user just delete or move the cvs repository and git clone, fresh > start? Basically yes. Howver, you may want to do a final update of the tree From sourceforge and verify you have no uncommitted changes that you want to keep. (If so, you will have to manage them manually.) pgpg8Y7vnXeE4.pgp Description: PGP signature
Re: pkgsrc-2015Q3 released
Now that pkgsrc-wip has been moved to a git repository, how does a user who already has pkgsrc-wip by cvs update? I checked the URL, http://pkgsrc.org/wip/ , and this was not discussed. Or does the user just delete or move the cvs repository and git clone, fresh start? Tom