All kipi-plugins are gone ...

[Veaceslav Munteanu]

well.. when i try to install libkipi from sorces shiped with digikam, it installs libkipi.so.9 and libkipi..so.9.1.0

but when starting digikam it requires:

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

and i need to install libkipi from my distro's repo, to obtain libkipi.so.8, but i still have no kipi-plugins...

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

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

--
Veaceslav

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

[Pierre Hanser]

strange

here if i use ldd on digikam it lists

> ldd /usr/bin/digikam |grep libkipi
        libkipi.so.9 => /usr/lib/libkipi.so.9 (0xb6e81000)

that does not prevent me to have many likipi installes

> ls -l  /usr/lib/libkipi.so*
lrwxrwxrwx 1     12 2012-01-29 18:31 /usr/lib/libkipi.so -> libkipi.so.9
lrwxrwxrwx 1     16 2012-01-24 07:32 /usr/lib/libkipi.so.8 ->
libkipi.so.8.0.2
-rw-r--r-- 1    87872 2012-01-14 00:51 /usr/lib/libkipi.so.8.0.0
-rw-r--r-- 1  1901321 2012-01-01 15:08 /usr/lib/libkipi.so.8.0.1
-rw-r--r-- 1  1901321 2012-01-25 18:23 /usr/lib/libkipi.so.8.0.2
lrwxrwxrwx 1     16 2012-03-09 21:15 /usr/lib/libkipi.so.9 ->
libkipi.so.9.1.0
-rw-r--r-- 1  1448879 2012-02-29 18:09 /usr/lib/libkipi.so.9.0.0
-rw-r--r-- 1  1448883 2012-03-17 21:00 /usr/lib/libkipi.so.9.1.0

some that i could remove, but clearly .8 and .9 installed in parallel


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

> well.. when i try to install libkipi from sorces shiped with digikam, it
> installs libkipi.so.9 and libkipi..so.9.1.0
>
> but when starting digikam it requires:
>
> digikam: error while loading shared libraries: libkipi.so.8: cannot open
> shared object file: No such file or directory
>
> and i need to install libkipi from my distro's repo, to obtain
> libkipi.so.8, but i still have no kipi-plugins...
>
> On Sun, Mar 18, 2012 at 11:50 AM, Gilles Caulier
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     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]
>     <mailto:[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] <mailto:[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]
>     <mailto:[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] <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
>     >
>     _______________________________________________
>     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