On AIX 7.2 had installed dnf system through https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/dnf_aixtoolbox.sh I need install rust but, when i try do it i got:

bash-5.2# dnf install rust
Last metadata expiration check: 1 day, 4:00:30 ago on Tue Jul 22 04:31:45 EDT 2025.
Error: 
 Problem: package rust-1.86.0-250527.ppc requires rust1.86 >= 1.86.0, but none of the providers can be installed
  - cannot install the best candidate for the job
  - nothing provides libunwind.a(libunwind.so.1) needed by rust1.86-1.86.0-250516.ppc
  - nothing provides libc++.a(libc++.so.1) needed by rust1.86-1.86.0-250516.ppc
  - nothing provides libc++abi.a(libc++abi.so.1) needed by rust1.86-1.86.0-250516.ppc
  - nothing provides libunwind.a(libunwind.so.1) needed by rust1.86-1.86.0-250527.ppc
  - nothing provides libc++.a(libc++.so.1) needed by rust1.86-1.86.0-250527.ppc
  - nothing provides libc++abi.a(libc++abi.so.1) needed by rust1.86-1.86.0-250527.ppc
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Thanks in advance for any help

I need to install few RPM files within a TeradataToolsAndUtilitiesBase__linux_x8664.17.00.31.00.tar.gz from URL below and the file name is "TTU 17.10.11.00 Linux - Base" https://downloads.teradata.com/download/tools/teradata-tools-and-utilities-linux-installation-package-0 how can we do install by using command line by using either yum or rpm.

I have a software which needs Berkeley DB 4.5 or above. But in my CentOS 5.11 x86_64 Server I have: * Package db4-4.3.29-10.el5_5.2.x86_64 already installed and latest version * Package db4-4.3.29-10.el5_5.2.i386 already installed and latest version How can I upgrade these rpm to a newer version? I tried to upgrade using Centos 6.6 rpm in this way: rpm -Uvh ftp://195.220.108.108/linux/centos/6.6/os/x86_64/Packages/db4-4.7.25-18.el6_4.i686.rpm but I receive this error: Retrieving ftp://195.220.108.108/linux/centos/6.6/os/x86_64/Packages/db4-4.7.25-18.el6_4.i686.rpm warning: /var/tmp/rpm-xfer.IKWqHE: Header V3 RSA/SHA1 signature: NOKEY, key ID c105b9de error: Failed dependencies: rpmlib(FileDigests) = 4.4.0 conflicts with pam-0.99.6.2-12.el5.i386 db4 >= 4.4.0 conflicts with pam-0.99.6.2-12.el5.x86_64 libdb-4.3.so is needed by (installed) subversion-1.6.11-12.el5_10.i386 libdb-4.3.so is needed by (installed) pam_ccreds-3-5.i386 libdb-4.3.so is needed by (installed) apr-util-1.2.7-11.el5_5.2.i386 libdb-4.3.so is needed by (installed) db4-devel-4.3.29-10.el5_5.2.i386 libdb_cxx-4.3.so is needed by (installed) db4-devel-4.3.29-10.el5_5.2.i386 I also tried to compile from source db-4.5.20.tar.gz. I compiled it with no problem, however my software is still seeing the Berkley DB preinstalled in rpm package db4-4.3.29. Any help please ?

I'm trying to install libstdc++-4.4.4-13.el6.i686.rpm but it says newer version of this package is already installed. [root@isoft Downloads]# rpm -ivh libstdc++-4.4.4-13.el6.i686.rpm warning: libstdc++-4.4.4-13.el6.i686.rpm: Header V4 DSA/SHA1 Signature, key ID 192a7d7d: NOKEY Preparing... ########################################### [100%] package libstdc++-4.4.7-17.el6.x86_64 (which is newer than libstdc++-4.4.4-13.el6.i686) is already installed* Even i cannot uninstall libstdc++-4.4.7-17.el6.x86_64. [root@isoft yum.repos.d]# yum install libstdc++-4.4.6-4.el6.i686 Loaded plugins: refresh-packagekit, security, ulninfo Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package libstdc++.i686 0:4.4.6-4.el6 will be installed --> Finished Dependency Resolution Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for libstdc++ which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libstdc++ of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude libstdc++.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of libstdc++ installed, but yum can only see an upgrade for one of those arcitectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of libstdc++ installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: libstdc++-4.4.6-4.el6.i686 != libstdc++-4.4.7-17.el6.x86_64 any one has thoughts to resolve this error.

My experience with CentOS and RPM's is limited so I might be missing something obvious, but I can't seem to figure this out... I'm trying to install Sphinx into CentOS 6 in a Docker image using the instructions here: http://sphinxsearch.com/docs/current/installing-redhat.html (though, I'm trying to install from the source RPM instead of the binary) I run docker run -i -t centos:centos6 bash to get a CentOS image running and then here's what I get when trying to run the commands (slightly different than the instructions to give more information and skip prompts): [root@db60006ae258 /]# yum -y install postgresql-libs unixODBC Loaded plugins: fastestmirror Setting up Install Process base | 3.7 kB 00:00 base/primary_db | 4.6 MB 00:37 extras | 3.4 kB 00:00 extras/primary_db | 34 kB 00:00 updates | 3.4 kB 00:00 updates/primary_db | 3.3 MB 00:08 Resolving Dependencies --> Running transaction check ---> Package postgresql-libs.x86_64 0:8.4.20-4.el6_7 will be installed ---> Package unixODBC.x86_64 0:2.2.14-14.el6 will be installed --> Processing Dependency: libltdl.so.7()(64bit) for package: unixODBC-2.2.14-14.el6.x86_64 --> Running transaction check ---> Package libtool-ltdl.x86_64 0:2.2.6-15.5.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ========================================================================================================================================== Package Arch Version Repository Size ========================================================================================================================================== Installing: postgresql-libs x86_64 8.4.20-4.el6_7 updates 202 k unixODBC x86_64 2.2.14-14.el6 base 378 k Installing for dependencies: libtool-ltdl x86_64 2.2.6-15.5.el6 base 44 k Transaction Summary ========================================================================================================================================== Install 3 Package(s) Total download size: 624 k Installed size: 1.8 M Downloading Packages: (1/3): libtool-ltdl-2.2.6-15.5.el6.x86_64.rpm | 44 kB 00:00 (2/3): postgresql-libs-8.4.20-4.el6_7.x86_64.rpm | 202 kB 00:00 (3/3): unixODBC-2.2.14-14.el6.x86_64.rpm | 378 kB 00:01 ------------------------------------------------------------------------------------------------------------------------------------------ Total 234 kB/s | 624 kB 00:02 warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c105b9de: NOKEY Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 Importing GPG key 0xC105B9DE: Userid : CentOS-6 Key (CentOS 6 Official Signing Key) Package: centos-release-6-7.el6.centos.12.3.x86_64 (installed) From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : libtool-ltdl-2.2.6-15.5.el6.x86_64 1/3 Installing : unixODBC-2.2.14-14.el6.x86_64 2/3 Installing : postgresql-libs-8.4.20-4.el6_7.x86_64 3/3 Verifying : postgresql-libs-8.4.20-4.el6_7.x86_64 1/3 Verifying : unixODBC-2.2.14-14.el6.x86_64 2/3 Verifying : libtool-ltdl-2.2.6-15.5.el6.x86_64 3/3 Installed: postgresql-libs.x86_64 0:8.4.20-4.el6_7 unixODBC.x86_64 0:2.2.14-14.el6 Dependency Installed: libtool-ltdl.x86_64 0:2.2.6-15.5.el6 Complete! [root@db60006ae258 /]# rpm -Uhvv http://sphinxsearch.com/files/sphinx-2.2.10-1.rhel6.src.rpm Retrieving http://sphinxsearch.com/files/sphinx-2.2.10-1.rhel6.src.rpm D: ============== /var/tmp/rpm-tmp.Knfx7x D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key D: loading keyring from rpmdb D: opening db environment /var/lib/rpm cdb:mpool:joinenv D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 D: locked db index /var/lib/rpm/Packages D: opening db index /var/lib/rpm/Name rdonly mode=0x0 D: read h# 155 Header sanity check: OK D: added key gpg-pubkey-c105b9de-4e0fd3a3 to keyring D: Using legacy gpg-pubkey(s) from rpmdb D: Expected size: 4201741 = lead(96)+sigs(180)+pad(4)+data(4201461) D: Actual size: 4201741 D: /var/tmp/rpm-tmp.Knfx7x: Header SHA1 digest: OK (f86024cbd050d0758ddb1aa0fc73c246deeb2f90) D: added source package D: found 1 source and 0 binary packages D: Expected size: 4201741 = lead(96)+sigs(180)+pad(4)+data(4201461) D: Actual size: 4201741 D: InstallSourcePackage at: psm.c:244: Header SHA1 digest: OK (f86024cbd050d0758ddb1aa0fc73c246deeb2f90) D: created directory(s) /root/rpmbuild mode 0755 D: created directory(s) /root/rpmbuild/SOURCES mode 0755 D: created directory(s) /root/rpmbuild/SPECS mode 0755 1:sphinx D: ========== Directories not explicitly included in package: D: 0 /root/rpmbuild/SOURCES/ D: 1 /root/rpmbuild/SPECS/ D: ========== warning: user builder does not exist - using root warning: group builder does not exist - using root D: fini 100644 1 ( 0, 0) 288 /root/rpmbuild/SOURCES/config.patch;56a3c57f unknown warning: user builder does not exist - using root warning: group builder does not exist - using root D: fini 100664 1 ( 0, 0) 129584 /root/rpmbuild/SOURCES/libstemmer_c.tgz;56a3c57f unknown warning: user builder does not exist - using root warning: group builder does not exist - using root D: fini 100664 1 ( 0, 0) 1064388 /root/rpmbuild/SOURCES/re2.tar.gz;56a3c57f unknown warning: user builder does not exist - using root warning: group builder does not exist - using root ########################################### [100%] D: fini 100644 1 ( 0, 0) 3109250 /root/rpmbuild/SOURCES/sphinx-2.2.10-release.tar.gz;56a3c57f unknown warning: user builder does not exist - using root warning: group builder does not exist - using root D: fini 100644 1 ( 0, 0) 2048 /root/rpmbuild/SOURCES/sphinx.init;56a3c57f unknown warning: user builder does not exist - using root warning: group builder does not exist - using root D: fini 100644 1 ( 0, 0) 9647 /root/rpmbuild/SPECS/sphinx_rel22.spec;56a3c57f unknown GZDIO: 527 reads, 4316100 total bytes in 0.021979 secs D: closed db index /var/lib/rpm/Name D: closed db index /var/lib/rpm/Packages D: closed db environment /var/lib/rpm [root@db60006ae258 /]# service searchd start bash: service: command not found [root@db60006ae258 /]# find / -name "searchd*" [root@db60006ae258 /]#

I'd like to build an RPM from https://src.fedoraproject.org/rpms/Thunar with some changes in the source code. Do they use a docker/podman image to build it? I couldn't find information about it. I'd like to build the RPM for RHEL 10 since it isn't supported yet.

I am working on creating deb/rpm packages for a little project of mine . I have already created the packages for a few rpm-based and deb-based distros. In deb distros one python file is being setup in /usr/lib/python3/dist-packages/. In rpm-based distros, I have to first detect the version of python being used when building and then I can set it up at the right directory. So, for rockylinux 9, I use /usr/lib64/python3.9/site-packages, for fedora 42 I use /usr/lib64/python3.13/site-packages. It works! However, I just realized that because on rpm distros the file is located in a python-version-dependent directory established when I am packaging it, if on the box it will run python is updated to a newer version from the one I used by default on that distro during packaging-time, it will break. Is there a more python-minor-version independent directory that could be used in rpm-based distros? I don't want to add the file in multiple places just so that it is available in all the python versions that could be installed from distro packages.

I have an application that I am packaging as an RPM and installing on CentOS 7. When I install the RPM I want it to install some compiled binaries as well as some Python modules with their dependencies. My Python modules require a newer version of Python than is provided by CentOS, so I will be installing the modules in a Python altinstall under /usr/local/lib/python2.7/site-packages. This means I can't use CentOS-provided RPMs since they install under /usr/lib. I can easily install the modules under /usr/local/lib using pip. Is there a way to package my application such that: * I can install my application from an RPM. * My Python modules get installed under /usr/local/lib when the application is installed. * Any Python dependencies also get installed. * I avoid maintaining RPM packages for the Python dependencies. Is there a convention for this kind of thing? Or are there maybe some examples? I didn't see anything directly relevant in Fedora's Python Packaging documentation . The options I have considered are: 1. Bundle my application, Python modules, and all Python dependencies into one RPM. I don't like this option because I would not be able to update individual dependencies on the client system without upgrading my entire application to a new version. 2. Create individual RPMs for my application, my Python modules, and third-party dependencies. I don't like this option because I would have to maintain RPMs for every single third-party module in my dependency tree. 3. Call pip from within my RPM. I don't like this option because RPM would not be able to track the changes that pip makes, and I would not be able to determine whether I can safely remove third-party Python modules when removing the RPM.

Since a couple of days, I'm unable to retrieve repositories data with Yum, in my CentOS 6.5 server. I did yum clean all a dozen of times, it emptied all but didn't solved the problem. I tried to retrieve things by restricting to the single base repo : [base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 yum --verbose update results in : Loading "fastestmirror" plugin Loading "priorities" plugin Config time: 0.010 Yum Version: 3.2.29 Setting up Package Sacks Determining fastest mirrors Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was 14: PYCURL ERROR 22 - "The requested URL returned error: 403 Forbidden" Error: Cannot find a valid baseurl for repo: base And when I configure a baseurl instead of a mirrorlist, I get this : Loading "fastestmirror" plugin Loading "priorities" plugin Config time: 0.010 Yum Version: 3.2.29 Setting up Package Sacks Determining fastest mirrors http://mirror.centos.org/centos/6/os/x86_64/repodata/repomd.xml : [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again The server pings mirror.centos.org and I can reach without any problem the mirrorlist and the repomd.xml in a web browser. Disabling the plugins changed nothing. The mirrorlist gives a 403 error and a baseurl 404... rpm -q --verify -f /etc/yum.repos.d/* results in : S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo S.5....T. c /etc/issue .......T. c /etc/yum.repos.d/CentOS-Base.repo .......T. c /etc/yum.repos.d/CentOS-Debuginfo.repo .......T. c /etc/yum.repos.d/CentOS-Media.repo .......T. c /etc/yum.repos.d/CentOS-Vault.repo .......T. c /etc/yum.repos.d/epel-testing.repo .......T. c /etc/yum.repos.d/epel.repo .......T. c /etc/yum.repos.d/epel-testing.repo .......T. c /etc/yum.repos.d/epel.repo le fichier /etc/yum.repos.d/isv:ownCloud:community.repo n'appartient à aucun paquetage .......T. c /etc/yum.repos.d/jpackage.repo le fichier /etc/yum.repos.d/jpackage.repo.rpmsave n'appartient à aucun paquetage « n'appartient à aucun paquetage » means « doesn't belong to any package », in french... Those problems occur with whatever repo I enable/disable.

Simple question, but no resources found about this. Is there any way to install only a PostgreSQL client, the terminal-based one, psql, on a CentOS7 system, without installing the complete PostgreSQL server? There is no dedicated postgresql-client or postgresql94-client or anything similar on the repositories.

I am trying to install libxml2, but my system complains about dependencies. The dependent packages exist on system. The ultimate goal is to install xml_grep2, I have been trying various methods (cpan, etc). [root@testserver xml]# rpm -ivh libxml2-2.9.0-1.x86_64.rpm warning: libxml2-2.9.0-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID de95bc1f error: Failed dependencies: libc.so.6(GLIBC_2.14)(64bit) is needed by libxml2-2.9.0-1.x86_64 [root@testserver xml]# yum install glibc Package glibc-2.5-107.x86_64 already installed and latest version Package glibc-2.5-107.i686 already installed and latest version [root@testserver xml]# find / -name libc.so.6 /lib64/libc.so.6 /lib/libc.so.6 /lib/i686/nosegneg/libc.so.6

I was using centOS8 and try to execute yum install -y gcc tcl and failed. The error shows it has some problem with signature check or something at rpm install process.The console log is like error: /var/cache/dnf/base-82351eca59c28538/packages/cpp-8.5.0-21.el8.x86_64.rpm: signature hdr data: BAD, no. of bytes(9088) out of range and Error: GPG check FAILED. I tried to upgrade my rpm installer and get same problem, and yum update didn't work either. I tried to use --nogpgcheck, it still didn't work.

I have to implement two yum repos, **x** and **y** which contains same packages with different versions. If a user do: 1. yum install x - should install the latest packages of one branch 2. yum install y - should install the stable version from different branch When I execute yum install x, installs the latest version package from **x** repository, but when I execute, yum install y, doesn't work as expected though I have created meta packages. I have experimented with yum plugins protect, priority. Both plugins works as expected but removes the other package versions. I am able to execute yum install y, but unable to execute yum install x afterwards. I should be able to execute both repositories in one server. Could you please suggest me, how to achieve this in yum? I have to implement it in server.

I am trying to make chef-11.16.4-1.el6.x86_64.rpm available to our servers via a local yum repo that we've built. it is not available in RHEL Repos, so i had to manually download and save it in our repo. so here is what i did on yum repo server: 1. cd /packages/rhel65-base/; wget https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.16.4-1.el6.x86_64.rpm 2. createrepo /packages/rhel65-base/ Yum client was able to see the new package available: [user1@testserver01 ~]$ yum list chef Loaded plugins: amazon-id, rhui-lb, security Installed Packages chef.x86_64 11.16.0-1.el6 installed Available Packages chef.x86_64 11.16.4-1.el6 local-rhel65-base But when trying to install the latest package of chef, it ends with below error: warning: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, key ID 83ef826a: NOKEY Public key for chef-11.16.4-1.el6.x86_64.rpm is not installed Assuming that the chef rpm has not been signed, i tried to sign it myself by following https://iuscommunity.org/pages/CreatingAGPGKeyandSigningRPMs.html but still couldn't get it working. Some useful info i can find in Chef's website is the SHA1 checksum value of this package. Anyone got ideas/suggestions to solve this issue? thanks!

I've got a question about yum. When I upgrade my system using dnf, it downloads packages from the Web. Can I set dnf configuration so that I could save rpm files for later use, with the same system but without Web connection?

I see that it is an error that happend here and there for some packages, but I didnt find any solution working for me. Everything broke down trying to install Jupyter by dnf install python2-qtconsole python2-jupyter-core, when I found that python2-urllib3 was giving an error trying to install. Now whenever I do: dnf install python2-urllib3, I get: Dependencies resolved. ======================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================== Installing: python2-urllib3 noarch 1.22-3.fc27 updates 178 k Transaction Summary ======================================================================================================================================== Install 1 Package Total download size: 178 k Installed size: 678 k Is this ok [y/N]: y Downloading Packages: python2-urllib3-1.22-3.fc27.noarch.rpm 78 kB/s | 178 kB 00:02 ---------------------------------------------------------------------------------------------------------------------------------------- Total 53 kB/s | 178 kB 00:03 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : python2-urllib3-1.22-3.fc27.noarch 1/1 Error unpacking rpm package python2-urllib3-1.22-3.fc27.noarch Error unpacking rpm package python2-urllib3-1.22-3.fc27.noarch error: unpacking of archive failed on file /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: cpio: File from package already exists as a directory in system python2-urllib3-1.22-3.fc27.noarch was supposed to be installed but is not! Verifying : python2-urllib3-1.22-3.fc27.noarch 1/1 Failed: python2-urllib3.noarch 1.22-3.fc27 Error: Transaction failed I tried all these dnf clean all yum clean all && rpm --rebuilddb package-cleanup --problems rpm -e python3-urllib3-1.22-3.fc27.noarch --nodeps rpm -i python2-urllib3-1.22-3.fc27.noarch.rpm ... and I'm losing ideas fast ...

I find myself unable to convert a .deb package to .rpm to install it on fedora. I am not able to download the equivalent rpm file, so conversion is my only way out. I get this error after using the prompt alien -r package.deb as su. Package build failed. Here's the log of the command (cd shadow-beta-0.8.62; rpmbuild --buildroot='/home/user/shadow/shadow-alpha-artful(1)/shadow-beta-0.8.62' -bb --target x86_64 'shadow-beta-0.8.62-2.spec'): Fehler: Zeile 5: Leerer Tag: Summary: Für folgende Zielplattform(en) wird gebaut: x86_64 Edit: I am unable to follow the suggestions in the answers. How can I edit a file that is not even generated because the conversion failed?

I'm stuck with a problem when I try to install a local .rpm packages. Error message:

Total size: 124 M
Installed size: 124 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
error: Couldn't create temporary file for %pre(PACKAGE): Success
Error in PREIN scriptlet in rpm package PACKAGE
  Verifying  : PACKAGE                                                 1/1

Failed:
  PACKAGE

I'm completely lost, since I'm pretty new with linux. I'm testing on a: OS: "Oracle Linux Server 7.9" Kernel release: 5.4.17-2136.309.4.el7uek.x86_64

Recently lambda/dotnet:8 switch over to amazonlinux:2023 instead of amazonlinux:2. As a result I can't install simply the native compilers directly inside the image. Steps: > docker pull public.ecr.aws/lambda/dotnet:8 > docker run --rm --entrypoint bash -it public.ecr.aws/lambda/dotnet:8 bash-5.2# dnf group install -y "Development Tools" This is microdnf, which implements subset of `dnf'. [...] error: Unknown command: 'group' Using: # rpm -q microdnf microdnf-3.8.1-1.amzn2023.0.1.x86_64 Is there a simple way to install plain yum or regular dnf over an existing microdnf setup ? --- For example I cannot simply install yum over the existing microdnf setup: % docker run --rm --entrypoint bash -it public.ecr.aws/lambda/dotnet:8 bash-5.2# dnf install yum Downloading metadata... error: Could not depsolve transaction; 1 problem detected: Problem: problem with installed package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package yum-4.12.0-2.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.12.0-2.amzn2023.0.4, but none of the providers can be installed - conflicting requests - package yum-4.14.0-1.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.4, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package yum-4.14.0-1.amzn2023.0.5.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.5, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux Which is identical to: bash-5.2# microdnf install yum error: Could not depsolve transaction; 1 problem detected: Problem: problem with installed package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.12.0-2.amzn2023.0.4.noarch from amazonlinux - package yum-4.12.0-2.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.12.0-2.amzn2023.0.4, but none of the providers can be installed - conflicting requests - package yum-4.14.0-1.amzn2023.0.4.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.4, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.4.noarch from amazonlinux - package yum-4.14.0-1.amzn2023.0.5.noarch from amazonlinux requires dnf = 4.14.0-1.amzn2023.0.5, but none of the providers can be installed - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from @System conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.10.0-2.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux - package microdnf-dnf-3.8.1-1.amzn2023.0.1.x86_64 from amazonlinux conflicts with dnf provided by dnf-4.14.0-1.amzn2023.0.5.noarch from amazonlinux

I have an utility installed that requires some package (inxi). When I try to remove inxi, package manager offers to remove my utility too.

[root@host-15 ~]# apt-get remove inxi
Чтение списков пакетов... Завершено
Построение дерева зависимостей... Завершено
Следующие пакеты будут УДАЛЕНЫ:
  inxi my-utility
0 будет обновлено, 0 новых установлено, 2 пакетов будет удалено и 166 не будет обновлено.
Необходимо получить 0B архивов.
После распаковки будет освобождено 5671kB дискового пространства.
Продолжить? [Y/n]

Is there a way to protect my-utility from removing while I'm removing inxi? I I use Alt Linux with apt 0.5.15lorg2 version based on RPM packages.