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!
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!
FS#2277 - psi incorrectly packaged
Attached to Project:
Arch Linux
Opened by Mircea Bardac (IceRAM) - Thursday, 24 February 2005, 11:00 GMT
Last edited by Dale Blount (dale) - Thursday, 24 February 2005, 14:06 GMT
Opened by Mircea Bardac (IceRAM) - Thursday, 24 February 2005, 11:00 GMT
Last edited by Dale Blount (dale) - Thursday, 24 February 2005, 14:06 GMT
|
DetailsPsi 0.9.2 package had it's criptographic dependencies built with it, because nobody needed them.
Psi 0.9.3 depends on QCA (QT Cryptography Architecture), because QCA will also be used by KDE in the future. QCA has some plugings: QCA-SASL & QCA-TLS. In order for Psi to have SSL support when connecting to Jabber servers, QCA-TLS is used. Psi can live without QCA-TLS, but not without QCA. Yesterday, Psi 0.9.3 was packed. I had a look over the PKGBUILD and I've noticed that QCA-TLS is built within. QCA-TLS is more part of QCA than Psi (I may say). Some other program might need QCA-TLS also. Note also that QCA-TLS is delivered in a separate archive, and I personally don't know how it could compile with the old PKBUILD which considers it a part of Psi's archive (I might have missed something in that archive, but I don't think so). http://bbs.archlinux.org/viewtopic.php?t=7517#49807 (main developer's comments) http://mircea.bardac.net/psi/ |
This task depends upon
Closed by dorphell (dorphell)
Thursday, 24 February 2005, 16:45 GMT
Reason for closing: Not a bug
Additional comments about closing: no bug.
Thursday, 24 February 2005, 16:45 GMT
Reason for closing: Not a bug
Additional comments about closing: no bug.
No bug here, closing.