I've no reason to think that the patch I supplied here, some years ago now, was
anything but a good idea, but it seems that my coworker Susi Berrington has
found the real cause of my pain. According to:
https://github.com/systemd/systemd/issues/2039 (Change default value of
RemoveIPC in
> A new bug is better
Agreed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856439 (
fakeroot doesn't detect and handle message queue and semaphore id collision
> 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
On Fri, Feb 24, 2017 at 02:58:41AM +, Martin Dorey wrote:
> 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
On Mon, Feb 20, 2017 at 05:31:15PM -0800, Martin Dorey wrote:
> I enclose a patch to address that.
Thanks!
> I don't know at this juncture whether it fixes my original problem.
> I doubt it but fingers crossed.
Good luck.
Package: fakeroot
Version: 1.20.2-1
Severity: normal
Tags: patch
Dear Maintainer,
I'm trying to track down an intermittent failure that originally presented like
this:
dh_md5sums
dh_builddeb -- -Znone
dpkg-deb: building package `mercury-main-4604p00p1099' in
6 matches
Mail list logo
