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

Remove 2.071.x compatibility code #1998

Merged
merged 3 commits into from
Dec 12, 2017
Merged

Conversation

s-ludwig
Copy link
Member

No description provided.

@s-ludwig
Copy link
Member Author

Meson failing again?

@s-ludwig
Copy link
Member Author

May be an issue with the tag_version script, since it started to fail in 38d5da2 with:

Meson encountered an error in file meson.build, line 1, column 0:

Subproject_dir must not contain a path segment.

I'll have a look.

@s-ludwig
Copy link
Member Author

Hm, it's actually still mesonbuild/meson#2719 and there is just a new Meson version that still has the issue.

@@ -52,7 +52,7 @@ matrix:

before_install:
- pyenv global system 3.5
- pip3 install 'meson>=0.42,!=0.43'
- pip3 install 'meson>=0.42,!=0.43,!=0.44'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pip install 'meson==0.42' would be a lot safer ...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's true, I was also thinking about that. I guess the idea behind that was to not forget about this issue and enforce getting back to the latest release at some point. To me it would be fine to keep it like this for another version, but then I'd also rather like to go with ==0.42 to avoid this becoming a regular distraction.

@dlang-bot dlang-bot merged commit 935385a into master Dec 12, 2017
@s-ludwig s-ludwig deleted the remove_compatibility_code branch December 12, 2017 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants