-
-
Notifications
You must be signed in to change notification settings - Fork 562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to scan on user home with ~ #1748
Comments
@pombredanne Is scancode failing to scan a folder in your home directory? I am unable to reproduce the error. |
@pombredanne Thanks, I am able to reproduce the error with the attached zip. |
@pombredanne The issue is with the directory |
OK, I think we can now drop ignoring RCS ten... I have not seen RCS directories in ages, and digging in them if we ever meet some real ones is not a problem IMHO. We still need to avoid this kind of errors too BEFORE removing skipping rcs |
* Create new test Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Remove RCS from list of VCS names to ignore #1748
We now scan the RCS directory and we properly ignore directories when creating the codebase. Closing. |
* Create new test Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
I've come across this same problem running scancode 3.0.2 on ubuntu 18.04. The directory named "rcs" was ignored by scancode, but not its contents. It seems to me that it might be a good idea not only to remove "RCS" from the ignored list but also to make checks case sensitive (except on Windows) -- get_matches() in fileste.py changes the case of the item to be ignored to lower and I suggest it shouldn't. |
@adambhere Let's create a new ticket for that then. Do you have the same problem using the tip of the develop branh? |
@pombredanne We have plans to move to it, but the decision is out of my hands. |
Description
A scan to ~/ fails:
System configuration
For bug reports, it really helps us to know:
The text was updated successfully, but these errors were encountered: