-
Notifications
You must be signed in to change notification settings - Fork 4
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
Etckeeper warning because of special files #1
Comments
What are those files? Pipes? Note: I am not the original author of etckeeper, this is just a fork I create to incorporate a few changes that now have been merged upstream. http://joey.kitenet.net/code/etckeeper/ is probably the site you are looking for :-) |
Yes, that files are pipes: $ sudo ls -ls /etc/sv/project_a/supervise/control I also thought about .gitignore. I've added that files to .gitignore, but the problem did't disappear. Thank you for the information that you are not the original author. I've found his email and send him message about this problem. I think that we should leave this issue unsolved. You never know, maybe someone will fork this project and pull the solution. =) |
Did someone find a solution for this issue? It is really annoying to get those warning every night, but I guess you know this problem =). |
The bug is fixed in etckeeper 0.55. The following patch solved it for me on Ubuntu 10.04 (derived from upstream commit, see https://github.com/joeyh/etckeeper/commit/ad3fbb8d31894bfbff30e143dc18e85eed5afd20
|
And here is the same patch for Debian Squeeze:
|
I'm using etckeeper and it works great except for one thing. It shows errors when trying to commit:
etckeeper warning: special files could cause problems with git:
./sv/project_a/supervise/ok
./sv/project_a/supervise/control
As I understood this is because of file pre-commit.d/20warn-special-file.I've simply deleted it and after that I have no warnings. But I'm sure this is not the perfect solution =)
By the way, this behaviour is described in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529253
The text was updated successfully, but these errors were encountered: