Unable to build a .deb package

[patrick330602]

• Your Windows build number: 10.0.16193.1001

• What you're doing and what's happening:
  I am trying to build a Debian package on Bash On Windows using command sudo debuild -us -uc

• What's wrong / what should be happening instead:
  It is expected to be built properly, however, following errors is produced:

dpkg-buildpackage -rfakeroot -D -us -uc
dpkg-buildpackage: warning: using a gain-root-command while being root
dpkg-buildpackage: source package wslu
dpkg-buildpackage: source version 0.14-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Patrick Wu <[email protected]>
dpkg-source --before-build wslu-0.14
dpkg-buildpackage: host architecture amd64
fakeroot debian/rules clean
fakeroot, while creating message channels: Function not implemented
This may be due to a lack of SYSV IPC support.
fakeroot: error while starting the `faked' daemon.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 1
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -D -us -uc failed

[sunjoong]

@patrick330602 - In #2013 (comment), there is a comment saying "System V semaphores and shared memory were implemented during Creators Update but message queues were not."; This means you cannot use fakeroot yet, and so dpkg-buildpackage -rfakeroot -D -us -uc failed.

And, I found a interesting comment too; #8 (comment). I don't understand that comment, but think that might (or might not) be helpful to you.

[Aerocatia]

Rebuilding fakeroot to use tcp will work around your problem.

[patrick330602]

@Vaporeon Thanks! this solved my issue

[patrick330602]

@sunjoong nice to know about it, and I solved my problem. Thanks!

[therealkenc]

dpkg-buildpackage: warning: using a gain-root-command while being root

Not faking it will also "work around" this particular problem. --root-command=sudo

[ehrlich-b]

--root-command didn't work for me -rsudo did.

[tjwebb]

#2132 (comment)

Rebuilding fakeroot to use tcp will work around your problem.

Let's pretend that some of us arrived at this thread by googling our error message, and might have no clue what this means or how to accomplish it. How might one go about "rebuilding fakeroot to use tcp"?

[ddamw]

I had the same question as @tjwebb and found out you can run:
sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

This solved the issue for me on WSL.

source: https://superuser.com/questions/1236338/a-workaround-which-lets-you-use-mk-build-deps-and-fakeroot-on-the-windows-li

[OrangeDog]

Is it possible for fakeroot-tcp to be the default alternative on WSL?

[ddamw]

For WSL in general, this is not possible to my knowledge. This is because fakeroot is managed by the Linux distribution you are running and not by WSL itself.

If you are not running Debian or a derivative, you can always rename the original fakeroot to something else and then rename (or symlink) fakeroot-tcp to fakeroot.