Я пытаюсь установить fail2ban на CentOS, но не могу понять, почему он не будет установлен:
[root@server ~]# yum install fail2ban
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.linux.duke.edu
* epel: mirror.steadfast.net
* extras: centosx5.centos.org
* updates: centosc6.centos.org
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package fail2ban.noarch 0:0.8.4-29.el5 will be installed
--> Processing Dependency: shorewall for package: fail2ban-0.8.4-29.el5.noarch
--> Processing Dependency: python-inotify for package: fail2ban-0.8.4-29.el5.noarch
--> Processing Dependency: gamin-python for package: fail2ban-0.8.4-29.el5.noarch
--> Running transaction check
---> Package gamin-python.i686 0:0.1.10-9.el6 will be installed
---> Package python-inotify.noarch 0:0.9.1-1.el5 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: python-inotify-0.9.1-1.el5.noarch
---> Package shorewall.noarch 0:4.0.15-1.el5 will be installed
--> Processing Dependency: shorewall-perl = 4.0.15-1.el5 for package: shorewall-4.0.15-1.el5.noarch
--> Processing Dependency: shorewall-shell = 4.0.15-1.el5 for package: shorewall-4.0.15-1.el5.noarch
--> Processing Dependency: shorewall-common = 4.0.15-1.el5 for package: shorewall-4.0.15-1.el5.noarch
--> Running transaction check
---> Package python-inotify.noarch 0:0.9.1-1.el5 will be installed
--> Processing Dependency: python(abi) = 2.4 for package: python-inotify-0.9.1-1.el5.noarch
---> Package shorewall-common.noarch 0:4.0.15-1.el5 will be installed
---> Package shorewall-perl.noarch 0:4.0.15-1.el5 will be installed
---> Package shorewall-shell.noarch 0:4.0.15-1.el5 will be installed
--> Finished Dependency Resolution
Error: Package: python-inotify-0.9.1-1.el5.noarch (epel)
Requires: python(abi) = 2.4
Installed: python-2.6.6-29.el6_3.3.i686 (@updates)
python(abi) = 2.6
Available: python-2.6.6-29.el6_2.2.i686 (base)
python(abi) = 2.6
Available: python26-2.6.8-2.el5.i386 (epel)
python(abi) = 2.6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root@server ~]#