Search found 2389 matches

by avij
2018/05/22 00:01:52
Forum: CentOS 6 - Software Support
Topic: yum update issue
Replies: 1
Views: 11

Re: yum update issue

You should not use "epel7" packages on CentOS 6. Remove/disable that download.mono-project.com_repo_centos repository and find one that has "6" in its name. And the other question, sorry, there is no upgrade path from CentOS 6 to CentOS 7. You need to install CentOS 7 from scratch.
by avij
2018/05/21 13:41:33
Forum: CentOS 7 - General Support
Topic: How to install a specific 7.4 kernel
Replies: 3
Views: 89

Re: How to install a specific 7.4 kernel

Grabbing the kernels from http://mirror.centos.org/centos/7.4.170 ... /Packages/ is not an option for you?
by avij
2018/05/16 19:58:35
Forum: CentOS 7 - General Support
Topic: /etc/cron.daily/0yum-daily.cron: error
Replies: 6
Views: 109

Re: /etc/cron.daily/0yum-daily.cron: error

OK, great. One other option is that if you are not actively using gthumb, you can remove the package now and then later on reinstall it again when it has been compiled against the new libraries. This would stop the libexiv-related messages in your yum-daily output.
by avij
2018/05/16 19:37:47
Forum: CentOS 7 - General Support
Topic: /etc/cron.daily/0yum-daily.cron: error
Replies: 6
Views: 109

Re: /etc/cron.daily/0yum-daily.cron: error

Hopefully the packager can rebuild the package soon. When that bugzilla entry states that "gthumb has been pushed to the Fedora EPEL 7 testing repository" you can update with yum update --enablerepo=epel-testing to get the new gthumb package.
by avij
2018/05/16 15:26:12
Forum: CentOS 7 - General Support
Topic: redhat-lsb.i686 pkg missing in CentOS 7.5
Replies: 6
Views: 149

Re: redhat-lsb.i686 pkg missing in CentOS 7.5

Yes, it was initially misplaced, but despite that, yum install redhat-lsb.i686 would have worked because the repodata knew about the oddly placed package. The package has now been moved into Packages at it should.
by avij
2018/05/16 10:21:58
Forum: CentOS 7 - Security Support
Topic: CVE-2018-8781 resolution for Centos 7
Replies: 2
Views: 99

Re: CVE-2018-8781 resolution for Centos 7

That page you linked to (and the related Bugzilla entry) has all the information that is available.

If you are looking for a schedule for when a fix might be published, that information is not available either.
by avij
2018/05/16 06:41:03
Forum: CentOS 7 - Software Support
Topic: WTH is going on with Yum?!
Replies: 7
Views: 200

Re: WTH is going on with Yum?!

Yum's fastestmirror plugin establishes several connections to the mirrors to measure the time it takes to connect to each mirror. Some routers might think this is some sort of an attack and block the offending IP address for a while. Firefox may also establish several connections at startup. If your...
by avij
2018/05/16 05:17:48
Forum: CentOS 7 - General Support
Topic: redhat-lsb.i686 pkg missing in CentOS 7.5
Replies: 6
Views: 149

Re: redhat-lsb.i686 pkg missing in CentOS 7.5

Yes, this is indeed unfortunate. The package will be added to the "updates" repository soon. You can use multiple repositories in kickstart files. If you have both "os" and "updates" repositories defined in your kickstart file, you can install redhat-lsb.i686 just fine.
by avij
2018/05/15 11:39:26
Forum: CentOS Social
Topic: [Solved - sort of] Machine shutting itself down randomly
Replies: 11
Views: 210

Re: Machine shutting itself down randomly

Heat does not do good to components. Perhaps your motherboard or power supply is damaged (see for leaking transistors and such). There's a very good chance that you will need to buy replacement parts. You may also need to consider scrapping the entire system and getting a replacement.
by avij
2018/05/15 11:35:01
Forum: CentOS 7 - General Support
Topic: 7.5 upgrade: systemd.i686 requires liblz4.so.1
Replies: 5
Views: 140

Re: 7.5 upgrade: systemd.i686 requires liblz4.so.1

There is lz4-1.7.5-2.el7.i686.rpm in the repository, I don't know what is the problem. Perhaps seeing the full yum update output would help. In any case, unless you have a specific need for some 32bit package, you can yum remove '*.i686' . Perhaps the 32bit packages got pulled in when you up...