* Antonio Terceiro <terce...@debian.org> [12-05-2014 12:32 EEST]: > hah, that's it, that chroot did have eatmydata configured as a > command-prefix! I have now removed eaymydata usage, and I can narrow > down the problem to: > > $ faketime +1day date > Tue May 13 12:06:09 UTC 2014 > $ eatmydata faketime +1day date > shm_open: Bad address > $ faketime +1day eatmydata date > shm_open: Bad address > > I can also reproduce that problem on my main system, so it is not > specific to the chroot configuration.
I also had the same problem with eatmydata causing faketime to fail. I built and installed an updated eatmydata from http://anonscm.debian.org/cgit/users/mapreri-guest/pkg-libeatmydata.git and faketime no longer fails. $ faketime '1 day ago' /bin/date Tue Sep 16 00:04:35 UTC 2014 $ eatmydata faketime '1 day ago' /bin/date Tue Sep 16 00:04:38 UTC 2014 $ dpkg -s eatmydata |grep ^Version Version: 82-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
