Mageia's OpenSSL package doesn't have zlib support. To witness, take the following C program (let's call it "sslcomp.c"): #include <stdio.h> #include "openssl/ssl.h" int main(int argc, char **argv) { COMP_METHOD *comp = COMP_zlib(); if (comp->type == NID_undef) { fprintf(stderr, "zlib unsupported\n"); return 1; } return 0; } Compile and run it: $ gcc -lssl sslcomp.c -o sslcomp $ ./sslcomp zlib unsupported
CC: (none) => pitrou
(for the record, this C snippet was inspired by OpenSSL's own "ssl/ssltest.c" program)
The same snippet works fine under Debian stable. Debian's libssl is explicitly linked against the zlib: $ ldd /usr/lib/libssl.so linux-gate.so.1 => (0xb7847000) libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0xb769d000) libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7699000) libz.so.1 => /usr/lib/libz.so.1 (0xb7684000) libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb753e000) /lib/ld-linux.so.2 (0xb7848000)
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. (Please set the status to 'assigned' if you are working on it)
CC: (none) => arnaud.patard, fundawang, mageia, pterjan
Well, fixing it is very simple, but I don't know if it is allowed adding extra dependences for updated packages.
(In reply to comment #4) > Well, fixing it is very simple, but I don't know if it is allowed adding extra > dependences for updated packages. Well, at least doing it in Cauldron would be nice (I reported the bug against Mageia 1 since that's what I'm using). Note that there's a build flag named "zlib-dynamic" which makes OpenSSL find the zlib at runtime, instead of linking against it (meaning you wouldn't have to add a dependency). Don't know if it works correctly.
I've already pushing updated package into cauldron. zlib-dynamic flag will make openssl trying to load libz.so rather than libz.so.1, which is not feasible.
(In reply to comment #4) > Well, fixing it is very simple, but I don't know if it is allowed adding extra > dependences for updated packages. It is allowed. When the source rpm is pushed from updates testing, to updates, the newly added dependencies (and any dependencies of the added dependencies that are not in base-system-minimal), have to have the binary rpm packages linked from Release to Updates. Just make sure that when the package is assigned to qa, you let them know dependencies have been added. This is the current work around for the infamous bug 2317.
CC: (none) => davidwhodgins
(In reply to comment #7) > (In reply to comment #4) > > Well, fixing it is very simple, but I don't know if it is allowed adding extra > > dependences for updated packages. > > It is allowed. When the source rpm is pushed from updates testing, > to updates, the newly added dependencies (and any dependencies of > the added dependencies that are not in base-system-minimal), have > to have the binary rpm packages linked from Release to Updates. > > Just make sure that when the package is assigned to qa, you let them > know dependencies have been added. This is the current work around > for the infamous bug 2317. @ Funda assigning to you, because I understand you are willing to fix this for Mageia 1, too. Please assign back to bugsquad in case I misunderstood
CC: (none) => marja11Assignee: bugsquad => fundawang
Depends on: (none) => 4409
Depends on: 4409 => 4049
*** Bug 4821 has been marked as a duplicate of this bug. ***
CC: (none) => hmandevteam
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and 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. 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. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX