Why dnf config-manager --save does not work? - configuration

I want to add a rpm repo for my system with dnf config-manager:
# dnf config-manager --add-repo=http://example.com/rpm-repo --setopt=gpgcheck=0 --save
Adding repo from: http://example.com/rpm-repo
# cat /etc/yum.repos.d/example.com_rpm-repo.repo
[example.com_rpm-repo]
name=created by dnf config-manager from http://example.com/rpm-repo
baseurl=http://example.com/rpm-repo
enabled=1
Why the resulted example.com_rpm-repo.repo file does not contain the specified option: gpgcheck=0?
Environment:
# cat /etc/centos-release
CentOS Linux release 8.0.1905 (Core)
# yum list installed | grep dnf
dnf.noarch 4.0.9.2-5.el8 #System
dnf-data.noarch 4.0.9.2-5.el8 #System
dnf-plugins-core.noarch 4.0.2.2-3.el8 #BaseOS
dnf-utils.noarch 4.0.2.2-3.el8 #BaseOS
libdnf.x86_64 0.22.5-4.el8 #System
python3-dnf.noarch 4.0.9.2-5.el8 #System
python3-dnf-plugins-core.noarch 4.0.2.2-3.el8 #BaseOS
python3-libdnf.x86_64 0.22.5-4.el8 #System

(sadly) you cannot do this in a single operation. You first need to create the repository, then set the option(s):
dnf config-manager --add-repo=http://example.com/rpm-repo
dnf config-manager --save --setopt=gpgcheck=0 example.com_rpm-repo
yes sadly this means that you need to know the repoid, so this will be slightly complicated to automate into one operation.

Related

cuda 9 packages no longer required after installation

I installed CUDA 9 from the local deb but afterwards apt reports:
The following packages were automatically installed and are no longer required:
cuda-command-line-tools-9-0 cuda-core-9-0 cuda-cublas-9-0 cuda-cublas-dev-9-0 cuda-cudart-9-0 cuda-cudart-dev-9-0
cuda-cufft-9-0 cuda-cufft-dev-9-0 cuda-curand-9-0 cuda-curand-dev-9-0 cuda-cusolver-9-0 cuda-cusolver-dev-9-0
cuda-cusparse-9-0 cuda-cusparse-dev-9-0 cuda-documentation-9-0 cuda-driver-dev-9-0 cuda-libraries-9-0
cuda-libraries-dev-9-0 cuda-license-9-0 cuda-misc-headers-9-0 cuda-npp-9-0 cuda-npp-dev-9-0 cuda-nvgraph-9-0
cuda-nvgraph-dev-9-0 cuda-nvml-dev-9-0 cuda-nvrtc-9-0 cuda-nvrtc-dev-9-0 cuda-samples-9-0 cuda-toolkit-9-0
cuda-visual-tools-9-0 freeglut3 freeglut3-dev libdrm-dev libgl1-mesa-dev libglu1-mesa-dev libx11-xcb-dev
libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxcb-randr0-dev libxcb-shape0-dev
libxcb-sync-dev libxcb-xfixes0-dev libxmu-dev libxmu-headers libxshmfence-dev libxxf86vm-dev linux-headers-4.10.0-38
linux-headers-4.10.0-38-generic linux-image-4.10.0-38-generic linux-image-extra-4.10.0-38-generic mesa-common-dev
nvidia-modprobe x11proto-dri2-dev x11proto-gl-dev x11proto-xf86vidmode-dev
Use 'sudo apt autoremove' to remove them.
nvcc --version reports V9.0.176 and I have the following in /usr/local:
$ ls /usr/local/cuda-*
/usr/local/cuda-8.0:
bin samples
/usr/local/cuda-9.0:
bin extras lib64 libnvvp nsightee_plugins nvvm samples src tools
doc include libnsight LICENSE nvml README share targets version.txt
What did I do wrong?
I could not determine why the CUDA 9.0 packages were "no longer required", but I went ahead and removed all old packages and then installed CUDA 9.1 from the local deb linked in my question.
sudo apt autoremove
sudo apt --purge remove cuda-repo-ubuntu1704-9-0-local
sudo dpkg -i cuda-repo-ubuntu1704-9-1-local_9.1.85-1_amd64.deb
sudo apt-key add /var/cuda-repo-9-1-local/7fa2af80.pub
sudo apt update
sudo apt install cuda
And then I verified /usr/local/cuda-9.1/bin was in my $PATH, and I added export PATH=$PATH:/usr/local/cuda-9.1/bin to my ~/.bashrc.

I attempted to enable the EPEL repo on my Fedora 22 machine and I broke it, now errors are thrown

I made the attempt at enabling EPEL on my Fedora 22 machine by running
wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
Then
sudo rpm -ivh epel-release-7-5.noarch.rpm
And now when I run
dnf repolist
I get the following
[sinux1#horrible-host ~]$ sudo dnf repolist
Extra Packages for Enterprise Linux 7 - x86_64 1.8 MB/s | 9.0 MB 00:05
Failed to open: /var/cache/dnf/epel-2b6dfc5904c26562/repodata/49c4e3bd54f19136521be9b254830c954369cc22ce1b661db502ebef13b0004c-updateinfo.xml.bz2.
[sinux1#horrible-host ~]$
I'm stuck and not sure what my next step is. How can I reverse what I did, and what would have been the proper way of enabling EPEL?
Thanks for any input
This is what appears to have worked for me.
Remove the epel repo
rm -rf /etc/yum.repos.d/epel*
then try install epel via dnf
dnf clean all
dnf install epel-release
I did the same as Sinux Tine and ended up in some sort of deadlock.
First try to do like Rup says.
If everything fails, try the following as a last resort. It worked for me.
> su
> cd /var/cache/dnf/epel-2b6dfc5904c26562/repodata
> mkdir throwaway
> mv 49c4e3bd54f19136521be9b254830c954369cc22ce1b661db502ebef13b0004c-updateinfo.xml.bz2 throwaway
That effectively deletes the file which dnf says it cannot open.
When and if the problem is solved, you can delete the throwaway directory and its contents.
Current libsolv version does not have bz2 compression.
Solution: enable bunzip2 compression in libsolv, Basically 'yum update libsolv', then reinstall epel-release.
To complement the answer for Centos 7, I followed the next steps:
Download the libsolv-0.6.14-1.el7 wich was patched
Install it
sudo rpm -ivh libsolv-0.6.14-1.el7.centos.x86_64.rpm
If we get a conflict with the previous version
warning: libsolv-0.6.14-1.el7.centos.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 1b6f9f55: NOKEY
Preparing... ################################# [100%]
file /usr/lib64/libsolv.so.0 from install of libsolv-0.6.14-1.el7.centos.x86_64 conflicts with file from package libsolv-0.6.11-1.el7.x86_64
file /usr/lib64/libsolvext.so.0 from install of libsolv-0.6.14-1.el7.centos.x86_64 conflicts with file from package libsolv-0.6.11-1.el7.x86_64
We proceed to remove the previous version
sudo yum erase libsolv-0.6.11-1.el7.x86_64
and install the patched libsolv package
sudo rpm -ivh libsolv-0.6.14-1.el7.centos.x86_64.rpm
We need to reinstall the dnf package manager, because it was removed after to remove the libsolv so we install with the following command.
sudo yum install dnf
We validate it using sudo dnf repolist now it, give us the right output.
Using metadata from Mon Jun 13 10:53:11 2016
repo id repo name status
base CentOS-7 - Base 9,007

Cygnus installation

I try to install cygnus. I install yum install java-1.6.0-openjdk-devel and run , my problem is:
Then, the developed classes must be packaged in a Java jar file which must be added to the APACHE_FLUME_HOME/lib directory:
$ git clone https://github.com/telefonicaid/fiware-connectors.git
$ git checkout release/0.1
$ cd fiware-connectors/flume
$ APACHE_MAVEN_HOME/bin/mvn package
$ cp target/cosmos-injector-1.0-SNAPSHOT.jar APACHE_FLUME_HOME/lib
in this step, I create cygnus.jar not cosmos-injector-1.0-SNAPSHOT.jar , and # APACHE_FLUME_HOME/conf/cosmos-injector.conf not exist on my flume directory.
Alejandro, I recommend you to install last version of Cygnus (currenty, 0.7.1), which can be installed through RPM packages (recommended). Simply configure the FIWARE repo and install it using yum (CentOS):
$ sudo cat > /etc/yum.repos.d/fiware.repo <<EOL [Fiware]
name=FIWARE
repository baseurl=http://repositories.testbed.fi-ware.eu/repo/rpm/x86_64/
gpgcheck=0
enabled=1
EOL
$ yum install cygnus
You can find the Cygnus Quick Start Guide at this link.
The README will give you extended information about the tool.
Advanced topics can be found at the doc/ folder.

Compiler error mysql.h not found

On compiling a software I get this error
mysql/mysql.h: No such file or directory
result of running mysql_config --include is
-I/usr/local/mysql/include
How can I get mysql.h to be detected?
Install mysql development packages on Debian/ubuntu.
sudo apt-get install libmysqld-dev
on CentOs/Redhat (to know who provide - yum provides mysql/mysql.h):
sudo yum install mysql-devel
While building Kamailio from sources on CentOS / Fedora, I encountered mysql/mysql.h: No such file or directory
Since my target was MariaDB, installing mariadb-devel package helped
# yum -y install mariadb-devel
Before installing above package, it was necessary for me to clean-up previously installed MariaDB-client package.
# yum remove MariaDB-client
# yum remove MariaDB-common
# mv /etc/yum.repos.d/mariadb.repo /etc/yum.repos.d/mariadb.repo.bak
If necessary we can get back the original MariaDB-client package after the build process, such as
# mv /etc/yum.repos.d/mariadb.repo.bak /etc/yum.repos.d/mariadb.repo
# yum -y install MariaDB-client

Install single package from Rawhide

How can one install a single Rawhide package, without upgrading the entire
operating system?
yum install fedora-repos-rawhide
yum install --enablerepo rawhide bash
This is the top search result for this inquiry. Key signing has changed for F27 on, so to pull a package from rawhide use the following:
sudo dnf install fedora-repos-rawhide -y
sudo dnf --disablerepo=* --enablerepo=rawhide --releasever=[next release #, e.g. if you're on 27 use 28] install [package name]
You can also import the key manually from the Fedora website or force an unauthenticated upgrade to the newest fedora-repos.