Skip to content
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

error on awesome 3.5.6 #4

Closed
ilovepumpkin opened this issue Jun 18, 2015 · 5 comments
Closed

error on awesome 3.5.6 #4

ilovepumpkin opened this issue Jun 18, 2015 · 5 comments
Assignees

Comments

@ilovepumpkin
Copy link

Hi, thanks for your effort. I am using Ubuntu 14.04 with Awesome 3.5.6. I got an error "module 'vicious' not found". From the error, it seems that it is looking for a file vicious.lua but it your files I only see a vicious directory.
image

@setkeh
Copy link
Owner

setkeh commented Jun 19, 2015

It looks like when you have pulled the repo the link to the vicious repo did not work is there any files in the vicious directory and if not try pulling vicious your self if there is files c into that directory and update them by doing a git pull.

if you can please provide more info on how you ran into this error that would also be helpfull.

thanks,

@ilovepumpkin
Copy link
Author

Yes, vicious is empty. I noticed that http://git.sysphere.org/vicious is broken - it says 'No repositories found'.

@setkeh
Copy link
Owner

setkeh commented Jun 19, 2015

try http://git.sysphere.org/vicious/ im not 100% sure why the trailing / matters but apparently it does ill add the new link to the pull and hopefully that resolves the issue :) its not really an issue with my repo just the linking to the vicious repo :D

setkeh added a commit that referenced this issue Jun 19, 2015
@setkeh setkeh self-assigned this Jun 19, 2015
@setkeh
Copy link
Owner

setkeh commented Jun 19, 2015

Ok i have fixed the Link in the Submodule and updated the README i had forgotten to add to the command the --recursive flag that tells git to download submodules after cloning master so you can either remove the config and re clone with the updated command (recommended so you get the new submodule) or you can try to update the submodule manually by doing the following .

git submodule init
git submodule update

but i cannot guarantee that will work since the link may still be broken in the commit you pulled but im not so sure it was completely to blame :D

Hope this resolves the Issue for you.

@setkeh setkeh closed this as completed Jun 19, 2015
@ilovepumpkin
Copy link
Author

Thank you very much! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants