added a snippet to actually install the lfs package after adding the repository with the quick curl command

[w0000000t]

Fixes #replaceWithIssueNr, fixes #replaceWithIssueNr

Your PR description here.

[boring-cyborg]

Thanks for opening this pull request!

Please check out our contributor checklist and check if Travis or Codacy found any issues with your PR. Also make sure your commits are signed, and that you applied Bisq's code style and formatting.

A maintainer will add an is:priority label to your PR if it is up for compensation. Please see our Bisq Q1 2020 Update post for more details.

[ripcurlx]

@w0000000t But isn't that explained on https://git-lfs.github.com/ on how to install git lfs in the LInk "Install v3.02 via PackageCloud (Linux)? Also your solution would only work on Linux and not on all other supported platforms. Or was that the problem, that you followed the guide on the git lfs page and it didn't work for you in the end?

[w0000000t]

Hello, and thank you for getting back to me.
I did follow that link, which on my Linux VM brought me to https://packagecloud.io/github/git-lfs/install
There, I used the oneliner provided for the deb quick install, yet after that I got the error message as per my PR.
I had to improvise for a while and at the end thought of manually running the apt command first to search for a lfs package and then to actually get lfs installed, that is the reason I thought it might be useful to include my findings in the repo.

[ripcurlx]

Hello, and thank you for getting back to me. I did follow that link, which on my Linux VM brought me to https://packagecloud.io/github/git-lfs/install There, I used the oneliner provided for the deb quick install, yet after that I got the error message as per my PR. I had to improvise for a while and at the end thought of manually running the apt command first to search for a lfs package and then to actually get lfs installed, that is the reason I thought it might be useful to include my findings in the repo.

Sorry for my late reply on this. Maybe add the note on which OSes this workaround would fix the issue (it is obvious for most, but probably good to mention it anyways)

[w0000000t]

Sorry for my late reply on this. Maybe add the note on which OSes this workaround would fix the issue (it is obvious for most, but probably good to mention it anyways)

I have very limited GH skills, and only ever access its functions from the web UI, so I should have made the requested updates, please let me know if something is amiss

[ripcurlx]

@w0000000t Yes, Git/GitHubs workflow can be overwhelming in the beginning. For the future to improve your commit messages please have a look at @cbeams article on git commit messages: https://cbea.ms/git-commit/

For this time I'll squash your commits into one during the merge.

[ripcurlx]

ACK

[boring-cyborg]

Awesome work, congrats on your first merged pull request!