This bug was already fixed in the last version available on Debian
** Changed in: dnsproxy (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (674186).
https://bugs.launchpad.net
Nice to see that a year after the official LTS release, this package is
still unusable. 1.16 works, and is in every other non-LTS release
since. Can we get an official backport please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I faced the same problem but I am not able to understand how to apply the
solution.
I manually downloaded from here
wget
http://debian.nctu.edu.tw/ubuntu//pool/universe/d/dnsproxy/dnsproxy_1.16-0.1_amd64.deb
and then tried dpkg -i dnsproxy_1.16-0.1_amd64.deb
as I am having a 64 bit lucid server
** Tags added: lucid
--
dnsproxy will not start: symbol lookup error
https://bugs.launchpad.net/bugs/567008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
Until this issue is fixed in Ubuntu using the dnsproxy_1.16-0.1 package
from Debian unstable works fine on Lucid.
--
dnsproxy will not start: symbol lookup error
https://bugs.launchpad.net/bugs/567008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed