-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
[WIP] filezilla: 3.31.0 -> 3.40.0, libfilezilla: 0.13.0 -> 0.15.1 #56883
Conversation
@tokudan this is not working for me, I'm getting assertion failures, e.g.:
If I untick "Show this dialog" and click "Continue", the main window seems OK, but try clicking the Session Manager: it would segfault. |
Ok, good to know that it's breaking somewhere else as well. I probably won't be able to work on master or release-19.03 till it's matured a bit, so I'll leave this for now and will come back later in a couple of weeks. If someone wants to pick it up in the meantime, feel free. |
@tokudan I could push my changes here or start a new PR, let me know if it is OK to edit your PR commits. The changes simplify things quite, but FileZilla still segfaults. I forgot to add the last message I see once it segfaults:
|
@jokogr I don't mind if you hijack this PR, I wont get to work on 19.03 or master soon. |
OK, my commits are mostly cleaning things up:
Unfortunately it has still assertion failures and it segfaults whenever Session Manager pops up. A quick FileZilla code finds |
cc @peterhoeg in case he has the solution already |
Filezilla 3.42.1 is already on master, let's close this :) |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)The filezilla project has migrated their source away from sourceforge, so the source is now pulled from their subversion repo. This also required some additional preparation with the auto*-tools.
The download link to their current source code uses some changing hash and timestamp, so it's probably unreliable.
Important: I've only verified these changes against release-18.09 and it's working for me.
Building against master and the new release-19.03 branch results in SIGSEGV when starting filezilla, which I believe is due to some incompatible mixing of the building and running gtk libraries, with similar output as observed in #56832