I highly discourage you from trying to upgrade major CentOS releases. Something always goes wrong. It's also about that time to be upgrading everything from scratch when RHEL/CentOS release cycles end. There is more than just packages needing to be upgraded. the whole system is different. For example; CentOS 6 uses SysV INIT while CentOS 7 uses SystemD INIT with compatibility symbolic links for legacy INIT only programs. Trust me it is more difficult and time consuming to upgrade a CentOS6 box to CentOS 7 than to just start a new CentOS 7 box and migrate your stuff over. You don't want be be running EOL software especially in a production environment.
On 03/16/2017 04:49 PM, Michael Christopher Robinson wrote: > I have a custom compiled perl and to update to the last CentOS 6.x > packages I have to add --skip-broken. That appears to be working. > One concern, > > [admin@goose yum.repos.d]$ ls -R > .: > CentOS-Base.repo epel-testing.repo mirrors-rpmforge- > testing > CentOS-Debuginfo.repo error.txt remove > CentOS-Media.repo fc6.repo.bak rpmforge.repo > CentOS-Vault.repo mirrors-rpmforge > epel.repo mirrors-rpmforge-extras > > ./remove: > adobe-linux-x86_64.repo > [admin@goose yum.repos.d]$ > > There are multiple non stock repositories here. How do I find out what > non standard packages are installed? I'm hoping that perl-5.18.1 is > the only custom compiled and installed package. I can't do an in-place > upgrade until I do something about perl and the nonstandard > packages? I wish I could build an rpm from the installed perl... > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
