FEDORA-EPEL-2014-0881 created by pavlix 7 years ago for Fedora EPEL 6
stable

New upstream version and a number of bug fixes.

This update has been submitted for testing by pavlix.

7 years ago

This update is currently being pushed to the Fedora EPEL 6 testing updates repository.

7 years ago

This update has been pushed to testing

7 years ago
User Icon awjb commented & provided feedback 7 years ago
karma
  • The new initscript is broken: @SBINDIR@/@IPSEC_SCRIPT@ in exec is not replaced correctly with /usr/sbin/strongswan * 1069928 is not fixed. I am still seeing the /usr/bin/pki errors when calling 'strongswan pki' * Calling /usr/libexec/strongswan/pki directly seems work correctly now

pavlix has edited this update. New build(s): strongswan-5.1.2-3.el6. Removed build(s): strongswan-5.1.2-2.el6.

7 years ago

This update has been submitted for testing by pavlix.

7 years ago

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.

This update is currently being pushed to the Fedora EPEL 6 testing updates repository.

7 years ago

This update is currently being pushed to the Fedora EPEL 6 testing updates repository.

7 years ago

This update is currently being pushed to the Fedora EPEL 6 testing updates repository.

7 years ago

This update has been pushed to testing

7 years ago
User Icon awjb commented & provided feedback 7 years ago
karma

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.

7 years ago

This update has been submitted for testing by pavlix.

7 years ago

This update is currently being pushed to the Fedora EPEL 6 testing updates repository.

7 years ago
User Icon awjb commented & provided feedback 7 years ago
karma

-4 fixes 1062954 and 1069928 for me

This update has been pushed to testing

7 years ago
User Icon trekoid commented & provided feedback 7 years ago
karma

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, BuildID[sha1]=0x25464f9abba994d0e8ca1b3fce4ea7ef93c3b358, stripped

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 bugzilla.

User Icon trekoid commented & provided feedback 7 years ago
karma

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.

7 years ago

Thanks trekoid. Looking forward to the bugzilla ticket.

This update is currently being pushed to the Fedora EPEL 6 stable updates repository.

7 years ago

This update has been pushed to stable

7 years ago

Please login to add feedback.

Metadata
Type
bugfix
Karma
2
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
7 years ago
in testing
7 years ago
in stable
7 years ago
modified
7 years ago
BZ#1062954 strongswan-pki segfaults
0
0
BZ#1069928 /usr/bin/pki: No such file or directory
0
0
BZ#1071338 strongswan is compiled without xauth-pam plugin
0
0

Automated Test Results