Libraries upgrading policy (Was: Bug#9826)
My problem I have submited as lprng bug (9826) in May 97. I have reply from
> I have never experienced this problem. Please discuss this at
Maybe it's more general. This bug I have experienced twice: in May and now.
After I upgraded lib's (all was Ok with ldconfig) - I've got in /var/log/lp-errs:
/usr/bin/gs: can't load library 'libXt.so.6'
/usr/sbin/ljet4-filter: /usr/bin/gs -q -dSAFER -dNOPAUSE -r600 -sDEVICE=ljet4 -sOutputFile=- - failed
gs works from terminal without problems.
I changed real filter for lpd to my script:
and in /tmp/filter.test.out are:
They are defaults in /usr/sbin/lpd and I don't see path for /usr/X11R6/lib.
OK lpd don't need it:
19:55:11 3:mirek@dionizos~$ ldd lpd
libc.so.5 => /lib/libc.so.5
But gs as filter don't work. I run ldconfig twice and more :(
I have /usr/X11R6/lib in /etc/ld.so.conf and run ldconfig without
problems. Probably lpd runs its childs whith old ld.so.cache?
I have 3 solutions for this problem
1) down and up lpd demon
2) Set LD_LIBRARY_PATH in /etc/lpd.conf
3) Set LD_LIBRARY_PATH in filter script
I don't see any of those solusion are good for future system upgrades.
I have questions:
1) lprng isn't full debianized?
2) How to find those not explicite dependiences in packages?
3) Should I do down&up all daemons after libraries upgrade?
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .