updating kipi-plugins

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

updating kipi-plugins

Tac Tacelosky
How do I update kipi-plugins?  I'm using the .appimage, but previously had 5.6 installed via the ppa, so I think they're out of sync.  (And this may solve the oAuth problem, I've started a new thread to make it easier to search the archives for this specific issue).

> apt-cache policy kipi-plugins
kipi-plugins:
  Installed: (none)
  Candidate: 4:5.6.0-0ubuntu2
  Version table:
     4:5.6.0-0ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packag

Does appimage automatically have kipi-plugins embedded?

Feature request: on the plugins page, is it possible to include the version number of the specific plugin?  Especially since I'm guessing the plugins will be refactored to get the oAuth token automatically, rather than the cut-and-paste method.

Thanks,

Tac



Reply | Threaded
Open this post in threaded view
|

Re: updating kipi-plugins

Gilles Caulier-4
Hi,

The AppImage embed all kipi plugins, of course.

Gilles Caulier

2018-02-02 13:30 GMT+01:00 Tac Tacelosky <[hidden email]>:
How do I update kipi-plugins?  I'm using the .appimage, but previously had 5.6 installed via the ppa, so I think they're out of sync.  (And this may solve the oAuth problem, I've started a new thread to make it easier to search the archives for this specific issue).

> apt-cache policy kipi-plugins
kipi-plugins:
  Installed: (none)
  Candidate: 4:5.6.0-0ubuntu2
  Version table:
     4:5.6.0-0ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packag

Does appimage automatically have kipi-plugins embedded?

Feature request: on the plugins page, is it possible to include the version number of the specific plugin?  Especially since I'm guessing the plugins will be refactored to get the oAuth token automatically, rather than the cut-and-paste method.

Thanks,

Tac




Reply | Threaded
Open this post in threaded view
|

Re: updating kipi-plugins

Tac Tacelosky
Hmm.  My laptop shows a slightly different plugins screen, says 5.6, whereas my desktop (where Flickr is working) shows this.  Same OS, both from the appimage download on digikam.  The only difference with the laptop is that at various points it's had digikam 4 and digikam 5.6 installed.  If the individual plugins have version numbers, they'd be valuable here.

Should I run the 5.9 appimage?  There's no mention of plugin changes in 5.9, and am cautious about doing a database migration which might prevent me from using the stable 5.8.

Tac

Inline image 1

On Fri, Feb 2, 2018 at 8:34 AM, Gilles Caulier <[hidden email]> wrote:
Hi,

The AppImage embed all kipi plugins, of course.

Gilles Caulier

2018-02-02 13:30 GMT+01:00 Tac Tacelosky <[hidden email]>:
How do I update kipi-plugins?  I'm using the .appimage, but previously had 5.6 installed via the ppa, so I think they're out of sync.  (And this may solve the oAuth problem, I've started a new thread to make it easier to search the archives for this specific issue).

> apt-cache policy kipi-plugins
kipi-plugins:
  Installed: (none)
  Candidate: 4:5.6.0-0ubuntu2
  Version table:
     4:5.6.0-0ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packag

Does appimage automatically have kipi-plugins embedded?

Feature request: on the plugins page, is it possible to include the version number of the specific plugin?  Especially since I'm guessing the plugins will be refactored to get the oAuth token automatically, rather than the cut-and-paste method.

Thanks,

Tac





Reply | Threaded
Open this post in threaded view
|

Re: updating kipi-plugins

Christoph Knauer-2
Hi

I've just tested DK 5.9.0 - and here it shows also Kipi 5.6.0 as in DK 5.8.0
before?

Greetz,
Christoph

Am Freitag, 2. Februar 2018, 14:47:44 CET schrieb Tac Tacelosky:

> Hmm.  My laptop shows a slightly different plugins screen, says 5.6,
> whereas my desktop (where Flickr is working) shows this.  Same OS, both
> from the appimage download on digikam.  The only difference with the laptop
> is that at various points it's had digikam 4 and digikam 5.6 installed.  If
> the individual plugins have version numbers, they'd be valuable here.
>
> Should I run the 5.9 appimage?  There's no mention of plugin changes in
> 5.9, and am cautious about doing a database migration which might prevent
> me from using the stable 5.8.
>
> Tac

Reply | Threaded
Open this post in threaded view
|

Re: updating kipi-plugins

cool.chris65
In reply to this post by Tac Tacelosky
Hi

I've just tested DK 5.9.0 - and here it shows also Kipi 5.6.0 as in DK 5.8.0
before?

Greetz,
Christoph

Am Freitag, 2. Februar 2018, 14:47:44 CET schrieb Tac Tacelosky:

> Hmm.  My laptop shows a slightly different plugins screen, says 5.6,
> whereas my desktop (where Flickr is working) shows this.  Same OS, both
> from the appimage download on digikam.  The only difference with the laptop
> is that at various points it's had digikam 4 and digikam 5.6 installed.  If
> the individual plugins have version numbers, they'd be valuable here.
>
> Should I run the 5.9 appimage?  There's no mention of plugin changes in
> 5.9, and am cautious about doing a database migration which might prevent
> me from using the stable 5.8.
>
> Tac

Reply | Threaded
Open this post in threaded view
|

Re: updating kipi-plugins

Gilles Caulier-4
Mine, from the AppImage :

digikam version 5.9.0
CPU cores: 3
Eigen: 3.2.5
Exiv2: 0.26
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
KF5: 5.42.0
LensFun: 0.3.2-0
LibCImg: 130
LibJPEG: 80
LibJasper: 1.900.29
LibLCMS: 2080
LibLqr support: No
LibPGF: 7.15.32
LibPNG: 1.6.34
LibRaw: 0.18.8
LibTIFF: 4.0.9
Marble: 0.27.20
Parallelized demosaicing: Yes
Qt: 5.9.3
AkonadiContact support: no
Baloo support: no
Calendar support: yes
DBus support: Yes
Database backend: QSQLITE
HTML Gallery support: yes
Kipi-Plugins: 5.9.0                                <<== The kipiplugins version with right value.
LibGphoto2: 2.5.16
LibKipi: 5.2.0                                        <<== Kipi library interface frozen since a while
LibOpenCV: 3.4.0
LibQtAV: 1.12.0
Media player support: Yes
Panorama support: yes

No problem...

Gilles Caulier

2018-03-19 16:47 GMT+01:00 <[hidden email]>:
Hi

I've just tested DK 5.9.0 - and here it shows also Kipi 5.6.0 as in DK 5.8.0
before?

Greetz,
Christoph

Am Freitag, 2. Februar 2018, 14:47:44 CET schrieb Tac Tacelosky:
> Hmm.  My laptop shows a slightly different plugins screen, says 5.6,
> whereas my desktop (where Flickr is working) shows this.  Same OS, both
> from the appimage download on digikam.  The only difference with the laptop
> is that at various points it's had digikam 4 and digikam 5.6 installed.  If
> the individual plugins have version numbers, they'd be valuable here.
>
> Should I run the 5.9 appimage?  There's no mention of plugin changes in
> 5.9, and am cautious about doing a database migration which might prevent
> me from using the stable 5.8.
>
> Tac


Reply | Threaded
Open this post in threaded view
|

Re: updating kipi-plugins

cool.chris65

Mine, from DK 5.8.0 Appimage:

 

digikam version 5.8.0

CPU cores: 4

Eigen: 3.2.5

Exiv2: 0.26

Exiv2 can write to Jp2: Ja

Exiv2 can write to Jpeg: Ja

Exiv2 can write to Pgf: Ja

Exiv2 can write to Png: Ja

Exiv2 can write to Tiff: Ja

Exiv2 supports XMP metadata: Ja

KF5: 5.36.0

LensFun: 0.3.2-0

LibCImg: 130

LibJPEG: 80

LibJasper: 1.900.29

LibLCMS: 2080

LibLqr support: Nein

LibPGF: 7.15.32

LibPNG: 1.6.26

LibRaw: 0.18.6

LibTIFF: 4.0.6

Marble: 0.27.20

Parallelized demosaicing: Ja

Qt: 5.9.1

Datenbanktreiber: QMYSQL

HTML Gallery support: Ja

Interner Datenbank-Server:: Keine

KIPI-Module: 5.6.0

LibGphoto2: 2.5.14

LibKipi: 5.2.0

LibOpenCV: 3.2.0

LibQtAV: 1.12.0

Unterstützung für Baloo: Nein

Unterstützung für Calender: Ja

Unterstützung für DBus: Ja

Unterstützung für Medienwiedergabe: Ja

Unterstützung für Panorama: Ja

Unterstützung von Akonadi-Kontakten: Nein

 

Maybe a problem with a parallel installed version from kubuntu backports (DK 5.6.0)? Should I delete the DK-Packages and it's komponents, if they are not used by other tools?

 

Greets,

 

Christoph

 

Am Montag, 19. März 2018, 17:00:19 CET schrieb Gilles Caulier:

> Mine, from the AppImage :

>

> digikam version 5.9.0

> CPU cores: 3

> Eigen: 3.2.5

> Exiv2: 0.26

> Exiv2 can write to Jp2: Yes

> Exiv2 can write to Jpeg: Yes

> Exiv2 can write to Pgf: Yes

> Exiv2 can write to Png: Yes

> Exiv2 can write to Tiff: Yes

> Exiv2 supports XMP metadata: Yes

> KF5: 5.42.0

> LensFun: 0.3.2-0

> LibCImg: 130

> LibJPEG: 80

> LibJasper: 1.900.29

> LibLCMS: 2080

> LibLqr support: No

> LibPGF: 7.15.32

> LibPNG: 1.6.34

> LibRaw: 0.18.8

> LibTIFF: 4.0.9

> Marble: 0.27.20

> Parallelized demosaicing: Yes

> Qt: 5.9.3

> AkonadiContact support: no

> Baloo support: no

> Calendar support: yes

> DBus support: Yes

> Database backend: QSQLITE

> HTML Gallery support: yes

> Kipi-Plugins: 5.9.0 <<== The kipiplugins

> version with right value.

> LibGphoto2: 2.5.16

> LibKipi: 5.2.0 <<== Kipi library

> interface frozen since a while

> LibOpenCV: 3.4.0

> LibQtAV: 1.12.0

> Media player support: Yes

> Panorama support: yes

>

> No problem...

>

> Gilles Caulier

 

 

Reply | Threaded
Open this post in threaded view
|

Re: updating kipi-plugins

Gilles Caulier-4
yes, you can remove.

In fact kipi-plugins version is taken from .desktop file. Probably the system based file are loaded before item from the bundle...

In all cases, this situation will be not reproducible with 6.0.0 where a lots of changes have been done to reduce the puzzle between these components.

Gilles Caulier

2018-03-19 17:40 GMT+01:00 <[hidden email]>:

Mine, from DK 5.8.0 Appimage:

 

digikam version 5.8.0

CPU cores: 4

Eigen: 3.2.5

Exiv2: 0.26

Exiv2 can write to Jp2: Ja

Exiv2 can write to Jpeg: Ja

Exiv2 can write to Pgf: Ja

Exiv2 can write to Png: Ja

Exiv2 can write to Tiff: Ja

Exiv2 supports XMP metadata: Ja

KF5: 5.36.0

LensFun: 0.3.2-0

LibCImg: 130

LibJPEG: 80

LibJasper: 1.900.29

LibLCMS: 2080

LibLqr support: Nein

LibPGF: 7.15.32

LibPNG: 1.6.26

LibRaw: 0.18.6

LibTIFF: 4.0.6

Marble: 0.27.20

Parallelized demosaicing: Ja

Qt: 5.9.1

Datenbanktreiber: QMYSQL

HTML Gallery support: Ja

Interner Datenbank-Server:: Keine

KIPI-Module: 5.6.0

LibGphoto2: 2.5.14

LibKipi: 5.2.0

LibOpenCV: 3.2.0

LibQtAV: 1.12.0

Unterstützung für Baloo: Nein

Unterstützung für Calender: Ja

Unterstützung für DBus: Ja

Unterstützung für Medienwiedergabe: Ja

Unterstützung für Panorama: Ja

Unterstützung von Akonadi-Kontakten: Nein

 

Maybe a problem with a parallel installed version from kubuntu backports (DK 5.6.0)? Should I delete the DK-Packages and it's komponents, if they are not used by other tools?

 

Greets,

 

Christoph

 

Am Montag, 19. März 2018, 17:00:19 CET schrieb Gilles Caulier:

> Mine, from the AppImage :

>

> digikam version 5.9.0

> CPU cores: 3

> Eigen: 3.2.5

> Exiv2: 0.26

> Exiv2 can write to Jp2: Yes

> Exiv2 can write to Jpeg: Yes

> Exiv2 can write to Pgf: Yes

> Exiv2 can write to Png: Yes

> Exiv2 can write to Tiff: Yes

> Exiv2 supports XMP metadata: Yes

> KF5: 5.42.0

> LensFun: 0.3.2-0

> LibCImg: 130

> LibJPEG: 80

> LibJasper: 1.900.29

> LibLCMS: 2080

> LibLqr support: No

> LibPGF: 7.15.32

> LibPNG: 1.6.34

> LibRaw: 0.18.8

> LibTIFF: 4.0.9

> Marble: 0.27.20

> Parallelized demosaicing: Yes

> Qt: 5.9.3

> AkonadiContact support: no

> Baloo support: no

> Calendar support: yes

> DBus support: Yes

> Database backend: QSQLITE

> HTML Gallery support: yes

> Kipi-Plugins: 5.9.0 <<== The kipiplugins

> version with right value.

> LibGphoto2: 2.5.16

> LibKipi: 5.2.0 <<== Kipi library

> interface frozen since a while

> LibOpenCV: 3.4.0

> LibQtAV: 1.12.0

> Media player support: Yes

> Panorama support: yes

>

> No problem...

>

> Gilles Caulier