Closed ThomasHauth closed 11 years ago
Hi Thomas, this should actually work out fine if you use the latest version of git-cms-addpkg (because it will always add .gitignore to the sparse checkout first).
Giulio ( @ktf ), could you push the latest tools to some CMSSW release ?
.A
Hi Andrea, I just tried with the latest git-cms-addpkg version from git and it works fine.
Thanks Thomas
A call to "git cms-addpkg Foo/Bar" in a Vanilla CMSSW project area gives an unclear error message: ... bash-4.1$ git cms-addpkg Foo/Bar No release tags specified, using default CMSSW_7_0_0_pre1. You are on branch CMSSW_7_0_X Checking out Foo/Bar in tag CMSSW_7_0_0_pre1. Cloning into '/build/hauth/cmssw/TrackingMat/CMSSW_7_0_0_pre1/src'... remote: Counting objects: 620, done. remote: Compressing objects: 100% (231/231), done. remote: Total 305 (delta 215), reused 162 (delta 74) Receiving objects: 100% (305/305), 102.36 KiB | 0 bytes/s, done. Resolving deltas: 100% (215/215), completed with 154 local objects. error: Sparse checkout leaves no entry on working directory fatal: Could not reset index file to revision 'CMSSW_7_0_0_pre1'.
This will happen only if there have not been any other (valid) packages added. After adding valid packages, the output is more clear:
bash-4.1$ git cms-addpkg Foo/Bar No release tags specified, using default CMSSW_7_0_0_pre1. You are on branch CMSSW_7_0_X Checking out Foo/Bar in tag CMSSW_7_0_0_pre1. Error: package Foo/Bar does not exist in tag CMSSW_7_0_0_pre1.
Thanks, Thomas