Skip to main content

Adding EPEL 7 repo to Satellite 5


Repository URL: http://mirrors.kernel.org/fedora-epel/7/x86_64/

You will likely get the following error (/var/log/rhn/reposync/epel_rhel7_x86_64.log

[root@rh6sat5 reposync]# tail -f epel_rhel7_x86_64.log
Sync started: Fri May 22 18:58:00 2015
['/usr/bin/spacewalk-repo-sync', '--channel', 'epel_rhel7_x86_64', '--type', 'yum', '']
Repo URL: http://mirrors.kernel.org/fedora-epel/7/x86_64/
ERROR: xz compression not available
Sync completed.
Total time: 0:00:03

So - to fix this, do the following...
yum -y install http://mirrors.kernel.org/fedora-epel/epel-release-latest-6.noarch.rpm
cd /etc/yum.repos.d/
sed -i -e 's/enabled=1/enabled=0/g' epel.repo
yum --enablerepo epel list pyliblzma

To resolve the mess from above...

yum remove pyliblzma && yum --enablerepo epel -y install pyliblzma



Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...