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

Upgrade method for broken sample paths #3533

Closed
lukas-w opened this issue May 6, 2017 · 3 comments
Closed

Upgrade method for broken sample paths #3533

lukas-w opened this issue May 6, 2017 · 3 comments
Labels
Milestone

Comments

@lukas-w
Copy link
Member

lukas-w commented May 6, 2017

#1719 introduced a bug that made all sample paths being saved as absolute in project files (reported in #3491).

#3510 fixed the regression, but we should try to find a method to fix/relativize samples from existing projects since 1.2.0-rc2.

@lukas-w lukas-w added this to the 1.2.0 milestone May 6, 2017
@tresf
Copy link
Member

tresf commented May 7, 2017

Started the upgrade logic here tresf@08581c5, but something's broken. Can't get the debugs to fire. Second set of eyes appreciated.

@tresf
Copy link
Member

tresf commented May 7, 2017

I had run into a self-inflicted snag checking for newer project versions. I'm glad I did... Although first instinct is to honor this logic, making samples relative can fix an annoyance occurred when the LMMS WORKING DIRECTORY is misconfigured. So I'm proposing to run this upgrade task on the load of each project regardless of version; thus it can't really be referred to as an "upgrade" task. PR available in #3540. Thoughts and testing welcome.

@tresf
Copy link
Member

tresf commented May 11, 2017

Fixed via #3510, we just didn't know it at the time. Explanation here: #3540 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants