Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16783 - [qca] package not providing sha1, md5 etc.

Attached to Project: Arch Linux
Opened by Matthias Fuchs (mat69) - Thursday, 22 October 2009, 14:25 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 31 October 2009, 08:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
qca-ossl is supposed to add support for md2, md4, md5, sha0, sha1, sha256 etc. yet the version provided by Arch does not have support for any of these. Compiling the most recent version of qca (trunk) myself (and thus qca-ossl) does fix it.


Additional info:
* qca 2.0.2-1
* qca-ossl 2.0.0-1

Steps to reproduce:

Create a directory and download the attached code into that.
Then
mkdir build && cd build/ && cmake ../ && make
./qca_test
if it only outpus () when it does not work.

It looks like this when I compile it myself:
("sha1", "sha0", "ripemd160", "md2", "md4", "md5", "sha224", "sha256", "sha384", "sha512")


NOTE: I use KDE4 stuff to have the cmake-file for QCA2.
   main.cpp (0.4 KiB)
   CMakeLists.txt (0.4 KiB)
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Saturday, 31 October 2009, 08:53 GMT
Reason for closing:  Not a bug
Comment by Pierre Schmitz (Pierre) - Thursday, 22 October 2009, 15:32 GMT
Is there any package that is broken due to this? Otherwise I don't see a problem here.
Comment by Matthias Fuchs (mat69) - Thursday, 22 October 2009, 15:45 GMT
I'm not sure, afaik KTorrent uses QCA::Hash (sha1) for verification, at least they do in trunk. I don't think that this breaks KTorrent (just glimpsing at it), rather I think that it might result in fewer features, as would be the case with KGet 4.4.
Comment by Matthias Fuchs (mat69) - Friday, 23 October 2009, 06:19 GMT
Ok, guess that I found the problem. I compiled Qt 4.6 myself and that caused it not to work, maybe there is a binary incompatible change between 4.5 and 4.6. Using Qt 4.5.3 from the repo made it work.

Loading...