update to python-dnspython needed for code bug fix

I didn't look at the commit, but if it's reasonably self contained to the
issue you've described, it should be doable. I'll try and have a look next
week. If you don't see any progress on this in a week, please send me a ping.

In order to get the fix for this into Maverick (since it's post-release), I will need a test case that a QA person could use to verify the problem and the fix. Could you provide a minimal python script that demonstrates the problem?

This bug was fixed in the package dnspython - 1.8.0-1ubuntu1

---------------
dnspython (1.8.0-1ubuntu1) natty; urgency=low

  * Fix TSIG algorithm value passing, upstream git commit
    e80c56c6c5c6dd7aa12c439b1f3b664811f65dcb (LP: #660749)
 -- Scott Kitterman <email address hidden> Fri, 15 Oct 2010 10:22:34 -0400

I've gone ahead and uploaded this for maverick-proposed on the assumption that you'll provide the test case.

Since I've never committed a package request for Ubuntu before, I'm not sure exactly what you folks require. To provide a test case for this, one would need a BIND server running and configured to accept DDNS updates for a particular zone with TSIG keys for authentication.

The test I did was running my python script against the Ubuntu-provided python-dnspython package and the compiled-from-git-checkout that contains the above code fix from the module author. With the former package my script showed the above traceback. With the compiled-from-git package, it worked as expected.

The script I used on both tests was:

add_dnsrecord.py:
----------------------------------
#!/usr/bin/env python

import dns.query
import dns.tsigkeyring
import dns.update
import sys

keyring = dns.tsigkeyring.from_text({
    'ddns-key.' : "kzz766iy/JXF/rUkFuFSKQ=="
})

update = dns.update.Update('test.mydomaintest.net.', keyring = keyring)
update.replace('host4', 300, 'A', sys.argv[1])

response = dns.query.tcp(update,'10.10.0.1')
---------------------------
executed as: add_dnsrecord.py 10.30.0.4

Thank you.

Particularly for a first attempt, your report was very complete and thorough. You can be the QA person that validates the fixed package solves the problem once it's reviewed by the ubuntu-sru team and accepted. Given the non-trivial setup requirements, that's likely to get the package validated the most quickly.

Now we wait for the Stable Release Updates (SRU) team to review and accept this.

Accepted dnspython into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Works great now! Thanks to all for the quick fix, I look forward to making this into the dominant repositories.

package info:
jforman@monitor:~$ apt-cache showpkg python-dnspython
Package: python-dnspython
Versions:
1.8.0-1ubuntu0.1 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_maverick-proposed_main_binary-amd64_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_maverick-proposed_main_binary-amd64_Packages
                  MD5: 5c7ff37ec0055b47241c383f2c0e3c03

1.8.0-1 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick_main_binary-amd64_Packages)
 Description Language:
                 File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick_main_binary-amd64_Packages
                  MD5: 5c7ff37ec0055b47241c383f2c0e3c03
.....

Executing the same script as above, this time without error:
jforman@monitor:~$ ./add_dnsrecord.py 10.30.0.44
jforman@monitor:~$

I would consider this issue fixed, at least from my viewpoint.

This bug was fixed in the package dnspython - 1.8.0-1ubuntu0.1

---------------
dnspython (1.8.0-1ubuntu0.1) maverick-proposed; urgency=low

  * Fix TSIG algorithm value passing, upstream git commit
    e80c56c6c5c6dd7aa12c439b1f3b664811f65dcb (LP: #660749)
 -- Scott Kitterman <email address hidden> Fri, 15 Oct 2010 10:22:34 -0400