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

Doesn't automatically pull in python-dnspython on Debian 9 #14

Closed
JamesTheAwesomeDude opened this issue Jun 17, 2018 · 8 comments

Comments

@JamesTheAwesomeDude
Copy link

commented Jun 17, 2018

When installing version 0.7.1(-1) on a fresh Debian 9.4.0 installation, it doesn't pull in the necessary dependencies.

This creates an error message about missing the DNS module during installation, and it's not at all obvious how to fix the error afterwards (when the DUID needs to be made by-hand).

@JamesTheAwesomeDude

This comment has been minimized.

Copy link
Author

commented Jun 17, 2018

(for some reason, even when DUID generation fails, the package is still tagged as fully-installed, so not even apt-get install -f will finish up the configuration after the dependencies have been manually acquired.)

@HenriWahl

This comment has been minimized.

Copy link
Owner

commented Jun 17, 2018

Thanks for the hint. Actually the package is still built on a Debian 8 because it worked, so it might be a good idea to port the packaging to Debian 9. I will check this asap.
After resolving the DNS issue - does it work at all?

@JamesTheAwesomeDude

This comment has been minimized.

Copy link
Author

commented Jun 17, 2018

Yeah, it's actually a pretty great server! Once I had generated and inserted the DUID manually, it really works well. 😄👍 (Although, it might be good to at least document which of the three config files scattered across /etc is the one which must be edited to make it actually respond to clients. I figured it out, it's not a massive undertaking; but it's the kind of troubleshooting that doesn't seem like it belongs out-of-the-box.)

<offtopic>
Only thing that seemed "off" was that it temporarily semi-broke the OS's default DNS suffix (the IPv4 server WAS advertising it; the IPv6 server was NOT: it showed up in Win10 Task Manager, but most applications seemed not to resolve the domains); I fixed it by hard-coding the network's specific domain $sitexxx$.hsv.al.us.xn--l3h.$mydomain$ into the config file. (The IPv4 server is the canonical/authoritative source of site domain information)

but that (i.e., slaving an aspect of dhcpy6d's configuration to a source) is probably pretty easy to implement with something like a DHCP(v4) client hook, if it ever becomes an issue.

@HenriWahl

This comment has been minimized.

Copy link
Owner

commented Jun 18, 2018

Thanks for the hint - added the info to documentation.

Regarding the offtopic: what was the configuration statement to tell clients about the DNS suffix?

@HenriWahl

This comment has been minimized.

Copy link
Owner

commented Jun 18, 2018

Now with db1c16b the package builds with Debian 9 and has the python-dns dependencies included.

@HenriWahl HenriWahl closed this Jun 18, 2018

@karaluh

This comment has been minimized.

Copy link

commented Jul 9, 2018

Still not properly fixed. python-dnspython is only suggested and not dependent on. From the control file:

Depends: adduser, ucf, init-system-helpers (>= 1.18~), python, python:any (<< 2.8), python:any (>= 2.7.5-5~)
Suggests: python-dnspython, python-mysqldb, python-psycopg2

Edit:
OK, I see that it's fixed in the code, but the binary package doesn't have the fix included.

@HenriWahl

This comment has been minimized.

Copy link
Owner

commented Jul 9, 2018

Where did you get the binary from?

Edit:
Found it on homepage - building new package right now.

@HenriWahl

This comment has been minimized.

Copy link
Owner

commented Jul 10, 2018

Uploaded fixed package - thanks for the hint!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.