JoeHill wrote: 

> Just did an svn up to Revision: 643, but I'm still getting an unmatched
> checksum error from gtkpod.
> 
> This is what it shows in the gpodder console:
> 
> [42270.381] (iPodDevice) Error when writing iTunesDB.ext
> Traceback (most recent call last):
>   File "/home/joehill/svn/gpodder/src/gpodder/sync.py", line 211, in close
>     db = gpod.ipod.Database(self.mountpoint)
>   File "/usr/lib/python2.4/site-packages/gpod/ipod.py", line 85, in __init__
>     self._load_gtkpod_extended_info()
>   File "/usr/lib/python2.4/site-packages/gpod/ipod.py", line 101, in
> _load_gtkpod_extended_info gtkpod.parse(itdbext_file, self, self._itdb_file)
>   File "/usr/lib/python2.4/site-packages/gpod/gtkpod.py", line 108, in parse
>     tracks_by_sha[sha1_hash(track.ipod_filename())] = track
>   File "/usr/lib/python2.4/site-packages/gpod/gtkpod.py", line 25, in
> sha1_hash size = os.path.getsize(filename)
>   File "/usr/lib/python2.4/posixpath.py", line 139, in getsize
>     return os.stat(filename).st_size
> TypeError: coercing to Unicode: need string or buffer, NoneType found
> 
> Googling that last bit got me this:
> 
> "This may be an indication that in your database you have a record with a
> None value, e. g.
> 
>         [('Developmental Neurobiology', 'ANAT2008'),
>          ('Neuroanatomy', 'ANAT2009'),
>          ('Man in black', None)])
> 
> and most likely the right fix is to correct the database entry and make sure
> that no new such records can be entered into it."
> 
> However, I have no idea how I would go about following this advice...

sorry, should have given a link to what I found:

http://mail.python.org/pipermail/python-list/2006-July/395253.html

-- 
JoeHill
++++++++++++++++++++
Bender: "You know the secret of traditional robot cooking? Start with a good
high-quality oil, then eat it." 

Attachment: signature.asc
Description: PGP signature

_______________________________________________
gpodder-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-devel

Reply via email to