Temporary fix Apparmor in OpenMandriva (sudo dnf in apparmor)

Support
,
1

Sorry I misbehaved last time. The solution is :

sudo dnf rm iputils

and

sudo dnf in apparmor

I suspect and chatgpt that Because apparmor is trying to install the same file

(/etc/apparmor.d/bin.ping)

I don’t really see any other way to avoid this error and I don’t know much about why it happens.

I hope the OpenMandriva team will fix this bug in the next version of Rock.

:white_check_mark: I have Searched the forum for my issue and found nothing related or helpful
:white_check_mark: I have checked the Resources category (Resources Index)
:white_check_mark: I have reviewed the Wiki for relevant information
:white_check_mark: I have read the the Release Notes and Errata

OpenMandriva Lx version:
OpenMandriva Lx release 6.0 (Vanadium) Rock for x86_64

Desktop environment (KDE, LXQT…):
KDE Plasma Version 6.3.4

Description of the issue (screenshots if relevant):

Package                 Architecture          Version                 Repository                        Size

Installing:
apparmor                x86_64                4.0.3-2                 rock-x86_64-extra                772 k

Transaction Summary

Install  1 Package

Total download size: 772 k

Installed size: 2.5 M
Is this ok \[y/N\]: y
Downloading Packages:
apparmor-4.0.3-2-omv2490.x86_64.rpm                                           343 kB/s | 772 kB     00:02

Total                                                                         342 kB/s | 772 kB     00:02
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘dnf clean packages’.
Error: Transaction test error:
file /etc/apparmor.d/bin.ping from install of apparmor-4.0.3-2.x86_64 conflicts with file from package iputils-20221126-1.x86_64
2

A hint:

Resources Index

[Forum] How to post code as code

Edit: This is courtesy to everyone else and an asset to problem solving, it is a lot easier to read code posted as code.

3

I edited the content.
@FernPolskaOriginal next time(s) please use the preformatted text for code, thank you.

4

I don’t see the “fix” or the “solution” when you say you don’t know how to avoid the error. It looks like a packaging bug. I would also suggest you don’t use AI to solve problems with our distro. They aren’t going to train their AI to bother with it.