Looks like the
lzo PKGBUILD has
$this->bbcode_second_pass_code('', 'pkgname=lzo')
but then has
$this->bbcode_second_pass_code('', 'provides=("lzo2=$pkgver")
replaces=('lzo2')
conflicts=('lzo2')')
On my alarm installation on pogo e02 I have the same problem with openvpn not working due to lzo2. However, on my system the pkgname shows as lzo which matches the above and is in keeping with the
rename of lzo2 to lzo . But as can be seen above it will "provide" lzo2. So even though all packages have been changed to depend on lzo, the lzo package itself still "provides" lzo2 which is not in keeping with the rename of lzo2 to lzo.
I've installed
abs, copied /var/abs/core/lzo to my home directory and built it using the following modified in the PKGBUILD using
hydro's suggestion as a base. It's working great so far:
increment package release:
$this->bbcode_second_pass_code('', 'pkgrel=4')
update provides, replaces, conflicts with lzo. Some users may still have lzo2 installed while others may have lzo. To address this just include both in provides, replaces, conflicts.:
$this->bbcode_second_pass_code('', 'provides=("lzo2=$pkgver" "lzo=$pkgver")
replaces=('lzo2' 'lzo')
conflicts=('lzo2' 'lzo')')
add CFLAG to allow building on arm otherwise tests fail on my pogo e02 and it doesn't build:
$this->bbcode_second_pass_code('', 'CFLAGS="-DLZO_DEBUG" ./configure --prefix=/usr --enable-shared')
This problem is in upstream archlinux. I've been searching everywhere I can think of to determine how to submit a change to this PKGBUILD in upstream but cannot locate it. If anyone knows how let me know.
Also, since I had to add a CFLAG to get it to build on pogo e02 I believe this can be added to archlinuxarm PKGBUILDs.