[opensuse-factory] digikam-libs conflicts when updating Tumbleweed 20160121
Hi I have Tumbleweed 20160121 and just did a "zypper up". It brings up the following error. 8 Dateikonflikte festgestellt: File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System) File /usr/lib64/libkexiv2.so.11.3.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkexiv2-11-15.08.3-2.1.x86_64(@System) File /usr/lib64/libkface.so.3.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkface3-15.08.3-1.1.x86_64(@System) File /usr/lib64/libkgeomap.so.2.1.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkgeomap2-15.08.3-1.1.x86_64(@System) File /usr/lib64/libkipi.so.11.1.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkipi11-15.08.3-1.1.x86_64(@System) File /usr/lib64/libksane.so.0.2.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libksane0-15.08.3-1.2.x86_64(@System) File /usr/lib64/libmediawiki.so.1.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libmediawiki1-4.13.0-2.1.x86_64(@System) File /usr/share/kde4/servicetypes/kipiplugin.desktop from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkipi11-15.08.3-1.1.x86_64(@System) How to fix this double packaged files? best regards Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Thomas, On Sat, 30 Jan 2016, 13:20:18 +0100, Thomas Wagner wrote:
Hi
I have Tumbleweed 20160121 and just did a "zypper up". It brings up the following error.
8 Dateikonflikte festgestellt:
File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System) [...]
I see this on almost all of my systems every once in a while. I believe this might be caused by some data still carried in caches while the real file system status/data is different. When I see this, I cause some traffic on the file system like running this as the root user depmod -a -e -F /boot/System.map-$(uname -r); ldconfig; sync; sync; sync; sync; rpm --rebuilddb; sync; sync; sync; sync Typically the same zypper command then works without any issue. FWIW, the write-caching is enabled (hdparm -W 1) on all my SATA drives (4x combined in an mdraid10, but I have seen similar zypper failures even on a single disk machine), but running without the cache is unacceptably slow.
How to fix this double packaged files?
Please try if the above command helps in your case, too.
best regards
Thomas
HTH, cheers. l8er manfred
On Saturday 2016-01-30 14:12, Manfred Hollstein wrote:
Hi
I have Tumbleweed 20160121 and just did a "zypper up". It brings up the following error.
8 Dateikonflikte festgestellt:
File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System) [...]
I see this on almost all of my systems every once in a while.
This is absolutely normal, as `zypper up` will not propose packages for deletion -- but this is an action you have to permit for for Tumbleweed, and therefore, you have to use `zypper dup`. It has absolutely nothing, *zilch* to do with caches or the kernel. Your hypothesis of running depmod is utterly flawed.
depmod -a -e -F /boot/System.map-$(uname -r); ldconfig; sync; sync; sync; sync; rpm --rebuilddb; sync; sync; sync; sync
Typically the same zypper command then works without any issue. FWIW, the write-caching is enabled (hdparm -W 1) on all my SATA drives (4x combined in an mdraid10[...] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, 30 Jan 2016, 14:39:27 +0100, Jan Engelhardt wrote:
On Saturday 2016-01-30 14:12, Manfred Hollstein wrote:
Hi
I have Tumbleweed 20160121 and just did a "zypper up". It brings up the following error.
8 Dateikonflikte festgestellt:
File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System) [...]
I see this on almost all of my systems every once in a while.
This is absolutely normal, as `zypper up` will not propose packages for deletion -- but this is an action you have to permit for for Tumbleweed, and therefore, you have to use `zypper dup`.
It has absolutely nothing, *zilch* to do with caches or the kernel. Your hypothesis of running depmod is utterly flawed.
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas? Cheers. l8er manfred
On Sat, 30 Jan 2016, 14:53:04 +0100, Manfred Hollstein wrote:
On Sat, 30 Jan 2016, 14:39:27 +0100, Jan Engelhardt wrote:
On Saturday 2016-01-30 14:12, Manfred Hollstein wrote:
Hi
I have Tumbleweed 20160121 and just did a "zypper up". It brings up the following error.
8 Dateikonflikte festgestellt:
File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System) [...]
I see this on almost all of my systems every once in a while.
This is absolutely normal, as `zypper up` will not propose packages for deletion -- but this is an action you have to permit for for Tumbleweed, and therefore, you have to use `zypper dup`.
It has absolutely nothing, *zilch* to do with caches or the kernel. Your hypothesis of running depmod is utterly flawed.
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
As Wolfgang just pointed out, this might actually caused by some real file conflicts between the KDE4 and KF5 based packages (I'm surprised though, that no other people reported about this issue then), so, if this is the case (here), Jan please take my apologies for this case, but as I wrote, I see this here on a regular basis on four different systems, all with openSUSE 13.1, 13.2, Leap 42 and Tumbleweed installed for multi-booting. So, this is clearly not only happening (here) for TW only ;) Cheers. l8er manfred
Am Samstag, 30. Januar 2016, 16:24:14 schrieb Manfred Hollstein:
As Wolfgang just pointed out, this might actually caused by some real file conflicts between the KDE4 and KF5 based packages
Well, to be exact it's actually *not* a file conflict between the KDE4 and KF5 based packages. But the KDE4 libraries have been moved to a different package (digikam-libs) which has a file conflict with the old separate KDE4 packages that are no longer available (but you still have them installed, and they are not uninstalled automatically).
(I'm surprised though, that no other people reported about this issue then)
Good question. Maybe just nobody noticed yet, or "zypper dup" would indeed automatically remove the old packages because of the file conflicts without complaining. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne sobota 30. ledna 2016 17:53:39 CET, Wolfgang Bauer napsal(a):
Am Samstag, 30. Januar 2016, 16:24:14 schrieb Manfred Hollstein:
As Wolfgang just pointed out, this might actually caused by some real file conflicts between the KDE4 and KF5 based packages
Well, to be exact it's actually *not* a file conflict between the KDE4 and KF5 based packages. But the KDE4 libraries have been moved to a different package (digikam-libs) which has a file conflict with the old separate KDE4 packages that are no longer available (but you still have them installed, and they are not uninstalled automatically).
(I'm surprised though, that no other people reported about this issue then)
Good question. Maybe just nobody noticed yet, or "zypper dup" would indeed automatically remove the old packages because of the file conflicts without complaining.
Zypper dup would remove those as there were no such libs on the system and with luck the sort order removed them first prior the install of the digikam- libs. Cheers Tom -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
30.01.2016 19:59, Tomáš Chvátal пишет:
Maybe just nobody noticed yet, or "zypper dup" would indeed automatically remove the old packages because of the file conflicts without complaining.
Zypper dup would remove those as there were no such libs on the system and
I hope it does not. zypper dup removes packages which have been *manually* added to "to be removed" list. Would you use tool that silently removed packages you installed manually from download RPM? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
30.01.2016 16:53, Manfred Hollstein пишет:
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
Your command line included about dozen of different commands. So saying "depmod and nothing else" is simply wrong unless you can demonstrate that running depmod only does it.
On Sat, 30 Jan 2016, 17:18:55 +0100, Andrei Borzenkov wrote:
30.01.2016 16:53, Manfred Hollstein пишет:
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
Your command line included about dozen of different commands. So saying "depmod and nothing else" is simply wrong unless you can demonstrate that running depmod only does it.
Misunderstanding here! As I tried to indicate, I don't have a clear explanation, I just found out that in such situations, running _some_ commands like "depmod ... sync; sync" *always* solves the problem here. In fact, every once in a while "zypper up" or "zypper dup" shows such behaviour, and I always _thought_ that it would be caused by some inconsistencies between rpm and zypper cache or whatsoever. Running _some_ commands which obviously have an influence on some caches always remove these conflicts, and these commands *never* installed/uninstalled any packages, it was just a matter of massaging the system internal buffers. That's why I said there must be some interference between some layers... Because it's not predictable I never created a bugzilla for this, though... (But, as I wrote before, it's happening on all of my systems, so it's not some HW related problem) Cheers. l8er manfred
On Saturday 2016-01-30 20:59, Manfred Hollstein wrote:
On Sat, 30 Jan 2016, 17:18:55 +0100, Andrei Borzenkov wrote:
30.01.2016 16:53, Manfred Hollstein пишет:
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
Your command line included about dozen of different commands. So saying "depmod and nothing else" is simply wrong unless you can demonstrate that running depmod only does it.
Misunderstanding here! As I tried to indicate, I don't have a clear explanation, I just found out that in such situations, running _some_ commands like "depmod ... sync; sync" *always* solves the problem here.
Well you seem to like banging random commands into the keyboard hoping that something good comes out of it. You probably embezzled a "rm -rf /var/lib/rpm" somewhere. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, 30 Jan 2016, 21:16:40 +0100, Jan Engelhardt wrote:
On Saturday 2016-01-30 20:59, Manfred Hollstein wrote:
On Sat, 30 Jan 2016, 17:18:55 +0100, Andrei Borzenkov wrote:
30.01.2016 16:53, Manfred Hollstein пишет:
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
Your command line included about dozen of different commands. So saying "depmod and nothing else" is simply wrong unless you can demonstrate that running depmod only does it.
Misunderstanding here! As I tried to indicate, I don't have a clear explanation, I just found out that in such situations, running _some_ commands like "depmod ... sync; sync" *always* solves the problem here.
Well you seem to like banging random commands into the keyboard hoping that something good comes out of it. You probably embezzled a "rm -rf /var/lib/rpm" somewhere.
perhaps, yeah, but probably "* ^From: .*jengelh@inai.de.*\n/dev/null" might be useful as well. I'd be much more interested to hear from the OP *if* the problem persists for him ;) ... Cheers. l8er manfred
Am Samstag, 30. Januar 2016, 21:42:39 schrieb Manfred Hollstein:
I'd be much more interested to hear from the OP *if* the problem persists for him ;) ...
Probably yes, because the problem has not been fixed yet (in the actual Tumbleweed repo that is). Btw, there's even a bug report about this: http://bugzilla.opensuse.org/show_bug.cgi?id=963565 That's about the running digikam update for Leap, but the problem is the same. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Wolfgang Bauer
Am Samstag, 30. Januar 2016, 21:42:39 schrieb Manfred Hollstein:
I'd be much more interested to hear from the OP *if* the problem persists for him ;) ...
Probably yes, because the problem has not been fixed yet (in the actual Tumbleweed repo that is).
Btw, there's even a bug report about this: http://bugzilla.opensuse.org/show_bug.cgi?id=963565
That's about the running digikam update for Leap, but the problem is the same.
Appears fixed for tw, 20160126 affected packages, libkdcraw*, libkexiv2*, libkface*, .... no longer exist ???? -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 30. Januar 2016, 19:13:32 schrieb Patrick Shanahan:
Appears fixed for tw, 20160126
Not yet, AFAICS. And we noticed two more problems during the weekend. But everything should be fixed in the devel repo now, and will hopefully be soon in Tumbleweed proper.
affected packages, libkdcraw*, libkexiv2*, libkface*, .... no longer exist ????
Yes, that's the point. Those packages are no longer there, the files have been moved to digikam-libs, because they actually have been part of digikam before. But digikam-libs didn't properly remove those packages, so you get file conflicts (by "zypper up" at least) when they are installed. The libkcraw, libkexiv, and so on, *source* package has been updated to the KF5 versions, the binary packages are called libKF5KDcraw5 (and so on) per the shared library package convention now. Upstream renamed them so that they are co-installable with the KDE4 versions and confirm to the rest of the KF5 libraries. And that's good, because the KF5 versions would just make digikam (and other KDE4 applications) crash on start. I hope that clears it up. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-02-01 14:55, Wolfgang Bauer wrote:
Am Samstag, 30. Januar 2016, 19:13:32 schrieb Patrick Shanahan:
Appears fixed for tw, 20160126
Not yet, AFAICS. And we noticed two more problems during the weekend.
But everything should be fixed in the devel repo now, and will hopefully be soon in Tumbleweed proper.
affected packages, libkdcraw*, libkexiv2*, libkface*, .... no longer exist ????
Yes, that's the point. Those packages are no longer there, the files have been moved to digikam-libs, because they actually have been part of digikam before. But digikam-libs didn't properly remove those packages, so you get file conflicts (by "zypper up" at least) when they are installed.
The libkcraw, libkexiv, and so on, *source* package has been updated to the KF5 versions, the binary packages are called libKF5KDcraw5 (and so on) per the shared library package convention now.
Upstream renamed them so that they are co-installable with the KDE4 versions and confirm to the rest of the KF5 libraries. And that's good, because the KF5 versions would just make digikam (and other KDE4 applications) crash on start. Just did again a "zypper up" and got two conflicts according to the libs you mentiond above: 2 Dateikonflikte festgestellt:
File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-3.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System) File /usr/lib64/libkexiv2.so.11.3.0 from install of digikam-libs-4.14.0-3.1.x86_64(repo-oss) conflicts with file from package libkexiv2-11-15.08.3-2.1.x86_64(@System)
I hope that clears it up. So I wait another couple of days and try again later.
br Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mittwoch, 3. Februar 2016, 14:38:10 schrieb Thomas Wagner:
Just did again a "zypper up" and got two conflicts according to the libs you mentiond above: 2 Dateikonflikte festgestellt:
File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-3.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System)
File /usr/lib64/libkexiv2.so.11.3.0 from install of digikam-libs-4.14.0-3.1.x86_64(repo-oss) conflicts with file from package libkexiv2-11-15.08.3-2.1.x86_64(@System)
Yes, those two Obsoletes were still missing (well, libkexiv2-11 was actually there but incorrectly specified as libkexiv2). They have been added during the weekend, but the new package is not in Tumbleweed yet.
So I wait another couple of days and try again later.
Or just uninstall libkexiv2-11 and libkdcraw23 manually. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-02-03 15:06, Wolfgang Bauer wrote:
Or just uninstall libkexiv2-11 and libkdcraw23 manually. Did that now and upgrade works again with no conflicts. Thanks for helping. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Samstag, 30. Januar 2016, 20:59:26 CET schrieb Manfred Hollstein:
On Sat, 30 Jan 2016, 17:18:55 +0100, Andrei Borzenkov wrote:
30.01.2016 16:53, Manfred Hollstein пишет:
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
Your command line included about dozen of different commands. So saying "depmod and nothing else" is simply wrong unless you can demonstrate that running depmod only does it.
Misunderstanding here! As I tried to indicate, I don't have a clear explanation, I just found out that in such situations, running _some_ commands like "depmod ... sync; sync" *always* solves the problem here.
What you see is more than strange - I'm not surprised that Jan's answer sounds like you told him that you see ghosts ;-) Actually, I'm also wondering why some unrelated commands solve the problem for you. Well, mostly unrelated - rpm --rebuilddb should in theory only put the RPM database in a cleaner shape, but it could also repair something. _If_ something is broken with the cache handling, another surprising part is that only you see it, and only when using zypper and not during normal usage of your systems. Do you have only local disks, or also NFS etc. mounts? When you hit the problem next time, can you please try some other methods? I'd suggest: - wait 5 minutes and try again - drop the cache: echo 1 > /proc/sys/vm/drop_caches (2 and 3 are also possible, see http://linux-mm.org/Drop_Caches) - run 'sync' and then drop the cache - try a different set of commands that cause traffic on the filesystem - especially avoid the rpm --rebuilddb - or _only_ use rpm --rebuilddb - if that helps, it would point to a problem in your RPM database I know this are quite some things to test - try one of them whenever you see the problem on one of your machines ;-)
In fact, every once in a while "zypper up" or "zypper dup" shows such behaviour, and I always _thought_ that it would be caused by some inconsistencies between rpm and zypper cache or whatsoever. Running _some_ commands which obviously have an influence on some caches always remove these conflicts, and these commands *never* installed/uninstalled any packages, it was just a matter of massaging the system internal buffers.
Which filesystem are you using? (The partition containing /var/ is most interesting since the RPM database and the zypper cache are on it.) I remember that I sometimes have strange effects with NFS - it can take some seconds until the client can see a file that was just created on the server. However I've never seen something like that on a local filesystem.
That's why I said there must be some interference between some layers... Because it's not predictable I never created a bugzilla for this, though... (But, as I wrote before, it's happening on all of my systems, so it's not some HW related problem)
What do your systems have in common? Ideally name something that most openSUSE users won't have or use ;-) Regards, Christian Boltz -- Unterdessen hat sich die Filmindustrie was ganz, ganz tolles ausgedacht: Ultraviolet (Man hätte einen beknackteren Namen finden können, aber das wäre Arbeit gewesen) ist DRM-as-a-service, 100% Buzzword Compliant und in der Cloud. [http://blog.koehntopp.de/archives/3068-Diesmal-also-eBooks-und-Filme.html] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Moin, On Sun, 31 Jan 2016, 02:07:32 +0100, Christian Boltz wrote:
Hello,
Am Samstag, 30. Januar 2016, 20:59:26 CET schrieb Manfred Hollstein:
On Sat, 30 Jan 2016, 17:18:55 +0100, Andrei Borzenkov wrote:
30.01.2016 16:53, Manfred Hollstein пишет:
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
Your command line included about dozen of different commands. So saying "depmod and nothing else" is simply wrong unless you can demonstrate that running depmod only does it.
Misunderstanding here! As I tried to indicate, I don't have a clear explanation, I just found out that in such situations, running _some_ commands like "depmod ... sync; sync" *always* solves the problem here.
What you see is more than strange - I'm not surprised that Jan's answer sounds like you told him that you see ghosts ;-)
Yeah, that's why I never thought to open a bug report for this.
Actually, I'm also wondering why some unrelated commands solve the problem for you. Well, mostly unrelated - rpm --rebuilddb should in theory only put the RPM database in a cleaner shape, but it could also repair something.
The "depmod ...; rpm --rebuilddb; ..." sequence actually is a result from finding some arbitrary command that does something sensible and creates enough noise in the system so that "zypper ..." succeeds afterwards. FWIW, "rpm --rebuilddb" does not need to be executed to achieve the same effect.
_If_ something is broken with the cache handling, another surprising part is that only you see it, and only when using zypper and not during normal usage of your systems.
Do you have only local disks, or also NFS etc. mounts?
/ xfs, /boot ext2, /var xfs
When you hit the problem next time, can you please try some other methods? I'd suggest: - wait 5 minutes and try again - drop the cache: echo 1 > /proc/sys/vm/drop_caches (2 and 3 are also possible, see http://linux-mm.org/Drop_Caches) - run 'sync' and then drop the cache - try a different set of commands that cause traffic on the filesystem - especially avoid the rpm --rebuilddb - or _only_ use rpm --rebuilddb - if that helps, it would point to a problem in your RPM database
I know this are quite some things to test - try one of them whenever you see the problem on one of your machines ;-)
Did most of it already, but again, rpm --rebuilddb is not _required_.
In fact, every once in a while "zypper up" or "zypper dup" shows such behaviour, and I always _thought_ that it would be caused by some inconsistencies between rpm and zypper cache or whatsoever. Running _some_ commands which obviously have an influence on some caches always remove these conflicts, and these commands *never* installed/uninstalled any packages, it was just a matter of massaging the system internal buffers.
Which filesystem are you using? (The partition containing /var/ is most interesting since the RPM database and the zypper cache are on it.)
See above.
I remember that I sometimes have strange effects with NFS - it can take some seconds until the client can see a file that was just created on the server. However I've never seen something like that on a local filesystem.
Parts are automounted via NFSv4, but they are out of package scope, so no package installs stuff on the NFS mounted directories.
That's why I said there must be some interference between some layers... Because it's not predictable I never created a bugzilla for this, though... (But, as I wrote before, it's happening on all of my systems, so it's not some HW related problem)
What do your systems have in common? Ideally name something that most openSUSE users won't have or use ;-)
The most different thing, I believe, is the mdraid10 setup with LVM on top. I'm not sure how many people are using such a setup, but I may be wrong. However, the rest is probably quite common, so I actually hoped to see someone else seeing the same issues, when Thomas sent his e-mail ;)
Regards,
Christian Boltz
Cheers. l8er manfred
30.01.2016 22:59, Manfred Hollstein пишет:
On Sat, 30 Jan 2016, 17:18:55 +0100, Andrei Borzenkov wrote:
30.01.2016 16:53, Manfred Hollstein пишет:
Of course, you know better (as usual), but *why* does running the "depmod ..." command and _nothing else_ solve the issue then? Any constructive ideas?
Your command line included about dozen of different commands. So saying "depmod and nothing else" is simply wrong unless you can demonstrate that running depmod only does it.
Misunderstanding here! As I tried to indicate, I don't have a clear explanation, I just found out that in such situations, running _some_ commands like "depmod ... sync; sync" *always* solves the problem here.
If anything I would bet on "rpm --rebuilddb". This was the only one related to RPM in your list.
Am Sonntag, 31. Januar 2016, 08:46:18 schrieb Andrei Borzenkov:
If anything I would bet on "rpm --rebuilddb". This was the only one related to RPM in your list.
Yeah. Or maybe some update inbetween that fixed possible dependency problems... ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 30. Januar 2016, 13:20:18 schrieb Thomas Wagner:
I have Tumbleweed 20160121 and just did a "zypper up". It brings up the following error.
The main reason is that those libraries are now KF5 based. But digikam (still a KDE4 application) needs them too, so they have been added there, as a subpackage digikam-libs. Unfortunately that package doesn't properly obsolete the older separate packages, so you get those file conflicts. This has been fixed 4 days ago, the fix has been accepted to Factory 4 hours ago so there should be no conflict in the next snapshot. https://build.opensuse.org/request/show/356746 Although, AFAICS the Obsoletes for libkdcraw23 is still missing... :-(
How to fix this double packaged files?
Uninstall those libraries manually. E.g.: zypper rm libkipi11 libksane0 libmediawiki1 libkface3 libkexiv2 libkdcraw23 (zypper should automatically install digikam-plugins then I think) You could also just ignore those file conflicts for now, but removing the packages is probably safer. Or wait for the next snapshot. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
Christian Boltz -
Jan Engelhardt -
Manfred Hollstein -
Patrick Shanahan -
Thomas Wagner -
Tomáš Chvátal -
Wolfgang Bauer