I think the problem here is that gdb's modules file uses module aliases. This means that cvs co gdb works out being equivalent to something like (actually it's more complicated, but never mind):
cvs co !src/gdb/gdbtk !src/gdb/testsuite/gdb.gdbtk src/gdb and this interacts badly with passing the -d option to co as well. The thing is, even if we get this to work, the way gdb's cvs is set up still seems a bit crazy. code imports run 'cvs up -Pd' in the stored working tree, and that will end up creating far more directories than we want to import. -- cvs imports fail when using alias modules https://bugs.launchpad.net/bugs/605568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
