> Good luck. Sadly, after several days of parallel package building later, I've had another failure. Happily, now errno's been preserved by my previous patch, I have A New Clue:
FAKEROOT: r=-1, received message type=1, message=3 FAKEROOT, get_msg: Identifier removed errno=43, EINTR=4 On this system, that's: martind@ussw-cbld00:~$ grep -w 43 /usr/include/asm-generic/errno.h #define EIDRM 43 /* Identifier removed */ martind@ussw-cbld00:~$ Now through early evening fog I see that the message queues and the semaphore are being generated with a random key. Collisions with existing keys aren't detected. I have a patch that I hope will detect that and retry. Would you like that here or in a new bug? Including the first patch or assuming it's applied first or against the baseline version? Any way is easy for me. I imagine the BTS will just do the right thing with a text attachment but five minutes of googling hasn't confirmed that's how to submit a patch to an existing Debian bug. Waiting a week for the patch to dis/prove itself would be perfectly sensible, but I'm happy to embarrass myself if you're happy to look at it before then.
