digiKam › digikam-devel

All kipi-plugins are gone ...

Classic

List

Threaded

22 messages Options

Veaceslav Munteanu

All kipi-plugins are gone ...

Hello.

I was working with my students on bugs when after a git pull and new build, all kipi-plugins are missing.

We have the same problem on all 3 computers and it's a result of a recent commit, because i pulled this morning and everything was ok and after a hour it was broken.

Can you help me?

--
Veaceslav

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Pierre Hanser

Re: All kipi-plugins are gone ...

same thing here

Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :

> Hello.
>
> I was working with my students on bugs when after a git pull and new
> build, all kipi-plugins are missing.
> We have the same problem on all 3 computers and it's a result of a
> recent commit, because i pulled this morning and everything was ok and
> after a hour it was broken.
>
> Can you help me?
>
> --
> Veaceslav
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Gilles Caulier-4

Re: All kipi-plugins are gone ...

Make clean, and reinstall all including libkipi

Gilles Caulier

2012/3/17 Pierre Hanser <[hidden email]>:

> same thing here
>
> Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :
>> Hello.
>>
>> I was working with my students on bugs when after a git pull and new
>> build, all kipi-plugins are missing.
>> We have the same problem on all 3 computers and it's a result of a
>> recent commit, because i pulled this morning and everything was ok and
>> after a hour it was broken.
>>
>> Can you help me?
>>
>> --
>> Veaceslav
>>
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Veaceslav Munteanu

Re: All kipi-plugins are gone ...

compiled libkipi from sources, made a clean digikam build. No luck :(

On Sat, Mar 17, 2012 at 7:41 PM, Gilles Caulier <[hidden email]> wrote:

Make clean, and reinstall all including libkipi

Gilles Caulier

2012/3/17 Pierre Hanser <[hidden email]>:

> same thing here
>
> Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :
>> Hello.
>>
>> I was working with my students on bugs when after a git pull and new
>> build, all kipi-plugins are missing.
>> We have the same problem on all 3 computers and it's a result of a
>> recent commit, because i pulled this morning and everything was ok and
>> after a hour it was broken.
>>
>> Can you help me?
>>
>> --
>> Veaceslav
>>
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

--
Veaceslav

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Veaceslav Munteanu

Re: All kipi-plugins are gone ...

It seem that digikam can't see my shared libkipi when i install it from sources>

[slavik@ArchAngel build]$ digikam

digikam: error while loading shared libraries: libkipi.so.8: cannot open shared object file: No such file or directory

[slavik@ArchAngel build]$ sudo pacman -S libkipi

resolving dependencies...

looking for inter-conflicts...

Targets (1): libkipi-4.8.1-1

Total Installed Size: 0.25 MiB

Proceed with installation? [Y/n] y

(1/1) checking package integrity

error: failed to commit transaction (conflicting files)

libkipi: /usr/include/libkipi/exportinterface.h exists in filesystem

libkipi: /usr/include/libkipi/extension.h exists in filesystem

libkipi: /usr/include/libkipi/imagecollection.h exists in filesystem

libkipi: /usr/include/libkipi/imagecollectionselector.h exists in filesystem

libkipi: /usr/include/libkipi/imagecollectionshared.h exists in filesystem

libkipi: /usr/include/libkipi/imageinfo.h exists in filesystem

libkipi: /usr/include/libkipi/imageinfoshared.h exists in filesystem

libkipi: /usr/include/libkipi/interface.h exists in filesystem

libkipi: /usr/include/libkipi/libkipi_export.h exists in filesystem

libkipi: /usr/include/libkipi/plugin.h exists in filesystem

libkipi: /usr/include/libkipi/pluginloader.h exists in filesystem

libkipi: /usr/include/libkipi/uploadwidget.h exists in filesystem

libkipi: /usr/include/libkipi/version.h exists in filesystem

libkipi: /usr/lib/libkipi.so exists in filesystem

libkipi: /usr/lib/pkgconfig/libkipi.pc exists in filesystem

libkipi: /usr/share/apps/kipi/data/kipi-icon.svg exists in filesystem

libkipi: /usr/share/apps/kipi/data/kipi-logo.svg exists in filesystem

libkipi: /usr/share/apps/kipi/data/kipi-plugins_logo.png exists in filesystem

libkipi: /usr/share/icons/hicolor/128x128/apps/kipi.png exists in filesystem

libkipi: /usr/share/icons/hicolor/16x16/apps/kipi.png exists in filesystem

libkipi: /usr/share/icons/hicolor/22x22/apps/kipi.png exists in filesystem

libkipi: /usr/share/icons/hicolor/32x32/apps/kipi.png exists in filesystem

libkipi: /usr/share/icons/hicolor/48x48/apps/kipi.png exists in filesystem

libkipi: /usr/share/kde4/servicetypes/kipiplugin.desktop exists in filesystem

Errors occurred, no packages were upgraded.

[slavik@ArchAngel build]$

Do i miss something?

On Sat, Mar 17, 2012 at 8:31 PM, Veaceslav Munteanu <[hidden email]> wrote:

compiled libkipi from sources, made a clean digikam build. No luck :(

On Sat, Mar 17, 2012 at 7:41 PM, Gilles Caulier <[hidden email]> wrote:

Make clean, and reinstall all including libkipi

Gilles Caulier

2012/3/17 Pierre Hanser <[hidden email]>:

> same thing here
>
> Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :
>> Hello.
>>
>> I was working with my students on bugs when after a git pull and new
>> build, all kipi-plugins are missing.
>> We have the same problem on all 3 computers and it's a result of a
>> recent commit, because i pulled this morning and everything was ok and
>> after a hour it was broken.
>>
>> Can you help me?
>>
>> --
>> Veaceslav
>>
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

--
Veaceslav

--
Veaceslav

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Gilles Caulier-4

Re: All kipi-plugins are gone ...

do you re-run cmake configure.

Problem is not reproducible here...

Gilles

2012/3/17 Veaceslav Munteanu <[hidden email]>:

> It seem that digikam can't see my shared libkipi when i install it from
> sources>
>
> [slavik@ArchAngel build]$ digikam
> digikam: error while loading shared libraries: libkipi.so.8: cannot open
> shared object file: No such file or directory
> [slavik@ArchAngel build]$ sudo pacman -S libkipi
> resolving dependencies...
> looking for inter-conflicts...
>
> Targets (1): libkipi-4.8.1-1
>
> Total Installed Size: 0.25 MiB
>
> Proceed with installation? [Y/n] y
> (1/1) checking package integrity
>
> error: failed to commit transaction (conflicting files)
> libkipi: /usr/include/libkipi/exportinterface.h exists in filesystem
> libkipi: /usr/include/libkipi/extension.h exists in filesystem
> libkipi: /usr/include/libkipi/imagecollection.h exists in filesystem
> libkipi: /usr/include/libkipi/imagecollectionselector.h exists in filesystem
> libkipi: /usr/include/libkipi/imagecollectionshared.h exists in filesystem
> libkipi: /usr/include/libkipi/imageinfo.h exists in filesystem
> libkipi: /usr/include/libkipi/imageinfoshared.h exists in filesystem
> libkipi: /usr/include/libkipi/interface.h exists in filesystem
> libkipi: /usr/include/libkipi/libkipi_export.h exists in filesystem
> libkipi: /usr/include/libkipi/plugin.h exists in filesystem
> libkipi: /usr/include/libkipi/pluginloader.h exists in filesystem
> libkipi: /usr/include/libkipi/uploadwidget.h exists in filesystem
> libkipi: /usr/include/libkipi/version.h exists in filesystem
> libkipi: /usr/lib/libkipi.so exists in filesystem
> libkipi: /usr/lib/pkgconfig/libkipi.pc exists in filesystem
> libkipi: /usr/share/apps/kipi/data/kipi-icon.svg exists in filesystem
> libkipi: /usr/share/apps/kipi/data/kipi-logo.svg exists in filesystem
> libkipi: /usr/share/apps/kipi/data/kipi-plugins_logo.png exists in
> filesystem
> libkipi: /usr/share/icons/hicolor/128x128/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/16x16/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/22x22/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/32x32/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/48x48/apps/kipi.png exists in filesystem
> libkipi: /usr/share/kde4/servicetypes/kipiplugin.desktop exists in
> filesystem
> Errors occurred, no packages were upgraded.
> [slavik@ArchAngel build]$
>
> Do i miss something?
>
> On Sat, Mar 17, 2012 at 8:31 PM, Veaceslav Munteanu <[hidden email]>
> wrote:
>>
>> compiled libkipi from sources, made a clean digikam build. No luck :(
>>
>>
>> On Sat, Mar 17, 2012 at 7:41 PM, Gilles Caulier <[hidden email]>
>> wrote:
>>>
>>> Make clean, and reinstall all including libkipi
>>>
>>> Gilles Caulier
>>>
>>> 2012/3/17 Pierre Hanser <[hidden email]>:
>>> > same thing here
>>> >
>>> > Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :
>>> >> Hello.
>>> >>
>>> >> I was working with my students on bugs when after a git pull and new
>>> >> build, all kipi-plugins are missing.
>>> >> We have the same problem on all 3 computers and it's a result of a
>>> >> recent commit, because i pulled this morning and everything was ok and
>>> >> after a hour it was broken.
>>> >>
>>> >> Can you help me?
>>> >>
>>> >> --
>>> >> Veaceslav
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> Digikam-devel mailing list
>>> >> [hidden email]
>>> >> https://mail.kde.org/mailman/listinfo/digikam-devel
>>> > _______________________________________________
>>> > Digikam-devel mailing list
>>> > [hidden email]
>>> > https://mail.kde.org/mailman/listinfo/digikam-devel
>>> _______________________________________________
>>> Digikam-devel mailing list
>>> [hidden email]
>>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>
>>
>>
>>
>> --
>> Veaceslav
>
>
>
>
> --
> Veaceslav
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Veaceslav Munteanu

Re: All kipi-plugins are gone ...

Yes.. i deleted entire build folder and rerun cmake...

On Sat, Mar 17, 2012 at 9:14 PM, Gilles Caulier <[hidden email]> wrote:

do you re-run cmake configure.

Problem is not reproducible here...

Gilles

2012/3/17 Veaceslav Munteanu <[hidden email]>:

> It seem that digikam can't see my shared libkipi when i install it from
> sources>
>
> [slavik@ArchAngel build]$ digikam
> digikam: error while loading shared libraries: libkipi.so.8: cannot open
> shared object file: No such file or directory
> [slavik@ArchAngel build]$ sudo pacman -S libkipi
> resolving dependencies...
> looking for inter-conflicts...
>
> Targets (1): libkipi-4.8.1-1
>
> Total Installed Size: 0.25 MiB
>
> Proceed with installation? [Y/n] y
> (1/1) checking package integrity
>
> error: failed to commit transaction (conflicting files)
> libkipi: /usr/include/libkipi/exportinterface.h exists in filesystem
> libkipi: /usr/include/libkipi/extension.h exists in filesystem
> libkipi: /usr/include/libkipi/imagecollection.h exists in filesystem
> libkipi: /usr/include/libkipi/imagecollectionselector.h exists in filesystem
> libkipi: /usr/include/libkipi/imagecollectionshared.h exists in filesystem
> libkipi: /usr/include/libkipi/imageinfo.h exists in filesystem
> libkipi: /usr/include/libkipi/imageinfoshared.h exists in filesystem
> libkipi: /usr/include/libkipi/interface.h exists in filesystem
> libkipi: /usr/include/libkipi/libkipi_export.h exists in filesystem
> libkipi: /usr/include/libkipi/plugin.h exists in filesystem
> libkipi: /usr/include/libkipi/pluginloader.h exists in filesystem
> libkipi: /usr/include/libkipi/uploadwidget.h exists in filesystem
> libkipi: /usr/include/libkipi/version.h exists in filesystem
> libkipi: /usr/lib/libkipi.so exists in filesystem
> libkipi: /usr/lib/pkgconfig/libkipi.pc exists in filesystem
> libkipi: /usr/share/apps/kipi/data/kipi-icon.svg exists in filesystem
> libkipi: /usr/share/apps/kipi/data/kipi-logo.svg exists in filesystem
> libkipi: /usr/share/apps/kipi/data/kipi-plugins_logo.png exists in
> filesystem
> libkipi: /usr/share/icons/hicolor/128x128/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/16x16/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/22x22/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/32x32/apps/kipi.png exists in filesystem
> libkipi: /usr/share/icons/hicolor/48x48/apps/kipi.png exists in filesystem
> libkipi: /usr/share/kde4/servicetypes/kipiplugin.desktop exists in
> filesystem
> Errors occurred, no packages were upgraded.
> [slavik@ArchAngel build]$
>
> Do i miss something?
>
> On Sat, Mar 17, 2012 at 8:31 PM, Veaceslav Munteanu <[hidden email]>
> wrote:
>>
>> compiled libkipi from sources, made a clean digikam build. No luck :(
>>
>>
>> On Sat, Mar 17, 2012 at 7:41 PM, Gilles Caulier <[hidden email]>
>> wrote:
>>>
>>> Make clean, and reinstall all including libkipi
>>>
>>> Gilles Caulier
>>>
>>> 2012/3/17 Pierre Hanser <[hidden email]>:
>>> > same thing here
>>> >
>>> > Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :
>>> >> Hello.
>>> >>
>>> >> I was working with my students on bugs when after a git pull and new
>>> >> build, all kipi-plugins are missing.
>>> >> We have the same problem on all 3 computers and it's a result of a
>>> >> recent commit, because i pulled this morning and everything was ok and
>>> >> after a hour it was broken.
>>> >>
>>> >> Can you help me?
>>> >>
>>> >> --
>>> >> Veaceslav
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> Digikam-devel mailing list
>>> >> [hidden email]
>>> >> https://mail.kde.org/mailman/listinfo/digikam-devel
>>> > _______________________________________________
>>> > Digikam-devel mailing list
>>> > [hidden email]
>>> > https://mail.kde.org/mailman/listinfo/digikam-devel
>>> _______________________________________________
>>> Digikam-devel mailing list
>>> [hidden email]
>>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>
>>
>>
>>
>> --
>> Veaceslav
>
>
>
>
> --
> Veaceslav
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

--
Veaceslav

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Pierre Hanser

Re: All kipi-plugins are gone ...

Le 17/03/2012 20:16, Veaceslav Munteanu a écrit :
> Yes.. i deleted entire build folder and rerun cmake...

same here, with cmake line

cmake -DCMAKE_INSTALL_PREFIX=/usr -DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS=1 ..

this install a new libkipi

but still no luck

> On Sat, Mar 17, 2012 at 9:14 PM, Gilles Caulier
> <[hidden email] <mailto:[hidden email]>> wrote:
>
> do you re-run cmake configure.
>
> Problem is not reproducible here...
>
> Gilles
>
> 2012/3/17 Veaceslav Munteanu <[hidden email]
> <mailto:[hidden email]>>:
> > It seem that digikam can't see my shared libkipi when i install it
> from
> > sources>
> >
> > [slavik@ArchAngel build]$ digikam
> > digikam: error while loading shared libraries: libkipi.so.8:
> cannot open
> > shared object file: No such file or directory
> > [slavik@ArchAngel build]$ sudo pacman -S libkipi
> > resolving dependencies...
> > looking for inter-conflicts...
> >
> > Targets (1): libkipi-4.8.1-1
> >
> > Total Installed Size: 0.25 MiB
> >
> > Proceed with installation? [Y/n] y
> > (1/1) checking package integrity
> >
> > error: failed to commit transaction (conflicting files)
> > libkipi: /usr/include/libkipi/exportinterface.h exists in filesystem
> > libkipi: /usr/include/libkipi/extension.h exists in filesystem
> > libkipi: /usr/include/libkipi/imagecollection.h exists in filesystem
> > libkipi: /usr/include/libkipi/imagecollectionselector.h exists in
> filesystem
> > libkipi: /usr/include/libkipi/imagecollectionshared.h exists in
> filesystem
> > libkipi: /usr/include/libkipi/imageinfo.h exists in filesystem
> > libkipi: /usr/include/libkipi/imageinfoshared.h exists in filesystem
> > libkipi: /usr/include/libkipi/interface.h exists in filesystem
> > libkipi: /usr/include/libkipi/libkipi_export.h exists in filesystem
> > libkipi: /usr/include/libkipi/plugin.h exists in filesystem
> > libkipi: /usr/include/libkipi/pluginloader.h exists in filesystem
> > libkipi: /usr/include/libkipi/uploadwidget.h exists in filesystem
> > libkipi: /usr/include/libkipi/version.h exists in filesystem
> > libkipi: /usr/lib/libkipi.so exists in filesystem
> > libkipi: /usr/lib/pkgconfig/libkipi.pc exists in filesystem
> > libkipi: /usr/share/apps/kipi/data/kipi-icon.svg exists in filesystem
> > libkipi: /usr/share/apps/kipi/data/kipi-logo.svg exists in filesystem
> > libkipi: /usr/share/apps/kipi/data/kipi-plugins_logo.png exists in
> > filesystem
> > libkipi: /usr/share/icons/hicolor/128x128/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/16x16/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/22x22/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/32x32/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/48x48/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/kde4/servicetypes/kipiplugin.desktop exists in
> > filesystem
> > Errors occurred, no packages were upgraded.
> > [slavik@ArchAngel build]$
> >
> > Do i miss something?
> >
> > On Sat, Mar 17, 2012 at 8:31 PM, Veaceslav Munteanu
> <[hidden email] <mailto:[hidden email]>>
> > wrote:
> >>
> >> compiled libkipi from sources, made a clean digikam build. No luck :(
> >>
> >>
> >> On Sat, Mar 17, 2012 at 7:41 PM, Gilles Caulier
> <[hidden email] <mailto:[hidden email]>>
> >> wrote:
> >>>
> >>> Make clean, and reinstall all including libkipi
> >>>
> >>> Gilles Caulier
> >>>
> >>> 2012/3/17 Pierre Hanser <[hidden email]
> <mailto:[hidden email]>>:
> >>> > same thing here
> >>> >
> >>> > Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :
> >>> >> Hello.
> >>> >>
> >>> >> I was working with my students on bugs when after a git pull
> and new
> >>> >> build, all kipi-plugins are missing.
> >>> >> We have the same problem on all 3 computers and it's a result
> of a
> >>> >> recent commit, because i pulled this morning and everything
> was ok and
> >>> >> after a hour it was broken.
> >>> >>
> >>> >> Can you help me?
> >>> >>
> >>> >> --
> >>> >> Veaceslav
> >>> >>
> >>> >>
> >>> >> _______________________________________________
> >>> >> Digikam-devel mailing list
> >>> >> [hidden email] <mailto:[hidden email]>
> >>> >> https://mail.kde.org/mailman/listinfo/digikam-devel
> >>> > _______________________________________________
> >>> > Digikam-devel mailing list
> >>> > [hidden email] <mailto:[hidden email]>
> >>> > https://mail.kde.org/mailman/listinfo/digikam-devel
> >>> _______________________________________________
> >>> Digikam-devel mailing list
> >>> [hidden email] <mailto:[hidden email]>
> >>> https://mail.kde.org/mailman/listinfo/digikam-devel
> >>
> >>
> >>
> >>
> >> --
> >> Veaceslav
> >
> >
> >
> >
> > --
> > Veaceslav
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email] <mailto:[hidden email]>
> > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> _______________________________________________
> Digikam-devel mailing list
> [hidden email] <mailto:[hidden email]>
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
>
>
> --
> Veaceslav
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Pierre Hanser

Re: All kipi-plugins are gone ...

In reply to this post by Veaceslav Munteanu

pb is with a git content from this afternoon

there are a few file new in git (plugin metadata,..)

let's try a new compilation...

Le 17/03/2012 20:16, Veaceslav Munteanu a écrit :

> Yes.. i deleted entire build folder and rerun cmake...
>
> On Sat, Mar 17, 2012 at 9:14 PM, Gilles Caulier
> <[hidden email] <mailto:[hidden email]>> wrote:
>
> do you re-run cmake configure.
>
> Problem is not reproducible here...
>
> Gilles
>
> 2012/3/17 Veaceslav Munteanu <[hidden email]
> <mailto:[hidden email]>>:
> > It seem that digikam can't see my shared libkipi when i install it
> from
> > sources>
> >
> > [slavik@ArchAngel build]$ digikam
> > digikam: error while loading shared libraries: libkipi.so.8:
> cannot open
> > shared object file: No such file or directory
> > [slavik@ArchAngel build]$ sudo pacman -S libkipi
> > resolving dependencies...
> > looking for inter-conflicts...
> >
> > Targets (1): libkipi-4.8.1-1
> >
> > Total Installed Size: 0.25 MiB
> >
> > Proceed with installation? [Y/n] y
> > (1/1) checking package integrity
> >
> > error: failed to commit transaction (conflicting files)
> > libkipi: /usr/include/libkipi/exportinterface.h exists in filesystem
> > libkipi: /usr/include/libkipi/extension.h exists in filesystem
> > libkipi: /usr/include/libkipi/imagecollection.h exists in filesystem
> > libkipi: /usr/include/libkipi/imagecollectionselector.h exists in
> filesystem
> > libkipi: /usr/include/libkipi/imagecollectionshared.h exists in
> filesystem
> > libkipi: /usr/include/libkipi/imageinfo.h exists in filesystem
> > libkipi: /usr/include/libkipi/imageinfoshared.h exists in filesystem
> > libkipi: /usr/include/libkipi/interface.h exists in filesystem
> > libkipi: /usr/include/libkipi/libkipi_export.h exists in filesystem
> > libkipi: /usr/include/libkipi/plugin.h exists in filesystem
> > libkipi: /usr/include/libkipi/pluginloader.h exists in filesystem
> > libkipi: /usr/include/libkipi/uploadwidget.h exists in filesystem
> > libkipi: /usr/include/libkipi/version.h exists in filesystem
> > libkipi: /usr/lib/libkipi.so exists in filesystem
> > libkipi: /usr/lib/pkgconfig/libkipi.pc exists in filesystem
> > libkipi: /usr/share/apps/kipi/data/kipi-icon.svg exists in filesystem
> > libkipi: /usr/share/apps/kipi/data/kipi-logo.svg exists in filesystem
> > libkipi: /usr/share/apps/kipi/data/kipi-plugins_logo.png exists in
> > filesystem
> > libkipi: /usr/share/icons/hicolor/128x128/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/16x16/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/22x22/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/32x32/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/icons/hicolor/48x48/apps/kipi.png exists in
> filesystem
> > libkipi: /usr/share/kde4/servicetypes/kipiplugin.desktop exists in
> > filesystem
> > Errors occurred, no packages were upgraded.
> > [slavik@ArchAngel build]$
> >
> > Do i miss something?
> >
> > On Sat, Mar 17, 2012 at 8:31 PM, Veaceslav Munteanu
> <[hidden email] <mailto:[hidden email]>>
> > wrote:
> >>
> >> compiled libkipi from sources, made a clean digikam build. No luck :(
> >>
> >>
> >> On Sat, Mar 17, 2012 at 7:41 PM, Gilles Caulier
> <[hidden email] <mailto:[hidden email]>>
> >> wrote:
> >>>
> >>> Make clean, and reinstall all including libkipi
> >>>
> >>> Gilles Caulier
> >>>
> >>> 2012/3/17 Pierre Hanser <[hidden email]
> <mailto:[hidden email]>>:
> >>> > same thing here
> >>> >
> >>> > Le 17/03/2012 18:18, Veaceslav Munteanu a écrit :
> >>> >> Hello.
> >>> >>
> >>> >> I was working with my students on bugs when after a git pull
> and new
> >>> >> build, all kipi-plugins are missing.
> >>> >> We have the same problem on all 3 computers and it's a result
> of a
> >>> >> recent commit, because i pulled this morning and everything
> was ok and
> >>> >> after a hour it was broken.
> >>> >>
> >>> >> Can you help me?
> >>> >>
> >>> >> --
> >>> >> Veaceslav
> >>> >>
> >>> >>
> >>> >> _______________________________________________
> >>> >> Digikam-devel mailing list
> >>> >> [hidden email] <mailto:[hidden email]>
> >>> >> https://mail.kde.org/mailman/listinfo/digikam-devel
> >>> > _______________________________________________
> >>> > Digikam-devel mailing list
> >>> > [hidden email] <mailto:[hidden email]>
> >>> > https://mail.kde.org/mailman/listinfo/digikam-devel
> >>> _______________________________________________
> >>> Digikam-devel mailing list
> >>> [hidden email] <mailto:[hidden email]>
> >>> https://mail.kde.org/mailman/listinfo/digikam-devel
> >>
> >>
> >>
> >>
> >> --
> >> Veaceslav
> >
> >
> >
> >
> > --
> > Veaceslav
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email] <mailto:[hidden email]>
> > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> _______________________________________________
> Digikam-devel mailing list
> [hidden email] <mailto:[hidden email]>
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
>
>
> --
> Veaceslav
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Matthias Welwarsky-2

Re: All kipi-plugins are gone ...

In reply to this post by Veaceslav Munteanu

Same here, current git master, completely uninstalled, deleted the build
directory and re-made everything. no kipi-plugins whatsoever.

I'm guessing: Some symbol vanished and dlopen fails when the plugin is loaded?

regards,
matthias

On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
> Hello.
>
> I was working with my students on bugs when after a git pull and new build,
> all kipi-plugins are missing.
> We have the same problem on all 3 computers and it's a result of a recent
> commit, because i pulled this morning and everything was ok and after a
> hour it was broken.
>
> Can you help me?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Matthias Welwarsky-2

Re: All kipi-plugins are gone ...

On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:
> Same here, current git master, completely uninstalled, deleted the build
> directory and re-made everything. no kipi-plugins whatsoever.
>
> I'm guessing: Some symbol vanished and dlopen fails when the plugin is
> loaded?
>

Or even simpler, KipiPluginLoader::loadPlugins() isn't called any more? At
least static call analysis in Eclipse does not show a place where it is
called. There were a lot of modifications in that area recently ...

> regards,
> matthias
>
> On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
> > Hello.
> >
> > I was working with my students on bugs when after a git pull and new
> > build, all kipi-plugins are missing.
> > We have the same problem on all 3 computers and it's a result of a
> > recent
> > commit, because i pulled this morning and everything was ok and after a
> > hour it was broken.
> >
> > Can you help me?
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Pierre Hanser

Re: All kipi-plugins are gone ...

in any case, digikam loading is much faster without any plugins ;)

Le 17/03/2012 21:54, Matthias Welwarsky a écrit :

> On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:
>> Same here, current git master, completely uninstalled, deleted the build
>> directory and re-made everything. no kipi-plugins whatsoever.
>>
>> I'm guessing: Some symbol vanished and dlopen fails when the plugin is
>> loaded?
>>
>
> Or even simpler, KipiPluginLoader::loadPlugins() isn't called any more? At
> least static call analysis in Eclipse does not show a place where it is
> called. There were a lot of modifications in that area recently ...
>
>
>> regards,
>> matthias
>>
>> On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
>>> Hello.
>>>
>>> I was working with my students on bugs when after a git pull and new
>>> build, all kipi-plugins are missing.
>>> We have the same problem on all 3 computers and it's a result of a
>>> recent
>>> commit, because i pulled this morning and everything was ok and after a
>>> hour it was broken.
>>>
>>> Can you help me?
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Matthias Welwarsky-2

Re: All kipi-plugins are gone ...

In reply to this post by Matthias Welwarsky-2

OK, pretty simple:

It's the patches merged by Ananta Palani, in particular this one:

commit 8453c8f2def5e917d731aa636eced77e79d4a4a2
Author: Supreet Pal Singh <[hidden email]>
Date: Sat Mar 17 01:32:07 2012 +0530

Removed the code from setup

It removes the loadPlugins() call from the Constructor of KipiPluginLoader
class

Ananta, can you _please_ check what you are pushing into master? And please,
do not do merge commits. It's very annoying and difficult to eliminate single
patches out of a merge, or even to remove the merge patch entirely.

See man git-merge:

-m parent-number, --mainline parent-number
Usually you cannot revert a merge because you do not know which
side of the merge should be considered the
mainline. This option specifies the parent number (starting from 1)
of the mainline and allows revert to reverse
the change relative to the specified parent.

Reverting a merge commit declares that you will never want the tree
changes brought in by the merge. As a result,
later merges will only bring in tree changes introduced by commits
that are not ancestors of the previously
reverted merge. This may or may not be what you want.

See the revert-a-faulty-merge How-To[1] for more details.

This is the How-To mentioned, and if your head is spinning after reading it,
you know why merge commits should not happen if you just want to push changes
into the master branch:

http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-
faulty-merge.txt

In my opinion, there is almost never a need for merge commits. Even after you
merged from some other branch, you should still rebase onto the head of the
remote master branch before you commit.

On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:

> Same here, current git master, completely uninstalled, deleted the build
> directory and re-made everything. no kipi-plugins whatsoever.
>
> I'm guessing: Some symbol vanished and dlopen fails when the plugin is
> loaded?
>
> regards,
> matthias
>
> On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
> > Hello.
> >
> > I was working with my students on bugs when after a git pull and new
> > build, all kipi-plugins are missing.
> > We have the same problem on all 3 computers and it's a result of a
> > recent
> > commit, because i pulled this morning and everything was ok and after a
> > hour it was broken.
> >
> > Can you help me?
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Veaceslav Munteanu

Re: All kipi-plugins are gone ...

Ok.. can someone fix this? :)

Removed the code from setup

It removes the loadPlugins() call from the Constructor of KipiPluginLoader
class

Ananta, can you _please_ check what you are pushing into master? And please,
do not do merge commits. It's very annoying and difficult to eliminate single
patches out of a merge, or even to remove the merge patch entirely.

See man git-merge:

-m parent-number, --mainline parent-number
Usually you cannot revert a merge because you do not know which
side of the merge should be considered the
mainline. This option specifies the parent number (starting from 1)
of the mainline and allows revert to reverse
the change relative to the specified parent.

Reverting a merge commit declares that you will never want the tree
changes brought in by the merge. As a result,
later merges will only bring in tree changes introduced by commits
that are not ancestors of the previously
reverted merge. This may or may not be what you want.

See the revert-a-faulty-merge How-To[1] for more details.

This is the How-To mentioned, and if your head is spinning after reading it,
you know why merge commits should not happen if you just want to push changes
into the master branch:

<a href="http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a- faulty-merge.txt" target="_blank">http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-
faulty-merge.txt

In my opinion, there is almost never a need for merge commits. Even after you
merged from some other branch, you should still rebase onto the head of the
remote master branch before you commit.

On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:

> Same here, current git master, completely uninstalled, deleted the build
> directory and re-made everything. no kipi-plugins whatsoever.
>
> I'm guessing: Some symbol vanished and dlopen fails when the plugin is
> loaded?
>
> regards,
> matthias
>
> On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
> > Hello.
> >
> > I was working with my students on bugs when after a git pull and new
> > build, all kipi-plugins are missing.
> > We have the same problem on all 3 computers and it's a result of a
> > recent
> > commit, because i pulled this morning and everything was ok and after a
> > hour it was broken.
> >
> > Can you help me?
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

--
Veaceslav

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Gilles Caulier-4

Re: All kipi-plugins are gone ...

done

Gilles

2012/3/17 Veaceslav Munteanu <[hidden email]>:

>> Ok.. can someone fix this? :)
>>
>>
>> Removed the code from setup
>>
>>
>> It removes the loadPlugins() call from the Constructor of KipiPluginLoader
>> class
>>
>> Ananta, can you _please_ check what you are pushing into master? And
>> please,
>> do not do merge commits. It's very annoying and difficult to eliminate
>> single
>> patches out of a merge, or even to remove the merge patch entirely.
>>
>> See man git-merge:
>>
>> -m parent-number, --mainline parent-number
>> Usually you cannot revert a merge because you do not know which
>> side of the merge should be considered the
>> mainline. This option specifies the parent number (starting from
>> 1)
>> of the mainline and allows revert to reverse
>> the change relative to the specified parent.
>>
>> Reverting a merge commit declares that you will never want the
>> tree
>> changes brought in by the merge. As a result,
>> later merges will only bring in tree changes introduced by
>> commits
>> that are not ancestors of the previously
>> reverted merge. This may or may not be what you want.
>>
>> See the revert-a-faulty-merge How-To[1] for more details.
>>
>> This is the How-To mentioned, and if your head is spinning after reading
>> it,
>> you know why merge commits should not happen if you just want to push
>> changes
>> into the master branch:
>>
>>
>> http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-
>> faulty-merge.txt
>>
>> In my opinion, there is almost never a need for merge commits. Even after
>> you
>> merged from some other branch, you should still rebase onto the head of
>> the
>> remote master branch before you commit.
>>
>> On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:
>> > Same here, current git master, completely uninstalled, deleted the build
>> > directory and re-made everything. no kipi-plugins whatsoever.
>> >
>> > I'm guessing: Some symbol vanished and dlopen fails when the plugin is
>> > loaded?
>> >
>> > regards,
>> > matthias
>> >
>> > On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
>> > > Hello.
>> > >
>> > > I was working with my students on bugs when after a git pull and new
>> > > build, all kipi-plugins are missing.
>> > > We have the same problem on all 3 computers and it's a result of a
>> > > recent
>> > > commit, because i pulled this morning and everything was ok and after
>> > > a
>> > > hour it was broken.
>> > >
>> > > Can you help me?
>> >
>> > _______________________________________________
>> > Digikam-devel mailing list
>> > [hidden email]
>> > https://mail.kde.org/mailman/listinfo/digikam-devel
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
>
>
> --
> Veaceslav
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Ananta Palani

Re: All kipi-plugins are gone ...

In reply to this post by Matthias Welwarsky-2

Matthias,

I check my own code, which is what I pushed into master. How am I supposed to know that code pushed ahead of my commit is faulty? Seems like it is the responsibility of the other developers, in this case Supreet. Also, I see that other developers also merge with master in a similar fashion (4 separate developers this month!). How else is this supposed to be done?

Here's how this situation arose. I commit to master. I try to push my changes, oops, there are changes ahead of mine. So I pull, merge, push. Even if I were to pull before I commit, there is a chance someone else will push in between my last pull, and my commit and push attempt.

On Sat, Mar 17, 2012 at 9:16 PM, Matthias Welwarsky <[hidden email]> wrote:

OK, pretty simple:

It's the patches merged by Ananta Palani, in particular this one:

commit 8453c8f2def5e917d731aa636eced77e79d4a4a2
Author: Supreet Pal Singh <[hidden email]>
Date: Sat Mar 17 01:32:07 2012 +0530

Removed the code from setup

It removes the loadPlugins() call from the Constructor of KipiPluginLoader
class

Ananta, can you _please_ check what you are pushing into master? And please,
do not do merge commits. It's very annoying and difficult to eliminate single
patches out of a merge, or even to remove the merge patch entirely.

See man git-merge:

-m parent-number, --mainline parent-number
Usually you cannot revert a merge because you do not know which
side of the merge should be considered the
mainline. This option specifies the parent number (starting from 1)
of the mainline and allows revert to reverse
the change relative to the specified parent.

Reverting a merge commit declares that you will never want the tree
changes brought in by the merge. As a result,
later merges will only bring in tree changes introduced by commits
that are not ancestors of the previously
reverted merge. This may or may not be what you want.

See the revert-a-faulty-merge How-To[1] for more details.

This is the How-To mentioned, and if your head is spinning after reading it,
you know why merge commits should not happen if you just want to push changes
into the master branch:

http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-
faulty-merge.txt

In my opinion, there is almost never a need for merge commits. Even after you
merged from some other branch, you should still rebase onto the head of the
remote master branch before you commit.

On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:

> Same here, current git master, completely uninstalled, deleted the build
> directory and re-made everything. no kipi-plugins whatsoever.
>
> I'm guessing: Some symbol vanished and dlopen fails when the plugin is
> loaded?
>
> regards,
> matthias
>
> On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
> > Hello.
> >
> > I was working with my students on bugs when after a git pull and new
> > build, all kipi-plugins are missing.
> > We have the same problem on all 3 computers and it's a result of a
> > recent
> > commit, because i pulled this morning and everything was ok and after a
> > hour it was broken.
> >
> > Can you help me?
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Matthias Welwarsky-2

Re: All kipi-plugins are gone ...

On Saturday 17 March 2012 23:47:21 Ananta Palani wrote:
> Matthias,
>
> I check my own code, which is what I pushed into master. How am I supposed
> to know that code pushed ahead of my commit is faulty? Seems like it is the
> responsibility of the other developers, in this case Supreet. Also, I see
> that other developers also merge with master in a similar fashion (4
> separate developers this month!). How else is this supposed to be done?

Ah yes. I apologize, I misunderstood how the merge went. You were committing
on master, and the branch display in gitk makes it look like the faulty commit
was in a branch you merged with master. Hence I assumed you were working on a
separate branch together with Supreet and merged his code with your commit.
That assumption was wrong. I'm sorry.

> Here's how this situation arose. I commit to master. I try to push my
> changes, oops, there are changes ahead of mine. So I pull, merge, push.
> Even if I were to pull before I commit, there is a chance someone else will
> push in between my last pull, and my commit and push attempt.

I wrote a pretty lengthy description about that not too long ago.
The abridged version is:
- Always use "git pull --rebase" to update from master
- Use "git rebase origin/master" to eliminate accidental merge commits.

Gilles, this also applies to your commits.

There is almost never a need to do anything else. Merges are really not
required, unless you have worked on a separate topic outside of master and
absolutely want to preserve the commit history of the topic branch after the
merge.

regards,
matthias

>
> On Sat, Mar 17, 2012 at 9:16 PM, Matthias Welwarsky
>
> <[hidden email]>wrote:
> > OK, pretty simple:
> >
> > It's the patches merged by Ananta Palani, in particular this one:
> >
> > commit 8453c8f2def5e917d731aa636eced77e79d4a4a2
> > Author: Supreet Pal Singh <[hidden email]>
> > Date: Sat Mar 17 01:32:07 2012 +0530
> >
> > Removed the code from setup
> >
> > It removes the loadPlugins() call from the Constructor of
> > KipiPluginLoader class
> >
> > Ananta, can you _please_ check what you are pushing into master? And
> > please,
> > do not do merge commits. It's very annoying and difficult to eliminate
> > single
> > patches out of a merge, or even to remove the merge patch entirely.
> >
> > See man git-merge:
> > -m parent-number, --mainline parent-number
> >
> > Usually you cannot revert a merge because you do not
> > know which
> >
> > side of the merge should be considered the
> >
> > mainline. This option specifies the parent number
> > (starting from>
> > 1)
> > of the mainline and allows revert to reverse
> >
> > the change relative to the specified parent.
> >
> > Reverting a merge commit declares that you will
> > never want the
> >
> > tree
> > changes brought in by the merge. As a result,
> >
> > later merges will only bring in tree changes
> > introduced by
> >
> > commits
> > that are not ancestors of the previously
> >
> > reverted merge. This may or may not be what you
> > want.
> >
> > See the revert-a-faulty-merge How-To[1] for more
> > details.
> >
> > This is the How-To mentioned, and if your head is spinning after reading
> > it,
> > you know why merge commits should not happen if you just want to push
> > changes
> > into the master branch:
> >
> >
> > http://code.google.com/p/git-core/source/browse/Documentation/howto/reve
> > rt-a- faulty-merge.txt
> >
> > In my opinion, there is almost never a need for merge commits. Even
> > after
> > you
> > merged from some other branch, you should still rebase onto the head of
> > the remote master branch before you commit.
> >
> > On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:
> > > Same here, current git master, completely uninstalled, deleted the
> > > build directory and re-made everything. no kipi-plugins whatsoever.
> > >
> > > I'm guessing: Some symbol vanished and dlopen fails when the plugin
> > > is
> > > loaded?
> > >
> > > regards,
> > > matthias
> > >
> > > On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
> > > > Hello.
> > > >
> > > > I was working with my students on bugs when after a git pull and
> > > > new
> > > > build, all kipi-plugins are missing.
> > > > We have the same problem on all 3 computers and it's a result of
> > > > a
> > > > recent
> > > > commit, because i pulled this morning and everything was ok and
> > > > after a hour it was broken.
> > > >
> > > > Can you help me?
> > >
> > > _______________________________________________
> > > Digikam-devel mailing list
> > > [hidden email]
> > > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Veaceslav Munteanu

Re: All kipi-plugins are gone ...

In reply to this post by Gilles Caulier-4

Sorry, but problem isn't fixed for me... still have no kipi-plugins..

On Sun, Mar 18, 2012 at 12:32 AM, Gilles Caulier <[hidden email]> wrote:

done

Gilles

2012/3/17 Veaceslav Munteanu <[hidden email]>:

>> Ok.. can someone fix this? :)
>>
>>
>> Removed the code from setup
>>
>>
>> It removes the loadPlugins() call from the Constructor of KipiPluginLoader
>> class
>>
>> Ananta, can you _please_ check what you are pushing into master? And
>> please,
>> do not do merge commits. It's very annoying and difficult to eliminate
>> single
>> patches out of a merge, or even to remove the merge patch entirely.
>>
>> See man git-merge:
>>
>> -m parent-number, --mainline parent-number
>> Usually you cannot revert a merge because you do not know which
>> side of the merge should be considered the
>> mainline. This option specifies the parent number (starting from
>> 1)
>> of the mainline and allows revert to reverse
>> the change relative to the specified parent.
>>
>> Reverting a merge commit declares that you will never want the
>> tree
>> changes brought in by the merge. As a result,
>> later merges will only bring in tree changes introduced by
>> commits
>> that are not ancestors of the previously
>> reverted merge. This may or may not be what you want.
>>
>> See the revert-a-faulty-merge How-To[1] for more details.
>>
>> This is the How-To mentioned, and if your head is spinning after reading
>> it,
>> you know why merge commits should not happen if you just want to push
>> changes
>> into the master branch:
>>
>>
>> http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-
>> faulty-merge.txt
>>
>> In my opinion, there is almost never a need for merge commits. Even after
>> you
>> merged from some other branch, you should still rebase onto the head of
>> the
>> remote master branch before you commit.
>>
>> On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:
>> > Same here, current git master, completely uninstalled, deleted the build
>> > directory and re-made everything. no kipi-plugins whatsoever.
>> >
>> > I'm guessing: Some symbol vanished and dlopen fails when the plugin is
>> > loaded?
>> >
>> > regards,
>> > matthias
>> >
>> > On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
>> > > Hello.
>> > >
>> > > I was working with my students on bugs when after a git pull and new
>> > > build, all kipi-plugins are missing.
>> > > We have the same problem on all 3 computers and it's a result of a
>> > > recent
>> > > commit, because i pulled this morning and everything was ok and after
>> > > a
>> > > hour it was broken.
>> > >
>> > > Can you help me?
>> >
>> > _______________________________________________
>> > Digikam-devel mailing list
>> > [hidden email]
>> > https://mail.kde.org/mailman/listinfo/digikam-devel
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
>
>
> --
> Veaceslav
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

--
Veaceslav

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Pierre Hanser

Re: All kipi-plugins are gone ...

solved here

Le 18/03/2012 09:50, Veaceslav Munteanu a écrit :

> Sorry, but problem isn't fixed for me... still have no kipi-plugins..
>
> On Sun, Mar 18, 2012 at 12:32 AM, Gilles Caulier
> <[hidden email] <mailto:[hidden email]>> wrote:
>
> done
>
> Gilles
>
> 2012/3/17 Veaceslav Munteanu <[hidden email]
> <mailto:[hidden email]>>:
> >> Ok.. can someone fix this? :)
> >>
> >>
> >> Removed the code from setup
> >>
> >>
> >> It removes the loadPlugins() call from the Constructor of
> KipiPluginLoader
> >> class
> >>
> >> Ananta, can you _please_ check what you are pushing into master? And
> >> please,
> >> do not do merge commits. It's very annoying and difficult to
> eliminate
> >> single
> >> patches out of a merge, or even to remove the merge patch entirely.
> >>
> >> See man git-merge:
> >>
> >> -m parent-number, --mainline parent-number
> >> Usually you cannot revert a merge because you do not
> know which
> >> side of the merge should be considered the
> >> mainline. This option specifies the parent number
> (starting from
> >> 1)
> >> of the mainline and allows revert to reverse
> >> the change relative to the specified parent.
> >>
> >> Reverting a merge commit declares that you will never
> want the
> >> tree
> >> changes brought in by the merge. As a result,
> >> later merges will only bring in tree changes introduced by
> >> commits
> >> that are not ancestors of the previously
> >> reverted merge. This may or may not be what you want.
> >>
> >> See the revert-a-faulty-merge How-To[1] for more details.
> >>
> >> This is the How-To mentioned, and if your head is spinning after
> reading
> >> it,
> >> you know why merge commits should not happen if you just want to push
> >> changes
> >> into the master branch:
> >>
> >>
> >>
> http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-
> >> faulty-merge.txt
> >>
> >> In my opinion, there is almost never a need for merge commits.
> Even after
> >> you
> >> merged from some other branch, you should still rebase onto the
> head of
> >> the
> >> remote master branch before you commit.
> >>
> >> On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:
> >> > Same here, current git master, completely uninstalled, deleted
> the build
> >> > directory and re-made everything. no kipi-plugins whatsoever.
> >> >
> >> > I'm guessing: Some symbol vanished and dlopen fails when the
> plugin is
> >> > loaded?
> >> >
> >> > regards,
> >> > matthias
> >> >
> >> > On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
> >> > > Hello.
> >> > >
> >> > > I was working with my students on bugs when after a git pull
> and new
> >> > > build, all kipi-plugins are missing.
> >> > > We have the same problem on all 3 computers and it's a result
> of a
> >> > > recent
> >> > > commit, because i pulled this morning and everything was ok
> and after
> >> > > a
> >> > > hour it was broken.
> >> > >
> >> > > Can you help me?
> >> >
> >> > _______________________________________________
> >> > Digikam-devel mailing list
> >> > [hidden email] <mailto:[hidden email]>
> >> > https://mail.kde.org/mailman/listinfo/digikam-devel
> >> _______________________________________________
> >> Digikam-devel mailing list
> >> [hidden email] <mailto:[hidden email]>
> >> https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> >
> >
> >
> > --
> > Veaceslav
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > [hidden email] <mailto:[hidden email]>
> > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> _______________________________________________
> Digikam-devel mailing list
> [hidden email] <mailto:[hidden email]>
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
>
>
> --
> Veaceslav
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Gilles Caulier-4

Re: All kipi-plugins are gone ...

In reply to this post by Ananta Palani

Yes, it's not Ananta fault about pluginloader. Supreet has forget to
restore the call to load plugin in constructor... (:=)))...

Gilles

2012/3/18 Ananta Palani <[hidden email]>:

> Matthias,
>
> I check my own code, which is what I pushed into master. How am I supposed
> to know that code pushed ahead of my commit is faulty? Seems like it is the
> responsibility of the other developers, in this case Supreet. Also, I see
> that other developers also merge with master in a similar fashion (4
> separate developers this month!). How else is this supposed to be done?
>
> Here's how this situation arose. I commit to master. I try to push my
> changes, oops, there are changes ahead of mine. So I pull, merge, push. Even
> if I were to pull before I commit, there is a chance someone else will push
> in between my last pull, and my commit and push attempt.
>
>
> On Sat, Mar 17, 2012 at 9:16 PM, Matthias Welwarsky <[hidden email]>
> wrote:
>>
>> OK, pretty simple:
>>
>> It's the patches merged by Ananta Palani, in particular this one:
>>
>> commit 8453c8f2def5e917d731aa636eced77e79d4a4a2
>> Author: Supreet Pal Singh <[hidden email]>
>> Date: Sat Mar 17 01:32:07 2012 +0530
>>
>> Removed the code from setup
>>
>>
>> It removes the loadPlugins() call from the Constructor of KipiPluginLoader
>> class
>>
>> Ananta, can you _please_ check what you are pushing into master? And
>> please,
>> do not do merge commits. It's very annoying and difficult to eliminate
>> single
>> patches out of a merge, or even to remove the merge patch entirely.
>>
>> See man git-merge:
>>
>> -m parent-number, --mainline parent-number
>> Usually you cannot revert a merge because you do not know which
>> side of the merge should be considered the
>> mainline. This option specifies the parent number (starting from
>> 1)
>> of the mainline and allows revert to reverse
>> the change relative to the specified parent.
>>
>> Reverting a merge commit declares that you will never want the
>> tree
>> changes brought in by the merge. As a result,
>> later merges will only bring in tree changes introduced by
>> commits
>> that are not ancestors of the previously
>> reverted merge. This may or may not be what you want.
>>
>> See the revert-a-faulty-merge How-To[1] for more details.
>>
>> This is the How-To mentioned, and if your head is spinning after reading
>> it,
>> you know why merge commits should not happen if you just want to push
>> changes
>> into the master branch:
>>
>>
>> http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-
>> faulty-merge.txt
>>
>> In my opinion, there is almost never a need for merge commits. Even after
>> you
>> merged from some other branch, you should still rebase onto the head of
>> the
>> remote master branch before you commit.
>>
>> On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:
>> > Same here, current git master, completely uninstalled, deleted the build
>> > directory and re-made everything. no kipi-plugins whatsoever.
>> >
>> > I'm guessing: Some symbol vanished and dlopen fails when the plugin is
>> > loaded?
>> >
>> > regards,
>> > matthias
>> >
>> > On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:
>> > > Hello.
>> > >
>> > > I was working with my students on bugs when after a git pull and new
>> > > build, all kipi-plugins are missing.
>> > > We have the same problem on all 3 computers and it's a result of a
>> > > recent
>> > > commit, because i pulled this morning and everything was ok and after
>> > > a
>> > > hour it was broken.
>> > >
>> > > Can you help me?
>> >
>> > _______________________________________________
>> > Digikam-devel mailing list
>> > [hidden email]
>> > https://mail.kde.org/mailman/listinfo/digikam-devel
>> _______________________________________________
>> Digikam-devel mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel