[KPhotoAlbum] 3.1.0-rc1 released - scanning for new photos problem (test with exiv2-0.12 and newer snapshot)

[Martin Jost]

Jan Kundrát schrieb:
>> With 0.15 I now got the file names as titles on import of the new photos
>> as expected.
>>     
>
> That means that earlier versions of exiv2 didn't contain some
> interesting Exif key name. I've tried to have a quick glance at their
> SVN history, but wasn't able to see anything useful.
>
>   
>> I tried to go back to exiv2-0.12 and this crashed on the same reread.
>> (See attached stack backtrace)
>> On the terminal I got:
>> --------------
>>     
>>> /opt/kde3/bin/kphotoalbum
>>>       
>> terminate called after throwing an instance of 'Exiv2::Error'
>> KCrash: Application 'kphotoalbum' crashing.
>>     
>
> Please try it with newer KPA checkout and exiv2-0.12.
>
>   
Ok, here are the results:
> kphotoalbum
QSettings: failed to open file '/usr/lib/qt3//etc/settings/qtrc'
QSettings: failed to open file '/usr/lib/qt3//etc/settings/qtrc'
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0281.jpg for label: Invalid tag name or
ifdId `XPTitle', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0281.jpg for description: Invalid tag
name or ifdId `XPComment', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0281.jpg for categories: Invalid tag
name or ifdId `XPKeywords', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0282.jpg for label: Invalid tag name or
ifdId `XPTitle', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0282.jpg for description: Invalid tag
name or ifdId `XPComment', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0282.jpg for categories: Invalid tag
name or ifdId `XPKeywords', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0283.jpg for label: Invalid tag name or
ifdId `XPTitle', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0283.jpg for description: Invalid tag
name or ifdId `XPComment', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0283.jpg for categories: Invalid tag
name or ifdId `XPKeywords', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0284.jpg for label: Invalid tag name or
ifdId `XPTitle', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0284.jpg for description: Invalid tag
name or ifdId `XPComment', ifdId 1
kphotoalbum: Exiv2 exception when parsing file
/images/fotos/neu/2007-09-29/img_0284.jpg for categories: Invalid tag
name or ifdId `XPKeywords', ifdId 1
[...]

But no crash any more. OTOH the filename as description below the photos
is missing, despite the fact I had the mapping dialog opened and closed
again. (This worked as expected, when I changed back to exiv2-0.15. It
seems the exception from 0.12 somehow "kills" this)

Do you need a downscaled version of one of the photos ?

Martin

P.S.:
>> So CategoryItem.moc seems to be missing - and indeed, I couldn't find(1) it...
> 
> It is autogenerated. I've seen such stuff before and it is because the
> build system sucks. 

It will be great relief to me to know, that not only our build system at
work is badly broken in some respects.... ;-)

> A safe workaround is to proceed from the `make -f
> Makefile.cvs` point in the docs [1] on, the quicker (which might not
> work) is to either run `make clean` in kphotoalbum/Settings or `touch
> kphotoalbum/CategoryItem.{cpp,h}`. The later might not work, I don't
> remember how I fixed that, sorry.
> 
> And when everything fails, just do whole [1] from the beginning.

Thanks for the prompt reply. The touch did the trick mostly.
(This did a new configure, which funnily now failed because of missing
dcraw (or some such) I configured without this)

> BTW, if you are an IRC-friendly guy (or aren't too much scared to become
> one), you will usually get faster replies at #kphotoalbum on freenode.

No, not until now. Seems I have to give it a try.
Does this really mean, that busy maintainers work with IRC running to
look for questions ? Isn't that a source of permanent distraction ?
(Ok, mails like these are probably too... ;-)