yum repo issue prevention

Submitted by rhostager on Fri, 06/17/2016 - 17:47 Pro Licensee

I don't have an issue.... yet. I want to prevent one. I have been doing some maintenance on my server after a long break. The two things that I did are;1 - installed php 55 using the latest documentation for Virtualmin, "Multiple PHP Versions" and 2 added Letsencrypt to start trying out their Certs. The PHP install seems to have added a repo "rhscl-php55-epel-6-x86_64.repo" and the LetsEncrypt instructions had me add EPEL. I did not think about the package repos and need for Virtualmin to have some control over them until I noticed that EPEL wanted to update several of the packages that I knew were key to Virtualmin. I did not do the updates and pulled the epel repo out of the repos.d directory. Did yum clean all, yum update. Then, I noticed that I have "CentOS-SCLo-scl-rh.repo" added in and it is wanting to upgrade php54. I believe php54 was installed quite a while back using the old multiple php installation instructions. I did not do that upgrade either.

My goal is to NOT mess up Virtualmin and need some advice on how to proceed.

Here are the repos in repos.d:

CentOS-Base.repo CentOS-SCLo-scl-rh.repo CentOS-Base.repo.rpmnew CentOS-Vault.repo CentOS-Debuginfo.repo rhscl-php55-epel-6-x86_64.repo CentOS-fasttrack.repo virtualmin.repo CentOS-Media.repo

PHP 5.5 did not turn out to work properly with my templates so would not mind removing that if needed to get Virtualmin back to a safe repo state; it looks like I won't use it.

Thanks

Status: 
Active

Comments

Submitted by andreychek on Fri, 06/17/2016 - 19:11

Howdy -- hmm, you shouldn't actually need any other repositories to get Let's Encrypt working. Let's Encrypt is built into Virtualmin, it doesn't require any external libraries. However, you may be saying you installed the official client using that.

I suppose the question is, what packages from third party repositories do you need?

If you had enabled EPEL to install the official Let's Encrypt client, it's probably safe to disable that repository now that you have that installed.

Which other repositories do you want to have other than that one? Are you using any of those more recent PHP packages?

Submitted by rhostager on Fri, 06/17/2016 - 22:26 Pro Licensee

Yea, I figured out that Let's Encrypt was already built in to Virtualmin after I tried generic install information. There doesn't seem to be good documentation on the integration of Let's Encrypt into Virtualmin and how to use it. Once I figured it out... it is so simple and works perfectly! Nice job!!!

I guess the question in regards to repos is will "CentOS-SCLo-scl-rh.repo" possibly mess up my Virtualmin setup if I accidentally update a package out of there that Virtualmin normally provides? I do use php54. It looks like the new method of installing more php versions isolates the repo to just php. php54 was installed under the old method. Can I delete the "CentOS-SCLo-scl-rh.repo" repo and update php54 using the new method? Hope this makes sense.

Thanks

Submitted by andreychek on Fri, 06/17/2016 - 23:27

It's hard to say, I'm not quite sure what's included in that repo.

However, I'll offer that I'd only enable the repositories that you're certain you need. If you have any doubts about that one, I'd go ahead and disable it.

I'm unfortunately not quite sure what the procedure is from changing to using the PHP-specific repositories... but it might be as simple as disabling the repository you mentioned, and then enabling the PHP54 repository. It's definitely worth a try, and that's a lot safer than having the entire EPEL or SCL repository enabled.

Submitted by rhostager on Sat, 06/18/2016 - 10:19 Pro Licensee

OK. That helps. Thanks.