Skip to content
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

Fix checks with os.path.realpath() for systems with symlinked paths #1051

Merged
merged 2 commits into from
Sep 8, 2015

Conversation

markbastiaans
Copy link

I'm working on getting a recent version of Octoprint (1.2.6) packaged for Synology NASes in SynoCommunity/spksrc. I've gotten it to work after some tinkering, but it needed two trivial fixes to work with Synology's habit of putting packages in a symlinked location. Specifically, two checks using os.path.realpath() fail on Synology's OS while they shouldn't be.

I've not filed a bug report for this yet, let me know if I should. I've tested the fix on Synology only but I think the fix is so trivial that it won't will negatively impact other platforms.

@foosel
Copy link
Member

foosel commented Sep 8, 2015

Thanks for spotting this. Bug ticket is not necessary, I'll put that into the CHANGELOG with reference to the PR. Want me to also add you to the AUTHORS.md file while at it or do it yourself? :)

@markbastiaans
Copy link
Author

I've added my name to the authors file myself. Cheers!

foosel added a commit that referenced this pull request Sep 8, 2015
Fix checks with os.path.realpath() for systems with symlinked paths
@foosel foosel merged commit 0346002 into OctoPrint:devel Sep 8, 2015
@foosel
Copy link
Member

foosel commented Sep 8, 2015

Perfect, thanks again!

@markbastiaans
Copy link
Author

@foosel, would it be possible to merge this PR into the upcoming maintenance release? I'm working on a new version of the OctoPrint package for Synology NASes. Basing that package on a tagged release would make that a lot easier.

Thanks in advance!

@foosel
Copy link
Member

foosel commented Dec 4, 2015

@markbastiaans Just did. Planning on releasing 1.2.8 monday or tuesday (if nothing horrible happens again...)

@markbastiaans
Copy link
Author

Thanks @foosel!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants