Cannot connect when using Arch Linux about libnfs

[evanpurkhiser]

After much git bisecting (turns out libnfs-1.9.2 also works fine if you symlink libnfs.so.1.2.1 -> libnfs.so.4) I've located the commit that seems to have introduced the issue: f893b68

At least, the issue for libnfs-1.9.3

[evanpurkhiser]

d5f7880 fixes the issue in libnfs-1.9.3. Applying that as a patch onto the libnfs-1.9.3 tag and building works. Looking into what the issue is in the most recent git version because why not :p

[evanpurkhiser]

Bisecting from master...libgit-1.9.3 (with d5f7880 moved just before that) leads me to 1c1e09a.

That's all development though, so I'm sure the developer working on IPv6 support should get everything sorted before the next release.

And again it looks like the issue present in 1.9.3 has already been resolved, but using a git build right now isn't possible because of the previously mentioned issue. So it looks like there really isn't anything here to report, besides hopefully shedding some light for anyone else running into this issue in 1.9.3. All we can do now is wait and apply d5f7880 to fix the problem.

Please feel free to close the issue or whatever the proper action would be for this. Thanks!

[graysky2]

Thank you for your work on this Evan. A new version really needs to be released ASAP.

Evan - Perhaps you should send a pull request?

[evanpurkhiser]

Unfortunately there's not really a PR I can open. Applying d5f7880 to the 1.9.3 tag fixes the problem, so it's technically fixed in upstream, a new version hasn't been released yet though (last I checked there was a different issue in the latest git version though).

[graysky2]

I understand. I opened a flyspray (see your thread if you're interested).

[sahlberg]

I plan to release a new version of libnfs in a few days.

On Mon, Jun 16, 2014 at 3:30 PM, Evan Purkhiser [email protected]
wrote:

Unfortunately there's not really a PR I can open. Applying d5f7880
d5f7880
to the 1.9.3 tag fixes the problem, so it's technically fixed in upstream,
a new version hasn't been released yet though (last I checked there was a
different issue in the latest git version though).

—
Reply to this email directly or view it on GitHub
#78 (comment).

[graysky2]

Thanks for the update and for all the work you do on this project.

[sahlberg]

As far as I can tell this problem should be resolved in 1.9.4 which I just sent out.
Thanks. And closing this issue.

[sahlberg]

As far as I can tell this problem should be resolved in 1.9.4 which I just sent out.
Thanks. And closing this issue.