[opensuse-packaging] Need help by Fixing Bugreports
Hello Mates, i've getted an Bugreport for my kde4-skrooge Package. But sadly i'm on the End of my Knowledge. Has anyone an Idea? The Report is: https://bugzilla.novell.com/show_bug.cgi?id=502553 -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com
Hi, On Wed, 13 May 2009, Sascha 'saigkill' Manns wrote:
i've getted an Bugreport for my kde4-skrooge Package. But sadly i'm on the End of my Knowledge. Has anyone an Idea? The Report is: https://bugzilla.novell.com/show_bug.cgi?id=502553
comment # reveals it. From the attachment there: # wget http://download.opensuse.org/repositories/home:/elvigia:/branches:/KDE:/KDE4... ... 2009-05-12 10:11:43 (77.4 KB/s) - `libskgbasegui1-0.2.8-20.1.x86_64.rpm' saved [4218/4218] [Ugh, quite short ...] # rpm -Uhv --force libskgbasegui1-0.2.8-20.1.x86_64.rpm ... # l /usr/lib64/libskgbas* lrwxrwxrwx 1 root root 44 May 12 10:11 /usr/lib64/libskgbasegui.so.0.2.8 -> kde4/plugins/designer/libskgbasegui.so.0.2.8* lrwxrwxrwx 1 root root 22 May 12 10:11 /usr/lib64/libskgbasegui.so.1 -> libskgbasegui.so.0.2.8* -rwxr-xr-x 1 root root 363145 May 11 18:51 /usr/lib64/libskgbasemodeler.so.0.2.8* lrwxrwxrwx 1 root root 26 May 12 10:05 /usr/lib64/libskgbasemodeler.so.1 -> libskgbasemodeler.so.0.2.8* See how /usr/lib64/libskgbasegui.so.0.2.8 is only a softlink to kde4/plugins/designer/libskgbasegui.so.0.2.8 . The latter file is missing from the package. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Mittwoch, 13. Mai 2009 schrieb Sascha 'saigkill' Manns:
Hello Mates,
i've getted an Bugreport for my kde4-skrooge Package. But sadly i'm on the End of my Knowledge. Has anyone an Idea? The Report is: https://bugzilla.novell.com/show_bug.cgi?id=502553
in my packman package I worked around this problem with packaging both *.so and *.so.* in the lib-pacakges (because I'm too lazy to fix this ...) and added a rule in rpmlintrc: addFilter("devel-file-in-non-devel-package .*/lib.*.so") from my spec-file: .... %files -n libskgbankgui1 %defattr(-, root, root) %{_libdir}/libskgbankgui.so %{_libdir}/libskgbankgui.so.* %files -n libskgbankmodeler1 %defattr(-, root, root) %{_libdir}/libskgbankmodeler.so %{_libdir}/libskgbankmodeler.so.* %files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/libskgbasegui.so %{_libdir}/libskgbasegui.so.* %files -n libskgbasemodeler1 %defattr(-, root, root) %{_libdir}/libskgbasemodeler.so %{_libdir}/libskgbasemodeler.so.* Reason of the error: make install creates symlinks from libXXX.so to libXXX.so.nr the make install should create symlinks from libXXX.so.nr to libXXX.so (the *.so is always only a symlink) have fun Toni -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Mittwoch 13 Mai 2009 22:33:22 schrieb oc2pus@arcor.de:
Am Mittwoch, 13. Mai 2009 schrieb Sascha 'saigkill' Manns:
Hello Mates,
i've getted an Bugreport for my kde4-skrooge Package. But sadly i'm on the End of my Knowledge. Has anyone an Idea? The Report is: https://bugzilla.novell.com/show_bug.cgi?id=502553
in my packman package I worked around this problem with packaging both *.so and *.so.* in the lib-pacakges (because I'm too lazy to fix this ...)
and added a rule in rpmlintrc: addFilter("devel-file-in-non-devel-package .*/lib.*.so")
from my spec-file: ....
%files -n libskgbankgui1 %defattr(-, root, root) %{_libdir}/libskgbankgui.so %{_libdir}/libskgbankgui.so.*
%files -n libskgbankmodeler1 %defattr(-, root, root) %{_libdir}/libskgbankmodeler.so %{_libdir}/libskgbankmodeler.so.*
%files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/libskgbasegui.so %{_libdir}/libskgbasegui.so.*
%files -n libskgbasemodeler1 %defattr(-, root, root) %{_libdir}/libskgbasemodeler.so %{_libdir}/libskgbasemodeler.so.*
Reason of the error: make install creates symlinks from libXXX.so to libXXX.so.nr
the make install should create symlinks from libXXX.so.nr to libXXX.so (the *.so is always only a symlink)
have fun Toni I'm using the following: %files -n libskgbankgui1 %defattr(-, root, root) %{_libdir}/libskgbankgui.so.*
%files -n libskgbankmodeler1 %defattr(-, root, root) %{_libdir}/libskgbankmodeler.so.* %files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/libskgbasegui.so.* %files -n libskgbasemodeler1 %defattr(-, root, root) %{_libdir}/libskgbasemodeler.so.* %files devel %defattr(-, root, root) %{_libdir}/libskgbankgui.so %{_libdir}/libskgbankmodeler.so %{_libdir}/libskgbasegui.so %{_libdir}/libskgbasemodeler.so %{_libdir}/kde4/plugins/designer/libskgbasegui.so %files lang -f %{realname}.lang %defattr(-, root, root) Specfile added... -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com
Hi, On Wed, 13 May 2009, Sascha 'saigkill' Manns wrote:
in my packman package I worked around this problem with packaging both *.so and *.so.* in the lib-pacakges (because I'm too lazy to fix this ...)
Don't do this please. If you're too lazy that's okay, but don't advise this to others.
I'm using the following:
%files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/libskgbasegui.so.*
%files devel %defattr(-, root, root) %{_libdir}/libskgbankgui.so %{_libdir}/libskgbankmodeler.so %{_libdir}/libskgbasegui.so %{_libdir}/libskgbasemodeler.so %{_libdir}/kde4/plugins/designer/libskgbasegui.so
You need to move the last file (the one in .../kde4/plugins/...) to the libskgbasegui1 package. It is an *.so file, so your initial intuition to put it into a -devel package was correct. But in this case it's a plugin, not a shared library, so it needs to be part of the base package as it's required at runtime, not to build against. That will fix the immediate problem. But this whole skrooge thingy is highly dubious. Plugins are not supposed to be reachable from /usr/lib (which it here is via the versioned libskgbasegui.so.* links), they are not supposed to be linked against either (again possible here via the %{_libdir}/libskgbasegui.so link). They are supposed to be loaded via a plugin loader at runtime, and in that case those links in %{_libdir}/*.so.* are not required. When I look at the other librararies in there, though, it seems as if also libskgbasegui.so isn't actually supposed to be a plugin from the start. This is also supported by the fact that the application actually links (in the ld.so sense) against this library/plugin/mixup. But this all needs to be sorted out by upstream. For now it's enough if you provide the plugin in the lib package (not the other *.so files, only the plugin). It is possible that you need to add an exception for rpmlint anyway, because it is named 'lib<something>'. Normally rpmlint should detect that this is only a plugin and not bitch about packaging *.so files in non-devel packages. But you'll need to try. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Donnerstag, 14. Mai 2009 schrieb Michael Matz:
Hi,
On Wed, 13 May 2009, Sascha 'saigkill' Manns wrote:
in my packman package I worked around this problem with packaging both *.so and *.so.* in the lib-pacakges (because I'm too lazy to fix this ...)
Don't do this please. If you're too lazy that's okay, but don't advise this to others. <snip>
I didn't advise someone, I wanted just to show how it is done in my package and why this package works. That's also the reason why I marked this workaround with the comment: # to fix by upstream install addFilter("devel-file-in-non-devel-package .*/kde4/plugins/designer/lib.*.so") addFilter("devel-file-in-non-devel-package .*/lib.*.so")
You need to move the last file (the one in .../kde4/plugins/...) to the libskgbasegui1 package. It is an *.so file, so your initial intuition to put it into a -devel package was correct. But in this case it's a plugin, not a shared library, so it needs to be part of the base package as it's required at runtime, not to build against. A devel package in this case is "senseless" without headers. How could someone use those libs without knowledge about the interface ?
And the plugin should be part of the main package and/or part of a sub-package, not part of the lib-package so I put it in the main package. Just my 2 cent.
That will fix the immediate problem. yes.
But this whole skrooge thingy is highly dubious. Plugins are not supposed to be reachable from /usr/lib (which it here is via the versioned libskgbasegui.so.* links), they are not supposed to be linked against either (again possible here via the %{_libdir}/libskgbasegui.so link). They are supposed to be loaded via a plugin loader at runtime, and in that case those links in %{_libdir}/*.so.* are not required.
When I look at the other librararies in there, though, it seems as if also libskgbasegui.so isn't actually supposed to be a plugin from the start. This is also supported by the fact that the application actually links (in the ld.so sense) against this library/plugin/mixup. But this all needs to be sorted out by upstream. For now it's enough if you provide the plugin in the lib package (not the other *.so files, only the plugin). It is possible that you need to add an exception for rpmlint anyway, because it is named 'lib<something>'. Normally rpmlint should detect that this is only a plugin and not bitch about packaging *.so files in non-devel packages. But you'll need to try.
Ciao, Michael.
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, On Thu, 14 May 2009, oc2pus@arcor.de wrote:
You need to move the last file (the one in .../kde4/plugins/...) to the libskgbasegui1 package. It is an *.so file, so your initial intuition to put it into a -devel package was correct. But in this case it's a plugin, not a shared library, so it needs to be part of the base package as it's required at runtime, not to build against. A devel package in this case is "senseless" without headers. How could someone use those libs without knowledge about the interface ?
And the plugin should be part of the main package and/or part of a sub-package, not part of the lib-package so I put it in the main package.
Well, that is what I said. I just wanted to clarify that the normal reaction of putting *.so files (being softlinks to be used by ld) into -devel packages was okay, just that in this case it's a funnily named plugin, not a lib. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi Mates, no i've modified the Spec to the following (Full Spec attatched): %files -n libskgbankgui1 %defattr(-, root, root) %{_libdir}/libskgbankgui.so.* %files -n libskgbankmodeler1 %defattr(-, root, root) %{_libdir}/libskgbankmodeler.so.* %files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/kde4/plugins/designer/libskgbasegui.so %{_libdir}/libskgbasegui.so.* %files -n libskgbasemodeler1 %defattr(-, root, root) %{_libdir}/libskgbasemodeler.so.* %files devel %defattr(-, root, root) %{_libdir}/libskgbankgui.so %{_libdir}/libskgbankmodeler.so %{_libdir}/libskgbasegui.so %{_libdir}/libskgbasemodeler.so %files lang -f %{realname}.lang %defattr(-, root, root) Actual Results: * i've set the Priority from KDE:KDE4:Community to "89" and Packman to "99" * If i now choose kde4-skrooge Yast choose the following: + all 4 libskg* Packages + lang Package + devel Package * After install all via Yast i'm get the Error: sascha@linux-eh47:~/osc/home:saigkill/kde4-skrooge> skrooge skrooge: error while loading shared libraries: libskgbasegui.so.1: cannot open shared object file: No such file or directory * Now i'm going to Yast. If i type skrooge in the Searchfield, i see that he installed all from KDE:KDE4:Community. But: kde4-skrooge, devel and lang was installed in Version 0.2.8-21.1 (my last Release). But all libskg* Files are installed in Version 0.2.8-17.1 (marked in blue). * After updating these 4 Files skrooge works. -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com
Hi Mates,
no i've modified the Spec to the following (Full Spec attatched):
%files -n libskgbankgui1 %defattr(-, root, root) %{_libdir}/libskgbankgui.so.*
%files -n libskgbankmodeler1 %defattr(-, root, root) %{_libdir}/libskgbankmodeler.so.*
%files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/kde4/plugins/designer/libskgbasegui.so %{_libdir}/libskgbasegui.so.*
%files -n libskgbasemodeler1 %defattr(-, root, root) %{_libdir}/libskgbasemodeler.so.*
%files devel %defattr(-, root, root) %{_libdir}/libskgbankgui.so %{_libdir}/libskgbankmodeler.so %{_libdir}/libskgbasegui.so %{_libdir}/libskgbasemodeler.so
%files lang -f %{realname}.lang %defattr(-, root, root)
Actual Results: * i've set the Priority from KDE:KDE4:Community to "89" and Packman to "99" * If i now choose kde4-skrooge Yast choose the following: + all 4 libskg* Packages + lang Package + devel Package * After install all via Yast i'm get the Error: sascha@linux-eh47:~/osc/home:saigkill/kde4-skrooge> skrooge skrooge: error while loading shared libraries: libskgbasegui.so.1: cannot open shared object file: No such file or directory
* Now i'm going to Yast. If i type skrooge in the Searchfield, i see that he installed all from KDE:KDE4:Community. But: kde4-skrooge, devel and lang was installed in Version 0.2.8-21.1 (my last Release). But all libskg* Files are installed in Version 0.2.8-17.1 (marked in blue).
* After updating these 4 Files skrooge works. do a real test: remove all packages AND remove all old files from former installations. Than
Am Donnerstag, 14. Mai 2009 schrieb Sascha 'saigkill' Manns: libskgbasegui.so.1 is only a link ... so it can't work or you install the devel package That's the reason yast pulls in the devel package. And your devel-package is missing Requires, nomally all packages you need as BuildRequires for the main package should be required by the devel-package as Requires. And than, your devel package will pull in a lot of devel packages as long as you don't change the links for libsk* ==> libskgbasegui.so.1 must be a real file and libskgbasegui.so is a link to it. try to reinstall and you'll see it won't work as libskgbasegui.so.1 is only a link. have fun Toni -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, On Thu, 14 May 2009, oc2pus@arcor.de wrote:
%files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/kde4/plugins/designer/libskgbasegui.so ^^^^^^^^^^^^^^^^^
libskgbasegui.so.1 is only a link ... so it can't work
That's why he includes the link target now also in the base package as advised. His mail can be understood as a before/after test, when he installs the fixed (as of above) packages, instead of the old ones with the broken link. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Donnerstag 14 Mai 2009 13:55:08 wrote Michael Matz:
Hi,
On Thu, 14 May 2009, oc2pus@arcor.de wrote:
%files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/kde4/plugins/designer/libskgbasegui.so
^^^^^^^^^^^^^^^^^
libskgbasegui.so.1 is only a link ... so it can't work
That's why he includes the link target now also in the base package as advised. His mail can be understood as a before/after test, when he installs the fixed (as of above) packages, instead of the old ones with the broken link. I readed the CMakeList.txt: INSTALL(TARGETS skgbasegui LIBRARY DESTINATION ${LIB_INSTALL_DIR} ) INSTALL(TARGETS skgbasegui LIBRARY DESTINATION ${PLUGIN_INSTALL_DIR}/plugins/designer ) AFAIK this means, that two libskgbasegui created. One in %{_libdir} and one in %{_libdir}/kde4/plugins/designer/....
-- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com
Hi, On Thu, 14 May 2009, Sascha 'saigkill' Manns wrote:
On Thu, 14 May 2009, oc2pus@arcor.de wrote:
%files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/kde4/plugins/designer/libskgbasegui.so
^^^^^^^^^^^^^^^^^
libskgbasegui.so.1 is only a link ... so it can't work
That's why he includes the link target now also in the base package as advised. His mail can be understood as a before/after test, when he installs the fixed (as of above) packages, instead of the old ones with the broken link. I readed the CMakeList.txt: INSTALL(TARGETS skgbasegui LIBRARY DESTINATION ${LIB_INSTALL_DIR} ) INSTALL(TARGETS skgbasegui LIBRARY DESTINATION ${PLUGIN_INSTALL_DIR}/plugins/designer ) AFAIK this means, that two libskgbasegui created. One in %{_libdir} and one in %{_libdir}/kde4/plugins/designer/....
Then somebody else converts the former into a softlink to the latter. But we know that something does that. You'll have to find out :) Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Donnerstag 14 Mai 2009 17:41:59 wrote Michael Matz:
Hi,
On Thu, 14 May 2009, Sascha 'saigkill' Manns wrote:
On Thu, 14 May 2009, oc2pus@arcor.de wrote:
%files -n libskgbasegui1 %defattr(-, root, root) %{_libdir}/kde4/plugins/designer/libskgbasegui.so
^^^^^^^^^^^^^^^^^
libskgbasegui.so.1 is only a link ... so it can't work
That's why he includes the link target now also in the base package as advised. His mail can be understood as a before/after test, when he installs the fixed (as of above) packages, instead of the old ones with the broken link.
I readed the CMakeList.txt: INSTALL(TARGETS skgbasegui LIBRARY DESTINATION ${LIB_INSTALL_DIR} ) INSTALL(TARGETS skgbasegui LIBRARY DESTINATION ${PLUGIN_INSTALL_DIR}/plugins/designer ) AFAIK this means, that two libskgbasegui created. One in %{_libdir} and one in %{_libdir}/kde4/plugins/designer/....
Then somebody else converts the former into a softlink to the latter. But we know that something does that. You'll have to find out :) I've grepped the BuildLog:
Linking CXX shared library ../lib/libskgbasegui.so cd /usr/src/packages/BUILD/skrooge-0.2.8/skgbasegui && /usr/bin/cmake -E cmake_link_script CMakeFiles/skgbasegui.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -Wall -O2 -DNDEBUG -DQT_NO_DEBUG -Wl,--enable-new- dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc -Wl,-Bsymbolic- functions -shared -Wl,-soname,libskgbasegui.so.1 -o ../lib/libskgbasegui.so.0.2.8 CMakeFiles/skgbasegui.dir/skgbasegui_automoc.o CMakeFiles/skgbasegui.dir/skgmainpanel.o CMakeFiles/skgbasegui.dir/skgobjectmodelbase.o CMakeFiles/skgbasegui.dir/skgtabwidget.o CMakeFiles/skgbasegui.dir/skginterfaceplugin.o CMakeFiles/skgbasegui.dir/skgwidgetcollectiondesignerplugin.o CMakeFiles/skgbasegui.dir/skgtableviewdesignerplugin.o CMakeFiles/skgbasegui.dir/skgtableview.o CMakeFiles/skgbasegui.dir/skgtreeviewdesignerplugin.o CMakeFiles/skgbasegui.dir/skgtreeview.o CMakeFiles/skgbasegui.dir/skgcomboboxdesignerplugin.o CMakeFiles/skgbasegui.dir/skgcombobox.o CMakeFiles/skgbasegui.dir/skgcalculatoreditdesignerplugin.o CMakeFiles/skgbasegui.dir/skgcalculatoredit.o CMakeFiles/skgbasegui.dir/skggraphicsviewdesignerplugin.o CMakeFiles/skgbasegui.dir/skggraphicsscene.o CMakeFiles/skgbasegui.dir/skggraphicsview.o CMakeFiles/skgbasegui.dir/skgtablewithgraphdesignerplugin.o CMakeFiles/skgbasegui.dir/skgtablewithgraph.o CMakeFiles/skgbasegui.dir/skgdateeditdesignerplugin.o CMakeFiles/skgbasegui.dir/skgdateedit.o CMakeFiles/skgbasegui.dir/skgsortfilterproxymodel.o CMakeFiles/skgbasegui.dir/skgautohide.o CMakeFiles/skgbasegui.dir/skrooge.o - L/usr/src/packages/BUILD/skrooge-0.2.8/lib -lQtDesigner -lQtScript - lQtSvg -lQtCore -lpthread -lkdecore -lSM -lICE -lX11 -lXext -lXft -lXau -lXdmcp -lXpm -lQtGui -lQtXml -lXtst -lXcursor -lXfixes -lXrender - lkdeui -lQtCore -lpthread -lkdecore -lkdeui -lkio -lkparts -lQtCore - lpthread -lkdecore -lkdeui -lkio -lz -lQtCore -lpthread -lkdecore - lsolid -lkfile ../lib/libskgbasemodeler.so.0.2.8 -lkdeui -lQtSvg -lXtst -lXcursor -lXfixes -lstreamanalyzer -lstreams -lkdecore -lbz2 -lresolv - lSM -lICE -lX11 -lXext -lXft -lXau -lXdmcp -lXpm -lQtNetwork -lfam - lXrender -lz -lsolid -lQtGui -lQtDBus -lQtXml -lQtSql -lQtCore -lpthread -lqca -lsqlite3 cd /usr/src/packages/BUILD/skrooge-0.2.8/skgbasegui && /usr/bin/cmake -E cmake_symlink_library ../lib/libskgbasegui.so.0.2.8 ../lib/libskgbasegui.so.1 ../lib/libskgbasegui.so Installing: /var/tmp/kde4-skrooge-0.2.8- build/usr/lib64/libskgbasegui.so.0.2.8 -- Installing: /var/tmp/kde4-skrooge-0.2.8- build/usr/lib64/libskgbasegui.so.1 -- Installing: /var/tmp/kde4-skrooge-0.2.8- build/usr/lib64/libskgbasegui.so Installing: /var/tmp/kde4-skrooge-0.2.8- build/usr/lib64/kde4/plugins/designer/libskgbasegui.so.0.2.8 Installing: /var/tmp/kde4-skrooge-0.2.8- build/usr/lib64/kde4/plugins/designer/libskgbasegui.so.1 -- Installing: /var/tmp/kde4-skrooge-0.2.8- build/usr/lib64/kde4/plugins/designer/libskgbasegui.so find %buildroot in *.spec: /var/tmp/kde4-skrooge-0.2.8-build/usr/lib64/libskgbasegui.so.1 INFO: relinking /usr/lib64/libskgbasegui.so.0.2.8 -> kde4/plugins/designer/libskgbasegui.so.0.2.8 (was /usr/lib64/kde4/plugins/designer/libskgbasegui.so.0.2.8) Is this right? Or must i fix on another Place? -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com
Hi, On Thu, 14 May 2009, Sascha 'saigkill' Manns wrote:
INFO: relinking /usr/lib64/libskgbasegui.so.0.2.8 -> kde4/plugins/designer/libskgbasegui.so.0.2.8 (was /usr/lib64/kde4/plugins/designer/libskgbasegui.so.0.2.8)
Is this right? Or must i fix on another Place?
Yes, it is right, but that output also means that at that point /usr/lib64/libskgbasegui.so.0.2.8 already was a softlink to /usr/lib64/kde4/plugins/designer/libskgbasegui.so.0.2.8 . And at least I don't see anything obvious in your greped logfile. Maybe one could make cmake more verbose during the install phase. Otherwise somebody needs to build it locally and try to figure out what makes this a symlink instead of a normal copy which was generated initially by cmake (at least according to the INSTALL() commands). Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hello Mates, it would be great, if you can test kde4-skrooge from KDE:KDE4:Community. Works that Program for you? -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com
participants (3)
-
Michael Matz -
oc2pus＠arcor.de -
Sascha 'saigkill' Manns