Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to call fakeroot-tcp after 1809 #3629

Closed
M1K8 opened this issue Oct 23, 2018 · 4 comments
Closed

Unable to call fakeroot-tcp after 1809 #3629

M1K8 opened this issue Oct 23, 2018 · 4 comments
Labels

Comments

@M1K8
Copy link

M1K8 commented Oct 23, 2018

Windows Version: Microsoft Windows [Version 10.0.17763.55]

Since updating to 1809, I have been unable to run fakeroot-tcp, meaning I have been unable to successfully run anything that requires a fakeroot environment, such as building the "yay" package manager. It appears to have something to do with the Windows firewall, as a prompt to allow "faked" appeared when I first ran fakeroot. Allowing it through both public and private firewalls does not help the issue.

I have attached strace logs for both Ubuntu and Arch below.
fctpUbuntu.log
fctpArch.log

Repro (Ubuntu):

  1. Install fakeroot
  2. Run sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp
  3. Run fakeroot. Observe error.

Repro (Arch):

  1. Install prebuilt fakeroot-tcp
  2. Attempt to build the yay package manager
  3. Observe error when fakeroot is ran.
@therealkenc
Copy link
Collaborator

The strace doesn't appear to be threaded (-f). It will probably just show connection refused but it's a start.

@M1K8
Copy link
Author

M1K8 commented Oct 23, 2018

Apologies, please find the updated file here:
tcpUbuntu.log

@kayhayen
Copy link

I can call it with current 1910 just fine, however I get a firewall prompt for each run of a pbuilder, each in a different build directory. how to setup the rule to allow it? Seems to work even if I ignore the firewall prompt, but they are annoying.

Copy link
Contributor

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants