A new major version of lzo was released the 17 Oct 2005 It's supposed to be much better - the FE lzo package needs a refresh
Does this cause a so-name bump? If so please be sure that you identify and rebuild EVERYTHING that relies upon it before the packages are signed and pushed.
That's why doing it before the FC5 FE mass rebuild is better than doing it after it
It's not a soname change. It's a filename change : %{_libdir}/liblzo2.so %{_libdir}/liblzo2.a We now have liblzo2. Do we create a new liblzo2 package ? liblzo and liblzo2 wouldnt conflict : include files are in different path (%{includedir}/lzo*.h vs %{_includedir}/lzo) and libs are different (liblzo.so vs liblzo2.so). Does everything can migrate easily to liblzo2 without pain ? (have to check "in some other repository" also). I got a working spec file for a liblzo-2.02 package. Comments appreciated.
please attach the spec so people can test-rebuild stuff
Created attachment 123417 [details] lzo-2.02-1 spec file. I have to find out if the asm code on i386 wont make the package i686-only but here it is.
lzop seems to build fine with this lzo version. I'll be able to update whenever lzo 2 goes in. Thanks!
I've taken over as maintainer of lzo quite some time and somehow have missed this bug. lzo has already been at 2.02 for some time now, closing.