[opensuse] digikam crashes
The system I used before my fatal upgrade ran digikam. Now I receive a signal: Segmentation fault when it is run. It says it is using /lib64/libthread_db.so.1, and the current thread is 1. If I examine the dependencies for digikam in Yast2, it shows libpthread.so.0(GLIBC_2.2.5)(64bit) Could this be the problem, or is there more info somewhere else? The last entry in the dump for thread 1 is: Thread 1 (Thread 0x7f145f4a7880 (LWP 3562)): [KCrash Handler] #5 0x00007f1457fb406c in __strcmp_ssse3 () at /lib64/libc.so.6 I did a search for libthread under Yast2, with the contains switch, and is says there are no results. But the same Yast2 code lists libthread_db as a dependency. Comments welcome. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-01-22 22:21, don fisher wrote:
I did a search for libthread under Yast2, with the contains switch, and is says there are no results. But the same Yast2 code lists libthread_db as a dependency.
cer@Telcontar:~> l /lib/libthread_db-1.0.so -rwxr-xr-x 1 root root 34555 Aug 5 12:01 /lib/libthread_db-1.0.so* cer@Telcontar:~> rpm -qf /lib/libthread_db-1.0.so glibc-32bit-2.18-4.38.2.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qf /lib64/libthread_db-1.0.so glibc-2.18-4.38.1.x86_64 It comes in a different library. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 01/23/2016 08:26 AM, Carlos E. R. wrote:
On 2016-01-22 22:21, don fisher wrote:
I did a search for libthread under Yast2, with the contains switch, and is says there are no results. But the same Yast2 code lists libthread_db as a dependency.
cer@Telcontar:~> l /lib/libthread_db-1.0.so -rwxr-xr-x 1 root root 34555 Aug 5 12:01 /lib/libthread_db-1.0.so* cer@Telcontar:~> rpm -qf /lib/libthread_db-1.0.so glibc-32bit-2.18-4.38.2.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qf /lib64/libthread_db-1.0.so glibc-2.18-4.38.1.x86_64
It comes in a different library.
Thanks. Do you know how I determine what library it is part of? I did a YaST2 search, with the switch contains, and received no results. I though the contains switch was supposed to inform a user of what package some component is contained in. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/23/2016 11:48 AM, don fisher wrote:
On 01/23/2016 08:26 AM, Carlos E. R. wrote:
On 2016-01-22 22:21, don fisher wrote:
I did a search for libthread under Yast2, with the contains switch, and is says there are no results. But the same Yast2 code lists libthread_db as a dependency.
cer@Telcontar:~> l /lib/libthread_db-1.0.so -rwxr-xr-x 1 root root 34555 Aug 5 12:01 /lib/libthread_db-1.0.so* cer@Telcontar:~> rpm -qf /lib/libthread_db-1.0.so glibc-32bit-2.18-4.38.2.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qf /lib64/libthread_db-1.0.so glibc-2.18-4.38.1.x86_64
It comes in a different library.
Thanks. Do you know how I determine what library it is part of? I did a YaST2 search, with the switch contains, and received no results. I though the contains switch was supposed to inform a user of what package some component is contained in.
Don
He showed you a command line example of how to do that. (two of them). In Yast, Contains means you are giving a partial name. You want to check the RPM provides box, as well as setting search mode to "contains" or "begins with". -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/23/2016 12:59 PM, John Andersen wrote:
On 01/23/2016 11:48 AM, don fisher wrote:
On 01/23/2016 08:26 AM, Carlos E. R. wrote:
On 2016-01-22 22:21, don fisher wrote:
I did a search for libthread under Yast2, with the contains switch, and is says there are no results. But the same Yast2 code lists libthread_db as a dependency.
cer@Telcontar:~> l /lib/libthread_db-1.0.so -rwxr-xr-x 1 root root 34555 Aug 5 12:01 /lib/libthread_db-1.0.so* cer@Telcontar:~> rpm -qf /lib/libthread_db-1.0.so glibc-32bit-2.18-4.38.2.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qf /lib64/libthread_db-1.0.so glibc-2.18-4.38.1.x86_64
It comes in a different library.
Thanks. Do you know how I determine what library it is part of? I did a YaST2 search, with the switch contains, and received no results. I though the contains switch was supposed to inform a user of what package some component is contained in.
Don
He showed you a command line example of how to do that. (two of them).
In Yast, Contains means you are giving a partial name.
You want to check the RPM provides box, as well as setting search mode to "contains" or "begins with".
sorry to be so dumb about this. I turned on the provides, as well as contains, and get nothing unless I reduce the search string to "libthread_db". I received glibc-2.19-16.18.1, and under installed version it listed 2.19-16.18.1, which matches. Below, where I thought is was saying provides, there are numerous entries for libthread_db.so.1. So my question is, how does one install the glibc-2.18-4.38.1.x86_64 package referenced above, and what impact will installing an older revision have on my system. Can both exist at once? Shouldn't digikam be rewritten/compiled consistent with the current libraries? I just do not know which way to go. I wish I could get statically linked versions of some of these apps. Thanks for your suggestions, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1/23/2016 12:57 PM, don fisher wrote:
On 01/23/2016 12:59 PM, John Andersen wrote:
On 01/23/2016 11:48 AM, don fisher wrote:
On 01/23/2016 08:26 AM, Carlos E. R. wrote:
On 2016-01-22 22:21, don fisher wrote:
I did a search for libthread under Yast2, with the contains switch, and is says there are no results. But the same Yast2 code lists libthread_db as a dependency.
cer@Telcontar:~> l /lib/libthread_db-1.0.so -rwxr-xr-x 1 root root 34555 Aug 5 12:01 /lib/libthread_db-1.0.so* cer@Telcontar:~> rpm -qf /lib/libthread_db-1.0.so glibc-32bit-2.18-4.38.2.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qf /lib64/libthread_db-1.0.so glibc-2.18-4.38.1.x86_64
It comes in a different library.
Thanks. Do you know how I determine what library it is part of? I did a YaST2 search, with the switch contains, and received no results. I though the contains switch was supposed to inform a user of what package some component is contained in.
Don
He showed you a command line example of how to do that. (two of them).
In Yast, Contains means you are giving a partial name.
You want to check the RPM provides box, as well as setting search mode to "contains" or "begins with".
sorry to be so dumb about this. I turned on the provides, as well as contains, and get nothing unless I reduce the search string to "libthread_db". I received glibc-2.19-16.18.1, and under installed version it listed 2.19-16.18.1, which matches. Below, where I thought is was saying provides, there are numerous entries for libthread_db.so.1.
So my question is, how does one install the glibc-2.18-4.38.1.x86_64 package referenced above, and what impact will installing an older revision have on my system.
Can both exist at once?
This is where Yast really shines. Go into yast, select just the glibc-2.18-4.38.1.x86_64 and select install option. If there is a conflict it will tell you and you can bail out. If it says its going to load in a boat load of additional packages, you might also choose to bail out at that time. But its FAR BETTER to let yast handle the whole thing than to end-run it and start installing packages. If Yast says the dependencies for Digicam can't be met, then you might need to add another of the suse repositories or you might need to wait a week for the repositories to catch up. Or file a bug report.
Shouldn't digikam be rewritten/compiled consistent with the current libraries?
Yes it should be, and it probably will be. If you put this issue aside for a week or two it probably will solve itself. And by Yast I mean Yast2 -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/23/2016 04:08 PM, John Andersen wrote:
On 1/23/2016 12:57 PM, don fisher wrote:
On 01/23/2016 12:59 PM, John Andersen wrote:
On 01/23/2016 11:48 AM, don fisher wrote:
On 01/23/2016 08:26 AM, Carlos E. R. wrote:
On 2016-01-22 22:21, don fisher wrote:
I did a search for libthread under Yast2, with the contains switch, and is says there are no results. But the same Yast2 code lists libthread_db as a dependency.
cer@Telcontar:~> l /lib/libthread_db-1.0.so -rwxr-xr-x 1 root root 34555 Aug 5 12:01 /lib/libthread_db-1.0.so* cer@Telcontar:~> rpm -qf /lib/libthread_db-1.0.so glibc-32bit-2.18-4.38.2.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qf /lib64/libthread_db-1.0.so glibc-2.18-4.38.1.x86_64
It comes in a different library.
Thanks. Do you know how I determine what library it is part of? I did a YaST2 search, with the switch contains, and received no results. I though the contains switch was supposed to inform a user of what package some component is contained in.
Don
He showed you a command line example of how to do that. (two of them).
In Yast, Contains means you are giving a partial name.
You want to check the RPM provides box, as well as setting search mode to "contains" or "begins with".
sorry to be so dumb about this. I turned on the provides, as well as contains, and get nothing unless I reduce the search string to "libthread_db". I received glibc-2.19-16.18.1, and under installed version it listed 2.19-16.18.1, which matches. Below, where I thought is was saying provides, there are numerous entries for libthread_db.so.1.
So my question is, how does one install the glibc-2.18-4.38.1.x86_64 package referenced above, and what impact will installing an older revision have on my system.
Can both exist at once?
This is where Yast really shines. Go into yast, select just the glibc-2.18-4.38.1.x86_64 and select install option. If there is a conflict it will tell you and you can bail out. If it says its going to load in a boat load of additional packages, you might also choose to bail out at that time.
But its FAR BETTER to let yast handle the whole thing than to end-run it and start installing packages.
If Yast says the dependencies for Digicam can't be met, then you might need to add another of the suse repositories or you might need to wait a week for the repositories to catch up. Or file a bug report.
Shouldn't digikam be rewritten/compiled consistent with the current libraries?
Yes it should be, and it probably will be. If you put this issue aside for a week or two it probably will solve itself.
And by Yast I mean Yast2
I do no know how to get Yast2 to show glibc-2.18-4.38.1. The only glibc shown is 2.19-16.18.1, the currently installed version. As an alternative I looked at rebuilding digikam from the src RPM, but 31 additional packages are required. So while it may be a great exercise, I do not dare attempt it at this point. How can I find out if anybody is doing a rebuild? Along the same lines, how does one find the status of bug reports? I filed one, and there is nothing under my bugzilla account. Is there an index somewhere? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* don fisher
On 01/23/2016 04:08 PM, John Andersen wrote:
On 1/23/2016 12:57 PM, don fisher wrote:
On 01/23/2016 12:59 PM, John Andersen wrote:
On 01/23/2016 11:48 AM, don fisher wrote:
On 01/23/2016 08:26 AM, Carlos E. R. wrote:
On 2016-01-22 22:21, don fisher wrote:
>I did a search for libthread under Yast2, with the contains switch, and >is says there are no results. But the same Yast2 code lists libthread_db >as a dependency.
cer@Telcontar:~> l /lib/libthread_db-1.0.so -rwxr-xr-x 1 root root 34555 Aug 5 12:01 /lib/libthread_db-1.0.so* cer@Telcontar:~> rpm -qf /lib/libthread_db-1.0.so glibc-32bit-2.18-4.38.2.x86_64 cer@Telcontar:~> cer@Telcontar:~> rpm -qf /lib64/libthread_db-1.0.so glibc-2.18-4.38.1.x86_64
It comes in a different library.
Thanks. Do you know how I determine what library it is part of? I did a YaST2 search, with the switch contains, and received no results. I though the contains switch was supposed to inform a user of what package some component is contained in.
Don
He showed you a command line example of how to do that. (two of them).
In Yast, Contains means you are giving a partial name.
You want to check the RPM provides box, as well as setting search mode to "contains" or "begins with".
sorry to be so dumb about this. I turned on the provides, as well as contains, and get nothing unless I reduce the search string to "libthread_db". I received glibc-2.19-16.18.1, and under installed version it listed 2.19-16.18.1, which matches. Below, where I thought is was saying provides, there are numerous entries for libthread_db.so.1.
So my question is, how does one install the glibc-2.18-4.38.1.x86_64 package referenced above, and what impact will installing an older revision have on my system.
Can both exist at once?
This is where Yast really shines. Go into yast, select just the glibc-2.18-4.38.1.x86_64 and select install option. If there is a conflict it will tell you and you can bail out. If it says its going to load in a boat load of additional packages, you might also choose to bail out at that time.
But its FAR BETTER to let yast handle the whole thing than to end-run it and start installing packages.
If Yast says the dependencies for Digicam can't be met, then you might need to add another of the suse repositories or you might need to wait a week for the repositories to catch up. Or file a bug report.
Shouldn't digikam be rewritten/compiled consistent with the current libraries?
Yes it should be, and it probably will be. If you put this issue aside for a week or two it probably will solve itself.
And by Yast I mean Yast2
I do no know how to get Yast2 to show glibc-2.18-4.38.1. The only glibc shown is 2.19-16.18.1, the currently installed version. As an alternative I looked at rebuilding digikam from the src RPM, but 31 additional packages are required. So while it may be a great exercise, I do not dare attempt it at this point. How can I find out if anybody is doing a rebuild? Along the same lines, how does one find the status of bug reports? I filed one, and there is nothing under my bugzilla account. Is there an index somewhere?
zypper -vv in --force digikam will reinstall digikam and display discrepancies and probably will correct errors on your system by offering to install the correct libs. I *is* supposed to. zypper ve will verify that correct file dependencies are installed on your system, and note problems. use the force, luke -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* don fisher
On 01/23/2016 04:59 PM, Patrick Shanahan wrote:
zypper -vv in --force digikam
Still crashes on my system. Does it run on yours?
most certainly. But you give no information here. Did you run: zypper ve ??? Was there any messages from "zypper -vv in --force digikam"? I cannot see you monitor. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/23/2016 05:28 PM, Patrick Shanahan wrote:
zypper ve Sorry. What is the entire command. zypper ve digikam yields Unknown option 'e'
sudo zypper verify Loading repository data... Reading installed packages... Dependencies of all installed packages are satisfied. On the zypper -vv in --force digikam there were many messages, but no references to /lib64/libthread_db.so.1 that I could see. Again, my dump screen complains about segfault Using host libthread_db library /lib64/libthread_db.so.1. If I look at the Yast2 dependencies, it claims it is built against for /lib64/libthread_db.so.0. So examined the files in /lib64 and found: /lib64/libthread_db-1.0.so* /lib64/libthread_db.so.1 -> libthread_db-1.0.so* Do libthread_db.so.1 is a link to libthread_db-1.0. So I do not know why it crashes:-( I have attached the crash dump if you are curious. Thanks for the help. And curious why it is working for you. Don
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-01-24 02:05, don fisher wrote:
On 01/23/2016 05:28 PM, Patrick Shanahan wrote:
zypper ve Sorry. What is the entire command. zypper ve digikam yields
Just "zypper ve". No more words.
itI have attached the crash dump if you are curious.
There is no signal there that there is a problem with libthread_db. Rather that something is using that library and an error is detected. Please do not assume that you have to replace that library. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlakKbAACgkQja8UbcUWM1wPUgD/WfNPhhJ5/tNO3trhFll/qv3t g62+w3aH13ReVRRiuccA/j3NvtKgNAFkCfEFnRENanSaY+xm+sz/Le2oqy7r3/v2 =Ybqv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* don fisher
On 01/23/2016 05:28 PM, Patrick Shanahan wrote:
zypper ve Sorry. What is the entire command. zypper ve digikam yields Unknown option 'e'
sudo zypper verify Loading repository data... Reading installed packages... Dependencies of all installed packages are satisfied.
On the zypper -vv in --force digikam there were many messages, but no references to /lib64/libthread_db.so.1 that I could see. Again, my dump screen complains about segfault Using host libthread_db library /lib64/libthread_db.so.1. If I look at the Yast2 dependencies, it claims it is built against for /lib64/libthread_db.so.0.
So examined the files in /lib64 and found: /lib64/libthread_db-1.0.so* /lib64/libthread_db.so.1 -> libthread_db-1.0.so*
Do libthread_db.so.1 is a link to libthread_db-1.0. So I do not know why it crashes:-( I have attached the crash dump if you are curious.
Thanks for the help. And curious why it is working for you. Don
I have: tw 20160121 digikam-4.14.0-86.3.x86_64 glibc-2.22-6.2.x86_64 which provides /usr/lib64/libthread_db.so.1 I would be interested in what you got from "zypper -vv in --force digikam", especially since you say "zypper ve" said "Dependencies of all installed packages are satisfied." It appears you have a broken package installed, I'm guessing. And the final step w/o running gdb and someone reading the failure output for you (I am not qualified), would be to run: rpm -q --requires digikam output will be packages that digikam requires and reinstall all or several and intermittently trying to run digikam to determing when you have replaced the borked package. ie: rpm -q --requires digikam /bin/sh /sbin/ldconfig /sbin/ldconfig /usr/bin/perl digikam-libs kdebase4-runtime >= 4.14.0 kipi-plugins >= 4.14.0 libQtCore.so.4()(64bit) libQtDBus.so.4()(64bit) ... taking libQtCore.so.4: zypper -v wp libQtCore.so.4 Verbosity: 1 Non-option program arguments: 'libQtCore.so.4' Command 'what-provides' is replaced by 'search --provides --match-exact'. See 'help search' for all available options. Initializing Target Loading repository data... Reading installed packages... Force resolution: No S | Name | Summary | Type --+--------------+--------------------------------------+-------- i | libqt4 | C++ Program Library, Core Components | package | libqt4-32bit | C++ Program Library, Core Components | package zypper -v in --force libqt4 BUT, you might first try: zypper -v in --force digikam-libs and see if that solves it. If not, the loong road..., -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/23/2016 06:33 PM, Patrick Shanahan wrote:
zypper -v in --force digikam-libs Command zypper -v in --force digikam-libs yielded Package 'digikam-libs' not found.
I will try more tomorrow. Thanks for your help:-) Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/23/2016 06:53 PM, don fisher wrote:
On 01/23/2016 06:33 PM, Patrick Shanahan wrote:
zypper -v in --force digikam-libs Command zypper -v in --force digikam-libs yielded Package 'digikam-libs' not found.
I will try more tomorrow. Thanks for your help:-) Don
If one downloads the digikam src RPM there many dependencies called for. ImageMagick-devel is needed by digikam-4.3.0-2.2.x86_64 bison is needed by digikam-4.3.0-2.2.x86_64 boost-devel is needed by digikam-4.3.0-2.2.x86_64 doxygen is needed by digikam-4.3.0-2.2.x86_64 flex is needed by digikam-4.3.0-2.2.x86_64 libxml2-devel is needed by digikam-4.3.0-2.2.x86_64 libxslt-devel is needed by digikam-4.3.0-2.2.x86_64 baloo-devel is needed by digikam-4.3.0-2.2.x86_64 gstreamer-plugins-qt-devel is needed by digikam-4.3.0-2.2.x86_64 lensfun-devel is needed by digikam-4.3.0-2.2.x86_64 libeigen3-devel is needed by digikam-4.3.0-2.2.x86_64 libgpod-devel is needed by digikam-4.3.0-2.2.x86_64 libjasper-devel is needed by digikam-4.3.0-2.2.x86_64 libkdcraw-devel is needed by digikam-4.3.0-2.2.x86_64 libkde4-devel is needed by digikam-4.3.0-2.2.x86_64 libkdepimlibs4-devel is needed by digikam-4.3.0-2.2.x86_64 libkexiv2-devel is needed by digikam-4.3.0-2.2.x86_64 pkgconfig(libkipi) >= 2.0.0 is needed by digikam-4.3.0-2.2.x86_64 libkqoauth-devel is needed by digikam-4.3.0-2.2.x86_64 libMagick++-devel is needed by digikam-4.3.0-2.2.x86_64 libksane-devel is needed by digikam-4.3.0-2.2.x86_64 libkvkontakte-devel is needed by digikam-4.3.0-2.2.x86_64 liblcms2-devel is needed by digikam-4.3.0-2.2.x86_64 liblqr-devel is needed by digikam-4.3.0-2.2.x86_64 libpgf-devel is needed by digikam-4.3.0-2.2.x86_64 libqca2-devel is needed by digikam-4.3.0-2.2.x86_64 libqjson-devel is needed by digikam-4.3.0-2.2.x86_64 libusb-compat-devel is needed by digikam-4.3.0-2.2.x86_64 marble-devel is needed by digikam-4.3.0-2.2.x86_64 opencv-devel >= 2.4.5 is needed by digikam-4.3.0-2.2.x86_64 pkgconfig(glu) is needed by digikam-4.3.0-2.2.x86_64 Previously I have not tried to recompile an opensuse source RPM. Do I just make a script and ask zypper to install all if these packages. Or is there some automated way to do it? Then I guess I have to turn around and remove all of them? If I wish to build some of them to support gdb, is there a way to do all of this in some local directory? In my past life I was able to keep all of my experimental builds separate from the running system. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/24/2016 11:15 AM, don fisher wrote:
On 01/23/2016 06:53 PM, don fisher wrote:
On 01/23/2016 06:33 PM, Patrick Shanahan wrote:
zypper -v in --force digikam-libs Command zypper -v in --force digikam-libs yielded Package 'digikam-libs' not found.
I will try more tomorrow. Thanks for your help:-) Don
If one downloads the digikam src RPM there many dependencies called for. ImageMagick-devel is needed by digikam-4.3.0-2.2.x86_64 bison is needed by digikam-4.3.0-2.2.x86_64 boost-devel is needed by digikam-4.3.0-2.2.x86_64 doxygen is needed by digikam-4.3.0-2.2.x86_64 flex is needed by digikam-4.3.0-2.2.x86_64 libxml2-devel is needed by digikam-4.3.0-2.2.x86_64 libxslt-devel is needed by digikam-4.3.0-2.2.x86_64 baloo-devel is needed by digikam-4.3.0-2.2.x86_64 gstreamer-plugins-qt-devel is needed by digikam-4.3.0-2.2.x86_64 lensfun-devel is needed by digikam-4.3.0-2.2.x86_64 libeigen3-devel is needed by digikam-4.3.0-2.2.x86_64 libgpod-devel is needed by digikam-4.3.0-2.2.x86_64 libjasper-devel is needed by digikam-4.3.0-2.2.x86_64 libkdcraw-devel is needed by digikam-4.3.0-2.2.x86_64 libkde4-devel is needed by digikam-4.3.0-2.2.x86_64 libkdepimlibs4-devel is needed by digikam-4.3.0-2.2.x86_64 libkexiv2-devel is needed by digikam-4.3.0-2.2.x86_64 pkgconfig(libkipi) >= 2.0.0 is needed by digikam-4.3.0-2.2.x86_64 libkqoauth-devel is needed by digikam-4.3.0-2.2.x86_64 libMagick++-devel is needed by digikam-4.3.0-2.2.x86_64 libksane-devel is needed by digikam-4.3.0-2.2.x86_64 libkvkontakte-devel is needed by digikam-4.3.0-2.2.x86_64 liblcms2-devel is needed by digikam-4.3.0-2.2.x86_64 liblqr-devel is needed by digikam-4.3.0-2.2.x86_64 libpgf-devel is needed by digikam-4.3.0-2.2.x86_64 libqca2-devel is needed by digikam-4.3.0-2.2.x86_64 libqjson-devel is needed by digikam-4.3.0-2.2.x86_64 libusb-compat-devel is needed by digikam-4.3.0-2.2.x86_64 marble-devel is needed by digikam-4.3.0-2.2.x86_64 opencv-devel >= 2.4.5 is needed by digikam-4.3.0-2.2.x86_64 pkgconfig(glu) is needed by digikam-4.3.0-2.2.x86_64
Previously I have not tried to recompile an opensuse source RPM. Do I just make a script and ask zypper to install all if these packages. Or is there some automated way to do it? Then I guess I have to turn around and remove all of them? If I wish to build some of them to support gdb, is there a way to do all of this in some local directory?
In my past life I was able to keep all of my experimental builds separate from the running system.
Don
Why not just use Yast? Select the item you want, (digikam src RPM) from the source repository, and let it worry about the dependencies. These are all Developmental libraries, usually quite small. But still you don't want to be micromanaging the install of individual RPMs. There is probably an equivalent zypper to fetch all the dependencies, when you install digikam src RPM but writing a script is the exactly wrong thing to do. We've spent 10 years trying to get away from RPM-Hell, and jumping back into it is crazy. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/24/2016 02:50 PM, John Andersen wrote:
But still you don't want to be micromanaging the install of individual RPMs.
+ BIGNUM
There is probably an equivalent zypper to fetch all the dependencies, when you install digikam src RPM but writing a script is the exactly wrong thing to do.
See my other post for details.
We've spent 10 years trying to get away from RPM-Hell, and jumping back into it is crazy.
+ BIGNUM SQUARED! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/24/2016 02:15 PM, don fisher wrote:
On 01/23/2016 06:53 PM, don fisher wrote:
On 01/23/2016 06:33 PM, Patrick Shanahan wrote:
zypper -v in --force digikam-libs Command zypper -v in --force digikam-libs yielded Package 'digikam-libs' not found.
I will try more tomorrow. Thanks for your help:-) Don
If one downloads the digikam src RPM there many dependencies called for.
[BIG SNIP]
Previously I have not tried to recompile an opensuse source RPM.
I've not built digikam but i have built other packages. The way zypper works, if you download a package that needs other packages it tells you and offers to download them automatically. no need to write a script to do the extraction. if you are downloading from a regular repository its going to make use of the repository indexes that it knows about (all the ones you have enabled) to find those packages. If this is a J.random.RPM from who knows where, it may or may not be able to find the packages.
is there a way to do all of this in some local directory?
Yes, RTFM.
In my past life I was able to keep all of my experimental builds separate from the running system.
It depends what you mean by 'running system'. In a professional context such as the bank, we don't let any development be done on the production systems, that is those that are client-facing. But any development system in the development labs is of course running. How else could it work? If you notice, there is already a /usr/src tree. if you mean doing the development & testing there rather than /usr/bin, then .... guess what? Some of this you could have found out by RTFM, some by experimentation using the "-D for --dry-run" option of zypper which you'd have found if you RTFM, or the "--test" for rpm, ditto. All this I found out, and more, by (a) RTFM, and (b) experimentation. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-01-23 21:57, don fisher wrote:
So my question is, how does one install the glibc-2.18-4.38.1.x86_64 package referenced above,
When YaST gives a response to the query about which rpm contains certain file, it is because it is already installed.
and what impact will installing an older revision have on my system.
Don't even think to try. No kidding. Only consider it when you know yourself the answer to that question. Again, no kidding. The problem is not the threads library or glibc. glibc is only reporting a problem with your application, that is, digikam. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-01-23 20:48, don fisher wrote:
It comes in a different library.
Thanks. Do you know how I determine what library it is part of? I did a YaST2 search, with the switch contains, and received no results. I though the contains switch was supposed to inform a user of what package some component is contained in.
I used first "locate libthread_db" to find the file, then "rpm -qf /path/file" to find out what rpm it comes from. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (5)
-
Anton Aylward -
Carlos E. R. -
don fisher -
John Andersen -
Patrick Shanahan