Of course, it's not until exactly 2 minutes after I submit the bug report that I figure out the fix. I maintain that this is still a bug, because the installation should have failed, but at least I have a workaround now.
After noticing that dnsdomainname complained during the install, I decided to wager that it was the main contributing factor, so I started fiddling around and found that it was, indeed the problem. One just needs to make sure that dnsdomainname returns a proper result, and that is done by fiddling with either your dns or the /etc/hosts file... the latter is what I did. After dnsdomainname returned a proper result, I did
and all was well. Perhaps there should be a fallback for when dnsdomainname doesn't return properly during installation? Either way, installation shouldn't fail that critically when there is something amiss with the dns, no?
Of course, it's not until exactly 2 minutes after I submit the bug report that I figure out the fix. I maintain that this is still a bug, because the installation should have failed, but at least I have a workaround now.
After noticing that dnsdomainname complained during the install, I decided to wager that it was the main contributing factor, so I started fiddling around and found that it was, indeed the problem. One just needs to make sure that dnsdomainname returns a proper result, and that is done by fiddling with either your dns or the /etc/hosts file... the latter is what I did. After dnsdomainname returned a proper result, I did
$ sudo aptitude purge krb5-admin-server
$ sudo apt-get install krb5-admin-server
and all was well. Perhaps there should be a fallback for when dnsdomainname doesn't return properly during installation? Either way, installation shouldn't fail that critically when there is something amiss with the dns, no?
-Matt