You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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.
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.
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):
Repro (Arch):
The text was updated successfully, but these errors were encountered: