FS#42869 - [lzo] PKGBUILD provides listed as lzo2 instead of lzo
Attached to Project:
Arch Linux
Opened by Melissa Padilla (mpadilla2) - Friday, 21 November 2014, 22:22 GMT
Last edited by Anatol Pomozov (anatolik) - Tuesday, 30 December 2014, 19:09 GMT
Opened by Melissa Padilla (mpadilla2) - Friday, 21 November 2014, 22:22 GMT
Last edited by Anatol Pomozov (anatolik) - Tuesday, 30 December 2014, 19:09 GMT
|
Details
Description:
Openvpn has changed it's dependency to reflect the rename of lzo2 to lzo. However, it still fails when trying to use lzo. This is due to lzo PKGBUILD provides value as lzo2 instead of lzo. Additional info: * package version(s) 2.08-3 * config and/or log files etc. The PKGBUILD uses: provides=("lzo2=$pkgver") replaces=('lzo2') conflicts=('lzo2') Proposed PKGBUILD: pkgrel=4 provides=("lzo2=$pkgver" "lzo=$pkgver") replaces=('lzo2' 'lzo') conflicts=('lzo2' 'lzo') Steps to reproduce: 1. Install lzo 2.08-3 2. Install openvpn and configure with comp-lzo 3. Start openvpn 4. Note that openvpn will not start. Nov 21 10:11:49 STORAGE openvpn@UNS[2289]: library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.08 Nov 21 10:11:49 STORAGE openvpn@UNS[2289]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 21 10:11:49 STORAGE openvpn@UNS[2289]: Cannot initialize LZO compression library Nov 21 10:11:49 STORAGE openvpn@UNS[2289]: Exiting due to fatal error 5. rebuild lzo with modified PKGBUILD as noted above to provide, replace, and conflict with lzo. 6. Upgrade package lzo. 7. restart openvpn and note there are no longer any errors as openvpn now sees that lzo provides lzo. Reference: https://wiki.archlinux.org/index.php/PKGBUILD#provides |
This task depends upon
Closed by Anatol Pomozov (anatolik)
Tuesday, 30 December 2014, 19:09 GMT
Reason for closing: Fixed
Additional comments about closing: Previous reopen was related to an ARM specific issue
Tuesday, 30 December 2014, 19:09 GMT
Reason for closing: Fixed
Additional comments about closing: Previous reopen was related to an ARM specific issue
https://www.archlinux.org/todo/lzo2-lzo-rename/