-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
git-lfs does not appear to work with TKL-Gitlab-14.1 #810
Comments
Thanks for the bug report. I'm guessing you have, but can you please confirm that you've double checked the GItLab git-lfs docs and have configured everything as they suggest? Regardless, we hope to be releasing our v14.2 version (which will include the latest GitLab stable release) sometime really soon. |
Yep. Reading the manual would help. That's what I get for trying to do stuff late in the day. |
Just popping in to note that following the instructions does not appear to have resulted in a working setup. I don't have as much time to track the issue down as I'd like, so while I'll be leaving this closed, I'd encourage you guys to take the time to figure out how/why it doesn't seem to be working I'm sure I'm missing something obvious, but it might make for a good entry into some sort of "Errata" page, e.g. "Don't forget to X or else you won't be able to get git-lfs working." Back to work for me! |
Hmm, thanks for the feedback. Considering that you can't get it working, let's reopen this. |
I'm leaving this open until we properly investigate, but we're going to skip it for v14.2. Debian have just released Stretch (aka Debian 9), so we need to get a wriggle on! After v14.2, v15.0 will be the next release and will be based on Debian Stretch. |
That's perfectly fine. I'll take another stab at it soon at home and see if I can't figure out what all is missing that's needed to do this. |
Really not sure what to test or where to go next with this. This might be related to #686 and #758, but I'm not sure. It's quitting time here, so I can't be more verbose today.
The text was updated successfully, but these errors were encountered: