Lars Brueckner <[EMAIL PROTECTED]> wrote: > I found that a cvs import does not import all > files it should. [ ... ]
Make sure you import with the "-I !" option. Yep, you did. Good. > < ./extensions/tasks/resources/content/contents.rdf > < ./extensions/tasks/resources/locale/en-US/contents.rdf > < ./security/manager/.nss.checkout > < ./security/nss/lib/ckfw/builtins/certdata.c > < ./security/nss/lib/ckfw/nssck.api > < ./security/nss/lib/ckfw/nssckepv.h > < ./security/nss/lib/ckfw/nssckft.h > < ./security/nss/lib/ckfw/nssckg.h > < ./security/nss/lib/pki1/oiddata.c > < ./security/nss/lib/pki1/oiddata.h Strange. There is nothing unusual about these file names. > < ./xpinstall/packager/windows/.cvsignore > < ./xpinstall/wizard/windows/setuprsc/.cvsignore Ah hah. The imported tree has .cvsignore files. Hunt them down and remove them. Then, repeat the import. Use the exact same command as on the first attempt, with identical vendor and release tags. That will bring in the missing files and do nothing to the already imported files. The last two .cvsignore's seem to ignore themselves, which is unfortunate. You can't import them unless you remove them, at which point you can no longer import them ! A workaround would be to rename them, repeat the import, and go un-rename the ,v files in the repository. An alternative would be to see if you can live without the missing files. Usually they are generated files that the developers don't want in *their* repository, but they include them in the tarballs to remove the dependency on the tools that generates them. If you have the tools, you can leave them out of your repository too. (I do hate tarballs with .cvsignore's, though.) -- pa at panix dot com _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
