Bug#745678: broken by upgrade

[Joey Hess]

Package: assword
Version: 0.7-1
Severity: important

joey@darkstar:~>assword gui
Traceback (most recent call last):
  File "/usr/bin/assword", line 267, in <module>
    gui(sys.argv[2:], method=method)
  File "/usr/bin/assword", line 218, in gui
    db = open_db(keyid)
  File "/usr/bin/assword", line 95, in open_db
    db = assword.Database(DBPATH, keyid)
  File "/usr/lib/python2.7/dist-packages/assword.py", line 48, in __init__
    cleardata = self._decryptDB(self.dbpath)
  File "/usr/lib/python2.7/dist-packages/assword.py", line 72, in _decryptDB
    raise DatabaseError(sigs, 'Signature on database was not fully valid.')
TypeError: __init__() takes exactly 2 arguments (3 given)
- exit 1

Very happy about the plain json file format right about now!

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages assword depends on:
ii  python                2.7.5-5
ii  python-gpgme          0.3-1
ii  python-gtk2           2.24.0-3+b1
ii  python-pkg-resources  3.4.4-1

Versions of packages assword recommends:
ii  python-xdo  0.2-2
ii  xclip       0.12+svn84-4

assword suggests no packages.

-- no debconf information

-- 
see shy jo

signature.asc
Description: Digital signature