Bug #4887
closed
nonexistent lib file - (lightsquid not work)
Added by Alex . over 9 years ago.
Updated about 9 years ago.
Affected Architecture:
i386
Description
lightsquid not work - nonexistent lib
#perl not work
ln -s /lib/libutil.so.9 /lib/libutil.so.8
#GD not work
ln -s /lib/libz.so.6 /lib/libz.so.5
ln -s /usr/local/lib/libfreetype.so.6 /usr/lib/libfreetype.so.9
v2.2.3&v2.2.4
#squid2
ln -s /usr/lib/libssl.so.7 /usr/lib/libssl.so.6
ln -s /lib/libcrypt.so.5 /usr/lib/libcrypto.so.6
im using lightsquid with squid3 and works fine on 2.2.4
As already noted on another bug - please, remove the unmaintained, horribly broken and dead Squid2 package. Noone should use this.
Alexander H.: Do not do similar things. It causes more breakage that it fixes!
OK
Today checked the update from version 2.1.5 to 2.2.4 on a clean system (vmware), everything works. I think the problem has accumulated during the work of this system (2.0.x -> ... -> 2.2.4).
Alex . wrote:
I think the problem has accumulated during the work of this system (2.0.x -> ... -> 2.2.4).
2.0.x was using /usr/local prefix. 2.1/2.2 is using the craptastic PBI with /usr/pbi/$packagename-$arch/. In between that, PBI being super-idiotic and various craft being left over that PBI picks up for god knows what reason, yes, there lies the problem.
- Assignee set to Jim Thompson
So can we kill this?
pkg(ng) is coming to 2.3.
- Status changed from New to Assigned
- Status changed from Assigned to Resolved
- Target version changed from 2.2.5 to 2.3
yes this can go, fixed in 2.3 by removing PBI.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Kill Bill 
Updated by 
Updated by