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
Specify awesome version beyond "git" #10
Comments
FWIW, the error I get with master is different:
|
Thanks for the report! Previously the awesome-git package in the AUR worked perfectly, it would appear that awesome recently updated the API, effectively borking my config. Ill work on updating it this evening! |
Thanks! I think any -git package, by definition is a moving target. So it's better to pinpoint a SHA or tag if possible. |
This is taking a lot longer than i anticipated, I'm essentially recreating the config piece by piece on the most recent non git branch (this will ensure stability and allow non arch distros to run it without compiling from github). That being said, have made a lot of progress and am aiming to push the new version out on friday |
Looking like it will be a sunday release, all that is left to do it the left panel, however the icons are being difficult Current changes are on branch 4.3 |
I tried using the master of
awesome
(29f6387defd
) but that doesn't work with this config. I also tried6101ef51
(which is currently in the AUR PKGBUILD of awesome-git) but that also doesn't work. I'm getting the following error:This is pretty hard to google, but it seems like this is a part of awesome that's removed/renamed in more recent versions. So what's the latest version (git SHA) of awesome that works with this config?
The text was updated successfully, but these errors were encountered: