-
Notifications
You must be signed in to change notification settings - Fork 42
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
Can't run sudo takyctl systemd --user bluetack
#79
Comments
|
It looks like |
@gncnpk would you say this is a bug? Hit this following instructions in getting started using ubuntu. |
@cniles Yes, I'll take a look after work and see what I can do to fix it and make a PR |
Oh dear. This is one of the ugly parts of taky, the setup script. I really should have this fixed, since it's what's in the documentation! @gncnpk Do you think you will submit a PR? I'd love to have more contributors to the codebase! |
Hi @tkuester, I would be glad to submit a PR! How/what should the setup script exactly do/check for? |
First, it should be noted that the configuration system is terribly broken, and in desperate need of overhaul! I was able to recreate the bug by deleting all previous installs and configuration files, and then running:
If I remember correctly, |
Gotcha, will do that now, as a quick fix for new users attempting to use taky, and later on we can work together on overhauling the configuration system. |
Hoping not to disturb with my noob nonsense, here's how I fixed it (using Debian 10 but I assume it's worht trying on other distros as well):
edited line 138 as follows:
|
Hello, all! Not trying to pile on, but I just ran into this issue and I'm unsure what the recommended workaround is. Should I make the change as @wuhei suggests above? Or should I pull down the latest version from Github instead? (And if I should do the latter, is it going to create a problem to install the Github version on top of the released For completeness, this is what I am seeing, on a brand-new install of Ubuntu 22.04 (which comes with Python 3.10), with
|
Fixes #79. cfg_path was a terrible decision, and really shouldn't exist. The idea was for the config object to keep track of where it was loaded from -- but I'm abusing the ever loving stuffing out of it, and it should be removed in a future release. For the time being, however, I'm moving this line within the conditional to ensure that cfg_path is only set when we are directly reading a file on the disk. It's pedantic, but hopefully this will prevent any further undefined behavior until I can revamp the config system.
Hey everyone! I've pushed the fix to the To install the
|
@tkuester Just tested your next branch fix and it appears to work fine. Debian 12 (container on top of Proxmox) with system wide install. |
Attempts to run
sudo takyctl systemd --user bluetack
end with following error:The text was updated successfully, but these errors were encountered: