well.. when i try to install libkipi from sorces shiped with digikam, it installs libkipi.so.9 and libkipi..so.9.1.0<div><br></div><div>but when starting digikam it requires:</div><div><br></div><div><div>digikam: error while loading shared libraries: libkipi.so.8: cannot open shared object file: No such file or directory</div>
<div><br></div><div>and i need to install libkipi from my distro's repo, to obtain libkipi.so.8, but i still have no kipi-plugins...</div><br><div class="gmail_quote">On Sun, Mar 18, 2012 at 11:50 AM, Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes, it's not Ananta fault about pluginloader. Supreet has forget to<br>
restore the call to load plugin in constructor... (:=)))...<br>
<br>
Gilles<br>
<br>
2012/3/18 Ananta Palani <<a href="mailto:anantapalani@gmail.com">anantapalani@gmail.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> Matthias,<br>
><br>
> I check my own code, which is what I pushed into master. How am I supposed<br>
> to know that code pushed ahead of my commit is faulty? Seems like it is the<br>
> responsibility of the other developers, in this case Supreet. Also, I see<br>
> that other developers also merge with master in a similar fashion (4<br>
> separate developers this month!). How else is this supposed to be done?<br>
><br>
> Here's how this situation arose. I commit to master. I try to push my<br>
> changes, oops, there are changes ahead of mine. So I pull, merge, push. Even<br>
> if I were to pull before I commit, there is a chance someone else will push<br>
> in between my last pull, and my commit and push attempt.<br>
><br>
><br>
> On Sat, Mar 17, 2012 at 9:16 PM, Matthias Welwarsky <<a href="mailto:matthias@welwarsky.de">matthias@welwarsky.de</a>><br>
> wrote:<br>
>><br>
>> OK, pretty simple:<br>
>><br>
>> It's the patches merged by Ananta Palani, in particular this one:<br>
>><br>
>> commit 8453c8f2def5e917d731aa636eced77e79d4a4a2<br>
>> Author: Supreet Pal Singh <<a href="mailto:supreetpal@gmail.com">supreetpal@gmail.com</a>><br>
>> Date: Sat Mar 17 01:32:07 2012 +0530<br>
>><br>
>> Removed the code from setup<br>
>><br>
>><br>
>> It removes the loadPlugins() call from the Constructor of KipiPluginLoader<br>
>> class<br>
>><br>
>> Ananta, can you _please_ check what you are pushing into master? And<br>
>> please,<br>
>> do not do merge commits. It's very annoying and difficult to eliminate<br>
>> single<br>
>> patches out of a merge, or even to remove the merge patch entirely.<br>
>><br>
>> See man git-merge:<br>
>><br>
>> -m parent-number, --mainline parent-number<br>
>> Usually you cannot revert a merge because you do not know which<br>
>> side of the merge should be considered the<br>
>> mainline. This option specifies the parent number (starting from<br>
>> 1)<br>
>> of the mainline and allows revert to reverse<br>
>> the change relative to the specified parent.<br>
>><br>
>> Reverting a merge commit declares that you will never want the<br>
>> tree<br>
>> changes brought in by the merge. As a result,<br>
>> later merges will only bring in tree changes introduced by<br>
>> commits<br>
>> that are not ancestors of the previously<br>
>> reverted merge. This may or may not be what you want.<br>
>><br>
>> See the revert-a-faulty-merge How-To[1] for more details.<br>
>><br>
>> This is the How-To mentioned, and if your head is spinning after reading<br>
>> it,<br>
>> you know why merge commits should not happen if you just want to push<br>
>> changes<br>
>> into the master branch:<br>
>><br>
>><br>
>> <a href="http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-" target="_blank">http://code.google.com/p/git-core/source/browse/Documentation/howto/revert-a-</a><br>
>> faulty-merge.txt<br>
>><br>
>> In my opinion, there is almost never a need for merge commits. Even after<br>
>> you<br>
>> merged from some other branch, you should still rebase onto the head of<br>
>> the<br>
>> remote master branch before you commit.<br>
>><br>
>> On Saturday 17 March 2012 21:31:38 Matthias Welwarsky wrote:<br>
>> > Same here, current git master, completely uninstalled, deleted the build<br>
>> > directory and re-made everything. no kipi-plugins whatsoever.<br>
>> ><br>
>> > I'm guessing: Some symbol vanished and dlopen fails when the plugin is<br>
>> > loaded?<br>
>> ><br>
>> > regards,<br>
>> > matthias<br>
>> ><br>
>> > On Saturday 17 March 2012 19:18:03 Veaceslav Munteanu wrote:<br>
>> > > Hello.<br>
>> > ><br>
>> > > I was working with my students on bugs when after a git pull and new<br>
>> > > build, all kipi-plugins are missing.<br>
>> > > We have the same problem on all 3 computers and it's a result of a<br>
>> > > recent<br>
>> > > commit, because i pulled this morning and everything was ok and after<br>
>> > > a<br>
>> > > hour it was broken.<br>
>> > ><br>
>> > > Can you help me?<br>
>> ><br>
>> > _______________________________________________<br>
>> > Digikam-devel mailing list<br>
>> > <a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br>
>> > <a href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
>> _______________________________________________<br>
>> Digikam-devel mailing list<br>
>> <a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Digikam-devel mailing list<br>
> <a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
><br>
_______________________________________________<br>
Digikam-devel mailing list<br>
<a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-devel" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Veaceslav<br>
</div>