-
Notifications
You must be signed in to change notification settings - Fork 30
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
Source distribution cannot include symlinks #284
Comments
In GitLab by [Gitlab user @tristanvb] on Mar 8, 2018, 07:52 I may be mistaken about the reason for our workaround which I mentioned in !295 i.e. https://gitlab.com/BuildStream/buildstream/blob/master/tests/sources/local.py#L58 documents this as a problem with The datafiles upstream bug report is here. I've commented on the pypa upstream bug report here, which is currently closed. |
In GitLab by [Gitlab user @tristanvb] on Mar 8, 2018, 07:53 mentioned in merge request !295 |
In GitLab by [Gitlab user @cs-shadow] on Oct 10, 2019, 13:46 Since https://gitlab.com/BuildStream/buildstream/merge_requests/1629, symlinks are created on the fly and we shouldn't have any symlinks in BuildStream source and/or tests. |
In GitLab by [Gitlab user @cs-shadow] on Oct 10, 2019, 13:46 closed |
See original issue on GitLab
In GitLab by [Gitlab user @jmacarthur] on Mar 7, 2018, 18:43
Reporting as minor as I don't know if this is really a problem with BuildStream's CI setup or with
setuptools
.!295 added a test which used an
import
element of a directory which contained a symlink. However,setup.py sdist
will not capture that file, giving this warning, easily missed:Since all our CI tests create a source distribution and test that we ended up with an unfortunate situation where tests passed locally but not on CI. Direct import of a directory (not a tarball or zip) containing a symlink seems like something we should test but we can't at the moment. There don't appear to be any options to sdist to include symlinks in the archive.
I can't think of a clean solution, but work-arounds are:
The text was updated successfully, but these errors were encountered: