Hi!
Elena Grandi <elena.valha...@gmail.com> writes:
> When trying to use a recent ( > 2013-01-30 ) .wot file from
> http://wot.christoph-egger.org/ I get the following error:
>
> $ wotsap -w 2013-02-09.wot 01809E2A
> Strange. Found longkeys file.
> Traceback (most recent call last):
> File "/usr/bin/wotsap", line 1903, in <module>
> wotsapmain(sys.argv)
> File "/usr/bin/wotsap", line 1751, in wotsapmain
> wot = Wot(wotfile)
> File "/usr/bin/wotsap", line 1471, in __init__
> self.loadfile(dumpfile)
> File "/usr/bin/wotsap", line 1484, in loadfile
> self.filename, self.fileversion, self.debug) = loadfile(dumpfile)
> File "/usr/bin/wotsap", line 462, in loadfile
> f.seek(size + (size&1), 1)
> IOError: [Errno 29] Illegal seek
>
> bunzip2: I/O or other error, bailing out. Possible reason follows.
> bunzip2: Broken pipe
> Input file = (stdin), output file = (stdout)
>
> The .wot file is a valid bzip2 file (tested with bunzip2 2013-02-09.wot)
> and it seems that the pathfinder at http://pgp.cs.uu.nl/ is able to
> read the new files, which is why I suspect (but I'm not sure) that the
> problem
> could be in wotsap itself.
Newer wotsap files were created with an additional file content (I'm
trying to get something longer than 4byte short IDs in). Must have
missed to check with wotsap for compatibility there. I'll probably
revert the change for now (doesn't work as intended right now anyway)
but would be cool if wotsap could deal wiuth an additional component in
the ar archive!
Christoph
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
