Jim,

What errors are you getting? I was able to cvsup using your supfile with no
problem:


========================================
*default host=cvsup13.us.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_6
*default delete use-rel-suffix
*default date=2006.04.01.12.00.00

# If you seem to be limited by CPU rather than network or disk bandwidth,
try
# commenting out the following line.  (Normally, today's CPUs are fast
enough
# that you want to run compression.)
*default compress

## Main Source Tree.
#
# The easiest way to get the main source tree is to use the "src-all"
# mega-collection.  It includes all of the individual "src-*" collections.
src-all
ports-all tag=.
doc-all tag=.
========================================

su-2.05b# cvsup -g -L2 /etc/supfile
Parsing supfile "/etc/supfile"
Connecting to cvsup13.us.FreeBSD.org
Connected to cvsup13.us.FreeBSD.org
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed-mode data connection
Running
Updating collection src-all/cvs
 Checkout src/COPYRIGHT
 Checkout src/LOCKS
 Checkout src/MAINTAINERS
 Checkout src/Makefile
 Checkout src/Makefile.inc1
 Checkout src/ObsoleteFiles.inc
 Checkout src/README
 Checkout src/UPDATING
 Checkout src/bin/Makefile
 Checkout src/bin/Makefile.inc
 Checkout src/bin/cat/Makefile
...

-David

On 4/12/06, Jim Stapleton <[EMAIL PROTECTED]> wrote:
>
> Thanks, I'll try that again, however, when I've tried to do that, it
> has refused to update.
>
> On 4/12/06, David Stanford <[EMAIL PROTECTED]> wrote:
> > Jim,
> >
> > You currently have your default tag set to RELENG_6 (which is correct),
> but
> > when you place "tag=." next to your src, ports, and doc entries, you
> > override the default setting of RELENG_6. Remove the "tag=." next to
> your
> > src, ports, and doc entires, cvsup again, and your sources should be
> updated
> > with 6 STABLE.
> >
> > -David
> >
> >
> > On 4/12/06, Jim Stapleton <[EMAIL PROTECTED]> wrote:
> > >
> >  I used the examples as a basis, and a little trial and error if things
> > didn't work, so I eventually got a working supfile. However, it did
> > some weird stuff, even though this should be downloading 6.0 stable
> > (from what I can tell), I get errors in port builds (even without
> > optimisation flags).
> >
> > On top of that, I tried to build my kernel, and when all was said and
> > done, and it booted, it said 7.0 current. Is there a problem in my
> > supfile, or is this just a "HTF did you manage that??" error?
> >
> > I ran:
> > $ cvsup -g -L 2 /etc/supfile
> >
> > /etc/supfile
> > ========================================
> > *default host=cvsup13.us.FreeBSD.org
> > *default base=/var/db
> >  *default prefix=/usr
> > *default release=cvs tag=RELENG_6
> > *default delete use-rel-suffix
> > *default date=2006.04.01.12.00.00
> >
> > # If you seem to be limited by CPU rather than network or disk
> bandwidth,
> > try
> > # commenting out the following line.  (Normally, today's CPUs are fast
> > enough
> > # that you want to run compression.)
> > *default compress
> >
> > ## Main Source Tree.
> > #
> > # The easiest way to get the main source tree is to use the "src-all"
> > # mega-collection.  It includes all of the individual "src-*"
> collections.
> > src-all tag=.
> > ports-all tag=.
> > doc-all tag=.
> > ========================================
> >
> > Thanks,
> > -Jim
> > _______________________________________________
> >  freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "
> > [EMAIL PROTECTED]"
> >
> >
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to