var/cache/yum/x86_64/7/base/gen/primary_db.sqlite: SQLite 3.x database > find /var/cache/yum/x86_64/7/ -iname '*.sqlite' | xargs file Configure the failing repository to be skipped, if it is unavailable. Will then just ignore the repository until you permanently enable itĪgain or use -enablerepo for temporary usage:ĥ. Disable the repository permanently, so yum won't use it by default. Run the command with the repository temporarily disabledĤ. Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos This happened abruptly and was fixed fairly quick so is the answer, if you need epel, to just wait? Or maybe have a local copy of the epel repo but keep it behind by a couple of versions?Ĭleaning repos: base epel extras nux-dextop updates If I did need epel (and I did but I was just doing some home lab stuff - no money was lost, no businesses were shut down and no VMs were harmed) what do experts (I'm not one) do? How did you determine that from the error message? I couldn't figure it out to know which repo to try to disable. You answered that this was likely the epel repo. Does this mean that an upstream repo error can effectively shutdown anything yum related, even on other repos, globally? So I was unable to do anything with yum because one, more, or all mirrors for a repo get corrupted. I have a few questions please understand that it is just in the interest of understanding and learning what to do. This is an interesting problem I hadn't considered. Yum-config-manager -save -setopt=.skip_if_unavailable=true If it is a very temporary problem though, this is often a nice So will have to try and fail each time (and thus. Note that yum will try to contact the repo. Just ignore the repository until you permanently enable it again or useĤ. Disable the repository, so yum won't use it by default. Packages for the previous distribution release still work).ģ. This is most often useful if you are using a newerĭistribution release than is supported by the repository (and the for the repository, to point to a working Contact the upstream for the repository and get them to fix the problem.Ģ. There are a few ways to work "fix" this:ġ. One of the configured repositories failed (Unknown),Īnd yum doesn't have enough cached data to continue. Verifying : php-pgsql-5.3.29-1.8.amzn1.Loading mirror speeds from cached hostfile Try remove command to remove the packages: ec2-user]# yum remove php-pgsql* -y Installed Packages - this line shows it installed. Loaded plugins: priorities, update-motd, upgrade-helper ![]() Now if the plugin in installed on ec2 and you run list command, it shows the installed packages: ec2-user]# yum list php-pgsql* To support my answer, I had tried to run both of your command on ec2, and which does remove the package, if its installed. and that's why, when you hit the remove command, it shows that no packages marked for removal. If you look at the output of the list command, it shows that the php-pgsql.x86_64 is available, not installed on the machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |