Bug#765695: hardcoded libeatmydata path now is wrong
Hi Mattia, On Fr, 2014-10-17 at 14:01 +0200, Mattia Rizzolo wrote: Package: mini-buildd Version: 1.0.4 The new upload of libeatmydata changed the position of the actual library (due to now supporting Multi-Arch). yes, thanks. I also already noticed that ;). You appear to be using /usr/lib/libeatmydata/libeatmydata.so directly: http://sources.debian.net/src/mini-buildd/1.0.4/mini_buildd/models/repository.py/?hl=417#L417 http://sources.debian.net/src/mini-buildd/1.0.4/mini_buildd/models/repository.py/?hl=432#L432 I don't know what's the purpose of it (given that you don't depends/recommends/suggest eatmydata), but for sure now it'll do just nothing. No, these are snippets for the build chroot's setup, so it actually does something (albeit no more for sid/jessie builds right now). FWIW: I experienced dramatically increased install times on builds without eatmydata and 'aufs' chroots. As 'aufs' is the default, this is the reason why the eatmydata snippet is also per default enabled. Again, this snippet is _not_ hardcoded, rather a hardcoded default. You can change/fix it at any time yourself changing the resp. Distribution instance (chroot setup script). Please set the severity of this bug accordingly. I'd suggest you to just use libeatmydata.so instead of using the full path. Alas, this is no possible. As ye olde eatmydata does not install in standard locations, I needed the full path to make it work. Hth! S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765695: hardcoded libeatmydata path now is wrong
On Di, 2014-10-21 at 11:24 +0200, Stephan Sürken wrote: Hi Mattia, (...) I'd suggest you to just use libeatmydata.so instead of using the full path. Alas, this is no possible. As ye olde eatmydata does not install in standard locations, I needed the full path to make it work. ahh, and yes, I am currently thinking about a script goblin similar to that outlined in my bug report... So if you have an idea how to do this (i.e., posix shell snippet run as root, installing _and_ enabling eatmydata, working for all versions of eatmydata) simpler/better, I'd love to hear ;). Thx! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765695: hardcoded libeatmydata path now is wrong
Package: mini-buildd Version: 1.0.4 The new upload of libeatmydata changed the position of the actual library (due to now supporting Multi-Arch). You appear to be using /usr/lib/libeatmydata/libeatmydata.so directly: http://sources.debian.net/src/mini-buildd/1.0.4/mini_buildd/models/repository.py/?hl=417#L417 http://sources.debian.net/src/mini-buildd/1.0.4/mini_buildd/models/repository.py/?hl=432#L432 I don't know what's the purpose of it (given that you don't depends/recommends/suggest eatmydata), but for sure now it'll do just nothing. Please set the severity of this bug accordingly. I'd suggest you to just use libeatmydata.so instead of using the full path. -- 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: Digital signature
