You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Installed the latest Mariner OS available in Mariner 2.0 x86_64 ISO.
This comes with Linux 5.15.145.2-1.cm2 kernel by default.
For my task, I require "kernel-mos-drivers-gpu" driver to be installed for fetching GPU driver.
However, there seems conflict with the default kernel which is resulting into rpm installation failure.
To Reproduce
Steps to reproduce the behavior:
root@dut [ ~ ]# tdnf install -y kernel-mos kernel-mos-drivers-gpu
Loaded plugin: tdnfrepogpgcheck
Installing:
kernel-mos-drivers-gpu x86_64 5.15.145.2-1.cm2 mariner-official-base 4.87M 4.88M
kernel-mos x86_64 5.15.145.2-1.cm2 mariner-official-base 41.30M 35.02M
Total installed size: 46.17M
Total download size: 39.90M
kernel-mos-drivers-gpu 5121424 100%
kernel-mos 36721097 100%
Testing transaction
Found 1077 problems
file /boot/.vmlinuz-5.15.145.2-1.cm2.hmac from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /boot/System.map-5.15.145.2-1.cm2 from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /boot/config-5.15.145.2-1.cm2 from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /boot/linux-5.15.145.2-1.cm2.cfg from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /boot/vmlinuz-5.15.145.2-1.cm2 from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /lib/modules/5.15.145.2-1.cm2/.vmlinuz.hmac from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
...
...
file /lib/modules/5.15.145.2-1.cm2/modules.devname from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /lib/modules/5.15.145.2-1.cm2/modules.order from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /lib/modules/5.15.145.2-1.cm2/modules.symbols from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
file /lib/modules/5.15.145.2-1.cm2/modules.symbols.bin from install of kernel-mos-5.15.145.2-1.cm2.x86_64 conflicts with file from package kernel-5.15.145.2-1.cm2.x86_64
Error(1525) : rpm transaction failed
Expected behavior
"kernel-mos-drivers-gpu" with it's supported "kernel-mos" package installation should be successful without any errors.
Please fix this issue at the earliest Or provide a workaround at the minimum to proceed with the activity.
Possibly having a "force" option to reinstall the existing packages in case of common files/packages would be done.
The text was updated successfully, but these errors were encountered:
Before running the command do a test with sudo rpm -ivh --force --test kernel-mos-5.15.145.2-1.cm2.x86_64.rpm kernel-mos-drivers-gpu-5.15.145.2-1.cm2.x86_64.rpm
Thanks @zcobol for the suggestion. That helps to proceed.
May I please know, if there is any plan to fix this issue from Microsoft to allow seamless installation of these packages without worrying about namespace collisions ?
Describe the bug
Installed the latest Mariner OS available in Mariner 2.0 x86_64 ISO.
This comes with Linux 5.15.145.2-1.cm2 kernel by default.
For my task, I require "kernel-mos-drivers-gpu" driver to be installed for fetching GPU driver.
However, there seems conflict with the default kernel which is resulting into rpm installation failure.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
"kernel-mos-drivers-gpu" with it's supported "kernel-mos" package installation should be successful without any errors.
Please fix this issue at the earliest Or provide a workaround at the minimum to proceed with the activity.
Possibly having a "force" option to reinstall the existing packages in case of common files/packages would be done.
The text was updated successfully, but these errors were encountered: