[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug in CVS 1.11 with client/server 'cvs export'.
From: |
Tony Byrne |
Subject: |
Bug in CVS 1.11 with client/server 'cvs export'. |
Date: |
Wed, 23 May 2001 11:14:17 +0100 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
bug-cvs,
I've come across a problem with client/server 'cvs export' in version
1.11, where the export fails while trying to export a module to a
clean directory. CVS complains that I cannot 'export into a working
directory' despite the target directory being empty and thus free of
any CVS admin files.
Last month Anthony Caetano posted a description of a very similar
problem with 'cvs export' to this list. As far as I can tell his
problem remains unresolved and I suspect that both share a root cause.
The good news is that I've tracked the cause of my problem down to the
'TopLevelAdmin' setting that I had enabled in the repository's
CVSROOT/config file. The problem occurs when TopLevelAdmin=yes, but
not when TopLevelAdmin=no or when it is omitted from the config file.
While fiddling with this setting fixes the export problem, surely
remote exports *should* work regardless of what TopLevelAdmin is set
to?
Regards,
Tony.
- --
- --------------------------------------------------------------
Tony Byrne, Head of Application Development, Directski.com
tonyb@directski.com http://www.directski.com - ski the web
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5i
iQA/AwUBOwuNhKpf11lW69VJEQLKPwCg9oe2FrVi46IMcMn2X/5oi5pbMI4AoKNe
PrNmgoX+Fcv4hLo2tB6gNItR
=xrSc
-----END PGP SIGNATURE-----
- Bug in CVS 1.11 with client/server 'cvs export'.,
Tony Byrne <=