Bugzilla – Bug 966618
Problem with bbswitch bumblebee and bbswitch default @System
Last modified: 2018-06-26 14:19:23 UTC
I got this every zypper dup. How to fix this? Checking for file conflicts: ................................................[error] Detected 1 file conflict: File /lib/modules/4.4.0-3-default/updates/bbswitch.ko from install of bbswitch-kmp-default-0.8_k4.4.0_3-24.28.x86_64 (Bumblebee project (openSUSE_Tumbleweed)) conflicts with file from package bbswitch-kmp-default-0.8_k4.4.0_3-24.26.x86_64 (@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): yes
Don't think this is critical. Please do not raise the severity trying to draw more attention to your problem. bbswitch-kmp-default-0.8_k4.4.0_3-24.28.x86_64 is really the version of the 'Bumblebee project Factory' package. Not sure why this is considered a 'System' package. The package version in oepnSUSE:Factory is bbswitch-kmp-default-0.8_k4.4.0_3-5.32.x86_64.rpm. This seems to be a zypper issue. Reassigning to YaST team. In the mean time, please provide the output of 'zypper lr -d'.
This is a packaging issue. Already installed on the system: bbswitch-kmp-default-0.8_k4.4.0_3-24.26.x86_64 (@System just indicates that the installed version is not available in any known repo anymore). To be installed: bbswitch-kmp-default-0.8_k4.4.0_3-24.28.x86_64 from Bumblebee project Obviously the bbswitch-kmp is tagged as 'multiversion' install, but the different versions share common files (/lib/modules/4.4.0-3-default/updates/bbswitch.ko) with changing content. This causes a file conflict as install of one version damages the other. ============= Most common problem is, that you want multiple bbswitch-kmps (one per installed kernel version), but actually want to be able to update each kernel specific kmp to a new release. This can not be achieved by making the bbswitch-kmp as a whoole 'multiversion'. You actually need no multiversion at al. You need the kernel version being part of the kmp name ('bbswitch-kmp-4.4.0-3-default' i.e. 'bbswitch-kmp for kernel 4.4.0-3-default'). This way you have multiple kernel specific bbswitch-kmp-<KERNELTAG> packages. And each package can be independently updated to a new release (a new /lib/modules/<KERNELTAG>/updates/bbswitch.ko) without file conflicts.
Reassigned to maintainer.
This is mostly problem of the multiversioning in kernel. We discussed it here in the office. Possible solution: Each of the kmp's would Provide and Obsolete some symbol that would be same as the kernel they built against. Thus we would remove package that is built against same kernel. Otherwise we would just co-install without problem.
Reassigning to maintainer of bbswitch of factory. Adding Michal Suchanek to Cc. He took over some Kernel tasks of Michal Marek. Not sure if this belongs to his area though.
This is on michal to tweak :) Basically the kmp macros need to do this for all packages.
IS this fixed or is there something else needed?
.