[opensuse] [opensuse-factory] Conflicts to update R-core-libs
Hi, When I try to update R-core-libs on openSUSE TW, zypper finds the following conflicts: Checking for file conflicts: ...............................................................................................................................................................................[error] Detected 3 file conflicts: File /usr/lib64/R/lib/libR.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) File /usr/lib64/R/lib/libRblas.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) File /usr/lib64/R/lib/libRlapack.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) ============ So these are basically conflicts between the updated package and the installed package. I am able to continue the update but this should not be regarded as conflict. I am able to update other packages without conflict. Could this be due to some misconfiguration on my system or a packaging error? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, 30 March 2016 16:29:54 EEST Edwin Aponte wrote:
Hi,
Hi,
When I try to update R-core-libs on openSUSE TW, zypper finds the following conflicts:
Checking for file conflicts: ...................................................................... ...................................................................... ...................................[error] Detected 3 file conflicts:
File /usr/lib64/R/lib/libR.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System)
File /usr/lib64/R/lib/libRblas.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System)
File /usr/lib64/R/lib/libRlapack.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System)
============
So these are basically conflicts between the updated package and the installed package. I am able to continue the update but this should not be regarded as conflict. I am able to update other packages without conflict.
Could this be due to some misconfiguration on my system or a packaging error?
I had something similar occur here recently. Did you use the shell (zypper sh)? Often it has weird problems, perhaps it is related. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/30/2016 10:29 AM, Edwin Aponte wrote:
Hi,
When I try to update R-core-libs on openSUSE TW, zypper finds the following conflicts:
Yes, I ran into that. I noticed the "(@System)" for "R-base-libs". That indicates that it is no longer in the repos. So I aborted "zypper dup", and started Yast software management. Checking orphaned packages, I saw "R-base-libs" and uninstalled it. Yast wanted to install a bunch of other stuff (probably to handle the dependencies that "R-base-libs" was satisfying). After that, I repeated the "zypper dup" and there were no conflicts. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
There was a fairly significant repackaging of R-base which split it
into a ton of sub-packages and I wonder if you're seeing the after
effect of this.
--
Later,
Darin
On Thu, Mar 31, 2016 at 11:39 AM, Neil Rickert
On 03/30/2016 10:29 AM, Edwin Aponte wrote:
Hi,
When I try to update R-core-libs on openSUSE TW, zypper finds the following conflicts:
Yes, I ran into that.
I noticed the "(@System)" for "R-base-libs". That indicates that it is no longer in the repos. So I aborted "zypper dup", and started Yast software management. Checking orphaned packages, I saw "R-base-libs" and uninstalled it. Yast wanted to install a bunch of other stuff (probably to handle the dependencies that "R-base-libs" was satisfying). After that, I repeated the "zypper dup" and there were no conflicts.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I noticed the "(@System)" for "R-base-libs". That indicates that it is no longer in the repos. So I aborted "zypper dup", and started Yast software management. Checking orphaned packages, I saw "R-base-libs" and uninstalled it. Yast wanted to install a bunch of other stuff (probably to handle the dependencies that "R-base-libs" was satisfying). After that, I repeated the "zypper dup" and there were no conflicts.
Thank you I removed the orphaned package and did dup again without conflicts. I checked orphan packages with zypper pa --orphan. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
auxsvr -
Darin Perusich -
Edwin Aponte -
Neil Rickert