Bug 15012

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD

The problem is present in MGA5

--- details

Preparing...                     ####################################################################################################################
Note that by downloading snx you indicate your acceptance of the EULA,
available at http://www.checkpoint.com/download_agreement.html
Downloading from https://ssl02.upcbroadband.com/CSHELL/snx_install.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
Download checksum failed
error: %prein(snx-75.40-4.mga5.nonfree.i586) scriptlet failed, exit status 1
ERROR: 'script' failed for snx-75.40-4.mga5.nonfree
error: snx-75.40-4.mga5.nonfree.i586: install failed

Status: RESOLVED => REOPENED
Version: 4 => 5
Resolution: OLD => (none)

Adding "--insecure" to curlrc gives this error:

Download checksum failed
error: %prein(snx-75.40-4.mga5.nonfree.i586) scriptlet failed, exit status 1
ERROR: 'script' failed for snx-75.40-4.mga5.nonfree
error: snx-75.40-4.mga5.nonfree.i586: install failed

I have fixed this issue in cauldron, so this will be ok in Mageia 6.
Do you need a Mageia 5 update package?

Status: REOPENED => ASSIGNED

I wouldn't be able to test it since we currently have changed vpn software; so I think it would be ok to wait for mga6.

Thanks for your feedback.
Not sure what's the appropriate way to close this one, closing as RESOLVED MOVED since the fix is in cauldron and will be in Mageia 6.

Status: ASSIGNED => RESOLVED
Resolution: (none) => MOVED

(In reply to Olivier Blin from comment #7)
> Thanks for your feedback.
> Not sure what's the appropriate way to close this one, closing as RESOLVED
> MOVED since the fix is in cauldron and will be in Mageia 6.

Tbh, i prefer setting version to cauldron and closing as fixed.

iiuc, the moved resolution is for bug reports that have become confusing, either because unrelated issues were mixed with it, or because there are very many comments. Moving the bug report to a new one, with only the needed information in it, will then help.

CC: (none) => marja11
Version: 5 => Cauldron
Resolution: MOVED => FIXED