[Pkg-ltsp-devel] Bug#765694: hardcoded libeatmydata path now is wrong

[Vagrant Cascadian]

On 2014-10-27, Petter Reinholdtsen wrote:
> We do this now in Debian Edu, but there is something wrong with the
> new ltsp version.  I see lots of "ERROR: ld.so: object
> 'libeatmydata.so' from LD_PRELOAD cannot be preload (cannot open
> shared object file): ignored" messages in the installation log.
>
> The strange thing is that later in the installation, exim4-config
> trigger #762103, which is supposed to be fixed in the newer eatmydata
> package entering testing yesterday.
>
> Is --eatmydata working now for you when using Jessie?  It isn't for me
> any more.

I'll try again, now that eatmydata has migrated to jessie.

It worked with amd64 server with and amd64 chroot with newer versions in
all places.

I had troubles with an amd64 server with an i386 chroot, with the newer
version of libeatmydata.

It didn't work with older versions of eatmydata at all, which is
unfortunate.

So I've had mixed results.

It dramatically improves speed building LTSP chroots, so I'd really like
to get it working more reliably, but figured even in the imperfect state
it was better to move forward where it works in some cases than leave it
totally broken.

live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/attachments/20141027/0ed5527e/attachment.sig>