On Thu, Oct 16, 2014 at 12:35 PM, Klaus Ethgen <[email protected]> wrote: > The new eatmydata put the .so file to another location so while > upgrading the system, there will be many of the following error messages > when apt is run with eatmydata:
I feel you are doing something really wrong in using apt with eatmydata. I hope you will not blame someone different to yourself if some bad things occur to your system. > ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from > LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. > > The upgrade process should put a link in the old location and remove it > only if LD_PRELOAD is populated with the new location. Well, this would mean change the content of LD_PRELOAD of a running process (apt and children), not something wise to do. Actually the content of LD_PRELOAD is changed once you restart apt, not before. I could drop a symlink, but when I'm going to remove it? I can't think of anything sane to do here. A better thing to do wuold be change the eatmydata script in wheezy to do something more clever (e.g. by using the script currently in experimental) so even the libeatmydata library path change in the middle of the upgrade ld would know where to find it. Either way, I'd be for just ignore the warning and go ahead. I'll think it better, but currently I'm overload. -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo
signature.asc
Description: GooPG digital signature
