On Sat, Feb 17, 2018 at 4:48 PM, frieder <[email protected]> wrote:
> Am Freitag, den 16.02.2018, 12:05 +0300 schrieb Roman Lebedev:
>> On Fri, Feb 16, 2018 at 2:38 AM, frieder <[email protected]> wrote:
>> > Am Donnerstag, den 15.02.2018, 23:51 +0300 schrieb Roman Lebedev:
>> >> Please keep lists in cc.
>> >>
>> >> On Thu, Feb 15, 2018 at 11:46 PM, frieder <[email protected]> wrote:
>> >> > Am Mittwoch, den 14.02.2018, 23:40 +0300 schrieb Roman Lebedev:
>> >> >> On Wed, Feb 14, 2018 at 11:37 PM, frieder <[email protected]> wrote:
>> >> >> > Hallo,
>> >> >
>> >> >> 2.2.1 is about one year old, btw.
>> >
>> >> Not the db's. The package itself.
>> >
>> > Instead of V. 0.2.8 wich came with Debian I updated lensfun libary to:
>> >
>> > /usr/lib/liblensfun.so.0.3.2
>> >
>> > I think it is from projedt home on sourceforge (when remerbered corret).
>> > It is derived from the tar-file: lensfun-0.3.2.tar.gz
>> Congrats, you get to keep the pieces.
>> Don't turn Debian into FrankenDebian / slackware :)
>>
>> Downgrading back will solve that geometry = "thoby fish-eye"
>> issue. Google will tell you the details, but basically it's an ABI
>> problem.
>>
> Well, well, now I dowgraded to lensfun 0.2.8 from the repository.
> I don't know if its fine now. Now my gear isn supported any more.
Uhm, is that debian *old*stable?
Because debian stable has lensfun-0.3.2 (and darktable-2.2.5 in backports).

> There are the xml files in /usr/share/lensfun/ and
> in /var/lib/lensfun-updates/version_1 which I need both for my camera
> gear. But it looks like lensfun 0.2.8 doesn't care about later.

Not surprising, given just how old debian oldstable is...

I'd try http://wilson.bronger.org/db/version_0.tar.bz but no idea how
up-to-date it is.

> A search engine isn't much help at the moment:
> http://lensfun.sourceforge.net/manual/dbsearch.html
>
> Fred.
Roman.

> btw: Is ABI = application binary interface?
Yeah
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to