> As I said, I trust you when you said it's libeatmydata related, and the
> message makes it pretty clear :)
Don't trust anybody :-), several times I found that the /etc/hosts in
some autobuilders had a wrong IP associated with the hostname,
and sometimes this was the reason some packages failed f
On Wed, Jan 11, 2017 at 12:35:39AM +0100, Santiago Vila wrote:
> The bug should be reproducible with sbuild on a single CPU machine.
>
> I have described my building environment here:
>
> https://people.debian.org/~sanvila/my-building-environment.txt
You're build env looks very sane to me, and I
On Tue, Jan 10, 2017 at 11:30:48PM +0100, Mattia Rizzolo wrote:
> I still don't get this bug and why I can't reproduce it in any chroot
> with eatmydata (and tbh it has very low priority in my task list, so
> it's not like I ever looked at it since my last message), but anyway.
The bug should be
Hi Valentin,
I still don't get this bug and why I can't reproduce it in any chroot
with eatmydata (and tbh it has very low priority in my task list, so
it's not like I ever looked at it since my last message), but anyway.
On Tue, Jan 10, 2017 at 10:56:08PM +0100, Valentin Lorentz wrote:
> Matti
On 20/08/2016 23:15, Santiago Vila wrote:
> On Sat, Aug 20, 2016 at 11:05:26PM +0200, Val Lorentz wrote:
>
>> On 20/08/2016 22:45, Santiago Vila wrote:
>>> AFAIK, it's the dynamic linker (ld.so) who shows the error, not ping
>>> itself.
>>
>> Probably because ping uses setuid.
>> http://stackove
On Sat, Aug 20, 2016 at 11:05:26PM +0200, Val Lorentz wrote:
> On 20/08/2016 22:45, Santiago Vila wrote:
> > AFAIK, it's the dynamic linker (ld.so) who shows the error, not ping
> > itself.
>
> Probably because ping uses setuid.
> http://stackoverflow.com/a/11148167/539465
Actually, in Debian it
On 20/08/2016 22:45, Santiago Vila wrote:
> AFAIK, it's the dynamic linker (ld.so) who shows the error, not ping
> itself.
Probably because ping uses setuid.
http://stackoverflow.com/a/11148167/539465
> Could maybe the test suite discard all lines from stderr containing
> the string "libeatmyda
On Sat, Aug 20, 2016 at 10:30:22PM +0200, Valentin Lorentz wrote:
> Hello, upstream here
Hi Valentin, Santiano :)
> $ eatmydata ping -W 1 -c 1 127.0.0.1 > /dev/null
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be
> preloaded (cannot open shared object file): ignored.
This is i
On Sat, Aug 20, 2016 at 10:30:22PM +0200, Valentin Lorentz wrote:
> Hello, upstream here
>
> This issue is caused by the test suite calling a command which uses
> ping. Calling ping from a shell shows the same error:
>
> $ eatmydata ping -W 1 -c 1 127.0.0.1 > /dev/null
> ERROR: ld.so: object 'lib
Hello, upstream here
This issue is caused by the test suite calling a command which uses
ping. Calling ping from a shell shows the same error:
$ eatmydata ping -W 1 -c 1 127.0.0.1 > /dev/null
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be
preloaded (cannot open shared object fil
Package: limnoria
Version: 2016.06.29-2
Severity: wishlist
Hello Mattia.
I can't build this package from source when using eatmydata.
I'm using sbuild and a file /etc/schroot/chroot.d/stretch like this:
[stretch]
type=directory
description=Debian stretch
directory=/chroot/stretch
groups=sbuild
11 matches
Mail list logo
