New upstream version and a number of bug fixes.
This update has been submitted for testing by pavlix.
This update is currently being pushed to the Fedora EPEL 6 testing updates repository.
This update has been pushed to testing
pavlix has edited this update. New build(s): strongswan-5.1.2-3.el6. Removed build(s): strongswan-5.1.2-2.el6.
Updated the build. Let's see how the karma system copes with it, never done that
before for an update that already has (negative) karma.
The karma issue will be fixed according to
Sorry, according to https://fedorahosted.org/bodhi/ticket/388
Init script is fixed with -3. strongswan pki is still broken (see #1069928).
pavlix has edited this update. New build(s): strongswan-5.1.2-4.el6. Removed build(s): strongswan-5.1.2-3.el6.
-4 fixes 1062954 and 1069928 for me
Please forgive me if I should be reporting this with Amazon. When I try to
install strongswan-5.1.2-4.el6 on an Amazon Linux instance in EC2 I get a
dependency failure for OpenSSL. [root@ip-XX-XX-XX-XX ~]# yum update
--enablerepo=epel-testing strongswan-5.1.2-4.el6 Loaded plugins: priorities,
update-motd, upgrade-helper amzn-main/latest
| 2.1 kB 00:00 amzn-updates/latest
| 2.3 kB 00:00 689 packages excluded due to repository priority
protections Resolving Dependencies --> Running transaction check ---> Package
strongswan.x86_64 0:5.1.1-4.el6 will be updated --> Processing Dependency:
strongswan = 5.1.1 for package: strongswan-tnc-imcvs-5.1.1-4.el6.x86_64 --->
Package strongswan.x86_64 0:5.1.2-4.el6 will be an update --> Processing
Dependency: libcrypto.so.10(OPENSSL_1.0.1_EC)(64bit) for package:
strongswan-5.1.2-4.el6.x86_64 --> Running transaction check ---> Package
strongswan.x86_64 0:5.1.2-4.el6 will be an update --> Processing Dependency:
libcrypto.so.10(OPENSSL_1.0.1_EC)(64bit) for package:
strongswan-5.1.2-4.el6.x86_64 ---> Package strongswan-tnc-imcvs.x86_64
0:5.1.1-4.el6 will be updated ---> Package strongswan-tnc-imcvs.x86_64
0:5.1.2-4.el6 will be an update --> Finished Dependency Resolution Error:
Package: strongswan-5.1.2-4.el6.x86_64 (epel-testing) Requires:
libcrypto.so.10(OPENSSL_1.0.1_EC)(64bit) You could try using --skip-broken to
work around the problem You could try running: rpm -Va --nofiles --nodigest
Checking, what version of OpenSSL Amazon currently has, it shows it is already
1.0.1e. [root@ip-XX-XX-XX-XX ~]# yum list installed | grep openssl
openssl.x86_64 1:1.0.1e-4.55.amzn1 @amzn-updates
[root@ip-XX-XX-XX-XX ~]# file /lib64/libcrypto.so.10 /lib64/libcrypto.so.10:
symbolic link to `libcrypto.so.1.0.1e' [root@ip-XX-XX-XX-XX ~]# file
/lib64/libcrypto.so.1.0.1e /lib64/libcrypto.so.1.0.1e: ELF 64-bit LSB shared
object, x86-64, version 1 (SYSV), dynamically linked,
Hi trekoid. This is a pretty important update that works for other users.
Negative karma was certainly not the right tool in this case and if it blocks
releasing, I'm going to get it removed. Please start a new bug report for the
EPEL package, check whether your system meets requirements to install EPEL6
packages and specify the problem and ideally also possible solutions in the
Release -4 worked on CentOS 6.5. Bug 1069928 and 1062954 were resolved.
Thanks Pavlix. I will go to bugzilla for the Amazon Linux issue. I understand
the importance. I am amongst those waiting for/wanting the fix.
This update has been submitted for stable by pavlix.
Thanks trekoid. Looking forward to the bugzilla ticket.
This update is currently being pushed to the Fedora EPEL 6 stable updates repository.
This update has been pushed to stable
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.